lun mapping add-reporting-nodes

Description​

This command is used before or after a data mobility event that modifies the owning node of the LUN to add the new optimized nodes to the specified LUN mapping's reporting nodes.

For more information on managing reporting nodes in response to data mobility events, please see the Data ONTAP SAN Administration Guide.

Parameters​

-vserver <Vserver Name> - Vserver Name

Specifies the name of the Vserver containing the LUN.

{ -path <path> - LUN Path

Specifies the path of the LUN. Examples of correct LUN paths are /vol/vol1/lun1 and /vol/vol1/qtree1/lun1.

| -volume <volume name> - Volume Name

Specifies the volume that contains the LUN.

[-qtree <qtree name>] - Qtree Name

Specifies the qtree that contains the LUN.

-lun <text>} - LUN Name

Specifies the LUN name.

-igroup | -g <text> - Igroup Name

Specifies the igroup the LUN is mapped to.

{ -local-nodes [true] - Add Nodes for Current LUN Location

Add the current LUN owner node and HA partner to the LUN mapping's reporting nodes.

This option should be used after a LUN mobility event to restore optimized access to the LUN.

| -destination-aggregate <aggregate name> - Add Nodes for Aggregate

Add the specified aggregate's owner node and HA partner to the LUN mapping's reporting nodes.

This option may be used prior to a LUN mobility event that changes the LUN's containing aggregate.

| -destination-volume <volume name> - Add Nodes for Volume

Add the specified volume's owner node and HA partner to the LUN mapping's reporting nodes.

This option may be used prior to a LUN mobility event that changes the LUN's containing volume.

| -all [true]} - Add All Nodes (privilege: advanced)

Set the LUN mapping to report on all nodes in preparation for a revert to a previous version of Data ONTAP.