AToM GR works in strict helper mode, which means it helps a neighboring route processor that has AToM NSF/SSO to recover from a disruption in service without losing its MPLS forwarding state. The disruption in service could result from a TCP or User Datagram Protocol (UDP) event or the stateful switchover of a route processor. AToM GR is based on the MPLS LDP Graceful Restart feature, which preserves forwarding information for AToM circuits during an LDP session interruption. When the neighboring router establishes a new session, the LDP bindings and MPLS forwarding state are recovered. For more information related to how the LDP Graceful Restart feature works, see the MPLS LDP Graceful Restart feature module.

Before You Begin

• See the MPLS LDP Graceful Restart document for information about how LDP GR works and how you can customize it for your network.
• Configure AToM. For information about setting up or configuring AToM, see the Any Transport over MPLS document.

Note	AToM GR is supported in strict helper mode. AToM NSF/SSO is supported in Cisco IOS Release 12.2(25)S and 12.2(33)SRA. Tag Distribution Protocol (TDP) sessions are not supported. Only LDP sessions are supported. MPLS LDP GR cannot be configured on label-controlled ATM (LC-ATM) interfaces. >

1.    enable

2.    configure terminal

3.    ip cef [distributed]

4.    mpls ldp graceful-restart

The following example shows an Ethernet VLAN over MPLS configuration. PE1 is configured with AToM Graceful Restart. PE2 is configured with AToM NSF/SSO. The commands for configuring AToM GR and NSF/SSO are shown in bold.

ip cef
!
mpls label protocol ldp
mpls ldp graceful-restart
mpls ldp router-id Loopback0
!
pseudowire-class atom
encapsulation mpls
!
interface Loopback0
 ip address 10.1.1.2 255.255.255.255
!
interface FastEthernet5/1/1
 no ip address
!
interface FastEthernet5/1/1.2
 description "xconnect to PE2"
 encapsulation dot1Q 2 native
 xconnect 10.2.2.2 1002 pw-class mpls
!
! IGP for MPLS
router ospf 10
log-adjacency-changes
auto-cost reference-bandwidth 1000
network 10.1.1.2 10.0.0.0 area 0
network 10.1.1.0 10.0.0.255 area 0

redundancy
  mode sso
ip cef
!
mpls label protocol ldp
mpls ldp graceful-restart
mpls ldp router-id Loopback0
!
pseudowire-class atom
encapsulation mpls
!
interface Loopback0
 ip address 10.2.2.2 255.255.255.255
!
interface Ethernet3/3
 no ip address
!
interface Ethernet3/3.2
 description "xconnect to PE1"
 encapsulation dot1Q 2
 xconnect 10.1.1.2 1002 pw-class mpls
!
! IGP for MPLS
router ospf 10
log-adjacency-changes
nsf enforce global
auto-cost reference-bandwidth 1000
network 10.2.2.2 10.0.0.0 area 0
network 10.1.1.0 10.0.0.255 area 0

The following examples show the output of the show mpls l2transport vccommand during normal operation and when an LDP session is recovering from a disruption.

The following example shows the status of the VC on PE1 with AToM GR during normal operation:

Router# show mpls l2transport vc
Local intf     Local circuit        Dest address    VC ID      Status
-------------  -------------------- --------------- ---------- ----------
Fa5/1/1.2      Eth VLAN 2           10.2.2.2         1002       UP

The following example shows the status of the VC on PE1 with AToM GR while the VC is recovering from an LDP session disruption. The forwarding state for the circuit remains as it was before the disruption.

Router# show mpls l2transport vc
Local intf     Local circuit        Dest address    VC ID      Status
-------------  -------------------- --------------- ---------- ----------
Fa5/1/1.2      Eth VLAN 2           10.2.2.2         1002       RECOVERING

The following example shows the status of the VC on PE1 with AToM GR after the LDP session disruption was cleared. The AToM label bindings were advertised within the allotted time and the status returned to UP.

Router# show mpls l2transport vc
Local intf     Local circuit        Dest address    VC ID      Status
-------------  -------------------- --------------- ---------- ----------
Fa5/1/1.2      Eth VLAN 2           10.2.2.2         1002       UP

The following example shows the detailed status of the VC on PE1 with AToM GR during normal operation:

Router# show mpls l2transport vc detail
Local interface: Fa5/1/1.2 up, line protocol up, Eth VLAN 2 up
  Destination address: 10.2.2.2, VC ID: 1002, VC status: up
    Preferred path: not configured
    Default path: active
    Tunnel label: imp-null, next hop point2point
    Output interface: Se4/0/3, imposed label stack {16}
  Create time: 1d00h, last status change time: 1d00h
  Signaling protocol: LDP, peer 10.2.2.2:0 up
    MPLS VC labels: local 21, remote 16
    Group ID: local 0, remote 0
    MTU: local 1500, remote 1500
    Remote interface description: "xconnect to PE2"
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 3466, send 12286
    byte totals:   receive 4322368, send 5040220
    packet drops:  receive 0, send 0

The following example shows the detailed status of the VC on PE1 with AToM GR while the VC is recovering.

Router# show mpls l2transport vc detail
Local interface: Fa5/1/1.2 up, line protocol up, Eth VLAN 2 up
  Destination address: 10.2.2.2, VC ID: 1002, VC status: recovering
    Preferred path: not configured
    Default path: active
    Tunnel label: imp-null, next hop point2point
    Output interface: Se4/0/3, imposed label stack {16}
  Create time: 1d00h, last status change time: 00:00:03
  Signaling protocol: LDP, peer 10.2.2.2:0 down
    MPLS VC labels: local 21, remote 16
    Group ID: local 0, remote 0
    MTU: local 1500, remote 1500
    Remote interface description: "xconnect to PE2"
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 20040, send 28879
    byte totals:   receive 25073016, send 25992388
    packet drops:  receive 0, send 0