This post is more than 5 years old
2 Posts
0
2609
PowerVault MD3200i - Unable to Ping (or use) RAID ISCSI ports
Hi
We have a MD3200i with two RAID controllers each with 4 ports (so 8 ports total), after a recent power cut (longer than UPS could help so servers shutdown) everything seems to have come back online fine but the Power Vault seems to have a problem with its iSCSI ports.
The two RAID controllers are setup with 4 subnets and previously I was able to use (and ping) them using servers connecting via those subnets, now I can only use/ping 1 port (RAID 0, Port 0) all other ports do not respond to pings.
I've tried changing the IP address on those none responsive ports but they still won't respond.
Settings are:
RAID0
--Port0 192.168.20.5
--Port1 192.168.21.5
--Port2 192.168.22.5
--Port3 192.168.23.5
RAID1
--Port0 192.168.20.6
--Port1 192.168.21.6
--Port2 192.168.22.6
--Port3 192.168.23.6
Server
-- NIC1 : 192.168.20.100
-- NIC2 : 192.168.21.100
-- NIC3 : 192.168.22.100
Ignoring subnet 192.168.23.xx for the moment (as the server I'm testing with only has the three NICs, though others servers are on that .23 subnet and can't talk to the RAID ports either) the ONLY port/IP that responds to PING or iSCSI initiator is 192.168.20.5 (Raid 0, port 0).
I've tried changing the IPs (and the next day changing them back) in case the config was going wrong somehow, I've confirmed all RAID Ports and NICs on the same VLAN etc.
Is there anything else I can do to figure out what's wrong?
Any help much appreciated,
Iain
IainShadwell
2 Posts
1
December 28th, 2016 06:00
Hi,
Since creating this post I've been able to do a full shut down of our system (very hard to arrange as people are constantly using it).
I powered down all the connected servers and networking then turned the power off to the Powervault (literally removing power cables as there is no on/off process to my knowledge), then after powering things back on the RAID Ports are responding correctly again.
Hope this helps someone,
Iain