Good evening all,
I am attempting to troubleshoot my internet service and have reached a point of frustration that I need outside eyes in looking into this.
Back in July 2017 I went from my existing single pair dual DSL lines (2 lines, each at 8Mbit/sec), to two bonded 24Mbit/sec lines (2 pair per modem at 13919 per line, for a total of 4 lines and 2 modems). From the day of upgrade onward, 1 of the 4 lines drops each evening right around sunset for about an hour or 2 every few minutes, and then again the same around sunrise. It was dropping around 8:15pm EST when all this started, and has backed up about 5 minutes per night since then to around 6:40pm-ish EST now.
I have opened quite a few (4-5) support tickets and they saw the line dropping during their testing, and dispatched a tech the next week. He would try a few things and then let it sit a week. Rinse and repeat since July and its now almost November.
The same tech has come out now for the last 4 visits (same tech that did the bonded install) and he has done many things to troubleshoot it. The problem now is since he has done the below troubleshooting steps, now THREE of my 4 lines are doing the dropping at sunset/sunrise. Was told by the tech the last time that if it was still having issues he would have to forward me to another tech as he did not know how to fix this.
Troubleshooting steps
- Swapped lines in house to make sure the dropping followed the line and not the modem, confirmed it is not the modems by testing a 3rd spare and it did the same
- Ensured we are using the appropriate PPPoE logons by generating new passwords for both line sets
- Replaced the ENTIRE NID on the side of the house with a new 6 line capable NID and rewired all connections in
- Ran a home run cable from the NID to my office with all 4 pair on the same run, and split into the appropriate lines going into each modem with a twisted pair phone cord right into the backs of the modems
- Ran a home run cable from the pole across my yard to the NID to rule out the underground cable, which has since been switched back to the underground cable when that didn't work
- Replaced all wiring coming from the top of the pole junction down to the underground cross connect
- Changed out all 4 pairs to a new 25 pair and all appropriate cross connects
- Did a side by side comparison of all 4 lines programming and confirmed there were no differences
- Replaced the card at the terminal (?) that the faulty line was on
Here is a sample of the log from when it goes down. I refresh the xDSL stats page and can watch the SN Margin creep down, then plummet to -7.1dB. At the same time, the Super Frame Errors and HEC Errors skyrocket, then the line drops and resyncs, rinse and repeat.
Does this sound like a faulty streetlight somewhere that is throwing some massive interference when it kicks on or something? I have attached screenshots of my DSL stats pages from my modems so you can see the general look of them.
Screenshot 1 is modem 1
Screenshot 1-1 is modem 1 about 30 sec after screenshot 1. Shows the drop in signal and massive burst of Super Frame Errors and HEC Errors and the SN Margin drop.
Screenshot 2 is from modem 2
Log Sample:
2017-10-17T20:57:12-04:00 L3 sdb[1037]: DSL: line-1: Mode ADSL2+ (PTM)
2017-10-17T20:57:12-04:00 L3 sdb[1037]: DSL: line-1: Sync Rate in kbps D/S 13783 U/S 606
2017-10-17T20:57:12-04:00 L3 sdb[1037]: DSL: line-1: Latency path Fast
2017-10-17T20:57:12-04:00 L3 sdb[1037]: DSL: line-1: Trellis D/S:ON U/S:ON
2017-10-17T20:57:12-04:00 L3 sdb[1037]: DSL: line-1: CO Vendor b5004946544ed086
2017-10-17T20:57:12-04:00 L3 sdb[1037]: DSL: line-1: Link showtime counter since boot 111
2017-10-17T20:57:12-04:00 L3 sdb[1037]: DSL: line-1: Retrain Reason RDI
2017-10-17T20:57:43-04:00 L3 sdb[1037]: DSL: line-1: Link drop counter 111
2017-10-17T20:58:04-04:00 L3 sdb[1037]: DSL: line-2: Link drop counter 13
2017-10-17T20:58:08-04:00 L3 sdb[1037]: DSL: line-1: Mode ADSL2+ (PTM)
2017-10-17T20:58:08-04:00 L3 sdb[1037]: DSL: line-1: Sync Rate in kbps D/S 13919 U/S 606
2017-10-17T20:58:08-04:00 L3 sdb[1037]: DSL: line-1: Latency path Fast
2017-10-17T20:58:08-04:00 L3 sdb[1037]: DSL: line-1: Trellis D/S:ON U/S:ON
2017-10-17T20:58:08-04:00 L3 sdb[1037]: DSL: line-1: CO Vendor b5004946544ed086
2017-10-17T20:58:08-04:00 L3 sdb[1037]: DSL: line-1: Link showtime counter since boot 112
2017-10-17T20:58:08-04:00 L3 sdb[1037]: DSL: line-1: Retrain Reason RDI
2017-10-17T20:58:55-04:00 L3 sdb[1037]: DSL: line-2: Mode ADSL2+ (PTM)
2017-10-17T20:58:55-04:00 L3 sdb[1037]: DSL: line-2: Sync Rate in kbps D/S 0 U/S 606
2017-10-17T20:58:55-04:00 L3 sdb[1037]: DSL: line-2: Latency path Fast
2017-10-17T20:58:55-04:00 L3 sdb[1037]: DSL: line-2: Trellis D/S:ON U/S:ON
2017-10-17T20:58:55-04:00 L3 sdb[1037]: DSL: line-2: CO Vendor b5004946544ed086
2017-10-17T20:58:55-04:00 L3 sdb[1037]: DSL: line-2: Link showtime counter since boot 14
2017-10-17T20:58:55-04:00 L3 sdb[1037]: DSL: line-2: Retrain Reason RDI
2017-10-17T20:58:57-04:00 L3 dnsmasq[2971]: no responses from nameserver '8.8.4.4'
2017-10-17T20:59:09-04:00 L3 dnsmasq[2971]: no responses from nameserver '8.8.8.8'
2017-10-17T21:03:16-04:00 L5 pppd[18666]: Serial link appears to be disconnected.
2017-10-17T21:03:22-04:00 L5 pppd[18666]: Connection terminated.
2017-10-17T21:03:22-04:00 L5 pppd[18666]: Modem hangup
2017-10-17T21:03:22-04:00 L4 mcp[18741]: mcp: processing STOP signal
2017-10-17T21:03:42-04:00 L5 pppd[24856]: pppd 2.4.6 started by root, uid 0
2017-10-17T21:03:45-04:00 L4 pppd[24856]: Connected to f4:b5:2f:a1:48:52 via interface br2
2017-10-17T21:03:45-04:00 L5 pppd[24856]: Connect: ppp2 br2
2017-10-17T21:03:46-04:00 L5 pppd[24856]: PAP authentication succeeded
2017-10-17T21:03:46-04:00 L5 pppd[24856]: peer from calling number F4:B5:2F:A1:48:52 authorized
2017-10-17T21:03:46-04:00 L5 pppd[24856]: local IP address 172.78.170.235
2017-10-17T21:03:46-04:00 L5 pppd[24856]: remote IP address 74.42.148.172
2017-10-17T21:03:46-04:00 L5 pppd[24856]: primary DNS address 74.40.74.40
2017-10-17T21:03:46-04:00 L5 pppd[24856]: secondary DNS address 74.40.74.41
2017-10-17T21:03:46-04:00 L5 cwmp[2653]: DSLF_WanMgmtChg path[conn[2].ipaddr] val[172.78.170.235]
2017-10-17T21:03:46-04:00 L5 sdb[1037]: route[1]: forcing onlink route for nexthop (74.42.148.172)
2017-10-17T21:03:46-04:00 L3 cwmp[2653]: DSLF_WANIPChgProc 2
2017-10-17T21:03:47-04:00 L5 mcp[24925]: mcp: kernel's mcfwd_upstream_if is 31 (ppp2)
2017-10-17T21:03:47-04:00 L4 cwmp[2653]: Resolving ACS URL - Retry 0
2017-10-17T21:03:47-04:00 L3 dnsmasq[2971]: nameserver '8.8.8.8' is now responding
2017-10-17T21:03:47-04:00 L5 cwmp[2653]: Connect to https://secure.acs.frontier.com [216.52.29.165] Retry 0
2017-10-17T21:03:48-04:00 L5 cwmp[2653]: (SSL) Connect Success: secure.acs.frontier.com
2017-10-17T21:03:48-04:00 L5 cwmp[2653]: (SSL) Certificate Verify Success: secure.acs.frontier.com
2017-10-17T21:04:00-04:00 L5 cwmp[2653]: Post Inform - reason 4 VALUE CHANGE
2017-10-17T21:04:00-04:00 L5 cwmp[2653]: Receive InformResponse
2017-10-17T21:04:00-04:00 L5 cwmp[2653]: Post 0
2017-10-17T21:04:00-04:00 L5 cwmp[2653]: Receive GetParameterValues
2017-10-17T21:04:00-04:00 L5 cwmp[2653]: Post GetParameterValuesResponse (chunk-length - 3982)
2017-10-17T21:04:00-04:00 L5 cwmp[2653]: Continue GetParameterValuesResponse (chunk-length - 0)
2017-10-17T21:04:01-04:00 L5 cwmp[2653]: Closing connection on HTTP 204
2017-10-17T21:04:01-04:00 L5 cwmp[2653]: (SSL) Closing Connection: secure.acs.frontier.com
2017-10-17T21:04:27-04:00 L3 sdb[1037]: DSL: line-1: Link drop counter 112
2017-10-17T21:04:51-04:00 L3 sdb[1037]: DSL: PTM/ATM changed No Reboot, non-AUTO WAN detection
2017-10-17T21:05:17-04:00 L3 sdb[1037]: DSL: line-1: Mode ADSL2+ (PTM)
2017-10-17T21:05:17-04:00 L3 sdb[1037]: DSL: line-1: Sync Rate in kbps D/S 13860 U/S 606
2017-10-17T21:05:17-04:00 L3 sdb[1037]: DSL: line-1: Latency path Fast
2017-10-17T21:05:17-04:00 L3 sdb[1037]: DSL: line-1: Trellis D/S:ON U/S:ON
2017-10-17T21:05:17-04:00 L3 sdb[1037]: DSL: line-1: CO Vendor b5004946544ed086
2017-10-17T21:05:17-04:00 L3 sdb[1037]: DSL: line-1: Link showtime counter since boot 113
Anyone have ANY idea on how to troubleshoot this?
↧