Observer

Upstream signal woes

Issues started about a week and a half ago. I moved my modem across the room. Same cables, same modem. Upstream would not lock after reconnecting the modem. After three service appointments and four different cable modems over the week (and no internet), things finally settled down last Saturday. Sadly, the issues came back today. Upstream keeps dropping to one channel. It is raining, that's about the only thing that's 'new' since before.

Support has always insisted that its my modem, since I refuse to use one provided by Spectrum. The CM600 is on the approved list. I cannot believe after four modems in one week that the evidence supports that theory. Every time a tech comes out, they report nothing found on the lines. The intermittent nature of the signal drops really makes this hard to catch and prove to TWC. Power cycling and pulling the coaxial cable usually remedies the issue: for 10 min to a few hours. I swear it's an intermittent line issue, but I can't get any response other than 'it is you' from Spectrum. Gotta be better tools in place on their end or that I can apply to prove my case, but they just want to kick the can down the road. Just want the service that I pay for to work as advertised...

 9617890b-520e-454d-ac32-abda19c7a742.png

b99baa1e-9eb6-4cae-baa9-ca8e3a09d747.png05eff7f6-6932-440d-997d-4dab4a70d9ab.png95da8035-86fa-43e6-b8d8-64ff8a52f7cf.png

21 REPLIES
Expert

Re: Upstream signal woes

Copy and paste the modem signal and error log pages, We can't see what's in the yellow triangles.... snapshots DO NOT work in the forum

 

 

Observer

Re: Upstream signal woes

Didn't realize that the forum would be so draconian as to not allow posting a screenshot of the appopriate windows. Incoming text spam. I just dropped again a few moments ago after nearly getting a full day:

 

TimePriorityDescription
2017-12-09, 21:29:39Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-09, 21:29:06Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 23:48:03Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 23:48:01Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 23:47:57Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 23:47:47Critical (3)No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 23:46:59Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 23:46:26Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 19:31:03Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 19:30:51Critical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 19:30:36Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 19:30:05Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 19:30:05Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 19:30:05Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 19:30:05Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 19:30:05Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 19:30:05Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 19:27:08Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 19:27:06Critical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 19:26:49Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 19:26:17Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 18:31:13Critical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 18:30:00Critical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 18:29:45Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 18:29:12Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 18:03:01Critical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 18:02:52Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 18:02:19Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 17:35:37Critical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 17:35:21Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 17:34:49Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 17:18:26Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 17:17:50Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 17:17:26Critical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
2017-12-08, 17:17:17Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 17:16:45Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
2017-12-08, 15:21:41Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedNotice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

 

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel603000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnableBPI+
IP Provisioning ModeOverride MDDIPv6 only
 
<tabindex=-1>Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM25625603000000 Hz0.0 dBmV40.2 dB726
2LockedQAM25610513000000 Hz-4.6 dBmV38.7 dB00
3LockedQAM25611519000000 Hz-5.9 dBmV37.9 dB00
4LockedQAM25612525000000 Hz-5.7 dBmV37.9 dB00
5LockedQAM25613531000000 Hz-6.0 dBmV37.6 dB00
6LockedQAM25614537000000 Hz-5.0 dBmV38.0 dB00
7LockedQAM25615543000000 Hz-4.3 dBmV38.7 dB00
8LockedQAM25616549000000 Hz-3.5 dBmV39.0 dB00
9LockedQAM25617555000000 Hz-2.1 dBmV39.6 dB00
10LockedQAM25618561000000 Hz-1.6 dBmV39.8 dB00
11LockedQAM25619567000000 Hz-0.5 dBmV40.2 dB00
12LockedQAM25620573000000 Hz-1.1 dBmV39.9 dB00
13LockedQAM25621579000000 Hz-1.0 dBmV40.0 dB00
14LockedQAM25622585000000 Hz-0.7 dBmV40.0 dB00
15LockedQAM25623591000000 Hz-0.5 dBmV40.1 dB00
16LockedQAM25624597000000 Hz0.2 dBmV40.2 dB00
17LockedQAM2569507000000 Hz-4.8 dBmV39.0 dB00
18LockedQAM25626609000000 Hz0.2 dBmV41.4 dB00
19LockedQAM25627615000000 Hz0.9 dBmV41.8 dB00
20LockedQAM25628621000000 Hz1.1 dBmV41.9 dB00
21LockedQAM25629627000000 Hz0.9 dBmV41.4 dB00
22LockedQAM25630633000000 Hz-0.2 dBmV40.8 dB00
23LockedQAM25631639000000 Hz0.5 dBmV41.3 dB00
24LockedQAM25632645000000 Hz0.7 dBmV41.3 dB00
 
<tabindex=-1>Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA25120 Ksym/sec24200000 Hz39.0 dBmV
2LockedTDMA12560 Ksym/sec19400000 Hz37.0 dBmV
3LockedATDMA35120 Ksym/sec30600000 Hz39.0 dBmV
4LockedATDMA42560 Ksym/sec37000000 Hz39.0 dBmV
5Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
6Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
7Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
8Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
 
Current System Time: Sat Dec 09 21:34:21 2017 

 

Proven Sharer

Re: Upstream signal woes


@turboska5 wrote:

Didn't realize that the forum would be so draconian as to not allow posting a screenshot of the appopriate windows. Incoming text spam. I just dropped again a few moments ago after nearly getting a full day:

 

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel603000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnableBPI+
IP Provisioning ModeOverride MDDIPv6 only
 
<tabindex=-1>Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM25625603000000 Hz0.0 dBmV40.2 dB726
2LockedQAM25610513000000 Hz-4.6 dBmV38.7 dB00
3LockedQAM25611519000000 Hz-5.9 dBmV37.9 dB00
4LockedQAM25612525000000 Hz-5.7 dBmV37.9 dB00
5LockedQAM25613531000000 Hz-6.0 dBmV37.6 dB00
6LockedQAM25614537000000 Hz-5.0 dBmV38.0 dB00
7LockedQAM25615543000000 Hz-4.3 dBmV38.7 dB00
8LockedQAM25616549000000 Hz-3.5 dBmV39.0 dB00
9LockedQAM25617555000000 Hz-2.1 dBmV39.6 dB00
10LockedQAM25618561000000 Hz-1.6 dBmV39.8 dB00
11LockedQAM25619567000000 Hz-0.5 dBmV40.2 dB00
12LockedQAM25620573000000 Hz-1.1 dBmV39.9 dB00
13LockedQAM25621579000000 Hz-1.0 dBmV40.0 dB00
14LockedQAM25622585000000 Hz-0.7 dBmV40.0 dB00
15LockedQAM25623591000000 Hz-0.5 dBmV40.1 dB00
16LockedQAM25624597000000 Hz0.2 dBmV40.2 dB00
17LockedQAM2569507000000 Hz-4.8 dBmV39.0 dB00
18LockedQAM25626609000000 Hz0.2 dBmV41.4 dB00
19LockedQAM25627615000000 Hz0.9 dBmV41.8 dB00
20LockedQAM25628621000000 Hz1.1 dBmV41.9 dB00
21LockedQAM25629627000000 Hz0.9 dBmV41.4 dB00
22LockedQAM25630633000000 Hz-0.2 dBmV40.8 dB00
23LockedQAM25631639000000 Hz0.5 dBmV41.3 dB00
24LockedQAM25632645000000 Hz0.7 dBmV41.3 dB00
 
<tabindex=-1>Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA25120 Ksym/sec24200000 Hz39.0 dBmV
2LockedTDMA12560 Ksym/sec19400000 Hz37.0 dBmV
3LockedATDMA35120 Ksym/sec30600000 Hz39.0 dBmV
4LockedATDMA42560 Ksym/sec37000000 Hz39.0 dBmV
5Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
6Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
7Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
8Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
 
Current System Time: Sat Dec 09 21:34:21 2017 

 

 

Sorry, but it's not the users enforcing stupid rules; it's simply that the screenshot function doesn't work.  The forum volunteers have to be able to read the diagnosic messages retrieved from the modem's signal and event reports to predict what might be wrong at your location. 

 

The problem appears to be uneven incoming (DS) signal levels, often caused by a sloppy system maintenance and/or water in the drop cable.  Levels of individual channels MUST all be within 3 dBmV from highest (strongest) to weakest.  Your modem reports that its 'home' channel DS25 at 603 MHz is strongest at 0.0 dBmV, while other assigned DS channels range from channel DS28 at 621 MHz strongest at +1.1 dBmV to channel DS13 at 631 MHz weakest at -6.8 dBmV. 

 

VERDICT:  You need a line maintenance crew out there to recalibrate the inline trunk amplifiers along your street.  Home service techs aren't allowed to do that work, but they can write a service request ticket to get the properly trained line maintenance crews out there. 

 

NOTE:  The Spectrum folks staffing the phone and chat help desks cannot do anything for you except to make the initial home service appointment.  Do NOT let them reset your modem, that will erase data in the event and signal level logs. 

Lead Moderator

Re: Upstream signal woes

Good morning.

 

The majority of us are able to see your screen shot. Unsure why MsRaye  is not 

able to see those.

 

We will review the settings from this side. @MsRaye if after Monday afternoon 

you are still unable to view the screen shots please let us know via PM.

 

Any others not able to post or view those please contact us. 

 

Thank you!

 

Observer

Re: Upstream signal woes

Problems peristing. The issue seems to be when the correctables and uncorrectables counts jump from zero:

 

Startup Procedure

Procedure

Status

Comment

Acquire Downstream Channel

603000000 Hz

Locked

Connectivity State

OK

Operational

Boot State

OK

Operational

Security

Enable

BPI+

IP Provisioning Mode

Override MDD

IPv6 only

 

Downstream Bonded Channels

Channel

Lock Status

Modulation

Channel ID

Frequency

Power

SNR

Correctables

Uncorrectables

1

Locked

QAM256

25

603000000 Hz

-0.2 dBmV

40.0 dB

14

21

2

Locked

QAM256

10

513000000 Hz

-5.2 dBmV

38.1 dB

12

25

3

Locked

QAM256

11

519000000 Hz

-6.4 dBmV

37.3 dB

10

27

4

Locked

QAM256

12

525000000 Hz

-5.7 dBmV

37.8 dB

8

29

5

Locked

QAM256

13

531000000 Hz

-5.4 dBmV

37.9 dB

7

30

6

Locked

QAM256

14

537000000 Hz

-4.3 dBmV

38.4 dB

19

18

7

Locked

QAM256

15

543000000 Hz

-4.1 dBmV

38.8 dB

8

28

8

Locked

QAM256

16

549000000 Hz

-3.5 dBmV

38.9 dB

17

20

9

Locked

QAM256

17

555000000 Hz

-2.0 dBmV

39.4 dB

15

84

10

Locked

QAM256

18

561000000 Hz

-1.2 dBmV

39.8 dB

19

18

11

Locked

QAM256

19

567000000 Hz

-0.1 dBmV

40.1 dB

5

30

12

Locked

QAM256

20

573000000 Hz

-1.2 dBmV

39.7 dB

6

29

13

Locked

QAM256

21

579000000 Hz

-1.3 dBmV

39.8 dB

12

25

14

Locked

QAM256

22

585000000 Hz

-0.5 dBmV

39.9 dB

8

30

15

Locked

QAM256

23

591000000 Hz

0.0 dBmV

40.0 dB

8

28

16

Locked

QAM256

24

597000000 Hz

0.5 dBmV

40.1 dB

9

26

17

Locked

QAM256

9

507000000 Hz

-5.1 dBmV

39.0 dB

0

0

18

Locked

QAM256

26

609000000 Hz

0.4 dBmV

41.4 dB

0

0

19

Locked

QAM256

27

615000000 Hz

1.7 dBmV

41.4 dB

0

0

20

Locked

QAM256

28

621000000 Hz

1.9 dBmV

41.9 dB

0

0

21

Locked

QAM256

29

627000000 Hz

1.3 dBmV

41.2 dB

0

0

22

Locked

QAM256

30

633000000 Hz

0.1 dBmV

40.8 dB

0

0

23

Locked

QAM256

31

639000000 Hz

1.2 dBmV

41.1 dB

0

0

24

Locked

QAM256

32

645000000 Hz

1.6 dBmV

41.1 dB

0

0

 

Upstream Bonded Channels

Channel

Lock Status

US Channel Type

Channel ID

Symbol Rate

Frequency

Power

1

Locked

ATDMA

2

5120 Ksym/sec

24200000 Hz

41.0 dBmV

2

Locked

TDMA

1

2560 Ksym/sec

19400000 Hz

39.5 dBmV

3

Locked

ATDMA

3

5120 Ksym/sec

30600000 Hz

40.8 dBmV

4

Locked

ATDMA

4

2560 Ksym/sec

37000000 Hz

40.8 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

 

 

Observer

Re: Upstream signal woes

 

Time

Priority

Description

2017-12-11, 13:40:53

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:39:52

Error (4)

Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:39:52

Error (4)

Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:37:57

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:37:24

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:25:53

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

2017-12-11, 13:25:42

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:25:09

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:18:59

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

2017-12-11, 13:18:41

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:18:09

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:15:56

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

2017-12-11, 13:15:43

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:15:10

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:13:20

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

2017-12-11, 13:13:06

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:12:33

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:09:25

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

2017-12-11, 13:09:20

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

2017-12-11, 13:09:08

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 13:08:35

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 08:10:10

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

2017-12-11, 08:09:55

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 08:09:23

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 05:59:39

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 05:59:07

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 05:59:03

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-11, 05:59:01

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-10, 17:01:56

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

2017-12-10, 17:01:47

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-10, 17:01:15

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-10, 09:53:49

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-10, 09:53:23

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

2017-12-10, 09:53:15

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-10, 09:52:42

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-09, 21:58:39

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-09, 21:58:07

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.0;CM-VER=3.0;

2017-12-09, 21:57:51

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

2017-12-09, 21:57:18

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f4:b4:d1;CMTS-MAC=00:17:10:8b:6b:14;CM-QOS=1.1;CM-VER=3.0;

 

Please advise. Lost connection 5 times in the last hour, and this makes working from home nigh impossible.

Expert

Re: Upstream signal woes

This could be an open splitter port  or chewed up outside line or loose/ corroded connections.

 Everything must be shiny and a tad more than finger tight.

 

Observer

Re: Upstream signal woes

Respectfully, I've examined and retightened the coaxial cable five ways to Sunday. After four new cable modems over a week, it's gotta be a line problem. Are there no tools I can run in the background (or Spectrum for that matter) to gather diagnostics for when this spottiness recurs? I hate haveing to roll the dice when a tech come out, only to not be able to reproduce the issue in the small window they are present.

 

It seems archaic to just keep chewing up support bandwidth by pestering Spectrum for service calls until they finally escalate, but if that's the game I have to play, I guess I'll redial every hour tomorrow until this situation is resolved. Two weeks is about 1.5 too long. Really sucks when they are the ONLY game in town.

Proven Sharer

Re: Upstream signal woes

Well, you COULD agree to use the FREE Spectrum modem, which will blow up their present excuse for your poor service.  Then they will be forced to stop blaming your modem and send out service people to fix the cabling issues in their network.  Plus you can rub their nose in it by getting a credit for all the time the internet service is not working.