Hi,

I'm seeing MAC flapping errors on my Cisco switch.  An ESXi host is attached with four interfaces.  No LACP or port-channel is configured.  In any case CDP is a per-physical interface protocol (which should be advertised on physical interfaces and NOT bundles, etc.).

The problem is that the host is sending CDP packets from the same virtual MAC down two interfaces (although the other two interfaces are fine).

Here are the four CDP packets coming from ESX to the Cisco switch (note that the MAC flap error only complains about two of the four ports)

Mar  9 05:13:55.329: CDP-PA: Packet received from esx-01.local on interface GigabitEthernet0/6

Mar  9 05:13:55.329: **Entry NOT found in cache**

Mar  9 05:13:55.329: CDP-EV: Packet Received from esx-01.local with capability = 8 and Platform string = VMware ESX on interface GigabitEthernet0/6

Mar  9 05:13:55.329: CDP-EV: Powernet Event request received on interface GigabitEthernet0/6

Mar  9 05:13:55.329: CDP-EV: New Neighbor discovered, notified registered clients on interface GigabitEthernet0/6

Mar  9 05:13:55.329: CDP-PA: Packet received from esx-01.local on interface GigabitEthernet0/4

Mar  9 05:13:55.329: **Entry NOT found in cache**

Mar  9 05:13:55.329: CDP-EV: Packet Received from esx-01.local with capability = 8 and Platform string = VMware ESX on interface GigabitEthernet0/4

Mar  9 05:13:55.329: CDP-EV: Powernet Event request received on interface GigabitEthernet0/4

Mar  9 05:13:55.329: CDP-EV: New Neighbor discovered, notified registered clients on interface GigabitEthernet0/4

Mar  9 05:13:55.329: CDP-PA: Packet received from esx-01.local on interface GigabitEthernet0/3

Mar  9 05:13:55.329: **Entry NOT found in cache**

Mar  9 05:13:55.329: CDP-EV: Packet Received from esx-01.local with capability = 8 and Platform string = VMware ESX on interface GigabitEthernet0/3

Mar  9 05:13:55.329: CDP-EV: Powernet Event request received on interface GigabitEthernet0/3

Mar  9 05:13:55.329: CDP-EV: New Neighbor discovered, notified registered clients on interface GigabitEthernet0/3

Mar  9 05:13:55.337: CDP-PA: Packet received from esx-01.local on interface GigabitEthernet0/2

Mar  9 05:13:55.337: **Entry NOT found in cache**

Mar  9 05:13:55.337: CDP-EV: Packet Received from esx-01.local with capability = 8 and Platform string = VMware ESX on interface GigabitEthernet0/2

Mar  9 05:13:55.337: CDP-EV: Powernet Event request received on interface GigabitEthernet0/2

Mar  9 05:13:55.337: CDP-EV: New Neighbor discovered, notified registered clients on interface GigabitEthernet0/2

Mar  9 16:13:55.363 AEDST: %SW_MATM-4-MACFLAP_NOTIF: Host 0050.565c.13e7 in vlan 1 is flapping between port Gi0/4 and port Gi0/3

Here is a pcap of the two packets on Gi0/3 and Gi0/4.  Note the identical source MAC (00:50:56:5c:13:e7), however the advertised ports are different.

14:43:55.361048 00:50:56:5c:13:e7 (oui Unknown) > 01:00:0c:cc:cc:cc (oui Unknown), 802.3, length 164: LLC, dsap SNAP (0xaa) Individual, ssap SNAP (0xaa) Command, ctrl 0x03: oui Cisco (0x00000c), pid CDP (0x2000), length 156: CDPv2, ttl: 1

80s, checksum: 0x1812 (unverified), length 156

        Device-ID (0x01), value length: 21 bytes: 'esx-01.local'

        Address (0x02), value length: 13 bytes: IPv4 (1) 0.0.0.0

        Port-ID (0x03), value length: 6 bytes: 'vmnic1'

        Capability (0x04), value length: 4 bytes: (0x00000008): L2 Switch

        Version String (0x05), value length: 21 bytes:

          Releasebuild-11675023

        Platform (0x06), value length: 10 bytes: 'VMware ESX'

        VTP Management Domain (0x09), value length: 1 byte: '^@'

        Duplex (0x0b), value length: 1 byte: full

        MTU (0x11), value length: 4 bytes: 9000 bytes

        AVVID untrusted ports CoS (0x13), value length: 1 byte: 0x00

        AVVID trust bitmap (0x12), value length: 1 byte: 0x00

        System Name (0x14), value length: 21 bytes: 'esx-01.local'

14:44:55.360698 00:50:56:5c:13:e7 (oui Unknown) > 01:00:0c:cc:cc:cc (oui Unknown), 802.3, length 164: LLC, dsap SNAP (0xaa) Individual, ssap SNAP (0xaa) Command, ctrl 0x03: oui Cisco (0x00000c), pid CDP (0x2000), length 156: CDPv2, ttl: $

80s, checksum: 0x1811 (unverified), length 156

        Device-ID (0x01), value length: 21 bytes: 'esx-01.local'

        Address (0x02), value length: 13 bytes: IPv4 (1) 0.0.0.0

        Port-ID (0x03), value length: 6 bytes: 'vmnic2'

        Capability (0x04), value length: 4 bytes: (0x00000008): L2 Switch

        Version String (0x05), value length: 21 bytes:

          Releasebuild-11675023

        Platform (0x06), value length: 10 bytes: 'VMware ESX'

        VTP Management Domain (0x09), value length: 1 byte: '^@'

        Duplex (0x0b), value length: 1 byte: full

        MTU (0x11), value length: 4 bytes: 9000 bytes

        AVVID untrusted ports CoS (0x13), value length: 1 byte: 0x00

        AVVID trust bitmap (0x12), value length: 1 byte: 0x00

        System Name (0x14), value length: 21 bytes: 'esx-01.local'

Thoughts?

Thanks,

Scott

I used the esxi-customizer tool, but it gave me an error.The log information is as follows：

[2019/03/14 周四  9:09:02.43] This is ESXi-Customizer v2.7.2 ...

[2019/03/14 周四  9:09:02.44] Called with parameters:

[2019/03/14 周四  9:09:02.44] ... sISO             = "F:\VMware-VMvisor-Installer-6.7.0.update01-10302608.x86_64.iso"

[2019/03/14 周四  9:09:02.44] ... fOEM             = "F:\net55-r8168-8.045a-napi-offline_bundle.zip"

[2019/03/14 周四  9:09:02.44] ... wDir             = "G:"

[2019/03/14 周四  9:09:02.44] ... repackOpt        = "1"

[2019/03/14 周四  9:09:02.44] ... enableUEFI       = "1"

[2019/03/14 周四  9:09:02.46] ... updateCheck      = "0"

[2019/03/14 周四  9:09:02.46] Creating the temp-directory "G:\esxicust.tmp" ...

[2019/03/14 周四  9:09:02.46] Run: mkdir "G:\esxicust.tmp"

[2019/03/14 周四  9:09:02.47] Extracting the source ISO ...

[2019/03/14 周四  9:09:02.47] Run: "F:\ESXi-Customizer-v2.7.2\tools\7zip\7z.exe" x -y -o"G:\esxicust.tmp\iso" "F:\VMware-VMvisor-Installer-6.7.0.update01-10302608.x86_64.iso"

7-Zip 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18

Processing archive: F:\VMware-VMvisor-Installer-6.7.0.update01-10302608.x86_64.iso

Extracting  .DISCINFO

Extracting  ATA_LIBA.V00

Extracting  ATA_PATA.V00

Extracting  ATA_PATA.V01

Extracting  ATA_PATA.V02

Extracting  ATA_PATA.V03

Extracting  ATA_PATA.V04

Extracting  ATA_PATA.V05

Extracting  ATA_PATA.V06

Extracting  ATA_PATA.V07

Extracting  B.B00

Extracting  BLOCK_CC.V00

Extracting  BNXTNET.V00

Extracting  BNXTROCE.V00

Extracting  BOOT.CAT

Extracting  BOOT.CFG

Extracting  BRCMFCOE.V00

Extracting  BTLDR.T00

Extracting  CHARDEVS.B00

Extracting  CHAR_RAN.V00

Extracting  EFI

Extracting  EFI\BOOT

Extracting  EFI\BOOT\BOOT.CFG

Extracting  EFI\BOOT\BOOTIA32.EFI

Extracting  EFI\BOOT\BOOTX64.EFI

Extracting  EFIBOOT.IMG

Extracting  EHCI_EHC.V00

Extracting  ELXISCSI.V00

Extracting  ELXNET.V00

Extracting  ELX_ESX_.V00

Extracting  ESXUPDT.V00

Extracting  ESX_DVFI.V00

Extracting  ESX_UI.V00

Extracting  FEATURES.GZ

Extracting  HID_HID.V00

Extracting  I40EN.V00

Extracting  IAVMD.V00

Extracting  IGBN.V00

Extracting  IMA_QLA4.V00

Extracting  IMGDB.TGZ

Extracting  IMGPAYLD.TGZ

Extracting  IPMI_IPM.V00

Extracting  IPMI_IPM.V01

Extracting  IPMI_IPM.V02

Extracting  ISER.V00

Extracting  ISOLINUX.BIN

Extracting  ISOLINUX.CFG

Extracting  IXGBEN.V00

Extracting  JUMPSTRT.GZ

Extracting  K.B00

Extracting  LPFC.V00

Extracting  LPNIC.V00

Extracting  LSI_MR3.V00

Extracting  LSI_MSGP.V00

Extracting  LSI_MSGP.V01

Extracting  LSI_MSGP.V02

Extracting  LSU_HP_H.V00

Extracting  LSU_INTE.V00

Extracting  LSU_LSI_.V00

Extracting  LSU_LSI_.V01

Extracting  LSU_LSI_.V02

Extracting  LSU_LSI_.V03

Extracting  LSU_SMAR.V00

Extracting  MBOOT.C32

Extracting  MENU.C32

Extracting  MISC_CNI.V00

Extracting  MISC_DRI.V00

Extracting  MTIP32XX.V00

Extracting  NATIVE_M.V00

Extracting  NE1000.V00

Extracting  NENIC.V00

Extracting  NET_BNX2.V00

Extracting  NET_BNX2.V01

Extracting  NET_CDC_.V00

Extracting  NET_CNIC.V00

Extracting  NET_E100.V00

Extracting  NET_E100.V01

Extracting  NET_ENIC.V00

Extracting  NET_FCOE.V00

Extracting  NET_FORC.V00

Extracting  NET_IGB.V00

Extracting  NET_IXGB.V00

Extracting  NET_LIBF.V00

Extracting  NET_MLX4.V00

Extracting  NET_MLX4.V01

Extracting  NET_NX_N.V00

Extracting  NET_TG3.V00

Extracting  NET_USBN.V00

Extracting  NET_VMXN.V00

Extracting  NFNIC.V00

Extracting  NHPSA.V00

Extracting  NMLX4_CO.V00

Extracting  NMLX4_EN.V00

Extracting  NMLX4_RD.V00

Extracting  NMLX5_CO.V00

Extracting  NMLX5_RD.V00

Extracting  NTG3.V00

Extracting  NVME.V00

Extracting  NVMXNET3.V00

Extracting  NVMXNET3.V01

Extracting  OHCI_USB.V00

Extracting  PROCFS.B00

Extracting  PVSCSI.V00

Extracting  QCNIC.V00

Extracting  QEDENTV.V00

Extracting  QFLE3.V00

Extracting  QFLE3F.V00

Extracting  QFLE3I.V00

Extracting  QFLGE.V00

Extracting  QLNATIVE.V00

Extracting  RSTE.V00

Extracting  S.V00

Extracting  SAFEBOOT.C32

Extracting  SATA_AHC.V00

Extracting  SATA_ATA.V00

Extracting  SATA_SAT.V00

Extracting  SATA_SAT.V01

Extracting  SATA_SAT.V02

Extracting  SATA_SAT.V03

Extracting  SATA_SAT.V04

Extracting  SB.V00

Extracting  SCSI_AAC.V00

Extracting  SCSI_ADP.V00

Extracting  SCSI_AIC.V00

Extracting  SCSI_BNX.V00

Extracting  SCSI_BNX.V01

Extracting  SCSI_FNI.V00

Extracting  SCSI_HPS.V00

Extracting  SCSI_IPS.V00

Extracting  SCSI_ISC.V00

Extracting  SCSI_LIB.V00

Extracting  SCSI_MEG.V00

Extracting  SCSI_MEG.V01

Extracting  SCSI_MEG.V02

Extracting  SCSI_MPT.V00

Extracting  SCSI_MPT.V01

Extracting  SCSI_MPT.V02

Extracting  SCSI_QLA.V00

Extracting  SHIM_ISC.V00

Extracting  SHIM_ISC.V01

Extracting  SHIM_LIB.V00

Extracting  SHIM_LIB.V01

Extracting  SHIM_LIB.V02

Extracting  SHIM_LIB.V03

Extracting  SHIM_LIB.V04

Extracting  SHIM_LIB.V05

Extracting  SHIM_VMK.V00

Extracting  SHIM_VMK.V01

Extracting  SHIM_VMK.V02

Extracting  SMARTPQI.V00

Extracting  TOOLS.T00

Extracting  UC_AMD.B00

Extracting  UC_HYGON.B00

Extracting  UC_INTEL.B00

Extracting  UHCI_USB.V00

Extracting  UPGRADE

Extracting  UPGRADE\ESXIMAGE.ZIP

Extracting  UPGRADE\EXTLINUX

Extracting  UPGRADE\ISOINFO

Extracting  UPGRADE\MBR.BIN

Extracting  UPGRADE\MCOPY

Extracting  UPGRADE\METADATA.XML

Extracting  UPGRADE\METADATA.ZIP

Extracting  UPGRADE\PRECHECK.PY

Extracting  UPGRADE\PREP.PY

Extracting  UPGRADE\PROFILE.XML

Extracting  USBCORE_.V00

Extracting  USB_STOR.V00

Extracting  USER.B00

Extracting  USEROPTS.GZ

Extracting  VIM.V00

Extracting  VMKATA.V00

Extracting  VMKFCOE.V00

Extracting  VMKPLEXE.V00

Extracting  VMKUSB.V00

Extracting  VMWARE-ESX-BASE-OSL.TXT

Extracting  VMWARE-ESX-BASE-README

Extracting  VMWARE_E.V00

Extracting  VMW_AHCI.V00

Extracting  VMX.V00

Extracting  VSAN.V00

Extracting  VSANHEAL.V00

Extracting  VSANMGMT.V00

Extracting  WEASELIN.T00

Extracting  XHCI_XHC.V00

Extracting  XORG.V00

Extracting  [BOOT]\Bootable_NoEmulation.img

Everything is Ok

Folders: 3

Files: 184

Size:       329346510

Compressed: 329611264

[2019/03/14 周四  9:09:09.35] Checking media type ...

[2019/03/14 周四  9:09:09.35] --- INFO: This looks like an ESXi 5.x installation media.

[2019/03/14 周四  9:09:09.37] ---       No admin rights needed to customize ESXi 5.x. Continuing ...

[2019/03/14 周四  9:09:09.37] Removing old boot.cat from ISO directory. It will be created by mksiofs ...

[2019/03/14 周四  9:09:09.38] Run: del /f /q "G:\esxicust.tmp\iso\boot.cat"

[2019/03/14 周四  9:09:09.38] Removing [BOOT] directory from ISO directory ...

[2019/03/14 周四  9:09:09.38] Run: rmdir /s /q "G:\esxicust.tmp\iso\[BOOT]"

[2019/03/14 周四  9:09:09.40] Selected customization type is .zip.

[2019/03/14 周四  9:09:09.40] Unpacking the IMGDB.TGZ file ...

[2019/03/14 周四  9:09:09.40] Run: "F:\ESXi-Customizer-v2.7.2\tools\7zip\7z.exe" x -y -o"G:\esxicust.tmp" "G:\esxicust.tmp\iso\IMGDB.TGZ"

7-Zip 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18

Processing archive: G:\esxicust.tmp\iso\IMGDB.TGZ

Extracting  <fdopen>

Everything is Ok

Size:       1792000

Compressed: 227919

[2019/03/14 周四  9:09:09.45] Run: "F:\ESXi-Customizer-v2.7.2\tools\7zip\7z.exe" x -y -o"G:\esxicust.tmp\imgdb" "G:\esxicust.tmp\IMGDB.tar"

7-Zip 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18

Error:

cannot find archive

[2019/03/14 周四  9:09:09.46] !-----------------------------------------------------------------------------------

[2019/03/14 周四  9:09:09.46] !-- FATAL ERROR: Error un-taring IMGDB.tar!

[2019/03/14 周四  9:09:09.48] !-----------------------------------------------------------------------------------

[2019/03/14 周四  9:09:09.48] Run: "F:\ESXi-Customizer-v2.7.2\tools\MsgBox.exe" 266260 "FATAL ERROR:&n   Error un-taring IMGDB.tar!&n&nSee log file 'G:\ESXi-Customizer.log' for details! Do you want to open the log file in notepad now?"

[2019/03/14 周四  9:09:18.60] Cleaning up ...

[2019/03/14 周四  9:09:18.62] Run: rmdir /s /q "G:\esxicust.tmp"

[2019/03/14 周四  9:09:18.70] This is the end.

I have a question to deploy so many type of server for production

This is an automated implementation of installing various server-based hypervisor

I would like to ask you what solution you have and based on the actual organized case.

For example, , Have you designed automation based on Dell rack server or HP rack server and implemented automation until esxi server installation?

I found out the method to deploy it automatically.

1) based on physical server

   when we use Dell server deployment automatically with Openmanager

2) based on virtualization layer

   https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc_50%2FGUID-9A827220-177E-40DE-99A0-E1EB62A49408.html

    it mean that cloud engineer can use this manual to deploy hypervisor automatically.

As I say again,  I try to search the method to configure two layer from physical server and hypervisor automatically.

The method contain two solution like open source and vendor solution.

Thank you.

Have a nice day.!

Basically im trying to make some windows 7 x64 Virtual Machines and seems Amd-V Is failing?

This virtual machine requires AVX2 but AVX is not present. This virtual machine cannot be powered on.

I try to install virtual machines with 7.1 and 15.0.2 and worked witouth any problem. But i want to use 11 Due to im testing some things.

VMware Version:11.1.4 build-3848939

CPU: Amd Ryzen 7 2700

Motherboard: asus prime x470 pro

Host OS:Windows 10 PRO , 64-bit  (Build 17763) 10.0.17763

Is Amd-V (SVM Mode in BIOS) Activated in my motherboard?: Yes

Hardware compatibility : 6.5.7x, it cannot be higher i need to use these specifically.

I am having trouble getting Windows 10 to save Default App Association when using Non-Persistent VDI, I am using UEM 9 and Horizon 7.1.  Any help would be appreciated. 

Good day .

Please can i be assisted in the following log error message:

Logging to storage has failed.  Logs are no longer  being stored locally on this host.

Vmware client

Windows 10 latest version and updates as of Feb 26 2019

Nat works but outside computers cant connect to SCO 5.0.6 Server running on Workstation 15.2 on top of Windows 10.
Dell 7020 optiplex.

This document highlights NSX-T LB capabilities and it's latest NSX-T 2.4 enhancements.

Author :

URL : http:////docs.vmware.com/en/vRealize-Automation/7.4/com.vmware.vra.prepare.use.doc/GUID-530ABF4D-E0EA-4266-BEB2-C507CCCDAA9D.html

Topic Name : Install the Guest Agent on a Linux Reference Machine

Publication Name : Preparing and Using Service Blueprints in vRealize Automation

Product/Version : vRealize Automation/7.4

Question :

Ok, I'm running vRA 7.4. I added a software component (bash script) to a blueprint that creates a RHEL 7 virtual machine. The vRA guest automation agent/software bootstrap agent is installed and running on the RHEL 7 template that is being provisioned. I also prepared the Linux machine by running the script the agent provides. There is not a networking issue because I can reach everything (good ping, ssh, nslookup, etc.) I can't get the deployment to complete, the bash script does not execute. It just hangs up and then finally fails the deployment because the bash script is not run (times out).

Hello,

I created an RDM disk and copied / moved it to another folder.

But when I try to add an existing disk and locate the pointer, it does not show as a physical lun. Shows a common disk (Thick).

If I try to add the existing disk that is still in the VM folder, it shows as physical lun.

What did I do wrong?

Thank you.

We have currently running on version 17.2 and will be upgrading to 18.3 Horizon Cloud Hosted to be done by VMware.

We need to install HAI unified agent 18.2.2 which replaces DaaS agent and Horizon Agent on our RDSH master image.

Do we need to update the ADMX files which is included in the download link for 18.3?

File: Horizon 7.5.0 View GPO Bundle (VMware-Horizon-Extras-Bundle-4.8.0-8519436.zip)

Hi, Is there anyone saw this error message while running the recovery pla ? I am using SRM with vSphere replication and while Test recovery.

- Tired with same network both site

- Tired with Isolated network (auto created)

I am using power cli VMware vSphere 6.7 and i am tring to start VM which is inside a cluster.

If i am entring "Get-VM" command i get the VM`s list properly, But when im tring "Start-VM -VM VM02 -Confirm" i get "Start-VM : 10/2/2018 4:57:04 PM Start-VM                Exception has been thrown by the target of an invocation.

At line:1 char:1

+ Start-VM -VM VM02 -Confirm

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Start-VM], VimException

    + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.StartVM"

Error 550 authentication is required for relay is usually crops up whenever you try to send emails and unable to send it due to the SMTP server issue. An authentication is required that means you have to enter your ID and password in order to send emails, when SMTP server is unable to deliver your send emails to the sender. This is not so hard process, which can’t be performed by a user. You can also eliminate this error 550 and able to send messages again. For this, if you any help, you can go for Microsoft Live Chat support. Here, you can get on time solution in no time.

We can download free Windows 10/7 VM (90 days) from Microsoft here,

https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/

But fails to import into vCenter6.7/ESXi6.7 with ELEMENT ILLEGAL error.

I found the solution that,

Edit the ova file from here

        <vssd:VirtualSystemType>vmx-09</vssd:VirtualSystemType>

To

        <vssd:VirtualSystemType>vmx-10</vssd:VirtualSystemType>

Delete the following two lines,

      <vmw:ExtraConfig ovf:required="false" vmw:key="nvram" vmw:value="IE8 - Win7.nvram"/>

      <vmw:ExtraConfig ovf:required="false" vmw:key="virtualhw.productcompatibility" vmw:value="hosted"/>

Import ova and vmdk files would be fine but don't select mf since the ova file is modified.

Hi all

Having issues powering down / restarting / suspending a VM.

As shown in the screenshot, Whenever I try initiating any of those three functions, I get a error message another task already in progress. I do note that my RAM usage is up to the hilt. I cannot increase RAM as it's disallowing me to power down the VM. I've tried running a VEEAM restore which also failed saying that 'another task is already in progress'.

Any one having this issue? thanks

Can not find Watchlist on Android, Why Watchlist removed from play store?

Hi!

I recently bought a new laptop and installed Workstation Pro 14. Old virtual machines which I created on my previous laptop with Workstation pro 12 are running, but I cant create new ones. The program is throwing error messages as seen below. The error message is thrown instantly after clicking on the create new virtual machine button, so theres a problem in the creation first way.

Since I couldnt solve the problem I installed the demo version for Workstation pro 15. Same problem.

I attached the mentioned logfile. Does anybody know what causes this problem?

The old laptop was running on Windows 7 with Workstation 12. The new one is running on Windows 10 pro with Workstation 14.

Some Hardware infos for understanding:

Fujitsu Lifebook U758

processor:     Intel Core i7-8650U vPro

memory module:     2x 16 GB DDR4, 2.400 MHz, SO DIMM

display:  3.640x2.160 pixel (4k)

Is the problem a common one caused by the new hardware? If workstation pro 15 definitely solves my problems I will buy and install this version.

There is a problem with the upper toolbar as well. Beside the menu button no tool button like the shortcut for creating a new vm is shown. The menuoptions and tools have to be openend and selected via the menu. The toolbar loooks like shown below:

I suppose there is some problem with the screen resolution, so it can not present the tool bar.

Thanks in advance!