Cisco UCS Fabric Interconnect Clustering Redundancy
A network architect designs a high-availability architecture for the Cisco UCS Fabric Interconnects that are installed in a data center. The architecture must support clustering and redundancy. Which architecture meets these requirements?
Community Votes
67% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests knowledge of UCS FIs' dedicated cluster ports (L1/L2) and mandates using standard Ethernet cables for these specific inter-FI links to ensure redundancy.
This question tests the correct physical cabling topology for high-availability clustering between Cisco UCS Fabric Interconnects, specifically distinguishing between twinax and Ethernet cable requirements.
Many candidates incorrectly choose twinax cables (Options A or B), likely confusing the cluster interconnect with server uplink ports (like L3/L4) which often use direct attach copper (DAC/twinax).
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Correct answer: C — The architecture requires dual connections from port L1 to L2 on one FI and L2 to L1 on the other using Ethernet cables. In a Cisco UCS domain, the Fabric Interconnects must be clustered for high availability. The dedicated cluster ports are labeled L1 and L2. To provide redundancy, you connect L1 on FI-A to L2 on FI-B, and L2 on FI-A to L1 on FI-B. These specific ports are designed to operate over standard Ethernet cabling (typically 10GbE SFP+), not twinax/DAC cables which are typically reserved for server connectivity ports like L3/L4.Why the Other Options Are Wrong
Option A suggests L1-to-L1 connections, which would create a loop or fail to establish the required cross-cluster link; additionally, it specifies twinax cables which are incorrect for L1/L2 cluster ports. Option B uses the correct cross-connection logic but specifies twinax cables, which is technically inaccurate for the L1/L2 cluster interface in this context. Option D suggests connecting L1 to L1 and L2 to L2, which does not provide the necessary diversity or proper cluster handshake mechanism, and while it uses Ethernet, the port mapping is wrong.Community Comment Notes
The community vote strongly favors option C, with one user noting that "dual connections between L1 and L2 ports... with standard Ethernet cables provides a redundant high-availability architecture." Another commenter initially suggested D based on a document but later corrected themselves, highlighting the confusion around port labeling. The consensus confirms that the cross-connect (L1-L2, L2-L1) with Ethernet is the standard design.Exam Strategy
Always verify the specific port types on hardware diagrams. Remember that 'Cluster Ports' on UCS FIs are distinct from 'Server Uplink Ports'. Cluster ports (L1/L2) use Ethernet, while server ports (L3/L4) often use Twinax/DAC.
Frequently Asked Questions
Why can't I use twinax cables for UCS FI cluster ports?
Twinax (DAC) cables are typically used for server uplink ports (L3/L4). The dedicated cluster ports (L1/L2) are designed for standard Ethernet SFP+ modules and cabling.
What is the purpose of connecting L1 to L2 instead of L1 to L1?
Cross-connecting L1 to L2 ensures that if one internal switch plane fails, the other path remains active, providing true redundancy for the cluster control plane.