Observer

Constantly getting errors and lossing UPSTREAM connection

I had 2 local visits and a phone call so far with support and techs.  We did fix a few things, there was alot of egress on the line due to a faulty joint on my appartment neighbors line, and i was splilt from them.  I am not not splilt from there and they fixed thier issue.  However it kept report errors on my modem and loosing connection, they claim it was due to a outage issue and fixed it (was either a big coincidence or not related)

 

Now Im typing here with only 1 of the 3 upstream channels working and a redlight on my modem. 

 

Here are the Recent errors from the log and the current data.  As you can see unlike in the past, the downstream is looking very clean. But the upstream is missing a few.

 

2019-8-15, 08:01:12Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:01:39Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.0;CM-VER=3.0;
2019-8-15, 08:01:43Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2019-8-15, 08:02:04Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:02:04Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:03:11Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:03:16Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2019-8-15, 08:03:23Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.0;CM-VER=3.0;
2019-8-15, 08:03:28Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2019-8-15, 08:03:36Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:03:36Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:03:40Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.0;CM-VER=3.0;
2019-8-15, 08:03:46Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.0;CM-VER=3.0;
2019-8-15, 08:04:03Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2019-8-15, 08:04:16Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:04:16Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:05:48Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:06:21Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2019-8-15, 08:06:36Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:06:36Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:06:40Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.0;CM-VER=3.0;
2019-8-15, 08:06:45Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.0;CM-VER=3.0;
2019-8-15, 08:06:57Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2019-8-15, 08:07:11Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:07:11Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:07:15Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.0;CM-VER=3.0;
2019-8-15, 08:07:21Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.0;CM-VER=3.0;
2019-8-15, 08:07:32Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2019-8-15, 08:07:46Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 08:07:46Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;
2019-8-15, 11:03:59Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:f1:fd:68;CMTS-MAC=00:01:5c:7b:9a:67;CM-QOS=1.1;CM-VER=3.0;

 

Acquire Downstream Channel525000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
IP Provisioning ModeIPv6 Onlyipv6Only(1)
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1LockedQAM2561525000000 Hz-0.8 dBmV40.4 dB00
2LockedQAM2562531000000 Hz-0.9 dBmV40.4 dB00
3LockedQAM2563537000000 Hz-1 dBmV40.5 dB130
4LockedQAM2564543000000 Hz-1.1 dBmV40.3 dB00
5LockedQAM2565555000000 Hz-1.4 dBmV40 dB00
6LockedQAM2566561000000 Hz-1.4 dBmV40.2 dB00
7LockedQAM2567567000000 Hz-1.4 dBmV40.2 dB00
8LockedQAM2568573000000 Hz-1.4 dBmV40.1 dB10
9LockedQAM2569579000000 Hz-1.5 dBmV40.1 dB00
10LockedQAM25611591000000 Hz-1.8 dBmV40.1 dB00
11LockedQAM25612597000000 Hz-2 dBmV40 dB00
12LockedQAM25613603000000 Hz-2 dBmV40 dB00
13LockedQAM25616621000000 Hz-2.3 dBmV40 dB00
14LockedQAM25617627000000 Hz-2.4 dBmV39.9 dB10
15LockedQAM25620645000000 Hz-2.5 dBmV39.9 dB00
16LockedQAM25624669000000 Hz-3.2 dBmV39.6 dB10
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1LockedATDMA745120 Ksym/sec24200000 Hz41 dBmV
2 REPLIES 2
Lead Moderator

Re: Constantly getting errors and lossing UPSTREAM connection

Missing channels would require a tech visit. I would suggest first speaking with a customer service agent to see if we are seeing the missing channels on neighboring connections also.

 

If you would like to contact our Social Media Customer Service team to check on that they can be reached at 

 

Twitter: @Ask_Spectrum

Facebook: https://www.facebook.com/Spectrum

 

I would ask for you to specifically ask them to check the number of upstream channels they see. 

 

Regards,

Julia R.

Spectrum-Social Media Customer Service

Lead Moderator-Community Forums

Proven Sharer

Re: Constantly getting errors and lossing UPSTREAM connection

Although you feel that your problem is with the upstream channels, your modem's status report tells a different story.  You'll find several reports of T3 and T4 dropouts, which mark the loss of one or more incoming (downstream) data channels.  They usually involve loose or water-corroded connectors or waterlogged cable which could be either buried or hanging overhead. 

You said you live in a multi-tenant apartment building and that a previous  Spectrum tech found that your cable was cross-connected with another tenant.  If your TV cable or internet service fees are included in your rent, you are not considered to be a residential subscriber by the FCC. 

In the early years of cable TV,  many local cable companies made special deals to obtain exclusive non-competitive access to large multi-unit properties. They required the building owners to pay the cable company to rewire the on-premise cabling if the original (now technically obsolete) RG59 wiring causes problems for viewers.  Although outlawed now, many of those existing contracts are still legally in force today. 

A Spectrum home service tech will first have to determine the cause of your excessively high upstream channel levels.  Then if building rewiring is needed to permanently repair that issue, Spectrum can decide who is financially responsible for the cost of that work.