24. Troubleshooting Network Issues
This section describes some of the troubleshooting measures that could be undertaken by technical personnel with various levels of expertise.
The most typical statement of an issue, as applicable to ChiefNET's place in the network topology, is that the branch-branch traffic does not work. The second most typical statement of the issue is that Internet is not reachable.
However, there could be many underlying causes and ChiefNET provides the following tips and measures.
24.1 Verify WAN Link Connectivity
ChiefNET's WAN ports are typically connected to the ISP-provided devices. It is often best to check your ISP's portals, alerts and notifications to check for outages in their network service. In the event this information is not available or reliable, the following could be done.
- Access the orchestrator webui from a mobile phone with LTE or on any system that has Internet access.
- Check alerts and notifications which would indicate if the WAN links are down. A WAN link is declared down, if a ping response is not received for an interval of 30 seconds.
- ChiefNET keeps trying to check if the WAN link comes back alive by sending periodic ping probes.
If one WAN link is down, and if failover feature is configured, ChiefNET will automatically switch traffic over to the other WAN link if available.
If failover and load-balancing are both configured, traffic will continue on the operational WAN link and will not be forwarded over to the failed WAN link. In this case, it is possible that the traffic may exceed the capacity of the operational WAN link (as that would have been the reason to configure load-balancing). For smoother operation -- configure QoS on the WAN links so that the traffic is shaped at the application-level -- configure exclusive traffic forwarding so that low-priority traffic is allowed on some WAN links only and discarded if those WAN links are not operational. This way, only the high-priority traffic is forwarded on the available/operational WAN links.
24.2 Firewall Configuration Changes
Verify the the changes done on firewalls possibly between ChiefNET and the ISP are not blocking the traffic in any way.
24.3 ChiefNET Alerts and Notifications
When the WAN links are found to be failed, ChiefNET sends alerts/notifications as emails. Watch for such notifications and alert your ISP immediately for customer support.
24.4 Debugging ChiefNET
If ChiefNET device is suspected under such conditions, the following should be done. - Access the webui orchestrator and verify that the device is reported as 'up' with green background. This indicates that the CPE device gets connected to the Orchestrator on its management connection (HTTPS based connection). - Verify that there are no alerts. - Check the statistics on the WAN ports and the LAN ports to see if they are increasing.
24.5 Customer Support
ChiefNET customer support team continually monitors the customer networks for new alerts and uses the backend monitoring tools to isolate customers' network issues.
24.6 Frequently Asked Questions
24.6.1 Why is the ChiefNET CPE not able to reach the Internet through the firewall?
- Check mac-address whitelist on the firewall.
- Check logs on firewall (if any) to see if CPE device is blocked for any reason.
Many a time, we have noticed that the customers modify the configurations of the firewalls which sometimes blocks ChiefNET. Use the standard network troubleshooting tools like ping/traceroute to isolate the problem.
Always check the firewall logs and events to see what are blocked for additional clues to isolating the problem.
24.6.2 Do firewalls need to be configured for ChiefNET?
In some organizations, the IT department hard-codes the mac-address into the firewalls, so that only specific devices are allowed to go through the firewall. This implies that the customer would have to configure the mac-address of ChiefNET in the firewall configuration.
24.6.3 Why is the Internet slow?
- In most cases, the Internet is slow due to the service provider's network and not necessarily with any of the equipment online.
- If traffic bandwidth is suspected of slowing down the Internet for critical applications (e.g. branch locations trying to update the inventory and sales data at the HQ), it can be resolved by configuring QoS for critical applications. ChiefNET's QoS features provide miinimum bandwidth quarantee, as well as limit the maximum for a given class of applications.