![]() |
Table Of Contents
Prerequisites for OSPF Sham-Link MIB Support
Restrictions for OSPF Sham-Link MIB Support
Information About OSPF Sham-Link MIB Support
OSPF Sham-Links in PE-PE Router Connections
Cisco OSPF MIB and Cisco OSPF Trap MIB Enhancements
OSPF Sham-Link Configuration Support
OSPF Sham-Link Neighbor Support
OSPF Sham-Link Interface Transition State Change Support
OSPF Sham-Link Neighbor Transition State Change Support
How to Configure OSPF Sham-Link MIB Support
Configuring the Router to Send SNMP Notifications
OSPF Configuration Error Notifications
Enabling OSPF Sham-Link Error Traps
Enabling OSPF Sham-Link Retransmissions Traps
Enabling OSPF Sham-Link State Change Traps
Verifying OSPF Sham-Link MIB Traps on the Router
Configuration Examples for OSPF Sham-Link MIB Support
Enabling and Verifying OSPF Sham-Link Error Traps: Example
Enabling and Verifying OSPF State Change Traps: Example
Enabling and Verifying OSPF Sham-Link Retransmissions Traps: Example
snmp-server enable traps ospf cisco-specific errors config-error
snmp-server enable traps ospf cisco-specific errors shamlink
snmp-server enable traps ospf cisco-specific retransmit
snmp-server enable traps ospf cisco-specific state-change
Feature Information for OSPF Sham-Link MIB Support
OSPF Sham-Link MIB Support
First Published: October 28, 2004Last Updated: July 13, 2007This feature introduces MIB support for the OSPF Sham-Link feature through the addition of new tables and trap MIB objects to the Cisco OSPF MIB (CISCO-OSPF-MIB) and the Cisco OSPF Trap MIB (CISCO-OSPF-TRAP-MIB). New commands have been added to enable Simple Network Management Protocol (SNMP) notifications for the Open Shortest Path First (OSPF) sham-link trap objects. Notifications are provided for errors, state changes, and retransmissions across a sham-link interface.
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 Sham-Link MIB Support" 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 Sham-Link MIB Support
•
Restrictions for OSPF Sham-Link MIB Support
•
Information About OSPF Sham-Link MIB Support
•
How to Configure OSPF Sham-Link MIB Support
•
Configuration Examples for OSPF Sham-Link MIB Support
•
Feature Information for OSPF Sham-Link MIB Support
Prerequisites for OSPF Sham-Link MIB Support
•
It is presumed that you already have configured an Open Shortest Path First (OSPF) sham-link.
•
SNMP must be enabled on the router before notifications (traps) can be configured or before SNMP GET operations can be performed.
Restrictions for OSPF Sham-Link MIB Support
All enhancements that are introduced by this feature are provided only by the Cisco private MIBs CISCO-OSPF-MIB and CISCO-OSPF-TRAP-MIB.
Information About OSPF Sham-Link MIB Support
This section contains the following information:
•
OSPF Sham-Links in PE-PE Router Connections
•
Cisco OSPF MIB and Cisco OSPF Trap MIB Enhancements
OSPF Sham-Links in PE-PE Router Connections
In a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) configuration, a virtual connection called a sham-link can be configured to interconnect between two VPN sites that want to be in the same OSPF area. The sham-link is configured on top of the MPLS VPN tunnel that connects two provider edge (PE) routers. The OSPF packets are propagated over the sham-link. For more information on configuring sham-links, refer the OSPF Sham-Link Support for MPLS VPN feature at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ospfshmk.htm
Cisco OSPF MIB and Cisco OSPF Trap MIB Enhancements
The OSPF Sham-Link MIB Support feature introduces MIB support for OSPF sham-links through the addition of new tables and trap MIB objects to the Cisco OSPF MIB (CISCO-OSPF-MIB) and the Cisco OSPF Trap MIB (CISCO-OSPF-TRAP-MIB) for Cisco IOS Releases 12.0(30)S, 12.3(14)T, 12.2(33)SRA, 12.2(31)SB2, and 12.2(33)SXH. New CLI has been added to enable SNMP notifications for the OSPF sham-link trap objects. Notifications are provided for errors, state changes, and retransmissions across a sham-link interface. The following sections describe the enhancements:
•
OSPF Sham-Link Configuration Support
•
OSPF Sham-Link Neighbor Support
•
OSPF Sham-Link Interface Transition State Change Support
•
OSPF Sham-Link Neighbor Transition State Change Support
OSPF Sham-Link Configuration Support
The cospfShamLinksTable table object stores information about the sham-links that have been configured for the OSPF area. Beginning with Cisco IOS Releases 12.0(30)S, 12.3(14)T, 12.2(33)SRA, 12.2(31)SB2, and 12.2(33)SXH, the cospfShamLinksTable replaces the cospfShamLinkTable. The cospfShamLinksTable allows access to the following MIB objects:
•
cospfShamLinksAreaId
•
cospfShamLinksLocalIpAddrType
•
cospfShamLinksLocalIpAddr
•
cospfShamLinksRemoteIpAddrType
•
cospfShamLinksRemoteIpAddr
•
cospfShamLinksRetransInterval
•
cospfShamLinksHelloInterval
•
cospfShamLinksRtrDeadInterval
•
cospfShamLinksState
•
cospfShamLinksEvents
•
cospfShamLinksMetric
OSPF Sham-Link Neighbor Support
The cospfShamLinkNbrTable table object describes all OSPF sham-link neighbor entries. The cospfShamLinkNbrTable allows access to the following MIB objects:
•
cospfShamLinkNbrArea
•
cospfShamLinkNbrIpAddrType
•
cospfShamLinkNbrIpAddr
•
cospfShamLinkNbrRtrId
•
cospfShamLinkNbrOptions
•
cospfShamLinkNbrState
•
cospfShamLinkNbrEvents
•
cospfShamLinkNbrLsRetransQLen
•
cospfShamLinkNbrHelloSuppressed
OSPF Sham-Link Interface Transition State Change Support
The cospfShamLinksStateChange trap object is used to notify the network manager of a transition state change for the OSPF sham-link interface. The cospfShamLinksStateChange trap object replaces the original cospfShamLinkStateChange trap object for Cisco IOS Releases 12.0(30)S, 12.3(14)T, 12.2(33)SRA, and 12.2(31)SB2. The cospfShamLinksStateChange trap objects contains the following MIB objects:
•
ospfRouterId
•
cospfShamLinksAreaId
•
cospfShamLinksLocalIpAddrType
•
cospfShamLinksLocalIpAddr
•
cospfShamLinksRemoteIpAddrType
•
cospfShamLinksRemoteIpAddr
•
cospfShamLinksState
OSPF Sham-Link Neighbor Transition State Change Support
The cospfShamLinkNbrStateChange trap object is used to notify the network manager of a transition state change for the OSPF sham-link neighbors. The cospfShamLinkNbrStateChange trap object contains the following MIB objects:
•
ospfRouterId
•
cospfShamLinkNbrArea
•
cospfShamLinksLocalIpAddrType
•
cospfShamLinksLocalIpAddr
•
cospfShamLinkNbrIpAddrType
•
cospfShamLinkNbrIpAddr
•
cospfShamLinkNbrRtrId
•
cospfShamLinkNbrState
Sham-Link Errors
Trap notifications are provided for OSPF sham-link configuration, authentication, and bad packet errors. These errors include the following trap objects:
•
cospfShamLinkConfigError
•
cospfShamLinkAuthFailure
•
cospfShamLinkRxBadPacket
Note
The cospfShamLinkAuthFailure trap will not be generated because Cisco IOS Releases 12.0(30)S, 12.3(14)T, 12.2(33)SRA, and 12.2(31)SB2 do not yet support authentication over sham-links. The cospfShamLinkRxBadPacket trap will not be generated because it also is not supported by Cisco IOS Releases 12.0(30)S, 12.3(14)T, 12.2(33)SRA, and 12.2(31)SB2. However, the information can be retrieved from the existing OSPF bad packet traps.
How to Configure OSPF Sham-Link MIB Support
This section describes the configuration tasks for the OSPF Sham-Link MIB Support feature. Each task in the list is identified as either required or optional.
•
Configuring the Router to Send SNMP Notifications (required)
•
Enabling OSPF Sham-Link Error Traps (required)
•
Enabling OSPF Sham-Link Retransmissions Traps (required)
•
Enabling OSPF Sham-Link State Change Traps (required)
•
Verifying OSPF Sham-Link MIB Traps on the Router (optional)
Configuring the Router to Send SNMP Notifications
Perform this task to enable the router to send SNMP notifications (traps or informs) defined in the OSPF MIBs. SNMP notifications can be configured on the router and GET operations can be performed from an external management station only after MIB support is enabled.
OSPF Configuration Error Notifications
To enable the sending of OSPF configuration errors notifications, enable the following traps:
•
cospfShamLinkConfigError
•
cospfShamLinkAuthFailure
•
cospfShamLinkRxBadPacket
SUMMARY STEPS
1.
enable
2.
show running-config
3.
configure terminal
4.
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]
5.
snmp-server enable traps ospf
6.
end
DETAILED STEPS
Enabling OSPF Sham-Link Error Traps
Notifications are sent when OSPF sham-link configuration errors are detected. To enable the sending of sham-link configuration error notifications, enable the following cospfShamLinkConfigError trap.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
snmp-server enable traps ospf cisco-specific errors config-error
4.
snmp-server enable traps ospf cisco-specific errors shamlink [authentication [bad-packet [config] | [config [bad-packet]]]
5.
end
DETAILED STEPS
Enabling OSPF Sham-Link Retransmissions Traps
Notifications are sent when OSPF packets retransmissions across a sham-link are detected. To enable the sending of sham-link packet retransmission notifications, enable the following cospfShamLinkTxRetransmit trap.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
snmp-server enable traps ospf cisco-specific retransmit [packets [shamlink | virt-packets] | shamlink [packets | virt-packets] | virt-packets [shamlink]]
4.
end
DETAILED STEPS
Enabling OSPF Sham-Link State Change Traps
Notifications are sent when sham-link interface and neighbor state changes are detected. To enable the sending of sham-link state changes notifications, you can enable the following cospfShamLinksStateChange trap, which replaces the original cospfShamLinkStateChange trap, as well as the cospfShamLinkNbrStateChange trap, which is new for Cisco IOS Releases 12.0(30)S, 12.3(14)T, 12.2(33)SRA, and 12.2(31)SB2:
•
cospfShamLinksStateChange
•
cospfShamLinkNbrStateChange
Note
The replaced cospfShamLinkChange trap can still be enabled, but not when you want to enable the new cospfShamLinksStateChange trap.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
snmp-server enable traps ospf cisco-specific state-change [nssa-trans-change | shamlink [interface | interface-old | neighbor]]
4.
end
DETAILED STEPS
Verifying OSPF Sham-Link MIB Traps on the Router
This task verifies that you have enabled OSPF sham-link MIB support.
SUMMARY STEPS
1.
enable
2.
show running-config | include traps
DETAILED STEPS
Configuration Examples for OSPF Sham-Link MIB Support
This section provides the following configuration examples:
•
Enabling and Verifying OSPF Sham-Link Error Traps: Example
•
Enabling and Verifying OSPF State Change Traps: Example
•
Enabling and Verifying OSPF Sham-Link Retransmissions Traps: Example
Enabling and Verifying OSPF Sham-Link Error Traps: Example
The following example enables all Cisco-specific OSPF sham-link error traps. Note that the first attempt to enter the snmp-server enable traps ospf cisco-specific errors shamlink command results in an error message that the snmp-server enable traps ospf cisco-specific errors config-error command must be entered first:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# snmp-server enable traps ospf cisco-specific errors shamlink% Sham-link config error trap not enabled.% Configure "cisco-specific errors config-error" first.% This requirement allows both traps to be sent.Router(config)# snmp-server enable traps ospf cisco-specific errors config-errorRouter(config)# snmp-server enable traps ospf cisco-specific errors shamlinkRouter(config)# end
The show running-config command is entered to verify that the traps are enabled:
Router# show running-config | include trapssnmp-server enable traps ospf cisco-specific errors config-errorsnmp-server enable traps ospf cisco-specific errors shamlinkAt the time of disabling the traps, if the no snmp-server enable traps ospf cisco-specific errors config-error command is entered before the snmp-server enable traps ospf cisco-specific errors shamlink command, a message will be displayed to indicate that the sham-link configuration errors traps have also been disabled:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# no snmp-server enable traps ospf cisco-specific errors config-error! This command also disables the previously-enabled shamlink configuration error traps.Router(config)# end
Enabling and Verifying OSPF State Change Traps: Example
The following example enables all Cisco-specific OSPF state change traps including the cospfShamLinksStateChange and cospfShamLinkNbrStateChange traps that are new for Cisco IOS Releases 12.0(30)S, 12.3(14)T, 12.2(33)SRA, and 12.2(31)SB2:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# snmp-server enable traps ospf cisco-specific state-change shamlinkThe show running-config command is entered to verify that the traps are enabled:
Router# show running-config | include trapssnmp-server enable traps ospf cisco-specific state-change shamlink interfacesnmp-server enable traps ospf cisco-specific state-change shamlink neighborNote that the snmp-server enable traps ospf cisco-specific state-change shamlink command enables the sham-link interface state change for the cospfShamLinksStateChange trap that is new for Cisco IOS Releases 12.0(30)S, 12.3(14)T, 12.2(33)SRA, and 12.2(31)SB2.
To enable the original cospfShamLinkStateChange trap, you must first disable the cospfShamLinksStateChange trap. An attempt to enter the snmp-server enable traps ospf cisco-specific state-change shamlink interface-old command results in the following error message:
Router(config)# snmp-server enable traps ospf cisco-specific state-change shamlink interface-old% Cannot enable both sham-link state-change interface traps.% Deprecated sham link interface trap not enabled.Router(config)# no snmp-server enable traps ospf cisco-specific state-change shamlink interfaceRouter(config)# snmp-server enable traps ospf cisco-specific state-change shamlink interface-oldEnabling and Verifying OSPF Sham-Link Retransmissions Traps: Example
The following example enables all OSPF sham-link retransmissions traps:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# snmp-server enable traps ospf cisco-specific retransmit shamlinkRouter(config)# endThe show running-config command is entered to verify that the traps are enabled:
Router# show running-config | include trapssnmp-server enable traps ospf cisco-specific retransmit shamlinkWhere to Go Next
For more information about SNMP and SNMP operations, see the "Configuring SNMP Support" part of the Cisco IOS Network Management Configuration Guide, Release 12.4T.
Additional References
The following sections provide references related to the OSPF Sham-Link MIB Support feature.
Related Documents
Related Topic Document TitleConfiguring OSPF sham-links
SNMP configuration
Cisco IOS Network Management Configuration Guide, Release 12.4T
SNMP commands
Cisco IOS Network Management Command Reference,
Release 12.4TCisco IOS Network Management Command Reference,
Release 12.2SBCisco IOS Network Management Command Reference,
Release 12.2SR
Standards
MIBs
MIB MIBs Link•
CISCO-OSPF-MIB
•
CISCO-OSPF-TRAP-MIB
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.
•
snmp-server enable traps ospf cisco-specific errors config-error
•
snmp-server enable traps ospf cisco-specific errors shamlink
•
snmp-server enable traps ospf cisco-specific retransmit
•
snmp-server enable traps ospf cisco-specific state-change
snmp-server enable traps ospf cisco-specific errors config-error
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) nonvirtual interface mismatch errors, use the snmp-server enable traps ospf cisco-specific errors config-error command in global configuration mode. To disable OSPF nonvirtual interface mismatch error SNMP notifications, use the no form of this command.
snmp-server enable traps ospf cisco-specific errors config-error
no snmp-server enable traps ospf cisco-specific errors config-error
Syntax Description
This command has no keywords or arguments.
Command Default
This command is disabled by default; therefore, SNMP notifications for OSPF nonvirtual interface mismatch errors are not created.
Command Modes
Global configuration
Command History
Usage Guidelines
To enable the cospfShamLinkConfigError trap, you must first enter the snmp-server enable traps ospf cisco-specific errors config-error command in global configuration mode. The snmp-server enable traps ospf cisco-specific errors config-error command enables the cospfConfigError trap, so that both traps can be generated at the same place and maintain consistency with a similar case for configuration errors across virtual links.
If you try to enable the cospfShamLinkConfigError trap before configuring the cospfospfConfigError trap you will receive an error message stating you must first configure the cospfConfigError trap.
Examples
The following example enables the router to send nonvirtual interface mismatch error 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 errors config-errorRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicRelated Commands
snmp-server enable traps ospf cisco-specific errors shamlink
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) sham-link errors, use the snmp-server enable traps ospf cisco-specific errors shamlink 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 errors shamlink [authentication [bad-packet] [[config] | config [bad-packet]]]]
no snmp-server enable traps ospf cisco-specific errors shamlink [authentication [bad-packet] [[config] | config [bad-packet]]]]
Syntax Description
Command Default
This command is disabled by default; therefore, SNMP notifications for OSPF sham-link errors are not created.
Command Modes
Global configuration
Command History
Usage Guidelines
To enable the cospfShamLinkConfigError trap, you must first enter the snmp-server enable traps ospf cisco-specific errors config-error command in global configuration mode. The snmp-server enable traps ospf cisco-specific errors config-error command enables the cospfConfigError trap, so that both traps can be generated at the same place and maintain consistency with a similar case for configuration errors across virtual links.
If you try to enable the cospfShamLinkConfigError trap before configuring the cospfospfConfigError trap you will receive an error message stating you must first configure the cospfConfigError trap.
Examples
The following example enables the router to send OSPF sham-link error 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 errors config-errorRouter(config)# snmp-server enable traps ospf cisco-specific errors shamlinkRouter(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 by default; therefore, SNMP notifications for OSPF retransmission errors are not created.
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 shamlinkRelated 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 by default; therefore, SNMP notifications for OSPF transition state changes are not created.
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 shamlinkRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicRelated Commands
Feature Information for OSPF Sham-Link MIB Support
Table 1 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 1 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.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)
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.
© 2004-2007 Cisco Systems, Inc. All rights reserved.