Problem on the up to 50mb service. [Archive]

View Full Version : Problem on the up to 50mb service.

MacmillaN

18-04-2010, 17:32

Hi
Everything had been going great until around a week ago, my connection kept disconnecting having to switch the router and modem off and back on again, i ended up getting fed up of doing that just to re-establish a connection, this would happen often.

I then thought maybe it is the supplied Netgear Router WNR2000. so i disconnected that and just set it up so it was connected straight into the modem, but i am still having random disconnection of service and a modem switch off and back on seems to re-establish the connection.

Can anyone help me with finding a solution to this?

speedfreak

18-04-2010, 19:41

to save others who do have the knowledge to help asking, do you know how how to access your modem stats and copy and paste them on here? Including error logs and up/down power levels, remember to edit out your cm mac address from the error logs with a xxxx

Peter_

18-04-2010, 19:45

MacmillaN

18-04-2010, 21:03

Hi, i was not sure on the information you wanted and not wanted, hope this is right.
Thanks for your help guys, i really appreciate it.

Cable Modem Information
Cable Modem : DOCSIS 1.0/1.1/2.0/3.0 Compliant
Serial Number : [mod]serial number removed
Boot Code Version : 6.1.1c
Software Version : 3.11.1011
Hardware Version : 1.39
CA Key : Installed

Cable Modem Status
Item
Status
Comments
Acquired Downstream Channel

299.001343 MHz

Primary Downstream Locked
Ranged Upstream Channel

25.799999 MHz

Success
Provisioning State

OK

Operational
Ethernet Link Status

Up

1000 Mbps/Full duplex

Cable Modem Downstream

DS-1
DS-2
DS-3
DS-4
Frequency
299000000
307000000
315000000
323000000
Lock Status
(QAM Lock/FEC Sync/MPEG Lock)
Y/Y/Y
Y/Y/Y
Y/Y/Y
Y/Y/Y
Channel Id
13
14
15
16
Modulation
256QAM
256QAM
256QAM
256QAM
Symbol Rate
(Msym/sec)
6.952
6.952
6.952
6.952
Interleave Depth
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level
(dBmV)
2.43
3.23
3.50
3.74
RxMER
(dB)
37.36
37.94
37.36
37.64
Correctable
Codewords
10
4
6
1
Uncorrectable
Codewords
885
273
897
974

Cable Modem Upstream

US-1
US-2
US-3
US-4
Channel Type
1.0
N/A
N/A
N/A
Channel ID
8
N/A
N/A
N/A
Frequency
(Hz)
25800000
N/A
N/A
N/A
Ranging Status
Success
N/A
N/A
N/A
Modulation
16QAM
N/A
N/A
N/A
Symbol Rate
(KSym/sec)
2560
N/A
N/A
N/A
Mini-Slot Size
2
N/A
N/A
N/A
Power Level
(dBmV)
52.25
N/A
N/A
N/A
T1 Timeouts
0
T2 Timeouts
0
0
0
0
T3 Timeouts
0
0
0
0
T4 Timeouts
0
0
0
0

Cable Modem Upstream Burst

US-1

Req
Init Maint
Per Maint
Short Data
Long Data

(1)
(3)
(4)
(5)
(6)
Modulation Type
QPSK
QPSK
QPSK
16QAM
16QAM
Differential Encoding
OFF
OFF
OFF
OFF
OFF
Preamble Length
64
128
128
144
160
Preamble Value Offset
140
6
6
216
216
FEC Error Correction (T)
0
5
5
5
10
FEC Codeword Information Bytes (k)
16
34
34
78
235
Maximum Burst Size
2
0
0
8
0
Guard Time Size
8
48
48
8
8
Last Codeword Length
FIX
FIX
FIX
SHORT
SHORT
Scrambler on/off
ON
ON
ON
ON
ON

_________________
Cable Modem Operation Configuration
General Configuration
Network Access :
Allowed
Maximum Number of CPEs :
1
Baseline Privacy :
Enabled
DOCSIS Mode :
DOCSIS 3.0
Config File :
Pcaa1a92007a50b13.cm
Primary Downstream Service Flow
SFID :
13419
Max Traffic Rate :
53000000 bps
Max Traffic Burst :
10000 bytes
Min Traffic Rate :
0 bps
Primary Upstream Service Flow
SFID :
13418
Max Traffic Rate :
1750000 bps
Max Traffic Burst :
3044 bytes
Min Traffic Rate :
0 bps
Max Concatenated Burst :
0 bytes
Scheduling Type :
Best Effort

Cable Modem Event Log
First Time Last Time Priority Description
Thu Mar 4 00:34:23 2010 Thu Mar 4 00:34:23 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Thu Mar 4 09:07:54 2010 Thu Mar 4 09:07:54 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Thu Mar 4 14:52:21 2010 Thu Mar 4 14:52:21 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Thu Mar 4 18:31:39 2010 Thu Mar 4 18:31:39 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Thu Mar 4 22:42:52 2010 Sat Mar 20 05:55:25 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sat Mar 20 16:09:26 2010 Sat Mar 20 16:09:26 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 21 01:24:23 2010 Mon Mar 22 13:20:55 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Mar 22 21:37:14 2010 Mon Mar 22 21:37:14 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Wed Mar 24 00:30:23 2010 Thu Mar 25 06:26:38 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Thu Mar 25 06:27:08 2010 Thu Mar 25 06:27:08 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sat Mar 27 14:23:57 2010 Fri Apr 2 08:34:08 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 2 17:00:18 2010 Sat Apr 3 16:23:11 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 4 07:28:12 2010 Wed Apr 7 18:01:06 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 7 20:07:48 2010 Wed Apr 7 20:07:48 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 7 20:07:55 2010 Wed Apr 7 20:07:55 2010 Warning (5) MDD message timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 7 20:12:19 2010 Wed Apr 7 20:12:47 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 7 20:12:49 2010 Wed Apr 7 20:12:49 2010 Critical (3) Ranging Request Retries exausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 7 20:12:49 2010 Wed Apr 7 20:12:49 2010 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Thu Apr 8 13:16:10 2010 Sat Apr 10 10:22:03 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 10 10:35:53 2010 Sat Apr 10 13:56:19 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 11 22:57:11 2010 Sun Apr 11 22:57:11 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:46:20 2010 Mon Apr 12 12:46:20 2010 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:46:44 2010 Mon Apr 12 12:46:44 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:53:47 2010 Mon Apr 12 12:53:50 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:54:03 2010 Mon Apr 12 12:54:03 2010 Error (4) More than one primary downstream channel assignment present in RCC;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:58:52 2010 Mon Apr 12 12:59:14 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:59:44 2010 Mon Apr 12 12:59:44 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:59:51 2010 Mon Apr 12 12:59:51 2010 Warning (5) MDD message timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 13:02:56 2010 Mon Apr 12 13:03:24 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 13:03:26 2010 Mon Apr 12 13:03:26 2010 Critical (3) Ranging Request Retries exausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 13:03:26 2010 Mon Apr 12 13:03:26 2010 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 18:15:56 2010 Thu Apr 15 19:46:38 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Thu Apr 15 21:59:12 2010 Thu Apr 15 21:59:12 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 16 05:38:13 2010 Sat Apr 17 18:11:33 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 17 23:38:04 2010 Sat Apr 17 23:38:04 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 18 11:33:57 2010 Sun Apr 18 11:33:57 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 18 13:31:42 2010 Sun Apr 18 13:31:42 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 18 13:41:29 2010 Sun Apr 18 13:41:29 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 18 13:58:00 2010 Sun Apr 18 13:58:00 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

Peter_

18-04-2010, 22:21

Downstream
Power Level
(dBmV)
2.43 3.23 3.50 3.74
RxMER
(dB)
37.36 37.94 37.36 37.64

Upstream
Power Level
(dBmV)52.25

Your power levels are all with operational parameters so a call to the 50Mb Support Team is in order so call tomorrow morning after 0800 and they will check your connection.

MacmillaN

18-04-2010, 22:43

at 22:30pm, I lost my connection again...

I will do as you suggest.
Thanks Masque

MacmillaN

24-04-2010, 22:41

UPDATE:
I lost my connection again at 6pm on Friday - decided to give virgin a phone call - very pleasant gentleman on the other end, although i had reset the modem whilst on hold which took ages to get through, once i got through my connection was live again so i told him what happened before connection lose and what i did to solve it and he said it sounds like your modem may need replaced, but i cannot see any issues in the stats- as soon as the drop happens give us a call back and we will look into it further - although the gentlemen did ask if any lights on top of the modem went out when you got the drop and none did go out.

Today 6ish - Connection drop again called them again - was in the queue for 35mins and finally got through to someone reading a script - i told him everything the gentleman before told me and then i was put on hold for another 20mins and got fed up listening to the god damn awful music i gave up. - would of been OK if he told me he was going to do something and just hold on - but after i told him everything i was placed on hold.
Too bad i did not get this persons name otherwise i would of complained at his shockingly bad customer service - could not understand a word he was saying and he just went silent on me.

Sephiroth

26-04-2010, 08:56

It would help if we can see your stats again (in a better format if you can). I'd be looking to see if the uncorrectable codewords count has grown. If it has, the either your modem is playing up or there is RF noise getting in that is not shown in the RxMER/SNR value.

Keep a copy of the event log because it gets purged when full and if you cold start your modem.

Also, what is the symptom you see of losing your connection? The evebt log you posted shows no disconnection on 23rd April.

Cheers

MacmillaN

26-04-2010, 16:26

DS-1 DS-2 DS-3 DS-4
Frequency 299000000 307000000 315000000 323000000
Lock Status
(QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y Y/Y/Y Y/Y/Y Y/Y/Y
Channel Id 13 14 15 16
Modulation 256QAM 256QAM 256QAM 256QAM
Symbol Rate
(Msym/sec) 6.952 6.952 6.952 6.952
Interleave Depth I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17
Power Level
(dBmV) 1.07 1.89 1.87 2.12
RxMER
(dB) 37.94 37.94 37.36 37.94
Correctable
Codewords 44 34 37 41
Uncorrectable
Codewords 296 976 881 880

First Time Last Time Priority Description
Thu Apr 8 13:16:10 2010 Sat Apr 10 10:22:03 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 10 10:35:53 2010 Sat Apr 10 13:56:19 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 11 22:57:11 2010 Sun Apr 11 22:57:11 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:46:20 2010 Mon Apr 12 12:46:20 2010 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=0;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:46:44 2010 Mon Apr 12 12:46:44 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:53:47 2010 Mon Apr 12 12:53:50 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:54:03 2010 Mon Apr 12 12:54:03 2010 Error (4) More than one primary downstream channel assignment present in RCC;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:58:52 2010 Mon Apr 12 12:59:14 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:59:44 2010 Mon Apr 12 12:59:44 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 12:59:51 2010 Mon Apr 12 12:59:51 2010 Warning (5) MDD message timeout;CM-MAC;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 13:02:56 2010 Mon Apr 12 13:03:24 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 13:03:26 2010 Mon Apr 12 13:03:26 2010 Critical (3) Ranging Request Retries exausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 13:03:26 2010 Mon Apr 12 13:03:26 2010 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 12 18:15:56 2010 Thu Apr 15 19:46:38 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Thu Apr 15 21:59:12 2010 Thu Apr 15 21:59:12 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 16 05:38:13 2010 Sat Apr 17 18:11:33 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 17 23:38:04 2010 Sat Apr 17 23:38:04 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 18 11:33:57 2010 Sun Apr 18 11:33:57 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 18 13:31:42 2010 Sun Apr 18 13:31:42 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 18 13:41:29 2010 Sun Apr 18 13:41:29 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 18 13:58:00 2010 Sun Apr 18 13:58:00 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 18 20:24:27 2010 Sun Apr 18 20:24:27 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 18 21:26:48 2010 Sun Apr 18 21:26:48 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 19 13:24:29 2010 Wed Apr 21 00:48:51 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 21 20:40:02 2010 Wed Apr 21 21:04:01 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Thu Apr 22 19:19:08 2010 Fri Apr 23 15:59:58 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 23 16:05:11 2010 Fri Apr 23 16:29:20 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 23 16:29:27 2010 Fri Apr 23 16:29:27 2010 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Time Not Established Warning (5) ToD request sent - No Response received;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 23 16:43:17 2010 Fri Apr 23 16:43:17 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 23 17:16:01 2010 Fri Apr 23 17:16:01 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 23 21:55:03 2010 Fri Apr 23 21:55:03 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 24 06:58:45 2010 Sat Apr 24 06:58:45 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 24 11:23:10 2010 Sat Apr 24 14:08:37 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 24 17:07:11 2010 Sat Apr 24 17:07:11 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 24 17:37:40 2010 Sun Apr 25 17:00:34 2010 Critical (3) No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 25 17:14:52 2010 Sun Apr 25 17:49:14 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 26 13:46:01 2010 Mon Apr 26 13:46:01 2010 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC;CMTS-MAC;
Mon Apr 26 13:46:25 2010 Mon Apr 26 13:46:25 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0;

Peter_

26-04-2010, 16:29

Could you also post the Upstream power level as well thanks.

MacmillaN

26-04-2010, 16:35

US-1 US-2 US-3 US-4
Channel Type 1.0 N/A N/A N/A
Channel ID 8 N/A N/A N/A
Frequency
(Hz) 25800000 N/A N/A N/A
Ranging Status Success N/A N/A N/A
Modulation 16QAM N/A N/A N/A
Symbol Rate
(KSym/sec) 2560 N/A N/A N/A
Mini-Slot Size 2 N/A N/A N/A
Power Level
(dBmV) 53.25 N/A N/A N/A
T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 0 0 0 0
T4 Timeouts 0 0 0 0

Peter_

26-04-2010, 17:14

Your power levels appear normal so try calling now and we will check your connection.

MacmillaN

26-04-2010, 17:17

Well about a few minutes ago i had a engineer come in and check our set-top box.

he checked the cables outside and said one of them appeared to have water damage so he replaced the seal- he then changed the set-top box with a newer one, i also told him about the issues with the broadband and he said what he done might solve your connection drops.

but left my carpet with black marks all over it- which will not come out- a complaint has been logged with VM.

The black marks is like oil or tar.

Peter_

26-04-2010, 17:36

MacmillaN

26-04-2010, 17:56

The engineer who came to me, did not remove his boots.