Managing LightStream 2020 Traps

Procedure for Turning an Individual Trap On or Off

This section tells you how to turn a particular trap on or off. Turning a trap on allows it to be passed to the MMA, even if it has a priority level below the trap filter level set for the process filter.

The default for all traps in all processes is off. When a trap is set to off, the trap is passed to the MMA only if its trap filter level is equal to or higher than the trap filter level setting of the process filter.

To turn a trap on or off, perform the following steps:

Step 1 Enter protected mode:

cli> protected

Step 2 Enter the protected mode password:

Enter password: password

Step 3 Verify that the target switch is correct:

* cli> show chassis general

If you need instructions on changing the target switch, refer to the LightStream 2020 Network Operations Guide.

Step 4 Set the SNMP community to a read/write community:

* cli> set snmp community <community name>

Where

<community name> is the SNMP read/write community that you want to access.

Step 5 If you want to turn the trap on or off for a particular process:

* cli> walksnmp lwmaTrapCliAlias

Find the process you want in the resulting list. Figure 2-1 shows the typical output from this command.

Step 6 Turn a trap on or off using either of the following procedures:

If you want the trap on for a single process:

* cli> set trap pid{<#|alias>} {on|off} <trap#> [<group name>]

If you want the trap on for all processes:

* cli> set trap global {on|off} <trap#> [<group name>]

Where

• {<#>|<alias>} is the process number or alias name.
  

• {on|off} specifies whether the trap is on or off. The default is off.
  

• <trap#> is the trap(s) you want to turn on or off. Enter the symbolic trap name or trap number. You can set multiple trap by specifying the trap numbers (for example, ndd_3 ndd_14 lcc_5), or by using the wild card character " * " to specify all traps for a particular process. If you use * , you must enclose the expression in which it appears with quotes. For example, to specify all NDD traps, type show trap "ndd*" .
  

• [<group name>] is an optional argument that defines a group of traps. For this argument to be used, the group must be defined in an ASCII file called cli.groups in the /usr/app/base/config directory. Refer to the section "Creating cli.groups File" later in this chapter for instructions on creating the cli.groups file.
  

Step 7 To display the status of the trap for a single process, enter

* cli> show trap pid {<#>|<alias>} "*"

To display the status of the trap for all processes: :

* cli> show trap "*"

The status display shows whether a trap is on, off, or disabled. If the status is either on or off, the trap is enabled. Otherwise, the trap is disabled.

At the conclusion of this procedure, each trap that you have turned on passes to the MMA whenever that trap is generated in the selected process. Traps that are turned off pass to the MMA only if they have a priority level equal to or higher than that for the process filter.

Procedure for Enabling/Disabling an Individual Trap

This section tells you how to enable or disable individual traps for all processes. When you disable a trap in an LS2020 switch, the MMA does not send it to the display device, though it will still go into the traps log. You may want to disable a trap if it appears frequently and you feel that its display is unnecessary.

To enable or disable a trap, perform the following steps:

Step 1 Enter protected mode:

cli> protected

Step 2 Enter the protected mode password:

Enter password: password

Step 3 Verify that the target switch is correct:

* cli> show chassis general

If you need instructions on changing the target switch, refer to the LightStream 2020 Network Operations Guide.

Step 4 Set the SNMP community to a read/write community:

* cli> set snmp community <community name>

Where

<community name> is the SNMP read/write community that you want to access.

Step 5 Enable or disable the trap:

* cli> set trap {enable|disable} <trap#> [<group name>]

Where

• {enable|disable} indicates whether the trap is enabled or disabled. The default is enabled.
  

• <trap#> identifies the trap(s) that you want to turn on or off. Enter the symbolic trap name or trap number. You can set multiple trap numbers by specifying the trap numbers (ndd_3 ndd_14 lcc_5), or by using the wild card character ( *) to specify all traps for a particular process. If you use the wild card character ( *) , you must enclose the expression in which it appears with quotes. For example, to specify all NDD traps, you type show trap "ndd*"
  

• [<group name>] is an optional argument used to define a group of traps that you want to turn on or off. For this argument to be used, the group must be defined in an ASCII file called cli.groups in the /usr/app/base/config directory. Refer to the section "To create the cli.groups file, perform the following steps:," later in this chapter, for instructions on creating the cli.groups file.
  

Step 6 Display the status of each trap in the MMA:

* cli> show trap "*"

The status display shows whether a trap is on, off, or disabled. If the status is either on or off, the trap is enabled. Otherwise, the trap is disabled. See the section "Procedure for Turning an Individual Trap On or Off" for a more detailed description of trap handling in a specific process.

After you perform this procedure, the disabled trap for the selected node is neither passed to the CLI nor displayed on a third-party NMS.

Working with Trap Filter Levels

This section explains how to set trap filter levels. Trap filters control which trap types are dropped, saved, or displayed. Because trap filters reside on a trap path, you might need to modify the settings of more than one filter in order to achieve your desired goal. For instance, if your system uses the default setting and you want to view a trace trap for a particular process on the console, you would need to modify the process filter, as well as the console filter. For an overview of trap filter levels, refer to the chapter entitled "About LightStream 2020 Traps."

This section discusses the four trap filters:

• The process filter determines which traps are passed from an active software process to the MMA.
  

• The console filter determines which traps are passed from the MMA to the local console for display.
  

• The chassis filter determines which traps are passed from the MMA to the CLI process or to the NMS for display.
  

• The CLI session filter determines which traps are passed from the CLI process for display on the CLI terminal.
  

By default, the trap filter levels are set so that SNMP and operational traps are displayed, and SNMP, operational, and informational traps are logged. Trace and debug traps are discarded. The default works well for most networks.

Passing Traps Through the Process Filter

Setting the trap filter level for a particular process determines which traps generated by that process will be passed to the MMA. Traps that are passed from the processes into the MMA are, by default, logged in the trap log. (For more information, see the section entitled "Logging Traps.")

The default trap filter level for all processes is informational. This level transmits all SNMP, operational, and informational traps to the MMA. This level is appropriate for most applications. If the defaults have not been changed, you would use the following procedure to let in all trace or debug traps for a specific process or to exclude all info or oper traps for a specific process

LSnode:2$   cbufpr [-hv] [-all] [-tail] -<number> [-f] [-stat] -<level> /usr/tmp/mma/mma.traplog | more

cli> show file traplog