Difference between revisions of "Troubleshooting Switches"
From Internet Computer Wiki
Katie.peters (talk | contribs) (Created this entire page) |
Katie.peters (talk | contribs) (Adding links to other issues) |
||
Line 1: | Line 1: | ||
+ | Here are the first steps to try when all of your nodes are down. | ||
# Verify if the ISP gateway is pingable: | # Verify if the ISP gateway is pingable: | ||
#* Check the connectivity to the Internet Service Provider (ISP) gateway. | #* Check the connectivity to the Internet Service Provider (ISP) gateway. | ||
Line 29: | Line 30: | ||
#* Provide them with detailed information about the issue, including any troubleshooting steps already taken. | #* Provide them with detailed information about the issue, including any troubleshooting steps already taken. | ||
#* Follow vendor guidance to further investigate and resolve the problem. | #* Follow vendor guidance to further investigate and resolve the problem. | ||
+ | |||
+ | Also see: | ||
+ | |||
+ | * [[Troubleshooting Packet Loss Issues]] | ||
+ | * [[Troubleshooting Interface issues]] | ||
Latest revision as of 18:26, 14 September 2023
Here are the first steps to try when all of your nodes are down.
- Verify if the ISP gateway is pingable:
- Check the connectivity to the Internet Service Provider (ISP) gateway.
- Ping the ISP gateway IP address to determine if it responds.
- If there is no response, contact the ISP to inquire about any connectivity issues or outages in your area.
- Check if the /64 IPv6 subnet default gateway is pingable from outside/inside:
- Ping the default gateway IP address of the IPv6 subnet from both inside and outside the network.
- If there is no response from either side, it indicates a potential issue with the default gateway.
- Verify the configuration of the default gateway and make sure it is properly set up.
- Check for recent port flaps/link failures or any other activities which might cause it:
- Examine logs or monitoring systems for any signs of port flapping, link failures, or abnormal network activities.
- Investigate recent changes, such as software updates, configuration modifications, or physical changes.
- Identify any potential factors that might have caused the network disruption.
- Verify the cabling and port status on the switch:
- Check the physical connections between the affected nodes and the switch.
- Ensure that the cables are securely plugged into the correct ports on both ends.
- Inspect the cables for any damage or loose connections.
- Test the connectivity by using different network cables or ports.
- Try to perform a re-seat of cable/breakout/SFP/QSFP toward the affected machines:
- Disconnect and reconnect the network cables at both the switch and the affected nodes.
- If applicable, re-seat any breakout cables, SFP modules, or QSFP modules used in the connections.
- Ensure all connections are properly seated and secured.
- Try to reboot the switch:
- Save switch configuration before proceeding.
- Reboot the switch to ensure it is functioning correctly.
- Follow proper procedures to avoid any disruption to the network.
- Monitor the switch during and after the reboot to check if the issue is resolved.
- Check with the switch vendor:
- If the problem persists or if you are unable to identify the cause, contact the switch vendor's support team.
- Provide them with detailed information about the issue, including any troubleshooting steps already taken.
- Follow vendor guidance to further investigate and resolve the problem.
Also see:
Back to Node Provider Troubleshooting
Back to Node Provider Documentation