nerdexam
Brocade

143-130 · Question #92

You are using channel extension with FICON Acceleration between two remote sites using Brocade 7800s and a cascaded Brocade DCX 8510. You need to isolate paths to specific ports. Which feature…

The correct answer is A. TI Zone with failover disabled. See the full explanation below for the reasoning.

Question

You are using channel extension with FICON Acceleration between two remote sites using Brocade 7800s and a cascaded Brocade DCX 8510. You need to isolate paths to specific ports. Which feature should you use?

Options

  • ATI Zone with failover disabled
  • BTI Zone with failover enabled
  • CExchange Based Routing
  • DBrocade Trunking

How the community answered

(55 responses)
  • A
    73% (40)
  • B
    7% (4)
  • C
    5% (3)
  • D
    15% (8)

Community Discussion

8
Imani T.Imani T.Jun 5, 2026

TI Zone with failover disabled is your answer here. When you need to lock paths down to specific ports in a FICON over channel extension environment with cascaded Brocade gear, you use Traffic Isolation Zoning with failover off because failover enabled would allow traffic to spill onto other paths if the preferred one goes down, which defeats the whole point of isolating to specific ports for FICON compliance and deterministic routing.

8
Hiroshi T.Hiroshi T.Jun 1, 2026

TI Zones with failover disabled is correct here. When you need to isolate paths to specific ports in a FICON over channel extension environment, failover must be disabled because FICON does not support dynamic path changes, and the Brocade FICON Channel Extension documentation explicitly states that TI Zones used for FICON Acceleration must have failover disabled to maintain strict path isolation.

2
Lena V.Lena V.May 27, 2026

Going with D on this one, and here is why it makes sense to me. The 7800 is purpose-built for long-distance extension over IP or DWDM, and Brocade Trunking is exactly the mechanism that aggregates ISL bandwidth and controls which physical ports traffic flows across between those switches. When you have a cascaded DCX 8510 in the mix, trunking lets you pin specific paths by controlling trunk group membership, which is the practical way to isolate traffic to particular ports in that kind of topology. The FICON Acceleration piece needs deterministic, low-latency path control, and trunking gives you that port-level granularity without the overhead of zone policy changes every time you adjust. I have seen TI Zones come up in routing questions but those are more about frame-level routing preferences across a fabric, not the physical port isolation the question is describing with that hardware combo.

0
Imani T.Imani T.May 27, 2026

Lena, good breakdown but I think A is the call here, because TI Zones are specifically designed to bind traffic to designated ISL paths in the fabric, which is exactly the mechanism Brocade documentation points to for isolating FICON traffic across that kind of cascaded topology. Trunking manages bandwidth aggregation and port grouping, but the actual traffic path enforcement for FICON Acceleration scenarios is handled at the zone policy layer with TI Zones, not the trunk configuration.

0
Luis F.Luis F.May 21, 2026

Exchange Based Routing isolates paths to specific ports in FICON environments, go with C.

-2
Hiroshi T.Hiroshi T.May 24, 2026

Luis, Exchange Based Routing ensures frames within the same exchange follow a single consistent path to preserve ordering, it does not isolate paths to specific ports, so C does not fit that definition. The correct answer is A, which aligns with what the official IBM FICON documentation actually describes for that function.

0
Samuel O.Samuel O.Jun 9, 2026

I keep coming back to B on this one and here is why it actually makes sense in context. TI Zones with failover enabled give you the path isolation you need for FICON traffic across those 7800s while still protecting you if a link goes down, because the zone will reroute rather than just drop your channel connections cold. In a cascaded DCX 8510 environment where you have multiple possible paths through the fabric, you want that deterministic routing behavior to steer traffic to specific ports, but you cannot afford a single point of failure on a mainframe channel. Failover disabled sounds like stronger isolation on paper, but in production FICON that is a risk I would never take because a dead path means a dead channel end, and that is a conversation nobody wants to have with the storage team at 2am.

-2
Imani T.Imani T.Jun 11, 2026

Samuel, I get where you are coming from but the correct answer is A, TI Zones with failover disabled, because IBM explicitly requires strict path isolation for FICON and the mainframe handles path redundancy at the channel level through the IODF definitions, so fabric-level failover actually interferes with the deterministic routing FICON depends on rather than protecting it.

0
Full 143-130 Practice