Remote Loop-Free Alternate - Fast Reroute - cisco.com · Remote Loop-Free Alternate - Fast Reroute...

Remote Loop-Free Alternate - Fast Reroute

This feature module describes the Remote Loop-free Alternate (LFA) - Fast Reroute (FRR) feature that usesa backup route, computed using dynamic routing protocol during a node failure, to avoid traffic loss.

• Finding Feature Information, page 1

• Prerequisites for Remote Loop-Free Alternate - Fast Reroute, page 1

• Restrictions for Remote Loop-Free Alternate - Fast Reroute, page 2

• Feature Overview, page 3

• How to Configure Remote Loop-Free Alternate - Fast Reroute, page 5

• Configuration Examples for Remote LFA-FRR, page 36

• Additional References, page 38

• Feature Information for Remote Loop-Free Alternate - Fast Reroute, page 40

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 Remote Loop-Free Alternate - Fast Reroute• Cisco IOS Release 15.2(2)SNI or a later release that supports the Remote LFA-FRR feature must beinstalled previously on the Cisco ASR 901 Series Aggregation Services Router.

• You should enable the following commands at the global configuration mode before configuring theRemote LFA-FRR feature.

Cisco ASR 901S Series Aggregation Services Router Software Configuration Guide OL-30498-03 1

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

asr901-platf-frr enable•

• mpls label protocol ldp

• mpls ldp router-id loopback-id force

• mpls ldp discovery targeted-hello accept

• no l3-over-l2 flush buffers

• Your network must support the following Cisco IOS features before you can enable fast reroute linkprotection:

• 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)

• You should use throttle interior gateway protocol (IGP) timers for IS-IS and OSPF protocols.

Restrictions for Remote Loop-Free Alternate - Fast Reroute• 4-label push is not supported. Due to this limitation, Labeled BGP access (RFC 3107) with RemoteLFA-FRR/TE-FRR is not supported, if it exceeds three labels. Four label push is observed on L2VPNand L3VPN scenarios where multihop tunnel terminates before the destination. The four labels are givenbelow:

• Backup-Repair Label

• Tunnel Label

• MPLS LDP Label

• VC or VRF Label

• Since FRR is a software based solution on the Cisco ASR 901 router, you should keep the number ofprefixes, label-entries, and pseudowires to a minimum to obtain good convergence numbers.

• Remote LFA-FRR is not supported on layer 3 over layer 2 deployments. Disable this configuration usingthe no l3-over-l2 flush buffers command before configuring Remote LFA-FRR.

• Ethernet over Multiprotocol Label Switching (EoMPLS) redundancy is not useful unless you have dualhome pseudowire and a protecting backup pseudowire egress link with FRR.

• Psuedowire redundancy over RLFA is supported effective with Cisco IOS Realease 15.4(1)S.

• TDM psuedowires over RLFA is supported effective with Cisco IOS Realease 15.3(3)S.

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

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

Cisco ASR 901S Series Aggregation Services Router Software Configuration Guide2 OL-30498-03

Remote Loop-Free Alternate - Fast RerouteRestrictions for Remote Loop-Free Alternate - Fast Reroute

• The Border Gateway Protocol (BGP) Prefix-Independent Convergence (PIC) edge is not supported.Specifically, the bgp additional-paths install command is not supported.

• If the network port is an LAG interface (etherchannel), you must use BFD over SVI to achieve FRRconvergence numbers.

• If the LAG interface is used either on access side or towards the core, you should shutdown the interfacebefore removing it.

Feature OverviewThe LFA-FRR is a mechanism that provides local protection for unicast traffic in IP, MPLS, EoMPLS, InverseMultiplexing over ATM (IMA) over MPLS, Circuit Emulation Service over Packet Switched Network(CESoPSN) over MPLS, and Structure-Agnostic Time Division Multiplexing over Packet (SAToP) overMPLS networks. However, some topologies (such as the ring topology) require protection that is not affordedby LFA-FRR alone. The Remote LFA-FRR feature is useful in such situations.

The Remote LFA-FRR extends the basic behavior of LFA-FRR to any topology. It forwards the traffic arounda failed node to a remote LFA that is more than one hop away.

In Remote LFA-FRR, a node dynamically computes its LFA node. After determining the alternate node (whichis non-directly connected), the node automatically establishes a directed Label Distribution Protocol (LDP)session to the alternate node. The directed LDP session exchanges labels for the particular forward errorcorrection (FEC).

When the link fails, the node uses label stacking to tunnel the traffic to the remote LFA node, to forward thetraffic to the destination. All the label exchanges and tunneling to remote LFA node are dynamic in natureand pre-provisioning is not required.

The following figure shows the repair path that is automatically created by the Remote LFA-FRR feature tobypass looping. In this figure, the traffic is flowing between CE nodes (R1 to R7) through the PE nodes(protected link - R2 and R3). When the PE node fails, the repair path (R2 - R4- R5 - R6 - R3) is used to routethe traffic between CE nodes.

Figure 1: Remote LFA-FRR Link Protection


Remote Loop-Free Alternate - Fast RerouteFeature Overview

P nodesR6 - R5 - R4CE nodesR1 and R7

Fast Reroute Repair PathR2 - R4- R5 - R6 - R3PE nodes (protected link)R2 and R3

Benefits of Remote LFA-FRR• Simplifies operation with minimum configuration

• Eliminates additional traffic engineering (TE) protocols.

• Computes PQ node dynamically without any manual provisioning (PQ node is a member of both theextended P-space and the Q-space. P-space is the set of routers reachable from a specific router withoutany path (including equal cost path splits) transiting the protected link. Q-space is the set of routers fromwhich a specific router can be reached without any path, including equal cost path splits, transiting theprotected link.)

• Prevents hair pinning that occurs in TE-FRR

• Remote LFA-FRR supports the following:

◦Basic LFA-FRR (supported for OSPF and IS-IS protocols)

◦IP, L2VPN, and L3VPN

◦BFD triggered MPLS TE-FRR. Supports BFD sessions with 50ms interval.

Avoiding Traffic DropsTraffic drops can occur due to congestion as a result of formation of micro loops during link recovery. Toavoid traffic drops, the tunnel-buffer port command is introduced to set the hardware buffer values on theport. For more details on this command, see the Cisco ASR 901 Series Aggregation Services Router CommandReference guide.

Pseudowire Redundancy over FRRPseudowire redundancy enables you to configure a pseudowire as a backup for the primary pseudowire.Whenthe primary pseudowire fails, the services are switched to the backup pseudowire. Effective with Cisco IOSRelease 15.4(1)S, Pseudowire Redundancy over FRR feature is supported.

You can enable FRR (TE-FRR and RLFA) in the network for both active and standby pseudowires separately.The primary and backup paths for these virtual circuits (VCs) may or may not overlap. This feature supportslink failures through FRR and node failures through PW redundancy. It supports up to 500 primary and backuppseudowires.


Remote Loop-Free Alternate - Fast RerouteBenefits of Remote LFA-FRR

http://www.cisco.com/en/US/docs/wireless/asr_901/Command/Reference/Cmdref_asr901.html

http://www.cisco.com/en/US/docs/wireless/asr_901/Command/Reference/Cmdref_asr901.html

The following figure shows the pseudowire redundancy over FRR implementation.

Figure 2: Pseudowire Redundancy Over FRR

Conditions for Switchover• If the primary path to the peer node goes down for active VC, the FRR changes to backup and the VCremains active.

• A VC switchover does not occur unless both primary and backup paths are down for active VC.

• The standby VC does not go down until both primary and backup paths to the standby peer are down.

• A VC switchover occurs when the peer node of the active VC reboots or when the access circuit goesdown.

• If the peer node of active VC reboots when the standby VC is in backup state, the VC switchover occursimmediately and the standby VC becomes active.

How to Configure Remote Loop-Free Alternate - Fast Reroute

Effective with Cisco IOS Release 15.3(3)S, the Remote LFA-FRR feature is supported on CESoPSN,SAToP, and ATM/IMA.

Note

• Effective with Cisco IOS Release 15.4(1)S, the Pseudowire Redundancy over FRR feature is supported.

This section describes how to configure Remote LFA-FRR feature:

Configuring Remote LFA-FRR for IS-ISTo configure Remote LFA-FRR for the IS-IS routing process, complete the following steps:


Remote Loop-Free Alternate - Fast RerouteHow to Configure Remote Loop-Free Alternate - Fast Reroute

SUMMARY STEPS

1. enable2. configure terminal3. interface type number4. no negotiation auto5. service instance id ethernet6. encapsulation dot1q vlan-id7. rewrite ingress tag pop 1 symmetric8. bridge-domain bridge-domain-id9. interface vlan bridge-domain-id10. ip address ip-address11. ip router isis12. mpls ip13. isis network point-to-point14. exit15. router isis16. fast-reroute per-prefix {level-1 | level-2} {all | route-map route-map-name}17. fast-reroute remote-lfa {level-1 | level-2} mpls-ldp [maximum-metric metric-value]18. mpls ldp sync19. mpls ldp igp sync holddown milliseconds

DETAILED STEPS

PurposeCommand or Action

Enables privileged EXEC mode.enableStep 1

Example:

Router> enable

• Enter your password if prompted.

Enters global configuration mode.configure terminal

Example:

Router# configure terminal

Step 2

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

interface type number

Example:

Router(config)# interface vlan 40

Step 3


Remote Loop-Free Alternate - Fast RerouteConfiguring Remote LFA-FRR for IS-IS


Disables automatic negotiation.no negotiation auto

Example:

Router(config-if)# no negotiation auto

Step 4

Configures an Ethernet service instance on an interface.service instance id ethernetStep 5

Example:

Router(config-if)# service instance 7ethernet

• id—Integer that uniquely identifies a service instance on aninterface.

Enables IEEE 802.1Q encapsulation of traffic on a specified interfacein a VLAN.

encapsulation dot1q vlan-id

Example:

Router(config-if)# encapsulation dot1q7

Step 6

• vlan-id—Virtual LAN identifier.

Specifies the encapsulation adjustment to be performed on a frameingressing a service instance.

rewrite ingress tag pop 1 symmetric

Example:

Router(config-if)# rewrite ingress tagpop 1 symmetric

Step 7

• pop—Removes a tag from a packet.

• 1—Specifies the outermost tag for removal from a packet.

• symmetric—Indicates a reciprocal adjustment to be done inthe egress direction. For example, if the ingress pops a tag, theegress pushes a tag and if the ingress pushes a tag, the egresspops a tag.

Enables RFC 1483 ATM bridging or RFC 1490 Frame Relaybridging to map a bridged VLAN to an ATM permanent virtualcircuit (PVC) or Frame Relay data-link connection identifier (DLCI).

bridge-domain bridge-domain-id

Example:

Router(config-if)# bridge-domain 7

Step 8

• bridge-domain-id—Bridge domain identifier.

Configures an Ethernet interface to create or access a dynamic SwitchVirtual Interface (SVI).

interface vlan bridge-domain-id

Example:

Router(config-if)# interface vlan 7

Step 9

Specifies an IP address for the specified interface.ip address ip-address

Example:

Router(config-if)# ip address 7.7.7.1255.255.255.0

Step 10




Configures an IS-IS routing process for an IP on an interface.ip router isis

Example:

Router(config-if)# ip router isis

Step 11

Enables MPLS forwarding of IPv4 packets along normally routedpaths for a particular interface.

mpls ip

Example:

Router(config-if)# mpls ip

Step 12

Configures a network of two networking devices that use theintegrated IS-IS routing protocol to function as a point-to-point link.

isis network point-to-point

Example:

Router(config-if)# isis networkpoint-to-point

Step 13

Exits the interface configuration mode and enters the globalconfiguration mode.

exit

Example:

Router(config-if)# exit

Step 14

Enables the IS-IS routing protocol and enters the router configurationmode.

router isis

Example:

Router(config)# router isis

Step 15

Configures an FRR path that redirects traffic to a remote LFA tunnelfor either level 1 or level 2 packets.

fast-reroute per-prefix {level-1 | level-2} {all| route-map route-map-name}

Step 16

Example:

Router(config-router)# fast-rerouteper-prefix level-1 all

• level-1—Enables per-prefix FRR of level 1 packets.


• all—Enables FRR of all primary paths.

• route-map—Specifies the route map for selecting primarypaths for protection.

• route-map-name—Route map name.

Configures an FRR path that redirects traffic to a remote LFA tunnel.fast-reroute remote-lfa {level-1 | level-2}mpls-ldp [maximum-metric metric-value]

Step 17

• level-1—Enables LFA-FRR of level 1 packets.

Example:

Router(config-router)# fast-rerouteremote-lfa level-1 mpls-ldp


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

• maximum-metric—Specifies the route map for selectingprimary paths for protection.

• metric-value—Metric value.




Enables MPLS LDP synchronization on interfaces for an IS-ISprocess.

mpls ldp sync

Example:

Router(config-router)# mpls ldp sync

Step 18

Specifies how long an Interior Gateway Protocol (IGP) should waitfor Label Distribution Protocol (LDP) synchronization to beachieved.

mpls ldp igp sync holddown milliseconds

Example:

Router(config)# mpls ldp igp syncholddown 1000

Step 19

• milliseconds—Peer host name or IP address.

Configuring Remote LFA-FRR for OSPFTo configure Remote LFA-FRR for the OSPF routing process, complete the following steps:

SUMMARY STEPS

1. enable2. configure terminal3. interface type number4. no negotiation auto5. service instance id ethernet6. encapsulation dot1q vlan-id7. rewrite ingress tag pop 1 symmetric8. bridge-domain bridge-domain-id9. interface vlan bridge-domain-id10. ip address ip-address11. exit12. router ospf13. fast-reroute per-prefix enable [area area-id]14. fast-reroute per-prefix remote-lfa [area area-id]15. mpls ldp sync

DETAILED STEPS




Remote Loop-Free Alternate - Fast RerouteConfiguring Remote LFA-FRR for OSPF


Example:

Router> enable



Example:


Step 2



Example:


Step 3


Example:


Step 4


Example:



Enables IEEE 802.1Q encapsulation of traffic on a specifiedinterface in a VLAN.


Example:

Router(config-if)# encapsulation dot1q 7

Step 6




Example:

Router(config-if)# rewrite ingress tagpop 1 symmetric

Step 7



• symmetric—Indicates a reciprocal adjustment to be done inthe egress direction. For example, if the ingress pops a tag,the egress pushes a tag and if the ingress pushes a tag, theegress pops a tag.

Enables RFC 1483 ATM bridging or RFC 1490 Frame Relaybridging to map a bridged VLAN to an ATM permanent virtual


Example:

Router(config-if)# bridge-domain 7

Step 8

circuit (PVC) or Frame Relay data-link connection identifier(DLCI).





Configures an Ethernet interface to create or access a dynamicSVI.

interface vlan bridge-domain-id

Example:

Router(config-if)# interface vlan 7

Step 9


Example:


Step 10

Exits the interface configuration mode and enters the globalconfiguration mode.

exit

Example:

Router(config-if)# exit

Step 11

Enables the OSPF routing protocol and enters the routerconfiguration mode.

router ospf

Example:

Router(config)# router ospf

Step 12

Configures a per-prefix loop-free alternate (LFA) Fast Reroute(FRR) path that redirects traffic to an alternative next hop otherthan the primary neighbor.

fast-reroute per-prefix enable [area area-id]

Example:

Router(config-router)# fast-rerouteper-prefix enable area 1

Step 13

• area—Specifies the area in which to enable LFA-FRR.

• area-id—OSPF area ID expressed as a decimal value or inIP address format.

Configures a per-prefix LFA FRR path that redirects traffic to aremote LFA area.

fast-reroute per-prefix remote-lfa [area area-id]

Example:

Router(config-router)# fast-rerouteper-prefix remote-lfa area 1

Step 14

Enables MPLS LDP synchronization on interfaces for an OSPFprocess.

mpls ldp sync

Example:


Step 15



Configuring Remote LFA-FRR for Ethernet and TDM Pseudowires

The Remote LFA-FRR feature is supported on the TDM pseudowires from Cisco IOS Realease 15.3(3)Sonwards. The configuration and restrictions for EoMPLS are also applicable to the TDM pseudowires.

Note

During packet loss, SAToP requires one second for convergence and two seconds for recovery.Note

• Configuring Remote LFA-FRR on a Global Interface, on page 12

• Configuring Remote LFA-FRR on a GigabitEthernet Interface, on page 13

• Configuring Remote LFA-FRR on an SVI Interface, on page 15

• Configuring Remote LFA-FRR on IS-IS , on page 16

• Configuring LFA-FRR for EoMPLS , on page 20

• Configuring LFA-FRR for ATM/IMA , on page 22

• Configuring LFA-FRR for CESoPSN , on page 24

• Configuring LFA-FRR for SAToP , on page 27

Configuring Remote LFA-FRR on a Global InterfaceTo configure Remote LFA-FRR on a global interface, complete the following steps:

SUMMARY STEPS

1. enable2. configure terminal3. mpls label protocol ldp4. no l3-over-l2 flush buffers5. asr901-platf-frr enable6. mpls ldp discovery targeted-hello accept

DETAILED STEPS



Example:

Router> enable



Remote Loop-Free Alternate - Fast RerouteConfiguring Remote LFA-FRR for Ethernet and TDM Pseudowires



Example:


Step 2

Specifies that this LDP is the default distribution protocol.mpls label protocol ldp

Example:

Router(config)# mpls label protocol ldp

Step 3

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

Example:

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

Step 4

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

Example:

Router(config)# asr901-platf-frr enable

Step 5

Configures the neighbors from which requests for targetedhello messages may be honored.

mpls ldp discovery targeted-hello accept

Example:

Router(config)# mpls ldp discoverytargeted-hello accept

Step 6

• targeted-hello—Configures the intervals and hold timesfor neighbors that are not directly connected.

• accept—Configures the router to respond to requests fortargeted hello messages from all neighbors.

Configuring Remote LFA-FRR on a GigabitEthernet InterfaceTo configure Remote LFA-FRR on a GigabitEthernet interface, complete the following steps:

SUMMARY STEPS

1. enable2. configure terminal3. interface type number4. no negotiation auto5. service instance id ethernet6. encapsulation dot1q vlan-id7. rewrite ingress tag pop 1 symmetric8. bridge-domain bridge-domain-id



DETAILED STEPS



Example:

Router> enable



Example:


Step 2



Example:


Step 3


Example:


Step 4


Example:



Enables IEEE 802.1Q encapsulation of traffic on a specified interfacein a VLAN.


Example:

Router(config-if-srv)# encapsulationdot1q 7

Step 6




Example:

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

Step 7



• symmetric—Indicates a reciprocal adjustment to be done inthe egress direction. For example, if the ingress pops a tag, theegress pushes a tag and if the ingress pushes a tag, the egresspops a tag.




Enables RFC 1483ATMbridging or RFC 1490 FrameRelay bridgingto map a bridged VLAN to an ATM permanent virtual circuit (PVC)or Frame Relay data-link connection identifier (DLCI).


Example:

Router(config-if-srv)# bridge-domain 7

Step 8


Configuring Remote LFA-FRR on an SVI InterfaceTo configure Remote LFA-FRR on an SVI interface, complete the following steps:

SUMMARY STEPS

1. enable2. configure terminal3. interface type number4. ip address ip-address5. ip router isis6. mpls ip7. isis network point-to-point

DETAILED STEPS



Example:

Router> enable



Example:


Step 2



Example:


Step 3





Example:


Step 4

Configures an IS-IS routing process for an IP on an interface.ip router isis

Example:

Router(config-if)# ip router isis

Step 5

Enables MPLS forwarding of IPv4 packets along normallyrouted paths for a particular interface.

mpls ip

Example:

Router(config-if)# mpls ip

Step 6

Configures a network of two networking devices that use theintegrated IS-IS routing protocol to function as apoint-to-point link.

isis network point-to-point

Example:

Router(config-if)# isis networkpoint-to-point

Step 7

Configuring Remote LFA-FRR on IS-ISTo configure Remote LFA-FRR for the IS-IS routing process, complete the following steps:



SUMMARY STEPS

1. enable2. configure terminal3. router isis4. net net5. is-type level-16. advertise-passive-only7. ispf level-18. fast-flood9. max-lsp-lifetime seconds10. lsp-refresh-interval seconds11. spf-interval [level-1 | level-2] spf-max-wait [spf-initial-wait spf-second-wait]12. prc-interval prc-max-wait [prc-initial-wait prc-second-wait]13. lsp-gen-interval [level-1 | level-2] lsp-max-wait [lsp-initial-wait lsp-second-wait]14. no hello padding15. log-adjacency-changes16. fast-reroute per-prefix {level-1 | level-2} {all | route-map route-map-name}17. fast-reroute remote-lfa {level-1 | level-2} mpls-ldp [maximum-metric metric-value]18. passive-interface interface-type interface-number19. mpls ldp sync

DETAILED STEPS



Example:

Router> enable



Example:


Step 2

Enables the IS-IS routing protocol and enters the router configurationmode.router isis

Example:

Router(config)# router isis

Step 3




Configures an IS-IS network entity table (NET) for the routing process.net net

Example:

Router(config-router)# net49.0001.0002.0001.0001.00

Step 4

Configures the routing level for an instance of the IS-IS routing process.is-type level-1Step 5

Example:

Router(config-router)# is-typelevel-1

• level-1—Router performs only Level 1 (intra-area) routing. Thisrouter learns only about destinations inside its area.

Configures IS-IS to advertise only prefixes that belong to passive interfaces.advertise-passive-only

Example:

Router(config-router)#advertise-passive-only

Step 6

Enables incremental shortest path first (SPF).ispf level-1Step 7

Example:

Router(config-router)# ispf level-1

• level-1—Enables incremental SPF for Level 1 packets only. Thelevel-1 keyword applies only after enabling IS-IS.

When IS-IS incremental SPF is configured on a ring topology,high convergence numbers are observed for random globalprefixes. See CSCue11410 for details.

Note

Fills IS-IS link-state packets (LSPs).fast-flood

Example:

Router(config-router)# fast-flood

Step 8

Configures the maximum link-state packets (LSPs) lifetime.max-lsp-lifetime secondsStep 9

Example:

Router(config-router)#max-lsp-lifetime 65535

• seconds—Maximum LSP lifetime in seconds. The range is from 1 to65535.

Sets the link-state packet (LSP) refresh interval.lsp-refresh-interval secondsStep 10

Example:

Router(config-router)#lsp-refresh-interval 900

• seconds—Interval (in seconds) at which LSPs are refreshed.The rangeis 1 to 65535 seconds. The default value is 900 seconds (15 minutes).

Customizes IS-IS throttling of shortest path first (SPF) calculations.spf-interval [level-1 | level-2] spf-max-wait[spf-initial-wait spf-second-wait]

Step 11

• level-1—(Optional) Apply intervals to Level-1 areas only.

Example:

Router(config-router)# spf-interval5 50 200





• spf-max-wait—Indicates themaximum interval (in seconds) betweentwo consecutive SPF calculations. The range is 1 to 120 seconds. Thedefault is 10 seconds.

• spf-initial-wait—(Optional) Indicates the initial SPF calculation delay(in milliseconds) after a topology change. The range is 1 to 120000milliseconds. The default is 5500 milliseconds (5.5 seconds).

• spf-second-wait—(Optional) Indicates the hold time between the firstand second SPF calculation (inmilliseconds). The range is 1 to 120000milliseconds. The default is 5500 milliseconds (5.5 seconds).

Customizes IS-IS throttling of partial route calculations (PRC).prc-interval prc-max-wait [prc-initial-waitprc-second-wait]

Step 12

• prc-max-wait—Indicates the maximum interval (in seconds) betweentwo consecutive PRC calculations. Value range is 1 to 120 seconds.The default is 5 seconds.Example:

Router(config-router)# prc-interval5 50 200 • prc-initial-wait—(Optional) Indicates the initial PRC calculation

delay (in milliseconds) after a topology change. The range is 1 to120,000 milliseconds. The default is 2000 milliseconds.

• prc-second-wait—(Optional) Indicates the hold time between the firstand second PRC calculation (in milliseconds). The range is 1 to120,000 milliseconds. The default is 5000 milliseconds (5 seconds).

Customizes IS-IS throttling of LSP generation.lsp-gen-interval [level-1 | level-2]lsp-max-wait [lsp-initial-waitlsp-second-wait]

Step 13


Example:

Router(config-router)#lsp-gen-interval 5 50 200


• lsp-max-wait—Indicates themaximum interval (in seconds) betweentwo consecutive occurrences of an LSP being generated. The rangeis 1 to 120 seconds. The default is 5 seconds.

• lsp-initial-wait—(Optional) Indicates the initial LSP generation delay(in milliseconds). The range is 1 to 120,000 milliseconds. The defaultis 50 milliseconds.

• lsp-second-wait—(Optional) Indicates the hold time between the firstand second LSP generation (in milliseconds). The range is 1 to120,000 milliseconds. The default is 5000 milliseconds (5 seconds).

Reenables IS-IS hello padding at the router level.no hello padding

Example:

Router(config-router)# no hellopadding

Step 14




Configures the router to send a syslog message when an OSPF neighborgoes up or down.

log-adjacency-changes

Example:

Router(config-router)#log-adjacency-changes

Step 15

Configures an FRR path that redirects traffic to a remote LFA tunnel foreither level 1 or level 2 packets.

fast-reroute per-prefix {level-1 | level-2}{all | route-map route-map-name}

Step 16

Example:

Router(config-router)# fast-rerouteper-prefix level-1 all



• all—Enables FRR of all primary paths.

• route-map—Specifies the route map for selecting primary paths forprotection.

• route-map-name—Route map name.

Configures an FRR path that redirects traffic to a remote LFA tunnel.fast-reroute remote-lfa {level-1 | level-2}mpls-ldp [maximum-metricmetric-value]

Step 17


Example:

Router(config-router)# fast-rerouteremote-lfa level-1 mpls-ldp


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

• maximum-metric—(Optional)Specifies the maximum metric valuerequired to reach the release node.

• metric-value—Metric value.

Disables sending routing updates on an interface.passive-interface interface-typeinterface-number

Step 18

• interface-type—Interface type.

Example:

Router(config-router)#passive-interface Loopback0

• interface-number—Interface number.

Enables MPLS LDP synchronization on interfaces for an IS-IS process.mpls ldp sync

Example:


Step 19

Configuring LFA-FRR for EoMPLSTo configure LFA-FRR for EoMPLS, complete the following steps:



Effective with Cisco IOS release 15.4(1)S, the EoMPLS Pseudowire Redundancy over FRR feature issupported.

Note

SUMMARY STEPS

1. enable2. configure terminal3. interface type number4. no ip address5. negotiation auto6. service instance id ethernet7. encapsulation dot1q vlan-id8. rewrite ingress tag pop 1 symmetric9. xconnect peer-ip-address vc-id encapsulation mpls10. backup peer peer-ip-address vc-id

DETAILED STEPS



Example:

Router> enable



Example:


Step 2

Specifies an interface type and number and enters interfaceconfiguration mode.


Example:

Router(config)# interfacegigabitethernet 0/1

Step 3

Removes an IP address or disables IP processing.no ip address

Example:

Router(config-if)# no ip address

Step 4

Enables automatic negotiation.negotiation auto

Example:

Router(config-if)# negotiation auto

Step 5





Example:


• id—Integer that uniquely identifies a service instance on aninterface. The value varies by the platform. Range: 1 to4294967295. The identifier need not map to a VLAN and is localin scope to the interface.

Enables IEEE 802.1Q encapsulation of traffic on a specifiedsubinterface in a VLAN.


Example:

Router(config-if-srv)# encapsulationdot1q 101

Step 7

• vlan-id—Virtual LAN identifier. The allowed range is from 1 to4094. For the IEEE 802.1Q-in-QVLANTag Termination feature,the first instance of this argument defines the outer VLAN ID,and the second and subsequent instances define the inner VLANID.



Example:

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

Step 8

Binds an attachment circuit to a pseudowire, and to configure an AnyTransport over MPLS (AToM) static pseudowire.

xconnect peer-ip-address vc-id encapsulationmpls

Step 9

Example:

Router(config-if-srv)# xconnect 10.0.0.44 encapsulation mpls

• peer-ip-address—IP address of the remote provider edge (PE)peer. The remote router ID can be any IP address, as long as itis reachable.

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

• encapsulation—Specifies the tunneling method to encapsulatethe data in the pseudowire.

• mpls—Specifies Multiprotocol Label Switching (MPLS) as thetunneling method.

Specifies a redundant peer for a pseudowire VC.backup peer peer-ip-address vc-idStep 10

Example:

Router(config-if-ether-vc-xconn)# backuppeer 10.0.0.5 4

• peer-ip-address—IP address of the remote peer.

Configuring LFA-FRR for ATM/IMATo configure LFA-FRR for ATM/IMA, complete the following steps:



Effectivewith Cisco IOS release 15.4(1)S, the TDMPseudowire Redundancy over FRR feature is supported.Note

SUMMARY STEPS

1. enable2. configure terminal3. controller {t1 | e1} slot/port4. ima-group ima-group-number5. exit6. interface ATM slot /IMA group-number7. no ip address8. no atm ilmi-keepalive9. pvc vpi/vci l2transport10. xconnect ip-address encapsulation mpls11. backup peer peer-ip-address

DETAILED STEPS



Example:

Router> enable



Example:


Step 2

Selects a T1 or E1 controller and enters controller configurationmode.

controller {t1 | e1} slot/port

Example:

Router(config)# controller e1 0/0

Step 3

Assigns the interface to an IMA group.ima-group ima-group-numberStep 4

Example:

Router(config-controller)# ima-group 2

• ima-group-number—IMA group number.

Exits controller configuration mode and enters global configurationmode.

exit

Example:

Router(config-controller)# exit

Step 5




Configures inverse multiplexing over ATM (IMA) group.interface ATM slot /IMA group-numberStep 6

Example:

Router(config)# interface ATM0/IMA2

• slot—Specifies the slot location of the ATM IMA port adapter.

• group-number—Specifies the group number of the IMA group.

Disables IP address configuration for the physical layer interface.no ip address

Example:


Step 7

Disables the Interim Local Management Interface (ILMI) keepaliveparameters.

no atm ilmi-keepalive

Example:

Router(config-if)# no atm ilmi-keepalive

Step 8

Create or assigns a name to an ATM permanent virtual circuit (PVC),to specify the encapsulation type on an ATM PVC.

pvc vpi/vci l2transport

Example:

Router(config-if)# pvc 90/90 l2transport

Step 9

• vpi—ATM network virtual path identifier (VPI) for this PVC.

• vci—ATM network virtual channel identifier (VCI) for thisPVC.

Binds an attachment circuit to a pseudowire, to configure an AnyTransport over MPLS (AToM) static pseudowire.

xconnect ip-address encapsulation mpls

Example:

Router(config-if-cem)# xconnect 2.2.2.2111 encapsulation mpls

Step 10

• ip-address—IP address of the remote provider edge (PE) peer.The remote router ID can be any IP address, as long as it isreachable.

• encapsulation—Specifies the tunnelingmethod to encapsulatethe data in the pseudowire.

• mpls—Specifies Multiprotocol Label Switching (MPLS) asthe tunneling method.

Specifies a redundant peer for a pseudowire VC.backup peer peer-ip-addressStep 11

Example:

Router(config-if-xconn)# backup peer2.2.2.3 111


Configuring LFA-FRR for CESoPSNTo configure LFA-FRR for CESoPSN, complete the following steps:




SUMMARY STEPS

1. enable2. configure terminal3. controller {t1 | e1} slot/port4. clock source internal5. cem-group group-number timeslots timeslot-range6. description descriptive-name7. exit8. interface cem slot/port9. no ip address10. cem group-number11. xconnect ip-address encapsulation mpls12. backup peer peer-ip-address

DETAILED STEPS



Example:

Router> enable



Example:


Step 2



Example:


Step 3

Sets clocking for individual links.clock source internal

Example:

Router(config-controller)# clock sourceinternal

Step 4

Assigns channels on the T1 or E1 circuit to the circuit emulation(CEM) channel and specific timeslots to the CEM channel.

cem-group group-number timeslotstimeslot-range

Step 5




Example:

Router(config-controller)# cem-group 0timeslots 1-31

• group-number—Channel number to be used for this groupof time slots.

• timeslot—Specifies that a list of time slots is to be used asspecified by the timeslot-range argument.

• timeslot-range—List of the time slots to be included in theCEM channel. The list may include commas and hyphenswith no spaces between the numbers.

Specifies a descriptive name for the controller.description descriptive-name

Example:

Router(config-controller)# description E1CESoPSN example

Step 6

Exits global configuration mode.exit

Example:

Router(config)# exit

Step 7

Defines a CEM channel.interface cem slot/port

Example:

Router(config)# interface CEM 0/0

Step 8


Example:

Router(config-cem)# no ip address

Step 9

Defines a CEM channel.cem group-number

Example:

Router(config-cem)# cem 0

Step 10

Binds an attachment circuit to a pseudowire, to configure an AnyTransport over MPLS (AToM) static pseudowire.


Example:

Router(config-cem)# xconnect 2.2.2.2 111encapsulation mpls

Step 11

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

• encapsulation—Specifies the tunneling method toencapsulate the data in the pseudowire.

• mpls—SpecifiesMultiprotocol Label Switching (MPLS) asthe tunneling method.





Example:

Router(config-if-xconn)# backup peer2.2.2.3 111


Configuring LFA-FRR for SAToPTo configure LFA-FRR for SAToP, complete the following steps:


SUMMARY STEPS

1. enable2. configure terminal3. controller {t1 | e1} slot/port4. framing unframed5. clock source internal6. cem-group group-number unframed7. description descriptive-name8. exit9. interface cem slot/port10. no ip address11. cem group-number12. xconnect ip-address encapsulation mpls13. backup peer peer-ip-address

DETAILED STEPS



Example:

Router> enable






Example:


Step 2



Example:


Step 3

Specifies the framing format of a circuit emulation (CEM) T1or E1 port.

framing unframed

Example:

Router(config-controller)# framing unframed

Step 4

Sets clocking for individual T1 or E1 links.clock source internal

Example:

Router(config-controller)# clock sourceinternal

Step 5

Assigns channels on the T1 or E1 circuit to the CEM channel.cem-group group-number unframedStep 6

Example:

Router(config-controller)# cem-group 0unframed

• group-number—Channel number to be used for this groupof time slots.

• unframed—Specifies that a single CEM channel is beingcreated including all time slots and the framing structureof the line.

Specifies a descriptive name for the controllerdescription descriptive-name

Example:

Router(config-controller)# description E1SAToP example

Step 7

Exits controller configuration mode.exit

Example:

Router(config-controller)# exit

Step 8

Defines a CEM channel.interface cem slot/port

Example:

Router(config)# interface CEM 0/0

Step 9





Example:


Step 10

Defines a CEM channel.cem group-number

Example:

Router(config-if)# cem 0

Step 11

Binds an attachment circuit to a pseudowire, to configure anAny Transport over MPLS (AToM) static pseudowire.


Example:

Router(config-if-cem)# xconnect 2.2.2.2 111encapsulation mpls

Step 12

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

• encapsulation—Specifies the tunneling method toencapsulate the data in the pseudowire.

• mpls—SpecifiesMultiprotocol Label Switching (MPLS)as the tunneling method.


Example:

Router(config-if-cem-xconn)# backup peer2.2.2.3 111


Verification Examples for Remote LFA-FRR

Verifying Remote LFA-FRR ConfigurationTo verify the remote LFA-FRR configuration, use the show commands described in the following examples.

To display information for an OSPF per-prefix LFA-FRR configuration, use the following show command.

Router# show ip ospf fast-reroute remote-lfa tunnelsOSPF Router with ID (1.1.1.1) (Process ID 1)

Area with ID (0)Base Topology (MTID 0)

Interface MPLS-Remote-Lfa5Tunnel type: MPLS-LDPTailend router ID: 5.5.5.5Termination IP address: 5.5.5.5Outgoing interface: Vlan4004First hop gateway: 71.14.1.4Tunnel metric: 2


Remote Loop-Free Alternate - Fast RerouteVerification Examples for Remote LFA-FRR

Protects:71.17.1.7 Vlan4003, total metric 4

Interface MPLS-Remote-Lfa6Tunnel type: MPLS-LDPTailend router ID: 6.6.6.6Termination IP address: 6.6.6.6Outgoing interface: Vlan4003First hop gateway: 71.17.1.7Tunnel metric: 2Protects:71.14.1.4 Vlan4004, total metric 4

To display entries in the Cisco Express Forwarding (CEF) Forwarding Information Base (FIB), use thefollowing show command.

Router# show ip cef 171.1.1.0 internal171.1.1.0/24, epoch 0, RIB[I], refcount 5, per-destination sharingsources: RIB, LTEfeature space:IPRM: 0x00028000LFD: 171.1.1.0/24 1 local labellocal label info: global/542

contains path extension listdisposition chain 0x12E83850label switch chain 0x12E83850

ifnums:Vlan4004(30): 71.14.1.4MPLS-Remote-Lfa6(37)path 12C70E98, path list 12D52154, share 1/1, type attached nexthop, for IPv4, flags

has-repairMPLS short path extensions: MOI flags = 0x20 label 31

nexthop 71.14.1.4 Vlan4004 label [31|537], adjacency IP adj out of Vlan4004, addr 71.14.1.412CD6A40

repair: attached-nexthop 6.6.6.6 MPLS-Remote-Lfa6 (12C70FE8)path 12C70FE8, path list 12D52154, share 1/1, type attached nexthop, for IPv4, flags

repair, repair-onlynexthop 6.6.6.6 MPLS-Remote-Lfa6, repair, adjacency IP midchain out of MPLS-Remote-Lfa6

12CD7880output chain: label [31|537]FRR Primary (0x11139020)<primary: TAG adj out of Vlan4004, addr 71.14.1.4 12D8A780><repair: TAG midchain out of MPLS-Remote-Lfa6 12CD6580 label 338 TAG adj out of Vlan4003,addr 71.17.1.7 12CD7160>To display local Routing Information Base (RIB) or locally redistributed routes use the following showcommand.

Router# show ip ospf rib 171.1.1.0OSPF Router with ID (1.1.1.1) (Process ID 1)

Base Topology (MTID 0)OSPF local RIBCodes: * - Best, > - Installed in global RIBLSA: type/LSID/originator*> 171.1.1.0/24, Intra, cost 2, area 0

SPF Instance 130, age 00:03:52Flags: RIB, iSPFvia 71.14.1.4, Vlan4004Flags: RIB, iSPFLSA: 1/2.0.0.2/2.0.0.2repair path via 6.6.6.6, MPLS-Remote-Lfa6, cost 4Flags: RIB, Repair, IntfDj, BcastDj, CostWonLSA: 1/2.0.0.2/2.0.0.2

To display information for an IS-IS per-prefix LFA-FRR configuration, use the following show command.

Router# show isis fast-reroute remote-lfa tunnelsTag Null - Fast-Reroute Remote-LFA Tunnels:MPLS-Remote-Lfa1: use Vl4003, nexthop 71.17.1.7, end point 6.6.6.6MPLS-Remote-Lfa2: use Vl4004, nexthop 71.14.1.4, end point 5.5.5.5



To display entries in the CEF Forwarding Information Base (FIB) use the following show command.

Router# show ip cef 171.1.1.0 internal171.1.1.0/24, epoch 0, RIB[I], refcount 5, per-destination sharingsources: RIB, LTEfeature space:IPRM: 0x00028000LFD: 171.1.1.0/24 1 local labellocal label info: global/18

contains path extension listdisposition chain 0x12B537C8

ifnums:Vlan4004(30): 71.14.1.4MPLS-Remote-Lfa1(32)path 12C55CB4, path list 12C856E8, share 1/1, type attached nexthop, for IPv4, flags

has-repairMPLS short path extensions: MOI flags = 0x20 label none

nexthop 71.14.1.4 Vlan4004 label [none|23], adjacency IP adj out of Vlan4004, addr 71.14.1.41139FAA0

repair: attached-nexthop 6.6.6.6 MPLS-Remote-Lfa1 (12C55D24)path 12C55D24, path list 12C856E8, share 1/1, type attached nexthop, for IPv4, flags

repair, repair-onlynexthop 6.6.6.6 MPLS-Remote-Lfa1, repair, adjacency IP midchain out of MPLS-Remote-Lfa1

12D512C0output chain: label [none|23]FRR Primary (0xA74F800)<primary: IP adj out of Vlan4004, addr 71.14.1.4 1139FAA0><repair: TAG midchain out of MPLS-Remote-Lfa1 11180740 label 366 TAG adj out of Vlan4003,addr 71.17.1.7 12D51520>To display information about IS-IS FRR configurations, use the following show command.

Router# show isis fast-reroute summaryTag null:IPv4 Fast-Reroute Protection Summary:Prefix Counts: Total Protected CoverageHigh priority: 0 0 0%Normal priority: 10 8 80%Total: 10 8 80%

To display paths for a specific route or for all routes under a major network that are stored in the IP localRouting Information Base (RIB), use the following show command.

Router# show isis rib 171.1.1.0IPv4 local RIB for IS-IS processIPV4 unicast topology base (TID 0, TOPOID 0x0) =================Repair path attributes:

DS - Downstream, LC - Linecard-Disjoint, NP - Node-ProtectingPP - Primary-Path, SR - SRLG-Disjoint

Routes under majornet 171.1.0.0/16:171.1.1.0/24[115/L1/10] via 71.14.1.4(Vlan4004), from 71.14.1.4, tag 0, LSP[2/18]

(installed)repair path: 6.6.6.6(MPLS-Remote-Lfa1) metric:20 (DS,SR) LSP[2]

Verifying Remote LFA-FRR Configuration for EoMPLS on a GigabitEthernet InterfaceTo verify the remote LFA-FRR configuration for EoMPLS on a GigabitEthernet interface, use the showcommands described in the following examples.

Router# show mpls l2transport vc 1 detailLocal interface: Gi0/0 up, line protocol up, Ethernet upDestination address: 3.3.3.3, VC ID: 1, VC status: upOutput interface: Vl4000, imposed label stack {18 16}Preferred path: not configuredDefault path: activeNext hop: 71.12.1.2

Create time: 00:00:06, last status change time: 00:00:06



Last label FSM state change time: 00:00:06Signaling protocol: LDP, peer 3.3.3.3:0 upTargeted Hello: 1.1.1.1(LDP Id) -> 3.3.3.3, LDP is UPGraceful restart: not configured and not enabledNon stop routing: not configured and not enabledStatus TLV support (local/remote) : enabled/supportedLDP route watch : enabledLabel/status state machine : established, LruRruLast local dataplane status rcvd: No faultLast BFD dataplane status rcvd: Not sentLast BFD peer monitor status rcvd: No faultLast local AC circuit status rcvd: No faultLast local AC circuit status sent: No faultLast local PW i/f circ status rcvd: No faultLast local LDP TLV status sent: No faultLast remote LDP TLV status rcvd: No faultLast remote LDP ADJ status rcvd: No fault

MPLS VC labels: local 323, remote 16Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:

Sequencing: receive disabled, send disabledControl Word: On (configured: autosense)Dataplane:SSM segment/switch IDs: 4801/4799 (used), PWID: 1

VC statistics:transit packet totals: receive 0, send 1009697transit byte totals: receive 0, send 96933706transit packet drops: receive 0, seq error 0, send 0

Local interface: Gi0/0 up, line protocol up, Ethernet upDestination address: 4.4.4.4, VC ID: 1, VC status: standbyOutput interface: Vl4000, imposed label stack {21 16}Preferred path: not configuredDefault path: activeNext hop: 71.12.1.2

Create time: 00:00:06, last status change time: 00:16:44Last label FSM state change time: 00:00:06

Signaling protocol: LDP, peer 4.4.4.4:0 upTargeted Hello: 1.1.1.1(LDP Id) -> 4.4.4.4, LDP is UPGraceful restart: not configured and not enabledNon stop routing: not configured and not enabledStatus TLV support (local/remote) : enabled/supportedLDP route watch : enabledLabel/status state machine : established, LrdRruLast local dataplane status rcvd: No faultLast BFD dataplane status rcvd: Not sentLast BFD peer monitor status rcvd: No faultLast local AC circuit status rcvd: DOWN(standby)Last local AC circuit status sent: No faultLast local PW i/f circ status rcvd: No faultLast local LDP TLV status sent: DOWN(standby)Last remote LDP TLV status rcvd: No faultLast remote LDP ADJ status rcvd: No fault






Verifying Remote LFA-FRR Configuration for EoMPLS on an EVC InterfaceTo verify the remote LFA-FRR configuration for EoMPLS on an EVC interface, use the show commandsdescribed in the following examples.

Router# show mpls l2transport vc 3001 detailLocal interface: Gi0/0 up, line protocol up, Eth VLAN 200 upInterworking type is EthernetDestination address: 3.3.3.3, VC ID: 1, VC status: upOutput interface: Vl4000, imposed label stack {18 16}Preferred path: not configuredDefault path: activeNext hop: 71.12.1.2


Signaling protocol: LDP, peer 3.3.3.3:0 upTargeted Hello: 1.1.1.1(LDP Id) -> 3.3.3.3, LDP is UPGraceful restart: not configured and not enabledNon stop routing: not configured and not enabledStatus TLV support (local/remote) : enabled/supportedLDP route watch : enabledLabel/status state machine : established, LruRruLast local dataplane status rcvd: No faultLast BFD dataplane status rcvd: Not sentLast BFD peer monitor status rcvd: No faultLast local AC circuit status rcvd: No faultLast local AC circuit status sent: No faultLast local PW i/f circ status rcvd: No faultLast local LDP TLV status sent: No faultLast remote LDP TLV status rcvd: No faultLast remote LDP ADJ status rcvd: No fault

MPLS VC labels: local 16, remote 16Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:MAC Withdraw: sent:1, received:0



Local interface: Gi0/0 up, line protocol up, Eth VLAN 200 upInterworking type is EthernetDestination address: 4.4.4.4, VC ID: 1, VC status: standbyOutput interface: Vl4000, imposed label stack {21 16}Preferred path: not configuredDefault path: activeNext hop: 71.12.1.2


Signaling protocol: LDP, peer 4.4.4.4:0 upTargeted Hello: 1.1.1.1(LDP Id) -> 4.4.4.4, LDP is UPGraceful restart: not configured and not enabledNon stop routing: not configured and not enabledStatus TLV support (local/remote) : enabled/supportedLDP route watch : enabledLabel/status state machine : established, LrdRruLast local dataplane status rcvd: No faultLast BFD dataplane status rcvd: Not sentLast BFD peer monitor status rcvd: No faultLast local AC circuit status rcvd: DOWN(standby)Last local AC circuit status sent: No faultLast local PW i/f circ status rcvd: No faultLast local LDP TLV status sent: DOWN(standby)Last remote LDP TLV status rcvd: No faultLast remote LDP ADJ status rcvd: No fault

MPLS VC labels: local 17, remote 16



Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:MAC Withdraw: sent:1, received:0



Verifying Remote LFA-FRR Configuration on IS-ISTo verify the remote LFA-FRR configuration on IS-IS, use the show commands described in the followingexamples.

Router# show isis fast-reroute remote-lfa tunnelsTag aggg - Fast-Reroute Remote-LFA Tunnels:No Remote-LFA tunnel

Tag Null - Fast-Reroute Remote-LFA Tunnels:No Remote-LFA tunnel

Tag agg - Fast-Reroute Remote-LFA Tunnels:MPLS-Remote-Lfa5: use Vl27, nexthop 27.27.27.2, end point 192.168.1.2MPLS-Remote-Lfa6: use Vl50, nexthop 50.50.50.2, end point 192.168.1.2

Verifying Remote LFA-FRR Configuration on ATM/IMATo verify the remote LFA-FRR configuration onATM/IMA, use the show commands described in the followingexample.

Router# show mpls l2 vc 90 detailLocal interface: AT0/IMA2 up, line protocol up, ATM AAL5 90/90 Basic 1 upDestination address: 2.2.2.2, VC ID: 111, VC status: upOutput interface: Vlan300, imposed label stack {29 32}Preferred path: not configuredDefault path: activeNext hop: point2point




Sequencing: receive disabled, send disabledControl Word: On (configured: autosense)



Verifying Remote LFA-FRR Configuration on CESoPSNTo verify the remote LFA-FRR configuration on CESoPSN, use the show commands described in the followingexample.

Router# show mpls l2 vc 111 detailLocal interface: CE0/0 up, line protocol up, CESoPSN Basic 1 upDestination address: 2.2.2.2, VC ID: 111, VC status: upOutput interface: Vlan300, imposed label stack {29 32}Preferred path: not configuredDefault path: activeNext hop: point2point






Verifying Remote LFA-FRR Configuration on SAToPTo verify the remote LFA-FRR configuration on SAToP, use the show commands described in the followingexample.

Router# show mpls l2 vc 111 detail

Local interface: CE0/0 up, line protocol up, SATOP Basic 1 upDestination address: 2.2.2.2, VC ID: 111, VC status: upOutput interface: Vlan300, imposed label stack {29 32}Preferred path: not configuredDefault path: activeNext hop: point2point


Signaling protocol: LDP, peer 2.2.2.2:0 upTargeted Hello: 170.0.0.201(LDP Id) -> 2.2.2.2, LDP is UPGraceful restart: not configured and not enabledNon stop routing: not configured and not enabledStatus TLV support (local/remote) : enabled/supportedLDP route watch : enabledLabel/status state machine : established, LruRruLast local dataplane status rcvd: No fault



Last BFD dataplane status rcvd: Not sentLast BFD peer monitor status rcvd: No faultLast local AC circuit status rcvd: No faultLast local AC circuit status sent: No faultLast local PW i/f circ status rcvd: No faultLast local LDP TLV status sent: No faultLast remote LDP TLV status rcvd: No faultLast remote LDP ADJ status rcvd: No fault


Sequencing: receive disabled, send disabledControl Word: On (configured: autosense)

Configuration Examples for Remote LFA-FRRThis section provides sample configuration examples for Remote LFA-FRR feature on the Cisco ASR 901Srouter.

Example: Configuring Remote LFA-FRR for IS-ISThe following is a sample configuration of Remote LFA-FRR for IS-IS on all nodes.

!mpls label protocol ldpmpls ldp router-id lo0 forcempls ldp discovery targeted-hello acceptno l3-over-l2 flush buffersasr901-platf-frr enablerouter isismetric-style widefast-floodmax-lsp-lifetime 65535lsp-refresh-interval 65000spf-interval 5 50 200prc-interval 5 50 200lsp-gen-interval 5 50 200no hello paddinglog-adjacency-changes allfast-reroute per-prefix level-1 allfast-reroute remote-lfa level-1 mpls-ldpmpls ldp sync!

Example: Configuring Remote LFA-FRR for OSPFThe following is a sample configuration of Remote LFA-FRR for OSPF on all nodes.

!mpls label protocol ldpmpls ldp router-id lo0 forcempls ldp discovery targeted-hello acceptno l3-over-l2 flush buffersasr901-platf-frr enablerouter ospf 1router-id 5.5.5.5fast-reroute per-prefix enable area 0 prefix-priority lowfast-reroute per-prefix remote-lfa tunnel mpls-ldptimers throttle spf 50 200 5000timers throttle lsa 50 200 5000


Remote Loop-Free Alternate - Fast RerouteConfiguration Examples for Remote LFA-FRR

timers lsa arrival 100mpls ldp sync!

Example: Configuring Remote LFA-FRR GloballyThe following is a sample configuration of Remote LFA-FRR at a global level.

!mpls label protocol ldpmpls ldp discovery targeted-hello acceptno l3-over-l2 flush buffersasr901-platf-frr enable!

Example: Configuring Remote LFA-FRR on a GigabitEthernet InterfaceThe following is a sample configuration of Remote LFA-FRR on a GigabitEthernet Interface.

!interface GigabitEthernet0/5no ip addressnegotiation autoservice instance 7 ethernetencapsulation dot1q 7rewrite ingress tag pop 1 symmetricbridge-domain 7

!

Example: Configuring Remote LFA-FRR on an SVI InterfaceThe following is a sample configuration of Remote LFA-FRR on an SVI Interface.

!interface Vlan7ip address 7.7.7.2 255.255.25ip router isismpls ipisis network point-to-point!

Example: Configuring EoMPLS Pseudowire Redundancy over FRRThe following is a sample configuration of EoMPLS pseudowire redundancy over FRR.

!interface GigabitEthernet0/0no ip addressload-interval 30negotiation autoservice instance 1 ethernetencapsulation dot1q 200rewrite ingress tag pop 1 symmetricxconnect 3.3.3.3 1 encapsulation mplsbackup peer 4.4.4.4 1mtu 1500

!


Remote Loop-Free Alternate - Fast RerouteExample: Configuring Remote LFA-FRR Globally

Example: Configuring LFA-FRR on ATM/IMAThe following is a sample configuration of LFA-FRR on ATM/IMA, which also includes pseudowireredundancy.

!controller E1 0/0ima-group 2!interface ATM0/IMA1no ip addressno atm enable-ilmi-trapxconnect 2.2.2.2 90 encapsulation mplsbackup peer 180.0.0.201 90

!

Example: Configuring LFA-FRR on CESoPSNThe following is a sample configuration of LFA-FRR on CESoPSN, which also includes pseudowireredundancy.

!controller E1 0/0clock source internalcem-group 0 timeslots 1-31description E1 CESoPSN example!!interface CEM0/2no ip addresscem 1xconnect 2.2.2.2 111 encapsulation mpls pw-class testbackup peer 180.0.0.201 111

!

Example: Configuring LFA-FRR on SAToPThe following is a sample configuration of LFA-FRR on SAToP, which also includes pseudowire redundancy.

!controller E1 0/0clock source internalcem-group 1 unframeddescription E1 SATOP example!interface CEM0/0no ip addresscem 0xconnect 2.2.2.2 111 encapsulation mplsbackup peer 180.0.0.201 111

!!

Additional ReferencesThe following sections provide references related to Remote Loop-Free Alternate - Fast Reroute feature.


Remote Loop-Free Alternate - Fast RerouteExample: Configuring LFA-FRR on ATM/IMA

Related Documents

Document TitleRelated Topic

Cisco IOS Master Commands List, All ReleasesCisco IOS Commands

Cisco ASR 901S Series Aggregation Services RouterCommand Reference

Cisco ASR 901S Router Commands

IS-IS Remote Loop-Free Alternate Fast RerouteIS-IS Remote LFA FRR

OSPFv2 Loop-Free Alternate Fast RerouteOSPFv2 LFA FRR

Standards

TitleStandard

—None

MIBs

MIBs LinkMIB

To locate and downloadMIBs for selected platforms,Cisco IOS releases, and feature sets, use Cisco MIBLocator found at the following URL:

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

None

RFCs

TitleRFC

—None

Technical Assistance

LinkDescription

http://www.cisco.com/techsupportThe Cisco Technical Support website containsthousands of pages of searchable technical content,including links to products, technologies, solutions,technical tips, and tools. Registered Cisco.com userscan log in from this page to access evenmore content.


Remote Loop-Free Alternate - Fast RerouteAdditional References

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

http://www.cisco.com/c/en/us/td/docs/wireless/asr_901s/cr/b_cr_for_asr901s.html

http://www.cisco.com/c/en/us/td/docs/wireless/asr_901s/cr/b_cr_for_asr901s.html

http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_isis/configuration/15-s/irs-15-s-book.html

http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_ospf/configuration/xe-3s/iro-lfa-frr-xe.html

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

http://www.cisco.com/techsupport

Feature Information for Remote Loop-Free Alternate - FastReroute

Table 1: Feature Information for Remote Loop-Free Alternate - Fast Reroute, on page 40 lists the featuresin 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 Remote Loop-Free Alternate - Fast Reroute, on page 40 lists only thesoftware release that introduced support for a given feature in a given software release train. Unless notedotherwise, subsequent releases of that software release train also support that feature.

Note

Table 1: Feature Information for Remote Loop-Free Alternate - Fast Reroute

Feature InformationReleasesFeature Name

This feature was introduced on theCisco ASR 901 routers.

The following sections provideinformation about this feature:

15.2(2)SNIRemote Loop-Free Alternate - FastReroute

This feature was introduced on theCisco ASR 901 routers.

The following section providesinformation about this feature:

15.3(2)SRemote Loop-Free Alternate - FastReroute for EoMPLS

Support for TDMPseudowires wasadded.

15.3(3)SRemote Loop-Free Alternate - FastReroute for TDM Pseudowires.

Support was added for EoMPLSpseudowire redundancy over FRR.

15.4(1)SEoMPLS Pseudowire Redundancyover FRR

Support was added for TDMpseudowire redundancy over FRR.

15.4(1)STDM Pseudowire Redundancyover FRR


Remote Loop-Free Alternate - Fast RerouteFeature Information for Remote Loop-Free Alternate - Fast Reroute

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

Remote Loop-Free Alternate - Fast Reroute - cisco.com · Remote Loop-Free Alternate - Fast Reroute...

Documents

Transcript of Remote Loop-Free Alternate - Fast Reroute - cisco.com · Remote Loop-Free Alternate - Fast Reroute...