An Implementation Engineer has completed cabling a DirectFlash Shelf (DFS) to the FlashArray.

Adding an external DirectFlash Shelf (DFS) or a legacy SAS Expansion Shelf to a Pure Storage FlashArray requires precise physical cabling to ensure backend high availability. Because the controllers utilize an active/active backend topology—where both controllers must maintain redundant loops to every single capacity shelf—a single misplaced cable can cause a severe hardware fault.

Once the physical installation is complete, the Implementation Engineer must definitively validate the topology before handing the array over to production. To do this, they log into the local KVM console or SSH session using the restricted puresetup account. From here, the official Pure Storage post-installation procedure dictates running two specific Python validation scripts: storage_view.py enclosures and storage_view.py config .

While both are used, storage_view.py config is the primary command utilized to map the specific SAS or NVMe-oF (RoCE) port bindings. The script actively polls the physical ports on the rear of the controllers and traces the loops down through the I/O Modules (IOMs) on the shelves. If the cabling is flawless, the CLI will explicitly return: "No errors detected." If a cable is crossed (e.g., Controller 0 plugged into IOM 1 instead of IOM 0), the script will instantly flag the topology mismatch, allowing the engineer to correct it on the spot.