Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

IPT Clusters Data Center Move 8.6(2a)SU3‏

Hi Voice Experts,

Any help will be appreciated, I have read Cisco BCP and understand the best practice but Cisco doesn’t talk clearly about the questions mentioned [only adding subscriber needs a cluster reboot is confirmed but wanted to know from the experience of experts here]:-

 

We have a plan to move data center for IPT Clusters, and we are working for POC for server build as of now, I would need your guidance for the following questions:-

 

1-      Adding a new Subscriber:

a.        Is rebooting for all nodes in a cluster required?

b.      Is this mandatory to remove the subscriber from the list of servers from publisher before building the same subscriber in a live environment? [lets say need to replace MCS server for a subscriber]

c.       Can the replica subscriber be built in an isolated environment first by building the replica Publisher and then Subscriber, and later promote this newly build subscriber in live environment by replacing this with the original non working subscriber?

 

 

2-      Node licensing:

a.       The node licensing reflects the no of Subscribers in a cluster [not non subscribers like MOH, TFTP servers], lets say we have one subscriber in one data center, we need to move this in another Second data center, so can we build this server with different ip address in live running environment [will shut down the original subscriber first before promoting newly built server as SUBSCRIBER considering node licensing limitations], is that doable ? OR First we need to decommission the current running server from one Data Center and then start building the subscriber in second data center?

Regards,

Shah

 

2 REPLIES

I dont quite follow what you

I dont quite follow what you are trying to do, are you actually going to move your whole cluster to a DC?

 

if you move DC, can you move your VMs across and Re-IP?

 

if you are going to build new subs in the new DC, you will need to add these to your existing cluster yes, no full reboot of your cluster should be required when adding a sub.  once you have all subs spun up in your new DC, move your phones across to it (change option 150 in each voice subnet). lastly Re-IP your PUB to fit in the new IP range in your new DC

always make sure you ready the release notes!!!!!  

You will need to get temporary licences for your interim period where you have a bunch of sub in the new as well as the old DC. All you need is node licences. Speak to your reseller.

 

 

please rate if usefull

Please remember to rate useful posts, by clicking on the stars below.

I dont quite follow what you

I dont quite follow what you are trying to do, are you actually going to move your whole cluster to a DC?

 

if you move DC, can you move your VMs across and Re-IP?

 

if you are going to build new subs in the new DC, you will need to add these to your existing cluster yes, no full reboot of your cluster should be required when adding a sub.  once you have all subs spun up in your new DC, move your phones across to it (change option 150 in each voice subnet). lastly Re-IP your PUB to fit in the new IP range in your new DC

always make sure you ready the release notes!!!!!  

You will need to get temporary licences for your interim period where you have a bunch of sub in the new as well as the old DC. All you need is node licences. Speak to your reseller.

 

 

please rate if usefull

Please remember to rate useful posts, by clicking on the stars below.

49
Views
0
Helpful
2
Replies
CreatePlease login to create content