New Poster
•
1 Message
"Started Unicast Maintenance Ranging - No Response received", "Dynamic Range Window violation"
Hi all,
Really at wits end here. For the past few months I've experienced frequent connection drops from 10 seconds to 1-2 minutes. Bought a new modem and the issue persists.
Any help would be greatly appreciated!
Here's a short excerpt from my brand new (not refurb) Arris SB6183 Event Log:
Fri Jun 19 21:59:54 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 00:40:57 2020 | Warning (5) | Dynamic Range Window violation |
Sat Jun 20 01:02:59 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 01:24:14 2020 | Warning (5) | Dynamic Range Window violation |
Sat Jun 20 03:59:24 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 12:44:55 2020 | Warning (5) | Dynamic Range Window violation |
Sat Jun 20 13:57:13 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 13:58:28 2020 | Warning (5) | Dynamic Range Window violation |
Sat Jun 20 14:17:48 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 14:18:08 2020 | Warning (5) | Dynamic Range Window violation |
Sat Jun 20 16:20:44 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 18:17:46 2020 | Warning (5) | Dynamic Range Window violation |
Sat Jun 20 19:49:19 2020 | Warning (5) | MDD message timeout;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 19:49:19 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 19:50:22 2020 | Warning (5) | MDD message timeout;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 19:50:22 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 19:59:36 2020 | Warning (5) | MDD message timeout;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
Sat Jun 20 19:59:37 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=f8:a0:97:b9:1e:e1;CMTS-MAC=00:5f:86:93:d7:22;CM-QOS=1.1;CM-VER=3.0; |
And modem status:
Status
No Responses!