Start a Conversation

Unsolved

M

222 Posts

3073

October 8th, 2018 05:00

md3000i question

Hi,

We have an md3000i with 2 controler that we would like to connected to a server with a single switch.

The server is a power edge R710 with 4 nics.

Can we use the current 4 nics for ISCSI connection for use with the md30001? or we need to add 4 new iscsi enable nics to the server?

Thanks

222 Posts

October 8th, 2018 07:00

Hi,

We have an MD3000i with 2 controllers that was connected  directly to a single host.

The host that is connected to the md3000i has been crashed and we have a new server with a server 2016 OS and we want to connect this new host to the Array.

The data on the array is not importent becuase we have already restore the data from backup to a different storage.

Now we want to configure the Array throuw an single switch, .

can I connect both ISCSI controller of md3000i and connect 1 nic of the new server to this switch a give it an IP in the same range as ISCSI controller and run the installation on the new server and re discover the array again?

I would like also to add that I can access the md3000i management port from a virtual server in the same subnet as the mg ports.

Thanks

 

Moderator

 • 

8.5K Posts

October 8th, 2018 11:00

Hi,

Which model NICs are in the server? Most likely you can use the existing ones with iSCSI.

9.3K Posts

October 8th, 2018 13:00

NIC models don't really matter, as long as they are proper 1Gbit NICs (basically; Intel or Broadcom).

Do stick with the general guidelines for an MD3k; use 2 subnets for iSCSI and give one port on a controller an IP in one subnet, and the mirror port from the other controller another IP in the same subnet.

Example from default settings:

Controller 0 iSCSI port 0: 192.168.130.101

Controller 0 iSCSI port 1: 192.168.131.101

Controller 1 iSCSI port 0: 192.168.130.102

Controller 1 iSCSI port 1: 192.168.131.102

This will work fine still with a single switch. Using separate vlans is preferred, but as long as it is isolated from your LAN traffic (e.g. switch dedicated to just iSCSI traffic), they can co-exist till you can budget a second switch.

222 Posts

October 9th, 2018 00:00

Hi Josh,

 

Thanks for your reply,

I think the NIC's will work, becuase the NIC's are the same as the old server.

Does the software of MD3000i supported on a server 2016 server?

Thanks

222 Posts

October 9th, 2018 00:00

Sorry Guy's,I dont undertand why these 2 questions are mixed.

Thank you for your reply,

Because of single switch use, I think there is no use to us the port 1 of both controllers. I will give the same IP range to one of the NICs on the new server. Or should I connect all 4 ISCSI ports as you mentioned? (I dont have a Vlan on the switch)

Controller 0 iSCSI port 0: 192.168.130.101

Controller 1 iSCSI port 0: 192.168.130.102

what is the next steps? run the setup and run a auto discover?

Before the server crash we did install the storage managment on a VM machine and now when connect to the array from the VM I can see still the crashed server map to the array.

Is this correct way to replace the old server? after maping the new server to the array will we be able to use the data that is already on the Array?

 

Thanks

 

 

Moderator

 • 

8.5K Posts

October 9th, 2018 08:00

It should work fine with Server 2016.

222 Posts

October 10th, 2018 05:00

Hi Josh,

 

Thanks for your update,

I have taken the new server to the data center, connect one of the NICs of the server to a cisco catalyst 3950 g and also connect the port 0 of both controllers  to the cisco switch

Server NIC IP: 192.168.130.116

ISCSI port 0  controller 1 IP: 192.168.130.101

ISCSI port 0 Controller 2 IP : 192.168.130.102

Both management ports are connected to the LAN swtich, 10.0.10.165 and 10.0.10.169

In past we have had installed only the storage software on a second server, now when go to Edit Host topology still can see the crashed server.

What would be the correct next steps on the new server 2016?  Download the md3000i_2_2_0_18_R294936.iso and first install storage software and after that run the Moduler Disk Configuration utility?and map the new server to the SAN and then remove the crashed server?

Or becuase we have already storage manager on a different server (it says Array optimal) we must just run the Moduler Disk Configuration utility?

 

Thanks

 

 

Moderator

 • 

8.5K Posts

October 10th, 2018 09:00

You should be able to just install mdsm on the new server and find the array.

222 Posts

October 11th, 2018 00:00

Hi,

I try to install a full mdsm for md3000i on a server 2016 from md3000i_2_2_0_18_R294936.iso but get this error:

MPIO device specific Module installation failed md3000i

strange part is, I did reboot the server and now I can see the MPIO in de server manager!!

is this means the MPIO is not correctly installed? what should we do before go ahed with running the Modular Disck configuration utility

Thank

222 Posts

October 11th, 2018 00:00

Hi Josh,

 

Thanks for the update,

I will install MDSM on the new server and map it to the md3000i.

What should we do with the crashed server? I still see it as an host that is connected to the md3000! can I after maping the new server just remove the old server? remove the old host will not effect the data on the virtual disks right?

Or shoud we first remove the old server first? if I try to install the disk moduler utility before removeing the old server get this error, but I am not sure if becuse of this or becuase currenlty only port 0 of controller 0 (192.168.130.101) and port 0 of controller 1 (192.168.130.102) and one of de server NICs (192.168.130.110) connected to the same switch. (I have already open other post for this error)

iscsierror.JPG

 

Thanks

222 Posts

October 11th, 2018 02:00

Hi,

We have a md3000i with two controller. currently we have a single switch, we have connected the

Controller 0 Port 0 192.168.130.101

Controller 1 Port 0 192.168.130.102

Server Nic: 192.168.130.120

To the same switch.

connect the mamgment ports (10.0.10.15 and 10.0.10.16) of the md3000i to the the same lan as the server (10.0.10.11) second NIC

The port 1 of both controllers have IP address but are not connected to any swtich.

Now when run the Disk configuration utility on a Host I can discove the Array with management ports, when go to the ISCSI ports the port 0 of both controller is connected to the IP of the server but the port 1 of both controller is grayout and disconnected. Now when finish the inistall get this error:

 

iscsierror.JPG

Is this becuase the Ports 1 of the controller 0 and 1 is not connected? can I untill get a second switch connect the controller 1 port 0 and port 1 also to the same.switch? (currently no vlan on the switch)

 Or I should only use the ports of controller 0 and leave the controller 1 disconnected for this I will change the IP of port1 controller 0 to 192.168.131.101 and also connect a second NIC of the server (192.168.131.110) to the same switch?

Thanks

 

Moderator

 • 

8.5K Posts

October 11th, 2018 09:00

Right, just remove the old server once the new one is there. It won’t affect the data. I don’t think that error is because the old server is still there. It looks like something else with the networking configuration.

222 Posts

October 11th, 2018 13:00

is this config correct (with get error with this config)

controller 0 port 0= 192.168.130.101

controller 1 port 0= 192.168.130.102

server IP= 192.168.130.110

other ports of both controllers has ip but not connected

with old server we didnt have switch and crashed server was directly connected to controller 0 and this was the config

controller 0 port0= 192.168.130.101

controller 0 port 0= 192.168.131.101

server  IP nic1= 192.168.130.110

server IP nic2= 192.168.131.110

Thanks

 

 

Moderator

 • 

8.5K Posts

October 11th, 2018 14:00

That looks fine to me.

222 Posts

October 13th, 2018 10:00

Do I need 2 vlans for each iscsi subnets?

No Events found!

Top