Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
After user attempts to upgrade a subscriber to Cisco CallManager 3.3, the subscriber has phones incorrectly registered
In the middle of a critical subscriber upgrade, the upgrade fails. The publisher has been upgraded, and currently the cluster is operating in a stand alone configuration. These are among the trouble symptoms and other strange behavior reported:
The subscriber thinks it is primary and has phones registered to it.
The publisher thinks it is primary and has phones registered to it.
Most phones think the subscriber is primary and the publisher is standby.
These symptoms come from the fact that the publisher needs to be rebooted. During the upgrade, it is important to reboot all the machines in the cluster so they can be synchronized, start with fresh caches, and have a common point of reference. Also, in this particular case, the subscriber did not have a robust name resolution method as the Hosts and LMHOSTS were not converged and were in conflict. It is important that both of these files are synchronized with each other. Although NetBios procedures are falling out of favor, they have not yet reached the point where they can be dispensed, and important processes mostly related to database replication rely on the services of NetBios.
Note: The Microsoft Structured Query Language (SQL) server uses NetBIOS name resolution for some types of Remote-Procedure Call (RPC) tasks. Because of this, the publisher and all subscribers should use the LMHOSTS file for NetBIOS name resolution. All servers in the cluster should also use HOSTS files for proper name resolution between the servers.
Even though these symptoms seem to indicate something is wrong, the fix is made my editing a text file, and rebooting.
For more information about SQL server and NetBios and their role in the upgrade and everyday operation of Cisco CallManger, refer to these links: