Highlighted
Participant

A connectivity puzzle for MsRaye ...

Dear MsRaye, You were very helpful at Christmas with my connectivity problem, thank you.  I got a new drop, a new modem/router (Netgear C7000-100NAS), new splitters, new ground plug - had 3 good months, then it started up again: intermittent outages, mostly at night, with the download LED on and the upload light flashing.  Yesterday the tech came out, checked the pole, changed the connectors and said the signal's good, could be your modem/router - but we got lucky and had an outage while his meter was still connected before the grounding plug: no upload, and no upload from the two splitters between the ground and the modem.    He went back up the pole and changed the connector on the tap,  problem solved - but today it's back!  So (I think) my equipment and wiring is exonerated.  The problem could be the tap - but the tech said there's 7 others besides you on that tap, if it's bad why aren't the others complaining?  So my questions are: could it be the central office equipment that's faulty?  What other possible explanations are there?  And of course:  What should I do now?  Thanks in anticipation!    

10 REPLIES
Expert

Re: A connectivity puzzle for MsRaye ...

The tap is simply a directional coupler and 8 way splitter. It could have bad contacts on a single connector, Needs the bucket truck guys out to replace it as well as all the other customers connectors on that tap uff block.

Hopefully this is an 8 port and not a 4 port with a bunch of loose splitters, if that's the case, it needs to be replaced with an 8 port and levels at the upstream amp corrected.

 

 Are you seeing levels change, either down or upstream? Are the upstream levels over +50 dBmv?

 

 Post the page

Post the log, don't reset it.

 

Participant

Re: A connectivity puzzle for MsRaye ...

The tap is 8-port, levels all seem in range when I check them, right now all four upstream  are north of 44.5 dBmv, all downstream are between -2.9 and -4.4 dBmv

Participant

Re: A connectivity puzzle for MsRaye ...

1LockedQAM25624657000000 Hz-2.8 dBmV41.7 dB17184733
2LockedQAM2569567000000 Hz-3.2 dBmV42.1 dB19355413
3LockedQAM25610573000000 Hz-3.2 dBmV42.1 dB18785272
4LockedQAM25611579000000 Hz-3.6 dBmV41.8 dB19515142
5LockedQAM25612585000000 Hz-3.4 dBmV41.9 dB17665162
6LockedQAM25613591000000 Hz-3.4 dBmV41.7 dB19175239
7LockedQAM25614597000000 Hz-3.7 dBmV41.5 dB18325150
8LockedQAM25615603000000 Hz-3.5 dBmV41.6 dB17385051
9LockedQAM25616609000000 Hz-3.4 dBmV41.7 dB19154849
10LockedQAM25617615000000 Hz-3.2 dBmV41.5 dB18964858
11LockedQAM25618621000000 Hz-3.1 dBmV41.3 dB18704810
12LockedQAM25619627000000 Hz-3.1 dBmV41.7 dB19354473
13LockedQAM25620633000000 Hz-2.9 dBmV41.7 dB18064583
14LockedQAM25621639000000 Hz-2.9 dBmV41.5 dB16704621
15LockedQAM25622645000000 Hz-2.5 dBmV42 dB19014557
16LockedQAM25623651000000 Hz-2.5 dBmV42 dB16664481
17LockedQAM25625663000000 Hz-2.8 dBmV43.2 dB16715536
18LockedQAM25626669000000 Hz-3 dBmV43.2 dB17765585
19LockedQAM25627675000000 Hz-3.3 dBmV42.5 dB17705508
20LockedQAM25628681000000 Hz-3.3 dBmV42.6 dB9092969
21LockedQAM25629687000000 Hz-3.7 dBmV42.5 dB18465424
22LockedQAM25630693000000 Hz-3.8 dBmV42.5 dB17925620
23LockedQAM25631699000000 Hz-4.1 dBmV42.5 dB19825549
24LockedQAM25632705000000 Hz-4.4 dBmV41.9 dB17105729
 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA505120 Ksym/sec23300000 Hz44.5 dBmV
2LockedTDMA492560 Ksym/sec18500000 Hz44.5 dBmV
3LockedATDMA515120 Ksym/sec30600000 Hz44.7 dBmV
4LockedATDMA525120 Ksym/sec37000000 Hz45.1 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
Participant

Re: A connectivity puzzle for MsRaye ...

Event log:

2017-4-6, 21:11:26Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:11:27Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:11:30Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:11:34Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-4-6, 21:11:36Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-4-6, 21:11:59Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-4-6, 21:12:04Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.0;CM-VER=3.0;
2017-4-6, 21:12:16Notice (6)Honoring MDD; IP provisioning mode = IPv4
2017-4-6, 21:12:22Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:12:22Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:12:22Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:17Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:20Warning (5)MDD message timeout;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:26Warning (5)MDD message timeout;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:28Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:28Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:36Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:44Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:45Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:48Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:43:52Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-4-6, 21:43:54Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-4-6, 21:44:07Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.0;CM-VER=3.0;
2017-4-6, 21:44:09Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.0;CM-VER=3.0;
2017-4-6, 21:44:10Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.0;CM-VER=3.0;
2017-4-6, 21:44:16Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.0;CM-VER=3.0;
2017-4-6, 21:44:18Notice (6)Honoring MDD; IP provisioning mode = IPv4
2017-4-6, 21:44:21Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:44:21Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:44:21Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:46:20Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:46:24Warning (5)MDD message timeout;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:46:25Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:46:30Warning (5)MDD message timeout;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:46:31Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:46:31Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
2017-4-6, 21:56:51Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6f:d5:28;CMTS-MAC=00:01:5c:6a:76:58;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: A connectivity puzzle for MsRaye ...

Looks like the levels are a couple dB better than December. but if those correcteds/ uncorrecteds are since the reset, you've got a noise ingress issue or there's a bad amplifier somewhere down the street.

Here's the 2016 #'s

ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM25624657000000 Hz-5.9 dBmV40.9 dB5061641
2LockedQAM2569567000000 Hz-6.1 dBmV41.5 dB00
3LockedQAM25610573000000 Hz-6.1 dBmV41.3 dB00
4LockedQAM25611579000000 Hz-6.4 dBmV41.2 dB00
5LockedQAM25612585000000 Hz-6.2 dBmV41.3 dB00
6LockedQAM25613591000000 Hz-6.3 dBmV41.1 dB00
7LockedQAM25614597000000 Hz-6.5 dBmV40.8 dB00
8LockedQAM25615603000000 Hz-6.3 dBmV40.9 dB00
9LockedQAM25616609000000 Hz-6.3 dBmV41 dB00
10LockedQAM25617615000000 Hz-6.2 dBmV40.9 dB00
11LockedQAM25618621000000 Hz-6 dBmV40.9 dB00
12LockedQAM25619627000000 Hz-5.9 dBmV41 dB00
13LockedQAM25620633000000 Hz-5.8 dBmV41.2 dB00
14LockedQAM25621639000000 Hz-5.9 dBmV40.7 dB00
15LockedQAM25622645000000 Hz-5.6 dBmV41.2 dB00
16LockedQAM25623651000000 Hz-5.7 dBmV41.1 dB00
17LockedQAM25625663000000 Hz-5.9 dBmV42.5 dB00
18LockedQAM25626669000000 Hz-5.8 dBmV42.5 dB00
19LockedQAM25627675000000 Hz-6.1 dBmV41.9 dB653
20LockedQAM25628681000000 Hz-5.9 dBmV41.9 dB00
21LockedQAM25629687000000 Hz-6.3 dBmV41.9 dB00
22LockedQAM25630693000000 Hz-6.3 dBmV41.9 dB00
23LockedQAM25631699000000 Hz-6.6 dBmV41.9 dB00
24LockedQAM25632705000000 Hz-7 dBmV41.6 dB00
 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA505120 Ksym/sec23300000 Hz47.4 dBmV
2LockedTDMA492560 Ksym/sec18500000 Hz47.4 dBmV
3LockedATDMA515120 Ksym/sec30600000 Hz47.9 dBmV
4LockedATDMA525120 Ksym/sec37000000 Hz48.6 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:Wed Dec 14 21:06:57 2016

 

 

 
 
Sharer

Re: A connectivity puzzle for MsRaye ...


Jonty2 wrote:

  The problem could be the tap - but the tech said there's 7 others besides you on that tap, if it's bad why aren't the others complaining?  


I hate this argument from techs. If your neighbors are anything like my dad they may be experiencing the problems and never complain about it but instead have learned to live with it. Up until last week he had Uverse and it would experience intermittent outages for minutes at a time... for 5 years. Never once did he call to complain.

Participant

Re: A connectivity puzzle for MsRaye ...

Now you come tomention it we're all pretty eccentric on my street, would surprise me at all if no one called tech support in spite of problems!  Maybe because it's such fun calling tech support hahahahhahahha - not

Participant

Re: A connectivity puzzle for MsRaye ...

Wow that got right past me - when I refreshed the router page, the correctables and uncorrectables figures looked the same, could they be a one-time thing?

Expert

Re: A connectivity puzzle for MsRaye ...

That's what I was looking for as well as channel lineup changes. If nothing has increased (a few correctables a day are acceptable), You may have fixed the issues.