In Cisco UCCE, what is the reference design for vmnic configuration on UCS Tested Reference Configuration (TRCs)?

Question

Options

• AAn active-standby scheme
• BWith UCS B, use only active-active scheme with Fabric Interconnect switch (FI)
• CEither Mode (active-active or active-standby) with Nexus 1000v
• DAn active-active non-failover ride scheme

• A
  6% (3)
• B
  88% (46)
• C
  4% (2)
• D
  2% (1)

Explanation

Option B is correct because in Cisco UCCE Tested Reference Configurations using UCS B-Series blade servers, the Fabric Interconnect (FI) inherently provides fabric-level redundancy, making the active-active vmnic scheme the validated and recommended design - it maximizes bandwidth utilization while leveraging the FI's built-in high availability rather than relying on NIC-level failover.

Option A (active-standby) is wrong because it wastes half the available uplink bandwidth and is not the TRC-validated design for UCS B; active-standby is more relevant to traditional rack-mount server environments. Option C is wrong because it introduces the Nexus 1000v virtual switch, which is a separate software-defined switching solution not specified as the reference for UCS B TRCs, and "either mode" is overly permissive - TRCs define a specific validated configuration. Option D is wrong because "active-active non-failover ride" misrepresents the scheme; the active-active design with the FI does support failover, just at the fabric layer rather than the NIC layer.

Memory tip: Think "B for Blade = Balanced (active-active)" - UCS B-Series blades connect through Fabric Interconnects that already handle redundancy, so you go fully active-active and let the FI do the heavy lifting.

No community discussion yet for this question.