This is a GREAT post over at Reddit ANYONE who takes upgrading code on Cisco UCS as BAU.

ALWAYS have serial access to a UCS logged in and watch the process of FI’s upgrading and rebooting. Have “Restoring from bricked FI” as part of the backout plan and practice in a lab.

I noticed this post because it has links back to

Sobering and entertaining stories of upgrades gone wrong at below link.

Cisco UCS: How often does the primary FI (fiber interconnect) blow up when you are upgrading the firmware on the subordinate FI? from sysadmin

Can honestly say “Been there, done that, have the t-shirt”

Configuring Policy Based Zoning in Cisco UCS Central 1.5

Create SAN Connectivity Policy


Select Organization and Name



Create Zoning. These will be the WWPN’s in Boot Policy. So far have only been able to select VSAN 1. That is fine since VSAN 1 is unique per FI


Create SAN Connectivity Policy


Select Org and Name


Select WWPN Pool


Select vHBA Initiators


Select the Storage Connectivity Policy that matches required Zoning


What an EPIC test!

Cisco Systems commissioned Network Test, an independent third-party test lab, to help answer that question. Network Test assessed the Cisco Nexus 9516 core switch fully loaded with 128 100G interfaces, making this the largest Cisco Nexus 9000 Series evaluation ever conducted.

Looking forward to 100G uplinks in the UCS FI’s.

Read More:


Is anyone doing this out there? It needs to happen.

Hit me on twitter with a DM if you know of any

Intelligent End-to-End Automation with Network Integrated Hyperconvergence
Simplified Operations – Hyperconverged and Converged Infrastructure Working Together
Independent Scaling of nodes, compute or capacity with UCS Racks and Blades
Private and Hybrid Cloud Automation with UCS Director and CloudCenter
Tech Preview of our new HyperFlex Monitoring and Management Dashboard

Good post over at

“Ensure traffic types are spread across different PCIe slots or channels. With the UCS, we use Adapter Placement Policies to accomplish this”

Real World Cisco UCS Adapter Placement

Good post over at

“FI will prompt you to sync the firmware on the FI to the one that is running the cluster”

YES! This makes replacing failed FI’s much easier. Not sure I would trust this and would probably match code before adding new FI first anyhow. This is the kind of procedure that has “New code bug” found after wiping both FI’s all over it.

Read More:

A good post on Dual VIC’s over at

My take is don’t bother unless it is about throughput to a server. Doubt any one server will ever have that much throughput. Also sometimes the dual VIC’s allows for desired vNIC speeds and may be worth it.



Still not sure what I think of HyperFlex I would “Just buy a standard UCS” and install ESX with VSAN, but UCSguru has a good post on sizing HyperFlex.

“Calculating the usable capacity of your HyperFlex cluster under all scenarios is worth taking some time to fully understand

The most significant design decision to take, is whether to optimise your HyperFlex cluster for Capacity or Availability, as with most things in life there is a trade-off to be made.

If you size your cluster for maximum capacity obviously you will lose some availability, likewise if you optimise your cluster for availability you will not have as much usable capacity available to you.

The setting that determines this is the Replication Factor

Read More:

« Older entries