iSCSI networks

Similar Questions

• Hyper-V and iSCSI network

  Hello

  We evaluate a migration of vmware for hyperv.

  I try to understand best practices for networks iSCSI comments.

  I have physical 4ports 1GBit dedicated, on the host for iSCSI traffic.

  I like to use all 4 for iSCSI host (vhdx volumes) traffic.

  Now I thought to do 2 of them shared by creating 2 logical switches in VMM, adding 2 virtual network cards for the host to use.

  The new virtual network cards are 10 Gbit. I don't see an option to change them to 1GBit. To me it seems now that the system prefers the 10 GB adapters. My other two physical cards are no more used.

  I tried to do all 4 ports as virtual, but somehow the 4.7EPA ASM does not see virtual cards. He said only: "no network adapters don't find" at the opening of the MPIO settings.

  Should I just ignore this idea to share and use 2 for host and 2 for iSCSI hosts, or is it a medium work?

  It is recommended to devote at least 2 interfaces on the host iSCSI network.  In addition, you must install the Dell EqualLogic for Microsoft host integration tools and install the MPIO feature.  To enable the MPIO in the guest operating system, you must create at least two virtual switches that are related to the physical SAN on the Hyper-V host adatpers.  Virtual machines must be configured with at least two of these virtual switches.  Then, since the guest operating system, configure interfaces with IP iSCSI network, Subnet, etc...  You must also install the Dell EqualLogic for Microsoft host integration tools and functionality MPIO DSM in the guest operating system, if it is not running Windows.  If you use Jumbo frames, ensure that all NETWORK adapters used for iSCSI (NETWORK physical cards, NETWORK cards, Guest OS NICs) are enabled for frames.

  In regards to ASM v4.7 EPA you don't see not cards network for MPIO - there is a known ASM / ME v4.7 bug in Windows Server R2 2012 linked to the EPA.  It is likely that the configuration of MPIO is fine (you can check it out through the initiator Microsoft iSCSI MPIO EqualLogic tab - it's just that ASM / me has a problem of information display.)  This bug has been fixed in version recommended to v4.7 GA HIT/Microsoft - which is intended to be published very soon.

• Adding the iSCSI network switch

  Hello

  We have an iSCSI network for guests of vSphere 5.1 EQL boxes. The network is 192.168.0.0/24, we use the switches PC5548 and we have three groups EQL. Everything is configured following best practices from DELL, and everything is kind of okay job.

  Since we are affected by the poor performance of our SQL servers virtualized and troubleshooting led switches as a guilty suspect I want to try to use other switches to know.

  So I intend to add a pair of parallel to the PC5548 cisco switches and connect a host and a group of PS to those (where the SQL VM reside) and see the difference, but my question is that I can use the same network 192.168.0.0. / 24 although cisco and dell switches are not physically connected. VMotion work?

  You shouldn't use the entry level switches with 10 tables. The interlink trunk has 80% of eql bandwidh. You can consider buying Dell Force10 switches with buffers of large size and low latency.

  Kind regards

  Joerg

• How to segragate VM of each other AND Management & iSCSI network traffic?

  I want to test how I can keep VM isolated from each other AND the segments of iSCSI network and management... It's just a proof of concept, so I not be using redundant paths.  I want to know how I can keep all my shelter of the attackers 'would '?  that is if one of the virtual machines becomes "compromise" How could I isolate all "would be attackers" to travel to other virtual machines or networks of management/iSCSI?   Is there a way to create each virtual machine in a VIRTUAL LAN on the ESX host? Or is there a better way?

  For the installation of the physical hardware - sounds?

  TahoeTech wrote:

  "So, to make sure that I understand...". I'll install VMware ESX on

  the physical host machine and then create 3 vSwitches which will be

  related to 1 physical NETWORK card by vSwitch? "

  Since I only need to the DMZ network available to VMS - must - I still 3 vSwitches?

  Yes, one for virtual machines, one for management and one for iSCSI. You may combine up to vSwitches (2) combining management and iSCSI, but it is not recommended.

  The host machine does the iSCSI storage to virtual machines as a "disk"?

  More or less, Yes. When you create a virtual machine, you need to configure the disks for this virtual machine. You will be asked which data source to use, and you choose the iSCSI data store, that you create when you set up the data store and iSCSI.

  The host uses the vSwitches? I thought that the host machine could use physical NETWORK cards... i.e. Teddy 1 would be management and Teddy 2 would be iSCSI, Teddy 3 would be linked to a vSWITCH for virtual machines?

  Yes the host use the vSwitch, after all the console, etc. is a virtual machine its self

  Virtual machines will never see a teddy bear. You want to assign a vNIC to the virtual machine when you create the virtual machine. The vNIC is connected to a group of ports, which in turn is connected to a vSwitch, which in turn is connected to a teddy bear.

  The virtual machines do NOT need access to the networks of management or iSCSI (I don't think)?

  Fix.

  The management network connects to ESX physical HOST (Teddy 1) in order to control the accurate virtual machines?

  The management of the network give you access to control everything via vCenter or the VI client or the command line.

  And the iSCSI network connects to the physical ESX HOST (Teddy 2) where the ESX host will present data warehouses to virtual machines as 'physical' disks correct?

  Yes, it will look like just a physical disk to the VM operating system.

  I guess what I'm trying to understand, or how I see it is that the host ESX is the only machine that has 'see' the iSCSI network?

  The VMKernel manages iSCSI seamlessly. Guests don't need to know anything iSCSI.

  Virtual machines see drives that presents the ESX host? For the virtual machines do not need is access to the iSCSI network (unless I need to install additional storage or drive shared etc...)

  Fix.

  any idea when VI4 is scheduled to be released?

  Rumor is soon. But unless there is there a feature that radically changes your design I wouldn't get too worried about it.

• install new PS6510e - no communication on Iscsi network

  Getting desperate here now.

  bought refurbished ps6510e of third-party reseller - have been categorically denied access to the site of dell for support on that basis.

  connected to 2 servers R720 via grouped 10 gb SFP + cables through a switch of 8024F to SAN with redundant connections of 10 GB on two controllers. configured on the private network for iscsi only traffic with addresses private to each server, switch, Saint Nic individual and the Group ip san.

  set up in business / management network for servers / san / management switch with works perfectly.

  2 (2012r2) servers can communicate with each other via the links of 20 GB. No communication with san via ping or connecting iscsi connectors at all. servers can ping each other and switch, not san. CLI in san - cannot ping anything - not even his own individual ip addresses. SAN web interface reports that snap ports (15 + 16), it is plugged into the switch so that he knows that she is and that she connects to her apparently happy.

  configured according to the guidelines of dell white papers, frames, LAG switch. I swapped 10 GB connections between servers and san groups, and regardless of the combination of connections, servers talk, san does not work.

  interface Web and SAN HQ all report everything is hunky dory. one mistake is on the free space that we have configured volumes while.

  bright ideas about what was fundamentally wrong very favorably received.

  Hello

  Re: refurbished.  Sorry, but Dell does not offer without PS Series in this way.  Dell partners cannot provide these services either.  Support requires the table under warranty or support contract access to firmware, and other downloads.  In addition, the license to use the table is maintained in the contract, not the hardware.  This license may not be transferred or resold.

  Re: is associated. PS Do not support series without grouping at all.  You need to configure MPIO on servers instead.  Almost sure that tagging VLAN is not in use, or stripped of all PS Series ports.

  In the GUI, network ports show online?

  On the switch, make sure that you have the current firmware, and data center bridging (DCB) is disabled.

  Given you cannot ping anything, I suspect the cable or switch configuration.  If you use TWINAX cables be PASSIVE, Active cables are not supported.

  Kind regards

  Don

• How to use 4 x 1 GB for software iSCSI NETWORK interface card.

  Hello. I have a HP P2000 G3, with iSCSI connections 4 x 1 GB. I have 4 free 1 GB NIC on my 5.5 esxi server. IM wondering how I could put things upwards, so it would use iSCSI 4x1Go at the same time, so I would get a 4 Gbps to my SAN connection. Is this possible? I read something about iSCSI multi-trip and Port binding, but is all a bit confusing. It seems to me which is used for failover? I tried to put in place using a multipathing guide and got to the top and his display I 8 paths to my SAN, but it seems that a NETWORK adapter is used when considering my switch activity.

  Any help would be appreciated.

  Take a look at this blog post: http://www.virtualtothecore.com/en/howto-configure-a-small-redundant-iscsi-infrastructure-for-vmware/

• iSCSI network configuration

  Hello world

  I did two configured 5.1 esxi hosts with iSCSI SAN and they work very well. In fact, the configuration of the network is as below:

  MD3200i: 4 of the 8 ports configured on both controllers. two on a subnet on VLAN x and two on another subnet on VLAN y.

  ESX HOSTS: two different vSwitches with a vmnic and a vmkernel on each host.

  Everything works well, with configured multipath.

  So now: I want to improve the performance of storage using the last four ports on the md3200i and the two NICs per host.

  My question is do I have to create new vmkernel for each nic 'new' or do I just add nics on my vSwitches?

  Maybe I misunderstood the documentation I've read, but the portbinding is not improve performance but only HA feature?

  

  Thanks in advance

  Martin

  Unless there is something that has changed lately, you need a one-to-one relationship between groups of VMkernel ports and vmnic. Actually regardless if configure you this in a single vSwitch - with setting the vmnic as assets/Unused - or by using a vSwitch by group of VMkernel ports.

  André

• 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é

• iSCSI Network Design

  Hello

  I read the guides to good practice and familiarize themselves with VAAI vStorage API allowing integration of table, but remained little clear on the two designs I am currently working on. Can someone provide suggestions for the following configurations? Thanks,-Jeff

  CONFIG HAS

  ESX 3.5

  Two network ports available for iSCIS traffic on physical servers

  two controllers Server - NetApp 2040 - iSCSI - each controller can only see the LUNS on this controller

  The controller has two network cards configured in a high HEAT

  Ports switch Cisco 24 in the interval configured for frames and the VLAN native

  Question - should separate vSwitches two be created on networks separated for failover, or network cards must be involved?

  If the network adapters are associated are active, reserve active?

  B CONFIG

  ESX 4.1

  Up to six network ports available for iSCIS traffic on physical servers

  iSCSI - 480 EMC server, two controllers, level of talent to support VAAI

  Each controller can see all LUNS

  Each contreller will have four network adapters configured in two ALIVE

  Cisco 48 ports between the two switch configured for frames and VLAN native

  No idea what this config shoud be to support high availability and multi-pathing (is multi-pathing support in this config?)

  CONFIG HAS

  Question - should separate vSwitches two be created on networks separated for failover, or network cards must be involved?

  If the network adapters are associated are active, reserve active?

  Grouping of NETWORK cards would probably be a better bet, here, with assets.  In fact, you won't see a lot of load balancing between the two network cards, but a little does not hurt.  If you configure your political grouping based on the destination IP address and you have your storage ports are numbered sequentially, you'll have the best of the use cases of these two ports.

  B CONFIG

  ESX 4.1

  Using iSCSI multipathing.  Here is a good blog on how better to use with a Clariion system.  FLARE 30 should be out soon and take care of this limitation, so you can use iSCSI multipathing as described in the Guide of Config of iSCSI SAN.

  http://virtualgeek.typepad.com/virtual_geek/2009/08/important-note-for-all-EMC-CLARiiON-customers-using-iSCSI-and-vSphere.html

  Andy

• Right for iSCSI network switch

  I am looking at a switch for an entry-level iSCSI SAN and I'm looking to find the right sort of numbers for the speed and the size of the Mac Address Table.  My storage network is a MSA2324i HP array connected to two HP DL380 G6 servers using iSCSI.

  I had looked at HP Pro curved Switch 2824 and switch SRW2016 of Linksys.  The Linksys, I have used before in the 24 port model and me found it performs well for a 30 users network with VLAN but I want to know if it will support storage network traffic.

  HP Pro curve that I know will be good but it is three times the price and I am limited in the budget.

  Anyone has any advice on a switch which must support traffic from 15 servers, including Exchange 2010 and SQL Server 2005 with DR and HA.

  I would struggle see exhaustion MAC address as a problem. A storage switch must be insulated, and with 15 servers + SAN, you have 16 MAC addresses. Even something very entry level should handle this.

  That you need to make sure, is that the recommendations of the iSCSI standard are supported:

  • Jumbo frames

  • Flow control

  • Rapid STP

  • A bottom of basket fast enough run at full speed on all ports

  • A high level of management.

• Need help to set up my dish-solution ISCSI network

  If the network is flat and since then have been introducing iscsi I want to segment the iscsi traffic, but networking's obviously not my thing.

  How would I go about isolating iscsi traffic? We are a Microsoft shop. Microsoft DNS and 10. .. * network.

  A bit of a personal choice.  But we put our iSCSI on two netowork unmanaged switched networks completely isolated from his own.    Decent switches non-managed CONCERT are darn cheap these days.

• Reviews for iSCSI NETWORK card

  Hello, this is my first post so please excuse me if I violate no forum label.

  I would like some advice on the EP 12 G rack range NIC.

  There someone of any quad 1 GB port card a TOE NETWORK interface? It seems that the standard 5720/5719 Broadcome that comes with tell the R420 - r.620 has only TSO and no TOE. And none of the cards 1 GB iSCSI unloading.

  However Cisco servers have a NIC called Broadcom 5709 1G and TOE.

  Only 10 GB NIC/NAC has full TOE/iSCSI unloading.

  Please advice :)

  Kind regards

  Hosni

  unloading iSCSI is probably relatively expensive for a 1 Gbit NIC, which is a reason why Dell does not offer this (more (I remember older Dell Broadcom NIC offering him)).

  Add $50 to $ 100 NIC solution (1 GB dual port) is a fairly significant increase, but adding $50 to $500 (dual port 10 GB) card NETWORK solution is a lot less impacting. Reference Dell seems often to look at it this way.

  Also; unloading iSCSI doesn't seem to be useful in some situations; boot-from-SAN and if you want to put a file on a volume of SAN. These two have some major drawbacks when there is (much more difficult to solve) SAN connectivity problems.

  Add iSCSI unloading to record the power CPU, in my opinion, is worth it because the use of the CPU by the Broadcom or Intel NIC driver is very low on the modern servers than the total processing power of the server.

  If you really want the iSCSI unloading, I would suggest that you consider a Qlogic solution, or go with a solution of 10 GB.

• iSCSI network

  In ESX Server 4.

  The Service Console port is necessary for vSwitch used for the iSCSI connection?

  How can you use the GUI mgmt without the service console?

  You can build a vSwitch, which includes only a vmkernel port. You can use it to connect your iSCSI strorage.

• Questions of ESXi 5.1 ISCSI--> cannot establish a network connection (continued)

  Hello world

  I had a problem there not too long ago (thread link below) where my ESXi hosts could not establish a connection with an IBM DS3500 on start up and "rescan", however their connectivity worked correctly without any problem after commissioning and when a "rescan" finished. We determined that the most likely cause was the unit IBM itself. However, I wasn't completely satisfied.

  In order to deepen the question and dismiss my guests being the problem, I created a unit ISCSI myself with two new hosts of ESXi 5.1 (version 1157734).

  ESXi signals that it cannot connect to the initiator ISCSI (network error) - but it can run virtual machines and browse data stores?

  The configuration is the following:

  Test environment:

  2 x ESXi 1157734 hosts

  1 x server Freenas ISCSI (ZFS R10)

  At the start of my ESXi hosts in the test environment, download the same error as our production environment. They also put on the same error message (in the event log) when I "rescan" map of the ISCSI software. However, once the scan is finished, I can't see any error message and everything continues as it should (Round robin, active active). I can get a brilliant flow also. It's as if the errors are almost... false positives?

  Example of the error message (test environment):

  Connection to the iSCSI target

  IQN.2011 - 03.org.example.istgt:iscsi on vmhba35

  @ vmk2 has failed. The iSCSI initiator couldn't

  establish a network connection to the target.

  error

  17/10/2013-08:33:35

  ESXi hosts are configured as follows:

  Test environment:

  • (ESXi hosts) Two network cards for ISCSI, one for VM traffic
    • NIC1: 10.20.20.2/24, NIC2: 10.30.30.2/24
  • (Freenas) Two network cards installed on the ISCSI device (dedicated to ISCSI traffic)
    • NIC1: 10.20.20.1/24, NIC2: 10.30.30.1/24
  • ESXi is set to round robin, which works properly (I can max on both ports at the same time)
  • Two VMKs are related to the ISCSI Software initiator and defined to dynamically discover the two ISCSI addresses
  • Unity of ISCSI and the hosts are not on the VLAN, the switch is dedicated to ISCSI traffic (However in the production, the two networks are separated by VLAN.) I removed the in the test environment to simplify everything)
  • The vSwitches (who hold a single VMK for ISCSI) are fixed:
    • "Promiscuous" mode: reject
    • Change of MAC address: accept
    • Forged passes: accept
    • The traffic shaping: disabled
    • No NIC teaming (obviously)
    • Each VMK inherits the settings of these

  Quick points:

  • My hosts use VMware approved NIC in my test environment. My production environment runs on full VMware hardware approved
  • Can I use ping of vmk join each each VMK ISCSI initiator
  • I can use the nc-z target_ip 3260 command to check connectivity to the port
  • The ISCSI test has two network adapters, each on 1 Gbps ports
    • I can get around 800mbps per port when copying lots of files (both ports are active)
    • I see no error in copying a large number of virtual machines around, or backup files
  • I only see errors on start up and "rescan".
  • I have two network adapters on each host ESXi dedicated for ISCSI. Each NETWORK card has a single VMK. A single mapped port on ISCSI, the other is mapped to port B (I used to have two VMKs by nic, but I removed that in order to simplify everything)
  • I have updated the firmware on our switch of production. No results
  • I've used 4 different switches in order to avoid a network problem. No results
  • I tested ESXi versions 5.0, 5.1 (799733 & 1157734), all have the same mistakes
  • The ISCSI ports are on different networks according to the VMware (I was told not to put on the same network VMKs)

  Any ideas? It's starting to drive me up the wall. Any help would be greatly appreciated

  I've seen several times in recent months and was beginning to think it is specific to the HP P2000 units because it's the only time wherever I saw him! I now believe that ESX/iSCSI rather than issues of driver or table.

  On my last install, I found that errors occur as soon as the table is connected, i.e. before any storage is displayed.

  Single host ESX, no guests. 2 Intel adapters to 2 HP past by dedicated HP P2000 1 GB table with all 8 wired ports.

  All roads are good, all lights are in the State expected.

  It did not affect the use of the storage in question to any site, so there has been no need / a momentum of any further investigation.

  B! 886y annoying however!

• Set up new network iSCSI for VCenter

  Originally when we configure our environment VSphere, that we could not have our network engineers set up a separate subnet for iSCSI traffic.  Now, I have this ability and plan configuration.  I will be using our maintenance window to make this change instead of driving through the sectoral approach.

  My questions are about what communication is necessary between the two subnets, if necessary.  I will bind to the vmk ESXi iSCSI on the new subnet and they are the separate vSwitches but I'm not clear if the two networks require that any communication on the VCenter server.  The management network and LAN traffic will remain where it is in my plan will and so one of the network adapters on each host ESXi. Our network engineers want the two subnets to be completely separated, because this new iSCSI subnet will speak also to our recovery for SAN replication site, which brings me to another question. in order to use the software EqualLogic Auto - SnapShot Manager\VMWare Edition, she wants to be able to talk to the iSCSI network and the VCenter.  Anyone here used this feature without SRM?  I'm not planning to allow the SRM software currently in production, only half of my servers are VMs where all are as in DR and slightly different configs, so until I can duplicate both slots and fully use SRM I'll wait.

  I am also having a different subnet created only for devices management and applications such as updates of HQ of EqualLogic SAN, head of group and the servers, devices, etc.  It would be a more ideal situation to move the VCenter for?

  FYI, VSphere 4.1, ESXi 4.1, EquaLogic PS6000

  Also, I use FT and VMotion on different VLAN internal to the production of LAN and those will not change.

  Any idea or clarification is appreciated, I would like some feedback before .

  Welcome to the community - there is no need for vCenter communicate to your iSCSI subnet - all communication is handled by the ESX/ESXi hosts if ther EqualLogic can't answer to and his need to connect to vCenter.