Sun Microsystems 3900, 6900 manual Virtualization Engine Error Messages

Virtualization Engine Error Messages

TABLE B-1Virtualization Engine Error Messages

Source of Error Message	Cause of Error Message	Suggested Corrective Action
Common to	Invalid virtualization engine pair	Run ps -ef grep savevemap
virtualization engine	name, or the virtualization engine is	or listavailable -v (which
	unavailable. This is usually because	returns the status of individual
	the savevemap command is running	virtualization engines) to confirm
		that the configuration locks are set.
Common to	No virtualization engine pairs were	Run ps -ef grep savevemap
virtualization engine	found, or the virtualization engine	or listavailable -v (which
	pairs are offline. This is usually due	returns the status of individual
	to the savevemap command	virtualization engines) to confirm
	running.	that the configuration locks are set.
Common to	The virtualization engine was unable	1.	Run listavailable -v (which
virtualization engine	to obtain a lock on $vepair.		returns the status of individual
			virtualization engines)
	Another virtualization engine	2.	Check for the lock file directly by
	command is updating the		using ls -la
	configuration.		/opt/SUNWsecfg/etc (look for
			.v1.lock or .v2.lock).
		3. If the lock is set in error, use the
			removelocks -v command to
			clear.
Common to	The virtualization engine was unable	1.	Run startslicd and then
virtualization engine	to start slicd on ${vepair, so it		showlogs -e 50 to determine
	cannot execute the command.		why startslicd could not start
			the daemon.
		2. Reset or power off the
			virtualization engine if the
			problem persists.
Common to	The login failed.	1.	Set the VEPASSWD environment
virtualization engine			variable with the proper value.
	A password is required to log in to	2.	Try to login again.
	the virtualization engine. The utility
	uses the VEPASSWD environment
	variable to login.
	The environment variable VEPASSWD
	might be set to an incorrect value.

164 Sun StorEdge 3900 and 6900 Series 2.0 Troubleshooting Guide • March 2003

Sun Proprietary/Confidential: Internal Use Only