FBAP_002 practice question 5 of 15

A FlashBlade is designed with a properly implemented single 4x40Gb/s LAG. During implementation, the architect is informed that the ISL on the uplink switches in broken. The customer has no budget to repair or replace it. What should the architect do?

Full set: 75 questions

Domain Implement, Migrate, and Integrate FlashArray and FlashBlade Solutions

Answer options
A: Divide the single LAG into one LAG per switch. *** Correct answer
B: Change out the 40Gb/s cable for breakout cable.
C: Using the same LAG, create a second subnet and VIP.
D: Remove all uplink from FM2.
Correct Answer:
A. Divide the single LAG into one LAG per switch. ***
Explanation

A single Link Aggregation Group (LAG) spanning two physical switches requires a functional Inter-Switch Link (ISL) or a multi-chassis link aggregation technology (like MLAG or vPC) to make the switches appear as a single logical device. When the ISL is broken, the switches operate independently. This causes a Layer 2 loop and MAC address flapping, leading to severe network instability. The correct architectural solution is to reconfigure the network into two separate LAGs, with one LAG connecting to each independent switch. The FlashBlade networking stack is designed to manage traffic and failover across multiple independent network interfaces, thus preserving redundancy and restoring stability.

Why Incorrect

B. Changing to breakout cables alters the physical connection speed but does not solve the fundamental Layer 2 problem of a single LAG spanning two independent switches.
C. Adding a second subnet and VIP is a Layer 3 action. It will not fix the underlying Layer 2 MAC flapping and instability caused by the misconfigured LAG.
D. Removing all uplinks from a Fabric Module cripples the system's high availability and performance, which contradicts the core design principles of FlashBlade for redundancy.

References

1. Pure Storage, "FlashBlade Networking Deployment Guide," Page 10, Section: "Network Topology Options."

This guide explicitly differentiates between connecting to switches with MLAG/vPC and connecting to independent switches. It states, "If the upstream switches are not configured for MLAG/vPC... two separate LACP bonds must be created. One bond will connect to the first switch, and the second bond will connect to the second switch." A broken ISL effectively creates an independent switch scenario, mandating this approach.

2. Pure Storage, "FlashBlade Best Practices," Document ID 200-000135-00, Section: "Network Architecture."

This document emphasizes designing for high availability by connecting to two separate, redundant top-of-rack switches. It details that in a non-MLAG environment, separate network bonds (LAGs) to each switch are required for the FlashBlade to manage redundant paths correctly. The scenario described (broken ISL) reverts the network to a non-MLAG state, making separate LAGs the only viable solution.

Scroll to Top