I found a typo in the name of the publisher so I changed it in the OS Administration. After the server rebooted I can no longer log into the Administration of the unit. I get database error messages when I try to log in. The subscriber is operating as primary right now.
So I guess I need to reload the machine completely. My question is once I start the install process and bring this machine back on line, will it take all of the database information from the subscriber or is there something I need to do during the install to make that happen. I really do not want to recreate everything that is there even though these units have not gone into production yet.
There are also no backups done since it is not in production. I know that during the install I get asked if this is the first server in the cluster, do I answer no even though eventually I want this server to be the publisher again?
Thanx, any help is greatly appreciated.
Well, if you want to go the reload route then this is the way to do it:
1) Shutdown the Subscriber.
2) Rebuild the Publisher via DVD which will overwrite the hard drive. The DVD comes with the server. Do not try to use the "Recovery" CD, just the straight up application CD - CUCM version (whatever you had shipped).
3) Before you install the Subscriber, make sure you verify NTP sync on the Pub (critical).
4) Once you have the Publisher rebuilt, add the Subscriber in CU Admin as part of the cluster just as you normally would. Use the IP address of the server (recommended).
5) Rebuild the Subscriber from DVD as you did the Publisher. It should be added as the second node in the cluster so make sure you have DNS and IP connectivity to/from all resources needed BEFORE STEP 2 ever occurs.
6) Once both servers are up and running, check CUC Serviceability and look at the cluster status.
7) Then, go to the CLI on both servers and run "show tech network hosts". The /etc/hosts file should have a loopback address and both cluster servers included in the file.
8) Make a test user on the Pub, verify it replicates to the Sub. Delete it from the Sub, make sure it deletes from the Pub.
9) Test failover then test failback by going to CUC Serviceability and putting the Publisher back as active.
10) You can also look at the cluster status on both servers from the CLI - show cuc cluster status is the command to do that.
11) If all that checks out, get your license files loaded and do your configurations.
12) Make sure you set up DRS backups on a schedule (for both servers) and perform an initial manual DRS backup of both as well.
13) I would also recommend that you upgrade both systems to the latest SU for 7.1.3 which is 7.1(3b)SU2. You can download it from CCO.
As for MWI, there is a specific service that enables MWI to work properly. If that service didn't start on the Sub for whatever reason when it failed over, then that may be the cause. Get the servers rebuilt and let's go from there. Sound good?
Please rate helpful posts!