Contents
Introduction
You can optionally deploy a pair of devices for High Availability. High Availability (HA) protects SIP to SIP calls using HA functionality. HA functionality enhances resiliency by offering Active and Standby SWe Edge instances. When the Active instance fails during a call, the Standby instance takes over the call management to maintain the call.
The Active and Standby SWe Edge instances operate using a single HA license. At the time of initial setup, you install the HA license on the Active instance. Once accepted, the HA system replicates the information to the Standby instance.
Provisioning for HA can only be done at the time of initial installation and only for on a pair of devices that solely support SIP to SIP calls. Additional limitations apply. See Limitations.
For installation and HA activation instructions, refer to Workflow for Initial Setup - High Availability.
Architecture
In an High Availability setup, two devices share the responsibility of supporting the HA function. Each device’s gigabit Ethernet 5 (ge5) port (internal Bridge 4, SBC SWe Edge logical interface Ethernet 3 in the following example) serves the WAN side of the network. The ge1 port (internal Bridge 1, SBC SWe Edge logical interface Ethernet 1) serves the LAN side of the network. Each device has a unique IP address for its management connection (Admin port ge7). The two devices physically connect through a back-to-back Ethernet connection of their corresponding HA interface ports (ge6 in the following example).device is assigned with corresponding Ethernet interfaces to serve the requirements of the deployment, as shown in the following table:
HA Deployment: Typical Interface Assignments
Ethernet Interface Requirement | |
| | Associated SBC SWe Edge Logical Interface |
---|
LAN side of the network | ge1 |
| br1 | Ethernet 1 |
Device management | ge7 |
| br2 | Admin |
WAN side of the network | ge5 |
| br4 | Ethernet 3 |
HA monitoring between the two devices | ge6 |
| br5 | High Availability |
Once HA is enabledDuring the initial setup, the Standby and Active devices, shown as 8300-1 and 8300-2 in the following diagram, each receive their own Eth1 and Eth3 IP assignments using the static IP assignment method. (The HA IP addresses must be at least three numbers apart. Example: 10.10.10.50 and 10.10.10.21.) Once you enable HA, the Standby instance monitors the Active instance through the HA interface (port ge6)High Availability interface. When a failover occurs, the HA function "floats" (assigns) the Eth1 Ethernet 1 and Eth3 Ethernet 3 addresses from the (former) Active instance to the Standby instance, and the Standby instance acts as the new Active instance to process calls.. To the outside world, no change of the
device is discernible other than a change in the MAC address of the (new) Active device. The following diagram depicts the architecture of a typical HA setupdeployment. Note that:
- Your network administrator will
assign specific IP addresses to suit the needs of your particular network topology. The physical ports associated with the Bridge 1 assignments supporting the LAN network - provide unique IP addresses for the bridge interfaces and the SWe Edge logical interfaces. (The Gigabit Ethernet ports themselves do not receive IP addresses. Rather, each port is assigned to be a member of a bridge.)
- The physical port assignments for the LAN, management, and WAN services can be any of the available
ge1 through ge8 - Gigabit Ethernet ports or SFP+ ports, exclusive of the port used for the
HA interface (shown as ge6 in the example). Likewise, the physical port associated with the Bridge 4 assignment supporting the WAN network can be any of the available ge1 through ge8 ports, exclusive of the port being used for the HA interface, or one of the available SFP ports, sfp9 or sfp10.- High Availability interface.
Info |
---|
|
The High Availability (HA) interfaces must have static IPv4 addresses on the same subnet and at least three addresses apart. Example: 10.10.10.41 and 10.10.10.44. |
HA Architecture: Deployment Example
Limitations
The following limitations apply for to HA functionality:
- Deployment
- HA can only be provisioned at the time of initial installation. does not offer a path for stand-alone (SA) to HA conversion.
- High Availability through a pair of devices HA only applies to SIP to SIP calls (excludes analog). Analog calls are excluded.
- HA ports connecting two devices are only allowed on the same subnet.supports only static IP addressing on the Ethernet Media (packet) and High Availability ports, not DHCP. (On the Admin port, The HA interface requires a single back-to-back Ethernet cable connecting the HA ports of the two devices.
- DHCP on the HA Interface is not supported.
- Geo Redundancy is not supported. The two devices must be co-located.
- devices only support floating IPs on the packet interfaces, not the HA or Admin interfaces.
- HA supports static and DHCP addressing.)
- The devices' HA interfaces must be static IPv4 addresses on the same subnet at least three addresses apart.
- HA supports floating IP addresses only on the Ethernet Media (packet) interfaces, not on the Admin or High Availability interfaces. (The HA function automatically assigns, or "floats," the packet interfaces of the Active device to the Standby device when a failover occurs.)
- HA does not support Geo Redundancy. The two HA devices must be on the same subnet.
- devices do not support redundancy at the card redundancy or port redundancylevel.
- Data Replication
Multiexcerpt include |
---|
SpaceWithExcerpt | UXDOC121 |
---|
MultiExcerptName | Data Replication |
---|
PageWithExcerpt | UXDOC121:Deploying High Availability on the SBC SWe Edge |
---|
|
- Call Features
Multiexcerpt include |
---|
SpaceWithExcerpt | UXDOC121 |
---|
MultiExcerptName | Call Features - first bullet |
---|
PageWithExcerpt | UXDOC121:Deploying High Availability on the SBC SWe Edge |
---|
|
- Others
Multiexcerpt include |
---|
SpaceWithExcerpt | UXDOC121 |
---|
MultiExcerptName | Limitations - Others - bullet A |
---|
PageWithExcerpt | UXDOC121:Deploying High Availability on the SBC SWe Edge |
---|
|
Multiexcerpt include |
---|
SpaceWithExcerpt | UXDOC121 |
---|
MultiExcerptName | Limitations - Others - bullet B |
---|
PageWithExcerpt | UXDOC121:Deploying High Availability on the SBC SWe Edge |
---|
|
The Edge does not support card redundancy or port redundancy.
Licenses
Multiexcerpt include |
---|
SpaceWithExcerpt | UXDOC121 |
---|
MultiExcerptName | HA SKU |
---|
PageWithExcerpt | UXDOC121:Licenses |
---|
|