Forum Discussion

DJGem's avatar
DJGem
New Contributor

Intermittent modem connectivity issues

    I had a tech out on July 17 and was advised that he found such horrible signals on the line for our TV service (we cancelled it a few months ago) that it was bleeding through to the line for our internet; he disconnected the television cable completely. Our internet service worked fine up until July 23rd and the issue has returned. I called tech support and the first person I spoke with simply said "you need a new modem". I called again a little later and was transferred to a tier two tech who checked the poller signals in their system; that tech said there's nothing wrong. I verified that my modem (Motorola SBG6580) has the latest firmware version of SBG6580-3.5.8.4-GA-00-505-NOSH. So right now my modem keeps rebooting itself.

    So I have verified the correct firmware version, Cox says the signals are fine and I have been told to get a new modem. I am still having a tough time believing this is a modem issue to be honest. My modem is slightly warm to the touch but does not feeling like it is getting too hot. I previously worked for an ISP so I have some knowledge about how all of this stuff works. We had a system called fastpoller which allowed us to actively see a modems signals and exactly what the modem was doing. We could see what the download and upload were doing as well. I helped a guy that couldn't figure out why his companies internet was so slow. When I looked at fastpoller I found the problem immediately; I saw that the upstream was completely maxed out and it was slowing everything else down. It turned out that the owner was having all of the store camera's broadcast, through their internet service, directly to his home. So I do have half a clue here.......

    Can anyone tell me what all these Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0 mean?

    I know the CMTS is on the service providers end and the CM is my cable modem. I just want to get the issue fixed because I am one of these crazy "cable cutters" and have two Google Chromcast's that are worthless with my internet constantly going out.

Current signal levels:

Downstream Bonded Channels

Channel

Lock Status

Modulation

Channel ID

Frequency

Power

SNR

Correctables

Uncorrectables

1

Locked

QAM256

33

849000000 Hz

4.8 dBmV

38.0 dB

338

0

2

Locked

QAM256

34

855000000 Hz

5.2 dBmV

37.9 dB

253

0

3

Locked

QAM256

35

861000000 Hz

5.0 dBmV

37.9 dB

353

0

4

Locked

QAM256

36

867000000 Hz

4.6 dBmV

37.9 dB

478

0

5

Locked

QAM256

37

873000000 Hz

4.7 dBmV

38.0 dB

376

0

6

Locked

QAM256

38

879000000 Hz

5.4 dBmV

38.8 dB

394

0

7

Locked

QAM256

39

885000000 Hz

5.3 dBmV

38.9 dB

457

0

8

Locked

QAM256

40

891000000 Hz

5.0 dBmV

38.8 dB

392

0

 

Upstream Bonded Channels

Channel

Lock Status

US Channel Type

Channel ID

Symbol Rate

Frequency

Power

1

Locked

ATDMA

3

5120 Ksym/sec

29800000 Hz

42.5 dBmV

2

Locked

TDMA and ATDMA

1

2560 Ksym/sec

18400000 Hz

42.5 dBmV

3

Locked

ATDMA

2

5120 Ksym/sec

23300000 Hz

42.5 dBmV

4

Locked

ATDMA

4

5120 Ksym/sec

36300000 Hz

42.5 dBmV

Here is an internal modem  log from just today:

 Fri Jul 29 13:44:17 2016  

 Notice (6) 

 TLV-11 - unrecognized OID;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Time Not Established 

 Warning (5) 

 DHCP WARNING - Non-critical field invalid in response ;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.0;CM-VER=3.0; 

 Time Not Established 

 Critical (3) 

 No Ranging Response received - T3 time-out  

 Fri Jul 29 12:45:48 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:27 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:25 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:24 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:21 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:20 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:20 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:16 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:16 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:13 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:08 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:05 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:02 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:44:01 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:58 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:55 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:55 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:52 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:47 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:46 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:45 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:41 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:41 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:39 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:39 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:36 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:33 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:31 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:30 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:30 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:30 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:29 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:29 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:26 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:24 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:24 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:23 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:21 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:19 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:19 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:17 2016  

 Critical (3) 

 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:17 2016  

 Critical (3) 

 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:17 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:17 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:17 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:15 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:15 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:14 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:14 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:13 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:13 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:12 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:12 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:10 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:10 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:09 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:07 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:05 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:04 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:03 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:01 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:43:00 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:59 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:58 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:58 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:57 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:57 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:56 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:53 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:52 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:48 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:47 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:44 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:44 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:40 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:40 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:36 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:35 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:33 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:32 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:28 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:28 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:26 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:23 2016  

 Critical (3) 

 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; 

 Fri Jul 29 12:42:19 2016  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0;

3 Replies

Replies have been turned off for this discussion
  • ChrisL's avatar
    ChrisL
    Former Moderator
    @DJGem

    A T3 error indicates a 200ms interruption in upstream communication from the modem back to us. Most likely this is a signal issue of some kind although it could be a modem. I did see where a previous tech mentioned they were seeing an ingress issue at your location which would fit with what you're seeing. It may be time to have another tech come back out and investigate further what could be going on.

  • DJGem's avatar
    DJGem
    New Contributor

    Chris,

        Thank you for your response. I have done a little research online today and found some information that will have me calling tech support again today.

        "T3 timeouts are almost always caused by not getting a correct upstream signal returned. It's almost always caused by noise on the line (possibly someone's messed up connection up the line causing issues for other customers), a bad amplifier or a bad tap. And yes, a lot of the time the signal levels show fine when tested. Then the problem comes right back at certain times of the day, maybe when there's more activity from the customer up the line causing the issue, maybe when the temps change."

    My current signals look fine right now but that will probably change when it starts cooling off a little later tonight.

  • EdwardH's avatar
    EdwardH
    Valued Contributor
    We may be able to drill down on it a little more knowing the time frames you see the issues, if its a temperature issue there may be damaged shielding on the line somewhere outside causing it to see the noise bleed onto the line, or there may be something else going on if the time frames are different. We can pull the logs at general points of day but knowing when it happens will narrow that down for us.

    ---