Re: Hardware replacement for a CallManager Subscriber
The recommended method is Procedure # 2. Have a look at the following;
Restoring Subscriber Servers
When you perform a server replacement, you must always manually enter the IP information, computer name, and other configuration data exactly as it was entered on the original server.
Make sure that you locate the configuration information for this server before you begin.
Cisco does not require that you remove the subscriber server from the Cisco Unified CallManager database before recovering the server. When the subscriber server authenticates to the publisher database server and pulls a duplicate of the database from the server, the subscriber server automatically adds itself to the database.
If you are reinstalling a subscriber server only, you did not need to do a BARS restore unless the CDR and TFTP data on this subscriber server was backed up with BARS and now needs to be restored. The subscriber server will acquire all Cisco Unified CallManager configuration data from the publisher server.
Use the following guidelines to restore the subscriber server(s):
Perform a new installation of both Cisco Unified CallManager and the Cisco-provided operating system:
For Cisco CallManager 3.3(3), as the minimum required operating system, use version 2000.2.3 with an upgrade to 2000.2.4 or a fresh install to operating system version 2000.2.4.
For Cisco Unified CallManager 4.0, 4.1, and 4.2, as the minimum required operating system, use version 2000.2.3 with an upgrade to version 2000.2.5. Ensure the operating system is also SR2 or later.
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.