2172 ExtremeWare Software 7.3.0 Command Reference Guide
Troubleshooting Commands
configure debug-trace mpls
configure debug-trace mpls <level>
Description
This command records debug information to the syslog.
Syntax Description
Default
The default level is 0.
Usage Guidelines
The
debug level
range is 0 to 5. Higher levels record more verbose messages. Higher levels also record
the messages recorded at lower levels.
Example
The following command sets the reporting level for MPLS errors to 3:
configure debug-trace mpls 3
Following is the log output at this level:
<DBUG:IPHS> Skipping FDB refresh for 10.3.1.1 due to LSP
<DBUG:IPHS> last message repeated 3 times
<DBUG:IPHS> Skipping FDB refresh for 10.3.1.1 due to LSP
<DBUG:IPHS> last message repeated 3 times
<DBUG:IPHS> Skipping FDB refresh for 10.3.1.1 due to LSP
<DBUG:IPHS> last message repeated 3 times
<DBUG:IPHS> Skipping FDB refresh for 10.3.1.1 due to LSP
<DBUG:IPHS> last message repeated 2 times
<DBUG:IPHS> Skipping FDB refresh for 10.3.1.1 due to LSP
debug level Specifies a debug level:
0 — None.
1 — Records error and warning messages, such as session up, state machine errors,
Initialization errors, label allocation errors, patricia tree failures, invalid message
type or format, memory allocation errors, NVRAM parse errors, TLS tunnel
creation errors, socket errors, label manager problems, and null pointer or
handle.
2 — Records informational messages, such as LDP entity up, LDP parameter setting,
LSP bind event, NHLFE creation, and MPLS GPP and session down errors.
3 — Records debug information, such as
patricia Tree Adds/Deletes,
Label
Propagation and Release Msgs, Message encoding, Parameter setting, MPLS
enable messages, Memory initialization, TLS setup messages, Invalid value
messages, LSP Init/Teardown msgs, Event processing, RDB (route) callback
information.
4 — Records more detailed debug information.
5 — No additional information recorded.
To Next Page
Loading...
Need help?
General
