Configure High Availability (HA) on CUBE Routers

Available Languages

Download Options

  • PDF     (1.8 MB)
    View with Adobe Reader on a variety of devices
  • ePub     (2.2 MB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (1.1 MB)
    View on Kindle device or Kindle app on multiple devices
Updated:August 7, 2026
Document ID:221645

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This document describes how to configure High Availability (HA) on two Cisco Unified Border Element (CUBE) routers with all required commands.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

  • IP Routing
  • Cisco Switch
  • Cisco Unified Border Element (CUBE)

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Components Used

Cisco ASR1001-X routers running version 16.09.04.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Configure

Network Diagram

This network connectivity diagram shows you how CUBE routers are connected to the network.

  • Ingress side (Local Area Network - LAN) of both CUBEs are connected to VLAN 1900 via the interface Gi 0/0/1.
  • Egress side (Wide Area Network - WAN) of both the CUBEs are connected to VLAN 1967 via the interface Gi 0/0/2.
  • Keepalive interfaces of both CUBEs are connected to VLAN 17 via the interface Gi 0/0/0
note-icon

Note: CUBE interfaces are connected to physical Cisco Switch and the switchports are configured to allow the respective VLANs.

Network DiagramNetwork Diagram.

Configurations

Steps to configure the CUBE HA:

  1. Checkpointing configuration
  2. Commands to track the status of the LAN & WAN interfaces on the CUBEs
  3. Assign the configured tracks to the redundancy group
  4. Configuring virtual IP (VIP) on the LAN side
  5. Configuring virtual IP (VIP) on the WAN side
  6. Enable CUBE redundancy
  7. Save the configuration and reboot

Checkpointing Configuration

For checkpointing, configure these commands on both the CUBEs

note-icon

Note: The interface Gi 0/0/0 on both the CUBEs are used for checkpointing.

#conf t
(config)#redundancy
(config-red)#
(config-red)#application redundancy
(config-red-app)#group 1
(config-red-app-grp)#
(config-red-app-grp)#name cube-ha
(config-red-app-grp)#data gi 0/0/0
(config-red-app-grp)#control gi 0/0/0 protocol 1
(config-red-app-grp)#

This screenshot shows the command ran on the CUBE-2 router. You must run the same set of commands on CUBE-1 router:

Checkpointing Configuration on CUBE-2Checkpointing configuration on the CUBE-2.

Commands to Track the Status of the LAN & WAN Interfaces on the CUBEs

Configure these commands for tracking the status of the LAN & WAN interfaces. You must execute these commands on both the CUBE routers.

note-icon

Note: The interface Gi 0/0/1 on both the CUBEs are connected to the LAN network and Gi 0/0/2 are connected to the WAN network.

#conf t
(config)#track 1 interface gi 0/0/1 line-protocol
(config-track)#track 2 interface gi 0/0/2 line-protocol

CUBE-1

Interface Status Tracking Commands on CUBE-1Interface status tracking commands on CUBE-1.

CUBE-2

Interface Status Tracking Commands on CUBE-2Interface status tracking commands on CUBE-2.

Assign the Configured Tracks to Redundancy Group

Assign the configured tracks to group 1 by running these commands on both the CUBE routers:

#conf t
(config)#redundancy
(config-red)#
(config-red)#application redundancy
(config-red-app)#group 1
(config-red-app-grp)#track 1 shutdown
(config-red-app-grp)#track 2 shutdown

CUBE-1

Assign Tracked Interfaces to the Redundancy Group on CUBE-1Assign the tracked interfaces to the redundancy group on CUBE-1.

CUBE-2

Assign the Tracked Interfaces to the Redundancy Group on CUBE-2Assign the tracked interfaces to the redundancy group on CUBE-2.

Configuring the Virtual IP (VIP) on the LAN Side of Both CUBEs

These commands help configure the VIP for the LAN side of the CUBEs

(config)#interface GigabitEthernet0/0/1
(config-if)#description VLAN-1900 LAN side
(config-if)#ip address 10.88.11.184 255.255.255.0
(config-if)#redundancy rii 1
(config-if)#redundancy group 1 ip 10.88.11.185 exclusive

CUBE-1

LAN-Side Virtual IP (VIP) Configuration on CUBE-1LAN side Virtual IP (VIP) configuration on CUBE-1.

CUBE-2

LAN-Side Virtual IP (VIP) Configuration on CUBE-2LAN side Virtual IP (VIP) configuration on CUBE-2.

Configuring the Virtual IP (VIP) on the WAN Side of both CUBEs

These commands help configure the VIP for the WAN side of the CUBEs:

(config)#interface GigabitEthernet0/0/2
(config-if)#description VLAN-1967 WAN side
(config-if)#ip address 10.201.251.176 255.255.255.224
(config-if)#redundancy rii 2
(config-if)#redundancy group 1 ip 10.201.251.179 exclusive

CUBE-1

WAN Side Virtual IP (VIP) Configuration on CUBE-1WAN side Virtual IP (VIP) configuration on CUBE-1.

CUBE-2

WAN Side Virtual IP (VIP) Configuration on CUBE-2WAN side Virtual IP (VIP) configuration on CUBE-2.

Enable CUBE Redundancy

Enable CUBE Redundancy on both the routers by running these commands.

#conf t
Enter configuration commands, one per line. End with CNTL/Z.
(config)#
(config)#voice service voip
(conf-voi-serv)#redundancy-group 1
(conf-voi-serv)#
(conf-voi-serv)#exit
(config)#
(config)#ip rtcp report interval 3000
(config)#
(config)#gateway
(config-gateway)#media-inactivity-criteria all
(config-gateway)#
(config-gateway)#timer receive-rtcp 5
(config-gateway)#
(config-gateway)#timer receive-rtp 86400
(config-gateway)#

CUBE-1

Enable CUBE Redundancy on CUBE-1Enable CUBE Redundancy on CUBE-1.

CUBE-2

Enable CUBE Redundancy on CUBE-2Enable CUBE Redundancy on CUBE-2.

Save the Configuration and Reboot both CUBEs

After enabling redundancy, you must reload both routers. Before the reload, save the configurations.

CUBE-1

Save Configuration and Reboot CUBE-1Save the configuration and reboot the CUBE-1.

CUBE-2

Save Configuration and Reboot CUBE-2Save the configuration and reboot the CUBE-2.

Verify

You can validate the CUBE HA by running this show command:

#show redundancy application group 1

CUBE-1

Output of Command 'show redundancy application group 1' from CUBE-1Output of the command 'show redundancy application group 1' from CUBE-1.

CUBE-2

Output of Command 'show redundancy application group 1' from CUBE-2Output of the command 'show redundancy application group 1' from CUBE-2.

You can check the Virtual IP (VIP)'s status by running this show command:

#show redundancy application if-mgr group 1

For the active CUBE, the VIP status is shown as 'no shut' and the standby CUBE VIP status is shown as 'shut'.

CUBE-1

Output of Command 'show redundancy application if-mgr group 1' from CUBE-1Output of the command 'show redundancy application if-mgr group 1' from CUBE-1.

CUBE-2

Output of Command 'show redundancy application if-mgr group 1' from CUBE-2Output of the command 'show redundancy application if-mgr group 1' from CUBE-2.

Troubleshoot

There are currently no specific troubleshooting information available for this configuration.

Related Information

For more information about the CUBE HA, refer to these links:

Revision History

Revision Publish Date Comments
2.0
07-Aug-2026
Updated Introduction, spelling, grammar, inserted horizontal lines to separate sections for readability, updated alt text, fixed CCW errors.
1.0
07-Feb-2024
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • Ramesh Balakrishnan

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products