Standby Mode for HA Nodes

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

Use the show health command to determine the state of your Acme Packet 6400. If the Acme Packet 6400 due for maintenance is in standby mode, you can continue with the appropriate procedures to replace a part.

If the Acme Packet 6400 due for maintenance is in active mode, you must manually force a switchover. Performing a switchover forces the currently active Acme Packet 6400 to standby mode while the current standby Acme Packet 6400 will assume all traffic processing and forwarding as the active system.

Note:

This procedure is only applicable to Acme Packet 6400 in an HA deployment.
  1. Use the show health command to identify which system is the active and which is the standby.
    SBC1# show health
              Media Synchronized           false
              SIP Synchronized             false
              REC Synchronized             false
              XSERV Synchronized           disabled
              Config Synchronized          disabled
              Collect Synchronized         false
              RADIUS CDR Synchronized      false
              Rotated CDRs Synchronized    false
              IPSEC Synchronized           disabled
              Iked Synchronized            false
              Lbpd Synchronized            disabled
              tCCD Synchronized            disabled
              Service Health Synchronized  false
              License Monitor 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
    SBC2# show health
              Media Synchronized           false
              SIP Synchronized             false
              REC Synchronized             false
              XSERV Synchronized           disabled
              Config Synchronized          disabled
              Collect Synchronized         false
              RADIUS CDR Synchronized      false
              Rotated CDRs Synchronized    false
              IPSEC Synchronized           disabled
              Iked Synchronized            false
              Lbpd Synchronized            disabled
              tCCD Synchronized            disabled
              Service Health Synchronized  false
              License Monitor 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
  2. Confirm that SBC1 and SBC2’s current configurations match by typing display-current-cfg-version and press Enter at the ACLI prompt.
    SBC1# display-current-cfg-version
    Current configuration version is 5
    SBC1#
    SBC2# display-current-cfg-version
    Current configuration version is 5
    SBC2#

    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.
  3. Confirm that the running configuration of SBC1 and SBC2 match by typing display-running-cfg-version and pressing Enter at the ACLI prompt.
    SBC1# display-running-cfg-version
    Running configuration version is 5
    SBC1#
    SBC2# display-running-cfg-version
    Running configuration version is 5
    SBC2#

    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.
  4. Initiate a switchover on SBC1 by typing notify berpd force and pressing Enter at the ACLI prompt.
    SBC1# notify berpd force
  5. 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.
    SBC2# show health

    Refer to the Software Upgrade section of the Platform Preparation and Installation Guide for more information.