Which two components are required when the integration of Cisco UCS C-series servers within a Cisco UCS Manager Direct Connect mode? (Choose two )

Question

Options

• ACompatible Cisco Nexus Fabric Extenders
• BCisco Management Controller
• CCompatible UCS VIC adapter installed via the server's PCIe or MLOM slot
• DCompatible UCS 6200 or 6300 Fabric Interconnects
• ECompatible Cisco UCS Manager version

• A
  1% (1)
• B
  4% (3)
• C
  93% (65)
• E
  1% (1)

Explanation

Integrating C-Series servers into UCS Manager Direct Connect mode requires two physical infrastructure elements: a UCS VIC adapter (C) in the server, and Fabric Interconnects (D) to terminate those connections. The VIC adapter - installed in a PCIe or MLOM slot - is what enables the server to speak the UCS protocol and be discovered and managed by UCS Manager. The 6200/6300 Fabric Interconnects are the management and switching backbone that UCS Manager runs on; without them, there is no "UCS Manager Direct Connect" topology at all.

Why the distractors are wrong:

• A (Nexus FEX): FEX modules are used in the older Nexus-attached C-Series integration model, not Direct Connect. Direct Connect eliminates the middleman switch entirely.
• B (Cisco Management Controller / CIMC): CIMC is the built-in BMC for standalone C-Series management; in Direct Connect mode, UCS Manager takes over that role via the FIs - CIMC is not the enabling component.
• E (UCS Manager version): Software compatibility matters operationally, but UCS Manager is bundled on the Fabric Interconnects - it is not a discrete required "component" the way hardware is.

Memory tip: Think "VIC to FI" - the server needs a VIC to talk UCS, and the FI is the other end of that conversation. No VIC, no connection; no FI, no manager. Everything else (FEX, CIMC, software versions) belongs to different modes or is implied.

No community discussion yet for this question.