Skip to main content

Routing Troubleshooting

This document follows a structured method for troubleshooting route configuration-related connectivity issues on the CE (Customer Edge) devices. It is designed to be used step-by-step in order to solve the issue correctly.

Issue: Route Configuration Not Working​

Symptom​

The routes are not configured as expected on the CE device. and connectivity tests (e.g., ping) fail to reach the target IP.

Troubleshooting Steps​

1. Access the CE Terminal​

  • Log in to the CE terminal with superuser privileges to perform diagnostic checks.
sudo su -

2. Verify Current Routes​

  • Use the IP route show to display the current routing table and confirm the presence and correctness of expected routes.
ip route show
  • Analyze output. If missing, incorrect, or does not exist, continue on to the next step.

3. Check Route Configuration File​

Review the CE device's configuration file (for example, the following file is shown, although the actual location of the file may vary). The file and format will depend on the CE device's operating system and method of configuration.

cat /tmp/last_config_response.json

Carefully look at the contents of the file and identify any misconfigurations, typos, or omissions regarding the problematic routes.

4. Test Route Connectivity​

Use the ping command to test the connectivity to your target IP address.

ping <target-ip>

Replace target-ip with your destination IP. Successful pings mean that your route is active. IF there are no replies to your pings, skip to the next step.

5. Check Logs for Errors​

  • Review system logs for any errors related to routing or connectivity:
logread | grep route