UCS Partner Webinar

Session 2 15th March 2017

By: BGL-SV TAC
Presenters Panelists
Yogesha MG
Rahul Kumar
Saurabh Kalra

Navneet Gupta Harish Jamakhandi

Agenda

1. Detailed workflow of UCSM (30 min)

2. Detailed workflow of CIMC (10 min)
3. Detailed workflow of UCS-Central (15 min)
4. End to End Configuration of Server for OS Install
(BFS) (15 min)
5. Maintenance actions like FW upgrade (20 min)
Detailed workflow of UCS Manager
UCS Manager
UCS Manager Configuration Overview
 UCS Manager Configuration Overview
Enter the installation method (console/gui)?
Console Setup console
Enter the setup mode (restore from backup or
initial setup) [restore/setup]? setup
You have chosen to setup a new switch. Continue?
(y/n): y
Enter the password for "admin": cisco@123
Confirm the password for "admin": cisco@123
Do you want to create a new cluster on this
switch (select 'no' for standalone setup or if
you want this switch to be added to an existing
cluster)? (yes/no) [n]: yes
Enter the switch fabric (A/B): A
Enter the system name: UCS
Mgmt0 IPv4 address: 192.168.10.10
Mgmt0 IPv4 netmask: 255.255.255.0
IPv4 address of the default gateway: 192.168.10.1
Virtual IPv4 address: 192.168.10.12
CAB-CONSOLE-RJ45= Configure the DNS Server IPv4 address? (yes/no)
COM port configuration [n]: yes
9600 baud 8 data bits .
No parity 1 stop bit .
UCS Manager Configuration Overview
Configure Administration Policies
UCS Manager Configuration Overview
Configure Equipment Policies
UCS Manager Configuration Overview
Configure Unified Ports
UCS Manager Configuration Overview
Configure Fabric Interconnect Server Ports
UCS Manager Configuration Overview
Configure LAN Connectivity
UCS Manager Configuration Overview
Configure SAN Connectivity
Organizational Hierarchy
Multitenancy allows to divide the large physical infrastructure of an Cisco UCS
domain into logical entities known as organizations.

Achieve a logical isolation between organizations without providing a dedicated

physical infrastructure for each organization.

Assign unique resources to each tenant through the related organization in the
multitenant environment.

Can implement locales to assign or restrict user privileges and roles by

organization.
Organizational Hierarchy
Pools
Base building blocks for uniquely identifying hardware resources.

Allow Service Profiles to be associated with any blade while still providing the same
exact ID and presentation to the upstream LAN or SAN.

3 sets of pools are used:-

UUID Pools
MAC Address Pools
WWNN and WWPN Pools
Pools
UUID Pools
Pools
MAC Address Pools
Pools
WWNN and WWPN Pools
Server Policies
Policies are a primary mechanism for enforcing rules, which helps ensure consistency
and repeatability.

Defining and using a comprehensive set of policies enables greater consistency,

control, predictability and automation.

Commonly used policies are listed below:-

- Boot Policy - Scrub Policy
- Host Firmware Policy - Local Disk Configuration Policy
- Maintenance Policy - BIOS Policy
Server Policies
Boot Policy
Server Policies
Host Firmware Policy
Server Policies
Maintenance Policy
Server Policies
Scrub Policy
Server Policies
Local Disk
Configuration Policy
Server Policies
BIOS Policy
Server Policies
Adapter Policy
vNIC/vHBA and Service Profile Templates
vNIC Templates
vNIC/vHBA and Service Profile Templates
vHBA Templates
vNIC/vHBA and Service Profile Templates
Service
Profile
Templates
Visual Tour of Cisco UCS Manager
Manage the UCS environment.

Stateless Computing - Create

different profiles, templates,
policies, pools etc.

Configure northbound and

southbound connectivity.

Multitenancy - Divide the large

physical infrastructure of a domain
into logical entities known as
organizations.
Equipment tab
Servers tab
LAN tab
SAN tab
VM tab
Storage tab
Admin tab
Power Policy
Ethernet Switching Modes
Fibre Channel Switching Modes
Changing Switching Modes
Chassis/FEX Discovery Policy
Server Discovery Policy
Service Profile
Adapter Policy with vNIC Template
Backup Configuration
QUIZZZZ !!!

What are the most commonly

used Templates in Cisco UCS?
Detailed workflow of CIMC
Options to Deploy
Integrated
Existing mgmt tools
plus
UCS API
Integrated mgmt tools

Enabled in UCSM 1.4.1

Heterogeneous
Existing mgmt tools
IPMI, CLI, Web GUI, KVM

Available at Launch
Options to Manage the Server
Initial CIMC Configuration
Refer the specific server specification sheet (example C240M4)
Check for the available ports and their functionality.
Server (3D view)
Plug the power cord into the chassis, CIMC initializes system standby (Power Off
mode).

The Fans begins to spin up, then POST sequence begins.

Initial CIMC Configuration
F2: Access BIOS configuration
F6: Manually Boot (one time Boot
menu)
F8: To configure/view
1.Choose CIMC
either DHCP orIP
Static config.
2. Enter the VLAN tag if
needed.
CIMC3. IPEnter the CIMC
Address password.
and the CIMC
4. After you make a change
MAC address (CIMC PORT), would to
help IPinor trouble
enable DHCP, you can
shooting network
press F5
related issues. in order to display
the configured IP.
5. Press F10 in order to save
the configuration.
Server Compute Details, Processor
and memory details.
Managing the Chassis

Navigation Pane
Navigating through CIMC

Demo Server
BIOS Configuration
Managing the Server Compute Boot Order

The Advanced configuration allows you to

configure the device with specific parameters
such as slot, port and LUN.

The Actual Boot Devices section displays

the boot order actually used by BIOS when
the server last booted. The actual boot order
will differ from the configured boot order if:

The BIOS encounters issues while trying to

boot using the configured boot order.
Available boot Configured boot
options Order A user changes the boot order directly
through the BIOS. To override any manual
changes, you can change the configured
boot order through Cisco IMC and reboot the
server.
 Overview to Unified Extensible Firmware
Interface (UEFI) Secure Boot
Enable/Disable UEFI
We can use UEFI to ensure all the required EFI drivers, option
ROMs or operating systems prior to boot are signed and verified
for authenticity and integrity.

When you enable UEFI secure boot mode, the boot mode is set
to UEFI mode and you cannot modify the configured boot mode
until the UEFI boot mode is disabled.
If you enable UEFI secure boot on a non-supported OS, on the
next reboot, you cannot boot from that particular OS. If you try to
boot from the previous OS, an error is reported and recorded
the under system software event in the web UI.

Also, if you use an unsupported adapter, an error log event in

Cisco IMC SEL is recorded. The error messages is displayed
that says:

System Software event: Post sensor, System Firmware error.

EFI Load Image Security Violation. [0x5302] was asserted.
Configuring Management Network
IP Blocking Fail Count field:
The number of times a user can attempt to log in
unsuccessfully before the system locks that user
out for a specified length of time. Enter an integer
The
Using
betw eenNIC 3 mode
this
and option, setting
10. youdetermines
can eitherwhich ports can
set the
reachork
netw theport
Cisco IMC. and duplex values for the
speed
DedicatedThe management toport that is used to
IP sw itch, or Fail
Blocking allowWindow the systemfield: automatically
access the Cisco IMC.
Thederive
lengththe of values
time, infrom the swinitch.
seconds, Thisthe
w hich option
Cisco CardAny port on the adapter card that can
is available
unsuccessful for
login dedicated
attempts
be used to access the Cisco IMC. mode
must only.
occur in order
for the user to be locked out. Enter an integer
IfNIC
betw checked,
een 60 and
Redundancy: the120.netw ork port speed
active-active and e-
AND activ duplex
settings
standby are ignored by the system and Cisco
IP IMC
Blockingretains the speed
Penalty Timat w hichThe
e field: the number
sw itch isof
If you choose
configured.
seconds the user this option, make
remains locked sure
out,that all ports
Enter an
associated
integer betweenwith the 300 configured
and 900.NIC mode are
Ifconnected
unchecked, to the same subnet to ensure that traffic
you can configure the netw ork
is secure regardless of which port is used.
port speed
Enable and duplex
IP Filtering checkvalues.
box

IP Filter fields
To provide secure access to the server, you can
now set a filter to allow only a selected set of IPs
to access it.
Managing Network Adapter
Managing Storage Adapter
QUIZZZZ !!!

Which Operating Systems

support UEFI Secure Boot?
Detailed workflow of UCS-Central
Introduction to UCS Central
Features & Benefits
Centralized inventory and health status information for all Cisco UCS components for
a definitive view of the entire infrastructure.

Centralized, policy-based firmware upgrades that can be applied globally or

selectively through automated schedules or as business workloads demand.

Global ID pooling and multidomain ID visibility to eliminate identifier conflicts.

Global administrative policies that enable both global and local management of Cisco
UCS domains.

An XML API that builds on the Cisco UCS Manager XML API for easy integration into
higher-level data center management frameworks
Installation
Easy to install & configure.

Two options available:-

ISO (supported by the following)

VMWare ESXi5.0 U3, ESXi5.1, ESXi5.5, and ESXi 6.0 U1b

Microsoft Hyper-V Server 2012 R2, Microsoft Hyper-V Server 2016
KVM Hypervisor on Redhat Enterprise Linux 6.5 and 7.2

OVA (supported by VMWare ESXi5.0 U3, ESXi5.1, ESXi5.5, and ESXi 6.0 U1b)

Two modes of installation:-

Standalone
Cluster
Installation
Cluster Mode

One VM acts as the primary node and the other as the secondary node. This cluster
configuration provides redundancy and high availability in case of a VM failure.

With a cluster configuration, the VMs use NFS shared storage disk for the database
and the images repository.

As a result, firmware images are downloaded to the shared storage. The statistics
used for reporting are also collected and stored in the shared storage.

The two VMs in the cluster should not be on the same server. If both VMs are in the
same server, a single host failure would bring down the cluster.
Installation
Cluster Mode

Both hosts must have the same versions of ESX, HyperV or KVM installed on them.

Both hosts must have access to the same NFS server for shared storage.

Both VMs must be on the same sub-net.

You must install the same release version of Cisco UCS Central in both VMs.

You must install the first node completely and then install the second node.

Only NFS shared storage is supported in Cisco UCS Central 1.5 and later releases.

Snapshots can impact performance in scale environments.

HTML5-based UI
HTML5-based user interface is now the default user interface.

The previous flash-based user interface is available at http://UCSCentral_IP/flex.html.

The flash-based user interface is being deprecated, and will not be supported after
Cisco UCS Central release 1.5.

UCS Central FLEX UI

UCS Central HTML5 UI

HTML5-based UI
1. Browse Tables icon
2. Organization navigation icon
3. Domain group navigation icon
4. Dashboard widget
5. Search bar
6. Profile Configuration icon
7. System Alerts icon
8. System Tools icon
9. System Configuration icon
10. Help icon
11. Logout icon
12. Actions bar
13. Tab navigator
14. Dashboard widgets library icon
15. Refresh icon
16. Widget menu
Register a UCS Domain
Configure an NTP server and the correct time zone in both Cisco UCS Manager and
Cisco UCS Central to ensure that they are in sync.

Obtain the hostname or IP address of Cisco UCS Central. You cannot use the same
hostname for both Cisco UCS Central and Cisco UCS Manager.
For standalone mode, use individual VM IP address.
For cluster mode, use virtual IP address.

Obtain the shared secret that you configured when you deployed Cisco UCS Central.

Ensure that the Cisco UCS Manager is running Release 2.1(2) or greater before
registering with Cisco UCS Central.

Ensure that the Cisco UCS Manager Domain that you are trying to register is not
registered to another Cisco UCS Central system.
Register a UCS Domain
From UCS Manager
Register a UCS Domain
From UCS Central
Unregister a UCS Domain
Cannot manage the service profiles, policies and other configuration for the Cisco
UCS Domain from Cisco UCS Central.

All global service profiles and policies become local and continues to operate as local
entities.

Even upon re-registering the domain, the service profiles and polices still remain
local.

Two cleanup modes:-

Localize Global
Deep Removal Global
Unregister a UCS Domain
From UCS Manager
Unregister a UCS Domain
From UCS Central
Creating a Service Profile/Template
Identifying Entities pushed from UCS Central
UCS Central Upgrade
Cisco UCS Central, release 1.5 supports Cisco UCS Manager, release 2.1(2), 2.1(3),
2.2(x), 3.0(x), and 3.1(x).

It is recommended to upgrade Cisco UCS Manager to one of the supported release

versions before upgrading Cisco UCS Central.

Else Cisco UCS Central generates version mismatch errors and any registered Cisco
UCS domains stop receiving updates from Cisco UCS Central.

Upgrade Cisco UCS Central to release 1.5 from any of the following two releases:
From 1.3 to 1.5(1a)
From 1.4 to 1.5(1a)

Upgrade is performed using the ISO.

Recommended to backup the Cisco UCS Central data before the upgrade.
UCS Central Upgrade
Standalone

Reboot the VM and change the boot options to boot from CD ROM.

Mount the Cisco UCS Central ISO image with the virtual CD/DVD drive.

From the Cisco UCS Central Installation menu on the ISO image, choose Upgrade
Existing Cisco UCS Central.

After the upgrade is complete, unmount the Cisco UCS Central ISO image from the
virtual CD/DVD drive.

Reboot the Cisco UCS Central VM.

UCS Central Upgrade
Cluster

Reboot the UCS Central VM in either Node and change the boot options to boot from CD
ROM.
Mount the Cisco UCS Central ISO image with the virtual CD/DVD drive.
From the Cisco UCS Central Installation menu on the ISO image, choose Upgrade
Existing Cisco UCS Central.
After the upgrade is complete, unmount the Cisco UCS Central ISO image from the virtual
CD/DVD drive.
Reboot the Cisco UCS Central VM.
Repeat the above steps on the other node.
After upgrading both nodes, wait for the HA election to complete and check the cluster
state on one of the nodes.
Licensing Information
Cisco UCS Central can be licensed either per domain using the traditional product
activation key (PAK) or per server using Cisco Smart Licensing.

License Type License

Cisco UCS Central Per Server license through the
Cisco Smart Licensing
Cisco UCS Central Per Domain license using
traditional PAK-based licensing
UCS-MDMgr-Lic=
Suboptions that include discounts are available
based on the quantity of licenses ordered.
UCS-MDMgr-1Dmn=
QUIZZZZ !!!

Upto how many servers can be

managed by UCS Central?
One instance of End to End Configuration of
Server, OS Install & Boot
Service Profile Creation
Service Profile Creation
Service Profile Creation
Service Profile Creation
Service Profile Creation
Service Profile Creation
Service Profile Creation
Service Profile Creation
Service Profile Creation
Service Profile Creation
Service Profile Creation
vHBA Details
Service Profile Circuit Diagram
BGL16-J14-EUSV-FI-B# show service-profile circuit server 1/2
Service Profile: Webinar
Server: 1/2
Fabric ID: A
Path ID: 1
VIF vNIC Link State Oper State Prot State Prot Role Admin Pin Oper Pin Transport
---------- --------------- ----------- ---------- ------------- ----------- ---------- ---------- ---------
9154 Up Active No Protection Unprotected 0/0 0/0 Ether
960 mgmt-A Up Active No Protection Unprotected 0/0 0/10 Ether
962 A Up Active No Protection Unprotected 0/0 2/1 Fc <<<<<
Fabric ID: B
Path ID: 1
VIF vNIC Link State Oper State Prot State Prot Role Admin Pin Oper Pin Transport
---------- --------------- ----------- ---------- ------------- ----------- ---------- ---------- ---------
9155 Up Active No Protection Unprotected 0/0 0/0 Ether
961 mgmt-B Up Active No Protection Unprotected 0/0 0/20 Ether
963 B Up Active No Protection Unprotected 0/0 2/1 Fc <<<<<
vHBA WWPN
BGL16-J14-EUSV-FI-B# scope server 1/2

BGL16-J14-EUSV-FI-B /chassis/server # scope adapter 1

BGL16-J14-EUSV-FI-B /chassis/server/adapter # show host-fc-if

FC Interface:
Id WWPN Model Name Operability
---------- ----------------------- ---------- ---------- -----------
1 20:00:00:25:B5:AB:00:CF UCSB-MLOM-40G-01 <<<<<
A Operable
2 20:00:00:25:B5:AB:00:AF UCSB-MLOM-40G-01 <<<<<
B Operable
FI nxos flogi-table
BGL16-J14-EUSV-FI-B# connect nxos a

BGL16-J14-EUSV-FI-A(nxos)# show npv flogi-table

--------------------------------------------------------------------------------
SERVER EXTERNAL
INTERFACE VSAN FCID PORT NAME NODE NAME INTERFACE
--------------------------------------------------------------------------------
vfc735 100 0x5a0003 20:00:00:25:b5:ab:00:ef 20:00:00:25:b5:aa:00:9f fc2/1
vfc948 100 0x5a0002 20:00:00:25:b5:ab:00:ff 20:00:00:25:b5:aa:00:8f fc2/1
vfc958 100 0x5a0004 20:00:00:25:b5:ab:00:8f 20:00:00:25:b5:aa:00:7f fc2/1
vfc962 100 0x5a0001 20:00:00:25:b5:ab:00:cf 20:00:00:25:b5:aa:00:6f fc2/1 <<<<<

Total number of flogi = 4.

BGL16-J14-EUSV-FI-B# connect nxos b

BGL16-J14-EUSV-FI-B(nxos)# show npv flogi-table

--------------------------------------------------------------------------------
SERVER EXTERNAL
INTERFACE VSAN FCID PORT NAME NODE NAME INTERFACE
--------------------------------------------------------------------------------
vfc736 200 0xdb0001 20:00:00:25:b5:ab:00:bf 20:00:00:25:b5:aa:00:9f fc2/1
vfc949 200 0xdb0004 20:00:00:25:b5:ab:00:df 20:00:00:25:b5:aa:00:8f fc2/1
vfc959 200 0xdb0002 20:00:00:25:b5:ab:00:9f 20:00:00:25:b5:aa:00:7f fc2/1
vfc963 200 0xdb0003 20:00:00:25:b5:ab:00:af 20:00:00:25:b5:aa:00:6f fc2/1 <<<<<

Total number of flogi = 4.

Upstream Device Check
BGL16.J14.N5K-1# show flogi database
--------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
--------------------------------------------------------------------------------
fc2/9 100 0x5a0000 20:41:8c:60:4f:4f:4f:c0 20:64:8c:60:4f:4f:4f:c1
fc2/9 100 0x5a0001 20:00:00:25:b5:ab:00:cf 20:00:00:25:b5:aa:00:6f <<<<<
fc2/9 100 0x5a0002 20:00:00:25:b5:ab:00:ff 20:00:00:25:b5:aa:00:8f
fc2/9 100 0x5a0003 20:00:00:25:b5:ab:00:ef 20:00:00:25:b5:aa:00:9f
fc2/9 100 0x5a0004 20:00:00:25:b5:ab:00:8f 20:00:00:25:b5:aa:00:7f
fc2/15 100 0x5a0020 50:0a:09:81:88:4c:be:ef 50:0a:09:80:88:4c:be:ef <<<<<

Total number of flogi = 6.

BGL16.J14.N5K-1# show fcns database

VSAN 100:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0x5a0000 N 20:41:8c:60:4f:4f:4f:c0 (Cisco) npv
0x5a0001 N 20:00:00:25:b5:ab:00:cf (Cisco) scsi-fcp:init fc-gs <<<<<
0x5a0002 N 20:00:00:25:b5:ab:00:ff (Cisco) scsi-fcp:init fc-gs
0x5a0003 N 20:00:00:25:b5:ab:00:ef (Cisco) scsi-fcp:init fc-gs
0x5a0004 N 20:00:00:25:b5:ab:00:8f (Cisco) scsi-fcp:init fc-gs
0x5a0020 N 50:0a:09:81:88:4c:be:ef (NetApp) scsi-fcp:target <<<<<

Total number of entries = 6

Upstream Device Check
BGL16.J14.N5K-2# show flogi database
--------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
--------------------------------------------------------------------------------
fc2/9 200 0xdb0000 20:41:8c:60:4f:4f:53:40 20:c8:8c:60:4f:4f:53:41
fc2/9 200 0xdb0001 20:00:00:25:b5:ab:00:bf 20:00:00:25:b5:aa:00:9f
fc2/9 200 0xdb0002 20:00:00:25:b5:ab:00:9f 20:00:00:25:b5:aa:00:7f
fc2/9 200 0xdb0003 20:00:00:25:b5:ab:00:af 20:00:00:25:b5:aa:00:6f <<<<<
fc2/9 200 0xdb0004 20:00:00:25:b5:ab:00:df 20:00:00:25:b5:aa:00:8f
fc2/15 200 0xdb0020 50:0a:09:82:88:4c:be:ef 50:0a:09:80:88:4c:be:ef <<<<<

Total number of flogi = 6.

BGL16.J14.N5K-2# show fcns database

VSAN 200:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0xdb0000 N 20:41:8c:60:4f:4f:53:40 (Cisco) npv
0xdb0001 N 20:00:00:25:b5:ab:00:bf (Cisco) scsi-fcp:init fc-gs
0xdb0002 N 20:00:00:25:b5:ab:00:9f (Cisco) scsi-fcp:init fc-gs
0xdb0003 N 20:00:00:25:b5:ab:00:af (Cisco) scsi-fcp:init fc-gs <<<<<
0xdb0004 N 20:00:00:25:b5:ab:00:df (Cisco) scsi-fcp:init fc-gs
0xdb0020 N 50:0a:09:82:88:4c:be:ef (NetApp) scsi-fcp:target <<<<<

Total number of entries = 6

Cisco VIC FC Boot Driver
Cisco VIC Adapter Check
BGL16-J14-EUSV-FI-B# connect adapter 1/2/1 adapter 1/2/1 (fls):2# lunlist
adapter 1/2/1 # connect vnic : 15 lifid: 4
No entry for terminal type "dumb"; - FLOGI State : flogi est (fc_id 0x5a0001)
using dumb terminal settings. - PLOGI Sessions
- WWNN 50:0a:09:81:88:4c:be:ef WWPN 50:0a:09:81:88:4c:be:ef fc_id 0x5a0020
adapter 1/2/1 (top):1# attach-fls - LUN's configured (SCSI Type, Version, Vendor, Serial No.)
No entry for terminal type "dumb"; LUN ID : 0x0000000000000000 (0x0, 0x4, NETAPP , P3WYPKEdiLyc)
using dumb terminal settings. - REPORT LUNs Query Response
adapter 1/2/1 (fls):1# vnic LUN ID : 0x0000000000000000
---- ---- ---- ------- ------- LUN ID : 0x0001000000000000
vnic ecpu type state lif - Nameserver Query Response
---- ---- ---- ------- ------- - WWPN : 20:00:00:25:b5:ab:00:ff
15 1 fc active 4 - WWPN : 20:00:00:25:b5:ab:00:ef
16 2 fc active 5 - WWPN : 20:00:00:25:b5:ab:00:8f
- WWPN : 50:0a:09:81:88:4c:be:ef

adapter 1/2/1 (fls):3# lunmap vnic : 16 lifid: 5

lunmapid: 0 port_cnt: 1 - FLOGI State : flogi est (fc_id 0xdb0003)
lif_id: 4 - PLOGI Sessions
PORTNAME NODENAME - WWNN 50:0a:09:82:88:4c:be:ef WWPN 50:0a:09:82:88:4c:be:ef fc_id 0xdb0020
LUN PLOGI - LUN's configured (SCSI Type, Version, Vendor, Serial No.)
50:0a:09:81:88:4c:be:ef LUN ID : 0x0000000000000000 (0x0, 0x4, NETAPP , P3WYPKEdiLyc)
00:00:00:00:00:00:00:00 0000000000000000 Y - REPORT LUNs Query Response
LUN ID : 0x0000000000000000
lunmapid: 0 port_cnt: 1 LUN ID : 0x0001000000000000
lif_id: 5 - Nameserver Query Response
PORTNAME NODENAME - WWPN : 20:00:00:25:b5:ab:00:bf
LUN PLOGI - WWPN : 20:00:00:25:b5:ab:00:9f
50:0a:09:82:88:4c:be:ef - WWPN : 20:00:00:25:b5:ab:00:df
00:00:00:00:00:00:00:00 0000000000000000 Y - WWPN : 50:0a:09:82:88:4c:be:ef
OS LUN Detection
QUIZZZZ !!!

What is the most preferred boot

order for Boot From SAN?
Maintenance actions like FW upgrade
Server Firmware Management through UCSM
Infrastructure FW upgrade
Creating a Host Firmware Package

Right Click, to
create HFP.

Simple config, pulls

the FW versions as
per the build
packages, Advanced
will let admin to set
the required FW
versions.
Firmware Upgrades through Firmware Packages in Service Profiles
QUIZZZZ !!!

Under which tab is the option for

Host Firmware Package Policy?
Questions & Answers