Voyager
•
2 Messages
Connection problems (NVG510)
Several times a day our connection to the internet goes out for 2-4 minutes. On our NVG510 the broadband and service lights go out. Could this be due to low SN Margin (dB) stats (see table below).
I have ipv6 turned off on the modem.
Here is the last log entry:
2017-01-02T00:24:18-06:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x1 RDI Detector 2017-01-02T00:24:19-06:00 L3 sdb[305]: DSL: Link drop counter since boot 51 2017-01-02T00:24:19-06:00 L1 sdb[305]: nm_ipv6_add_firewall: (4) 2017-01-02T00:24:19-06:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy 2017-01-02T00:24:19-06:00 L1 sdb[305]: nm_ipv6_add_firewall: (4) The last message was repeated 2 times. 2017-01-02T00:24:19-06:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy 2017-01-02T00:24:19-06:00 L1 sdb[305]: nm_ipv6_add_firewall: (4) The last message was repeated 3 times. 2017-01-02T00:24:21-06:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy 2017-01-02T00:24:42-06:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2 2017-01-02T00:25:29-06:00 L1 sdb[305]: nm_ipv6_add_firewall: (4) 2017-01-02T00:25:29-06:00 L3 sdb[305]: DSL: Mode ADSL2+ (PTM) 2017-01-02T00:25:29-06:00 L3 sdb[305]: DSL: Sync Rate in kbps D/S 14396 U/S 1020 2017-01-02T00:25:29-06:00 L3 sdb[305]: DSL: Latency path Interleaved 2017-01-02T00:25:29-06:00 L3 sdb[305]: DSL: Trellis D/S:ON U/S:ON 2017-01-02T00:25:29-06:00 L3 sdb[305]: DSL: CO Vendor BDCM 2017-01-02T00:25:29-06:00 L3 sdb[305]: DSL: Link showtime counter since boot 52 2017-01-02T00:25:30-06:00 L1 sdb[305]: nm_ipv6_add_firewall: (4) 2017-01-02T00:25:30-06:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy 2017-01-02T00:25:30-06:00 L1 sdb[305]: nm_ipv6_add_firewall: (4) The last message was repeated 2 times. 2017-01-02T00:25:33-06:00 L5 supp1x[1312]: Sending START Packet 2017-01-02T00:25:36-06:00 L5 supp1x[1312]: Supplicant event = SUCCESS 2017-01-02T00:25:36-06:00 L1 sdb[305]: nm_ipv6_add_firewall: (4) 2017-01-02T00:25:41-06:00 L3 dhcpd[362]: WARNING: server ignoring option dhcp-renewal-time in configuration file. 2017-01-02T00:25:41-06:00 L3 dhcpd[362]: WARNING: server ignoring option dhcp-rebinding-time in configuration file. 2017-01-02T00:25:41-06:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
Here are my stats:
Downstream and Upstream Statistics
| Downstream | Upstream | |
| SN Margin (dB) | 5.3 | 8.2 |
| Line Attenuation (dB) | 29.0 | 16.1 |
| Output Power(dBm) | 17.9 | 12.1 |
| Errored Seconds | 51 | 0 |
| Loss of Signal | 0 | 0 |
| Loss of Frame | 0 | 0 |
| FEC Errors | 3701 | 3 |
| CRC Errors | 70 | 0 |
ApexRon
Professor
•
2.2K Messages
7 years ago
@ATTDSLCare
0
0
randrmu3ll3r
Voyager
•
2 Messages
7 years ago
Apexron: Sorry, I didn't see an answer in your reply???
0
0
my thoughts
Former Employee
•
21.1K Messages
7 years ago
Yes, SN needs to be 6.0 or better to maintain service....
Recommend scheduling a service tech (4 hour appointment window) to have issue resolved.
SN is a combination of loop length, line quality and broadband being sent.
Loop length, physical distance, the longer the copper wire the lower the profile as copper loss reduces signal.
Line quality, poor connection either inside the home (data cable, jack, inside wiring, NID connection) or outside (drop, terminal connection, plant, crossbox connection, etc)
Lastly how much being crammed, if service was recently upgraded, not enough signal reaching gateway to maintain service. An example was a 6M profile requirement was raised... Where see ice might have been stable the new requirement of 7.2 for 6 means dropping below support. Result need to lower profile and speed from 6 to 3 to improve SN margin.
A Uverse tech would have the equipment to identify and correct issue, if inside wiring could be billable $99. This is most often when a customer has done a self install to save money ($99 installation charge) and have old wiring going to multiple jacks instead of single cat5e from NID to gateway.
0
0