|
Table Of Contents
OSPF MIB Support of RFC 1850 and Latest Extensions
Prerequisites for OSPF MIB Support of RFC 1850 and Latest Extensions
Restrictions for OSPF MIB Support of RFC 1850 and Latest Extensions
Information About OSPF MIB Support of RFC 1850 and Latest Extensions
OSPF MIB Changes to Support RFC 1850
How to Enable OSPF MIB Support of RFC 1850 and Latest Extensions
Verifying OSPF MIB Traps on the Router
Configuration Examples for OSPF MIB Support of RFC 1850 and Latest Extensions
Enabling and Verifying OSPF MIB Support Traps: Example
snmp-server enable traps ospf cisco-specific errors
snmp-server enable traps ospf cisco-specific lsa
snmp-server enable traps ospf cisco-specific retransmit
snmp-server enable traps ospf cisco-specific state-change
snmp-server enable traps ospf errors
snmp-server enable traps ospf lsa
snmp-server enable traps ospf rate-limit
snmp-server enable traps ospf retransmit
snmp-server enable traps ospf state-change
Feature Information for OSPF MIB Support of RFC 1850 and Latest Extensions
OSPF MIB Support of RFC 1850 and Latest Extensions
First Published: August 23, 2003Last Updated: December 5, 2006The OSPF MIB Support of RFC 1850 and Latest Extensions feature introduces the capability for Simple Network Management Protocol (SNMP) monitoring on the Open Shortest Path First (OSPF) routing protocol. Users have an improved ability to constantly monitor the changing state of an OSPF network by use of MIB objects to gather information relating to protocol parameters and trap notification objects that can signal the occurrence of significant network events such as transition state changes. The protocol information collected by the OSPF MIB objects and trap objects can be used to derive statistics that will help monitor and improve overall network performance.
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 OSPF MIB Support of RFC 1850 and Latest Extensions" 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 OSPF MIB Support of RFC 1850 and Latest Extensions
• Restrictions for OSPF MIB Support of RFC 1850 and Latest Extensions
• Information About OSPF MIB Support of RFC 1850 and Latest Extensions
• How to Enable OSPF MIB Support of RFC 1850 and Latest Extensions
• Configuration Examples for OSPF MIB Support of RFC 1850 and Latest Extensions
• Feature Information for OSPF MIB Support of RFC 1850 and Latest Extensions
Prerequisites for OSPF MIB Support of RFC 1850 and Latest Extensions
•OSPF must be configured on the router.
•Simple Network Management Protocol (SNMP) must be enabled on the router before notifications (traps) can be configured or before SNMP GET operations can be performed.
Restrictions for OSPF MIB Support of RFC 1850 and Latest Extensions
For routers that are running Cisco IOS Release 12.0(26)S, 12.2(25)S, 12.2(27)SBC, 12.2(31)SB2 and later releases, the OSPF MIB and CISCO OSPF MIB will be supported only for the first OSPF process (except for MIB objects that are related to virtual links and sham links, and in cases where support for multiple topologies is provided). SNMP traps will be generated for OSPF events that are related to any of the OSPF processes. There is no workaround for this situation.
Information About OSPF MIB Support of RFC 1850 and Latest Extensions
The following sections contain information about MIB objects standardized as part of RFC 1850 and defined in OSPF-MIB and OSPF-TRAP-MIB. In addition, extensions to RFC 1850 objects are described as defined in the two Cisco private MIBs, CISCO-OSPF-MIB and CISCO-OSPF-TRAP-MIB.
• OSPF MIB Changes to Support RFC 1850
OSPF MIB Changes to Support RFC 1850
The following sections describe the new MIB objects that provide RFC 1850 support:
• OSPF MIB
OSPF MIB
This section describes the new MIB objects that are provided by RFC 1850 definitions. These OSPF MIB definitions provide additional capacity that is not provided by the standard OSPF MIB that supported the previous RFC 1253. To see a complete set of OSPF MIB objects, see the OSPF-MIB file.
Table 1 shows the new OSPF-MIB objects that are provided by RFC 1850 definitions. The objects are listed in the order in which they appear within the OSPF-MIB file, per the tables that describe them.
For the table, the following objects are provided to support RFC 1850:
OSPF TRAP MIB
This section describes scalar objects and MIB objects that are provided to support FRC 1850.
The following scalar objects are added to OSPF-TRAP-MIB and are listed in the order in which they appear in the OSPF-TRAP-MIB file:
•OspfExtLsdbLimit
•OspfMulticastExtensions
•OspfExitOverflowInterval
•OspfDemandExtensions
The ospfSetTrap control MIB object contains the OSPF trap MIB objects that enable and disable OSPF traps in the IOS CLI. These OSPF trap MIB objects are provided by the RFC 1850 standard OSPF MIB. To learn how to enable and disable the OSPF traps, see the "How to Enable OSPF MIB Support of RFC 1850 and Latest Extensions" section.
Table 2 shows the OSPF trap MIB objects, listed in the order in which they appear within the OSPF-TRAP-MIB file.
CISCO OSPF MIB
This section describes scalar and Cisco-specific OSPF MIB objects that are provided as extensions to support the RFC 1850 OSPF MIB definitions, to provide capability that the standard MIB cannot provide.
The following scalar objects are added to OSPF-OSPF-MIB:
•cospfRFC1583Compatibility
•cospfOpaqueLsaSupport
•cospfOpaqueASLsaCount
•cospfOpaqueASLsaCksumSum
For each of the following table entries, the new Cisco-specific MIB objects that are provided as extensions to support the RFC 1850 OSPF MIB definitions are listed. To see the complete set of objects for the Cisco-specific OSPF MIB, refer to the CISCO-OSPF-MIB file.
Table 3 shows the new CISCO-OSPF-MIB objects that are provided by RFC 1850 definitions. The objects are listed in the order in which they appear within the CISCO-OSPF-MIB file, per the tables that describe them.
CISCO OSPF TRAP MIB
The cospfSetTrap MIB object represents trap events in CISCO-OSPF-TRAP-MIB. This is a bit map, where the first bit represents the first trap. The following MIB objects are TRAP events that have been added to support RFC 1850. To see a complete set of Cisco OSPF Trap MIB objects, see the CISCO-OSPF-TRAP-MIB file.
Table 4 shows the trap events described within the cospfSetTrap MIB object in the CISCO-TRAP-MIB:
For information about how to enable OSPF MIB traps, see the "How to Enable OSPF MIB Support of RFC 1850 and Latest Extensions" section.
Benefits of the OSPF MIB
The OSPF MIBs (OSPF-MIB and OSPF-TRAP-MIB) and Cisco private OSPF MIBs (CISCO-OSPF-MIB and CISCO-OSPF-TRAP-MIB) allow network managers to more effectively monitor the OSPF routing protocol through the addition of new table objects and trap notification objects that previously were not supported by the RFC 1253 OSPF MIB.
New CLI commands have been added to enable SNMP notifications for OSPF MIB support objects, Cisco-specific errors, retransmission and state-change traps. The SNMP notifications are provided for errors and other significant event information for the OSPF network.
How to Enable OSPF MIB Support of RFC 1850 and Latest Extensions
This section describes the configuration tasks for the OSPF MIB Support feature. Each task in the list is identified as either required or optional.
• Enabling OSPF MIB Support (required)
• Enabling Specific OSPF Traps (optional)
• Verifying OSPF MIB Traps on the Router (optional)
Enabling OSPF MIB Support
Perform this task to configure the SNMP server and enable the CISCO-OSPF-MIB and OSPF-MIB.
Prerequisites
Before the OSPF MIB Support of RFC 1850 and Latest Extensions feature can be used, the SNMP server for the router must be configured.
SUMMARY STEPS
1. enable
2. configure terminal
3. snmp-server community string1 ro
4. snmp-server community string2 rw
5. snmp-server host {hostname | ip-address} [vrf vrf-name] [traps | informs] [version {1 | 2c | 3 [auth | noauth | priv]}] community-string [udp-port port] [notification-type]
6. snmp-server enable traps ospf
7. end
DETAILED STEPS
What to Do Next
If you did not want to enable all OSPF traps, follow the steps in the following section to selectively enable one or more type of OSPF trap:
• Enabling Specific OSPF Traps
Enabling Specific OSPF Traps
Rather than entering the snmp-server enable traps ospf command to enable all OSPF traps, you can enter one or more of the commands in this section to enable just one trap or a subset of traps.
SUMMARY STEPS
1. enable
2. configure terminal
3. snmp-server enable traps ospf cisco-specific errors [config-error] [virt-config-error]
4. snmp-server enable traps ospf cisco-specific retransmit [packets] [virt-packets]
5. snmp-server enable traps ospf cisco-specific state-change [nssa-trans-change] [shamlink-state-change]
6. snmp-server enable traps ospf cisco-specific lsa [lsa-maxage] [lsa-originate]
7. snmp-server enable traps ospf errors [authentication-failure] [bad-packet] [config-error] [virt-authentication-failure] [virt-config-error]
8. snmp-server enable traps ospf lsa [lsa-maxage] [lsa-originate]
9. snmp-server enable traps ospf rate-limit seconds trap-number
10. snmp-server enable traps ospf retransmit [packets] [virt-packets]
11. snmp-server enable traps ospf state-change [if-state-change] [neighbor-state-change] [virtif-state-change] [virtneighbor-state-change]
DETAILED STEPS
Verifying OSPF MIB Traps on the Router
This task verifies that you have enabled OSPF MIB support.
SUMMARY STEPS
1. enable
2. show running-config [options]
DETAILED STEPS
Configuration Examples for OSPF MIB Support of RFC 1850 and Latest Extensions
The following example enables all OSPF MIB traps and verifies the configuration:
• Enabling and Verifying OSPF MIB Support Traps: Example
Enabling and Verifying OSPF MIB Support Traps: Example
The following example enables all OSPF traps.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# snmp-server enable traps ospf
Router(config)# end
The show running-config command is entered to verify that the traps are enabled:
Router# show running-config | include traps
snmp-server enable traps ospf
Where to Go Next
For more information about SNMP and SNMP operations, see the " Configuring SNMP Support" chapter of the Cisco IOS Configuration Fundamentals and Network Management Configuration Guide, Release 12.3.
Additional References
The following sections provide references related to the OSPF MIB Support of RFC 1850 and Latest Extensions feature.
Related Documents
Related Topic Document TitleSNMP configuration
Cisco IOS Configuration Fundamentals and Network Management Configuration Guide, Release 12.3
SNMP commands
Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3
OSPF sham-link configuration
Sham-Link MIB Support, Release 12.0(30)S:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s30/ospfslms.htm
Standards
Standard TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIB
RFC
Technical Assistance
Command Reference
This section documents modified commands only.
• snmp-server enable traps ospf
• snmp-server enable traps ospf cisco-specific errors
• snmp-server enable traps ospf cisco-specific lsa
• snmp-server enable traps ospf cisco-specific retransmit
• snmp-server enable traps ospf cisco-specific state-change
• snmp-server enable traps ospf errors
• snmp-server enable traps ospf lsa
• snmp-server enable traps ospf rate-limit
• snmp-server enable traps ospf retransmit
• snmp-server enable traps ospf state-change
snmp-server enable traps ospf
To enable all Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF), use the snmp-server enable traps ospf command in global configuration mode. To disable all SNMP notifications for OSPF, use the no form of this command.
snmp-server enable traps ospf
no snmp-server enable traps ospf
Syntax Description
This command has no arguments or keywords.
Command Default
SNMP notifications for OSPF are disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
If you wish to enable or disable specific OSPF SNMP notifications, enter one or more of the following commands of the following commands:
[no] snmp-server enable traps ospf cisco-specific errors
[no] snmp-server enable traps ospf cisco-specific lsa
[no] snmp-server enable traps ospf cisco-specific retransmit
[no] snmp-server enable traps ospf cisco-specific state-change
[no] snmp-server enable traps ospf errors
[no] snmp-server enable traps ospf lsa
[no] snmp-server enable traps ospf retransmit
[no] snmp-server enable traps ospf state-change
Examples
The following exampleglobally enables SNMP notifications for OSPF:
Router(config)# snmp-server enable traps ospf
Related Commands
snmp-server enable traps ospf cisco-specific errors
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) configuration mismatch errors, use the snmp-server enable traps ospf cisco-specific errors command in global configuration mode. To disable SNMP notifications for OSPF configuration mismatch errors, use the no form of this command.
snmp-server enable traps ospf cisco-specific errors [config-error] [virt-config-error]
no snmp-server enable traps ospf cisco-specific errors [config-error] [virt-config-error]
Syntax Description
Command Default
SNMP notifications for OSPF configuration mismatch errors are disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
To enable the SNMP notifications for OSPF configuration errors for both virtual and nonvirtual interfaces, enter the snmp-server enable traps ospf cisco-specific errors command in global configuration mode without the optional keywords.
Examples
The following example enables the router to send OSPF configuration mismatch errors only for nonvirtual interfaces:
Router(config)# snmp-server enable traps ospf cisco-specific errors config-error
Related Commands
snmp-server enable traps ospf cisco-specific lsa
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) opaque link-state advertisements (LSAs), use the snmp-server enable traps ospf cisco-specific lsa command in global configuration mode. To disable SNMP notifications for OSPF opaque LSAs, use the no form of this command.
snmp-server enable traps ospf cisco-specific lsa [lsa-maxage] [lsa-originate]
no snmp-server enable traps ospf cisco-specific lsa [lsa-maxage] [lsa-originate]
Syntax Description
Command Default
SNMP notifications for OSPF opaque LSAs are disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The snmp-server enable traps ospf cisco-specific lsa command enables the traps that are defined by the CISCO-OSPF-TRAP-MIB for opaque LSAs. An opaque link-state advertisement (LSA) is used in MPLS traffic engineering to distribute attributes such as capacity and topology of links in a network. The scope of this LSA can be confined to the local network (Type 9, Link-Local), OSPF area (Type 20, Area-Local), or Autonomous System (Type 11, AS scope). The information in an opaque LSA can be used by an external application across the OSPF network. To enable the cospfMaxAgeLsa trap, enter the snmp-server enable traps ospf cisco-specific lsa command with the lsa-maxage keyword. To enable the cospfOriginateLsa trap, enter the snmp-server enable traps ospf cisco-specific lsa command with the lsa-originate keyword. When you enter the snmp-server enable traps ospf cisco-specific lsa command without either keyword, both traps will be enabled.
Examples
The following example enables the router to send OSPF opaque LSA notifications to the host at the address myhost.cisco.com using the community string defined as public whenever new opaque LSAs are created:
Router(config)# snmp-server enable traps ospf cisco-specific lsa lsa-originate
Router(config)# snmp-server host myhost.cisco.com informs version 2c public
Related Commands
snmp-server enable traps ospf cisco-specific retransmit
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) retransmission errors, use the snmp-server enable traps ospf cisco-specific retransmit command in global configuration mode. To disable OSPF sham-link error SNMP notifications, use the no form of this command.
snmp-server enable traps ospf cisco-specific retransmit [packets [shamlink | virt-packets] | shamlink [packets | virt-packets] | virt-packets [shamlink]]
no snmp-server enable traps ospf cisco-specific retransmit [packets [shamlink | virt-packets] | shamlink [packets | virt-packets] | virt-packets [shamlink]]
Syntax Description
Command Default
This command is disabled.
Command Modes
Global configuration
Command History
Examples
The following example enables the router to send OSPF sham-link retransmission notifications:
Router(config)# snmp-server enable traps ospf cisco-specific retransmit shamlink
Related Commands
snmp-server enable traps ospf cisco-specific state-change
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) transition state changes, use the snmp-server enable traps ospf cisco-specific state-change command in global configuration mode. To disable OSPF transition state change SNMP notifications, use the no form of this command.
snmp-server enable traps ospf cisco-specific state-change [nssa-trans-change | shamlink [interface | interface-old | neighbor]]
no snmp-server enable traps ospf cisco-specific state-change [nssa-trans-change | shamlink [interface | interface-old | neighbor]]
Syntax Description
Command Default
This command is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
You cannot enter both the interface and interface-old keywords because you cannot enable both the new and replaced sham-link interface transition state change traps. You can configure only one of the two traps, but not both.
Examples
The following example enables the router to send OSPF sham-link transition state change notifications to the host at the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps ospf cisco-specific state-change shamlink
Router(config)# snmp-server host myhost.cisco.com informs version 2c public
Related Commands
snmp-server enable traps ospf errors
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) errors, use the snmp-server enable traps ospf errors command in global configuration mode. To disable SNMP notifications for OSPF errors, use the no form of this command.
snmp-server enable traps ospf errors [authentication-failure] [bad-packet] [config-error] [virt-authentication-failure] [virt-bad-packet] [virt-config-error]
no snmp-server enable traps ospf errors [authentication-failure] [bad-packet] [config-error] [virt-authentication-failure] [virt-bad-packet] [virt-config-error]
Syntax Description
Command Default
SNMP notifications for OSPF errors are disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
When you enter the snmp-server enable traps ospf errors command without any optional keywords, all OSPF error traps will be enabled. To enable only one or more OSPF error traps, enter one or more of the optional keywords.
Examples
The following example enables the router to send all OSPF error notifications:
Router(config)# snmp-server enable traps ospf errors
Related Commands
snmp-server enable traps ospf lsa
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) link-state advertisements (LSAs), use the snmp-server enable traps ospf lsa command in global configuration mode. To disable SNMP notifications for OSPF LSAs, use the no form of this command.
snmp-server enable traps ospf lsa [lsa-maxage] [lsa-originate]
no snmp-server enable traps ospf lsa [lsa-maxage] [lsa-originate]
Syntax Description
Command Default
SNMP notifications for OSPF LSAs are disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The snmp-server enable traps ospf lsa command enables the traps for standard LSAs that are defined by the OSPF-MIB. To enable the ospfMaxAgeLsa trap, enter the snmp-server enable traps ospf lsa command with the lsa-maxage keyword. To enable the ospfOriginateLsa trap, enter the snmp-server enable traps ospf lsa command with the lsa-originate keyword. When the ospfOriginateLsa trap is enabled, it will not be invoked for simple LSA refreshes that take place every 30 minutes or when an LSA has reached its maximum age and is being flushed. When you enter the snmp-server enable traps ospf lsa command without either keyword, both traps will be enabled.
To enable the traps that are defined by the CISCO-OSPF-TRAP-MIB for opaque LSAs, enter the snmp-server enable traps ospf cisco-specific lsa command in global configuration mode.
Examples
The following example enables the router to send SNMP notifications when new LSAs are originated by the router as a result of a topology change:
Router(config)# snmp-server enable traps ospf lsa lsa-originate
Related Commands
snmp-server enable traps ospf rate-limit
To limit the number of Open Shortest Path First (OSPF) traps that are sent during a specified number of seconds, use the snmp-server enable traps ospf rate-limit command in global configuration mode. To disable the limit placed on the number of OSPF traps sent during a specified number of seconds, use the no form of this command.
snmp-server enable traps ospf rate-limit seconds trap-number
no snmp-server enable traps ospf rate-limit seconds trap-number
Syntax Description
Command Default
No limit is placed on the number of OSPF traps sent.
Command Modes
Global configuration
Command History
Usage Guidelines
There is a possibility that a router sends trap bursts, which can drain network resources in a small interval of time. It is recommended that you enter the snmp-server enable traps ospf rate-limit command to configure a sliding window mechanism that will limit the number of traps that are sent within a specified number of seconds.
Examples
The following example sets the trap rate limit window so that during a 40-second window of time, no more that 50 traps are sent.
Router(config)# snmp-server enable traps ospf rate-limit 40 50
Related Commands
snmp-server enable traps ospf retransmit
To enable Simple Network Management Protocol (SNMP) notifications when packets are re-sent in an Open Shortest Path First (OSPF) network, use the snmp-server enable traps ospf retransmit command in global configuration mode. To disable SNMP notifications, use the no form of this command.
snmp-server enable traps ospf retransmit [packets] [virt-packets]
no snmp-server enable traps ospf retransmit [packets] [virt-packets]
Syntax Description
Command Default
SNMP notifications are disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
To enable the ospfTXRetransmit trap so that SNMP notifications are sent only when packets from nonvirtual interfaces are re-sent, enter the snmp-server enable traps ospf retransmit command with the packets keyword. To enable the ospfTxRetransmit trap so that SNMP notifications are sent only when packets from virtual interfaces are re-sent, enter the snmp-server enable traps ospf retransmit command with the virt-packets keyword. When you enter the snmp-server enable traps ospf retransmit command without either keyword, both traps will be enabled.
Examples
The following example enables the router to send SNMP notifications when packets are re-sent by virtual interfaces:
Router(config)# snmp-server enable traps ospf retransmit virt-packets
Related Commands
snmp-server enable traps ospf state-change
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) transition state changes, use the snmp-server enable traps ospf state-change command in global configuration mode. To disable SNMP notifications for OSPF transition state changes, use the no form of this command.
snmp-server enable traps ospf state-change [if-state-change] [neighbor-state-change] [virtif-state-change] [virtneighbor-state-change]
no snmp-server enable traps ospf state-change [if-state-change] [neighbor-state-change] [virtif-state-change] [virtneighbor-state-change]
Syntax Description
Command Default
SNMP notifications for OSPF transition state changes are disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
To enable all traps for transition state changes, enter the snmp-server enable traps ospf state-change command without of the optional keywords.
Examples
The following example enables the router to send SNMP notifications for transition state changes for virtual interfaces and virtual neighbors:
Router(config)# snmp-server enable traps ospf state-change virtif-state-change virtneighbor-state-change
Related Commands
Feature Information for OSPF MIB Support of RFC 1850 and Latest Extensions
Table 5 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 Table 5 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
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.
© 2003-2006 Cisco Systems, Inc. All rights reserved.
Posted: Tue Dec 5 00:30:35 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.