UCS Configuration and Setup Guide.
I.Table of Content.
- a.Cisco UCS Configuration Guide – Part 1 – Overview
- b.Cisco UCS Configuration Guide – Part 2 – Equipment
- c.Cisco UCS Configuration Guide – Part 3 – LAN
- d.Cisco UCS Configuration Guide – Part 4 – SAN
- e.Cisco UCS Configuration Guide – Part 5 – Server
- f.Cisco UCS Configuration Guide – Part 6 – Admin
- G.Cisco UCS Configuration Guide – Part 7 – Firmware Upgrade
If you normally work with traditional servers, then you will have to adjust to the “policy-based”
configuration of compute resources.
The 1st step is to build a Service Template, which is a collection of software
defined policies. This is the hardest part, once you have the template, you can reuse it as many times as you like.
2nd step is to create a Service Profile from the Service Template and then associate the Service Profile with the actual Server hardware. The “association” of the Service Profile and the Server hardware is the equivalent of the fully configured “traditional” server. If the hardware fails, you then associate the Service Profile with the new Server hardware without any change to the Service Profile policy.
The UCS Manager has six fundamental silos: Equipment, Server, LAN, SAN, VM and Admin.
This diagram shows the relationship of how these silos are used.
This is a summary of the tasks that need to be completed to bring a Cisco UCS online with SAN storage, which will be covered in detail during the series:
1.Connect Laptop to Fabric Interconnect-A with Cisco Console cable and assign IP addresses
2.Connect Laptop to Fabric Interconnect-B with Cisco Console cable and join cluster of Fabric Interconnect-A
3.Connect to Cisco UCS Manager with Java-enabled Browser (connect to Cluster IP address)
4.Configure server ports (from Fabric Interconnects to Chassis FEX IO Modules)
5.Acknowledge Chassis, Note: Fabric Interconnects, Chassis and Servers should now be
6.Update UCS Manager to latest version (3 packages required – A-type, B-type and C-type)
7.Configure Uplink ports (from Fabric Interconnects to Nexus)
8.Configure FC ports (from Fabric Interconnects to SAN Switches)
9.Create Pools (5 types) – UUID, IP, WWPN, WWNN and MAC
10.Create VLANs in LAN tab
11.Create VSANs and Assign VSANs to FC ports (SAN cloud, not Storage cloud)
12.Create Service Profile Template – vNICs, vHBAs, Local Disk Policy, Firmware Policy, BIOS Policy, Boot Policy
*13.Create Service Profiles from Service Profile Template
14.Assign Service Profiles to Cisco UCS blades
15.Power On each UCS blade and mount ISO image to install ESXi
NOTE: Internal fabric will not become active until the FC and Ethernet Uplinks are active
NOTE: If multiple UCS Managers are available, deploy UCS Central virtual appliance to manage multiple domains from a single interface
Core Switch cabling and configuration is completed with virtual port-channel
SAN Fabric cabling and configuration is completed
SAN Storage cabling and configuration is completed
VM-FEX is not required (out of scope of this Use-case)
Have a range of IP addresses for Fabric Interconnect & Blade Management
Have a range of WWPN and WWNN addresses for vHBAs
Have a range of MAC addresses for vNICs
Sufficient Fabric Interconnect Port Licences for the required Fabric Interconnect ports (FC, 10GE, FEX, Server)
Cisco UCS Configuration Guide for vSphere Server Profile
Cisco UCS Homepage
Cisco UCS Platform Emulator:
Version 2.5(1aPE1) – UCS M-series: and Version 3.0(2cPE1) – UCS Mini: