Standby Mode for HA Nodes

When performing hardware maintenance on the Acme Packet 6300/6350, it is best to minimize any risk of interrupting network traffic or losing data. If the Acme Packet 6300/6350 is configured as an HA node, you should only work on the Acme Packet 6300/6350 that is in standby mode.

There are two ways to determine the HA state of each Acme Packet 6300/6350 in an HA pair.

1. If you are in the same physical location as the Acme Packet 6300/6350, you can view the graphic display on the front panel. The display will indicate the HA state. There is no (S) designation for an active system, but there is for a standby system.
2. If you are not in the same physical location as the Acme Packet 6300/6350, you can use the ACLI show health command. The output of this command indicates the current HA state of the Acme Packet 6300/6350.

   Once you have determined that the Acme Packet 6300/6350 due for maintenance is in standby mode, you can continue with the appropriate procedures to replace a part.

   If you need to perform maintenance on the active Acme Packet 6300/6350, you need to manually force the two Acme Packet 6300/6350s to switch HA states. Performing a switchover forces the currently active Acme Packet 6300/6350 to standby mode while the current standby Acme Packet 6300/6350 will assume all traffic processing and forwarding as the active system.

   Note:

   This procedure is only applicable to Acme Packet 6300/6350 in an HA deployment.

   To force a Acme Packet 6300/6350 into the standby HA state:

3. Confirm that the relevant systems on SBC1 and SBC2 are synchronized with the show health command. Type show health and press Enter on each system.

   system-1# show health
   
                  Media Synchronized            true
                  SIP Synchronized              true
                  REC Synchronized              disabled
                  MGCP Synchronized             disabled
                  H248 Synchronized             disabled
                  XSERV Synchronized            disabled
                  Config Synchronized           true
                  Collect Synchronized          disabled
                  RADIUS CDR  Synchronized      true
                  Rotated CDRs Synchronized     true
                  IPSEC Synchronized            true
                  Iked Synchronized             disabled
                  TSCF Synchronized             disabled
                  Active Peer Address           
   
   Redundancy Protocol Process (v3):
                  State                                                   Active
                  Health                                                100
                  Lowest Local Address                     169.254.1.2:9090
                  1 peer(s) on 2 socket(s):
                  system-2: v3, Standby, health=100, max silence=1050
                         last received from 169.254.1.1 on wancom1:0
   
   
   system-2# show health
                  Media Synchronized            true
                  SIP Synchronized              true
                  REC Synchronized              disabled
                  MGCP Synchronized             disabled
                  H248 Synchronized             disabled
                  XSERV Synchronized            disabled
                  Config Synchronized           true
                  Collect Synchronized          disabled
                  RADIUS CDR  Synchronized      true
                  Rotated CDRs Synchronized     true
                  IPSEC Synchronized            true
                  Iked Synchronized             disabled
                  TSCF Synchronized             disabled
                  Active Peer Address           169.254.2.2
   
   Redundancy Protocol Process (v3):
                  State                                                   Standby
                  Health                                                100
                  Lowest Local Address                     169.254.1.1:9090
                  1 peer(s) on 2 socket(s):
                  system-1: v3, Active, health=100, max silence=1050
                         last received from 169.254.2.2 on wancom2:0
   

4. Confirm that SBC1 and SBC2’s current configurations match by typing display-current-cfg-version and press Enter at the ACLI prompt.

   NETNETSBC1# display-current-cfg-version
   Current configuration version is 5
   NETNETSBC1#
   NETNETSBC2# display-current-cfg-version
   Current configuration version is 5
   NETNETSBC2#

   Note:

   While the two current configuration version numbers on the two systems MUST match each other, they do not have to match the shared running configuration version.
5. Confirm that the running configuration of SBC1 and SBC2 match by typing display-running-cfg-version and pressing Enter at the ACLI prompt.

   NETNETSBC1# display-running-cfg-version
   Running configuration version is 5
   NETNETSBC1#
   NETNETSBC2# display-running-cfg-version
   Running configuration version is 5
   NETNETSBC2#

   Note:

   While the two running configuration version numbers on the two systems MUST match each other, they do not have to match the shared current configuration version.
6. Initiate a switchover on SBC1 by typing notify berpd force and pressing Enter at the ACLI prompt.

   NETNETSBC1# notify berpd force

7. Wait for SBC2 to transition to the standby state. Confirm that SBC2 is in the standby state by typing show health and pressing Enter at the ACLI prompt.

   NETNETSBC2# show health

   Refer to the Upgrade section of the Maintenance and Troubleshooting Guide (400-0063-40A) for more information.