1) Check if you logged into the Control Station with 'Local' or 'Global' scope within Unisphere?

2) You could reboot the Control Station, then try again.

Hello Jikamsila,

This could be a storage domain issue.

If the control station is failed over to slot_1 then Failback the control station by logging into slot_1 Control Station and rebooting it.

If you have access to Putty session (ssh) to control station (Primary), try the command(Type "yes" when it prompts):

[nasadmin@VNX137 ~]$ /nasmcd/sbin/getreason

If the result shows that:
slot_1 Primary Control station
slot_0 Secondary Control station

You need to fail back the control station by rebooting slot_1 control station. Just login as root (su) and run the following command:

[nasadmin@VNX137 ~]# reboot

This would take few minutes to reboot the control station and it to come up in the original configuration.

Once the control stations are back on original status, check the domain files:
[nasadmin@VNX137 ~]$ /nasmcd/sbin/getreason
10 - slot_0 primary control station
11 - slot_1 secondary control station
5 - slot_4 contacted
5 - slot_3 contacted

[nasadmin@VNX137 ~]$ ll /nas/http/domain
total 15
drwxr-xr-x 2 apache apache 1024 Jun 27 14:35 bak
drwxr-xr-x 2 apache apache 1024 Nov 14  2013 ldap
-rw-r--r-- 1 apache apache    0 Mar 24 22:04 lock_file
[nasadmin@VNX137 ~]$

Verify the Control Station hostname to be same as in storage domain:
[nasadmin@VNX137 ~]$ hostname
VNX137
[nasadmin@VNX137 ~]$ hostname -i
10.31.139.137
[nasadmin@VNX137 ~]$ grep initiator /nas/dos/slot_3/boot.cfg
setinitiator cs_hostname=Celerra_VNX137 cs_external_ip=10.31.139.137

[nasadmin@VNX137 ~]$ /nas/sbin/navicli -h spa domain -list
Node:                 VNX_137
IP Address:           10.31.139.141 (Master)
Name:                 SPA
Port:                 80
Secure Port:          443
IP Address:           10.31.139.142
Name:                 SPB
Port:                 80
Secure Port:          443
IP Address:           10.31.139.137
Name:                Celerra_VNX137
Port:                 80
Secure Port:          443


[nasadmin@VNX137 ~]$

If the external IP of Primary Control Station is not matching then follow the Scenario 3 in KBA https://support.emc.com/kb/448653 otherwise go further.

(nas_cs -set -hostname )

As root run below commands:
# /nas/http/webui/bin/domain_admin -i
# /nas/sbin/naviseccli -h SPA -user sysadmin -password -scope 0 domain -messner -add -system
# /nas/http/webui/bin/update_domain_directory.pl

Then verify the updated domain files:
[nasadmin@VNX137 ~]$ ll /nas/http/domain
total 13
drwxr-xr-x 2 apache apache 1024 Sep  1 10:20 bak
-rw-r--r-- 1 apache apache   64 Sep  8 12:00 domain_list
-rw-r--r-- 1 apache apache  194 Sep  8 12:00 domain_master
-rw-r--r-- 1 apache apache 6764 Sep  8 12:00 domain_provider_xml
-rw------- 1 apache apache   58 Sep  8 12:00 domain_users
-rw-r--r-- 1 apache apache   47 Sep  1 10:20 domain_version
drwxr-xr-x 2 apache apache 1024 Nov 14  2013 ldap
-rw-r--r-- 1 apache apache    0 Aug 23 14:46 lock_file

Now, login to Unisphere to verify if the alert is cleared and the File options are up.

---------------------------------------------------------------------------------------------------------------------------

If the File options are still grayed out or the same warning is still there, then Recover the domain as follows:
[nasadmin@VNX137 ~]# /nas/http/bin/set_passphrase
[nasadmin@VNX137 ~]#  /nas/sbin/cst_setup -getKey domain
[nasadmin@VNX137 ~]#  /nas/sbin/naviseccli -h SPA -user sysadmin -password -scope 0 domain - messner -recover

WARNING: This operation will destroy the old domain and create a new domain of one system with sysadmin/sysadmin credentials. Promote a different system to domain master and remove this one from a larger domain before continuing. Proceed? (y/n) y

Note: This unjoin the array from the domain and makes it single domain. Also,this would reset the sysadmin password back to default "sysadmin"  then you can go in the GUI and change it.

This process recovers the whole domain but it removes all global users and LDAP config and recreates sysadmin with default password.


[nasadmin@VNX137 ~]$ ll /nas/http/domain
total 13
drwxr-xr-x 2 apache apache 1024 Sep  1 10:20 bak
-rw-r--r-- 1 apache apache   64 Sep  8 12:00 domain_list
-rw-r--r-- 1 apache apache  194 Sep  8 12:00 domain_master
-rw-r--r-- 1 apache apache 6764 Sep  8 12:00 domain_provider_xml
-rw------- 1 apache apache   58 Sep  8 12:00 domain_users
-rw-r--r-- 1 apache apache   47 Sep  1 10:20 domain_version
drwxr-xr-x 2 apache apache 1024 Nov 14  2013 ldap
-rw-r--r-- 1 apache apache    0 Aug 23 14:46 lock_file

Now, login to Unisphere to verify if the alert is cleared and the File options are up.

In case of multidomain system, on recovering the domain the boxes will disappear from the domain which you can observe from below command
[nasadmin@VNX137 ~]$ /nasmcd/sbin/navicli -h spa domain -list

In that case, open Unisphere for this Master Node and start to add box by box as per the steps below.

a - Open Unisphere for this Master box.
b - Press the domain button.
c - Click on Add/Remove system from the right side.

You can start to add the Boxes to the domain through CLI by using the following command.

/nas/sbin/navicli -h spa -user sysadmin -password sysadmin -scope 0 domain -add xxx.xx.xx.xx -olduser sysadmin -oldpassword sysadmin -oldscope 0 -o

-Ramya