Description
This article describes steps which can be taken to confirm the root of the issue that has brought the ADSL service status down in the event of an ADSL connectivity failure.
One possible cause is an actual physical failure that sometimes cannot be detected by an HQIP test.
Scope
FortiWiFi-60CA using an ADSL port.
Solution
- Whilst having the interface connected to an ADSL modem, run 'diagnose debug application adsl2 255' in the CLI. Confirm the ADSL status is DOWN.
Day Mon Dat HH:MM:SS YYYY 60soc_adsl.c[686] adsl2plus_check_status - ADSL's link is down
- Run 'diagnose adsl show 2'. If the 'Modem Status' is 'SHOWTIME_TC_SYNC', the issue is not a hardware module failure.
Modem Status [SHOWTIME_TC_SYNC]
If the 'Modem Status' is 'SILENT', there may be a physical link issue or ADSL module hardware issue.
Modem Status [SILENT]
- A further test should then be made with another device being connected to the ADSL modem in order to confirm the connectivity status. If the status is also 'SILENT', it is a physical link issue. Otherwise, it may well be a FortiWiFi ADSL module hardware failure and it should be replaced by an RMA exchange.
Related articles:
Troubleshooting Tip: Collecting Logs and Configuration for DSL Troubleshooting with TAC
