Previous Topic: vCenter AIM Instance Status Icon Shows Discovery in ProgressNext Topic: vCenter AIM Instance Status Icon Shows No Polling


vCenter AIM Instance Status Icon Shows Error

Symptom:

After I add a vCenter AIM instance for a vCenter Server under Administration, Configuration, the status icon shows error (Error). Unable to connect to the AIM.

Solution:

The following procedures address the most common issues which can cause a connection failure to the vCenter AIM:

To verify if the vCenter AIM server system is accessible:

  1. Open a command prompt on the CA Virtual Assurance manager system and run the following commands:
    ping servername
    
  2. Verify the output of the commands to find out whether the vCenter AIM server has a valid DNS entry and IP address.

    If the vCenter AIM server is not in the DNS, add the vCenter AIM server to the Windows host file on the CA Virtual Assurance manager system. Continue with Step 3.

    If the vCenter Server is in the DNS, continue with Step 4.

  3. Open the hosts file in the %windir%\system32\drivers\etc directory with an ASCII editor and add the following line:
    ipaddress servername
    

    Enter the correct IP address and vCenter AIM server name. For example:

    192.168.50.51 myvCenterAIM
    
  4. Click validate (Validate) in the upper-right corner of the vCenter AIM Server pane.

    If the error status remains unchanged, continue with the next procedure.

To verify if SystemEDGE is running:

  1. Log in to the vCenter AIM server and run sysedge.cpl from the %windir%\Program Files\CA\SystemEdge\bin directory.

    The SystemEDGE Control Panel appears, showing the running state of SystemEDGE.

  2. Start or restart SystemEDGE.

    Wait until the SystemEDGE Control Panel indicates that SystemEDGE is running.

  3. Change to the CA Virtual Assurance user interface, vCenter AIM Server pane on the manager system and click validate (Validate) in the upper-right corner.

    CA Virtual Assurance validates the vCenter AIM Server connection.

    If the error status remains unchanged, verify whether the data you gathered according to the requirements for this scenario is still valid.