dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1917
share rss forum feed

memlaneinc

join:2013-08-29
Tustin, CA

NVG510 Modem Issues at Night (3am-7am)

Hello,

We are having issues with our modem dropping signal right around 3am-7am and we have to restart the modem to get back on and then we are able to get online for the entire day but every morning we have to restart the modem. I know it is around 3am-7am because it shows on my alerts on the server that it shows the signal drop around that time frame. I know I saw on other messages/topics on this site that if the Line Attenuation is high and the SN Margin (dB) is low, there is usually a problem with the line. If you guys can give me any input on this issue, I would very much appreciated it.

Thanks Brad

Here is some diagnostic information below:

Downstream and Upstream Statistics

Downstream Upstream
SN Margin (dB) 7.1 16.4
Line Attenuation (dB) 41.0 26.1
Output Power(dBm) 18.9 12.0
Errored Seconds 0 0
Loss of Signal 0 0
Loss of Frame 0 0
FEC Errors 10910 9
CRC Errors 0 0

memlaneinc

join:2013-08-29
Tustin, CA
Here is also my diagnostic log if this helps as well.

2013-08-29T09:05:17-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.153'
2013-08-29T09:05:17-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.153' is now responding
2013-08-29T09:16:58-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.153'
2013-08-29T09:17:02-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.153' is now responding
2013-08-29T09:19:44-07:00 L3 sdb[305]: Wi-Fi: 8c:58:77:3f:9e:1f re-joined ATT184 after 30 d 16 h 16 m 47 seconds
2013-08-29T09:19:44-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 1
2013-08-29T09:20:02-07:00 L3 sdb[305]: Wi-Fi: Client 8c:58:77:3f:9e:1f left ATT184
2013-08-29T09:20:02-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 0
2013-08-29T09:25:18-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.53'
2013-08-29T09:25:18-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.53' is now responding
2013-08-29T09:26:02-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.153'
2013-08-29T09:26:02-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.153' is now responding
2013-08-29T09:43:18-07:00 L3 sdb[305]: Wi-Fi: 8c:58:77:3f:9e:1f re-joined ATT184 after 30 d 16 h 23 m 16 seconds
2013-08-29T09:43:18-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 1
2013-08-29T09:43:38-07:00 L3 sdb[305]: Wi-Fi: Client 8c:58:77:3f:9e:1f left ATT184
2013-08-29T09:43:38-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 0
2013-08-29T09:46:18-07:00 L3 sdb[305]: Wi-Fi: 8c:58:77:3f:9e:1f re-joined ATT184 after 30 d 16 h 2 m 40 seconds
2013-08-29T09:46:18-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 1
2013-08-29T09:46:48-07:00 L3 sdb[305]: Wi-Fi: Client 8c:58:77:3f:9e:1f left ATT184
2013-08-29T09:46:48-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 0
2013-08-29T09:48:16-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.153'
2013-08-29T09:48:16-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.153' is now responding
2013-08-29T09:49:31-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.153'
2013-08-29T09:49:32-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.153' is now responding
2013-08-29T09:52:20-07:00 L3 sdb[305]: Wi-Fi: 8c:58:77:3f:9e:1f re-joined ATT184 after 30 d 16 h 5 m 32 seconds
2013-08-29T09:52:20-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 1
2013-08-29T09:52:22-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.153'
2013-08-29T09:52:22-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.153' is now responding
2013-08-29T09:55:58-07:00 L3 sdb[305]: Wi-Fi: Client 8c:58:77:3f:9e:1f left ATT184
2013-08-29T09:55:58-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 0
2013-08-29T09:58:25-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.53'
2013-08-29T09:58:25-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.53' is now responding
2013-08-29T10:05:20-07:00 L3 sdb[305]: Wi-Fi: 8c:58:77:3f:9e:1f re-joined ATT184 after 30 d 16 h 9 m 22 seconds
2013-08-29T10:05:20-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 1
2013-08-29T10:05:38-07:00 L3 sdb[305]: Wi-Fi: Client 8c:58:77:3f:9e:1f left ATT184
2013-08-29T10:05:38-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 0
2013-08-29T10:07:36-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.53'
2013-08-29T10:07:36-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.53' is now responding
2013-08-29T10:08:08-07:00 L3 sdb[305]: Wi-Fi: 8c:58:77:3f:9e:1f re-joined ATT184 after 30 d 16 h 2 m 30 seconds
2013-08-29T10:08:08-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 1
2013-08-29T10:08:44-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.153'
2013-08-29T10:08:44-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.153' is now responding
2013-08-29T10:09:22-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.153'
2013-08-29T10:09:23-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.153' is now responding
2013-08-29T10:10:24-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.53'
2013-08-29T10:10:24-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.53' is now responding
2013-08-29T10:10:36-07:00 L3 sdb[305]: Wi-Fi: Intializing the subsystem
2013-08-29T10:10:36-07:00 L3 sdb[305]: Wi-Fi: Killing NAS daemon
2013-08-29T10:10:36-07:00 L3 sdb[305]: Wi-Fi: Killing EAPD daemon
2013-08-29T10:10:36-07:00 L3 sdb[305]: Wi-Fi: Setting country code to US
2013-08-29T10:10:36-07:00 L3 sdb[305]: Wi-Fi: Country code set to US/100000
2013-08-29T10:10:36-07:00 L3 sdb[305]: Wi-Fi: Starting autochannel scan...
2013-08-29T10:10:38-07:00 L3 sdb[305]: Wi-Fi: Autochannel found channel 1 on attempt 1
2013-08-29T10:10:38-07:00 L3 sdb[305]: Wi-Fi: EAPD daemon started
2013-08-29T10:10:38-07:00 L3 sdb[305]: Wi-Fi: NAS daemon started
2013-08-29T10:10:38-07:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2013-08-29T10:10:40-07:00 L3 sdb[305]: Wi-Fi: Client 8c:58:77:3f:9e:1f left ATT184
2013-08-29T10:10:40-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 0
2013-08-29T10:10:42-07:00 L3 sdb[305]: Wi-Fi: 8c:58:77:3f:9e:1f re-joined ATT184 after 30 d 16 h 0 m 2 seconds
2013-08-29T10:10:42-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 1
2013-08-29T10:11:00-07:00 L3 sdb[305]: Wi-Fi: Client 8c:58:77:3f:9e:1f left ATT184
2013-08-29T10:11:00-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 0
2013-08-29T10:16:24-07:00 L3 sdb[305]: Wi-Fi: 8c:58:77:3f:9e:1f re-joined ATT184 after 30 d 16 h 5 m 24 seconds
2013-08-29T10:16:24-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 1
2013-08-29T10:18:08-07:00 L3 sdb[305]: Wi-Fi: Client 8c:58:77:3f:9e:1f left ATT184
2013-08-29T10:18:08-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 0
2013-08-29T10:19:34-07:00 L3 dnsmasq[2465]: no responses from nameserver '99.99.99.53'
2013-08-29T10:19:35-07:00 L3 dnsmasq[2465]: nameserver '99.99.99.53' is now responding
2013-08-29T10:20:00-07:00 L3 sdb[305]: Wi-Fi: 8c:58:77:3f:9e:1f re-joined ATT184 after 30 d 16 h 1 m 52 seconds
2013-08-29T10:20:00-07:00 L3 sdb[305]: Wi-Fi: Number of clients associated 1


whamel
billhamel .net
Premium
join:2002-05-09
Hinsdale, IL
kudos:10
Reviews:
·Verizon Broadban..
·AT&T U-Verse
·Comcast
reply to memlaneinc
You are using regular DSL, well ADSL2+. It is not a U-Verse product, and you posted in the U-Verse forum. However I will help out a bit, as much as I can.
I noticed that what's really happening is that your modem is having trouble with DNS resolution. It seems to not be able to connect to the DNS servers assigned to you ASIN ATT184.
Here is a helpful article on this modem and its problems, specifically it talks about this problem.
»www.networkworld.com/columnists/···282.html
--
Bill - Hinsdale, IL - »www.billhamel.net


mackey
Premium
join:2007-08-20
kudos:12
said by whamel:

You are using regular DSL, well ADSL2+. It is not a U-Verse product

Wrong. ADSL2+, aka IPDSLAM, is very much a Uverse product. My guesstimate puts it at somewhere between 1/3 and 1/2 of all Uverse installs. In case you didn't know, there's also a (very rare) FTTP version of Uverse as well.

/M


whamel
billhamel .net
Premium
join:2002-05-09
Hinsdale, IL
kudos:10
Reviews:
·Verizon Broadban..
·AT&T U-Verse
·Comcast
said by mackey:

said by whamel:

You are using regular DSL, well ADSL2+. It is not a U-Verse product

Wrong. ADSL2+, aka IPDSLAM, is very much a Uverse product. My guesstimate puts it at somewhere between 1/3 and 1/2 of all Uverse installs. In case you didn't know, there's also a (very rare) FTTP version of Uverse as well.
/M

Well I just learned that! I was assuming U-Verse was a VDSL2+ demodulation. Since that's what I use. And yea, i've heard of the rare FTTP version before...
--
Bill - Hinsdale, IL - »www.billhamel.net

memlaneinc

join:2013-08-29
Tustin, CA
I have a Netgear WNDR4300 connected to the NVG510 Modem so the Netgear is the router that hands out the DNS through DHCP to all the clients. I believe it is something to deal with some type of interference at around 3am-5am in the morning that makes the modem go into a mode that you cannot access the internet unless you restart the NVG510 Modem. I added shielded cat5 cables to two of the devices that are plugged into the back of the netgear router thinking that might help the issue but it has not worked. There are still two more cables plugged into the back of the netgear that are not shielded. The internet works fine for the entire day, it is just in the morning when the internet is at a halt. Some days in the morning it tries to load a webpage and then the internet just stops and halts and I have to restart the modem and it works for the entire day with no interruptions.


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
reply to whamel
said by whamel:

Well I just learned that! I was assuming U-Verse was a VDSL2+ demodulation. Since that's what I use. And yea, i've heard of the rare FTTP version before...

A couple of salient differences between U-verse and legacy ADSL (and legacy ADSL2+ in the 9-state former Bellsouth region:

• Legacy ADSL/ADSL2+ uses an ATM backhaul while IPDSL (U-verse; ADSL2+/ADSL2+) uses a PTM backhaul.
• Legacy ADSL/ADSL2+ uses PPPoE authentication while IPDSL (U-verse; ADSL2+/ADSL2+) uses 802.1x authentication.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum


whamel
billhamel .net
Premium
join:2002-05-09
Hinsdale, IL
kudos:10
Reviews:
·Verizon Broadban..
·AT&T U-Verse
·Comcast
reply to memlaneinc
It's the modem, read that article. The modem has problems with DNS. Thats why internet won't work. When u reboot, it re-connects to the DNS....
--
Bill - Hinsdale, IL - »www.billhamel.net

COjosh

join:2011-02-21
kudos:1
It could still be outside trouble as well being that 3-7am is generally the coldest time of the night. If it is resistive trouble in the plant the problem will be more evident when the copper cools off, or when it is wet.

Her SNR is fairly low and her attenuation is indeed high...kind of...without knowing what her provisioned rate is.

To the OP- What speed are you paying for? Do you have any idea what your loop length is back to the CO? Is the service light out or red when you have to reboot or is the broadband light out or blinking? ...If the service light is out/red it could be the DNS problem Whamel is talking about....It would be useful getting into the broadband tab of the NVG510 when you are down to see if the DSL connection is still active when it's "Locked Up". If you are still physically connected, and not out of sync, Whamel hit the nail on the head.

To Whamel- Good catch on the DNS problem. But that issue could be coinciding with a potential plant problem as well. Reboots/Re-sync's will restore the connection to the DSLAM and therefore restore the connection to the POP and the DNS beyond.


brookeKrige

join:2012-11-05
San Jose, CA
kudos:3

1 edit
Netgear config: unclear, but suspect OP's point is it's already configured to by-pass use of NVG510 as DNS proxy. Rather it hands out real DNS servers to the DHCP clients?

+1 on likely line issue as well: If no line problem, you could restart NVG510 in the evening to retain connectivity thru the next morning. Use this site's Tools/smokeping to start a 3 day ping. Immediately start doing evening restarts every night. See if ping results show repeated wee hour drop offs, despite recent restarts every time: then post results here and in direct forum.

+1 on unclear how bad it gets: During issue, can you still ping/traceroute to numeric IP's (no DNS) without (for ping) large packet loss?

edit: How have you (OP) been doing modem restarts? Thru a reboot button on its web page, or physical button, or power cycle?


whamel
billhamel .net
Premium
join:2002-05-09
Hinsdale, IL
kudos:10
Reviews:
·Verizon Broadban..
·AT&T U-Verse
·Comcast
said by brookeKrige:

How do you restart modem? Thru a reboot button on its web page, or physical button, or power cycle?

You can through the "Diagnostics" tab I believe, if it's like the NVG589. Also there is a reset button on back.
--
Bill - Hinsdale, IL - »www.billhamel.net

memlaneinc

join:2013-08-29
Tustin, CA
reply to COjosh
I am not sure on the loop length is back to the CO. Is there a program that will tell me the loop length or do I have to have AT&T come out and take a look at it? The service light is not red. We have four steady green lights when we come in the morning and sometimes when we come in, the internet is very slow and then when we unplug the power cable from the device and replug back it in, the internet works fine for the rest of the day until 2:00am or so and then when my coworker comes in, he restarts the modem around 7:00am.

COjosh

join:2011-02-21
kudos:1
There isn't a "program" for you to use that would be able to tell you that. I was just curious in case you had an ATT tech out there who had mentioned your loop length.

It does sound more like a DNS issue now that you said the internet light isn't out and the broadband light isn't blinking. It's rare, but you can have outside copper trouble that can cause the modem to "lock up" and not respond even though all the necessary lights are lit.

I'm assuming that all the computers are behind the Netgear router? Try a computer/laptop going directly to the LAN ports on the modem, bypassing the 3rd party router for that one workstation, and use the smokeping utility from this site to try and isolate the issue.

Something must be going on with an IP lease or DNS server around the 3-7am time frame...

Do you have any computers/servers/etc. that run online backups during this time frame? Perhaps there are ARP requests flooding the DNS server from your end that is causing the DNS resolution to fail...I may have butchered that, I'm not a networking dude...

memlaneinc

join:2013-08-29
Tustin, CA
All of the computers are behind the Netgear Router. Where would I find the Smokeeping utility on this site? We do have a online backup that runs around 5:30pm but that is the only time during the day when the backup is being run. We had no problems with this scenario when we had the old AT&T DSL Modem with the router hooked up to it. Once we converted from DSL to UVERSE, that is when we started to have this issue.

COjosh

join:2011-02-21
kudos:1
reply to memlaneinc
Smokeping is found under the "Tools" tab at the top of the forum screen.

ATT DSL and Uverse apparently have, and use, different DNS servers. I'm not surprised that you were stable until the transition.

You know, this problem could also be just a plain-old bad NVG510 as well. I'm assuming that hasn't been swapped yet?

Run the utility for 24hrs and if the problem is as consistent as you say it WILL be evident on the results. If not, you have another internal network issue that we will need to delve into.

memlaneinc

join:2013-08-29
Tustin, CA
Actually this is our second NVG510 and we are having the same issues so that could be a red flag right there. In the meantime, I will download the smokeping utlitity and run it on a laptop.