Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1598276.1
Update Date:2017-05-31
Keywords:

Solution Type  Technical Instruction Sure

Solution  1598276.1 :   Acme Packet: Standby Session Border Controller Goes Out of Service  


Related Items
  • Acme Packet 4500
  •  
  • Acme Packet 3820
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
  •  




In this Document
Goal
Solution


Applies to:

Acme Packet 4500 - Version S-Cx6.2.0 and later
Acme Packet 3820 - Version S-Cx6.2.0 and later
Information in this document applies to any platform.

Goal

 Recovering when a standby session border controller (SBC) goes out of service (OOS).

Solution

The standby SBC may time out before it is able to transfer all necessary redundancy information. A log entry similar to the following will be created in the log.brokerd:

May 15 15:40:09.005 [CRITICAL] Unable to synchronize with Active redundant peer within BecomingStandby timeout, going OutOfService

Increase the becoming-standby value in the redundancy-config. The timer needs to be increased as usage of the SBC grows since it will take longer to synchronize between the two Session Directors (SD) (not only configuration but call information as well is synchronized).

1. Increase the timer to 360000 (steps shown below).

2. Save and activate the configuration from the active SBC.

3. Reboot the standby SBC.

4. At this point it will read the new config but it needs to be rebooted again as I believe it will go OOS again as it got the new configuration information but needs a reboot to activate. So reboot the standby SD a second time. Verify that it is in service and standby.

5. It may be necessary to wait for a slow time/maintenance window in order to fail-over / switchover the SBC. As long as the SBC is correctly at standby state, issue a 'notify berpd force' to switch the active SBC to the standby SBC.

6. Verify that the 'new' active SBC is processing calls ok.

7. Reboot the previously active SBC (should now be standby).

 

ActiveSBC# configure terminal

ActiveSBC(configure)# system

ActiveSBC(system)# redundancy

ActiveSBC(redundancy)# select

ActiveSBC(redundancy)# show redundancy-config

 state enabled

log-level INFO

health-threshold 75

emergency-threshold 50

port 9090

advertisement-time 500

percent-drift 210

initial-time 1250

becoming-standby-time 180000---------->changing to 360000 ....

last-modified-by last-modified-date 2006-08-02 20:16:02

 

ActiveSBC(redundancy)# becoming-standby-time 360000

ActiveSBC(redundancy)# done

ActiveSBC(redundancy)# exit

ActiveSBC(system)# exit

ActiveSBC(configure)# exit

ActiveSBC# save

Save-Config received, processing. waiting 1200 for request to finish

Request to 'SAVE-CONFIG' has Finished,

Save complete

Currently active and saved configurations do not match! To sync & activate, run 'activate-config' or 'reboot activate'.

ActiveSBC# activate

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback