Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85b00e8, userName='null'}
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cca00892, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c749000c, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ccd408f3, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ccd408f3, userName='null'}

Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

...

Panel

In this section:

Table of Contents
maxLevel4

...

width50%
Info
iconfalse

Related articles:

...

Switching to GRHA Mode

Info
titleNote

This feature is not configurable during software installation nor is it changeable during an upgrade.

Include Page
GRHA_not_in_SWe_Cloud
GRHA_not_in_SWe_Cloud


Accomplish the following steps to switch to GRHA mode:

  1. Upgrade the SBC application either using LSWU or Platform Manager.

As user root, stop the standby server using the following command:

Code Block
languagenone
# service sbx stop
Note

The services on standby SBC server must be stopped before switching to GRHA mode since the switch to GRHA mode causes a temporary HA link outage. The script will verify the state of the servers and make the necessary changes.


  1. From the CLI command prompt, perform one of the steps below, depending on your configuration. For example, in SBC Core, set bond monitoring type to network-connect and leader election algorithm type to enhanced:

    Code Block
    > request system admin sbx1 setHaConfig bondMonitoring network-connect leaderElection enhanced

Verifying GRHA Mode

Accomplish the following step to verify GRHA mode:

Code Block
languagenone
> show table system haConfig 
                        LEADER     BOND 
SERVER NAME             ELECTION   MONITORING 
--------------------------------------------------
sbx1.eng.sonusnet.com   enhanced   network-connect
sbx2.eng.sonusnet.com   enhanced   network-connect

Switching Out of the GRHA Mode

To set bond monitoring type to direct-connect and leader election algorithm type to standard, enter the following command:

Code Block
> request system admin sbx1 setHaConfig bondMonitoring direct-connect leaderElection standard

 

On the standby server, execute the following command:
 

Code Block
languagenone
# geoRedundHa.sh enable

On the active server, execute the following command:
 

Code Block
languagenone
# geoRedundHa.sh enable

...

Code Block
languagenone
# service sbx start
Note

The standby server comes up and reconnects as standby with the GRHA mode enabled on both the machines.

Verifying GRHA Mode

Accomplish the following

...

step to verify non-GRHA mode

...

:

Code Block
languagenone

...

# service sbxbond status

...

Code Block
languagenone
***** pbond0 status *****
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
 
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
ARP Polling Interval (ms): 100
ARP IP target/s (n.n.n.n form): 169.254.66.8

 

> show table system haConfig 
                        LEADER     BOND 
SERVER NAME             ELECTION   MONITORING 
--------------------------------------------------
sbx1.eng.sonusnet.com   standard   direct-connect
sbx2.eng.sonusnet.com   standard   direct-connect

Pagebreak

Checking the openclovis sys.latest log.
After switching to GRHA mode and reconnecting to SBC, a log entry appears.
For example,

...

languagenone

...