Appendix A. Understanding SNMPA-4 TSU 120 User Manual 61202052L1-1SNMP Trap ConfigurationTraps received by the TSU 120 from external units and the hostunit are converted into SNMP traps and forwarded to the con-figured NMS. The source of the trap is uniquely identified atthe 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 inthe trap packet appended to the end of the trap communitypacket name, for example public.4. It is also included as anOctet String variable (adProdPhysAddress) in the trap packet asdefined in the individual product MIBs. The latest versions ofthe 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 productMIBs contain keywords embedded in comments that can beused by some network management platforms to automaticallygenerate Trap Definitions. Otherwise, the descriptions may beused as a template for Trap Definitions.If individual option card port and slot identification isrequired, it is present in the four- byte adProdPhysAddress fieldof the trap packet. The first two bytes are the Unit ID of thebase controller (least significant byte first). The next two bytesare port and slot number. This field is the second object identi-fier in all traps sent from TSU/TDU products. For traps fromthe ISU 512, the Unit ID is the first object identifier. See theproduct MIBs for more informationDefinitions for Poll Link Up/Down traps are included in theTSU 120e MIB file: TSU 120e.MIB.The TSU 120 and TSU 120e share the same MIB.
