VMkernel

Similar Questions

• 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

• VMkernel for VSANs

  Hello

  I have a question about Vsan

  1 can. 1 vcenter cause 2 vsan cluster? Each vsan cluster will have its own separate cluster by cluster (in VMware vCenter).

  2. for clusters VSAN, they will use same physical switch uplink. How can we separate these clusters? Is - this same correct range of IP addresses with the same multicast address? or we have to separate the IP address range and the multicast address?

  I use vSAN 6.2.

  Thank you.

  Hi, to comment further on your second question, if you have multiple clusters VSAN, best practices is to provide these more separate network segments (say, different VLAN). I'm not sure what you mean by "same multicast address"; each VSAN node performs the multicast, so all vmkernels VSAN are multicast addresses.

  For more help with this kind of considerations, please consult the Virtual SAN 6.2 Networking Design Guide.

• 6 host Cluster VSAN - I want to change the IP vmkernel VSAN

  Hello

  as the title says, I have 6 cluster host VSANS 6.2 (with some VMS on the store of data VSAN, off right now). What is the best method to change the addresses IP of VSAN vmkernel, without loss of data...

  Someone did he do such a thing? The last byte will change slightly to the decline in the number... None VLAN / subnet etc. changes... I have just change the VSAN vmkernel and change the last octet...

  See you soon

  Paul.

  I re-IPed hosts and their IP of vmk corresponding VSAN in maintenance mode as you describe. With all that in maintenance mode, you can just go and change it. I don't think that there is no danger of data loss. If you make a mistake and all start, it would detect split partitions network or other network through the assessment of health problems and you would have a data store does not work until you fix the network problems.

• VMkernel on 10G natachasery interface connectivity

  Hi all

  I've got:

  Hardware: HP ProLiant DL380 G7 + HP NC523SFP 10GbE (by QLogic), the firmware is up to date.

  Software: ESXi 6.0 U2 last available ISO custom HP.

  The server has how six physical network interface cards:

  4 * 1G Ethernet connected to vSwitch0 uplinks (management VMkernel vmk0 here, several VLANs in the trunk & port-channel, all goes well)

  Uplinks 2 * 10G Ethernet connected to vSwitch1 (these cards are for NFS and vMotion), be they vmnic4 and vmnic5

  The question that I am running comes on maps of 10 G and vSwitch1 (and Yes, I tried to remove-everything-and-recreate-it-all-from-scratch).

  The vSwitch was supposed to be used for the connection of NFS over 10G to ESXi storage using a VLAN isolated not routed.

  Vmnic4 vmnic5 and 10G uplinks are connected to a Cisco 4500-X VSS stack (ports are in trunk mode), standard MTU of 1500 everywhere, no jumbo frames don't yet.

  So, when I add a port VM group and define a VLAN ID (say 3, or the 10.10.3.0/24 subnet) for the traffic of the virtual machine - VM is accessible via vSwitch1 and Physics 10G NIC, rattling of the virtual interface of the Cisco switch very well.

  But when I add a port group VMkernel wearing the same VLAN ID and add an interface vmk1 - he reached the VM on the same virtual switch very well (which means that connectivity is OK inside a vSwitch), but could not ping/ARP/what whether through physical EPS of 10 G.

  Tried using a stack of TCP/IP by default, but also to create a new - no effect too.

  
  

  For now, I have tried all ways to diagnose and/or fix it, except perhaps for the black magic - removed the second physical NETWORK adapter on vSwitch, deleted everything and re-created vSwitch and port groups/vmkernel from scratch, without result.

  When I try to ping the vmk1 of the physical switch and vice versa ARPs are incomplete as there is no connectivity of L1, but the fact that VM pings anything on / subnet 24 fine makes me believe that the wiring is OK.

  I tried setting Cisco switch ports to switchport access mode and VLAN3 and remove the VLAN tagging on VM and VMkernel port, in the same direction - VM pings without problem and VMkernel groups does not work.

  After a week of reading, checked everything I can think of and trials, to anything not made, I would be very grateful for any ideas on that.

  Thank you very much!

  To the right: re-setup of the ESXi nihilo resolved the automagically, phew.

  Or maybe it was an update of the HP firmware somewhere along the way. Or by using only new ESXi 6.0 customer web and avoid completely the installable old...

• Get the number of VMkernel Ports on a vDS

  I've searched and just can not find the code snippet to read the number of Ports VMkernel on distributed switch.

  Anyone got an excerpt?

  The following PowerCLI command will give you a list of the number of VMKernel ports for all of your distributed switches:

  Get-VDSwitch | Select-Object - property name,

  @{Name = "Number of VMKernel ports"; Expression = {($_ |)} Get-VMHostNetworkAdapter | Where-Object {$_.} {DeviceName as "vmk *"} | Measure - Object). County}}

• Put virtual machines inside the VMkernel port group

  Hello

  Network for administrators of VMware SIAS layout:

  "You can not put VMs within that group of port because it is made especially for a VMkernel port."

  However, I use ESXi 5.5 and is able to put normal interface of VM inside the vmk port group. (I only created 1 vmk port group so all virtual machines in the same group with the vmkernel interface)

  May I know if this is a new feature, or something is wrong?

  Thank you!

  This may be possible with distributed switches not with standard switches.

• How to disable journaling documented in vmkernel.log in ESXi 5.5 u2

  Hello community!

  I'm trying to disable debug logging vmkernel.log but so far nothing helps. My vmkernel.log is watered by something like this:

  [Debug ACPI]  (Integer 2015 - 06-30T 07: 17:08.051Z cpu0:32866) 0 x

  00000000

  00001e00

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.051Z cpu0:32866) [0 x 16] "" H2: 0xD7 command == 0 ".

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.051Z cpu0:32866) [0x0f] ' H2: 0xD7 PETE:

  [Debug ACPI]  (Integer 2015 - 06-30T 07: 17:08.051Z cpu0:32866) 0 x

  00000000

  00000080

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.051Z cpu0:32866) [0x1c] ' H2: 0xD8 notification processor.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.052Z cpu0:32866) [0 x 24] ' H2: 0xD3: bits4 CSR_HA set to 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.052Z cpu0:32866) [0 x 19] ' H2: CSR_HA 0xD4 Bit3-> 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.055Z cpu0:32866) [0 x 28] ' H2: 0xD0 enter Manager SCI for HECI-2.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.055Z cpu0:32866) [0x2d] ' H2: 0xD1 host interrupt status set to 1.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.055Z cpu0:32866) [0 x 24] ' H2: 0xD3: bits4 CSR_HA set to 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.055Z cpu0:32866) [0 x 19] ' H2: CSR_HA 0xD4 Bit3-> 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.350Z cpu0:32866) [0 x 28] ' H2: 0xD0 enter Manager SCI for HECI-2.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.350Z cpu0:32866) [0x2d] ' H2: 0xD1 host interrupt status set to 1.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.350Z cpu0:32866) [0 x 24] ' H2: 0xD3: bits4 CSR_HA set to 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.350Z cpu0:32866) [0 x 19] ' H2: CSR_HA 0xD4 Bit3-> 0.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.350Z cpu0:32866) [0 x 17] ' H2: 0xD6 ME WP! = ME PR'

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.350Z cpu0:32866) [0 x 19] ' H2: 0xD6 Message header:

  [Debug ACPI]  (Integer 2015 - 06-30T 07: 17:08.351Z cpu0:32866) 0 x

  0000000080040011

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.351Z cpu0:32866) [0 x 26] "H2: 0xD6 TState:PState:SeqNo:Command:

  [Debug ACPI]  (Integer 2015 - 06-30T 07: 17:08.351Z cpu0:32866) 0 x

  00000000

  00001f00

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.351Z cpu0:32866) [0 x 16] "" H2: 0xD7 command == 0 ".

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.351Z cpu0:32866) [0x0f] ' H2: 0xD7 PETE:

  [Debug ACPI]  (Integer 2015 - 06-30T 07: 17:08.351Z cpu0:32866) 0 x

  00000000

  00000080

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.351Z cpu0:32866) [0x1c] ' H2: 0xD8 notification processor.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.352Z cpu0:32866) [0 x 24] ' H2: 0xD3: bits4 CSR_HA set to 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.352Z cpu0:32866) [0 x 19] ' H2: CSR_HA 0xD4 Bit3-> 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.353Z cpu0:32866) [0 x 28] ' H2: 0xD0 enter Manager SCI for HECI-2.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.353Z cpu0:32866) [0x2d] ' H2: 0xD1 host interrupt status set to 1.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.353Z cpu0:32866) [0 x 24] ' H2: 0xD3: bits4 CSR_HA set to 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.353Z cpu0:32866) [0 x 19] ' H2: CSR_HA 0xD4 Bit3-> 0.

  What I did:

  1. updated the file config.xml in/etc/vmware/hoistd. Currently, section < Journal > looks like this:

  < Log >

  < Directory >/var/log/vmware/< / book >

  Info < level > < / level >

  < maxFileNum > 8 < / maxFileNum >

  < > 524288 maxFileSize < / maxFileSize >

  pass < name > < / name >

  < outputToConsole > false < / outputToConsole >

  < outputToFiles > false < / outputToFiles >

  < outputToSyslog > true < / outputToSyslog >

  < syslog >

  local4 < Setup > < / installation >

  < ident > go < / ident >

  < logHeaderFile > /var/run/vmware/hostdLogHeader.txt < / logHeaderFile >

  < / syslog >

  < / log >

  For the record, I changed < level > (was verbose)

  2. changes to the advanced settings:

  Verbose for info Config.HostAgent.log.level

  Vpx.Vpxa.config.log.level verbose for info.

  No results even after reboot of the host.

  I missed something?

  This ESXi is Lenovo custom image.

  Hello

  I met exactly same problem with our brand new Lenovo x 3650 M5 machines. Unfortunately, VMware was not able to say where these newspapers come as there is not a hardware problem.

  If you feel comfortable, you can decrease vmkernel loging level by:

  core of the system settings set - setting = acpiDbgLevel - value = 1 esxcli

  Then, you will need to reboot your host.

  I hope it helps.

• VMkernel newspaper filled with fcoe errors

  I'm building a 6 ESXi host. He has a broadcom (now qlogic) of dell 57800 brand. I'm running the latest ESXi and firmware for the card.

  My vmkernel.log is full of these messages every 2 seconds

  (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

  I found this article:

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

  that could explain what's going on but I do not know how to fix it.

  I use not FCoE. I use the iSCSI storage network on the same link 10gig (other 10gig link i NTHE card is not pluged). I checked the bios on the dell server, but cannot find anything to disable just one port.

  It is a bug? Is there somehow circumvents these garbage problem of FCoE filling the newspaper? Looking at another host with the same material (but older firmware and esxi 5.5), I don't see any FCoE adapter listed.

  I just found which looks pretty interesting: Zenfolio | Michael Davis | Broadcom BCM57810 FCoE and ESXi

• explanation of VMkernel ports

  Someone can explain to me why vmkernel ports have ip addresses and what are they?

  I know it's stupid, but if someone could explain me as if I wasa kid of 5 years... would be nice.

  Thank you.

  A nice Article is here to help VMware - Networkinginfo. you will get all the information here.

• subnet VMkernel iSCSI for direct-attached storage

  Hello

  I have two hosts esxi 6.0 that I connect to a shared via iSCSI storage. I followed this document technical http://www.vmware.com/files/pdf/techpaper/vmware-multipathing-configuration-software-iSCSI-port-binding.pdf#sthash.7bztDoAS.dpf to configure interfaces iSCSI on the esxi with binding ports host. No problem.

  I use HP MSA 2040 with a dual controller and I'll connect two hosts directly on the shared storage. As for the hardware, according to the documents on best practices, it is recommended to follow a vertical subneting for ports of controllers. However, I have not found no requirement for iSCSI ports in vmware, all of the examples I found configure each vmkernel port in a different subnet, as I did:

  vSwitch0

  iSCSI1 - vmk2 - 192.168.1.11 (unused vmk3)

  iSCSI2 - vmk3 - 192.168.2.11 (unused vmk2)

  So, my question is vmkernel ports are in different subnets? or could they be in the same subnet with no difference performance wise?

  Any help would be appreciated.

  Thank you!

  in your case, because you are trying to achieve Multipathing to iSCSI Software initiator, the vmkernel ports should be in the same subnet.

• Will be communicating with VTEP and NSX flow controller (for example the NAV VTEP) network vmkernel management?

  Hello

  I have question concerning communication with the controller VTEP and NSX.

  Will be communicating with workflows VTEP and controller within the network vmkernel management NSX?

  Alternatively, it empties the VTEP network? (Network VXLAN?)

  I think it is by the vmkernel management network, as ESXi host with controller NSX need not always have

  VTEP (or Logical switches) segment.

  I thought that it could flow within the segment of NSX controller if it is independent of the normal (communication of host of ESXi and vCenter)

  management vmkernel, but I think that there are restrictions which network of the controller must be in the same segment of layer 2.

  I tried to find some document but nothing of any document clearly states what network port group transmits VTEP and NSX flow controller.

  I'll be very happy if the experts give me answer.

  BR

  As far as I know: you're right - this traffic is via the host management network and a connection routed between controllers it is not currently supported with NSX - v.

• NIC team Active standby failover - how to see which physical adapter is actively used at a specific time by a VM or VMKernel port

  Hello, simple question.

  I have a vSwitch with two portgroup VMKernel. The switch is connected with two network adapters. The failover policy is set at the level of Portgroup. PG1 has active nic1 and nic 2 in standby mode. PG2 nic 1 standby and active NIC 2. I want to know via cli or gui, command which nic is actually used for a portgroup at a specific time. Is this possible?

  Thank you!
  Francesco

  You can see the active uplink for each vNIC in the network view (press 'n') with esxtop (r):

  

• replication ports 6 VMkernel vSphere

  Thanks to Jeff Hunter for his recent updates and documentation on vSphere for replication 6.0.  Read the docs online, I have a few questions on the vSphere newly supported, dedicated replication VMkernel profits.

  Here (vSphere replication 6.0 Documentation Center) and here (vSphere replication 6.0 Documentation Center) are notes on configuring the VMkernel ports dedicated to the RV on a source host and RV traffic on a target host (one for the VR traffic and another for VR NFC traffic, respectively).

  Considering that it is probably a common practice to use VR as the replication engine with SRM with the intention to fail on the original production site, what is the value in the configuration of two ports VMkernel for VR?

  On the protected Site, you configure a VR VMkernel port to send traffic.  He sends the replicated data from VM for device of recovery of the RV Site, who turns and sends that data replicated for recovery Site ESXi hosts VR NFC VMkernel ports.

  To not return, then the recovery Site can (should?) have an additional port of VR VMkernel, which sends the data replicated VM for device of original VR protected site, which in turn sends the data replicated to the ports of VR NFS VMkernel from the original host protected Site ESXi.

  This looks like it may or must be a distinction between the traffic between the sites and traffic of VR NFC within a site since there are two types of traffic for VMkernel (VR and VR NFC) VR.

  What is this distinction that guarantees a dedicated RV NFC VMkernel port? Why not just use VR VMkernel port? Thank you!

  Edit: I consider these types of traffic to be at the same level of importance and safety.  I have no problem to put two VMkernel ports in the same VLAN.  If I did this, it would put two VMkernel ports per host, in the same network segment.  I wonder why I don't want to do that rather than just use a single VMkernel port or multiple VLANs.

  Post edited by: Mike Brown

  I think it boils down essentially to the options. you don't have to do that, but based on the reviews, it has been estimated that US aircraft enough requests from customers to provide a mechanism which not only allows you to control the path allows the replication traffic (incoming and outgoing) (the source host and VR target devices), and routes it takes on the network but also control the card used for the VR NFC traffic on the target sites. As you RV relies on the NFC to push the data down to the storage of data target on the target sites and some desired customers be able to separate this circulation as well.

  So in the case of the NFC, you can if you want things together (optional) upwards so that the traffic is storage hosts (and I mean here the hosts VR has determined have access to data target stores) can be sent on a physical LAN separated if you wanted that... and a lot of people have asked that flexibility. Allows customers to isolate the common VR NFC (and traffic pass VR) of management traffic not VR "regular".

  Once VRM note that a host has a vmknic marked as RV NFC, only this address is reported on the VR server, which means when it comes to this host in the future that we will only use this address for traffic from VR NFC.

  just my 2cents on why we did it.

• datastore idle after you migrate vmkernel

  Hi all
  

  After you migrate a port vmkernel for storage NFS to a switch to distribute to a Standard switch, I am unable to vMotion VMs to the ESXi host were I made the migration. The data store switches to inactive mode and the failure of the operation. Just after the operation fails, it made a datastore has groups and he returns to the active state. If I create a vNIC in a server test and added to the Port NFS group, I am able to use the NFS network without problem. I also noticed that happens when I tried to browse the store of data as well. the vNIC is that all the same configuration in gossip the dSwitch and the encrassante. Any help will be be appreciated.

  Thank you!

  This problem was solved by changing the MTU value of 1500 to 9000 since my vmnic came to 9000.