Infrastructure Deployment Policy Group
The Infrastructure Deployment policy group contains the following policies for component deployment within the DSM infrastructure. You can modify policy parameter values by double-clicking a policy to display the Setting Properties dialog.
Indicates whether packages should always be deployed to target computers. This policy can be useful if you want to roll back to particular software versions, for example. Typically, if the deployment scan indicates that a package is already "Deployed" or "Newer," you are unable to re-deploy the same package, but a value of True overrides this behavior.
Default: False
Indicates whether a primer software package is always deployed and installed on a target. This policy is useful if the primer installation on the target host has become corrupt or an upgrade of the primer is required. Valid values are True and False.
Default: True
Indicates the method by which the primer package is delivered to the target computer. Valid values are as follows:
Specifies that the primer package be deployed from a scalability server to the target computer if the deployment is configured to deploy from a scalability server.
Specifies that the primer package be deployed from the management server to the target computer.
Note: A value of True allows better utilization of network bandwidth and faster deployments if there is a scalability server that is geographically closer to the intended target computers.
Default: True
Controls the maximum number of concurrent deployments to target computers that are running on the deployment manager at any one time. This value can be increased or decreased depending on the current workload of the deployment manager.
Default: 4
Indicates whether DMDeploy is set to "ping" targets during a deployment scan. Some networks may be configured through firewall settings and router configuration policy to stop attempts to check whether a computer is active on a network. Setting this policy to True bypasses such checks and marks the computer as "Responding," allowing deployment to continue.
Note: This policy should be set to True if deploying to a Microsoft Windows Vista computer that returns a status of "No Response" during the scan phase.
Default: False
Specifies the number of minutes of inactivity until a machine state is set to Failed status. The deployment manager expects confirmation from the target for both package delivery and installation. In some cases, package delivery and installation can take a considerable amount of time, especially if running over large networks that have low bandwidth to target computers that are very slow or heavily loaded. This policy allows the reset time to be increased (or decreased) before a deployment is marked as Failed.
Note: Marking the job as Failed on the manager does not affect any installation running on the target computer. If the installation is in progress but completes after the job reset time, the job on the manager will be marked as Failed but the installation continues as normal.
Default: 120
Specifies the maximum length of time in minutes that the deployment manager waits for a response to any control message sent to the DMPrimer during deployment. This value can be increased if deployment is taking place over a slow network link.
Default: 2
Specifies the maximum length of time in minutes to wait for a primer package to be installed on a target system. This timeout period starts after the primer software has been transferred to the target computer. Increase this value if deploying to very slow or heavily loaded target computers. If this timeout expires, the deployment manager assumes that the installation on the target computer failed. However, if installation is actually still in progress, a subsequent deployment attempt to the same target (after primer installation competes) continues successfully.
Note: This policy is applicable when deploying to target computers running any operating system.
Limits: 1–500
Default: 10
Specifies the maximum number of seconds that the deployment manager waits for a response to a ping of a target computer during the scan phase.
Default: 15
Specifies the size in bytes of a Secure Shell (SSH) data packet used when deploying the primer package. Reducing the SSH data packet size increases the time taken to deliver the primer to the target system.
Note: Reduce this value if you are experiencing problems deploying the primer to UNIX/Linux systems, especially if you are seeing a partial primer install image transfer to the /tmp/dmprimer directory when deploying the primer package.
Note: Some SFTP servers do not accept the default packet size, which results in an "SSH cannot perform SFTP" status message. In this case, you must reduce the packet size. A value of 12288 typically allows successful deployment.
Default: 24576
Specifies the maximum number of times that the deployment manager should attempt to create a share to a Windows target computer when deploying the primer software package. If you encounter network interruptions when carrying out DSM package deployments, increase the value. There is a delay of a few seconds between each connection attempt.
Note: This policy is only applicable when deploying to Windows targets.
Limits: 1–100
Default: 2
Specifies the share to which the primer software package is copied during deployment. By default the primer installation package is copied to admin$ before being installed. If this is not required or wanted due to security reasons, for example, then an alternative share location can be specified from which to run the primer installation.
Default: admin$
Indicates whether host names are preferred for deployment instead of IP addresses. This policy should be set to True if you are running in a network environment where IP address to host name mappings could be affected by Dynamic Host Configuration Protocol (DHCP) considerations during the lifetime of the job. Valid values are True (use host names) and False (use IP addresses).
Default: False
Indicates whether CA Message Queuing (CAM) should disable translation of IP addresses to host names. This policy should be set to True if messaging is likely to be affected by DHCP considerations during the lifetime of the job.
Default: False
|
Copyright © 2013 CA.
All rights reserved.
|
|
