|
Contents
- Easy Virtual Network Management and Troubleshooting
- Finding Feature Information
- Prerequisites for EVN Management and Troubleshooting
- Information About EVN Management and Troubleshooting
- Routing Context for EXEC Mode Reduces Repetitive VRF Specification
- Output of traceroute Command Indicates VRF Name and VRF Tag
- Debug Output Filtering Per VRF
- CISCO-VRF-MIB
- How to Manage and Troubleshoot EVN
- Setting the Routing Context for EXEC Mode to a Specific VRF
- Enabling Debug Output for VRFs
- Setting SNMP v2c Context for Virtual Networks
- Setting SNMP v3 Context for Virtual Networks
- Additional References
- Feature Information for EVN Management and Troubleshooting
Easy Virtual Network Management and Troubleshooting
This module describes how to manage and troubleshoot Easy Virtual Network (EVN).
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 EVN Management and Troubleshooting
- Read the Overview of Easy Virtual Network section and the Configuring Easy Virtual Network section, and implement EVN.
Information About EVN Management and Troubleshooting
- Routing Context for EXEC Mode Reduces Repetitive VRF Specification
- Output of traceroute Command Indicates VRF Name and VRF Tag
- Debug Output Filtering Per VRF
- CISCO-VRF-MIB
Routing Context for EXEC Mode Reduces Repetitive VRF Specification
There may be occasions when you want to issue several EXEC commands to apply to a single virtual network. In order to reduce the repetitive entering of virtual routing and forwarding (VRF) names for multiple EXEC commands, the routing-context vrf command allows you to set the VRF context of such EXEC commands once, and then proceed with EXEC commands.
The table below contrasts four EXEC commands in Cisco IOS XE software without routing context and in routing context. Note that in the left column, each EXEC command must specify the VRF. In the right column, the VRF context is specified once and the prompt changes to reflect that VRF; there is no need to specify the VRF in each command.
Table 1 | EXEC Commands with Routing Context |
Cisco IOS XE CLI without Routing Context |
Routing Context |
---|---|
-- |
Router# routing-context vrf red
Router%red#
|
Router# show ip route vrf red
[Routing table output for VRF red] |
Router%red# show ip route
[Routing table output for VRF red] |
Router# ping vrf red 10.1.1.1
[Ping result using VRF red] |
Router%red# ping 10.1.1.1
[Ping result using VRF red] |
Router# telnet 10.1.1.1 /vrf red
[Telnet to 10.1.1.1 in VRF red] |
Router%red# telnet 10.1.1.1
[Telnet to 10.1.1.1 in VRF red] |
Router# traceroute vrf red 10.1.1.1
[Traceroute output in VRF red] |
Router%red# traceroute 10.1.1.1
[Traceroute output in VRF red] |
Output of traceroute Command Indicates VRF Name and VRF Tag
Output of the traceroute command is enhanced to make troubleshooting easier by displaying the incoming VRF name/tag and the outgoing VRF name/tag, as shown in the following example:
Router# traceroute vrf red 10.0.10.12
Type escape sequence to abort.
Tracing the route to 10.0.10.12
VRF info: (vrf in name/id, vrf out name/id)
1 10.1.13.15 (red/13,red/13) 0 msec
10.1.16.16 (red/13,red/13) 0 msec
10.1.13.15 (red/13,red/13) 1 msec
2 10.1.8.13 (red/13,red/13) 0 msec
10.1.7.13 (red/13,red/13) 0 msec
10.1.8.13 (red/13,red/13) 0 msec
3 10.1.2.11 (red/13,blue/10) 1 msec 0 msec 0 msec
4 * * *
Debug Output Filtering Per VRF
Using EVN, you can filter debug output per VRF by using the debug condition vrfcommand. The following is sample output from the debug condition vrfcommand:
Router# debug condition vrf red
Condition 1 set
CEF filter table debugging is on
CEF filter table debugging is on
R1#
*Aug 19 23:06:38.178: vrfmgr(0) Debug: Condition 1, vrf red triggered, count 1
R1#
Note | The debug condition vrfcommand does not work in an EIGRP environment. |
How to Manage and Troubleshoot EVN
- Setting the Routing Context for EXEC Mode to a Specific VRF
- Enabling Debug Output for VRFs
- Setting SNMP v2c Context for Virtual Networks
- Setting SNMP v3 Context for Virtual Networks
Setting the Routing Context for EXEC Mode to a Specific VRF
In order to reduce the repetitive entering of VRF names when you are issuing EXEC commands on the router, set the routing context of such EXEC commands once, and then proceed with EXEC commands in any order. Perform this task to set the routing context for EXEC mode to a specific VRF, issue EXEC commands, and then restore the system to the global EXEC context.
DETAILED STEPS
Enabling Debug Output for VRFs
DETAILED STEPS
Setting SNMP v2c Context for Virtual Networks
Perform this task to map an SNMP v2c context to a VRF. The following SNMP v2c configurations will then be done by the system automatically:
- Context creation (instead of the snmp-server contextcommand), using the same name as the context-name entered in the snmp context command.
- Group creation (instead of the snmp-server groupcommand), using the same name as the community-name entered in the snmp contextcommand.
- Community creation (instead of the snmp-server communitycommand), using the same name as the community-name entered in the snmp contextcommand. The default permission is ro (read-only).
- Community context mapping (instead of the snmp mib community-mapcommand).
DETAILED STEPS
Setting SNMP v3 Context for Virtual Networks
Perform this task to map an SNMP v3 context to a VRF. The following SNMP v3 configurations will then be done by the system automatically:
- Context creation (instead of the snmp-server contextcommand), using the same name as the context-name entered in the snmp context command.
- Group creation (instead of the snmp-server groupcommand). The group name will be generated by appending "_acnf" to the context-name entered in the snmp contextcommand.
- User creation (instead of the snmp-server usercommand). The user will be created using the detailes configured in the snmp contextcommand.
DETAILED STEPS
Additional References
Related Documents
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
Easy Virtual Network commands |
|
Overview of Easy Virtual Network |
"Overview of Easy Virtual Network" module in the Easy Virtual Network Configuration Guide. |
Configuring Easy Virtual Network |
"Configuring Easy Virtual Network" module in the Easy Virtual Network Configuration Guide. |
Easy Virtual Network shared services and route replication |
"Easy Virtual Network Shared Services" module in the Easy Virtual Network Configuration Guide. |
MIBs
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. |
Feature Information for EVN Management and Troubleshooting
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 2 | Feature Information for EVN Management and Troubleshooting |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)
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.