Intermittent Disconnects T3 time-out, CM1100 status and logs
Hi, I have a CM1100 modem, about 3 months out of the box. I am experiencing time outs. The all modem lights stay connected. Only quick but noticeable drops. There are no coaxial splitters inside or the outside box. I remember the team of technicians that setup my service say that my house is bit far from the node. Any recommendations would be appreciated. Thank you. Startup Procedure Procedure Status Comment Acquire Downstream Channel 795000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Honor MDD IPv4 only Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked QAM256 3 795000000 Hz -0.9 dBmV 39.7 dB 3782564102 0 0 2 Locked QAM256 1 783000000 Hz -0.7 dBmV 39.6 dB 3811638155 0 0 3 Locked QAM256 2 789000000 Hz -0.9 dBmV 39.5 dB 3811642244 0 0 4 Locked QAM256 22 909000000 Hz 0.6 dBmV 40.0 dB 3781155783 0 0 5 Locked QAM256 4 801000000 Hz -1.0 dBmV 39.4 dB 3811649459 0 0 6 Locked QAM256 9 831000000 Hz -1.0 dBmV 39.7 dB 3811652951 0 0 7 Locked QAM256 10 837000000 Hz -1.3 dBmV 39.4 dB 3811638094 0 0 8 Locked QAM256 11 843000000 Hz -1.2 dBmV 39.3 dB 3811659453 0 0 9 Locked QAM256 12 849000000 Hz -1.1 dBmV 39.3 dB 3811663676 0 0 10 Locked QAM256 17 879000000 Hz -1.3 dBmV 39.0 dB 3811667062 0 0 11 Locked QAM256 18 885000000 Hz -1.1 dBmV 39.2 dB 3811670676 0 0 12 Locked QAM256 19 891000000 Hz -0.6 dBmV 39.4 dB 3811674427 0 0 13 Locked QAM256 20 897000000 Hz 0.0 dBmV 39.8 dB 3811678384 0 0 14 Locked QAM256 21 903000000 Hz 0.0 dBmV 39.7 dB 3811681944 0 0 15 Locked QAM256 25 927000000 Hz -1.5 dBmV 39.1 dB 3811684860 0 0 16 Locked QAM256 26 933000000 Hz -2.1 dBmV 38.7 dB 3811689326 0 0 17 Locked QAM256 27 939000000 Hz -1.6 dBmV 38.9 dB 3811693305 0 0 18 Locked QAM256 28 945000000 Hz -1.1 dBmV 39.3 dB 3811697183 0 0 19 Locked QAM256 29 951000000 Hz -1.0 dBmV 39.3 dB 3811700247 0 0 20 Locked QAM256 30 957000000 Hz -0.9 dBmV 39.4 dB 3811704223 0 0 21 Locked QAM256 33 357000000 Hz 2.5 dBmV 40.2 dB 3811708229 0 0 22 Locked QAM256 34 363000000 Hz 2.4 dBmV 40.6 dB 3811711727 0 0 23 Locked QAM256 35 369000000 Hz 2.4 dBmV 40.6 dB 3811715045 0 0 24 Locked QAM256 36 375000000 Hz 2.6 dBmV 40.6 dB 3811718942 0 0 25 Locked QAM256 37 381000000 Hz 2.6 dBmV 40.7 dB 3811722765 0 0 26 Locked QAM256 38 387000000 Hz 2.5 dBmV 40.6 dB 3811726072 0 0 27 Locked QAM256 41 405000000 Hz 2.3 dBmV 40.4 dB 3811729486 0 0 28 Locked QAM256 42 411000000 Hz 2.2 dBmV 40.4 dB 3811733185 0 0 29 Locked QAM256 43 417000000 Hz 2.0 dBmV 40.4 dB 3811736632 0 0 30 Locked QAM256 44 423000000 Hz 2.3 dBmV 40.6 dB 3811741068 0 0 31 Locked QAM256 45 429000000 Hz 2.3 dBmV 40.6 dB 3811741409 0 0 32 Locked QAM256 46 435000000 Hz 2.3 dBmV 40.6 dB 3811760159 0 0 Upstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power 1 Locked ATDMA 1 16900000 Hz 41.3 dBmV 2 Locked ATDMA 2 23500000 Hz 42.0 dBmV 3 Locked ATDMA 3 29900000 Hz 43.3 dBmV 4 Locked ATDMA 4 36300000 Hz 44.0 dBmV 5 Not Locked Unknown 0 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Hz 0.0 dBmV Downstream OFDM Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 0, 1, 2, 3 159 300000000 Hz 7.2 dBmV 42.5 dB 1108 ~ 2987 4074496805 918687451 0 2 Not Locked 0 0 0 Hz -40.5 dBmV 0.0 dB 0 ~ 4095 0 0 0 Upstream OFDMA Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked Unknown 0 0 Hz 0 dBmV 2 Not Locked Unknown 0 0 Hz 0 dBmV Here are the logs on the modem. Time Priority Description 2020-07-24, 04:26:20 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 19:46:23 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 19:34:26 Notice (6) CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: ); MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 19:34:26 Warning (5) Unicast DSID PSN startup error 2020-07-23, 19:34:14 Warning (5) Dynamic Range Window violation 2020-07-23, 19:34:14 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 19:34:08 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 19:34:03 Notice (6) TLV-11 - unrecognized OID;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 19:34:02 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 08:47:43 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 08:47:42 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 08:47:40 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 08:47:39 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 08:47:38 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 08:47:37 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 08:47:36 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-23, 08:47:32 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-22, 15:42:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-21, 04:47:01 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:50:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:29:21 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:29:20 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:29:02 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:29:01 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:28:17 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:28:15 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:28:03 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:28:01 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:27:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:27:38 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:27:34 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:27:31 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:27:19 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:27:18 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;CM-QOS=1.1;CM-VER=3.1; 2020-07-19, 01:27:08 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:80:88:ac:66:70;CMTS-MAC=00:38:df:09:24:ee;
Understanding entries and timestamps in panoramic wifi gateway logs
When logged into my wifi gateway, I can see "system", "firewall", and "event" logs. My questions is regarding the firewall logs specifically. I've noticed there is a huge difference between the "number of attempts" from one time stamp to another. Is that determined by the length and level of activity of the user? Also, what does the timestamp imply? Is that the time at which activity, or a certain type of activity, was ended? Or when it began? Does it represent a set time period? Should they correspond with time stamps for system and event logs? FW.WANATTACK DROP, 3 ATTEMPTS, 2020/3/26 05:58:01 FIREWALL BLOCKED FW.WANATTACK DROP, 432 ATTEMPTS, 2020/3/11 10:59:01 FIREWALL BLOCKED FW.IPv6 FORWARD drop, 148Attempts, 2020/3/17 16:58:01 FIREWALL BLOCKED FW.IPv6 FORWARD drop,9073Attempts, 2020/4/14 16:58:01 FIREWALL BLOCKED FW.IPv6 INPUT drop, 1Attempts, 2020/3/28 12:58:01 FIREWALL BLOCKED FW.IPv6 INPUT drop,9467Attempts, 2020/4/20 12:58:01 FIREWALL BLOCKED I'm also curious what the entries mean, as in the difference between a FORWARD DROP and an INPUT DROP. But I've asked a lot already. Thanks so much for your time!