ACE - Guru
•
953 Messages
NVG589 Log file errors
I see this has been discussed a number of times before.
Arris and AT&T have ideas what's causing the issue but nobody is coming up with a solution.
It's not only the log file filling up so quickly it's also the odd freezes when trying to browse or receive emails. When it works it works very well, getting consistent 29Mb/s speeds.
This problem started when I was upgraded from Bpon to Gpon in December. AT&T say it's a NVG589 firmware issue and ARRIS say it's AT&T's problem. So, AT&T, when can we expect a solution?
Here is an extract of the log file
2015-02-02T12:30:25-08:00 L4 cwmp[1524]: Continue GetParameterValuesResponse (chunk-length - 0) 2015-02-02T12:30:25-08:00 L5 cwmp[1524]: Closing connection on HTTP 204 2015-02-02T12:30:25-08:00 L5 cwmp[1524]: (SSL) Closing Connection: cwmp.c01.sbcglobal.net 2015-02-02T12:37:20-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T12:37:20-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T12:43:18-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership 2015-02-02T12:43:18-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF 2015-02-02T12:43:31-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T12:43:31-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T12:51:22-08:00 L3 sdb[333]: ELAN: Port lan-4 (eth3) is DOWN 2015-02-02T12:53:13-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T12:53:13-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17 2015-02-02T12:58:02-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T12:58:02-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T12:59:01-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership 2015-02-02T12:59:01-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF 2015-02-02T13:08:58-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T13:08:58-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17 2015-02-02T13:13:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T13:13:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T13:14:48-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership 2015-02-02T13:14:48-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF 2015-02-02T13:24:43-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T13:24:43-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T13:24:47-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T13:24:47-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17 2015-02-02T13:28:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T13:28:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T13:30:36-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership 2015-02-02T13:30:36-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF 2015-02-02T13:40:32-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T13:40:32-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T13:43:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T13:43:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T13:46:24-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership 2015-02-02T13:46:24-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF 2015-02-02T13:56:19-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T13:56:19-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T13:56:21-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T13:56:21-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17 2015-02-02T13:58:20-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T13:58:20-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T14:02:25-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership 2015-02-02T14:02:25-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF 2015-02-02T14:12:15-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T14:12:15-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T14:18:03-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T14:18:03-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T14:18:08-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership 2015-02-02T14:18:08-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF 2015-02-02T14:28:06-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T14:28:06-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17 2015-02-02T14:33:04-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T14:33:04-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T14:33:54-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership 2015-02-02T14:33:54-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF 2015-02-02T14:43:50-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T14:43:50-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T14:43:56-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T14:43:56-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17 2015-02-02T14:48:02-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T14:48:02-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T14:49:42-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership 2015-02-02T14:49:42-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF 2015-02-02T14:51:15-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T14:51:15-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T14:59:40-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T14:59:40-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T15:03:25-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:03:25-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T15:15:24-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:15:24-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T15:18:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:18:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T15:29:52-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:29:52-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T15:29:56-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:29:56-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T15:31:08-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.53' 2015-02-02T15:31:08-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.53' is now responding 2015-02-02T15:31:12-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:31:12-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T15:31:16-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:31:16-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17 2015-02-02T15:33:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:33:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T15:46:59-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:46:59-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T15:48:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:48:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 15 2015-02-02T15:50:39-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.153' 2015-02-02T15:50:40-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.153' is now responding 2015-02-02T15:53:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:53:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12 2015-02-02T15:55:56-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.53' 2015-02-02T15:55:56-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.53' is now responding 2015-02-02T15:55:59-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T15:55:59-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T15:57:08-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.153' 2015-02-02T15:57:08-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.153' is now responding 2015-02-02T16:03:22-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.53' 2015-02-02T16:03:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T16:03:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T16:03:27-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.153' is now responding 2015-02-02T16:03:40-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5 2015-02-02T16:03:40-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16 2015-02-02T16:09:23-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.153' 2015-02-02T16:09:23-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.153' is now responding 2015-02-02T16:10:26-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.53' 2015-02-02T16:10:28-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.53' is now responding
Award for Community Excellence 2021 Achiever*
*I am not an AT&T employee, and the views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
*I am not an AT&T employee, and the views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
I just noticed that if ipv6 is on then the dns settings on the 589 are set to 99.99.xx.xx and if ipv6 is off then the dns is set to 68.94.xx.xx.
This does not change the nameserver stop/start issues I am having but may explain why turning off ipv6 works for some of you.
0
0
MadisonAL
Mentor
•
68 Messages
8 years ago
The tech has requested the port swap, but so far, not action. He says that it is in the queue.
In the meantime, I have removed the loop from the Data Cable. The extraneous cable length now runs back and forth behind my desk and the errors have significantly reduced. Even with regular phone cord, using only one of the paired DSL lines, yielded better service during my testing.
If you have a coil within the Data Cable, get rid of it!
My log file is now boring. The TV does not freeze, the dsname no responding occurs maybe once per day.
The bad name at /var/etc/hosts.dyn line messages only occur when my laptop joins or leaves the network, either wireless or ethernet. The message, mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership, occurs when I leave the network from my laptop.
0
0
MadisonAL
Mentor
•
68 Messages
8 years ago
Hi Joel,
Those are not log errors, but rather are log entries for AT&T running diagnostics on your line. The "next periodic inform" indicates this is set to run automatically. The "Connect" is AT&T connecting to your gateway/router.
The AT&T NVG589 comes with a "data cable" of extensive length. Often, the excess length is formed into a coil for neatness. If that is the case, remove the coil and extend the cable. This worked for me and has significantly reduced the amount of errors. In fact, if you replace the "data cable" with a short telephone line, you may find improved service though only usiing one of the DSL lines.
I am still getting "mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership" either two or three times per day, but internet and TV service have been relatively consistent.
Barry
0
0
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
Hi Barry,
Thanks for the update.
Except for the
mcp[1038]: mcp[handle_timers]: group (0xE00000FB) has stale rep/src entries C0A801E5 00000000 0000BEEF
I have eliminated all errors on my setup. I have FTTH not bonded pair so don't have the telephone data cable you refer to, mine is an Ethernet cable coming in from the outside.
My fix was to put my second wifi access point on a separate ip range (10.0.0.0) and connect it's internet port to an Ethernet port on the RG. DNS servers on the Netgear are set to 8.8.8.8 and 8.8.4.4
So I now use the wifi from the RG for upstairs and the wifi from the Netgear AP downstairs.
Solid signals almost all of the time specially when using the 5ghz wifi from the Netgear.
The only downside is that the two networks don't see each other but that's not a requirement in my setup.
0
0
MrsKryten
Mentor
•
34 Messages
8 years ago
Disabling IPv6 seems to have taken care of the numerous "bad name" messages in my log. It's too soon to see if it resolves the rebooting issue but it sounds like those two issues are connected so fingers crossed that it resolves my rebooting problem as well.
0
0
stevep65
Tutor
•
2 Messages
8 years ago
Per the advice here I disabled IPv6 on the router and my intermittent connection issues have disappeared. Hopefully there will be a permanent fix soon.
0
0
DarkFury
Tutor
•
6 Messages
8 years ago
Is there any special kind of "data cable" in use here... or is it just basic telephone cord cable? I'm thinking of buying a shorter version of the cable ... since recently a tech was at my house and replaced my connector and now I'm getting the mcp[handle_timers]: group (0xEF800164) timer expired - dropping membership error messages. (I wasn't getting them before).
I do in fact see that he looped the data cable... so wouldn't it be smarter to just use a shorter cable? Thanks in advance for any advice on this.
0
0
MadisonAL
Mentor
•
68 Messages
8 years ago
The data cable consists of two phone lines. However, using a shorter phone line reduced my errors without degradation of service. However, I put back the AT&T provided cable and have the wire running back and forth, one time, between the jack and the NVG589. I continue to get dropping membership messages, about twice per day and an occasional DNS server response issue.
One day, I may either look for a shorter cable or see if I can get AT&T to provide one.
0
0
aviewer
Expert
•
10.1K Messages
8 years ago
I believe the cable in question is a "data grade"cable. But it does have uniqueness.
I believe the cable has construction of a cat5 cable or close to it.
But a cat5 cable has rj-45 ends (more pairs)
The cable in question has rj-11 ends - same as a tel jack/line.
It is hard to find a "data grade" cable with RJ-11 ends.
An Rj-11 end does fit & click into an RJ-45 jack. Since the pairs are assigned from the middle out, it works.
I guess you can always change the wall jack from RJ-11 to RJ-45.
Is the RG jack RJ-45 or is there an RJ-45 on the RG that works?
Google RJ-11 & RJ-45 for images of connection to the cable.
0
0
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
See here
{commercial link removed}
0
0