PDA

View Full Version : 1:44 am modem disconnects (daily)


Kard
21-12-2008, 03:16
Since the 12th December, each and every day at 1:44am, my cable modem has reset, disconnecting me from my gaming server and generally making things awkward for me (i'm a night owl). I'm wondering if this is something others are experiencing or perhaps it's a fault my side.

The log, every time looks like this;


Sun Dec 21 01:44:41 2008 Sun Dec 21 01:44:41 2008 Information (7) The s/w filename specified in the config file is the same as ...
Sun Dec 21 01:44:41 2008 Sun Dec 21 01:44:41 2008 Information (7) A software upgrade filename was specified in the config file.
Sun Dec 21 01:44:41 2008 Sun Dec 21 01:44:41 2008 Information (7) Authorized
Sun Dec 21 01:44:41 2008 Sun Dec 21 01:44:41 2008 Information (7) Registration complete!
Sun Dec 21 01:44:41 2008 Sun Dec 21 01:44:41 2008 Information (7) We registered with a DOCSIS 1.0 config file!
Sun Dec 21 01:44:41 2008 Sun Dec 21 01:44:41 2008 Information (7) Received a REG-RSP message from the CMTS...
Sun Dec 21 01:44:41 2008 Sun Dec 21 01:44:41 2008 Information (7) Sending a REG-REQ to the CMTS...
Sun Dec 21 01:44:41 2008 Sun Dec 21 01:44:41 2008 Information (7) CableModem SNMP configure complete
Sun Dec 21 01:44:39 2008 Sun Dec 21 01:44:39 2008 Information (7) IP init completed ok
Sun Dec 21 01:44:39 2008 Sun Dec 21 01:44:39 2008 Information (7) CableModem TFTP init ok
Sun Dec 21 01:44:33 2008 Sun Dec 21 01:44:33 2008 Error (4) ToD request sent- No Response received
Sun Dec 21 01:44:33 2008 Sun Dec 21 01:44:33 2008 Information (7) CableModem DHCP client init ok
Sun Dec 21 01:44:33 2008 Sun Dec 21 01:44:33 2008 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Sun Dec 21 01:44:28 2008 Sun Dec 21 01:44:28 2008 Information (7) MAP w/initial maintenance region received
Sun Dec 21 01:44:28 2008 Sun Dec 21 01:44:28 2008 Information (7) Downstream sync ok
Sun Dec 21 01:44:28 2008 Sun Dec 21 01:44:28 2008 Information (7) MAP w/initial maintenance region received
Sun Dec 21 01:44:28 2008 Sun Dec 21 01:44:28 2008 Information (7) Beginning initial ranging...
Sun Dec 21 01:44:28 2008 Sun Dec 21 01:44:28 2008 Information (7) downstream time sync acquired...
Sun Dec 21 01:44:28 2008 Sun Dec 21 01:44:28 2008 Information (7) Downstream sync ok
Sun Dec 21 01:44:27 2008 Sun Dec 21 01:44:27 2008 Information (7) starting ds time sync acquisition...
Sun Dec 21 01:44:25 2008 Sun Dec 21 01:44:25 2008 Information (7) MAP w/initial maintenance region received
Sun Dec 21 01:44:24 2008 Sun Dec 21 01:44:24 2008 Information (7) Downstream sync ok
Sun Dec 21 01:44:24 2008 Sun Dec 21 01:44:24 2008 Information (7) Beginning initial ranging...
Sun Dec 21 01:44:24 2008 Sun Dec 21 01:44:24 2008 Information (7) downstream time sync acquired...
Sun Dec 21 01:44:24 2008 Sun Dec 21 01:44:24 2008 Information (7) Downstream sync ok
Sun Dec 21 01:44:23 2008 Sun Dec 21 01:44:23 2008 Information (7) starting ds time sync acquisition...
Sun Dec 21 01:44:19 2008 Sun Dec 21 01:44:19 2008 Information (7) MAP w/initial maintenance region received
Sun Dec 21 01:44:18 2008 Sun Dec 21 01:44:18 2008 Information (7) Downstream sync ok
Sun Dec 21 01:44:18 2008 Sun Dec 21 01:44:18 2008 Information (7) Beginning initial ranging...
Sun Dec 21 01:44:18 2008 Sun Dec 21 01:44:18 2008 Information (7) downstream time sync acquired...
Sun Dec 21 01:44:18 2008 Sun Dec 21 01:44:18 2008 Information (7) Downstream sync ok
Sun Dec 21 01:44:17 2008 Sun Dec 21 01:44:17 2008 Information (7) starting ds time sync acquisition...
Sadly the log doesn't really show anything other than the usual start sequence, and I'm guessing due to log limits it doesn't show what triggers the reset, but it's the same every night.

The reset is very fast, lasting only a few seconds (30 tops), but it's enough to cause havoc for the people i'm playing with at the moment because it disconnects me from all active services meaning my downtime is actually around 5 minutes (doesn't sound much, but for gaming it's a pain in the ass).

A call to the CS ended badly (Thursday), I couldn't understand a word the woman was saying and sadly I had a hard time explaining to her that my service was actually fine other than these modem resets, yet she insisted that I rebooted, did some kind of dance whilst balancing my keyboard and mouse on my little toe :p:

It's a 250 NTL branded modem, power/signal levels acceptable, UBR moderate overcrowding but nothing too serious.

Any advice would be appreciated.

CM20 User
21-12-2008, 14:02
Happens to me pretty much every night between 1am and 2:30am, sometimes I get a different IP so I have to reboot also.

Why it happens? I don't know but heres my log from last night anyway.

Sun Dec 21 01:47:12 2008 Sun Dec 21 01:47:12 2008 Information (7) The s/w filename specified in the config file is the same as ...
Sun Dec 21 01:47:12 2008 Sun Dec 21 01:47:12 2008 Information (7) A software upgrade filename was specified in the config file.
Sun Dec 21 01:47:12 2008 Sun Dec 21 01:47:12 2008 Information (7) Authorized
Sun Dec 21 01:47:12 2008 Sun Dec 21 01:47:12 2008 Information (7) Registration complete!
Sun Dec 21 01:47:12 2008 Sun Dec 21 01:47:12 2008 Information (7) We registered with a DOCSIS 1.0 config file!
Sun Dec 21 01:47:12 2008 Sun Dec 21 01:47:12 2008 Information (7) Received a REG-RSP message from the CMTS...
Sun Dec 21 01:47:12 2008 Sun Dec 21 01:47:12 2008 Information (7) Sending a REG-REQ to the CMTS...
Sun Dec 21 01:47:12 2008 Sun Dec 21 01:47:12 2008 Information (7) CableModem SNMP configure complete
Sun Dec 21 01:47:10 2008 Sun Dec 21 01:47:10 2008 Information (7) IP init completed ok
Sun Dec 21 01:47:10 2008 Sun Dec 21 01:47:10 2008 Information (7) CableModem TFTP init ok
Sun Dec 21 01:47:02 2008 Sun Dec 21 01:47:02 2008 Error (4) ToD request sent- No Response received
Sun Dec 21 01:47:02 2008 Sun Dec 21 01:47:02 2008 Information (7) CableModem DHCP client init ok
Sun Dec 21 01:47:02 2008 Sun Dec 21 01:47:02 2008 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Sun Dec 21 01:46:55 2008 Sun Dec 21 01:46:55 2008 Information (7) MAP w/initial maintenance region received
Sun Dec 21 01:46:54 2008 Sun Dec 21 01:46:54 2008 Information (7) Downstream sync ok
Sun Dec 21 01:46:54 2008 Sun Dec 21 01:46:54 2008 Information (7) MAP w/initial maintenance region received
Sun Dec 21 01:46:54 2008 Sun Dec 21 01:46:54 2008 Information (7) Beginning initial ranging...
Sun Dec 21 01:46:54 2008 Sun Dec 21 01:46:54 2008 Information (7) downstream time sync acquired...
Sun Dec 21 01:46:54 2008 Sun Dec 21 01:46:54 2008 Information (7) Downstream sync ok
Sun Dec 21 01:46:54 2008 Sun Dec 21 01:46:54 2008 Information (7) starting ds time sync acquisition...
Sun Dec 21 01:46:50 2008 Sun Dec 21 01:46:50 2008 Information (7) MAP w/initial maintenance region received
Sun Dec 21 01:46:48 2008 Sun Dec 21 01:46:48 2008 Information (7) Downstream sync ok
Sun Dec 21 01:46:48 2008 Sun Dec 21 01:46:48 2008 Information (7) Beginning initial ranging...
Sun Dec 21 01:46:48 2008 Sun Dec 21 01:46:48 2008 Information (7) downstream time sync acquired...
Sun Dec 21 01:46:48 2008 Sun Dec 21 01:46:48 2008 Information (7) Downstream sync ok
Sun Dec 21 01:46:48 2008 Sun Dec 21 01:46:48 2008 Information (7) starting ds time sync acquisition...
Sun Dec 21 01:46:45 2008 Sun Dec 21 01:46:45 2008 Information (7) Locked on the downstream. Waiting for UCDs...
Sun Dec 21 01:46:45 2008 Sun Dec 21 01:46:45 2008 Information (7) Downstream lock ok
Sun Dec 21 01:46:40 2008 Sun Dec 21 01:46:40 2008 Information (7) MAP w/initial maintenance region received
Sun Dec 21 01:46:38 2008 Sun Dec 21 01:46:38 2008 Information (7) Downstream sync ok
Sun Dec 21 01:46:38 2008 Sun Dec 21 01:46:38 2008 Information (7) Beginning initial ranging...
Sun Dec 21 01:46:38 2008 Sun Dec 21 01:46:38 2008 Information (7) downstream time sync acquired...

confucious
21-12-2008, 14:49
Sorry no idea but just wanted to say I nearly had a heart attack when I saw the titel to your thread as I saw 144 and modem and thought someone was still using a 14400 modem.....


:dunce:

Traduk
21-12-2008, 15:17
As it started on the 12th of Dec it will not as it is cable be this problem but maybe something Christmas oriented. ADSL was found to be knocked off line by close proximity to certain types of flashing Christmas lights.

The problem was radio frequency interference and although co-axial is less affected I wouldn't mind betting the something switches on or off at 01.44 (on an electronic timer) and knocks your modem off line.

RF problems can have a wide area of travel. We had an situation on our estate whereby several car alarms malfunctioned. Somebody went round all 50 houses and found that the affected number of vehicles was 15. Fortunately somebody with access to a RF tester located the source and it was a kiddies plastic computer game motorbike which was connected to a computer and left switched on and thereby constantly pulsing an RF signal. The furthest affected house was a 100 metres from the source.

My BIL can use his electronic garage door opener Mon to Fri but never at weekends. Nobody has found the blocking cause even after a year of trying.

Kard
23-12-2008, 03:04
Caught it in action tonight, last night the reset was at 1:51am, so tonight I refreshed the log every 30 seconds from 1:44 onwards (yeah it bugs me that much).

The log entry for the reset (no power surge, no external RF, no aliens <-- my young son's suggestion :erm:);

Tue Dec 23 01:50:52 2008 Tue Dec 23 01:50:52 2008 Information (7) Reset downstream scanning state!

After the reboot the log is filled with the usual boot information and this line is lost. I'm still at a loss to why this happens, i'll make a thread on the support newsgroup. :dunce:

pabscars
23-12-2008, 14:36
i have no idea whats causing your problem, but thinking what could be switching on or off at that time, could it be your central heating boiler, water pump for radiators, immersion heater etc, just a wild stab in the dark i know.

Milambar
23-12-2008, 16:11
LOL, sorry but I think the people here are using the famous BOFH excuses calendar (http://bofh.ntk.net/*******3.html).

Personally, I think that more likely its some kind of scheduled task being run every night at the head-end of the cable that causes a hiccup, and he should really be talking to the technicians via technical support or via the newsgroup.

And the url I posted won't work because the swearword filter filters it (it contains a swearword, don't blame me, blame Simon Travaglia, the original BOFH who maintains that site), so just search for "BOFH excuses calendar".

gc7
23-12-2008, 16:32
I had the same problem, everynight, about the same time as you but it only lasted for a week. I used to check the modem config every day. Although it has now stopped on a nightly basis, it does still happen but only on Sunday mornings the last one on Sun Dec 21 01:37:40 2008.

I just put it down to VM doing work and the modem just resetting after VM rebooting something at their end.

I've never experienced any problems after this has happened so have never reported it, although I doubt that I'd get a explanation I could understand.

I'm not a technician so can't offer any advice, my internet speed is the same as it always has so I won't do anything just yet.