Cisco Cube Redundancy 8200

[simon hester]

Hi

Looking for some help around Box to Box redundancy for a pair of new Cisco 8200 running as CUBE. 

We have followed this guide High Availability on Cisco 4000 Series ISR and Cisco Catalyst 8000 Series Edge Platforms 

We have the CUBE patches to the same logical switch but the CUBEs do not come up full in HA

The primary CUBE has the following

Bic_Cube_8200#show redundancy application group 2
Group ID:2
Group Name:Cube-HA

Administrative State: No Shutdown
Aggregate operational state : Up
My Role: ACTIVE
Peer Role: UNKNOWN
Peer Presence: No
Peer Comm: Yes
Peer Progression Started: No

RF Domain: btob-two
RF state: ACTIVE
Peer RF state: UNKNOWN

The backup CUBE has the following

Muni_Cube_8200#show redundancy application group 2
Group ID:2
Group Name:Cube-HA

Administrative State: No Shutdown
Aggregate operational state : Up
My Role: STANDBY
Peer Role: ACTIVE
Peer Presence: Yes
Peer Comm: Yes
Peer Progression Started: No

RF Domain: btob-two
RF state: STANDBY COLD
Peer RF state: DISABLED

We have confirmed comms across the control and data port using ping and also took a packet captures that showed heartbeat packets. 

The output above appears to shows peer comms yet they do not come up in HA. 

Any help would be greatly appreciated. 

Thanks

[b.winter]

Without the config, probably nobody will be able to help you.
Please post the config of both routers, and the info, which interfaces are used for which traffic ("internal", "external", keepalive link).

[simon hester]

I will look to get the config uploaded mean time we have found a possible issue with the HA multicast traffic that is running between the two CUBE over a N5k Fabric path link. 

It seem traffic is leaving one side but not arriving at the other. 

[b.winter]

According to the info you shared, "Bic_Cube_8200" doesn't see the other cube, so it looks like a communication issue via the HA-link.

My Role: ACTIVE
Peer Role: UNKNOWN

[simon hester]

So test the HA with a back to back direct fibre and it works so it is not a CUBE issue per-say. 

We now have TAC looking at potential Fabric Path issue. But we may opt to go for a pair of fibres for the HA link.