Which setup is correct when you configure the Cisco UCS B VICs to reach the Fabric Interconnect Switches for the Cisco UCCE on UCS B deployments?

Question

Options

• ADisable the Fabric Failover only when the UCS B FI connects to a Disjointed L2 domain in the
• BEnable the Fabric Failover to reach both Fabric Interconnect A and B in HA paths
• CDisable the Fabric Failover option.
• DEnable the Fabric Failover only when the UCS B FI connects to a Common L2 domain in the

• A
  7% (3)
• B
  2% (1)
• C
  88% (36)
• D
  2% (1)

Explanation

Disabling Fabric Failover (option C) is correct because Cisco UCCE on UCS B relies on its own built-in High Availability mechanisms to detect and respond to link failures. When Fabric Failover is enabled, the VIC abstracts the physical link state from the OS and application, hiding actual failures from UCCE - this prevents UCCE from triggering its own redundancy processes correctly, breaking the expected HA behavior.

Why the distractors are wrong:

• B is wrong because enabling Fabric Failover to "reach both FI-A and FI-B" sounds intuitive for HA, but it conflicts with UCCE's internal failover logic by masking link-level events that UCCE must see.
• D is wrong for the same reason as B - enabling Fabric Failover regardless of L2 domain type (Common or Disjointed) interferes with UCCE's ability to manage its own redundancy.
• A is wrong because it inverts the logic - it conditionally disables Fabric Failover only for Disjointed L2 domains, but the Cisco design guide recommendation is to always disable it for UCCE deployments, not conditionally.

Memory tip: "UCCE is the boss of its own failover." Since UCCE manages HA itself, you must disable VIC Fabric Failover so UCCE can see real link failures and act on them - if the VIC silently masks a failure, UCCE never knows to respond.

No community discussion yet for this question.