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

Contents

Panel

Table of Contents


Internal_display_only

Introduction

You can optionally deploy a pair of Edge 8300 of 

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

Spacevars
0product
devices that solely support SIP to SIP calls. Additional limitations apply. See Overview of High Availability#Limitations Limitations.

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

Architecture

In an Edge 8000

Spacevars
0product
High Availability setup, two Edge 8300
Spacevars
0product
 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).device is assigned with corresponding Ethernet interfaces to serve the requirements of the deployment, as shown in the following table:

HA Interface Assignments: Typical Deployment

Ethernet Interface Requirement

Spacevars
0product
Physical Port

Internal BridgeSWe Edge Logical Interface
LAN side of the networkge1br1Ethernet 1
WAN side of the networkge5br4Ethernet 3
HA monitoring between the two devicesge6br5High Availability

Once HA is enabledDuring 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)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 which 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 topology of a typical HA setupdeployment. Note that:

  • Your network administrator will
assign specific
  • provide unique 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
  • for the bridge interfaces (br4, br5, and br1) and the 
    Spacevars
    0product4
    logical interfaces (SBC Eth 3, SBC HA, and SBC Eth1). 
  • The physical port assignments for the LAN and WAN services can be any of the available
ge1 through ge8 ports
  • Gigabit Ethernet ports, ge1-8, or SFP+ ports, SFP9 or SFP10, exclusive of the port used for the
HA
  • High Availability interface. (Note that the ports do not receive IP addresses. Rather, you simply assign a port to be a member of a bridge.)

HA Deployment Example (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

Image Modified

Limitations 

The following limitations apply for to

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 HA 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.
    • . Analog calls are excluded.
    • HA supports only static IP addressing on the Ethernet Media (packet) and High Availability ports, not DHCP.
    • The HA interface IP addresses must be static IPv4 addresses on the same subnet at least three addresses apart. Example: 10.10.10.41 and 10.10.10.44.
    • HA supports floating IP addresses only on the Ethernet Media (packet) interfaces, not on the High Availability interface. (The HA function automatically assigns, or "floats," the media 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 only support floating IPs on the packet interfaces, not the HA or Admin interfaces.
    • Spacevars
      0product
       devices do not support redundancy at the card redundancy or port redundancylevel.
  • Data Replication

Multiexcerpt include
SpaceWithExcerptUXDOC121UXDOC122
MultiExcerptNameData Replication
PageWithExcerptUXDOC121UXDOC122:Deploying High Availability on the SBC SWe Edge

  • Call Features
    • Multiexcerpt include
      SpaceWithExcerptUXDOC121UXDOC122
      MultiExcerptNameCall Features - first bullet
      PageWithExcerptUXDOC121UXDOC122:Deploying High Availability on the SBC SWe Edge
  • Others
    • Multiexcerpt include
      SpaceWithExcerptUXDOC121UXDOC122
      MultiExcerptNameLimitations - Others - bullet A
      PageWithExcerptUXDOC121UXDOC122:Deploying High Availability on the SBC SWe Edge
    • Multiexcerpt include
      SpaceWithExcerptUXDOC121UXDOC122
      MultiExcerptNameLimitations - Others - bullet B
      PageWithExcerptUXDOC121UXDOC122:Deploying High Availability on the SBC SWe Edge
    • The Edge 8300 does not support card redundancy or port redundancy.

Licenses

Multiexcerpt include
SpaceWithExcerptUXDOC121UXDOC122
MultiExcerptNameHA SKU
PageWithExcerptUXDOC121UXDOC122:Licenses