Archive for category vmware
While attemtping to upgrade from ESXi 6.0 to 6.5, I received the following message from Upgrade Manager:
The upgrade contains the following set of conflicting VIBs: VMware_bootbank_ehci-ehci-hcd_1.0-4vmw.600.3.69.5572656 Remove the conflicting VIBs or use Image Builder to create a custom upgrade ISO image that contains the newer versions of the conflicting VIBs, and try to upgrade again.
After researching this message and not finding an answer that could fix it, I called Vmware support and this is what they suggested.
My server hardware: DELL PowerEdge R330
- Support asked me to download 6.5 upgrade, the zip file though. ESXi 6.5 zip file for DELL PowerEdge R330 can be found here. Click on the Vmware ESXi 6.5 U2 section and then click on the ‘Other formats’ link do download the .zip file.
- Next, upload this file to the host you’re trying to upgrade.
- Log on to the host as root and type the following command
- esxcli software vib install -d “/vmfs/volumes/Datastore/DirectoryName/PatchName.zip”
- Reboot your host
The actual Vmware KB can be found here.
The project was to install MS Advanced Thread Analytic Gateway in a virtual machine, in Vmware, to monitor a physical domain controller.
- Domain controller (physical) – DCServer1
- DELL switch – switch1
- ESXi host – host1
- MS ATA Gateway – atagw1
Setup Port Mirroring at Physical Switch Level
DC server DCserver1 and ESXi host1 are physically connected to switch1. DCserver1 connects on port 40 and host1 connects on port 44 of the switch.
We’re going to configure port mirroring on switch1 as source being port 40 and destination port 44 and we’re going to use use both directions in our config. You can use the following link to configure port mirroring on DELL switches.
Configure Vmware for Port Mirroring
As mentioned before, host1 connects to switch1, and we’re going to use this connection (vmnic2) and create a new standard switch (that was my setup). So, at point, vmnic2 connects to port 44 on switch1.
Once your new standard switch is created (vSwitch2), then we’ll create a new port group (ATA-Capture). While creating port group ATA-Capture, make sure to enable Promiscuous Mode and set VLAN ID to All (4095) – this part crucial!
Configure Microsoft ATA Gateway VM
Your MS ATA Gateway will need to have two NICs. One NIC will be used for day to day work and the second NIC for capture. To make thing easier, rename the NIC to something like ‘Capture‘. Next, make sure that your Capture NIC belongs to the ATA-Capture port group.
At this point you should be able to install MS ATA Gateway software.
Using VMware PowerCLI, PowerShell, there’s a nifty way to get a list of all VMDKs associated with a virtual machine(s).
Here’s the command:
For this sample, I chose to output the following fields: