- The load balancing etc should be taken care of at the OS level
- So assuming that you are using the VMWare vSwitch
- As an example, you can allocate two vmnics to the same vSwitch
- One of these vmnics can point to FI A and the other to FI B
- You can choose the FI preference in the UCS vNIC settings
- Then choose 'Route based on originating virtual port ID' as the load
- This would distribute your traffic across the two interfaces
However, you might configure VMkernel interfaces for eg. VMotion or iSCSI/NFS differently
2 vnic's one connected to fabric A resp B, no hardware failover flag set; and go active/passive
Policy Fail back
Policy Fail back
I hope you are aware of the fact, that e.g. in case of VMotion, if source is on A, destination on B, same Vlan -> traffic has to go out of UCS, which can be a bottlenek, and adds at least one additional hop.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...