mpls traffic engineering - fast reroute link protection...tunne1l0 tun pos5/0:untagged tu0:12304...

MPLS Traffic Engineering - Fast Reroute LinkProtection

This feature module describes the Fast Reroute (FRR) link protection and Bidirectional Forwarding Detection(BFD)-triggered FRR feature of Multiprotocol Label Switching (MPLS) traffic engineering (TE).

• Finding Feature Information, on page 1• Prerequisites for MPLS Traffic Engineering - Fast Reroute Link Protection, on page 1• Restrictions for MPLS Traffic Engineering - Fast Reroute Link Protection, on page 2• MPLS TE-FRR Link Protection Overview, on page 2• How to Configure Traffic Engineering - Fast Reroute Link Protection, on page 4• Verification Examples, on page 15• Configuration Examples, on page 22• Additional References, on page 22• Feature Information for MPLS Traffic Engineering - Fast Reroute Link Protection, on page 23

Finding Feature InformationYour software release may not support all the features documented in this module. For the latest featureinformation and caveats, see the release notes for your platform and software release. To find informationabout 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 module.

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

Prerequisites for MPLS Traffic Engineering - Fast Reroute LinkProtection

• Cisco IOS Release 15.2(2)SNG or a later release that supports theMPLS TE-FRR link protection featuremust be installed previously on the Cisco ASR 901 Series Aggregation Services Router.

• You should enable the asr901-platf-frr command at the global configuration before using TE-FRR.

MPLS Traffic Engineering - Fast Reroute Link Protection1

http://tools.cisco.com/ITDIT/CFN/

• Your network must support both the following Cisco IOS features before you can enable Fast Reroutelink protection:

• IP Cisco Express Forwarding (CEF)• Multiprotocol Label Switching (MPLS)

• Your network must also support at least one of the following protocols:

• Intermediate System-to-Intermediate System (IS-IS)• Open Shortest Path First (OSPF)

Restrictions for MPLS Traffic Engineering - Fast Reroute LinkProtection

• MPLS TE works only on the Switch Virtual Interface (SVI).

• MPLS TE-FRR feature is used only for link protection and not for node protection.

• MPLS deployments that allows 4-label push is not supported.

• When the TE-FRR deployments are in ring topology, hair-pinning can occur while trying to reach thedestination during cutover.

• MPLS TE-FRR is not supported on layer 3 over layer 2 deployments.

• You cannot configure BFD and RSVP on the same interface.

• You should use the no l3-over-l2 flush buffers command before configuring MPLS TE-FRR feature.

• Path protection is not supported.

• Time-division multiplexing (TDM) psuedowire over TE-FRR is not supported.

• QoS is not supported on the MPLS TE tunnels.

• You cannot enable FRR hello messages on a router that also has Resource Reservation Protocol (RSVP)Graceful Restart enabled.

• Psuedowire redundancy over TE-FRR is not supported.

• CFM over Xconnect over TE-FRR is not supported.

• The imposition statistics will not work for EOMPLS after the FRR event or layer 3 cutover.

MPLS TE-FRR Link Protection OverviewThe MPLS TE is supported on the Cisco ASR 901 router to enable only the FRR. The traffic engineeringaspects of MPLS TE is currently not supported. The MPLS TE is the process of establishing and maintaininglabel-switched paths (LSPs) across the backbone using Resource Reservation Protocol (RSVP). The path usedby a given LSP at any point in time is based upon the LSP resource requirements and available networkresources.


MPLS Traffic Engineering - Fast Reroute Link ProtectionRestrictions for MPLS Traffic Engineering - Fast Reroute Link Protection

The MPLS TE-FRR feature is useful for time critical applications like voice calls that require minimal lossof data during link failures. This feature is used to overcome the issue of convergence speed experienced bythe Interior Gateway Protocol (IGP) fast timers.

In the MPLS TE-FRR feature, backup tunnels are used to minimize the impact of link breakages. The pointof failure can either be a head-end tunnel or a mid-point. In both the cases, the scope of recovery is local. Thereroute decision is completely controlled locally by the router interfacing the failed link. The recovery is doneby the node that listens to the failure. The node that detects the failure switches the traffic to the backup linkwith the least amount of delay.

The following figure illustrates the FRR link protection.Figure 1: FRR Link Protection

Backup linkR2-R6-R7-R3Head-end of the tunnelR2

Tail-end of tunnelR3Protected linkR2-R3

Primary linkR2-R3

The MPLS TE-FRR feature supports the following:

• IP, L3VPN, and EoMPLS.• Supports BFD sessions with 50ms interval.• Single hop tunnel and multi-hop tunnel deployments.• Auto-tunnel feature in primary and backup nodes.• Targeted LDP sessions on tunnels.

BFD-triggered Fast RerouteThe MPLS Traffic Engineering: BFD-triggered Fast Reroute feature allows you to obtain link protection byusing the BFD protocol.

BFDBFD is a detection protocol designed to provide fast forwarding link failure detection times for all mediatypes, encapsulations, topologies, and routing protocols. In addition to fast forwarding link failure detection,BFD provides a consistent failure detection method for network administrators. Because the networkadministrator can use BFD to detect forwarding link failures at a uniform rate, rather than the variable ratesfor different routing protocol Hello mechanisms, network profiling and planning is easier, and reconvergencetime is consistent and predictable.


MPLS Traffic Engineering - Fast Reroute Link ProtectionBFD-triggered Fast Reroute

Fast RerouteFast Reroute is a mechanism for protecting MPLS TE LSPs from link failures by locally repairing the LSPsat the point of failure. This allows the data to continue to flow on them while their headend routers attemptto establish new end-to-end LSPs to replace them. FRR locally repairs the protected LSPs by rerouting themover backup tunnels that bypass failed links.

Link ProtectionBackup tunnels that bypass only a single link of the LSP’s path provide link protection. They protect LSPs ifa link along their path fails by rerouting the LSP’s traffic to the next hop (bypassing the failed link). Theseare referred to as next-hop (NHOP) backup tunnels because they terminate at the LSP’s next hop beyond thepoint of failure.

How to Configure Traffic Engineering - Fast Reroute LinkProtection

This section describes how to configure MPLS TE-FRR Link Protection feature:

Enabling MPLS TE-FRR on an SVI InterfaceTo enable MPLS TE-FRR on an SVI interface, perform the steps given below:

SUMMARY STEPS

1. enable2. configure terminal3. interface type number4. mpls traffic-engg tunnels

DETAILED STEPS

PurposeCommand or Action

Enables the privileged EXEC mode.enableStep 1

Example: • Enter your password if prompted.

Router> enable

Enters the global configuration mode.configure terminal

Example:

Step 2

Router# configure terminal

Specifies an interface type and number and enters interfaceconfiguration mode.

interface type number

Example:

Step 3

Router(config)# interface vlan 40


MPLS Traffic Engineering - Fast Reroute Link ProtectionFast Reroute


Enables MPLS TE tunnel signaling on the specifiedinterface.

mpls traffic-engg tunnels

Example:

Step 4

Router(config-if)# mpls traffic-engg tunnels

Example:

Enabling MPLS TE-FRR for EoMPLS on a Global InterfaceTo enable MPLS TE-FRR for EoMPLS on a global interface, perform the steps given below:

SUMMARY STEPS

1. enable2. configure terminal3. no l3-over-l2 flush buffers4. asr901-platf-frr enable5. mpls ldp discovery targeted-hello accept6. pseudowire-class pw-class-name7. encapsulation encapsulation-type8. preferred-path {[interface] tunnel tunnel-number| peer host-ip-address} [disable-fallback]9. exit10. mpls label protocol ldp11. mpls ldp igp sync holddown milli-seconds

DETAILED STEPS




Router> enable


Example:

Step 2


Disables layer 3 over layer 2 deployments.no l3-over-l2 flush buffers

Example:

Step 3

Router(config)# no l3-over-l2 flush buffers


MPLS Traffic Engineering - Fast Reroute Link ProtectionEnabling MPLS TE-FRR for EoMPLS on a Global Interface


Enables TE-FRR link protection.asr901-platf-frr enable

Example:

Step 4

Router(config)# asr901-platf-frr enable

Configures the neighbors fromwhich requests for targetedhello messages may be honored.

mpls ldp discovery targeted-hello accept

Example:

Step 5

Router(config)# mpls ldp discovery targeted-helloaccept

Specifies the name of a layer 2 pseudowire class and enterspseudowire class configuration mode.

pseudowire-class pw-class-name

Example:

Step 6

Router(config)# pseudowire-class T41

Specifies the encapsulation method used by the interface.encapsulation encapsulation-type

Example:

Step 7

Router(config-pw-class)# encapsulation mpls

Specifies the MPLS TE tunnel that traffic uses.preferred-path {[interface] tunnel tunnel-number| peerhost-ip-address} [disable-fallback]

Step 8

• interface—Specifies the preferred path using anoutput interface.Example:

• tunnel—Specifies an MPLS TE tunnel interface thatis the core-facing output interface.Router(config-pw-class)# preferred-path interface

Tunnel41 disable-fallback • tunnel-number—Tunnel interface number.• peer—Specifies a destination IP address or DNSname configured on the peer provider edge (PE)router, which is reachable through a label switchedpath (LSP).

• host-ip-address—Peer host name or IP address.

Exits the pseudowire class configuration mode and entersthe global configuration mode.

exit

Example:

Step 9

Router(config-pw-class)# exit

Specifies the label distribution protocol for an interface.Here LDP protocol is used.

mpls label protocol ldp

Example:

Step 10

Router(config)# mpls label protocol ldp

Specifies how long an Interior Gateway Protocol (IGP)should wait for Label Distribution Protocol (LDP)synchronization to be achieved.

mpls ldp igp sync holddown milli-seconds

Example:

Router(config)# mpls ldp igp sync holddown 1000

Step 11


MPLS Traffic Engineering - Fast Reroute Link ProtectionEnabling MPLS TE-FRR for EoMPLS on a Global Interface

Enabling MPLS TE-FRR for EoMPLS on an InterfaceTo enable MPLS TE-FRR for EoMPLS on an interface, perform the steps given below:

SUMMARY STEPS

1. pw-class2. auto terminal3. pseudowire-class pw-class-name4. no negotiation auto5. service instance id ethernet6. encapsulation dot1q vlan-id7. rewrite ingress tag pop 1 symmetric8. xconnect peer-ip-address vc-id pw-class pw-class-name

DETAILED STEPS


Enables the privileged EXEC mode.pw-classStep 1


Router> enable

Enters the global configuration mode.auto terminal

Example:

Step 2


Specifies the name of a layer 2 pseudowire class and enterspseudowire class configuration mode.

pseudowire-class pw-class-name

Example:

Step 3

Router(config)# pseudowire-class T41

Disables the automatic negotiation.no negotiation auto

Example:

Step 4

Router(config-if)# no negotiation auto

Configures an Ethernet service instance on an interface.The id is an integer that uniquely identifies a service

service instance id ethernet

Example:

Step 5

instance on an interface. The value varies by the platform.

Router(config-if)# service instance 100 ethernetRange: 1 to 4294967295. The identifier need not map to aVLAN and is local in scope to the interface.

Enables IEEE 802.1Q encapsulation of traffic on a specifiedsubinterface in a VLAN. The vlan-id is the Virtual LAN

encapsulation dot1q vlan-id

Example:

Step 6

identifier. The allowed range is from 1 to 4094. For the

Router(config-if-srv)# encapsulation dot1q 101IEEE 802.1Q-in-Q VLAN Tag Termination feature, thefirst instance of this argument defines the outer VLAN ID,


MPLS Traffic Engineering - Fast Reroute Link ProtectionEnabling MPLS TE-FRR for EoMPLS on an Interface


and the second and subsequent instances define the innerVLAN ID.

Specifies the encapsulation adjustment to be performed ona frame ingressing a service instance.

rewrite ingress tag pop 1 symmetric

Example:

Step 7

Router(config-if-srv)# rewrite ingress tag pop 1symmetric

Binds an attachment circuit to a pseudowire, and toconfigure an Any Transport over MPLS (AToM) staticpseudowire.

xconnect peer-ip-address vc-id pw-class pw-class-name

Example:

Router(config-if-srv)# xconnect 10.0.0.4 4 pw-classT41

Step 8

• peer-ip-address—IP address of the remote provideredge (PE) peer. The remote router ID can be any IPaddress, as long as it is reachable.

• vc-id—The 32-bit identifier of the virtual circuit (VC)between the PE routers.

• pw-class—Specifies the pseudowire class for advancedconfiguration.

• pw-class-name—Pseudowire class name.

Enabling MPLS TE-FRR for IS-ISTo enable MPLS TE-FRR for IS-IS routing process, perform the steps given below:

SUMMARY STEPS

1. mpls-ldp2. configure terminal3. router isis4. mpls traffic-eng router-id interface-name5. mpls traffic-eng {level-1 | level-2}6. router isis7. net net-18. is-type level-19. fast-reroute per-prefix level-1 all10. fast-reroute per-prefix level-2 all11. fast-reroute remote-lfa level-1 mpls-ldp12. fast-reroute remote-lfa level-2 mpls-ldp13. bfd all-interfaces14. mpls ldp sync


MPLS Traffic Engineering - Fast Reroute Link ProtectionEnabling MPLS TE-FRR for IS-IS

DETAILED STEPS


Enables the privileged EXEC mode.mpls-ldpStep 1


Router> enable


Example:

Step 2


Activates the IS-IS routing process for IP and puts thedevice into router configuration mode.

router isis

Example:

Step 3

Router(config)# router isis

Specifies that the traffic engineering router identifier forthe node is the IP address associated with a given interface.

mpls traffic-eng router-id interface-name

Example:

Step 4

The interface-name is the interface whose primary IPaddress is the router's identifier

Router(config-router)# mpls traffic-eng router-idLoopback102

Configures a router running IS-IS so that it floods MPLSTE link information into the indicated IS-IS level.

mpls traffic-eng {level-1 | level-2}

Example:

Step 5

• level-1—Floods MPLS TE link information intoIS-IS level 1.Router(config-router)# mpls traffic-eng level-1

• level-2—Floods MPLS TE link information intoIS-IS level 2.

Enables the IS-IS routing protocol and enters the routerconfiguration mode.

router isis

Example:

Step 6

Router(config)# router isis

Configures an Intermediate System-to-Intermediate System(IS-IS) network entity table (NET) for the routing process.

net net-1

Example:

Step 7

• net-1—NET network services access point (NSAP)name or address for the IS-IS routing process on theRouter(config)# net 49.0001.0000.0000.0001.00

Mulltilayer Switch Feature Card (MSFC) in theprimary slot.

Configures the routing level for an instance of theIntermediate System-to-Intermediate System (IS-IS)routing process.

is-type level-1

Example:

Router(config-router)# is-type level-1

Step 8


MPLS Traffic Engineering - Fast Reroute Link ProtectionEnabling MPLS TE-FRR for IS-IS


Configures an FRR path that redirects traffic to a remoteLFA tunnel for level-1 packets.

fast-reroute per-prefix level-1 all

Example:

Step 9

• level-1—Enables per-prefix FRR of level 1 packets.Router(config-router)# fast-reroute per-prefixlevel-1 all

• all—Enables FRR of all primary paths.

Configures an FRR path that redirects traffic to a remoteLFA tunnel for level-2 packets.

fast-reroute per-prefix level-2 all

Example:

Step 10

• level-2—Enables per-prefix FRR of level 2 packets.Router(config-router)# fast-reroute per-prefixlevel-2 all

• all—Enables FRR of all primary paths.

Configures an FRR path that redirects traffic to a remoteLFA tunnel.

fast-reroute remote-lfa level-1 mpls-ldp

Example:

Step 11

• level-1—Enables LFA-FRR of level-1 packets.Router(config-router)# fast-reroute remote-lfalevel-1 mpls-ldp

• mpls-ldp—Specifies that the tunnel type is MPLSor LDP.

Configures an FRR path that redirects traffic to a remoteLFA tunnel.

fast-reroute remote-lfa level-2 mpls-ldp

Example:

Step 12

• level-2—Enables LFA-FRR of level-2 packets.Router(config-router)# fast-reroute remote-lfalevel-2 mpls-ldp

• mpls-ldp—Specifies that the tunnel type is MPLS orLDP.

Enables Bidirectional Forwarding Detection (BFD) for allinterfaces participating in the routing process.

bfd all-interfaces

Example:

Step 13

Router(config-router)# bfd all-interfaces

Enables MPLS LDP synchronization on interfaces for anIS-IS process.

mpls ldp sync

Example:

Step 14

Router(config-router)# mpls ldp sync

Configuring Primary One-hop Auto-TunnelsTo configure primary one-hop auto-tunnels for MPLS TE-FRR, perform the following steps.

SUMMARY STEPS

1. enable2. configure terminal3. mpls traffic-eng auto-tunnel primary onehop4. mpls traffic-eng auto-tunnel primary tunnel-num [min min-num] [max max-num ]5. mpls traffic-eng auto-tunnel primary config unnumbered interface6. mpls traffic-eng auto-tunnel primary timers removal rerouted sec


MPLS Traffic Engineering - Fast Reroute Link ProtectionConfiguring Primary One-hop Auto-Tunnels

7. mpls traffic-eng auto-tunnel primary config mpls ip

DETAILED STEPS


Enables privileged EXEC mode.enableStep 1


Router> enable

Enters global configuration mode.configure terminal

Example:

Step 2


Creates primary tunnels to all the next hops automatically.mpls traffic-eng auto-tunnel primary onehop

Example:

Step 3

Router(config)# mpls traffic-engauto-tunnel primary onehop

Configures the range of tunnel interface numbers forprimary autotunnels.

mpls traffic-eng auto-tunnel primary tunnel-num [minmin-num] [max max-num ]

Step 4

Example: • min-num—(Optional)Minimumnumber of the primarytunnels. The range is 0 to 65535, with a default valueof 65436.Router(config)# mpls traffic-eng auto-tunnel

primary tunnel-num min 3 max 400 • max-num—(Optional) Maximum number of theprimary tunnels. The max number is the minimumnumber plus 99. The range is from 0 to 65535.

Enables IP processing without an explicit address.mpls traffic-eng auto-tunnel primary configunnumbered interface

Step 5

• interface—Interface on which IP processing is enabledwithout an explicit address.Example:

Router(config)# mpls traffic-eng auto-tunnelprimary config unnumbered-interface Loopback102

Configures the period after a failure to remove primaryautotunnels.

mpls traffic-eng auto-tunnel primary timers removalrerouted sec

Step 6

Example: • sec—Number of seconds after a failure that primaryautotunnels are removed. The range is from 30 to604,800, with a default of 0.Router(config)# mpls traffic-eng auto-tunnel

primary timers removal rerouted 604800

Enables Label Distribution Protocol (LDP) on primaryautotunnels.

mpls traffic-eng auto-tunnel primary config mpls ip

Example:

Step 7

Router(config)# mpls traffic-eng auto-tunnelprimary config mpls ip


MPLS Traffic Engineering - Fast Reroute Link ProtectionConfiguring Primary One-hop Auto-Tunnels

Configuring Backup Auto-TunnelsTo configure backup auto-tunnels, perform the following steps.

SUMMARY STEPS

1. enable2. configure terminal3. mpls traffic-eng auto-tunnel backup4. mpls traffic-eng auto-tunnel backup nhop-only5. mpls traffic-eng auto-tunnel backup tunnel-num [min min-num] [max max-num]6. mpls traffic-eng auto-tunnel backup timers removal unused sec7. mpls traffic-eng auto-tunnel backup config unnumbered-interface interface

DETAILED STEPS


Enables privileged EXEC mode.enableStep 1


Router> enable

Enters global configuration mode.configure terminal

Example:

Step 2


Builds next-hop (NHOP) and next-next hop (NNHOP)backup tunnels automatically.

mpls traffic-eng auto-tunnel backup

Example:

Step 3

Router(config)# mpls traffic-eng auto-tunnelbackup

Builds next-hop (NHOP) backup tunnels automatically.mpls traffic-eng auto-tunnel backup nhop-only

Example:

Step 4

Router(config)# mpls traffic-eng auto-tunnelbackup nhop-only

Configures the range of tunnel interface numbers for backupautotunnels.

mpls traffic-eng auto-tunnel backup tunnel-num [minmin-num] [max max-num]

Step 5

Example: • min-num—(Optional)Minimumnumber of the backuptunnels. The range is 0 to 65535, with a default valueof 65436.Router(config)# mpls traffic-eng auto-tunnel

backup tunnel-num min 3 max 400 • max-num—(Optional)Maximumnumber of the backuptunnels. Themax number is the minimum number plus99. The range is from 0 to 65535.


MPLS Traffic Engineering - Fast Reroute Link ProtectionConfiguring Backup Auto-Tunnels


Configures how frequently a timer scans the backupautotunnels and remove tunnels that are not being used.

mpls traffic-eng auto-tunnel backup timers removalunused sec

Step 6

Example: • sec—Configures (in seconds) the timer scan interval.The range is 0 to 604,800.

Router(config)# mpls traffic-eng auto-tunnelprimary timers removal rerouted 604800

Configures a specific unnumbered interface for all backupauto-tunnels.

mpls traffic-eng auto-tunnel backup configunnumbered-interface interface

Step 7

Example: • interface—Interface for all backup auto-tunnels.Default interface is Loopback0.

Router(config)# mpls traffic-eng auto-tunnelbackup config unnumbered-interface Loopback0

Enabling Targeted LDP session over Primary one-hop Auto-TunnelsAnMPLS LDP targeted session is a label distribution session between routers that are not directly connected.When you create an MPLS TE tunnel interface, you need to establish a label distribution session between thetunnel headend and the tailend routers. You establish non-directly connectedMPLS LDP sessions by enablingthe transmission of targeted Hello messages.

The default behavior of an LSR is to ignore requests from other LSRs that send targeted Hello messages. Youcan configure an LSR to respond to requests for targeted Hello messages by using the mpls ldp discoverytargeted-hello accept command.

The active LSR mandates the protocol that is used for a targeted session. The passive LSR uses the protocolof the received targeted Hello messages.

To enable targeted LDP sessions over primary one-hop auto-tunnels, perform the steps given below:

For targeted mpls session, the head end tunnel should have “mpls ip” configuration.Note

SUMMARY STEPS

1. enable2. configure terminal3. mpls ldp discovery targeted-hello accept

DETAILED STEPS




Router> enable


MPLS Traffic Engineering - Fast Reroute Link ProtectionEnabling Targeted LDP session over Primary one-hop Auto-Tunnels



Example:

Step 2


Configures the router to respond to requests for targetedHello messages from all neighbors.

mpls ldp discovery targeted-hello accept

Example:

Step 3

Router(config)# mpls ldp discovery targeted-helloaccept

Enabling BFD Triggered FRR on an SVI InterfaceTo enable BFD triggered FRR on an SVI interface, perform the steps given below:

SUMMARY STEPS

1. enable2. configure terminal3. interface type number4. ip rsvp signalling hello bfd

DETAILED STEPS




Router> enable


Example:

Step 2


Specifies an interface type and number, and enters interfaceconfiguration mode.

interface type number

Example:

Step 3

Router(config)# interface vlan 40

Enables BFD protocol on an interface for FRR linkprotection.

ip rsvp signalling hello bfd

Example:

Step 4

Router(config-if)# ip rsvp signalling hello bfd


MPLS Traffic Engineering - Fast Reroute Link ProtectionEnabling BFD Triggered FRR on an SVI Interface

Enabling BFD Triggered FRR on a RouterTo enable BFD triggered FRR on a router, perform the steps given below:

SUMMARY STEPS

1. enable2. configure terminal3. ip rsvp signalling hello bfd

DETAILED STEPS




Router> enable


Example:

Step 2


Enables BFD protocol on an interface for FRR linkprotection.

ip rsvp signalling hello bfd

Example:

Step 3

Router(config-if)# ip rsvp signalling hello bfd

What to do next

Verification Examples

Verifying MPLS TE-FRR ConfigurationTo verify the MPLS TE-FRR configuration, use the show commands given below:

• show mpls traffic-eng tunnels brief• show ip rsvp sender detail• show mpls traffic-eng fast-reroute database• show mpls traffic-eng tunnels backup• show ip rsvp reservation detail

For more information on the above show commands, see:http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-frr-node-prot.html

Note


MPLS Traffic Engineering - Fast Reroute Link ProtectionEnabling BFD Triggered FRR on a Router

http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-frr-node-prot.html#GUID-302A02C6-080E-4390-AE39-8516410313DE

Use the following command to verify whether the backup tunnels are up.

Router# show mpls traffic-eng tunnels briefSignalling Summary:

LSP Tunnels Process: runningRSVP Process: runningForwarding: enabledPeriodic reoptimization: every 3600 seconds, next in 1706 seconds

TUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROTRouter_t1 10.112.0.12 - PO4/0/1 up/upRouter_t2 10.112.0.12 - unknown up/downRouter_t3 10.112.0.12 - unknown admin-downRouter_t1000 10.110.0.10 - unknown up/downRouter_t2000 10.110.0.10 - PO4/0/1 up/upDisplayed 5 (of 5) heads, 0 (of 0) midpoints, 0 (of 0) tails

Use the following command to verify whether the LSPs are protected by the appropriate backup tunnels.

Router# show ip rsvp sender detailPATH:Tun Dest: 10.10.0.6 Tun ID: 100 Ext Tun ID: 10.10.0.1Tun Sender: 10.10.0.1 LSP ID: 31Path refreshes:arriving: from PHOP 10.10.7.1 on Et0/0 every 30000 msecsSession Attr:Setup Prio: 7, Holding Prio: 7Flags: (0x7) Local Prot desired, Label Recording, SE Stylesession Name: R1_t100ERO: (incoming)10.10.7.2 (Strict IPv4 Prefix, 8 bytes, /32)10.10.0.6 (Strict IPv4 Prefix, 8 bytes, /32)RRO:10.10.7.1/32, Flags:0x0 (No Local Protection)10.10.4.1/32, Flags:0x9 (Local Prot Avail/to NNHOP) !Available to NNHOP10.10.1.1/32, Flags:0x0 (No Local Protection)

Traffic params - Rate: 10K bits/sec, Max. burst: 1K bytesMin Policed Unit: 0 bytes, Max Pkt Size 4294967295 bytes

Fast-Reroute Backup info:Inbound FRR: Not activeOutbound FRR: No backup tunnel selected

Path ID handle: 50000416.Incoming policy: Accepted. Policy source(s): MPLS/TEStatus: Proxy-terminated

Use the following command to verify whether the LSPs are protected.

Router# show mpls traffic-eng fast-reroute databaseTunnel head end item frr information:Protected Tunnel In-label intf/label FRR intf/label StatusTunne1l0 Tun pos5/0:Untagged Tu0:12304 readyPrefix item frr information:Prefix Tunnel In-label Out intf/label FRR intf/label Status10.0.0.11/32 Tu110 Tun hd pos5/0:Untagged Tu0:12304 readyLSP midpoint frr information:LSP identifier In-label Out intf/label FRR intf/label Status10.0.0.12 1 [459] 16 pos0/1:17 Tu2000:19 ready

Use the following command to verify the backup tunnel information.

Router# show mpls traffic-eng tunnels backupRouter_t578LSP Head, Tunnel578, Admin: up, Oper: up


MPLS Traffic Engineering - Fast Reroute Link ProtectionVerifying MPLS TE-FRR Configuration

Src 10.55.55.55, Dest 10.88.88.88, Instance 1Fast Reroute Backup Provided:Protected i/fs: PO1/0, PO1/1, PO3/3Protected lsps: 1Backup BW: any pool unlimited; inuse: 100 kbps

Router_t5710LSP Head, Tunnel5710, Admin: admin-down, Oper: downSrc 10.55.55.55, Dest 10.7.7.7, Instance 0Fast Reroute Backup Provided:Protected i/fs: PO1/1Protected lsps: 0Backup BW: any pool unlimited; inuse: 0 kbps

Router_t5711LSP Head, Tunnel5711, Admin up, Oper: upSrc 10.55.55.55,, Dest 10.7.7.7, Instance 1Fast Reroute Backup Provided:Protected i/fs: PO1/0Protected lsps: 2Backup BW: any pool unlimited; inuse: 6010 kbps

Use the following command to verify the reservation detail.

Router# show ip rsvp reservation detailReservation:Tun Dest: 10.1.1.1 Tun ID: 1 Ext Tun ID: 172.16.1.1Tun Sender: 172.16.1.1 LSP ID: 104Next Hop: 172.17.1.2 on POS1/0Label: 18 (outgoing)Reservation Style is Shared-Explicit, QoS Service is Controlled-LoadAverage Bitrate is 0 bits/sec, Maximum Burst is 1K bytesMin Policed Unit: 0 bytes, Max Pkt Size: 0 bytesRRO:172.18.1.1/32, Flags:0x1 (Local Prot Avail/to NHOP)Label subobject: Flags 0x1, C-Type 1, Label 18

172.19.1.1/32, Flags:0x0 (Local Prot Avail/In Use/Has BW/to NHOP)Label subobject: Flags 0x1, C-Type 1, Label 16

172.19.1.2/32, Flags:0x0 (No Local Protection)Label subobject: Flags 0x1, C-Type 1, Label 0

Resv ID handle: CD000404.Policy: Accepted. Policy source(s): MPLS/TE

Verifying Primary One-hop Auto-TunnelsTo verify the configuration of primary one-hop auto-tunnels, use the show commands as shown in the followingexamples.

Router# show ip rsvp fast-reroutePrimary Protect BW BackupTunnel I/F BPS:Type Tunnel:Label State Level Type------ ------- -------- ------------- ------ ----- ------R3-PRP_t0 PO3/1 0:G Tu1000:24 Ready any-unl NhopRouter# show ip interface briefInterface IP-Address OK? Method Status ProtocolPOS2/0 10.0.0.14 YES NVRAM down downPOS2/1 10.0.0.49 YES NVRAM up upPOS2/2 10.0.0.45 YES NVRAM up upPOS2/3 10.0.0.57 YES NVRAM administratively down downPOS3/0 10.0.0.18 YES NVRAM down downPOS3/1 10.0.0.33 YES NVRAM up upPOS3/2 unassigned YES NVRAM administratively down downPOS3/3 unassigned YES NVRAM administratively down down


MPLS Traffic Engineering - Fast Reroute Link ProtectionVerifying Primary One-hop Auto-Tunnels

GigabitEthernet4/0 10.0.0.37 YES NVRAM up upGigabitEthernet4/1 unassigned YES NVRAM administratively down downGigabitEthernet4/2 unassigned YES NVRAM administratively down downLoopback0 10.0.3.1 YES NVRAM up upTunnel0 10.0.3.1 YES unset up upTunnel65436 10.0.3.1 YES unset up upEthernet0 10.3.38.3 YES NVRAM up upEthernet1 unassigned YES NVRAM administratively down down

Verifying Backup Auto-TunnelsTo verify the configuration of backup auto-tunnels, use the show commands as shown in the followingexamples.

Router# show ip rsvp fast-reroutePrimary Protect BW BackupTunnel I/F BPS:Type Tunnel:Label State Level Type------ ------- ------- ------------ ------ ----- ----R3-PRP_t0 PO3/1 0:G None None NoneRouter# show ip interface briefInterface IP-Address OK? Method Status ProtocolPOS2/0 10.0.0.14 YES NVRAM down downPOS2/1 10.0.0.49 YES NVRAM up upPOS2/2 10.0.0.45 YES NVRAM up upPOS2/3 10.0.0.57 YES NVRAM administratively down downPOS3/0 10.0.0.18 YES NVRAM down downPOS3/1 10.0.0.33 YES NVRAM up upPOS3/2 unassigned YES NVRAM administratively down downPOS3/3 unassigned YES NVRAM administratively down downGigabitEthernet4/0 10.0.0.37 YES NVRAM up upGigabitEthernet4/1 unassigned YES NVRAM administratively down downGigabitEthernet4/2 unassigned YES NVRAM administratively down downLoopback0 10.0.3.1 YES NVRAM up upTunnel0 10.0.3.1 YES unset up upTunnel65436 10.0.3.1 YES unset up upTunnel65437 10.0.3.1 YES unset up upEthernet0 10.3.38.3 YES NVRAM up upEthernet1 unassigned YES NVRAM administratively down downRouter# show mpls traffic-eng tunnels backupRouter_t578LSP Head, Tunnel578, Admin: up, Oper: upSrc 10.55.55.55, Dest 10.88.88.88, Instance 1Fast Reroute Backup Provided:Protected i/fs: PO1/0, PO1/1, PO3/3Protected lsps: 1Backup BW: any pool unlimited; inuse: 100 kbps


Router_t5711LSP Head, Tunnel5711, Admin up, Oper: upSrc 10.55.55.55,, Dest 10.7.7.7, Instance 1Fast Reroute Backup Provided:Protected i/fs: PO1/0Protected lsps: 2Backup BW: any pool unlimited; inuse: 6010 kbps


MPLS Traffic Engineering - Fast Reroute Link ProtectionVerifying Backup Auto-Tunnels

Verifying BFD Triggered FRR ConfigurationTo verify the configuration of BFD triggered FRR, use the show commands as shown in the followingexamples.

• show mpls traffic-eng tunnels brief• show ip rsvp sender detail• show mpls traffic-eng fast-reroute database• show mpls traffic-eng tunnels backup• show ip rsvp reservation detail• show ip rsvp hello• show ip rsvp interface detail• show ip rsvp hello bfd nbr• show ip rsvp hello bfd nbr detail• show ip rsvp hello bfd nbr summary

For more information on the above show commands, see:http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-bfd-frr.html

Note

Use the following command to verify whether or not the backup tunnels are up:

Router# show mpls traffic-eng tunnels briefSignalling Summary:

LSP Tunnels Process: runningRSVP Process: runningForwarding: enabledPeriodic reoptimization: every 3600 seconds, next in 1706 seconds

TUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROTRouter_t1 10.112.0.12 - Gi4/0/1 up/upRouter_t2 10.112.0.12 - unknown up/downRouter_t3 10.112.0.12 - unknown admin-downRouter_t1000 10.110.0.10 - unknown up/downRouter_t2000 10.110.0.10 - Gi4/0/1 up/upDisplayed 5 (of 5) heads, 0 (of 0) midpoints, 0 (of 0) tails

Use the following command to verify whether the LSPs are protected by the appropriate backup tunnels.

Router# show ip rsvp sender detailPATH:Tun Dest: 10.10.0.6 Tun ID: 100 Ext Tun ID: 10.10.0.1Tun Sender: 10.10.0.1 LSP ID: 31Path refreshes:arriving: from PHOP 10.10.7.1 on Et0/0 every 30000 msecsSession Attr:Setup Prio: 7, Holding Prio: 7Flags: (0x7) Local Prot desired, Label Recording, SE Stylesession Name: R1_t100ERO: (incoming)10.10.7.2 (Strict IPv4 Prefix, 8 bytes, /32)10.10.0.6 (Strict IPv4 Prefix, 8 bytes, /32)RRO:10.10.7.1/32, Flags:0x0 (No Local Protection)10.10.4.1/32, Flags:0x9 (Local Prot Avail/to NNHOP) !Available to NNHOP10.10.1.1/32, Flags:0x0 (No Local Protection)

Traffic params - Rate: 10K bits/sec, Max. burst: 1K bytes


MPLS Traffic Engineering - Fast Reroute Link ProtectionVerifying BFD Triggered FRR Configuration

http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-bfd-frr.html#GUID-0C7C02CD-6D9F-480F-83D5-1F816E08D71E

Min Policed Unit: 0 bytes, Max Pkt Size 4294967295 bytesFast-Reroute Backup info:Inbound FRR: Not activeOutbound FRR: No backup tunnel selected

Path ID handle: 50000416.Incoming policy: Accepted. Policy source(s): MPLS/TEStatus: Proxy-terminated

Use the following command to verify whether the LSPs are protected:

Router# show mpls traffic-eng fast-reroute databaseTunnel head end item frr information:Protected tunnel In-label Out intf/label FRR intf/label StatusTunnel500 Tun hd AT4/0.100:Untagg Tu501:20 readyPrefix item frr information:Prefix Tunnel In-label Out intf/label FRR intf/label Status10.0.0.8/32 Tu500 18 AT4/0.100:Pop ta Tu501:20 ready10.0.8.8/32 Tu500 19 AT4/0.100:Untagg Tu501:20 ready10.8.9.0/24 Tu500 22 AT4/0.100:Untagg Tu501:20 readyLSP midpoint item frr information:LSP identifier In-label Out intf/label FRR intf/label Status

Use the following command to verify the backup tunnel information.

Router# show mpls traffic-eng tunnels backupRouter_t578LSP Head, Tunnel578, Admin: up, Oper: upSrc 10.55.55.55, Dest 10.88.88.88, Instance 1Fast Reroute Backup Provided:Protected i/fs: PO1/0, PO1/1, PO3/3Protected lsps: 1Backup BW: any pool unlimited; inuse: 100 kbps


Router_t5711LSP Head, Tunnel5711, Admin: up, Oper: upSrc 10.55.55.55, Dest 10.7.7.7, Instance 1Fast Reroute Backup Provided:Protected i/fs: PO1/0Protected lsps: 2Backup BW: any pool unlimited; inuse: 6010 kbps

Use the following command to verify detailed RSVP-related receiver information currently in the database.

Router# show ip rsvp reservation detailReservation:Tun Dest: 10.1.1.1 Tun ID: 1 Ext Tun ID: 10.1.1.1Tun Sender: 10.1.1.1 LSP ID: 104Next Hop: 10.1.1.2 on Gi1/0Label: 18 (outgoing)Reservation Style is Shared-Explicit, QoS Service is Controlled-LoadAverage Bitrate is 0 bits/sec, Maximum Burst is 1K bytesMin Policed Unit: 0 bytes, Max Pkt Size: 0 bytesRRO:10.1.1.1/32, Flags:0x1 (Local Prot Avail/to NHOP)Label subobject: Flags 0x1, C-Type 1, Label 18

10.1.1.1/32, Flags:0x0 (Local Prot Avail/In Use/Has BW/to NHOP)Label subobject: Flags 0x1, C-Type 1, Label 16



10.1.1.2/32, Flags:0x0 (No Local Protection)Label subobject: Flags 0x1, C-Type 1, Label 0

Resv ID handle: CD000404.Policy: Accepted. Policy source(s): MPLS/TE

Use this command to display hello status and statistics for FRR, reroute (hello state timer), and graceful restart.

Router# show ip rsvp helloHello:RSVP Hello for Fast-Reroute/Reroute: EnabledStatistics: DisabledBFD for Fast-Reroute/Reroute: EnabledRSVP Hello for Graceful Restart: Disabled

Use this command to display the interface configuration for Hello.

Router# show ip rsvp interface detailGi9/47:RSVP: EnabledInterface State: UpBandwidth:Curr allocated: 0 bits/secMax. allowed (total): 0 bits/secMax. allowed (per flow): 0 bits/secMax. allowed for LSP tunnels using sub-pools (pool 1): 0 bits/secSet aside by policy (total): 0 bits/secSignalling:DSCP value used in RSVP msgs: 0x3FNumber of refresh intervals to enforce blockade state: 4Authentication: disabledKey chain: <none>Type: md5Window size: 1Challenge: disabledFRR Extension:Backup Path: Configured (or "Not Configured")BFD Extension:State: DisabledInterval: Not ConfiguredRSVP Hello Extension:State: DisabledRefresh Interval: FRR: 200 , Reroute: 2000Missed Acks: FRR: 4 , Reroute: 4DSCP in HELLOs: FRR: 0x30 , Reroute: 0x30

Use this command to display information about all MPLS traffic engineering link and node protected neighborsthat use the BFD protocol.

Router# show ip rsvp hello bfd nbrClient Neighbor I/F State LostCnt LSPsFRR 10.0.0.6 Gi9/47 Up 0 1

Use this command to display detailed information about all MPLS traffic engineering link and node protectedneighbors that use the BFD protocol:

Router# show ip rsvp hello bfd nbr detailHello Client NeighborsRemote addr 10.0.0.6, Local addr 10.0.0.7Type: ActiveI/F: Gi9/47State: Up (for 00:09:41)Clients: FRR



LSPs protecting: 1 (frr: 1, hst upstream: 0 hst downstream: 0)Communication with neighbor lost: 0

Use this command to display summarized information about all MPLS traffic engineering link and nodeprotected neighbors that use the BFD protocol.

Router# show ip rsvp hello bfd nbr summaryClient Neighbor I/F State LostCnt LSPsFRR 10.0.0.6 Gi9/47 Up 0 1

Configuration ExamplesThis section provides sample configuration examples for IPv6 over MPLS: 6PE and 6VPE feature on therouter.

Example: Configuring MPLS TE-FRRFor a sample configuration of MPLS TE-FRR, see:

http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-frr-node-prot.html

Example: Configuring Primary One-hop Auto-TunnelsFor a sample configuration of primary one-hop auto-tunnels, see:

http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-autotunnel.html

Example: Configuring Backup Auto-TunnelsFor a sample configuration of backup auto-tunnels, see:

http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-autotunnel.html

Example: Configuring BFD Triggered FRRFor a sample configuration of BFD triggered FRR, see:

http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-bfd-frr.html

Additional ReferencesThe following sections provide references related to IPv6 Multicast feature.

Related Documents

Document TitleRelated Topic

Cisco IOS Master Commands List, All ReleasesCisco IOS Commands


MPLS Traffic Engineering - Fast Reroute Link ProtectionConfiguration Examples

http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-frr-node-prot.html#GUID-9A7E7EDE-0FC0-4E96-A2EE-8D2C7974BE5E

http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-autotunnel.html#GUID-57EF0CCB-1270-4DCB-8745-3BB56D5E42B6

http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-autotunnel.html#GUID-57EF0CCB-1270-4DCB-8745-3BB56D5E42B6

http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-bfd-frr.html#GUID-5B58FE3D-CB6E-4765-ACB3-97DC1A2C9A97

http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html

Document TitleRelated Topic

Router Commands

Standards and RFCs

TitleStandards/RFCs

Multicast Listener Discovery (MLD) for IPv6RFC 2710

MIBs

MIBs LinkMIB

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use CiscoMIB Locator found at the following URL:

http://www.cisco.com/go/mibs

None

Technical Assistance

LinkDescription

http://www.cisco.com/techsupportThe Cisco Technical Support website contains thousands of pages ofsearchable technical content, including links to products, technologies,solutions, technical tips, and tools. Registered Cisco.com users can login from this page to access even more content.

Feature Information for MPLS Traffic Engineering - Fast RerouteLink Protection

Table 1: Feature Information for MPLS Traffic Engineering - Fast Reroute Link Protection, on page 24 liststhe features in this module and provides links to specific configuration information.

Use Cisco Feature Navigator to find information about platform support and software image support. CiscoFeature Navigator enables you to determine which software images support a specific software release, featureset, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn . An account onCisco.com is not required.

Table 1: Feature Information for MPLS Traffic Engineering - Fast Reroute Link Protection, on page 24 listsonly the software release that introduced support for a given feature in a given software release train. Unlessnoted otherwise, subsequent releases of that software release train also support that feature.

Note


MPLS Traffic Engineering - Fast Reroute Link ProtectionFeature Information for MPLS Traffic Engineering - Fast Reroute Link Protection

http://www.cisco.com/go/mibs

http://www.cisco.com/techsupport

http://tools.cisco.com/ITDIT/CFN/

Table 1: Feature Information for MPLS Traffic Engineering - Fast Reroute Link Protection

Feature InformationReleasesFeature Name

This feature was introduced on the Cisco ASR 901 routers.

The following sections provide information about this feature:

15.2(2)SNGMPLS Traffic Engineering



15.2(2)SNGBFD-triggered Fast Reroute



15.3(2)STE-FRR for EoMPLS


MPLS Traffic Engineering - Fast Reroute Link ProtectionFeature Information for MPLS Traffic Engineering - Fast Reroute Link Protection