Skip to content

Commit a8e8acd

Browse files
committed
formatted
1 parent 0e2c1c7 commit a8e8acd

File tree

1 file changed

+17
-20
lines changed

1 file changed

+17
-20
lines changed

articles/virtual-wan/how-to-routing-policies.md

Lines changed: 17 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ For customers using routing intent, the maximum number of address spaces across
105105

106106
If the number of directly connected Virtual Network address spaces connected to a hub exceeds the limit, enabling routing intent on the Virtual Hub will fail. For hubs already configured with routing intent where Virtual Network address spaces exceeds the limit as a result of an operation such as a Virtual Network address space update, the newly connected address space may not be routable.
107107

108-
Request a limit increase if your network has Virtual Network address spaces greater than 90% of the limit or if you have any planned network expansion or deployment operations that will increase the number of Virtual Network address spaces past this limit.
108+
Proactively request a limit increase if the total number of address spaces across all locally connected Virtual Networks is exceeding 90% of the documented limit or if you have any planned network expansion or deployment operations that will increase the number of Virtual Network address spaces past the limit.
109109

110110
The following table provides a few example Virtual Network address space calculations.
111111

@@ -121,27 +121,24 @@ Make sure to modify the resource ID of the Virtual WAN Hub in the script to matc
121121

122122
```powershell-interactive
123123
$hubVNETconnections = Get-AzVirtualHubVnetConnection -ParentResourceId "/subscriptions/<subscription id>/resourceGroups/<resource group name>/providers/Microsoft.Network/virtualHubs/<virtual hub name>"
124-
125124
$addressSpaceCount = 0
126-
125+
127126
foreach($connection in $hubVNETconnections) {
128-
129-
try{
130-
131-
$resourceURI = $connection.RemoteVirtualNetwork.Id
132-
$RG = ($resourceURI -split "/")[4]
133-
$name = ($resourceURI -split "/")[8]
134-
$VNET = Get-AzVirtualNetwork -Name $name -ResourceGroupName $RG -ErrorAction "Stop"
135-
$addressSpaceCount += $VNET.AddressSpace.AddressPrefixes.Count
136-
}
137-
catch{
138-
Write-Host "An error ocurred while processing VNET connected to Virtual WAN hub with resource URI: " -NoNewline
139-
Write-Host $resourceURI
140-
Write-Host "Error Message: " -ForegroundColor Red
141-
Write-Host $_.Exception.Message -ForegroundColor Red
142-
}
143-
finally{
144-
}
127+
try{
128+
$resourceURI = $connection.RemoteVirtualNetwork.Id
129+
$RG = ($resourceURI -split "/")[4]
130+
$name = ($resourceURI -split "/")[8]
131+
$VNET = Get-AzVirtualNetwork -Name $name -ResourceGroupName $RG -ErrorAction "Stop"
132+
$addressSpaceCount += $VNET.AddressSpace.AddressPrefixes.Count
133+
}
134+
catch{
135+
Write-Host "An error ocurred while processing VNET connected to Virtual WAN hub with resource URI: " -NoNewline
136+
Write-Host $resourceURI
137+
Write-Host "Error Message: " -ForegroundColor Red
138+
Write-Host $_.Exception.Message -ForegroundColor Red
139+
}
140+
finally{
141+
}
145142
}
146143
Write-Host "Total Address Spaces in VNETs connected to this Virtual WAN Hub: " -ForegroundColor Green -NoNewline
147144
Write-Host $addressSpaceCount -ForegroundColor Green

0 commit comments

Comments
 (0)