Unsolved
This post is more than 5 years old
3 Posts
0
4503
October 3rd, 2013 06:00
Celerra Unisphere Blank Blue Screen
Hello,
I've been all over trying to solve this. We upgraded our Celerra to VNX series but still have Celerra up and running connected to 3 Hosts via ISCSI.
We did an upgrade to VMware 5.1 and on two of the hosts, the networking was deleted. no problem, we fixed but now on those two hosts, we cannot see the ISCSI. We have verified all on the hosts and it appears to be okay.
Trying to get into the Celerra to make sure the ISCSI LUNs permission is good for the Initiators, we cannot.
We have tried many clients, IE8, IE9, win7, win2008, win2003 and when trying to login, we get the JAVA messages and the splash screens for unisphere but never get a login. Just a blank blue screen.
We have verified the time on the Celerra and timezone. We have re-generated the SSL as well as rebooting the CS.
Am I missing something? Of course, we have done this before and its been about 6 months since we migrated to the VNX so we have not tried since then to manage the Celerra.
Its not critical yet but may become in the near future.
Or if I can get the CLI commands to make sure that the IP addresses for the ISCSI NICs in the hosts are allowed to connect to the Celerra, that would work too.
Thanks for any help.
Ron
umichklewis
3 Apprentice
•
1.2K Posts
1
October 3rd, 2013 09:00
If you SSH to the Control Station, you can use man server_iscsi to get the man page for the iSCSI software.
You can use server_iscsi server_2 -target -info -all to see which hosts are logged into which iSCSI targets. If you don't see hosts you expect to see, you can check the iSCSI LUN mask with server_iscsi -mask -list and see which hosts are permitted on which targets.
Let us know if that helps!
Sue5
13 Posts
0
October 3rd, 2013 13:00
What version of JAVA are you using with IE? I had to have a very current level of JAVA AND I had to access the control station by IP address.
JimBrown101
3 Posts
0
October 3rd, 2013 20:00
Here's the output.
I see only one host connected - VMware:host3 - is correct.
It also appears that the other two hosts, VMware:host4 and VMware:host5 have permission (from second command) ?
issue on VMware host side?
Thanks
[nasadmin@san01 ~]$ /nas/bin/server_iscsi server_2 -mask -list
server_2 :
target: iscsi_target_1
initiator_name grant LUNs
iqn.1998-01.com.vmware:host3-3b068352 0,10,12-15
iqn.1998-01.com.vmware:host1-13198181 0,10,12-15
iqn.1998-01.com.vmware:host1-66c1ee62 0,10,12-15
iqn.1998-01.com.vmware:vmhost4-38fd1fac 0,10,12-15
iqn.1998-01.com.vmware:vmhost5-70a1bd91 0,10,12-15
[nasadmin@san01 ~]$ /nas/bin/server_iscsi server_2 -target -info -all
server_2 :
Target Alias Name: iscsi_target_1
Target iSCSI Name: iqn.1992-05.com.emc:sl7e91004000360000-3
Serial Number: 3
Portal Group Tag: 1
Portal: 10.10.0.1:3260
Portal: 10.11.0.1:3260
Logical Units:
0 : (Production) fsid=30 size=652000MB alloc=592461MB dense path=/VMFS_2/fs30_T3_LUN0_SL7E9100400036_0000/fs30_T3_LUN0_SL7E9100400036_0000
10 : (Production) fsid=25 size=639500MB alloc=518450MB dense path=/VMFS_1/fs25_T3_LUN10_SL7E9100400036_0000/fs25_T3_LUN10_SL7E9100400036_0000
12 : (Production) fsid=29 size=1340000MB alloc=1302992MB dense path=/VMFS_3/fs29_T3_LUN12_SL7E9100400036_0000/fs29_T3_LUN12_SL7E9100400036_0000
13 : (Production) fsid=28 size=1340000MB alloc=1316587MB dense path=/VMFS_4/fs28_T3_LUN13_SL7E9100400036_0000/fs28_T3_LUN13_SL7E9100400036_0000
14 : (Production) fsid=31 size=1760000MB alloc=1727929MB dense path=/VMFS_5/fs31_T3_LUN14_SL7E9100400036_0000/fs31_T3_LUN14_SL7E9100400036_0000
15 : (Production) fsid=32 size=1760000MB alloc=1134068MB dense path=/VMFS_6/fs32_T3_LUN15_SL7E9100400036_0000/fs32_T3_LUN15_SL7E9100400036_0000
Connected Initiators:
iqn.1998-01.com.vmware:host3-3b068352
Target Alias Name: iscsi_target_2
Target iSCSI Name: iqn.1992-05.com.emc:sl7e91004000360000-5
Serial Number: 5
Portal Group Tag: 1
Portal: 10.11.0.1:3260
Portal: 10.10.0.1:3260
No Logical Units
Connected Initiators:
iqn.1998-01.com.vmware:host3-3b068352
[nasadmin@san01 ~]$ /nas/bin/server_iscsi server_2 -mask -list
server_2 :
target: iscsi_target_1
initiator_name grant LUNs
iqn.1998-01.com.vmware:host3-3b068352 0,10,12-15
iqn.1998-01.com.vmware:host1-13198181 0,10,12-15
iqn.1998-01.com.vmware:host1-66c1ee62 0,10,12-15
iqn.1998-01.com.vmware:vmhost4-38fd1fac 0,10,12-15
iqn.1998-01.com.vmware:vmhost5-70a1bd91 0,10,12-15
JimBrown101
3 Posts
0
October 3rd, 2013 20:00
Thank you for the replies. I will try the commands and report.
What would be the command to permit an IP should that be the case? This is exactly what I was going to check via the GUI - what I did when we installed the two new hosts.
Thanks
Sue5
13 Posts
0
October 4th, 2013 07:00
Hi Ron,
Sorry I wasn't very clear in my post. What I meant was to logon to the control station vai GUI I had to use the IP address for example https://111.22.255.1 (The IP instead of the fully qualified domain name). That got me passed the blue screen issue and I could use the GUI again.
Hopefully you can get the GUI to work.
Thanks Sue