Call Server: Device Becomes Corrupted

From DocWiki

Revision as of 18:51, 18 December 2009 by Docwikibot (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Device Becomes Corrupted

Problem Summary A device has become corrupted. The user receives a specific error message that indicates what device has been corrupted.
Error Message "Device with IP Address: {1} and Hostname: {2} is in an inconsistent state. Please Save and Deploy the properties of this Server again to fix the problem. If problem persists, please contact your administrator for more details."

"Device with IP Address: {1} and Hostname: {2} is not ready at this time. Please retry the operation at a later time."

"Device with IP Address: {1} and Hostname: {2} is in an inconsistent state and cannot be properly deleted at this time. Please retry the operation later or try deleting again for forceful delete."

Possible Cause The most likely cause is that the Unified CVP software was reinstalled.
Recommended Action The following steps outline the process to resolve the issue of software being reinstalled on a server.
  1. Identify the affected devices from the Control Center of the Operations Console. The affected devices are:
    - devices with the same IP addresses, and
    - devices associated to the devices identified with the same IP address.
  2. Go to the Edit page of each device and click Save&Deploy.
  3. Restart all affected devices from Control Center in the Operations Console.

If the procedure above does not resolve the issue, then you must clean up the device by performing the following steps.

Device Clean Up

  1. Delete the device from the Operations Console.
  2. Reinstall the software on that device.
  3. Recreate the device from the Operations Console.
Each Operations Console Server will be identified by a unique identifier. The identifier is generated at the time of creating a first device through that Operations Console Server. Once generated, the identifier will then be stored in the Operations Console Server database and in the Resource Manager Configuration file on every device that includes the Operations Console Server. The purpose of this unique identifier is to prevent management of a device from multiple Operations Consoles.

The unique identifier gets imported whenever the import functionality of an Operations Console database is invoked. Importing a database which was exported from a different Operations Console Server is not a supported feature unless the Operations Console is newly installed or has never been used before.

If a user uses an Operations Console Server that is already managing at least one device to import a database (from a different Operations Console Server or an empty database which was never used to create a device) the following side effects will occur:

User may not be able to manage devices which were managed by the same Operations Console server prior to the import. This is because the unique identifiers will now be different between the Operations Console Server and the previously managed device. User may not be able to create an IOS device such as Gatekeeper(s), Gateway(s), and CSS(s) from the Operations Console.

An Operations Console Server that is managing at least one device must not import an empty database that was previously exported from any Operations Console Server. This will cause a mismatch in the unique identifiers used since the Operations Console database and the Operations Console Server have a unique identifier and the empty database has no identifier. If a customer requires replacing the existing database with an empty database, the recommended way is to reinstall the Operations Console Server software. If this step is not followed, the customer can no longer manage devices that were previously managed by the same Operations Console Server.

Release Release 7.0(2)
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools