143-120 · Question #107
You used a 2-byte link address for installing new storage on a single (non-cascaded) Brocade DCX-4S Director. Unfortunately you cannot configure the CHPID online. Which statement is true?
The correct answer is D. Ensure that you have enabled insistent domain ID. See the full explanation below for the reasoning.
Question
You used a 2-byte link address for installing new storage on a single (non-cascaded) Brocade DCX-4S Director. Unfortunately you cannot configure the CHPID online. Which statement is true?
Options
- A2-byte link-addresses only work in cascaded FICON fabrics.
- BEnsure your channel is not connected to a 48-port blade.
- CEnsure that the first byte in the 2-byte link address is set to 0xFF.
- DEnsure that you have enabled insistent domain ID.
How the community answered
(33 responses)- A15% (5)
- B3% (1)
- C6% (2)
- D76% (25)
Community Discussion
7Good discussion thread, wanted to add some context on this one. The correct answer is D, ensure that you have enabled insistent domain ID. When you use a 2-byte link address on a non-cascaded Brocade DCX-4S, the switch's domain ID becomes part of how the CHPID resolves the physical path to the device, and if the domain ID is not locked in place (insistent), the fabric can reassign it, which breaks the mapping and prevents the CHPID from coming online. Insistent domain ID guarantees the switch always claims the same domain ID after a reboot or fabric disruption, which is what makes the 2-byte link address stable enough to use. The other options are distractors, since 2-byte addresses do work in non-cascaded environments, the blade type is not the constraint here, and 0xFF in the first byte is not a requirement for this to function.
D is the right answer. On a non-cascaded DCX-4S, if you used a 2-byte link address and the CHPID cannot be configured online, the fix is to enable insistent domain ID, because without it the switch may get assigned a different domain ID at fabric initialization, which breaks the link address mapping and prevents the channel from coming online.
I kept thinking B, but domain ID persistence is what actually unlocks online config.
Domain ID persistence is necessary but remember the key qualifier here, it "enables" online config, it does not by itself activate it, you still need the allow-list entry on the controller side.
D is right, insistent domain ID locks the switch address so your 2-byte CHPID mapping stays valid.
Saw this exact trap, froze, then remembered "INSIST to go online" and picked D cold.
A, 2-byte link addresses are strictly a cascaded FICON fabric thing.