Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

No Ranging Response received - T3 time-out

Go to solution
Lexsed
Tuning in

on ‎08-05-2017 19:54

Hi,

Got this going on for the last month or so, frequent drops, while short, are extremely annoying and frequent. Tried all the troubleshooting I could find here, as well as from 3rd party sources, but no dice, it comes back and goes away randomly

Here are the logs which I assume can help determine the issue:

Date Time Error Number Error Description

08/05/201718:35:04 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:35:02 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:33:43 GMT66050310Auth Success - Web login successful.
08/05/201718:31:26 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:31:00 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:30:59 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:28:35 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:28:09 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:21:56 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:21:55 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:15:53 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:15:45 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:10:56 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:10:40 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:10:10 GMT84020200Lost MDD Timeout
08/05/201718:08:41 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:08:06 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:07:51 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:07:50 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:07:46 GMT82000200No Ranging Response received - T3 time-out

 

Downstream Channels

Lock StatusChannel IDFrequencyModulationRx PowerRxMERPre RS ErrorsPost RS ErrorsLocked1171000000 Hz256 QAM-5.6 dBmV 37.1 dB994843745736Locked2179000000 Hz256 QAM-5.7 dBmV 37.6 dB955494700219Locked3187000000 Hz256 QAM-5.6 dBmV 37.6 dB1090159729393Locked4195000000 Hz256 QAM-5.6 dBmV 37.1 dB1309304915025Locked5203000000 Hz256 QAM-5.7 dBmV 37.4 dB1196401796995Locked6211000000 Hz256 QAM-5.9 dBmV 37.4 dB841841575510Locked7219000000 Hz256 QAM-6.0 dBmV 37.4 dB775186506153Locked8227000000 Hz256 QAM-6.0 dBmV 37.6 dB778429499077

Upstream Channels

Lock StatusChannel IDFrequencyModulationTx PowerModeChannel BandwidthSymbol RateLocked7439400000 HzATDMA48.3 dBmV16QAM6400000 Hz5120 Ksym/secNotLocked00 Hz 0 dBmV  0 Ksym/secNotLocked00 Hz 0 dBmV  0 Ksym/secLocked7625800000 HzATDMA46.8 dBmV16QAM6400000 Hz5120 Ksym/sec

0 Kudos
118 REPLIES 118

Go to solution
Emma_E
Forum Team (Retired)
Forum Team (Retired)
In response to szuster

on ‎07-11-2018 21:25

Hi szuster,

 

I would love to take a look at this for you but I am having trouble locating your connection details.

 

Your last log in was from an IP address which doesn't relate to a Virgin Media account, and your sign-up email address is also non-Virgin Media. Consequently I am unable to identify your account. I will pop you a PM (Purple Envelope, top right hand corner) so we can investigate further.

 

Speak to you soon. 

 

Emma


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos

Go to solution
suryamamidala
Joining in
In response to Emma_E

‎30-11-2018 17:21 - edited ‎30-11-2018 17:22

 

Hi

I am having the same problem for the past 4 to 5 months. Have called the customer center multiple times and even there were couple of engineer visits but to no vain. Can you please have someone fix this issue. 

Network Log

Time Priority Description

2018-11-08 10:44:27.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-12 21:22:06.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-14 03:23:24.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-15 00:48:21.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-17 08:18:17.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-17 08:50:40.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-17 18:47:35.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-18 02:32:25.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-18 02:39:34.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-18 05:16:57.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-20 09:04:16.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-23 12:01:03.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-24 11:15:11.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-24 11:38:33.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-24 19:31:07.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-27 19:41:13.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-28 14:05:35.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-28 14:08:21.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-28 15:22:13.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-29 03:05:46.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos

Go to solution
Samantha_L
Forum Team (Retired)
Forum Team (Retired)
In response to suryamamidala

on ‎04-12-2018 09:45

Hi suryamamidala,

 

Welcome to the community and thanks for posting.

 

I'm sorry to read you are experiencing intermittent connection.

 

From checking your line, everything has come back as fine. There are no faults reported and no time-outs since the router has been online.

 

If you are still having the same issue, can you post an up to date network log please? When this happens do any lights change on the router at all?

 

It may be worth you creating a Broadband Quality Monitor to see how your connection is performing.

 

Let us know how you get on
Sam


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos

Go to solution
suryamamidala
Joining in
In response to Samantha_L

on ‎09-12-2018 09:41

Hi Samantha:

As requested please find the latest network log below. The frequent connection drop out problem still exists.

Network Log

Time Priority Description

2018-11-14 03:23:24.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-15 00:48:21.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-17 08:18:17.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-17 08:50:40.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-17 18:47:35.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-18 02:32:25.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-18 02:39:34.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-18 05:16:57.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-20 09:04:16.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-23 12:01:03.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-24 11:15:11.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-24 11:38:33.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-24 19:31:07.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-27 19:41:13.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-28 14:05:35.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-28 14:08:21.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-28 15:22:13.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-29 03:05:46.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-07 03:51:26.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-12-08 08:24:07.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos

Go to solution
Emma_E
Forum Team (Retired)
Forum Team (Retired)
In response to suryamamidala

on ‎12-12-2018 14:02

Hi suryamamidala,

 

 Thanks for getting in touch. I am sorry to see you have had trouble with your connection.

 

I have taken a look and things seem to be ok from this side. It may help to try the following so we can rule some things out:

 

Pop the hub into Modem Mode with the computer in Safe Mode with Networking at different times of the day.

 

Try on separate devices.

 

Check Ethernet cable. Make sure it is new / up to date. (Cat 5e or above).

 

Make sure device is capable of agreed speed.

 

Check wireless card slide.

 

Take care.

 

 Emma

 


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos

Go to solution
nathanb91
Joining in

on ‎12-12-2018 16:00

Hi,

Sorry to Hijack on this thread but I'm not sure where else to post in order to get a response.

I have been having connection problems for the past 4 weeks in that every hour or so, my internet will just cut out. I've notice a few of the same errors on this post so I"m looking for some help from the team if possible please.

My log is as follows:

Time

Priority

Description

2018-12-11 01:50:50.00

Error

DHCP RENEW sent - No response for IPv4;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-11 02:01:40.00

Error

DHCP REBIND WARNING - Field invalid in response;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-11 07:57:10.00

critical

No Ranging Response received - T3 time-out;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-11 09:38:53.00

Warning!

RCS Partial Service;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 12:13:22.00

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 12:13:22.00

Warning!

RCS Partial Service;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 12:13:22.00

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 12:13:27.00

Warning!

Lost MDD Timeout;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 14:59:18.00

critical

No Ranging Response received - T3 time-out;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 15:00:02.00

critical

Ranging Request Retries exhausted;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 15:00:02.00

critical

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 15:00:09.00

critical

No Ranging Response received - T3 time-out;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 15:00:09.00

critical

Ranging Request Retries exhausted;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 15:00:09.00

critical

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 15:00:10.00

critical

No Ranging Response received - T3 time-out;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 15:00:16.00

critical

Ranging Request Retries exhausted;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 15:00:16.00

critical

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 15:00:17.00

critical

No Ranging Response received - T3 time-out;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

2018-12-12 15:04:09.00

critical

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;

1970-01-01 00:01:39.00

critical

No Ranging Response received - T3 time-out;CM-MAC=**”**”**”**”**”**;CMTS-MAC=**”**”**”**”**”**;CM-QOS=1.1;CM-VER=3.0;

 

Thanks.

0 Kudos

Go to solution
Gethsemane
Superfast
In response to nathanb91

on ‎12-12-2018 17:53

hijacking someone else's thread isn't the done thing...

________________________________________________________________________________

 Has this post helped you out? say thanks by clicking on the Kudos Star.

Smiley Happy

0 Kudos

Go to solution
nathanb91
Joining in
In response to Gethsemane

on ‎12-12-2018 19:04

Well considering numerous other have done so and received a response, I thought I’d try.

Thank you for you input however, and please continue to contribute to society in the same, productive manner.

 

 

0 Kudos

Go to solution
Ron-ski
On our wavelength

on ‎18-08-2019 14:06

Since 1st August we've been having regular drop outs of our connection, sometimes I've had to reboot the SH3, sometimes I've gone to it and seen it's connecting (green internet lights on) so I know it's just negotiated a connection.

My Broadband Ping - Ronski's Virgin CableMy Broadband Ping - Ronski's Virgin CableMy Broadband Ping - Ronski's Virgin Cable

Item Status Comments
Acquired Downstream Channel (Hz)
298750000
Locked
Ranged Upstream Channel (Hz)
39400000
Locked
Provisioning State
Online

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 298750000 -2.5 40 256 qam 21
2 138750000 -2.7 40 256 qam 1
3 146750000 -2.7 40 256 qam 2
4 154750000 -2.7 40 256 qam 3
5 162750000 -2.7 40 256 qam 4
6 170750000 -2.5 38 256 qam 5
7 178750000 -2.4 38 256 qam 6
8 186750000 -2.2 38 256 qam 7
9 194750000 -2 40 256 qam 8
10 202750000 -2.2 40 256 qam 9
11 210750000 -2.2 40 256 qam 10
12 218750000 -2.2 40 256 qam 11
13 226750000 -2.2 40 256 qam 12
14 234750000 -2.2 40 256 qam 13
15 242750000 -2.2 40 256 qam 14
16 250750000 -2.4 40 256 qam 15
17 258750000 -2.5 40 256 qam 16
18 266750000 -2.5 40 256 qam 17
19 274750000 -2.5 40 256 qam 18
20 282750000 -2.5 40 256 qam 19
21 290750000 -2.5 40 256 qam 20
22 306750000 -2.4 40 256 qam 22
23 314750000 -2.2 40 256 qam 23
24 322750000 -2 40 256 qam 24


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.9 18 0
2 Locked 40.9 0 0
3 Locked 40.3 6 0
4 Locked 40.3 4 0
5 Locked 40.3 5 0
6 Locked 38.9 21 0
7 Locked 38.9 18 0
8 Locked 38.9 5 0
9 Locked 40.3 5 0
10 Locked 40.9 18 0
11 Locked 40.3 5 0
12 Locked 40.9 5 0
13 Locked 40.9 5 0
14 Locked 40.9 4 0
15 Locked 40.3 5 0
16 Locked 40.3 6 0
17 Locked 40.3 6 0
18 Locked 40.3 4 0
19 Locked 40.3 5 0
20 Locked 40.9 3 0
21 Locked 40.3 6 0
22 Locked 40.9 4 0
23 Locked 40.3 5 0
24 Locked 40.3 14 0

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39400000 3.75 5120 64 qam 12
2 32600139 3.75 5120 32 qam 13
3 46199976 3.75 5120 64 qam 11
4 53699961 3.75 5120 64 qam 10


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

General Configuration
Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
KDHSUBsgvca69834ncxv9873254k;fg


Primary Downstream Service Flow
SFID 15976
Max Traffic Rate 402500089
Max Traffic Burst 42600
Min Traffic Rate 0


Primary Upstream Service Flow
SFID 15975
Max Traffic Rate 38500089
Max Traffic Burst 42600
Min Traffic Rate 0
Max Concatenated Burst 42600
Scheduling Type BestEffort

Network Log
Time Priority Description
17/08/2019 06:29:57 critical 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;
17/08/2019 07:40:24 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/08/2019 07:42:40 critical 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;
18/08/2019 09:13:25 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 09:16:47 critical 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;
18/08/2019 10:20:44 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 10:20:44 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 10:23:8 critical 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;
18/08/2019 10:23:48 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 10:24:36 critical 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;
18/08/2019 10:25:6 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 10:25:53 critical 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;
18/08/2019 10:26:55 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 10:28:6 critical 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;
18/08/2019 10:28:36 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 10:29:3 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 10:29:3 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 10:29:51 Warning! ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 10:30:11 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 10:31:9 notice Received REG-RSP while in REG-HOLD1 state;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

0 Kudos

Go to solution
Ron-ski
On our wavelength
In response to Ron-ski

on ‎20-08-2019 19:10

With reference to my above post.

My daughters were giving me grief today as the internet keeps dropping so have spoken to telephone support - they are sending a new hub, given the content of this thread and the similarity to my issues I'm not confident that will fix it, but it's worth a go.

0 Kudos
Top