2,187
edits
Difference between revisions of "Lab Manager"
Jump to navigation
Jump to search
→Troubleshooting: Added "Unable to Export Configuration"
m (Typo) |
(→Troubleshooting: Added "Unable to Export Configuration") |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 51: | Line 51: | ||
== Put Spanned ESX Host into Maintenance Mode == | == Put Spanned ESX Host into Maintenance Mode == | ||
You can't put | You can't put a Lab Manager enabled ESX directly into maintenance mode, if it's also enabled for host spanning. The service VM (called something like <code>012345-VMwareLM-ServiceVM-I6-H78</code>) won't power-down or undeploy automatically (and it can't be migrated via vMotion as it needs to stay on its ESX to enable host-spanning). | ||
# Deployed but powered off LM VM's can't be moved, so any on the host have to be either powered on, or undeployed | # Deployed but powered off LM VM's can't be moved either, so any on the host have to be either powered on, or undeployed | ||
# With DRS set to '''Fully Automated''', select '''Enter Maintenance Mode''' for your ESX host | # With DRS set to '''Fully Automated''', select '''Enter Maintenance Mode''' for your ESX host | ||
# Once all deployed (non service) VM's have migrated off, put DRS to '''Partially Automated''' and '''''cancel'''''' the ''Enter Maintenance Mode'' task | # Once all deployed (non service) VM's have migrated off, put DRS to '''Partially Automated''' and '''''cancel'''''' the ''Enter Maintenance Mode'' task | ||
| Line 60: | Line 60: | ||
# Finally, put the host in '''Maintenance Mode''' | # Finally, put the host in '''Maintenance Mode''' | ||
Once your work is complete, take the host out of maintenance mode, enable for host spanning and as LM host, then put DRS back to Fully Automated | Once your work is complete, take the host out of maintenance mode, enable for host spanning and as LM host, then put DRS back to Fully Automated. Its worth manually vMotioning a Lab Manager deployed VM onto the host to double check everything is back in full working order. | ||
== Change a Deployed VM's Resources == | == Change a Deployed VM's Resources == | ||
| Line 102: | Line 102: | ||
== SOAP API == | == SOAP API == | ||
As of 2010, there is no [[ | As of 2010, there is no [[:Category:PowerShell|PowerShell]] or [[:Category:PowerCLI|PowerCLI]] interface into Lab Manager, and there is unlikely to be one now that Lab Manager is going end of life. There is an underlying SOAP interface (on which a PowerCLI interface would be built), which provides limited interaction. This can be utilised via PowerShell scripts. | ||
The functions below were taken from http://poshcode.org/753, note that whilst you can connect to the Lab manager web service without explicitly supplying a user/pass (assuming the logged in user has access), you do need credentials in order to be able to create the Authentication Header that's required for all API calls. I tend to store a local copy of my user/pass (see [[Power_Shell#Store_Password_Securely|Store Password Securely]]) to make this less of a chore. | The functions below were taken from http://poshcode.org/753, note that whilst you can connect to the Lab manager web service without explicitly supplying a user/pass (assuming the logged in user has access), you do need credentials in order to be able to create the Authentication Header that's required for all API calls. I tend to store a local copy of my user/pass (see [[Power_Shell#Store_Password_Securely|Store Password Securely]]) to make this less of a chore. | ||
| Line 227: | Line 227: | ||
If Lab Manager keeps dropping the connection to the ESX, check activity in the Virtual Centre. If an ESX is continually being instructed to complete tasks that fail you need to consider restarting that ESX. | If Lab Manager keeps dropping the connection to the ESX, check activity in the Virtual Centre. If an ESX is continually being instructed to complete tasks that fail you need to consider restarting that ESX. | ||
=== Unable to Export Configuration === | |||
Export of a configuration to full fat VM's fails... | |||
* Lab Manager shows... | |||
** '''VirtualMachine.clone task on CloneVM_Task failed'''... | |||
* vCenter also shows... | |||
** '''Incompatible device backing specified for device 'x'.''' for the affected VM's Clone virtual machine task | |||
Suspect the problem is caused by a problem with the VM's config file (VMX) - to work around, create a clone of the configuration and then export from that clone. | |||
=== Unable to Enable Datastore === | === Unable to Enable Datastore === | ||