Speed drops overnight from ~270Mbps to ~2-6Mbps 3rd day in row - SB6190 + DSA321N
Hello Everyone,
We upgraded our Internet speed to 300Mbps Package and as soon as we installed new SB6190 modem using a splitter provided by Cox, we were getting promised speeds. We activated SB6190 as our Internet modem and left Cisco DSA321N as our telephone modem.
Next day, around 6AM we noticed that our speed dropped to 2Mbps. Power cycling the modem seemed to fix the issue so we shrugged it off. Our 2nd night with this new setup resulted in the same issue - dropped speed overnight then power-cycling. The 3rd night is the same with one exception: while I was chatting around 8AM with Cox representative via online support, my speed at some point went from 5Mbps to 200+Mbps without me doing anything. I really did nothing except check the speed from time to time.
at 7:56, Jan 1:
Thank you for your time, (name removed), your service is not interrupted, however, I see here that the modem service levels are lower than it should be, I'm going to send a network refresh to your modem, most likely this will fix the issue, however the equipment will reboot and we might lose connection, if the modem after the reboot still have internet issues please contact us back and we'll schedule a technician visit to fix that as soon as possible.
Me
at 7:59, Jan 1:
have you send a refreshed signal already?
Jhon
at 7:59, Jan 1:
I am waiting for your response (name removed)
Me at 8:00, Jan 1:
Because I haven't lost the connection yet but my speed is back to what it is supposed to be without me doing anything
Jhon at 8:00, Jan 1:
I've made an additional configuration here.
Me at 8:00, Jan 1:
so it seems like the drop in speed during night time and morning has nothing to do with equipment on my side
Jhon at 8:00, Jan 1:
I am glad to hear that.
Me at 8:01, Jan 1:
What is an additional configuration?
Jhon at 8:01, Jan 1:
Modem ports configuration.
Me at 8:02, Jan 1:
Can you be more specific please? I would like to make sure that we won't be getting 3-6 download speeds over the next night-morning again Thank you
Jhon at 8:05, Jan 1:
I change the connection port of the modem in the system so that it has a better reception of the signal.
I thought that maybe "changing the port" was the reason why my speed improved, but 10 minutes later while still chatting with Cox representative I checked the speed again and noticed a drop to around 40Mbps, then 20Mbps and finally 6Mbps. We agreed that Cox will send "reset signal" after we finish our chat. Reset signal did not help with improving our speed.
I power cycled our modem and speed went back to normal. I don't understand what the issue is and why our speed slows down only at night. Is it possible that an extra splitter leading to 2 different modems is at fault? Please help. Thank you.
Below is our Event Log
Sun Dec 31 05:55:14 2017 |
4 |
Service Change Response rejected - Invalid transaction ID;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 05:58:19 2017 |
5 |
Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 06:53:00 2017 |
4 |
Service Change Response rejected - Invalid transaction ID;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 06:53:31 2017 |
5 |
Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 07:11:04 2017 |
4 |
Service Change Response rejected - Invalid transaction ID;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 07:11:14 2017 |
5 |
Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 09:22:31 2017 |
4 |
Service Change Response rejected - Invalid transaction ID;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 09:50:09 2017 |
5 |
RCS Partial Service;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 15:26:20 2017 |
3 |
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 15:26:20 2017 |
5 |
RCS Partial Service;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 15:26:20 2017 |
3 |
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 15:26:24 2017 |
5 |
Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Sun Dec 31 15:26:35 2017 |
5 |
RCS Partial Service;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 03:48:12 2018 |
4 |
Service Change Response rejected - Invalid transaction ID;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Time | Priority | Description |
---|---|---|
Mon Jan 01 04:03:49 2018 | 3 | No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 04:07:03 2018 | 5 | Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 04:30:35 2018 | 4 | Service Change Response rejected - Invalid transaction ID;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 04:34:51 2018 | 5 | Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 05:15:13 2018 | 4 | Service Change Response rejected - Invalid transaction ID;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 05:32:33 2018 | 5 | Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 07:30:36 2018 | 4 | Service Change Response rejected - Invalid transaction ID;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 07:34:49 2018 | 5 | Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 07:40:00 2018 | 4 | Service Change Response rejected - Invalid transaction ID;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:21:21 2018 | 4 | DCC-ACK rejected authentication failure;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:29:03 2018 | 5 | RCS Partial Service;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:29:52 2018 | 5 | Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:35:48 2018 | 4 | Service Change Response rejected - Invalid transaction ID;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:36:10 2018 | 5 | Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:55:00 2018 | 5 | RCS Partial Service;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:55:01 2018 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:55:01 2018 | 5 | RCS Partial Service;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:55:01 2018 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:55:06 2018 | 5 | Lost MDD Timeout;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jan 01 08:55:09 2018 | 5 | RCS Partial Service;CM-MAC=b0:da:f9:f0:2e:c7;CMTS-MAC=00:b0:e1:73:9c:e9;CM-QOS=1.1;CM-VER=3.0; |