Defining SNMP Traps

In a Simple Network Managed Protocol (SNMP) based management solution each monitored computer on the network contains a processing agent that reports information back to some central management software. These nodes can be computers (workstations or mainframes), routers, bridges, and even printers.

If the company requires tight integration between its SNMP management software and its WebSphere MQ network management solution (MainView Middleware Monitor), the BMC MIB implementation provides that functionality and support for SNMP. This feature provides SNMP consoles with the provision of an SNMP MIB.

Using SNMP, administrators can retrieve and modify the value of management information. They can also detect and respond to defined events in the system such as hardware or software failures. The definitions for the management information and these events are specified by the Management Information Base (MIB) model. MIBs are specifications containing definitions of management information so that network systems can be remotely monitored, configured, and controlled.

MainView Middleware Monitor provides two Perl scripts to send an SNMP trap to a specific destination. These scripts are named BMC_SNMPTRAP.pl and qpasatraps.pl. Use of the qpasatraps.pl script has been deprecated and is only included for reference for customers that have used that script with previous versions of the product. Customers should migrate to the BMC_SNMPTRAP.pl script.

Along with other SNMP management software packages, MainView Middleware Monitor works with CA Unicenter, HP OpenView IT/Operations, HP NetView, Netcool, and Tivoli.