[cisco-voip] Rebuilding a CUCM Publisher in a Different Location and Rehosting the License Files
Nicholas Samios
nsamios at staff.iinet.net.au
Thu Nov 18 19:45:34 EST 2010
>> I am assuming you could rebuild your Pub in a location with a different IP address.
Yep, keep in mind the WAN considerations though (refer to your versions SRND) e.g. 80ms RTT for v6.1+ between nodes, bandwith requirement for intracluster comms and active services (TFTP/MOH, etc)
>>What would you need to do to for the Subs to recognize the new Pub, just reboot the Subs??
Once the publisher is up, rehome the license files and follow the DR procedure. I would then rebuild each Sub.
>>you would need your license files rehosted. if you have multiple license files on the Pub, what do you need to provide to TAC, or the Licensing team for them to rehost the files?
The PAK keys and/or MAC address of the PUB.
TAC/Licensing know all the PAKs/Keys assigned to a MAC but they usually ask for it anyway.
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Joe Albertini
Sent: Friday, November 19, 2010 3:30 AM
To: cisco-voip (cisco-voip at puck.nether.net)
Cc: 7albertinis at comcast.net
Subject: [cisco-voip] Rebuilding a CUCM Publisher in a Different Location and Rehosting the License Files
Hello,
I know you can change the hostname and IP address on the Publisher server, but what if your Pub was destroyed. I am assuming you could rebuild your Pub in a location with a different IP address. What would you need to do to for the Subs to recognize the new Pub, just reboot the Subs??
Also, if the PUB is destroyed, you would need your license files rehosted. if you have multiple license files on the Pub, what do you need to provide to TAC, or the Licensing team for them to rehost the files? Thanks.
Regards,
Joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101119/e577db69/attachment.html>
More information about the cisco-voip
mailing list