ESX3.5 and MD3200i

[eosserver]

hi

We are using a simple configuration with a 2 node cluster with ESX 3.5 U4,  a virtual center machine (ESX 3.5), storage md3000i

All esx3.5, all Vmkernel and md300i have IP 10.1.1.*

yestrday i try to add a new storage: MD3200i

New Storgae use ip icsci 192.168.13*.*   (default configuration)

into ESX i try to add a new Vswith with VMkernel 192.168.130.1 but ESX3.5 (RESCAN STORAGE) don't find storage

I must change IP into ICSCI CONFIGUTAIONT FROM 192* to 10* ?

Thanks
Regards

[FranckRookie]

Hi Eosserver,

Your vmkernel is 10.1.1.21 with a subnet mask of 255.255.255.0 . Every target outside the 10.1.1.x network is unreachable. You need to modify your new storage network configuration. Check with a simple "vmkping" to verify if you can reach it through the network before trying to attach the storage device.

Good luck.

Regards

Franck

[IRIX201110141]

Just edit the Network settings for the iSCSI Ports of your new MD3200i. You can choose between a setup with 4 different iSCSI Subnet or just one.  For the later DELL have an "vSphere howto" but youre using VI 3.5 so i'would go for the different Subnet method in the same way youre using your MD3000i. You can add some additional VMKs/SC if needed.

Be sure that you create a Hostgroup and add the Host IQNs on MD3200i side to get access to the virtual disks. Without that your ESX hosts never will see any LUN.

Regards

Joerg

[eosserver]

Thanks for you answer

I add  vSwitch2 (vswitch1)

i add vmkernel with subnet 192

now i've vswitch0 for old MD3000i

and vswitch for new MD3200i

i try ping from ssh and ping is ok to all 8 ips (ip address hosts ports)

i add Mapping and host on PMDSM

i click on esx 3.5 up4, "Storage adapter", click Rescan but no found md3200i:(

i try to add only firts IP 192.168.130.101 on ISCSI INITIATOR and rescan, but nothing

thanks in advance..

But can I add 2 storage iscsi to ESX 3.5?
can i add md33200i to ESX 3.5?

I hope the problem is some ips configuration and not compatibility or storage number

Sorry for my english

[IRIX201110141 · Accepted solution]

The old ESX 3.5 need a Service Console in the iSCSI net for discovering the iSCSI target. This was not necessary when using ESXi 3.5 or vSphere.

The md32x0i is not certified for ESX 3.5 because the modell is from q4/2010 and vSphere 4.x was available for 1.5 years right now.

Regards

Joerg

[eosserver]

GREAT  ALTIX!

To inform who will have my same problem (i hope this is right)

ESX 3.5
MD3200i

1)
enter into esx and add VSWITH and configure VMKERNEL
1 vmkernel for every subnet

1Virtual console (here i must understand a little problem..about Ips ****)

2)

open Md3200i management and add HOST.
Name your host and choose network

3)

open esx and rescan storage

Now all SCSCI TARGET arfe on ESX

------------------------------------------------

only a problem

I add Virtual Console with IP 192.168.130.110 netmask 255.255.0.0 (i try with 255.255.255.0 too)

But is not right configuration.

IPS ISCSI are

192.168.130.101    netmask 255.255.255.0

192.168.130.102    netmask 255.255.255.0

192.168.131.101  netmask 255.255.255.0

192.168.131.102  netmask 255.255.255.0

192.168.132.101  netmask 255.255.255.0

192.168.132.102  netmask 255.255.255.0

192.168.133.101  netmask 255.255.255.0

192.168.133.102  netmask 255.255.255.0

Vmkernel

192.168.130.100  netmask 255.255.255.0

192.168.131.100  netmask 255.255.255.0

192.168.132.100  netmask 255.255.255.0

192.168.133.100  netmask 255.255.255.0

I must find right configuration for Service Console don't receive error like these

Connection to Discovery Address 192.168.132.102 failed
Connection to Discovery Address 192.168.133.102 failed

Connection to Discovery Address 192.168.131.102 failed

I've these errors on 3 Ips because Virtual Console has not right ips configuration

THANKS