Cisco MGX 8850 Command Reference Manual page 736

dsplog
-sev
-tle
-tge
Related Commands
clrlog, dsplogs
Attributes
Log: no log
Cisco MGX 8850 Routing Switch Command Reference
9-118
Specifies the severity of the alarm. Select it by entering a number in the range 1–7:
1. EVENT_FATAL: This severity indicates that the event affects the existing data
traffic for the systems and is considered fatal because the platform cannot recover.
Fatal events cause a card reset. Also, any error or condition that damages or causes
loss of ongoing data traffic is fatal. Examples of fatal events are hardware watchdog
timeout, critical task failure or suspension, and hardware device failures of CBC or
QE.
2. EVENT_MAJOR_ALERT: This severity indicates a major service or feature of the
platform has been damaged or lost but that existing data traffic is not affected. These
events indicate that immediate action is necessary to recover the platform or service
by posting traps and major alarms. Examples of major alerts are hard disk crashes,
critical memory shortages, and inability to complete a configuration change.
3. EVENT_MINOR_ALERT: This severity indicates a minor event or partial damage
to or loss of a service on the platform. Nevertheless, existing data traffic and critical
services are not affected. These events indicate that eventual action is necessary to
recover the platform or service by posting a minor alarm condition. Examples of
minor alerts are loss of some tftp or telnet sessions and loss of statistics or other
non-critical features.
4. EVENT_ERROR: This severity indicates that an error occurred but is not sever
enough or it does not know the scope of its implication to be more sever. Most
detected failures are reported with this severity, then the higher levels of software
determine the appropriate response. Examples of these errors are malloc failures,
illegal API parameter values, bad PDUs, and most internally detected failures.
5. EVENT_WARNING: This severity indicates that some threshold has been reached
and could be a warning of a future error condition. Examples are resource shortages
of memory and disk space, voltage and temperature just out of tolerance, and other
conditions that could lead to a more serious situation.
6. EVENT_NOTICE: This severity indicates that a normal but significant event has
occurred on the platform. Events for significant configuration changes would be in
this category. Examples of notice type events would be addition of lines or ports and
connection alarms.
7. EVENT_INFO: This severity indicates an event is informational. It does not
indicate an abnormal condition. Examples of informational events are logging of user
logins and important commands.
Specifies a particular time for which to display events: same time or earlier time.
Specifies a particular time for which to display events: same time or later time.
State: active, standby, init
Chapter 9 Troubleshooting Commands
Privilege: ANYUSER
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001