KNOWLEDGE BASE

Knowledge Base Article: 000078871

VNX File OE health-check Error occurs with "One of the VNX IP addresses is missing from the
domain" (000078871)
Version:6

Audience: Level 30 = Customers

Article Type: Break Fix

Last Published: Wed Dec 03 13:33:51 GMT 2014

Validation Status: Final Approved

Summary:

Issue:

Pre-Upgrade Health Check error during VNX OE for File upgrade

-------------------------------------Errors------------------------------------Storage System : Check for domain and federations health on VNX
Error HC_BE_14505017510: One of the VNX IP addresses is missing from the domain.
Action : Contact your service provider and reference EMC Knowledgebase article emc273714.

Environment:

Product : VNX Unified/File

Product : Unisphere Service Manager (USM)
EMC SW: VNX Operating Environment (OE) 7.0.35.3 and later
EMC SW: VNX Operating Environment (OE) for Block 05.31.000.5.502 or later

Cause:

The latest VNX OE release contains a number of domain health-checks between the File and Block components. In this
scenario, the upgrade health-check failed because the SP host names were not correctly referenced in the Control
Station /etc/hosts file. In this particular example, the recommended actions in the health-check symptom statement are
not the correct steps to take to resolve the problem.

Resolution:

Because the upgrade health-checks can generate a variety of different errors or warnings, and may in fact apply to more
than one scenario. Check this solution first before executing the recommendations outlined in emc273714 (kb78002).
Scenario 1 : Check Unisphere domain list
First run domain list to obtain current config for this array and ensure the CS is fused (that is, it is listed in the output), if
not, follow emc273714 (kb78002) to fuse correctly
Command : /nas/sbin/navicli -h spa domain -list
Example:
$ /nas/sbin/navicli -h spa domain -list
Node:
vnx-a
IP Address:
XX.XX.XX.XX (Master)
Name:
VNX_SPA_10
Port:
80
Secure Port:
443
IP Address:
XX.XX.XX.XX
Name:
VNX_SPB_10
Port:
80
Secure Port:
443
IP Address:
XX.XX.XX.XX
Name:
Celerra_vnx5300-a
Port:
80
Secure Port:
443
On a Dual control station environment, the above Celerra control station (In this example : Celerra_vnx5300-a) - Check if
this is correct. If this details are for secondary control station, not for the primary control station, restarting the SP
management agent service like following will fix:
$ /nas/sbin/navicli -h spa networkadmin -restartcimom -o
$ /nas/sbin/navicli -h spb networkadmin -restartcimom -o
$ sleep 120
$ /nas/sbin/navicli -h spa domain -list
And check the IP is re-updated to Primary control station, correctly. If so, another checkup will show this check as "Pass"
and this issue is fixed (Same effect can be achived by control station reboots too)
Scenario 2 : Check /etc/hosts for SP Alias

SPA and SPB (case sensitve/upper case) are the proper alias for integrated VNX systems. Examples of alias names
missing or wrong from /etc/hosts file for the SPs:
XX.XX.XXX.XX A_XXXXXXXXXXXXXX # CLARiiON SP
XX.XX.XXX.XX B_XXXXXXXXXXXXXX # CLARiiON SP
XX.XX.XXX.XX A_XXXXXXXXXXXXXX spa # CLARiiON SP <<- lower case is wrong
XX.XX.XXX.XX B_XXXXXXXXXXXXXX spb # CLARiiON SP
Another examples of alias names missing or wrong from /etc/hosts file for the Control station
XX.XX.XX.XX VNX5700CS0.bbb.ccc.emc.com
VNX5700CS0
Fix:
Use the vi editor and add the missing aliases to the /etc/hosts file:
XX.XX.XXX.XX A_XXXXXXXXXXXXXX SPA # CLARiiON SP <<< SPA/SPB should be capital letters
XX.XX.XXX.XX B_XXXXXXXXXXXXXXSPB # CLARiiON SP
XX.XX.XX.XX VNX5700CS0
VNX5700CS0
Scenario 3 : Check Control station hostname
Verify the hostname of the CS is matching with domain list output .
1. Run the domain list output and note the CS hostname
$ /nas/sbin/navicli -h spa domain -list
Node:
vnx-a
IP Address:
XX.XX.XX.XX (Master)
Name:
VNX_SPA_10
Port:
80
Secure Port:
443
IP Address:
XX.XX.XX.XX
Name:
VNX_SPB_10
Port:
80
Secure Port:
443
IP Address:
XX.XX.XX.XX
Name:
Celerra_vnx5300-a <<<- here the CS hostname is vnx5300-a
Port:
80
Secure Port:
443
1. Verify the host is listed on the /etc/hosts
$ grep vnx5300-a /etc/hosts
XX.XX.XX.XX vnx5300-a
vnx5300-a
1. Run hostname command on the CS to see it matches
$ hostname
vnx-a
This is an error, hostname is not matching with what is listed in domain -list
Fix:
Run the following commands to fix the hostname (run as su to root):
# nas_cs -set -hostname vnx5300-a
OK
# hostname vnx5300-a
# hostname
vnx5300-a
Re-verify the problem is solved by running "nas_checkup -rerun"
rerun usually runs failed tasks, but if old run log is not available, it will initiate full nas checkup again. A successful
example is :
# nas_checkup -rerun
Check Version: 7.1.72.1
Check Command: /nas/bin/nas_checkup
Check Log : /nas/log/checkup-run.140108-010159.log
-------------------------------------Checks------------------------------------Storage System : Checking for domain and federations health on VNX......... Pass
-------------------------------------------------------------------------------Product:

Unisphere Service Manager

External Source:

Primus

Primus/Webtop solution ID:

emc278025