Ok the first thing to do is get the servers on the same version. This is not optional; the new subscriber will not join the cluster if the version does not match. I recommend getting a 6.1(3a) installable disc. I suggest upgrading your cluster to a newer version at another time; get yourself and the database a stable state first! If you do not have that exact version but can find a 6.1(1) or perhaps 6.0(1) you can piece together what you need:
- Install the base version from the bootable DVD that you have.
- Download, merge, and apply the patch to the 6.1(3a) (i.e. 6.1.3.2000). You will be asked if you want to apply a patch after booting from the original DVD. Note that ISOs downloaded from CCO are not bootable for licensing reasons.
Once you have the new subscriber on 6.1(3) it will ask you to do the initial platform configuration. The values you specify (e.g. hostname, IP address, gateway, etc) need to be identical to the original subscriber. You want to try reclaiming this node's position and CTI ID in the database if possible. Note that without a valid backup from the subscriber this may not be possible. What you likely won't have is the security passphrase. This is a shared secret used to secure intra-cluster communications signaling (a.k.a. ICCS). The only way to get this is reseting it on your publisher. Note this will require a restart of the publisher to take effect.
After the Pub and Sub are talking to each other, what other general configuration steps do I have to do? (aside from setting up backup!) Do I have to do a bunch of manual stuff, or will they pretty much be ready to act as a fault-tolerant cluster?
If it assumed the original node's CTI ID and place in the database, nothing. If it doesn't, you'll need to update your CallManager Groups to ensure that the node is added and first so the phones register to it first. Phones require a reset to notice CMG changes.
After everything is online you should also ensure that the database has synchronized using the utils dbreplication status command. You can do this publisher only. What you want to see is all nodes at a two (2) eventually. Anything above three (3) indicates a failure and you should call TAC.
admin:utils dbreplication status
-------------------- utils dbreplication status --------------------
Replication status check is now running in background.
Use command 'utils dbreplication runtimestate' to check its progress
The final output will be in file cm/trace/dbl/sdi/ReplicationStatus.2010_11_15_20_07_30.out
Please use "file view activelog cm/trace/dbl/sdi/ReplicationStatus.2010_11_15_20_07_30.out " command to see the output
admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.2010_11_15_20_07_30.out
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_manager1_ccm8_0_3_10000_8 2 Active Local 0
g_manager2_ccm8_0_3_10000_8 3 Active Connected 0 Oct 14 07:31:02
end of the file reached
Back in the 4.2 days, I recall that once the Subscriber was added, it took over the main functions of call setup and completion. Is that still the case?
This is best-practice but only happens if you configure the CMGs properly. The phones/gateways only speak to node(s) in their assigned CMG and it's an ordered list.
