ADTRAN TSU 120e user manual Snmp Trap Configuration

Models: TSU 120e TSU 120

1 140
Download 140 pages 56.89 Kb
Page 112
Image 112

Appendix A. Understanding SNMP

SNMP Trap Configuration

Traps received by the TSU 120 from external units and the host unit are converted into SNMP traps and forwarded to the con- figured NMS. The source of the trap is uniquely identified at the NMS by a combination of the IP address of the TSU 120, 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 example public.4. It is also included as an Octet String variable (adProdPhysAddress) in the trap packet as defined in the individual product MIBs. The latest versions of the product MIBs, by default, display the appended trap com- munity name in their descriptions.

Typical steps required for Management Station trap configura- tion are loading the device specific MIBs and loading or creat- ing device-specific Trap Definition Files. The current product MIBs contain keywords embedded in comments that can be used by some network management platforms to automatically generate Trap Definitions. 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 identi- fier 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 information

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

The TSU 120 and TSU 120e share the same MIB.

A-4

TSU 120 User Manual

61202052L1-1

Page 112
Image 112
ADTRAN TSU 120e user manual Snmp Trap Configuration