Selective LUN Map (SLM) reduces the number of paths from the host to the LUN. With SLM, when a new LUN map is created, the LUN is accessible only through paths on the node owning the LUN and its HA partner.

SLM enables management of a single igroup per host and also supports non-disruptive LUN move operations that do not require portset manipulation or LUN remapping.

Portsets can be used with SLM just as in previous versions of Data ONTAP to further restrict access of certain targets to certain initiators . When using SLM with portsets, LUNs will be accessible on the set of LIFs in the portset on the node that owns the LUN and on that node’s HA partner.

Beginning with Data ONTAP 8.3 SLM is enabled by default on all new LUN maps. For LUNs created prior to Data ONTAP 8.3, you can manually apply SLM by using the lun mapping remove-reporting-nodes command to remove the LUN reporting nodes and restrict LUN access to the LUN owning node and its HA partner.

Example

An SVM has 4 nodes and 16 LIFs per node. The storage administrator creates a portset with 2 LIFs from each node, binds the portset to an igroup, and maps a LUN to the igroup. The LUN is only accessible on the node that owns the LUN and that node’s HA partner through the 4 LIFS specified in the portset.

More information

How to determine whether SLM is enabled on a LUN map If your environment has a combination of LUNs created in Data ONTAP 8.3 and LUNs transitioned into Data ONTAP 8.3 from previous versions, you might need to determine whether Selective LUN Map (SLM) is enabled on a specific LUN.

Modifying SLM reporting nodes If you are moving a LUN or a volume containing LUNs to another HA pair within the same cluster, you should modify the Selective LUN Map (SLM) reporting-nodes list, before initiating the move. This ensures that active/optimized LUN paths are maintained.

FlexPod Boot LUNs

At Red8, it is part of our operational recommendation when configuring FlexPod with 4-Node+ cDOT clusters, and SAN boot, to have boot policies where the primary and secondary paths to the boot LUN are configured to node 1 and node 3 of the cDOT cluster (assumes the boot LUN is configured on node 1). This would allow SAN boot to continue to work over the unoptimized path via the Cluster Interconnect Switch. In a cDOT 8.3 environment, where SLM is enabled by default, this would not be possible. To emulate a pre cDOT 8.3 environment and allow the paths of the boot LUNs to be visible across all nodes you need to modify the reporting nodes.