Nice page all about Cisco ONE Enterprise Cloud Suite. Of course UCS is a part. The coolest part :)

Had to toss together quickly a high level “What is going to happen” email regarding updating code on a UCS. Put the below together in a blazing 15 minutes. Isn’t perfect but was fun to make. Thought I would share my primitive diagram skills. Feel free to crib any of this for your purposes.

UCS has two controllers FIA & FIB. 50% of connectivity for each server on UCS goes through the Active/Active controllers. Each FI is rebooted for code update, one at a time.

For SAN:
If the a server has 4 paths to SAN, 2 are on each FI. So 2 will fail each FI update, but the updates are staggered so connectivity is never lost completely. Multipathing should handle this server side.

For Network:
When networking fails over Bonded NIC’s will see one side fail at a time but not both at once. If only one NIC is present on server, UCS will handle failover and server will not see it (other than tcp/ip session reconnect but interface will not go down).

Most servers live through this without any issues. ESX, Linux, and Windows bare metal servers usually do fine.

Can only give a 99% guarantee that a server will have no issues.

Graphical interpretation of upgrade below


Doctors are working on a cure… but only more UCS seems to help :)

Story of my life, stuck at 99% (on many levels sometimes) :)

UCS Yoda says “UCS or Do Not, there is No Try”

UCS Yoda says “UCS or Do Not, there is No Try”

Best document for making Policy Based Zoning and direct attached storage happen on the hurry-up.
Cisco UCS Local Zoning Configuration Example

Both FI’s are a world onto themselves, always check both.

BigUCS-A# connect nxos a

Let’s say the MAC is 0050.1234.1234 and we find it on FIA.

BigUCS-A# show mac address-table dynamic  |grep 0050.1234.1234

* 327      0050.1234.1234    dynamic   0          F    F  Veth3724

Now we know the MAC belongs to Veth3724! :)

Another need might be listing all MAC’s in a vlan:

BigUCS-A# show mac address-table vlan 250

To find Service Profile the Virtual Interface (VIF) belongs to: 

BigUCS-B(nxos)# show interface vethernet 3724
Vethernet3724 is up
Bound Interface is port-channel1000
Hardware: Virtual, address: 7777.1234.9000 (bia 7777.1234.9000)
Description: server 8/7, VNIC nic7 (There ya go, the vethernet belongs to Server 8/7, nic7)
Encapsulation ARPA
Port mode is trunk
EtherType is 0x8100
885402916 unicast packets  6424 multicast packets  1543 broadcast packets
885410883 input packets  440712548014 bytes
0 input packet drops
1216581715 unicast packets  87995452 multicast packets  26284108 broadcast packets
1330861275 output packets  485079662330 bytes
0 flood packets
0 output packet drops

From knowing the Blade the corresponding Service Profile can be found with:

BigUCS-B(nxos)# exit

BigUCS-B(nxos)# show server assoc 8/7 

Remember to have fun during your UCT (Unified Computing Transcendence). This is an amazing interview with a great mind. A must listen interview for delving into the pleasure of curiosity and creativity itself.

Cisco UCS Performance Manager
All is running on VolGroup-lv_root (dm-0) “/”
[root@lucprf01094p01 ~]# dmsetup ls
VolGroup-lv_swap        (253:1)
VolGroup-lv_root        (253:0)
This is a VM and hanging in there with 4 cores and 32GB of memory just fine. CPU’s are working for sure.
rwucs ucs perf top iostat

rwucs ucs perf top iostat


Good YouTube on Cisco UCS Performance Manager by the “UCS Guys” at Cisco.

Monitoring UCS Integrated Infrastructure with UCS Performance Manager


Have to 101% agree with “#1 Don’t assume that your server multi-pathing software is installed or working, or even licensed, or installed but never used/tested by your server team!”

To be good with UCS, have to understand the foundations of SAN.

5 Top Challenges of SAN Design: View from our SAN Design Experts – Part 1

« Older entries