Sun Microsystems 3900, 6900 manual Sun Proprietary/Confidential Internal Use Only

TABLE B-1Virtualization Engine Error Messages (Continued)

Source of Error Message	Cause of Error Message	Suggested Corrective Action
checkvemap	Cannot establish communication	1.	Run the checkvemap command
	with ${vepair}		again.
		2.	If this fails, check the status of
			both virtualization engines.
		3.	If there is an error condition, see
			Appendix A for corrective action.
createvezone	An invalid WWN ($wwn) is on the	The WWN that was specified has a
	$vepair initiator ($init), or the	SLIC zone and/or an HBA alias has
	virtualization engine is unavailable.	already been assigned.
		1.	If a zone name is assigned, run the
	For a WWN to be available for		rmvezone command.
	createvezone, the WWN in the	2.	If errors still exist, run
	map file (showvemap -n		sadapter alias -d $vepair
	ve_pairname) must be “Undefined”		-r $initiator -a $zone -n
	and the online status should be		“ “.
	“Yes.”	3.	Run savemap -n $vepair.
createvlun	Invalid disk pool $diskpool on	1.	Run the showvemap -n
	$vepair, or disk pool is unavailable.		$vepair command to verify that
			the disk pool was created
			properly.
		2.	If the disk pool is unavailable, run
			creatediskpools -n $t3name.
		3.	If that fails, check the Sun
			StorEdge T3+ array for
			unmounted volumes or path
			failures, by running
			checkt3config -n $t3name -v.
createvlun	Unable to execute command. The	1.	Run checkt3mount -n
	associated Sun StorEdge T3+ array		$t3name
	physical LUN ${t3lun} for disk		-l ALL to see the mount status of
	pool ${diskpool} might not be		the volume.
	mounted.	2.	For further information about
			problems with the underlying Sun
			StorEdge T3+ array, run
			checkt3config -n $t3name -v.

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

Sun Proprietary/Confidential: Internal Use Only