PDA

View Full Version : Possible faulty Ambit 255 on 20Mb/s


mattross
23-12-2009, 13:06
Hi,

I've had this modem a couple of years and has been fine for most of that time, but in the past couple of months every few days it loses connection. Although I can dhcp release/renew [via Linksys WRT54GL with DD-WRT] I can never connect to anything until I've rebooted the modem. I also cannot connect to http://192.168.100.1 until it's rebooted. When I can get onto it there are lots of 'No Ranging Response received - T3 time-out' messages.

A complete event log from the most recent failure this morning before and after its reboot:

Wed Dec 23 11:30:08 2009 Wed Dec 23 11:30:08 2009 Information (7) The s/w filename specified in the config file is the same as ...
Wed Dec 23 11:30:08 2009 Wed Dec 23 11:30:08 2009 Information (7) A software upgrade filename was specified in the config file.
Wed Dec 23 11:30:08 2009 Wed Dec 23 11:30:08 2009 Information (7) Authorized
Wed Dec 23 11:30:08 2009 Wed Dec 23 11:30:08 2009 Information (7) Registration complete!
Wed Dec 23 11:30:07 2009 Wed Dec 23 11:30:07 2009 Information (7) We registered with a DOCSIS 1.1 config file!
Wed Dec 23 11:30:07 2009 Wed Dec 23 11:30:07 2009 Information (7) Received a REG-RSP message from the CMTS...
Wed Dec 23 11:30:07 2009 Wed Dec 23 11:30:07 2009 Information (7) Sending a REG-REQ to the CMTS...
Wed Dec 23 11:30:07 2009 Wed Dec 23 11:30:07 2009 Information (7) CableModem SNMP configure complete
Wed Dec 23 11:30:07 2009 Wed Dec 23 11:30:07 2009 Information (7) IP init completed ok
Wed Dec 23 11:30:07 2009 Wed Dec 23 11:30:07 2009 Information (7) CableModem TFTP init ok
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
Wed Dec 23 11:03:35 2009 Wed Dec 23 11:03:35 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Wed Dec 23 11:03:24 2009 Wed Dec 23 11:03:24 2009 Critical (3) No Ranging Response received - T3 time-out
Wed Dec 23 11:03:15 2009 Wed Dec 23 11:03:15 2009 Critical (3) No Ranging Response received - T3 time-out
Wed Dec 23 11:03:04 2009 Wed Dec 23 11:03:04 2009 Critical (3) No Ranging Response received - T3 time-out
Wed Dec 23 11:02:53 2009 Wed Dec 23 11:02:53 2009 Critical (3) No Ranging Response received - T3 time-out
Wed Dec 23 11:02:51 2009 Wed Dec 23 11:02:51 2009 Critical (3) No Ranging Response received - T3 time-out
Wed Dec 23 11:02:49 2009 Wed Dec 23 11:02:49 2009 Critical (3) No Ranging Response received - T3 time-out
Wed Dec 23 11:02:45 2009 Wed Dec 23 11:02:45 2009 Critical (3) No Ranging Response received - T3 time-out
Wed Dec 23 11:02:44 2009 Wed Dec 23 11:02:44 2009 Critical (3) No Ranging Response received - T3 time-out
Wed Dec 23 11:02:41 2009 Wed Dec 23 11:02:41 2009 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Wed Dec 23 11:02:08 2009 Wed Dec 23 11:02:08 2009 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...

From reading other threads here the power settings seem fine to me:

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

Upstream Lock : Locked
Upstream Channel ID : 4
Upstream Frequency : 47400000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 39.0 dBmV
Upstream Mini-Slot Size : 2

For days I can get perfect performance from it. There are no issues with bandwidth as I can get 20Mb/s when it's working. I'd say about every 3-4 days it just stops working at random times of the day. Usually it's idle when the failure occurs.

Is this likely to be a fault with the modem or its PSU? Can it be diagnosed in more detail remotely by a VM techie? I can provide the MAC address if it would be useful to check it.

Thank you.

Ben B
23-12-2009, 13:15
Hello and :welcome:,

Your downstream level of 10.3dBmV is way too high and is probably causing the issues you are describing. You will need an Engineer to correct this for you. Give tech support a call on 151 from a Virgin phone or 08454541111 from any other phone.

Ben :)

mattross
23-12-2009, 13:23
In the sticky thread titled 'Cable Modem Signal Levels' it says Both Telewest and ntl are now using the more efficient, but demanding 256QAM modulation in some areas. This gives more bandwidth but required better networks. For this modulation the recommended power range is -6dBmV to +15dBmV with a recommended SNR of 33dB.

Is that no longer accurate?

Peter_
23-12-2009, 21:41
If you are having issues with your connection then you need to call Tech Support which is open 24/7 on 151 from your Virgin Media Phone.

It's absolutely free.

Or call 0845 454 1111 from any other phone line.

They will be able to check what is going on remotely and if required book an engineer.

mattross
24-12-2009, 14:05
Well I got lucky with tech support. I posted a thread on the broadband support newsgroup late last night and managed to snag an engineer visit today. He's just left in fact. He said the power levels were fine and within specification so he replaced the modem in case it was a hardware fault. Hopefully that's it solved.