For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/de/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/de/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/de/guides/storage-and-backup/file-storage/ha-nas/nas-pci-connection-via-vrack.md.
Zum Inhalt springen

HA-NAS - Connect a Public Cloud instance to a HA-NAS volume via vRack (Beta)

Als Markdown ansehen

Find out how to mount a HA-NAS volume on a Public Cloud instance through a vRack private network, with no exposure of your data traffic to the Internet

Info

This feature is currently in beta phase. This guide can be updated in the future with the advances of our teams in charge of this product.

Objective

Mount a HA-NAS volume from a Public Cloud instance using a private vRack network.

This ensures that all data traffic remains on the private network, with no Internet exposure.

Info

The HA-NAS volume and the Public Cloud instance must be located in the same region (e.g. RBX, GRA, or SBG), as OpenStack private networks are regional.

Requirements

Overview

The diagram below illustrates how a HA-NAS volume connects to a Public Cloud instance through a private vRack network.

Diagram of a HA-NAS volume connected to Public Cloud instances through vRack Services
  1. Critical Match — VLAN ID

    The VLAN ID (e.g. 1900) must be identical in both the Public Cloud private network and the vRack Services configuration.

  2. Critical Match — Subnet CIDR

    The subnet CIDR (e.g. 10.235.0.0/24) must also match across both services to ensure they operate within the same logical network in the vRack.

  3. Info — Service address range

    The service address range (e.g. 10.235.0.240/28) is a reserved subset of the main subnet. These IPs are exclusively used by HA-NAS service endpoints (e.g. 10.235.0.241) and must not be assigned to instances.

  4. Security — ACL Rule

    The HA-NAS volume's Access Control List (ACL) must explicitly authorise the private IP of any instance requiring access (e.g. 10.235.0.15).

  5. Concept — vRack Services

    vRack Services acts as a secure network bridge, allowing managed services such as HA-NAS outside your Public Cloud project to connect seamlessly to your private vRack network.


OVHcloud Console Access

  • Direct link:
  • Navigation path: Bare Metal Cloud > Storage > NAS-HA > Private NAS-HA > Select your NAS-HA

Instructions

Step 1 - Associating the Public Cloud project with the vRack

Before deploying your HA-NAS volume through a private vRack network, first associate your Public Cloud project with a vRack.

This association enables private networking between your Public Cloud instances and OVHcloud managed services such as HA-NAS.

Follow step 1: activating and managing a vRack in our guide "Configuring vRack for Public Cloud".

Step 2 - Creating a private network in your Public Cloud project

To connect your Public Cloud instance to a HA-NAS volume via vRack, first provision a dedicated private network within your project.

This isolated network enables secure communication between your instances and OVHcloud storage resources through the vRack architecture.

Follow step 2: creating a private network in the vRack in our guide "Configuring vRack for Public Cloud".

Step 3 — Launching the instance on the private network

Deploy your Public Cloud instance within the private network you created. Ensure it is connected to the correct subnet to enable secure communication over the vRack.

Follow step 3: integrating an instance into vRack in our guide "Configuring vRack for Public Cloud".

Ensure that an IP address is assigned to the instance in the selected subnet (e.g. 10.235.0.15).

Step 4 - Creating a vRack Service resource for HA-NAS

There are two ways to create a vRack Service resource for your HA-NAS volume.

Both methods achieve the same goal: securely connecting your HA-NAS service to your vRack and Public Cloud instances.

First method: creating via vRack Services

A vRack Service resource acts as a network adapter, connecting managed services like HA-NAS to your vRack and its private subnet.

For detailed guidance, see OVHcloud's official documentation: vRack Services - Exposing a Managed Service on your vRack.

  1. In the OVHcloud Console, open Bare Metal Cloud, then click vRack Services under Network in the left-hand menu.

  2. Click Order a vRack Service.

  3. Select the same Region as your vRack, Public Cloud instance and HA-NAS service. Then click Order a vRack Service.

  4. Click No thanks, I already have a vRack, tick the box to accept the terms and conditions, then click Confirm.

  5. Locate your newly created vRack Services in the list and click its name.

  6. Configure the vRack Services as follows:

    • vRack: in the General information tile of the Overview tab, click Attach a vRack, select the same vRack used for your Public Cloud project, then click Attach.

    • Create a subnet: in the Subnets tab, click Add a subnet and fill in the form.

      Info

      Ensure the CIDR matches your Public Cloud private network.

      • CIDR: e.g. 10.235.0.0/24.
      • Service range: e.g. 10.235.0.240/28.
        • Reserved subset of the private subnet for assigning IPs to managed HA-NAS services within the vRack.
      • VLAN: select Use a VLAN and enter the same VLAN number as your Public Cloud private network (see Step 2).
      • Click Add a subnet.
    • Create a Service Endpoint: in the Endpoints tab, click Create an endpoint. Select NAS-HA as the Service type, select your HA-NAS service in Managed service and your Subnet, then click Create an endpoint.

Second method: creating via the NAS-HA section
  1. Click the name of your HA-NAS service in the list.

  2. In the Network configuration tile of the Overview tab, click Configure network.

  3. Select your vRack in the vRack field.

  4. If no vRack Services have been created yet, click Activate vRack Services and follow the first method: creating via vRack Services from step 3.

  5. If you have already created a vRack Services, select it in the vRack Services field, select your Subnet, then click Configure network.

Step 5 — Connecting the HA-NAS volume to the vRack

Once the previous steps are completed successfully, all volumes created in your HA-NAS service automatically reside within your vRack and its dedicated subnet, making them immediately accessible to your Public Cloud instances.

Step 6 — Configuring access control (ACLs)

In the ACL tab of your HA-NAS volume, click Add a rule:

  • In IP address, add the IP or CIDR range authorised to mount the volume:

    • To allow a single instance, enter the instance's IP address, for example: 10.235.0.15.
    • To allow all instances within the subnet, enter the subnet address, for example: 10.235.0.0/24.
  • Set the desired Access level: Read/Write or Read only, then click Add a rule.

Info

Recommendation: Use individual IPs whenever possible to enhance security.

After applying the ACLs, verify network connectivity from your Public Cloud instance:

ping <YOUR-HA-NAS-SERVICE-IP>

Step 7 — Mounting the volume

You can mount your HA-NAS volume via NFS or via CIFS. You will need the following values:

ArgumentDescription
<YOUR-HA-NAS-SERVICE-IP>The IP address of your Service Endpoint, displayed in the Network configuration tile of your HA-NAS service (e.g. 10.235.0.241)
<NFS_PATH>The path to the volume, consisting of the service name and the partition name (e.g. zpool-123456/partition01)
<CIFS_PATH>The path to the volume, consisting of the service name and the partition name separated by _ (e.g. zpool-123456_partition01)
Warning

The NFS user is root and the SMB/CIFS user is nobody. Changing permissions with one of these users may generate conflicts with the permissions set by the other protocol.

Mounting via NFS

  1. Install the NFS client on your Public Cloud instance:

    sudo apt install -y nfs-common
  2. Mount the HA-NAS volume:

    sudo mkdir -p /mnt/ha-nas
    sudo mount -t nfs <YOUR-HA-NAS-SERVICE-IP>:/<NFS_PATH> /mnt/ha-nas
    df -h /mnt/ha-nas

    Example:

    sudo mount -t nfs 10.235.0.241:/zpool-123456/partition01 /mnt/ha-nas

HA-NAS supports NFSv3 and NFSv4. If no version is specified, your NFS client uses the latest version it supports. To force a version, add the -o vers=3 (or vers=4, vers=4.1, vers=4.2) option. For more information, and for the instructions for other operating systems, see our guide "Mounting HA-NAS via NFS share".

Mounting via CIFS

From a Linux instance

  1. Install the CIFS utilities on your Public Cloud instance:

    sudo apt install -y cifs-utils
  2. Mount the HA-NAS volume:

    sudo mkdir -p /mnt/ha-nas
    sudo mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //<YOUR-HA-NAS-SERVICE-IP>/<CIFS_PATH> /mnt/ha-nas

From a Windows instance

Open Windows PowerShell and run the following command:

net use z: \\<YOUR-HA-NAS-SERVICE-IP>\<CIFS_PATH>

Example:

net use z: \\10.235.0.241\zpool-123456_partition01

For more information, including how to resolve the Windows errors System error 1272 and System error 3227320323, see our guide "Mount your HA-NAS via a CIFS share".

Step 8 — Enabling automatic NFS mount on boot (optional)

To mount your HA-NAS volume automatically at startup via NFS, add the following entry to the /etc/fstab file:

<YOUR-HA-NAS-SERVICE-IP>:/<NFS_PATH> /mnt/ha-nas nfs rw 0 0

Then test the configuration:

sudo umount /mnt/ha-nas
sudo mount -a

If no errors occur, the HA-NAS volume will now automatically mount on boot.

Expected Result

  • The instance can access the HA-NAS volume via <YOUR-HA-NAS-SERVICE-IP>.
  • All communication occurs privately within the vRack.
  • The NFS or CIFS mount is fully functional, and the NFS mount is persistent across reboots.

Troubleshooting

SymptomLikely CauseResolution
mount.nfs: No route to hostInstance and HA-NAS not in the same region, or wrong VLAN ID.Ensure the instance, HA-NAS, and vRack Services are in the same region. Recreate the vRack Service using the same VLAN ID as the private network.
mount.nfs: access denied by serverHA-NAS ACL missing or incorrect.Add the instance IP (e.g. 10.235.0.x) or subnet (e.g. 10.235.0.0/24) with Read/Write access.
mount command hangs indefinitelyWrong NFS version or unresponsive endpoint.Use: -o vers=3,timeo=600,retrans=2 to force NFSv3 and define timeouts.
mount succeeds but no read/writeACLs or POSIX permissions too strict.Adjust ACLs or update volume-level permissions.
mount works, but not after rebootMissing /etc/fstab entry.Add: <YOUR-HA-NAS-SERVICE-IP>:/<NFS_PATH> /mnt/ha-nas nfs rw 0 0.
vRack Services shows "Inactive"Service not yet provisioned.Wait for provisioning to complete, or reconfigure it from the Network configuration tile of your HA-NAS service.

Go further

Getting started with a HA-NAS solution

HA-NAS - API Quickstart

HA-NAS - Private network configuration (Beta)

Mounting HA-NAS via NFS share

Mount your HA-NAS via a CIFS share

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.

War diese Seite hilfreich?