Avaya Octel 200, Octel 300 SNMP Trap CP TraceExample, Hardware Error Table Entries for an SNMP Trap

11B-10 Installationand Maintenance Volume
Octel 200/300 S.4.1 PB60019−01
SNMP Trap CP TraceExample
Following is an example of a CP trace for an SNMP trap:
MM/DD/YY HH:MM:SS PRT TYPE EVENT AUX MBX/EXTN MSG# SL U L SOURCE
D1D2 D3 D4 D5
MM/DD/YY 12:06:08 LAN_OUT SNMP_TRAP 001
The value 001 (currently the only one defined) in the auxiliary field (AUX) indicates that the SNMP trap
is being sent because of a hardware error.
Hardware Error Table Entries for an SNMP Trap
A hardware error type 42, DATA1= 17(hex) will be logged if a trap needs to be sent but the SNMP
system manager is not known. For example,
@LH
THU MM/DD 09:13:17 YYYY ABC,INC ID:123456 S/N:123456 PBX:23
CLEARED: 05/19 09:10
TYPE SLOT CHNL PRIO DATE TIME #BAD DATA1DATA2 DATA3 DATA4
42 06 00 105/19 09:13100000017 00000000 00000000 00000000
For the SNMP manager system to be configured, either its IP address (System Parameter 235) or its host
name (System Parameter 236) and the IP address of the domain name server (System Parameter 233)
must be known.
Once an SNMP trap has been generated, the LHcommanddisplays this information. For example,
@LH
THU MM/DD 13:22:08 YYYY ASKME ID:123456 S/N:123456 PBX:23
CLEARED: 05/1912:51
*** SNMP MANAGER SYSTEM HAS BEEN NOTIFIED ***
TYPE SLOT CHNL PRIO DATE TIME #BAD DATA1DATA2 DATA3 DATA4
33 0100 3 05/1912:54 100000000 00000003 00000002 00000000
64 06 00 3 05/1913:01100000002 0000000100000000 00000000
After successful completion of an SNMP TEST, hardware error type 64, DATA1 = 0E(hex) with a
priority of 0 is logged.