Skip to main content

vCenter forgot my ESX is in standby mode. What now ?

I used VirtualCenter (vCenter) to put an ESX in standby mode. I restarted VirtualCenter for Windows patches, and now VirtualCenter says the ESX host is "not responding", and doesn't give me the option to wake it from standby mode. Fortunately, the solution is right there under your fingertips: do manually what VirtualCenter would have done for you:
Log on to another ESX on the same network, get the MAC address(es) of the sleeping ESX host, and run:
# ether-wake -i vswif0 aa:bb:cc:dd:ee:ff
You could optionally repeat this for every interface you know of the sleeping ESX. Remember to use the real MAC addresses of the real NICs, not the virtual MAC addresses of service console ports, vmkernel ports, or virtual machines.
After a couple of minutes, VirtualCenter will notice that the host is responding, and will connect it again. If you wish, you can put it in standby mode again using the VI-Client.

If you don't know the MAC address of the host in standby mode, you would need to look for it in the VC database, but you can also find it in /etc/vmware/esx.conf, if you happen to have a backup (such as a vm-support dump). Look for /net/pnic/child[*]/mac values.


Popular posts from this blog

Volkswagen UHV bluetooth touch adapter & its problems

My Volkswagen car has the "universal cellphone preparation" UHV built-in. This is the main part of a car kit, but requires an additional adapter for connecting to a cellphone. At first, I was using an adapter for my good old Nokia 6310, even after I changed to the Nokia E71. Connecting was easy: pair the phone with the "VW UHV" bluetooth entity, and done. This has the phone connected to the car kit at all times, so even non-call-related functions use the car audio system (e.g. voice recognition).
But progress will have its way, no matter what happens. So in comes the "bluetooth touch adapter". Instead of a phone-specific adapter, this is a small touchscreen device that slots into the UHV dashboard mount. Connecting a phone is very different now:
the Bluetooth Touch Adapter connects to the "VW UHV" device via bluetooth
the phone connects to "Touch Adapter" device, also via bluetoothThe device doesn't allow step 2 if step 1 didn't s…

How to solve "user locked out due to failed logins" in vSphere vMA

In vSphere 6, if the vi-admin account get locked because of too many failed logins, and you don't have the root password of the appliance, you can reset the account(s) using these steps:

reboot the vMAfrom GRUB, "e"dit the entry"a"ppend init=/bin/bash"b"oot# pam_tally2 --user=vi-admin --reset# passwd vi-admin # Optional. Only if you want to change the password for vi-admin.# exitreset the vMAlog in with vi-admin These steps can be repeated for root or any other account that gets locked out.

If you do have root or vi-admin access, "sudo pam_tally2 --user=mylockeduser --reset" would do it, no reboot required.

Multiple VLANs on a Synology NAS

Synology, like other SOHO/SMB NAS vendors, touts VLAN functionality with their current DSM 4.1 software. However, the web interface just lets you specify one VLAN tag to use over each eth interface (or bond interface).
Manual approachIn the busybox environment that you can ssh into as root (after enabling ssh through the webinterface), there's all the tools you need to use multiple VLANs over one link (eth or bond), however:
First you insert the 802.1q module into the Linux kernel:
 /sbin/lsmod | /bin/grep -q 8021q || /sbin/insmod /lib/modules/8021q.koThen you add each VLAN you need to every interface (bond0 in this example)
 /sbin/vconfig add bond0 4And finally you can configure IP addresses on every interface.vlan combination (bond0.4 in this example)
 /sbin/ifconfig bond0.4 broadcast netmask same type of script would work on a QNAP NAS too, by the way. They offer 8021q.ko and vconfig in their commandline environment as well.
Packets from…