Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c8613a801e016167f8a31a002b, userName='null'}
REV5UserResourceIdentifier{userKey=8a00a0c85f4199b1015f7ea6e836000d, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85f4199b1015f7ea6e836000d, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd8b0a598a00a0c85f4199b1015f7ea6e836000d, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd8b0a598a00a0c85f4199b1015f7ea6e836000d, userName='null'}

Contents

Panel

Table of Contents

Introduction

You can optionally deploy a pair of

Spacevars
0product
devices for High Availability. High Availability (HA) protects SIP to SIP calls using
Spacevars
0product4
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

Spacevars
0product
High Availability setup, two
Spacevars
0product
 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

Spacevars
0product
Physical Port


Internal Bridge

Associated SBC SWe Edge Logical Interface
LAN side of the networkge1
br1Ethernet 1
Device managementge7
br2Admin
WAN side of the networkge5
br4 Ethernet 3
HA monitoring between the two devicesge6
br5High Availability

Once HA is enabledDuring the initial setup, the Standby device (8300-2 in the example) receives its own Eth1 and Eth3 IP address assignments (IP Assign Method: Static). 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

Spacevars
0product
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
Spacevars
0product
 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
Spacevars
0product
 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
iconfalse
titleAttention

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

Spacevars
0product
HA functionality:

  • Deployment
    • HA can only be provisioned at the time of initial installation.
      Spacevars
      0company
      does not offer a path for stand-alone (SA) to HA conversion.
    • High Availability through a pair of
      Spacevars
      0product
       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
      Spacevars
      0product
       devices.
    • DHCP on the HA Interface is not supported.
    • Geo Redundancy is not supported. The two
      Spacevars
      0product
       devices must be co-located.
    • Spacevars
      0product
       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.
    • Spacevars
      0product
       devices do not support redundancy at the card redundancy or port redundancylevel.
  • Data Replication

Multiexcerpt include
SpaceWithExcerptUXDOC121
MultiExcerptNameData Replication
PageWithExcerptUXDOC121:Deploying High Availability on the SBC SWe Edge

  • Call Features
    • Multiexcerpt include
      SpaceWithExcerptUXDOC121
      MultiExcerptNameCall Features - first bullet
      PageWithExcerptUXDOC121:Deploying High Availability on the SBC SWe Edge
  • Others
    • Multiexcerpt include
      SpaceWithExcerptUXDOC121
      MultiExcerptNameLimitations - Others - bullet A
      PageWithExcerptUXDOC121:Deploying High Availability on the SBC SWe Edge
    • Multiexcerpt include
      SpaceWithExcerptUXDOC121
      MultiExcerptNameLimitations - Others - bullet B
      PageWithExcerptUXDOC121:Deploying High Availability on the SBC SWe Edge
      The
      Edge
      Spacevars
      0product
       does not support card redundancy or port redundancy.

Licenses

Multiexcerpt include
SpaceWithExcerptUXDOC121
MultiExcerptNameHA SKU
PageWithExcerptUXDOC121:Licenses