After adding two nodes to a FC-enabled cluster, what is required to allow existing LUNs to use paths on the new nodes?

After adding two nodes to a FC-enabled cluster, what is required to allow existing LUNs to use paths on the new nodes?

• A. lun map add
• B. add-path
• C. lun mapping add-reporting-nodes
• D. set-lun-path

Answer: (C)

When you add new nodes to a FC-enabled NetApp cluster, those nodes become potential path sources for existing LUNs, but only if the LUN’s mapping is updated to include them as reporting nodes. The pathing and visibility of a LUN to hosts depend on which cluster nodes report that LUN; the new nodes won’t automatically start serving or presenting paths until they’re added to the LUN’s reporting-nodes list. Using the operation to add the new nodes as reporting nodes updates the LUN mapping so the hosts can access the LUN via those new nodes’ Fibre Channel paths, enabling proper path failover and load sharing across all available paths. Other options either map the LUN to a host or adjust path settings, but they don’t extend which cluster nodes report the LUN for existing paths.

When you add new nodes to a FC-enabled NetApp cluster, those nodes become potential path sources for existing LUNs, but only if the LUN’s mapping is updated to include them as reporting nodes. The pathing and visibility of a LUN to hosts depend on which cluster nodes report that LUN; the new nodes won’t automatically start serving or presenting paths until they’re added to the LUN’s reporting-nodes list. Using the operation to add the new nodes as reporting nodes updates the LUN mapping so the hosts can access the LUN via those new nodes’ Fibre Channel paths, enabling proper path failover and load sharing across all available paths. Other options either map the LUN to a host or adjust path settings, but they don’t extend which cluster nodes report the LUN for existing paths.