ADTRAN ESU 120e user manual Snmp Trap Configuration

A ppendix A . Understanding SNMP

SNMP TRAP CONFIGURATION

Traps received by the ESU 120e from external units and the host unit are converted into SNMP traps and forwarded to the config- ured NMS. The source of the trap is uniquely identified at the NMS by a combination of the IP address of the ESU 120e, and the Unit ID of the sending device. The Unit ID is present in the trap packet appended to the end of the trap community packet name, for exam- ple public.4. It is also included as an Octet String variable (adProd- PhysAddress) in the trap packet as defined in the individual product MIBs. The latest versions of the product MIBs, by default, display the appended trap community name in their descriptions.

Typical steps required for Management Station trap configuration are loading the device specific MIBs and loading or creating device- specific Trap Definition Files. The current product MIBs contain keywords embedded in comments that can be used by some net- work management platforms to automatically generate Trap Defi- nitions. Otherwise, the descriptions may be used as a template for Trap Definitions.

If individual option card port and slot identification is required, it is present in the four- byte adProdPhysAddress field of the trap packet. The first two bytes are the Unit ID of the base controller (least significant byte first). The next two bytes are port and slot number. This field is the second object identifier in all traps sent from ESU/TDU products. For traps from the ISU 512, the Unit ID is the first object identifier. See the product MIBs for more informa- tion

Definitions for Poll Link Up/Down traps are included in the ESU 120e MIB file: ESU 120e.MIB.

A-4 ESU 120e User Manual 1200420L1-1