Step 1 |
In the Navigation pane, click the Servers tab. |
Step 2 |
On the Servers tab, expand . |
Step 3 |
Expand the node for the organization that includes the service profile for which you want to change the boot order. If the system does not include multi-tenancy, expand the root node. |
Step 4 |
Click the service profile for which you want to change the boot order. |
Step 5 |
In the Work pane, click the Boot Order tab. |
Step 6 |
Click Modify Boot Policy to change the existing boot policy. |
Step 7 |
In the Modify Boot Policy dialog box, choose one of the following from the Boot Policy drop-down list:
Option |
Description |
Select Boot Policy to use |
Assigns the default boot policy to this service profile. Continue with Step 14. |
Create a Specific Boot Policy |
Enables you to create a local boot policy that can only be accessed by this service profile. Continue with Step 8. |
Boot Policies Policy_Name |
Assigns an existing boot policy to the service profile. If you choose this option, Cisco UCS Manager displays the details of the policy. If you do not want use any of the existing policies, but instead want to create a policy that all service profiles can access, click Create Boot Policy and continue with Step 2. Otherwise, continue with Step 14. |
|
Step 8 |
If you chose to create a boot policy, in the Create Boot Policy dialog box, enter a unique name and description for the policy. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. |
Step 9 |
(Optional)To reboot all servers that use this boot policy after you make changes to the boot order, check the Reboot on Boot Order Change check box. In the Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not directly affect the boot order and the server does not reboot. |
Step 10 |
(Optional)If desired, check the Enforce vNIC/vHBA/iSCSI Name check box.
-
If checked, Cisco UCS Manager displays a configuration error and reports whether one or more of the vNICs, vHBAs, or iSCSI vNICs listed in the Boot Order table match the server configuration in the service profile.
-
If not checked, Cisco UCS Manager uses the vNICs, vHBAs, or iSCSI vNICs (as appropriate for the boot option) from the server configuration in the service profile. It does not report whether the vNICs, vHBAs, or iSCSI vNICs specified in the boot policy match the server configuration in the service profile.
|
Step 11 |
To add a local disk, virtual CD-ROM, or virtual floppy to the boot order, do the following:
-
Click the down arrows to expand the Local Devices area.
-
Click one of the following links to add the device to the Boot Order table:
-
Add Local Disk
-
Add CD-ROM
-
Add Floppy
-
Add another boot device to the Boot Order table, or click OK to finish.
|
Step 12 |
To add a LAN boot to the boot order, do the following:
-
Click the down arrows to expand the vNICs area.
-
Click the Add LAN Boot link.
-
In the Add LAN Boot dialog box, enter the name of the vNIC that you want to use for the LAN boot in the vNIC field, then click OK.
-
Add another device to the Boot Order table, or click OK to finish.
|
Step 13 |
To add a SAN boot to the boot order, do the following:
-
Click the down arrows to expand the vHBAs area.
-
Click the Add SAN Boot link.
-
In the Add SAN Boot dialog box, complete the following fields, and click OK:
Name |
Description |
vHBA field |
Enter the name of the vHBA you want to use for the SAN boot. |
Type field |
This can be one of the following:
-
Primary—The first address defined for the associated boot device class. A boot policy can only have one primary LAN, SAN, or iSCSI boot location.
-
Secondary—The second address defined for the associated boot device class. Each boot policy can have only one secondary LAN or SAN boot location.
The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order. |
-
If this vHBA points to a bootable SAN image, click the
Add SAN Boot Target link and, in the Add SAN Boot Target dialog box, complete the following fields, then click OK:
Name |
Description |
Boot Target LUN field |
The LUN that corresponds to the location of the boot image. |
Boot Target WWPN field |
The WWPN that corresponds to the location of the boot image. |
Type field |
This can be one of the following:
-
Primary—The first address defined for the associated boot device class. A boot policy can only have one primary LAN, SAN, or iSCSI boot location.
-
Secondary—The second address defined for the associated boot device class. Each boot policy can have only one secondary LAN or SAN boot location.
The use of the terms primary or secondary boot devices does not imply a boot order. The effective order of boot devices within the same device class is determined by PCIe bus scan order. |
-
Add another boot device to the Boot Order table, or click OK to finish.
|
Step 14 |
Click OK. |