Using VMware Cloud on AWS and AWS FSx for NetApp ONTAP single AZ

-

 Gilles Chekroun


Lead VMware Cloud on AWS Solutions Architect
---

With the release of FSx for NetApp ONTAP, Customers are looking to attach cloud storage to their VMware VMs like NFS mount or iSCSI access.
The initial release of FSx for NetApp is a multi Availability Zones implementation and is presenting an external IP address that doesn't belong to the VPC CIDR it's deployed on.
This created a challenge for SDDC VMs to access that IP over the ENI to the connected VPC.

Recently, on April 13 - 2022, AWS and NetApp have released a single AZ version of FSx-N and that is becoming interesting since all FSx IP addresses are now within the VPC CIDR and then visible by the SDDC.

Note: This setup is for guest VMs mounts only.
It is not adding a VMware datastore 

Test setup

Create an Amazon FSx for NetApp ONTAP file system

Open the AWS FSx console at https://console.aws.amazon.com/fsx/ and create a File System
Select the File System Type
Create a small FSx for NetApp using Single AZ 
Under Networking and Security select the SDDC Attached VPC, Default SG and the SDDC attached Subnet
Select a password for "fsxadmin" user for ONTAP CLI
Use the default SVM (Storage Virtual Machine) Configuration
Create a Volume Name, Path, Size for the SVM
Verify the Summary and create
It takes around 30 mins to create
Check the Endpoints and specifically the NFS IP address

SDDC Connectivity

Verify that an SDDC VM can ping the SVM NFS Endpoint
Verify access to the management Endpoint

Mounting the NFS File System

Before mounting the file system to the SDDC VM, update the VM and install NFS
  • sudo apt-get update
  • sudo apt-get install nfs-common
Create an fsx directory
  • sudo mkdir /fsx
Mount the AWS FSx for NetApp using
  • mount - t nfs 172.200.10.104:/vol1 /fsx
Check the result

Considerations

Since we are using the Cross Account ENI between the VMC environment and the Connected VPC with the FSx installed, there are NO DATA CHARGES at all in that setup between VMware and AWS



Thanks for reading.

Comments

Post a Comment

Populars

Egress VPC and AWS Transit Gateway (Part1)

-
Image
Gilles Chekroun
 Lead VMware Cloud on AWS Solutions Architect --- Usually my blog posts are customer driven and recently I have been working on a design that would include an Egress VPC and AWS Transit Gateway. This customer is going to use both VMware Managed Transit Gateway and also AWS Transit Gateway. I will split this post in 3 parts: The Egress VPC - this article Adding a VMC SDDC to the Egress VPC here Adding VMware Managed Transit Gateway here Why do we need an Egress VPC? Numerous posts on AWS site  will describe how to build an Egress VPC and the subtleties of the various route tables of the TGW and the Egress VPC itself. The main goal is to have ONE Internet gateway only  that will allow workloads to go out to internet on the Egress VPC. One of the most important point is redundancy and multi-availability zones. Applications usually reside in private subnets, while NAT Gateways reside in a public subnet. NAT Gateways To focus the Internet access to a single point, we can cre
Read more

AWS Transitive routing with Transit Gateways in the same region

-
Image
Gilles Chekroun Lead VMware Cloud on AWS Specialist --- At the AWS Re:invent 2019 conference, the long waited TGW peering functionality was announced and available in a few AWS regions. This is an INTER-REGION peering only meaning that the Transit Gateways need to be in different regions. Hoping that AWS will soon release an INTRA-REGION capability I discussed with a few AWS Solutions Architects in Las Vegas, among them Tom Adamski , about using a VPC as a bridge between two TGWs in the same region. Tom assured me that it is possible opening for the first time the transitive routing capability in AWS networking. Well . . . I needed to test that and see by myself. Test bed For a simple test, I will use 2 TGWs in the same regions with 2 VPCs attached each and another VPC as "bridge" connected to both TGWs. Yes you can connect a VPC up to 5 TGWs . The whole idea is to use this "bridging VPC" and point the default route of the TGWs to it. To do that I c
Read more

Considerations on vTGW to TGW Peering Link

-
Image
   Gilles Chekroun
 Lead VMware Cloud on AWS Solutions Architect --- Recently I was talking with a Customer on designing their VMware Cloud on AWS environment and linking it to their existing AWS infrastructure. The idea was to have 2 SDDCs, Test and Prod, and link them with a VMware Managed TGW and peer it to their existing TGW. The customer requirements were: VMs in each SDDC should have internet access from the SDDC out VMs from Test should be able to talk to VMs in Prod VMs in any SDDC should be able to access their own vCenter but also the other one Some VMs any SDDC should have a Public IP and NAT rule to be accessible from outside VMware traffic should stay within VMware SDDCs Other traffic, like on-prem, should go via the Customer TGW Test Setup Step1 - Create SDDC Group Create an SDDC Group and attach the 2 SDDCs Prod and Test Make sure the proper FireWall rules are open in each SDDC Compute GW. Step 2 - Attach the Customer TGW In the SDDC Groups, under External TGW TAB, add t
Read more