Extreme Networks ExtremeWare XOS 10.1, Manual

Page: 110 / 256

110 ExtremeWare XOS 10.1 Concepts Guide
Status Monitoring and Statistics
You must specify the TFTP host and the filename to use in uploading the log. There are many options
you can use to select the log entries of interest. You can select to upload only those messages that
conform to the specified:
• Severity
• Starting and ending date and time
•
Match expression
The uploaded messages can be formatted differently from the format configured for the targets, and you
can choose to upload the messages in order of newest to oldest, or in chronological order (oldest to
newest).
Displaying Counts of Event Occurrences
EMS adds the ability to count the number of occurrences of events. Even when an event is filtered from
all log targets, the event is counted. (The exception to this is events of any of the debug severities,
which are only counted when the log debug mode is enabled.) To display the event counters, use the
following command:
show log counters {<event condition> | [all | <event component>]} {include | notified
| occurred} {severity <severity> {only}}}
Two counters are displayed. One counter displays the number of times an event has occurred, and the
other displays the number of times that notification for the event was made to the system for further
processing. Both counters reflect totals accumulated since reboot or since the counters were cleared
using the
clear log counters
or
clear counters
command.
This command also displays an included count (the column titled
In
in the output). The included
count is the number of enabled targets receiving notifications of this event without regard to matching
parameters.
The keywords
include
,
notified
, and
occurred
only display events with non-zero counter values for
the corresponding counter.
Output of the command:
show log counters stp.inbpdu severity debug-summary
will be similar to the following:
Comp SubComp Condition Severity Occurred In Notified
------- ----------- ----------------------- ------------- -------- -- --------
STP InBPDU Drop Error 0 Y 0
STP InBPDU Ign Debug-Summary 0 N 0
STP InBPDU Mismatch Warning 0 Y 0
Occurred : # of times this event has occurred since last clear or reboot
Flags : (*) Not all applications responded in time with there count values
In(cluded): Set to Y(es) if one or more targets filter includes this event
Notified : # of times this event has occurred when ’Included’ was Y(es)
Output of the command:
show log counters stp.inbpdu.drop