[Top] [Prev] [Next] [Bottom]
Using the Event Logging System
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:
When an event occurs, ELS generates a message describing the event. Using ELS commands, you can set up a configuration that sorts out only those messages that are important to you. You can display the messages on the terminal screen and/or through SNMP (Simple Network Management Protocol).
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,
- 1. Type config at the * prompt.
* config
Config>
The Config> prompt appears. If the prompt does not appear, press Enter again.
- 2. Type event at the Config> prompt.
Config> event
ELS config>
The ELS config> prompt appears. Now you can enter ELS configuration commands.
To leave the ELS configuration prompt, type exit and return to the Config> prompt.
ELS config>exit
Config>
Displaying the ELS Monitoring Prompt
You can look at messages in a temporary configuration, other than the one you set up at the 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,
- 1. Type monitor at the * prompt.
* monitor
+
The + prompt appears. If the prompt does not appear, press Enter again.
- 2. Type event to access ELS.
+ event
ELS>
The ELS> prompt appears. Now you can type ELS monitoring commands.
To leave the ELS monitoring prompt, type exit and return to the + prompt.
ELS> exit
+
Entering and Exiting EVENT Display
To enter EVENT from the * prompt, type EVENT at the * prompt.
* EVENT
The EVENT process does not display any prompt and you cannot enter any commands; it does, however, display the messages EVENT has accumulated.
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.
Commands Affecting EVENT
The following commands affect EVENT:
Receiving EVENT Messages
To receive EVENT messages at your terminal, type event, as described above. Then EVENT displays all the messages it has recorded since it was last invoked. While you are connected to EVENT, all messages appear as they arrive.
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
Figure 2 ELS Message Format
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.
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:
ELS>display subsystem eth error
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.
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.
ELS displays network information as follows:
nt 1 int Eth/0 or network 1, interface Eth/0,
where:
Ethernet and 802.5 hardware addresses appear as long hexadecimal numbers.
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:
ELS>nodisplay group grouptwo
To delete a group, use the delete command.
Using ELS
To use ELS effectively,
When you initially view ELS messages from EVENT, you see a considerable amount of information. Because the router cannot buffer and display every packet under moderate to heavy loads, it flushes the buffers. When this occurs the following message appears on the screen:
xx messages flushed
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.
Managing ELS Message Rotation
ELS messages scroll continually. To pause and resume the ELS message rotation, press
Ctrl s to pause scrolling
Ctrl q to resume scrolling
Ctrl p to go back to the last process
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:
- 1. Access your router.
- 2. Set up ELS for the messages you want to capture, using the commands in ELS from the + prompt.
- 3. Terminate your router connection.
- 4. Type telnet ip address > outputfilename
where ip address is your router address and outputfilename is the file in which you want the messages to go.
The following steps are invisible to you. You can see the messages in your output file by either opening another window and viewing the file or quitting the telnet process and using a viewer or editor to see it.
- 1. To get to the * prompt, press Ctrl p.
- 2. To get all ELS messages to dump to your output file, type event.
- 3. Press ctrl ] to get to the telnet> prompt. Then, type quit to return to your UNIX prompt.
You can also capture the ELS output to a file by attaching a PC to the router's console port and starting a log file from within the terminal emulation package.
You need this output information to help Customer Service diagnose a problem.
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,
- 1. At ELS config> or ELS>, type
trap event snmp.002
Note:
If you are at the ELS config> prompt, you need to reboot.
SNMP.002 P-TRACE snt pkt to hst %I
- 2. At the 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.
- 3. Start your trap tool on your remote SNMP workstation.
You can follow the steps above for trapping groups, subsystems, and events.
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:
ELS> display subsystem bri all
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 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.
Example: ISDN
ISDN is not working.
- 1. Check configuration.
- 2. Using the MONITOR list device command, verify that the ISDN device is not disabled.
Device Hardware CSR Vector State
LAN SCC Ethernet 81600 94 Up
WAN Basic Rate ISDN 81620 93 Disabled
- 3. Type the following:
* config
Config> event
ELS config> nodisplay subsystem all all
ELS config> display subsystem bri all
ELS config> exit
Config>Ctrl p
* restart
* event
Check the Basic Rate ISDN (BRI) messages.
ELS Commands
This section describes each of 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.
* These commands function in the same way whether used for configuring or monitoring; their effect is temporary when used for monitoring.
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
- Note:
If the specified group does not exist, a prompt asks you to confirm the creation of a new group.
Clear [C]
Clears all of the ELS configuration information.
Syntax: clear
Example: clear
You are about to clear all ELS configuration information
Are you sure you want to do this (Yes or No):
Clear [M]
Clears counters in the monitoring environment as they relate to specific events, groups, or subsystems.
Syntax: clear
- event
- group
- subsystem
event event.name
Disables the displaying or trapping of messages for the specified event.
Example: clear event gw.019
group group.name
Disables the displaying or trapping of messages for the specified group.
Example: clear group groupb
subsystem subsystem.name
Disables the displaying or trapping of messages associated with the specified subsystem. If you do not specify a logging level, disables all messages for that subsystem.
Example: clear subsystem gw
Default [C]
Resets the display or trap setting of an event, group, or subsystem back to a non-configured state.
Syntax: default
- display
- trap
display event or group or subsystem
Controls the output of the display of messages to the screen or to the trap host. A trap host is a remote network management workstation. Sets the default display to On, Off, or Unset.
Example: default display event snmp.016
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
Removes a single event from a group containing a string of events.
Example: delete Mygroup gw.019
Removes an entire group.
Example: delete Mygroup all
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.
Syntax: display
- event
- group
- subsystem
event event name
Displays messages of the specified event.
Example: display event gw.019
group group name
Displays messages of a specified group.
Example: display group groupb
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.
Syntax: exit
Example: exit
List [C]
Displays updated information regarding ELS settings and listings of selected messages.
Syntax: list
- all
- groups
- pin
- status
- subsystems
all
Lists all subsystems, defined groups, enabled subsystems, enabled events, and pins.
Example: list all
groups
Lists the user-defined group names and contents. If no group is defined, type add to create a new group.
Example: list groups
Group: test
GW.019
pin
Lists the number of events per second as the current pin value. If no pin is defined, type set pin.
Example: list pin
Pin: 100 events/second
status
Lists the subsystems, groups and events modified by the default, display, nodisplay, trap, and notrap commands.
Example: list status
Subsystem: ETH
Disp levels: STANDARD
Trap levels: none
Subsystem: IP
Disp levels: STANDARD
Trap levels: none
Subsystem: RIP
Disp levels: STANDARD
Trap levels: none
Subsystem: SNMP
Disp levels: STANDARD
Trap levels: none
Event Display Trap
ISDN.021 Unset On
subsystems
Lists the names, events, and descriptions of all the subsystems.
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
Lists all events in a specified subsystem.
Example: list subsystems bri
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
If you leave out the name of the subsystem, the system lists the events in all subsystems.
List [M]
Displays updated information regarding ELS settings and listings of selected messages.
Syntax: list
- all
- active
- event
- groups
- pin
- subsystems
all
Lists all subsystems, defined groups, enabled subsystems, enabled events, and pins.
Example: list all
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.
Example: list active ip
Event Active Count
IP.007 D 238894
IP.022 T 2
IP.036 DT 237498
IP.059 1
IP.061 1397
IP.068 8109
IP.070 28
IP.072 3
The following list displays the different status values that may appear under the Active column.
event event.name
Lists the logging level, the message, and the count of the specified event.
Example: list event ip.007
Level: p-TRACE
Message: %I -> %I
Active: Count: 84182
groups group name
Lists the user-defined group names.
Example: list groups
pin
Lists the number of events per second as the current pin value. If no pin is defined, use the set pin command.
Example: list pin
Pin: 100 events/second
subsystems subsystem
Lists all events in a specified subsystem.
Example: list subsystems circ
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>
Lists the name, events, and a description of all subsystems.
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
Nodisplay [C] [M]
Selects and turns off messages displaying on the terminal. When turning off group and subsystem messages with the nodisplay command, you can use the logging level as a message qualifier.
Syntax: nodisplay
- event
- group
- subsystem
event event name
Suppresses the display of a specified event.
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
Notrap [C] [M]
Selects and turns off messages being trapped and sent over SNMP. You can specify the logging level of the trapped messages.
Syntax: notrap
- event
- group
- subsystem
event event name
Suppresses the trapping of the specified message.
Example: notrap event gw.019
group group name
Suppresses the trapping messages previously added to the specified group.
Example: notrap group groupb
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.
Syntax: remove
Example: 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.
Syntax: restore
Example: 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.
Syntax: retrieve
Example: 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.
Syntax: save
Example: save
Set [C] [M]
Sets the pin value and/or the timestamp.
Syntax: set
- pin
- timestamp
pin events/second
Sets the pin value to the maximum number of traps that can be sent to the SNMP host per second. Internally, the pin resets every tenth of a second. (One-tenth of the number is sent every tenth of a second.) The maximum value is 65535 events per second.
Example: set pin 100
timestamp off or timeofday or uptime
Allows you to turn on message timestamping so that when EVENT displays a message, either the time of day or uptime (number of hours, minutes, and seconds, but no date, since the router was last initialized) appears next to each message. You can turn off set timestamp.- 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 M
Displays a list of all of the available subsystems and their statistics.
Syntax: statistics
Example: 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
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.
Syntax: trap
- event
- group
- subsystem
event event name
Traps the specified message.
Example: trap event gw.019
group group name
Traps messages that were previously added to the specified group.
Example: trap group groupb
subsystem subsystem name
Traps messages associated with the specified subsystem.
Example: trap subsystem gw
[Top] [Prev] [Next] [Bottom]
docs@openroute.com
Copyright © 1998, OpenROUTE Networks, Inc. All rights
reserved.