Send Light Not Flickering As Much As It Used To When PC is Off. [Archive]

View Full Version : Send Light Not Flickering As Much As It Used To When PC is Off.

VMboy

04-12-2009, 16:23

graf_von_anonym

04-12-2009, 18:22

Honestly?

The send light will usually flash when the modem is passing data upstream, presumably (when your PC is off) when it's requested by the UBR. It might not be requesting as much, but to my knowledge there's no firmware update that's been pushed out or anything.

You'd be better off not worrying about it and having a cup of tea.

VMboy

04-12-2009, 19:01

Honestly?
You'd be better off not worrying about it and having a cup of tea.

I ain't worrying about it, just thought why the change of symptoms that's all.

darren.b

04-12-2009, 21:59

Has there been a modem software update for the Ambit 256?

I ask as normally my send light flickers continuously when the computer is off, but today it doesn't flicker much at all, I'm not saying it has stopped flickering, just that it isn't as bad as it used to be and thought that there must have been some kind of software update for this and or other modems.

That happened to mine after I was shunted from DOCSIS 1 to DOCSIS 1.1. If this has happened to you, you'll have other headaches to worry about soon enough :P

VMboy

04-12-2009, 22:05

That happened to mine after I was shunted from DOCSIS 1 to DOCSIS 1.1. If this has happened to you, you'll have other headaches to worry about soon enough :P

How will I know if this has happened to me?

What other headaches come from this can you tell me please?

Can I tell which version I have, and is it on Cable Modem Information, if so mine says Cable Modem : DOCSIS 1.0/1.1/2.0 Compliant

musicbravo

04-12-2009, 22:15

in your lof dilw on the modem it will say registered with docsis 1.0 or docsis 1.1

VMboy

04-12-2009, 22:24

in your lof dilw on the modem it will say registered with docsis 1.0 or docsis 1.1

What is lof dilw??

Anyway I have just checked the Cable Modem Event Log, and it says the following....

Wed Dec 02 20:07:15 2009 Wed Dec 02 20:07:15 2009 Information (7) The s/w filename specified in the config file is the same as ...
Wed Dec 02 20:07:15 2009 Wed Dec 02 20:07:15 2009 Information (7) A software upgrade filename was specified in the config file.
Wed Dec 02 20:07:15 2009 Wed Dec 02 20:07:15 2009 Information (7) Authorized
Wed Dec 02 20:07:15 2009 Wed Dec 02 20:07:15 2009 Information (7) Registration complete!
Wed Dec 02 20:07:14 2009 Wed Dec 02 20:07:14 2009 Information (7) We registered with a DOCSIS 1.0 config file!
Wed Dec 02 20:07:14 2009 Wed Dec 02 20:07:14 2009 Information (7) Received a REG-RSP message from the CMTS...
Wed Dec 02 20:07:14 2009 Wed Dec 02 20:07:14 2009 Information (7) Sending a REG-REQ to the CMTS...
Wed Dec 02 20:07:14 2009 Wed Dec 02 20:07:14 2009 Information (7) CableModem SNMP configure complete
Wed Dec 02 20:07:14 2009 Wed Dec 02 20:07:14 2009 Information (7) IP init completed ok
Wed Dec 02 20:07:14 2009 Wed Dec 02 20:07:14 2009 Information (7) CableModem TFTP init ok
Wed Dec 02 20:07:14 2009 Wed Dec 02 20:07:14 2009 Information (7) CableModem DHCP client init ok
Wed Dec 02 20:07:14 2009 Wed Dec 02 20:07:14 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.

---------- Post added at 22:24 ---------- Previous post was at 22:22 ----------

So it looks like there was indeed a software upgrade, and it's no coincidence that the send light has changed since the upgrade.

darren.b

04-12-2009, 22:29

How will I know if this has happened to me?

What other headaches come from this can you tell me please?

Can I tell which version I have, and is it on Cable Modem Information, if so mine says Cable Modem : DOCSIS 1.0/1.1/2.0 Compliant
Well since I was moved to 1.1, I have seen hundreds of sync errors in the logs, usually every hour. After about 48 continuous hours of this the modem just gives up and dies. The ready LED sometimes flashes, sometimes it doesn't. Either way there is no network, no access to the modem itself via http://192.168.100.1/ and the only remedy is a power cycle of the modem. My friend over in Holland has similar issues, only his modem automatically reboots. The VM ones just roll over on their backs, legs up in the air and do nothing.

Latest software version...

Cable Modem : Euro-DOCSIS 1.0/1.1/2.0 Compliant
MAC Address : hah!
Serial Number : hah!
Boot Code Version : 1.1.2c
Software Version : 2.111.1002 <<<< as far as I can tell this fixed the display bugs..ie your max bit rates are no longer both 0 but it doesn't make the modem reboot upon a loss of sync or stop it from giving up after 48 hours.
Hardware Version : 1.9

Peter_

04-12-2009, 22:38

Well since I was moved to 1.1, I have seen hundreds of sync errors in the logs, usually every hour. After about 48 continuous hours of this the modem just gives up and dies. The ready LED sometimes flashes, sometimes it doesn't. Either way there is no network, no access to the modem itself via http://192.168.100.1/ and the only remedy is a power cycle of the modem. My friend over in Holland has similar issues, only his modem automatically reboots. The VM ones just roll over on their backs, legs up in the air and do nothing.

Latest software version...

Cable Modem : Euro-DOCSIS 1.0/1.1/2.0 Compliant
MAC Address : hah!
Serial Number : hah!
Boot Code Version : 1.1.2c
Software Version : 2.111.1002 <<<< as far as I can tell this fixed the display bugs..ie your max bit rates are no longer both 0 but it doesn't make the modem reboot upon a loss of sync or stop it from giving up after 48 hours.
Hardware Version : 1.9
I have an Ambit 256 the same as you and mine never reboots and it has the same versions as posted above, it should not fail after 48 hours.

Go to the event log does it have this "We registered with a DOCSIS 1.0 config file!"

If you are having the issues you state then the is a fault local to you that you need to call in about.

VMboy

04-12-2009, 22:45

The ready LED sometimes flashes, sometimes it doesn't.

Let me just say that if your ready light is flashing in any way then you won't have the use of the modem until the light is steady.

darren.b

04-12-2009, 22:48

Moldova,

My modem logs fill up with this all the time so I have to reboot to get the config file jobby...

Fri Dec 04 22:17:45 2009 Fri Dec 04 22:17:45 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:45 2009 Fri Dec 04 22:17:45 2009 Information (7) locked and synced to rescue CMTS...all is well!
Fri Dec 04 22:17:45 2009 Fri Dec 04 22:17:45 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:45 2009 Fri Dec 04 22:17:45 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Fri Dec 04 22:17:45 2009 Fri Dec 04 22:17:45 2009 Information (7) Downstream sync failed
Fri Dec 04 22:17:33 2009 Fri Dec 04 22:17:33 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:33 2009 Fri Dec 04 22:17:33 2009 Information (7) locked and synced to rescue CMTS...all is well!
Fri Dec 04 22:17:33 2009 Fri Dec 04 22:17:33 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:33 2009 Fri Dec 04 22:17:33 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Fri Dec 04 22:17:33 2009 Fri Dec 04 22:17:33 2009 Information (7) Downstream sync failed
Fri Dec 04 22:17:32 2009 Fri Dec 04 22:17:32 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:32 2009 Fri Dec 04 22:17:32 2009 Information (7) locked and synced to rescue CMTS...all is well!
Fri Dec 04 22:17:32 2009 Fri Dec 04 22:17:32 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:32 2009 Fri Dec 04 22:17:32 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Fri Dec 04 22:17:32 2009 Fri Dec 04 22:17:32 2009 Information (7) Downstream sync failed
Fri Dec 04 22:17:28 2009 Fri Dec 04 22:17:28 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:28 2009 Fri Dec 04 22:17:28 2009 Information (7) locked and synced to rescue CMTS...all is well!
Fri Dec 04 22:17:28 2009 Fri Dec 04 22:17:28 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:28 2009 Fri Dec 04 22:17:28 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Fri Dec 04 22:17:28 2009 Fri Dec 04 22:17:28 2009 Information (7) Downstream sync failed
Fri Dec 04 22:17:28 2009 Fri Dec 04 22:17:28 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:28 2009 Fri Dec 04 22:17:28 2009 Information (7) locked and synced to rescue CMTS...all is well!
Fri Dec 04 22:17:28 2009 Fri Dec 04 22:17:28 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:27 2009 Fri Dec 04 22:17:27 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Fri Dec 04 22:17:27 2009 Fri Dec 04 22:17:27 2009 Information (7) Downstream sync failed
Fri Dec 04 22:17:27 2009 Fri Dec 04 22:17:27 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:27 2009 Fri Dec 04 22:17:27 2009 Information (7) locked and synced to rescue CMTS...all is well!
Fri Dec 04 22:17:27 2009 Fri Dec 04 22:17:27 2009 Information (7) Downstream sync ok
Fri Dec 04 22:17:26 2009 Fri Dec 04 22:17:26 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Fri Dec 04 22:17:26 2009 Fri Dec 04 22:17:26 2009 Information (7) Downstream sync failed
Fri Dec 04 22:16:08 2009 Fri Dec 04 22:16:08 2009 Information (7) Downstream sync ok
Fri Dec 04 22:16:08 2009 Fri Dec 04 22:16:08 2009 Information (7) locked and synced to rescue CMTS...all is well!

OK, after a reboot...

Fri Dec 04 22:45:06 2009 Fri Dec 04 22:45:06 2009 Information (7) DCC arrive new
Fri Dec 04 22:45:05 2009 Fri Dec 04 22:45:05 2009 Information (7) Locked on the downstream. Waiting for UCDs...
Fri Dec 04 22:45:05 2009 Fri Dec 04 22:45:05 2009 Information (7) Downstream lock ok
Fri Dec 04 22:45:04 2009 Fri Dec 04 22:45:04 2009 Information (7) DCC depart old
Fri Dec 04 22:45:04 2009 Fri Dec 04 22:45:04 2009 Information (7) Received DCC-REQ message...
Fri Dec 04 22:45:00 2009 Fri Dec 04 22:45:00 2009 Information (7) The s/w filename specified in the config file is the same as ...
Fri Dec 04 22:45:00 2009 Fri Dec 04 22:45:00 2009 Information (7) A software upgrade filename was specified in the config file.
Fri Dec 04 22:44:59 2009 Fri Dec 04 22:44:59 2009 Information (7) Authorized
Fri Dec 04 22:44:59 2009 Fri Dec 04 22:44:59 2009 Information (7) Registration complete!
Fri Dec 04 22:44:59 2009 Fri Dec 04 22:44:59 2009 Information (7) We registered with a DOCSIS 1.1 config file!
Fri Dec 04 22:44:59 2009 Fri Dec 04 22:44:59 2009 Information (7) Received a REG-RSP message from the CMTS...
Fri Dec 04 22:44:59 2009 Fri Dec 04 22:44:59 2009 Information (7) Sending a REG-REQ to the CMTS...
Fri Dec 04 22:44:59 2009 Fri Dec 04 22:44:59 2009 Information (7) CableModem SNMP configure complete
Fri Dec 04 22:44:58 2009 Fri Dec 04 22:44:58 2009 Information (7) IP init completed ok
Fri Dec 04 22:44:58 2009 Fri Dec 04 22:44:58 2009 Information (7) CableModem TFTP init ok
Fri Dec 04 22:44:58 2009 Fri Dec 04 22:44:58 2009 Information (7) CableModem DHCP client init ok
Fri Dec 04 22:44:58 2009 Fri Dec 04 22:44:58 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Beginning initial ranging...
Time Not Established Time Not Established Information (7) downstream time sync acquired...
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) starting ds time sync acquisition...
Time Not Established Time Not Established Information (7) Locked on the downstream. Waiting for UCDs...
Time Not Established Time Not Established Information (7) Downstream lock ok
Time Not Established Time Not Established Information (7) Sync Start
Fri Dec 04 21:02:30 2009 Fri Dec 04 21:02:30 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Fri Dec 04 20:56:02 2009 Fri Dec 04 20:56:02 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Fri Dec 04 11:58:33 2009 Fri Dec 04 11:58:33 2009 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Dec 04 10:45:28 2009 Fri Dec 04 10:45:28 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Fri Dec 04 10:45:27 2009 Fri Dec 04 10:45:27 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync

I've already reported it on the newsgroups..."we will send this to Motorola and apologise for the time it'll take to investigate and resolve".

It is definitely an issue with the 1.1 system, because before the move I never saw a sync error once nor did it ever drop.

Welshchris

04-12-2009, 22:56

ive been reporting it since August on the BSR in Swansea and all i was told its normal and nothing to worry about! Yeah like the constant drop outs of people on the BSR also i bet thats normal in their eyes to.

Peter_

04-12-2009, 22:59

Moldova,

My modem logs fill up with this all the time so I have to reboot to get the config file jobby...

OK, after a reboot...

I've already reported it on the newsgroups..."we will send this to Motorola and apologise for the time it'll take to investigate and resolve".

It is definitely an issue with the 1.1 system, because before the move I never saw a sync error once nor did it ever drop.
Yes you are on DOCSIS 1.1 and as I said the is an issue elsewhere and from what you are saying it is on the Motorola BSR that you are connected to and has nothing to do with your modem.

Cable Modem : DOCSIS 1.0/1.1/2.0 Compliant, all that means is that the modem can run on either DOCSIS

darren.b

04-12-2009, 23:06

Let me just say that if your ready light is flashing in any way then you won't have the use of the modem until the light is steady.
Wrong. Because this very morning it was blinking away, yet I still had a connection to the intrawebs. Because of this, I suspect the issue is a bug in the software update to the modem. Or my modem is faulty.

I also suspect this because of the 48 hours of sync timeouts before it dies completely. Not even access to http://192.168.100.1/ is possible when it goes.

VMboy

04-12-2009, 23:35

Wrong. Because this very morning it was blinking away, yet I still had a connection to the intrawebs. Because of this, I suspect the issue is a bug in the software update to the modem. Or my modem is faulty.

Well if your modem is faulty then how can you say I am wrong?

A fully functional modem ie not faulty with the ready light flashing should not let you connect to the internet until the light goes steady.

Peter_

04-12-2009, 23:42

darren.b

04-12-2009, 23:52

Well if your modem is faulty then how can you say I am wrong?

A fully functional modem ie not faulty with the ready light flashing should not let you connect to the internet until the light goes steady.
Because you said it shouldn't let me connect. But it was online and working. Faulty modem or not, your theory was incorrect. ;)

Whether this is a modem fault or some other glitch elsewhere is yet to be proven. The modem "talks to" the CMTS in South Gyle, plenty of places it could go wrong between me and there. It'll be interesting to see who blames who. Is it Moto's fault? VM? Ambit? Whoever piped the co-ax into this flat 15 years ago? For sure it worked fine when I had my Moto SB5100E modem, and it worked fine when they switched me to an Ambit 256. Since the shunt to DOCSIS 1.1 it has went wrong.

VMboy

05-12-2009, 00:52

Because you said it shouldn't let me connect. But it was online and working. Faulty modem or not, your theory was incorrect. ;)

Whether this is a modem fault or some other glitch elsewhere is yet to be proven. The modem "talks to" the CMTS in South Gyle, plenty of places it could go wrong between me and there. It'll be interesting to see who blames who. Is it Moto's fault? VM? Ambit? Whoever piped the co-ax into this flat 15 years ago? For sure it worked fine when I had my Moto SB5100E modem, and it worked fine when they switched me to an Ambit 256. Since the shunt to DOCSIS 1.1 it has went wrong.

Sorry but my theory is not incorrect, the techs always said to me that until the ready light is steady the modem is ok to connect, so what do you take from that?

Because you have a fault somewhere this wouldn't be the case with you as your modem could quite possibly have a fault.

darren.b

05-12-2009, 01:19

Sorry but my theory is not incorrect, the techs always said to me that until the ready light is steady the modem is ok to connect, so what do you take from that?

Because you have a fault somewhere this wouldn't be the case with you as your modem could quite possibly have a fault.
The techs aren't always correct. I'm not arguing with you mate. Bugs (no matter where they are) can and will alter expected behaviour.

Bugs or not, it doesn't alter the fact you said I cannot be online while my ready light is flashing. It has done it lots of times and I have been online. Fact. You forgot to include anomalies and software/hardware bugs in your comment.

The modem has also been offline (and dead) while not flashing - and sometimes it is. Please...I am not pretending these issues happen for attention's sake. Nor am I saying it to score points.

I just want it fixed so it is as reliable as it was before. You're still on 1.0...it works as expected.

VMboy

05-12-2009, 10:55

solcuerda,

Call 151 and get this sorted out.

caph

06-12-2009, 17:02

Solcuerda,

I too am on 20Mb on DOCSIS 1.1 and I too get the same messages sometimes very frequently as per my event log this morning:-

Sun Dec 06 03:25:15 2009 Sun Dec 06 03:25:15 2009 Information (7) Downstream sync ok
Sun Dec 06 03:25:15 2009 Sun Dec 06 03:25:15 2009 Information (7) locked and synced to rescue CMTS...all is well!
Sun Dec 06 03:25:15 2009 Sun Dec 06 03:25:15 2009 Information (7) Downstream sync ok
Sun Dec 06 03:25:15 2009 Sun Dec 06 03:25:15 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sun Dec 06 03:25:15 2009 Sun Dec 06 03:25:15 2009 Information (7) Downstream sync failed
Sun Dec 06 03:25:15 2009 Sun Dec 06 03:25:15 2009 Information (7) Downstream sync ok
Sun Dec 06 03:25:14 2009 Sun Dec 06 03:25:14 2009 Information (7) locked and synced to rescue CMTS...all is well!
Sun Dec 06 03:25:14 2009 Sun Dec 06 03:25:14 2009 Information (7) Downstream sync ok
Sun Dec 06 03:25:14 2009 Sun Dec 06 03:25:14 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sun Dec 06 03:25:14 2009 Sun Dec 06 03:25:14 2009 Information (7) Downstream sync failed
Sun Dec 06 03:23:06 2009 Sun Dec 06 03:23:06 2009 Information (7) Downstream sync ok
Sun Dec 06 03:23:06 2009 Sun Dec 06 03:23:06 2009 Information (7) locked and synced to rescue CMTS...all is well!
Sun Dec 06 03:23:06 2009 Sun Dec 06 03:23:06 2009 Information (7) Downstream sync ok
Sun Dec 06 03:23:06 2009 Sun Dec 06 03:23:06 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sun Dec 06 03:23:06 2009 Sun Dec 06 03:23:06 2009 Information (7) Downstream sync failed
Sun Dec 06 03:23:06 2009 Sun Dec 06 03:23:06 2009 Information (7) Downstream sync ok
Sun Dec 06 03:23:06 2009 Sun Dec 06 03:23:06 2009 Information (7) locked and synced to rescue CMTS...all is well!
Sun Dec 06 03:23:06 2009 Sun Dec 06 03:23:06 2009 Information (7) Downstream sync ok
Sun Dec 06 03:23:05 2009 Sun Dec 06 03:23:05 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sun Dec 06 03:23:05 2009 Sun Dec 06 03:23:05 2009 Information (7) Downstream sync failed
Sun Dec 06 03:12:34 2009 Sun Dec 06 03:12:34 2009 Information (7) Downstream sync ok
Sun Dec 06 03:12:34 2009 Sun Dec 06 03:12:34 2009 Information (7) locked and synced to rescue CMTS...all is well!

but I get an almost perfect 20Mb connection. So although I haven't got any suggestions for you, at least you know that a perfect connection is possible even with all those event log messages.

Peter_

06-12-2009, 17:04

Solcuerda,

I too am on 20Mb on DOCSIS 1.1 and I too get the same messages sometimes very frequently as per my event log this morning:-

but I get an almost perfect 20Mb connection. So although I haven't got any suggestions for you, at least you know that a perfect connection is possible even with all those event log messages.
He is on a Motorola and you are on a Cisco so that will be the difference.