500-170: Cisco and NetApp FlexPod Design SpecialistDemo

By Cisco · Question Mode

QuestionQ34

Designing the FlexPod Solution

Refer to the exhibit.

Question Image

Following FlexPod recommended practices, which port-channel configuration is valid for the connectivity shown?

  • A A and B. portchannel 1C and E. po2 and vpc 2D and F. po3 and vpc 3G and H. portchannel 1I and K. po11 and vpc 11J and L. po12 and vpc 12
  • B A and B. vpc 1C and E. po2 and vpc 2D and F. po3 and vpc 3G and H. vpc 4I and K. po11 and vpc 11J and L. po12 and vpc 12
  • C A and B. portchannel 1C and D. po2 and vpc 2E and F. po3 and vpc 3G and H. portchannel 4I and J. po11 and vpc 11K and L. po12 and vpc 12
  • D A and B. portchannel 1C and D. vpc 2E and F. vpc 2G and H. portchannel 4I and J. vpc 11K and L. vpc 11
  • E A and B. po1 and vpc 1C and D. po2 and vpc 2E and F. po3 and vpc 3G and H. po4 and vpc 4I and J. po11 and vpc 11K and L. po12 and vpc 12
Explanation

Cisco/NetApp FlexPod validated designs cable the Nexus switch pair to both the UCS Fabric Interconnects and the NetApp storage controllers using redundant physical links that are bonded into port-channels, and because these port-channels terminate on two different upstream/downstream Nexus switches acting as one logical switch, each port-channel is simultaneously configured as a virtual Port Channel (vPC) with a matching ID on the Nexus pair. Following this recommended practice, every redundant link pair in the topology — the Fabric-Interconnect-facing bundles and the NetApp-facing bundles alike — is assigned a corresponding poN and vpc N pair (for example po1/vpc1 through po4/vpc4 for the fabric interconnect uplinks and po11/vpc11, po12/vpc12 for the storage links), which is the consistent numbering pattern that matches valid FlexPod connectivity.

Community Discussion

No comments yet. Be the first to start the discussion!