I've gone through the steps to change hostname on my unity connection cluster, everything seems to have completed fine with Pub retaining the primary status, however one thing bugs me when I get output of show network status, I get the following:
tcp 0 0 produc02:51485 produc02:unityconnect02_ccm7_1_5_30000_1 TIME_WAIT
tcp 0 0 produc02:51486 produc02:unityconnect02_ccm7_1_5_30000_1 ESTABLISHED
tcp 0 0 produc02:51487 produc02:unityconnect02_ccm7_1_5_30000_1 ESTABLISHED
tcp 0 0 produc02:51490 produc02:unityconnect02_ccm7_1_5_30000_1 TIME_WAIT
tcp 0 0 produc02:51496 produc02:unityconnect02_ccm7_1_5_30000_1 TIME_WAIT
tcp 0 0 produc02:51499 produc02:unityconnect02_ccm7_1_5_30000_1 ESTABLISHED
tcp 0 0 localhost:1502 localhost:33053 ESTABLISHED
tcp 0 0 localhost:1502 localhost:33052 ESTABLISHED
tcp 0 0 produc02:unityconnect02_ccm7_1_5_30000_1 produc02:51487 ESTABLISHED
tcp 0 0 produc02:unityconnect02_ccm7_1_5_30000_1 produc02:51486 ESTABLISHED
tcp 0 0 localhost:1502 localhost:33049 ESTABLISHED
tcp 0 0 localhost:1502 localhost:33051 ESTABLISHED
tcp 0 0 localhost:1502 localhost:33063 ESTABLISHED
oldname was unityconnect02, and new name is produc02. Am not sure what is "unityconnect02_ccm7_1_5_30000_1" which still has this old hostname. Does it matter or needs to be changed, if yes, where do I get to change this to reflect the new name rather than old one.
I believe you are OK looking at the output. However, my first question is does the host table look the same on both servers? Are you running DNS or not?
So, your output actually shows this: produc02:unityconnect02_ccm7_1_5_30000_1 produc02:51487
So, you have the new name followed by a reference to the old name which is followed by the full version that was loaded at the time followed by the new host name.
Is this an 8.0 cluster?
Please rate helpful posts!
No this isn't an 8.0 cluster, just like the name shows its a 7.1(5) cluster.
I am not using DNS, just using IP addresses(now that you've asked, I wanted to ask whether DNS is a must/recommended? or can I just not use it and be good to go). Currently we have DNS on our network, but on UC servers it is not configured aka not dependent on it.
For this entry, I'm showing the same on both servers, pub and sub. I can re-run the db sync but wonder if that would clear out this entry cause the first time it didn't which is why I'm seeing it in the output.
Making the Unity dependent on DNS is not advisable as you would be adding another point of possible failure in your network.
Hi Thomas, thanks for reiterating this and that was the reason behind going with IP addresses. I appreciate your input.
Still looking answers on the other query I posted.
you've probably gone through this - http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrug060.html
did u follow the steps as per the document? or where there any steps you ommited?
also verify replication via RTMT and/or CU Reporting. we'll first try to get an idea whether this is affecting your servers in any way
Any suggestion on this one?
Here is one clue I can provide.
When you go to UC Administration page, and click on Message Storage>Mailbox Sotres
Click on the mail database link
Against the server field, it shows the older name, even though everything has been changed to the new one.
PLUS this name is all greyed out so one cannot tweak it in this field, it just displays and is greyed out.
How do we correct this to the new hostname of the server? (OR) does it matter if we really have to?
I like things consistent which is why this is bugging me.
thanks for your help.