emc health check error

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

Upload: vijayen123

Post on 18-Dec-2015

137 views

Category:

Documents

6 download

Report

Download

Embed Size (px):

DESCRIPTION

Emc Health Check Error

TRANSCRIPT

KNOWLEDGE BASE

Knowledge Base Article: 000078871VNX 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 VNXError 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/FileProduct : Unisphere Service Manager (USM)EMC SW: VNX Operating Environment (OE) 7.0.35.3 and laterEMC 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 thisscenario, the upgrade health-check failed because the SP host names were not correctly referenced in the ControlStation /etc/hosts file. In this particular example, the recommended actions in the health-check symptom statement arenot 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 morethan one scenario. Check this solution first before executing the recommendations outlined in emc273714 (kb78002).Scenario 1 : Check Unisphere domain listFirst run domain list to obtain current config for this array and ensure the CS is fused (that is, it is listed in the output), ifnot, follow emc273714 (kb78002) to fuse correctlyCommand : /nas/sbin/navicli -h spa domain -list

Example:

$ /nas/sbin/navicli -h spa domain -listNode: vnx-aIP Address: XX.XX.XX.XX (Master)Name: VNX_SPA_10Port: 80Secure Port: 443IP Address: XX.XX.XX.XXName: VNX_SPB_10Port: 80Secure Port: 443IP Address: XX.XX.XX.XXName: Celerra_vnx5300-aPort: 80Secure Port: 443

On a Dual control station environment, the above Celerra control station (In this example : Celerra_vnx5300-a) - Check ifthis is correct. If this details are for secondary control station, not for the primary control station, restarting the SPmanagement 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
1.

1.

1.

SPA and SPB (case sensitve/upper case) are the proper alias for integrated VNX systems. Examples of alias namesmissing or wrong from /etc/hosts file for the SPs:XX.XX.XXX.XX A_XXXXXXXXXXXXXX # CLARiiON SPXX.XX.XXX.XX B_XXXXXXXXXXXXXX # CLARiiON SPXX.XX.XXX.XX A_XXXXXXXXXXXXXX spa # CLARiiON SP