Skip to content

Commit aae95fd

Browse files
committed
vnets1
1 parent e6a171c commit aae95fd

File tree

1 file changed

+17
-15
lines changed

1 file changed

+17
-15
lines changed

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

Lines changed: 17 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: jasonh
77
ms.service: hdinsight
88
ms.topic: conceptual
99
ms.custom: hdinsightactive
10-
ms.date: 02/25/2020
10+
ms.date: 03/31/2020
1111
---
1212

1313
# Plan a virtual network for Azure HDInsight
@@ -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.
@@ -232,6 +232,8 @@ For more information on controlling outbound traffic from HDInsight clusters, se
232232
233233
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.
234234
235+
You do not need to create user-defined routes as you can rely on automated routing.
236+
235237
## <a id="hdinsight-ip"></a> Required IP addresses
236238
237239
If you use network security groups or user-defined routes to control traffic, see [HDInsight management IP addresses](hdinsight-management-ip-addresses.md).

0 commit comments

Comments
 (0)