Browser

Re: Daily connectivity issues

Just a power reset. Not sure how to do a factory reset on that model. There is a reset button on the back panel, will that do it? No one in our house has verizon, but we do have several that are US Cellular.

 

Expert

Re: Daily connectivity issues

US cellular doesn't have channels of their own, they rent space off one of the 4 channel owners.

 

If you keep seeing corrected/ uncorrecteds increase a lot and all connectors are a tad more than finger tight,, yes, hit the reset button for 30 seconds then power down and power it back up... After 5 minutes it should pull down a new profile and hopefully with a different home channel

 

Browser

Re: Daily connectivity issues

Tried that reset and still got 747 MHz back. Power levels and correcteds seem much better though. Power was between 9 and 10 earlier and seems to have gone down some. Readings are for the last 12 hours since reset.

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 132747.00 MHz7.70 dBmV40.37 dB256QAM28684981110
Downstream 29609.00 MHz7.70 dBmV40.37 dB256QAM1607146700
Downstream 310615.00 MHz7.60 dBmV40.95 dB256QAM1940842000
Downstream 411621.00 MHz7.70 dBmV40.37 dB256QAM1713830300
Downstream 512627.00 MHz7.80 dBmV40.37 dB256QAM1654718500
Downstream 613633.00 MHz7.80 dBmV40.37 dB256QAM2799781600
Downstream 714639.00 MHz7.90 dBmV40.95 dB256QAM1716523400
Downstream 815645.00 MHz7.90 dBmV40.37 dB256QAM1961097800
Downstream 916651.00 MHz7.60 dBmV40.37 dB256QAM1850636800
Downstream 1017657.00 MHz7.60 dBmV40.37 dB256QAM2278431900
Downstream 1118663.00 MHz7.50 dBmV40.37 dB256QAM1838413500
Downstream 1219669.00 MHz7.80 dBmV38.98 dB256QAM2240595400
Downstream 1320675.00 MHz7.80 dBmV40.37 dB256QAM2906825500
Downstream 1421681.00 MHz8.00 dBmV40.37 dB256QAM2431590900
Downstream 1522687.00 MHz7.90 dBmV40.37 dB256QAM1920352200
Downstream 1623693.00 MHz8.10 dBmV40.37 dB256QAM2126304800
Downstream 1724699.00 MHz8.10 dBmV40.37 dB256QAM2313164200
Downstream 1825705.00 MHz8.10 dBmV40.37 dB256QAM1878217500
Downstream 1926711.00 MHz8.20 dBmV38.98 dB256QAM2042233310
Downstream 2027717.00 MHz8.00 dBmV38.61 dB256QAM1796066100
Downstream 2128723.00 MHz7.90 dBmV40.37 dB256QAM2036607400
Downstream 2229729.00 MHz7.60 dBmV40.37 dB256QAM18727064150
Downstream 2330735.00 MHz7.50 dBmV38.98 dB256QAM3241768140
Downstream 2431741.00 MHz7.80 dBmV40.37 dB256QAM1990827120
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 12624.20 MHz39.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 22837.00 MHz40.00 dBmVDOCSIS2.0 (ATDMA)2560 kSym/s64QAM
Upstream 32730.60 MHz40.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 42519.40 MHz39.25 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 

 Status
System Uptime:0 d: 11 h: 34 m
Computers Detected:staticCPE(1), dynamicCPE(1)
CM Status:OPERATIONAL
Time and Date:Fri 2018-01-19 09:37:11

 

DOCSIS(CM) Events

Date TimeEvent IDEvent LevelDescription
1/16/2018 10:29840007005RCS Partial Service;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/16/2018 10:29840202005Lost MDD Timeout;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/16/2018 10:29840007005RCS Partial Service;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/16/2018 10:31840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/16/2018 10:31840007005RCS Partial Service;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/16/2018 10:31840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/16/2018 10:31840202005Lost MDD Timeout;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/16/2018 11:51820002003No Ranging Response received - T3 time-out;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/16/2018 12:43730402003TLV-11 - Illegal Set operation failed;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/16/2018 16:17820002003No Ranging Response received - T3 time-out;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/17/2018 9:31730402003TLV-11 - Illegal Set operation failed;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/17/2018 10:26820002003No Ranging Response received - T3 time-out;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/17/2018 10:37730402003TLV-11 - Illegal Set operation failed;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/17/2018 22:53820002003No Ranging Response received - T3 time-out;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/18/2018 9:38730402003TLV-11 - Illegal Set operation failed;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/18/2018 12:30820002003No Ranging Response received - T3 time-out;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/18/2018 17:09730402003TLV-11 - Illegal Set operation failed;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/18/2018 18:12820002003No Ranging Response received - T3 time-out;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/18/2018 21:54730402003TLV-11 - Illegal Set operation failed;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-QOS=1.1;CM-VER=3.0;
1/19/2018 1:11820002003No Ranging Response received - T3 time-out;CM-MAC=2c:7e:81:bc:a0:91;CMTS-MAC=00:01:5c:84:f4:55;CM-
Expert

Re: Daily connectivity issues

looks like the reset is disabled...

As long as the numbers stay low you should be ok

 you are getting hits on the 729/735/741 4 G fixed channels, that may be a corroded or loose outside cable issue. As long as numbers remain really low you should be ok

 

Browser

Re: Daily connectivity issues

Ok, thank you for the help. All of the connections I can reach look good and tight. I can't check the one on the pole outside. Smiley Wink Thanks for the help.

Expert

Re: Daily connectivity issues

keep your cell phones away from the modem. and coax

 

Browser

Re: Daily connectivity issues

Some new information has come to light since I last posted. I upgraded my service to 100 mbps and tried a different modem. This only made things worse as I now had intermittent connectivity on internet outside of my VPN. Called cable company to come in again and this tech said I had a couple of issues. He did mention I had high signal level and he also said that the cable from the wall to the modem had old connectors on it that they do not use anymore because they tend to leak. He changed that cable out and put something on (a pad?) to lower the signal level. He also changed back to the TM1602 again. Latest readings look pretty similar to the ones before the changes and I can get back on internet again outside of VPN. I also contacted techs at work and they did some troubleshooting and found that the issue I had with the disconnects were not internet related, but due to having too many apps open on the VPN at once. It was running out of memory.  So the main issues are resolved.

 

I also found out something interesting in talking to someone that has been in the neighborhood longer than I have. Is seems approximately 6 or 8 years ago the electric company ran new power lines on the poles behind the house and while they were doing it, one of the lines fell and hit the cable company's line. He told the electric company person that it had hit the line and they said they would check it. They then told him that only the insulation was melted, not the internal conductors.  All they did was put tape over it and the cable was never changed by the cable company. Is it possible that all of the errors and other issues are caused by this?

 

Current readings after approx 6 hrs runtime:

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 132747.00 MHz5.50 dBmV38.98 dB256QAM1557162741240
Downstream 29609.00 MHz6.10 dBmV40.37 dB256QAM1219307760
Downstream 310615.00 MHz5.80 dBmV38.98 dB256QAM12332284100
Downstream 411621.00 MHz5.70 dBmV40.37 dB256QAM16580476190
Downstream 512627.00 MHz5.60 dBmV38.98 dB256QAM18296540200
Downstream 613633.00 MHz5.40 dBmV38.98 dB256QAM65141809250
Downstream 714639.00 MHz5.40 dBmV40.37 dB256QAM16601752310
Downstream 815645.00 MHz5.50 dBmV38.98 dB256QAM16606654210
Downstream 916651.00 MHz5.30 dBmV38.98 dB256QAM34055506460
Downstream 1017657.00 MHz5.30 dBmV40.37 dB256QAM14924029580
Downstream 1118663.00 MHz5.30 dBmV38.98 dB256QAM16176813550
Downstream 1219669.00 MHz5.40 dBmV38.98 dB256QAM16532663780
Downstream 1320675.00 MHz5.30 dBmV38.98 dB256QAM19295141850
Downstream 1421681.00 MHz5.50 dBmV38.98 dB256QAM22114000760
Downstream 1522687.00 MHz5.50 dBmV38.98 dB256QAM15453907870
Downstream 1623693.00 MHz5.30 dBmV38.98 dB256QAM17388066780
Downstream 1724699.00 MHz5.40 dBmV38.98 dB256QAM29019653990
Downstream 1825705.00 MHz5.50 dBmV38.98 dB256QAM16638522880
Downstream 1926711.00 MHz5.60 dBmV38.98 dB256QAM190822901040
Downstream 2027717.00 MHz5.60 dBmV38.98 dB256QAM166169431340
Downstream 2128723.00 MHz5.40 dBmV38.98 dB256QAM163774271500
Downstream 2229729.00 MHz5.50 dBmV38.61 dB256QAM191152001680
Downstream 2330735.00 MHz5.30 dBmV38.98 dB256QAM188706201570
Downstream 2431741.00 MHz5.50 dBmV38.61 dB256QAM153840161280
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 12624.20 MHz39.50 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 22837.00 MHz39.75 dBmVDOCSIS2.0 (ATDMA)2560 kSym/s64QAM
Upstream 32730.60 MHz40.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 42519.40 MHz39.00 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 

 Status
System Uptime:0 d: 6 h: 08 m
Computers Detected:staticCPE(1), dynamicCPE(1)
CM Status:OPERATIONAL
Time and Date:Thu 2018-02-08 15:45:10
Expert

Re: Daily connectivity issues

 

 

I also found out something interesting in talking to someone that has been in the neighborhood longer than I have. Is seems approximately 6 or 8 years ago the electric company ran new power lines on the poles behind the house and while they were doing it, one of the lines fell and hit the cable company's line. He told the electric company person that it had hit the line and they said they would check it. They then told him that only the insulation was melted, not the internal conductors.  All they did was put tape over it and the cable was never changed by the cable company. Is it possible that all of the errors and other issues are caused by this?"

   

The coax Maybe destroyed... If something got hot enough to melt the insulation, it damaged the foil and center insulations as well. 

If after their last "repair" you still have issues, The outside drop  needs to be replaced.

 

Browser

Re: Daily connectivity issues

Thanks. At least I have a direction to go if the problems keep happening. It was getting very frustrating that none of their fixes completely eliminated the issue. Is there a good way to point them to the issue on that main cable? It is not really on the drop to the house, it is on the cable between poles, about 40 feet from where my drop is tapped in.

Expert

Re: Daily connectivity issues

The aluminum hardline between poles is a little more rugged . If everything from the modem to the pole was replaced, I'd suspect a bad connection somewhere between poles. Good luck getting them to trace that down and repair it until it totally fails.

you don't have any uncorrecteds and just a very low % of correcteds, that shouldn't drop a vpn