Lab Manager - Revision history

Sstrutt: /* Troubleshooting */ Added "Unable to Export Configuration"

2012-07-19T09:30:36Z

Troubleshooting: Added "Unable to Export Configuration"

← Older revision		Revision as of 09:30, 19 July 2012
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 ===

Sstrutt: /* SOAP API */ Fix broken links

2012-05-17T14:00:04Z

SOAP API: Fix broken links

← Older revision		Revision as of 14:00, 17 May 2012
Line 102:		Line 102:

	== SOAP API ==		== SOAP API ==
	As of 2010, there is no [[~~Power_Shell~~\|PowerShell]] or [[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.		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.

Sstrutt: /* Put Spanned ESX Host into Maintenance Mode */ Minor wording improvments

2012-05-04T10:27:40Z

Put Spanned ESX Host into Maintenance Mode: Minor wording improvments

← Older revision		Revision as of 10:27, 4 May 2012
Line 51:		Line 51:

	== Put Spanned ESX Host into Maintenance Mode ==		== Put Spanned ESX Host into Maintenance Mode ==
	You can't put an ESX directly into maintenance mode, if ~~its enable~~ for host spanning~~, as the~~ service VM (called something like <code>012345-VMwareLM-ServiceVM-I6-H78</code>) won't power-down or undeploy automatically.		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 ==

Sstrutt: Typo

2011-12-21T14:26:22Z

Typo

← Older revision		Revision as of 14:26, 21 December 2011
Line 50:		Line 50:
	# 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 ===		== Put Spanned ESX Host into Maintenance Mode ==
	You can't put an ESX directly into maintenance mode, if its enable for host spanning, as the service VM (called something like <code>012345-VMwareLM-ServiceVM-I6-H78</code>) won't power-down or undeploy automatically.		You can't put an ESX directly into maintenance mode, if its enable for host spanning, as the service VM (called something like <code>012345-VMwareLM-ServiceVM-I6-H78</code>) won't power-down or undeploy automatically.

Sstrutt: Added "Put Spanned ESX Host into Maintenance Mode"

2011-11-17T13:13:03Z

Added "Put Spanned ESX Host into Maintenance Mode"

← Older revision		Revision as of 13:13, 17 November 2011
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 an ESX directly into maintenance mode, if its enable for host spanning, as the service VM (called something like <code>012345-VMwareLM-ServiceVM-I6-H78</code>) won't power-down or undeploy automatically.

			# Deployed but powered off LM VM's can't be moved, 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

	== 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 ~~acheived~~.		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).

Sstrutt: /* SOAP API */ Added "Configuration IP's Lister and RDP Tester"

2011-07-13T16:46:53Z

SOAP API: Added "Configuration IP's Lister and RDP Tester"

← Older revision		Revision as of 16:46, 13 July 2011
Line 158:		Line 158:
	* '''[[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 ==

Sstrutt: Added Lab Manager category

2011-07-13T16:41:39Z

Added Lab Manager category

← Older revision		Revision as of 16:41, 13 July 2011
Line 230:		Line 230:

	[[Category:VMware]]		[[Category:VMware]]
			[[Category:Lab Manager]]

Sstrutt: /* Configuration IP's Lister */ Changed linked page name

2011-04-18T13:19:58Z

Configuration IP's Lister: Changed linked page name

← Older revision		Revision as of 13:19, 18 April 2011
Line 156:		Line 156:

	=== Configuration IP's Lister ===		=== Configuration IP's Lister ===
	* '''[[Lab Manager 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.

Sstrutt: /* SOAP API */ Added "Configuration IP's Lister" link

2011-04-18T13:18:34Z

SOAP API: Added "Configuration IP's Lister" link

← Older revision		Revision as of 13:18, 18 April 2011
Line 90:		Line 90:

	== SOAP API ==		== SOAP API ==
	As of 2010, there is no [[Power_Shell\|PowerShell]] or [[PowerCLI]] interface into Lab Manager. 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.		As of 2010, there is no [[Power_Shell\|PowerShell]] or [[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 155:		Line 155:
	</source>		</source>

			=== Configuration IP's Lister ===
			* '''[[Lab Manager IP List]]'''
			The above script allows you to generate a email showing the external (NATed) addresses of a configuration.

	== Troubleshooting ==		== Troubleshooting ==

Sstrutt: /* Unable to Deploy Virtual Machine */ Added "vCenter Lab Manager timed out trying to read the virtual machine's file on the remote host"

2011-04-14T10:04:24Z

Unable to Deploy Virtual Machine: Added "vCenter Lab Manager timed out trying to read the virtual machine's file on the remote host"

← Older revision		Revision as of 10:04, 14 April 2011
Line 163:		Line 163:
	# Locate the problem network and go to '''Properties'''		# Locate the problem network and go to '''Properties'''
	# Update the '''Physical Network Bindings''' for the relevant ESX		# Update the '''Physical Network Bindings''' for the relevant ESX


	'''Unable to deploy VM ''VM'' in VirtualCenter. The session is not authenticated.'''<br>		'''Unable to deploy VM ''VM'' in VirtualCenter. The session is not authenticated.'''<br>
Line 172:		Line 173:
	# Click on '''OK''' to re-apply the user/pass		# Click on '''OK''' to re-apply the user/pass

	'''''ESX'' does not support virtual machine hardware version "0"'''
			'''''ESX'' does not support virtual machine hardware version "0"'''<br>
	Caused by config data corruption, potentially from the machine's VMX file		Caused by config data corruption, potentially from the machine's VMX file
	# Locate the VM's config and confirm the hardware version is set correctly (eg to v7 for ESX4)		# Locate the VM's config and confirm the hardware version is set correctly (eg to v7 for ESX4)
Line 181:		Line 183:
	#* <code> UPDATE VirtualServer SET hw_version=<correctNumber> WHERE hw_version=0 AND name='VirtualMachineName' </code>		#* <code> UPDATE VirtualServer SET hw_version=<correctNumber> WHERE hw_version=0 AND name='VirtualMachineName' </code>
	# The VM then needs to be cloned to template and then redeployed (clone required to prevent reoccurrance)		# The VM then needs to be cloned to template and then redeployed (clone required to prevent reoccurrance)


			'''vCenter Lab Manager timed out trying to read the virtual machine's file on the remote host'''<br>
			Caused by either of...
			* The ESX experiencing problems reading the files of the VM (and its parents) on VMFS storage
			*# Check out VMFS storage!
			* The VM is still partially running on an ESX (so its files are locked)
			*# Run the following command on the likely ESX(s) to running VM processes
			# <code> ps auxwww \| grep -i vmx </code>
			*# Kill the relevant processes, eg
			# <code> 7135117 7179577 mks:001876-VM-Server-A /bin/vmx </code>
			# <code> 7180174 7179577 vcpu-0:001876-VM-Server-A /bin/vmx </code>
			# <code> 7180175 7179577 vcpu-1:001876-VM-Server-A1 /bin/vmx </code>
			# Run <code> kill 7179577 </code>

	=== Lab Manager Disconnected from ESX ===		=== Lab Manager Disconnected from ESX ===