Loading...
Loading...
There are two VNX5400 units in the storage domain. In this article, these units are referred to as VNX A and VNX B. The primary domain is VNX A. When a user logs in to Unisphere using the VNX A IP address, the VNX A file menu appears as unavailable. However, VNX B functions correctly. Everything functions correctly after destroying and rebuilding the domain on VNX A. Manually add VNX B to the VNX A storage domain. The VNX B file menu then appears as grayed out. After performing the rebuild action on VNX B again and adding VNX A to the VNX B storage domain, the VNX A file menus appear as unavailable. Destroy the domain on the SPs for both VNX arrays by running the domain destroy script. This does not resolve the issue. While the primary domain is VNX A, the file menus function correctly when logging in to Unisphere using the SP IP address of VNX B. The following Unisphere Warning alert appears: Severity: Warning System: vnx5300cs Domain: Local Created: Jul 25, 2017 8:14:19 AM Message: Logging into xxx.xxx.xxx.xxx encountered an error. Full Description: An error occurred during the login process. The control station did not log in properly. Recommended Action: The login error may have occurred because: 1. Certificates are not accepted. 2. Both storage processors or the control stations are not accessible. 3. You have logged in to a File or Block system using a local user account not defined on both the File and Block systems. Event Code: 0xfffffffffffffff9
Both the VNX A control station and the VNX B control station have the same hostname, "VNX5400." Both the VNX A array name and the VNX B array name are set to the same value, "VNX5400." This duplicate naming is the root cause of the issue.
Procedure: Change the hostname of the VNX B control station (for example, "VNX5400-117"). #nas_cs -set -hostname VNX5400-117 Change VNX B array name from VNX5400 to VNX5400-117: #/nas/sbin/navicli -h spa arrayname VNX5400-117 Reboot the control station. This action recolves the issue.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.