Cisco Systems SBC-111 User Manual
Implementing SBC Redundancy (High
Availability)
SBC fault tolerant redundancy is based on a 1:1 paired protection model. For each active service card running
with the SBC, there should be another service card providing failure protection (that is, standby). The same
services must be provisioned on both cards (one as the primary card, one as the standby card); in this instance,
the service cards are described as “paired”.
From a Cisco IOX XR system perspective, service cards are always running in active mode. SBC services
running on these cards, however, run as either a primary service or standby service.
Given that SBC functionality is split among two logical service entities—the signaling border element (SBE)
service and data border element (DBE) service—these services run on Cisco IOX XR service cards as
follows:
• In the Unified model, SBE and DBE run on the same service card. In this case, SBE and DBE
services are implemented as a single Cisco IOS XR process.
• In the Distributed model, SBE and DBE services run as separate Cisco IOX XR processes (and there
may be one or more distributed DBE(s) per SBE). When running in this mode:
–
SBE and DBE services may be provisioned on different cards within the same physical device
to distribute the processing load across available service cards.
–
SBE and DBE may be located on different physical devices.
Where there is no standby service card available, a software failure results in a restart of the primary SBC
process. If this succeeds, the SBC process loses all call states, but management and configuration information
stored in SysDb is recovered and re-applied on restart.
When there is a standby SBC provisioned, the active SBC replicates the state to the standby to provide hot
standby support. The SBC process is fate shared with the Media Packet forwarder component; if one
component restarts, the other component will restart.
Note For a complete description of commands used in this chapter, refer to the Cisco IOS XR Session Border
Controller Command Reference. To locate documentation for other commands that appear in this
chapter, use the command reference master index, or search online.
Feature History for Implementing SBC Redundancy
Release Modification
Release 3.3.0 This feature was introduced on the Cisco XR 12000 Series Router.
Cisco IOS XR Session Border Controller Configuration Guide
SBC-111
Implementing SBC Redundancy (High Availability)
Contents
Contents
• Prerequisites for Implementing Redundancy, page SBC-112
• Information About Implementing Redundancy, page SBC-112
• How to Implement Redundancy, page SBC-112
• Configuration Examples of Implementing a Redundancy, page SBC-116
• Additional References, page SBC-117
• Related Command Summary, page SBC-118
Prerequisites for Implementing Redundancy
The following prerequisites are required to implement SBC redundancy:
• You must be in a user group associated with a task group that includes the proper task IDs for SBC
commands being used. For detailed information about user groups and task IDs, see the defined task
ID required per command in the Cisco IOS XR Session Border Controller Command Reference.
• You must install and activate the package installation envelope (PIE) for the SBC software.
For detailed information about PIE installation, refer to the Upgrading and Managing Cisco IOS XR
Software module in the Cisco IOS XR Getting Started Guide.
• Before implementing interworking SBC redundancy, the SBC must already be created. See the
procedures described in the “SBC Configuration Prerequisites” module.
Information About Implementing Redundancy
SBC fault tolerance is based on a 1:1 paired-protection model. For each service card running active SBC
components, there can be one service card providing failure protection. The same services must be
provisioned on both cards (one as the primary card, one as the standby card), and the service cards are then
said to be paired. Although from an Cisco IOX XR system perspective, service cards are always running in
active mode, SBC services running on these cards run as either the primary service or the standby service.
How to Implement Redundancy
Redundancy configurations are described in the following sections:
• Configuring a Redundancy
• Deleting a Redundancy
SBC-112
Cisco IOS XR Session Border Controller Configuration Guide
Implementing SBC Redundancy (High Availability)
Configuring a Redundancy
This task configures a redundancy.
SUMMARY STEPS
1. configure
2. sbc service-name
3. service-location preferred-active node-id preferred-standby node-id
4. commit
5. exit
6. interface sbcnumber
7. service-location preferred-active node-id [preferred-standby node-id]
8. commit
9. end
10. show services redundancy
How to Implement Redundancy
DETAILED STEPS
Command or Action Purpose
Step 1
configure
Example:
RP/0/0/CPU0:router# configure
Step 2
sbc service-name
Example:
RP/0/0/CPU0:router(config)# sbc mysbc
RP/0/0/CPU0:router(config-sbc)#
Step 3
service-location preferred-active node-id
[preferred standby node-id]
Example:
RP/0/0/CPU0:router(config-sbc)#
preferred-active 0/2/CPU0 preferred-standby
0/4/CPU0
Step 4
commit
Example:
RP/0/0/CPU0:router(config-sbc)# commit
Step 5
exit
Enables global configuration mode.
Enters the mode of an SBC service.
• Use the service-name argument to define the name of
the service.
Enables a service card to run SBC function as a primary, and
optionally, secondary location.
Saves configuration changes. Use the commit command to
save the configuration changes to the running configuration
file and remain within the configuration session.
Exits sbc mode to config mode.
Example:
RP/0/0/CPU0:router(config-sbc)# exit
RP/0/0/CPU0:router(config)#
Cisco IOS XR Session Border Controller Configuration Guide
SBC-113
Loading...