A storage administrator is configuring inter-VSAN routing on a fabric that contains duplicate domain IDs. Which feature must be configured to ensure continued operation?

Question

Options

• Aauto topology
• Btransit VSANs
• CIVR NAT
• Dvirtual domains

• A
  2% (1)
• B
  7% (4)
• C
  80% (44)
• D
  11% (6)

Explanation

IVR NAT (Network Address Translation) solves the duplicate domain ID problem by translating the conflicting domain IDs into unique virtual domain IDs at the IVR boundary, allowing traffic to flow between VSANs without address conflicts. Without NAT, IVR cannot route between fabrics that share the same Fibre Channel domain ID, since the routing logic would be unable to distinguish between identical addresses across VSANs.

• A. Auto topology is an IVR feature that automates the discovery of IVR topology, but it does nothing to resolve domain ID conflicts - it will simply fail or produce incorrect routing if duplicates exist.
• B. Transit VSANs are VSANs used as intermediary paths to connect edge VSANs that aren't directly connected; they're an IVR topology concept, not a conflict-resolution mechanism.
• D. Virtual domains is the result of enabling IVR NAT (NAT creates virtual domain IDs), not a standalone feature you configure independently to fix the conflict.

Memory tip: Think of IVR NAT like NAT in IP networking - just as IP NAT translates private addresses to avoid conflicts on the internet, IVR NAT translates duplicate FC domain IDs to avoid conflicts across VSANs. If you see "duplicate domain IDs + IVR," the answer is always NAT.

No community discussion yet for this question.