Part 2 – How to list vSwitch “MAC Address table” on ESXi host?
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. 🙂
Part 1 – How to list vSwitch “MAC Address table” on ESXi host?
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…
vMotion fails to migrate VMs between ESXi host which have the same configuration
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…
Perennially reservations weird behaviour whilst not configured correctly
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…
vCenter Appliance 6.0 U3 email notifications are not sent when multiple email addresses are defined in an alarm action
Recently I tried to configure email notifications on my lab vCenter Server Appliance (6.0u3), but experience issue: “Diagnostic-Code: SMTP;550 5.7.60 SMTP; Client does not have permissions to send as this sender” I tried to use solution from kb: https://kb.vmware.com/kb/2075153 but apparently, the solution does not work with latest 6.0.x appliance! After some research and digging deeper (header analysis ), it seems that root cause was invalid return path in the email header. To resolve this you need to edit two…
Esxi Net.ReversePathFwdCheckPromisc Advanced setting
During deployment of Cisco proxy appliance, we discovered a problem. According to cisco to resolve this problem “Net.ReversePathFwdCheckPromisc” should be set to “1” on ESX’s. The question is – do you know any negative effects which such change could cause. We believe that there must be a reason why by default this option is set to 0 ? That’s why I decided to figure our what it is used for. After some research I was able to find answer: Setting…
ESXi and Likewise – troubleshooting guide – part 2
In last part of this small series, we discussed theoretical background about components and technology related for adding ESX host to windows AD environment. Now it is time to describe troubleshooting options and some real life problems with solutions. Let’s start from dividing all ESXi/Likewise issues into categories: Domain Join Failures Here are most often reasons that an attempt to join a domain fails: The user name or password of the account used to join the domain is incorrect. The…
ESXi and Likewise – troubleshooting guide – part 1
Last week I had to troubleshoot strange issue related to Active Directory integration with ESXI (6.0 version), this was motivation to prepare small (two articles) series about ESXi / Likewise integration and troubleshooting based on my latest experience. VMware use Powerbroker Identity Services (Formerly known as Likewise) for adding ESX host to windows AD environment. To begin as usual is good to have some theoretical background about related components and technology and we describe it all in this part. Below…
Mystery of the broken VM
Today my colleague (vmware administrator) asked me a small favour – help to perform RCA (root cause analyze) – related to one of production VM that had recently a problem. VM for some reason was migrated (collegue stands that it happened without administrative intervention) to other ESXi host that do not have proper network config for this vm – this caused outage for whole system. I asked about issue time and we went deeper into logs in order to find…