Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e98a00a0c8613a801e016167f8a31a002b, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c862eadf5e0163170affe7001b, userName='null'}
JIRAIDAUTHCHOR-1074110133
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb2305708a00a0c8613a801e016167f8a31a002b, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9b903048a00a0c8613a801e016167f8a31a002b, userName='null'}

The following workflow defines the procedures for upgrading an SA NLL SWe Edge to an HA NLL SWe Edge in a RAMP scenario.


Workflow


Locating a Registered SA SBC SWe Edge on RAMP
Anchor
Locating a Registered SA SBC SWe Edge on RAMP
Locating a Registered SA SBC SWe Edge on RAMP

Start

  1. Log in to RAMP. For more information on logging in to RAMP, refer to Log onto the RAMP GUI.

  2. In the left navigation pane, go to Device Management > Devices. The Devices pane opens on the right.

  3. Locate the registered SA SBC SWe Edge you wish to remove.

DeconfiguringRAMP from SBC SWe Edge 
Anchor
Deconfiguring RAMP from SBC SWe Edge
Deconfiguring RAMP from SBC SWe Edge

Start

  1. Log in to your SA 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. The Node-Level Settings pane opens on the right.

  4. In the Ribbon Application Management Platform (RAMP) section, select No from the Connect to RAMP dropdown list.
    Image RemovedImage Added

  5. Click Apply. The following message opens.
    Image RemovedImage Added

    Info
    titleNote

    It takes about 3 minutes for the disconnection to be reflected on RAMP. Once you successfully disconnect your SWe Edge and RAMP, the Status of the SWe Edge shows Registered - Offline on RAMP.


Removing an SBC SWe Edge Node from RAMP
Anchor
Removing an SBC SWe Edge Node from RAMP
Removing an SBC SWe Edge Node from RAMP

Start

  1. Log in to RAMP.
  2. Unregister the SA SBC SWe Edge from RAMP. For more information, refer to Unregister Nodes.
  3. Remove the SA SBC SWe Edge node from RAMP. For more information, refer to Delete Nodes.


Installing an SBC SWe Edge on a Hypervisor 
Anchor
Installing an SBC SWe Edge on a Hypervisor
Installing an SBC SWe Edge on a Hypervisor

You must install a second SBC SWe Edge instance on VMware ESXi, KVM, or Hyper-V to upgrade an SA NLL SWe Edge to an HA NLL SWe Edge. For more information on installing an SBC SWe Edge instance on VMware ESXi. KVM, or Hyper-V, refer to:

...

Info
titleNote

The second SBC SWe Edge instance must be installed on the same supported hypervisor type as the SA SWe Edge or the first SBC SWe Edge.


Obtaining a Node-Locked License for an HA SWe Edge Pair
Anchor
Obtaining a Node-Locked License for an HA SWe Edge Pair
Obtaining a Node-Locked License for an HA SWe Edge Pair

You must obtain a new NLL with two SWe Edge IDs for your HA SWe Edge pair, one SWe Edge ID for the Active instance and the other for the Standby instance. You will receive an email that contains information on the two SWe Edge IDs after you purchase an NLL license from Ribbon Sales or through the Ribbon Partner Portal.

For more information on obtaining a new NLL with a SWe Edge ID, refer to Obtaining and Installing an SBC SWe Edge Production Node-Locked License.


Deploying High Availability on SBC SWe Edge 
Anchor
Deploying High Availability on SBC SWe Edge
Deploying High Availability on SBC SWe Edge

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


Workflow


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

Enabling HA on Active and Standby SWe Edge instances allows you to have increased system stability during mid-call failovers.

...

  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
    Image Added
    Image Removed

     

  5. Enter the Local IP Address, Local IP Netmask, and Remote IP Address in the In the Create HA Interface pop-up window, enter the local IP addresslocal IP netmask, and remote IP address

    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 Prerequisites section. 


    Create an HA Interface on the Instance
    Image RemovedImage Added


  6. You will be prompted with the below confirmation. Click on OK to continue.
    Image Removed
    Image Added
  7. Click OK. The instance will reboot for about 2 minutes until it displays the HA interface. 

    HA Interface on the Active Instance

    Image RemovedImage Added

  8. Confirm that HA is enabled on this instance. The HA role of the instance is seen in the right-hand corner of the WebUI.

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

    Image RemovedImage Added

  9. Repeat steps 1 to 7 in the second instance, becoming the Standby. 


Verify High Availability Status 
Anchor
Verify High Availability Status
Verify High Availability Status

Verifying HA pair status allows you to ensure that both Active and Standby SBC SWe Edge instances are correctly enabled.

...

  1. Log in to the Active HA 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.
    Image RemovedImage Added

  4. Repeat steps 1 to 3 on the Standby HA instance.
    Image RemovedImage Added


Install a Node-Locked License 
Anchor
Install a Node-Locked License
Install a Node-Locked License

Installing a Node-Locked license allows you to use SBC SWe Edge features. Licenses applied to the Active instance are replicated to the Standby instance. 

...

  1. Log in to the Active instance.

  2. Click the Settings tab at the top of the WebUI.

  3. In the left navigation window, go to System > Licensing > Install New License.
    Image RemovedImage Added

  4. Click Choose File and upload your license.

  5. Click Decode to see the details of the license.
    Image RemovedImage Added

  6. Click Apply. The newly added license can be seen in the Feature Licenses Decoded from the Provided License Key window. 


Managing an HA NLL SWe Edge through RAMP 
Anchor
Managing an HA NLL SWe Edge through RAMP
Managing an HA NLL SWe Edge through RAMP

Depending on your requirements, you may choose to manage your HA NLL SWe Edge with RAMP version 23.06 or later to track the statistics on the SWe Edge, such as the number of calls.The following workflow defines the procedures for managing HA NLL SWe Edge through RAMP. 

For more information on managing SBC SWe Edge through RAMP, refer to SBC SWe Edge Management via Ribbon Application Management Platform.


Workflow

StepAction
1Upgrade an SA Node-Locked Licensed Connect an HA NLL SWe Edge to an HA Node-Locked Licensed SWe Edge in a RAMP Scenario
2Verify the Registration of the SBC SWe Edge HA Pair on RAMP


Connect an HA NLL SWe Edge to RAMP 
Anchor
Connect an HA NLL SWe Edge to RAMP
Connect an HA NLL SWe Edge to RAMP

Connecting an HA NLL SWe Edge to RAMP allows you to register the HA NLL SWe Edge with RAMP and associate NLL licenses with your SBC SWe Edge HA pair.

...

  1. Log in to the Active instance.
  2. Click the Settings tab at the top of the WebUI.
  3. In the left navigation pane, go to System > Node-Level Settings. The Node-Level Settings window opens on the right.
  4. In the Ribbon Application Management Platform (RAMP) section, select Yesfor to Connect to RAMP.
    Image RemovedImage Added

  5. Complete the following fields:
    • Management Address
    • Management ID
     HA Pair Name


    Note
    titleCaution

    The HA pair name must be unique within a management domain and remain the same. You cannot modify the HA pair name once you successfully pair the Active and Standby SWe Edge instances.


    RAMP Parameter

    ParameterDescription
    HA Pair Name

    Enter the name of the Active and Standby instance instances to be paired. 

    The HA pair name allows RAMP to identify the Active and Standby SWe Edge HA instances as a single network entity

    Image RemovedImage Added


  6. Click Apply. The following message opens. 
    Image RemovedImage Added

  7. Click OK. The following message opens.
    Image RemovedImage Added

    Info
    titleNote

    It takes about 2 minutes for RAMP to detect the SBC SWe Edge HA pair. 

    Once the configuration is successful, the RAMP section displays as follows: 
    Image RemovedImage Added

    Info
    titleNote

    RAMP Connection displays as Up if If the SWe Edge instance is successfully connected to the RAMP server successfully, RAMP Connection displays as Up. If you use NLL licensing, RAMP Online Licensing displays as None.

     

  8. Repeat steps 1 to 7 in the Standby instance.

    Info
    titleNote

    You must use the same HA pair name as the one you used for configuring the Active instance.


...


Verify the Registration of the HA NLL SWe Edge on RAMP 
Anchor
Verify the Registration of the HA NLL SWe Edge on RAMP
Verify the Registration of the HA NLL SWe Edge on RAMP

Verifying the Registration registration of the HA NLL SWe Edge on RAMP ensures that you can manage the HA NLL SWe Edge it through RAMP. The SBC SWe Edge automatically registers with RAMP after you complete Upgrade an SA Node-Locked Licensed Connect an HA NLL SWe Edge to an HA Node-Locked Licensed SWe Edge in a RAMP Scenario.

For more information on registering an SBC SWe Edge HA pair with RAMP, refer to Register an SBC Edge Device.

...