Skip to content

Commit c238163

Browse files
committed
Acrolinx
1 parent f135758 commit c238163

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

AKS-Arc/connectivity-troubleshoot.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ Use this guidance when BGP sessions fail to establish, external IP routing doesn
2020

2121
In environments using MetalLB with FRR for BGP peering, you might experience the following issues:
2222

23-
- BGP sessions are not established or keep flapping, a condition where the BGP session repeatedly goes up and down, causing route instability. This can be due to network issues, misconfigurations, or hardware problems. It can result in degraded performance or loss of service availability.
24-
- Services of type `LoadBalancer` do not receive properly routed external IPs.
23+
- BGP sessions are not established or keep flapping, a condition where the BGP session repeatedly goes up and down, causing route instability. This behavior can be due to network issues, misconfigurations, or hardware problems. It can result in degraded performance or loss of service availability.
24+
- Services of type `LoadBalancer` don't receive properly routed external IPs.
2525
- Advertised routes are missing or not propagated to upstream routers.
2626
- Network connectivity to exposed services is inconsistent or unavailable.
2727

@@ -74,7 +74,7 @@ kubectl logs -n kube-system arcnetworking-metallb-speaker-xxxxx -c frr
7474
### Review TOR switch configuration
7575

7676
- Configuration and logs from the top-of-rack (TOR) switch or upstream router might be necessary.
77-
- These are hardware/vendor-specific and not covered in this guide.
77+
- These logs are hardware/vendor-specific and not covered in this guide.
7878

7979
## Next steps
8080

0 commit comments

Comments
 (0)