SNMP Configuration and Management Manual

NonStop NET/MASTER Trap Subagent
SNMP Configuration and Management Manual—424777-006
10-3
RFC Compliance
Figure 10-2 shows how the NonStop NET/MASTER Trap Subagent fits into this
environment. The subagent consists of two NCL procedures, GENTRAP and
NMMTRAP, which are invoked from EMSPROC or an RMS message handler:
•
GENTRAP assembles an SNMP trap from an EMS event and calls NMMTRAP for
handling communications with the SNMP agent. If you are fluent in NCL and
ASN.1, you can define your own trap MIB and then modify GENTRAP to
correspond. The MIB that corresponds to the trap defined in GENTRAP initially is
the EMS Trap MIB.
•
NMMTRAP contains procedures for opening and closing sessions with the SNMP
agent and for forwarding traps to the SNMP agent. Do not modify this NCL code.
The subagent sends trap messages to the SNMP agent for forwarding to SNMP
managers, which can interpret the traps after the EMS Trap MIB has been installed.
RFC Compliance
The EMS Trap MIB complies with RFC 1215, A Convention for Defining Traps for Use
with the SNMP.
Installation
This subsection describes how to install the NonStop NET/MASTER Trap Subagent.
Dependencies
The following products must be configured and running for the NonStop NET/MASTER
Subagent to operate properly:
•
SNMP agent (D21 or later).
•
EMS (D21 or later). The ASN.1 source code file (EMSMIBA) containing the EMS
Trap MIB definition is shipped with EMS.
•
NonStop NET/MASTER (C30 or later). These NonStop NET/MASTER Trap
Subagent files are distributed with NonStop NET/MASTER:
°
GENTRAP: NCL procedure for translating EMS events into SNMP traps.
°
NMMTRAP: NCL library that handles communications between the subagent
and the SNMP agent.
°
TESTSEND: NCL procedure that generates an example trap.
•
At least one SNMP manager communicating with the SNMP agent that is capable
of displaying values for the variable bindings of enterprise-specific traps.