Community Forum

Error on Netgear device: Started Unicast Maintenance Ranging - No Response received - T3 time-out

Ryan3030
Regular Visitor

Error on Netgear device: Started Unicast Maintenance Ranging - No Response received - T3 time-out

 

I am losing my internet connectivity on a daily basis, multiple times a day,  from my Xfinity  400 package.  On average, from a couple of minutes up to an hour. with 10 dropped signals at various times, throughout today.   This problem started at the beginning of the year and is progressively get worse on a daily basis. 

 

Xfinity came out for a service call yesterday.  The service technician ran several diagnostic tests from the inside of the house and the tested numbers are within the acceptable range of tolerance.  

 

I have the Netgear CM1150v V4.02.02 that works flawlessly since it was purchased. From the pole to the house, there no splitters attached.  Several years ago Xfinity installed a 5 Port signal booster splitter PPC EV01-5-U/U 

Again, no problems until this year.  I have enclosed my stats and error logs for review and comment. 

 

The log files below denote the following critical errors  

 

  • Started Unicast Maintenance Ranging - No Response received - T3
  • No Ranging Response received - T3 time-out
  • SYNC Timing Synchronization failure
  • No Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities Ranging Response received - T3 time-out

 

 

I need some help with my Xfinity dropping connection and I appreciate any assistance.  

 

 

 

Frequency start Value

This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.

Starting Frequency

Startup Procedure

Procedure

Status

Comment

Acquire Downstream Channel

579000000 Hz

Locked

Connectivity State

OK

Operational

Boot State

OK

Operational

Security

Enabled

BPI+

IP Provisioning Mode

Honor MDD

honorMdd(4)

Downstream Bonded Channels

Channel

Lock Status

Modulation

Channel ID

Frequency

Power

SNR

Correctables

Uncorrectables

1

Locked

QAM256

21

579000000 Hz

6.1 dBmV

38.9 dB

0

0

2

Locked

QAM256

6

483000000 Hz

5.9 dBmV

39.4 dB

0

0

3

Locked

QAM256

7

489000000 Hz

5.9 dBmV

39.3 dB

28

0

4

Locked

QAM256

8

495000000 Hz

6 dBmV

39.2 dB

32

1

5

Locked

QAM256

9

507000000 Hz

6.2 dBmV

39.3 dB

28

0

6

Locked

QAM256

10

513000000 Hz

6.1 dBmV

39.3 dB

1

0

7

Locked

QAM256

11

519000000 Hz

6.2 dBmV

39.3 dB

0

0

8

Locked

QAM256

12

525000000 Hz

6.2 dBmV

39.2 dB

0

0

9

Locked

QAM256

13

531000000 Hz

6.3 dBmV

39.3 dB

0

0

10

Locked

QAM256

14

537000000 Hz

6.3 dBmV

39.2 dB

0

0

11

Locked

QAM256

15

543000000 Hz

6.3 dBmV

39.2 dB

0

0

12

Locked

QAM256

16

549000000 Hz

6.3 dBmV

39.2 dB

0

0

13

Locked

QAM256

17

555000000 Hz

6.3 dBmV

39.1 dB

0

0

14

Locked

QAM256

18

561000000 Hz

6.3 dBmV

39 dB

0

0

15

Locked

QAM256

19

567000000 Hz

6.2 dBmV

39 dB

0

0

16

Locked

QAM256

20

573000000 Hz

6.2 dBmV

38.9 dB

0

0

17

Locked

QAM256

22

585000000 Hz

6.2 dBmV

38.8 dB

0

0

18

Locked

QAM256

23

591000000 Hz

6.1 dBmV

38.8 dB

0

0

19

Locked

QAM256

24

597000000 Hz

6.2 dBmV

38.8 dB

0

0

20

Locked

QAM256

25

603000000 Hz

6.1 dBmV

38.7 dB

0

0

21

Locked

QAM256

26

609000000 Hz

6.1 dBmV

38.6 dB

0

0

22

Locked

QAM256

27

615000000 Hz

6 dBmV

38.5 dB

0

0

23

Locked

QAM256

28

621000000 Hz

6 dBmV

38.6 dB

0

0

24

Locked

QAM256

29

627000000 Hz

6 dBmV

38.5 dB

1

0

25

Locked

QAM256

30

633000000 Hz

6.1 dBmV

38.6 dB

0

0

26

Locked

QAM256

31

639000000 Hz

5.9 dBmV

38.5 dB

0

0

27

Locked

QAM256

32

645000000 Hz

6.1 dBmV

38.6 dB

0

0

28

Locked

QAM256

33

651000000 Hz

6 dBmV

38.4 dB

0

0

29

Locked

QAM256

34

657000000 Hz

5.9 dBmV

38.3 dB

0

0

30

Locked

QAM256

35

663000000 Hz

5.8 dBmV

38.2 dB

0

0

31

Locked

QAM256

36

669000000 Hz

5.9 dBmV

38.2 dB

0

0

32

Not Locked

Unknown

0

0 Hz

0.0 dBmV

0.0 dB

0

0

Upstream Bonded Channels

Channel

Lock Status

US Channel Type

Channel ID

Symbol Rate

Frequency

Power

1

Locked

ATDMA

1

5120 Ksym/sec

35600000 Hz

41 dBmV

2

Locked

ATDMA

2

5120 Ksym/sec

29200000 Hz

41.8 dBmV

3

Locked

ATDMA

3

5120 Ksym/sec

22800000 Hz

42.3 dBmV

4

Locked

ATDMA

4

5120 Ksym/sec

16400000 Hz

42.5 dBmV

5

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

6

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

7

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

8

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

Downstream OFDM Channels

Channel

Lock

Status

Modulation /

Profile ID

Channel

ID

Frequency

Power

SNR /

MER

Active Subcarrier

Number Range

Unerrored

Codewords

Correctable

Codewords

Uncorrectable

Codewords

1

Locked

0 ,1 ,2 ,3

37

722000000 Hz

6.2 dBmV

37.6 dB

1228 ~ 2867

2080859646

2043288292

0

2

Not Locked

0

0

0 Hz

0 dBmV

0.0 dB

0 ~ 4095

0

0

0

Upstream OFDMA Channels

Channel

Lock Status

Modulation / Profile ID

Channel ID

Frequency

Power

1

Not Locked

0

0

0 Hz

0 dBmV

2

Not Locked

0

0

0 Hz

0 dBmV

 

 

 
Ryan3030
Regular Visitor

Re: Error on Netgear device: Started Unicast Maintenance Ranging - No Response received - T3 time-ou

 

 

Event Log

 

Time

Priority

Description

Thu Feb 11 20:49:58 2021

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:54:02 2021

Notice (6)

CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:53:48 2021

Notice (6)

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:53:43 2021

Notice (6)

TLV-11 - unrecognized OID;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:45:11 2021

Notice (6)

CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:44:58 2021

Notice (6)

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:44:53 2021

Notice (6)

TLV-11 - unrecognized OID;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:23:52 2021

Notice (6)

CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:23:38 2021

Notice (6)

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:23:33 2021

Notice (6)

TLV-11 - unrecognized OID;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:21:17 2021

Notice (6)

CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:21:05 2021

Notice (6)

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:21:04 2021

Notice (6)

TLV-11 - unrecognized OID;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:21:10 2021

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

Tue Feb 09 14:21:01 2021

Warning (5)

Lost MDD Timeout;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:20:54 2021

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:16:52 2021

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:16:52 2021

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:16:46 2021

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:16:46 2021

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:16:40 2021

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:16:39 2021

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:15:42 2021

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:15:41 2021

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:13:32 2021

Warning (5)

MDD message timeout;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:13:30 2021

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:13:23 2021

Notice (6)

CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 14:13:22 2021

Notice (6)

CM-STATUS message sent. Event Type Code: 20; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Tue Feb 09 13:57:39 2021

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 08 23:59:49 2021

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 08 23:59:41 2021

Notice (6)

CM-STATUS message sent. Event Type Code: 23; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 08 23:59:41 2021

Notice (6)

CM-STATUS message sent. Event Type Code: 22; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=78:d2:94:59:93:70;CMTS-MAC=00:01:5c:64:f0:79;CM-QOS=1.1;CM-VER=3.1;

 

EG
Expert

Re: Error on Netgear device: Started Unicast Maintenance Ranging - No Response received - T3 time-ou

The signal stats are o/k but the error log entries indicate that something is going on. Perhaps there is noise ingress into the line(s) somewhere.

 

There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.

 

I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS to see whether or not everything is in the green zone, see your node / cable plant and modem health, and also see a history plot for the modem. You should get a reply here in your topic. Good luck !



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Ryan3030
Regular Visitor

Re: Error on Netgear device: Started Unicast Maintenance Ranging - No Response received - T3 time-ou

Thank you!

EG
Expert

Re: Error on Netgear device: Started Unicast Maintenance Ranging - No Response received - T3 time-ou

My pleasure !



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Ryan3030
Regular Visitor

Re: Error on Netgear device: Started Unicast Maintenance Ranging - No Response received - T3 time-ou

Any luck or updates?   My internet is up and down like a yo-yo. 

 

Thank you, 

EG
Expert

Re: Error on Netgear device: Started Unicast Maintenance Ranging - No Response received - T3 time-ou

I can't know what happens after I escalate something, sorry. I can however try re-escalating this.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!