MPLS Traffic Engineering - Fast Reroute Link Protection 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 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 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 not required. Prerequisites for MPLS Traffic Engineering - Fast Reroute Link Protection • Cisco IOS Release 15.2(2)SNG or a later release that supports the MPLS TE-FRR link protection feature must 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 Protection 1
24
Embed
MPLS Traffic Engineering - Fast Reroute Link Protection...Tunne1l0 Tun pos5/0:Untagged Tu0:12304 ready Prefixitemfrrinformation: Prefix Tunnel In-label Outintf/label FRRintf/label
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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
• 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 Protection2
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 Protection3
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 Protection4
MPLS Traffic Engineering - Fast Reroute Link ProtectionFast Reroute
PurposeCommand or Action
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:
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 Protection6
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
PurposeCommand or Action
Enables the privileged EXEC mode.pw-classStep 1
Example: • Enter your password if prompted.
Router> enable
Enters the global configuration mode.auto terminal
Example:
Step 2
Router# configure terminal
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 Protection7
MPLS Traffic Engineering - Fast Reroute Link ProtectionEnabling MPLS TE-FRR for EoMPLS on an Interface
PurposeCommand or Action
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.
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:
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 Protection11
MPLS Traffic Engineering - Fast Reroute Link ProtectionConfiguring Primary One-hop Auto-Tunnels
Configuring Backup Auto-TunnelsTo configure backup auto-tunnels, perform the following steps.
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 Protection12
MPLS Traffic Engineering - Fast Reroute Link ProtectionConfiguring Backup Auto-Tunnels
PurposeCommand or Action
Configures how frequently a timer scans the backupautotunnels and remove tunnels that are not being used.
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
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
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
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 Protection14
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
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
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 Protection15
MPLS Traffic Engineering - Fast Reroute Link ProtectionEnabling BFD Triggered FRR on a Router
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 Protection17
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_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
MPLS Traffic Engineering - Fast Reroute Link Protection18
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)
MPLS Traffic Engineering - Fast Reroute Link Protection20
MPLS Traffic Engineering - Fast Reroute Link ProtectionVerifying BFD Triggered FRR Configuration
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
MPLS Traffic Engineering - Fast Reroute Link Protection21
MPLS Traffic Engineering - Fast Reroute Link ProtectionVerifying BFD Triggered FRR Configuration
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 Protection23
MPLS Traffic Engineering - Fast Reroute Link ProtectionFeature Information for MPLS Traffic Engineering - Fast Reroute Link Protection