CWZIP1200E Unable to communicate with the virtual management software using IP address <nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn>

Diagnosing The Problem

1. Look at the 'count' on the event - verify whether it was raised once or many times
2. Note the date and time the event was last recorded
3. Find the serial number of the Compute Node associated with the IP address indicated at the end of the CWZIP1200E event message:
   1. Go to System > System troubleshooting > Click "Collect system logs..." > In the list, select "System Health Check", then click "Submit".
   2. Once the "System Health Check" is generated, download the resulting .tgz file.
   3. Unpack the "System Health Check" archive and find the compute node configuration details in the file
      Health_YY-MM-DD.HH.MM.SS.tgz\Health_YY-MM-DD.HH.MM.SS.tar\config\compute_nodes_resolved.json
   4. Within that file, search on the IP address from the event.  You find data for the related Compute Node similar to the following:
               {
            "compute_nodes": "/admin/resources/compute_nodes/nnnnn-nnnn-nnn-nnnnn",
            "created_time_raw": 1563445757341,
            "hardware": "T",
            "rack_unit_number": 0,
            "rack_number": "8283/NNNNNNN",
            "node_bay_number": 4,
            "mm_bay_number": 0,
            "width": 1,
            "state": "available",
            "label_text": "Rack 8283/NNNNNNN Chassis 1 Node Bay 4",
            "drive_bay_number": 0,
            "ipaddress": "nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn",
            "type": "compute_node",
            "label_key": "pure4504",
            "updated_time": "Thu 02 Apr 2020 00:07:41.942 UTC",
            "version": "2.3.1.1",
            "id": "/admin/resources/locations/936f71f2-5a96-4481-9d05-a6d19849b332",
            "physical_location": "n/a",
            "height": 0,
            "updated_time_raw": 1585786061942,
            "parent_type": "compute_nodes",
            "name": "SN#NNNNNNN",
            "io_bay_number": 0,
            "chassis_number": 1,
            "created_time": "Thu 18 Jul 2019 10:29:17.341 UTC"
         }
      ],
   5. Note the value in the "name" field - it is the serial number of the Compute Node that uses the IP address indicated in the event message.
4. Verify the date of any recent hardware repairs for the Compute Node with the serial number from step 3.5.