PDA

View Full Version : Now this is really weird

Welshchris
22-09-2009, 00:49
A few moments ago my modem rebooted....

As we speak my modems ready light is flashing as if i dont have a connection... yet i can access all sites, and msn thats how i can post on here and this is what the modem log shows....

Mon Sep 21 23:42:21 2009 Mon Sep 21 23:42:21 2009 Information (7) DCC arrive new
Mon Sep 21 23:42:20 2009 Mon Sep 21 23:42:20 2009 Information (7) Locked on the downstream. Waiting for UCDs...
Mon Sep 21 23:42:20 2009 Mon Sep 21 23:42:20 2009 Information (7) Downstream lock ok
Mon Sep 21 23:42:20 2009 Mon Sep 21 23:42:20 2009 Information (7) DCC depart old
Mon Sep 21 23:42:20 2009 Mon Sep 21 23:42:20 2009 Information (7) Received DCC-REQ message...
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) The s/w filename specified in the config file is the same as ...
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) A software upgrade filename was specified in the config file.
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) Authorized
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) Registration complete!
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) We registered with a DOCSIS 1.1 config file!
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) Received a REG-RSP message from the CMTS...
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) Sending a REG-REQ to the CMTS...
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) CableModem SNMP configure complete
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) IP init completed ok
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) CableModem TFTP init ok
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Information (7) CableModem DHCP client init ok
Mon Sep 21 23:42:10 2009 Mon Sep 21 23:42:10 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Mon Sep 21 23:42:04 2009 Mon Sep 21 23:42:04 2009 Information (7) MAP w/initial maintenance region received
Mon Sep 21 23:42:04 2009 Mon Sep 21 23:42:04 2009 Information (7) Downstream sync ok
Mon Sep 21 23:42:04 2009 Mon Sep 21 23:42:04 2009 Information (7) Beginning initial ranging...
Mon Sep 21 23:42:04 2009 Mon Sep 21 23:42:04 2009 Information (7) downstream time sync acquired...
Mon Sep 21 23:42:04 2009 Mon Sep 21 23:42:04 2009 Information (7) Downstream sync ok
Mon Sep 21 23:42:04 2009 Mon Sep 21 23:42:04 2009 Information (7) starting ds time sync acquisition...
Mon Sep 21 23:42:02 2009 Mon Sep 21 23:42:02 2009 Information (7) MAP w/initial maintenance region received
Mon Sep 21 23:42:01 2009 Mon Sep 21 23:42:01 2009 Information (7) Downstream sync ok
Mon Sep 21 23:42:01 2009 Mon Sep 21 23:42:01 2009 Information (7) Beginning initial ranging...
Mon Sep 21 23:42:01 2009 Mon Sep 21 23:42:01 2009 Information (7) downstream time sync acquired...
Mon Sep 21 23:42:01 2009 Mon Sep 21 23:42:01 2009 Information (7) Downstream sync ok
Mon Sep 21 23:42:00 2009 Mon Sep 21 23:42:00 2009 Information (7) starting ds time sync acquisition...
Mon Sep 21 23:41:59 2009 Mon Sep 21 23:41:59 2009 Information (7) Locked on the downstream. Waiting for UCDs...
Mon Sep 21 23:41:59 2009 Mon Sep 21 23:41:59 2009 Information (7) Downstream lock ok
Mon Sep 21 23:41:15 2009 Mon Sep 21 23:41:15 2009 Information (7) DS channel override in cfg file, re-scanning downstream


Anyone have a clue?

Downstream Lock : Locked
Downstream Channel Id : 193
Downstream Frequency : 315000000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 3.5 dBmV
Downstream SNR : 39.5 dB

Upstream Lock : Locked
Upstream Channel ID : 1
Upstream Frequency : 47400000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 51.0 dBmV
Upstream Mini-Slot Size : 2
moaningmags
22-09-2009, 00:50
All that information is just over a minute, I think that's pretty amazing :)
Welshchris
22-09-2009, 00:55
and what i also find funny about it all is that they STILL havnt updated teh daylight savings time on the modems.

Why is the ready light flashing and what does that mean in the log?

http://img97.imageshack.us/img97/3185/vml1.th.jpg (http://img97.imageshack.us/i/vml1.jpg/)

http://img242.imageshack.us/img242/6759/vml2.th.jpg (http://img242.imageshack.us/i/vml2.jpg/)

http://img246.imageshack.us/img246/3298/vml3.th.jpg (http://img246.imageshack.us/i/vml3.jpg/)
xocemp
22-09-2009, 00:55
Since the ready light serves to show upstream RF and CMTS/upstream SNR/MER and your RF is fine, then perhaps at some point in the day your modulation had changed due to ASM, upstream SNR/MER is now corrected and modulation type has been reset. **

Helpful?

**The information contained in this post was best/educated guess from the limited amount of information offered. Information contained in this post should not be taken as 100% proof of anything and therefor should not be used to brow beat* VirginMedia

*ISPA, OFCOM etc.
Welshchris
22-09-2009, 01:19
but why is it flashing ALL the time?
xocemp
22-09-2009, 01:24
Broken light?
After restarting the modem does it continue?
Welshchris
22-09-2009, 01:28
yes, it continues and modem has been restarted twice and its only happened since the reboot when that log was taken.
Paul
22-09-2009, 01:31
Does it matter if your online and working ?
xocemp
22-09-2009, 01:34
And what do the logs show now since the logs you posted where from:
23:42:21 to 23:41:15 though you posted them at 00:49 and its now 01:34.
Also you'll be looking for upstream values in the logs not downstream.

**The information contained in this post was best/educated guess from the limited amount of information offered. Information contained in this post should not be taken as 100% proof of anything and therefor should not be used to brow beat* VirginMedia

*ISPA, OFCOM etc.
Welshchris
22-09-2009, 01:42
take into account the modem time is an hour out for daylight savings as that hasnt been adjusted.
xocemp
22-09-2009, 01:49
DLS on the CM isn't important, DLS on the CMTS however, is as this needs to be correct for STM.
It could just simply be a defective light Chris, if it isn't broke don't fix it.
Or as Paul put it:
Does it matter if your online and working ?

There is noting in the log you posted to indicate return path defects, so the ready light wouldn't be flashing due to RF, modulation is also correct.




**The information contained in this post was best/educated guess from the limited amount of information offered. Information contained in this post should not be taken as 100% proof of anything and therefor should not be used to brow beat* VirginMedia.

*ISPA, OFCOM etc.
Kymmy
22-09-2009, 09:45
Sorry but I've now heard "defective light" from two people in this thread...

LED's (as in the modem) do not flash when defective, they tend to be either on or off ;) Even a dry joint won't make an LED Flash as stated in the OP's post :p:
Ignitionnet
22-09-2009, 10:06
Maybe something in the modem's firmware got tetchy at this DCC?

Mon Sep 21 23:42:21 2009 Mon Sep 21 23:42:21 2009 Information (7) DCC arrive new
Mon Sep 21 23:42:20 2009 Mon Sep 21 23:42:20 2009 Information (7) Locked on the downstream. Waiting for UCDs...
Mon Sep 21 23:42:20 2009 Mon Sep 21 23:42:20 2009 Information (7) Downstream lock ok
Mon Sep 21 23:42:20 2009 Mon Sep 21 23:42:20 2009 Information (7) DCC depart old
Mon Sep 21 23:42:20 2009 Mon Sep 21 23:42:20 2009 Information (7) Received DCC-REQ message...

Maybe a new firmware which has a bug was downloaded.

Maybe switching the modem off for a couple of minutes to totally discharge will sort it.

Maybe, maybe, maybe. Come on people I have an issue and still no answers, focus!
Welshchris
22-09-2009, 13:56
another log a few hrs later.....

Tue Sep 22 05:13:47 2009 Tue Sep 22 05:13:47 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Tue Sep 22 05:13:07 2009 Tue Sep 22 05:13:07 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Tue Sep 22 05:13:00 2009 Tue Sep 22 05:13:00 2009 Critical (3) No Ranging Response received - T3 time-out
Tue Sep 22 05:13:36 2009 Tue Sep 22 05:13:36 2009 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Sep 22 05:11:57 2009 Tue Sep 22 05:11:57 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Tue Sep 22 05:11:47 2009 Tue Sep 22 05:11:47 2009 Critical (3) No Ranging Response received - T3 time-out
Tue Sep 22 05:12:38 2009 Tue Sep 22 05:12:38 2009 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Sep 22 05:10:56 2009 Tue Sep 22 05:10:56 2009 Critical (3) TFTP failed - configuration file NOT FOUND
Tue Sep 22 05:10:54 2009 Tue Sep 22 05:10:54 2009 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Tue Sep 22 05:10:29 2009 Tue Sep 22 05:10:29 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Tue Sep 22 05:10:18 2009 Tue Sep 22 05:10:18 2009 Critical (3) No Ranging Response received - T3 time-out
Ignitionnet
22-09-2009, 15:22
Are we perhaps thinking that there might have been a good reason why 20M customers in your area weren't on the overlay network and that pushing VM to migrate you back via the ISPA, MI5, GCHQ, etc before they had resolved the underlying issues wasn't such a hot idea?
Welshchris
22-09-2009, 17:27
ive had no problems with my connection at all until last night since ive been put back on the new network and a few mins ago it rebooted again..

Time Not Established Time Not Established Information (7) The s/w filename specified in the config file is the same as ...
Time Not Established Time Not Established Information (7) A software upgrade filename was specified in the config file.
Time Not Established Time Not Established Information (7) Authorized
Time Not Established Time Not Established Information (7) Registration complete!
Time Not Established Time Not Established Information (7) We registered with a DOCSIS 1.1 config file!
Time Not Established Time Not Established Information (7) Received a REG-RSP message from the CMTS...
Time Not Established Time Not Established Information (7) Sending a REG-REQ to the CMTS...
Time Not Established Time Not Established Information (7) CableModem SNMP configure complete
Time Not Established Time Not Established Information (7) IP init completed ok
Time Not Established Time Not Established Information (7) CableModem TFTP init ok
Time Not Established Time Not Established Error (4) ToD request sent- No Response received
Time Not Established Time Not Established Information (7) CableModem DHCP client init ok
Time Not Established Time Not Established 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) 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
Tue Sep 22 16:18:25 2009 Tue Sep 22 16:18:25 2009 Critical (3) No Ranging Response received - T3 time-out
Tue Sep 22 16:18:25 2009 Tue Sep 22 16:18:25 2009 Critical (3) No Ranging Response received - T3 time-out
Tue Sep 22 16:18:20 2009 Tue Sep 22 16:18:20 2009 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Tue Sep 22 16:17:24 2009 Tue Sep 22 16:17:24 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Tue Sep 22 16:17:15 2009 Tue Sep 22 16:17:15 2009 Critical (3) No Ranging Response received - T3 time-out
Tue Sep 22 16:17:09 2009 Tue Sep 22 16:17:09 2009 Critical (3) No Ranging Response received - T3 time-out
Tue Sep 22 16:18:06 2009 Tue Sep 22 16:18:06 2009 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Sep 22 16:16:18 2009 Tue Sep 22 16:16:18 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Tue Sep 22 16:16:09 2009 Tue Sep 22 16:16:09 2009 Critical (3) No Ranging Response received - T3 time-out
Tue Sep 22 16:15:58 2009 Tue Sep 22 16:15:58 2009 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Welshchris
22-09-2009, 21:41
ffs i have another Engineer coming out on Thursday to sort this as again they claim its an upstream issue but last engineer that came here claimed "All i can do is change the modem"
Ignitionnet
23-09-2009, 08:31
The high upstream issue that was resolved when you were returned to the older platform, albeit at the cost of performance as there was congestion there?
Welshchris
23-09-2009, 10:14
actually no it wasnt resolved because powerlevels were apparently the problem factor of poor performance on the older platform. Since being back on newer platform performance has been brilliant and only now ive had modem reboots.
Ignitionnet
23-09-2009, 13:12
actually no it wasnt resolved because powerlevels were apparently the problem factor of poor performance on the older platform. Since being back on newer platform performance has been brilliant and only now ive had modem reboots.

Really.

Just to refresh your memory, relevant parts in bold:

http://www.cableforum.co.uk/board/34859344-post20.html

Where when i was on the Docsis 1 network my upstream was 45 - 49 dbmv when it switched to docsis 1.1 my upstream was getting as high as 59 dbmv and causing my modem to reboot almost on a daily basis.

An engineer came out on tuesday and said it was the modem and i argued saying NO! and he was like well i cant do anything but he changed the modem and since then i am now back on the docsis 1 network, i enquired why and told im on some sort of overspil UBR for 20mb customers. my upstream is now back to around 47dbmv most of the time and no modem reboots since.

From what I can see the first time you were moved to the BSR your connection was munted, stability was fixed by moving you back to the legacy network, you kicked and screamed to the ISPA because you were only getting about 9Mbit at peak times and were moved back to the overlay where your connection has become unstable again.

I would speculate that there were return path issues and VM were moving modems back to the legacy platform to try and provide better service there than to the not fully functional overlay but you put paid to that with your complaints so they moved you back prematurely. I would speculate that there may be SNR issues on the overlay now though you'd need to speak with VM about it, probably newsgroups are the best bet.

The overlay is much more vulnerable to ingress than the legacy network for a few reasons. My own area's SNR sits in the low 30s dB upstream then dives to ~20dB in the evenings from a source of ingress somewhere on the MAC domain.

You're really not having much luck are you?
Welshchris
23-09-2009, 22:08
im only going by what im told by VM themselves