143-120 · Question #109
You have consolidated several Linux servers to an LPAR on a mainframe that also has some LPARs with FICON channels. All LPARs have connections to the same fabric switches. Which type of zoning…
The correct answer is D. D,I zoning should be used for the FICON connections and WWN zoning should be used for the Linux. Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test…
Question
You have consolidated several Linux servers to an LPAR on a mainframe that also has some LPARs with FICON channels. All LPARs have connections to the same fabric switches. Which type of zoning should be used?
Options
- ADomain Index (D,I) zoning must be used for all connections.
- BWWN zoning must be use for all connections.
- CWWN zoning should be used for the FICON connections and D,I zoning should be used for the Linux
- DD,I zoning should be used for the FICON connections and WWN zoning should be used for the Linux
How the community answered
(26 responses)- A4% (1)
- B12% (3)
- C4% (1)
- D81% (21)
Explanation
Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at any of the email addresses listed below. Any problems about IT certification or our products, you could rely upon us, we will give you satisfactory answers in 24 hours.
Topics
Community Discussion
5
Lena V.Oct 23, 2025D is the one you want locked in. FICON requires D,I zoning because IBM mandates it for mainframe FICON channels on shared fabrics, and WWN zoning covers your Linux LPARs where D,I is not required and WWN gives you the port-level flexibility Linux workloads expect.
Wesley A.Oct 25, 2025D is right, but option C will absolutely wreck you if you memorized "WWN zoning is best practice" without thinking about what FICON actually requires. FICON demands D,I zoning because the protocol is channel-address dependent, while your Linux LPARs on the same fabric stay on WWN zoning since they just run standard FCP like any other open-systems host.
Viktor S.Oct 31, 2025Took me a second on this one because I almost flipped it in my head, then remembered FICON is a control-unit protocol that keys off of physical port locations so D,I zoning is the right fit there, while your Linux HBAs are just plain Fibre Channel hosts that move around and need WWN zoning to stay flexible. Saw a guy at my testing center change his answer on this one right before submitting and walk out looking confident, heard later he got it wrong, which is what happens when you memorize "always use WWN" without understanding that FICON plays by different rules.
Orla P.Nov 13, 2025C has to be right here because FICON is notoriously picky about its fabric environment and IBM consistently steers you toward WWN zoning for those connections to avoid the port-binding headaches that come with D,I in a mixed setup, while the Linux LPARs on the same fabric get the tighter D,I control you want when you are consolidating workloads onto shared infrastructure. The split approach in C is exactly what makes sense when you have two different traffic types sharing the same switches.
Viktor S.Nov 15, 2025Orla, that reasoning sounds intuitive but it is backwards. IBM actually recommends D,I zoning for FICON precisely because mainframe channel paths are stable and predictable, making port-based zoning the safer, more manageable choice there, while the Linux LPARs with their swappable HBAs are the side of the house where WWN zoning earns its keep.