<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>MKguy Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>MKguy Tracker</description>
    <pubDate>Sun, 12 Nov 2023 01:15:49 GMT</pubDate>
    <dc:date>2023-11-12T01:15:49Z</dc:date>
    <item>
      <title>Re: Using HA, how to get VM to go back to original host?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Using-HA-how-to-get-VM-to-go-back-to-original-host/m-p/940617#M81298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Usually people use DRS and VM-to-Host affinity rules to migrate the VM back to a preferred host. You need DRS which is only included in enterprise plus licenses. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See the DRS documentation:&lt;/P&gt;&lt;P&gt;&lt;A href="https://pubs.vmware.com/vsphere-55/topic/com.vmware.vsphere.resmgmt.doc/GUID-FF28F29C-8B67-4EFF-A2EF-63B3537E6934.html" title="https://pubs.vmware.com/vsphere-55/topic/com.vmware.vsphere.resmgmt.doc/GUID-FF28F29C-8B67-4EFF-A2EF-63B3537E6934.html"&gt;Using DRS Affinity Rules&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you don't have enterprise plus licenses for DRS then you can script something with basic PowerCLI. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Nov 2016 12:11:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Using-HA-how-to-get-VM-to-go-back-to-original-host/m-p/940617#M81298</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-11-01T12:11:01Z</dc:date>
    </item>
    <item>
      <title>Re: ESX host to vCenter network traffic</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESX-host-to-vCenter-network-traffic/m-p/2731850#M269411</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How much bandwidth are we talking about exactly here? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There shouldn't be too much traffic between vCenter and ESXi hosts, it's mostly management traffic and ESXi sending periodic performance data of host and VM objects to vCenter. Depending on how many VMs run on that host and what your vCenter statistics collection level is, the amount of performance data being sent data can vary a lot:&lt;/P&gt;&lt;P&gt;Especially statistics level 3 and 4 will generate a lot of data and also bloat your vCenter database: &lt;A href="https://pubs.vmware.com/vsphere-55/topic/com.vmware.vsphere.vcenterhost.doc/GUID-25800DE4-68E5-41CC-82D9-8811E27924BC.html" title="https://pubs.vmware.com/vsphere-55/topic/com.vmware.vsphere.vcenterhost.doc/GUID-25800DE4-68E5-41CC-82D9-8811E27924BC.html"&gt;Data Collection Levels&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have VUM on vCenter as well then pushing patches can take up a lot of bandwidth, but I don't think you're doing that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Oct 2016 13:06:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESX-host-to-vCenter-network-traffic/m-p/2731850#M269411</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-28T13:06:10Z</dc:date>
    </item>
    <item>
      <title>Re: NIC Speed Issue of VMNIC7 - Cable is Cat6</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/NIC-Speed-Issue-of-VMNIC7-Cable-is-Cat6/m-p/938995#M80998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm pretty sure the cable type is not the problem here. It might be a faulty cable (unlikely) but otherwise it should work just as well as cat5e or cat7.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the physical switch port configuration where your vmnic7 is attached to. Make sure both ends are configured for auto-negotiation of speed AND duplex. A mismatch will typically cause a fallback to a lower speed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can confirm this pretty quickly if you just swap the cables on the host-end between vmnic7 and another NIC that is running at 1000/full. If the other NIC gets only get 100 now then the switch port probably has misconfigured speed/duplex settings. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Oct 2016 20:25:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/NIC-Speed-Issue-of-VMNIC7-Cable-is-Cat6/m-p/938995#M80998</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-27T20:25:57Z</dc:date>
    </item>
    <item>
      <title>Re: SMTP settings</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SMTP-settings/m-p/1805142#M176321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately vCenter supports neither SMTP authentication nor SSL/STARTTLS at this point. This is confirmed by VMware in the following KB article:&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2063147" title="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2063147"&gt;Support for SMTP authentication and STARTTLS in the vCenter Server and vCenter Server Appliance 5.x and 6.0 (2063147) | …&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a workaround you could setup a simple SMTP forwarding server that takes the unauthenticated and unencrypted mails from vCenter and forwards them with authentication and encryption to you production mail server. If you run vCenter on Windows you could just install the builtin Windows SMTP service. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Oct 2016 10:08:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SMTP-settings/m-p/1805142#M176321</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-25T10:08:38Z</dc:date>
    </item>
    <item>
      <title>Re: VMDK disk as Windows Cluster</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VMDK-disk-as-Windows-Cluster/m-p/936152#M11014</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, when running clusters across hosts with RDMs you have to use an additional SCSI controller for the cluster disks and set its SCSI bus sharing mode to physical.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The detailed steps are explained in the MSCS guide starting from page 16 on the "Cluster Virtual Machines Across Physical Hosts" chapter and in the checklist on page 27:&lt;/P&gt;&lt;P&gt;&lt;A href="http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-setup-mscs.pdf" title="http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-setup-mscs.pdf"&gt;http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-setup-mscs.pdf&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Oct 2016 22:36:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VMDK-disk-as-Windows-Cluster/m-p/936152#M11014</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-20T22:36:14Z</dc:date>
    </item>
    <item>
      <title>Re: VMDK disk as Windows Cluster</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VMDK-disk-as-Windows-Cluster/m-p/936149#M11011</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, RDM implies you use the host-side passthrough of a physical block storage device presented to the ESXi host as opposed to in-guest iSCSI, which is transparent to the host.&lt;/P&gt;&lt;P&gt;Both types support the cluster-across-boxes configuration.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Oct 2016 13:48:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VMDK-disk-as-Windows-Cluster/m-p/936149#M11011</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-19T13:48:04Z</dc:date>
    </item>
    <item>
      <title>Re: VMDK disk as Windows Cluster</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VMDK-disk-as-Windows-Cluster/m-p/936147#M11009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you can build Windows Failover Clusters with shared VMDK disks sitting on normal VMFS volumes. Shared VMDKs on NFS however are not supported.&lt;/P&gt;&lt;P&gt;The caveat is that the shared VMDK on VMFS option is only formally supported for "Cluster-in-a-box" configurations where all VMs must reside on the same ESXi host.&lt;/P&gt;&lt;P&gt;This is probably not what you want for a clustered service where high availability is key. For "Cluster-acorss-boxes" with shared disks you have to use RDMs or in-guest ISCSI/SMB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See these documents for more details:&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1037959" title="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1037959"&gt;Microsoft Clustering on VMware vSphere: Guidelines for supported configurations (1037959) | VMware KB&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;docTypeID=DT_KB_1_1&amp;amp;externalId=1004617" title="https://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;docTypeID=DT_KB_1_1&amp;amp;externalId=1004617"&gt;Microsoft Cluster Service (MSCS) support on ESXi/ESX (1004617) | VMware KB&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-setup-mscs.pdf" title="http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-setup-mscs.pdf"&gt;http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-setup-mscs.pdf&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Oct 2016 12:09:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VMDK-disk-as-Windows-Cluster/m-p/936147#M11009</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-19T12:09:02Z</dc:date>
    </item>
    <item>
      <title>Re: The VIBs was Skipped when upgrade scsi_megaraid_sas from 6.505 to 6.506</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/The-VIBs-was-Skipped-when-upgrade-scsi-megaraid-sas-from-6-505/m-p/1399357#M133737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First off, you should use the &lt;STRONG&gt;update&lt;/STRONG&gt; instead of &lt;STRONG&gt;install&lt;/STRONG&gt; command when updating existing VIBs, though this should be irrelevant for your issue just as a general recommendation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at just the build number it seems to be identical, both have 472560.&lt;/P&gt;&lt;P&gt;Here's a newer version of the driver version 6.610.15.00-5.5-3342447:&lt;/P&gt;&lt;P&gt;&lt;A href="https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI55-LSI-SCSI-MEGARAID-SAS-66101500-1OEM&amp;amp;productId=353" title="https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI55-LSI-SCSI-MEGARAID-SAS-66101500-1OEM&amp;amp;productId=353"&gt;https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI55-LSI-SCSI-MEGARAID-SAS-66101500-1OEM&amp;amp;productId=353&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Download the offline package instead of the VIB file and run the following commands and post the output here:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;# esxcli storage core adapter list&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;# esxcli software sources vib list -d /tmp/megaraid_sas-6.610.15.00-5.5-offline_bundle-3342447.zip&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;# esxcli software sources vib get -d &lt;SPAN style="font-size: 13.3333px;"&gt;/tmp/megaraid_sas-6.610.15.00-5.5-offline_bundle-3342447.zip&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will tell you a lot of information from the metadata contained in the offline bundle. It will also tell you whether this is considered an upgrade, a downgrade or if the same version is already installed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To actually upgrade then run:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px; font-family: 'courier new', courier;"&gt;# esxcli software vib update -d /tmp/megaraid_sas-6.610.15.00-5.5-offline_bundle-3342447.zip&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Oct 2016 10:04:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/The-VIBs-was-Skipped-when-upgrade-scsi-megaraid-sas-from-6-505/m-p/1399357#M133737</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-18T10:04:30Z</dc:date>
    </item>
    <item>
      <title>Re: Block ssh and ICMP for VMs on VDS</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Block-ssh-and-ICMP-for-VMs-on-VDS/m-p/1398574#M15568</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, rules defined on individual dvports only apply to that dvport and not to the entire port group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just be aware that with filtering both Ingress/Egress, your VM will not be able to establish outboud SSH connections either. If you just want to filter SSH connections TO and not FROM the port you need to set the rule to Egress only as Egress/Ingress traffic is always seen from the VDS point of view.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2016 19:54:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Block-ssh-and-ICMP-for-VMs-on-VDS/m-p/1398574#M15568</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-17T19:54:29Z</dc:date>
    </item>
    <item>
      <title>Re: Question regarding NPIV</title>
      <link>https://communities.vmware.com/t5/vSphere-Storage-Discussions/Question-regarding-NPIV/m-p/2730383#M24130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is a common misunderstanding with NPIV:&lt;/P&gt;&lt;P&gt;NPIV does NOT present a virtual FC HBA to your VMs. Your VM will only see an ordinary disk on an ordinary SCSI controller you selected. It's a logical abstraction allowing you to map virtual WWNs to VMs, but this abstraction is done on the host-side transparently for VMs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please see these similar threads:&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/455544"&gt;NPIV question&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/534181"&gt;Presenting Fiber HBA's to VM under ESXi 6&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2016 10:16:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Storage-Discussions/Question-regarding-NPIV/m-p/2730383#M24130</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-17T10:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: Block ssh and ICMP for VMs on VDS</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Block-ssh-and-ICMP-for-VMs-on-VDS/m-p/1398572#M15566</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have to select the appropriate layer 4 transport protocol, which is TCP in this case. Then you can enter the layer 4 destination port to match, which is port 22 for SSH:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="dzfd.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/68518i051E67D4788F3244/image-size/large?v=v2&amp;amp;px=999" role="button" title="dzfd.png" alt="dzfd.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2016 10:02:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Block-ssh-and-ICMP-for-VMs-on-VDS/m-p/1398572#M15566</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-17T10:02:42Z</dc:date>
    </item>
    <item>
      <title>Re: Block ssh and ICMP for VMs on VDS</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Block-ssh-and-ICMP-for-VMs-on-VDS/m-p/1398568#M15562</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you're on 5.5 or later you can use the traffic filtering feature of the VDS, which allows you to define basic ACLs based on Layer 2 and 3 Source/Destination as well as layer 4 ports. Note that you &lt;STRONG&gt;need to use the Web Client&lt;/STRONG&gt; to access these settings in the VDS.&lt;/P&gt;&lt;P&gt;Refer to the documentation for more information on how to enable traffic filtering:&lt;/P&gt;&lt;P&gt;&lt;A href="https://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.networking.doc/GUID-DC14D8EE-110B-4321-8BF6-51C259971CF1.html#GUID-DC14D8EE-110B-4321-8BF6-51C259971CF1" title="https://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.networking.doc/GUID-DC14D8EE-110B-4321-8BF6-51C259971CF1.html#GUID-DC14D8EE-110B-4321-8BF6-51C259971CF1"&gt;Filter Traffic on a Distributed Port Group or Uplink Port Group&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would prefer implementing a proper firewall though. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Oct 2016 18:51:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Block-ssh-and-ICMP-for-VMs-on-VDS/m-p/1398568#M15562</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-14T18:51:41Z</dc:date>
    </item>
    <item>
      <title>Re: What is a express patch ?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/What-is-a-express-patch/m-p/463806#M38522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with you that the ESXi patch terminology and versioning are very confusing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you need to be aware of is that ESXi patches are cumulative - they always update the entire esx-base VIB package. This means Patch 10 includes not only the fixes it was developed for, but also all fixes from patch 1-9. This includes any earlier "express" patches. &lt;SPAN style="font-size: 13.3333px;"&gt;There is no need to apply earlier esx-base patches prior to updating to the latest package because all fixes are included in the full cumulative package anyways. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would just get the latest Cisco offline bundle which includes other packages like drivers and update to this version:&lt;/P&gt;&lt;P&gt;&lt;A href="https://my.vmware.com/web/vmware/details?downloadGroup=OEM-ESXI55U3B-CISCO&amp;amp;productId=353" title="https://my.vmware.com/web/vmware/details?downloadGroup=OEM-ESXI55U3B-CISCO&amp;amp;productId=353"&gt;https://my.vmware.com/web/vmware/details?downloadGroup=OEM-ESXI55U3B-CISCO&amp;amp;productId=353&lt;/A&gt;&lt;/P&gt;&lt;P&gt;And then update to the latest ESXi patches. You can apply any normal VMware ESXi patches on top of specific ISO installations because 3rd party vendors like Cisco, HP, Dell etc do not modify any actual ESXi code. They just add management extensions and update drivers to specificially support their hardware. Anyone can create identical ISOs by grabbing all the individual packages from VMware and the vendors and combine them together in one ISO/offline bundle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ESXi build number (vmware -vl) corresponds to the esx-base VIB version (esxcli software vib list | grep base). You can check which current patch level you have by matching the build number against this list:&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;docTypeID=DT_KB_1_1&amp;amp;externalId=2143832" title="https://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;docTypeID=DT_KB_1_1&amp;amp;externalId=2143832"&gt;Build numbers and versions of VMware ESXi/ESX (2143832) | VMware KB&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Oct 2016 17:15:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/What-is-a-express-patch/m-p/463806#M38522</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-13T17:15:25Z</dc:date>
    </item>
    <item>
      <title>Re: ESXCLI shows Receive Packets Dropped on vmk0. Is this normal?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXCLI-shows-Receive-Packets-Dropped-on-vmk0-Is-this-normal/m-p/1801550#M175728</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try this recently released patch which fixes a false drop reporting issue. While it mentions performance charts, it might help with your issue as well: &lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/kb/2145667" title="https://kb.vmware.com/kb/2145667"&gt;VMware ESXi 6.0, Patch ESXi-6.0.0-20160804001-standard (2145667) | VMware KB&lt;/A&gt;‌&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A newer ixgbe driver version 4.4.1 is available as well:&lt;/P&gt;&lt;P&gt;&lt;A href="https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI60-INTEL-IXGBE-441&amp;amp;productId=491" title="https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI60-INTEL-IXGBE-441&amp;amp;productId=491"&gt;https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI60-INTEL-IXGBE-441&amp;amp;productId=491&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You should check for firmware updates while you're at it too. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doing some math with the port stat numbers shows you have 347,884,869 (Unicast) + 1,214,237 (Broadcasts) = 349,099,106 RX packets total&lt;/P&gt;&lt;P&gt;Meanwhile you have 430,499 dropped RX packets, which equals a drop rate of 0.12%.&lt;/P&gt;&lt;P&gt;My bet is still rather on a reporting issue or filtering of irrelevant broadcast/multicast traffic, but even if it's real, then this should't cause noticeable issues, especially not on VMs which are separate from a vmk interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2016 18:38:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXCLI-shows-Receive-Packets-Dropped-on-vmk0-Is-this-normal/m-p/1801550#M175728</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-12T18:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: ESXCLI shows Receive Packets Dropped on vmk0. Is this normal?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXCLI-shows-Receive-Packets-Dropped-on-vmk0-Is-this-normal/m-p/1801548#M175726</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;Where are these drops reported? These may be false positives:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2052917" style="font-family: proxima-nova, Arial, sans-serif; font-size: 14px;" title="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2052917"&gt;https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2052917&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;Do you see any DRPRX in the esxtop network view?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;What ESXi version, your physical NIC type, firmware and drivers? Please p&lt;/SPAN&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;rovide the output of the following commands on the ESXi shell to give us more information:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;# vmware -vl&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #666666; font-family: 'courier new', courier; font-size: 14px;"&gt;# esxcli network nic list&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;# &lt;/SPAN&gt;&lt;SPAN style="color: #666666; font-size: 14px; font-family: 'courier new', courier;"&gt;esxcli network nic get -n vmnicX&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;Check the virtual port packet counters of your vmk0 in vsish as described here and post the output as well:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;A href="https://www.reddit.com/r/vmware/comments/3l306b/esxi_6_and_receive_packets_dropped_counter/" title="https://www.reddit.com/r/vmware/comments/3l306b/esxi_6_and_receive_packets_dropped_counter/"&gt;https://www.reddit.com/r/vmware/comments/3l306b/esxi_6_and_receive_packets_dropped_counter/&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Even if there were drops on your vmk0, this should technically have no impact on the separated VM network traffic.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2016 17:23:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXCLI-shows-Receive-Packets-Dropped-on-vmk0-Is-this-normal/m-p/1801548#M175726</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-12T17:23:20Z</dc:date>
    </item>
    <item>
      <title>Re: The most basic VSAN question</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/The-most-basic-VSAN-question/m-p/2276640#M9596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;do I have to RAID my physical drives before I can use them for vsan?&lt;/SPAN&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;No, it's actually more recommended to use JBOD/passthrough mode on the storage controller and only configure RAID0 if you have to. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;1x ssd for ESXi (on host)&lt;/SPAN&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;Running the ESXi system from a SSD is a real waste of money and resources. A USB SD-card is enough as a boot drive for an ESXi host, as it runs from a RAMDISK after booting anyways. &lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;According to the HCL you need the &lt;STRONG style="font-size: 14px; font-family: proxima-nova, Arial, 'Meiryo UI'; color: #666666;"&gt;aacraid &lt;/STRONG&gt;driver for your &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;71605Q controller. What you linked and described is for management/monitoring CIM provides and not the actual drivers.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-size: 14px; font-family: proxima-nova, Arial, sans-serif;"&gt;Try installing this recent aacraid-6.0.6.2.1.50667 driver:&lt;/SPAN&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;A href="https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI60-PMC-AACRAID-62150667&amp;amp;productId=491" title="https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI60-PMC-AACRAID-62150667&amp;amp;productId=491"&gt;https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI60-PMC-AACRAID-62150667&amp;amp;productId=491&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;After installing you can confirm the version with&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;STRONG&gt;# esxcli software vib list | grep aacraid&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;If that doesn't make the drives work in JBOD/passthrough mode then you may have to use a RAID0 on top or switch to a different controller. &lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2016 16:09:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/The-most-basic-VSAN-question/m-p/2276640#M9596</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-12T16:09:36Z</dc:date>
    </item>
    <item>
      <title>Re: How do I log what hardware setting were changed on VM from what to what (vCPU, RAM, harddisks a.o.)?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/How-do-I-log-what-hardware-setting-were-changed-on-VM-from-what/m-p/1320467#M121269</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately the data from vCenter tasks and events is very generic and hard to make sense of in detail or for audit purposes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At VMworld they demoed a tech preview for the next major release with logging enhancements that are supposed to tackle these shortcomings:&lt;/P&gt;&lt;P&gt;&lt;A href="http://vmware.mediasite.com/mediasite/Play/51745b030dc24ca5944c40487a5ce5571d?catalog=dbf1ec28-255%0A7-4dd3-a381-e5fe4ceabc40" title="http://vmware.mediasite.com/mediasite/Play/51745b030dc24ca5944c40487a5ce5571d?catalog=dbf1ec28-255%0A7-4dd3-a381-e5fe4ceabc40"&gt;INF8845 - vSphere Logs Grow Up! Tech Preview of Actionable Logging with vRealize Log Insight&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Oct 2016 09:09:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/How-do-I-log-what-hardware-setting-were-changed-on-VM-from-what/m-p/1320467#M121269</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-10-05T09:09:50Z</dc:date>
    </item>
    <item>
      <title>Re: vmware encryption</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmware-encryption/m-p/459912#M38104</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;vSphere 6 currently does not offer any form of storage or VM-level encryption features. This might change with a future release (try to get in the beta program), but at the moment you only have two options:&lt;/P&gt;&lt;P&gt;1. Encryption at the physical array/disk level&lt;/P&gt;&lt;P&gt;2. Encryption inside the Guest OS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2016 13:38:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmware-encryption/m-p/459912#M38104</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-09-29T13:38:43Z</dc:date>
    </item>
    <item>
      <title>Re: Command line tool for datastore performance test in ESXi 6</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Command-line-tool-for-datastore-performance-test-in-ESXi-6/m-p/1777194#M171672</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As you noted there is no such thing and it's not easy to port an existing one over to ESXi, since it's Linux.&lt;/P&gt;&lt;P&gt;But even if there was, don't run benchmarks inside the limited ESXi base OS. You would probably get some very wonky numbers.&lt;/P&gt;&lt;P&gt;As a type-1 Hypervisor, the ESXi userspace shell based on a busybox environment is just a limited interface for management purposes separate from the actual vmkernel. It's limited in terms of resources and IO scheduling. &lt;/P&gt;&lt;P&gt;I know this might seem counter-intuitive at first, but benchmarking from a VM will actually allow you to make use of the full host's capabilities, since that IO really runs in vmkernel space from the host-perspective.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you still really insist you want to test your hardware from a baremetal point of view, then boot the server into a live Linux of your choice and test there.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2016 12:57:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Command-line-tool-for-datastore-performance-test-in-ESXi-6/m-p/1777194#M171672</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-09-29T12:57:09Z</dc:date>
    </item>
    <item>
      <title>Re: cisco discovery protocol</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/cisco-discovery-protocol/m-p/1386276#M6522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree that using a VM with Wireshark or tcpdump would be far better, but unfortunately this probably won't work in this case, even with the catch-all 4095 VLAN and promiscuous mode. &lt;/P&gt;&lt;P&gt;Just like its LLDP counterpart, CDP is link-layer protocol using a special multicast destination MAC - frames will not be forwarded between directly attached links, i.e. they will be terminated at the physical NIC. This is the reason why you need to use the pktcap-uw tool instead of tcpdump-uw (which only operates on vmkernel NICs) on the shell. &lt;/P&gt;&lt;P&gt;If the CDP multicast frames were forwarded like normal frames on the network, you would see information about every switch in the same layer 2 domain on every port at the same time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Sep 2016 21:39:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/cisco-discovery-protocol/m-p/1386276#M6522</guid>
      <dc:creator>MKguy</dc:creator>
      <dc:date>2016-09-08T21:39:55Z</dc:date>
    </item>
  </channel>
</rss>

