nerdexam
Network_Appliance

NS0-520 · Question #202

You are testing FCP paths failures on a 2-node Netapp AFF All SAN Array and verify that persistent ports are correctly enabled. Before testing, a host sees four optimized paths to a LUN. You perform…

The correct answer is A. The host sees four optimized paths to the LUN. Support for persistent ports Beginning in ONTAP 9.8, persistent ports are enabled by default on All SAN Arrays (ASAs) that are configured to use the FC protocol. Persistent ports are only available for FC and require zone membership identified by World Wide Port Name (WWPN)…

ONTAP SAN Solution Troubleshooting

Question

You are testing FCP paths failures on a 2-node Netapp AFF All SAN Array and verify that persistent ports are correctly enabled. Before testing, a host sees four optimized paths to a LUN. You perform a node takeover and re-check the host. Which statement is true after the node takeover?

Options

  • AThe host sees four optimized paths to the LUN
  • BThe host sees two non-optimized paths and two dead paths to the LUN
  • CThe host sees two optimized paths and two non-optimized paths to the LUN
  • DThe host sees two optimized paths and two dead paths to the LUN

How the community answered

(29 responses)
  • A
    72% (21)
  • B
    17% (5)
  • C
    7% (2)
  • D
    3% (1)

Explanation

Support for persistent ports Beginning in ONTAP 9.8, persistent ports are enabled by default on All SAN Arrays (ASAs) that are configured to use the FC protocol. Persistent ports are only available for FC and require zone membership identified by World Wide Port Name (WWPN). Persistent ports reduce the impact of takeovers by creating a shadow LIF on the corresponding physical port of the HA partner. When a node is taken over, the shadow LIF on the partner node assumes the identity of the original LIF, including the WWPNe. Before the status of path to the taken over node is changed to faulty, the shadow LIF appears as an Active/Optimized path to the host MPIO stack, and I/O is shifted. This reduces I/O disruption because the host always sees the same number of paths to the target, even during storage failover operations.

Topics

#persistent ports#FCP paths#node takeover#All SAN Array

Community Discussion

No community discussion yet for this question.

Full NS0-520 Practice