Sun Microsystems 6900 - Manual (Page 186)

166 Sun StorEdge 3900 and 6900 Series 2.0 Troubleshooting Guide • March 2003
Sun Proprietary/Confidential: Internal Use Only
checkvemap Cannot establish communication
with
${vepair}
1. Run the checkvemap command
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
$vepair initiator ( $init) , or the
virtualization engine is unavailable.
For a WWN to be available for
createvezone , the WWN in the
map file ( showvemap -n
ve_pairname ) must be “Undefined”
and the online status should be
“Yes.”
The WWN that was specified has a
SLIC zone and/or an HBA alias has
already been assigned.
1. If a zone name is assigned, run the
rmvezone command.
2. If errors still exist, run
sadapter alias -d $vepair
-r $initiator -a $zone -n
“ “ .
3. Run savemap -n $vepair .
createvlun Invalid disk pool $diskpool on
$vepair , or disk pool is unavailable.
1. Run the showvemap -n
$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
associated Sun StorEdge T3+ array
physical LUN
${t3lun} for disk
pool ${diskpool} might not be
mounted.
1. Run checkt3mount -n
$t3name
-l ALL to see the mount status of
the volume.
2. For further information about
problems with the underlying Sun
StorEdge T3+ array, run
checkt3config -n $t3name -v .
TABLE B-1 Virtualization Engine Error Messages (Continued)
Source of Error Message Cause of Error Message Suggested Corrective Action