Frequent Visitor
•
6 Messages
Random Network Resets, some days several times, after TLV-11 - unrecognized OID log
This appears to be a similar problem to what some other people have reported and ultimately only solvable by having an actual Comcast technician who can look at the back end to get involved.
My power and SNR look in spec, however the cable modem will reset at which point it generates the following error:
| Wed Jun 24 09:17:10 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0; |
| Wed Jun 24 09:13:25 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0; |
both of these errors today were associated with a few minute outage
sometimes there are more logs generated, June 17 was a particularly bad day:
Wed Jun 17 19:32:43 2020 Warning (5) Unicast DSID PSN startup error
Wed Jun 17 19:32:29 2020 Notice (6) TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 17 19:31:04 2020 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 17 19:31:01 2020 Warning (5) MDD message timeout;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 17 19:06:24 2020 Warning (5) Unicast DSID PSN startup error
Wed Jun 17 19:06:04 2020 Notice (6) TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 17 18:25:10 2020 Warning (5) Unicast DSID PSN startup error
Wed Jun 17 18:24:54 2020 Notice (6) TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 17 18:23:24 2020 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 17 18:23:22 2020 Warning (5) MDD message timeout;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 17 17:22:15 2020 Warning (5) Unicast DSID PSN startup error
Wed Jun 17 17:21:54 2020 Notice (6) TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 17 17:05:38 2020 Notice (6) TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 17 17:01:42 2020 Warning (5) Unicast DSID PSN startup error
Wed Jun 17 17:01:27 2020 Notice (6) TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 17 13:18:48 2020 Notice (6) TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:90:83:aa;CMTS-MAC=dc:eb:94:b5:e6:b1;CM-QOS=1.1;CM-VER=3.0;
snapshot of connection information with my signal levels right now:
| Cable Modem | |
|---|---|
| HW Version: | 1.5 |
| Vendor: | Technicolor |
| BOOT Version: | 2.1.8_Technicolor |
| Core Version: | 01.E6.01.22.54 |
| Model: | TC8305C |
| Product Type: | Technicolor DOCSIS 3.0 Packet Cable 2.0 advanced cable gateway |
| Flash Part: | 64 MB |
| Download Version: | 01.E6.01.22.54 |
| Serial Number: | 1408303052 |
| Downstream | Channel Bonding Value | |||||||
|---|---|---|---|---|---|---|---|---|
| Index | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| Lock Status | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked |
| Frequency | 651 MHz | 657 MHz | 663 MHz | 669 MHz | 675 MHz | 681 MHz | 687 MHz | 693 MHz |
| SNR | 40.3 dB | 39.9 dB | 39.6 dB | 39.5 dB | 39.4 dB | 39.4 dB | 39.8 dB | 40.0 dB |
| Power | 7.3 dBmV | 7.4 dBmV | 7.3 dBmV | 7.0 dBmV | 6.7 dBmV | 7.3 dBmV | 7.9 dBmV | 8.1 dBmV |
| Modulation | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM | 256 QAM |
| Upstream | Channel Bonding Value | |||
|---|---|---|---|---|
| Index | 1 | 2 | 3 | 4 |
| Lock Status | Locked | Locked | Locked | Locked |
| Frequency | 30 MHz | 36 MHz | 23 MHz | 17 MHz |
| Symbol Rate | 5120 Ksym/sec | 5120 Ksym/sec | 5120 Ksym/sec | 5120 Ksym/sec |
| Power Level | 46.0 dBmV | 44.5 dBmV | 46.0 dBmV | 47.5 dBmV |
| Modulation | ATDMA | ATDMA | ATDMA | ATDMA |
| Channel ID | 6 | 5 | 7 | 8 |
| CM Error Codewords | ||||||||
|---|---|---|---|---|---|---|---|---|
| Unerrored Codewords | 57547673 | 55785228 | 55783045 | 55780774 | 55778503 | 55776146 | 55773963 | 55771605 |
| Correctable Codewords | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Uncorrectable Codewords | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Accepted Solution
EG
Expert
•
110K Messages
5 years ago
The signal stats are o/k but the error log entries indicate that something is going on. Perhaps there is noise ingress into the line(s) somewhere.
There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS to see whether or not everything is in the green zone, see your node / cable plant and modem health, and also see a history plot for the modem. You should get a reply here in your topic. Good luck !
0
mwjonson
Frequent Visitor
•
6 Messages
5 years ago
Spent most of 90 minutes on the phone with comcast who ultimately made some changes to the modem and in the back end and think they have resolved the issue. I would have liked to know what sorts of changes were made, but they were working through a front line intermediary so I never talked to an engineer.
snapshot after they worked on it: no obvious changes here...
0
0
mwjonson
Frequent Visitor
•
6 Messages
5 years ago
Thank you! please do. I spent an hour and a half on the phone and they said they made changes (which were invisible to me) but the problems started again yesterday evening and happened again today, so it is not resolved. I have marked your reply "Best Answer" because I am sure escalation is the only good answer, thanks! (for anyone else reading this, if you have something marked best answer already and you get a better one, you can edit the old best answer at the three dots in the header and choose "not the answer" which will unmark that post -- then you can mark the new post)
(edited)
0
0
mwjonson
Frequent Visitor
•
6 Messages
5 years ago
Somebody has obviously been into my comcast modem today as the wireless network it broadcasts is now gone and i am blocked from logging into it.
0
0
XfinityJoeTru
Official Employee
•
7K Messages
5 years ago
Hi mwjonson. Thanks for posting on the Forum. Are you still experiencing connectivity issues with your service? If so, I can help further troubleshoot. If needed, please reach out to me via private message and include your full name and service address so I can assist you.
0
0
mwjonson
Frequent Visitor
•
6 Messages
5 years ago
I think there may have been a firmware upgrade done to the modem, and it was reset to defaults. i got back into it with default credentials and set it back up to have the home internet and other services. I guess i am just surprised this was done without any communication to me.
0
0
EG
Expert
•
110K Messages
4 years ago
0
0