Sudden TBB Graph Issues with Hub 4

[alphaomega16]

Anybody else been having a lot of trouble with their modems being funny with TBB?

Can't seem to get it to stop going red, could this be related to QAM channel keep getting stuck on 16qam?

[Chris_W1]

HI alphaomega16, thanks for the message, 

I have looked into this and cannot see any disconnections, when was the graph done?

Can you  perform a reboot to see if anything changes? How is the connection at the moment?

Kind regards, Chris. 

[alphaomega16]

connection still laggy every now and then and ever since hte software update on the 15th it shows no errors on upstream or downstream which is nonsense because before the software update there was always some on the downstream and ive been seeing intermittent packet loss on TBB graph and the upstream QAM is still stuck on 16 and for some reason the network log wont show times of incidents unless I log in.

Just loading this website up just now took over 15 seconds. Also only just received an E-Mail saying I had a reply.

[Adduxi]

Post the power levels, Pre and PostRS errors and network log from the Hub. Once done we can comment.  Thanks

[alphaomega16]

Ever since the software update ive gotten 0 errors which is suspicious because since I have been having problems with teh upstream channel I check at least 30 times a day the status page and there have always been pre errors but as soon as the software update for hub went on on 15th ive not seen one error not even upstream timeouts which there should be due to the same issues ive been having and they were like clockwork.

Router status

• Status
• Downstream
• Upstream
• Configuration
• Networklog

Refresh data

Network Log

Time Priority Description

Sat Feb 18	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan	3	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 18	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 17	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 17	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Feb 16	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Feb 15	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan	3	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Feb 15	6	SW download Successful - Via NMS
Wed Feb 15	6	SW Download INIT - Via NMS
Fri Feb 10	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Feb	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Feb	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Feb	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Feb	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[alphaomega16]

Ok, why was I pushed an update to the superhub that is purposely hiding errors from the log so I cant see any pre/post or upstream errors?

Sun 19/02/2023 02:40:20

3

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

PS 

In the time it took me to alt tab, copy paste and post picture THIS PAGE STILL HASNT FULLY LOADED and after clicking "Post" it took over a minute to star out the mac addresses

[legacy1]

A case of "there are no problems you are looking for".

[alphaomega16]

I couldn't prove it via the pre errors but I sure can with the timeouts because they dont reset til you reboot the modem and the modem was rebooted 18th Feb at ~10:30 and that timeout was 1h 5m ago which I am assuming is the red mark above the green dot and the problems I had posting a reply here I am assuming is the big spike on the blue dot.

I don't know why I keep getting those big spikes but I wouldn't expect them to be there at nearly 4am when pretty much everyone is in bed but they are always there when stuff starts loading real slow, not sure if its related to teh upstream QAM dancing around playing musical chairs with its modulation but its the first time ive seen it above 16qam in several days

[Kath_F]

Hi alphaomega, 

Thanks for your posts here. 

I can see my colleague Travis has already replied to your posts here: High speeds yet poor internet

Please make sure you are only posting once about your issues. If you need to update the thread then just reply to your original thread rather than on a new one. We understand it's frustrating when something's not right however posting more than once about the same issues makes the boards look busier than what they actually are. It also means we could take longer to reply due to needing to sift through duplicate posts.

Have a look at Travis's reply on the other thread and stick with that one so we keep all the information in one place. 

Thanks,