In this section:
Accomplish the following steps to switch to GRHA mode:
Stop the standby SBC application. On the SBC main screen, go to Administration > System Administration > Platform Management. The Platform and SBC Application Controls window is displayed. To stop the application, click Stop SBC Application in the status panel.
For details, refer to the section System Administration - Platform Management.
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.
On the standby server, execute the following command:
To set bond monitoring type to 'network-connect' and leader election algorithm type to 'enhanced':
> request system sbx2 setHaConfig bondMonitoring network-connect leaderElection enhanced
To set bond monitoring type to 'direct-connect' and retain current setting of leader election algorithm:
> request system sbx2 setHaConfig bondMonitoring direct-connect leaderElection currentValue
On the active server, execute the following command:
To set bond monitoring type to 'network-connect' and leader election algorithm type to 'enhanced':
> request system sbx1 setHaConfig bondMonitoring network-connect leaderElection enhanced
To set bond monitoring type to 'direct-connect' and retain current setting of leader election algorithm:
> request system sbx1 setHaConfig bondMonitoring direct-connect leaderElection currentValue
Start the standby server. Log on SBC application in EMA Platform Mode.
The standby server comes up and reconnects as standby with the GRHA mode enabled on both the machines.
Accomplish the following step to verify GRHA mode:
> show table system haConfig LEADER BOND SERVER NAME ELECTION MONITORING -------------------------------------------------- sbx1.eng.sonusnet.com standard direct-connect sbx2.eng.sonusnet.com standard direct-connect