beautypg.com

Tftp logging and enablement, Deployment files logged to the tftp server – HP Virtual Connect 8Gb 20-port Fibre Channel Module for c-Class BladeSystem User Manual

Page 300

background image

Appendix B: Auto-deployment process 300

TFTP logging and enablement

When deploying a large number of enclosures with the auto-deployment capability, it might be difficult to
know which configurations completed (and when), and which configurations might have a failure or are

stuck in a waiting loop because of a configuration issue.
To help with deployment status awareness and provide a common place for TFTP logs, you can have the TFTP

status and logs posted back to the TFTP server. To enable this option before deployment, create a writable
directory in the root of the TFTP server called "deployment-logs" with appropriate permissions, and the

deployment process will publish the status and logs to the TFTP server. The log files are organized by

enclosure serial number and type of file.

Deployment files logged to the TFTP server

-vc-deployment.log

This log is created during the deployment process and contains the operational messages that occur during
the deployment process. This is the same log that is shown in the CLI with the show auto-deployment log

command and that is viewable in the GUI after a deployment is completed.

-vc-deployment.output

This console output is created from the execution of the configuration script during the deployment process. If
an error occurs during configuration, it is shown in the output file. This is the same log that is shown in the CLI
with the show auto-deployment output command, and that is viewable in the GUI after a deployment

is completed.

-vc-deployment-status.success

This tagfile is created if the deployment process was successful for a deployment target configuration. The

tagfile provides an easy way to view the deployment log directory and quickly identify which target
configuration deployments have completed successfully.

-vc-deployment-status.failed

This tagfile is created if the deployment process was not successful for a deployment target configuration. The

tagfile provides an easy way to view the deployment log directory and quickly identify which target

configuration deployments were not successful.
The following example shows what would be seen on the TFTP server after a single target configuration is
successfully deployed:
Example
TFTP Server Root

/deployment-logs/GB8849BJ7L-vc-deployment.log

/deployment-logs/GB8849BJ7L-vc-deployment.output

/deployment-logs/GB8849BJ7L-vc-deployment-status.success

If the deployment-logs directory exists, each deployment process writes back to the TFTP server and

overwrites the previous files that existed for the enclosure being deployed.
If you want to preserve the logs for each deployment, archive the existing logs and clear the deployment-logs

directory before the next deployment occurs.