Regular Visitor
•
3 Messages
Router/Modem Keeps Rebooting (Arris SBG10)
I saw some other posts on here where people's routers/modems keep resetting. I've gone ahead and included the event log from my router from this morning when I was having issues with connection. As it states in my post, the router I'm using is an Arris Surfboard SBG10. This has been an issue off and on for several months at this point. Since I work from home and take many phone calls via VOIP, it can be quite troublesome at times. Any help would be much appreciated!
| Date Time | Event ID | Event Level | Description |
| 1/1/1970 0:03 | 82000700 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 1/1/1970 0:03 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:23 | 73040100 | 6 | TLV-11 - unrecognized OID;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:23 | 82000500 | 3 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:24 | 82000700 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:24 | 85010200 | 5 | TCS Partial Service;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:24 | 82000400 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:24 | 82000500 | 3 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:25 | 82000400 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:25 | 82000500 | 3 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:25 | 82000400 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:25 | 82000700 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:25 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:25 | 82000400 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:26 | 82000700 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:26 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:26 | 82000400 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:29 | 73040100 | 6 | TLV-11 - unrecognized OID;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 8:41 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
| 10/11/2020 9:10 | 73040100 | 6 | TLV-11 - unrecognized OID;CM-MAC=c8:52:61:eb:8a:21;CMTS-MAC=00:56:2b:76:96:3f;CM-QOS=1.1;CM-VER=3.0; |
jarredkal
Regular Visitor
•
3 Messages
4 years ago
Downstream
Upstream
0
0
EG
Expert
•
103.5K Messages
4 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
EG
Expert
•
103.5K Messages
4 years ago
Quite welcome !
0
jarredkal
Regular Visitor
•
3 Messages
4 years ago
Thank you for your prompt reply on a Sunday and escalating this issue. Much appreciated!
0
0
CCChe
Official Employee
•
6.9K Messages
4 years ago
Hi @jarredkal,
Thank you for using the Xfinity Forums! We appreciate you for sharing your logs to help isolate a cause for your issue. I'd be more than happy to review your account, your signals, and the health of your node to get this resolved. Please send me a private message with your full name, as it appears on your monthly statement. Click on my name ComcastChe, then click Send a message.
0