Highlighted
Browser

Daily connectivity issues

  1. Milwaukee, WI, 53222. Single family home. Have Spectrum for internet only. Parents have Directv for internet and tv
  2. Internet only
  3. Arris TM1602
  4.  ARRIS DOCSIS 3.0 / PacketCable 2.0 Touchstone Telephony Modem
    HW_REV: 1
    VENDOR: ARRIS Group, Inc.
    BOOTR: 2.2.0.45
    SW_REV: 9.1.103J8.SIP.PC20.TW
    MODEL: TM1602AP2
  5. Confirm modem is Online : Yes
  6. What are your purchased speeds? 25 MBPS I believe. 23.67 MBPS Down, 2.48 MPBS up
  7. List symptoms using a wired (not wireless) connection with date and time and any repeating pattern: Have had daily issues with packet loss/apps freezing or closing on vpn connection
  8. Modem's signal, downstream and upstream, and event log pages. usually accessed at 192.168.100.1 or 192.168.0.1                                         All readings with direct connection from Modem to computer, with no router connected                                                    Downstream
     DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
    Downstream 132747.00 MHz9.30 dBmV38.98 dB256QAM24866411691993045
    Downstream 29609.00 MHz9.20 dBmV40.37 dB256QAM197374411104010544
    Downstream 310615.00 MHz9.10 dBmV40.37 dB256QAM213052901163713158
    Downstream 411621.00 MHz9.20 dBmV40.37 dB256QAM19293220106548053
    Downstream 512627.00 MHz9.20 dBmV38.98 dB256QAM33929428112467765
    Downstream 613633.00 MHz9.20 dBmV38.98 dB256QAM29045371101747394
    Downstream 714639.00 MHz9.30 dBmV40.37 dB256QAM23403883100695415
    Downstream 815645.00 MHz9.40 dBmV40.37 dB256QAM26632055101804578
    Downstream 916651.00 MHz9.10 dBmV38.98 dB256QAM21471704103895584
    Downstream 1017657.00 MHz9.10 dBmV40.37 dB256QAM24258796102906580
    Downstream 1118663.00 MHz9.10 dBmV38.61 dB256QAM273252341149710095
    Downstream 1219669.00 MHz9.10 dBmV38.98 dB256QAM3631968499059038
    Downstream 1320675.00 MHz9.10 dBmV38.98 dB256QAM29135953105326883
    Downstream 1421681.00 MHz9.30 dBmV38.98 dB256QAM2212786696106272
    Downstream 1522687.00 MHz9.40 dBmV38.98 dB256QAM2473712296044587
    Downstream 1623693.00 MHz9.50 dBmV40.37 dB256QAM2141650591714944
    Downstream 1724699.00 MHz9.60 dBmV38.98 dB256QAM2532689794294450
    Downstream 1825705.00 MHz9.60 dBmV40.37 dB256QAM2469077192523022
    Downstream 1926711.00 MHz9.70 dBmV38.61 dB256QAM2163263493582327
    Downstream 2027717.00 MHz9.50 dBmV38.61 dB256QAM6196102097115214
    Downstream 2128723.00 MHz9.40 dBmV38.61 dB256QAM2399754899595403
    Downstream 2229729.00 MHz9.20 dBmV38.98 dB256QAM1941188198812398
    Downstream 2330735.00 MHz9.10 dBmV38.61 dB256QAM23312279100703202
    Downstream 2431741.00 MHz9.40 dBmV38.98 dB256QAM2344726793703831
    Reset FEC Counters
    Upstream
     UCIDFreqPowerChannel TypeSymbol RateModulation
    Upstream 12624.20 MHz39.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
    Upstream 22837.00 MHz39.50 dBmVDOCSIS2.0 (ATDMA)2560 kSym/s64QAM
    Upstream 32730.60 MHz39.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
    Upstream 42519.40 MHz39.75 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

     Status
    System Uptime:0 d: 9 h: 26 m
    Computers Detected:staticCPE(1), dynamicCPE(1)
    CM Status:OPERATIONAL
    Time and Date:Mon 2018-01-15 22:09:17
                                                                                                                                                            DOCSIS(CM) Events
    Date TimeEvent IDEvent LevelDescription
    1/6/2018 17:19730402003TLV-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/6/2018 22:02680106006DHCP Renew - lease parameters tftp file-?BEWGlzIsfoG8oJEKHK46@ChyuOpJJLt0ZPmXAM_UUDaVLACuO0Z8r modified;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/6/2018 22:19730402003TLV-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/7/2018 5:20820002003No 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/9/2018 12:40840007005RCS 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/9/2018 12:42730402003TLV-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/10/2018 8:55820002003No 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/10/2018 9:56730402003TLV-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/10/2018 12:20820002003No 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/10/2018 12:40730402003TLV-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/10/2018 13:18820002003No 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/11/2018 12:44730402003TLV-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/11/2018 13:52820002003No 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/14/2018 11:20680106006DHCP Renew - lease parameters time server-65.24.21.120;tftp file-?BEWGlzIsfoG8oJEKHK46@ChyuOvWGE4qDNPsrz4DqQVTDtkbwRv94 modified;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/15/2018 12:04820002003No 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/15/2018 12:41840007005RCS 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/15/2018 12:44730402003TLV-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/15/2018 13:34820002003No 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/15/2018 15:15840007005RCS 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/15/2018 15:22820002003No 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;

     PacketCable(MTA) Events

    Date TimeEvent IDDescription
    12/1/2017 3:4816MTA TFTP: Successful
    12/1/2017 3:4826MTA PROV: Successful!
    12/1/2017 3:483Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
    12/1/2017 3:483Voice Line State Change, Line Number = 2, Prev State = OOS, New State = IS
                                               
  9. Description of your cable wiring from street and throughout house, include splitters, devices, cable type (rg6, rg59) and age, etc. and specifically the where the modem attaches.  One cable from pole to house - not marked as to type, inline connector, One cable from outside house to wall socket - not marked as to type, one cable from wall connector to moderm - not marked as to type. Cable from pole to house put in a few weeks ago when tech was here. Did not resolve issue. Rest were installed with system approx 3 years ago.
  10. Description of ethernet network from modem’s ethernet port to router(s) and to any additional devices including cable type, e.g., cat5, cat5e, cat6, etc. Modem to router using yellow Cat 5e cable. Router to computer using gray cat 5e cable. No wifi enabled from modem. Netgear WNDR3400v2, approx 7 years old, wifi turned off.
  11. Any recent or coincident changes or upgrades to your system, or any neighborhood changes. New drop from pole to house and new modem installed several weeks ago, did not resolve issue.
  12. Are any background tasks running that upload or download data automatically, e.g., backup programs, torrent client, file/photo/music sync, auto program/app update, etc.? No
21 REPLIES
Expert

Re: Daily connectivity issues

You've got a serious noise/ ingress issue, something is corroded or loose, verify the connectors on back of wall plates are a tad more than finger tight as well as all the rest.

Correcteds/ uncorrecteds are horrible.

rcs error indicates Ingress from local tv and 4G cellular channels & Devices.

 

Browser

Re: Daily connectivity issues

Found one connection that was not even finger tight but made all of the connections that I could reach just past finger tight. All seemed clean and had no corrosion.

New readings:

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 132747.00 MHz9.00 dBmV38.98 dB256QAM910622411281587263
Downstream 29609.00 MHz9.00 dBmV40.37 dB256QAM407067520637
Downstream 310615.00 MHz8.90 dBmV40.37 dB256QAM401479765660
Downstream 411621.00 MHz9.00 dBmV40.37 dB256QAM406197171759
Downstream 512627.00 MHz9.00 dBmV38.98 dB256QAM425855874643
Downstream 613633.00 MHz9.00 dBmV38.98 dB256QAM4260101517722
Downstream 714639.00 MHz9.10 dBmV40.37 dB256QAM40017161107633
Downstream 815645.00 MHz9.20 dBmV40.37 dB256QAM39956621117735
Downstream 916651.00 MHz8.90 dBmV38.98 dB256QAM4029048817908
Downstream 1017657.00 MHz8.90 dBmV40.37 dB256QAM3980991707904
Downstream 1118663.00 MHz8.80 dBmV38.98 dB256QAM43078281507367
Downstream 1219669.00 MHz8.90 dBmV38.98 dB256QAM40435421957349
Downstream 1320675.00 MHz9.00 dBmV38.98 dB256QAM42466691627330
Downstream 1421681.00 MHz9.20 dBmV38.98 dB256QAM45136871357359
Downstream 1522687.00 MHz9.10 dBmV38.98 dB256QAM3999890797452
Downstream 1623693.00 MHz9.30 dBmV40.37 dB256QAM4034642947352
Downstream 1724699.00 MHz9.30 dBmV38.98 dB256QAM3979634807363
Downstream 1825705.00 MHz9.30 dBmV38.98 dB256QAM40581521417326
Downstream 1926711.00 MHz9.40 dBmV38.61 dB256QAM42547101419037
Downstream 2027717.00 MHz9.30 dBmV38.61 dB256QAM4091505769209
Downstream 2128723.00 MHz9.20 dBmV38.98 dB256QAM39732512257919
Downstream 2229729.00 MHz8.90 dBmV38.98 dB256QAM40805031308193
Downstream 2330735.00 MHz8.80 dBmV38.61 dB256QAM40108392797832
Downstream 2431741.00 MHz9.20 dBmV38.61 dB256QAM42116892958117
Reset FEC Counters

Upstream

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

 

 Status
System Uptime:0 d: 23 h: 49 m
Computers Detected:staticCPE(1), dynamicCPE(1)
CM Status:OPERATIONAL
Time and Date:Tue 2018-01-16 12:32:36

 

DOCSIS(CM) Events

Date TimeEvent IDEvent LevelDescription
1/16/2018 8:50840202005Lost 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 8:51820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 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 8:55820002003No 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 8:56730402003TLV-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 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:29840005003SYNC 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: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:29840005003SYNC 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: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: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: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;

 

 PacketCable(MTA) Events

 

Date TimeEvent IDDescription
12/1/2017 3:4816MTA TFTP: Successful
12/1/2017 3:4826MTA PROV: Successful!
12/1/2017 3:483Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
12/1/2017 3:483Voice Line State Change, Line Number = 2, Prev State = OOS, New State = IS
Expert

Re: Daily connectivity issues

You need to see if the correcteds continue increasing in a 4-8 hour period.. Should be a "reset FEC counters" button to zero them out. Then see if after 4-8 hours channels have high correcteds and any partial service errors in the log.

 ALLL connections must be a tad more than finger tight, spec is 10-16 inch lbs...

coax can't go thru any surge protector outlet strips or UPS's, they allow severe ingress in.

 

Established Sharer

Re: Daily connectivity issues

Also note the subject router is an older obsolete version (V2) of the WNDR3400.  Netgear has issued at least two firmware updates in the last six months to resolve security and bug fix issues.  If you have not already done so, visit the Netgear website promptly to download and install these patches.  That step has greatly reduced lockups in my V3 version.

Browser

Re: Daily connectivity issues

Reset  counters approx 4pm and took this first reading shortly after:

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 132747.00 MHz9.40 dBmV38.98 dB256QAM971678261990
Downstream 29609.00 MHz9.30 dBmV40.95 dB256QAM10435839110
Downstream 310615.00 MHz9.10 dBmV40.37 dB256QAM8830043220
Downstream 411621.00 MHz9.20 dBmV40.37 dB256QAM23531123220
Downstream 512627.00 MHz9.30 dBmV38.98 dB256QAM20942606210
Downstream 613633.00 MHz9.30 dBmV38.98 dB256QAM22845342410
Downstream 714639.00 MHz9.40 dBmV40.95 dB256QAM9732434490
Downstream 815645.00 MHz9.40 dBmV40.37 dB256QAM9946682500
Downstream 916651.00 MHz9.20 dBmV38.98 dB256QAM10434983860
Downstream 1017657.00 MHz9.20 dBmV40.37 dB256QAM14729137940
Downstream 1118663.00 MHz9.00 dBmV38.98 dB256QAM10947377960
Downstream 1219669.00 MHz9.20 dBmV38.98 dB256QAM170931191020
Downstream 1320675.00 MHz9.20 dBmV38.98 dB256QAM285886061500
Downstream 1421681.00 MHz9.40 dBmV38.61 dB256QAM458345801340
Downstream 1522687.00 MHz9.30 dBmV38.98 dB256QAM73887001530
Downstream 1623693.00 MHz9.60 dBmV40.37 dB256QAM138398511540
Downstream 1724699.00 MHz9.50 dBmV38.98 dB256QAM118705461670
Downstream 1825705.00 MHz9.60 dBmV38.98 dB256QAM129435851670
Downstream 1926711.00 MHz9.70 dBmV38.61 dB256QAM192891871530
Downstream 2027717.00 MHz9.50 dBmV38.61 dB256QAM120068472310
Downstream 2128723.00 MHz9.50 dBmV38.61 dB256QAM108578752270
Downstream 2229729.00 MHz9.20 dBmV38.98 dB256QAM128431303220
Downstream 2330735.00 MHz9.20 dBmV38.61 dB256QAM119012372740
Downstream 2431741.00 MHz9.40 dBmV38.98 dB256QAM232546592340

 

Second reading is approximately 10pm, 6 hours later:

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 132747.00 MHz9.60 dBmV38.98 dB256QAM2460459894460
Downstream 29609.00 MHz9.50 dBmV40.37 dB256QAM17395548520
Downstream 310615.00 MHz9.40 dBmV40.37 dB256QAM15949125650
Downstream 411621.00 MHz9.40 dBmV40.37 dB256QAM31223430710
Downstream 512627.00 MHz9.50 dBmV40.37 dB256QAM29410183610
Downstream 613633.00 MHz9.50 dBmV38.98 dB256QAM305633611050
Downstream 714639.00 MHz9.60 dBmV40.37 dB256QAM167249761240
Downstream 815645.00 MHz9.60 dBmV40.95 dB256QAM173196111070
Downstream 916651.00 MHz9.40 dBmV38.98 dB256QAM176367631960
Downstream 1017657.00 MHz9.40 dBmV40.37 dB256QAM222564761950
Downstream 1118663.00 MHz9.30 dBmV38.98 dB256QAM182692892380
Downstream 1219669.00 MHz9.40 dBmV38.98 dB256QAM247948952250
Downstream 1320675.00 MHz9.40 dBmV40.37 dB256QAM365674013040
Downstream 1421681.00 MHz9.60 dBmV38.61 dB256QAM551542763050
Downstream 1522687.00 MHz9.60 dBmV38.98 dB256QAM145728153390
Downstream 1623693.00 MHz9.80 dBmV40.37 dB256QAM217912313420
Downstream 1724699.00 MHz9.80 dBmV38.98 dB256QAM190808643530
Downstream 1825705.00 MHz9.80 dBmV40.37 dB256QAM204244753820
Downstream 1926711.00 MHz10.00 dBmV38.98 dB256QAM271158173540
Downstream 2027717.00 MHz9.80 dBmV38.98 dB256QAM198271434720
Downstream 2128723.00 MHz9.80 dBmV38.98 dB256QAM183164184860
Downstream 2229729.00 MHz9.50 dBmV38.98 dB256QAM201733286680
Downstream 2330735.00 MHz9.50 dBmV38.98 dB256QAM195440825860
Downstream 2431741.00 MHz9.80 dBmV38.98 dB256QAM322072315150

 

Event log follows with it looks like only one T3 timeout and no partial service events.:

 

DOCSIS(CM) Events

Date TimeEvent IDEvent LevelDescription
1/16/2018 8:55820002003No 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 8:56730402003TLV-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 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:29840005003SYNC 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: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:29840005003SYNC 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: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: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: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;

 

Will check it again tomorrow to compare the readings and see if the issue persists. Also the Netgear router is not connected right now to try to narrow down the issue, and it was still happening with the router out of the system. I believe the router is up to date on firmware, but since the version I have is obsolete, I will probably get another router if there are still issues.

 

Expert

Re: Daily connectivity issues

I don't like seeing the correcteds on the first channel as it's the home ch.   It's possible you can get a cleaner first ch with a reset... Get it off 747 mHz which is a heavily used Verizon 4G LTE channel.

 

 I don't think your problem is fixed, but it's better. The +9 dBmv incomming level is on the high side of acceptable.

 

Problem is a street amps set with too high  of gain resulting in errors. The inhouse guys need to escallate it to the bucket truck guys.

 

Browser

Re: Daily connectivity issues

Looks like something may have been done on my line without my calling. Here are my latest logs after about 6 hours of operation, including working on VPN line for several hours with no issues:

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 132747.00 MHz7.80 dBmV40.37 dB256QAM13577038620
Downstream 29609.00 MHz7.90 dBmV40.37 dB256QAM905213300
Downstream 310615.00 MHz7.80 dBmV40.37 dB256QAM1024060450
Downstream 411621.00 MHz7.90 dBmV40.37 dB256QAM2282353000
Downstream 512627.00 MHz7.90 dBmV40.37 dB256QAM1434864100
Downstream 613633.00 MHz8.00 dBmV38.98 dB256QAM2499225500
Downstream 714639.00 MHz8.00 dBmV40.37 dB256QAM1026122300
Downstream 815645.00 MHz8.10 dBmV40.37 dB256QAM952961700
Downstream 916651.00 MHz7.80 dBmV40.37 dB256QAM1208460400
Downstream 1017657.00 MHz7.80 dBmV40.37 dB256QAM977162800
Downstream 1118663.00 MHz7.70 dBmV38.98 dB256QAM1552038000
Downstream 1219669.00 MHz7.90 dBmV40.37 dB256QAM1668798100
Downstream 1320675.00 MHz7.90 dBmV40.37 dB256QAM1457117900
Downstream 1421681.00 MHz8.10 dBmV38.98 dB256QAM4070591500
Downstream 1522687.00 MHz8.00 dBmV38.98 dB256QAM928009600
Downstream 1623693.00 MHz8.20 dBmV40.37 dB256QAM1784093600
Downstream 1724699.00 MHz8.20 dBmV38.98 dB256QAM993173100
Downstream 1825705.00 MHz8.20 dBmV40.37 dB256QAM1451829000
Downstream 1926711.00 MHz8.30 dBmV38.98 dB256QAM2077297700
Downstream 2027717.00 MHz8.10 dBmV38.98 dB256QAM1047946920
Downstream 2128723.00 MHz8.00 dBmV38.98 dB256QAM10206237150
Downstream 2229729.00 MHz7.70 dBmV38.98 dB256QAM13567946180
Downstream 2330735.00 MHz7.70 dBmV38.98 dB256QAM1035773310
Downstream 2431741.00 MHz7.90 dBmV40.37 dB256QAM2795600810
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.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 42519.40 MHz39.25 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 

 Status
System Uptime:0 d: 5 h: 48 m
Computers Detected:staticCPE(1), dynamicCPE(1)
CM Status:OPERATIONAL
Time and Date:Thu 2018-01-18 15:24:48

 

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: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: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;

 

These seem to be looking better,  correct?

Browser

Re: Daily connectivity issues

Could not get off of 747 MHz, even with several resets of modem.
Expert

Re: Daily connectivity issues

Are you doing a simple power reset or a factory reset? The latter may reassign the home ch.

747 is getting trashed from a verizon phone, probably yours.

 vpn's won't work with any uncorrecteds  orexcesssive  correcteds on the home channel