synner
09-01-2010, 20:28
Hi All,
I don't know if anyone can advise, but for the last 2 days I have been having some issues with my 50Mb connection.
If I reboot the modem it can take between 2 hours and 7 hours (7.5 hours today) to re-connect. This only started on Friday, prior to this it took a minute or two to reconnect.
50Mb support line want to send an engineer to replace the modem, but I think it's more a network issue. The modem tick light flashes continually, but everything on the modem web pages looks fine (apart from the "Status" section where it seems to get as far as BPI Initialising and then cycles back around through acquiring downstream etc).
While this is happening the V+ box connected to the same cable through a splitter is fine, On demand, red button etc all ok.
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 29 30 31 32
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.01 1.83 1.47 1.41
RxMER
(dB) 36.39 36.17 36.39 36.84
Correctable
Codewords 10937810 18776785 18733791 13523249
Uncorrectable
Codewords 299 288 304 280
Channel Type 1.0 N/A N/A N/A
Channel ID 3 N/A N/A N/A
Frequency
(Hz) 37500000 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) 36.25 N/A N/A N/A
T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 85 0 0 0
T4 Timeouts 228 0 0 0
Sat Jan 9 19:36:36 2010
Sat Jan 9 19:36:36 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 Jan 9 19:36:51 2010
Sat Jan 9 19:36:51 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:37:21 2010
Sat Jan 9 19:37:21 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 Jan 9 19:37:37 2010
Sat Jan 9 19:37:37 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:38:07 2010
Sat Jan 9 19:38:07 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 Jan 9 19:38:29 2010
Sat Jan 9 19:38:29 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:38:59 2010
Sat Jan 9 19:38:59 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 Jan 9 19:39:29 2010
Sat Jan 9 19:39:29 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:39:59 2010
Sat Jan 9 19:41:07 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 Jan 9 19:41:16 2010
Sat Jan 9 19:41:16 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:41:46 2010
Sat Jan 9 19:42:21 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 Jan 9 19:42:43 2010
Sat Jan 9 19:42:43 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:43:13 2010
Sat Jan 9 19:48:57 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 Jan 9 20:03:30 2010
Sat Jan 9 20:22:28 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Anyone got any ideas? Nothing at all has changed at this side, the modem does eventually connect, but a 7 hour delay is a little silly !
Cheers
I don't know if anyone can advise, but for the last 2 days I have been having some issues with my 50Mb connection.
If I reboot the modem it can take between 2 hours and 7 hours (7.5 hours today) to re-connect. This only started on Friday, prior to this it took a minute or two to reconnect.
50Mb support line want to send an engineer to replace the modem, but I think it's more a network issue. The modem tick light flashes continually, but everything on the modem web pages looks fine (apart from the "Status" section where it seems to get as far as BPI Initialising and then cycles back around through acquiring downstream etc).
While this is happening the V+ box connected to the same cable through a splitter is fine, On demand, red button etc all ok.
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 29 30 31 32
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.01 1.83 1.47 1.41
RxMER
(dB) 36.39 36.17 36.39 36.84
Correctable
Codewords 10937810 18776785 18733791 13523249
Uncorrectable
Codewords 299 288 304 280
Channel Type 1.0 N/A N/A N/A
Channel ID 3 N/A N/A N/A
Frequency
(Hz) 37500000 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) 36.25 N/A N/A N/A
T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 85 0 0 0
T4 Timeouts 228 0 0 0
Sat Jan 9 19:36:36 2010
Sat Jan 9 19:36:36 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 Jan 9 19:36:51 2010
Sat Jan 9 19:36:51 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:37:21 2010
Sat Jan 9 19:37:21 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 Jan 9 19:37:37 2010
Sat Jan 9 19:37:37 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:38:07 2010
Sat Jan 9 19:38:07 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 Jan 9 19:38:29 2010
Sat Jan 9 19:38:29 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:38:59 2010
Sat Jan 9 19:38:59 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 Jan 9 19:39:29 2010
Sat Jan 9 19:39:29 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:39:59 2010
Sat Jan 9 19:41:07 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 Jan 9 19:41:16 2010
Sat Jan 9 19:41:16 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:41:46 2010
Sat Jan 9 19:42:21 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 Jan 9 19:42:43 2010
Sat Jan 9 19:42:43 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 9 19:43:13 2010
Sat Jan 9 19:48:57 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 Jan 9 20:03:30 2010
Sat Jan 9 20:22:28 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Anyone got any ideas? Nothing at all has changed at this side, the modem does eventually connect, but a 7 hour delay is a little silly !
Cheers