Standby State for HA Nodes

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

There are two ways to determine the HA state of each Acme Packet 4900 in an HA pair.
  1. If you are in the same physical location as the Acme Packet 4900 you can view the HA LEDS on the front bottom right. A standby unit lights the STBY LED, while an active unit lights the ACT LED.
  2. If you are not in the same physical location as the Acme Packet 49004, you can use the ACLI show health command. The output of this command indicates the current HA state of the Acme Packet 4900.

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

If you need to perform maintenance on the active Acme Packet 4900 you need to manually force the two Acme Packet 4900s to switch HA states. Forcing a switchover renders the currently active Acme Packet 4900 in Standby state, and the current standby Acme Packet 4900 will assume all traffic processing and forwarding as the active system.

Note:

This procedure is only applicable to an HA deployment.
To force a Acme Packet 4900 into the standby HA state:
  1. Use the show health command to verify the State attribute has the value "Active".
    SBC1# show health
        Media Synchronized            true
        SIP Synchronized              true
        MGCP Synchronized             true
        H248 Synchronized             disabled
        Config Synchronized           true
        Collect Synchronized          disabled
        Radius CDR Synchronized       disabled
        Rotated CDRs Synchronized     disabled
        Active Peer Address           0.0.0.0
    
    Redundancy Protocol Process (v3):
        State                           Active
        Health                          100
        Lowest Local Address            169.254.1.1:9090
        1 peer(s) on 2 socket(s):       SML-STIC-49002: v3, Standby, health=100, max silence=1050
                                        last received from 169.254.1.2 on wancom1:0
        Switchover log:        
        Jun 25 19:03:02.029: Active to Becoming Standby
        Jun 25 19:04:54.684: Standby to Becoming Active
    
    SBC2# show health        
        Media Synchronized            true
        SIP Synchronized              true
        MGCP Synchronized             true
        H248 Synchronized             disabled 
        Config Synchronized           true
        Collect Synchronized          disabled
        Radius CDR Synchronized       disabled 
        Rotated CDRs Synchronized     disabled
        Active Peer Address           169.254.2.1
    Redundancy Protocol Process (v3):
        State                           Standby
        Health                          100
        Lowest Local Address            169.254.1.2:9090
        1 peer(s) on 2 socket(s):       SML-STIC-49001: v3, Active, health=100, max silence=1050
                                        last received from 169.254.2.1 on wancom2:0
  2. Use the display-current-cfg-version command to verify the configuration version is the same on both the active and standby nodes.
    SBC1# display-current-cfg-version
     Current configuration version is 5
    
     SBC2# display-current-cfg-version
     Current configuration version is 5
     NETNETSBC2#

    Note:

    While the two current configuration version numbers on the two systems do not need to match each other, they MUST match the shared running configuration version.
  3. Use the display-current-cfg-version command to verify the running configuration version is the same on both the active and standby nodes.
    SBC1# display-running-cfg-version
    Running configuration version is 5
    
    SBC2# display-running-cfg-version
    Running configuration version is 5
    NETNETSBC2#

    Note:

    While the two running configuration version numbers on the two systems do not need to match each other, they MUST match the shared current configuration version.
  4. Use the notify berpd force command to initiate a switchover from the active to the standby node.
    SBC1# notify berpd force
  5. Wait for the other Acme Packet 4900 to transition to the standby state. Confirm that it is in the standby state with the show health command.
    SBC2# show health
Refer to the Upgrade section of the Maintenance and Troubleshooting Guide for more information.