Filter
Top Products
Disassociating a Profile from a UCS Blade
107
6. Click the name of the UCS Manager.
A list is displayed that shows the names of the blades that are installed under the selected
manager.
7.
In the Actions column, click the Associate Profile icon.
8. In the dialog, select the name of the profile you want to associate with this blade, then click OK.
The dropdown list in the dialog box lists the profiles that are currently defined in the UCS Manager
where this blade resides. The list is refreshed any time you add or remove profiles on the UCS
Manager.
You might need to wait a few minutes for this operation to finish. The operation might take a long
time, depending on the complexity of the setup. The timeout is 60 minutes.
12.7.3. Disassociating a Profile from a UCS Blade
1. Log in to the CloudPlatform UI as administrator.
2. In the left navigation bar, click Infrastructure, then click Zones.
3. Click the name of a zone where you have registered a UCS Manager.
4. Click the Compute and Storage tab.
5. Scroll down in the diagram and click UCS.
6. Click the name of the UCS Manager.
A list is displayed that shows the names of the blades that are installed under the selected
manager.
7. Select the name of a blade that has been associated with a profile.
8.
In the Actions column, click the Disassociate Profile icon.
You might need to wait a few minutes for this operation to finish. The operation might take a long
time, depending on the complexity of the setup. The timeout is 60 minutes.
12.8. Changing Host Password
The password for a XenServer Node, KVM Node, or vSphere Node may be changed in the database.
Note that all Nodes in a Cluster must have the same password.
To change a Node's password:
1. Identify all hosts in the cluster.
2. Change the password on all hosts in the cluster. Now the password for the host and the password
known to CloudPlatform will not match. Operations on the cluster will fail until the two passwords
match.
3. Get the list of host IDs for the host in the cluster where you are changing the password. You will
need to access the database to determine these host IDs. For each hostname "h" (or vSphere
cluster) that you are changing the password for, execute: