A media company powered a fabric interconnect pair, configured the server ports, and still has no cluster and no virtual management address. The L1 and L2 ports between the interconnects are not cabled. What must be connected?
Select an answer to reveal the explanation.
Short Explanation
The two front desks have phones and signs, and the private hallway between them was never built. You cable L1 to L1 and L2 to L2 so the fabric interconnects can form a cluster and bring up the virtual management address. Server ports face the chassis, and pairing those ports together does not create the cluster.
Full Explanation
A fabric interconnect pair clusters over the dedicated L1 and L2 links, with L1 connected to L1 and L2 connected to L2. That cluster is what elects the primary, synchronizes the domain, and hosts the virtual management address. This media company already configured server ports, so chassis-facing cabling is not the missing piece. The empty L1 and L2 ports are. Connecting L1 to an upstream LAN switch turns a cluster port into a normal network cable and does not let spanning tree elect a fabric interconnect cluster. Server ports discover chassis and blades. Linking them to each other is not a peer-link and does not create the virtual address. Management ports are for IP reachability to the interconnects. They do not replace L1 and L2, and cabling them to the chassis IOMs does not start the cluster. Caveat: the interconnects also need a compatible cluster configuration and reachable management addressing, or the cables alone can be up while the virtual address is still wrong. Operational check: cable L1 to L1 and L2 to L2, confirm both links are up, and confirm the pair reports a clustered state with the virtual management address answering.