I have a customer with an 7 server cluster. They recently upgraded to 3.3. About a week later they went through and changed the administrator password on all of the machines. Since they did, there have been numerous problems. One of the sites keeps dropping into temporary failover mode and then bounces back. It looks as though they are losing their connection to the publisher at the main site. I have been getting the following errors in the event viewer:
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 100
Time: 1:14:17 PM
The server was unable to logon the Windows NT account 'administrator' due to the following error: Logon failure: unknown user name or bad password. The data is the error code.
Error: SDLLinkOOS - SDL link to remote application out of service.
Local node ID: 4
Local Application ID.: 100
Remote IP address of remote application: 10.255.255.241
Remote application ID.: 100
Unique Link ID.: 4:100:2:100
App ID: Cisco CallManager
Cluster ID: NT-MC-CM01-Cluster
Node ID: 10.64.41.240
Explanation: This alarm indicates that the local Cisco CallManager has lost communication with the remote Cisco CallManager. This alarm usually indicates network errors or a nonrunning remote Cisco CallManager.
Recommended Action: Investigate why the remote Cisco CallManager is not running or whether a network problem exists..
I also have a good number of phones and gateways that keep unregistering. I have no idea why this is happening. I think that part of it may be relaterd to them changing the local administrator account password on all the servers. Im not sure of all the places that would have to change to try and rectify the situation. Can anyone help?
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...