Avaya Session Manager Backup Server Configurations

[Avayapbxtech]

I have a Customer who wants to Install a Backup Avaya Session Manager on a DL360PG8 for a failover. I need to know the details on how to configure this for backup. Is it just a matter of copying the exiting configurations from the Main Session Manager to the Backup, or will software need to be installed on the Backup then configured?

 

[kyle555]

It's a bit of a vague question. I suppose the vague and appropriate answer is to install it on a different IP and build every trunk group in duplicate to it, every SIP profile with it as a secondary etc.

Also, you'd need to check the ports matrix and make sure everything's open there - SMs need to speak to each other and on more than just SIP ports.

What are you planning failover for? WAN/power? Is it in the same place as the primary or not?

 

[Avayapbxtech]

The Primary Session Manager is in the same location as the Backup. The Customer just wants to have the Backup server installed and Configured. Is there a way to Duplicate the Primary Session Manager to the Backup server, or does the Backup Server need to be build from scratch with the Software and License files installed? What information do I need to provide to make this clearer? I can ask the Customer more questions if necessary.

 

[wpetilli]

What's the harm in having this backup SM being online and linked to the same SMGR.. even though the IP info will different the rest of the data would be there.

 

[kyle555]

I wouldn't duplicate it. There's a whole enrollment thing with SMGR and security certificates and FQDNs and stuff - so you couldn't even try if you wanted to unless you took the primary offline.

And then, the backup whenever you'd use it would still be out of date and SMGR would see it like some impostor.

So, you gotta build a new one out with new hosts/IPs etc.

The config involved is only in how detailed your SIP design is. Do you have AAM? Need to point all their trunk servers to both SMs now. Same for any other adjunct - CM included - you'd need to map out all those routes to include the new sig/trunk to the new SM you're building.

As far as licensing goes, you should be fine, though it does depend on the release you're at. It ultimately is just based on sessions at 6.3. Its instance based at 7.0 - so you might need to pay for it if you're on that load. Although, the "right" way if at all possible is to have the single sw instance virtualized in VMWare appropriately so VMWare licensing to move it across servers makes your life easier by only worrying about the single software instance - and you got less trunks to play with on top of that.