HP Virtual Connect Enterprise Manager 6.3.1 CLI Guide
Table Of Contents
- HP Insight Software Virtual Connect Enterprise Manager
- Contents
- 1 Getting Started
- 2 Using VCEMCLI
- 3 Using VCEM commands
- add profile
- set profile
- assign profile
- export profiles
- unassign profile
- add enet-connection
- set enet-connection
- remove enet-connection
- add fc-connection
- set fc-connection
- remove fc-connection
- add fcoe-connection
- set fcoe-connection
- remove fcoe-connection
- add iscsi-connection
- set iscsi-connection
- remove iscsi-connection
- set iscsi-boot-param
- remove iscsi-boot-param
- add server-port-map
- set server-port-map
- remove server-port-map
- poweroff devicebay
- poweron devicebay
- show power-status
- show job
- show version
- show vcem-status
- startvcdmaint
- cancelvcdmaint
- completevcdmaint
- 4 Error messages
- 5 Troubleshooting VCEMCLI
- VCEMCLI calls result in access denied errors
- VCEMCLI calls result in errors for invalid leading character or invalid characters
- VCEMCLI calls result in 404 errors
- API timeouts
- High CPU usage on the CMS server while running a VCEMCLI client
- Job reports failed status
- Completed with warning job status
- Unable to assign a profile to a Domain Group
- VC Domain reports Configuration Mismatch status
- VC Domain reports Expired License status
- Error on database operation occurs
- Failed to execute VCEM operation because VC firmware not supported
- Creating a server profile fails
- Server profile edit operation fails when target server is powered on
- Server profile job completed with success but changes have not occurred
- After a server profile assignment, some connections defined in the server profile are not functional
- Commands -add profile or -set profile error messages
- Command -add profile error messages
- Additional Troubleshooting Information and tools
- 6 Support and other resources
- Index
Table 37 VCEM server error messages and descriptions (continued)
Error message description
NOTE: The error message descriptions in this table use
[x] to represent variables in the error message output.
Error message number
and that the VC Domain is locked for the VCEM and then
perform the operation again.
The operation could not be performed because a VC
Domain with name [x] is already being managed by
2015
VCEM. Enter a unique name for the VC Domain name and
perform this operation again.
The enabled VC feature(s) [x] are not supported by Virtual
Connect Enterprise Manager (VCEM). Verify how to disable
2016
VC features according to VC Domain Group firmware
mode in the VCEM User Guide.
The enabled VC feature(s) are not supported by Virtual
Connect Enterprise Manager (VCEM). Verify how to disable
2016
VC features according to VC Domain Group firmware
mode in the VCEM User Guide.
The operation could not be performed because the VC
Domain with ID [x] was not found in the VCEM database.
2035
Verify the entered VC Domain ID is valid and then perform
the operation again.
The operation could not be performed because the VC
Domain Group with id was not found in the VCEM
2037
database. Verify the specified VC Domain Group id is
valid and perform the operation again.
The operation could not be performed because the VC
Domain was not found. Provide a valid VC Domain and
then perform the operation again.
2038
The operation cannot be performed because VC firmware
version is not supported by VCEM. Refer to the VCEM User
2040
Guide to verify the VC firmware versions supported by
each VC Domain Group firmware mode.
The new VC Domain configuration is using uplink ports
from a VC Ethernet module of an cabinet [x] that is not
2041
configured in all VC Domains from a VC Domain Group
[x]. To use uplink ports present in a remote enclosure, verify
that all VC Domains that belong to the VC Domain Group
have a corresponding remote enclosure configured, and
then perform the operation again.
The operation could not be performed because VCEM was
not able to obtain the necessary permissions to manage
the VC Domain [x]. Possible causes are:
2045
1) Another user is enabled as the External Manager at VC
Domain and the VCEM cannot manage this VC Domain.
2) VCEM lost the External Manager lock at the VC Domain.
To resolve this issue:
1) Verify if there is no other user as the External Manager.
2) Remove this VC Domain from the VC Domain Group
and add it back to the same VC Domain Group.
The operation cannot be performed because VCEM could
not push the VC Domain base configuration to VC Domain
2055
[x]. Verify VCEM can communicate with VC Manager and
perform the operation again.
68 Error messages