This post is more than 5 years old
2 Posts
0
1715
July 18th, 2011 07:00
MD3000i - Changing Network
Good day,
I have a MD3000i that was installed by my company's previous IT guy.... long before I got here. Now I'm expected to sort out his mess. :emotion-1:
In trying to track down some serious performance issues on our network, I came to suspect the MD3000i SAN. It currently resides on the same LAN as the rest of the company, with no subnets or VLANs or any separation at all. I aim to fix that. We acquired a Cisco SG200-18 small business switch, and I intend to migrate all of the iSCSI traffic onto this dedicated switch. I'm running into some issues, largely because I'm very new to the world of SANs (I believe).
The SAN array is hosted by two servers, and is configured with out-of-band management. I've been able to move the management interfaces onto the new dedicated network with no issues. I'm a bit at a loss as far as what steps to take to get the iSCSI host ports moved over and functioning correctly.
If anyone could just give me a sequence of events for what I need to be doing (change physical connector here, then change this settings, then this one), it would be very much appreciated.
Thanks in advance for helping me out. I feel so lost!
-John
JOHNADCO
2 Intern
•
847 Posts
1
July 18th, 2011 14:00
Change it using MDSM with out of band mgt... After changing it, restart the MD3000i.
We have had massive issues getting it to work without the power cycle.
The modify your host iSCSI initiators for the new discovery addresses.
If your hosts are using the san to boot from? I am not sure how to tell you to go about it at all.
Dev Mgr
6 Operator
•
9.3K Posts
•
3 Points
0
July 18th, 2011 12:00
The management ports should be plugged into your LAN and your iSCSI traffic needs to be on an isolated (from your LAN) VLAN or dedicated switch. Each server that needs to access storage on the array will need at least 1 NIC into the iSCSI VLAN/switch.
I'd change the iSCSI ports to something like the factory defaults and use 2 subnets:
Controller 0 iSCSI port 0: 192.168.130.101 /24
Controller 0 iSCSI port 1: 192.168.131.101 /24
Controller 1 iSCSI port 0: 192.168.130.102 /24
Controller 1 iSCSI port 1: 192.168.131.102 /24
jbowdre
2 Posts
0
July 18th, 2011 14:00
Thanks to you both for the information. Managed to get it working using an IP scheme similar to that suggested by Dev Mgr, with actions happening in order as suggested by JOHNADCO.
Thanks!