Avaya 8800 Troubleshooting Manual page 120

Software troubleshooting tool configuration using CLI
mechanism by adding Ethernet tracing. With this enhancement, trace messages are
transmitted out as Ethernet 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 Ethernet trace packets and decodes them appropriately.
You can capture Ethernet trace packets and then decode them from either a file or in real
time.
• If you decode them from a file, capture the Ethernet trace packets with a packet capture
tool such as PCAP and save them to a file, then use the file as an input to a decoder that
decodes it into a readable format.
• If you decode them in real time, start the decoder in a PC first, which in turn captures and
decodes the Ethernet trace packets received from the switch.
Important:
Note the following points:
• When enabled, the output is not 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.
Prerequisites
• Connect a Linux or Solaris PC to the port that will generate the Ethernet trace packets.
• Use a packet capture tool to capture the Ethernet trace packets the switch generates.
(This is optional).
Procedure steps
1. Configure the outgoing port on which the Ethernet trace packets need to be
2. Enable Ethernet trace in the switch:
3. If the packet capture tool is going to capture packets, ensure that you configure the
120 Troubleshooting
transmitted using the command:
trace ethernet port <slot/port> [vlan <vlanId>]
trace ethernet enable
packet capture tool to capture the Ethernet trace packets and that you start the
packet capture.
(OR)
If packets are going to be decoded real time, then ensure that you execute the
following command in the Linux or Solaris PC in superuser mode:
Comments? infodev@avaya.com
July 2013