Benefits to vPC on 6200s (Fabric interconnects) in UCS
I'm a network guy, not VMware. There are benefits to having the Nexus 5Ks vPC'd together and have a single port channel going upstream to a pair of vPC'd 7Ks. I've heard this refered to as a 'bowtie' or 'figure 8'.
Are there similar benefits with the UCS 6Ks to the 7Ks or with the ensuing VMware cfg? Like maybe simplifying the pinning to the uplinks.
Re: Benefits to vPC on 6200s (Fabric interconnects) in UCS
The 6200's are not clustered switches as you might find with a pair of N5Ks/N7Ks. Best practice for UCS uplinks in thei regard would be to create port channels on from each 6200 side, going up to separate N5K/N7Ks as VPCs. This gives full mesh redundancy from each fabric.
From a VMware perspective, you would not do any specialized channeling at the vSwitch/vDS level. You woud use the default vSwitch teaming method - which is Source-Base-On-Virtual-Port-ID. This allows multlple uplinks connected to the same vSwitch wtihin VMware, without having to aggregate any of the links. This would completely complement the UCS configuration.
Hope this makes sense, if not let me know.
These two deployement guide would be a good read for you:
This article demonstrates the ability to toggle the boot order on a standalone C-Series server using the unified XML API. This is one of the many things that the programmatic nature of the API allows you to do, and helps facilitate and expedite initial sy...
Hello Team, I read a Cisco article back in Oct. 2019 on the UCS N20-C6508 blade chassis going EOSL on November 30th 2021 but now I am noticing on the Cisco Warranty online portal that its not showing any date announcements. I checked with Cisco ...
Since I was unable to find any info in the documentation or forums on this topic, I'm sharing my findings here. We did get boot to a M.2 SSD in RAID1 to boot ESXi on a new UCS Mini/FlashStack deployment with the new "UCS-M2-HWRAID Boot-Optimized M.2 RAID ...
We have discovered that sometimes UCS Server firmware doesn't always install properly. When you look at the server firmware, it displays sometimes like this;Firmware Version3.1(2f)C,3.2(3i)C Now we have track some of this down to human error. &...