Filter
Top Products
Maximum:7976 vector, 155 subsystem
Memory:71784/620 vector+ 81256/217714 data+ 64 heap=371438Subsys
Subsys
Name of subsystem
Vector
Maximum size of subsystem
Exist Number of events defined in this subsystem
String Number of bytes used for message storage in this subsystem
Active Number of active (displayed, trapped, or counted) events in the subsystem
Heap Dynamic memory in use by subsystem
Trace
Use the trace command to select the trace events to be displayed on the system
monitoring. This command provides function that is similar to the packet trace
command described in “Packet-trace Monitoring Commands” on page 205.
Syntax:
trace
event...
group...
range...
subsystem...
event
subsystem.event#
Causes the specified trace event (
subsystem.event#
) to be displayed on the
system monitoring.
group
groupname
Allows trace events that were previously added to the specified group to be
displayed on the router monitoring.
range
subsystemname first_event_number last_event_number
Where
first_event_number
is the number of the first event in the specified
event range, and
last_event_numbe
r is the number of the last event of the
specified event range.
Causes the trace events in the specified range for the specified subsystem
to be displayed on the system monitoring.
Example:
trace range gw 19 22
Causes the trace events gw.19, gw.20, gw.21, and gw.22 to be displayed on
the system monitoring.
subsystem
subsystemname
Allows trace events associated with the specified subsystem to be
displayed on the router monitoring.
ELS Monitoring Commands (Talk 5)
Chapter 13. Configuring and Monitoring the Event Logging System (ELS) 203