There is usually a virtual IP which failover/failback to the primary CS. Try pointing your browser to that IP instead of the CS IPs which stays with it. Also check whether all the NAS partitions are getting mounted on CS0. If not mount it manually and wait for few minutes and the GUI will open.
Hey Balaji and thank you for your time and effort.
i have found a few things interesting:
1. at the messages file i have found this line --> Jun 11 10:25:10 xxxx-cs0 get_backend_status: Storage System xxx00121000xxx not responding to ping !, however i am able to ping SPA and SPB from the ssh session to CS0.
2. proxy arp is running:
Public IP address for SPA: 192.168.100.246
Public IP address for SPB: 192.168.100.247
Start on boot : yes
Current implementation : Proxy-ARP
Status : Started
3. storage check failed:
[root@xxxx-cs0 nasadmin]# nas_storage -c -a
Discovering storage on xxxx-cs0 (may take several minutes)
Error 5026: xxx00121000xxx d7, Unknown, doesn't match any storage profile
Error 5017: storage health check failed
xxx00121000xxx d7, no storage API data available
4. /nas/sbin/navicli -h spa domain -list ---> looks right to me but i paste it anyway
Assaf_Cahlon
6 Posts
0
June 5th, 2013 09:00
when CS1 is primary i can see the gui and also to log in successfully. when CS0 is primary i get nothing.
cincystorage
2 Intern
•
467 Posts
0
June 5th, 2013 09:00
Is CS1 responging via the unispere interface at all? Can you see the gui just not log in, or no gui at all?
Assaf_Cahlon
6 Posts
0
June 5th, 2013 09:00
yes i cas access both CS0 and CS1 with ssh.
cincystorage
2 Intern
•
467 Posts
0
June 5th, 2013 09:00
After running your cs_standby, can you ping/ssh the interface on the control station?
Assaf_Cahlon
6 Posts
0
June 5th, 2013 09:00
yes i am aware of the time that the process takes. right now its about 2 hours after the cs_failover finished.
etaljic81
1K Posts
0
June 5th, 2013 09:00
How long did you wait? It usually takes 10-15 minutes
Narahari1
2 Intern
•
127 Posts
0
June 6th, 2013 12:00
There is usually a virtual IP which failover/failback to the primary CS. Try pointing your browser to that IP instead of the CS IPs which stays with it. Also check whether all the NAS partitions are getting mounted on CS0. If not mount it manually and wait for few minutes and the GUI will open.
Rainer_EMC
4 Operator
•
8.6K Posts
0
June 6th, 2013 14:00
I believe the virtual IP for dual control stations isn’t created by default
Check the documentation about control station IP alias
Assaf_Cahlon
6 Posts
0
June 9th, 2013 04:00
i have compered between the two CS mount list. both shows the same info when each is the Primary CS:
/dev/hda3 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda1 on /boot type ext3 (rw)
/dev/mapper/emc_vg_sec_ide-emc_lv_home on /home type ext3 (rw)
/dev/mapper/emc_vg_sec_ide-emc_lv_celerra_backup on /celerra/backup type ext3 (r w)
/dev/mapper/emc_vg_sec_ide-emc_lv_celerra_backendmonitor on /celerra/backendmoni tor type ext3 (rw)
/dev/mapper/emc_vg_sec_ide-emc_lv_celerra_audit on /celerra/audit type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
/dev/nde1 on /nbsnas type ext3 (rw,sync)
/dev/hda5 on /nas type ext3 (rw,sync)
/dev/nda1 on /nbsnas/dos type msdos (rw,sync,umask=002,gid=201)
/dev/mapper/emc_vg_lun_0-emc_lv_nbsnas_jserver on /nbsnas/jserver type ext3 (rw)
/dev/mapper/emc_vg_sec_ide-emc_lv_nas_jserver on /nas/jserver type ext3 (rw)
/dev/mapper/emc_vg_lun_5-emc_lv_nas_var on /nbsnas/var type ext3 (rw)
/dev/mapper/emc_vg_lun_5-emc_lv_nas_var_dump on /nbsnas/var/dump type ext3 (rw)
/dev/mapper/emc_vg_lun_0-emc_lv_nas_var_auditing on /nbsnas/var/auditing type ex t3 (rw)
/dev/mapper/emc_vg_lun_5-emc_lv_nas_var_backup on /nbsnas/var/backup type ext3 ( rw)
/dev/mapper/emc_vg_lun_5-emc_lv_nas_var_emcsupport on /nbsnas/var/emcsupport typ e ext3 (rw)
/dev/mapper/emc_vg_lun_5-emc_lv_nas_var_log on /nbsnas/var/log type ext3 (rw)
/dev/mapper/emc_vg_sec_ide-emc_lv_celerra_commoncache on /celerra/commoncache ty pe ext3 (rw)
/dev/mapper/emc_vg_sec_ide-emc_lv_celerra_ccc on /celerra/ccc type ext3 (rw)
/dev/mapper/emc_vg_sec_ide-emc_lv_celerra_wbem on /celerra/wbem type ext3 (rw)
/dev/mapper/emc_vg_lun_5-emc_lv_nbsnas_udoctor on /nbsnas/udoctor type ext3 (rw)
/dev/mapper/emc_vg_sec_ide-emc_lv_nas_udoctor on /nas/udoctor type ext3 (rw)
how can i manually mount the nas if its not mounted?
thanks
Assaf_Cahlon
6 Posts
0
June 11th, 2013 01:00
Hey Balaji and thank you for your time and effort.
i have found a few things interesting:
1. at the messages file i have found this line --> Jun 11 10:25:10 xxxx-cs0 get_backend_status: Storage System xxx00121000xxx not responding to ping !, however i am able to ping SPA and SPB from the ssh session to CS0.
2. proxy arp is running:
Public IP address for SPA: 192.168.100.246
Public IP address for SPB: 192.168.100.247
Start on boot : yes
Current implementation : Proxy-ARP
Status : Started
3. storage check failed:
[root@xxxx-cs0 nasadmin]# nas_storage -c -a
Discovering storage on xxxx-cs0 (may take several minutes)
Error 5026: xxx00121000xxx d7, Unknown, doesn't match any storage profile
Error 5017: storage health check failed
xxx00121000xxx d7, no storage API data available
4. /nas/sbin/navicli -h spa domain -list ---> looks right to me but i paste it anyway
Node: CS0
IP Address: 192.168.100.247
Name: SPB
Port: 80
Secure Port: 443
IP Address: 192.168.100.246 (Master)
Name: SPA
Port: 80
Secure Port: 443
IP Address: 192.168.100.248
Name: Celerra_xxxx-cs0
Port: 80
Secure Port: 443
6. nas is already mounted
7. nas service is running
thank you very much for your help and time this is really appreciated!
Assaf
Vipin VK
2 Intern
•
812 Posts
0
June 11th, 2013 01:00
You should be finding a primus solution by simply searching (support.emc.com)
"Error 5026: xxx00121000xxx d7, Unknown, doesn't match any storage profile"
It says you may have deleted unused LUNs from backend without deleting the same from File side. Hope this solution will resolve your issue.