Menu
Reply
  • 182
  • 5
  • 15
StormW4tch3r
Up to speed
113 Views
Message 1 of 4
Flag for a moderator

Connection check please

Hi all last couple days been getting MDD AND LOS MDD Timeout, lost internet for an hour at 4am this morning then again at 10am for about 30mins here is logs of SH3, before rebooting SH3 i did see channels 2 to 16 on downstream had power level of -33db and snr was in the 7's and modulation was unknown on them channels too. Also im on Gamer Package, should i have 4 upstream channels instead of 2?

Network Log
Date And Time Error Number Event Description
2016-11-25 09:57:33.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 09:57:47.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 09:58:32.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 09:58:32.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 09:58:46.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 09:59:49.00 68000100 DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:00:23.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:00:23.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:00:37.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:01:46.00 68000100 DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:04:41.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:04:41.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:04:54.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:05:14.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:05:14.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:05:28.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:07:51.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:07:51.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:08:05.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-25 10:08:54.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;


Downstream bonded channels
Channel Frequency(Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 210750000 5 37.6 256 qam 6
2 322750000 5.5 37.3 256 qam 20
3 314750000 5.1 37.3 256 qam 19
4 306750000 5.1 37.3 256 qam 18
5 298750000 5.3 36.3 256 qam 17
6 290750000 5 36.6 256 qam 16
7 282750000 4.9 37.3 256 qam 15
8 274750000 5 37.6 256 qam 14
9 266750000 5.1 37.3 256 qam 13
10 258750000 5.3 37.3 256 qam 12
11 250750000 5.3 37.3 256 qam 11
12 242750000 5.4 37.3 256 qam 10
13 234750000 5.1 37.6 256 qam 9
14 226750000 5.1 37.3 256 qam 8
15 218750000 5 37.6 256 qam 7
16 202750000 5 37.6 256 qam 5
17 194750000 5.3 37.6 256 qam 4
18 186750000 5.3 37.3 256 qam 3
19 178750000 5.3 37.3 256 qam 2
20 170750000 5.3 37.3 256 qam 1

Upstream bonded channels
Channel ID Frequency(Hz) Mode Power
(dBmV) Modulation Channel Bandwidth(Hz) Symbol Rate (ksps)
81 32600000 ATDMA 40.5 16 qam 6400000 5120
79 46200000 ATDMA 40.5 16 qam 6400000 5120

Here is ping graph as well..

23rd it last happened: http://www.thinkbroadband.com/ping/share-large/9111b700b8b31dbeab26b1a5140e3a6f-23-11-2016.png

Today: http://www.thinkbroadband.com/ping/share-large/f322ffe5b5c80414d8e629f895cddd53-25-11-2016.png

0 Kudos
Reply
  • 7.36K
  • 314
  • 523
Forum Team
Forum Team
84 Views
Message 2 of 4
Flag for a moderator

Re: Connection check please

Hi StormW4tch3r,

 

Welcome to the Community!

 

Sorry to hear you've had trouble with your connection.

 

I've located your account and I can see you've had a technician appointment to sort this for you. is everything OK now?

 

Speak soon Smiley Very Happy

 

Josh


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply
  • 182
  • 5
  • 15
StormW4tch3r
Up to speed
69 Views
Message 3 of 4
Flag for a moderator

Re: Connection check please

Hi he checked everything said he couldn't find out why it was doing it, but it has happned again at 2:04PM 09/12/16, looks like the same messages in log again, here is ping graph.. http://www.thinkbroadband.com/ping/share-large/b0f25f850214d3528caa7f4977160143-09-12-2016.png

Network Log Date And Time Error Number Event Description

2016-12-08 07:54:33.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-08 08:05:50.0068010400DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-08 09:12:49.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-08 09:31:09.0068010400DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-08 11:32:06.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:02:26.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:02:27.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:02:27.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:02:27.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:02:32.0084020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:02:35.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:02:49.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:03:30.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:04:04.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:04:04.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:04:04.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:04:05.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:04:08.0084020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:04:11.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-09 14:05:19.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 3.88K
  • 120
  • 203
Forum Team (Retired) Adam_L
Forum Team (Retired)
54 Views
Message 4 of 4
Flag for a moderator

Re: Connection check please

Hi StormW4tch3r, 

Thanks for letting us know that your connection is dropping still even after the engineer has been. I apologise for any inconvenience caused.

I have tested your connection from here and I can't see anything out of the ordinary no errors or time outs inside the Hubs logs and all of the power levels are within the preferred ranges.

Are you still having these issues? If so, please respond to me here with a recent copy of your Hubs logs for me to compare with the data we have here.

Also, when the connection drops, what does the Hubs light sequence indicate?

Take care, 

Thanks, 

Adam.


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply