Skip to main content
Amazon FSx for NetApp ONTAP

Create an FSx for ONTAP file system in BlueXP workload factory

Contributors netapp-rlithman
PDFs

Using BlueXP workload factory you can create first and second-generation FSx for ONTAP file systems to add and manage volumes and additional data services.

About this task

A storage VM and a security group are created as part of file system creation.

Before you begin

Before creating your FSx for ONTAP file system, you will need:

  • The ARN of an IAM role that gives workload factory the permissions needed to create an FSx for ONTAP file system. Learn how to grant permissions to an AWS account.

  • The region and VPC information for where you will create the FSx for ONTAP instance.

Create an FSx for ONTAP file system

You can create an FSx for ONTAP file system using Quick create or Advanced create. You can also use the following tools available in the Codebox: REST API, CloudFormation, and Terraform. Learn how to use Codebox for automation.

Note When using Terraform from Codebox, the code you copy or download hides fsxadmin and vsadmin passwords. You'll need to re-enter the passwords when you run the code.
Quick create

Quick create enables you to use a recommended best-practice configuration. You can change most settings after you create an FSx for ONTAP file system.

Second-generation FSx for ONTAP file systems are the default deployment type for quick create unless the selected region doesn't support second-generation FSx for ONTAP file systems.

Steps

  1. Log in using one of the console experiences.

  2. In Storage, select Create FSx for ONTAP.

  3. On the Create FSx for ONTAP page, select Quick create.

    You can also load a saved configuration.

  4. Under File system general configuration, provide the following:

    1. AWS credentials: Select to add AWS credentials in workload factory or continue without credentials.

    2. File system name: Enter a name for the file system.

    3. Region & VPC: Select the region and VPC for the file system.

    4. Deployment type: Select a deployment type.

      • Single Availability Zone (Single-AZ) deployment: provides availability by monitoring for hardware failures and automatically replacing infrastructure components in the event of a failure. Achieves high durability by automatically replicating your data within an Availability Zone to protect it from component failure.

        This configuration is recommended for high performance workloads or when workloads start small and incrementally scale out to 72 GB/s of throughput and 2.4 million IOPS.

      • Multiple Availability Zones (Multi-AZ) deployment: provides continuous availability to data even when an Availability Zone is unavailable. A Multi-AZ file system is designed for business-critical production workloads that require high availability to shared ONTAP file data and need storage with built-in replication across Availability Zones.

        This single HA-pair configuration is recommended for workloads that require up to 6 GB/s of throughput or 200,000 IOPS.

    5. Tags: Optionally, you can add up to 50 tags.

  5. Under File system details, provide the following:

    1. SSD storage capacity: Enter the storage capacity and select the storage capacity unit.

      • For first-generation deployments, you can't decrease capacity after file system creation.

      • For second-generation deployments, you can increase capacity after file system creation.

    2. ONTAP credentials: Optional. Enter your ONTAP user name and password. The password can be set now or later.

      If the user you provide is not the fsxadmin user, and later you need to reset the fsxadmin password, you'll be able to do this from the AWS console.

    3. SMB/CIFS setup: Optional. If you plan to use SMB/CIFS protocol to access volumes, you must configure the Active Directory for the storage VM during file system creation. Provide the following details for the storage VM that is created for this file system.

      1. Active Directory domain to join: Enter the fully qualified domain name (FQDN) for the Active Directory.

      2. DNS IP addresses: Enter up to three DNS IP addresses separated by commas.

      3. SMB server NetBIOS name: Enter the SMB server NetBIOS name of the Active Directory computer object to create for your storage VM. This is the name of this storage VM in the Active Directory.

      4. User name: Enter the user name of the service account in your existing Active Directory.

        Do not include a domain prefix or suffix. For EXAMPLE\ADMIN, use ADMIN.

      5. Password: Enter the password for the service account.

      6. Organization unit: Optionally, enter the name of the Organizational Unit where you intend to create the computer account for FSx for ONTAP. The OU is the distinguished path name of the organizational unit to which you want to join the file system.

      7. Delegated administrators group: Optionally, enter the name of the group in your Active Directory that can administer your file system.

        If you are using AWS Managed Microsoft AD, you must specify a group such as AWS Delegated FSx Administrators, AWS Delegated Administrators, or a custom group with delegated permissions to the OU.

        If you are joining to a self-managed AD, use the name of the group in your AD. The default group is Domain Admins.

  6. Open the Summary to review the configuration that you defined. If needed, you can change any setting at this time before saving or creating the file system.

  7. Save or create the file system.

If you created the file system, you can now view the FSx for ONTAP file system in the Inventory page.

Advanced create

With Advanced create, you set all of the configuration options, including availability, security, backups, and maintenance.

Steps

  1. Log in using one of the console experiences.

  2. In Storage, select Create FSx for ONTAP.

  3. On the Create FSx for ONTAP page, select Advanced create.

    You can also load a saved configuration.

  4. Under File system general configuration, provide the following:

    1. AWS credentials: Select to add AWS credentials in workload factory or continue without credentials.

    2. File system name: Enter a name for the file system.

    3. Region & VPC: Select the region and VPC for the file system.

    4. Deployment type: Select a deployment type and file system generation. The availability of a second-generation file system depends on the selected region. If the selected region doesn't support second-generation FSx for ONTAP file systems, the deployment type switches to first-generation.

      • Single Availability Zone (Single-AZ) deployment: provides availability by monitoring for hardware failures and automatically replacing infrastructure components in the event of a failure. Achieves high durability by automatically replicating your data within an Availability Zone to protect it from component failure.

        File system generation: Select one of the following:

        • Second-generation: This configuration is recommended for high performance workloads or when workloads start small and incrementally scale out to 72 GB/s of throughput and 2.4 million IOPS.

        • First-generation: This configuration is ideal for workloads that require up to 4 GB/s or 160,000 IOPS. First-generation file systems can only increase capacity.

      • Multiple Availability Zones (Multi-AZ) deployment: provides continuous availability to data even when an Availability Zone is unavailable. A Multi-AZ file system is designed for business-critical production workloads that require high availability to shared ONTAP file data and need storage with built-in replication across Availability Zones.

        File system generation: Select one of the following:

        • Second-generation: This single HA-pair configuration is recommended for workloads that require up to 6 GB/s of throughput or 200,000 IOPS. In a Multi-AZ and second-generation file system, capacity can increase or decrease to match workload demands.

        • First-generation: This configuration is ideal for workloads that require up to 4 GB/s or 160,000 IOPS. First-generation file systems can only increase capacity.

    5. Tags: Optionally, you can add up to 50 tags.

  5. Under File system details, provide the following:

    1. SSD storage capacity: Enter the storage capacity and select the storage capacity unit.

      • For first-generation deployments, you can't decrease capacity after file system creation.

      • For second-generation deployments, you can adjust capacity.

    2. Throughput capacity per HA pair: Select throughput capacity per number of HA pairs. First-generation file systems support only one HA pair.

    3. Provisioned IOPS: Select one of the following options:

      • Automatic: For automatic, for every GiB created, 3 IOPS are added.

      • User-provisioned: For user-provisioned, enter the IOPS value.

    4. ONTAP credentials: Optional. Enter your ONTAP user name and password. The password can be set now or later.

      If the user you provide is not the fsxadmin user, and later you need to reset the fsxadmin password, you'll be able to do this from the AWS console.

    5. Storage VM Credentials: Optional. Enter your user name. Password can be specific to this file system or you can use the same password entered for ONTAP credentials. The password can be set now or later.

    6. SMB/CIFS setup: Optional. If you plan to use SMB/CIFS protocol to access volumes, you must configure the Active Directory for the storage VM during file system creation. Provide the following details for the storage VM that is created for this file system.

      1. Active Directory domain to join: Enter the fully qualified domain name (FQDN) for the Active Directory.

      2. DNS IP addresses: Enter up to three DNS IP addresses separated by commas.

      3. SMB server NetBIOS name: Enter the SMB server NetBIOS name of the Active Directory computer object to create for your storage VM. This is the name of this storage VM in the Active Directory.

      4. User name: Enter the user name of the service account in your existing Active Directory.

        Do not include a domain prefix or suffix. For EXAMPLE\ADMIN, use ADMIN.

      5. Password: Enter the password for the service account.

      6. Organization unit: Optionally, enter the name of the Organizational Unit where you intend to create the computer account for FSx for ONTAP. The OU is the distinguished path name of the organizational unit to which you want to join the file system.

      7. Delegated administrators group: Optionally, enter the name of the group in your Active Directory that can administer your file system.

        If you are using AWS Managed Microsoft AD, you must specify a group such as AWS Delegated FSx Administrators, AWS Delegated Administrators, or a custom group with delegated permissions to the OU.

        If you are joining to a self-managed AD, use the name of the group in your AD. The default group is Domain Admins.

  6. Under Network & security, provide the following:

    1. Security group: Create or use an existing security group.

      For a new security group, refer to security group details for a description of the security group protocols, ports, and roles.

    2. Availability Zones: Select availability zones and subnets.

      • For Cluster configuration node 1: Select an availability zone and subnet.

      • For Cluster configuration node 2: Select an availability zone and subnet.

    3. VPC route tables: Select the VPC route table to enable client access to volumes.

    4. Endpoint IP address range: Select Floating IP address range outside your VPC or Enter an IP address range and enter an IP address range.

    5. Encryption: Select the encryption key name from the dropdown.

  7. Under Backup and maintenance, provide the following:

    1. FSx for ONTAP Backup: Daily automatic backups are enabled by default. Disable if desired.

      1. Automatic backup retention period: Enter the number of days to retain automatic backups.

      2. Daily automatic backup window: Select either No preference (a daily backup start time is selected for you) or Select start time for daily backups and specify a start time.

    2. Weekly maintenance window: Select either No preference (a weekly maintenance window start time is selected for you) or Select start time for 30-minute weekly maintenance window and specify a start time.

  8. Save or create the file system.

If you created the file system, you can now view the FSx for ONTAP file system in the Inventory page.

Security group details

The following table provides security group details including protocols, ports, and roles.

Protocol Port Role

SSH

22

SSH access to the IP address of the cluster management LIF or a node management LIF

TCP

80

Web page access to the IP address of the cluster management LIF

TCP/UDP

111

Remote procedure call for NFS

TCP/UDP

135

Remote procedure call for CIFS

UDP

137

NetBIOS name resolution for CIFS

TCP/UDP

139

NetBIOS service session for CIFS

TCP

443

ONTAP REST API access to the IP address of the cluster management LIF or an SVM management LIF

TCP

445

Microsoft SMB/CIFS over TCP with NetBIOS framing

TCP/UDP

635

NFS mount

TCP

749

Kerberos

TCP/UDP

2049

NFS server daemon

TCP

3260

iSCSI access through the iSCSI data LIF

TCP/UDP

4045

NFS lock daemon

TCP/UDP

4046

Network status monitor for NFS

UDP

4049

NFS quota protocol

TCP

10000

Network data management protocol (NDMP) and NetApp SnapMirror intercluster communication

TCP

11104

Management of NetApp SnapMirror intercluster communication

TCP

11105

SnapMirror data transfer using intercluster LIFs

TCP/UDP

161-162

Simple network management protocol (SNMP)

All ICMP

All

Pinging the instance
What's next

With a file system in your Storage inventory, you can create volumes, manage your FSx for ONTAP file system, and set up data protection for your resources.