ISCSI traffic

Similar Questions

• How a policy without moving can be configured for iSCSI traffic in Nexus 5548UP? Are there side effects?

  How a policy without moving can be configured for iSCSI traffic in Nexus 5548UP? Are there side effects?

  Hello

  Side effect depends on your network config, but I can tell you how config no iscsi traffic reduction policy...

  We have three-stage configuration in link below is image...

  1. QOS class - for the first traffic ranking

  2 queue (INPUT/OUTPUT) - this is where you book or traffic police

  3 Netwrok QOS - where you key or setting MTU for classified traffic at the bottom of the basket which tissue in the nexus program

  

  (config) # class-map type qos myTraffic / / traffic ISCSI of Match
  (config-WCPA-qos) # match iscsi Protocol

  #policy - type myQoS-QoS policy map / / qos Set group 2 ISCSI traffic so that it can be recognized
  class myTraffic
  the value of qos-Group 2

  (config-WCPA-may) # class-map type networks myTraffic
  (nq-WCPA-config) # match qos-Group 2

  (nq-WCPA-config) # type network-qos policy-map myNetwork-QoS-policy
  (nq-pmap-config) # class type networks myTraffic
  (config-pmap-nq-c) # break without moving
  (config-pmap-nq-c) # mtu 2158
  (config-pmap-nq-c) # sh type of network-qos policy-map myNetwork-QoS-policy

  (config-pmap-c-qos) # class-map type myTraffic queues
  (config-WCPA-may) # match qos-Group 2

  (config-pmap-nq-c) # policy - map type queues myQueuing-policy
  (config-pmap-may) # class type myTraffic queues
  % of bandwidth (config-pmap-c-only) # 50
  (config-pmap-c-only) # class type class default queues
  % of bandwidth (config-pmap-c-only) # 25
  (config-pmap-c-only) # sh policy-map type myQueuing-policy Queuing

  (config-sys-qos) # type of service-QoS policy entry strategy myQoS
  (config-sys-qos) # type of service-network-qos myNetwork-QoS-policy policy
  -service policy (qos-sys-config) # type myQueuing-policy input queues
  (config-sys-qos) # type of service-policy output myQueuing-policy queuing

  Let me know your concerns

• Installation of physical switches for ISCSI traffic

  Is that all I need to know from a networking perspective to configure ISCSI switches dedicated to support my ISCSI SAN on the left?

  I do not plan on switches connected to the prod network. I only plan on using these switches for ISCSI traffic.

  LeftHand supports LACP, if your supprt of switches that you should consider using the trunk mode. In my SAN P4300, I have two 3750's stacked. Each SAN node will connect to each switch and is located in a LACP/etherchannel link. All this is condensed to a single virtual IP address which is presented to ESX/i. don't forget to create a vmk for each dedicated vmware iscsi connection and bind according to this pdf.

• Question about VMKernel iSCSI traffic and VLANS

  Hello

  This is a very fundamental question that I'm sure I know the answer too, but I want to ask him anyway just to reassure myself.  As a precursor to my question, the configuration of my ESX infrastructure is best described here: http://www.delltechcenter.com/page/VMware+ESX+4.0+and+PowerVault+MD3000i.  Or more precisely, we have two controllers MD3000i.  Each controller has two ports and each port is configured on two different subnets, with every subnet connected to the different switch.  ESX host are connected to two switches.  The only difference for the guide, is we have two MD3000i configured the same, connection to the same switches.  Each MD ports is configured on the same subnet, but different IP addresses.

  At present, we are in the process of upgrading our two iSCSI switches of humble Dlink DGS - 1224T to Cisco 2960 T of.  The switches have been and continue to be dedicated to iSCSI traffic, however, I'm trying to set up VLAN s on the side of the switch.  Originally, we used the default VLANS on switches, however, after you have added an another MD3000i, noted the Support Dell best practices is to separate each on its own subnet and VLAN MD3000i iSCSI traffic. This would result in iSCSI 4 VLANS, two on each switch and two for each MD3000i.  Firstly, is this in fact of good practices?

  Second, if I migrate preceding 4 iSCSI VLANS, as each switch port will actually be an access port, will there need to complete the VLAN ID field in the VMKernel configuration page? Presumably, this field is used when the tagging VLAN is used, but as our switches do not need any other rocking trunk (as they are dedicated to iSCSI traffic), there should be no need to fill?  I guess it would be prudent to keep the two existing subnets, create two new subnets and make changes to an MD3000i and connection of the ESX host.  Provided the switch and switch ports has been appropriate configured with VLAN on the right, the rest should be transparent and he wouldn't be Intel VLAN in all ESX hosts?

  Would be nice to get answers and thank you in advance!

  Gene

  (1) Yes, it is best practice for ESX iscsi, having an independent network and vlan for iscsi traffic.

  (2) No, there is no need to mention anything in the area of vlan, if you use an access port. Its a mandatory thing than a choice. If you supply the id vland with access port, it loses connectivity.

  Please explain a bit why you need to create two different virtual local networks for each MD3000i. You are going to use several on the same ESX box iscsi storage? Alternatively, you use only a single iscsi and use these 4 ports for the same single VMkernel interface?

  NUTZ

  VCP 3.5

  (Preparation for VCP 4)

• Can I use 8 gb Fibre Channel for storage iscsi traffic and 1 GB for standby

  Environment

  Version - Vmware: ESXi 4.1

  -Host: 360 g-7 DL, 2 x 1 GB quad port NIC, 1 dual CF 8 gb HBAS

  -Storage: EMC VNX 5300 host FC HBAS are directly connected to the San

  Background

  We currently have a 1 GB LAN (Cisco 3750 battery) \storage (san is LeftHand 4500) network that will not provide the e/s, we need for our SQL server due to a limitation of the NMP esxi a company proposes a new solution of storage for us.

  Overview of storage design:

  2, 1 GB of NIC quad by the host in support of our networks (VM\MGMT, vMotion, DMZ, iSCSI).  Add a dual port 8 gb FC HBAS on each host for storage.  I then path redundancy but not the redundancy of HBA cards.  Can I use the existing 2, 1 GB iscsi NIC as the standby for the FC HBA just to limp along until I vMotion, virtual machine to sql server on a server that has a FC HBA?  Obviously the performance of I/o would be take a hit but I rather he would perform badly only totally cut off IO.

  Maybe that's not possible even remotley, but I look forward to comments.  Thank you!

  While I've seen this work his * explicitly * not supported by EMC.

• An iSCSI hardware network card can be used for ordinary IP traffic?

  If I have a hardware iSCSI HBA card, it's a NIC where ESX could unload all iSCSI handling to, this card could be used for something other than iSCSI or it will only be dedicated to iSCSI traffic?

  In other words, for example, could vMotion or VM traffic more than NIC go too? (It obviously wouldn't be a good thing to do, but I'm curious to know if it is possible).

  If you mean an HBA full offload iSCSI, then the answer is no. The HBA actually operates all the management of the TCP/IP Protocol and presents the iSCSI LUNS to the host as direct-attached storage. If you go to the QLogic website, you can find a few whitepapers that explain unloading as well as certain patterns showing the CPU load with a THAT HBA full offload compared with active TOE NIC (such as HP/Broadcom).

  André

• iSCSI - dedicated VLAN vs traffic switch

  I have a fairly low vSphere - 2 ESX hosts with 6 VM environment (will increase to 12 + VM the end of the year).  My iSCSI SAN has only 1 interface iSCSI traffic.  I currently have a VLAN defined on my switch/GB of network traffic for iSCSI traffic.  I know that the ideal is to have traffic iSCSI on its own switch.  It would be overkill for my environment? I can buy a HP ProCurve 1810 switch for under $ 400.

  Vote for her dedication also.

  In addition, you can change the iSCSI performance by substituting "automatic negotiation" in manual mode

  setting the parameters of speed of the card NETWORK and the switch. This allows you to

  enable control flow of traffic on the NETWORK adapter and the switch, Ethernet

  frames on the NETWORK adapter and the switch to 9000 bytes or more-

  data transfer more far in each packet while requiring less

  overhead. Extended frames are expected to improve the flow as well

  less than 50%.

  ---

  iSCSI SAN software

  http://www.starwindsoftware.com

• best to spend to iscsi or vmotion traffic

  I have a total of 10 network interface cards in my server and now cut out it as follows:

  2 Management (sc)

  iscsi traffic 3

  VM 3 traffic

  I have an Equallogic PS5000e iscsi.  I'd better give my last 2 network interface cards for iscsi traffic? VM traffic? or the last 2 vmotion?  I wonder what the bottlenecks are currently.  I wonder if the Equallogic can really do use connections more?

  Hello

  I'd better give my last 2 network interface cards for iscsi traffic? VM traffic? or the last 2 vmotion?  I wonder what the bottlenecks are currently.  I wonder if the Equallogic can really do use connections more?

  I consider the following basic concepts of networking virtual:

  (A) always have 2 natachasery by network

  (B) to maintain the separation of the network for security reasons.

  So I would like to do the following at least:

  2 natachasery for SC

  2 natachasery for VMotion

  2 natachasery for iSCSI

  2 natachasery for VM networks

  This leaves 2 natachasery you can place where you need it at a later date. You can find 2 months later that you need on iSCSI or network of the virtual machine to a whole new network. It is very easy to add them here where they are needed. You may not need them anywhere for the load that you have.

  Configure the system with 2 natachasery by network, configure virtual machines and run tests to determine where they are going. I bet you need it with iSCSI, but that depends on balancing than anything else.

  Best regards
  Edward L. Haletky
  VMware communities user moderator, VMware vExpert 2009, Analyst of DABCC
  ====
  Now available on Rough Cuts: ' VMware vSphere (TM) and Virtual Infrastructure Security: ESX security and virtual environment '
  Also available "VMWare ESX Server in the enterprise"
  SearchVMware Pro| Blue gears. Top virtualization security links| Security Round Table Podcast virtualization

• Net M4110x - Net management and iSCSI. Clarification of the configuration steps. The documentation is at best ambiguous.

  Hi guys,.

  I'm having a lot of trouble to translate what I know PS6000 table to the new M4100x.  Here's what I'm building:

  

  I want my iSCSI traffic that is completely isolated from all other traffic, and I want to use the CMC network to run the Board.  It must be a simple configuration, but Dell documentation for which is worse than useless.  It confuses and everyone who's read it confuses.  Why is this?

  It seems that I should be able to assign the IP addresses of management using the MCC according to DELL:

  Step 1.  Initialize the storage

  * Once in the CMC right-click on storage open storage gui initialization.

  * Member name: MY_SAN01
  * Member, IP: 192.168.101.10
  * Member gateway: 192.168.101.254
  Group name: MY_SAN
  Group IP address: 192.168.101.11
  Group of Memebersip password: groupadmin
  * Password Admin group: groupadmin

  It sounds simple enough, and when I apply this I guess I will be disconnected my M4110x simply because it currently resides on a separate network (net 2 in the image above).  Now how to set up the IP address of my CMC (net0 in the picture above) network management?

  Step 2.  Set ip management port

  According to the documentation of Dell, I have:

  To set the management port:

  * Open a telnet (ssh) session on a computer or console that has access to the PS-M4110 range. The array must be configured beforehand.
   
  * Connect the PS-M4110 modules using the following racadm command: racadm Server 15 connect
   
  * Connect to the PS-M4110 array as grpadmin

  Once I am in:

  Activate the management controller ports using the following commands in the CLI:
  0 > member select MY_SAN01
  1. (array1) > eth select 1
  2. (array1 eth_1) > 10.10.10.17 ipaddress netmask 255.255.255.0
  3. (array1 eth_1) > upward
  4. (array1 eth_1) > exit
  5. (array1) > grpparams
  6. (array1 (grpparams)) > network management-ipaddress 10.10.10.17

  (array1 (grpparams)) > exit

  My interpretation is correct?  Now my questions:

  1. in step 2. SubStep 1 - How can I know what ethernet interface to use?  Step 1 automatically assume eth0?

  2. am I correct in using the same IP address for both step 2 - substep 2 and substep 6?  Or do I have to assign a different IP address for these?  10.10.10.18 maybe.

  3. step 2 - substep 6, it doesn't seem to be that a network mask is that correct?

  4. comparison of the ps6000e - I set up an IP address for each controller (so 2) and then assigned an IP address for the group.  It's 3 IP addresses.  For this M4110, it seems that I have only one controller.  Is this correct?  The specifications make a point that there are 2 controllers.  What happened to the IP address of the controller of the 2nd?

  CLOSE-UPS

  I intend on building a VMware cluster using the algorithm of multiple paths of DELL and I built it to the DSC, but a technician Dell put in place the table initially and have not set up a dedicated management port.  Required configuration routing traffic on the net iSCSI management.  It is not recommended, and I don't want to set up this way.

  Currently, he is a blocking problemand I need to go beyond this ASAP.  I work with a large system integrator in Texas and plan on the order that these systems built this way on their part.  This means that I must be able to explain to them how to proceed.  This issue is standing in the way of progress, and I really hope I can get a satisfactory response from this forum.  Thanks for any helpful answers.

  I think I have the answers to my own questions:

  1. YES.  Step 1 automatically assume eth0.  There are TWO Ethernet interfaces and eth1 is disabled by default, and unless you use step 2 to set the management port this second Ethernet interface is never used.

  2. No. I can't use the same IP address for both lines.  In lower level 6 I need to use a different IP address on the same network 10.10.10.18 would work fine.

  3. YES.  It is correct.  Lower level 6 assumes the network mask that I have included in the point 2.

  4. it's tricky.  There is NO WAY to configure Active/active on these tables.  There are 2 controllers, but one "still asleep," unless the other fails.  Actually, the IP address is assigned to an Abstraction Layer, it maintains.  When fails another controller "awakens" and just starting to accept traffic and it doesn't care what its IP address.

  Another point.  Now that my table is initialized and my interfaces are configured, I need to know what IP address to point my ESXi hosts for their storage.  Use the IP address of the group assigned in step 1.  It is 192.168.101.11 (there is typo in the original post).

• EqualLogic PS6100X: direct connections (double) iscsi to 3 vmware ESX host

  Hello

  Due to the reduction of costs, we integrate

  1 x ps6100x Dell Equallogic (2 controllers to each 4 ports)

  3 x dell poweredge r720 (each have 2 ports dedicated for trafficking SAN storage)

  vSphere 5.5 (shared storage on the San)

  Without the use of SAN switches. Each host has dual direct connection (1 to each SAN controller) with the initiator iscsi software.

  We did before with Dell MD3200i, who has also 2 controllers and 8 ports, so we expect no problems.

  But now that I have read on the Equallogic, I'm starting to become uncertain if this Setup will work?

  I know that this is not recommended, but at this point, my only concern is that it will work (even with less performance).

  Can you please give me some advice on this?

  Best regards

  Joris

  P.S. If this is probably NOT possible, what would be the best/low average cost to make this possible?

  I've seen this failure at work, as in the connections dropped, BSOD was virtual machines with a single host with no switch.  iSCSI traffic tends to be very burst, which is having when the right switch pays you back.

  Re: 3750 X are those good switches, there is some adjustment settings that need to be addressed.  Also to solve a flowcontrol problem download the most current IOS firmware.

  For such a small group / number of servers, the stacked 2960 would be OK.  Perhaps to problems later if you need to scale this environment.  lack of 2960 allocate buffer, then you want to start without Jumbo frames, all enter into stable and of good practices.  So maybe later try enabling it.  3750 X works very well with Jumbo and Flowcontrol active BTW.

  These choices are better than no switch miles.  3750 x were pretty expensive last time I looked.  Unless you have a little already.  If you share them with the rest of the traffic that is not optimal, but at least put all ISCSI traffic on its own VIRTUAL local network.

  4948 are the right choice.  Some high-end HP switches.  Step away from the elders, like 2810 or 2824/48.  They seem to be there for cheap $$ but are designed for GbE Office not GbE iSCSI.

  Kind regards

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

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

• 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).)

• Change STP UME in RSTP mode on two stacked powerconnect 6224 configured for iSCSI during normal operation

  Hello

  I'll do a fw upgrade during normal operation on a stack of 6224 circulating BPMH, I am currently aware of recommendations Dells run RSTP on switches configured for iSCSI traffic connected to Equallogic SAN.

  I intend to set up another pile with two 6224 to failover and then perform the upgrade on the stack of "old." My question is if it's possible to run BPMH on the 'old' stack RSTP executing on the new stack when LAG is configured between the two batteries?

  Another option would be if it is possible to reconfigure the 'old' UME to RSTP stack without interruption between the hosts and the SAN first?

  Guidance on this subject would be greatly appreciated

  Cree

  Multiple Spanning Tree Protocol is based on RSTP and is backward compatible with

  RSTP and STP. So, you should be able to run BPMH on the old and RSTP on the new.

• Fabric of interconnection to Bay iSCSI connection

  I need to connect my fabric for interconnection to a new array of iSCSI.  There are a number of blades UCS that need to connect to iSCSI LUNS. The FI is currently connected to the rest of the network through switches to Nexus 7000 K.   Should I I plugged directly from the FI to the iSCSI array or go through the 7000 K and then to the table?

  Hi, this is more a matter of design, you need to think about what will need access to the storage ISCCI matrix. For example, if a single UCS blaes will have access to this storage group, you can consider plug directly such as iscsi traffic must pass your N7Ks if the two fabrics are active. If you want another type of server such as HP or IBM to access storage, you should consider to connect the storage array to the N7Ks if your tissues are configured in end-host mode. Again, this will depend on your current implementation