Appendix A. Understanding SNMP61202156L2-1 TDU 120e User Manual A-5SNMP Trap ConfigurationTraps received by the TDU 120e from external units andthe host unit are converted into SNMP traps and forward-ed to the configured NMS. The source of the trap isuniquely identified at the NMS by a combination of the IPaddress of the TDU 120e, and the Unit ID of the sendingdevice. 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 Stringvariable (adProdPhysAddress) in the trap packet as de-fined in the individual product MIBs. The latest versionsof the product MIBs, by default, display the appendedtrap community name in their descriptions.Typical steps required for Management Station trap con-figuration are:1. loading the device specific MIBs, and2. loading or creating device-specific Trap DefinitionFiles.The current product MIBs contain keywords embeddedin comments that can be used by some network manage-ment platforms to automatically generate Trap Defini-tions. Otherwise, the descriptions may be used as atemplate for Trap Definitions.If individual option card port and slot identification is re-quired, it is present in the four-byte adProdPhysAddressfield of the trap packet. The first two bytes are the Unit IDof the base controller (least significant byte first). The nexttwo bytes are port and slot number. This field is the sec-ond object identifier in all traps sent from TSU/TDUproducts. For traps from the ISU 512, the Unit ID is thefirst object identifier. See the product MIBs for more infor-mation.Definitions for Poll Link Up/Down traps are included inthe TDU 120e MIB file: TDU 120e.MIB.
