This document describes the Event Logging System (ELS). It also describes EVENT and how to control the way it collects and displays messages. EVENT provides a view of activity inside the router and on its networks. The information is divided into the following topics:
What is ELS?
Displaying the ELS Configuration Prompt
Displaying the ELS Monitoring Prompt
Entering and Exiting EVENT Display
Displaying ELS Through EVENT
Interpreting ELS Messages
Using ELS
Using ELS to Troubleshoot a Problem
ELS Commands
What is ELS?
Events occur continuously while the router is operating. Any of the following can cause an event:
System activity
Status changes
Service requests
Data transmission and reception
Data and internal errors
A quick scan of the event messages tells you whether or not the router has a problem and where to start looking for it.
See the Event Logging System Messages Guide documentation for a list of ELS messages.
ELS fits into the router software as shown in Figure 1.
Figure 1 ELS and EVENT in the Router Software Structure
Displaying the ELS Configuration Prompt
At the ELS config> prompt, you use commands to establish a default configuration. This default configuration does not take effect until you restart the router.
To enter the ELS configuration process,
* config
Config>
The Config> prompt appears. If the prompt does not appear, press Enter again.
Config> prompt.
Config> event
ELS config>
The ELS config> prompt appears. Now you can enter ELS configuration commands.
Config> prompt. ELS config>exit
Config>
ELS config> prompt, you can do this at the ELS monitoring prompt (ELS>), without re-initializing the router. Use commands at the ELS> prompt to change the default ELS display settings temporarily. Changes made at the ELS> prompt take effect immediately. They are not stored in non-volatile configuration memory.
You can also use the commands at the ELS> prompt to view statistical information regarding ELS uses of dynamic RAM.
To enter the ELS monitoring process,
* monitor
Monitor>
The Monitor> prompt appears. If the prompt does not appear, press Enter again.
Monitor> event
ELS>
The ELS> prompt appears. Now you can type ELS monitoring commands.
Monitor> prompt. ELS> exit
Monitor>
* prompt, type EVENT at the * prompt.The EVENT process does not display any prompt and you cannot enter any commands; it does, however, display the messages EVENT has accumulated.* EVENT
To exit EVENT and return to the * prompt, press Ctrl p.
Displaying ELS Through EVENT
The EVENT process receives messages from the Event Logging System (ELS) and displays them on the screen.
Note: You can also send events to a UNIX host that supports Syslog. See Sending ELS Output to a Syslog Host.
OPCON commands at the * prompt:
divert temporarily diverts output to a different device.
flush causes EVENT to discard the messages it collects.
halt reverses the action of the divert command.
event causes EVENT to display its output.
The set logging disposition command at the Config> prompt sets the initial device to which EVENT sends its output.
You can type divert and halt at the * prompt to view EVENT messages while you are doing something else with the router. Permitted devices divert output to TTY0 (the local terminal), TTY1, or TTY2 (the remote terminals).
To specify a default device for EVENT, define the device in the non-volatile configuration memory by typing set logging disposition at the Config> prompt. Specifying a default device is useful if you have a terminal set up to print.
Interpreting ELS Messages
This section describes how to interpret ELS messages. Figure 2 shows the message contents from a list displayed by typing the following:
ELS> list subsystems gw
A description of each part of this output is explained below.
Subsystem
Subsystem is a pre-defined short name for a router component, such as a protocol, interface, packet forwarder, or feature. In Figure 2, GW identifies the subsystem through which this event occurred. (GW is short for Gateway.)
Other examples of subsystems include ARP, IP, and ETH. On a particular router, the actual subsystems present depend on the hardware and software configured for that router. Use the list subsystems command to see a list of the subsystems on your router.
Enter the subsystem as a parameter to an ELS command when you want the command to affect the entire subsystem. For example, the ELS command display subsystem gw causes all events that occur through the GW subsystem to appear.
Event Number
Event Number is a pre-defined, unique, arbitrary number assigned to each message within a subsystem. It is not an indication of the message priority. In Figure 2, 019 is the event number within the GW subsystem. You can see a list of all the events within a subsystem by using the list subsystems command.
The event number always appears with a subsystem, separated by a period. For example: GW.019. The subsystem and event number together identify an individual event. You type them as a parameter to certain ELS commands. When you want a command to affect only the specified event, type the subsystem and event number as a parameter for the ELS command.
Look up messages in the Event Logging System Messages Guide.
Logging Level
Logging level is a pre-defined setting that classifies each message by the event that generated it. This setting appears whenever you use the list subsystems ELS monitoring command.
Table 1 lists the logging levels and types.
| Logging Level | Type |
|---|---|
| ALWAYS | Every time the router software is reloaded. Display of copyright information and confirmation of configuration. |
| UI-ERROR | Unusual internal errors |
| CI-ERROR | Common internal errors |
| UE-ERROR | Unusual external errors |
| CE-ERROR | Common external errors |
| ERROR | Includes all error levels above |
| U-INFO | Unusual informational comment |
| C-INFO | Common informational comment |
| INFO | Includes all comment levels above |
| STANDARD | Includes all error levels and U-INFO messages (default) |
| P-TRACE | Per packet trace |
| U-TRACE | Unusual operation trace message |
| C-TRACE | Common operation packet trace message |
| TRACE | Includes all trace levels above |
| ALL | Includes all logging levels |
In Table 1, ERROR, INFO, TRACE, STANDARD, and ALL are aggregates of other logging level types. STANDARD is the recommended default.
The logging level setting affects the operation of the following commands:
The logging level is set for a particular command when you specify it as a parameter to one of the above commands. For example:Including the logging level on the command line modifies the display command so that whenever an event with a logging level of either UI-ERROR or CI-ERROR occurs through subsystem ETH, the resulting message appears.ELS>display subsystem eth error
You cannot specify the logging level for operations affecting groups or events.
Message Text
Message Text appears in short form. In Figure 2, Slf tst nt 1 int ETH/0 is the message generated by this event. Variables, such as source_address or network, are replaced with actual data when the message appears on the screen.
Some ELS messages refer to the variable error_code by preceding them with rsn or reason. The error codes indicate the type of packet error the software detected. Table 2 describes the error or packet completion codes. Packet completion codes indicate the disposition of the packets that arrive at the router.
| Code | Meaning |
| 0 | Packet successfully queued for output |
| 1 | Random, unidentified error |
| 2 | Packet not queued for output because of flow control |
| 3 | Packet not queued because network is down |
| 4 | Packet not queued to avoid looping or bad broadcast |
| 5 | Packet not queued because destination host is down (only on networks where this can be detected) |
ELS displays network information as follows:
where:nt 1 int Eth/0 or network 1, interface Eth/0,
1 is the network number (Each network on the router is numbered sequentially from zero.)
0 is the unit number (The interfaces of each hardware type are numbered sequentially from zero.)
IP (Internet Protocol) addresses appear as four decimal bytes separated by periods, such as 126.180.220.16.
Groups
Groups are user-defined collections of events that are given a name, the group name. Like the subsystem, subsystem and event number, and logging level, you can use the group name as a parameter to ELS commands. However, there are no pre-defined group names. You must create a group before you can specify its name on the command line.
To create a group, use the add configuration command, specify the name you want to call the group, and then specify the events you want to be part of the group. You can add events to the group from different subsystems and have different logging levels.
After creating a group, use the group name to manipulate the events in the group as a whole. For example, to turn off display of all messages from events that have been added to a group named grouptwo, include the group name on the command line, as follows:
To delete a group, use the delete command.ELS>nodisplay group grouptwo
Using ELS
To use ELS effectively,
Know what you want to see before using the ELS system. Clearly define the problem or events that you want to see before using EVENT.
Enter the command nodisplay subsystem all all to turn off all ELS messages.
Turn on only those messages that relate to the problem you are experiencing.
The router cannot save these messages so that you can review them later. When this message appears, you may want to tailor the ELS output to display only the information that is important to the current task you are monitoring.xx messages flushed
Managing ELS Message Rotation
ELS messages scroll continually. To pause and resume the ELS message rotation, press
Ctrl p to go back to the last process
Sending ELS Output to a Syslog Host
ELS software supports remote logging of events by generating ELS messages in Syslog format and sending them to a UNIX host that supports Syslog.
The router supports the Syslog severity level value of LOG_NOTICE. However, there are some ARP or IP messages that the router cannot send to Syslog because these messages would cause an ELS/Syslog loop.
To set up ELS to generate Syslog messages,
ELS config>syslog event gw.019
ELS config>syslog subsystem ip
ELS config>set syslog
SYSLOG destination address? [0.0.0.0]? 128.185.123.35
To turn off the sending of Syslog messages, use the nosyslog command.
Capturing ELS Output Using a Telnet Connection on a UNIX Host
You may want to capture the ELS output in a file. To set up an output file you must make a Telnet connection so you can redirect your output to a file. To do this, follow these steps:
* prompt, press Ctrl p.
telnet> prompt. Then, type quit to return to your UNIX prompt.
Setting Up Traps
You can use ELS to set up an enterprise-specific trap for a remote SNMP workstation. A trap is a tool that listens for events, groups, or subsystems. Traps are useful for status, diagnostic, and remote monitoring. For a specific trap, a trap message occurs each time the selected event occurs.
To set up an enterprise-specific trap,
config> or ELS>, type
trap event snmp.002
Note:
If you are at the ELS config> prompt, you need to restart the router for your changes to take affect.
SNMP.002 P-TRACE snt pkt to hst %I
SNMP config> prompt, type
SNMP config>add address public ip address of remote workstation
SNMP config>enable trap enterprise public
SNMP config>set community access read_trap public
Note: These commands are dynamic.
Using ELS to Troubleshoot a Problem
When you are troubleshooting a particular problem, display those messages that relate to the problem. For example, if you are experiencing a problem with Basic Rate ISDN, turn on the BRI messages by typing:
Initially, because of the rapid pace of messages scrolling across the screen, you may want to record the numbers you see and look them up in the Event Logging System Messages Guide. Once you become familiar with different types of messages that appear for a particular protocol, you can turn on and off only those messages containing the information that you require.ELS> display subsystem bri all
ELS allows you to specify which messages are displayed to EVENT by setting up permanent and temporary message filters.
The ELS configuration commands allow you to design a permanent message filter that goes into effect when the router is re-initialized. This filter becomes known as the default message filter.
The ELS monitoring commands allow you to set up a temporary message filter that overrides the permanent filter for troubleshooting purposes. When you re-initialize the router, the software erases this temporary message filter. The monitoring commands also allow you to view statistical information related to the messages.
Device Hardware CSR Vector State
LAN SCC Ethernet 81600 94 Up
WAN Basic Rate ISDN 81620 93 Disabled
* config
Config> event
ELS config> nodisplay subsystem all all
ELS config> display subsystem bri all
ELS config> exit
Config>Ctrl p
* restart
* event
ELS Commands
This section describes the ELS commands. Press Space twice after you type a command to display the available parameters for each command for your router. Enter help for information about using the command line interface.
[C] means the command is available at the ELS config> prompt.
[M] means the command is available at the ELS> prompt.
| Command | Function |
|---|---|
| Add [C] | Adds an event to an existing group or creates a new group. |
| Clear [C] | Clears all ELS information. For monitoring, clears statistical counters for event, group, or subsystem. |
| Default [C] | Resets the display, Syslog, or trap setting of an event, group, or subsystem. |
| Delete [C] | Deletes an event number from an existing group or deletes an entire group. |
| Display [C] [M] | Enables message display on the screen. |
| Exit [C] [M] | Exits ELS. |
| List [C] [M] | Lists information on ELS settings and messages. |
| Nodisplay [C] [M] | Disables message display on the console. |
| Nosyslog [C] [M] | Disables messages sent to syslog. |
| Notrap [C] [M] | Keeps messages from being trapped and sent out over SNMP. |
| Remove [M] | Frees up memory by erasing stored information. |
| Restore [M] | Clears current settings and reloads initial ELS configuration. |
| Retrieve [M] | Reloads the saved ELS configuration. |
| Save [M] | Stores the current configuration. |
| Set [C] [M] | Sets the pin value, the timestamp, or the Syslog host address. |
| Statistics [M] | Displays available subsystems and pertinent statistics. |
| Syslog [C] [M] | Enables sending of messages for specific events, groups, or subsystems to Syslog. |
| Trap [C] [M] | Allows messages to be trapped and sent out over SNMP. |
Add [C]
Adds an event to an existing group or creates a new group. Group names must start with a letter and are case sensitive. You cannot add an entire subsystem to a group.
Syntax: add group_name subsystem.event_number
Example:add
group name? MyGroup
event []? gw.019
clear
You are about to clear all ELS configuration information
Are you sure you want to do this (Yes or No):
event name? gw.019
group name? groupb
Default [C]
Resets the display, Syslog, or trap setting of an event, group, or subsystem back to a nonconfigured state.
Example: default display event snmp.016
syslog
Resets the Syslog of an event, group, or subsystem back to its nonconfigured state. The nonconfigured state for Syslog is disabled.
trap event or group or subsystem
Controls the output of traps to the trap host. Sets the default trap to On, Off, or Unset.
Example: default trap subsystem snmp
Delete [C]
Deletes an event number from an existing group or deletes the entire group. If the event you specify is the last event in a group, a message appears. If you specify all instead of subsystem event.number, a prompt asks you to confirm the deletion of the entire group. This is the only command that allows you to delete a group from the ELS configuration without having to delete the entire configuration.
Syntax: delete group name subsystem event.number
The following example removes a single event from a group containing a string of events.
Example: delete Mygroup gw.019
The following example removes an entire group.
Display [C] [M]
Enables a message display for specific events, groups, or subsystems to EVENT. When turning on group and subsystem messages with the display command, you can use the logging level as a message qualifier. For more information about logging levels, see Table 2.
You can use the display command to turn on all subsystem messages at all logging levels in order to display a message to EVENT whenever any event occurs in the router.
CAUTION:
Do not turn on all subsystem messages at all logging levels for extended periods of time when the router is forwarding live protocal traffic because the router spends an inordinate amount of time communicating with EVENT. You should never turn on all subsystem messages at all logging levels when you are communicating with the router via a remote terminal. It causes the router to spend most of its time communicating with the remote terminal.
group group name
Displays messages of a specified group.
subsystem subsystem name
Displays messages associated with the specified subsystem. To find out which subsystems are on your router, type list subsystems.
Example: display subsystem eth
Exit [C] [M]
Returns you to the previous prompt level.
exit
List [C] [M]
The following sections describe the functionality of the list command at the configuration prompt and then at the monitoring prompt.
List [C]
Displays updated information regarding ELS settings and listings of selected messages.
groups
Lists the user-defined group names and contents. If no group is defined, type add to create a new group.
Group: test
GW.019
Pin: 100 events/second
Subsystem: ETH
Disp levels: STANDARD
Trap levels: none
Syslog levels: ALL
Subsystem: PPP
Disp levels: STANDARD
Trap levels: none
Syslog levels: CE-ERROR C-INFO P-TRACE U-TRACE
Event Display Trap Syslog
IP.007 Unset Unset On
Example: list subsystems summary
Name Events Description
ALL All subsystems
GW 101 Router base and network library
FLT 35 Filter Library
BRS 5 Bandwidth Reservation
ARP 22 Address Resolution Protocol
IP 91 Internet Protocol
ICMP 20 Internet Control Message Protocol
TCP 55 TCP
UDP 7 User Datagram Protocol
BTP 13 BOOTP relay agent
RIP 41 IP Routing Information Protocol
TFTP 29 TFTP Protocol
SNMP 21 Simple Network Management Protocol
DN 115 DECnet
XNS 1 Xerox Networking Systems Protocol
IPX 236 Internetwork Packet Exchange Protocol
IW 71 IPX WAN Protocol
APL 59 AppleTalk
AP2 68 AppleTalk Phase 2
ZIP2 51 Appletalk Phase 2 Zone Information Protocol
DDS 35 Apollo Domain Protocol
R2MP 38 Appletalk Phase 2 Routing Table Management Protocol
SRT 88 Source Routing Transparent Bridge
STP 32 Spanning Tree Protocol
BR 30 Bridge/Routing
ETH 47 Ethernet Handler
PPP 174 Point-to-Point
BRI 48 Basic Rate ISDN
IPPN 9 IP Protocol Net
WRR 28 WAN ReRoute
MCF 9 MAC Filtering
COMP 10 Data Compression Engines
NBS 50 NetBIOS Support Subsystem
CIRC 45 Circuit Subsystem
NAT 32 Network Address Translation
Event Level Message
BRI.021 P-TRACE Chn %d ConnID 0x%x RxD Pkt ln %d dev %s
BRI.022 U-TRACE ConnID 0x%x Rxd %s Pkt ln %d bd stt %s dev %s
BRI.023 C-TRACE ConnID 0x%x Rxd N_STAT_IN ln %d cause 0x%x:0x%x dev %s
BRI.024 UE-ERROR Start Rq bd st (0x%x) dev %s
BRI.025 C-INFO Start ok dev %s
BRI.026 C-INFO Hndlr inidev() st %s dev %s
BRI.027 C-INFO Hndlr N_START_RQ dev %s
BRI.028 C-INFO Can't N_START_RQ DCT i/o flg (0x%x:0x%x) dev %s
BRI.029 UE-ERROR Brd Crsh -- rstrng: dev %s
BRI.030 UE-ERROR Tx Frm too long (%d > %d) dev %s
BRI.031 U-INFO Cll rfsd frm %s:%s to %s:%s on dev %s
BRI.032 C-INFO Chn %d ConnID 0x%x Cll Txcmp on dev %s
BRI.033 C-INFO Chn %d ConnID 0x%x FSM st %s ev %s -> %s dev %s
SYSLOG is enabled to host 128.185.123.35
active subsystem.name
Lists all the events for a specific subsystem and indicates the status of each event. Also displays a count of the number of occurrences of each event since the last restart.
Event Active Count
IP.007 D S 238894
IP.022 T 2
IP.036 DT 237498
IP.059 S 1
IP.061 S 1397
IP.068 S 8109
IP.070 S 28
IP.072 S 3
event event.name
Lists the logging level, the message, and the count of the specified event.
Level: p-TRACE
Message: %I -> %I
Active: Count: 84182
pin
Lists the number of events per second as the current pin value. If no pin is defined, use the set pin command.
Pin: 100 events/second
Event Level Message
CIRC.001 UE-ERROR Dv up nt %d int %s/%d
CIRC.002 UE-ERROR Dv fld slf tst nt %d int %s/%d
CIRC.003 UE-ERROR Dv dwn nt %d int %s/%d
CIRC.004 U-INFO Op ovfl nt %d int %s/%d
CIRC.005 C-INFO Dv dwn, disc pkt on nt %d int %s/%d
CIRC.006 U-INFO Int dis nt %d int %s/%d
CIRC.007 UI-ERROR IP q alloc fl nt %d int %s/%d, avl %d
CIRC.008 C-TRACE Cmd %s from %s to %s (Nt %d int %s/%d)
CIRC.009 C-TRACE Ev %s from %s to %s (Nt %d int %s/%d)
CIRC.010 UI-ERROR Service %s inst fail err '%s'
CIRC.011 UI-ERROR Alloc of buffer failed
CIRC.012 UI-ERROR No Packet Rcvr
CIRC.013 UI-ERROR Circuit err %s nt %d int %s/%d
CIRC.014 UI-ERROR Prot Stk %s open fail err '%s'
CIRC.015 UE-ERROR Dev fld mnt nt %d int %s/%d
<more>
Example: list subsystems summary
Name Events Description
ALL All subsystems
GW 101 Router base and network library
FLT 35 Filter Library
BRS 5 Bandwidth Reservation
ARP 22 Address Resolution Protocol
IP 91 Internet Protocol
ICMP 20 Internet Control Message Protocol
TCP 55 TCP
UDP 7 User Datagram Protocol
BTP 13 BOOTP relay agent
RIP 41 IP Routing Information Protocol
TFTP 29 TFTP Protocol
SNMP 21 Simple Network Management Protocol
DN 115 DECnet
XNS 1 Xerox Networking Systems Protocol
IPX 236 Internetwork Packet Exchange Protocol
IW 71 IPX WAN Protocol
APL 59 AppleTalk
AP2 68 AppleTalk Phase 2
ZIP2 51 Appletalk Phase 2 Zone Information Protocol
DDS 35 Apollo Domain Protocol
R2MP 38 Appletalk Phase 2 Routing Table Management Protocol
SRT 88 Source Routing Transparent Bridge
STP 32 Spanning Tree Protocol
BR 30 Bridge/Routing
ETH 47 Ethernet Handler
PPP 174 Point-to-Point
BRI 48 Basic Rate ISDN
IPPN 9 IP Protocol Net
WRR 28 WAN ReRoute
MCF 9 MAC Filtering
COMP 10 Data Compression Engines
NBS 50 NetBIOS Support Subsystem
CIRC 45 Circuit Subsystem
NAT 32 Network Address Translation
GW.002 ALWAYS Portable CGW %s Rel %s strtd
GW.003 ALWAYS Unus pkt len %d nt %d int %s/%d
GW.004 ALWAYS Sys %s q adv alloc %d excd %d
GW.005 ALWAYS Bffrs: %d avail %d idle fair %d low %d
GW.006 C-INFO Pkt frm nt %d int %s/%d for uninit prt, disc
GW.007 C-INFO Ip err %x nt %d int %s/%d
GW.009 UI-ERROR Nt dwn ip rstrt nt %d int %s/%d
GW.010 UI-ERROR Ip q len %d no ip buf nt %d int %s/%d
GW.014 UI-ERROR Nt dwn op rstrt nt %d int %s/%d
GW.017 UE-ERROR Intfc hdw mssng nt %d int %s/%d
GW.018 U-TRACE Strt nt slf tst nt %d int %s/%d
SYSLOG is enabled to host 128.185.123.35
Example: nodisplay event gw.019
group group name
Suppresses the display of messages previously added to the specified group.
Example: nodisplay group groupb
subsystems subsystem name
Suppresses the display of messages associated with the specified subsystem.
Example: nodisplay subsystem isdn
Nosyslog [C] [M]
Selects and turns off messages sent to Syslog. When turning off group and subsystem messages with the nosyslog command, you can use the logging level as a message qualifier.
Example: nosyslog event gw.019
group
Suppresses the sending of messages previously added to the specified group.
Example: nosyslog group groupb
subsystem
Suppresses the sending of messages associated with the specified subsystem.
Example: nosyslog subsystem isdn
Notrap [C] [M]
Selects and turns off messages being trapped and sent over SNMP. You can specify the logging level of the trapped messages.
group group name
Suppresses the trapping messages previously added to the specified group.
subsystem subsystem name
Suppresses the trapping of messages associated with the specified subsystem.
Example: notrap subsystem eth error
Remove [M]
Frees up memory by erasing stored information. If you have previously saved the current configuration with the save command, remove allows you to erase the saved configuration. Once removed, you cannot load the configuration again.
remove
Restore [M]
Clears all current settings (except counters) temporarily and reloads the default ELS configuration. The restore command does not erase the temporary configuration stored in the router's configuration memory with the save command. To retain the current settings, type save before restoring the initial configuration.
restore
Retrieve [M]
Reloads the saved ELS configuration. If you previously saved the current configuration with the save command, type retrieve to reload it. Retrieve does not erase the saved configuration from configuration memory. To erase the saved configuration, type remove.
retrieve
Save [M]
Stores the current configuration (except counters). Save does not affect the default configuration (the one you set with the configuration commands). Use save after modifying the configuration with the monitoring commands to save this configuration for a restart. There can be only one saved configuration at a time. The next save command from the ELS monitoring environment overwrites it. To reload the saved configuration, type retrieve.
A saved configuration from one release may not be valid (or the same) when retrieved while running a newer release.
Example:save
Set [C] [M]
Sets the pin value, the timestamp, or the Syslog host address.
syslog
Sets the IP address of the Syslog host to which the router sends messages.
SYSLOG destination address? [0.0.0.0]? 128.185.123.35
Note: If you turn on timestamping, you must go back to the Config> prompt and set the router's date and time using the time command. Otherwise, all messages come out with 00:00:00, or negative numbers in the hours, minutes, and/or seconds, for example 00:-4:-5.
Example:set timestamp timeofday
.
.
.
16:21:07 BRI.045: Status Indication: LINE_NOT_READY
16:21:06 BRI.003: ConnID 0xFF Status msg cause (0x1A:0x0) on nt 1 int PPP/0
16:23:34 BRI.043: CLIENT CONNREQ: index 0, physchan 0
16:23:34 BRI.043: CLIENT CONNREQ: proceeding index 0, physchan 65535
16:23:34 BRI.033: Chn 65536 ConnID 0xFFFF FSM st Idle ev ConnReq -> Call_Init 0
16:23:34 BRI.046: NET CONNREQ: index 0, dialing ph# [1-555-8797:]
16:23:34 BRI.032: Chn 0 ConnID 0x0 Cll Txcmp on nt 1 int PPP/0
16:23:35 BRI.015: Chn 0 FSM st Idle ev ConnReq -> Call_Init nt 1 int PPP/0
.
.
.
statistics
Subsys Vector Exist String Active Heap
GW 110 101 3346 3 36
FLT 80 35 818 0 0
BRS 10 5 201 0 0
ARP 25 22 710 0 0
IP 100 91 2482 0 0
ICMP 30 20 506 0 0
TCP 60 55 2353 0 0
UDP 10 7 201 0 0
BTP 40 13 687 0 0
RIP 45 41 1237 0 0
TFTP 35 29 769 0 0
SNMP 30 21 624 0 0
IPX 260 236 4973 0 0
IW 90 71 2624 0 0
APL 60 59 68 0 0
AP2 80 68 1733 0 0
ZIP2 60 51 1859 0 0
DDS 50 35 40 0 0
R2MP 50 38 1233 0 0
SRT 120 88 4693 0 0
STP 60 32 1590 0 0
BR 50 30 1616 0 0
ETH 60 47 1098 0 0
PPP 175 174 6072 0 0
BRI 55 48 1757 0 0
IPPN 20 9 323 0 0
WRR 40 28 1601 0 0
MCF 15 9 239 0 0
COMP 80 10 305 0 0
NBS 100 50 3025 0 0
CIRC 45 45 1626 0 0
NAT 40 32 1139 0 0
Total 2265 1716 51584 3 36
Maximum: 5306 vector, 132 subsystem
Memory: 47754/528 vector + 28408/52433 data + 36 heap = 129159
Syslog [C] [M]
Enables sending of messages for specific events, groups, or subsystems to the Syslog host. When turning on group and subsystem messages with the syslog command, you can use the logging level as a message qualifier. For more information about logging levels, see Table 2.
You can use the syslog command to turn on all subsystem messages at all logging levels in order to send a message to Syslog whenever an event occurs in the router.
CAUTION:
Do not turn on all subsystem messages at all logging levels for extended periods of time when the router is forwarding live protocal traffic, because the router spends an inordinate amount of time communicating with EVENT. You should never turn on all subsystem messages at all logging levels when you are communicating with the router via a remote terminal. It causes the router to spend most of its time communicating with the remote terminal.
group group name
Sends messages of the specified group to Syslog.
subsystem subsystem name
Sends messages associated with the specified subsystem to Syslog. To find out which subsystems are on your router, enter list subsystems.
Trap [C] [M]
Selects the message to be sent to the remote SNMP workstation. Do not use this ELS feature on a router that is passing live protocol traffic as it causes the router to dedicate most of its processing time to trapping and sending ELS messages.
You can specify the logging level of the trapped messages.
group group name
Traps messages that were previously added to the specified group.
subsystem subsystem name
Traps messages associated with the specified subsystem.