You have multiple FC routers connected to the same edge fabric. You need to reduce the resources used in an FC router by limiting the number of LSAN zones. What would you do to accomplish this task?

Goran A.Nov 12, 2025

B is correct, and if you have worked with FC router deployments longer than five minutes you already know why. When you tag an LSAN zone with an enforce tag and configure only certain FC routers to honor that tag, those routers will not import LSAN zones that do not match, which directly limits the number of proxy devices and LSAN zone entries each router has to maintain in its forwarding tables. Without tagging, every FC router connected to that edge fabric sees every LSAN zone and allocates resources for all of them, and in a large multi-fabric environment that burns through your router proxy limits fast. Target proxies (A) are the result of LSAN processing, not a control mechanism for limiting it, and QoS (C) and speed tags (D) have nothing to do with zone import behavior at all. Bottom line: enforce tags give you surgical control over which routers participate in which LSAN zones, and that is the knob Brocade gives you to solve exactly the resource problem this question is describing.

Prof. SaraNov 15, 2025

The enforce tag is your scalpel here, letting each FC router selectively recognize only the LSAN zones tagged for it rather than processing every LSAN zone across the entire shared edge fabric, which is exactly where resource savings come from. Here is my question for you: can you explain why simply reducing the total number of LSAN zones in the fabric is not the same thing as controlling which router enforces which zones, and how the tagging mechanism makes that distinction possible?

Hiroshi T.Oct 31, 2025

Almost went with D, but enforce tag limits LSAN propagation, not speed.