Menu
Reply
  • 253
  • 2
  • 6
Big-Gaz
Up to speed
116 Views
Message 1 of 4
Flag for a moderator

Possible Upstream issue with T3s

Hi,

This last hour I have had 3 drop out, where the Hub 3 would drop the connection and try and reconnect.

I looked in the stats of the Hub

Upstream bonded channels Channel ID Frequency(Hz) Mode Power
(dBmV) Modulation Channel Bandwidth(Hz) Symbol Rate (ksps)

4 46200000 ATDMA 45.5 16 qam 6400000 5120
5 39400000 ATDMA 45.5 16 qam 6400000 5120

       
       




1970-01-01 00:01:19.00 84020100 Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:10:27.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:16:53.00 73040100 TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:cc;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:17:05.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:19:57.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:cc;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:19:57.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:cc;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:19:58.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:cc;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:19:58.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:19:59.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:19:59.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:20:00.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:20:00.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:21:56.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:21:56.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:21:57.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:21:57.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:21:58.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-27 16:21:58.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;

_____________________

_____________________
Regards
Gaz
0 Kudos
Reply
  • 253
  • 2
  • 6
Big-Gaz
Up to speed
111 Views
Message 2 of 4
Flag for a moderator

Re: Possible Upstream issue with T3s

Here we go again Smiley Sad

4 46200000 ATDMA 45 16 qam 6400000 5120
5 39400000 ATDMA 45 16 qam 6400000 5120

They was both 64 qam from around 7pm last night.

2017-03-28 11:53:34.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:34.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:35.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:35.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:36.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:36.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:37.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:37.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:38.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:38.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:39.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:40.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:40.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:41.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:41.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:42.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:42.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:43.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:43.00 82000700 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2017-03-28 11:53:44.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;

_____________________

_____________________
Regards
Gaz
0 Kudos
Reply
  • 3.88K
  • 120
  • 203
Forum Team (Retired) Adam_L
Forum Team (Retired)
68 Views
Message 3 of 4
Flag for a moderator

Re: Possible Upstream issue with T3s

Hi Big-Gaz, 

Thanks for the post! I am sorry to hear about your issues with T3 time outs occurring, I apologise for any inconvenience caused.

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

Are you still having these issues? If so, how are you connecting wired or wireless?

Also, please include a recent copy of your Hubs logs for us to compare with the information we have here.

Do these issues still occur even when the Hub is connected in modem mode?

Speak soon, 

Thanks, 

Adam.


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


0 Kudos
Reply
  • 253
  • 2
  • 6
Big-Gaz
Up to speed
63 Views
Message 4 of 4
Flag for a moderator

Re: Possible Upstream issue with T3s

Hi,

It has returned to normal now.
Yestarday, the status page said they was doing something in the area.
So I presume they fixed it

_____________________

_____________________
Regards
Gaz
0 Kudos
Reply