IN THIS ARTICLE
Outlines how to configure VNet peering for a Qumulo on Azure file system
- Active Qumulo subscription on Azure
- The Resource ID of the VNet you want to peer your Qumulo on Azure file system with
NOTE: You can find the VNet resource ID by clicking Properties on the VNet’s page in the Azure portal.
The table below lists the required permissions for configuring VNet Peering with a Qumulo on Azure file system.
Your Qumulo on Azure file system relies on a process called Virtual Network Peering to allow seamless communication between your network and the file system. The virtual networks appear as one for connectivity purposes. Note that all network traffic between peered virtual networks remains private. No public Internet, gateways, or encryption is required in the communication between the virtual networks.
After you have launched your Qumulo on Azure file system, the email or user account that you provided to Qumulo will receive an email with a link allowing the account to join the Qumulo Tenant. Once that has been completed, that user account will be granted permission to perform VNet Peering on the VNet created for the file system. VNet Peering must be configured on both your own local VNet as well as the VNet of the Qumulo on Azure file system. A Qumulo technician takes care of the latter step; follow the steps in this document to configure the same on your local end. VNet Peering can be accomplished through the Azure Portal or via API calls, using a single User account or multiple Service Principals.
Configure VNet Peering
- Navigate to your virtual networks list and click the VNet to be peered.
NOTE: Typically, the VNet will be named <FILESYSTEM_NAME>_vnet.
- Click Peerings from the navigation bar on the left.
- Click Add at the top of the page to add a new peering.
- Proceed by following the instructions provided in Create, change, or delete a virtual network peering. When prompted, select “I know my resource ID”, and specify the VNet ID of the VNet you wish to peer with.
Once that succeeds, you’ll need to repeat steps 1-4 using your own VNet, providing the resource ID for the Qumulo VNet.
You should now be able to successfully configure VNet peering for your Qumulo on Azure file system
Like what you see? Share this article with your network!