2,187
edits
Difference between revisions of "Lab Manager"
Jump to navigation
Jump to search
→Troubleshooting: Added "Unable to Export Configuration"
(→Configuration IP's Lister: Changed linked page name) |
(→Troubleshooting: Added "Unable to Export Configuration") |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 49: | Line 49: | ||
# Go to '''Manage | Resources | Physical Networks''' and add network bindings for each of the ESX's | # Go to '''Manage | Resources | Physical Networks''' and add network bindings for each of the ESX's | ||
# Go to '''Manage | Resources | Hosts''' and '''Enable''' the hosts | # Go to '''Manage | Resources | Hosts''' and '''Enable''' the hosts | ||
== Put Spanned ESX Host into Maintenance Mode == | |||
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 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 | |||
# Once all deployed (non service) VM's have migrated off, put DRS to '''Partially Automated''' and '''''cancel'''''' the ''Enter Maintenance Mode'' task | |||
# Then '''Disable''' the host in Lab Manager, and unselect the '''Enable host for Host Spanning''' to undeploy the service VM | |||
#* In Lab Manager, go to Manage > Resources > Hosts tab to Disable, and go into the ESX's Properties to disable host spanning | |||
# 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. 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 == | ||
In theory a deployed VM's config shouldn't be changed, in reality its bound to be required at some point as a one off, but its quite limited on what can be | In theory a deployed VM's config shouldn't be changed, in reality its bound to be required at some point as a one off, but its quite limited on what can be achieved. | ||
Any changes will be lost when the template is undeployed and its state not saved. If this isn't wanted, or if its a regular occurrence, the VM templates should be edited (CPU and memory can be edited with Lab Manager, the VM doesn't need to be re-imported). | Any changes will be lost when the template is undeployed and its state not saved. If this isn't wanted, or if its a regular occurrence, the VM templates should be edited (CPU and memory can be edited with Lab Manager, the VM doesn't need to be re-imported). | ||
| Line 90: | 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 158: | Line 170: | ||
* '''[[Lab Manager Configuration IP List]]''' | * '''[[Lab Manager Configuration IP List]]''' | ||
The above script allows you to generate a email showing the external (NATed) addresses of a configuration. | The above script allows you to generate a email showing the external (NATed) addresses of a configuration. | ||
=== Configuration IP's Lister and RDP Tester === | |||
* '''[[Lab Manager Config IP List and RDP Test]]''' | |||
The above script is really a version 2 of [[#Configuration_IP.27s_Lister|Configuration IP's Lister]] which still allows you to generate a email showing the external (NATed) addresses of a configuration, but also allows you to test RDP access to all your VM's within the config. | |||
== Troubleshooting == | == Troubleshooting == | ||
| Line 211: | 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 === | ||
| Line 230: | Line 255: | ||
[[Category:VMware]] | [[Category:VMware]] | ||
[[Category:Lab Manager]] | |||