-
Cisco MPLS Diagnostics Expert 2.1.3 User Guide on ISC 5.1
-
Index
-
About this Guide
-
Chapter 1: Introduction
-
Chapter 2: Getting Started
-
Chapter 3: Using Cisco MPLS Diagnostics Expert
-
Chapter 4: How Does Cisco MPLS Diagnostics Expert Work?
-
Appendix A: Frequently Asked Questions
-
Appendix B: VPN Topologies
-
Appendix C: Cisco MPLS Diagnostics Expert Supplemental License Agreement
-
Table Of Contents
1.3 Supported Hardware, IOS, and IOS XR Versions
Introduction
This chapter provides an overview of the Cisco MPLS Diagnostics Expert (MDE) application.
This chapter contains the following sections:
•
Supported Hardware, IOS, and IOS XR Versions
1.1 MDE Overview
MDE is an automated, workflow-based network management application that troubleshoots and diagnoses problems in Multiprotocol Label Switching (MPLS) VPNs. MDE offers users the capability to reduce the amount of time required to diagnose MPLS-related network outages—in many cases from hours to minutes. It performs diagnostics based on analysis of network failure scenarios, across MPLS access, edge, and core networks. It is equally applicable to both service provider and enterprise "self-deployed" MPLS VPN networks. Network operations center (NOC) support technicians as well as second-line and third-line support can benefit from this product. MDE optionally integrates with the ISC MPLS VPN provisioning component. To diagnose MPLS VPN core problems, Cisco IOS and IOS XR software releases supporting MPLS operations and maintenance (OAM) features including label-switched path (LSP) ping and LSP traceroute are required.
In effective fault finding and troubleshooting, there are five steps:
1.
2.
3.
4.
5.
MDE is designed to support reactive situations in which an end customer reports a problem with their VPN service. This is essentially the Detection step in Figure 1-1. The Repair function is not supported because many providers prefer to be in complete control of any changes made to router devices and might have specific in-house procedures for doing so.
Figure 1-1 The Reactive Fault Lifecycle
Note
MDE focuses on the Isolation, Diagnosis, and Verification steps. It provides invaluable functionality for isolating and diagnosing failures in the network, determining the device(s) at fault, and checking appropriate device status and configuration to determine the likely reason for the failure. MDE also provides the ability to rerun tests to verify that changes made to the device configuration have resolved the issue.
The functionality can be used on its own, without any dependency on any other modules in ISC (for example, VPN provisioning or Traffic Engineering Management). It can also be used in ISC installations where some or all of the other ISC modules are used. If the MPLS VPN Provisioning functionality is used, then Customer and VPN data can be used as a starting point for troubleshooting, to locate the endpoints (for example, Customer Edge devices) between which connectivity is tested.
In addition to troubleshooting, MDE can also be used for VPN post-provisioning checks. After deploying a VPN, either manually or using ISC VPN provisioning, a connectivity test can be run to verify that the VPN has been provisioned successfully.
1.2 Prerequisite Knowledge
MDE has been designed for use by users who have minimal MPLS VPN knowledge. An MDE MPLS VPN Connectivity Verification Test can be performed by a user with little or no MPLS VPN knowledge, and, where necessary, the test results can be exported for interpretation by an engineer familiar with MPLS VPNs. However, due to the complex nature of MPLS VPNs, it is recommended that you will gain maximum advantage from MDE if you are familiar with MPLS VPNs, in accordance with RFC 2547. In particular, knowledge of RFC 2547 architecture, topology, control, and data planes is helpful to understand how to best use the application and interpret the results.
MDE now diagnoses Cisco devices and networks that use IETF RFC 4379 compliant Label Switched Path (LSP) ping and LSP traceroute. MDE continues to support the earlier draft (draft 3) available in Cisco IOS. You must use a consistent draft of LSP ping and traceroute across all devices in your network.
Recommended reading:
•
•
•
•
•
•
products_feature_guide09186a00801eb054.html1.3 Supported Hardware, IOS, and IOS XR Versions
For details of Provider (P) and Provider Edge (PE) network device types and related Cisco IOS and IOS XR versions supported, see the Cisco IP Solution Center Installation Guide, 5.1.
Note
Device types, IOS, and IOS XR versions detailed in the Cisco IP Solution Center Installation Guide, 5.1 support the MPLS label switched path (LSP) Ping and Traceroute feature. This feature is required for MDE troubleshooting. If all P and PE devices comply with the list of supported device types, IOS, and IOS XR versions, MDE can troubleshoot access circuit, MPLS VPN, and MPLS core problems. MDE is tolerant to other device types, IOS, and IOS XR versions, including other vendors' equipment. However, when the network includes P or PE devices that do not comply with this list, a complete diagnosis might not be possible. Table 1-1 shows the possible scenarios and likely outcome.
MDE supports both managed and unmanaged CE routers from any vendor. There are no device type, IOS, or IOS XR version requirements for CE devices.
MDE can work with other device types, IOS, and IOS XR versions that support the MPLS LSP Ping and Traceroute feature. Use the Cisco Feature Navigator for details of device types, IOS, and IOS XR versions that support this feature. See http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp
Note
1.4 MDE Features
MDE troubleshooting and diagnostics supports the following three domains:
1.
2.
3.
MDE does not troubleshoot routing protocols within the core, IP connectivity within the core, and some variants of inter-Autonomous Systems (AS) or Carrier-Supporting-Carrier (CsC), specifically Inter AS option B and CsC where there is no LSP.
