You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/vpc/troubleshooting/connectivity-tests.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ It is particularly useful to carry out these steps before opening a support tick
31
31
32
32
2. Try to reach the non-communicating Instance with a ping via `ping instance-name` (where `instance-name` is the name you gave your Instance upon creation.)
33
33
34
-
3. Carry out the same test for both IPv4 and IPv6, ie `ping -4 instance-name` and `ping -6 instance-name`
34
+
3. Carry out the same test for both IPv4 and IPv6, ie `ping -4 instance-name` and `ping -6 instance-name`.
35
35
36
36
- If these tests fail, there may be a DNS issue meaning the Instance's hostname cannot be resolved, see step 4 directly below.
37
37
- Otherwise, if the tests succeed, continue to the section [Verify ARP table](#step-2-verify-artp-table)
@@ -54,7 +54,7 @@ A server's **A**ddress **R**esolution **P**rotocol (ARP) table maps IP addresses
54
54
172.16.8.2 dev ens5 lladdr 02:00:00:1c:0d:9b REACHABLE
55
55
```
56
56
57
-
2. Find the line beginning with the non-communicating Instance's private IP address, and containing also its MAC address (you can check both via the Scaleway console in the Private Network's **Attached resources** tab.)
57
+
2. Find the line beginning with the non-communicating Instance's private IP address, and containing also its MAC address (you can check both via the Scaleway console in the Private Network's **Attached resources** tab).
58
58
59
59
The line ends with the state of the probe for that Instance's MAC address.
60
60
@@ -64,7 +64,7 @@ A server's **A**ddress **R**esolution **P**rotocol (ARP) table maps IP addresses
64
64
65
65
### Step 3: Try reaching the Instance using its LLA
66
66
67
-
If the Instance could not be reached via resolution of its MAC address, next you should try to reach it via its IPv6 **L**ink **L**ocal **A**ddress (LLA) in the Private Network.
67
+
If the Instance could not be reached via the resolution of its MAC address, next you should try to reach it via its IPv6 **L**ink **L**ocal **A**ddress (LLA) in the Private Network.
68
68
69
69
The LLA is calculated from the Instance's MAC address.
0 commit comments