Table Of Contents
Alarm Filtering Support in the Cisco Entity Alarm MIB
Prerequisites for Alarm Filtering Support in the Cisco Entity Alarm MIB
Restrictions for Alarm Filtering Support in the Cisco Entity Alarm MIB
Information About Alarm Filtering Support in the Cisco Entity Alarm MIB
How to Configure Alarm Filtering for Syslog Messages and SNMP Notifications
Configuring Alarm Filtering for Syslog Messages
Configuring Alarm Filtering for SNMP Notifications
Configuration Examples for Alarm Filtering Support in the Cisco Entity Alarm MIB
Configuring Alarm Filtering for Syslog Messages: Example
Configuring Alarm Filtering for SNMP Notifications: Example
Feature Information for Alarm Filtering Support in the Cisco Entity Alarm MIB
Alarm Filtering Support in the Cisco Entity Alarm MIB
First Published: August 22, 2005Last Updated: February 27, 2007The Alarm Filtering Support in the Cisco Entity Alarm MIB feature implements the alarm filter profile capability defined in CISCO-ENTITY-ALARM-MIB. Also implemented are configuration commands to control the severity of syslog messages and SNMP notifications triggered by the alarms.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Alarm Filtering Support in the Cisco Entity Alarm MIB" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Alarm Filtering Support in the Cisco Entity Alarm MIB
•
•
•
•
•
Prerequisites for Alarm Filtering Support in the Cisco Entity Alarm MIB
•
•
Restrictions for Alarm Filtering Support in the Cisco Entity Alarm MIB
•
Information About Alarm Filtering Support in the Cisco Entity Alarm MIB
To configure alarm filtering in the Cisco Entity Alarm MIB, you should understand the following concepts:
CISCO-ENTITY-ALARM-MIB
The CISCO-ENTITY-ALARM-MIB provides a management client with the capability to monitor alarms generated by physical entities in a network that are identified in the entPhysicalTable of the Entity-MIB (RFC 2737). Examples of these physical entities are chassis, fans, modules, ports, slots, and power supplies. The management client interfaces with an SNMP agent to request access to objects defined in the CISCO-ENTITY-ALARM-MIB.
ceAlarmGroup
The ceAlarmGroup is a group in the CISCO-ENTITY-ALARM-MIB that defines objects that provide current statuses of alarms and the capability to instruct an agent to stop (cut off) signaling for any or all external audible alarms.
Following are the objects in ceAlarmGroup:
•
•
•
•
•
•
•
ceAlarmFilterProfileTable
The ceAlarmFilterProfileTable filters alarms according to configured alarm lists. The filtered alarms are then sent out as SNMP notifications or syslog messages, based on the alarm list enabled for each alarm type. This table is defined in the CISCO-ENTITY-ALARM-MIB and implemented in the group ceAlarmGroup.
ceAlarmFilterProfile
An alarm filter profile controls the alarm types that an agent monitors and signals for a corresponding physical entity. The ceAlarmFilterProfile object holds an integer value that uniquely identifies an alarm filter profile associated with a corresponding physical entity. When the value is zero, the agent monitors and signals all alarms associated with the corresponding physical entity.
How to Configure Alarm Filtering for Syslog Messages and SNMP Notifications
This section contains the following tasks:
•
•
Configuring Alarm Filtering for Syslog Messages
This task describes how to configure the alarm severity threshold for generating syslog messages. When you use this command, the alarm severity threshold is included in the running configuration and automatically applied when the configuration is reloaded.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Alarm Filtering for SNMP Notifications
This task describes how to configure the alarm severity threshold for generating SNMP notifications. When you use this command, the alarm severity threshold is included in the running configuration and automatically applied when the configuration is reloaded.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuration Examples for Alarm Filtering Support in the Cisco Entity Alarm MIB
This section provides the following configuration examples:
•
•
Configuring Alarm Filtering for Syslog Messages: Example
The following example shows how to configure an alarm filter for syslog messages:
Router# enable Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# logging alarm 2 Router(config)# exit Router#Router# show facility-alarm statusSystem Totals Critical: 1 Major: 0 Minor: 0Source Severity Description [Index] ------ -------- ------------------- Fa0/0 CRITICAL Physical Port Link Down [0] Fa0/1 INFO Physical Port Administrative State Down [1] AT6/0 INFO Physical Port Administrative State Down [8]Configuring Alarm Filtering for SNMP Notifications: Example
The following example shows how to configure an alarm filter for SNMP notifications:Router# Router# enable Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Router(config)# snmp-server enable traps alarms 2 Router(config)# Router(config)# exitRouter#Router# show facility-alarm statusSystem Totals Critical: 1 Major: 0 Minor: 0Source Severity Description [Index] ------ -------- ------------------- Fa0/0 CRITICAL Physical Port Link Down [0] Fa0/1 INFO Physical Port Administrative State Down [1] AT6/0 INFO Physical Port Administrative State Down [8]Additional References
The following sections provide references related to the Alarm Filtering Support in the Cisco Entity Alarm MIB feature.
Related Documents
Network management configuration tasks
Cisco IOS Network Management Configuration Guide, Release 12.4
Network management commands
Cisco IOS Network Management Command Reference, Release 12.4T
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature."
—
MIBs
•
•
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
This section documents only commands that are new or modified.
logging host
To log system messages and debug output to a remote host, use the logging host command in global configuration mode. To remove a specified logging host from the configuration, use the no form of this command.
logging host {{ip-address | hostname} [vrf vrf-name] | ipv6 {ipv6-address | hostname}} [discriminator discr-name | [[filtered [stream stream-id] | xml]] [transport {[beep [audit] [channel chnl-number] [sasl profile-name] [tls cipher [cipher-num] trustpoint trustpt-name]]] | tcp [audit] | udp}[port port-num]] [sequence-num-session] [session-id]
no logging host {ip-address | hostname} | ipv6 {ipv6-address | hostname}
Syntax Description
Command Default
System logging messages are not sent to any remote host.
When this command is entered without the xml or filtered keyword, messages are sent in the standard format.Command Modes
Global configuration
Command History
Usage Guidelines
Standard system logging is enabled by default. If logging is disabled on your system (using the no logging on command), you must enter the logging on command to reenable logging before you can use the logging host command.
The logging host command identifies a remote host (usually a device serving as a syslog server) to receive logging messages. By issuing this command more than once, you can build a list of hosts that receive logging messages.
To specify the severity level for logging to all hosts, use the logging trap command.
Use the vrf vrf-name keyword and argument to enable a syslog client (a provider edge [PE] router) to send syslog messages to a syslog server host connected through a VRF interface. To delete the configuration of the syslog server host from the VRF, use the no logging host command with the vrf vrf-name keyword and argument.
When XML-formatted syslog is enabled using the logging host command with the xml keyword, messages are sent to the specified host with the system-defined XML tags. These tags are predefined and cannot be configured by a user. XML formatting is not applied to debug output.
If you are using the ESM feature, you can enable ESM-filtered syslog messages to be sent to one or more hosts using the logging host filtered command. To use the ESM feature, you must first specify the syslog filter modules that should be applied to the messages using the logging filter command. See the description of the logging filter command for more information about the ESM feature.
Note
Using the BEEP transport protocol, you can have reliable and secure delivery for syslog messages and configure multiple sessions over 8 BEEP channels. The sasl profile-name, tls cipher cipher-num, trustpoint trustpt-name keywords and arguments are available only in crypto images.
To configure standard logging to a specific host after configuring XML-formatted or ESM-filtered logging to that host, use the logging host command without the xml or filtered keyword. Issuing the standard logging host command replaces an XML- or ESM- filtered logging host command, and vice versa, if the same host is specified.
You can configure the system to send standard messages to one or more hosts, XML-formatted messages to one or more hosts, and ESM-filtered messages to one or more hosts by repeating this command as many times as desired with the appropriate syntax. (See the "Examples" section.)
When the no logging host command is issued with or without the optional keywords, all logging to the specified host is disabled.
Examples
In the following example, messages at severity levels 0 (emergencies) through 5 (notifications) (logging trap command severity levels) are logged to a host at 192.168.202.169:
Router(config)# logging host 192.168.202.169Router(config)# logging trap 5In the following example, standard system logging messages are sent to the host at 192.168.200.225, XML-formatted system logging messages are sent to the host at 192.168.200.226, ESM-filtered logging messages with the stream 10 value are sent to the host at 192.168.200.227, and ESM-filtered logging messages with the stream 20 value are sent to host at 192.168.202.129:
Router(config)# logging host 192.168.200.225Router(config)# logging host 192.168.200.226 xmlRouter(config)# logging host 192.168.200.227 filtered stream 10Router(config)# logging host 192.168.202.129 filtered stream 20In the following example, messages are logged to a host with an IP address of 172.16.150.63 connected through a VRF named vpn1:
Router(config)# logging host 172.16.150.63 vrf vpn1In the following example, the default UDP on an IPv6 server is set because no port number is specified. The default port number of 514 is used:
Router(config)# logging host ipv6 AAAA:BBBB:CCCC:DDDD::FFFFIn the following example, TCP port 1774 on an IPv6 server is set:
Router(config)# logging host ipv6 BBBB:CCCC:DDDD:FFFF::1234 transport tcp port 1774In the following example, the UDP port default is used on an IPv6 server with a hostname of v6-hostname:
Router(config)# logging host ipv6 v6-hostname transport udp port 514In the following example, a message discriminator named fltr1 is specified as well as the BEEP protocol for port 600 and channel 3.
Router(config)# logging host host2 transport beep channel 3 port 600Related Commands
show facility-alarm
To display the status of a generated alarm, use the show facility-alarm command in global configuration mode.
show facility-alarm {status [severity] | relay}
Syntax Description
Command Default
Command Modes
Global configuration
Command History
Usage Guidelines
When a severity level is configured, statuses of alarms at that level and higher are shown. For example, when you set a severity of major, all major and critical alarms are shown.
Examples
The following example shows output of the show facility-alarm status command:
Router# show facility-alarm statusSystem Totals Critical:1 Major:0 Minor:0Source Severity Description [Index]------ -------- -------------------Fa0/0 CRITICAL Physical Port Link Down [0]Fa1/0 INFO Physical Port Administrative State Down [1]The following example shows output of a show facility-alarm status command with a severity level set at major:Router# show facility-alarm status majorSystem Totals Critical:1 Major:0 Minor:0Source Severity Description [Index]------ -------- -------------------Fa0/0 CRITICAL Physical Port Link Down [0]Table 1 describes the significant fields shown in the output.
Related Commands
clear facility-alarm
Clears alarm conditions and resets the alarm contacts.
facility-alarm
Configures threshold temperatures for minor, major, and critical alarms.
snmp-server enable traps
To enable all Simple Network Management Protocol (SNMP) notification types that are available on your system, use the snmp-server enable traps command in global configuration mode. To disable all available SNMP notifications, use the no form of this command.
snmp-server enable traps [notification-type] [vrrp]
no snmp-server enable traps [notification-type] [vrrp]
Syntax Description
Command Default
No notifications controlled by this command are sent.
Command Modes
Global configuration
Command History
Usage Guidelines
For additional notification types, see the Related Commands table for this command.
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. To specify whether the notifications should be sent as traps or informs, use the snmp-server host [traps | informs] command.
To configure the router to send these SNMP notifications, you must enter at least one snmp-server enable traps command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled. To enable multiple types of notifications, you must issue a separate snmp-server enable traps command for each notification type and notification option.
Most notification types are disabled by default but some cannot be controlled with the snmp-server enable traps command.
The snmp-server enable traps command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send notifications, you must configure at least one snmp-server host command.
Examples
The following example shows how to enable the router to send all traps to the host specified by the name myhost.cisco.com, using the community string defined as public:
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com publicThe following example shows how to configure an alarm severity threshold of 3:
Router# snmp-server enable traps alarms 3The following example shows how to enable the generation of a DSP operational state notification from from the command-line interface (CLI):
Router(config)# snmp-server enable traps dsp oper-stateThe following example shows how to enable the generation of a DSP operational state notification from a network management device:
setany -v2c 1.4.198.75 test cdspEnableOperStateNotification.0 -i 1cdspEnableOperStateNotification.0=true(1)The following example shows how to send no traps to any host. The Border Gateway Protocol (BGP) traps are enabled for all hosts, but the only traps enabled to be sent to a host are ISDN traps (which are not enabled in this example).
Router(config)# snmp-server enable traps bgpRouter(config)# snmp-server host user1 public isdnThe following example shows how to enable the router to send all inform requests to the host at the address myhost.cisco.com, using the community string defined as public:
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicThe following example shows how to send HSRP MIB traps to the host myhost.cisco.com using the community string public:
Router(config)# snmp-server enable traps hsrpRouter(config)# snmp-server host myhost.cisco.com traps version 2c public hsrpThe following example shows that VRRP will be used as the protocol to enable the traps:
Router(config)# snmp-server enable traps vrrpRouter(config)# snmp-server host myhost.cisco.com traps version 2c vrrpThe following example shows how to send IEEE 802.1x MIB traps to the host "myhost.domain.com" using the community string defined as public:
Router(config)# snmp-server enable traps dot1xRouter(config)# snmp-server host myhost.domain.com traps publicRelated Commands
Feature Information for Alarm Filtering Support in the Cisco Entity Alarm MIB
Table 2 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2005, 2007 Cisco Systems, Inc. All rights reserved.
Guest
