cancel
Showing results for 
Search instead for 
Did you mean: 

16 Consecutive T3 Timeouts Causing Internet Blips - another thread

fleetafoot
On our wavelength

Thanks to @AVI68 for communicating frustrations.  I have a similar problem and have my first engineer visit scheduled for 28th July.  I have tried three times via the CS, hard reset the hub, replaced in-house cables where I can, and even got a WiFi Pod for my CS efforts (go figure that waste of money - I have not even taken the device out of the box). But I have raised a formal complaint,  BQM and Network Log errors correlate - here is the BQM graph 

Thanks for communicating your frustrations.  I have a similar problem and have my first engineer visit scheduled on 28th July.  I have tried three times via the CS, hard reset the hub, replaced in-house cables where I can, even got a WiFi Pod for my CS efforts (go figure that waste of money - I have not even taken the device out of the box). But I have raised a formal complaint,  BQM and Network Log errors correlate - here is the BQM graph 

fleetafoot_1-1719353407446.png

 

Any comments are welcome as I am not a network expert but I do have rudimentary knowledge.

I'll attach the NW log in the following post

 

Any comments are welcome as I am not a network expert but I do have rudimentary knowledge.

12 REPLIES 12

fleetafoot
On our wavelength
TimePriorityDescription
25-06-2024 22:55:25noticeGUI Login Status - Login Success from LAN interface
25-06-2024 22:50:45warningDynamic Range Window violation
25-06-2024 22:50:45warning
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 22:48:06warning
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 22:47:52notice
US profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 22:16:44notice
US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:39:35notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:37:48notice
CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:06:44critical
16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:06:44critical
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:06:20critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:06:18warning
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:06:17notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:05:55warning
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:05:54warning
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:05:54critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:05:50critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:05:48critical
No Ranging Response received - T3 time-out;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:05:47critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:05:47critical
No Ranging Response received - T3 time-out;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:05:46critical
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:05:46critical
16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:04:38critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:03:51notice
CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 21:00:30warningDynamic Range Window violation
25-06-2024 21:00:30warning
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 20:58:50warning
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 20:51:24notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 20:50:41critical
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 20:50:41critical
16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 20:49:44critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 20:49:43critical
16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
25-06-2024 20:49:43critical
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xxx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;

jbrennand
Very Insightful Person
Very Insightful Person

Your BQM is rejected - it probably has your i.p. displayed - post again this way...

Click the lower link (Share Live Graph) then, click generate.

Copy the text in the Direct Link box, beware, there may be more text than you can see. On here click the Link icon (2 links chain to the left of the camera icon) In the URL box paste the link you copied and then click OK


--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

fleetafoot
On our wavelength

avi68
Up to speed

Can you post your downstream and upstream figures? Your bqm looks a lot worse then mine.

Hi Fleetafoot, 

Thanks for posting and welcome back to our Community Forums! 

Sorry you're seeing some errors on your Hub channels. 

We've taken a look at your services on our side and haven't found any issues, everything is running smoothly from what we can see. This means the connection that is going into your home is good. 

Could we ask if the device you've done the BQM on is connected via Ethernet or WIFI please? 

Do you have your Hub in modem mode at all?

Using a VPN or any other 3rd party equipment? 

Thanks,

Meg

@ForumTeaM

Th BQM content has nothing to do with the device displaying the result.  The BQM ping is from Thinkbroadband to the public IP address of the user’s circuit.  That would either be in the Hub itself when in router mode or the attached router if in modem mode.   Nothing to do with WiFi. 

Seph - ( DEFROCKED - My advice is at your risk)

Roger_Gooner
Alessandro Volta

The log indicates repeated failed attempts by the hub to establish communication with the CMTS. Unless there is a dodgy cable connection inside the home (and so easily remedied by the customer), a tech needs to be sent round.

--
Hub 5, TP-Link TL-SG108S 8-port gigabit switch, 360
My Broadband Ping - Roger's VM hub 5 broadband connection

fleetafoot
On our wavelength

Update on my issue. After a visit by VM tech who said he swapped the connection port on the street cabinet and checked signals which originally were bad and we're now good. The tech knew his stuff, understood the problem and followed up with a call 3 days later to check. The BQM and network logs are clean since a few hours after the change. Kudos to the tech and VM, just a pity it took a complaint to get things done.