SNMP Support for MTR
Download this chapter
SNMP Support for MTRSNMP Support for MTR
 Feedback

Contents

SNMP Support for MTR

Last Updated: July 23, 2010

The SNMP Support for MTR feature uses context-based the Simple Network Management Protocol (SNMP) to extend support for existing MIBs from representing the management information for just the base topology to representing the same information for multiple topologies. This module describes how to configure SNMP support for Multitopology Routing (MTR).

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Prerequisites for SNMP Support for MTR

Enable Simple Network Management Protocol (SNMP).

Information About SNMP Support for MTR

Network Management Support for MTR

Context-based Simple Network Management Protocol (SNMP) support has been integrated into Cisco IOS software. SNMP support for MTR leverages context-based SNMP to extend support for existing MIBs from representing the management information for just the base topology to representing the same information for multiple topologies.

You can configure the SNMP agent software component on the router to pass a context string to existing MIB access functions. Network management applications can provide these context strings in SNMP transactions to direct those transactions to a specific virtual private network (VPN) routing and forwarding (VRF) instance, a specific topology, and/or routing protocol instance. The SNMP infrastructure on the receiving router verifies that a context string is defined for the router, and that the accompanying internal identifier is defined for that context string, before passing the context string and the internal identifier to the MIB access function.

For detailed steps, see the Configuring SNMP Support for MTR section.

Standard network management utilities, such as ping and traceroute, have been enhanced to support MTR. You can configure a standard or extended ping using the topology name in place of a hostname or IP address. Traceroute has been similarly enhanced. For detailed steps, see the Testing Network Connectivity for MTR section.

How to Configure SNMP Support for MTR

Associating an SNMP Context with a VRF for MTR

Before You Begin
  • Enable SNMP.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    ip vrf vrf-name

4.    snmp context context-name

5.    end

6.    show snmp context mapping


DETAILED STEPS
 Command or ActionPurpose
Step 1
enable


Example:

Router> enable

 

Enables privileged EXEC mode.

  • Enter your password if prompted.
 
Step 2
configure terminal


Example:

Router# configure terminal

 

Enters global configuration mode.

 
Step 3
ip vrf vrf-name


Example:

Router(config)# ip vrf vrfA

 

Defines a VRF instance and enters VRF configuration mode.

 
Step 4
snmp context context-name


Example:

Router(config-vrf)# snmp context context-vrfA

 

Creates an SNMP context for MTR for a specific VRF.

 
Step 5
end


Example:

Router(config-af-topology)# end

 

Exits VRF configuration mode and returns to privileged EXEC mode.

 
Step 6
show snmp context mapping


Example:

Router# show snmp context mapping

 

(Optional) Displays information about SNMP contexts for MTR.

 

Associating an SNMP Context with a Data Topology for MTR

Before You Begin
  • Enable SNMP.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    global-address-family ipv4 [multicast | unicast]

4.    topology {base | topology-name}

5.    snmp context context-name

6.    end

7.    show snmp context mapping


DETAILED STEPS
 Command or ActionPurpose
Step 1
enable


Example:

Router> enable

 

Enables privileged EXEC mode.

  • Enter your password if prompted.
 
Step 2
configure terminal


Example:

Router# configure terminal

 

Enters global configuration mode.

 
Step 3
global-address-family ipv4 [multicast | unicast]


Example:

Router(config)# global-address-family ipv4

 

Enters global address family base topology configuration mode to configure the global topology.

  • The address family for the class-specific topology is specified in this step. The subaddress family can be optionally specified. Unicast is the default if no subaddress family is entered.
 
Step 4
topology {base | topology-name}


Example:

Router(config-af)# topology VOICE

 

Configures the global topology instance and enters routing topology configuration mode.

 
Step 5
snmp context context-name


Example:

Router(config-af-topology)# snmp context comp-topol

 

Creates an SNMP context for MTR for a specific topology.

 
Step 6
end


Example:

Router(config-af-topology)# end

 

Exits routing topology configuration mode and returns to privileged EXEC mode.

 
Step 7
show snmp context mapping


Example:

Router# show snmp context mapping

 

(Optional) Displays information about SNMP contexts for MTR.

 

Associating an SNMP Context with a Routing Protocol for MTR

Before You Begin
  • Enable SNMP.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    router ospf process-id [vrf vrf-name]

4.    snmp context context-name

5.    address-family ipv4 [multicast | unicast]

6.    topology {base | topology-name tid number}

7.    snmp context context-name

8.    end

9.    show snmp context mapping


DETAILED STEPS
 Command or ActionPurpose
Step 1
enable


Example:

Router> enable

 

Enables privileged EXEC mode.

  • Enter your password if prompted.
 
Step 2
configure terminal


Example:

Router# configure terminal

 

Enters global configuration mode.

 
Step 3
router ospf process-id [vrf vrf-name]


Example:

Router(config)# router ospf 1

 

Enables an OSPF routing process and enters router configuration mode.

  • You can configure support for multiple routing protocols.
 
Step 4
snmp context context-name


Example:

Router(config-router)# snmp context comp-prot

 

Creates an SNMP context for MTR for a specific topology under a routing protocol.

 
Step 5
address-family ipv4 [multicast | unicast]


Example:

Router(config-router)# address-family ipv4

 

Enters global address family configuration mode to configure an OSPF address family session.

 
Step 6
topology {base | topology-name tid number}


Example:

Router(config-router-af)# topology VOICE tid 10

 

Configures the global topology instance and enters router address family topology configuration mode.

 
Step 7
snmp context context-name


Example:

Router(config-router-af-topology)# snmp context comp-protocol

 

Creates an SNMP context for MTR for a specific topology under a routing protocol.

 
Step 8
end


Example:

Router(config-router-af-topology)# end

 

Exits router address family topology configuration mode and returns to privileged EXEC mode.

 
Step 9
show snmp context mapping


Example:

Router# show snmp context mapping

 

(Optional) Displays information about SNMP contexts for MTR.

 

Configuration Examples for SNMP Support for MTR

Examples SNMP Support for MTR

In the following example, the context string context-vrfA is configured to be associated with vrfA and will be passed on to the MIB access function during SNMP transactions: 

snmp-server community public
ip vrf vrfA
 snmp context context-vrfA
 exit

In the following example, the context string context-voice is configured to be associated with the data topology named voice and will be passed on to the MIB access function during SNMP transactions: 

global-address-family ipv4
 topology voice
  snmp context context-voice
  exit

In the following example, the context strings context-ospf and context-voice are configured to be associated with the OSPF process and topology named voice and will be passed on to the MIB access function during SNMP transactions: 

router ospf 3
 snmp context context-ospf
 address-family ipv4
 topology voice tid 10
  snmp context ospf-voice
  end

The following example shows how the context strings are mapped to the specified VRF, address family, topology, or to the protocol instance: 

Router# show snmp context mapping
Context: ospf-voice
  VRF Name: 
  Address Family Name: ipv4
  Topology Name: voice
  Protocol Instance: OSPF-3 Router
Context: context-ospf
  VRF Name: 
  Address Family Name: 
  Topology Name: 
  Protocol Instance: OSPF-3 Router
Context: context-vrfA
  VRF Name: vrfA
  Address Family Name: 
  Topology Name: 
  Protocol Instance: 
Context: context-voice
  VRF Name: 
  Address Family Name: ipv4
  Topology Name: voice
  Protocol Instance:

Additional References

Related Documents

Related Topic

Document Title

Cisco IOS commands

Cisco IOS Master Command List, All Releases

Multitopology Routing (MTR) commands

Cisco IOS Multitopology Routing Command Reference

Technical Assistance

Description

Link

The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html

Feature Information for SNMP Support for MTR

The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Table 1Feature Information for SNMP Support for MTR
Feature Name Releases Feature Information

SNMP Support for MTR

12.2(33)SB

12.2(33)SRB

15.0(1)S

Context-based SNMP functionality is integrated into Cisco software and can be used to support Multitopology Routing (MTR). SNMP support for MTR uses context-based Simple Network Management Protocol (SNMP) to extend support for existing MIBs from representing the management information for just the base topology to representing the same information for multiple topologies.

The following commands were introduced or modified: show snmp context mapping, snmp context.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2007-2012 Cisco Systems, Inc. All rights reserved.