For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/en/guides/storage-and-backup/file-storage/enterprise-file-storage/netapp-network-config.md.
Skip to content
Appearance
Console(the OVHcloud Console, opens in a new tab)

Enterprise File Storage - Private network configuration

View as Markdown

Find out how to set up a private network for your Enterprise File Storage service from the OVHcloud Console

Objective

Enterprise File Storage services can be managed via OVHcloud API or from the OVHcloud Console.

This guide explains how to connect your Enterprise File Storage service to a vRack private network using vRack Services and Service Endpoint technology.

Info

For more information on vRack Services, please refer to this page.

Requirements

Overview

global schema

Enterprise File Storage is a service that is exposed to the vRack via an IP address. There are three steps to assigning an IP address to your service:

  1. Selecting or creating a vRack
  2. Selecting or activating a vRack Services
  3. Selecting or creating of a subnet

OVHcloud Console Access

  • Direct link:
  • Navigation path: Bare Metal Cloud > Storage > Enterprise File Storage

Instructions

Click the name of your service in the list.

By default, the service is not connected to a private network: in the Network configuration tile of the Overview tab, its Status is Require user configuration. This step is required before you can create your volumes and/or set your ACLs.

Click Configure network in this tile to configure your Service Endpoint to enable your volumes to be consumed from your private network. The Configure the network page opens.

Step 1 - Selecting or creating a vRack

You must have a vRack to activate your vRack services. OVHcloud vRack is a free service. Select your vRack in the vRack field. If you don't have one at this stage, you can order one using the Order a vRack link under this field.

Info

Please note that creating vRack Services, Subnets, or Service Endpoints on a production vRack does not cause any service interruption. Therefore, you can safely follow steps 2 and 3 of this guide in a production environment.

Step 2 - Selecting or activating a vRack Services

Select a vRack Services in the vRack Services field. Only the vRack Services eligible for your service are listed. If you don't already have a vRack Services activated, click the Activate vRack Services link to be redirected to the vRack Services pages. For more information on vRack Services configuration, please refer to this page.

Once your new vRack Services is activated, go back to the Configure the network page of your service to perform the rest of the configuration.

Step 3 - Selecting or creating a subnet

Select the subnet on which you want to expose your Enterprise File Storage service in the Subnet field. If your subnet does not yet exist, it is necessary to create it: click the Create a subnet link, or go to the Subnets tab of your vRack Services. For more information on how to create a subnet, refer to this page.

Once you've completed these 3 steps, click the Configure network button. You will be redirected to the Overview tab of your Enterprise File Storage service, where you can follow the deployment of your Service Endpoint in the Network configuration tile.

After a few moments, the Status changes from Deploying… to Deployed: your new Service Endpoint is configured and available. The tile shows its vRack, vRack Services, Subnet, Service range and Endpoint IP.

You can now follow the guides below to create and manage your volumes, snapshots and ACLs.

Testing network connectivity from an NFS client to your Service Endpoint

Info

Prerequisites:

  • Your NFS client must have a network interface configured in the same subnet as your vRack Services and must be in the same VLAN as well. The vRack Services subnet is not routable and requires a CIDR 24 subnet (x.x.x.x/24 or x.x.x.x/255.255.255.0).
  • If this is not possible, you can use a gateway that will translate the address and port to it but you will have to contact OVHcloud support, otherwise you will not be able to mount your NFS shares.
  • The IP address of your Service Endpoint is in a subset of CIDR 27, 28 or 29 of your vRack Services subnet.
  • The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one.
  • Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24.
  • The arping IP_Endpoint command must return only one MAC address.
  • The traceroute -T IP_Endpoint -p 2049 command must not return an error.
  • The nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint command must return ports in the OPEN state (essential for the proper functioning of NFSv3).

Go further

Managing Enterprise File Storage from the OVHcloud Console

Enterprise File Storage - API Quickstart

Enterprise File Storage - Managing volumes

Enterprise File Storage - Managing volume ACLs

Enterprise File Storage - Managing volume snapshots

For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analysed by our experts.

Join our community of users.

Was this page helpful?