Appendix A. Understanding SNMP

SNMP Trap Configuration

Traps received by the TDU 120e from external units and the host unit are converted into SNMP traps and forward- ed to the configured NMS. The source of the trap is uniquely identified at the NMS by a combination of the IP address of the TDU 120e, and the Unit ID of the sending device. The Unit ID is present in the trap packet append- ed to the end of the trap community packet name, for ex- ample public.4. It is also included as an Octet String variable (adProdPhysAddress) in the trap packet as de- fined 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 con- figuration are:

1.loading the device specific MIBs, and

2.loading or creating device-specific Trap Definition Files.

The current product MIBs contain keywords embedded in comments that can be used by some network manage- ment platforms to automatically generate Trap Defini- tions. Otherwise, the descriptions may be used as a template for Trap Definitions.

If individual option card port and slot identification is re- quired, 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 sec- ond object identifier in all traps sent from TSU/TDU products. For traps from the ISU 512, the Unit ID is the first object identifier. See the product MIBs for more infor- mation.

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

61202156L2-1

TDU 120e User Manual

A-5

Page 121
Image 121
ADTRAN TDU 120e user manual Snmp Trap Configuration