Versions Compared

Old Version 5

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
AUTH2UserResourceIdentifier{userKey=8a00a0c8613a801e016167f8a31a002b, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c862eadf5e0163170affe7001b, userName='null'}
JIRAIDAUTHCHOR-10133
REV5UserResourceIdentifier{userKey=8a00a0c862eadf5e0163170affe7001b, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85f4199b1015f7ea6e836000d, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c85f4199b1015f7ea6e836000d, userName='null'}

Hide

ATTENTION: Content on this page is shared with the Edge 8000 product.


The following workflow defines the procedures to deploy for deploying HA on an SBC SWe Edge.

Prerequisites 

Anchor
Prerequisites
Prerequisites

Before you begin, make sure you have the following:

  • Hardware Requirements
    • Two SBC SWe Edge instances ESXi host with
      • a minimum Minimum of 4 vCPUs
      • a minimum Minimum of 4 GB of RAM
      • a minimum Minimum of 3 to a maximum of 5 virtual network interface cards (NICs):  
        • 1 One for the Management port,
        • 1 One or 3 three for Media/Packet ports

        • 1 One for the HA port

          Info
          titleNote

          Regardless of whether Whether you choose to use 3 or 5 virtual NICs, the last Media/Packet port is converted to an HA port. You cannot configure the HA port for signaling and media call handling, as it is used for such purposes as fault detections detection and storing and retrieving data from the database store.


      • all 5 Five network interfaces (mgt0, pkt0, pkt1, pkt2, pkt3) mapped through network configuration


  • Software Requirement
    • HA supported version is installed on the system, for example, release 12.1.


  • Ethernet Interface Requirements 

    Hide

    ATTENTIONAttention: Content on this page is shared with the Edge 8000 product using the MultiExcerpt macro here and the MultiExcerpt Include macro there.


Multiexcerpt
MultiExcerptNameEthernet IF Requirements - list
    a dedicated
  • Dedicated HA port
  • Media (packet) ports
    • a
  • Management port
Interface TypeLimitations and Characteristics
Dedicated HA portOnce you enable the HA feature on your SBC SWe Edge, you can only configure the static IP addresses on the Active and Standby instances of the HA port, which must be on the same subnet.
Media (packet) portsOnly static IP address are supported in SBC SWe Edge release 12.1.
Management portYou can use either static or DHCP IP addresses and configure different IP addresses on both the Active and the Standby instances.



Workflow

Step

Action

1Enabling High Availability an an SBC on Active and Standby SWe Edge Instances
2Enabling Verifying High Availability an an SBC SWe EdgeStatus


Enabling High Availability on Active and Standby SWe Edge Instances 
Anchor
Enabling High Availability on Active and Standby SWe Edge Instances
Enabling High Availability on Active and Standby SWe Edge Instances

Enable HA on the Active and Standby SWe Edge instances to increase the stability of the system during mid-call failovers.

Hide

ATTENTION: Content on this page is shared with the Edge 8000 product using the MultiExcerpt macro here and the MultiExcerpt Include macro there.


Multiexcerpt
MultiExcerptNameEnabling High Availability on Active and Standby SWe Edge Instances

Start

  1. Log in to your SBC SWe Edge instance. 
  2. Click the Settings tab at the top of the WebUI.
  3. In the left navigation pane, go to System > Node-level Settings.
  4. Click Enable HA.

    Enable HA on SBC SWe Edge Instance


  5. Enter the Local IP Address, Local IP Netmask, and Remote IP Address in the Create HA Interface pop-up window. 

    Info
    titleNote

    The Local IP is the HA IP address of the instance you are currently in. The Remote IP is the other HA IP address of the other instance, as mentioned in the the Enabling High Availability an an SBC SWe EdgePrerequisites section. 


    Create HA Interface on the Instance


  6. Click OK. The following message opens.


  7. Click OK. The following message opens.

    Info
    titleNote

    It takes about 2 minutes for the instance to reboot. The system takes you back to the log in page once the reboot is complete.


  8. Log in to your SBC SWe Edge instance.
  9. Click the Settings tab at the top of the WebUI.
  10. In the left navigation pane, go to Networking Interfaces > Logical Interfaces.

    HA Interface on the Active Instance

  11. Confirm that HA is enabled on this instance. The HA role of the instance is seen at the right hand corner of the WebUI.

    The HA Role is Shown at the Right-hand Corner of the Instance WebUI

  12. Repeat steps 1 to 11 in the second instance, which will become the Standby.


Verifying High Availability Status 
Anchor
Verifying High Availability Status
Verifying High Availability Status

Verify the HA pair status to ensure that both the Active and the Standby SBC SWe Edge instances are properly enabled.

Hide

ATTENTION: Content on this page is shared with the Edge 8000 product using the MultiExcerpt macro here and the MultiExcerpt Include macro there.


Multiexcerpt
MultiExcerptNameVerifying High Availability Status

Start

  1. Log in to the Active instance. 
  2. Click the Diagnostics tab at the top of the WebUI.
  3. In the left navigation pane, go to High Availability > HA Status Details to view the HA status.


  4. Repeat steps 1 to 3 on the Standby instance.