Step 1 | UCS-A#
scope org
org-name
|
Enters organization mode for the specified organization. To enter
the root organization mode, type
/
as the
org-name
.
|
Step 2 | UCS-A /org #
create boot-policy
policy-name
[purpose
{operational |
utility}]
|
Creates a boot policy with the specified policy name, and enters
organization boot policy mode.
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.
When you create the boot policy, specify the
operational
option. This ensures that the server
boots from the operating system installed on the server. The
utility
options is reserved and should only be
used if instructed to do so by a Cisco representative.
|
Step 3 | UCS-A /org/boot-policy #
set descr
description
| (Optional)
Provides a description for the boot policy.
Note
|
If your description includes spaces, special characters, or
punctuation, you must begin and end your description with quotation marks. The
quotation marks do not appear in the description field of any
show command output.
|
|
Step 4 | UCS-A /org/boot-policy #
set enforce-vnic-name
{no |
yes}
| (Optional)
If you choose yes, Cisco UCS Manager reports whether the device name specified in the boot policy matches what is specified in the service profile.
If you choose no, Cisco UCS Manager uses any vNIC, vHBA, or iSCSI device from the service profile and does not report whether the device name specified in the boot policy matches what is specified in the service profile.
|
Step 5 | UCS-A /org/boot-policy #
set reboot-on-update
{no |
yes}
|
Specifies whether the servers using this boot policy are
automatically rebooted after you make changes to the boot order.
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 6 | UCS-A /org/boot-policy #
create iscsi
|
Adds an iSCSI boot to the boot policy.
|
Step 7 | UCS-A /org/boot-policy/iscsi #
create path {primary | secondary}
|
Specifies the primary and secondary paths that Cisco UCS Manager uses to reach the iSCSI target .With iSCSI boot, you set up two paths. Cisco UCS Manager uses the primary path first, and if that fails, then it uses the secondary path.
|
Step 8 | UCS-A /org/boot-policy/iscsi/path #
create iscsivnicname iscsi-vnic-name
|
Creates an iSCSI vNIC.
|
Step 9 | UCS-A /org/boot-policy/iscsi/path #
exit
|
Exits iSCSI path mode.
|
Step 10 | UCS-A /org/boot-policy/iscsi/path #
set order order-num
|
Specifies the order for the iSCSI boot in the boot order.
|
Step 11 | Repeat steps 8-10 to create secondary iSCSI vNICs.
| (Optional)
|
Step 12 | UCS-A /org/boot-policy/iscsi #
commit-buffer
|
Commits the transaction to the system configuration.
|