Cisco ASR9000/XR - GigE bundles in cold standby

[Nsight_Transport]

Both 9Ks are on 5.3.4.  I have a single NV SAT that sits between the two 9K's

Is this the expected behavior of Router 9001_B to be in Cold Standby?  Thanks

****************************************** 9001 A config ******************************************

RP/0/RSP0/CPU0:9001_A#show bundle brief
Mon Dec  5 08:44:10.619 cst

Name   | IG       | State         | LACP | BFD |     Links     | Local b/w, |
       |          |               |      |     | act/stby/cfgd |    kbps    |
-------|----------|---------------|------|-----|---------------|------------|

BE3              - Up              Off    Off         2 / 0 / 2      2000000
BE4              - Up              Off    Off         2 / 0 / 2      2000000
BE5              - Up              Off    Off         2 / 0 / 2      2000000

           - Up              Off    Off         2 / 0 / 2      2000000

RP/0/RSP0/CPU0:9001_A#sh run redundancy iccp group 1
Mon Dec  5 08:48:08.266 cst
redundancy
 iccp
  group 1
   member
    neighbor 10.43.95.105
   !
   nv satellite
    system-mac 0100.4309.5105

!

!

interface TenGigE0/0/0/2
 mtu 9212
 vrf NV_MGMT
 ipv4 point-to-point
 ipv4 unnumbered Loopback100
 nv
  satellite-fabric-link network
   redundancy
    iccp-group 1
   !
   satellite 300
    remote-ports GigabitEthernet 0/0/0-43
   !

RP/0/RSP0/CPU0:9001_A#show bundle bundle-ether 3
Mon Dec  5 08:58:25.122 cst

Bundle-Ether3
  Status:                                    Up
  Local links <active/standby/configured>:   2 / 0 / 2
  Local bandwidth <effective/available>:     2000000 (2000000) kbps
  MAC address (source):                      8478.ac7f.71f3 (Chassis pool)
  Inter-chassis link:                        No
  Minimum active links / bandwidth:          1 / 1 kbps
  Maximum active links:                      4
  Wait while timer:                          1000 ms
  Load balancing:                            Default
  LACP:                                      Not operational
    Flap suppression timer:                  Off
    Cisco extensions:                        Disabled
    Non-revertive:                           Disabled
  mLACP:                                     Not configured
  IPv4 BFD:                                  Not configured

  Port                  Device           State        Port ID         B/W, kbps
  --------------------  ---------------  -----------  --------------  ----------
  Gi300/0/0/0           Local            Active       0x8000, 0x0000     1000000
      Link is Active
  Gi300/0/0/22          Local            Active       0x8000, 0x0000     1000000
      Link is Active

!

!

****************************************** 9001 B config ******************************************

RP/0/RSP0/CPU0:9001_B#show bundle brief
Mon Dec  5 08:45:18.258 cst

Name   | IG       | State         | LACP | BFD |     Links     | Local b/w, |
       |          |               |      |     | act/stby/cfgd |    kbps    |
-------|----------|---------------|------|-----|---------------|------------|

BE3              - Cold standby    Off    Off         0 / 0 / 2            0
BE4              - Cold standby    Off    Off         0 / 0 / 2            0
BE5              - Cold standby    Off    Off         0 / 0 / 2            0

RP/0/RSP0/CPU0:9001_B#sh run redundancy iccp group 1
Mon Dec  5 08:49:54.257 cst
redundancy
 iccp
  group 1
   member
    neighbor 10.43.95.113
   !
   nv satellite
    system-mac 0100.4309.5105

!

!

interface TenGigE0/0/0/2
 mtu 9212
 vrf NV_MGMT
 ipv4 point-to-point
 ipv4 unnumbered Loopback100
 nv
  satellite-fabric-link network
   redundancy
    iccp-group 1
   !
   satellite 300
    remote-ports GigabitEthernet 0/0/0-43
   !

RP/0/RSP0/CPU0:9001_B#show bundle bundle-ether 3
Mon Dec  5 08:59:07.104 cst

Bundle-Ether3
  Status:                                    Cold standby
  Local links <active/standby/configured>:   0 / 0 / 2
  Local bandwidth <effective/available>:     0 (0) kbps
  MAC address (source):                      d867.d961.83da (Chassis pool)
  Inter-chassis link:                        No
  Minimum active links / bandwidth:          1 / 1 kbps
  Maximum active links:                      4
  Wait while timer:                          1000 ms
  Load balancing:                            Default
  LACP:                                      Not operational
    Flap suppression timer:                  Off
    Cisco extensions:                        Disabled
    Non-revertive:                           Disabled
  mLACP:                                     Not configured
  IPv4 BFD:                                  Not configured

  Port                  Device           State        Port ID         B/W, kbps
  --------------------  ---------------  -----------  --------------  ----------
  Gi300/0/0/0           Local            Configured   0x8000, 0x0000     1000000
      Link is in standby redundancy state
  Gi300/0/0/22          Local            Configured   0x8000, 0x0000     1000000
      Link is in standby redundancy state

[xthuijs · Accepted solution]

could it be that there is a configuration mismatch between the active and standby POA for this bundle?

here are a few reasons for a bundle to be in cold standby:

The bundle interface will be Down on the Standby device if:
1.    The device is not ready to forward bundle traffic; if the bundle goes 
down on the Active device, traffic will be lost.
2.    The device is cold standby for the bundle [ie]:
The bundle has enough links available to take over if required.  However, it is 
marked as Down in IM because it will have to be Down initially after the 
switchover while LACP negotiations are in progress.  This is due to some 
missing configuration that is required for a  seamless switchover; e.g. lacp 
switchover suppress-flaps.

xander

[Nsight_Transport]

Thanks for the explanation Xander.  To note - the failover does work when the cold standby sides does go active.  It would appear if we implement "switchover suppress flaps" we'd still be looking at some downtime when the active link is restored and it fails back?

[xthuijs]

it should go very fast, but it is partially dependent on the DHD also.

the suppress flaps will allow us to keep the bundle up while the lacp negotiations are happening for a short period of time, as long as its timer value configured.

the down event can have a ripple effect obviously in terms of routing and other events that are happening when an interface goes from up to down to up again.

cheers!

xander