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
the connection, then edit the server profile again and add
a new connection.
It was not possible to remove the provided vNet mapping
from the server profile.
2629
The target server bay does not support server profiles.
Verify the device in the server bay is supported by VC
Manager.
2630
Specified Server Bay ID does not correspond to a managed
server profile in VCEM.
2632
Cannot perform server profile move because the specified
server profile was already moved from Server Bay on VC
Domain .
2633
Cannot perform the server profile operation because it is
not possible to have connections with different address
types in the same server profile.
2636
The target server is powered up. The operation requires
the server to be powered down.
2639
In the ethernet connection for port , the range type is not
compatible with the addresses inside the connection.
2640
In the ethernet connection for port , the connection was
replaced by a new one. To replace a connection by a new
2641
one, first edit the profile and delete the connection, then
edit the server profile again and add a new connection.
There are more than one FC SAN connections configured
as secondary SAN boot. Only one FC SAN connection
can be configured as secondary SAN boot.
2643
There is one FC SAN connection configured as secondary
SAN boot, but no one configured as primary SAN boot.
2644
There are missing or duplicate FC SAN connections. A
continuous sequence finishing on the last valid FC SAN
connection port is required.
2645
In the ethernet connection for port, the selected Network
does not exist. The provided Network must exist in the VC
Domain group the Server profile belongs.
2646
A server profile cannot have more than x Ethernet network
connections where x represents a number.
2647
Cannot find FC connection for the specified interconnect
bay because the interconnect bay number is invalid.
2650
Cannot perform server profile operation because the target
server bay is not specified. Select a target server bay and
perform the operation again.
2651
The server profile is configured to use Factory Defaults for
Serial Numbers. Verify no Serial Number and no UUID
2655
are entered when using the Factory Defaults Serial
Numbers.
76 Error messages