HP Virtual Connect 4Gb Fibre Channel Module for c-Class BladeSystem - Manual (Page 285)

Appendix B: Auto-deployment process 285
Typical failure deployment status values
Status Comment Resolution
Waiting for
DHCP
Cause: The DHCP server might not be properly
configured to support auto-deployment (BOOTP
settings).
This status does not result in a failed deployment, but
the deployment process enters a "polling" state
waiting for DHCP to provide the appropriate TFTP
settings to VC. If the deployment is in this state, the
process can be stopped with the stop
auto-deployment command if it cannot proceed.
The DHCP configuration should be
reviewed, especially the Option 66 and
67 settings, to make sure they are correct
for the VC domains expected to be
deployed.
Waiting for
TFTP Possible Causes:
• Cannot communicate with TFTP server specified
in TFTP settings from DHCP
• VC configuration file cannot be found on the
TFTP server
• The permissions on the file or TFTP directory
might not be correct for remote access
This status does not result in a failed deployment, but
the deployment process enters a "polling" state
waiting for DHCP to provide the appropriate TFTP
settings to VC. If the deployment is in this state, the
process can be stopped with the stop
auto-deployment command if it cannot proceed.
The TFTP file settings should be reviewed
in the DHCP configuration to ensure they
are correct. Additionally, the
configuration file should be checked to
make sure it exists and is in the proper
location. The access privileges should be
verified to allow remote access.
Failed to Create
Domain
Snapshot
At the time an enclosure is imported, the domain
configuration is saved for redeployment scenarios. If
a deployment configuration snapshot cannot be
created, then it results in this status value and
redeployment operations are not be allowed. This
status is caused by an internal failure and typically
does not occur.
If this error occurs, it is typically an
internal error that needs to be reported
back to HP Support along with a support
dump for diagnosing the
cause. Typically, this error should not
occur.
Aborted by
User The deployment operation was attempted but was
aborted by the user before it could complete. This
status occurs if the user stops the deployment process
by using the stop auto-deployment command,
or by using the VC GUI.
Correct the condition that caused the
user to abort the deployment operation,
and start the deployment operation
again using start
auto-deployment.
Failed to
Validate
Configuration
File
This status is caused by a failure that occurred during
the validation of the configuration file.
Make sure the configuration file is valid
on the TFTP server and start the
deployment operation again using
start auto-deployment.
No
Configuration
Needed
If redeployment is initiated, the configuration file on
the TFTP server has not changed from the previous
deployment that occurred, and the current running
configuration for the domain matches the
configuration file, then a new deployment is not
performed.
No action needed. If you want to
change the deployed configuration, the
configuration file must be modified,
uploaded to the TFTP server, and the
deployment can be initiated using the
start auto-deployment command.
Failed to Power
Server Off
One or more servers could not be properly powered
off as a part of the deployment process.
Diagnose the reason why the server is
having power management issues,
correct the condition, and restart the
deployment process.