Signaling Server Setup Question. 7.5 software version.

[blondboy71]

I have a CS1000 setup with 2 cabinets and has been configured has Highly Available. The call server CPU's are in the Join mode, so they look to be configured properly. In looking at the signaling servers, the SS in the first cabinet is setup as "Primary", and the SS in the second cabinet is setup as "Member". Is this the recommended setup, or should the SS in the second cabinet be set as a "Backup" to the "Primary", or is "Member" fine. This is suppose to be a fully redundant system and I want to make sure it is configured appropriately. Also if it does need to be set as a backup, can I just delete the element, and re-deploy it as a backup, or does to card need to be formatted and started from scratch. Thanks for any help!

 

[bignose21]

Do you mean that the Server in the first cabinet is setup as a Primary security server probably UCM, and the other is set as a member server but that is just the type of security server it is not what it is doing. Web browse the Primary

http://<fqdn>

and login under elements you can see what is defined.

Usually in a HA you would have a seperate UCM server, then a further 2 member servers that you would use to run the sig server applications (one as leader and one as follower).

 

[blondboy71]

Yes the SS in the first cabinet is the Primary, and the SS in the second cabinet is a Member. So should the one in the second cabinet be a follower to the Primary?

 

[KCFLHRC]

No reason to have a backup security server, the Primary and member server is just fine. Your system will function just fine without the primary Security Server if it would happen to fail.

 

[bignose21]

I think you are confused the The Primary Security server refers to just that it is not a sig server but a UCM runs on same type of server, the member server refers to the security and deployment status of that server not the job it is performing.

If you look in the CS1000 in LD 117
=> stat ucm info

You will probably see the IP address of what you are refering to as the Primary. If you web browse the that IP address and login you should see the elements configured such as

Call Servers
MGC's
Linux base (on the sig server(s) and UCM)
Element Manager
NRS

It is from here that you access element manager, also you can see what signaling server(s) are associated with your CS1000.

 

[blondboy71]

My primary has NRS, subscriber manager and other stuff deployed on it. The member has nothing deployed on it. If in my situation I do not need a follower, then when would the follower be needed. I just want to make sure my system is setup for redundancy as it is supposed to be. Seems like the member is sitting there doing nothing, and will not take over in the event the primary goes down. I did not mention this earlier, but this is a 7.5 system. I understand what each part does, MGC CS SS Linux UCM and such, just not 100% on the Primary Follower and Member roles. Any info would be great, thanks!

 

[bignose21]

The terms you are using is where you are getting confused i think

Primary, Secodary and Member refers to the type of Security server (UCM) it is ie a Primary UCM, Secondary UCM, or a memeber server (No UCM)

Leader, Follower are terms used in the Element Manager for the servers standing in the Telephony node.

In the Primary UCM if you click on Deployment and select Servers you can see the registered servers and what applications if any are deployed
Also in Deployment you can select CS1000 from the drop down an see the devices associated with your CS1K

For a proper HA you will need 3 servers, 1 built as the Primary UCM, and 2 member servers which you would deploy EM+SS to.

Of course if you have multiple CS1K's on your network you only need 1 or 2 UCM's to take care of all your sites.

To deploy applications if they are not there you open CS1000 in deployment, if there isnt one ther you select add, you should see CS1k TID in the drop down and just give the site a name click next. Add your Element Managers and assign sig server(s). Then when you go back to the Server view you will see the EM+SS pre-deployed, commit config, then select server and pick deploy from the drop down. Once it is deployed put the 3 patches on from CLI and deploy service pack from UCM. You should then have a functioning EM.

 

[KCFLHRC]

Just a few things to add here. So is your second signal server registering phones as a follower SS? If not it should be. Otherwise what is the point of having it. If you lose your Leader SS then your follower will take over that role. The 2 SS will load share the IP phone registration if configured properly. You actually put in the 3 base patches prior deployment,then you deploy and then the SP is installed. And YES, that second SS should have been deployed as a signal server, that's it. Then you have redundancy.