Help interpreting NVG510 logs

Tutor

Help interpreting NVG510 logs

Hi,

 

I recently (5/16/2013) began service with AT&T U-Verse (DSL only).  I resisted AT&T for the longest time, but now that I'm here I have to admit it's been a pretty good experience - even fantastic in some respects.

 

Anyways, I've been monitoring the logs in the NVG510 and I see some recurring messages.  Can someone interpret or explain what is going on in these situations?

 

I have a business U-Verse account with 5 (or 8?) static ip addresses.  My network consists of the NVG510 and a Netgear WNR2000 router behind it that has one of the public static ip addresses.  I haven't "forced" the NVG510 into a bridge type mode and the Netgear handles DNS and WLAN for the private network.

 

There are some other little issues with the service but I want to see if I can get answers to these questions first before bringing up other stuff.

 

Situation 1

 

JUNE 4, 1:56AM

2013-06-04T01:56:54-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2013-06-04T01:57:11-04:00 L3 sdb[305]: DSL: Filters may be missing: No
2013-06-04T01:57:11-04:00 L3 sdb[305]: DSL: Echo level: 0 dB
2013-06-04T01:57:11-04:00 L3 sdb[305]: DSL: Affected tones: 21
2013-06-04T01:57:17-04:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2
2013-06-04T01:57:35-04:00 L3 sdb[305]: DSL: Filters may be missing: No
2013-06-04T01:57:35-04:00 L3 sdb[305]: DSL: Echo level: 0 dB
2013-06-04T01:57:35-04:00 L3 sdb[305]: DSL: Affected tones: 26
2013-06-04T01:57:41-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
2013-06-04T01:57:41-04:00 L3 sdb[305]: DSL: Mode ADSL2+ (PTM)
2013-06-04T01:57:41-04:00 L3 sdb[305]: DSL: Sync Rate in kbps D/S 11996 U/S 1020
2013-06-04T01:57:41-04:00 L3 sdb[305]: DSL: Latency path Interleaved
2013-06-04T01:57:41-04:00 L3 sdb[305]: DSL: Trellis D/SSmiley SurprisedN U/SSmiley SurprisedN
2013-06-04T01:57:41-04:00 L3 sdb[305]: DSL: CO Vendor BDCM
2013-06-04T01:57:41-04:00 L3 sdb[305]: DSL: Link showtime counter since boot 5
2013-06-04T01:57:42-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
2013-06-04T01:57:42-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2013-06-04T01:57:42-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
The last message was repeated 2 times.
2013-06-04T01:57:45-04:00 L5 supp1x[1307]: Sending START Packet
2013-06-04T01:57:48-04:00 L5 supp1x[1307]: Supplicant event = SUCCESS
2013-06-04T01:57:49-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
The last message was repeated 2 times.

 

Situation 2

 

JUNE 4, 3:09AM

2013-06-04T03:09:56-04:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x1 RDI Detector
2013-06-04T03:09:57-04:00 L3 sdb[305]: DSL: Link drop counter since boot 5
2013-06-04T03:09:57-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
2013-06-04T03:09:57-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2013-06-04T03:09:57-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
The last message was repeated 2 times.
2013-06-04T03:09:58-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2013-06-04T03:09:58-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
The last message was repeated 3 times.
2013-06-04T03:09:58-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2013-06-04T03:10:15-04:00 L3 sdb[305]: DSL: Filters may be missing: No
2013-06-04T03:10:15-04:00 L3 sdb[305]: DSL: Echo level: 0 dB
2013-06-04T03:10:15-04:00 L3 sdb[305]: DSL: Affected tones: 26
2013-06-04T03:10:21-04:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2
2013-06-04T03:10:39-04:00 L3 sdb[305]: DSL: Filters may be missing: No
2013-06-04T03:10:39-04:00 L3 sdb[305]: DSL: Echo level: 0 dB
2013-06-04T03:10:39-04:00 L3 sdb[305]: DSL: Affected tones: 27
2013-06-04T03:10:45-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
2013-06-04T03:10:45-04:00 L3 sdb[305]: DSL: Mode ADSL2+ (PTM)
2013-06-04T03:10:45-04:00 L3 sdb[305]: DSL: Sync Rate in kbps D/S 11996 U/S 1020
2013-06-04T03:10:45-04:00 L3 sdb[305]: DSL: Latency path Interleaved
2013-06-04T03:10:45-04:00 L3 sdb[305]: DSL: Trellis D/SSmiley SurprisedN U/SSmiley SurprisedN
2013-06-04T03:10:45-04:00 L3 sdb[305]: DSL: CO Vendor BDCM
2013-06-04T03:10:45-04:00 L3 sdb[305]: DSL: Link showtime counter since boot 6
2013-06-04T03:10:46-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
2013-06-04T03:10:46-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2013-06-04T03:10:46-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
The last message was repeated 2 times.
2013-06-04T03:10:50-04:00 L5 supp1x[1307]: Sending START Packet
2013-06-04T03:10:53-04:00 L5 supp1x[1307]: Supplicant event = SUCCESS
2013-06-04T03:10:53-04:00 L1 sdb[305]: nm_ipv6_add_firewall: <sit1> (4)
The last message was repeated 2 times.

 

These two situations are happening several times a night between like 2am-5am.

 

Situation 3

 

JUNE 4, 7:20AM

2013-06-04T07:20:44-04:00 L5 cwmp[1370]: Next Periodic Inform after 86400 s
2013-06-04T07:20:44-04:00 L4 cwmp[1370]: Resolving ACS URL - Retry 0
2013-06-04T07:20:44-04:00 L5 cwmp[1370]: Connect to https://cwmp.c01.sbcglobal.net/cwmp/services/CWMP [144.160.14.12:443] Retry 0
2013-06-04T07:20:44-04:00 L5 cwmp[1370]: (SSL) Connect Success: cwmp.c01.sbcglobal.net
2013-06-04T07:20:44-04:00 L5 cwmp[1370]: (SSL) Certificate Verify Success: cwmp.c01.sbcglobal.net
2013-06-04T07:20:44-04:00 L5 cwmp[1370]: Post Inform - reason 2 PERIODIC
2013-06-04T07:20:45-04:00 L5 cwmp[1370]: Receive InformResponse
2013-06-04T07:20:45-04:00 L5 cwmp[1370]: Post 0
2013-06-04T07:20:45-04:00 L5 cwmp[1370]: Closing connection on HTTP 204
2013-06-04T07:20:45-04:00 L5 cwmp[1370]: (SSL) Closing Connection: cwmp.c01.sbcglobal.net

 

This message looks like some kind of routine check-in of the NVG510 with the upstream network?

Message 1 of 5 (10,577 Views)
Expert
Solution
Accepted by SomeJoe7777 (Expert)
‎09-30-2015 1:39 AM

Re: Help interpreting NVG510 logs

All of those messages look normal. AT&T does maintenance in the early morning hours, and a reboot or retrain of your modem and/or the DSLAM can occur.

The 3rd message means that the modem is contacting the AT&T central management network. All modems on the AT&T consumer network are managed and can be remotely controlled by AT&T.
Message 2 of 5 (10,532 Views)
Highlighted
Tutor

Re: Help interpreting NVG510 logs

Thank you!

Message 3 of 5 (10,522 Views)
Employee

Re: Help interpreting NVG510 logs

[ Edited ]

As for the IP address range, suppose you buy a range of eight addresses, That gives you five usable addresses, plus base, broadcast, and an address allocated to the router itself.

Employee Contributor*
*I am an AT&T employee and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.
Message 4 of 5 (10,330 Views)

Re: Help interpreting NVG510 logs

The RDI is Remote Defect Indicator, and in my experience (all three  weeks) it triggers a drop of the link and a retrain. In my case, it has a strong correlation  with sudden drops in the s/n margin. I have seen it mostly mid day and around midnight but a few weeks ago, when it rained, it was occuring up to six times a day. I have been trying to determine if there is any more information about the RDI, say by lowering the loglevel, but until I modify the  monitoring program I'm using to use persistent connection, that program produces an overwhelming amount of noise in the log.

 

I've also noticed that the two sets of DSL Echo Level and Affected Tones entries are around 20 seconds apart. For the time being, my SWAG is that it's two time delay samples to determine an adjustment (bit swapping ?). As a work in progress, I'm only at the point of guessing  that Echo Level has to do with VoIP Echo, and that  Affected Tones might be the number of degraded channels (in the downstream?) - I don't see any log entry information in the modem manual.

Message 5 of 5 (9,893 Views)
Share this topic
Announcements

Welcome to the AT&T Community Forums!!! Stop by the Community How-To section for tips on how to get started.