Phoenix, 85083 - Extreme Packet Loss - No Ranging Response received - T3 time-out & RCS Partial Service
I've been experiencing severe packet lossover the last several months. This has made working from home very difficult as I rely on video conferencing and VPN/remote access to do my job. The problem strikes sporadically and lasts for a few seconds up to a minute or so. My VPN connection will drop or my video conferences will time out. My cable modem (SB6109) shows several errors in the event log. These events show up in pairs. Sometimes separated by a few seconds, other times by a much larger time frame. Mon Aug 10 08:39:10 2020 3 No Ranging Response received - T3 time-out;CM-MAC=a8:9f:ec:dc:fe:0b;CMTS-MAC=00:87:31:90:ba:41;CM-QOS=1.1;CM-VER=3.0; Mon Aug 10 11:28:51 2020 5 RCS Partial Service;CM-MAC=a8:9f:ec:dc:fe:0b;CMTS-MAC=00:87:31:90:ba:41;CM-QOS=1.1;CM-VER=3.0; Tue Aug 11 09:47:45 2020 3 No Ranging Response received - T3 time-out;CM-MAC=a8:9f:ec:dc:fe:0b;CMTS-MAC=00:87:31:90:ba:41;CM-QOS=1.1;CM-VER=3.0; Tue Aug 11 09:47:58 2020 5 RCS Partial Service;CM-MAC=a8:9f:ec:dc:fe:0b;CMTS-MAC=00:87:31:90:ba:41;CM-QOS=1.1;CM-VER=3.0; The downstream channels are also showing anywhere from 7k to 67k of uncorrectable errors after less than 3 days of up time. With a total of over 1 million and an average of about 33k per channel. Sometimes I need to reset my modem and router in order for the connection to come back up. This problem has been observed: over wireless wired throughrouter -> modem. wired directly to the cable modem. I have had technicians come out in the past with no resolution. I don't have any splitters in my cable wiring. I would like this problem addressed.
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;
Critical T3 Errors - Multiple
Need some assistance. I've had multiple issues with disconnects while gaming and the history of errors listed below is alarming. Need some advice. Connections are tight and secure. No splitters in line. Cox installed coaxial cables. I've done the trouble shooting within the apartment. Sat Nov 23 01:48:43 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MA... Mon Nov 25 21:38:42 2019 Notice (6) TLV-11 - unrecognized OID;CM-MAC= ;CMTS-MAC=... Tue Nov 26 15:12:18 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/... Tue Nov 26 15:12:18 2019 Warning (5) MDD message timeout;CM-MAC= ;CMTS-MAC=70:6e:... Tue Nov 26 15:12:21 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/... Tue Nov 26 15:12:22 2019 Warning (5) MDD message timeout;CM-MAC= ;CMTS-MAC=70:6e:... Tue Nov 26 15:12:56 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:13:00 2019 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00... Tue Nov 26 15:15:48 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:15:48 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retrie... Tue Nov 26 15:15:48 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream... Tue Nov 26 15:18:47 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:18:47 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retrie... Tue Nov 26 15:18:47 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream... Tue Nov 26 15:19:07 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:19:07 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retrie... Tue Nov 26 15:19:07 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream... Tue Nov 26 15:28:27 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:29:09 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4... Thu Nov 28 07:37:54 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Fri Nov 29 03:43:24 2019 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-... Sat Nov 30 05:43:25 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Sat Nov 30 05:43:27 2019 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MA... Sat Nov 30 05:44:32 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no U... Sat Nov 30 10:34:19 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -...Many T3 Time Outs
I had been noticing servive drop outs for some months and decided to buy a new modem/router but, that did not solve the problem. My New Netgear C7000v2 Modem/Router is getting many T3 time outs. The Router error logs show the time outs and dates of the t3 errors and in addition I wrote a bash scrip that logs time out errors. It pings both google.com and yahoo.com. If both pings fail, it logs an error along with each ping return value. I would like to know to whom and were I can email this data for futher analysis and repair solution.
No Ranging Response received - T3 time-out error
Trying to figure out if I have a potential problem with my Netgear CMD31T modem or if there is a communication problem between the modem and Cox servers. As I expected this problem is way above the heads of Tier 1 support so I thought I'd check in here. My downstream throughput is fine (60M) and I do have upstream throughput that is within parameters (5M). My problem is the modem upstream channel/sync lights show a problem. 1/2 is orange and 3/4 is out. When I get into the modem it shows sync and signal issues: Connection Startup Procedure Procedure Status Comment Acquire Downstream Channel 789000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Configuration File Complete Security Enabled BPI+ Downstream Channel 0 Lock Status Locked Modulation 256 QAM Channel ID 1 Symbol rate 5360537 Downstream Frequency 789000000 Hz Downstream Power 9.3961 dBmV SNR 37.6363 dBmV Correctables 422 Uncorrectables 694 Downstream Channel 1 Lock Status Locked Modulation 256 QAM Channel ID 2 Symbol rate 5360537 Downstream Frequency 783000000 Hz Downstream Power 9.1820 dBmV SNR 37.9359 dBmV Correctables 393 Uncorrectables 1374 Downstream Channel 2 Lock Status Locked Modulation 256 QAM Channel ID 3 Symbol rate 5360537 Downstream Frequency 795000000 Hz Downstream Power 8.6046 dBmV SNR 37.9359 dBmV Correctables 414 Uncorrectables 469 Downstream Channel 3 Lock Status Locked Modulation 256 QAM Channel ID 4 Symbol rate 5360537 Downstream Frequency 801000000 Hz Downstream Power 8.9304 dBmV SNR 38.2578 dBmV Correctables 1644 Uncorrectables 8457 Upstream Channel 0 Lock Status Locked Modulation 64QAM Channel ID 4 Symbol rate 5120 Ksym/sec Upstream Frequency 36700000 Hz Upstream Power 35.7500 dBmV Upstream Channel 1 Lock Status Not Locked Modulation Channel ID 0 Symbol rate 0 Ksym/sec Upstream Frequency 0 Hz Upstream Power 0 dBmV Upstream Channel 2 Lock Status Not Locked Modulation Channel ID 0 Symbol rate 0 Ksym/sec Upstream Frequency 0 Hz Upstream Power 0 dBmV Upstream Channel 3 Lock Status Not Locked Modulation Channel ID 0 Symbol rate 0 Ksym/sec Upstream Frequency 0 Hz Upstream Power 0 dBmV Current System Time:Tue Jan 16 14:34:19 2018 This is a recent error log Tue Jan 2 23:12:32 2018 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e8:fc:af:ad... Wed Jan 3 23:11:16 2018 Notice (6) DHCP Renew - lease parameters tftp file-^1/C312B450/DEF/001 m... Sun Jan 7 08:49:02 2018 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e8:fc:af:ad Sun Jan 14 11:11:16 2018 Notice (6) DHCP Renew - lease parameters tftp file-^1/C312B450/DEF/001 m... Time Not Established Warning (5) MDD message timeout;CM-MAC=e8:fc:af:ad:XX:XX;CMTS-MAC=2c:86:d... Mon Jan 15 16:26:20 2018 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=... Mon Jan 15 16:26:20 2018 Notice (6) TLV-11 - unrecognized OID;CM-MAC=e8:fc:af:ad:XX:XX a note--I've modified the modem MAC address in this log for security. I'm trying to confirm if I've got a modem in a pre fail state. If that is the case, I don't need a truck roll to my site. Advice on next steps? Thanks