HP Virtual Connect Enterprise Manager Software - Manual (Page 8)

Security on the CMS
The VCEMCLI is installed on the CMS. By installing on the CMS, you get the benefits of the security
measures already in place for the CMS. The trade-off is that the script execution imposes additional
load on the CMS.
HP recommends that you evaluate the amount of load that the script places on the CMS, and either
program in pauses or reduce the amount of work that each invocation of the script accomplishes.
Authentication
Decide whether user name and password authentication or certificate-based authentication is
appropriate for your environment. For more information about authentication, see
“Authenticating
by using VCEM” (page 11) .
Using delays in script commands
Do not poll for results in a tight loop. Insert delays in your scripts to allow the CMS time to manage
other tasks. Polling for results by using tight loops without delays might overload the CMS.
Profiles and powering off or powering on
Assigning a profile to a bay that contains a server requires that the bay be powered off in order
to complete the assignment. Graceful power-off operations allow time for the operating system on
the server to go through its normal shutdown processing. If an unresponsive process prevents the
normal shutdown from proceeding, you may need to resort to an ungraceful power-off. You should
use this method only as a last resort because it may result in data loss on the affected server. The
same power-off constraint applies to unassigning or updating a profile for a bay that contains a
server.
Running scripts as Windows scheduled tasks
By configuring the Windows Task Scheduler to run your VCEMCLI script, you can schedule
operations such as server reboots so they occur during nonworking hours. Configure the scheduled
task by using the credentials that correspond to the specific VCEMCLI script that the task will run.
Comparing VCMCLI scripts to VCEMCLI scripts
The VCEMCLI uses the same keyword names that the VCMCLI uses for items common to both CLIs.
VCEMCLI keywords are always preceded by a dash. In the VCMCLI whether a dash is required
depends on the specific keyword. Name/Value pairs in the VCEMCLI are separated by a space,
whereas they are separated by an equal sign (=) in the VCMCLI.
8 Getting started