Use this command to transfer an existing service profile association to another profile for the purpose of blade failover.
This command has the following format:
dpmucs failoverserviceprofile [-sc sc_url] -ucs_manager ucsmanagername -service_profile_dn serviceprofiledn -blade_dn bladename [-ws_user username] [-ws_password password] [-locale iso639value]
(Optional) Defines the URL for the service controller host.
Example: https://hostname:port/...
Defines the fully qualified host where the service controller is installed.
Example: localhost.ca.com
Defines the listening port for the service controller server.
Example: 80
Defines the name of the UCS Manager for retrieving information or an operation.
The fully qualified and unique name of a blade service profile. The blade service profile must be created before provisioning an OS. A service profile contains boot order, network settings, and storage (local or remote). Valid format: org-root/serviceprofile. The profile specified must be an associated service profile.
The fully qualified and unique name of a blade. If a blade is not provided, an unassociated, available blade is selected. Valid format: systemid/chassisid/bladeid.If a blade is not provided (""), a random available blade is selected.
(Optional) Specifies the credentials to use for the web service security check. If you do not include credentials, you are prompted to enter them. Avoid the prompt for credentials by setting up your own session using caaipsecurity.
(Optional) Specifies an IS0 639_3166 combination to override the default English output, for example, fr_FR for French. To use the locale of the command prompt, specify "native".
Example: Create Failover Service Profile
This example associates a random, available blade with a service profile for failover.
dpmucs.exe failoverserviceprofile -ucs_manager ucsmanager -service_profile_dn org-root/ls-dev-boot-from-san-esx-2 -blade_dn "
Copyright © 2013 CA. All rights reserved. |
|