Event Logging and Reporting |
IntroductionThe Event Logging System (ELS) is a background process that records operational event messages for a DIGITAL GS2000 line card. You can view this log of event messages from your console's CLI, or by making the events available to an SNMP-based agent such as the DIGITAL clearVISN MultiChassis Manager. You can also configure the ELS to record specific types of events and to eliminate others, depending on the level of operational detail you require. For example, you may want to view information that relates only to bridging, or information that relates only to communication between the line card and an IPX server on an Ethernet LAN. Event messages are recorded by ELS and displayed on your console in abbreviated form. Refer to the Event Logging System Messages Guide for expanded descriptions of all event messages, as well as an explanation of the message, possible causes of the event (if applicable), and possible actions you can take to correct error conditions. |
Elements of an Event Message |
Event messages are composed of the following three elements:
Figure 1 is an example of a message generated by an event. It identifies the subsystem, event number, and message text components. |
Figure 1: Sample Message Generated by an Event
Subsystem |
The Event Logging System divides GS2000 line card functionality into several operational subsystems. These include bridging and the Spanning Tree Protocol, for example. When an event occurs, a subsystem short name is added as a prefix to the event message. The short name identifies with which subsystem the event is related. In Figure 1, for example, the event short name is STP, indicating the event is related to a Spanning Tree Protocol operation. When you display the log of event messages, the prefix should help you to more accurately monitor line card activity and isolate potential problems. Refer to Table 1 for a list of subsystems and their associated short names. You can configure the ELS to record only those events generated by one or more specific subsystems, or all subsystems. Recording events for one or a few specific subsystems can help you focus on events related to a particular operation or set of operations. Refer to the Selecting Which Events Are Logged section for information about recording events generated by one or more subsystems. |
Subsystem Description |
Subsystem Short Name |
Router base and network library |
GW |
Address Resolution Protocol |
ARP |
Internet Protocol |
IP |
Internet Control Message Protocol |
ICMP |
Transmission Control Protocol |
TCP |
User Datagram Protocol |
UDP |
BooTP relay agent |
BTP |
Trivial File Transfer Protocol |
TFTP |
Simple Network Management Protocol |
SNMP |
Source Routing Transparent Bridge |
SRT |
Spanning Tree Protocol |
STP |
Filter Library |
FLT |
IP Routing Information Protocol |
RIP |
Exterior Gateway Protocol |
EGP |
Open SPF-Based Routing Protocol |
OSPF |
OSPF Multicast extensions |
MSPF |
DECnet |
DN |
Xerox Networking Systems Protocol |
XNS |
Internetwork Packet Exchange Protocol |
IPX |
AppleTalk |
APL |
AppleTalk Phase 2 |
AP2 |
Apollo Domain Protocol |
DDS |
IP Protocol Net |
IPPN |
All subsystems |
Event Number The Event Logging System automatically assigns a unique number to each event message generated by a subsystem. In Figure 1, for example, the event number is 028. It is separated from the subsystem short name by a period. The short name and event number, together, identify an individual event. You can use the subsystem short name and event number as a parameter for specific ELS configuration and monitoring commands. Only the event indicated by the specified subsystem and event are affected by the ELS command. |
Message Text An abbreviated description of a specific event is provided in the text portion of an event message, as shown in Figure 1. For example, the following message text indicates that the instance of STP on VSD 1 is declaring itself as root, and has restarted the BPDU Hello Timer. Attmpt root TB-1, strt hello tmr The Event Logging System Messages Guide provides expanded descriptions of all abbreviated messages, as well as an explanation of the message, possible causes of the event (if applicable), and possible actions you can take to correct error conditions. Some event messages include fields that display variable values, such as network and interface numbers, source addresses, and error codes. Refer to the Event Logging System Messages Guide for a detailed discussion about these variables. |
Logging Levels and Event Types |
The logging level is a further classification of messages according to the type of event that generated a message. For example, a particular type of event might typically be caused by an unusual internal error. In such a case, ELS associates the UI-ERROR (unusual internal error) logging level with the event. Table 2 shows the full list of logging levels and the type of condition that generates events associated with the level. |
Logging Level |
Event Type |
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 all informational comment levels (recommended default) |
P-TRACE |
Per packet trace |
U-TRACE |
Unusual operation trace message |
C-TRACE |
Common operation trace message |
TRACE |
Includes all trace levels above |
ALL |
Includes all logging levels |
The logging level can be used for informational purposes, and to provide you with the ability to further narrow the scope of recorded events. Assume, for example, the following event message is displayed on your console: |
SNMP.005 no access; comm "community", hst source_address |
If you are interested in knowing the type of event that generated the message, you
would look up the event using the subsystem short name and event number (SNMP.005) in the Event Logging System Messages Guide. The
guide lists the logging level as U-TRACE, indicating the message is the result of an
"unusual operation packet trace." If you want to narrow the scope of events recorded by ELS to only those involving unusual operation packet traces, you would specify U-TRACE as the logging level when configuring ELS. Refer to the Selecting Which Events Are Logged section for information about how to do so. |
Modes of Configuration |
You can configure ELS in nonvolatile memory and in volatile memory. ELS configurations that you set in nonvolatile memory (NVRAM) require that you restart the line card to take effect. These settings survive power outages and line card restarts. This method of setting values is most useful when configuring selection criteria for events that you want to monitor on a regular basis. You configure ELS in NVRAM from the Config prompt. ELS configurations you set in volatile memory do not require that you restart the line card to take effect. These settings do not survive power outages and line card restarts unless you save them to a reserved portion of NVRAM (Refer to the Saving and Managing a Configuration in NVRAM section later in this document). Setting ELS configurations in volatile memory is most useful when configuring selection criteria you want to remain in effect only temporarily, and that you are likely to change from moment to moment as you troubleshoot a particular problem. You configure ELS in volatile memory from the Monitor prompt. |
Commands Used to Log Events |
You can view the log of event messages from your console's CLI, or by sending the events to SNMP. The process of sending specific events over SNMP is referred to as trapping. If sent to SNMP, the events are viewed using an SNMP-based agent such as the DIGITAL clearVISN MultiChassis Manager. The tasks you perform to select which events are logged are the same whether you plan to view the messages via the CLI, or through an SNMP agent. However, the commands you use are different. Table 3 lists the commands you use to record and clear events for viewing using the CLI, and the commands used to trap events and clear traps for SNMP. |
Command |
Description |
display |
Specifies which events are logged by ELS so you can display them using the CLI. |
nodisplay |
Clears previously configured events so they are not logged by ELS for display using the CLI. |
trap |
Specifies which events are trapped and sent to SNMP. |
notrap |
Clears previously configured events so they are not trapped and sent to SNMP. |
Refer to the Displaying the Event Log section for information about how to display the specified events through the CLI. For information about how to display events sent to SNMP, refer to the appropriate vendor documentation that supports the particular SNMP-based agent you are using. |
Special Convention Used in This Section The following sections present instructions for recording events you plan to view through the CLI and those instructions used to view events via SNMP. The steps you perform are the same for both viewing methods; however, the commands are different. A command used to trap events, or to clear a trap, are enclosed in parentheses and immediately follow the command used to record events to be viewed via the CLI. Example You can use only one command (display or trap) at a time. Do not enter the parentheses when using the SNMP-related commands. |
You can configure ELS to record all events generated by one or more subsystems. For example, you might want to log all events related to the ARP subsystem. Once you configure ELS to record all events generated by a subsystem, that setting remains in effect until you clear it. Assume, for example, you first configure ELS to record events generated by the STP subsystem, and you later decide you want to record events from only the ARP subsystem. In this situation, you must both clear the STP subsystem setting and configure ELS to record ARP subsystem events. If you do not clear the STP subsystem, events from both the STP and ARP subsystems are recorded. Recording Events By Subsystem |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
3 |
Enter display (trap) subsystem subsystem-shortname, where subsystem-shortname is the short name for the desired subsystem. Refer to Table 1 for a list of short names, or enter display (trap) subsystem ? at the ELS config> prompt to display a list of short names on your console. |
4 |
Press Return. The ELS is configured to record all messages generated by the specified subsystem using the Standard logging level, and the ELS config> prompt is displayed. If ELS was previously configured to record events from other subsystems or using other logging levels, those settings also remain in effect until you clear them. |
5 |
If you want to configure ELS to display events generated by yet another subsystem, repeat steps 3 and 4. |
6 |
Restart the line card if you want the new configuration settings to take effect. |
Example or ELS config>trap subsystem arp Clearing Events By Subsystem |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
Enter nodisplay (notrap) subsystem subsystem-shortname, where subsystem-shortname is the short name for the subsystem you want to clear. Refer to Table 1 for a list of short names, or enter nodisplay (notrap) subsystem ? at the ELS config> prompt to display a list of short names on your console. |
|
Press Return. The ELS is configured not to record messages generated by the specified subsystem, and the ELS config> prompt is displayed. If ELS was previously configured to record events from other subsystems, those settings remain in effect until you clear them. |
|
5 |
If you want to clear event recording for yet another subsystem, repeat steps 3 and 4. |
6 |
Restart the line card if you want the new configuration settings to take effect. |
Example or ELS config>notrap subsystem arp |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
Enter display (trap) subsystem subsystem-shortname logging-level, where subsystem-shortname is the short name for the desired subsystem and logging-level is the desired logging level. Refer to Table 1 for a list of short names, or enter display (trap) subsystem ? at the ELS config> prompt to display a list of short names on your console. Refer to Table 2 for a list of logging levels, or enter display (trap) subsystem subsystem-shortname ? at the ELS config> prompt to display a list of logging levels. |
|
Press Return. The ELS is configured to record all messages generated by the specified subsystem and associated with the logging level, and the ELS config> prompt is displayed. If ELS was previously configured to record events associated with other logging levels in the same or other subsystems, those settings also remain in effect until you clear them. |
|
5 |
If you want to configure ELS to record all events associated with other logging levels in the same or other subsystems, repeat steps 3 and 4. |
6 |
Restart the line card if you want the new configuration settings to take effect. |
Example or ELS config>trap subsystem stp ce-error Clearing Events By Subsystem and Logging Level |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
Enter nodisplay (notrap) subsystem subsystem-shortname logging-level, where subsystem-shortname is the short name for the desired subsystem and logging-level is the logging level you want to clear. Refer to Table 1 for a list of short names, or enter nodisplay (notrap) subsystem ? at the ELS config> prompt to display a list of short names on your console. Refer to Table 2 for a list of logging levels, or enter nodisplay (notrap) subsystem subsystem-shortname ? at the ELS config> prompt to display a list of logging levels. |
|
Press Return. The ELS is configured not to record messages generated by the specified subsystem and logging level, and the ELS config> prompt is displayed. If ELS was previously configured to record events associated with other logging levels in the same or other subsystems, those settings remain in effect until you clear them. |
|
5 |
If you want to clear event recording associated with other logging levels in the same or other subsystems, repeat steps 3 and 4. |
6 |
Restart the line card if you want the new configuration settings to take effect. |
Example or ELS config>notrap subsystem stp ce-error |
You can configure ELS to record all occurrences of a particular event. For example, you might want to record each time STP restarts the BPDU Hello Timer. The event number for this event is STP.028. Once you configure ELS to record all occurrences of an event, that setting remains in effect until you clear it. Assume, for example, you first configure ELS to record each time STP restarts the BPDU Hello Timer, and you later decide you want to record only when a BootP request is received on an interface (event number BTP.001). In this situation, you must both clear the STP.028 event number and configure ELS to record each time a BootP request is received on an interface. If you do not clear the STP.028 event number, all occurrences of both events (STP.028 and BTP.001) are recorded. Recording All Occurrences of an Event |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
Enter display (trap) event subsystem.event#, where subsystem.event# is the event number for the event you want to record. Refer to the Viewing Current Configuration Settings section for information about how to display event numbers associated with one or all subsystems. |
|
Press Return. The ELS is configured to record all occurrences of the specified event, and the ELS config> prompt is displayed. If ELS was previously configured to record all occurrences of other individual events, those settings also remain in effect until you clear them. |
|
5 |
If you want to configure ELS to record all occurrences of another individual event, repeat steps 3 and 4. |
6 |
Restart the line card if you want the new configuration settings to take effect. |
Example or ELS config>trap event stp.028 Clearing All Occurrences of an Event |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
Enter nodisplay (notrap) event subsystem.event#, where subsystem.event# is the event number for the event you want to clear. Refer to the Viewing Current Configuration Settings section for information about how to display event numbers associated with one or all subsystems. |
|
Press Return. The ELS is configured not to record all occurrences of the specified event, and the ELS config> prompt is displayed. If ELS was previously configured to record all occurrences of other individual events, those settings remain in effect until you clear them. |
|
5 |
If you want to clear recording of all occurrences of other individual events, repeat steps 3 and 4. |
6 |
Restart the line card if you want the new configuration settings to take effect. |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
Enter add group-name subsystem.event-number, where group-name is the name of a new group you want to create or is the name of an existing group to which you want to add an event, and subsystem.event-number is the name of the event you want to add to the group. The group name must begin with an alphabetic character. All subsequent characters can be alphabetic or numeric. ELS is case sensitive with respect to group names. The name you assign to a group should reflect the type of events the group contains, so that you can more easily distinguish between groups. For example, a group that is used to list particular types of Spanning Tree Protocol events might be named stp2. |
|
Press Return. The group is created or modified with the specified event entries, and the ELS config> prompt is displayed. |
|
5 |
Repeat steps 3 and 4 for each event you want to add to a group. |
6 |
Restart the line card if you want the new configuration settings to take effect. |
Example and ELS config>add stp2 stp.028 Deleting an Event From a Group and Deleting an Entire Group To delete an event from a group or to delete and entire group, perform the following steps: |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
If you want to delete an event from a group, enter delete group-name subsystem.event-number, where group-name is the name of the group containing the event you want to delete, and subsystem.event-number is the name of the event you want to delete. ELS is case sensitive with respect to group names. If you want to delete an entire group, including its contents, enter delete group-name all, where group-name is the name of the group you want to delete. Refer to the Viewing Current Configuration Settings section for information about how to display a list of current groups and the events that compose each group. |
|
Press Return. The event or group is deleted as specified. If you are deleting the last event in a group, a message is displayed to notify you of the fact. If you are not deleting the last event in a group, the ELS config> prompt is displayed. |
|
5 |
If you are deleting events from a group and you want to delete another event, repeat steps 3 and 4 for each event you want to delete from the group. |
6 |
Restart the line card if you want the deletion to take effect. |
Example and ELS config>delete stp2 all Recording All Occurrences of Events in a Group |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
Enter display (trap) group group-name, where group-name is the name of the group containing the events you want to record. Refer to the Viewing Current Configuration Settings section for information about how to display a list of current groups and the events that compose each group. |
|
Press Return. The ELS is configured to record all occurrences of the events specified in the group, and the ELS config> prompt is displayed. If ELS was previously configured to record all occurrences of events in other groups, those settings also remain in effect until you clear them. |
|
5 |
If you want to configure ELS to record all occurrences of events in another group, repeat steps 3 and 4. |
6 |
Restart the line card if you want the new configuration settings to take effect. |
Example or ELS config>trap group mygroup Clearing All Occurrences of Events in a Group |
Step |
Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
Enter nodisplay (notrap) group group-name, where group-name is the name of the group for which you do not want to record events. |
|
Press Return. ELS is configured not to record all occurrences of events in the specified group, and the ELS config> prompt is displayed. If ELS was previously configured to record all occurrences of events in other groups, those settings remain in effect until you clear them. |
|
5 |
If you want to clear recording of events in another group, repeat steps 3 and 4. |
6 |
Restart the line card if you want the new configuration settings to take effect. |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
3 |
Enter clear. |
4 |
Press Return. The following message is displayed: You are about to clear all ELS configuration
information. |
5 |
If you want to clear all ELS configuration information, enter y. If you do not want to clear all ELS configuration information, enter n. |
6 |
Press Return. The ELS config> prompt is displayed. |
7 |
Restart the line card if you want the new configuration setting to take effect. All events for which ELS was previously configured to log are no longer recorded. |
Setting Maximum Number of Traps Per Second You can configure ELS to limit the number of events that are trapped per second. This option is most useful when conditions result in such large numbers, or "bursts," of events that you are overwhelmed by the data. Reducing the maximum number of traps per second effectively results in a sampling of the events. The default value for the maximum number of traps per second is 0 (zero), meaning an unlimited number of traps per second is permitted. The maximum number of traps per second can be reset to its default setting by using the clear command. (Refer to the Clearing All Previously Configured Events section.) To set the maximum number of traps per second, perform the following steps: |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
3 |
Enter set pin. |
4 |
Press Return. The following message is displayed: events/second [0]? |
5 |
Enter the maximum number of events per second you want trapped. The range of acceptable values is 1 through 57600 traps per second. The default is 0 (zero), an unlimited number of events per second. |
6 |
Press Return. The maximum number of events trapped is set, and the ELS config> prompt is displayed. |
7 |
Restart the line card if you want the new configuration setting to take effect. |
Viewing Current Configuration Settings You can view several reports that detail the current ELS configuration settings in NVRAM. You may find these reports helpful if, for example, you want to check the settings before restarting the line card and before displaying the event log. (Refer to the Displaying the Event Log section for information about how to display events.) To view current configuration settings in NVRAM, perform the following steps: |
Step | Action |
1 |
At the Config prompt (Config>), enter els. |
2 |
Press Return. The ELS config> prompt is displayed. |
3 |
Enter list command-option, where command-option is the command you must enter to display the desired information. Refer to Table 4 for a list of commands, and for a description of the type of information that is displayed when you enter the command. |
4 |
Press Return. A report containing the desired information is displayed and the ELS config> prompt is displayed. |
Command Option |
Description |
groups |
Lists all group names and the events that compose each group. |
pin |
Displays the current maximum number of traps per second (pin). |
status |
Lists all event logging configurations by subsystem, subsystem and logging level, group, and event number. The information includes configurations for events that will be displayed through the CLI and those to be trapped for use by SNMP. |
subsystem |
Lists the short names for all possible subsystems, the number of different events that can be generated by the subsystem, and an expanded description of the subsystem short name. |
subsystem subsystem |
Lists all possible events that can be generated by a specified subsystem, where subsystem is the short name for the subsystem for which you want to list events. The information included for each event includes the event number, the logging level for the event, and a short description of the event. |
subsystems all |
Lists all possible events that can be generated by all subsystems. The information included for each event includes the event number, the logging level for the event, and a short description of the event. |
all |
Lists the following configuration information for events to be displayed through the CLI, and those to be trapped for use by SNMP:
|
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter display (trap) subsystem subsystem-shortname, where subsystem-shortname is the short name for the desired subsystem. Refer to Table 1 for a list of short names, or enter display (trap) subsystem ? at the ELS> prompt to display a list of short names on your console. |
|
Press Return. The ELS is configured to record all messages generated by the specified subsystem, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events from other subsystems, or if ELS was configured in NVRAM, those settings also remain in effect until you clear them. |
|
5 |
If you want to configure ELS to display events generated by yet another subsystem, repeat steps 3 and 4. |
Example or ELS>trap subsystem arp Clearing Events By Subsystem To clear event recording by subsystem, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter nodisplay (notrap) subsystem subsystem-shortname, where subsystem-shortname is the short name for the subsystem you want to clear. Refer to Table 1 for a list of short names, or enter nodisplay (notrap) subsystem ? at the ELS> prompt to display a list of short names on your console. |
|
Press Return. The ELS is configured not to record messages generated by the specified subsystem, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events from other subsystems, or if other subsystems were configured in NVRAM, those settings remain in effect until you clear them. |
|
5 |
If you want to clear event recording for yet another subsystem, repeat steps 3 and 4. |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter display (trap) subsystem subsystem-shortname logging-level, where subsystem-shortname is the short name for the desired subsystem and logging-level is the desired logging level. Refer to Table 1 for a list of short names, or enter display (trap) subsystem ? at the ELS> prompt to display a list of short names on your console. Refer to Table 2 for a list of logging levels, or enter display (trap) subsystem subsystem-shortname ? at the ELS> prompt to display a list of logging levels. |
|
Press Return. The ELS is configured to record all messages generated by the specified subsystem and associated with the specified logging level, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events associated with other logging levels in the same or other subsystems, or if other subsystems or logging levels were configured in NVRAM, those settings also remain in effect until you clear them. |
|
5 |
If you want to configure ELS to record all events associated with other logging levels in the same or other subsystems, repeat steps 3 and 4. |
Example or ELS>trap subsystem stp ce-error Clearing Events By Subsystem and Logging Level To clear events by subsystem and logging level, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter nodisplay (notrap) subsystem subsystem-shortname logging-level, where subsystem-shortname is the short name for the desired subsystem and logging-level is the logging level you want to clear. Refer to Table 1 for a list of short names, or enter nodisplay (notrap) subsystem ? at the ELS> prompt to display a list of short names on your console. Refer to Table 2 for a list of logging levels, or enter nodisplay (notrap) subsystem subsystem-shortname ? at the ELS> prompt to display a list of logging levels. |
|
Press Return. The ELS is configured not to record messages generated by the specified subsystem and logging level, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events associated with other logging levels in the same or other subsystems, or if other subsystems or logging levels were configured in NVRAM, those settings remain in effect until you clear them. |
|
5 |
If you want to clear event recording associated with other logging levels in the same or other subsystems, repeat steps 3 and 4. |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter display (trap) event subsystem.event#, where subsystem.event# is the event number for the event you want to record. Refer to the Viewing Current Configuration Settings and Statistics section for information about how to display event numbers associated with one or all subsystems. |
|
Press Return. The ELS is configured to record all occurrences of the specified event, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events based on other criteria, or if other event selection criteria were configured in NVRAM, those settings also remain in effect until you clear them. |
|
5 |
If you want to configure ELS to record all occurrences of another individual event, repeat steps 3 and 4. |
Example or ELS>trap event stp.028 Clearing All Occurrences of an Event To clear all occurrences of an event, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter nodisplay (notrap) event subsystem.event#, where subsystem.event# is the event number for the event you want to clear. Refer to the Viewing Current Configuration Settings and Statistics section for information about how to display event numbers associated with one or all subsystems. |
|
Press Return. The ELS is configured not to record all occurrences of the specified event, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events based on other criteria, or if other event selection criteria were configured in NVRAM, those settings remain in effect until you clear them. |
|
5 |
If you want to clear recording of all occurrences of other individual events, repeat steps 3 and 4. |
Example or ELS>notrap event stp.028 Recording and Clearing Events By Group You can configure ELS to record all occurrences of each event that is included in a group. For example, you might want to regularly record each time STP restarts the BPDU Hello Timer (event number STP.028), and each time a BPDU is received from a specified MAC address (event number STP.001). A group is a customized list of one or more event numbers that you define as members of a group. Configuring ELS using groups is most useful when you have combinations of events that you need to record regularly and helps eliminate the need to enter the desired event numbers individually. The name you assign to a group when you create it should reflect the type of events the group contains so that you can more easily distinguish between groups. Refer to the Configuring ELS in Nonvolatile Memory section for information about how to create, modify, and delete groups. Once you configure ELS to record all occurrences of events that are
members of a group, that setting remains in effect until you clear it. |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter display (trap) group group-name, where group-name is the name of the group containing the events you want to record. |
|
Press Return. The ELS is configured to record all occurrences of the events specified in the group, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events based on other criteria, or if other event selection criteria were configured in NVRAM, those settings also remain in effect until you clear them. |
|
5 |
If you want to configure ELS to record all occurrences of events in another group, repeat steps 3 and 4. |
Example or ELS>trap group mygroup Clearing All Occurrences of Events in a Group To clear all occurrences of events in a group, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter nodisplay (notrap) group group-name, where group-name is the name of the group for which you do not want to record events. |
|
Press Return. ELS is configured not to record all occurrences of events in the specified group, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events based on other criteria, or if other criteria are configured in NVRAM, those settings remain in effect until you clear them. |
|
5 |
If you want to clear recording of events in another group, repeat steps 3 and 4. |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter clear subsystem subsystem-shortname, where subsystem-shortname is the short name for the subsystem you want to clear. Refer to Table 1 for a list of short names, or enter list subsystem ? at the ELS> prompt to display a list of short names on your console. |
|
Press Return. The ELS deletes all historical entries in the log that match the specified subsystem, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events from other subsystems, or if other subsystems were configured in NVRAM, those settings remain in effect until you clear them. |
|
5 |
If you want to clear historical entries for yet another subsystem, repeat steps 3 and 4. |
Clearing Historical Entries By Subsystem and Logging Level |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter clear subsystem subsystem-shortname logging-level, where subsystem-shortname is the short name for the desired subsystem and logging-level is the logging level you want to clear. Refer to Table 1 for a list of short names, or enter list subsystem ? at the ELS> prompt to display a list of short names on your console. Refer to Table 2 for a list of logging levels, or enter list subsystem subsystem-shortname ? at the ELS> prompt to display a list of events and associated logging levels. |
|
Press Return. The ELS deletes historical entries from the log that match the specified subsystem and logging level, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events associated with other logging levels in the same or other subsystems, or if other subsystems or logging levels were configured in NVRAM, those settings remain in effect until you clear them. |
|
5 |
If you want to clear historical entries associated with other logging levels in the same or other subsystems, repeat steps 3 and 4. |
Clearing All Historical Entries of a Specific Event To clear all historical entries of a specific event, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter clear event subsystem.event#, where subsystem.event# is the event number for the event you want to clear. Refer to the Viewing Current Configuration Settings and Statistics section for information about how to display event numbers associated with one or all subsystems. |
|
Press Return. The ELS deletes all historical entries of the specified event from the log, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events based on other criteria, or if other event selection criteria were configured in NVRAM, those settings remain in effect until you clear them. |
|
5 |
If you want to clear recording of all occurrences of other individual events, repeat steps 3 and 4. |
Clearing Historical Entries By Group To clear all historical entries associated with events in a group, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
Enter clear group group-name, where group-name is the name of the group for which you do not want to record events. |
|
Press Return. ELS deletes all historical entries associated with events in the specified group, and the ELS> prompt is displayed. If ELS was previously configured in volatile memory to record events based on other criteria, or if other criteria are configured in NVRAM, those settings remain in effect until you clear them. |
|
5 |
If you want to clear recording of events in another group, repeat steps 3 and 4. |
Setting Maximum Number of Traps Per Second You can configure ELS to limit the number of events that are trapped per second. This option is most useful when conditions result in such large numbers, or "bursts," of events that you are overwhelmed by the data. Reducing the maximum number of traps per second effectively results in a sampling of the events. The default value for the maximum number of traps per second in volatile memory is equal to the maximum number of traps/second value set for NVRAM. (Refer to the Configuring ELS in Nonvolatile Memory section.) To set the maximum number of traps per second, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
3 |
Enter set pin. |
4 |
Press Return. The following message is displayed: events/second [0]? |
5 |
Enter the maximum number of events per second you want trapped. The range of acceptable values is 1 through 57600 traps per second. A value of 0 (zero), indicates an unlimited number of events per second. |
6 |
Press Return. The maximum number of events trapped is set, and the ELS> prompt is displayed. |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
3 |
Enter save. |
4 |
Press Return. The volatile settings are stored in NVRAM, separate from ELS settings configured from the Config prompt. The ELS> prompt is displayed. |
Retrieving Settings From NVRAM To retrieve previously saved (volatile settings) from NVRAM, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
3 |
Enter retrieve. |
4 |
Press Return. The settings stored in NVRAM are retrieved and reloaded as an ELS volatile configuration, and the ELS> prompt is displayed. The NVRAM copy of the settings from which the reload occurred is retained. (Refer to the Deleting Settings Saved in NVRAM section for information about how to delete (remove) the NVRAM copy.) |
Deleting Settings Saved in NVRAM To delete (remove) previously saved (volatile) settings from NVRAM, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
3 |
Enter remove. |
4 |
Press Return. The settings stored in NVRAM are deleted and the ELS> prompt is displayed. |
You can restore ELS volatile memory configuration defaults using the restore command. (Refer to Plug and Play Default Settings for a list of ELS volatile memory configuration default settings.) Restoring the default settings also stops ELS from recording events based on prior settings in volatile memory. However, ELS continues to record events that match selection criteria configured in NVRAM, if any. To restore ELS volatile memory configuration defaults, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
3 |
Enter restore. |
4 |
Press Return. The default settings are restored and the ELS> prompt is displayed. |
Viewing Current Configuration Settings and Statistics Viewing Current Configuration Settings You can view several reports that detail the current ELS configuration settings in volatile memory. Some reports include a count of specific events being recorded. You may find these reports helpful if, for example, you want to check the settings before displaying the event log. (Refer to the Displaying the Event Log section for information about how to display events.) To view current configuration settings in volatile memory, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
3 |
Enter list command-option, where command-option is the command you must enter to display the desired information. Refer to Table 5 for a list of commands, and for a description of the type of information that is displayed when you enter the command. |
4 |
Press Return. A report containing the desired information is displayed and the ELS> prompt is displayed. |
Command Option |
Description |
active subsystem-name |
Lists the following information about a specific subsystem, where subsystem-name is the subsystem:
|
event event-name |
Displays the following information about the specified event, where event-name is the name of the event:
|
groups |
Lists all group names and the events that compose each group. |
pin |
Displays the current maximum number of traps per second (pin). |
subsystems |
Lists the short names for all possible subsystems, the number of different events that can be generated by the subsystem, and an expanded description of the subsystem short name. |
subsystem subsystem |
Lists all possible events that can be generated by a specified subsystem, where subsystem is the short name for the subsystem for which you want to list events. The information included for each event includes the event number, the logging level for the event, and a short description of the event. |
subsystems all |
Lists all possible events that can be generated by all subsystems. The information included for each event includes the event number, the logging level for the event, and a short description of the event. |
all |
Lists the following configuration information:
|
Example ELS>list active stp |
Event | Active | Count |
STP.003 | D | 0 |
STP.004 | D | 0 |
STP.005 | D | 0 |
STP.006 | D | 0 |
STP.007 | D | 0 |
STP.008 | D | 0 |
STP.009 | D | 0 |
STP.013 | D | 0 |
STP.014 | D | 0 |
STP.015 | D | 0 |
STP.016 | D | 0 |
STP.021 | D | 0 |
STP.022 | 4397 | |
STP.024 | D | 0 |
STP.026 | D | 0 |
STP.028 | D | 4397 |
STP.029 | D | 0 |
STP.030 | D | 0 |
STP.032 | D | 0 |
STP.033 | D | 0 |
STP.034 | D | 0 |
Viewing Configuration Memory Statistics You can view statistics about ELS configuration volatile memory categorized by subsystem. The report includes the following information for each subsystem:
The report also includes totals for each of the above bulleted items, the maximum number of events (vector) of all subsystems, the maximum number of subsystems, and total heap memory size. To view configuration memory statistics, perform the following steps: |
Step | Action |
1 |
At the Monitor prompt (Monitor>), enter els. |
2 |
Press Return. The ELS> prompt is displayed. |
3 |
Enter statistics. |
4 |
Press Return. A report containing configuration memory is displayed, and the ELS> prompt is displayed. |
Displaying the Event Log |
The event log records all event messages until the buffer is full. Each new event then overwrites the oldest existing event in the log. The event log also displays new messages on your console as they occur. The categories of information and level of detail displayed varies, depending on how you configure ELS. (Refer to the Selecting Which Events Are Logged section for information about how to record and display selected information.) You can display the log of recorded event messages using either the CLI, or using an SNMP-based agent such as the DIGITAL clearVISN MultiChassis Manager. This section describes how to display the log using the CLI. Refer to the appropriate documentation supporting the particular SNMP agent you are using for information about displaying events. Choosing the Method of DisplayYou can display the event log from the CLI either directly or indirectly. When displaying the event log directly, you view events only. You cannot perform any other task while viewing the log using this method. Displaying the event log indirectly enables you to view events while entering commands from any CLI prompt (Main>, Config>, Monitor>, Bridge>, and so on). Although this method causes the command line to scroll off the screen as events are displayed, it enables you to more easily view the effect of configuration changes as you make them. This capability may also be of particular use if you need to view events that occur immediately after startup, but that might otherwise scroll off the screen if you first had to access the event log from the Main prompt (Main>), as described in the Displaying and Exiting the Event Log section. Displaying the event log indirectly does not affect output accessed via remote devices. You can set the method of display (direct or indirect) from either the Config> prompt or the Monitor prompt (Monitor>). Setting the method of display from the Config> prompt takes effect immediately, without restarting the line card. Because it is stored in NVRAM, the setting survives resets and loss of power. Setting the method of display from the Monitor prompt (Monitor>) also takes effect immediately, without restarting the line card. However, because the setting is stored in volatile memory it does not survive resets and loss of power. To choose the method of display, perform the following steps: |
Step | Action |
1 |
At either the Config> prompt or the Monitor prompt (Monitor>), enter set output method-of-display, where method-of-display is either the default or the console command option. The default command sets the method of display to direct (you can only view events). The console command sets the method of display to indirect (you can view events while entering commands). The default is the default command. |
2 |
Press Return. The chosen method of display is set. If you set the method of display to default, refer to Displaying and Exiting the Event Log section for information about how to view the event log directly. If you set the method of display to console, the event log is automatically displayed at any CLI prompt you access. |
Step | Action |
1 |
At the Main prompt (Main>) enter Events. |
2 |
Press Return. The event log is displayed. All existing event messages are displayed. New event messages are also added to the display as they occur. |
Displaying the Event Log Indirectly If you set the method of display to console, the event log is automatically displayed at any CLI prompt you access. If you log out after setting the method of display to console and then log in again, the stream of events that are output to the console are immediately displayed. To terminate the stream of output, at the Main prompt enter halt 2 and press Return. Exiting the Event Log If you are viewing the event log directly, enter the intercept character to exit the event log. The default intercept character is Ctrl/P. If you are displaying the event log indirectly, you can cancel display of events by entering set output default command at either the Config or Monitor prompt. Refer to the Choosing the Method of Display section for information about how to do so. |
Advanced Methods for Viewing EventsRefer to Appendix A in the Management guide for information about the following topics that may be useful when viewing the event log directly. |
Printing ELS Output |
You can obtain a hard copy printout of event messages, including startup messages, by attaching a printing terminal in place of the console terminal. You must then configure the line card so that events are displayed directly, as described in the Displaying the Event Log section. |