SLM will choose 4 LIFs per node, being 8 LIF total (owner and HA partner), enabling portsets will help to limit the ports per node... that way we can stablish only 2 LIF per node.
Creating port sets and binding igroups to port sets
In addition to using Selective LUN Map (SLM), you can create a port set and bind the port set to an igroup to further limit which LIFs can be used by an initiator to access a LUN. If you do not bind a port set to an igroup, then all of the initiators in the igroup can access mapped LUNs through all of the LIFs on the node owning the LUN and the owning node's HA partner.
You can find more information on this link:
https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-sanag%2FGUID-5CC27202-A43F-429F-AB13-C70E7CD58E09.html

Moving SAN LIFs
If a node needs to be taken offline, you can move a SAN LIF to preserve its configuration information, such as its WWPN, and avoid rezoning the switch fabric. Because a SAN LIF must be taken offline before it is moved, host traffic must rely on host multipathing software to provide nondisruptive access to the LUN. You can move SAN LIFs to any node in a cluster, but you cannot move the SAN LIFs between storage virtual machines (SVMs).
Yoy can find more information on this link:
https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-sanag%2FGUID-09F5C2A3-FA66-4252-BEEF-D556A143CD30.html