Larger environments tend to integrate their monitoring and ticketing systems. Some also add automated workflows based on alarms. The problem when setting up these workflows is how do you test the workflow is triggered based on specific alarms?
With thanks to William Lam for the tips, it’s possible to trigger specific events that make up alarms. It’s not a simple task (for someone who’s not a developer), but you can do some trial and error to work out how to trigger each event.
Pop Quiz Q: What’s the maximum number of disks per SCSI Controller?
A: It depends.. On your VCP exam, you would have said 15. Correct.
Although if you want to clone or snapshot and quiesce a VM, the maximum is 7 disks per SCSI controller.
Each SCSI Controller can control 15 disks and the quiesced snapshots in Windows 2008 require one available slot per existing disk.
If you have more than 7 disks, the clone / quiesce part will fail, and you’ll have the following errors in vCenter and the VM’s vmware.
Lets face it, there’s lots of things the web client sucks at. Using a console window in the browser is one of them.
This bar at the top of the console window just takes up space. How about a useful hint, tell me how to get rid of this to make more use of the screen.
Thankfully, on October 21st, 2014, VMware released the VM Remote Console (VMRC).
The storage views tab in the vSphere client disappeared, and vCenter System Services displayed some of the following errors: unable to retrieve health data from https://localhost:443/vsm/health.xmlunable to retrieve health data from https://localhost:443/eam/eamService-web/health.xmlunable to retrieve health data from https://localhost:443/SMS/health.xml VMware KB article 2016177 (vCenter Server Health status reports the error: Error retrieving health from url (2016177)) had the fix. This issue & kb is only for vCenter 5.
It’s amazing how much is going on when you dig through logs. On this occasion I was looking at “tasks & events” of a host and noticed a lot of network errors.
Alarm ‘Network uplink redundancy lost’ on triggered an action
The error was occurring every 5 minutes. This was made visual with the use of Log Insight. My new favourite tool.
I couldn’t find anything wrong with this particular ESXi host, vSwitch or uplink.
By accident while in Cluster Settings / Datastore Heartbeating, I noticed a datastore wasn’t available of one of the hosts.
Trying to mount it from the vSphere client failed with a popup:
Call “HostStorageSystem.ResolveMultipleUnresolvedVmfsVolumes” for object “storageSystem-326” on vCenter Server “vcenter” failed.
The command to force mount a snapshot that is persistent has changed from ESX(i)4.x to ESXi5.0.
The details are at http://kb.vmware.com/kb/1011387.
Use SSH or ESXi Shell and run: