Using Trace Syslog To Diagnose Problems - Avaya 8800 Troubleshooting Manual

Using trace syslog to diagnose problems

The trace command is the main debugging tool for the ERS 8800/8600. To alleviate some
of the overhead and make tracing more efficient, Avaya enhanced the current tracing
mechanism by adding Syslog tracing. With this enhancement, trace messages are transmitted
out as Syslog packets thereby avoiding the overhead caused by the traces for displaying the
messages on the switch console and logging to a file. An external entity captures these Syslog
trace packets and decodes them appropriately.
Important:
Note the following points:
• When enabled, the output will not be sent to the trace buffer.
• The port must be an inband Ethernet I/O port. This command does not work with the
CPU management port.
• The trace syslog enhancement has nothing to do with the existing syslog
functionality.
• In each syslog trace, the switch's management IP address is part of the syslog header.
This enables you to differentiate between multiple trace messages generated from
different switches.
Prerequisites
• Use a syslog server (such as a Linux PC running syslogd) that is reachable from the
test switch.
• Make sure there is an Active IP Route in the switch to the syslog server or relay. (This is
not required if the next-hop mac and port are specified while configuring the syslog
destination address).
Procedure steps
1. In any ACLI mode, configure the destination IP address to send the syslog trace
Troubleshooting
packets using the following command:
trace syslog destination <ipaddr> [next-hop-mac <mac>] [port
<port>] [vlan <vlan_Id>]
The destination IP address is typically the IP address of the syslog server or the
relay.
General troubleshooting
July 2013 209