Header Only - DO NOT REMOVE - Extreme Networks

TRACE function ERS4800

  • 6 September 2019
  • 1 reply

Anyone used the trace function on the ERS4800 product? Documentation just describes the trace functionality as per the VSP/ERS core products however the syntax for trace on the ERS4800 is different.

1 reply

Userlevel 3
Please see below for the debug trace command on ERS.

-Trace is a debug feature that facilitates understanding of the execution flow of an application module
-Trace can be useful for troubleshooting if an application module is not work properly
-Trace can be enabled from either console or telnet session via ACLI
-Use trace only for active troubleshooting because it is resource intensive.
-A trace command is available that is supported in OSPF, RIP, SMLT, IPMC, IGMP, PIM and 802.1X/EAP. There are five levels of trace command for each module or application. Following are the levels: Critical, Error, Warning, Info, Debug

- Procedure
1. Enter Global Configuration mode:
Enable and configure terminal
2. (Optional) Display the available module or submodule options:
trace module hint
trace module {ospf | igmp | pim | rip |eap | ntp | sflow | dvmrp}
submodule hint
3. Set the trace level:
trace module {ospf | igmp | pim | rip |eap | ntp | sflow | dvmrp}
[submodule ] level {critical | error | warning | info
| debug | no-display} [unit <1-8>]
4. Enable the trace screen:
trace screen enable
5. Disable the trace screen:
trace screen disable
6. Disable the trace:
trace shutdown

- Viewing the trace level
1. Enter Privileged EXEC mode:
2. DIsplay the trace level:
show trace level