You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/elastic-san/elastic-san-connect-linux.md
+27-12Lines changed: 27 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,17 @@ description: Learn how to connect to an Azure Elastic SAN (preview) volume from
4
4
author: roygara
5
5
ms.service: storage
6
6
ms.topic: how-to
7
-
ms.date: 10/24/2022
7
+
ms.date: 10/25/2022
8
8
ms.author: rogarana
9
9
ms.subservice: elastic-san
10
10
ms.custom: references_regions, ignite-2022
11
11
---
12
12
13
13
# Connect to Elastic SAN (preview) volumes - Linux
14
14
15
-
This article explains how to connect to an elastic storage area network (SAN) volume from a Linux client. For details on connecting from a Windows client, see [Connect to Elastic SAN (preview) volumes - Windows](elastic-san-connect-windows.md)
15
+
This article explains how to connect to an Elastic storage area network (SAN) volume from a Linux client. For details on connecting from a Windows client, see [Connect to Elastic SAN (preview) volumes - Windows](elastic-san-connect-windows.md).
16
+
17
+
In this article, you'll add the Storage service endpoint to an Azure virtual network's subnet, then you'll configure your volume group to allow connections from your subnet. Finally, you'll configure your client environment to connect to an Elastic SAN volume and establish a connection.
16
18
17
19
## Prerequisites
18
20
@@ -23,9 +25,16 @@ This article explains how to connect to an elastic storage area network (SAN) vo
To connect to a SAN volume, you need to enable the storage service endpoint on your Azure virtual network subnet, and then connect your volume groups to your Azure virtual network subnets.
31
+
32
+
### Enable Storage service endpoint
33
+
34
+
In your virtual network, enable the Storage service endpoint on your subnet. This ensures traffic is routed optimally to your Elastic SAN. To enable service point for Azure Storage, you must have the appropriate permissions for the virtual network. This operation can be performed by a user that has been given permission to the Microsoft.Network/virtualNetworks/subnets/joinViaServiceEndpoint/action [Azure resource provider operation](../../role-based-access-control/resource-provider-operations.md#microsoftnetwork) via a custom Azure role. An Elastic SAN and the virtual networks granted access may be in different subscriptions, including subscriptions that are a part of a different Azure AD tenant.
27
35
28
-
In your virtual network, enable the Storage service endpoint on your subnet. This ensures traffic is routed optimally to your Elastic SAN.
36
+
> [!NOTE]
37
+
> Configuration of rules that grant access to subnets in virtual networks that are a part of a different Azure Active Directory tenant are currently only supported through PowerShell, CLI and REST APIs. These rules cannot be configured through the Azure portal, though they may be viewed in the portal.
29
38
30
39
# [Portal](#tab/azure-portal)
31
40
@@ -56,11 +65,11 @@ az network vnet subnet update --resource-group "myresourcegroup" --vnet-name "my
56
65
```
57
66
---
58
67
59
-
## Configure networking
68
+
###Configure volume group networking
60
69
61
70
Now that you've enabled the service endpoint, configure the network security settings on your volume groups. You can grant network access to a volume group from one or more Azure virtual networks.
62
71
63
-
By default, no network access is allowed to any volumes in a volume group. Adding a virtual network to your volume group lets you establish iSCSI connections from clients in the same virtual network and subnet to the volumes in the volume group. For more information on networking, see [Configure Elastic SAN networking (preview)](elastic-san-networking.md).
72
+
By default, no network access is allowed to any volumes in a volume group. Adding a virtual network to your volume group lets you establish iSCSI connections from clients in the same virtual network and subnet to the volumes in the volume group. For details on accessing your volumes from another region, see [Enabling access to virtual networks in other regions (preview)](elastic-san-networking.md#enabling-access-to-virtual-networks-in-other-regions-preview).
64
73
65
74
# [Portal](#tab/azure-portal)
66
75
@@ -89,19 +98,19 @@ You can either create single sessions or multiple-sessions to every Elastic SAN
89
98
90
99
When using multiple sessions, generally, you should aggregate them with Multipath I/O. It allows you to aggregate multiple sessions from an iSCSI initiator to the target into a single device, and can improve performance by optimally distributing I/O over all available paths based on a load balancing policy.
91
100
92
-
## Environment setup
101
+
###Environment setup
93
102
94
103
To create iSCSI connections from a Linux client, install the iSCSI initiator package. The exact command may vary depending on your distribution, and you should consult their documentation if necessary.
95
104
96
105
As an example, with Ubuntu you'd use `sudo apt -y install open-iscsi` and with Red Hat Enterprise Linux (RHEL) you'd use `sudo yum install iscsi-initiator-utils -y`.
97
106
98
-
### Multipath I/O
107
+
####Multipath I/O - for multi-session connectivity
99
108
100
109
Install the Multipath I/O package for your Linux distribution. The installation will vary based on your distribution, and you should consult their documentation. As an example, on Ubuntu the command would be `sudo apt install multipath-tools` and for RHEL the command would be `sudo yum install device-mapper-multipath`.
101
110
102
-
Once you've installed the package, check if **/etc/multipath.conf** exists. If **/etc/multipath.conf** doesn't exist, create an empty file and use the settings in the following example for a general configuration. As an example, `mpathconf --enable`to create **/etc/multipath.conf** will create the file on RHEL.
111
+
Once you've installed the package, check if **/etc/multipath.conf** exists. If **/etc/multipath.conf** doesn't exist, create an empty file and use the settings in the following example for a general configuration. As an example, `mpathconf --enable`will create **/etc/multipath.conf** on RHEL.
103
112
104
-
You'll need to make some modifications to **/etc/multipath.conf**. You'll need to add the devices section in the following example, and the defaults section in the following example sets some defaults that'll generally be applicable. If you need to make any other specific configurations, such as excluding volumes from the multipath topology, see the man page for multipath.conf.
113
+
You'll need to make some modifications to **/etc/multipath.conf**. You'll need to add the devices section in the following example, and the defaults section in the following example sets some defaults are generally applicable. If you need to make any other specific configurations, such as excluding volumes from the multipath topology, see the man page for multipath.conf.
105
114
106
115
```
107
116
defaults {
@@ -138,7 +147,13 @@ You should see a list of output that looks like the following:
138
147
139
148
Note down the values for **targetIQN**, **targetPortalHostName**, and **targetPortalPort**, you'll need them for the next sections.
140
149
141
-
## Multi-session connections
150
+
## Determine sessions to create
151
+
152
+
You can either create single sessions or multiple-sessions to every Elastic SAN volume based on your application's multi-threaded capabilities and performance requirements. To achieve higher IOPS and throughput to a volume and reach its maximum limits, use multiple sessions and adjust the queue depth and IO size as needed, if your workload allows.
153
+
154
+
For multi-session connections, install [Multipath I/O - for multi-session connectivity](#multipath-io---for-multi-session-connectivity).
155
+
156
+
### Multi-session connections
142
157
143
158
To establish multiple sessions to a volume, first you'll need to create a single session with particular parameters.
144
159
@@ -168,7 +183,7 @@ for i in `seq 1 numberOfAdditionalSessions`; do sudo iscsiadm -m session -r sess
168
183
169
184
You can verify the number of sessions using `sudo multipath -ll`
170
185
171
-
## Single-session connections
186
+
###Single-session connections
172
187
173
188
To establish persistent iSCSI connections, modify **node.startup** in **/etc/iscsi/iscsid.conf** from **manual** to **automatic**.
Copy file name to clipboardExpand all lines: articles/storage/elastic-san/elastic-san-connect-windows.md
+25-12Lines changed: 25 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,17 @@ description: Learn how to connect to an Azure Elastic SAN (preview) volume from
4
4
author: roygara
5
5
ms.service: storage
6
6
ms.topic: how-to
7
-
ms.date: 10/24/2022
7
+
ms.date: 10/25/2022
8
8
ms.author: rogarana
9
9
ms.subservice: elastic-san
10
10
ms.custom: references_regions, ignite-2022
11
11
---
12
12
13
13
# Connect to Elastic SAN (preview) volumes - Windows
14
14
15
-
This article explains how to connect to an elastic storage area network (SAN) volume from a Windows client. For details on connecting from a Linux client, see [Connect to Elastic SAN (preview) volumes - Linux](elastic-san-connect-linux.md).
15
+
This article explains how to connect to an Elastic storage area network (SAN) volume from a Windows client. For details on connecting from a Linux client, see [Connect to Elastic SAN (preview) volumes - Linux](elastic-san-connect-linux.md).
16
+
17
+
In this article, you'll add the Storage service endpoint to an Azure virtual network's subnet, then you'll configure your volume group to allow connections from your subnet. Finally, you'll configure your client environment to connect to an Elastic SAN volume and establish a connection.
16
18
17
19
## Prerequisites
18
20
@@ -23,9 +25,16 @@ This article explains how to connect to an elastic storage area network (SAN) vo
To connect to a SAN volume, you need to enable the storage service endpoint on your Azure virtual network subnet, and then connect your volume groups to your Azure virtual network subnets.
27
31
28
-
In your virtual network, enable the Storage service endpoint on your subnet. This ensures traffic is routed optimally to your Elastic SAN.
32
+
### Enable Storage service endpoint
33
+
34
+
In your virtual network, enable the Storage service endpoint on your subnet. This ensures traffic is routed optimally to your Elastic SAN. To enable service point for Azure Storage, you must have the appropriate permissions for the virtual network. This operation can be performed by a user that has been given permission to the Microsoft.Network/virtualNetworks/subnets/joinViaServiceEndpoint/action [Azure resource provider operation](../../role-based-access-control/resource-provider-operations.md#microsoftnetwork) via a custom Azure role. An Elastic SAN and the virtual networks granted access may be in different subscriptions, including subscriptions that are a part of a different Azure AD tenant.
35
+
36
+
> [!NOTE]
37
+
> Configuration of rules that grant access to subnets in virtual networks that are a part of a different Azure Active Directory tenant are currently only supported through PowerShell, CLI and REST APIs. These rules cannot be configured through the Azure portal, though they may be viewed in the portal.
29
38
30
39
# [Portal](#tab/azure-portal)
31
40
@@ -56,11 +65,11 @@ az network vnet subnet update --resource-group "myresourcegroup" --vnet-name "my
56
65
```
57
66
---
58
67
59
-
## Configure networking
68
+
###Configure volume group networking
60
69
61
70
Now that you've enabled the service endpoint, configure the network security settings on your volume groups. You can grant network access to a volume group from one or more Azure virtual networks.
62
71
63
-
By default, no network access is allowed to any volumes in a volume group. Adding a virtual network to your volume group lets you establish iSCSI connections from clients in the same virtual network and subnet to the volumes in the volume group. For more information on networking, see [Configure Elastic SAN networking (preview)](elastic-san-networking.md).
72
+
By default, no network access is allowed to any volumes in a volume group. Adding a virtual network to your volume group lets you establish iSCSI connections from clients in the same virtual network and subnet to the volumes in the volume group. For details on accessing your volumes from another region, see [Enabling access to virtual networks in other regions (preview)](elastic-san-networking.md#enabling-access-to-virtual-networks-in-other-regions-preview).
64
73
65
74
# [Portal](#tab/azure-portal)
66
75
@@ -89,7 +98,7 @@ You can either create single sessions or multiple-sessions to every Elastic SAN
89
98
90
99
When using multiple sessions, generally, you should aggregate them with Multipath I/O. It allows you to aggregate multiple sessions from an iSCSI initiator to the target into a single device, and can improve performance by optimally distributing I/O over all available paths based on a load balancing policy.
91
100
92
-
## Set up your environment
101
+
###Set up your environment
93
102
94
103
To create iSCSI connections from a Windows client, confirm the iSCSI service is running. If it's not, start the service, and set it to start automatically.
95
104
@@ -104,9 +113,7 @@ Start-Service -Name MSiSCSI
104
113
Set-Service -Name MSiSCSI -StartupType Automatic
105
114
```
106
115
107
-
### Multipath I/O
108
-
109
-
Multipath I/O enables highly available and fault-tolerant iSCSI network connections. It allows you to aggregate multiple sessions from an iSCSI initiator to the target into a single device, and can improve performance by optimally distributing I/O over all available paths based on a load balancing policy.
116
+
#### Multipath I/O - for multi-session connectivity
110
117
111
118
Install Multipath I/O, enable multipath support for iSCSI devices, and set a default load balancing policy.
Note down the values for **StorageTargetIQN**, **StorageTargetPortalHostName**, and **StorageTargetPortalPort**, you'll need them for the next sections.
143
150
144
-
## Multi-session configuration
151
+
## Determine sessions to create
152
+
153
+
You can either create single sessions or multiple-sessions to every Elastic SAN volume based on your application's multi-threaded capabilities and performance requirements. To achieve higher IOPS and throughput to a volume and reach its maximum limits, use multiple sessions and adjust the queue depth and IO size as needed, if your workload allows.
154
+
155
+
For multi-session connections, install [Multipath I/O - for multi-session connectivity](#multipath-io---for-multi-session-connectivity).
156
+
157
+
### Multi-session configuration
145
158
146
159
To create multiple sessions to each volume, you must configure the target and connect to it multiple times, based on the number of sessions you want to that volume.
147
160
@@ -213,7 +226,7 @@ foreach ($Target in $TargetConfig.Targets.Target)
213
226
214
227
Verify the number of sessions your volume has with either `iscsicli SessionList` or `mpclaim -s -d`
215
228
216
-
## Single-session configuration
229
+
###Single-session configuration
217
230
218
231
Replace **yourStorageTargetIQN**, **yourStorageTargetPortalHostName**, and **yourStorageTargetPortalPort** with the values you kept, then run the following commands from your compute client to connect an Elastic SAN volume. If you'd like to modify these commands, run `iscsicli commandHere -?` for information on the command and its parameters.
Copy file name to clipboardExpand all lines: articles/storage/elastic-san/elastic-san-networking.md
+33-6Lines changed: 33 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: An overview of Azure Elastic SAN (preview), a service that enables
4
4
author: roygara
5
5
ms.service: storage
6
6
ms.topic: how-to
7
-
ms.date: 10/24/2022
7
+
ms.date: 10/25/2022
8
8
ms.author: rogarana
9
9
ms.subservice: elastic-san
10
10
ms.custom: ignite-2022
@@ -23,14 +23,41 @@ Each volume group supports up to 200 virtual network rules.
23
23
> [!IMPORTANT]
24
24
> If you delete a subnet that has been included in a network rule, it will be removed from the network rules for the volume group. If you create a new subnet with the same name, it won't have access to the volume group. To allow access, you must explicitly authorize the new subnet in the network rules for the volume group.
25
25
26
-
## Required permissions
26
+
## Enable Storage service endpoint
27
27
28
-
To enable service point for Azure Storage, the user must have the appropriate permissions for the virtual network. This operation can be performed by a user that has been given permission to the Microsoft.Network/virtualNetworks/subnets/joinViaServiceEndpoint/action [Azure resource provider operation](../../role-based-access-control/resource-provider-operations.md#microsoftnetwork) via a custom Azure role.
29
-
30
-
An Elastic SAN and the virtual networks granted access may be in different subscriptions, including subscriptions that are a part of a different Azure AD tenant.
28
+
In your virtual network, enable the Storage service endpoint on your subnet. This ensures traffic is routed optimally to your Elastic SAN. To enable service point for Azure Storage, you must have the appropriate permissions for the virtual network. This operation can be performed by a user that has been given permission to the Microsoft.Network/virtualNetworks/subnets/joinViaServiceEndpoint/action [Azure resource provider operation](../../role-based-access-control/resource-provider-operations.md#microsoftnetwork) via a custom Azure role. An Elastic SAN and the virtual networks granted access may be in different subscriptions, including subscriptions that are a part of a different Azure AD tenant.
31
29
32
30
> [!NOTE]
33
-
> Configuration of rules that grant access to subnets in virtual networks that are a part of a different Azure Active Directory tenant are currently only supported through PowerShell, CLI and REST APIs. Such rules cannot be configured through the Azure portal, though they may be viewed in the portal.
31
+
> Configuration of rules that grant access to subnets in virtual networks that are a part of a different Azure Active Directory tenant are currently only supported through PowerShell, CLI and REST APIs. These rules cannot be configured through the Azure portal, though they may be viewed in the portal.
32
+
33
+
# [Portal](#tab/azure-portal)
34
+
35
+
1. Navigate to your virtual network and select **Service Endpoints**.
36
+
1. Select **+ Add** and for **Service** select **Microsoft.Storage**.
37
+
1. Select any policies you like, and the subnet you deploy your Elastic SAN into and select **Add**.
38
+
39
+
:::image type="content" source="media/elastic-san-create/elastic-san-service-endpoint.png" alt-text="Screenshot of the virtual network service endpoint page, adding the storage service endpoint." lightbox="media/elastic-san-create/elastic-san-service-endpoint.png":::
0 commit comments