I'm preparing to do a UCS upgrade from 1.3(1n) to 2.0. In reading all of the release notes I have two things that I need a little clarification on.
#1. FCOE VLAN ID. I understand that this can no longer overlap with an ethernet vlan ID. The current systems (2 fabric interconnects, 2 5108 chasis) does have vlan 1 defined as the FCOE vlan ID and an ethernet vlan. If I change the FCOE VLAN ID to something not used ahead of time (say 20), what is the impact of that? This VLAN ID is only used within the UCS infrastructure. There is only 1 VSAN configured globally and it's ID is 1.
#2. Some of the network interfaces are configured for "Enable Failover" but I believe are also configured for Teaming on the host side. The hosts are both ESXi and Windows. What is the impact of this? Is it simply traffic black holing during a period when the nic has failed over but a VM hasn't sent out any data traffic, so the MAC isn't known yet? Would it simply be an outage until data traffic is seen from the guest? Is it recommended to remove the "Enable Failover" option for all interfaces before an upgrade? If so, is there any impact when you do that to a network interface?
Is it recommended to upgrade to 2.0 or just go to 1.4? It sounds like the early issues of PCI interface renumbering in 2.0 have been worked out.
Had all my servers off for the 2.0 update, and I think the vlan change rebooted them.
I use "Enable Failover" and never team nic's. All the traffic is moving on 1 vNIC if you bind to an FI anyhow. It just confuses teaming I have found. You only have one Mez card and if it fails you lose everything anyway. Just us "Enable Failover" and one vNIC. When you upgrade as each FI and IOM's reboot, you lose the path. Usually no big deal. "Enable Failover" just switches active FI and you are good vNIC wise. For vHBA's it fails just like a dual fabric would expect.
My advice is go to the latest 1.4x unless you need features that only 2.0 has, like iSCSI boot or something.
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. &...
Cisco UCS Platform Emulator, Release 4.0(4ePE1)
CONFIGURATION IMPORT NOTE: Importing configuration backups (All, System, or Logical) taken from the UCS Platform Emulator (UCSPE) to physical UCS Manager domains is not recommended or supported...