Skip to main content
NetApp Knowledgebase

How to utilize and set up portsets in clustered DATA ONTAP using CLI

Views:
171
Visibility:
Public
Votes:
0
Category:
clustered-data-ontap-8
Specialty:
san
Last Updated:

Applies to

  • Clustered Data ONTAP 8.2 
  • Clustered Data ONTAP 8.1

Description

Portsets apply a mask onto igroups to limit the total number of paths SAN clients can see. This can optimize SAN traffic, reduce congestion, and can be useful in clustered Data ONTAP where many nodes could present many available paths for SAN clients to effectively handle using ALUA.

Adding a host to an igroup allows it to see all available paths on the whole storage system. After you bind a portset to an igroup, only paths to the LIFs inside the portset will be accessible to the host. (All LIFs will still be advertised in a SendTargets response, to limit the number of LIFs advertised, consider either on how Selective LUN Mapping (SLM) works or how to limit iSCSI initiator access to target portals.

Warning: An igroup can only bind to one portset, however, a LUN can be mapped to multiple igroups. Ensure all igroups that allow the IQN (iSCSI) or WWPN (FC) of the client has the appropriate portset bound.

CRITICAL: Portsets must include the indirect partner paths, ALUA must be enabled on the SAN client, and the supported version of NetApp MPIO/ SAN utilities must be installed for successful failover to occur.

The following scenario helps define a portset and its purpose:

  • During initial setup, the iSCSI IQN of ESXi host 'SANclient' is added to Igroup1 on Cluster1 and a LUN is mapped to Igroup1
    (The following chart illustrates hierarchy and relationship of objects)
    Cluster1
        Igroup1
            SANclient_IQN
        SFO Aggregates
            VSM
                iSCSI_LIF (port bound)
                Volume
                    LUN (mapped to Igroup1)
        Node1
            CFO Aggregates
            Ports

     
  • A rescan is triggered on SANclient and it can see 16 paths to the LUN:
    node1_iscsi_lif1 via SANclient port 1
    node1_iscsi_lif1 via SANclient port 2
    node1_iscsi_lif2 via SANclient port 1
    node1_iscsi_lif2 via SANclient port 2
    node2_iscsi_lif1 via SANclient port 1
    node2_iscsi_lif1 via SANclient port 2
    node2_iscsi_lif2 via SANclient port 1
    node2_iscsi_lif2 via SANclient port 2
    node3_iscsi_lif1 via SANclient port 1
    node3_iscsi_lif1 via SANclient port 2
    node3_iscsi_lif2 via SANclient port 1
    node3_iscsi_lif2 via SANclient port 2
    node4_iscsi_lif1 via SANclient port 1
    node4_iscsi_lif1 via SANclient port 2
    node4_iscsi_lif2 via SANclient port 1
    node4_iscsi_lif2 via SANclient port 2


    SANclient can see paths to the LUN using iSCSI LIFs on node1 and node2, but also using LIFs on node3 and node4. The volume containing the LUN is going to failover to node2; and in the situation that both node1 and node 2 are down, the LUN will be inaccessible as there is no path to the disk shelves.

    A demonstration is proposed for portset creation - disabling the connections from node3 and node4.
    Note: You might require these connections from node3 and node4 in some special situations to access your data.

    There are no plans to move the volumes containing the LUN from node1 to node3 or node4; however, the iSCSI LIFs on node3 and node4 must be available to serve data to LUNs on node3 and node4 to other SAN clients in different igroups.
     
  • Portset1 is created to include only the appropriate LIFs and is bound to Igroup1
    (The following chart illustrates hierarchy and relationship of objects)
    Cluster1
        Portset1
            node1_iscsi_lif1
            node1_iscsi_lif2
            node2_iscsi_lif1
            node2_iscsi_lif2
        Igroup1 (portset1 bound)
            SANclient_IQN

     
  • SANclient can now see eight paths after the rescan is complete:
    node1_iscsi_lif1 via SANclient port 1
    node1_iscsi_lif1 via SANclient port 2
    node1_iscsi_lif2 via SANclient port 1
    node1_iscsi_lif2 via SANclient port 2
    node2_iscsi_lif1 via SANclient port 1
    node2_iscsi_lif1 via SANclient port 2
    node2_iscsi_lif2 via SANclient port 1
    node2_iscsi_lif2 via SANclient port 2

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support