Cube HA ISR 4431configuration question

[pavelherc]

Hello, 

I have a question regarding the box2box Cube HA. Our customer has a B2b configuration where each cube is connected to one switch on each end and there is direct connection between the cubes via Gigabit Port. 

The customer has tried to do a faillure scenario and he found out that the Voice calls are not preserved. In the test were the aggregation switches (Aruba) powered off,( show redundancy states shows one cube as Active and other as standby device) but the calls were not going through. After the reload of both boxes the connectivity was established. 

IN the documentation I have seen that each interface which is pointing to CUCM or SIP provider, should be connected to  the same physical switch (Cube1 and Cube to interfaces towards the CUCM to the same switch and also on the provider side the same..). Could this be the root cause for the issue mentioned above ? 

Thank you 

[acampbell]

Hi,

I think you need to have a good look at this document to see the options for what you are trying to achieve:-

Cisco Unified Border Element Configuration Guide Through Cisco IOS XE 17.5 - High Availability on Cisco 4000 Series ISR and Cisco Catalyst 8000 Series Edge Platforms [Cisco Unified Border Element] - Cisco

[pavelherc]

Hi Alex, 
Thank you for the link. Exactly there I have found under the restrictions the mention that cube 1 and cube 2 interfaces should be connected to the same physical switch on each side. Howerever the customer configuration is like I mentioned before configured a bit diferently, but the output of the show redundancycommands shows that there is an application redundancy.. this confuses me a bit. 

output of the on one of the router:

svr-cube01#show redundancy application group all
Faults states Group 1 info:
Runtime priority: [100]
RG Faults RG State: Up.
Total # of switchovers due to faults: 0
Total # of down/up state changes due to faults: 2

RG Protocol RG 1
------------------
Role: Standby
Negotiation: Enabled
Priority: 100
Protocol state: Standby-hot
Ctrl Intf(s) state: Up
Active Peer: address 192.168.xx.x, priority 100, intf Gi0/0/2
Standby Peer: Local
Log counters:
role change to active: 0
role change to standby: 1
disable events: rg down state 1, rg shut 0
ctrl intf events: up 1, down 2, admin_down 1
reload events: local request 0, peer request 0

RG Media Context for RG 1
--------------------------
Ctx State: Standby
Protocol ID: 1
Media type: Default
Control Interface: GigabitEthernet0/0/2
Current Hello timer: 4000
Configured Hello timer: 4000, Hold timer: 6000
Peer Hello timer: 4000, Peer Hold timer: 6000
Stats:
Pkts 56449, Bytes 3499838, HA Seq 0, Seq Number 56449, Pkt Loss 0
Authentication not configured
Authentication Failure: 0
Reload Peer: TX 0, RX 0
Resign: TX 0, RX 0
Active Peer: Present. Hold Timer: 6000
Pkts 56439, Bytes 1918926, HA Seq 0, Seq Number 56446, Pkt Loss 0

Group ID:1
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: Yes

RF Domain: btob-one
RF state: STANDBY HOT
Peer RF state: ACTIVE

svr-cube01#show redundancy states
my state = 13 -ACTIVE
peer state = 1 -DISABLED
Mode = Simplex
Unit = Primary
Unit ID = 48

Redundancy Mode (Operational) = Non-redundant
Redundancy Mode (Configured) = Non-redundant
Redundancy State = Non Redundant
Maintenance Mode = Disabled
Manual Swact = disabled (system is simplex (no peer unit))
Communications = Down Reason: Simplex mode

client count = 87
client_notification_TMR = 30000 milliseconds
RF debug mask = 0x0

and this output also confuses me a bit. application redundancy shows standby/active mode, but the redundancy states shows it is in a simplex mode ( no switchover possible ? ) Is it because of the redundancy mode none command ? 

[sjdamme]

Ignore the "show redundancy states" command output. That's for a different type of redundancy configuration, not the application group redundancy used by the CUBEs. Your "show redundancy application group all" output looks good with your cube-ha group in an operational state of up and your box and its peer in valid states of STANDBY HOT and ACTIVE. Do you have the redundancy group in your voice service voip config? You should have "redundancy-group 1" under voice service voip on both CUBEs in the HA pair. 

[pavelherc]

Hi SJDamme, 
I have checked the config and found there the no redundancy-reload command on both cubes under voice service voip. I guess this could make troubles there also... 
If I change the configuration to redundancy-reload under voice service voip - will it trigger an immediate reboot of the cube or  it will reload the cube only if triggered by redundancy issues ? 

[sjdamme]

You do not need redundancy-reload under voice service voip. You only need "redundancy-group 1". Do you see active calls on both of the HA CUBEs? If you run a "show call active voice compact" on both CUBEs you should see the same calls listed on both boxes. If you do not see the same calls on both your CUBEs, HA service is not working correctly and calls will not be preserved in a failover event. 

[pavelherc]

as what I have seen in the docu, the redundancy reload is enabled by default, so it is normally not visible. but in our configuration it was disabled. ( so the cubes are working in protected mode ? ) is it save to do it during the day, or it wiill trigger a reload of the router when used under the voice service voip?