Configuring Server Boot

This chapter includes the following sections:

• Boot Policy, page 1

• UEFI Boot Mode, page 2
• UEFI Secure Boot, page 3
• CIMC Secure Boot, page 3
• Creating a Boot Policy, page 5
• SAN Boot, page 7
• iSCSI Boot, page 10
• LAN Boot, page 42
• Local Devices Boot, page 43
• Deleting a Boot Policy, page 50
• UEFI Boot Parameters, page 50

Boot Policy
The Cisco UCS Manager boot policy overrides the boot order in the BIOS setup menu, and determines the
following:
• Selection of the boot device
• Location from which the server boots
• Order in which boot devices are invoked

For example, you can choose to have associated servers boot from a local device, such as a local disk or
CD-ROM (VMedia), or you can select a SAN boot or a LAN (PXE) boot.
You can either create a named boot policy that can be associated with one or more service profiles, or create
a boot policy for a specific service profile. A boot policy must be included in a service profile, and that service
profile must be associated with a server for it to take effect. If you do not include a boot policy in a service
profile, Cisco UCS Manager applies the default boot policy.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

1
 Configuring Server Boot
UEFI Boot Mode

Note Changes to a boot policy might be propagated to all servers created with an updating service profile
template that includes that boot policy. Reassociation of the service profile with the server to rewrite the
boot order information in the BIOS is automatically triggered.

UEFI Boot Mode

Unified Extensible Firmware Interface (UEFI) is a specification that defines a software interface between an
operating system and platform firmware. Cisco UCS Manager uses UEFI to replace the BIOS firmware
interfaces. This allows the BIOS to run in UEFI mode while still providing legacy support.
You can choose either legacy or UEFI boot mode when you create a boot policy. Legacy boot mode is supported
for all Cisco UCS servers. UEFI boot mode is supported only on M3 and M4 servers, and allows you to enable
UEFI secure boot mode.
The following limitations apply to the UEFI boot mode:
• UEFI boot mode is only supported on Cisco UCS B-Series M3 and M4 Blade Servers and Cisco UCS
C-Series M3 and M4 Rack Servers.
• UEFI boot mode is not supported with the following combinations:
◦Gen-3 Emulex & QLogic adapters on Cisco UCS blade & rack servers integrated with Cisco UCS
Manager.
◦PXE boot for all adapters on Cisco UCS rack servers integrated with Cisco UCS Manager.
◦iSCSI boot for all adapters on Cisco UCS rack servers integrated with Cisco UCS Manager.

• If you want to use UEFI boot mode with two iSCSI LUNs, you must manually specify a common iSCSI
initiator name in the service profile that is applied to both underlying iSCSI eNICs rather than allowing
Cisco UCS Manager to select the name from an IQN suffix pool. If you do not supply a common name,
Cisco UCS Manager will not be able to detect the second iSCSI LUN.
• You cannot mix UEFI and legacy boot mode on the same server.
• The server will boot correctly in UEFI mode only if the boot devices configured in the boot policy have
UEFI-aware operating systems installed. If a compatible OS is not present, the boot device is not displayed
on the Actual Boot Order tab in the Boot Order Details area.
• In some corner cases, the UEFI boot may not succeed because the UEFI boot manager entry was not
saved correctly in the BIOS NVRAM. You can use the UEFI shell to enter the UEFI boot manager entry
manually. This situation could occur in the following situations:
◦If a blade server with UEFI boot mode enabled is disassociated from the service profile, and the
blade is manually powered on using the Equipment tab or the front panel.
◦If a blade server with UEFI boot mode enabled is disassociated from the service profile, and a
direct VIC firmware upgrade is attempted.
◦If a blade or rack server with UEFI boot mode enabled is booted off SAN LUN, and the service
profile is migrated.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

2
 Configuring Server Boot
UEFI Secure Boot

UEFI Secure Boot

Cisco UCS Manager supports UEFI secure boot on Cisco UCS B-Series M3 and M4 Blade servers and Cisco
UCS C-Series M3 and M4 Rack servers. When UEFI secure boot is enabled, all executables, such as boot
loaders and adapter drivers, are authenticated by the BIOS before they can be loaded. To be authenticated,
the images must be signed by either the Cisco Certificate Authority (CA) or a Microsoft CA.
The following limitations apply to UEFI secure boot:
• UEFI boot mode must be enabled in the boot policy.
• The Cisco UCS Manager software and the BIOS firmware must be at Release 2.2 or greater.

Note UEFI boot mode is supported on Cisco UCS C-Series rack servers beginning with
Release 2.2(3a).

• User-generated encryption keys are not supported.

• UEFI secure boot can only be controlled by Cisco UCS Manager.
• If you want to downgrade to an earlier version of Cisco UCS Manager, and you have a server in secure
boot mode, you must disassociate and reassociate the server before downgrading. Otherwise, the server
will not be discovered successfully.

CIMC Secure Boot

With CIMC secure boot, only Cisco signed firmware images can be installed and run on the servers. When
the CIMC is updated, the image is certified before the firmware is flashed. If certification fails, the firmware
is not flashed. This prevents unauthorized access to the CIMC firmware.

Guidelines and Limitations for CIMC Secure Boot

• CIMC secure boot is supported on Cisco UCS M3 rack servers.

Note CIMC secure boot is enabled by default on the Cisco UCS C220 M4 and C240 M4 rack
servers, and is automatically enabled on the Cisco UCS C460 M4 rack server after
upgrading to CIMC firmware release 2.2(3).

• After CIMC secure boot is enabled, it cannot be disabled.

• After CIMC secure boot is enabled on a server, you cannot downgrade to a CIMC firmware image prior
to 2.1(3).

Cisco UCS Manager CLI Configuration Guide, Release 2.2

3
 Configuring Server Boot
Determining the CIMC Secure Boot Status

Determining the CIMC Secure Boot Status

Procedure

Command or Action Purpose

Step 1 UCS-A# scope server Enters server mode for the specified server.
server-num
Step 2 UCS-A /chassis/server # scope Enters server CIMC mode.
cimc
Step 3 UCS-A /server/cimc # show Displays the CIMC secure boot status for the specified server.
secure-boot This can be one of the following:
• Unsupported—CIMC secure boot is not supported on
the server.
• Disabled—CIMC secure boot is supported, but is
disabled on the server.
• Enabling—CIMC secure boot has been enabled, and the
operation is in process.
• Enabled—CIMC secure boot is enabled on the server.

The following example shows how to display the CIMC secure boot status:
UCS-A# scope server 1
UCS-A /chassis/server # scope cimc
UCS-A /chassis/server/cimc # show secure-boot
Secure Boot: Disabled
UCS-A /chassis/server/cimc #

Enabling CIMC Secure Boot

Procedure

Command or Action Purpose

Step 1 UCS-A# scope server server-num Enters server mode for the specified server.

Step 2 UCS-A /chassis/server # scope cimc Enters server CIMC mode.

Step 3 UCS-A /server/cimc # enable Enables CIMC secure boot status for the specified
secure-boot server. CIMC secure boot is only supported on Cisco
UCS M3 rack servers.
Note Once enabled, CIMC secure boot cannot be
disabled.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

4
 Configuring Server Boot
Creating a Boot Policy

Command or Action Purpose

Step 4 UCS-A /server/cimc # commit-buffer Commits the transaction to the system configuration.

The following example shows how to enable CIMC secure boot and commit the transaction:
UCS-A# scope server 1
UCS-A /chassis/server # scope cimc
UCS-A /chassis/server/cimc # enable secure-boot
Warning: When committed, CIMC Secure Boot and Installation Feature will be enabled for the
server.
This is an irreversible operation!!

UCS-A /chassis/server/cimc* # commit-buffer

UCS-A /chassis/server/cimc #

Creating a Boot Policy

You can also create a local boot policy that is restricted to a service profile or service profile template. However,
we recommend that you create a global boot policy that can be included in multiple service profiles or service
profile templates.

Before You Begin

If you are creating a boot policy that boots the server from a SAN LUN and you require reliable SAN boot
operations, you must first remove all local disks from servers associated with a service profile that includes
the boot policy.

Note This does not apply for Cisco UCS M3 and M4 servers.

Procedure

Command or Action Purpose

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 Creates a boot policy with the specified policy name, and
policy-name [purpose {operational enters organization boot policy mode.
| utility}] 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 (Optional)

descr description Provides a description for the boot policy.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

5
 Configuring Server Boot
Creating a Boot Policy

Command or Action Purpose

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 Specifies whether the servers using this boot policy are
reboot-on-update {no | yes} automatically rebooted after you make changes to the boot
order.

Step 5 UCS-A /org/boot-policy # set If you choose yes, Cisco UCS Manager displays a
enforce-vnic-name {no | yes} 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 you choose no, Cisco UCS Manager uses the vNICs,
vHBAs, or iSCSI vNICs (as appropriate for the boot option)
from the service profile.

Step 6 UCS-A /org/boot-policy # set Specifies whether the servers using this boot policy are using
boot-mode {legacy | uefi} UEFI or legacy boot mode.

Step 7 UCS-A /org/boot-policy # Commits the transaction to the system configuration.

commit-buffer
Step 8 UCS-A /org/boot-policy # create Enters boot security mode for the specified boot policy.
boot-security
Step 9 UCS-A Specifies whether secure boot is enabled for the boot policy.
/org/boot-policy/boot-security # set
secure-boot {no | yes}
Step 10 UCS-A Commits the transaction to the system configuration.
/org/boot-policy/boot-security #
commit-buffer

The following example shows how to create a boot policy named boot-policy-LAN, specify that servers using
this policy will not be automatically rebooted when the boot order is changed, set the UEFI boot mode, enable
UEFI boot security, and commit the transaction:
UCS-A# scope org /
UCS-A /org* # create boot-policy boot-policy-LAN purpose operational
UCS-A /org/boot-policy* # set descr "Boot policy that boots from the LAN."
UCS-A /org/boot-policy* # set reboot-on-update no
UCS-A /org/boot-policy* # set boot-mode uefi
UCS-A /org/boot-policy* # commit-buffer
UCS-A /org/boot-policy # create boot-security
UCS-A /org/boot-policy/boot-security* # set secure-boot yes
UCS-A /org/boot-policy/boot-security* # commit-buffer
UCS-A /org/boot-policy/boot-security #

What to Do Next
Configure one or more of the following boot options for the boot policy and set their boot order:

Cisco UCS Manager CLI Configuration Guide, Release 2.2

6
 Configuring Server Boot
SAN Boot

• LAN Boot —Boots from a centralized provisioning server. It is frequently used to install operating
systems on a server from that server.
If you choose the LAN Boot option, continue to Configuring a LAN Boot for a Boot Policy, on page
42.
• SAN Boot —Boots from an operating system image on the SAN. You can specify a primary and a
secondary SAN boot. If the primary boot fails, the server attempts to boot from the secondary.
We recommend that you use a SAN boot policy, because it offers the most service profile mobility
within the system. If you boot from the SAN, when you move a service profile from one server to another,
the new server boots from exactly the same operating system image. Therefore, the new server appears
to be exactly the same server to the network.
If you choose the SAN Boot option, continue to Configuring a SAN Boot for a Boot Policy, on page
8.
• Virtual Media Boot —Mimics the insertion of a physical CD into a server. It is typically used to
manually install operating systems on a server.
If you choose the Virtual Media boot option, continue to Configuring a Virtual Media Boot for a Boot
Policy, on page 47.

Tip If you configure a local disk and a SAN LUN for the boot order storage type and the operating system or
logical volume manager (LVM) is configured incorrectly, the server might boot from the local disk rather
than the SAN LUN.
For example, on a server with Red Hat Linux installed, where the LVM is configured with default LV
names and the boot order is configured with a SAN LUN and a local disk, Linux reports that there are
two LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local
disk.

Include the boot policy in a service profile and/or template.

SAN Boot
You can configure a boot policy to boot one or more servers from an operating system image on the SAN.
The boot policy can include a primary and a secondary SAN boot. If the primary boot fails, the server attempts
to boot from the secondary.
We recommend that you use a SAN boot, because it offers the most service profile mobility within the system.
If you boot from the SAN when you move a service profile from one server to another, the new server boots
from the exact same operating system image. Therefore, the new server appears to be the exact same server
to the network.
To use a SAN boot, ensure that the following is configured:
• The Cisco UCS domain must be able to communicate with the SAN storage device that hosts the operating
system image.
• A boot target LUN (Logical Unit Number) on the device where the operating system image is located.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

7
 Configuring Server Boot
Configuring a SAN Boot for a Boot Policy

Note SAN boot is not supported on Gen-3 Emulex adapters on Cisco UCS blade & rack servers.

Configuring a SAN Boot for a Boot Policy

Tip If you configure a local disk and a SAN LUN for the boot order storage type and the operating system or
logical volume manager (LVM) is configured incorrectly, the server might boot from the local disk rather
than the SAN LUN.
For example, on a server with Red Hat Linux installed, where the LVM is configured with default LV
names and the boot order is configured with a SAN LUN and a local disk, Linux reports that there are
two LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local
disk.

This procedure continues directly from Creating a Boot Policy.

Before You Begin

Create a boot policy to contain the SAN boot configuration.

Note If you are creating a boot policy that boots the server from a SAN LUN and you require reliable SAN
boot operations, we recommend that you first remove all local disks from servers associated with a service
profile that includes the boot policy.
This does not apply for Cisco UCS M3 and M4 servers.

Beginning with Release 2.2, all SAN boot-related CLI commands have been moved to the SAN scope. Any
existing scripts from previous releases that use SAN boot under the storage scope instead of org/boot-policy/san
or org/service-profile/boot-definition/san should be updated.

Procedure

Command or Action Purpose

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 # scope boot-policy Enters organization boot policy mode for the specified boot
policy-name policy.

Step 3 UCS-A /org/boot-policy # create Creates a SAN boot for the boot policy and enters
san organization boot policy storage mode.

Step 4 UCS-A /org/boot-policy/san # set Sets the boot order for the SAN boot. Enter an integer
order order_number between 1 and 16.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

8
Configuring Server Boot
Configuring a SAN Boot for a Boot Policy

Command or Action Purpose

Step 5 UCS-A /org/boot-policy/san # Creates a SAN image location, and if the san-image option
create san-image {primary | is specified, enters organization boot policy storage SAN
secondary} image mode.
When using the enhanced boot order on Cisco UCS M3
servers, or M4 servers, the boot order that you define is
used. For standard boot mode using the terms "primary" or
"secondary" do not imply a boot order. The effective order
of boot devices within the same device class is determined
by the PCIe bus scan order.

Step 6 UCS-A Specifies the vHBA to be used for the SAN boot.
/org/boot-policy/ssn/san-image #
set vhba vhba-name
Step 7 UCS-A Creates a primary or secondary SAN boot path and enters
/org/boot-policy/san/san-image # organization boot policy SAN path mode.
create path {primary | secondary} When using the enhanced boot order on Cisco UCS M3
servers, or M4 servers, the boot order that you define is
used. For standard boot mode using the terms "primary" or
"secondary" do not imply a boot order. The effective order
of boot devices within the same device class is determined
by the PCIe bus scan order.

Step 8 UCS-A Specifies the LUN or WWN to be used for the SAN path
/org/boot-policy/san/san-image/path to the boot image.
# set {lun lun-id | wwn wwn-num}
Step 9 UCS-A Commits the transaction to the system configuration.
/org/boot-policy/san/san-image/path
# commit-buffer

The following example shows how to enter the boot policy named lab1-boot-policy, create a SAN boot for
the policy, set the boot order to 1, create a primary SAN image, use a vHBA named vHBA2, create primary
path using LUN 0, and commit the transaction:
UCS-A# scope org /
UCS-A /org* # scope boot-policy lab1-boot-policy
UCS-A /org/boot-policy # create san
UCS-A /org/boot-policy/san* # set order 1
UCS-A /org/boot-policy/san* # create san-image primary
UCS-A /org/boot-policy/san/san-image* # set vhba vHBA2
UCS-A /org/boot-policy/san/san-image* # create path primary
UCS-A /org/boot-policy/san/san-image/path* # set lun 0
UCS-A /org/boot-policy/san/san-image/path* # commit-buffer
UCS-A /org/boot-policy/san/san-image/path #

The following example shows how to create a SAN boot for the service profile SP_lab1, set the boot order
to 1, create a primary SAN image, use a vHBA named vHBA2, create primary path using LUN 0, and commit
the transaction:
UCS-A# scope org /
UCS-A /org* # scope service-profile SP_lab1
UCS-A /org/service-profile # create boot-definition

Cisco UCS Manager CLI Configuration Guide, Release 2.2

9
 Configuring Server Boot
iSCSI Boot

UCS-A /org/service-profile/boot-definition* # create san

UCS-A /org/service-profile/boot-definition/san* # create san-image primary
UCS-A /org/service-profile/boot-definition/san/san-image* # set vhba vHBA2
UCS-A /org/service-profile/boot-definition/san/san-image* # create path primary
UCS-A /org/service-profile/boot-definition/san/san-image/path* # set lun 0
UCS-A /org/service-profile/boot-definition/san/san-image/path* # commit-buffer
UCS-A /org/service-profile/boot-definition/san/san-image/path #

What to Do Next
Include the boot policy in a service profile and/or template.

iSCSI Boot
iSCSI boot enables a server to boot its operating system from an iSCSI target machine located remotely over
a network.
iSCSI boot is supported on the following Cisco UCS hardware:
• Cisco UCS blade servers that have the Cisco UCS M51KR-B Broadcom BCM57711 network adapter
and use the default MAC address provided by Broadcom.
• Cisco UCS M81KR Virtual Interface Card
• Cisco UCS VIC-1240 Virtual Interface Card
• Cisco UCS VIC-1280 Virtual Interface Card
• Cisco UCS rack servers that have the Cisco UCS M61KR-B Broadcom BCM57712 network adapter.
• Cisco UCS P81E Virtual Interface Card
• Cisco UCS VIC 1225 Virtual Interface Card

There are prerequisites that must be met before you configure iSCSI boot. For a list of these prerequisites,
see iSCSI Boot Guidelines and Prerequisites, on page 11.
For a high-level procedure for implementing iSCSI boot, see Configuring iSCSI Boot, on page 14.

iSCSI Boot Process

Cisco UCS Manager uses the iSCSI vNIC and iSCSI boot information created for the service profile in the
association process to program the adapter, located on the server. After the adapter is programmed, the server
reboots with the latest service profile values. After the power on self-test (POST), the adapter attempts to
initialize using these service profile values. If the adapter can use the values and log in to its specified target,
the adapter initializes and posts an iSCSI Boot Firmware Table (iBFT) to the host memory and a valid bootable
LUN to the system BIOS. The iBFT that is posted to the host memory contains the initiator and target
configuration that is programmed on the primary iSCSI VNIC.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

10
 Configuring Server Boot
iSCSI Boot Guidelines and Prerequisites

Note Previously, the host would see only one of the boot paths configured, depending on which path completed
the LUN discovery first, and would boot from that path. Now, when there are two iSCSI boot vNICs
configured, the host will see both of the boot paths. So for multipath configurations, a single IQN needs
to be configured on both the boot vNICs If there are different IQNs configured on the boot vNICs on a
host, the host will boot with the IQN that is configured on the boot vNIC with the lower PCI order.

The next step, which is the installation of the operating system (OS), requires an OS that is iBFT capable.
During installation of the OS, the OS installer scans the host memory for the iBFT table and uses the information
in the iBFT to discover the boot device and create an iSCSI path to the target LUN. In some OS's a NIC driver
is required to complete this path. If this step is successful, the OS installer finds the iSCSI target LUN on
which to install the OS.

Note The iBFT works at the OS installation software level and might not work with HBA mode (also known
as TCP offload). Whether iBFT works with HBA mode depends on the OS capabilities during installation.
Also, for a server that includes a Cisco UCS M51KR-B Broadcom BCM57711 adapter, the iBFT normally
works at a maximum transmission unit (MTU) size of 1500, regardless of the MTU jumbo configuration.
If the OS supports HBA mode, you might need to set HBA mode, dual-fabric support, and jumbo MTU
size after the iSCSI installation process.

iSCSI Boot Guidelines and Prerequisites

These guidelines and prerequisites must be met before configuring iSCSI boot:
• After the iSCSI boot policies have been created, a user with ls-compute privileges can include them in
a service profile or service profile template. However, a user with only ls-compute privileges cannot
create iSCSI boot policies.
• To set up iSCSI boot from a Windows 2008 server where the second vNIC (failover vNIC) must boot
from an iSCSI LUN, consult Microsoft Knowledge Base Article 976042. Microsoft has a known issue
where Windows might fail to boot from an iSCSI drive or cause a bugcheck error if the networking
hardware is changed. To work around this issue, follow the resolution recommended by Microsoft.
• The storage array must be licensed for iSCSI boot and the array side LUN masking must be properly
configured.
• Two IP addresses must be determined, one for each iSCSI initiator. If possible, the IP addresses should
be on the same subnet as the storage array. The IP addresses are assigned statically or dynamically using
the Dynamic Host Configuration Protocol (DHCP).
• You cannot configure boot parameters in the Global boot policy. Instead, after configuring boot
parameters, you need to include the boot policy in the appropriate service profile.
• The operating system (OS) must be iSCSI Boot Firmware Table (iBFT) compatible.
• For Cisco UCS M51KR-B Broadcom BCM57711 network adapters:
◦Servers that use iSCSI boot must contain the Cisco UCS M51KR-B Broadcom BCM57711 network
adapter. For information on installing or replacing an adapter card, see the Cisco UCS B250
Extended Memory Blade Server Installation and Service Note. The service note is accessible from

Cisco UCS Manager CLI Configuration Guide, Release 2.2

11
 Configuring Server Boot
Initiator IQN Configuration

the Cisco UCS B-Series Servers Documentation Roadmap at http://www.cisco.com/go/

unifiedcomputing/b-series-doc.
◦Set the MAC addresses on the iSCSI device.
◦If you are using the DHCP Vendor ID (Option 43), configure the MAC address of an iSCSI device
in /etc/dhcpd.conf.
◦HBA mode (also known as TCP offload) and the boot to target setting are supported. However,
only Windows OS supports HBA mode during installation.
◦Before installing the OS, disable the boot to target setting in the iSCSI adapter policy, then after
installing the OS, reenable the boot to target setting.

Note Each time you change an adapter policy setting, the adapter reboots to apply the new
setting.

◦When installing the OS on the iSCSI target, the iSCSI target must be ordered before the device
where the OS image resides. For example, if you are installing the OS on the iSCSI target from a
CD, the boot order should be the iSCSI target and then the CD.
◦After the server has been iSCSI booted, do not modify the Initiator Name, Target name, LUN,
iSCSI device IP, or Netmask/gateway using the Broadcom tool.
◦Do not interrupt the POST (power on self-test) process or the Cisco UCS M51KR-B Broadcom
BCM57711 network adapter will fail to initialize.

• For Cisco UCS M81KR Virtual Interface Card and Cisco UCS VIC-1240 Virtual Interface Card:
◦Do not set MAC addresses on the iSCSI device.
◦HBA mode and the boot to target setting are not supported.
◦When installing the OS on the iSCSI target, the iSCSI target must be ordered after the device where
the OS image resides. For example, if you are installing the OS on the iSCSI target from a CD,
the boot order should be the CD and then the iSCSI target.
◦If you are using the DHCP Vendor ID (Option 43), the MAC address of the overlay vNIC needs
to be configured in /etc/dhcpd.conf.
◦After the server has been iSCSI booted, do not modify the IP details of the overlay vNIC.

• The VMware ESX/ESXi operating system does not support storing a core dump file to an iSCSI boot
target LUN. Dump files must be written to a local disk.

Initiator IQN Configuration

Cisco UCS uses the following rules to determine the initiator IQN for an adapter iSCSI vNIC at the time a
service profile is associated with a physical server:
• An initiator IQN at the service profile level and at the iSCSI vNIC level cannot be used together in a
service profile.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

12
 Configuring Server Boot
Enabling MPIO on Windows

• If an initiator IQN is specified at the service profile level, all of the adaptor iSCSI vNICs are configured
to use the same initiator IQN, except in the case of DHCP Option 43, where the initiator IQN is set to
empty on the adapter iSCSI vNIC.
• When an initiator IQN is set at the iSCSI vNIC level, the initiator IQN at the service profile level is
removed, if one is present.
• If there are two iSCSI vNIC in a service profile and only one of them has the initiator IQN set, the second
one is configured with the default IQN pool. You can change this configuration later. The only exception
is if DHCP Option 43 is configured. In this case, the initiator IQN on the second iSCSI vNIC is removed
during service profile association.

Note If you change an iSCSI vNIC to use the DHCP Option 43 by setting the vendor ID, it
does not remove the initiator IQN configured at the service profile level. The initiator
IQN at the service profile level can still be used by another iSCSI vNIC which does not
use the DHCP Option 43.

Enabling MPIO on Windows

Note If you change the networking hardware, Windows may fail to boot from an iSCSI drive. For more
information, see Microsoft support Article ID: 976042.

Before You Begin

The server on which you enable MPIO must have a Cisco VIC driver.
If there are multiple paths configured to the boot LUN, only one path should be enabled when the LUN is
installed.

Procedure

Step 1 In the service profile associated with the server, configure the primary iSCSI vNIC.
For more information, see Creating an iSCSI vNIC in a Service Profile, on page 24.

Step 2 Using the primary iSCSI vNIC, install the Windows operating system on the iSCSI target LUN.
Step 3 After Windows installation is completed, enable MPIO on the host.
Step 4 In the service profile associated with the server, add the secondary iSCSI vNIC to the boot policy.
For more information, see Creating an iSCSI Boot Policy, on page 20.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

13
 Configuring Server Boot
Configuring iSCSI Boot

Configuring iSCSI Boot

When you configure an adapter or blade in Cisco UCS to iSCSI boot from a LUN target, you need to complete
all of the following steps.

Procedure

Command or Action Purpose

Step 1 Configure the iSCSI boot adapter policy. (Optional)
For more information, see Creating an iSCSI Adapter
Policy, on page 15

Step 2 Configure the authentication profiles to be (Optional)

used by the initiator and target. For more information, see Creating an Authentication
Profile, on page 17

Step 3 If you plan to configure the iSCSI initiator (Optional)

to use an IP address from a pool of IP For more information, see Adding a Block of IP
addresses, add a block of IP addresses to Addresses to the Initiator Pool, on page 19
the iSCSI initiator pool.
Step 4 Create a boot policy that can be used in any For more information about creating a boot policy
service profile. Alternatively, you can that can be used in any service profile, see Creating
create a local boot policy only for the an iSCSI Boot Policy, on page 20.
specific service policy. However, we
recommend that you create a boot policy
that can be shared with multiple service
profiles.
Step 5 If you created a boot policy that can be For more information, see Creating a Service Profile
used in any service profile, you need to Template.
assign it to the service profile. Otherwise,
proceed to the next step.
Step 6 Configure an Ethernet vNIC in a service The Ethernet vNIC is used as the overlay vNIC for
profile. the iSCSI device. For more information, see
Configuring a vNIC for a Service Profile.

Step 7 Create an iSCSI vNIC in a service profile. For more information, see Creating an iSCSI vNIC
in a Service Profile, on page 24

Step 8 Set the iSCSI initiator to boot using a static See either Creating an iSCSI Initiator that Boots
IP Address, an IP address from an IP pool, Using a Static IP Address, on page 26, Creating an
or DHCP. iSCSI Initiator that Boots Using an IP Address from
an IP Pool, on page 28, or Creating an iSCSI
Initiator that Boots Using DHCP, on page 30.

Step 9 Create an iSCSI static or auto target. For more information, see either Creating an iSCSI
Static Target, on page 37 or Creating an iSCSI Auto
Target, on page 40.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

14
 Configuring Server Boot
Creating an iSCSI Adapter Policy

Command or Action Purpose

Step 10 Associate the service profile with a server. For more information, see Associating a Service
Profile with a Blade Server or Server Pool.

Step 11 Verify the iSCSI boot operation. For more information, see Verifying iSCSI Boot,
on page 42

Step 12 Install the OS on the server. For more information, see one of the following
guides:
• Cisco UCS B-Series Blade Servers VMware
Installation Guide
• Cisco UCS B-Series Blade Servers Linux
Installation Guide
• Cisco UCS B-Series Blade Servers Windows
Installation Guide

Step 13 Boot the server.

Creating an iSCSI Adapter Policy

Procedure

Command or Action Purpose

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 iscsi-policy Creates the iSCSI adapter policy.
policy-name
Step 3 UCS-A /org/iscsi-policy # set descr (Optional)
description Provides a description for the iSCSI adapter policy.

Step 4 UCS-A /org/iscsi-policy # set The number of seconds to wait until Cisco UCS assumes
iscsi-protocol-item that the initial login has failed and the iSCSI adapter is
connection-timeout timeout-secs unavailable.
Enter an integer between 0 and 255. If you enter 0, Cisco
UCS uses the value set in the adapter firmware (default:
15 seconds).

Step 5 UCS-A /org/iscsi-policy # set The number of seconds to wait before the initiator assumes
iscsi-protocol-item dhcp-timeout that the DHCP server is unavailable.
timeout-secs Enter an integer between 60 and 300 (default: 60 seconds).

Cisco UCS Manager CLI Configuration Guide, Release 2.2

15
 Configuring Server Boot
Creating an iSCSI Adapter Policy

Command or Action Purpose

Step 6 UCS-A /org/iscsi-policy # set The number of times to retry the connection in case of a
iscsi-protocol-item failure during iSCSI LUN discovery.
lun-busy-retry-count num Enter an integer between 0 and 60. If you enter 0, Cisco
UCS uses the value set in the adapter firmware (default:
15 seconds).

Step 7 UCS-A /org/iscsi-policy # set Specifies whether to apply a TCP timestamp. With this
iscsi-protocol-item tcp-time-stamp setting, transmitted packets are given a time stamp of when
{no | yes} the packet was sent so that the packet's round-trip time can
be calculated, when needed. This setting applies only to
Cisco UCS M51KR-B Broadcom BCM57711 adapters.

Step 8 UCS-A /org/iscsi-policy # set Specifies whether to enable HBA mode.

iscsi-protocol-item hbamode {no | This option should only be enabled for servers with the
yes} Cisco UCS NIC M51KR-B adapter running the Windows
operating system.

Step 9 UCS-A /org/iscsi-policy # set Specifies whether to boot from the iSCSI target.
iscsi-protocol-item boottotarget {no This option only applies to servers with the Cisco UCS
| yes} NIC M51KR-B adapter. It should be disabled until you
have installed an operating system on the server.

Step 10 UCS-A /org/iscsi-policy # Commits the transaction to the system configuration.

commit-buffer

The following example shows how to create an iSCSI adapter policy called iscsiboot, set the connection
timeout, DHCP timeout, and LUN busy retry count, apply a TCP timestamp, and commit the transaction:
UCS-A# scope org /
UCS-A /org # create iscsi-policy iscsiboot
UCS-A /org/iscsi-policy* # set iscsi-protocol-item connection-timeout 60
UCS-A /org/iscsi-policy* # set iscsi-protocol-item dhcp-timeout 200
UCS-A /org/iscsi-policy* # set iscsi-protocol-item lun-busy-retry-count 5
UCS-A /org/iscsi-policy* # set iscsi-protocol-item tcp-time-stamp yes
UCS-A /org/iscsi-policy* # set iscsi-protocol-item hbamode yes
UCS-A /org/iscsi-policy* # set iscsi-protocol-item boottotarget yes
UCS-A /org/iscsi-policy* # commit-buffer
UCS-A /org/iscsi-policy #

What to Do Next
Include the adapter policy in a service profile and/or template.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

16
 Configuring Server Boot
Deleting an iSCSI Adapter Policy

Deleting an iSCSI Adapter Policy

Procedure

Command or Action Purpose

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 # delete iscsi-policy Deletes the iSCSI adapter policy.
policy-name
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.

The following example shows how to delete an iSCSI adapter policy named iscsi-adapter-pol and commit the
transaction:
UCS-A# scope org /
UCS-A /org # delete iscsi-policy iscsi-adapter-pol
UCS-A /org* # commit-buffer
UCS-A /org #

Creating an Authentication Profile

If you use authentication for iSCSI boot, you need to create an authentication profile for both the initiator and
target.

Procedure

Command or Action Purpose

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 auth-profile Creates an authentication profile with the
profile-name specified name. The name can be up to 16
alphanumeric characters.

Step 3 UCS-A /org/auth-profile* # set user-id Creates a log in for authentication.

id-name
Step 4 UCS-A /org/auth-profile* # set password Creates a password for authentication.

Step 5 UCS-A /org/auth-profile* # commit-buffer Commits the transaction to the system

configuration.

Step 6 UCS-A /org/auth-profile* # exit Exits the current mode.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

17
 Configuring Server Boot
Deleting an Authentication Profile

Command or Action Purpose

Step 7 Repeat steps 2 through 6 to create an
authentication profile for the target.

The following example shows how to create an authentication profile for an initiator and target and commit
the transaction:

UCS-A# scope org

UCS-A /org # create auth-profile InitAuth
UCS-A /org/auth-profile* # set user-id init
UCS-A /org/auth-profile* # set password
Enter a password:
Confirm the password:
UCS-A /org/auth-profile* # commit-buffer
UCS-A /org/auth-profile # exit
UCS-A /org # create auth-profile TargetAuth
UCS-A /org/auth-profile* # set user-id target
UCS-A /org/auth-profile* # set password
Enter a password:
Confirm the password:
UCS-A /org/auth-profile* # commit-buffer
UCS-A /org/auth-profile # exit

What to Do Next
Create an Ethernet vNIC to be used as the overlay vNIC for the iSCSI device, and then create an iSCSI vNIC.

Deleting an Authentication Profile

Procedure

Command or Action Purpose

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 # delete auth-profile Deletes the specified authentication profile.
auth-profile-name
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.

The following example shows how to delete an authentication profile called iscsi-auth and commit the
transaction:
UCS-A# scope org
UCS-A /org # delete auth-profile iscsi-auth
UCS-A /org* # commit-buffer
UCS-A /org #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

18
 Configuring Server Boot
Adding a Block of IP Addresses to the Initiator Pool

Adding a Block of IP Addresses to the Initiator Pool

You can create a group of IP addresses to be used for iSCSI boot. Cisco UCS Manager reserves the block of
IP addresses you specify.
The IP pool must not contain any IP addresses that have been assigned as static IP addresses for a server or
service profile.

Procedure

Command or Action Purpose

Step 1 UCS-A# scope org org-name Enters the organization mode for the specified
organization. To enter the root organization mode, enter
/ as the org-name.

Step 2 UCS-A /org# scope ip-pool Enters the mode to specify an iSCSI initiator pool.
iscsi-initiator-pool
Step 3 UCS-A /org/ip-pool # set descr (Optional)
description Provides a description for the IP pool.
Note If your description includes spaces, special
characters, or punctuation, you must begin and
end your description with quotation marks. The
quotation marks will not appear in the
description field of any show command output.
Step 4 UCS-A /org/ip-pool # set This can be one of the following:
assignmentorder {default |
sequential} • default—Cisco UCS Manager selects a random
identity from the pool.
• sequential—Cisco UCS Manager selects the lowest
available identity from the pool.

Step 5 UCS-A /org/ip-pool# create block Creates a block of IP addresses for the iSCSI initiator.
from_ip_address to_ip_address
default_gateway subnet_mask
Step 6 UCS-A/org/ip-pool/block# show (Optional)
detail expand Shows the block of IP addresses that you have created.

Step 7 UCS-A /org/ip-pool/block # Commits the transaction to the system configuration.

commit-buffer

The following example shows how to create an IP initiator pool for the iSCSI vNIC and commit the transaction:

UCS-A # scope org /

UCS-A /org # scope ip-pool iscsi-initiator-pool
UCS-A /org/ip-pool # create block 40.40.40.10 40.40.40.50 40.40.40.1 255.0.0.0
UCS-A /org/ip-pool/block # show detail expand
Block of IP Addresses:
From: 40.40.40.10

Cisco UCS Manager CLI Configuration Guide, Release 2.2

19
 Configuring Server Boot
Deleting a Block of IP Addresses from the Initiator Pool

To: 40.40.40.50
Default Gateway: 40.40.40.1
Subnet Mask: 255.0.0.0
UCS-A /org/ip-pool/block # commit buffer

What to Do Next
Configure one or more service profiles or service profile templates to obtain the iSCSI initiator IP address
from the iSCSI initiator IP pool.

Deleting a Block of IP Addresses from the Initiator Pool

Procedure

Command or Action Purpose

Step 1 UCS-A# scope org org-name Enters the organization mode for the specified
organization. To enter the root organization mode,
enter / as the org-name.

Step 2 UCS-A /org# scope ip-pool Enters the mode to specify an iSCSI initiator pool.
iscsi-initiator-pool
Step 3 UCS-A /org/ip-pool# delete block Deletes the specified block of IP addresses from
from_ip_address to_ip_address the initiator pool.

Step 4 UCS-A/org/ip-pool/block# show detail (Optional)

expand Shows that the block of IP addresses has been
deleted.

Step 5 UCS-A /org/ip-pool# commit buffer Commits the transaction to the system
configuration.

The following example shows how to delete a block of IP addresses from the initiator pool and commit the
transaction:

UCS-A # scope org /

UCS-A /org # scope ip-pool iscsi-initiator-pool
UCS-A /org/ip-pool # delete block 40.40.40.10 40.40.40.50 40.40.40.1 255.0.0.0
UCS-A /org/ip-pool # show detail expand

IP Pool:
Name: iscsi-initiator-pool
Size: 0
Assigned: 0
Descr:
UCS-A /org/ip-pool # commit buffer

Creating an iSCSI Boot Policy

You can add up to two iSCSI vNICs per boot policy. One vNIC acts as the primary iSCSI boot source, and
the other acts as the secondary iSCSI boot source.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

20
Configuring Server Boot
Creating an iSCSI Boot Policy

Procedure

Command or Action Purpose

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 Creates a boot policy with the specified policy name, and enters
policy-name [purpose organization boot policy mode.
{operational | utility}] 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 (Optional)

descr description 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 (Optional)
enforce-vnic-name {no | yes} 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 Specifies whether the servers using this boot policy are
reboot-on-update {no | yes} 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 Adds an iSCSI boot to the boot policy.
iscsi
Step 7 UCS-A /org/boot-policy/iscsi # Specifies the primary and secondary paths that Cisco UCS
create path {primary | Manager uses to reach the iSCSI target .With iSCSI boot, you
secondary}

Cisco UCS Manager CLI Configuration Guide, Release 2.2

21
 Configuring Server Boot
Creating an iSCSI Boot Policy

Command or Action Purpose

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 Creates an iSCSI vNIC.

# create iscsivnicname
iscsi-vnic-name
Step 9 UCS-A /org/boot-policy/iscsi/path Exits iSCSI path mode.
# exit
Step 10 UCS-A /org/boot-policy/iscsi/path Specifies the order for the iSCSI boot in the boot order.
# set order order-num
Step 11 Repeat steps 8-10 to create (Optional)
secondary iSCSI vNICs.
Step 12 UCS-A /org/boot-policy/iscsi # Commits the transaction to the system configuration.
commit-buffer

The following example shows how to create an iSCSI boot policy named iscsi-boot-policy-LAN, provide a
description for the boot policy, specify that servers using this policy are not automatically rebooted when the
boot order is changed, set the boot order for iSCSI boot to 2, create an iSCSI boot and associate it with a vNIC
called iscsienic1, and commit the transaction:
UCS-A# scope org /
UCS-A /org* # create boot-policy iscsi-boot-policy-LAN purpose operational
UCS-A /org/boot-policy* # set descr "Boot policy that boots from iSCSI."
UCS-A /org/boot-policy* # set enforce-vnic-name yes
UCS-A /org/boot-policy* # set reboot-on-update no
UCS-A /org/boot-policy* # create iscsi
UCS-A /org/boot-policy/iscsi* # create path primary
UCS-A /org/boot-policy/iscsi/path* # set iscsivnicname iscsienic1
UCS-A /org/boot-policy/iscsi/path* # exit
UCS-A /org/boot-policy/iscsi* # set order 2
UCS-A /org/boot-policy/iscsi* # commit-buffer
UCS-A /org/boot-policy #

What to Do Next
Include the boot policy in a service profile and/or template.
After a server is associated with a service profile that includes this boot policy, you can verify the actual boot
order in the Boot Order Details area on the General tab for the server.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

22
 Configuring Server Boot
Deleting iSCSI Devices from a Boot Policy

Deleting iSCSI Devices from a Boot Policy

Procedure

Command or Action Purpose

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 # scope boot-policy Enters boot policy organization mode for the
boot-pol-name specified boot policy.

Step 3 UCS-A /org/boot-policy # delete iscsi Deletes the iSCSI boot from the boot policy.

Step 4 UCS-A /org/boot-policy # Commits the transaction to the system configuration.

commit-buffer

The following example shows how to delete an iSCSI boot from the boot policy named boot-policy-iscsi and
commit the transaction:
UCS-A# scope org /
UCS-A /org # scope boot-policy boot-policy-iscsi
UCS-A /org/boot-policy # delete iscsi
UCS-A /org/boot-policy* # commit-buffer
UCS-A /org/boot-policy #

Setting an Initiator IQN at the Service Profile Level

In a service profile, you can create an initiator with a specific IQN or one that is derived from a pool of IQNs.

Before You Begin

You cannot delete an IQN using the CLI.
To understand the initiator IQN configuration guidelines, see Initiator IQN Configuration, on page 12.

Procedure

Command or Action Purpose

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 # scope service-profile profile-name Enters service profile organization mode
for the service profile.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

23
 Configuring Server Boot
Creating an iSCSI vNIC in a Service Profile

Command or Action Purpose

Step 3 UCS-A /org/service-profile# set iscsi-identity Creates an initiator with the specified
{initiator name. The name can be up to 16
nameinitiator-name|initiator-pool-namepool-name} alphanumeric characters.

Step 4 UCS-A /org/service-profile* # commit buffer Commits the transaction to the system
configuration.

Step 5 UCS-A /org/auth-profile* # exit Exits the current mode.

The following example shows how to create a specific name for an iSCSI initiator and commit the transaction:

UCS-A# scope org /

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # set iscsi-identity initiator-name manual:IQN
UCS-A /org/service-profile* # commit-buffer

Creating an iSCSI vNIC in a Service Profile

You can create an iSCSI vNIC in a service profile.

Before You Begin

You must have an Ethernet vNIC in a service profile to be used as the overlay vNIC for the iSCSI device.

Procedure

Command or Action Purpose

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 # scope service-profile Enters service profile organization mode for the service
profile-name profile.

Step 3 UCS-A /org/service-profile # create Specifies the iSCSI vNIC name.

vnic-iscsi iscsi-vnic-name .
Step 4 UCS-A /org/service-profile/vnic-iscsi* # (Optional)
set iscsi-adaptor-policy Specifies the iSCSI adapter policy that you have
iscsi-adaptor-name created for this iSCSI vNIC.

Step 5 UCS-A /org/service-profile/vnic-iscsi* # (Optional)

set auth-name Sets the authentication profile to be used by the iSCSI
authentication-profile-name vNIC. The authentication profile must already exist
for it to be set. For more information, see Creating an
Authentication Profile, on page 17.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

24
Configuring Server Boot
Creating an iSCSI vNIC in a Service Profile

Command or Action Purpose

Step 6 UCS-A /org/service-profile/vnic-iscsi* # Specifies the MAC address for the iSCSI vNIC.
set identity { dynamic-mac Note The MAC address is only set for Cisco UCS
{dynamic-mac-address | derived } | NIC M51KR-B adapters.
mac-pool mac-pool-name }
Step 7 UCS-A /org/service-profile/vnic-iscsi* # Specifies the name of the iSCSI initiator or the name
set iscsi-identity {initiator-name of an IQN pool from which the iSCSI initiator name
initiator-name | initiator-pool-name will be provided. The iSCSI initiator name can be up
iqn-pool-name} to 223 characters.

Step 8 UCS-A /org/service-profile/vnic-iscsi* # Specifies the Ethernet vNIC that is used by the iSCSI
set overlay-vnic-name device as the overlay vNIC. For more information, see
overlay-vnic-name Configuring a vNIC for a Service Profile.

Step 9 UCS-A /org/service-profile/vnic-iscsi* # Creates an Ethernet interface for a VLAN assigned to

create eth-if the iSCSI vNIC.

Step 10 UCS-A Specifies the VLAN name. The default VLAN is

/org/service-profile/vnic-iscsi/eth-if* # default. For the Cisco UCS M81KR Virtual Interface
set vlanname vlan-name. Card and the Cisco UCS VIC-1240 Virtual Interface
Card, the VLAN that you specify must be the same as
the native VLAN on the overlay vNIC. For the Cisco
UCS M51KR-B Broadcom BCM57711 adapter, the
VLAN that you specify can be any VLAN assigned to
the overlay vNIC.

Step 11 UCS-A /org/service-profile/vnic-iscsi # Commits the transaction to the system configuration.

commit-buffer

The following example shows how to create an iSCSI vNIC called scsivnic1, add it to an existing service
profile called accounting, and commit the transaction:

UCS-A# scope org /

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # create vnic-iscsi iSCSI1
UCS-A /org/service-profile/vnic-iscsi* # set iscsi-adaptor-policy iscsiboot
UCS-A /org/service-profile/vnic-iscsi* # set auth-name initauth
UCS-A /org/service-profile/vnic-iscsi* # set identity dynamic-mac derived
UCS-A /org/service-profile/vnic-iscsi* # set iscsi-identity initiator-name iSCSI1
UCS-A /org/service-profile/vnic-iscsi* # set overlay-vnic-name eth1
UCS-A /org/service-profile/vnic-iscsi* # create eth-if
UCS-A /org/service-profile/vnic-iscsi/eth-if* # set vlanname default
UCS-A /org/service-profile/vnic-iscsi/eth-if* # commit buffer

What to Do Next
Configure an iSCSI initiator to boot using a static IP address, an IP address from a configured IP pool, or
DHCP.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

25
 Configuring Server Boot
Deleting an iSCSI vNIC from a Service Profile

Deleting an iSCSI vNIC from a Service Profile

Procedure

Command or Action Purpose

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 # scope service-profile Enters service profile organization mode for the
profile-name service profile.

Step 3 UCS-A /org/service-profile # delete Deletes the specified iSCSI vNIC from the specified
vnic-iscsi iscsi-vnic-name service profile.

Step 4 UCS-A /org/service-profile # Commits the transaction to the system

commit-buffer configuration.

The following example shows how to delete an iSCSI vNIC called scsivnic1 and commit the transaction:
UCS-A# scope org /
UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # delete vnic-iscsi scsivnic1
UCS-A /org/service-profile* # commit-buffer
UCS-A /org/service-profile #

Creating an iSCSI Initiator that Boots Using a Static IP Address

In a service profile, you can create an iSCSI initiator and configure it to boot using a static IP address.

Before You Begin

You have completed the following:
• Created iSCSI overlay vNICs in a service profile.
• Created an iSCSI vNIC in a service profile.

Procedure

Command or Action Purpose

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.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

26
Configuring Server Boot
Creating an iSCSI Initiator that Boots Using a Static IP Address

Command or Action Purpose

Step 2 UCS-A /org # scope service-profile profile-name Enters service profile
organization mode for the
service profile.

Step 3 UCS-A /org/service-profile # scope vnic-iscsi iscsi-vnic-name Enters the configuration

mode for the specified
iSCSI vNIC.

Step 4 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # create ip-if Creates an IP interface.

Step 5 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/eth-if/ip-if* # enter Specifies that you are

static-ip-params entering static IP boot
parameters.

Step 6 UCS-A Specifies the static IP

/org/service-profile/iscsi-boot/vnic-iscsi/eth-if/ip-if/static-ip-params* address.
# set addr ip-address
Step 7 UCS-A Specifies the default
/org/service-profile/iscsi-boot/vnic-iscsi/eth-if/ip-if/static-ip-params* gateway IP address.
# set default-gw ip-address
Step 8 UCS-A Specifies the primary DNS
/org/service-profile/iscsi-boot/vnic-iscsi/eth-if/ip-if/static-ip-params* IP address.
# set primary-dns ip-address
Step 9 UCS-A Specifies the secondary
/org/service-profile/iscsi-boot/vnic-iscsi/eth-if/ip-if/static-ip-params* DNS IP address.
# set secondary-dns ip-address
Step 10 UCS-A Specifies the subnet mask.
/org/service-profile/iscsi-boot/vnic-iscsi/eth-if/ip-if/static-ip-params*
# set subnet subnet-ip-address
Step 11 UCS-A Commits the transaction to
/org/service-profile/iscsi-boot/vnic-iscsi/eth-if/ip-if/static-ip-params* the system configuration.
# commit buffer

The following example shows how to configure the initiator to boot using a static IP address and commit the
transaction:

UCS-A # scope org

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # scope vnic-iscsi iSCSI1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # create ip-if
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # enter static-ip-params
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if/static-ip-params* # set addr
10.104.105.193
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if/static-ip-params* # set default-gw
10.104.105.1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if/static-ip-params* # set primary-dns
11.11.11.100
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if/static-ip-params* # set secondary-dns
11.11.11.100
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if/static-ip-params* # set subnet

Cisco UCS Manager CLI Configuration Guide, Release 2.2

27
 Configuring Server Boot
Deleting the Static IP Address Boot Parameters from an iSCSI Initiator

255.255.255.0
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if/static-ip-params* # commit-buffer

What to Do Next
Create an iSCSI target.

Deleting the Static IP Address Boot Parameters from an iSCSI Initiator

In a service profile, you can delete the static IP address boot parameters from an iSCSI initiator.

Procedure

Command or Action Purpose

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 # scope service-profile profile-name Enters service profile organization
mode for the service profile.

Step 3 UCS-A /org/service-profile # scope vnic-iscsi iscsi-vnic-name Enters the configuration mode for
the specified iSCSI vNIC.

Step 4 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # scope ip-if Enters the configuration mode for
an IP interface.

Step 5 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # delete Deletes the static IP boot

static-ip-params parameters from an initiator.

Step 6 UCS-A Commits the transaction to the

/org/service-profile/iscsi-boot/vnic-iscsi/ip-if/static-ip-params* system configuration.
# commit buffer

The following example shows how to delete the static IP address boot parameters from the initiator and commit
the transaction:

UCS-A # scope org

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # scope vnic-iscsi iSCSI1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # scope ip-if
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if # delete static-ip-params
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # commit-buffer

Creating an iSCSI Initiator that Boots Using an IP Address from an IP Pool

In a service profile, you can create an iSCSI initiator and configure it to boot using an IP address from an IP
pool that you have created.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

28
Configuring Server Boot
Creating an iSCSI Initiator that Boots Using an IP Address from an IP Pool

Before You Begin

You have completed the following:
• Created an overlay vNIC in a service profile
• Created an iSCSI vNIC in a service profile.

Procedure

Command or Action Purpose

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 # scope service-profile profile-name Enters service profile

organization mode for the service
profile.

Step 3 UCS-A /org/service-profile # scope iscsi-boot Enters the configuration mode for
configuring iSCSI boot
parameters.

Step 4 UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi Enters the configuration mode for
iscsi-vnic-name the specified iSCSI vNIC.

Step 5 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi* # scope ip-if Enters the configuration mode for
the iSCSI Ethernet interface.

Step 6 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # enter Specifies that the iSCSI initiator

pooled-ip-params boot using one of the IP addresses
from the previously created iSCSI
initiator IP pool.

Step 7 UCS-A Commits the transaction to the

/org/service-profile/iscsi-boot/vnic-iscsi/ip-if/pooled-ip-params* system configuration.
# commit buffer

The following example shows how to create an iSCSI initiator and configure it to boot using an IP address
from an IP pool:

UCS-A # scope org

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi iSCSI1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # scope ip-if
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # enter pooled-ip-params
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if/pooled-ip-params* # commit buffer

What to Do Next
Create an iSCSI target.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

29
 Configuring Server Boot
Deleting the IP Pool Boot Parameter from an iSCSI Initiator

Deleting the IP Pool Boot Parameter from an iSCSI Initiator

In a service profile, you can create an iSCSI initiator and configure it to boot using an IP address from an IP
pool that you have created.

Procedure

Command or Action Purpose

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 # scope service-profile profile-name Enters service profile

organization mode for the service
profile.

Step 3 UCS-A /org/service-profile # scope iscsi-boot Enters the configuration mode for
configuring the iSCSI boot
parameters.

Step 4 UCS-A /org/service-profile/iscsi-boot/ # scope vnic-iscsi Enters the configuration mode for
iscsi-vnic-name the specified iSCSI vNIC.

Step 5 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # enter ip-if Enters the configuration mode for
an IP interface.

Step 6 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # delete Specifies that the iSCSI initiator

pooled-ip-params does not use an IP address from
an IP pool to boot.

Step 7 UCS-A Commits the transaction to the

/org/service-profile/iscsi-boot/vnic-iscsi/ip-if/pooled-ip-params* system configuration.
# commit buffer

The following example shows how to delete the boot using an IP address from an IP poo parameter and commit
the transaction:

UCS-A # scope org

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # scope iscsi-boot
UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi iSCSI1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # enter ip-if
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # delete pooled-ip-params
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if/pooled-ip-params* # commit buffer

Creating an iSCSI Initiator that Boots Using DHCP

In a service profile, you can create an iSCSI initiator and configure it to boot using DHCP.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

30
 Configuring Server Boot
Deleting the DHCP Boot Parameter from an iSCSI Initiator

Before You Begin

You have completed the following:
• Created iSCSI overlay vNICs in a service profile.
• Created an iSCSI vNIC in a service profile.

Procedure

Command or Action Purpose

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 # scope service-profile profile-name Enters service profile organization
mode for the service profile.

Step 3 UCS-A /org/service-profile # scope iscsi-boot Enters the configuration mode for
configuring iSCSI boot
parameters.

Step 4 UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi Enters the configuration mode for
iscsi-vnic-name the specified iSCSI vNIC.

Step 5 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # create ip-if Creates an IP interface.

Step 6 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # create Specifies that you are setting the
dhcp-ip-params initiator to boot using DHCP.

Step 7 UCS-A Commits the transaction to the

/org/service-profile/iscsi-boot/vnic-iscsi/ip-if/dhcp-ip-params* system configuration.
# commit buffer

The following example shows how to configure the initiator to boot using DHCP and commit the transaction:

UCS-A # scope org

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # scope iscsi-boot
UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi iSCSI1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # create ip-if
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # create dhcp-ip-params
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if/dhcp-ip-params* # commit-buffer

What to Do Next
Create an iSCSI target.

Deleting the DHCP Boot Parameter from an iSCSI Initiator

In a service profile, you can remove the DHCP boot parameter from an iSCSI initiator.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

31
 Configuring Server Boot
IQN Pools

Procedure

Command or Action Purpose

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 # scope service-profile profile-name Enters service profile organization
mode for the service profile.

Step 3 UCS-A /org/service-profile # scope iscsi-boot Enters the configuration mode for
configuring iSCSI boot
parameters.

Step 4 UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi Enters the configuration mode for
iscsi-vnic-name the specified iSCSI vNIC.

Step 5 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # enter ip-if Enters the configuration mode for
an IP interface.

Step 6 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # delete Specifies that the initiator does not
dhcp-ip-params use DHCP to boot.

Step 7 UCS-A Commits the transaction to the

/org/service-profile/iscsi-boot/vnic-iscsi/ip-if/dhcp-ip-params* system configuration.
# commit buffer

The following example shows how to delete the boot using DHCP parameter and commit the transaction:

UCS-A # scope org

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # scope iscsi-boot
UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi iSCSI1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # enter ip-if
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if* # delete dhcp-ip-params
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ip-if/dhcp-ip-params* # commit-buffer

IQN Pools
An IQN pool is a collection of iSCSI Qualified Names (IQNs) for use as initiator identifiers by iSCSI vNICs
in a Cisco UCS domain.
IQN pool members are of the form prefix:suffix:number, where you can specify the prefix, suffix, and a block
(range) of numbers.
An IQN pool can contain more than one IQN block, with different number ranges and different suffixes, but
sharing the same prefix.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

32
 Configuring Server Boot
Creating an IQN Pool

Creating an IQN Pool

Note In most cases, the maximum IQN size (prefix + suffix + additional characters) is 223 characters. When
using the Cisco UCS NIC M51KR-B adapter, you must limit the IQN size to 128 characters.

Procedure

Command or Action Purpose

Step 1 UCS-A# scope org org-name Enters the organization mode for the specified organization. To
enter the root organization mode, enter / as the org-name.

Step 2 UCS-A /org # create iqn-pool Creates an IQN pool with the specified pool name and enters
pool-name organization IQN pool mode.
This name can be between 1 and 32 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 3 UCS-A /org/iqn-pool # set Specifies the prefix for the IQN block members. Unless limited
iqn-prefix prefix by the adapter card, the prefix can contain up to 150 characters.

Step 4 UCS-A /org/iqn-pool # set (Optional)

descr description Provides a description for the IQN pool. Enter up to 256 characters.
Note If your description includes spaces, special characters, or
punctuation, you must begin and end your description
with quotation marks. The quotation marks will not appear
in the description field of any show command output.
Step 5 UCS-A /org/iqn-pool # set This can be one of the following:
assignmentorder {default |
sequential} • default—Cisco UCS Manager selects a random identity from
the pool.
• sequential—Cisco UCS Manager selects the lowest available
identity from the pool.

Step 6 UCS-A /org/iqn-pool # create Creates a block (range) of IQNs, and enters organization IQN pool
block suffix from to block mode. You must specify the base suffix, the starting suffix
number, and the ending suffix number. The resulting IQN pool
members are of the form prefix:suffix:number. The suffix can be
up to 64 characters.
Note An IQN pool can contain more than one IQN block. To
create multiple blocks, enter multiple create block
commands from organization IQN pool mode.
Step 7 UCS-A /org/iqn-pool/block # Commits the transaction to the system configuration.
commit-buffer

Cisco UCS Manager CLI Configuration Guide, Release 2.2

33
 Configuring Server Boot
Adding a Block to an IQN Pool

The following example shows how to create an IQN pool named pool4, provide a description for the pool,
specify a prefix and a block of suffixes to be used for the pool, and commit the transaction:
UCS-A# scope org /
UCS-A /org # create iqn-pool pool4
UCS-A /org/iqn-pool* # set iqn-prefix iqn.alpha.com
UCS-A /org/iqn-pool* # set descr "This is IQN pool 4"
UCS-A /org/iqn-pool* # create block beta 3 5
UCS-A /org/iqn-pool/block* # commit-buffer
UCS-A /org/iqn-pool/block #

What to Do Next
Include the IQN suffix pool in a service profile and/or template.

Adding a Block to an IQN Pool

Procedure

Command or Action Purpose

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 # scope iqn-pool Enters organization IQN pool mode for the specified pool.
pool-name
Step 3 UCS-A /org/iqn-pool # create Creates a block (range) of IQN suffixes, and enters
block suffix from to organization IQN pool block mode. You must specify the
base suffix, the starting suffix number, and the ending suffix
number. The resulting IQN pool members are of the form
prefix:suffix:number.
Note An IQN pool can contain more than one IQN block.
To create multiple blocks, enter multiple create
block commands from organization IQN pool
mode.
Step 4 UCS-A /org/iqn-pool/block # Commits the transaction to the system configuration.
commit-buffer
Step 5 UCS-A /org/iqn-pool/block # exit (Optional)
Returns to organization IQN pool mode.

Step 6 UCS-A /org/iqn-pool # show (Optional)

block Displays the blocks of suffixes.

This example shows how to add a block of IQN suffixes to an IQN pool named pool4 and commit the
transaction:
UCS-A# scope org /
UCS-A /org # scope iqn-pool pool4
UCS-A /org/iqn-pool # create block beta 3 5

Cisco UCS Manager CLI Configuration Guide, Release 2.2

34
 Configuring Server Boot
Deleting a Block from an IQN Pool

UCS-A /org/iqn-pool/block* # commit-buffer

UCS-A /org/iqn-pool/block # exit
UCS-A /org/iqn-pool # show block
Block of IQN Names:
Suffix From To
---------- ----- --
beta 3 5

UCS-A /org/iqn-pool #

Deleting a Block from an IQN Pool

If you delete an address block from a pool, Cisco UCS Manager does not reallocate any addresses in that
block that have been assigned to vNICs or vHBAs. All assigned addresses from a deleted block remain with
the vNIC or vHBA to which they are assigned until one of the following occurs:
• The associated service profiles are deleted.
• The vNIC or vHBA to which the address is assigned is deleted.
• The vNIC or vHBA is assigned to a different pool.

Procedure

Command or Action Purpose

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 # scope iqn-pool Enters organization IQN pool mode for the specified
pool-name pool.

Step 3 UCS-A /org/iqn-pool # delete block Deletes a block (range) of IQNs. You must specify the
suffix from to base suffix and the first and last numbers in the block
to be deleted.

Step 4 UCS-A /org/iqn-pool # Commits the transaction to the system configuration.

commit-buffer

This example shows how to delete a block of suffixes from an IQN pool named pool4 and commit the
transaction:
UCS-A# scope org /
UCS-A /org # scope iqn-pool pool4
UCS-A /org/iqn-pool # delete block beta 0 12
UCS-A /org/iqn-pool* # commit-buffer
UCS-A /org/iqn-pool #

Deleting an IQN Pool

If you delete a pool, Cisco UCS Manager does not reallocate any addresses from that pool that have been
assigned to vNICs or vHBAs. All assigned addresses from a deleted pool remain with the vNIC or vHBA to
which they are assigned until one of the following occurs:

Cisco UCS Manager CLI Configuration Guide, Release 2.2

35
 Configuring Server Boot
Viewing IQN Pool Usage

• The associated service profiles are deleted.

• The vNIC or vHBA to which the address is assigned is deleted.
• The vNIC or vHBA is assigned to a different pool.

Procedure

Command or Action Purpose

Step 1 UCS-A# scope org org-name Enters the organization mode for the specified
organization. To enter the root organization mode,
enter / as the org-name.

Step 2 UCS-A /org # delete iqn-pool Deletes the specified IQN pool.
pool-name
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.

The following example shows how to delete the IQN pool named pool4 and commit the transaction:
UCS-A# scope org /
UCS-A /org # delete iqn-pool pool4
UCS-A /org* # commit-buffer
UCS-A /org #

Viewing IQN Pool Usage

Procedure

Command or Action Purpose

Step 1 UCS-A# scope org org-name Enters the organization mode for the specified
organization. To enter the root organization mode,
enter / as the org-name.

Step 2 UCS-A /org # scope iqn-pool Enters organization IQN pool mode for the specified
pool-name pool.

Step 3 UCS-A /org/iqn-pool # show pooled Displays the assignments of the IQN block members.

The following example shows how to display the assignments of suffixes in the IQN pool named pool4:
UCS-A# scope org /
UCS-A /org # scope iqn-pool pool4
UCS-A /org/iqn-pool # show pooled
Pooled:
Name Assigned Assigned To Dn
---------- -------- --------------
beta:3 No
beta:4 No
beta:5 No

Cisco UCS Manager CLI Configuration Guide, Release 2.2

36
 Configuring Server Boot
Creating an iSCSI Static Target

UCS-A /org/iqn-pool #

Creating an iSCSI Static Target

You can create a static target.

Before You Begin

You have already created an iSCSI vNIC.

Procedure

Command or Action Purpose

Step 1 UCS-A# scope org org-name Enters organization mode for the specified organi
enter the root organization mode, type / as the or

Step 2 UCS-A /org # scope service-profile profile-name Enters service profile organization mode for the
profile to which you want to add an iSCSI target

Step 3 UCS-A /org/service-profile # scope iscsi-boot Enters the mode for configuring iSCSI boot para

Step 4 UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi Enters the iSCSI vNIC mode for the specified vN
iscsi-vnic-name
Step 5 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # create Creates a static target for the iSCSI vNIC and ass
static-target-if {1 | 2} priority level to it.
Valid priority levels are 1 or 2.

Step 6 UCS-A A regular expression that defines the iSCSI Qualif

/org/service-profile/iscsi-boot/vnic-iscsi/static-target-if # set (IQN) or Extended Unique Identifier (EUI) name
name name iSCSI target.
You can enter any alphanumeric characters as we
following special characters:
• . (period)
• : (colon)
• - (dash)

Important This name must be properly format

standard IQN or EUI guidelines.
The following examples show properly formatted
target names:
• iqn.2001-04.com.example
• iqn.2001-04.com.example:storage:diskarrays-sn
• iqn.2001-04.com.example:storage.tape1.sy
• iqn.2001-04.com.example:storage.disk2.sy
• eui.02004567A425678D

Cisco UCS Manager CLI Configuration Guide, Release 2.2

37
 Configuring Server Boot
Creating an iSCSI Static Target

Command or Action Purpose

Step 7 UCS-A The port associated with the iSCSI target.
/org/service-profile/iscsi-boot/vnic-iscsi/static-target-if # set Enter an integer between 1 and 65535. The default is
port port-num
Step 8 UCS-A (Optional)
/org/service-profile/iscsi-boot/vnic-iscsi/static-target-if # set If you need the target to authenticate itself and have
auth-name auth-profile an authentication profile, you need to specify the nam
authentication profile.
The name of the associated iSCSI authentication pro

Step 9 UCS-A The IPv4 address assigned to the iSCSI target.

/org/service-profile/iscsi-boot/vnic-iscsi/static-target-if # set
ipaddress ipv4-address
Step 10 UCS-A Creates the LUN that corresponds to the location of
/org/service-profile/iscsi-boot/vnic-iscsi/static-target-if # interface.
create lun
Step 11 UCS-A Specifies the target LUN id. Valid values are from 0
/org/service-profile/iscsi-boot/vnic-iscsi/static-target-if/lun* 65535.
# set id id-number
Step 12 UCS-A Exits the current configuration mode.
/org/service-profile/iscsi-boot/vnic-iscsi/static-target-if/lun*
# exit
Step 13 UCS-A Exits the current configuration mode.
/org/service-profile/iscsi-boot/vnic-iscsi/static-target-if #
exit
Step 14 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # Commits the transaction to the system configuration
commit-buffer
Step 15 Repeat steps 5 through 14 to create a second static target. (Optional)

The following example shows how to create two iSCSI static target interfaces and commit the transaction:
UCS-A # scope org test
UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # scope iscsi-boot
UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi iSCSI1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # create static-target-if 1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # set name statictarget1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # set port 3260
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # set auth-name
authprofile1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # set ip-address
192.168.10.10
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # create lun
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if/lun* # set id 1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if/lun* # exit
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # exit
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # commit-buffer
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # create static-target-if 2
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # set ipaddress
192.168.10.11
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # set name statictarget2

Cisco UCS Manager CLI Configuration Guide, Release 2.2

38
 Configuring Server Boot
Deleting an iSCSI Static Target

UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # set port 3260

UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # set auth-name
authprofile1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # create lun
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if/lun* # set id 1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if/lun* # exit
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/static-target-if* # exit
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # commit-buffer

What to Do Next
To configure a second iSCSI device, repeat the steps for creating an iSCSI vNIC, initiator, and target.

Deleting an iSCSI Static Target

You can delete an iSCSI static target. However, you must have at least one iSCSI static target remaining after
you delete one. Therefore, you must have two iSCSI static targets in order to delete one of them.

Note If you have two iSCSI targets and you delete the first priority target, the second priority target becomes
the first priority target, although the Cisco UCS Manager still shows it as the second priority target.

Procedure

Command or Action Purpose

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 # scope service-profile Enters service profile organization mode for the
profile-name service profile to which you want to add an iSCSI
target.

Step 3 UCS-A /org/service-profile # scope Enters the mode for configuring iSCSI boot
iscsi-boot parameters.

Step 4 UCS-A /org/service-profile/iscsi-boot # Enters the iSCSI vNIC mode for the specified
scope vnic-iscsi iscsi-vnic-name vNIC name.

Step 5 UCS-A Deletes the static target for the iSCSI vNIC.
/org/service-profile/iscsi-boot/vnic-iscsi #
delete static-target-if
Step 6 UCS-A Commits the transaction to the system
/org/service-profile/iscsi-boot/vnic-iscsi # configuration.
commit-buffer

The following example shows how to delete an iSCSI static target and commit the transaction:
UCS-A # scope org test
UCS-A /org # scope service-profile sample
UCS-A /org # scope iscsi-boot

Cisco UCS Manager CLI Configuration Guide, Release 2.2

39
 Configuring Server Boot
Creating an iSCSI Auto Target

UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi trial

UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # delete static-target-if 1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # commit-buffer
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi #

Creating an iSCSI Auto Target

You can create an iSCSI auto target with or without the vendor IDs.

Before You Begin

These prerequisites must be met before creating iSCSI auto target:
• You have already created an iSCSI vNIC in a service profile.
• You have considered the prerequisites for the VIC that you are using. For more information, see iSCSI
Boot Guidelines and Prerequisites, on page 11

Procedure

Command or Action Purpose

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 # scope service-profile profile-name Enters service profile organization mode
for the service profile that you want to add
an iSCSI target interface to.

Step 3 UCS-A /org # scope iscsi-boot Enters the mode for configuring iSCSI
boot parameters.
Example:
Step 4 UCS-A /org/service-profile/iscsi-boot # scope Enters iSCSI vNIC service profile
vnic-iscsi iscsi-vnic-name organization mode for the specified vNIC
name.

Step 5 UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/ # Creates an auto target for the iSCSI vNIC.
create auto-target-if If you plan to use an auto target without
the vendor ID, you must configure an
initiator name. For more information, see
Creating an iSCSI vNIC in a Service
Profile, on page 24.

Step 6 UCS-A (Optional)

/org/service-profile/iscsi-boot/vnic-iscsi/auto-target-if* Sets a vendor ID for the auto target. The
# set dhcp-vendor-id vendor-id vendor ID can be up to 32 alphanumeric
characters.

Step 7 UCS-A Exists the current configuration mode.

/org/service-profile/iscsi-boot/vnic-iscsi/auto-target-if*
# exit

Cisco UCS Manager CLI Configuration Guide, Release 2.2

40
 Configuring Server Boot
Deleting an iSCSI Auto Target

Command or Action Purpose

Step 8 UCS-A /org/service-profile/iscis-boot/vnic-iscsi # Commits the transaction to the system
commit-buffer configuration.

The following example shows how to create an iSCSI auto target without a vendor ID and commit the
transaction:

UCS-A # scope org

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # scope iscsi-boot
UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi iSCSI1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # create auto-target-if
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/auto-target-if* # exit
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # commit-buffer
The following example shows how to create an iSCSI auto target with a vendor ID and commit the transaction:

UCS-A # scope org

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # scope iscsi-boot
UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi iSCSI1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # create auto-target-if
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/auto-target-if* # set dhcp-vendor-id
iSCSI_Vendor
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi/auto-target-if* # exit
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # commit-buffer

What to Do Next
To configure a second iSCSI device, repeat the steps for creating an iSCSI vNIC, initiator, and target.

Deleting an iSCSI Auto Target

You can delete an auto target only if you have a static target set.

Procedure

Command or Action Purpose

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 # scope service-profile Enters the service profile mode for the service
profile-name profile to which you want to add an iSCSI target.

Step 3 UCS-A /org/service-profile # scope Enters the mode for configuring iSCSI boot
iscsi-boot parameters.

Step 4 UCS-A /org/service-profile/iscsi-boot # Enters the iSCSI vNIC mode for the specified
scope vnic-iscsi iscsi-vnic-name vNIC name.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

41
 Configuring Server Boot
Verifying iSCSI Boot

Command or Action Purpose

Step 5 UCS-A Deletes the auto target.
/org/service-profile/iscsi-boot/vnic-iscsi #
delete auto-target-if
Step 6 UCS-A Commits the transaction to the system
/org/service-profile/iscsi-boot/vnic-iscsi # configuration.
commit-buffer

The following example shows how to delete an iSCSI auto target and commit the transaction:

UCS-A # scope org test

UCS-A /org # scope service-profile accounting
UCS-A /org/service-profile # scope iscsi-boot
UCS-A /org/service-profile/iscsi-boot # scope vnic-iscsi iSCSI1
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # delete auto-target-if
UCS-A /org/service-profile/iscsi-boot/vnic-iscsi # commit-buffer

Verifying iSCSI Boot

Use the KVM console to view the boot up messages as the adapter is booting. For information on how to
access the KVM console, see the Starting the KVM Console chapter.
This step can only be performed using the Cisco UCS Manager GUI. For more information, see the Starting
the KVM Console chapter in the UCS Manager GUI Configuration Guide.
• For the Cisco UCS M51KR-B Broadcom BCM57711, the following message appears:
Logging in the 1st iSCSI Target…. Succeeded.
• For the Cisco UCS M81KR Virtual Interface Card, the following message appears:
Option ROM installed successfully.

LAN Boot
You can configure a boot policy to boot one or more servers from a centralized provisioning server on the
LAN. A LAN (or PXE) boot is frequently used to install operating systems on a server from that LAN server.
You can add more than one type of boot device to a LAN boot policy. For example, you could add a local
disk or virtual media boot as a secondary boot device.

Configuring a LAN Boot for a Boot Policy

Before You Begin
Create a boot policy to contain the LAN boot configuration.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

42
 Configuring Server Boot
Local Devices Boot

Procedure

Command or Action Purpose

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 # scope boot-policy Enters organization boot policy mode for the
policy-name specified boot policy.

Step 3 UCS-A /org/boot-policy # create lan Creates a LAN boot for the boot policy and enters
organization boot policy LAN mode.

Step 4 UCS-A /org/boot-policy/lan # set order Specifies the boot order for the LAN boot.
{1 | 2 | 3 | 4}
Step 5 UCS-A /org/boot-policy/lan # create path Creates a primary or secondary LAN boot path and
{primary | secondary} enters organization boot policy LAN path mode.

Step 6 UCS-A /org/boot-policy/lan/path # set Specifies the vNIC to use for the LAN path to the
vnic vnic-name boot image.

Step 7 UCS-A /org/boot-policy/lan/path # Commits the transaction to the system configuration.

commit-buffer

The following example enters the boot policy named lab2-boot-policy, creates a LAN boot for the policy,
sets the boot order to 2, creates primary and secondary paths using the vNICs named vNIC1 and vNIC2 , and
commits the transaction:
UCS-A# scope org /
UCS-A /org* # scope boot-policy lab2-boot-policy
UCS-A /org/boot-policy* # create lan
UCS-A /org/boot-policy/lan* # set order 2
UCS-A /org/boot-policy/lan* # create path primary
UCS-A /org/boot-policy/lan/path* # set vnic vNIC1
UCS-A /org/boot-policy/lan/path* # exit
UCS-A /org/boot-policy/lan* # create path secondary
UCS-A /org/boot-policy/lan/path* # set vnic vNIC2
UCS-A /org/boot-policy/lan/path* # commit-buffer
UCS-A /org/boot-policy/lan/path #

What to Do Next
Include the boot policy in a service profile and/or template.

Local Devices Boot

Cisco UCS Manager allows you to boot from different local devices.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

43
 Configuring Server Boot
Configuring a Local Disk Boot for a Boot Policy

Note For Cisco UCS M3 and M4 blade and rack servers using enhanced boot order, you can select both top-level
and second-level boot devices. For Cisco UCS M1 and M2 blade and rack servers using standard boot
order, you can only select a top-level device.

Local Disk Boot

If a server has a local drive, you can configure a boot policy to boot the server from the top-level local disk
device or from any of the following second-level devices:
• Local LUN
• SD card
• Internal USB
• External USB

Note Second-level devices are only available for Cisco UCS M3 and M4 blade and rack servers using enhanced
boot order. For Cisco UCS M1 and M2 blade and rack servers using standard boot order, you can choose
only the top-level Add Local Disk.

Virtual Media Boot

You can configure a boot policy to boot one or more servers from a virtual media device that is accessible
from the server. A virtual media device mimics the insertion of a physical CD/DVD disk (read-only) or floppy
disk (read-write) into a server. This type of server boot is typically used to manually install operating systems
on a server.

Note Second-level devices are only available for Cisco UCS M3 and M4 blade and rack servers using enhanced
boot order. For Cisco UCS M1 and M2 blade and rack servers using standard boot order, you can choose
only the top-level Add CD/DVD or Add Floppy.

Remote Virtual Drive Boot

You can configure a boot policy to boot one or more servers from a remote virtual drive that is accessible
from the server.

Configuring a Local Disk Boot for a Boot Policy

You can also create a local boot policy that is restricted to a service profile or service profile template. However,
we recommend that you create a global boot policy that can be included in multiple service profiles or service
profile templates.
You can add more than one type of boot device to a boot policy. For example, you could add a virtual media
boot as a secondary boot device.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

44
Configuring Server Boot
Configuring a Local Disk Boot for a Boot Policy

Note Beginning with Release 2.2, if you want to add any top-level local storage device to the boot order, you
must use create local-any after the create local command. If you have any policies from previous releases
that contain a local storage device, they will be modified to use local-any during upgrade.

Procedure

Command or Action Purpose

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 # scope boot-policy policy-name Enters organization boot policy mode for the
specified boot policy.

Step 3 UCS-A /org/boot-policy # create storage Creates a storage boot for the boot policy and
enters organization boot policy storage mode.

Step 4 UCS-A /org/boot-policy/storage # create local Creates a local storage location and enters the
boot policy local storage mode.

Step 5 UCS-A /org/boot-policy/storage/local/ # create Specifies the type of local storage. This can be
{local-any | local-lun | sd-card | usb-extern | one of the following:
usb-intern }
• local-any—Any type of local storage
device. This option can be used in either
legacy or UEFI boot mode.
Note Cisco UCS M1 and M2 blade and
rack servers using standard boot
order can only use local-any.
• local-lun—A local hard disk drive.
• sd-card—An SD card.
• usb-extern—An external USB card.
• usb-intern—An internal USB card.

For Cisco UCS M3 and M4 blade and rack

servers using enhanced boot order, you can select
both top-level and second-level boot devices.
For Cisco UCS M1 and M2 blade and rack
servers using standard boot order, you can only
select a top-level device.

Step 6 UCS-A Sets the boot order for the specified local storage
/org/boot-policy/storage/local/local-storage-device device. Enter an integer between 1 and 16.
# set order order_number When using the enhanced boot order on Cisco
UCS M3 servers, or M4 servers, the boot order
that you define is used. For standard boot mode
using the terms "primary" or "secondary" do not

Cisco UCS Manager CLI Configuration Guide, Release 2.2

45
 Configuring Server Boot
Configuring a Local Disk Boot for a Boot Policy

Command or Action Purpose

imply a boot order. The effective order of boot
devices within the same device class is
determined by the PCIe bus scan order.

Step 7 UCS-A Commits the transaction to the system

/org/boot-policy/storage/local/local-storage-device configuration.
# commit-buffer

The following example shows how to create a boot policy named lab1-boot-policy, create a local hard disk
drive boot for the policy, set the boot order to 3, and commit the transaction:
UCS-A# scope org /
UCS-A /org* # scope boot-policy lab1-boot-policy
UCS-A /org/boot-policy* # create storage
UCS-A /org/boot-policy/storage* # create local
UCS-A /org/boot-policy/storage/local* # create local-lun
UCS-A /org/boot-policy/storage/local/sd-card* # set order 3
UCS-A /org/boot-policy/storage/local/sd-card* # commit-buffer
UCS-A /org/boot-policy/storage/local/sd-card #

The following example shows how to create a local SD card boot for the service profile SP_lab1, set the boot
order to 3, and commit the transaction:
UCS-A# scope org /
UCS-A /org* # scope service-profile SP_lab1
UCS-A /org/service-profile # create boot-definition
UCS-A /org/service-profile/boot-definition* # create storage
UCS-A /org/service-profile/boot-definition/storage* # create local
UCS-A /org/service-profile/boot-definition/storage/local* # create sd-card
UCS-A /org/service-profile/boot-definition/storage/local* # set order 3
UCS-A /org/service-profile/boot-definition/storage/local* # commit-buffer
UCS-A /org/service-profile/boot-definition/storage/local #
The following example shows how to create any top-level local device boot for the service profile SP_lab1,
set the boot order to 3, and commit the transaction:
UCS-A# scope org /
UCS-A /org* # scope service-profile SP_lab1
UCS-A /org/service-profile # create boot-definition
UCS-A /org/service-profile/boot-definition* # create storage
UCS-A /org/service-profile/boot-definition/storage* # create local
UCS-A /org/service-profile/boot-definition/storage/local* # create local-any
UCS-A /org/service-profile/boot-definition/storage/local/local-any* # set order 3
UCS-A /org/service-profile/boot-definition/storage/local/local-any* # commit-buffer
UCS-A /org/service-profile/boot-definition/storage/local/local-any #

What to Do Next
Include the boot policy in a service profile and/or template.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

46
 Configuring Server Boot
Configuring a Virtual Media Boot for a Boot Policy

Configuring a Virtual Media Boot for a Boot Policy

Note Virtual Media requires the USB to be enabled. If you modify the BIOS settings that affect the USB
functionality, you also affect the Virtual Media. Therefore, we recommend that you leave the following
USB BIOS defaults for best performance:
• Make Device Non Bootable—set to disabled
• USB Idle Power Optimizing Setting—set to high-performance

Before You Begin

Create a boot policy to contain the virtual media boot configuration.

Procedure

Command or Action Purpose

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 # scope boot-policy Enters organization boot policy mode for the specified boot
policy-name policy.

Step 3 UCS-A /org/boot-policy # create Creates the specified virtual media boot for the boot policy
virtual-media {read-only | and enters organization boot policy virtual media mode. This
read-only-local | can be one of the following:
read-only-remote | read-write |
read-write-drive | • read-only—Local or remote CD/DVD. This option can
be used in either legacy or UEFI boot mode.
read-write-local |
read-write-remote} • read-only-local—Local CD/DVD.
• read-only-remote—Remote CD/DVD.
• read-write—Local or remote floppy disk drive. This
option can be used in either legacy or UEFI boot mode.
• read-write-drive—Remote USB drive.
• read-write-local—Local floppy disk drive.
• read-write-remote—Remote floppy disk drive.

Note For Cisco UCS M3 and M4 blade and rack servers

using enhanced boot order, you can select both
top-level and second-level boot devices. For Cisco
UCS M1 and M2 blade and rack servers using
standard boot order, you can only select a top-level
device.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

47
 Configuring Server Boot
Creating a CIMC vMedia Boot Policy

Command or Action Purpose

Step 4 UCS-A Sets the boot order for the virtual-media boot. Enter an integer
/org/boot-policy/virtual-media # set between 1 and 16.
order order_number
Step 5 UCS-A Commits the transaction to the system configuration.
/org/boot-policy/virtual-media #
commit-buffer

The following example shows how to enter the boot policy named lab3-boot-policy, create a CD/DVD virtual
media boot, set the boot order to 3, and commit the transaction:
UCS-A# scope org /
UCS-A /org* # scope boot-policy lab3-boot-policy
UCS-A /org/boot-policy* # create virtual-media read-only-local
UCS-A /org/boot-policy/virtual-media* # set order 3
UCS-A /org/boot-policy/virtual-media* # commit-buffer

What to Do Next
Include the boot policy in a service profile and/or template.

Creating a CIMC vMedia Boot Policy

You can also create a local boot policy that is restricted to a service profile or service profile template. However,
we recommend that you create a global boot policy that can be included in multiple service profiles or service
profile templates.

Procedure

Command or Action Purpose

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 Creates a boot policy with the specified policy
policy-name name, and enters organization boot policy mode.

Step 3 UCS-A /org/boot-policy* # create Displays a list of local and remote devices to your
virtual-media ? can access and boot.

Step 4 UCS-A /org/boot-policy* # create Displays a list of local and remote devices to your
virtual-media {access | can access and boot.
vMediaMappingName}
Step 5 UCS-A /org/boot-policy* # create Creates vMedia Boot Device configuration for
virtual-media read-write-remote-drive specified vMedia.
vMediaMap0}
Step 6 UCS-A /org/boot-policy/virtual-media* # Commits the transaction to the system
commit-buffer configuration.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

48
 Configuring Server Boot
Viewing a CIMC vMedia Mount

Command or Action Purpose

Step 7 UCS-A /org/boot-policy/virtual-media* # Displays the following boot order.
show detail expand Boot virtual media:
Order: 1
Access: Read Write Remote vMedia Drive
Name: vmediaMap0

The following example creates a CIMC vMedia boot policy.

UCS-A# scope org /
UCS-A /org* # create boot-policy boot-policy vm-vmediamap-boot
UCS-A /org/boot-policy* # create virtual-media

Viewing a CIMC vMedia Mount

Procedure

Command or Action Purpose

Step 1 UCS-A# scope server chassis_id/blade_id Enters chassis server mode for the
specified server.

Step 2 UCS-A# /chassis/server # scope cimc Enters CIMC mode.

Step 3 UCS-A /chassis/server/cimc # show Displays the vMedia mapping details.

vmedia-mapping-list detail expand

The following example shows how to view a CIMC vMedia mount.

UCS-A# scope server 1/2
UCS-A /chassis/server # scope cimc
UCS-A /chassis/server/cimc # show vmedia-mapping-list detail expand

vMedia Mapping List:

vMedia Mapping:
Disk Id: 1
Mapping Name: cdd
Device Type: Cdd
Remote IP: 172.31.1.167
Image Path: cifs
Image File Name: ubunt-14.11-desktop-i386.iso
Mount Protocol: Cifs
Mount Status: Mounted
Error: None
Password:
User ID: Adminstrator

UCS-A /chassis/server/cimc #

Cisco UCS Manager CLI Configuration Guide, Release 2.2

49
 Configuring Server Boot
Deleting a Boot Policy

Deleting a Boot Policy

Procedure

Command or Action Purpose

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 # delete boot-policy Deletes the specified boot policy.
policy-name
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.

The following example deletes the boot policy named boot-policy-LAN and commits the transaction:
UCS-A# scope org /
UCS-A /org # delete boot-policy boot-policy-LAN
UCS-A /org* # commit-buffer
UCS-A /org #

UEFI Boot Parameters

UEFI boot mode for servers is dependent on information that is stored on the platform hardware. The boot
entry, which contains information about the UEFI OS boot loader, is stored in the BIOS flash of the server.
In Cisco UCS Manager releases earlier than Release 2.2(4), when a service profile is migrated from one server
to another server, the boot loader information is not available on the destination server. Hence, the BIOS
cannot load the boot loader information for the server to boot in UEFI boot mode.
Cisco UCSM Release 2.2(4) introduces UEFI boot parameters to provide the BIOS with information about
the location of the UEFI OS boot loader on the destination server from where the BIOS loads it. Now, the
server can use the boot loader information and boot in UEFI boot mode.

Guidelines and Limitations for UEFI Boot Parameters

• UEFI boot parameters can be configured only if the boot mode is UEFI.
• When you upgrade Cisco UCS Manager to Release 2.2(4), UEFI boot failure during service profile
migration is not handled automatically. You must explicitly create the UEFI boot parameters in the target
device to successfully boot to the UEFI-capable OS.
• UEFI boot parameters are supported on all M3 and higher servers that support second-level boot order.
• UEFI boot parameters can be specified for the following device types:
◦SAN LUN
◦ISCSI LUN
◦Local LUN

Cisco UCS Manager CLI Configuration Guide, Release 2.2

50
 Configuring Server Boot
Configuring UEFI Boot Parameters for a Local LUN

• UEFI boot parameters are specific to each Operating System. They can be specified for the following
Operating Systems:
◦VMware ESX
◦SuSE Linux
◦Microsoft Windows
◦Red Hat Enterprise Linux 7

Configuring UEFI Boot Parameters for a Local LUN

Before You Begin
Ensure that the boot mode for the local LUN is set to UEFI.

Procedure

Command or Action Purpose

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 # scope boot-policy policy-name Enters organization

boot policy mode for
the specified boot
policy.

Step 3 UCS-A /org/boot-policy # scope storage Enters organization

boot policy storage
mode for the boot
policy.

Step 4 UCS-A /org/boot-policy/storage # scope local Enters the boot

policy local storage
mode.

Step 5 UCS-A /org/boot-policy/storage/local/ # scope {local-any | local-lun | sd-card Specifies the type of
| usb-extern | usb-intern } local storage. This
can be one of the
following:
• local-any—Any
type of local
storage device.
This option

Cisco UCS Manager CLI Configuration Guide, Release 2.2

51
 Configuring Server Boot
Configuring UEFI Boot Parameters for a Local LUN

Command or Action Purpose

can be used in
either legacy
or UEFI boot
mode.
Note Cisco
UCS
M1
and
M2
blade
and
rack
servers
using
standard
boot
order
can
only
use
local-any.
• local-lun—A
local hard disk
drive.
• sd-card—An
SD card.
• usb-extern—An
external USB
card.
• usb-intern—An
internal USB
card.

Important The
only
type of
local
storage
for
which
you can
configure
UEFI
boot
parameters
is
local-lun.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

52
 Configuring Server Boot
Configuring UEFI Boot Parameters for an iSCSI LUN

Command or Action Purpose

Step 6 UCS-A /org/boot-policy/storage/local/local-lun # scope local-lun-image-path Enters the image
{primary | secondary} path for the local
LUN.

Step 7 UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path # create Creates UEFI boot

uefi-boot-param parameters and
enters UEFI boot
parameter mode.

Step 8 UCS-A Sets the name of the

/org/boot-policy/storage/local/local-lun/local-lun-image-path/uefi-boot-param* boot loader.
# set bootloader-name name
Step 9 UCS-A Sets the path of the
/org/boot-policy/storage/local/local-lun/local-lun-image-path/uefi-boot-param* boot loader.
# set bootloader-path path
Step 10 UCS-A Sets a description
/org/boot-policy/storage/local/local-lun/local-lun-image-path/uefi-boot-param* for the boot loader.
# set boot-description "description"
Step 11 UCS-A Commits the
/org/boot-policy/storage/local/local-lun/local-lun-image-path/uefi-boot-param* transaction to the
# commit-buffer system
configuration.

The following example shows how to create UEFI boot parameters for a local LUN, and commit the transaction:
UCS-A# scope org /
UCS-A /org* # scope boot-policy bp1
UCS-A /org/boot-policy* # scope storage
UCS-A /org/boot-policy/storage* # scope local
UCS-A /org/boot-policy/storage/local* # scope local-lun
UCS-A /org/boot-policy/storage/local/local-lun # scope local-lun-image-path primary
UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path # create uefi-boot-param
UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path/uefi-boot-param* # set
bootloader-name grub.efi
UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path/uefi-boot-param* # set
bootloader-path EFI\redhat
UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path/uefi-boot-param* # set
boot-description "Red Hat Enterprise Linux"
UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path/uefi-boot-param* #
commit-buffer

Configuring UEFI Boot Parameters for an iSCSI LUN

Before You Begin
Ensure that the boot mode for the iSCSI LUN is set to UEFI.

Cisco UCS Manager CLI Configuration Guide, Release 2.2

53
 Configuring Server Boot
Configuring UEFI Boot Parameters for an iSCSI LUN

Procedure

Command or Action Purpose

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 # scope boot-policy policy-name Enters organization boot policy mode for the
specified boot policy.

Step 3 UCS-A /org/boot-policy # scope iscsi Enters organization boot policy iSCSI mode
for the boot policy.

Step 4 UCS-A /org/boot-policy/iscsi # scope path Enters the image path for the iSCSI LUN.
{primary | secondary}
Step 5 UCS-A /org/boot-policy/iscsi/path # create Creates UEFI boot parameters and enters
uefi-boot-param UEFI boot parameter mode.

Step 6 UCS-A Sets the name of the boot loader.

/org/boot-policy/iscsi/path/uefi-boot-param* #
set bootloader-name name
Step 7 UCS-A Sets the path of the boot loader.
/org/boot-policy/iscsi/path/uefi-boot-param* #
set bootloader-path path
Step 8 UCS-A Sets a description for the boot loader.
/org/boot-policy/iscsi/path/uefi-boot-param* #
set boot-description "description"
Step 9 UCS-A Commits the transaction to the system
/org/boot-policy/iscsi/path/uefi-boot-param* # configuration.
commit-buffer

The following example shows how to create UEFI boot parameters for an iSCSI LUN, and commit the
transaction:
UCS-A# scope org /
UCS-A /org* # scope boot-policy bp2
UCS-A /org/boot-policy* # scope iscsi
UCS-A /org/boot-policy/iscsi # scope path primary
UCS-A /org/boot-policy/iscsi/path # create uefi-boot-param
UCS-A /org/boot-policy/iscsi/path/uefi-boot-param* # set bootloader-name grub.efi
UCS-A /org/boot-policy/iscsi/path/uefi-boot-param* # set bootloader-path EFI\redhat
UCS-A /org/boot-policy/iscsi/path/uefi-boot-param* # set boot-description "Red Hat Enterprise
Linux"
UCS-A /org/boot-policy/iscsi/path/uefi-boot-param* # commit-buffer

Cisco UCS Manager CLI Configuration Guide, Release 2.2

54
 Configuring Server Boot
Configuring UEFI Boot Parameters for a SAN LUN

Configuring UEFI Boot Parameters for a SAN LUN

Before You Begin
Ensure that the boot mode for the SAN LUN is set to UEFI.

Procedure

Command or Action Purpose

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 # scope boot-policy policy-name Enters organization boot policy mode
for the specified boot policy.

Step 3 UCS-A /org/boot-policy # scope san Enters organization boot policy SAN
mode for the boot policy.

Step 4 UCS-A /org/boot-policy/san # scope san-image Enters the SAN image.

{primary | secondary}
Step 5 UCS-A /org/boot-policy/san/san-image # scope path Enters the image path for the SAN
{primary | secondary} LUN.

Step 6 UCS-A /org/boot-policy/san/san-image/path # create Creates UEFI boot parameters and

uefi-boot-param enters UEFI boot parameter mode.

Step 7 UCS-A Sets the name of the boot loader.

/org/boot-policy/san/san-image/path/uefi-boot-param*
# set bootloader-name name
Step 8 UCS-A Sets the path of the boot loader.
/org/boot-policy/san/san-image/path/uefi-boot-param*
# set bootloader-path path
Step 9 UCS-A Sets a description for the boot loader.
/org/boot-policy/san/san-image/path/uefi-boot-param*
# set boot-description "description"
Step 10 UCS-A Commits the transaction to the system
/org/boot-policy/san/san-image/path/uefi-boot-param* configuration.
# commit-buffer

The following example shows how to create UEFI boot parameters for a SAN LUN, and commit the transaction:
UCS-A# scope org /
UCS-A /org* # scope boot-policy bp3
UCS-A /org/boot-policy* # scope san
UCS-A /org/boot-policy/san # scope san-image primary
UCS-A /org/boot-policy/san/san-image # scope path primary
UCS-A /org/boot-policy/san/san-image/path # create uefi-boot-param
UCS-A /org/boot-policy/san/san-image/path/uefi-boot-param* # set bootloader-name grub.efi

Cisco UCS Manager CLI Configuration Guide, Release 2.2

55
 Configuring Server Boot
Configuring UEFI Boot Parameters for a SAN LUN

UCS-A /org/boot-policy/san/san-image/path/uefi-boot-param* # set bootloader-path EFI\redhat

UCS-A /org/boot-policy/san/san-image/path/uefi-boot-param* # set boot-description "Red Hat
Enterprise Linux"
UCS-A /org/boot-policy/san/san-image/path/uefi-boot-param* # commit-buffer

Cisco UCS Manager CLI Configuration Guide, Release 2.2

56