Skip to content

Commit 7a8b120

Browse files
authored
Merge pull request #109765 from dagiro/vnets1
vnets1
2 parents 9be38ce + cc28505 commit 7a8b120

File tree

1 file changed

+19
-15
lines changed

1 file changed

+19
-15
lines changed

articles/hdinsight/hdinsight-plan-virtual-network-deployment.md

Lines changed: 19 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -171,22 +171,22 @@ To connect to Apache Ambari and other web pages through the virtual network, use
171171
172172
Replace `RESOURCEGROUP` with the name of the resource group that contains the virtual network, and then enter the command:
173173
174-
```powershell
175-
$clusterNICs = Get-AzNetworkInterface -ResourceGroupName "RESOURCEGROUP" | where-object {$_.Name -like "*node*"}
176-
177-
$nodes = @()
178-
foreach($nic in $clusterNICs) {
179-
$node = new-object System.Object
180-
$node | add-member -MemberType NoteProperty -name "Type" -value $nic.Name.Split('-')[1]
181-
$node | add-member -MemberType NoteProperty -name "InternalIP" -value $nic.IpConfigurations.PrivateIpAddress
182-
$node | add-member -MemberType NoteProperty -name "InternalFQDN" -value $nic.DnsSettings.InternalFqdn
183-
$nodes += $node
184-
}
185-
$nodes | sort-object Type
174+
```powershell
175+
$clusterNICs = Get-AzNetworkInterface -ResourceGroupName "RESOURCEGROUP" | where-object {$_.Name -like "*node*"}
176+
177+
$nodes = @()
178+
foreach($nic in $clusterNICs) {
179+
$node = new-object System.Object
180+
$node | add-member -MemberType NoteProperty -name "Type" -value $nic.Name.Split('-')[1]
181+
$node | add-member -MemberType NoteProperty -name "InternalIP" -value $nic.IpConfigurations.PrivateIpAddress
182+
$node | add-member -MemberType NoteProperty -name "InternalFQDN" -value $nic.DnsSettings.InternalFqdn
183+
$nodes += $node
184+
}
185+
$nodes | sort-object Type
186186
```
187187
188-
```azurecli
189-
az network nic list --resource-group RESOURCEGROUP --output table --query "[?contains(name,'node')].{NICname:name,InternalIP:ipConfigurations[0].privateIpAddress,InternalFQDN:dnsSettings.internalFqdn}"
188+
```azurecli
189+
az network nic list --resource-group RESOURCEGROUP --output table --query "[?contains(name,'node')].{NICname:name,InternalIP:ipConfigurations[0].privateIpAddress,InternalFQDN:dnsSettings.internalFqdn}"
190190
```
191191
192192
In the list of nodes returned, find the FQDN for the head nodes and use the FQDNs to connect to Ambari and other web services. For example, use `http://<headnode-fqdn>:8080` to access Ambari.
@@ -230,7 +230,11 @@ For more information on controlling outbound traffic from HDInsight clusters, se
230230
231231
#### Forced tunneling to on-premises
232232
233-
Forced tunneling is a user-defined routing configuration where all traffic from a subnet is forced to a specific network or location, such as your on-premises network. HDInsight does __not__ support forced tunneling of traffic to on-premises networks.
233+
Forced tunneling is a user-defined routing configuration where all traffic from a subnet is forced to a specific network or location, such as your on-premises network or Firewall. Forced tunneling of all data transfer back to on-premise is _not_ recommended due to large volumes of data transfer and potential performance impact.
234+
235+
Customers who are interested to setup forced tunneling, should use [custom metastores](./hdinsight-use-external-metadata-stores.md) and setup the approperiate connectivity from the cluster subnet or on-premise network to these custom metastores.
236+
237+
To see an example of the UDR setup with Azure Firewall, see [Configure outbound network traffic restriction for Azure HDInsight clusters](hdinsight-restrict-outbound-traffic.md).
234238
235239
## <a id="hdinsight-ip"></a> Required IP addresses
236240

0 commit comments

Comments
 (0)