Typical failure deployment status values

Status

Comment

Resolution

 

 

 

Waiting for

Cause: The DHCP server might not be properly

The DHCP configuration should be

DHCP

configured to support auto-deployment (BOOTP

reviewed, especially the Option 66 and

 

settings).

67 settings, to make sure they are correct

 

This status does not result in a failed deployment, but

for the VC domains expected to be

 

the deployment process enters a "polling" state

deployed.

 

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-deploymentcommand if it cannot proceed.

 

Waiting for

Possible Causes:

The TFTP file settings should be reviewed

TFTP

• Cannot communicate with TFTP server specified

in the DHCP configuration to ensure they

 

in TFTP settings from DHCP

are correct. Additionally, the

 

• VC configuration file cannot be found on the

configuration file should be checked to

 

TFTP server

make sure it exists and is in the proper

 

location. The access privileges should be

 

• The permissions on the file or TFTP directory

 

verified to allow remote access.

 

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-deploymentcommand if it cannot proceed.

 

Failed to Create

At the time an enclosure is imported, the domain

If this error occurs, it is typically an

Domain

configuration is saved for redeployment scenarios. If

internal error that needs to be reported

Snapshot

a deployment configuration snapshot cannot be

back to HP Support along with a support

 

created, then it results in this status value and

dump for diagnosing the

 

redeployment operations are not be allowed. This

cause. Typically, this error should not

 

status is caused by an internal failure and typically

occur.

 

does not occur.

 

Aborted by

The deployment operation was attempted but was

Correct the condition that caused the

User

aborted by the user before it could complete. This

user to abort the deployment operation,

 

status occurs if the user stops the deployment process

and start the deployment operation

 

by using the stop auto-deploymentcommand,

again using start

 

or by using the VC GUI.

auto-deployment.

Failed to

This status is caused by a failure that occurred during

Make sure the configuration file is valid

Validate

the validation of the configuration file.

on the TFTP server and start the

Configuration

 

deployment operation again using

File

 

start auto-deployment.

No

If redeployment is initiated, the configuration file on

No action needed. If you want to

Configuration

the TFTP server has not changed from the previous

change the deployed configuration, the

Needed

deployment that occurred, and the current running

configuration file must be modified,

 

configuration for the domain matches the

uploaded to the TFTP server, and the

 

configuration file, then a new deployment is not

deployment can be initiated using the

 

performed.

start auto-deployment command.

Failed to Power

One or more servers could not be properly powered

Diagnose the reason why the server is

Server Off

off as a part of the deployment process.

having power management issues,

 

 

correct the condition, and restart the

 

 

deployment process.

 

 

 

Appendix B: Auto-deployment process 299