ESXI 5 Broadcom 5709 ISCSI unloading

Similar Questions

• ESXi 6.0 challenges iSCSI Equallogic PS 6100

  Hi all

  I installed my Windows of 5.5 to 6.0 vCenter vCenter server.  At the same time, I wiped one of my Dell R710s 3 (3 years) to get a new installation, since it has been upgraded since ESXi 5.0.  I started with the Dell ESXi 6 disc.  Installation was smooth.  After you configure the host to match the configuration of my other two guests of ESXi 5.5, I couldn't have my Equallogic LUN to display.  Other LUN iSCSI (Drobo for backup, Openfiler to test) had no problem.  Only Equallogic and Nexenta.  The two without complain "Access denied" when the ESXi 6.0 Server tries to discover the San.

  By looking farther, two things have changed in ESXi 6 at face value: 1., My Broadcom NetXtreme II BCM5709 iSCSi cards are now registered as QLogic.  2. my software VMware iSCSI adapt now has a new name of the initiator.

  My Equallogic SAN running firmware 7.x.  To see if the pilot makes all the difference, I wiped the ESXi host once again and installed the version of VMware instead of Dells.  Now, my iSCSI network cards are a little different... ranked QLogic NetXtreme II.  Still, no luck on the SAN and errors on the persistence without 'access denied, or not allowed.

  I made sure I don't use CHAP or and ACL.  While the static tab to the Nexenta works (which means that he discovers all IQN) Lun never appear.  With the Equallogic, no IQN is discovered.

  I wanted to make this post to see if we can get this figured out and maybe after some good info if we get a resolution.  However, I don't have weeks to experiment, because I have to go back to vCenter 5.5 and recover the ESXi host.  Any help and suggestions would be appreciated!

  Hello

  On this page and update your firmware of hardware and its driver: VMware Compatibility Guide: search for i/o device

  Its brand name is also Qlogic

• ESXi 5.5u1 added iscsi storage adapter - reboot and now vSphere Client could not connect to "my ip" an unknown error has occurred.  The server could not interpret the customer's request.  The remote server returned an error (503) server unavailable

  I have not yet connect to an iSCSI target device.

  I can ping my host

  when I open http:// "hostip" in a web browser, I get a 503 service not available.

  restart the host gets me nowhere.

  SSH opens somehow, but can not connect

  Console seems OK

  vSphere Client can not connect

  If I reset to the default values of the console it is ok, but when I reconfigure the host, this error will be returned.

  I tried to reinstall from DVD

  I'm completely corrected to date via SSH esxcli

  This happens on both my hosts, although they are almost identical Lenovo thinkserver TS140s with broadcom 10Gig NIC and intel NETWORK card integrated

  It almost always seems to happen the next time I reboot after enabling iscsi support

  The only weird thing I have is that my Integrated NIC is a processor intel 217's and I have to use a special VIB so that it can be used in ESXi

  Customer's winning 8.1

  Here is my installation notes

  Install on USB/SSD stick with custimized ISO i217 NIC driver, reset the configuration and reboot

  Management NIC set to NIC0:1Gig

  IP management: hostIP/24 GW: my gateway

  DNS:DNS on windows vm1, vm2 Windows dns

  HostName:ESXi1.Sub.myregistereddomainname custom DNS Suffixes: sub.myregistereddomainname

  Reset

  Patch to date (https://www.youtube.com/watch?v=_O0Pac0a6g8)

  Download the VIB and .zip in a data store using the vSphere Client

  To get them (https://www.vmware.com/patchmgr/findPatch.portal)

  Start the SSH ESXi service and establish a Putty SSH connection to the ESXi server.

  Put the ESXi server in maintenance mode,

  example of order: software esxcli vib install /vmfs/volumes/ESXi2-2/patch/ESXi550-201404020.zip d

  Re install the Intel 217 NIC driver if removed by patch

  Change acceptance ESXi host sustained community level,

  command: esxcli software - acceptance-level = CommunitySupported

  Install the VIB

  command:esxcli vib software install - v /vmfs/volumes/datastore1/net-e1000e-2.3.2.x86_64.vib

  command: restart

  Connect via VSphere client

  -Storage

  Check/fix/create local storage. VMFS5

  -Networking

  vSwitch0

  Check vmnic0 (1)

  Network port group rename VM to the 'essential '.

  Rename management group of network ports for management of basic-VMkernel traffic.

  -Configuration time

  Enable NTP Client to start and stop the host. ntp.org set 0-3 time servers

  DNS and routing

  Start the virtual machine and stop

  -enable - continue immediately if tools start - stop - prompted action Shutdown - the two delay to 10 seconds

  Security profile

  Services

  SSH - startup - enable the start and stop with host

  Cache host configuration

  -Properties to start SSD - allocate 40GB for the cache host.

  Flashing warnings SSH:

  Advanced settings, UserVars, UserVars.SuppressShellWarning, change from 0 to 1.

  Storage adapters

  -Add - add-in adapter software iSCSI

  I think I saw that I was wrong.  In fact, I applied two patches when only suited. I started with 5.5u1rollup2 and then applied the ESXi550-201404001 and ESXi550-201404020.  Strangely I did not t o had problems until I worked with iSCSI.

• 6 ESXi and broadcom/qlogic 57800 errors in vmkernel.log

  The construction of a new host for ESXi 6. With the help of Dell custom ISO and then put to date with the latest patch. Have card 57800 2x10GB and broadcom 2x1GB (now qlogic). Firmware is the last 7.12.whatever and driver in vmware also seems to be later.

  In my vmkernel.log, I see the following messages every 2 minutes

  (2015 06-24 T 17: 08:47.788Z cpu0:33368)<6>host11: fip: host11: FIP VLAN ID no. Retry discovery VLAN.
  (2015 06-24 T 17: 08:47.788Z cpu0:33368)<6>host11: fip: fcoe_ctlr_vlan_request() is
  (2015 06-24 T 17: 08:49.790Z cpu31:33363)<6>host11: fip: host11: FIP VLAN ID no. Retry discovery VLAN.
  (2015 06-24 T 17: 08:49.790Z cpu31:33363)<6>host11: fip: fcoe_ctlr_vlan_request() is

  I found this article:

  http: //kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2120523

  but do not know how this applies.

  A 10gig links is used and also features offline in the vCenter. The other is showing that the unknown (it is not connected). I do not use FCoE and another r.620 with the old firmware but sam card and ESXi does not FCoE adapters.

  It is a bug? Is there somehow circumvents these garbage problem of FCoE filling the newspaper? Anyone see this before?

  The problem has been resolved. It is caused by the installed by the broadcom/qlogic driver startup script.

  As long as you do not use FCoE, you can remedy by you connecting to your ESXi host and running orders following, then reboot:

  software esxcli vib remove scsi - n-bnx2fc

  CD /etc/rc.local.d/

  RM 99bnx2fc.sh

  esxcli fcoe nic disable - n = vmnic0

  esxcli fcoe nic disable - n = vmnic1

  Depending on your configuration, adjust vmnic # according to your needs. I 2x10g and 2x1gig on my card but only had to do this on the ports 2x10g (vmnic0 and 1)

  If you try to disable the driver - instead of removing - and then remove the .sh file .sh file gets restored the next time you start to really remove the vib.

  Watch for patches that can reinstall the driver. This change can be found in the notes of the bnx2fc driver version. From 1.710.70.v version [50,55].2, this "feature" will be present.

  Dell helped me to find the solution for now, but there is at least another guy who stumbled upon this problem and posted the solution: www.davisphotoworks.com/.../broadcom-bcm57810-fcoe-and-esxi

• 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

• ESXi 4.1 or ESXi 5.0 with iSCSI SAN

  Hello

  I'm trying to establishing an environment that is / will be an iSCSI SAN backend entirely.  I know of a lot of reading that the best practice is to config the ESXi host with:

  VMKernel > vmnic > physical network adapter > switch ports > port on SAN (config 1:1 - no grouping of vmnic)

  Environment:

  ESXi 4.1 & 5.0

  Force10 switches

  EqualLogic iSCSI SAN (PS4000 & 6000)

  Here's my real question (playing the Devil's advocate):

  Why I shouldn't team 3-4 vnmics on a vswitch with multiple vmkernel ports?

  Given my environment.  Can someone point me to a technical document that explains what will / could happen if I set up the environment ESXi in this way?

  Thank you

  BDAboy22

  So, basically, we want the SAN to take full responsibility for the failover instead of the network and/or the SAN for who should resolve the failure (which could lead to the time of restitutio in integrum longer session).   I understand that correctly?

  Yes, that's right, we want to stack storage for vSphere manage with path selection and tipping - and by connecting each vmknic directly to the physical vmnic map we sort of "simulate" how to CF cards and also ignores the network failover mechanisms. As you probably know you also need to "bind" the iSCSI Software to the two vmnic (GUI now in 5.0, esxcli in 4.x)

• VMDK file between windows and ESXi with VMFS on iSCSI copy

  Hi all!  I searched here and that you find that no good answer but then I hope that someone can help you.

  We have a group of 3 servers ESXi running off a single iSCSI target and often need to copy VM from the VMFS file system.

  To help the conversion tool is incredibly slow, it's on.  WinSCP and FastSCP work at about 5 MB and 3 MB/sec.  FTP is the best option so far, but it is only 8 MB/sec.  When we have to copy around a virtual machine that takes a lot of time of 20 GB.  In addition, when we make 15 copies of a VM is incredibly long.

  I hoped to be able to directly connect to the iSCSI target and mount the system files somehow, but can't seem to find a way to do it.  Defect is there any method better or faster?  Perhaps a better FTP server than the option of proftpd?

  We hoped a local copy with either USB or eSATA method, but doesn't seem to work.  USB is not detected even and I can not get a non-VMFS file system to mount via eSATA.

  If it works better we can set up a linux machine to mount iSCSI target if copies of file can work this way.

  Thanks for the tips!

  NFS?

• DataCore DataCore-V with ESXi, vSphere 4.1 iSCSI running

  I have looked everywhere and come short on my problem, if this is a problem?  In the past, I have always connected all ESX / ESXi host through corn and now I work more with iSCSI.  I always try to get a handle on it.  It's one thing to read about iSCSI and he put in place of the other.  OK, now that I have that came down my chest, here is my question.

  Should the two iSCSI connections in DataCore-V show ready if I have both connected?

  Here's a high level race down the environment.

  1. a single node of DataCore

  2. a single ESXi host

  3. the two dual iSCSI ports

  4. on the DataCore node, only one port shows ready

  5. on the ESXi host two connections show connected

  

  Help, please

  Hello

  To meet ask you: It will say connected when a host 'iSCSI IQN init' is connected, simply because he says tell-connected does not necessarily mean that the 'network' is down... The host/s are not, cannot connected. (or none have been configured).

  More information about your configuration will be useful, however check over the info / recommendations below (Simple config)

  1. you set the "Port" Type for the two iSCSI ports on the DataCore for "FE" "Front End" Server?

  2. you have defined two separate IP addresses for the iSCSI on DataCore iSCSI ports ports?

  3 for simplicity on the ESX host, you have two distinct vSwitches for iSCSI with a NIC each with a vmKernel configured with IP to talk to the DataCore "target Ports.

  Therefore to confirm you can test the interfaces between them... now connect connection to DataCore target ports

  If you use software iSCSI Init, enable it on the ESX host... then you will need to "Discover" ports "targets" (static or dynamic)

  Once you add the two DataCore target Port IP please make sure that you "Login" for them to the ESX host. (BOTH)!

  If it worked, now you can join the 'Host' ESX in DataCore-V interface and assign the "iSCSI initiator" (from the ESX host) to it. (Only will be there for iSCSI Software...

  Now, remember, there is that a single iSCSI Software initiator, the important thing is to make sure this initiator is recorded in the TWO ports of DataCore target... Check the DataCore-V 'Remote Ports"tab on each port of 'target' for the IQN of the ESX host name.

  NOTE: DataCore servers don't support not multiple sessions to the same IQN to a vSphere Host to a unique DataCore iSCSI Target

  XXXXXXXXXXXXXXXXXXXXXX

  Also, please see best practice information about DataCore for your settings of the NETWORK adapter on the server of DataCore.

  the iSCSI traffic should be strictly separated from the public network (user).
  Use a separate hardware (LAN switches) to traffic storage iSCSI or less different virtual LAN (VLAN).
  Use separate NICs for iSCSI and inter-stockage server and communication management.
  Disable any other protocol or service except for "Protocol Internet (TCP/IP)" on the network adapters used for iSCSI. See help guide for detailed instructions.
  3260 port must be open on the firewall to allow the iSCSI traffic.
  On storage servers DataCore as well as disable Application servers/hosts these settings because they can cause disconnections and performance problems:
  Disable AutoTuning on W2K8: netsh interface tcp set global autotuninglevel = disabled
  disable RSS feeds: netsh interface tcp set global rss = disabled
  disable the TOE: netsh int tcp set global chimney = disabled

  Let us know how you and perhaps give a bit of monitoring more than info...

  Best regards

  Bernie.

• How many network adapters I - ESXi 4.1 with iSCSI

  I was wondering if someone could help me give a sense the news I read on # NIC for ESXi 4.1.  I came across the following article, but I'm not sure I understand all parts of traffic that he speaks:

  http://livingonthecloud.blogspot.com/2009/09/ESXi-networking-best-practices.html

  At the moment I have 6 cards 1 GB on each of my 3 servers.  I connect to my SAN via iSCSI, so I know I'm going to need at least 2 of these network adapters for that traffic. I know I'll need at least 2 NICs for connection between my ESXi server and my switch to the network of the VM.  What I don't understand is what I really need for the VMKernel FT, VMkernal Vmotion and VMKernal the Network Administration.  I do not plan on using Vmotion very often at all, so I'm not concerned about its impact on my network.

  Any advice?  I need to replace my double NICs with Quad NIC card or is it exaggerated?

  The management doesn't have a dedicated network card. It can share the network with virtual machines cards.

  In this case the following configuration would be interesting:

  vSwitch0: (3 NIC uplinks) (assuming vmnic0, vmnic1 vmnic2)

  Port group 1 - networking (vmnic0 and vmnic1-> active vmnic2,-> stand-by)

  Port group 2 - network of the VM (vmnic0 and vmnic1-> active vmnic2,-> stand-by)

  Port 3 - VM Network Group (vmnic0 and vmnic1-> stand-by, vmnic2-> active)-for the "Pervasive SQL.

  vSwitch1: (1 NIC/uplink)

  Port group 1 - VMkernel for vMotion on a separate network (192.168.x.x)

  vSwitch2: (2 cards network/links rising)

  configuration by following the best practices of your iSCSI storage provider

  In this way the "Pervasive SQL" would have a dedicated NIC (vmnic2) and may switch to another NETWORK card in the event of disruption of the network.

  André

• ESXI PE2950 Broadcom Vlan

  Hello

  I have 1 powerEdge 2950 III, with ESXi 3.5 (last update):

  (143129) I have two broadcom netxtreme NIC. They are connected to two

  first port of physical switch port (Hp procurve) .the is vlan tagged 101

  and the other is vlan tagged 103. I activated the vlan on both

  Broadcom. I put on esxi, 101 for the vlan of the first card network (for virtual machine Manager)

  and vlan 103 for the second (for the VM).

  Finally, the two broadcom ping anything.

  Can someone help me?

  Thank you

  (french)

  Hello

  I have a poweredge server 2950 with esxi 3.5 (build 143129). There are two

  broadcom netxtreme II plugged into two VLANs different cards. I have

  activated the VLAN in the broadcom bios. the two broadcom are connected

  to two different ports with two VLANS different: 101 and 103. My VM

  Manager is on the Prime Minister vlan (101) on the 1 NIC. the second NIC is

  plugged on the vlan 103 pour VM. But I can't ping.

  anyone has a solution. ?

  Thank you

  Thank you. I am currently not able to check with my VI. But in the meantime, you can read this article on ESX and VLAN.

  IS preferable, but might need to reconfigure the switch. Maybe you transfer the link or document to your networking guy for advice.

• Best practices for Exchange 2003 with VMWare ESXi 3.5 and iSCSI SAN

  Hello guys,.

  Here's the Q? We have 1 physical Exchange 2003, the HOST of 4 and 1 iSCSI SAN with LUN 3, 1 for data, 1 for VMWare and 1 for SQL, if we're going to virtualize it, I don't know where to put data Exchage and newspapers. I do not think that that is a good practice to put together the data but I do not have another SAN. So, what can I do?

  Thank you.

  We have 813 mailbox.

  I agree with cainics, start an average size and go from there.  I know it's a production mail server and you can not exactly 'play' with the settings because this requires time, but if you do the VM too big, you would have nothing left for other virtual machines.

  I would go 2 vCPU and at least 4 GB of RAM, maybe 8GB.  There must be parameters for the Exchange mailbox 813 and X users # to implement your environments in order to get an idea of the amount of RAM that will be... 4GB seems minimal to me, but 8 GB would probably be better like that.

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

• On broadcom BCM57800 10 Gb nic and iscsi

  Hi guys,.

  I have a 5.1 with 1 NIC broadcom NetXtreme II bcm57800 esxi server and would use my storage via iscsi.

  This adapter support iscsi off load but I do not understand if it is mandatory to add "iscsi software adapter" too esxi or not.

  Thanks in advance.

  Hi gianlucab,.

  Only, you would use the iSCSI Software adapter if you need the kernel ESXi itself to perform iSCSI operations. You would use this with Ethernet adapters that do not support iSCSI unloading.

• Broadcom NetXtreme II 5709 quad port NETWORK card issues

  Environment:

  -V4.1 ESXi on:

  -3 x servers Dell R710 (48GB of RAM) with SAS shared storage (No iSCSI) each with:

  -4 x Gigabit Broadcom PowerEdge R710 BCM5709 Ethernet ports on the motherboard (works well)

  -2 x Broadcom NetXtreme II BCM5709 1000Base-T on card 2 ports (works well)

  -4 x Broadcom NetXtreme II BCM5709 1000Base-T on a card 4 ports (problems!)

  Have installed ESXi 4.1 fees to each server.  When you configure the management network, I noticed that:

  -Server ESX1 correctly displays the 10 cards

  -Server ESX2 incorrectly shows 8 network interface cards (2 on the card 4 ports are "missing")

  -ESX3 server incorrectly displays 6 network interface cards (all 4 on the card 4 ports are "missing")

  VMware, I downloaded the latest drivers Broadcom 5709 for ESXi v4.1 and installed via the vSphere CLI (successfully) and restarted.  No difference.

  I exchanged the cards around in the server and 'mistakes' follow the cards.

  2 / 3 of the cards of brand new (I hope!) which have been purchased in an order are so apparently defective.  Maybe bad batch?

  Should I go with trying to replace these cards with the same model of 4-port Broadcom NetXtreme II 5709 cards... or should I try a different provider (for example a 4-port Intel card)?

  Suggestions welcome.

  In fact the network cards should be picked up in the order the PCI ID as described in example http://kb.vmware.com/kb/1002315

  Maybe it's allows you to run a 'Reset configuration data' in the BIOS of the server after connecting the network cards.

  The really strange thing is numbering ESX1, where even on a NETWORK card ports are not in ascending order.

  André

• Broadcom 57711 + ESX/ESXi 4.1 + Jumbo frames

  Having a few problems getting Broadcom 57711 NIC working on ESX/ESXi 4.1 with MTU 9000.

  ESX/ESXi 4.0 U2 I have no problems to do and work MTU 9000 and I can push our strong enough EQL PS6010 SAN get 550 000 kbit/s with e/s meter runs inside 4 x VM.

  I read the documentation and found that an MTU of 1500 is supported only for the NIC in ESX/ESXi 4.1 57711. It has somethig to do with the fact that these cards have hardware iSCSI unloading, there is additional iSCSI adapters that appear under the storage adapters heading 4.1 hosts.

  I everything configured properly with 1:1 binding maps iSCSI network to ports VMK iSCSI with an MTU of 1500. When configured, this is the max that I can get out the SAN is 280 000 kbit/s. If I try the same process using the virtual machine a MTU of 9000 / host appears to stop responding.

  While I understand that it is a limitation of 1500 when using iSCSI NIC hardware I am unable to get the iSCSI Software to work with a MTU of 9000 on ESX/ESXi 4.1. If I try the software iSCSI using a MTU of 9000 of the VM / host appears to stop responding.

  Is also a limitation, or am I missing something.

  Is there anyone else out there has the same problems as me?

  VCP3 & VCP4 32846

  VSP4

  VTSP4

  Looks like a CD to update the Broadcom Driver (1.60.50.v41.2) was recently published in the area of downloads/drivers & tools vsphere.  I have not tried yet, hopefully, it will solve this problem.