Sun Microsystems 6900 - Manual (Page 184)

164 Sun StorEdge 3900 and 6900 Series 2.0 Troubleshooting Guide • March 2003
Sun Proprietary/Confidential: Internal Use Only
Virtualization Engine Error Messages
TABLE B-1 Virtualization Engine Error Messages
Source of Error Message Cause of Error Message Suggested Corrective Action
Common to
virtualization engine Invalid virtualization engine pair
name, or the virtualization engine is
unavailable. This is usually because
the
savevemap command is running
Run ps -ef | grep savevemap
or listavailable -v (which
returns the status of individual
virtualization engines) to confirm
that the configuration locks are set.
Common to
virtualization engine No virtualization engine pairs were
found, or the virtualization engine
pairs are offline. This is usually due
to the
savevemap command
running.
Run ps -ef | grep savevemap
or listavailable -v (which
returns the status of individual
virtualization engines) to confirm
that the configuration locks are set.
Common to
virtualization engine The virtualization engine was unable
to obtain a lock on
$vepair .
Another virtualization engine
command is updating the
configuration.
1. Run listavailable -v (which
returns the status of individual
virtualization engines)
2. Check for the lock file directly by
using ls -la
/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
virtualization engine The virtualization engine was unable
to start
slicd on ${vepair , so it
cannot execute the command.
1. Run startslicd and then
showlogs -e 50 to determine
why startslicd could not start
the daemon.
2. Reset or power off the
virtualization engine if the
problem persists.
Common to
virtualization engine The login failed.
A password is required to log in to
the virtualization engine. The utility
uses the
VEPASSWD environment
variable to login.
The environment variable VEPASSWD
might be set to an incorrect value.
1. Set the VEPASSWD environment
variable with the proper value.
2. Try to login again.