## Prepare the network for Bare Metal
To mount the file share on a bare-metal server, the network must support bare-metal, and these servers require a dedicated VLAN.
If needed, create a new network and enable the **Bare Metal Network** toggle during configuration.
2. In the **Basic settings** panel, enter *File Share name*, specify *Size*, and select **Standard** as the *File Share type*.
3. In the **Network settings** panel, select the private *Network* and *Subnetwork* to use for the file share.
4. In the **Access** panel, click **Add rule** and specify the IP addresses of the resources that should have access to the file share, and their access modes.
5. Set **Additional options**, if required.
### Step 2. Set up NFS client support
Connect to the server via the [Gcore Customer Portal](/cloud/virtual-instances/connect/connect-to-your-instance-via-control-panel) or SSH and set up NFS client support.
For Ubuntu and Debian:
```bash theme={null}
sudo apt -y install nfs-common
```
For CentOS:
```bash theme={null}
sudo yum install nfs-utils
```
### Step 3. Mount the file share
1. Use an existing directory for mounting the share, or create a new one, for example:
```bash theme={null}
sudo mkdir -p /mount/path
```
2. Copy the mount command from the file share **Overview** tab.
Mount the file share:
```bash theme={null}
mount 0.0.0.0:/shares/share-d54589b8-132f-4de4-ae99-af5c6cdfdb9c /mount/path
```
Replace `/mount/path` with the absolute local directory path where the file share should be mounted.
## VAST file shares
When VAST share type is selected, controls in **Network settings** and **Access** panels are disabled, and the network is assigned automatically.
The access rules cannot be configured manually - the VAST share is always available in read/write mode within its assigned network only. This network is not visible in the general **Network** tab. It is only available when attaching interfaces to a resource (VM, Bare Metal, or GPU cluster).
VAST file shares always use read/write access; access rules are not supported.
### Step 2. Add VAST network interface to a compute resource
Once the VAST file share is created, it is best to add the VAST network interface while provisioning the corresponding GPU cluster or compute resource.
**Adding VAST interface while creating a compute resource**
While provisioning a compute resource:
1. Scroll down to the **Network settings** panel.
2. Click **Add interface**.
3. Click the interface to configure, and select the **VAST network**.
4. Continue with provisioning the compute resource.
The VAST network only becomes available after the file share has been created. It is a third, dedicated network, separate and distinct from public and private networks.
**Adding VAST interface to an existing compute resource**
While the VAST interface can be attached to an already-provisioned GPU cluster or compute resource, this requires additional manual network configuration and is not the standard workflow.
## Resizing file shares
Before picking a region, check that file shares are available there — look for `has_sfs: true` in the regions response:
```bash theme={null} curl "https://api.gcore.com/cloud/v1/regions" \ -H "Authorization: APIKey $GCORE_API_KEY" ```Each step below explains what the call does, which parameters matter, and what the response looks like. Use this section to understand the flow or to debug a specific step.
GET /cloud/v1/tasks/{task_id} every 5 seconds until `state` is `FINISHED`, then read the network ID:
```json theme={null}
{
"state": "FINISHED",
"created_resources": {
"networks": ["6880a081-..."]
}
}
```