You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Back to Table of Contents

In this section:

Related articles:

Switching to GRHA Mode

Accomplish the following steps to switch to GRHA mode:

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

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

    # service sbx stop


    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.


  3. On the standby server, execute the following command:
     

    # geoRedundHa.sh enable


  4. On the active server, execute the following command:
     

    # geoRedundHa.sh enable



  5. Start the standby server.

    # service sbx start

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

Verifying GRHA Mode

Accomplish the following steps to verify GRHA mode:

  1. As user root, execute the following command:

    # service sbxbond status


    The output of this command shows that an ARP address is in use.
    For example,

    ***** 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

     

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

    Wed Feb 10 12:14:47.994 2016 (CE_Node1.3779 : GMS.LEA. NA.00030 : CRITIC) SLEA: Custom leader election algorithm ENABLED


  • No labels