sbce high availability

[RINGINnBLINGIN]

hope i'm asking this in the right forum, the IPO section doesnt seem to have much on this.

We are adding a secondary sbc to a solution. The original is not configured for HA. There is already a standalone EMS. version 7.2.2.

Does the original sbc need to be uninstalled and reinstalled to activate HA? If so, is there a way to extract the configuration from it to restore it after it is reinstalled?

Thanks!!

 

[kyle555]

I think so, yeah. What kind of platform are you on right now? For a IPO or anything else needing 1 SBC, I wouldn't recommend a separate EMS+single SBC. 1 EMS can support many different SBCs, but for a single SBC, I'd think you'd just have the single EMS+SBC platform either on a Portwell or bare metal server or VM.

From the VMware installation, I believe the VM gets deployment instructions on spin up or from CLI about whether he's solo or part of a pair. All 3 get a management port, and the HA pair get a private link between the two. On deployment, the EMS generates a cert for itself and issues certs to the SBCs that get installed too. I'd think that little magic doesn't play nice if you just add a second box on the fly.

Also, you need a license for HA.
Also, the HA switchover uses gratuitous ARP, which some things don't play nice with. The recommendation is to have HA SBCs in a separate subnet and let a layer 3 router manage that. Otherwise, if you had them in the same subnet as a IPO server+IP500gateway, the IPO server might not know how to acquire the new MAC of the new SBC taking over the SIP interface and other stuff in the middle of a call might not know to flip to that interface to send RTP.

I'd think the configs all live in the EMS, so if you already had a standalone EMS, the procedure would be like recovering a dead SBC and just reinstall a pair of them.