ISCSI configuration

Similar Questions

• ESX iSCSI Configuration recommendation

  Hello

  I wonder what is the best configuration of the storage card in the following scenario to provide a NIC host and SAN controller redundancy. The SAN must be directly connected to each host that I don't have one at the moment gigabit switch, which means each link point to point in its own subnet as below.

  Host 1:

  iSCSI_A1: 192.168.1.2/30

  iSCSI_B1: 192.168.1.5/30

  Host 2:

  iSCSI_A2: 192.168.1.9/30

  iSCSI_B2: 192.168.1.13/30

  ISCSI SAN:

  A1 of the host: 192.168.1.3/30

  B1 the host: 192.168.1.6/30

  A2 of the host: 192.168.1.10/30

  Host B2: 192.168.1.14/30

  According to the article, VMware KB: considerations for use port binding software iSCSI in ESX/ESXi, I should not use links in Port because each link is in a separate broadcast domain. Does this mean that I have to put up 2 iSCSI adapters on each ESX host software and just use the dynamic discovery?

  Thanks for any help.

  Of course, no problem. Make sure you see both paths, under Configuration-> storage adapter-> select your iSCSI adapter. Example like this. In this case, I have 12 aircraft 24 channels, so 2 paths to each device (LUN).

  

  You can also mark the answers as useful or appropriate if you wish.

• Need suggestion for storage on the server ESXi5 iSCSI configuration

  Hi friends,

  I am new to vmware & I want t know if I have physical iSCSI card installed in my ESXi 5 & it connect directly to the server and then again I want to configure virtual SCSI for connection to the VM card? If so, why?

  Thank you and best regards,

  Pradip

  See page 63 of the http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-storage-guide.pdf link

• Software iSCSI configuration

  Where we get number IQN that we need to manually enter static configuration of the software iSCSI discovery.

  It depends - some have the ability to not be discovered. Give it a try, in case of doubt. If this does not work, then you will need access to the management interface or know someone who can.

• Newbie on iSCSI Configuration questions

  Hello everyone

  I'm new to VMware. I have two questions

  (a) once I have add an address IP of SendTargets discovery, how can I update it? for example, if a new target is visible via the IP discovery after that it has already been added in VMware and I want it to appear.

  (b) is there a provision the disconnection of one specifying IQN (San identifier)? I went though VSphere Documentation and I couldn't find anything.

  (c) VSphere he iSNS support such as Linux (iscsiadm)?

  Thank you

  Welcome to the Forums-

  (a) you will need to go to the section of the configuration of the ESX host storage card in the client vSphere select initator iSCSI, then click Rescan - this cause a target command send sending sllowing to the discovery of new targets

  (b) No, there isn't a way to disconnect from a specific IQN I know

  (c) to the vSphere, I think not vSphere supports iSNS.

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• How data travels in the iSCSI Configuration

  

  Hello

  I'm a little confused about how DATA moves through an environment of VI3.5 using iSCSI SAN.

  Before, I am attaching a schema, so everyone will be on the same page.

  It is a scenario with two servers ESX (ESX1 and ESX2), a physical server (Server1) and 4 Virtual Machines. (VM1 ~ 4)

  vmnic0 is for traffic Service console and the virtual machine.

  vmnic1 is for vmotion, but on the same subnet that are Virtual Machines.

  vmnic2 and 3 are for iSCSI and Service console for iscsi on a different subnet and different switch.

  The example is for the understanding of the performance and the communication network and not for security reasons.

  I know that when you want to use VMotion and HA, you need to use Shared Storage (IE iSCSI SAN) and your virtual machines are stored on the SAN.

  Here are my questions:

  1 - is this correct design?

  2-if I want to copy a VM1 VM2 to file, how data moves? (knowing that both are stored on the same SAN and they are both on the same ESX Server)

  3-if I want to copy a file from VM1 to VM3, how data moves? (Knowing that both are stored on the same SAN but they are on different ESX servers)

  4-if I want to copy a file to the server Server1 to VM1, how data moves?

  5 - If you do a VMotion VM1 from ESX1 ESX 2, how data travel? (I know for VMotion the contents of the RAM to the virtual computer will be copied to the second serve of ESX) This will affect the performance of the local network?

  6. What do you recommend to monitor traffic on vmnic?

  Please include the question number in your response.

  Thank you

  1 - is this correct design?

  OK for iSCSI.

  But you do not HA hat on the breakdown of the network cable or the NETWORK card (for the first 2 vswitches).

  It is good to have iSCSI separated by VM and VMotion, but usual for each vSwitch to give at least 2 cards of uplink.

  You can for example put VMotion and VM on vswitch, using 2 NICs and affecting a NIC preferred for the virtual machine and a preferred (different) for VMotion NETWORK card.

  2-if I want to copy a VM1 VM2 to file, how data moves? (knowing that both are stored on the same SAN and they are both on the same ESX Server)

  VM1 and VM2 could talk via the network of the VM.

  So VM1 get data from the vmknic2/3 (if is not in the cache of the comments), copy to network (vmknic0), VM and then store the data (and goes to vmknic2/3)

  3-if I want to copy a file from VM1 to VM3, how data moves? (Knowing that both are stored on the same SAN but they are on different ESX servers)

  Same as before, using 2 ESXs

  4-if I want to copy a file to the server Server1 to VM1, how data moves?

  vmknic0, then vmknic2/3

  5 - If you do a VMotion VM1 from ESX1 ESX 2, how data travel? (I know for VMotion the contents of the RAM to the virtual computer will be copied to the second serve of ESX) This will affect the performance of the local network?

  vmknic1

  6. What do you recommend to monitor traffic on vmnic?

  You can use the tab Performance on ESX.

  André

• switch-v iSCSI configuration

  I just got some iSCSI storage and try to add this to my vmware servers. The service console for my vmware server is on the subnet 192.168.2.x. I plan to use a separate subnet for iSCSI 192.168.3.x.  I don't want the iSCSI traffic on the same network as the rest of my servers.

  I've isolated 8 ports on my switch for use with iSCSI.

  The problem I have is that when I add a vmkernel interface to my v-switches, he wants to be on the same switch-v as my service console, but I want to use separate physical connections to the switch for 2 subnets. If someone else has had this problem and how did you get around it.

  Also be aware if you use ESX and the iSCSI initiator of software you will need to place a service on 192.168.3.x network console because for the software iSCSI initiator to work the vmkernel and service console need to communicate to it - also don't forget to open port 3260 in the service console firewall

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• SC40220 - iscsi - 2 * FD - unable to discover through the 2nd IP Portal

  Hello

  Trying to get multipath and switch fabric resilience working with installation of FD double on the SC4020. MSDS are ISCSI1 and ISCSI2.

  Addresses IP SAN

  10.154.167.205/24 address IP ISCSI1

  Controller X p1 10.154.167.201/24

  Controller Y p1 10.154.167.203/24

  10.154.168.206/24 address IP ISCSI2

  Controller X p2 10.154.168.202/24

  Controller Y p2 10.154.168.204/24

  As you can see, I have 2 SDS stretching across SAN controllers, IE 1 in ISCSI1 port & port 2 in ISCSI2 on both controllers. The reasoning behind this is that I should be able to maintain the multi-channel operation even if I lose a set on the SC4020 controller.

  Every FD and associated controller ports has been addresses above, every FD has its own 24 and VLAN own. All the switchports are in access mode on a pile of EX4550 of Juniper in the appropriate VLAN and run frames.

  On the side of linux client (oracle 7 UL - 3.8.13 - 35.3.1.el7uek.x86_64) we have two interfaces, hl4 and p3p2 which are also processed in the correct subnets, hl4 is 10.154.167.51/24 and p3p2 is 10.154.168.151/24

  The client can ping the IP addresses of the two ports members successfully as well as ip address of FD when restricted to the interface of good source.

  for example, of hl4 for ISCSI1

  root@PD-TK-DB01 ~ # ping - I hl4 - c1 10.154.167.201
  PING 10.154.167.201 (10.154.167.201) of 10.154.167.51 hl4: 56 (84) bytes of data.
  64 bytes from 10.154.167.201: icmp_seq = 1 ttl = 64 time = 0.063 ms

  -10.154.167.201 - ping statistics
  1 packets transmitted, received 1, 0% packet loss, time 0ms s
  RTT min/avg/max/leg = 0.063/0.063/0.063/0.000 ms
  root@PD-TK-DB01 ~ # ping - I hl4 - c1 10.154.167.203
  PING 10.154.167.203 (10.154.167.203) of 10.154.167.51 hl4: 56 (84) bytes of data.
  64 bytes from 10.154.167.203: icmp_seq = 1 ttl = 64 time = 0,067 ms

  -10.154.167.203 - ping statistics
  1 packets transmitted, received 1, 0% packet loss, time 0ms s
  RTT min/avg/max/leg = 0.067/0.067/0.067/0.000 ms
  root@PD-TK-DB01 ~ # ping - I hl4 - c1 10.154.167.205
  PING 10.154.167.205 (10.154.167.205) of 10.154.167.51 hl4: 56 (84) bytes of data.
  64 bytes from 10.154.167.205: icmp_seq = 1 ttl = 64 time = 0.125 ms

  -10.154.167.205 - ping statistics
  1 packets transmitted, received 1, 0% packet loss, time 0ms s
  RTT min/avg/max/leg = 0.125/0.125/0.125/0.000 ms
  root@PD-TK-DB01 ~ #.

  Ditto for p3p2 for ISCSI2

  root@PD-TK-DB01 ~ # ping - I p3p2-c1 10.154.168.202
  PING 10.154.168.202 (10.154.168.202) of 10.154.168.151 p3p2: 56 (84) bytes of d ata.
  64 bytes from 10.154.168.202: icmp_seq = 1 ttl = 64 time = 0,123 ms

  -10.154.168.202 - ping statistics
  1 packets transmitted, received 1, 0% packet loss, time 0ms s
  RTT min/avg/max/leg = 0.123/0.123/0.123/0.000 ms
  root@PD-TK-DB01 ~ # ping - I p3p2-c1 10.154.168.204
  PING 10.154.168.204 (10.154.168.204) of 10.154.168.151 p3p2: 56 (84) bytes of d ata.
  64 bytes from 10.154.168.204: icmp_seq = 1 ttl = 64 time = 0,113 ms

  -10.154.168.204 - ping statistics
  1 packets transmitted, received 1, 0% packet loss, time 0ms s
  RTT min/avg/max/leg = 0.113/0.113/0.113/0.000 ms
  root@PD-TK-DB01 ~ # ping - I p3p2-c1 10.154.168.206
  PING 10.154.168.206 (10.154.168.206) of 10.154.168.151 p3p2: 56 (84) bytes of d ata.
  64 bytes from 10.154.168.206: icmp_seq = 1 ttl = 64 time = 0.116 ms

  -10.154.168.206 - ping statistics
  1 packets transmitted, received 1, 0% packet loss, time 0ms s
  RTT min/avg/max/leg = 0.116/0.116/0.116/0.000 ms
  root@PD-TK-DB01 ~ #.

  If the basic network connectivity is fine.

  iSCSI configured on the client as follows:

  iface m iscsiadm - I ISCSI1 o new
  iface m iscsiadm - I ISCSI2 o new
  iface m iscsiadm-ISCSI1 o Update - n iface.net_ifacename - v hl4
  iface m iscsiadm-ISCSI2 o Update - n iface.net_ifacename - v p2p3

  If you are still with me now, the problem is the following. Anything done to the targets of ISCSI1 is very well. Discovery works as expected.

  root@PD-TK-DB01 ~ # iscsiadm-m - t st Pei 10.154.167.205 discovery - I ISCSI1
  10.154.167.205:3260, 0 iqn.2002 - 03.com.compellent:5000d31000ac201c
  10.154.167.205:3260, 0 iqn.2002 - 03.com.compellent:5000d31000ac201d
  10.154.167.205:3260, 0 iqn.2002 - 03.com.compellent:5000d31000ac201e
  10.154.167.205:3260, 0 iqn.2002 - 03.com.compellent:5000d31000ac201f
  root@PD-TK-DB01 ~ #.

  but not for ISCSI2

  root@PD-TK-DB01 ~ # iscsiadm-m - t st Pei 10.154.168.206 discovery - I ISCSI2
  iscsiadm: no portals found

  Don't forget I can ping 10.154.168.206, * I can even telnet to it on 3260 to prove connectivity TCP is good, but it won't allow me to see anything through it.

  When I added the definition to the server on the San and attempt to add the two HBAs that corresponding to the hl4/ISCSI1 appears as with the correct initiator; but with 4 virtual controller ports, 2 per controller port in ICSI1 physics. What worries me, I expect only 1 per physical port as each customer HBA can see only two physical ports altogether.

  I can add an HBA corresponding to p3p2, but it just never came up.

  We are not permissioned for compellent yet portal if can't whitepapers or baselines that can exist in there, but surely what we are trying is a fairly basic facility and we shouldn't have trouble with it.

  Out of curiosity - is the operating system on the server object set multipath in SC interface? I don't see any errors in your basic configuration, so I wonder if its something simple/specific to the supreme court as mapping

• ISCSI in VMware guest - slow speed

  SAN is a PS4100 with dedicated switches.

  In VMware, I have a Setup vSwitch according to EQ DELL Documentation. The VMKernal properties are:

  • VLAN ID = None (0)
  • vMotion = unchecked
  • Fault tolerance = unchecked Logging
  • Management traffic = unchecked
  • iSCSI Port Binding = Enabled
  • MTU = 9000

  NIC Teaming settings tab:

  • Load balancing = unchecked
  • Failover detection network = unchecked
  • Notify the switches = unchecked
  • Failback = check = No
  • Failover = checked to Override switch control failover

  One in which adapter is set to Active the other place in is not used. This command is enabled for the second VMKernal iSCSI connection.

  The DELL MPIO extension has been added to the VMware host and the connection is configured to use DELL_PSP_EQL_ROUTED for the managed to the ISCSI target paths.

  Managed paths show also active / active status.

  Flow tests with a physical server through a single initiator iSCSI LUNs dedicated show speeds completely saturate the link with 99 MB/s of throughput. All I can manage to inside the guest OS of Server 2012 with NIC vmxnet3, who is also on the SAN is around 30 MB throughput.

  Drops of speed even more during transfer of a network SAN Fibre Channel AX150 hosted VMware guest OS, with an Intel Pro 1000 MT network card, on the one hand of SAN PS4100, it falls to 13 MB/s.

  What I missed, and where should I look to make changes?

  What I should look to increase flow?

  Hello

  There's not much info here to go. I would like to start by making sure that the server is configured by Dell best practices doc.

  en.Community.Dell.com/.../20434601.aspx

  VMware iSCSI configuration will not affect the speed of connection iSCSI comments.   Ideally, comments iSCSI traffic should have its own NIC, separated from the ESXi NIC use because it is the iSCSI traffic.

  Make sure that the VMware tools is installed as well.  Who will ensure that the network driver is optimized.  Run the current version of ESXi is too important.  There was a few KBs on performance with the VMXNET3 adapter problems.   Sometimes change to the E1000 might better work.

• the UCS blade iscsi initialization cannot install windows server

  Hi all

  I have a problem when I try to install windows server 2008 in the storage of nexenta using iSCSI via ucs b-series, but his works well when I install ESXi 5.5. I can't find disk under windows server installation, and I see all the LUNS in ESXi what im create before nexenta storage and work when I install it.

  This vnic iSCSI Configuration:
  ----------------------------
  vnic_id: 13
  LINK_STATE: to the top

  Initiator Cfg:
  initiator_state: ISCSI_INITIATOR_READY
  initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR
  VLAN: 0
  DHCP status: false
  IQN: test: iqn.2014 - 11.com.:8
  IP address: 192.168.1.59
  Subnet mask: 255.255.255.0
  Gateway: 192.168.1.5

  Cfg of target:
  Target the Idx: 0
  State: ISCSI_TARGET_READY
  State of PREV: ISCSI_TARGET_DISABLED
  Target error: ISCSI_TARGET_NO_ERROR
  IQN: iqn.2010 - 08.org.illumos:02:windowsboot
  IP address: 192.168.1.49
  Port: 3260
  Starting logical unit number: 6
  Ping statistics: success (986.646ms)

  Info session:
  session_id: 0
  host_number: 0
  bus_number: 0
  target_id: 0

  can anyone help me to solve this problem?

  Thanks in advance - Fabre

  ENIC / fnic driver must be installed. they are not part of any Windows operating system.

  they can be found in

  Home downloads
  Products
  Servers - unified Computing
  Series B UCS Blade Server Software
   
  Unified Computing System (UCS) Drivers - 2.2 (3)

  ISO image of drivers based on the UCS 
  UCS-bxxx - drivers. 2.2.3.iso

  Depending on the version of the UCS.

• Nested ESXi 5.1 and iSCSI Shared Storage

  People:

  I am unable to get my ESXi servers nested to see the iSCSI shared storage, that I put in place for them.  I use iSCSI for the ESXi host, who holds the guests of ESXi, so I have a successful iSCSI configuration to use as my reference.

  Here's what I have for the host network config:

  iSCSI targets

  + IP1: 172.16.16.7 (subnet for host IP storage)

  + IP2: 172.16.17.7 (subnet for storage over IP comments)

  vSwitch associated vmnic2 on NIC IP storage

  + Port "IP storage" group containing virtual NIC both ESXi hosts

  + VMkernel Port for iSCSI host connections: 172.16.16.28

  Here's what I have to config network comments:

  + The highest virtual NIC group of ports "IP storage".

  + vSwitch with only a VMkernel port for iSCSI of the guest connections: 172.16.17.38

  From the iSCSI host, I am able to ping 172.16.16.28.  However, I am unable to ping 172.16.17.38, and here's the really confusing part - I am able to get an answer ARP of that associated with the VMkernel port with the correct MAC network CARD!  This eliminates all kinds of potential configuration issues (for example means bad NIC, bad IP, etc..)

  The firewall on the host indicates the software iSCSI port outgoing 3260 Client is open.  Capture of the target iSCSI host package reveals no. TRAFFIC from VMkernel IP guest when updating to storage adapters.

  What should I look at?  The configuration of the host against the host looks identical yet we work and there is no...

  -Steve

  In the debugging process so, I turned on the "Promiscuous" mode on the vSwitch associated vmnic2 on the NETWORK card on the host IP storage ESXi and poof!  Everything magically started working.  The iSCSI traffic be unicast, so I don't see why promiscuous mode would be necessary, but I can't argue with the results observed.  Clearly, I have more to learn more about nested ESX, that's why I'm playing with it.  :-)

  -Steve

• 5.0 to 5.5 with iSCSI ESXi ESXi

  I have some servers ESXi 5.0 with iSCSI configured for my storage. If I'm on 5.5 ESXi, should I reconfigure the iSCSI? If so, how differente different is the configuration? I know that we had to set up when we went from 4.x to 5.0 ESXi ESXi and the configuration options are very different. Is this the case with the new version?

  No, you stay within the same major version and it should work without any problems. ESX ESXi (i) 4-5 were important steps, they are smaller. Made this upgrade in environments of production before without any problem or reconfiguration.

• iSCSI network problem

  I have simply attach an iscsi storage to ESXI and then allocate space on the storage to a virtual machine. In the virtual machine I copy a large file (about 4G) to this disc, in the process, it's always happened that adaptation procedure does not.

  I tried iStorage server and Starwind. iStorage server is a little better than Starwind in performance.

  Without details about your configuration, it is difficult to say what the problem is. Please provide as much detail as possible about your test environment, the versions that you are using and the configuration of the network (especially the iSCSI configuration).

  Best bet is usually to use the vendor's documentation best practices. On the site of Starwind you find these resources, Kernsafe site is not easy to find documentation and what I've found, it's a little outdated (configurations for ESX 4.0), but maybe I missed something. However, given that you work for Kernsafe I am sure that you have access to the documentation.

  André

• Change IP iSCSI on the fly?

  
  Hello

  Just, I came across an interesting, whatever it frustrating problem.  Among the two survey periods that I use for my iSCSI configuration was 'borrowed '.

  I am running ESXi 4.1 Update 2 +.  The iSCSI configuration is a typical separate vSwitch containing two vmnic, each attached to their own port vmkernel for failover purposes.

  I am running with a single path, so he has not failed yet.  Can I change the IP address on the port of vmkernel iSCSI in question on the fly?  I guess the real question is, I have to reboot the host after changing the IP address?

  Thanks in advance!

  -Bob

  No you will not have to restart the ESXi host after changing the IP address of the iSCSI vmkernel

• How can I configure the SAN as much be access from the guest OS

  Hello... first post ever here so I apologize if this was already asked, but so far I can't find an answer.

  We have a 12 to SAN we would like to share and all the virtual machines on the virtual domain.

  The SAN is a dell powervault MD3200i.

  I read everything on iSCSI configuration, but what it feels like to give esxi host access to the LUNS for vmotion and other features of vcenter (made).

  We need is our access as a guest VM OSs logic 12 TB of drive as a drive to share space.

  Any ideas?

  Thank you.

  P.S. I tried connecting to the San of the guest OS via iSCI but once the MS iSCSI initiator will connect and connect to the IQN name local disk VM management cannot see the new volume/drive.

  1. Create a LUNa
  2. Add LUNa to the "storage group" in the SAN
  3. Add Datastore (LUNa) in vCenter formatted as a VMFS (datastore-LUNa)
  4. create a virtual machine.
     1. Installation of the OS, etc.
     2. Add the disk (vmdk)
        1. Select location "Datastore-LUNa.
        2. Maximum size, or you can create several small VMDK in "datastore-LUNa.
        3. Select another SCSI controller:
           1. OS (vmdk1) = 0:0 [(datastore-LUN-OSs)]
           2. Data1 (vmdk1) = 1:0 [(datastore-LUNa)]
           3. data2 (vmdk2) 2:0 = [(datastore-LUNa)]
           4. etc.
        4. log on to the operating system invited
        5. It Manager
        6. 1. turn on the drive
           2. initialize
           3. etc.
     3. Activate the "File server" role in the guest virtual machine OS
        1. create shares as much as you want!