The other way to list MAC addresses of open ports on vSwitches on the ESXi host is based on net-stats tool. Use this one-liner. for VSWITCH in $(vsish -e ls /net/portsets/ | cut -c 1-8); do net-stats -S $VSWITCH | grep \{\”name | sed ‘s/[{,”]//g’ | awk ‘{$9=$10=$11=$12=””; print $0}’; done This is not a final word. 🙂
Sometimes You need to list MAC addresses loged on host’s vSwitches to eliminate VM’s MAC address duplicates. Create a shell script: vi mac_address_list.sh Copy and past the code listed below: #!/bin/sh #vmrale for VSWITCH in `vsish -e ls /net/portsets/ | cut -c 1-8` do echo $VSWITCH for PORT in `vsish -e ls /net/portsets/$VSWITCH/ports | cut -c 1-8` do CLIENT_NAME=`vsish -e get /net/portsets/$VSWITCH/ports/$PORT/status | grep clientName | uniq` ADDRESS=`vsish -e get /net/portsets/$VSWITCH/ports/$PORT/status | grep unicastAdd | uniq` echo -e “\t$PORT\t$CLIENT_NAME\t$ADDRESS” done…
As a rule vMotion requires the same family of CPU among involved servers which ensure the same feature set to be presented in order to succeed. This is obvious statement, if you have for example Intel Xeon V3 and v4 CPU generations in your cluster you need EVC in order to make it work. But recently I have came across and issue that vMotion were failing to migrate VMs between hosts with identical configuration. That were Dells R730 with V3…
Whilst using RDM disks in your environment you might notice long (even extremely long) boot time of your ESXi hosts. That’s because ESXi host uses a different technique to determine if Raw Device Mapped (RDM) LUNs are used for MSCS cluster devices, by introducing a configuration flag to mark each device as perennially reserved that is participating in an MSCS cluster. During the start of an ESXi host, the storage mid-layer attempts to discover all devices presented to an ESXi host…
Going through our list of articles about new features in vSphere 6.5 the last one is vSphere Update Manager for vCenter Server Appliance. Since vSphere 6.5 it’s fully embedded and integrated with vCenter Server Appliance with no Windows dependencies. It means that vCenter Server Appliance delivers now Update Manager as an optional service similar to Auto Deploy, etc. Since vSphere 6.5 there is no longer possible to connect Update Manager instance that is installed on a Windows Server machine with vCenter Appliance….