How to Setup Amazon FSx for NetApp ONTAP

This document describes how to set up LifeKeeper to use Amazon FSx for NetApp ONTAP.

LifeKeeper accesses it via the iSCSI protocol and uses it as a shared disk.
Amazon FSx for NetApp ONTAP can be accessed via the iSCSI protocol or NFS as a shared disk from LifeKeeper. By configuring a multi-AZ, it ensures availability even if one of the Availability Zones (AZ) goes down.
Multipath should be configured for endpoints created for each AZ, and LifeKeeper uses it as a volume resource.

Installing LifeKeeper

To prevent split-brain, configure Quorum/Witness. Considering the AZ where the cluster nodes and ONTAP are located, configure it in a different location as described in LifeKeeper Quorum

Creating an FSx for NetApp ONTAP file system

1. Select Amazon FSx for NetApp ONTAP from the AWS FSx menu and create a file system.
2. Select a Standard create option. Supplementary information is provided below:
   • For Deployment type choose Multi-AZ. Note: Single AZ configuration is not supported.
   • The Preferred subnet and the Standby subnet are assigned to the subnets allocated to each AZ. An iSCSI endpoint is created here.
   • Other fields are optional.

Configuring iSCSI for ONTAP

https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/mount-iscsi-windows.html
Follow the steps outlined above to configure iSCSI for ONTAP. The explanation here assumes the following values:

Filesystem
 Management endpoint DNS name
  management.fs-aaaa.fsx.us-west-2.amazonaws.com
 Management endpoint IP address
  10.1.255.204
SVM
 Management DNS name
  svm-aaaa.fsx.us-west-2.amazonaws.com
 iSCSI DNS name
  iscsi.svm-aaaa.fsx.us-west-2.amazonaws.com
 Management IP address
  10.1.255.232
 iSCSI IP address
  10.1.1.175, 10.1.2.141

Start the MSiSCSI service on each cluster node

At this time, check the initiator name.

PS C:> Start-Service MSiSCSI
PS C:> Set-Service -Name msiscsi -StartupType Automatic
PS C:> (Get-InitiatorPort).NodeAddress
iqn.1991-05.com.microsoft:awsnode1.<domain>

Log in to the ONTAP File System management server

Execute lun create and lun igroup create, specifying the initiator name of each cluster node with the -initiator option.

# ssh fsxadmin@management.fs-aaaa.fsx.us-west-2.amazonaws.com
::> lun create -vserver fsx -path /vol/vol1_l/lun_001 -size 1G -ostype windows -space-allocation enabled
::> lun show
Vserver   Path                            State   Mapped   Type        Size
--------- ------------------------------- ------- -------- -------- --------
fsx       /vol/vol1_l/lun_001             online  unmapped windows        1GB
::> lun igroup create -vserver fsx -igroup igroup_001_l -initiator iqn.1991-05.com.microsoft:awsnode1.<domain>,iqn.1991-05.com.microsoft:awsnode2.<domain> -protocol iscsi -ostype windows
::> lun igroup show
Vserver   Igroup       Protocol OS Type  Initiators
--------- ------------ -------- -------- ------------------------------------
fsx       igroup_001_l   iscsi   windows iqn.1991-05.com.microsoft:awsnode1.<domain>
                                         iqn.1991-05.com.microsoft:awsnode2.<domain>

With lun mapping, ensure that igroup_001_1 has access to lun 001.

::> lun mapping create -vserver fsx -path /vol/vol1_l/lun_001 -igroup igroup_001_l -lun-id 001
::> lun show -path /vol/vol1_l/lun_001
Vserver   Path                            State   Mapped   Type        Size
--------- ------------------------------- ------- -------- -------- --------
fsx       /vol/vol1_l/lun_001             online  mapped   windows        1GB
::> network interface show -vserver fsx
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
fsx
            iscsi_1      up/up    10.1.1.175/24      FsxId0212ef1b4803190af-01 
                                                                   e0e     true
            iscsi_2      up/up    10.1.2.141/24      FsxId0212ef1b4803190af-02
                                                                   e0e     true
            nfs_smb_management_1 
                         up/up    10.0.255.232/26    FsxId0212ef1b4803190af-01 
                                                                   e0e     true
2 entries were displayed.
::> exit

Configure iSCSI on each cluster node

Copy the series of commands shown below to create and run the .ps1 script. In this example, replace “iscsi_1” with “10.1.1.175” and “iscsi_2” with “10.1.2.141”. Also, replace “ec2_ip” with the IP address of each cluster node.

#iSCSI IP addresses for Preferred and Standby subnets 
$TargetPortalAddresses = @("iscsi_1","iscsi_2") 

#iSCSI Initator IP Address (Local node IP address) 
$LocaliSCSIAddress = "ec2_ip" 

#Connect to FSx for NetApp ONTAP file system 
Foreach ($TargetPortalAddress in $TargetPortalAddresses) { 
New-IscsiTargetPortal -TargetPortalAddress $TargetPortalAddress -TargetPortalPortNumber 3260 -InitiatorPortalAddress $LocaliSCSIAddress 
} 

#Add MPIO support for iSCSI 
New-MSDSMSupportedHW -VendorId MSFT2005 -ProductId iSCSIBusType_0x9

#Set the MPIO path configuration for new servers to ensure that MPIO is properly configured and visible in the disk properities.
Set-MPIOSetting -NewPathVerificationState Enabled

#Establish iSCSI connection 
1..8 | %{Foreach($TargetPortalAddress in $TargetPortalAddresses)
{Get-IscsiTarget | Connect-IscsiTarget -IsMultipathEnabled $true -TargetPortalAddress $TargetPortalAddress -InitiatorPortalAddress $LocaliSCSIAddress -IsPersistent $true}}

#Set the MPIO Policy to Round Robin 
Set-MSDSMGlobalDefaultLoadBalancePolicy -Policy RR 

Start the Windows disk management application on both nodes, allocate volumes, and create volume resources in LifeKeeper.