104
ExtremeWare XOS 10.1 Concepts Guide
Status Monitoring and Statistics
InBPDU STP In BPDU subcomponent Warning
OutBPDU STP Out BPDU subcomponent Warning
System STP System subcomponent Error
...
...
The display above lists the components, subcomponents, and the default severity threshold assigned to
them. A period (.) is used to separate component, subcomponent, and condition names in EMS. For
example, you can refer to the InBPDU subcomponent of the STP component as STP.InBPDU. On the
CLI, you can abbreviate or TAB complete any of these.
A component or subcomponent will often have several conditions associated with it. To see the
conditions associated with a component, use the following command:
show log events [<event condition> | [all | <event component>] {severity <severity>
{only}}] {details}
For example, to see the conditions associated with the STP.InBPDU subcomponent, use the following
command:
show log events stp.inbpdu
The output produced by the command is similar to the following:
Comp SubComp Condition Severity Parameters
------- ----------- ----------------------- ------------- ----------
STP InBPDU Drop Error 2 total
STP InBPDU Dump Debug-Data 3 total
STP InBPDU Trace Debug-Verbose 2 total
STP InBPDU Ign Debug-Summary 2 total
STP InBPDU Mismatch Warning 2 total
The display above lists the five conditions contained in the STP.InBPDU component, the severity of the
condition, and the number of parameters in the event message are displayed. In this example, the
severities of the events in the STP.InBPDU subcomponent range from error to debug-summary.
When you use the
details
keyword you will see the message text associated with the conditions. For
example, if you want to see the message text and the parameters for the event condition
STP.InBPDU.Trace, use the following command:
show log events stp.inbpdu.trace detail
The output produced by the command is similar to the following:
Comp SubComp Condition Severity Parameters
------- ----------- ----------------------- ------------- ----------
STP InBPDU Trace Debug-Verbose 2 total
0 - string
1 - string (printf)
Port=%0%: %1%
The
Comp
heading shows the component name, the
SubComp
heading shows the subcomponent (if any),
the
Condition
heading shows the event condition, the
Severity
heading shows the severity assigned
to this condition, the
Parameters
heading shows the parameters for the condition, and the text string
shows the message that the condition will generate. The parameters in the text string (for example,
%0%
and
%1%
above) will be replaced by the values of these parameters when the condition is encountered,
and output as the event message.
Summary of Contents for ExtremeWare XOS 10.1
Page 12: ...12 ExtremeWare XOS 10 1 Concepts Guide Contents...
Page 15: ...Part 1 Using ExtremeWare XOS...
Page 16: ......
Page 20: ...20 ExtremeWare XOS 10 1 Concepts Guide ExtremeWare XOS Overview...
Page 32: ...32 ExtremeWare XOS 10 1 Concepts Guide Accessing the Switch...
Page 74: ...74 ExtremeWare XOS 10 1 Concepts Guide Virtual LANs VLANs...
Page 80: ...80 ExtremeWare XOS 10 1 Concepts Guide Forwarding Database FDB...
Page 112: ...112 ExtremeWare XOS 10 1 Concepts Guide Status Monitoring and Statistics...
Page 133: ...Part 2 Using Switching and Routing Protocols...
Page 134: ......
Page 174: ...174 ExtremeWare XOS 10 1 Concepts Guide Virtual Router Redundancy Protocol...
Page 184: ...184 ExtremeWare XOS 10 1 Concepts Guide IP Unicast Routing...
Page 202: ...202 ExtremeWare XOS 10 1 Concepts Guide Interior Gateway Protocols...
Page 216: ...216 ExtremeWare XOS 10 1 Concepts Guide Exterior Gateway Routing Protocols...
Page 224: ...224 ExtremeWare XOS 10 1 Concepts Guide IP Multicast Routing...
Page 225: ...Part 3 Appendixes...
Page 226: ......
Page 234: ...234 ExtremeWare XOS 10 1 Concepts Guide Software Upgrade and Boot Options...
Page 242: ...242 ExtremeWare XOS 10 1 Concepts Guide Troubleshooting...
Page 256: ...4 ExtremeWare XOS 10 1 Concepts Guide Index of Commands...