Skip to content

Commit eb69f2f

Browse files
committed
Interim checkin - updates from 02/22 Sync
1 parent f2d151a commit eb69f2f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/databox-online/azure-stack-edge-gpu-manage-access-power-connectivity-mode.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -119,13 +119,13 @@ If a user needs to be able to connect to the Azure Stack Edge appliance from an
119119

120120
- **Outbound traffic:** For outbound traffic from the appliance to the customer's laptop (network B to network A):
121121

122-
- Configure the <!--correct - CAN THIS GO?--> gateways on the appliance so that traffic can reach network A.
122+
- Configure the correct <!--What's meant by "correct"? Clarify, or remove "correct"?--> gateways on the appliance so that traffic can reach network A.
123123

124124
- If you configure multiple gateways on the appliance, ensure that traffic can reach network B on all gateways.
125125

126126
An appliance ideally tries to use the network interface card (NIC) with the lowest route metric. However, there's no clear way for an Azure Stack Edge appliance to identify the NIC with the lowest metric. So it's best to make network A reachable on all configured gateways.
127127

128-
> [!NOTE]
128+
> [!NOTE]
129129
> Diagnostic tests for Azure Stack Edge return a warning if all gateways don't have internet connectivity. For diagnostics information, see [Run diagnostics](azure-stack-edge-gpu-troubleshoot.md#run-diagnostics). <!--Terminology creep: This is the first reference to internet connectivity.-->
130130
131131

0 commit comments

Comments
 (0)