Log Message Format - Avaya 8800 Troubleshooting Manual

In addition to standardizing system messages, SMP captures all relevant error information
(system messages and crash dumps) in a single file. SMP helps collect, analyze, and provide
timely solutions to issues.
System Messaging Platform navigation
•

Log message format

• Log files
• Log file transfer
Log message format
The log messages for the Avaya Ethernet Routing Switch 8800/8600 have a standardized
format. All system messages are tagged with the following information:
• Module ID—software module from which the log is generated
• Avaya Proprietary (AP) information for debugging purposes
• SF/CPU slot—identifies which slot of the SF/CPU generated the log message
• Category—the category of the log message
• Severity—the severity of the message
The SMP message format is as follows:
<Module ID><Task><NP info><CPU slot><Time stamp><Category><Severity>
An SMP message example follows:
VLAN Task=tTrapd No-interface CPU5 [10/14/98 15:46:26] VLAN WARNING Link Down
AP information is encrypted before it is written to the log file. The encrypted information is for
debugging purposes. Only an Avaya Customer Service engineer can decrypt the information.
CLI commands display the logs without the encrypted information. Avaya recommends that
you do not edit the log file.
The following table lists the system message categories.
Table 4: SMP categories
ATM
CPU
DVMRP
EAP
Troubleshooting
on page 51
on page 53
on page 54
SMP categories
IP
IPMC
IP-RIP
IPX
PIM SNMP
POLICY STG
POS SW
QOS VLAN
System Messaging Platform
July 2013 51