Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 2

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=8a00a02355cd1c2f0155cd26c8a10148, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb1f0553, userName='null'}

Contents

Panel

Table of Contents

Introduction

You can optionally deploy a pair of Edge 8300 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 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 a pair of 8300 devices that solely support SIP to SIP calls. Additional limitations apply. See Limitations Overview of High Availability#Limitations.

Refer to Workflow for Initial Setup - High Availability for installation and HA activation instructions.

Architecture

In an Edge 8000 High Availability setup, two Edge 8300 devices share the responsibility of the HA function. Each device’s gigabit Ethernet 5 (ge5) port (internal Bridge 4, SBC SWe Edge logical interface Ethernet 3) 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 diagram).

During the initial setup, the Standby device (8300-2) 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). When a failover occurs, the HA function assigns the Eth1 and Eth3 addresses from the (former) Active instance to the Standby instance, and the Standby instance acts as the new Active instance to process calls.

The following diagram depicts a typical HA setup. Your network administrator will assign specific IP addresses to suit the needs of your particular network topology. The physical ports associated with the Edge 8300 Bridge 1 assignments supporting the LAN network can be any of the available ge1 through ge8 ports, exclusive of the port used for the HA interface (shown as ge6 in the diagram). Likewise, the physical port associated with the Edge 8300 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.

HA Architecture Diagram

Limitations 

The following limitations apply for

Spacevars
0product
HA functionality:

  • Deployment
    • Spacevars
      0company
      offers HA for Edge 8300 devices only.
      Spacevars
      0company
      does not support HA on 8100 devices.
    • 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 only applies to SIP to SIP calls (excludes analog)      .
    • HA ports connecting two devices are only allowed on the same subnet.
    • The HA interface requires a single back-to-back Ethernet cable connecting the HA ports of the two 8300 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.
    • Spacevars
      0product
       devices do not support card redundancy or port redundancy.
  • 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 8300 does not support card redundancy or port redundancy.

Licenses

Multiexcerpt include
SpaceWithExcerptUXDOC121
MultiExcerptNameHA SKU
PageWithExcerptUXDOC121:Licenses