8600 Smart Routers MPLS Applications Configuration Guide 76.8600-50123F 17.06.2015 Document Information Revision History Document No Date Description of Changes 76.8600-50123F 17.06.2015 Added in this revision: • Support of 8665 Smart Router • 3.6 BGP Multipath in S-MPLS Applications • 4.9 BGP Multipath over S-MPLS Configuration Example Updates or/and changes applied in: • 1.9.4 8600 NEs FRR with addition of LU1 and clarified FRR facility backup operation with RSVP-TE load balancing • 5.7 8600 NEs MPLS-TP Functionality where LU1 is added • Seamless MPLS Applications Enhancements applied in: • MPLS Configuration Examples • Seamless MPLS Configuration Examples 76.8600-50123E 06.11.2014 Added S-MPLS functionality Seamless MPLS Applications Added Seamless MPLS Configuration Examples Added support of 8602 Smart Router and 8615 Smart Router Update and changes applied to 1.9.4 8600 NEs FRR Updates applied in 5.7 8600 NEs MPLS-TP Functionality 76.8600-50123D 04.03.2014 Renewed related documentation table in 8600 Smart Routers Technical Documentation Added MPLS-TP functionality overview in MPLS-TP Applications Added MPLS-TP configuration examples, status in MPLS-TP Configuration Examples Added MPLS-TP Troubleshooting Updates and additions applied in 1.4 MPLS Protection Switching Added IP load balancing support in 8600 NEs in 1.5 RSVP-TE Traffic Load Balancing Changes applied in 1.9 Fast Reroute Including: • Updates in 1.9.2 FRR Operation and Applications • Rework and additions applied in 1.9.3 FRR Provisioning and BFD 8600 Smart Routers MPLS Applications Configuration Guide 76.8600-50123F © 2015 Coriant This revision of the manual documents the following network elements and the corresponding feature packs or higher 8602 Smart Router FP7.0 8605 Smart Router FP1.6 8607 Smart Router FP1.1 8609 Smart Router, 8611 Smart Router FP7.0 8615 Smart Router FP7.0 8620 Smart Router FP4.1 8630 Smart Router, 8660 Smart Router FP7.0 8665 Smart Router FP7.0 If a different feature pack of the 8600 Smart Routers is in use, please refer to the relevant product document program on the Coriant Portal by navigating to www.portal.tellabs.com > Product Documentation > Data Networking > 8600 Smart Routers> Technical Documentation The functionality described in this document for 8615 Smart Router is also applicable to 8615 Smart Router stacked, unless otherwise stated © 2015 Coriant All rights reserved This manual is protected by U.S and international copyright laws, conventions and treaties Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties The specifications and information regarding the products in this manual are subject to change without notice All statements, information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind, express or implied Users must take full responsibility for their application of any products Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries 76.8600-50123F © 2015 Coriant 8600 Smart Routers MPLS Applications Configuration Guide 8600 Smart Routers MPLS Applications Configuration Guide 76.8600-50123F © 2015 Coriant Document Information Terms and Abbreviations 76.8600-50123F © 2015 Coriant Term Explanation AC side interface Attachment Circuit side interface A physical or virtual interface, which connects a CE device to PE router and is bound to some network service, e.g IP VPN or PWE3 AN Access Node AS Autonomous System ASBR Autonomous System Boundary Router ATM Asynchronous Transfer Mode BA Behavior Aggregate BC Bandwidth Constraint BD Business Data BE Best Effort BFD Bidirectional Forwarding Detection BGP Border Gateway Protocol BN Border Node CAC Connection Admission Control CDC Control and DC Power Card There are two types: CDC1 and CDC2 CC Continuity Check CE Customer Equipment CLI Command Line Interface CS Class Selector CSG Customer Site Gateway CSPF Constrained Shortest Path First CT Class Type CV Connectivity Verification DM Packet Delay Measurement (OAM) DSCP DiffServ Code Point DS-TE Differentiated Services-aware MPLS Traffic Engineering eBGP External BGP ECMP Equal Cost Multi-Path ELC1 Ethernet Line Card in 8630 Smart Router, 8660 Smart Router ELP Ethernet Link Protection E-LSP EXP-Inferred-PSC LSPs, or Explicitly TC-Encoded-PSC LSPs ERO Explicit Route Object FD Forward Defect 8600 Smart Routers MPLS Applications Configuration Guide Document Information FFD Fast Failure Detection FIB Forwarding Information Base FM Fault Management FMC Fixed Mobile Convergence FR Frame Relay FRR Fast Reroute FTN Forwarding equivalence class To Next hop label forwarding entry map HDLC High-Level Data Link Control HE Head-End HM High speed Module in 8611 Smart Router iBGP Internal BGP IETF Internet Engineering Task Force IFC Interface Module Concentrator is the line card baseboard IFC line card The IFC line card in 8630 Smart Router and 8660 Smart Router and consists of an IFC and up to two IFMs There are two types of IFC line cards: IFC1 and IFC2 IFM Interface Module IGP Interior Gateway Protocol ILM Incoming Label Map IP Internet Protocol IRB Integrated Routing and Bridging IS-IS Intermediate System to Intermediate System LDP Label Distribution Protocol LER Label Edge Router L-LSP Label-Only-Inferred-PSC LSP LM Line module in 8607 Smart Router, 8609 Smart Router and 8611 Smart Router LM Packet Loss Measurement (OAM) LOC Loss of Continuity LSP Label Switched Path LSR Label Switch Router LU1 Line Unit in 8665 Smart Router MAC Media Access Control MAM Maximum Allocation Model MP Merging Point MP-BGP Multiprotocol Border Gateway Protocol MP-iBGP Multiprotocol iBGP MPLS Multiprotocol Label Switching MPLS-TP Multiprotocol Label Switching Transport Profile 8600 Smart Routers MPLS Applications Configuration Guide 76.8600-50123F © 2015 Coriant Document Information 76.8600-50123F © 2015 Coriant MS-PWE3 Multi-Segment PWE3 NE Network Element OA Ordered Aggregate OAM Operations, Administration and Maintenance ORF Outbound Route Filter OSPF Open Shortest Path First OTN Optical Transport Hierarchy PD Priority Data PE Provider Edge PHB Per Hop Behavior PHP Penultimate Hop Popping PIC Prefix Independent Convergence PLR Point of Local Repair P-LSP Protected LSP PLT Packet Loop Test POS Packet over SDH/SONET PSC PHB Scheduling Class PSC Protection State Coordination (MPLS-TP) PSN Packet Switched Network PTP Precision Time Protocol PWE3 Pseudowire Emulation Edge to Edge QinQ IEEE 802.1QinQ QoS Quality of Service RD Reverse Defect RDI Remote Defect Indication RDM Russian Dolls Model RFC Request For Comments (IETF documents) RIB Routing Information Base RR Router Reflector RRO Record Route Object RSVP-TE Resource Reservation Protocol with Traffic Engineering Extensions RT Real Time SAFI Subsequent Address Family Identifier SCTP Stream Control Transmission Protocol SDH Synchronous Digital Hierarchy S-MPLS Seamless MPLS SONET Synchronous Optical Network 8600 Smart Routers MPLS Applications Configuration Guide Document Information SPF Shortest Path First SS-PWE3 Single-Segment PWE3 TCP Transmission Control Protocol TDM Time Division Multiplexing TE Traffic Engineering TN Transport Node ToS Type of Service Trunk side interface Interface of a router, which is used on the PSN side UDP User Datagram Protocol VC Virtual Circuit VID VLAN ID VoIP Voice over Internet Protocol VPLS Virtual Private LAN Service VPN Virtual Private Network VRF Virtual Routing and Forwarding VSI Virtual Switching Instance WTR Wait to Restore 8600 Smart Routers MPLS Applications Configuration Guide 76.8600-50123F © 2015 Coriant Table of Contents Table of Contents About This Manual 13 Objectives 13 Audience 13 8600 Smart Routers Technical Documentation 13 Interface Numbering Conventions 17 Document Conventions 17 Documentation Feedback 17 8600 Smart Routers Discontinued Products 18 MPLS Overview 19 1.1 Label Distribution 20 1.1.1 LDP 21 1.1.2 RSVP-TE 21 1.2 MPLS Support of Differentiated Services 21 1.2.1 EXP-Inferred-PSC LSPs, or Explicitly TC-Encoded-PSC LSPs (E-LSP) 21 1.2.2 Label-Only-Inferred-PSC LSPs (L-LSP) 22 1.2.3 DiffServ Tunneling Models over MPLS 22 1.3 LSP Affinity Constraints 26 1.4 MPLS Protection Switching 28 1.4.1 MPLS Local Protection 29 1.4.2 RSVP-TE based 1:1 Protection Switching 29 1.5 RSVP-TE Traffic Load Balancing 29 1.6 MPLS Traffic Engineering 30 1.7 DiffServ-Aware MPLS Traffic Engineering 31 1.7.1 Maximum Allocation Model 31 1.7.2 Russian Dolls Model 32 1.8 MPLS MTU Concept 32 1.9 Fast Reroute 33 1.9.1 Overview 33 1.9.2 FRR Operation and Applications 33 1.9.3 FRR Provisioning and BFD 39 1.9.4 8600 NEs FRR 40 1.9.5 Fault Management 40 1.10 MPLS References 41 76.8600-50123F © 2015 Coriant 8600 Smart Routers MPLS Applications Configuration Guide Table of Contents MPLS Configuration Examples 42 2.1 2.2 2.3 2.4 Seamless MPLS Applications 74 3.1 3.2 3.3 3.4 3.5 3.6 3.7 LDP Configuration 42 Explicitly Routed RSVP-TE LSPs 42 2.2.1 RSVP-TE Configuration 43 2.2.2 E-LSP Configuration 44 2.2.3 L-LSP Configuration 46 2.2.4 RSVP-TE Path Protection Configuration 47 2.2.5 RSVP-TE Traffic Load Balancing Configuration 48 2.2.6 Controlled RSVP-TE Tunnel Selection 48 2.2.7 DiffServ Tunnelling Model Configuration 50 DS-TE Network Example 50 FRR CLI Configuration Examples 65 2.4.1 FRR One-to-One 66 2.4.2 Facility Backup 72 Overview 74 S-MPLS Networking 75 3.2.1 Transport Layer 76 3.2.2 End-to-End Service Layer 77 3.2.3 BGP Labeled Unicast Scalability 77 8600 Implementation of S-MPLS 77 3.3.1 S-MPLS Limitations and Restrictions 79 Operation 79 3.4.1 Transport Layer 82 3.4.2 Service Layer 83 Protection and Services Restorations 83 BGP Multipath in S-MPLS Applications 83 3.6.1 Operation 84 3.6.2 BGP Multipath Limitations and Restrictions 87 S-MPLS References 88 Seamless MPLS Configuration Examples 89 4.1 4.2 4.3 4.4 4.5 Configuration Summary 90 Node CSG1 Configuration 91 4.2.1 Configuration Prerequisites 92 4.2.2 S-MPLS Transport and BGP Configuration 93 4.2.3 End-to-End Services Configuration at the Local AS 94 Node R31 Configuration 95 4.3.1 Configuration Prerequisites 95 4.3.2 S-MPLS Transport and BGP Configuration 98 Node R32 Configuration 99 4.4.1 Configuration Prerequisites 99 4.4.2 S-MPLS Transport and BGP Configuration 101 Node R11/ASBR Configuration 102 4.5.1 Configuration Prerequisites 102 4.5.2 S-MPLS Transport and BGP Configuration 104 8600 Smart Routers MPLS Applications Configuration Guide 10 76.8600-50123F © 2015 Coriant MPLS-TP Configuration Examples 6.10 Operation Status in Fault Conditions This chapter provides an illustration of MPLS-TP operation status in different failure scenarios Please refer to BFD Faults and States for more information about BFD states and to 5.5.2 PSC Protocol for more details about the PSC protocol operation 6.10.1 Link Failure When there is a link failure on the tunnel path, BFD detects the failure due to loss of CC packets and the tunnel status goes down As an example, let’s assume that the link between P3 and P4 goes down (Fig 47) and this will cause the following events: • MPLS-TP tunnels go down • BFD session goes down • FTN entries corresponding to an outgoing interface are removed The following diagrams provide an illustration of the status provided when there is a link failure It should be noted that the 8600 NEs support independent BFD mode, where there are separate BFD states for source and sink Therefore, it is possible that based on the network situation a source can be UP while a sink is DOWN or both can be DOWN Fig 62 MPLS-TP LSP Down due to a Link Failure 8600 Smart Routers MPLS Applications Configuration Guide 182 76.8600-50123F © 2015 Coriant MPLS-TP Configuration Examples Fig 63 BFD Session Down due to a Link failure 76.8600-50123F © 2015 Coriant 8600 Smart Routers MPLS Applications Configuration Guide 183 MPLS-TP Configuration Examples Fig 64 MPLS-TP Tunnel Down due to a Link Failure The following figure shows the corresponding FTN entries of the outgoing interface xe7/0/0 in this example being removed due to the fact that the tunnel is down Fig 65 MPLS-TP Tunnel Down and FTN Entries Removed 6.10.2 Mis-Connectivity Mis-connectivity alarms are raised due to incorrect configurations such as: label allocation; next-hop; mismatch in setting global/node IDs Mis-connectivity can also be caused due to hardware faults When a mis-connectivity is detected: 8600 Smart Routers MPLS Applications Configuration Guide 184 76.8600-50123F © 2015 Coriant MPLS-TP Configuration Examples • Sink BFD session goes down with a FD • XCONE alarms are raised • MPLS-TP tunnel goes down Fig 66 MPLS-TP Tunnel Mis-Configuration Status 76.8600-50123F © 2015 Coriant 8600 Smart Routers MPLS Applications Configuration Guide 185 MPLS-TP Configuration Examples Fig 67 Node Detecting Mis-Configuration Status 8600 Smart Routers MPLS Applications Configuration Guide 186 76.8600-50123F © 2015 Coriant MPLS-TP Configuration Examples Fig 68 Peer Node Mis-Configuration Status 6.10.3 Primary Tunnel Failure If there is a failure on the primary tunnel (see diagram below), the following events will take place: • The MPLS-TP protection group status will move into degrade status • The primary tunnel goes down and data traffic will be switched to the backup path • PSC state will go to Protecting Failure • The cause of failure will be signaled as Local Signal Fail on Primary 76.8600-50123F © 2015 Coriant 8600 Smart Routers MPLS Applications Configuration Guide 187 MPLS-TP Configuration Examples Fig 69 Primary Tunnel Failure In protection switchover with revertive mode, when the primary tunnel resumes operation after recovering from a failure the status shown is provided below and the following events take place: • The protection group status will move to OK • PSC state will be in WTR • WTR timer starts counting and WTR alarm will be raised • Data traffic is still being carried over the backup tunnel until the WTR timer expires • After WTR timer expires, data traffic will be switched back to the primary tunnel and PSC state moves to Normal Fig 70 Primary Tunnel Resuming Operation After Failure 8600 Smart Routers MPLS Applications Configuration Guide 188 76.8600-50123F © 2015 Coriant MPLS-TP Configuration Examples When a protection type is set as non-revertive, data traffic will continue to flow through the backup tunnel even after the primary tunnel recovers from a failure condition Below is a sample status for non-revertive protection type Fig 71 Non-revertive Protection Mode Status 6.10.4 Backup Tunnel Failure As previously stated, the PSC protocol always runs on the backup MPLS-TP tunnel Therefore, when a backup tunnel goes down, the PSC state will go to Unavailable state and the PSC protocol failure alarm is raised in this case The following diagram shows the status of a protection group in case of a failure on the backup path Fig 72 Backup Tunnel Failure 6.10.5 Failure on Both Paths In a case when both the primary and backup MPLS-TP tunnels fail, the status of a protection group will be fail and protection group failed alarms will be raised on the NE active faults 76.8600-50123F © 2015 Coriant 8600 Smart Routers MPLS Applications Configuration Guide 189 MPLS-TP Configuration Examples Fig 73 Failure on Both Tunnel Paths 6.11 Manual/Forced Switchover As previously stated, the 8600 NEs support manual/forced switchover actions that are covered in Operator Switchover Actions The following are some use case examples of manual/forced switchover: • During maintenance of the primary tunnel - a manual/forced switchover can be used to move traffic to the backup tunnel • WTR timer overriding - when a WTR timer is running, a manual switchover to the primary tunnel can be performed • Non-revertive protection mode - in this mode traffic is not switched back to the primary tunnel after recovering from a failure Therefore, a manual switchover will allow traffic to be moved to the primary tunnel • During maintenance of the backup tunnel - when it is undesirable to move traffic to the backup tunnel, a lockout of protection can be used Forced/manual switchover does not cause any data loss during the switchover operation When a forced/manual switchover is performed, the state machine of a local node initiating a switchover will go into Protecting Administrative state with a cause set to Local Forced Switchover In this case, the state machine of the remote node will be in Protecting Administrative state with a cause set to Remote Forced Switchover The following is an example showing how to set a manual or forced protection switchover from the primary path to the backup path Manual switchover: Step Set a manual switchover P1# protection manual-switchover mpls-tp Group_P1_to_P6 P1_P2_P5_P6 Forced switchover: Step Set a forced switchover P1# protection force-switchover mpls-tp Group_P1_to_P6 P1_P2_P5_P6 8600 Smart Routers MPLS Applications Configuration Guide 190 76.8600-50123F © 2015 Coriant MPLS-TP Configuration Examples The following diagram shows the status of a forced protection switchover for both ends of the MPLS-TP tunnel (i.e ingress P1 and egress P6 nodes) Fig 74 Manual/Forced Protection Switchover Performing a forced protection switchover to the primary tunnel will cause a Lockout of Protection When a Lockout of Protection condition exists, PSC will transit to Unavailable state Below is an example showing a Lockout of Protection status for both ends of the MPLS-TP tunnel (i.e ingress P1 and egress P6 nodes) 76.8600-50123F © 2015 Coriant 8600 Smart Routers MPLS Applications Configuration Guide 191 MPLS-TP Configuration Examples Fig 75 Lockout of Protection Status A protection clear-switchover command allows to clear a manual/forced switchover operation and also to clear protection lockout condition When clearing a lockout of protection condition, the PSC state machine will transit back to Normal state The following is an example showing how to clear manual/forced switchover, i.e restoring data traffic back to the primary tunnel Step Clear manual/forced protection switchover P1# protection clear-switchover mpls-tp Group_P1_to_P6 After the command above is executed, data traffic will be switched back to the primary path and PSC state will move to Normal again as illustrated below Fig 76 Clearing Protection Switchover Status 8600 Smart Routers MPLS Applications Configuration Guide 192 76.8600-50123F © 2015 Coriant MPLS-TP Troubleshooting MPLS-TP Troubleshooting The overview of MPLS-TP features and functionality is outlined in MPLS-TP Applications and the configuration examples in MPLS-TP Configuration Examples This section provides some troubleshooting guidelines of MPLS-TP MPLS-TP Tunnel Failure Failure Cause MPLS-TP tunnel down BFD session is down due to mis-connectivity BFD session is down due to Loss of Continuity (LOC) Troubleshooting Step 76.8600-50123F © 2015 Coriant Use the show mpls-tp lsp command to verify and identify the name of the tunnel that is down 8600 Smart Routers MPLS Applications Configuration Guide 193 MPLS-TP Troubleshooting Step Verify the detailed tunnel BFD status using the CLI command show mpls-tp bfd name In the status shown, if the BFD session is in FD/RD state with: • XCONE/mis-connectivity defect: • Check configurations of the ingress, egress and transit nodes to verify if the labels are allocated properly Use the CLI command show run | block on ingress/egress/transit nodes to verify the forward and reverse LSP configurations of the tunnel • Verify if the “from node-ID” and “to node-ID” configurations are uniform on all the nodes through which the tunnel traverses This can be verified using the CLI command: show mpls-tp tunnel name The above command will display the tunnel level local configuration of the MPLS IDs (global, node and tunnel IDs) • Verify if a global ID configuration at the NE level matches with the tunnel level global ID configuration Use the CLI command show run | block on ingress/egress/transit nodes to verify if the set global ID is the same • LOC defect: • For point to point interfaces: • If a tunnel is traversing over point to point interfaces that not have IP address configured, ensure that the next-hop address is also not configured on forward and reverse LSPs • Verify that all the interfaces through which the tunnel traverses are in ADMIN UP / LINE STATE UP Using the CLI command show ip interface brief If any interface is ADMIN DOWN, then bring the interface up by executing a no shutdown command If any interface is in LINE STATUS DOWN, execute a no laser command If the interface still is down, please check cabling connectivity • For IP interfaces (interfaces where the IP address is set): • Verify that all the interfaces through which the tunnel traverses are in ADMIN UP / LINE STATE UP Using the CLI command show ip interface brief If any interface is ADMIN DOWN, then bring the interface up by executing a no shutdown command If any interface is in LINE STATUS DOWN, execute a laser command (in case of optical interface), or no shutdown-if command If the interface still is down, please check cabling connectivity • Verify if the next-hop is reachable, i.e ping to the next-hop IP address configured in forward and reverse LSP should be successful on ingress, egress and transit nodes by using the CLI command ping It is worth to note that the next-hop IP configuration is mandatory for non point-to-point interfaces • Alternatively troubleshooting of link state connectivity can also be performed using Ethernet OAM Ethernet ping/trace route tools can be used to identify any link connectivity issues in the network Step Resolve configuration errors or cabling issues if any Step If the tunnel still is DOWN, verify if there are any hardware faults This can be verified using the CLI show faults active command and resolve the hardware issues Step After performing the steps above and the MPLS-TP tunnel still is DOWN, please go through the MPLS-TP configuration flow outlined in MPLS-TP Configuration Examples to identify possible configuration issues that may cause the tunnel to be down 8600 Smart Routers MPLS Applications Configuration Guide 194 76.8600-50123F © 2015 Coriant MPLS-TP Troubleshooting Loss of Data Traffic Failure Cause Loss of data traffic Loss of data traffic could be due to one of the following reasons: • MPLS-TP tunnel is down • map-route statement is not defined properly Troubleshooting Step Verify if the MPLS-TP tunnel that carries data traffic is UP using the CLI command show mpls-tp lsp If the tunnel is DOWN, please follow the steps outlined in MPLS-TP Tunnel Failure to recover the tunnel Step If the MPLS-TP tunnel is UP, use the CLI command show mpls ftn to check if the label to the required destination exists If the FTN entries not exist, verify if the map-route statement is configured Execute the CLI command show run | block on ingress and egress nodes to verify if the map-route entries are defined Configure the map-route statements, if they are not configured Step If the MPLS-TP tunnel is UP and FTN entries exist and still data loss is observed, verify if the IP address/mask of the destination network is configured properly in map-route statement using the CLI command show mpls-tp tunnel name Correct configuration errors if any Step If data loss persist: • Verify if there are any mis-configurations in the tunnel affinity selection / QoS values in map-route statement Correct configuration errors if any • Verify if the remote interface that connects to the destination network is ADMIN/LINESTATE UP using the CLI command show ip interface brief If the interface is down, resolve cabling issues Step If there is a partial data loss, verify if the rate or amount of data traffic sent is exceeding the interface capacity using the CLI command show queue statistics The maximum threshold exceeded packets counter in the above command output can be used to verify if the interface threshold has been exceeded If it is exceeded, please limit the data rate within the interface capacity to avoid data loss, using eth bandwidth rate-limit CLI command (see more details in 8600 Smart Routers CLI Commands Manual) Step After performing the steps above and data lost persist, please contact Tellabs Technical Support MPLS-TP Protection and PSC Failure The following table provides an overview of some failure scenarios that can occur in protection switchover operation, which can also cause data loss during the switchover operation and ways to troubleshoot 76.8600-50123F © 2015 Coriant 8600 Smart Routers MPLS Applications Configuration Guide 195 MPLS-TP Troubleshooting Failure Cause Failure in operator switchover actions A manual switchover to the destination tunnel will fail, if the destination tunnel is DOWN (due to link down or configuration issues) Also if in a protection group the backup tunnel fails, the PSC protocol will fail, which will cause failures in any further operator switchover actions Unexpected data loss A failure on the primary tunnel will cause protection switchover to the backup tunnel A delay or failure in protection switchover may occur due to one of the following reasons: • Failure of PSC protocol due to configuration errors • Mismatch in map-route statements on the primary and backup tunnels • Backup tunnel is DOWN • Protection switchover denied due to Lockout of Protection Troubleshooting Step Check the protection group status and status of both the primary and backup tunnels using the command show protection mpls-tp name If the protection group is in degraded/failed state due to tunnel failure, please follow the steps outlined in MPLS-TP Tunnel Failure to recover the tunnel Step If the backup tunnel is UP, verify the protection group configuration PSC protocol should be enabled on the both ends for the switchover time to stay within the defined limits Use the CLI command show protection mpls-tp name to verify if the PSC protocol has RFC6378 on both ingress and egress nodes If the command output shows PSC protocol as none, configure the PSC protocol as RFC6378 inside the protection group on both ingress and egress nodes Step If the protection group is configured properly, verify that the map-route statements match on both the primary and backup tunnels using the CLI command show mpls-tp tunnel name If there is a mismatch in the map-route statement, correct the configuration mismatch so that both the primary and backup tunnels have exactly the same map-route statements configured Step If there are no configuration issues, verify that a protection lockout state exists using the CLI command show protection mpls-tp name A protection lockout will prevent data traffic switchover to the backup tunnel in case of failure on the primary tunnel Use the CLI command protection clear-switchover mpls-tp command to clear a lockout condition 8600 Smart Routers MPLS Applications Configuration Guide 196 76.8600-50123F © 2015 Coriant ... and/or other countries 76. 8600- 50123F © 2015 Coriant 8600 Smart Routers MPLS Applications Configuration Guide 8600 Smart Routers MPLS Applications Configuration Guide 76. 8600- 50123F © 2015 Coriant... fi-documentation@tellabs.com 76. 8600- 50123F © 2015 Coriant 8600 Smart Routers MPLS Applications Configuration Guide 17 8600 Smart Routers Discontinued Products 8600 Smart Routers Discontinued Products 8600 Smart Routers. .. This topic is covered in the 8600 Smart Routers VPNs Configuration Guide 8600 Smart Routers MPLS Applications Configuration Guide 20 76. 8600- 50123F © 2015 Coriant 1 MPLS Overview 1.1.1 LDP LDP