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