HP XP P9000 Command View Advanced Edition Suite Software 7.6.1-00 CLI Reference Guide

Description and recommended actionProblem
CAUSE: Authenticate failed in the Device Manager.
SOLUTION: Make sure that the user ID and password that you
specified when executing the command are correct.
If you are using the function for linking to an external authentication
server, take the action specified below.
If the external authentication server is an LDAP server:
1. Check the external authentication server settings or network
status in order to make sure you can use the host, port, and
protocol that are specified in exauth.properties to access
the external authentication server.
2. Use the hcmdsldapuser command to make sure that the in-
formation about the server identification names that are spe-
cified for the auth.server.name attributes of exauth.prop-
erties has been registered.
3. If you use StartTLS for communication, check the SSL settings.
When the external authentication server is a RADIUS server:
1. Check the external authentication server settings or network
status in order to make sure you can use the host, port, and
protocol that are specified in exauth.properties to access
the external authentication server.
2. Use the hcmdsradiussecret command to make sure that
the information about the server identification names that are
specified for the auth.server.name attributes of exau-
th.properties has been registered.
When the external authentication server is Kerberos:
Check the external authentication server settings and network
status to make sure you can use the host and port specified in
exauth.properties to access the external authentication
server.
If you cannot resolve the problem even after taking these actions,
collect maintenance information for Device Manager and Common
Component, and then contact the HP Technical Support.
The following message is displayed when
a Device Manager CLI command is
executed
#
:
[KAIC90084-E] HTTP Response:
"HTTP/1.0 401 Unauthorized"
If the command is executed from the command line:
CAUSE: The size of requests to the Device Manager server is
too large because too many operation targets are specified
on a single command line.
SOLUTION: Execute the command by dividing it into multiple
instances.
If the command is executed by using the batch functionality:
CAUSE: On a single command line, five or more THP/Smart
volume device numbers are specified for the devnums para-
meter of the ModifyVirtualVolume command.
SOLUTION: Check the execution status of the batch file, and
then re-create the batch file. However, if you want to re-execute
the batch functionality by specifying five or more device num-
bers, write them on separate command lines.
The following message is displayed when
a Device Manager CLI command is
executed
#
:
[KAIC90084-E] HTTP Response:
"HTTP/1.1 413 Request Entity
Too Large"
CLI Reference Guide 475