|Spanning Tree Protocol (STP)||✕||✕|
|802.1q (VLAN) support||✓||✓|
|NIC Teaming/Load Balancing||✓ (No LACP)||✓|
|Cisco Discovery Protocol (CDP)||Receive Only||✓|
|Traffic Shaping||Outbound Only||✓|
|Private VLAN (PVLAN)||✕||✓|
|SPAN (dvMirror) port||✕||✓|
|Link Layer Discovery Protocol (LLDP)||✕||✓|
When taking a snapshot you recieve the below errors:
The Guest OS has reported an error during quiesing: The error code was: 5 The error message was: ‘VssSyncStart’ operation failed. Operation aborted
The Guest OS has reported an error during quiesing: The error code was: 3 The error message was: Error Quiesce operation aborted
The Guest OS has reported an error during quiesing: The error code was: 3 The error message was: Error when notifying the sync provider Resolution:
1) Uninstall vmtools, reinstall, reboot server.
2) If this does not resolve the issue, uninstall vmware tools, reinstall using the custom option when prompted, deselect VSS, reboot the server after install completes.
When you try logging onto your Vsphere Client you receive the below error:
Vsphere Client could not connect to Server. A connection failure occured (Unable to connect to the remote server)
Check that your auto vm services are running. The most common cause.
Snapshots no longer showing within vmware Snapshot manager but still exist on datastore
You delete a snapshot via snapshot manager and it disappears from snapshot manager, but you find that it still exists on the datastore.
Try creating a new snapshot and then delete it. This should consolidate all your snapshots.
When removing a snapshot using vmware, the progress may hang at 95% and then time out with errors such as the ones below:
The request refers to an object that no longer exists or never existed
A general system error occured: Invalid fault
The snapshot should eventually delete, there is still stuff going on in the back ground.
To see progress, logon to the esx/esxi server directly via your vsphere client.