faild to connect to the MD3000i iSCSI

Similar Questions

• Fundamental and MD3000i ISCSI concepts

  Hi all

  I try to understand the concepts in a MS Windows and especially the MD3000i iscsi environment and online help does not help much. I understand that you need an innitiator on a host to connect to a target. A target is a San with a large logic unit number or multiple LUNS. A target may have a gigabit ethernet port or two. Each NETWORK adapter on the target must have a unique IP address. This is the case with MD3000i with one controller or connection "simplex". Let's say I set up 4 starts: exchange, sharepoint, sql, and files. These 4 starts will connect to 4 servers. Each server has two NETWORK adapter, an intranet, an iscsi network.  I only use a single NIC on the MD3000i, as I understand it, if I put the IP address of the target when configuring host innitiator on 4 servers. This means that a 1 GB connection is shared between 4 servers. Is this correct?

  Second, by presenting the diskgroup to the appropriate host, avoid a host 'touch' the another diskgroup host?

  For example, using the second NIC on the MD3000i, I will divide halved. I have to point two servers to a new IP address in the MS innitator and attend the diskgroup these two hosts correctly in the MD3000i. Is this a correct concept?

  Is it possible to combine two network cards on the MD3000i so that its total output/bandwidth is 2 GB?

  Now we have a second controller, which makes things more confusing for me. At this point, I would like to note that I speak not of "high availability of applications. In one controller, a controller has 4 starts. IIF this controller 0 failed, I'll lose data. In one two controllers, two controllers are configured as active/active. My understanding is that controller 0 can now own one or all four starts (or 2 own diskgroup and controller 1 has the diskgroup remaining, 3, and 4). So, in this case, my server must point to the 2 different IP addresses on the second controller. For simplicity, all IP addresses are the same subnet. Assuming that the controller 0 is broken, the diskgroup 1.2 will change ownership to controller 1.  Now, controller 1 will hold 4 starts. However, my server 1.2 will lose the iscsi network connectivity. In order for me to get the data back, I'll have to reconfigure the iscsi innitator pointing to the IP address of the controller 1. The question is, what IP addresses on the two network adapters on controller 1.

  I understand that if I want to achieve high availability of applications, I have 2 network cards on the server dedicated for iscsi between two controllers.

  I read this article and it has confused me more:

  http://support.Dell.com/support/eDOCS/systems/MD3000i/multlang/TS/FR483-info%20update/FR483A00MR.PDF

  According to this article: "two network cards on a controller can be aggregated to provide optimal performance. A host can be configured to simultaneously use the bandwidth of both ports on a controller of virtual disks, held by the access controller". This means that the total production is 2gbs? So in my case, is it possible to do it when I have a NETWORK to the iscsi network interface card? How to configure the host to take advantage of this?

  I know that I have a lot of questions, since it is a new concept for me. Thanks in advance for your time.

  
  

• VMkernel journal peripheral qualifier suggests 0 x 1 errors not supported for the MD3000i railways

  I have a vSphere cluster connected to the MD3000i and its configured by the book on two different subnets for each port on each controller. Robin is enabled for multi pahing on VC.

  That's what I see in newspaper vmkernel

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.613 cpu4:6882) ScsiScan: 839: Path 'vmhba33:C0:T0:L0': seller: "DELL" model: Rev 'MD3000i': '0735' "»

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.613 cpu4:6882) ScsiScan: 842: Path "vmhba33:C0:T0:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.613 cpu4:6882) ScsiScan: 105: path 'vmhba33:C0:T0:L0': peripheral qualifier 0 x 1 not supported

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.618 cpu4:6882) ScsiScan: 839: Path 'vmhba33:C1:T0:L0': seller: "DELL" model: Rev 'MD3000i': '0735' "»

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.618 cpu4:6882) ScsiScan: 842: Path "vmhba33:C1:T0:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.618 cpu4:6882) ScsiScan: 105: path 'vmhba33:C1:T0:L0': peripheral qualifier 0 x 1 not supported

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.623 cpu4:6882) ScsiScan: 839: Path 'vmhba33:C2:T0:L0': seller: "DELL" model: Rev 'MD3000i': '0735' "»

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.623 cpu4:6882) ScsiScan: 842: Path "vmhba33:C2:T0:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.623 cpu4:6882) ScsiScan: 105: path 'vmhba33:C2:T0:L0': peripheral qualifier 0 x 1 not supported

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.628 cpu4:6882) ScsiScan: 839: Path 'vmhba33:C3:T0:L0': seller: "DELL" model: Rev 'MD3000i': '0735' "»

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.628 cpu4:6882) ScsiScan: 842: Path "vmhba33:C3:T0:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  21 sep 16:19:29 db-esx2 vmkernel: 6:04:15:02.628 cpu4:6882) ScsiScan: 105: path 'vmhba33:C3:T0:L0': peripheral qualifier 0 x 1 not supported

  I see this on the two hosts vmkernel journal...

  should I be worried. "This isn't necesserely showing error but:" device qualifier 0 x 1 not supported "gets my attention.

  If you have NOT of LUNS assigned as Lun0 then you will get this error.   So always start with LUN Lun0 aka: Lun0 - first record entrust you, Lun1 - second disc etc.  You have not neccessarly to reallocate your currently lun, you could create a new lun and presenting it as Lun 0.     So try that if you are able to create a new Lun.   Otherwise if you have existing virtual machines running on the current Lun5 you would have to stop them, being cancelled at them in inventory, change the Monday from 5 to 0 and then re-record their I think.    Also, make sure that you do not jump also any number of LUNs... aka go Lun0, Lun1 and Lun2 Lun3 etc.

• Differences between the ISCSI connections to the storage in vSphere 4.1 and 5.0.

  I'm in trouble of setting up the connections of storage in a new VSphere 5.0 test environment. In our environment VSphere 4.1, it was possible to create a virtual switch add two Broadcom NetXtreme II 5709 NIC. Set assets. IP Hash value as load balancing. (LACP Etherchannel on physical switches) This configuration uses a grain port and a single IP address. Then add our NetApp NFS storage and ISCSI Equillogic storage. In VSphere 5.0, I can't create this same configuration. I have to create separate with separate IP addresses vmkernal ports? The idea was to have redundant connections to the storage and flow of these two NETWORK cards. Possibly adding additional if necessary to the futuer NETWORK cards. Any help with this would be greatly appreciated.

  How can I work around this:

  "VMkernel network adapter must have an active link exactly and no waiting rising to be eligible for the iSCSI HBA connection."

  I can certainly say that the way which allows you to configure the iSCSI Multipathing is incorrect.

  The main idea is to let Native Multipathing Plugin to decide what network path to choose, not the vSwitch.

  At the level of the network layer, you must have 1 VMK by a physical NIC.

  This technique applies as well for vSphere 4.1 and 5.0, but with the 5.0 it is configured easier and more quickly.

  Here's a very brief consequence of steps

  1. get 2 VMK interfaces and assign an IP by each VMK.

  2. set each VMK to use only one physical NETWORK adapter

  3 GB with storage iSCSI software adapter, turn it on and bind your VMKs 2.

  4 connect to your iSCSI storage space

  5 rescan devices, create the VMFS datastore

  6. set the desired load balancing VMFS method or just set up a prior default create new VMFS

  and it is strongly recommended to read this guide - http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-storage-guide.pdf

• After that stright connected to iSCSI (initiator) Host cannot ping the server iSCSI (target), but the target can, why?

  After that host on vSHere 4.0 strightly connected to iSCSI (initiator) host cannot ping the server iSCSI (target), but target can.  And iSCSI works well. I mean I can create and use the iSCSI disk, why? It makes me confused.

  Thank you!

  Geoarge,

  iSCSI traffic uses a VMkernel port, instead of using the command 'ping', use 'vmkping '.

  André

• Connect the NAS (iSCSI) to vSphere using the crossover Ethernet cable

  Hello

  I have a HP Proliant DL360 G5 in a data center (housing) directly connected to the internet. To save all the VM I would fix a NAS (QNAP with iSCSI) on the server. But given that the server is connected only to a 100 Mbps switch (supplier provide only 100 Mbit) I am looking for a direct solution to enjoy better performance.

  I use on my Proliant Server internal dual port NIC (VMNIC0 and VMNIC1) and an additional port of double NC360T NIC (VMNIC2 and VMNIC3). I made two switches, with VMNIC0 and VMNIC2 vSwitch0 and vSwitch1 with VMNIC1 and VMNIC3 for redundancy. Each vSwitch has its own service with the public IP console.

  Because I would like to continue using the above configuration, it came into my mind to buy an additional network (NC110T with 1 NIC) of the card and use a crossover cable directly to QNAP NAS. The NAS has two NIC, we'll be fixed as said to the ESX and directly to the internet (to manage from outside).

  But now I don't know how to configure it. What should I do that the ESX will intervene to the NAS, and what type of IP address I need to adjust on the NAS to talk to the ESX?

  What I have to configure a vSwitch2 (with physical adapter NC110T) and a new Console of Service with a private IP address: for example. 192.168.1.1 and the card NETWORK NAS Port that connects to the ESX, I put 192.168.1.2 and then it should be possible to work with ISCSI? I can then add the storage in vSphere?

  I would really appreciate if someone understands perfectly how such things can give me an advice!

  Thank you very much

  Best regards

  Phil

  It sounds like a good plan and you have the process down to the right.

  • After the installation of the new card as you did for the first configuration, you should see additional network cards.

  • • You create a new vSwitch for the internal network segment that connects the NAS and ESX you note and add these network adapters

    • Then you create the port console and IP address on the private network

  • Now both devices may be

  • In QNAP, you create your iSCSI target or your NFS volume

  • For iSCSI you go to storage adapters - properties - add the ip address of the NAS and then close and discover

  • • This should find the paths of the target.

    • Then you go into storage and add and format the iSCSI volume

  • For NFS, you go straight to the storage and add the name address and NAS volume and turn up the volume of storage

  All storage will be visible and usable by ESX.

  Steve Puluka

  JNCIA-ER

  JNCIA-EX

  Senior network administrator

  Liberty Dialysis

  http://puluka.com/home

• MD3000i iSCSI host RHEL4 connetion problems

  I have a MD3000i directly connected to a PE1750 with RHEL4.5 I iscsi utils installed and to the best of my knowledge that the MD3000i is configured correctly, but I am not able to fdisk the storage on the server.  In the logs I get this when I start iscsi:

  Jul 24 16:24:20 dev3 kernel: sdb: unknown partition table

  Jul 24 16:24:20 dev3 kernel: Attached scsi disk sdb to scsi9, channel 0, id 0, lun 31

  Jul 24 16:24:20 dev3 kernel: Attached scsi generic sg3 scsi9, channel 0, id 0, lun 31, type 0

  Jul 24 16:24:20 scsi.agent dev3 [6168]: disc/devices/platform/host9 / target9:0:0 / 9:0:0:31

  Jul 24 16:24:23 dev3 kernel: iscsi - sfnet:host10: Connect failed with CR - 113: no route to host

  Jul 24 16:24:23 dev3 kernel: iscsi - sfnet:host10: establish_session failed. Could not connect to the target

  Jul 24 16:24:23 dev3 kernel: iscsi - sfnet:host10: waiting 1 second before the next attempt to connect

  Jul 24 16:24:27 dev3 kernel: iscsi - sfnet:host10: Connect failed with CR - 113: no route to host

  Jul 24 16:24:27 dev3 kernel: iscsi - sfnet:host10: establish_session failed. Could not connect to the target

  Jul 24 16:24:27 dev3 kernel: iscsi - sfnet:host10: waiting 1 second before the next attempt to connect

  Jul 24 16:24:31 dev3 kernel: iscsi - sfnet:host10: Connect failed with CR - 113: no route to host

  Jul 24 16:24:31 dev3 kernel: iscsi - sfnet:host10: establish_session failed. Could not connect to the target

  Jul 24 16:24:31 dev3 kernel: iscsi - sfnet:host10: waiting 1 second before the next attempt to connect

  Jul 24 16:24:35 dev3 kernel: iscsi - sfnet:host10: Connect failed with CR - 113: no route to host

  Jul 24 16:24:35 dev3 kernel: iscsi - sfnet:host10: establish_session failed. Could not connect to the target

  Jul 24 16:24:35 dev3 kernel: iscsi - sfnet:host10: Session give up after 3 attempts

  
  

• Session connection problem target MD3000i

  I have a MD3000i connected to 2 iSCSI SW.

  When you add the connection at the Session of Targe, only one NET sub appears in the drop target portal.

  My IP is:

  10.23.250.1 and 10.23.250.2

  10.23.251.1 and 10.23.250.2

  BTW, it's in Windows 2 K 3 64-bit.

  Thank you!

  
  

• VMware vsphere essentials more and Dell MD3000i iSCSI - virtual disk not on preferred path

  Hello world

  I am trying to set up our new vmware vsphere essentials plus the facility. We have 2 x Dell R710 servers running vmware esx4 and have a md3000i SAN.

  Each server has a network cable to connect to a network SAN controller.

  vmserver1 a vmnic6 IP 192.168.130.110 the IP controller connection 0 192.168.130.101

  vmserver1 has IP 192.168.130.111 vmnic4 connection to controller 1 IP 192.168.130.102

  vmserver2 a vmnic 6 IP 192.168.131.110 the IP controller connection 0 192.168.131.101

  vmserver2 has IP 192.168.131.111 vmnic4 connection to controller 1 IP 192.168.131.102

  Whenever I start a virtual server it causes the dell md3000i start flashes orange, and management tool says disc not on favorite virtual path.

  After entering the tool configuration and affecting the path preferred, from the commencement to vmware, even with a single connected server it causes the error.

  I tried to configure vmware to use direct fixed and alternate paths.

  I did a quick search on Google and found these sites:

  http://www.delltechcenter.com/page/VMware ESX4.0andPowerVault MD3000i

  http://en.community.Dell.com/support-forums/storage/f/1216/t/19269507.aspx

  Strange configuration.

  Looks like you are using some cross cable?

  Each host must have 2 vSwitches, each with a port vmkernel on one of the two iSCSI network.

  Each host must reach all 4 of the MD3000i (test with the vmkping command) interface.

  See also:

  http://www.delltechcenter.com/page/VMware ESX4.0andPowerVault MD3000i

  André

• To access ESXi 4 Update 1 custom server from dell MD3000i iSCSI SAN

  Hello

  I'm brand new on VMware ESX/ESXi products and for the most part, no.  I configured several machines virtual with server 1 and 2.  I am trying to connect a virtual ESXi 4 server in a SAN and starts to become very confused about what I can or not do.  I hope that someone here can break it down for me because I couldn't find the answer to my specific questions.

  Here's how I'm Setup:

  I have a Dell PowerEdge R710 with ESXi 4 Update 1 'Custom Dell' (whatever that means) is installed.

  I have a Dell MD3000i SAN using iSCSI with a pre-configured dedicated virtual disk.

  I would like to create virtual machines on virtual disk said.

  I think that ESXi 4 is completely free.

  It seems that to manage the server, I need to use 1 of the 2 products.  The Vsphere client or web application of VMware Go.

  If I use Vsphere:

  I have the ability to add a type of storage through the user interface.

  I'm on a 60-day trial. I thought that it was free.

  If I configure my iSCSI via Vsphere and then the eval expires... what happens?  All jump on me and then I have to purchase a license to get it back?

  If I use VMware go:

  It seems I don't really have any options to do any kind of configuration iSCSI in VMware Go.  I do?

  I also have a XenServer that is configured in this way and it's all free. I wanted to try the bare metal of VMware solution, but now I wonder if I'll have to go back to Xen.

  Can someone please relieve me of my confusion until I have to pull the plug on this experience.  Maybe direct me to the proper documentation on how to configure what I need with what I have at the cost free-is possible.

  Thanks a lot for your comments and have a wonderful weekend!

  I'd go by QuickStart Webcast and Webcast ESXi Webstart to help get a better understanding.

  Here is a configuration to the MD3000i http://www.dell.com/downloads/global/solutions/esx_storage_deployment_guide_v1.pdf guide

• with vSphere and Dell MD3000i iSCSI design

  I installed a server ESX 4 (the first of three for this cluster), and a SAN Dell MD3000i iSCSI connected through two switches Dell PowerConnect 2816.

  Now I read the VMware 'iSCSI SAN configuration guide', and I wanted to just make sure I did the design correcly.

  I have connected a Teddy ESX (vmnic1) to one of the pSwitch and another (vmnic5) in the second. This pSwitch SAN iSCSI ports are connected, so that one of the switches carry the 10.10.10.x subnet and the other the 10.10.11.x (see IP plan below)

  The two natachasery have a vSwitch each (a do not share), a portgroup each and are configured on different subnets, IP (see attached screenshot)

  Plan of intellectual property:

  Port iSCSI-10 group (VMkernel): 10.10.10.1

  Port group iSCSI-11 (VMkernel): 10.10.11.1

  0-0 SAN controller: 10.10.10.10

  SAN 0-1 controller: 10.10.11.10

  Controller 1-0 San: 10.10.10.11

  SAN 1-1 controller: 10.10.11.11

  By using this configuration, I could see four different paths for each LUN. and I was able to make the ESX Server will switch to different switches/controllers as I unplug the vmnic1 network cables and vmnic5, one at a time.

  Then I found the section on 'esxcli' configuration guide and multipathing configuration, which I carried out in accordance with the instructions ("esxcli swiscsi nic add - n vmk0 d vmhba34" and "esxcli swiscsi nic add - n vmk1 vmhba34 d ')

  Now I have eight different paths for each logic unit number, three of whom are 'Active' and an 'active (i/o)' (see my screen attached the capture).

  So, my questions are:

  1. the eight paths to each LUN really normal in designs of iSCSI?

  2. is my vSwitch/Teddy/pSwitch correct design choices?

  Thanks in advance!

  / Anders

  @hennish,

  As long as your new design continues to meet your needs of failover and workload, your infrastructure design should be fine.

  But you might want to take a look at this design Dell. In particular, step 12 that configures multiple paths in round-robin policy using the VI GUI client, for

  Each LUN exposed to the ESX Server. This allows balancing on two

  Active paths to the LUN. After completing this step, you should see2 "IO Active" paths.

  Kind regards

  KongY@Dell Inc.

• Clean shutdown for EqualLogic PS6100 without stopping the host/iSCSI initiator

  In fact, I've known the procedure on how to stop the Equallogic PS storage. But I have a question as well as the procedure.

  Do you really need to stop the iSCSI initiator or the host connected to the storage before you shut down the storage controller?

  Because we move the Equallogic box on the rack on the other. I just want to stop the Equallogic without stopping the hosts.

  Hello

  The hosts are connected to some other storage that you want to keep as you move the table EQL?  If you stop the storage, it is similar to pulling on a hard drive in its operation.  Most of the time nothing bad will happen.  But all entries that did not allow the storage is lost.   For applications such as SQL or Exchange is not something you want.

  If you need to keep the server up, stop all applications accessing the volumes, then disconnect all EQL volumes first, and then stop the EQL table.  Will be served waiting for the written word.

  Kind regards

  Don

• Connection of the EQL team

  Hello

  Our systems have been designed and constructed by a dell partner, but I was unable to find articles online back up their design.

  6xR810 with 8 network ports

  2xPC6248 switches

  EQL PS6500X completely filled 8 ports connected network (4 active)

  R610 servers run 2012 R2 and have two teams configured integrated using making team with 4 NICs assigned to each team.

  -'1', that has all the virtual NIC connected and uses LACP to team.

  "iSCSI team" the independent switch value.

  When I look at the use of the adapter, it looks that only 1 of the 4 network cards takes virtually all traffic with the rest of the idle.

  I know that from 2012 team R2 is supported for iSCSI, but is this correct configuration in this case?

  Thank you

  Hello Bob,

  EQL does not pool.  Which is why you see only a single connection. You must configure MPIO with the iSCSI initiator.   You should have a connection on the EQLsupport.dell.com site.  You can download the HIT / ME software, v4.7.1.  This will include software to optimize the MPIO specifically with storage EQL.  iSCSI should be on its own IP subnet, so spend 2 x NICs for iSCSI and the other two for your normal aka traffic 'LAN '.

  Kind regards

• vCenter could not connect to the VSM Server

  I have SanHQ and HIT running well on vSphere 4.1. After upgrading vSphere 5.5 and HIT to 4 VSM, my new vCenter could not connect to the VSM server at all.

  1 VSM ip address must be configured on the management or iSCSI network?

  2. I have 2 vCenters to AC and DC, respectively. In this case, I have to install 2 VSM, each to each site? Note that although my VM networks on both sites and management are all connected via VPN, iSCSI networks are isolated.

  3. is it possible to deploy the VSM 3.5 and 4 so that the two vmware VI Client and Web Client have access to VSM features?

  VSM does not work with Linked vCenters mode so that a VSM would be able to access the two vCenters.

  You will need to deploy both VSMs.

  You cannot run two MSM 3.5.x and 4.0.x at the same time.

• Reattach the EqualLogic iSCSI for 2012 Windows volumes

  Hello

  We use EqualLogic, Windows 2008R2, HIT and initiator iSCSI access volumes. Now I'm re - install OS to Windows 2012. All materials, IP addresses, volumes, host name will be the same on the new operating system. BONES of some changes. Will it be the right way to remap the iSCSI volumes to the new operating system:

  1. on windows 2008 R2 take the volume offline in the disk management console.
  2. disconnect "Discovered targets" in the Windows iSCSI initiator.
  3 collect volumes offline in Manager Dell EqualLogic Group (to restore the connections).
  4. the new 2012 Windows Installer 4.5 HIT and set (is this version of the correct software for Windows 2012?)
  5 activate the volumes in the Dell EqualLogic Group Manager.
  6. Discovery target and connect to targets.
  7 collect volumes online in the OS disk management console.

  These steps are correct?
  Are they all necessary?
  Is a correct software 4.5 for windows 2012 HIT?

  Thank you

  Re: connections.  Are you referring to the iSCSI to table sessions?   If so, those are dynamic.  When you stop they will disappear.

  If everything is the same, so technically Yes.  Shutdown, you can reload and bring it to the top.