Skip to content

Commit 64d762d

Browse files
committed
added screenshot for portal to flow timeout section
1 parent 145a045 commit 64d762d

File tree

2 files changed

+14
-3
lines changed

2 files changed

+14
-3
lines changed
336 KB
Loading

articles/network-watcher/nsg-flow-logs-overview.md

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -448,12 +448,23 @@ Flows affected by non-default inbound rules become non-terminating. Additionally
448448

449449
You can resolve this difference by setting the `FlowTimeoutInMinutes` property on the associated virtual networks to a non-null value. You can achieve default stateful behavior by setting `FlowTimeoutInMinutes` to 4 minutes. For long-running connections where you don't want flows to disconnect from a service or destination, you can set `FlowTimeoutInMinutes` to a value of up to 30 minutes. Use [Set-AzVirtualNetwork](/powershell/module/az.network/set-azvirtualnetwork) to set `FlowTimeoutInMinutes` property:
450450

451+
451452
```azurepowershell-interactive
452-
$virtualNetwork = Get-AzVirtualNetwork -Name 'myVNet' -ResourceGroupName 'myResourceGroup'
453-
$virtualNetwork.FlowTimeoutInMinutes = 4
454-
$virtualNetwork | Set-AzVirtualNetwork
453+
$virtualNetwork = @{
454+
Name = 'myVNet'
455+
ResourceGroupName = 'myResourceGroup'
456+
}
457+
458+
$virtualNetworkConfig = Get-AzVirtualNetwork @virtualNetwork
459+
$virtualNetworkConfig.FlowTimeoutInMinutes = 4
460+
$virtualNetworkConfig | Set-AzVirtualNetwork
455461
```
456462

463+
Flow timeout can also be set using the Azure portal:
464+
465+
:::image type="content" source="./media/nsg-flow-logs-overview/virtual-network-timeout-settings.png" alt-text="Screenshot showing the virtual network timeout settings in the Azure portal." lightbox="./media/nsg-flow-logs-overview/virtual-network-timeout-settings.png":::
466+
467+
457468
### Inbound flows logged from internet IPs to VMs without public IPs
458469

459470
Virtual machines (VMs) that don't have a public IP address associated with the NIC as an instance-level public IP, or that are part of a basic load balancer back-end pool, use [default SNAT](../load-balancer/load-balancer-outbound-connections.md). Azure assigns an IP address to those VMs to facilitate outbound connectivity. As a result, you might see flow log entries for flows from internet IP addresses, if the flow is destined to a port in the range of ports that are assigned for SNAT.

0 commit comments

Comments
 (0)