[Top] [Prev] [Next] [Bottom]
Chapter 15
Using the Event Logging System
This chapter describes the Event Logging System (ELS). It also describes MONITR and how to control the way it collects and displays messages. MONITR provides a view of activity inside the router and on its networks. The information is divided into the following topics:
What is ELS?
Entering and Exiting the ELS Configuration Prompt
Entering and Exiting the ELS Monitoring Prompt
Entering and Exiting MONITR
Displaying ELS Through MONITR
Interpreting ELS Messages
Using ELS
Using ELS to Troubleshoot a Problem
ELS Configuration 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 for specific ELS messages.
ELS fits into the router software as shown in Figure 15-1.
Figure 15-1 ELS and MONITR in the Router Software Structure
Entering and Exiting 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 prompt,
- 1. Enter talk 6 at the * prompt.
* talk 6
Config>
The Config> prompt appears. If the prompt does not appear, press Ú again.
- 2. Enter 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>
Entering and Exiting 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 prompt,
- 1. Type talk and the pid for GWCON, 5.
* talk 5
+
The + prompt appears. If the prompt does not appear, press Ú 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 MONITR
To enter MONITR from the * prompt, type talk and the pid for MONITR, 2.
* talk 2
MONITR does not display any prompt and you cannot enter any commands; it does, however, display the messages MONITR has accumulated.
To exit MONITR and return to the * prompt, press p.
Displaying ELS Through MONITR
MONITR receives messages from the Event Logging System (ELS) and displays them on the screen.
Commands Affecting MONITR
The following commands affect MONITR:
Receiving MONITR Messages
To receive MONITR messages at your terminal, type talk 2, as described above. Then MONITR displays all the messages it has recorded since it was last invoked. While you are connected to MONITR, all messages appear as they arrive.
You can type divert and halt at the * prompt to view MONITR 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 MONITR, 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 15-2 shows the message contents from a list displayed by typing the following:
ELS> list subsystems gw
Figure 15-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 15-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 described in this chapter 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 15-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 15-1 lists the logging levels and types.
In Table 15-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 15-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 15-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 described on page 290, 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 MONITR, 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
s to pause scrolling
q to resume scrolling
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 p.
- 2. To get all ELS messages to dump to your output file, type talk 2.
- 3. Press ] 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. For more information about SNMP, see the Protocol Guide, Volume 2.
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 bridging, turn on the bridging messages by typing:
ELS> display subsystem isdn 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 to be displayed to MONITR 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.
The following example is for ISDN. Different problems may require different steps.
Example: ISDN
ISDN is not working.
- 1. Check configuration.
- 2. Using GWCON devices command, verify that the ISDN device is not disabled.
+devices
Device Hardware CSR Vector State
DEV0 SCC Ethernet 81600 94 Up
DEV1 ISDN Basic Rate 81620 93 Down
+
- 3. Type the following:
* talk 6
Config> event
ELS config> nodisplay subsystem all all
ELS config> display subsystem isdn all
ELS config> exit
Config> p
* restart
* talk 2
Check the ISDN messages.
ELS Configuration Commands
This section describes the ELS configuration commands. Enter these commands at the ELS configuration prompt, ELS config>.
? (Help)
Lists the commands that are available from the current prompt level. You can also enter ? after a command to list its options.
Syntax: ?
Example: list ?
ALL
GROUPS
PIN
STATUS
SUBSYSTEMS
Add
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
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):
Default
Resets the display or trap setting of an event, group, or subsystem back to a nonconfigured 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
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
Enables a message display for specific events, groups, or subsystems to MONITR. 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 15-2.
You can use the display command to turn on all subsystem messages at all logging levels in order to display a message to MONITR whenever any event occurs in the router.
CAUTION:
Do not do this for extended periods of time when the router is forwarding live protocal traffic because the router spends an inordinate amount of time communicating with MONITR. You should never do this 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 tkr
Exit
Returns you to the previous prompt level.
Syntax: exit
Example: exit
List
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 names and contents of groups that you have defined. If no group is defined, enter 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. Enter set pin to define a 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 subsystem all
Lists all router susbsystems, all events in a specified subsystem, or all events in all subsystems
Example 1: list subsystems
Name Events Description
ALL All subsystems
GW 99 Router base and network library
FLT 7 Filter Library
ARP 22 Address Resolution Protocol
IP 89 Internet Protocol
ICMP 20 Internet Control Message Protocol
TCP 55 TCP
UDP 6 User Datagram Protocol
BTP 13 BOOTP relay agent
RIP 19 IP Routing Information Protocol
TFTP 29 TFTP Protocol
SNMP 21 Simple Network Management Protocol
IPX 97 Internetwork Packet Exchange Protocol
AP2 68 AppleTalk Phase 2
ETH 47 Ethernet Handler
PPP 148 Point-to-Point
ISDN 41 Integrated Services Digital Network
COMP 10 Data Compression Engines
WAN 38 Wide-Area Network Manager
Include the name of a subsystem to see all the events for that subsystem.
Example 2: list subsystems isdn
Event Level Message
ISDN.027 C-INFO Hndlr N_START_RQ nt %d int %s/%d
ISDN.029 UE-ERROR Brd Crsh -- rstrng: nt %d int %s/%d
ISDN.030 UE-ERROR Tx Frm too long (%d > %d) nt %d int %s/%d
ISDN.031 U-INFO Cll rfsd frm %s:%s to %s:%s on nt %d int %s/%d
ISDN.032 C-INFO Chn %d ConnID 0x%x Cll Txcmp on nt %d int %s/%d
ISDN.035 U-INFO Inv Chn (0x%2x) ConnID 0x%x ev %s nt %d int %s/%d
ISDN.037 UE-ERROR Stat Rq bd st (0x%x) nt %d int %s/%d
ISDN.038 C-INFO Parameter download ok nt %d int %s/%d
ISDN.039 C-INFO Hndlr N_STAT_RQ nt %d int %s/%d
ISDN.041 U-INFO Too many non-resp, will try later nt %d int %s/%d
List all events in all subsystems.
Example 3: list subsystems all
You get all events, levels, and messages for each subsystem.
Nodisplay
Selects and turns off messages displaying on the terminal. When you turn 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 tkr
Notrap
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
Set
Sets the pin value and/or the timestamp. Works the same way for configuring or monitoring.
Syntax: set
- pin
- timestamp
pin events/second
Sets the pin value to the maximum number of traps that the router can send 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 MONITR 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
.
.
.
12:15:16 TKR.031: Main rcd on nt 2 int TKR/0
12:15:18 STP.028: Attmpt root TB-1, strt hello tmr
12:15:20 STP.028: Attmpt root TB-1, strt hello tmr
12:15:20 TKR.031: Main rcd on nt 2 int TKR/0
.
.
.
Trap
Selects messages to send to the remote SNMP workstation. A remote SNMP workstation is a remote workstation running the SNMP protocol.
This ELS feature should not be used 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
ELS Monitoring Commands
This section describes each of the ELS monitoring commands. Enter these commands at the ELS monitoring prompt, ELS>.
(Help)
Lists the commands that are available from the current prompt level. You can also enter ? after a command to list its options.
Syntax: ?
Example: list ?
ALL
ACTIVE
EVENT
GROUPS
PIN
SUBSYSTEMS
Clear
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
Display
Enables a message display for specific events, groups, or subsystems to MONITR. When you turn 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 15-2.
You can use the display command to turn on all subsystem messages at all logging levels in order to display a message to MONITR whenever any event occurs in the router.
CAUTION:
Do not do this for extended periods of time when the router is forwarding live protocal traffic because the router spends an inordinate amount of time communicating with MONITR. You should never do this 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
Returns to the previous prompt level.
Syntax: exit
Example: exit
List
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 describes the 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 all
Lists all events in a specified subsystem.
Example 1: list subsystems wan
Event Level Message
WAN.018 C-INFO DROP: Bridge port not fwding on nt %d int %s/%d
WAN.019 UI-ERROR Bad State (%d at %d), nt %d int %s/%d
WAN.020 UI-ERROR No Handle (%x), nt %d int %s/%d
WAN.021 UE-ERROR Int hw err nt %d int %s/%d
WAN.022 UE-ERROR Intfc hdw mssng nt %d int %s/%d
WAN.023 UI-ERROR Superfluous Link or Net up, nt %d int %s/%d
WAN.024 CE-ERROR Conn Rfsd, disabled int, nt %d int %s/%d
WAN.025 C-TRACE Rcv MAC Pkt, nt %d int %s/%d
WAN.026 C-TRACE Xmt %s Pkt, nt %d int %s/%d
WAN.027 C-TRACE Rcv %s Pkt, nt %d int %s/%d
WAN.028 CE-ERROR I_ERR on rcv nt %d int %s/%d
WAN.029 UI-ERROR Unbound WAN P-Net Fcn
WAN.030 UI-ERROR Call Fail, err %d, nt %d int %s/%d
WAN.032 U-INFO Int rsvd for rst nt %d int %s/%d
WAN.033 CE-ERROR Conn Rfsd, no inbnd allwd, nt %d int %s/%d
WAN.034 CE-ERROR Conn Rfsd, Caller %s not in ACL, nt %d int %s/%d
WAN.035 CE-ERROR Superfluous Link or Client Down, nt %d int %s/%d
WAN.036 CE-ERROR Conn Rfsd, Conn ID mismatch, nt %d int %s/%d
WAN.037 UE-ERROR Inst Fail, nt %d
If you leave out the name of the subsystem, the system lists the names, events, and descriptions of all subsystems.
Example 2: list subsystems
Lists all events in all subsystems.
Name Events Description
ALL All subsystems
GW 99 Router base and network library
FLT 7 Filter Library
ARP 22 Address Resolution Protocol
IP 89 Internet Protocol
ICMP 20 Internet Control Message Protocol
TCP 55 TCP
UDP 6 User Datagram Protocol
BTP 13 BOOTP relay agent
RIP 19 IP Routing Information Protocol
TFTP 29 TFTP Protocol
SNMP 21 Simple Network Management Protocol
IPX 105 Internetwork Packet Exchange Protocol
AP2 68 AppleTalk Phase 2
ETH 47 Ethernet Handler
PPP 151 Point-to-Point
ISDN 48 Integrated Services Digital Network
COMP 10 Data Compression Engines
WAN 38 Wide-Area Network Manager
Example 3: list subsystems all
You get all events, levels, and messages for each subsystem.
Nodisplay
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 tkr
Notrap
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 tkr error
Remove
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
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
Reloads the saved ELS configuration. If you have 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
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
Sets the pin value and/or the timestamp. Works the same way for configuring or monitoring.
Syntax: set
- pin
- timestamp
pin events/second
Sets the pin value to the maximum number of traps that the router can send 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 MONITR 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
.
.
.
12:15:16 TKR.031: Main rcd on nt 2 int TKR/0
12:15:18 STP.028: Attmpt root TB-1, strt hello tmr
12:15:20 STP.028: Attmpt root TB-1, strt hello tmr
12:15:20 TKR.031: Main rcd on nt 2 int TKR/0
.
.
.
Statistics
Displays a list of all of the available subsystems and their statistics.
Syntax: statistics
Example: statistics
Subsys Vector Exist String Active Heap
GW 50 31 1033 3 34
ARP 25 16 483 0 0
IP 80 70 1686 11 22
ICMP 20 14 335 0 0
TCP 60 55 2353 0 0
UDP 10 6 179 0 0
BTP 40 13 687 0 0
RIP 30 19 395 3 24
TFTP 35 29 769 0 0
SNMP 30 21 624 0 0
IPX 105 105 20 0 0
AP2 80 68 36 0 0
ETH 60 47 1098 0 0
PPP 155 151 5207 0 0
ISDN 55 48 2126 5 24
COMP 80 10 305 0 0
WAN 40 38 1362 0 0
Total 1345 1057 22381 15 108
Maximum: 4410 vector, 120 subsystem
Memory: 39690/480 vector + 17528/22929 data + 108 heap = 80735
Trap
Selects the message to be sent to the remote SNMP workstation. A remote SNMP workstation is a remote workstation running the SNMP protocol.
This ELS feature should not be used 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 © 1997, OpenROUTE Networks, Inc. All rights
reserved.