Menu
Reply
Highlighted
Joining in
  • 5
  • 0
  • 0
Registered: 4 weeks ago
Message 1 of 2 (50 Views)

New superhub 3 - Same old T3 time out issue

You replaced my Superhub 2 as I was getting constant T3 errors and no internet access but the problem has not be fixed with the new superhub 3 (infact there are also T4 errors appearing in the logs now).

 

Cable Modem Status Item Status Comments

Acquired Downstream Channel(Hz)
299000000
Locked
Ranged Upstream Channel(Hz)
23600000
Locked
Provisioning State
Online

 

 

Downstream bonded channels Channel Frequency(Hz) Power
(dBmV) SNR
(dB) Modulation Channel ID

12990000003.437.3256 qam13
23230000003.437.6256 qam16
33150000002.937.3256 qam15
4307000000337.3256 qam14
52910000003.437.6256 qam12
62830000003.737.6256 qam11
72750000003.737.6256 qam10
82670000003.737.6256 qam9
92590000003.738.6256 qam8
10251000000437.6256 qam7
112430000003.237.6256 qam6
12235000000437.6256 qam5
132270000003.737.6256 qam4
142190000004.537.3256 qam3
152110000004.638.6256 qam2
162030000004.638.6256 qam1

 

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

4723600000ATDMA35.516 qam64000005120
4536800000ATDMA35.516 qam6400000

5120

 

Network Log Date And Time Error Number Event Description

2017-05-18 15:51:26.0082000200No Ranging Response received - T3 time-out;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-18 15:59:50.0084000700RCS Partial Service;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-18 15:59:50.0082000200No Ranging Response received - T3 time-out;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-18 16:19:07.0084000700RCS Partial Service;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-18 16:19:43.0082000200No Ranging Response received - T3 time-out;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-18 16:20:31.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;
2017-05-18 16:37:01.0084000700RCS Partial Service;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-18 16:37:12.0082000200No Ranging Response received - T3 time-out;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-18 18:29:38.0084000700RCS Partial Service;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-18 18:29:51.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;
2017-05-18 18:50:34.0082000200No Ranging Response received - T3 time-out;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-18 21:29:21.0084000700RCS Partial Service;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-18 21:29:34.0082000200No Ranging Response received - T3 time-out;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-19 01:55:21.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;
2017-05-19 01:56:15.0082000200No Ranging Response received - T3 time-out;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-19 20:14:46.0084000700RCS Partial Service;CM-MAC=4************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-19 20:15:07.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;
2017-05-19 20:28:13.0082000200No Ranging Response received - T3 time-out;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
2017-05-19 20:29:01.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=************;CMTS-MAC=0************;CM-QOS=1.1;CM-VER=3.0;
2017-05-19 20:29:56.0082000200No Ranging Response received - T3 time-out;CM-MAC=************;CMTS-MAC=************;CM-QOS=1.1;CM-VER=3.0;
Reply
0 Kudos
Forum Team
  • 8.74K
  • 246
  • 513
Registered: ‎07-04-2015
Message 2 of 2 (13 Views)

Re: New superhub 3 - Same old T3 time out issue

Hi DpyMky,

 

Thanks for posting back on the community and apologies you are having an issue with the broadband connection.

 

I've taken a look into this and as there have been network faults reported in your area that has caused intermittent connection, this could be the reason for the T3 time-outs you are seeing. As the router has been online for 11 days, can you reboot the router when you get chance and if these time-outs are continuing we can book an engineer appointment to check this over.

 

Speak to you soon

Sam


New around here? To find out more about the Community check out our Getting Started guide


Reply
0 Kudos