Sun Microsystems StorEdge 6900 Series - Manual (Page 148)

132 Sun StorEdge 3900 and 6900 Series Troubleshooting Guide • March 2002
.
TABLE B-1 Virtualization Engine SUNWsecfg Error Messages
Message Description and Cause of Error Suggested Action
Common to
virtualization engines Invalid virtualization engine pair name
$vepair , or virtualization engine is
unavailable. Confirm that the
configuration locks are set. This is
usually due to the
savevemap
command running.
Try ps -ef | grep savevemap or
listavailable -v (which returns
the status of individual virtualization
engines).
Common to
virtualization engine No virtualization engine pairs found,
or the virtualization engine pairs are
offline. Confirm that the configuration
locks are set. This is usually due to the
savevemap command running.
Try ps -ef | grep savevemap or
listavailable -v (which returns
the status of individual virtualization
engines).
Common to
virtualization engine Unable to obtain lock on $vepair .
Another command is running.
Another virtualization engine
command is updating the
configuration. Try
listavailable -v
(which returns the status of individual
virtualization engines) and check for
lock file directly by using
ls -la
/opt/SUNWsecfg/etc (look for
.v1.lock or .v2.lock ). If the lock is
set in error, use the removelocks -v
command to clear.
Common to
virtualization engine Unable to start slicd on ${vepair }.
Cannot execute command.
Try running startslicd and then
showlogs -e 50 to determine why
startslicd couldn’t start the
daemon. You might have to reset or
power off the virtualization engine if
the problem persists.
Common to
virtualization engine Login failed. The environment variable
VEPASSWD might be set to an incorrect
value. Try again.
A password is required to log in to the
virtualization engine. The utility uses
the VEPASSWD environment variable
to login. Set the VEPASSWD
environment variable with the proper
value.
Common to
virtualization engine After resetting the virtualization
engine, the $VENAME is unreachable.
Be aware that after a reset, it takes
approximately 30 seconds to boot.
The hardware might be faulty.
Check the IP address and netmask that
has been assigned to the virtualization
engine hardware.