ESXi 5.1 Lab question (resolution/iSCSI discovery)

Similar Questions

• ESXi 6.0 U1 U2 upgrade, iSCSI questions

  Hello

  First post, so I'll try and summarize my thoughts and what I did with troubleshooting.  Please let me know if I left anything out or more information is required.

  I use the free ESXi 6.0 on a Board with a CPU Intel Xeon E3-1231v3 and 32 GB of DDR3 ECC UDIMM mATX to Supermicro X10SLL-F.  I use a 4G USB FlashDrive for start-up, 75 GB 2.5 "SATA to local storage (i.e. /scratch) and part of a 120 GB SSD for the cache of the host, as well as local storage.  The main data store for virtual machines are located on a target (current running FreeNAS 9.3.x). iSCSI  This Setup worked great since installing ESXi 6.0 (June 2015), then 6.0 U1 (September 2015) and I recently made the leap to 6.0 U2.  I thought everything should be business as usual for the upgrade...

  However, after upgrading to 6.0 U2 none of the iSCSI volumes are "seen" by ESXi- vmhba38:C0:T0 & vmhba38:C0:T1, although I can confirm that I can ping the iSCSI target and the NIC (vmnic1) vSwitch and VMware iSCSI Software adapter are loaded - I did not bring any changes to ESXi and iSCSI host before the upgrade to 6.0 U2.  It was all work beforehand.

  I went then to dig in the newspapers; VMkernel.log and vobd.log all report that there is not able to contact the storage through a network issue.  I also made a few standard network troubleshooting (see VMware KB 1008083); everything going on, with the exception of jumbo frame test.

  [root@vmware6:~] tail - f /var/log/vmkernel.log | grep iscsi

  [ ... ]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:41620 r L: 0: 10.xxx.yyy.109:3260]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T:1 CN:0: connection iSCSI is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:32715 r L: 0: 10.xxx.yyy.109:3260]

  [root@vmware6:~] tail - f /var/log/vobd.log

  [ ... ]

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023006us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T0

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023183us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to iqn.2005 - 10.org.freenas.ctl:vmware - iscsi because of a network connection failure.

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622002451us: [esx.problem.storage.iscsi.target.connect.error] connection iSCSI target iqn.2005 - 10.org.freenas.ctl:vmware - iscsi on vmhba38 @ vmk1 failed. The iSCSI Initiator failed to establish a network connection to the target.

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023640us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T1

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023703us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to

  [root@vmware6:~] ping 10.xxx.yyy.109

  PING 10.xxx.yyy.109 (10.xxx.yyy.109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,174 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,238 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0,309 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.174/0.240/0.309 ms

  vmkping [root@vmware6:~] 10. xxx.yyy.109

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,179 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,337 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0.382 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.179/0.299/0.382 ms

  [root@vmware6:~] NF - z 10. xxx.yyy3260.109

  Connection to 10. xxx.yyy3260.109 port [tcp / *] succeeded!

  [root@vmware6:~] vmkping 8972 10 s. xxx.yyy.109 - d

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 8972 data bytes

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 0 packets received, 100% packet loss

  I began to watch the drivers NIC thinking maybe something got screwed up during the upgrade; not the first time I saw problems with the out-of-box drivers supplied by VMware.  I checked VMware HCL for IO devices; the physical NIC used on that host are Intel I217-LM (nic e1000e), Intel I210 (nic - igb) and Intel® 82574 L (nic-e1000e).  Lists HCL from VMware that the driver for the I217-LM & 82574L should be version 2.5.4 - I210 and 6vmw should be 5.0.5.1.1 - 5vmw.  When I went to check, I noticed that he was using a different version of the e1000e driver (I210 driver version was correct).

  [root@vmware6:~] esxcli list vib software | e1000e grep

  Name Version Date seller installation acceptance level

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

  NET-e1000e 3.2.2.1 - 1vmw.600.1.26.3380124 VMware VMwareCertified 2016-03-31

  esxupgrade.log seems to indicate that e1000e 2.5.4 - VMware 6vmw should have been loaded...

  [root@esxi6-lab: ~] grep e1000e /var/log/esxupdate.log

  [ ... ]

  # ESXi 6.0 U1 upgrade

  2015-09 - 29 T 22: 20:29Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to "/ tmp/stagebootbank".

  [ … ]

  # ESXi 6.0 U2 upgrade

  2016-03 - 31 T 03: 47:24Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write to payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to ' / tmp/stagebootbank '

  3.2.2.1 - 1vmw e1000e is recommended for 5.5 U3 and not 6.0 U2 ESXi ESXi driver!  As these drivers are listed as "Inbox", I don't know if there is an easy way to download the drivers supplied by seller (vib) for him, or even if they exist.  I found an article online to manually update drivers on an ESXi host using esxcli; I tried check and install the new e1000e drivers.

  [root@vmware6:~] esxcli software update net-e1000e-n-d vib https://hostupdate.VMware.com/software/VUM/production/main/VMW-Depot-index.XML

  Result of the installation

  Message: The update completed successfully, but the system must be restarted for the changes to be effective.

  Restart required: true

  VIBs installed: VMware_bootbank_net - e1000e_3.2.2.1 - 2vmw.550.3.78.3248547

  VIBs removed: VMware_bootbank_net - e1000e_3.2.2.1 - 1vmw.600.1.26.3380124

  VIBs ignored:

  As you can see there is a newer version and installed it.  However after restarting it still did not fix the issue.  I even went so far as to force the CHAP password used to authenticate to reset and update on both sides (iSCSI initiator and target).  At this point, I wonder if I should somehow downgrade and use the driver of 2.5.4 - 6vmw (how?) or if there is another issue at play here.  I'm going down a rabbit hole with my idea that it is a NETWORK card driver problem?

  Thanks in advance.

  --G

  

  I found [a | the?] solution: downgrade for 2.5.4 drivers - Intel e1000e 6.0 U1 6vmw.  For the file name, see VMware KB 2124715 .

  Steps to follow:

  1. Sign in to https://my.vmware.com/group/vmware/patch#search
  2. Select ' ESXi (Embedded and Installable) ' and '6.0.0 '.  Click on the Search button.
  3. Look for the update of the release name - of - esxi6.0 - 6.0_update01 (released 10/09/2015). Place a check next to it and then download the button to the right.
     
  4. Save the file somewhere locally. Open archive ZIP once downloaded.
  5. Navigate to the directory "vib20". Extract from the record of the net-e1000e.  In East drivers Intel e1000e ESXi 6.0 U1: VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585.vib
     
  6. This transfer to your ESXi Server (be it via SCP or even the file within the vSphere Client browser). Save it somewhere you will remember (c.-a-d./tmp).
  7. Connect via SSH on the ESXi 6.0 host.
  8. Issue the command to install it: software esxcli vib install v - /tmp/VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585.vib
     
  9. Restart the ESXi host.  Once it comes back online your datastore (s) iSCSI / volumes should return.  You can check by issuing h df or the list of devices storage core esxcli at the CLI prompt.  vSphere Client also works
  
  

  It took some time to find the correct file (s), the steps and commands to use.  I hope someone else can benefit from this.  I love that VMware can provide for virtualization, but lately, it seems that their QA department was out to lunch.

  Do not always have a definitive explanation as to why Intel e1000e ESXi 5.5 U3 drivers were used when ESXi 6.0 U1 U2.  Maybe someone with more insight or VMware Support person can.

  & out

  --G

• Nested ESXi 5.5 lab for the SRM demo with iSCSI

  Hi all

  I was wondering if it is possible to install ESXi in ESXi 5.5 5.5 make recovery of the Server Tier - 1 Microsoft with Site Recovery manager?

  So level 1 server applications are: Exchange Server, SQL Server, SharePoint Server and AD DC servers with 5 x test Win 7 desktop.

  The external data store to the VMFS will take place by iSCSI NAS connected to the physical server.

  Any suggestion and input would be greatly appreciated.

  Thank you

  One thing you'll want to do is to make sure that use you VSphere switches distributed on your cluster nested to ESXi hosts so that you can use the network i/o control (NIOC). For me, I put iSCSI to high priority traffic and everything to normal priority.

  With the help of the NIOC will allow your cluster nested in order to operate more fluidly than without it.

  My SRM 5.x laboratory is fully nested - probably not supported in a production environment where supported VMware should however.

  Here's a blog post of Ather Beg on its results by using the nested NIOC and ESXi hosts - it is the reduction of the spikes that Ather blog article shows that made work nested ESXi hosts networks so much better:

  http://atherbeg.com/2014/02/04/why-enabling-NIOC-network-IO-control-in-a-home-lab-is-a-good-idea/

  Datto

• question of iSCSI with D-Link DSN-2100-10

  Server: HP DL380 G7 equipped of 4 ports (BCM5709) Broadcom adapter

  SAN: D-Link DSN-2100-10 (the latest firmware upgrade)

  Hypervisor: ESXi 5.0 U1 (build 623860)

  I have a few problems with access to the San, just using one of the four adapters to Broadcom iSCSI detected by ESXi, after implementation of the VMkernel port binding, I have run the dynamic discovery and after waiting for 10 minutes, the target is detected but is not accessible by train. At this point, the host became unstable do not allow me to access, ping to the host is expired. After a few minutes, the host is still once I could only have access via SSH and not through vSphere and after restarting the server via SSH, the host is accessed again by vSphere but the target iSCSI not still not accessible, and if I try to make simple as rescanning for HBA operations or remove the target dynamic discovery or static tab the to host crashes again with the same strange behavior.

  If I install and configure VMware iSCSI Software adapter, the target is almost instantly and without performance problem. I also configured 2 Ports of iSCSI binded to 2 network cards on a single vSwitch for multichannel goal and it's working like a charm, but I suppose for the moment that I can't benefit from the unloading feature of my NIC iSCSI. The only problem with this configuration is a few warnings San logs on which I look at (invalid field in the message of the CBD when I perform an action on the data store)

  Any suggestions?

  In my view, the storage is not supported by the VMware HCL, is it not?

  Sorry for my response, but it is a problem that I have in fact! Storage is supported up to ESXi 4.1U2, but I want to upgrade to ESXI 5 hypersivor...

  Maybe you have any other suggestions or solutions, to help me solve the problem? I will ask support from DLink and VMware for a solution too.

• ESXi 4.0 / 4.1 Broadcom iSCSI installation program / Support with unloading iSCSI

  Hello.

  I am new to the use of iSCSI on ESXi so I may have a few questions already answered. Sorry for that.

  Is it true that ESXi 4.1 supports iSCSI unloading, while ESXi 4.0 does not work?

  How to set up properly? I have a Dell R510 with an Quadport Broadcom NetXtreme II 5709.

  I like to use two network of 5709 with links LACP ports to connect to my iSCSI target (QNAP).

  I found a few messages about creating two vSwitches which each card of a network and mapping the vSwitch (vmkx) to the vmhbaXX (esxcli swiscsi nic add - n vmk1 vmhba35 - d).

  What is the right way? How to set up link aggregation then?

  This is what it looks like:

  

  

  Thank you

  Michael

  Hello

  you look here: http://blog.open-e.com/bonding-versus-mpio-explained/

• iSCSI - discovery dynamic vs. static?

  When you use iSCSI, there's an advantage to the use of static discovery from the dynamics for this?

  I understand when you use dynamic you point to one IP address and the TCP port and the initator iSCSI will communicate with the target and ask Lun, which will then be accessible. When you use static this information must be manually specified. Is that correct, and is there a reason to use static?

  You're right, dynamic discovery with initiator "SendTargets" send to a single IP address and port and if the target is listening on several names and addresses, all of them are sent to a form of TargetName and TargetAddress (incase #). I think that determine what are behind the target LUN is not part of dynamic discovery

  As for your second question, hardware server is probably more flexible in terms of network adapters that can be used, so software ISCSI is more flexible, allowing to configure several IP addresses.  Many have IP/port combinations the target gives many more options: one being the ability to connect to the storage of different networks (but which can also be performed on routed networks), the second being more paths in paths multiple configuration when same LUNS accessed using two different IP addresses. And finally, if this hash IP policy could be used for a better distribution of load between natachasery in NIC teaming configuration on the ESX host.

• VMware ESXi embedded test lab architecture and design?

  Hi people,

  Someone here built your DCA VCAP test lab using the nested ESXi approach?

  I want to build one but don't know where to start. Any kind of suggestion and comments would be greatly appreciated.

  Thank you

  Have a look here: http://sostechblog.com/2014/01/14/building-a-vcap-live-exam-test-environment/

• VMAP eliminates ESXi and VCenter Lab installs, thanks to greedy Pirates.

  I run a class of Virtualization Technologies. My college has acquired a subscription of VMAP mainly to use to set up our training lab.

  We run 18 servers Dell T110 with 16 GB of memory.

  We also run 18 desktops Dell with 8 GB of memory.

  Here's how I run the class of 16 weeks (used to):

  Each student would be:

  1. Install a version of eval of 180 days of Windows 2008 R2 on a bare desktop.
  2. Install Workstation 8 on the desktop. Introduce students to the concepts of virtual machines. Workstation is ideal for this.
  3. Bring their own USB 16 GB class and install ESXi 5.0 on it running on the server.
  4. Install the VCenter Server (and client) directly on the desktop.
  5. Create a VM virtual host two additional ESXi
  6. Create an another VM of the VCenter Server virtual appliance.
  7. Start creating virtual machines, Clusters, ect.

  The point is, each student will learn a wide range of features in VSphere. Each student has at least THREE ESXi licenses and need TWO licenses of VCenter Server.

  At the end of the class, the laboratory is demolished (uninstalled all the software).

  The VMAP subscription that my college bought recently announced that Install lab licenses are more offered for VCenter or ESXi products.

  Now, I only use the version of 60 days?

  Is there any way around this?

  I could create 50 or so "student users" and get the individual keys for each. I would then have to use each key individually on all hosts in the laboratory.

  Students enrolled in this class were very happy to try the VSphere environment, something they could not do at home.

  Why not just offer the installation lab keys that have a duration of 1 year. This woul be more long enough for any semester length class.

  Or VMware wants to only close the non academic 'partner' classes offered. The "certified" classes use the same account VMAP of Kivuto however. How do they make their laboratories?

  Other classes in this direction have found that the best way to run the class is to one) ask students to work in pairs or larger teams, so that they can share their licenses; and (b) have them download license keys themselves, as you suggest. They don't necessarily three license keys for ESXi each however, given that each license key has an associated CPU count (2 or 4, depending on the product) which can be used to activate the host several processors. Note that we recently made vCloud Suite available to students in addition to vSphere, which in the past was only available for teachers and staff, so there are various options for which products the students use in class.

  Happy to discuss this further with you help succeed your class.

  Steve Muir

  --

  Director of the academic program of VMware (VMAP)
  http://labs.VMware.com/academic
  VMware technical Journal Vol 1, no. 2, now- http://VMware.com/go/vmtj

• ESXi 4.1 for ESXi 5.1 vMotion Question

  I have a customer who has two servers esx esx 4.0 is and the other is 4.1. Esx 4.0 is an IBM System x 3650 m2 with an Intel Xeon E5530. Esxi 4.1 is a HP Proliant DL360 G6 with an Intel Xeon E5506.

  My question is esxi 5.1 does support vmotion and if yes - that will work with these processors being different?

  Please let me know if you need additional information.

  Thank you

  Ryan

  I would like to add that you can certainly configure vMotion between these 2 servers (license to of course), but you may need to activate CVS while they are a bit different revisions.

  EVC is configured in the properties of the cluster. You'll want to take the most compatible version on both hosts. To enable it, you may need to turn off some guests on the most recent processor box.

  JES

• ESXi 5 Networking newbie question

  Hi all,

  I'm new to ESXi and I need some advice from experts on the network on the ESXi 5 host configuration.

  The installation program looks like this.

  A HP DL380 G7 server running 3 Server ESXi 5 company 2K8R2 VM, 4 LAN ports on the server, one dedicated to the management network.

  I want to set up the connection in the following way:

  Each VM should have access to the physical network, but I also want that all three VM will not communicate via physical network interfaces but by intra-Server network basically do not touch physical network for VM VM networks.

  If I understand correctly, networking in ESXi if I attribute same vSwitch to all virtual machines they will speak between them via intra network server, but then I'll be able to only affect that one LAN card physical to the vSwitch if my physical switch does not support teaming them and in this case I'm stuck at 1000 Mbit/s for a total throughput of all three VM?

  Then I thought to create three vSwitches, assign a physical LAN card to each vSwitch and each VM to his own vSwitch, but in this case each VM will communicate with each other through physical network right?

  Next idea was to do it the same way as previously mentioned, but also to create a vSwitch more without a physical NETWORK card assigned to it, connect all three of the computer as a virtual card on VM virtual LAN and have a different for this second network subnet and set up all services on all VM to communicate with each other through this (other) network. Then I would have a few problems with the resolution of name between VM if I reference VM by IP? Or maybe not because they are all in the same field of broadcast just to put another network adapter intra-host higher on the priority list in VM network settings physically map network related?

  Thanks for help.

  Tim wrote:

  If you had 1 vSwitch with 2 exchanges, that traffic would be let through the network adapter.

  That's right if you have different VLANS on trade, but if they are the same then the traffic will also remain in the vSwitch.

  oryxcomp wrote:

  If I understand correctly, networking in ESXi if I attribute same vSwitch to all virtual machines they will speak between them via intra network server, but then I'll be able to only affect that one LAN card physical to the vSwitch if my physical switch does not support teaming them and in this case I'm stuck at 1000 Mbit/s for a total throughput of all three VM?

  You can have several VMNIC (physical ports on the physical network card) connected to the same vSwitch without problems, even if your physical switch does not support grouping. Just leave politics to the default id 'port' of load balancing.

  So create a vSwitch, add vmnic as much as you like, and then connect your virtual machines to the vSwitch. Note that a single virtual machine will not be able to get more than 1 Gbps in flow, but the different virtual machines will span outgoing ports.

• Questions about iSCSI and subnets

  IM planning on a deployment of 8 ESX servers connected to an array of iSCSI on double dedicated switches.

  1. 2 cards on each ESX host network is dedicated to iSCSI and VMware dependent ontraffic.
  2. SAN iSCSI target consists of two controllers with 2 uplinks of iscsi on each controller (4 total)
  3. The manufacturer of SAN is suggesting setting up of their SAN ports in separate subnets for higher throughput
  • For the sake of simplicity lets say assign 10.10.100.1 24 ports SAN 1 & 3 and 10.10.200.1 24-port SAN 2 & 4
  • On the side of ESX, a single iSCSI VMKernel address will be 10.10.100.2 and the other will be 10.10.200.2.

  My questions:

  1. do I have to enable trunking VLAN on the side of the switch so that the initiator 10.10.100.2 ESX failover to the port of SAN 10.10.200.1 and vice versa, because they are not in the same subnet and therefore not in the same VLAN?
  2. If this is the case, will trunking VLAN also solve the problem if we were to buy an identical iSCSI SAN on the road and 2 subnets more setup for controllers, but still only have two cards on the ESX Server.
  3. I would assign the 2nd ESX Server in this config with the same IP addresses as the first, or I re them with differnet IPs (but obviously still in the same subnet as the storage arrays), for example ESX 1 is 10.10.100.2 and ESX 2 would be 10.10.100.3

  Any other associated iSCSI I get with VMware, simply not able to think through this particular obsticle and I don't have the equipment to test it yet. Doesn't help that it's late in my part of the world and my brain power is depleting fast!

  Thank you!

  I mean really isolated network. No routing between them.

  Is the software of multiple paths that can pass a path to another, and if you need one network to another.

  Note that the PowerVault will have an interface of a mosquito net and to one another for each processor.

  André

• question of iSCSI san

  Hello everyone,

  I just created my first with software e open iscsi san solution.

  My situation: on the local disk, I put my VM

  I created 4 iscsi data warehouses

  1 will be used to back up my VM and can be reached for Vsphere

  The other 3 serve as a backup for my 3 VMS solution. I am connected to them through the Iscsi initiator in the virtual machine, format them, and now they appear as an additional drive in the virtual machine. I can see them in Vsphere but is no longer in data warehouses, but in devices (because they are formatted as NTFS)

  Now the question:

  Is it possible to see what data is on data warehouses that are formatted to ntfs When you are not connected to the virtual computer?

  When a virtual machine should crash, backupped data should always be saved to disk iscsi, but where can I get it?

  Thanks in advance, onkt

  NTFS is only accessible via windows server only. You can mount the iSCSI drive backup on another virtual computer.

• ESXi NIC Teaming - switch Question

  Got my first server ESXi upward and running last week.  This is my first production ESXi server.  The hardware itself has dual NIC from what I can tell, ESXi 4.1, if you put the NETWORK interface card in 'team' (I don't think that's the term they call it) ESXi will do a bit of himself load balancing, but also be able to use only one or the other in case of failure in the course.  So, my question is this, if I have 2 NIC on my server set in 'team', that I need to adjust the 2 ports on the switch to shared resources, as I do for any other server?  Or ESXi he manages in a way that I wouldn't need to put in place the trunking of the switch ports?

  That's right – from san traffice some through any port with all the load balancing methods you'll need to configure the same trunk ports

• Problem with ESXi 3.5 host or our iSCSI SAN

  Hello

  Last week, twice we came into work and notice that some virtual machines on a host somehow the bomb and break the connection or work habit and are turned off.  It happens with mutiple errors, but we are not sure if it's the host itself or iSCSI SAN is too connected a NETgear ReadyNAS.  All the vmdk and vmx VM files are on the SAN storage are loacted here for targets.  Your opinion on this if someone could help determine what may be the question, please, thank you?

  Welcome to the forums

  I edit your images and delete the business credentials. There is a security risk that you should not expose.

  Take a look at the following.

  http://communities.VMware.com/message/1333118#1333118

• Question of ISCSI port

  Hello

  If a dell MD3000i to a switch conneccted second ISCSI port and IP address in the same reng-IP (10.0.10.0) of other servers that are connected to the same switch, drives in the device would be available (via ISCSI inititor) to one of the servers that are connected to this switch? is that correct? now becuse one of the ports of ISCSI SAN is connected directly to the NETWORK card of one of the servers and the ISCSI port and the server NETWORK card is configured with the ip address of 192.168.8.0 but the rest of the servers in the domain is configured with IP reng 10.0.10.0, so all the other server has direct access to the San.

  Also how can we change the IP address of the second ISCSI port

  Thank you

  Servers should not communicate on the LAN with the SAN. The SAN must be on its own dedicated (and isolated) switch or VLAN. Each server then uses at least 1 NETWORK card in the switch or VLAN and it is assigned an IP address of the iSCSI subnet. For redundant configurations, you will use 2 switches or 2 VLANS on 2 switches (of the sort that if 1 switch goes down, iSCSI traffic continues with the other switches).

  When you use just 1 switch or VLAN, use only the 0 of each controller port (port 0 between 2 controllers will share the same subnet (but obviously have a different IP address).)