Adresses are 10.10.20.27 & 28, the managementserver has 10.10.9.81 and my workstation (where it works) has 10.70.1.63, but I don´t think its a network issue since everything else in the 10.10.20 net is reachable from the managementserver.
Navisphere is not reachable from the meanagementserver.
So you can start Navisphere from your desktop, but you can not start Navisphere from the Management Workstation?
You can ping the Management Ports on the SP from you desktop but you can not ping from the Management Workstation?
Seems like the problem is with the network between the Management Workstation and the array. Have you tried tracert?
Can you ping from the array to the Management Workstation? Right click on SPA and select Advanced Networking/Ping - in the Source drop down, select the IP address for SPA and the target as your desktop or the Management Workstation. You can also do a tracert.
2. from all workstations tested, you can ping the array
3. from the management station, you can not ping the array, but you can ping other workstations
I would suggest running tracert from the management station when you ping the array.
You might want to check the subnetting on the managment station and the array. This really sounds like a network conguration issue. Are you using DNS? Can you ping the hostname?
As Glen suggested, triple check the subnet mask entry on the array and management station. The subnet for your workstation is far enough apart that an incorrect subnet mask would easily explain this problem.
For example, if the mask *should be* 255.255.255.0 but you have 255.255.253.0, this problem could occur, and based on the symptoms I would lean toward the SPs network configuration.
The one thing that throws me off though is that this worked for a while, then stopped working. So unless someone changed the configuration on the SPs or Management station when it broke, misconfiguration doesn't explain the problem. Have you tried restarting the Management Server on each SP? Not rebooting the SP but just restarting management. It's possible that SMI-S locked up some process on the SP.
It turns out it was because 2 dummy ip's were set to prevent the navisphere from comming with an iscsi error everytime we logged in. They were set with th subnet mask 255.255.0.0. I had forgotten all about that.
kelleg
4 Operator
•
4.5K Posts
0
October 21st, 2010 11:00
What model clariion?
What is IP address for Management Ports
Can you acces Navisphere from IE?
glen
ekstrom
7 Posts
0
October 21st, 2010 23:00
CX4-240
Adresses are 10.10.20.27 & 28, the managementserver has 10.10.9.81 and my workstation (where it works) has 10.70.1.63, but I don´t think its a network issue since everything else in the 10.10.20 net is reachable from the managementserver.
Navisphere is not reachable from the meanagementserver.
kelleg
4 Operator
•
4.5K Posts
0
October 22nd, 2010 07:00
So you can start Navisphere from your desktop, but you can not start Navisphere from the Management Workstation?
You can ping the Management Ports on the SP from you desktop but you can not ping from the Management Workstation?
Seems like the problem is with the network between the Management Workstation and the array. Have you tried tracert?
Can you ping from the array to the Management Workstation? Right click on SPA and select Advanced Networking/Ping - in the Source drop down, select the IP address for SPA and the target as your desktop or the Management Workstation. You can also do a tracert.
glen
ekstrom
7 Posts
0
October 25th, 2010 00:00
Correct.
Correct.
I don't think it´s with the network because everything else is reachable.
I can ping everything from the sp's
kelleg
4 Operator
•
4.5K Posts
0
October 25th, 2010 10:00
Just to make sure I have this correct:
1. from the array you can ping any workstation
2. from all workstations tested, you can ping the array
3. from the management station, you can not ping the array, but you can ping other workstations
I would suggest running tracert from the management station when you ping the array.
You might want to check the subnetting on the managment station and the array. This really sounds like a network conguration issue. Are you using DNS? Can you ping the hostname?
glen
Storagesavvy
474 Posts
0
October 25th, 2010 11:00
As Glen suggested, triple check the subnet mask entry on the array and management station. The subnet for your workstation is far enough apart that an incorrect subnet mask would easily explain this problem.
For example, if the mask *should be* 255.255.255.0 but you have 255.255.253.0, this problem could occur, and based on the symptoms I would lean toward the SPs network configuration.
The one thing that throws me off though is that this worked for a while, then stopped working. So unless someone changed the configuration on the SPs or Management station when it broke, misconfiguration doesn't explain the problem. Have you tried restarting the Management Server on each SP? Not rebooting the SP but just restarting management. It's possible that SMI-S locked up some process on the SP.
ekstrom
7 Posts
0
October 26th, 2010 02:00
The subnet mask and gateway is the same as on my celerra and all my switches.
I can't ping the hostname, but I don´t think I have ever been able to.
Refreshing the management server state and restarting the management server did not help.
I do believe it has something to do with the smi-s. I have uninstalled it now.
kelleg
4 Operator
•
4.5K Posts
0
October 26th, 2010 06:00
With smi-s removed, were you able to ping the array?
glen
ekstrom
7 Posts
0
October 27th, 2010 01:00
Sadly, no.
ekstrom
7 Posts
0
October 27th, 2010 06:00
Ok. Problem solved.
It turns out it was because 2 dummy ip's were set to prevent the navisphere from comming with an iscsi error everytime we logged in. They were set with th subnet mask 255.255.0.0. I had forgotten all about that.
Thank you for yor help