Introduction
This document describes how to troubleshoot Unified Customer Voice Portal (CVP) server not reachable status in Operations Console after IP address change on the server.
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
- CVP Server
- Cisco Unified Contact Center Enterprise (UCCE)
Problem Summary
The IP address of a Unified CVP server is changed and is now listed as Not Reachable.
Possible Causes
The IP address of a Unified CVP server was changed in local the configuration file.
Note: In order to change the IP address use the CVP Operations Console administration page.
Recomended Action
If you have already changed the IP address of the server in the local configuration file, you can delete the server from the Operations Console, but the configuration properties files remain on the server. This is because the Operations Console cannot access the server with the original IP address. When you add the server with the new IP address to the Operations Console new property entries are created. The original configuration property files are not cleaned up and must be removed manually. Contact your Cisco Partner or Cisco Technical Support for assistance in order to remove the property files.
This is the correct procedure in order to change the server IP address:
Step 1. From the command prompt, run CVP_HOME\in\tac\reimage.bat on the device.
Step 2. Starting with Unified CVP 10.0(1), the batch file is made available at C:\Cisco\CVP\bin\UpdateRMIServerIP\updatermiserverip.bat as a part of the ES1. Double-click on the batch file to update the IP address in Windows Registry and wrapper.conf file.
Note: For Unified CVP 9.0(1) and earlier releases ignore the step 2.
Step 3. Delete the old license from the device, if you need to re-host a license.
Step 4. Restart all the CVP services from this device. The device is at the post installation state ready to receive the configuration changes from CVP Operate Administer Maintain Provision (OAMP).
Step 5. From the Operations Console, select Save and Deploy of the new device.
Step 6. Re-host the new license if required.
Feedback