--- title: "Connect a network volume to a dedicated server with VMware ESXi hypervisor" sidebar_label: "Connect a network volume to a dedicated server with VMware ESXi hypervisor" sidebar_position: 5 description: "How to connect a network volume to a dedicated server with VMware ESXi hypervisor" --- import Formbricks from '@theme/MDXComponents/Formbricks'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import { TabItemLabel } from '@selectel/docux/components'; import SanBlockStorage from '@site/i18n/en/docusaurus-plugin-content-docs/current/_partials/dedicated/block-storage/san-of-block-storage.mdx'; import ConnectBlockStorageInPanel from '@site/i18n/en/docusaurus-plugin-content-docs/current/_partials/dedicated/block-storage/connect-block-storage-to-server-in-panel.mdx'; # Connect a network volume to a dedicated server with VMware ESXi hypervisor Learn more about network volumes in the [General Product Information: Network Volumes](/block-storage/about/about-block-storage.mdx) guide. 1. [Create a SAN network](#create-san). 2. [Connect the network volume to the server](#connect-block-storage-to-server-in-panel). 3. [Connect the network volume to the server in the server OS](#connect-block-storage-to-server-in-os). 4. [Mount the VMFS file system](#mount-vmfs-file-system). ## 1. Create a SAN network \{#create-san} ## 2. Connect the network volume to the server \{#connect-block-storage-to-server-in-panel} ## 3. Connect the network volume to the server in the server OS \{#connect-block-storage-to-server-in-os} You can connect a network volume to the server manually or using a ready-made script generated in the control panel. The script can only be used on Ubuntu OS — see the [Connect a network volume to a dedicated Linux server](/block-storage/manage/connect-block-storage-to-linux.mdx). instruction for more details. SAN network 1. [Connect to the server via SSH](/dedicated/manage/connect-to-server.mdx#connect-via-ssh) or via [KVM console](/dedicated/manage/connect-to-server.mdx#connect-via-kvm-console). 2. Display the list of network interfaces: ```bash esxcli network nic list ``` The response will contain a list of network interfaces. For example: ```bash Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description -------- ------------ -------- ------------ ----------- ----- ------ ----------------- ---- ----------- vmnic0 0000:01:00.0 nmlx4_en Up Up 10000 Full 1x:11:xx:0x:00:x0 1500 Mellanox Technologies ConnectX-3 Pro EN NIC; 10GigE; dual-port SFP+ (MCX312B-XCC) vmnic1 0000:02:00.0 igbn Up Up 1000 Full aa:1a:0a:11:1a:a0 1500 Intel Corporation I350 Gigabit Network Connection vmnic128 0000:01:00.0 nmlx4_en Up Up 10000 Full 1c:00:cc:0c:00:c0 1500 Mellanox Technologies ConnectX-3 Pro EN NIC; 10GigE; dual-port SFP+ (MCX312B-XCC) vmnic2 0000:02:00.1 igbn Up Up 1000 Full cc:1c:6c:01:6c:c1 1500 Intel Corporation I350 Gigabit Network Connection ``` Here, in the `Name` field, are the names of the network interfaces. 3. Display information about the network interface configuration: ```bash esxcli network vswitch standard list ``` The response will contain the current configuration of network interfaces. For example: ```bash vSwitch0 Name: vSwitch0 Class: cswitch Num Ports: 2560 Used Ports: 4 Configured Ports: 128 MTU: 1500 CDP Status: listen Beacon Enabled: false Beacon Interval: 1 Beacon Threshold: 3 Beacon Required By: Uplinks: vmnic1 Portgroups: VM Network, Management Network ``` 4. Create two virtual switches for the SAN network: ```bash esxcli network vswitch standard add --vswitch-name= esxcli network vswitch standard add --vswitch-name= ``` Specify: * `` — the name of the first virtual switch; * `` — the name of the second virtual switch. 5. Assign network interfaces to the virtual switches: ```bash esxcli network vswitch standard uplink add --vswitch-name= --uplink-name= esxcli network vswitch standard uplink add --vswitch-name= --uplink-name= ``` Specify: * `` — the name of the first virtual switch that you created in step 4; * `` — the name of the first network interface on the first port of the network card that you obtained in step 2; * `` — the name of the second virtual switch that you created in step 4; * `` — the name of the second network interface on the second port of the network card that you obtained in step 2. 6. Ensure that the network interfaces are configured correctly: ```bash esxcli network vswitch standard list ``` The response will show the configuration of the network interfaces that you configured in steps 4 and 5. 7. Create port groups on the virtual switches: ```bash esxcli network vswitch standard portgroup add --portgroup-name= --vswitch-name= esxcli network vswitch standard portgroup add --portgroup-name= --vswitch-name= ``` Specify: * `` — the name of the first port group; * `` — the name of the first virtual switch that you created in step 4; * `` — the name of the second port group; * `` — the name of the second virtual switch that you created in step 4. 8. Ensure that the port groups are correctly created on the virtual switches: ```bash esxcli network vswitch standard portgroup list ``` The response will contain a list of the port groups that you created in step 7. 9. Create virtual interfaces: ```bash esxcli network ip interface add --interface-name= --portgroup-name= esxcli network ip interface add --interface-name= --portgroup-name= ``` Specify: * `` — the name of the first virtual interface; * `` — the name of the first port group that you created in step 7; * `` — the name of the second virtual interface; * `` — the name of the second port group you created in step 7. 10. Add IP addresses to the virtual interfaces: ```bash esxcli network ip interface ipv4 set --interface-name= --ipv4 --netmask --type static esxcli network ip interface ipv4 set --interface-name= --ipv4 --netmask --type static ``` Specify: * `` — the name of the first virtual network interface that you created in step 9; * `` — the IP address of the first network card port. You can view it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → section **Network Volumes and Storage** → tab **Network Volumes** → disk page → block **Network interface configuration** → column **Port IP address**; * `` – the destination subnet interface mask for the first network card port in IPv4 mask format. For example: `255.255.252.0` for `/22`, `255.255.255.0` for `/24`, `255.255.255.252` for `/30`. You can view it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → section **Network Volumes and Storage** → tab **Network Volumes** → disk page → block **Static routes for iSCSI target connection** → column **Destination Subnet**; * `` — name of the second virtual network interface that you created in step 9; * `` — the IP address of the second network card port. You can view it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → section **Network Volumes and Storage** → tab **Network Volumes** → disk page → block **Network interface configuration** → column **Port IP address**; * `` – the destination subnet interface mask for the second network card port in IPv4 mask format. For example: `255.255.252.0` for `/22`, `255.255.255.0` for `/24`, `255.255.255.252` for `/30`. You can view it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → section **Network Volumes and Storage** → tab **Network Volumes** → disk page → block **Static routes for iSCSI target connection** → column **Destination Subnet**. 11. Ensure that the virtual network interfaces are created and configured correctly: ```bash esxcfg-vmknic -l ``` The response will show the configuration of the virtual network interfaces that you configured in steps 9 and 10. 12. Ensure that the destination network gateway is reachable: ```bash vmkping -I vmkping -I ``` Specify: * `` — name of the first virtual network interface that you created in step 9; * `` — the gateway for the first network card port. You can view it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → section **Network Volumes and Storage** → tab **Network Volumes** → disk page → block **Network interface configuration** → column **Next hop (gateway)**; * `` — name of the second virtual network interface that you created in step 9; * `` — the gateway for the second network card port. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **Network interface configuration** block → the **Next hop (gateway) \*\*\*\* column**. 13. Add static routes to access the iSCSI targets: ```bash esxcli network ip route ipv4 add --network --gateway esxcli network ip route ipv4 add --network --gateway ``` Specify: * `` — the destination subnet for the first network card port. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **Static routes for iSCSI target connection** block → the **Destination Subnet \*\*\*\* column**; * `` — the gateway for the first network card port. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **Network interface configuration** block → the **Next hop (gateway) \*\*\*\* column**; * `` — the destination subnet for the second network card port. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **Static routes for iSCSI target connection** block → the **Destination Subnet \*\*\*\* column**; * `` — the gateway for the second network card port. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **Network interface configuration** block → the **Next hop (gateway) \*\*\*\* column**. 14. Ensure that the routes added in step 13 have been applied: ```bash esxcli network ip route ipv4 list ``` 15. Ensure that the iSCSI target is reachable: ```bash vmkping -I vmkping -I ``` Specify: * `` — name of the first virtual network interface that you created in step 9; * `` — the IP address of the first iSCSI target. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **iSCSI target IP address 1 \*\*\*\* field**; * `` — name of the second virtual network interface that you created in step 9; * `` — the IP address of the second iSCSI target. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **iSCSI target IP address 2 \*\*\*\* field**. 16. Check the status of the iSCSI initiator: ```bash esxcli iscsi software get ``` 17. If the iSCSI initiator status is `false`, enable it: ```bash esxcli iscsi software set --enabled true ``` 18. Display the list of iSCSI adapters: ```bash esxcli iscsi adapter list ``` The response will contain a list of iSCSI adapters. For example: ```bash Adapter Driver State UID Description ------- --------- ------ ------------- ----------- vmhba64 iscsi_vmk online iscsi.vmhba64 iSCSI Software Adapter ``` Here, the `Adapter` field contains the names of the iSCSI adapters. 19. Set the iSCSI initiator name: ```bash esxcli iscsi adapter set --adapter= --name= ``` Specify: * `` — iSCSI adapter name that you obtained in step 18; * `` — the iSCSI initiator name. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **Initiator name \*\*\*\* field**. 20. Bind the virtual interfaces to the iSCSI adapter: ```bash esxcli iscsi networkportal add --nic --adapter esxcli iscsi networkportal add --nic --adapter ``` Specify: * `` — name of the first virtual network interface that you created in step 9; * `` — name of the second virtual network interface that you created in step 9; * `` — iSCSI adapter name that you obtained in step 18. 21. Ensure that the virtual interfaces are bound to the iSCSI adapter: ```bash esxcli iscsi networkportal list ``` 22. Configure CHAP authentication for the iSCSI initiator: ```bash esxcli iscsi adapter auth chap set -A --authname= --secret= --level required ``` Specify: * `` — iSCSI adapter name that you obtained in step 18; * `` — the username for iSCSI initiator authorization. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **Username \*\*\*\* field**; * `` — the password for iSCSI initiator authorization. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **Password \*\*\*\* field**. 23. Ensure that CHAP authentication is configured correctly: ```bash esxcli iscsi adapter auth chap get -A ``` Specify `` — iSCSI adapter name that you obtained in step 18. 24. Configure static iSCSI targets for the iSCSI adapter: ```bash esxcli iscsi adapter discovery statictarget add -A -a :3260 -n esxcli iscsi adapter discovery statictarget add -A -a :3260 -n ``` Specify: * `` — iSCSI adapter name that you obtained in step 18; * `` — the IP address of the first iSCSI target. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **iSCSI target IP address 1 \*\*\*\* field**; * `` — the IP address of the second iSCSI target. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **iSCSI target IP address 2 \*\*\*\* field**; * `` — the IQN of the first and second iSCSI target. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **Target name \*\*\*\* field**. 25. Ensure that static iSCSI targets for the iSCSI adapter are configured correctly: ```bash esxcli iscsi adapter target list ``` 26. Initiate a rescan for iSCSI targets for the iSCSI adapter: ```bash esxcli iscsi adapter discovery rediscover -A ``` Specify `` — iSCSI adapter name that you obtained in step 18. 27. Check the status of the last iSCSI target discovery: ```bash esxcli iscsi adapter discovery status get -A ``` Specify `` — iSCSI adapter name that you obtained in step 18. 28. Ensure that all static iSCSI targets are configured correctly: ```bash esxcli iscsi adapter discovery statictarget list -A ``` Specify `` — iSCSI adapter name that you obtained in step 18. 29. Initiate an iSCSI session: ```bash esxcli iscsi session add -A -n ``` Specify: * `` — iSCSI adapter name that you obtained in step 18; * `` — the IQN of the first and second iSCSI target. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **Target name \*\*\*\* field**. 30. Ensure that the iSCSI session is running: ```bash esxcli iscsi session list ``` 31. Check connectivity to the iSCSI targets: ```bash nc -s -z 3260 nc -s -z 3260 ``` Specify: * `` — the IP address of the first network card port. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **Network interface configuration** block → the **Port IP address \*\*\*\* column**; * `` — the IP address of the first iSCSI target. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **iSCSI target IP address 1 \*\*\*\* field**; * `` — the IP address of the second network card port. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **Network interface configuration** block → the **Port IP address \*\*\*\* column**; * `` — the IP address of the second iSCSI target. You can find it in the [control panel](https://my.selectel.ru/servers/shd/block-storage/disks): in the top menu, click **Products** → **Dedicated Servers** → the **Network Volumes and Storage** section → the **Network Volumes** tab → disk page → the **iSCSI connection configuration** block → the **iSCSI target IP address 2 \*\*\*\* field**. 32. Update the list of all adapters: ```bash esxcli storage core adapter rescan --all ``` 33. Get the network volume identifier: ```bash esxcli storage core device list ``` The response will contain a list of connected storage devices. For example: ```bash Device: naa.600140558e7a2bfee234358ad22f7c79 Display Name: naa.600140558e7a2bfee234358ad22f7c79 Has Settable Display Name: true Size: 100.00 GB Device Type: Direct-Access Multipath Plugin: NMP Devfs Path: /vmfs/devices/disks/naa.600140558e7a2bfee234358ad22f7c79 Vendor: LIO-ORG Model: iscsi-disk ``` Where: * `Device` — network volume identifier; * `Model` — storage device model or software description as specified by the target, e.g., an iSCSI server. 34. Display the network volume information: ```bash esxcli storage core device list -d ``` Specify `` — network volume identifier that you obtained in step 33. 35. Configure the network volume access policy: ```bash esxcli storage nmp device set -d -P ``` Specify: * `` — network volume identifier that you obtained in step 33. * `` — path selection policy, which determines how I/O requests are directed to storage when multiple paths are available: * Round Robin (`VMW_PSP_RR`) — evenly distributes I/O requests across all available paths; * Most Recently Used (`VMW_PSP_MRU`) — uses the last active path. If a failure occurs, it switches to another path and does not return to the original path after it is restored. Suitable for configurations with active-passive storage; * Fixed (`VMW_PSP_FIXED`) — uses only one specified path; by default, the first functional one. If a failure occurs, it switches to an available path but returns to the original one when it is restored; * Fixed with Automatic Path Failover (`VMW_PSP_FIXED_AP`) — similar to the Fixed policy, but path switching occurs automatically. 36. Display the network volume information: ```bash esxcli storage nmp device list -d ``` Specify `` — network volume identifier that you obtained in step 33. 37. Ensure that `Round Robin` is configured correctly: ```bash esxcli storage nmp psp roundrobin deviceconfig get -d ``` Specify `` — network volume identifier that you obtained in step 33. 38. Ensure that the paths the server uses to connect to the network volume are configured correctly: ```bash esxcli storage core path list -d ``` Specify `` — network volume identifier that you obtained in step 33. ## 4. Mount the VMFS file system \{#mount-vmfs-file-system} VMFS (VMware File System) is a clustered file system used by VMware ESXi to store virtual machine files. VMFS supports shared storage access by multiple ESXi hosts. This is the only type of file system for network storage. 1. Create a GPT partition table on the disk: ```bash partedUtil mklabel /dev/disks/ gpt ``` Specify `` — network volume identifier that you obtained when [connecting the network volume to the server in the server OS](#connect-block-storage-to-server-in-os) in step 33. 2. Obtain the range of valid sectors for partitioning: ```bash partedUtil getUsableSectors /dev/disks/ ``` Specify `` — network volume identifier that you obtained when [connecting the network volume to the server in the server OS](#connect-block-storage-to-server-in-os) in step 33. The response will contain the start and end sector values available for use. For example: ```bash 2048 314572766 ``` Where: * `2048` — start sector; * `314572766` — end sector. 3. Create a partition on the disk: ```bash partedUtil setptbl /dev/disks/ gpt " AA31E02A400F11DB9590000C2911D1B8 0" ``` Specify: * `` — network volume identifier that you obtained when [connecting the network volume to the server in the server OS](#connect-block-storage-to-server-in-os) in step 33; * `` — partition number; * `` — start sector; * `` — end sector. 4. Format the partition with the VMFS file system: ```bash vmkfstools -C vmfs6 -S /dev/disks/: ``` Specify: * `` — logical data store name; * `` — network volume identifier that you obtained when [connecting the network volume to the server in the server OS](#connect-block-storage-to-server-in-os) in step 33; * `` — partition number that you specified in step 3. 5. Ensure that the file system is available for mounting: ```bash esxcli storage filesystem list ``` 6. Ensure that the datastore you created in step 4 is available for use: 6.1. Open the vSphere Web Client web interface. 6.2. Go to **Storage** → **Datastore 2**. 6.3. Check that a storage with type `VMFS6` and status `Accessible` has appeared in the list 3.