RuggedSwitch™ User Guide
Tracing Events
The CLI trace command provides a means to trace the operation of various
protocols. The trace provides detailed information including RSTP packet
decodes, IGMP activity and MAC address displays.
Notes:
Note that all tracing is disabled upon switch startup.
In order to display the current trace settings and discover the systems that be
traced, enter the CLI command "trace ?".
>trace ?
Supported commands:
noclear
alloff
allon
stp
link
mac
forward
ip
igmp
Enter "trace command ?" for more information on a particular command.
STP
: Logging is disabled
LINK : Logging is disabled
MAC
: Logging is disabled
FORW : IP: 0.0.0.0
IP
: Logging is disabled
IGMP : Logging is disabled
Figure 63: Displaying Trace settings
Enabling Tracing
Tracing can be enabled on a per subsystem basis. Obtain detailed information
about individual subsystems by entering "trace subsystem_name ?<CR>". Some
subsystems offer a mechanism to enable tracing only on certain ports.
>trace stp ?
trace stp syntax:
stp [-|+] [all] [verbose] [packets] [timers] [actions]
STP
: Logging is disabled
>trace stp all
STP
: Logging all conditions on port(s) 1-16
>trace link ?
trace link syntax
link changes | stats | allon | alloff | statsonce
LINK : Logging is disabled
>trace link changes
LINK : changes
Figure 64: Changing Trace settings
Tracing has been designed to provide detailed information to expert users.
Starts the log without clearing it first
Disables all trace subsystems from tracing
Enables all flags in all trace subsystems
Traces STP operations
Displays switch fabric statistics
Displays MAC Events
Forwards trace messages to an IP:UDP address
Traces IP communications
Displays IGMP Snooping events
UDP: 0 (OFF)
[decodes] [ports[port_number|all]]
RuggedCom
Need help?
Do you have a question about the RuggedSwitch RS1600 and is the answer not in the manual?