Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Yet another broken upload thread

risc19
Well-informed

on ‎26-09-2022 16:29

Just like so many others, my upload is busted after 'work in the area'.
 
I wouldn't be so bad but only a while ago I had to get them to fix the download power levels.
 

It's on modem mode and its staying that way.

I know by the time someone gets back to me it may be fixed, so I'll get to my point.

I simple notification would that this was happening would have been just super.

We know you are working on improving upload capacity to try and stay competitive but,

Breaking everyone service to do so is not good.

 

 
3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
13260000038.55120 KSym/sec16QAM5
22580000038.35120 KSym/sec16QAM6
33940000038.85120 KSym/sec32QAM4
44620000039.35120 KSym/sec32QAM3

 

Network Log

Time Priority Description
Sun 25/09/2022 13:38:415MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:26:543SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:26:595Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:27:453Received 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.1;
Sun 25/09/2022 23:36:173No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:37:235B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:37:253No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:38:315B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:38:323No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:39:285B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:39:313No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:40:193SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:40:245Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/09/2022 23:40:293No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:08:403No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:09:465B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:09:473No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:12:063DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:12:143Received 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.1;
Mon 26/09/2022 00:12:313No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:13:215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:13:253No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:52:273Received 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.1;
Mon 26/09/2022 00:53:543No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:55:145B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:55:163No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:56:085B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:56:103No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:57:075B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:57:103No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:58:105B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:58:123No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:59:235B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 00:59:263No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 01:01:283DHCP FAILED - Request sent, No response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 01:01:523No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 01:03:125B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 01:03:465MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 01:03:503No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 26/09/2022 07:10:085MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

 

Its the constant barrage of this kind of behavior that makes people leave VM.

Untitlcxxced.pngUntitled.png

0 Kudos
5 REPLIES 5

farske
On our wavelength

on ‎26-09-2022 16:34

Im having the same issues, constant dropped packets on and off today, and you are right. Service is what drives people to move to other suppliers.
0 Kudos

Travis_M
Forum Team (Retired)
Forum Team (Retired)

on ‎28-09-2022 16:48

Hi @farske

 

Good afternoon and thanks for posting on our community forum.  

 

Sorry to hear about the issues with your broadband. I am going to drop you a private message to collect some more information so we can investigate further on this. Please keep an eye on your inbox for a message from myself.

 

Regards

Travis_M
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs
0 Kudos

risc19
Well-informed
In response to Travis_M

on ‎01-10-2022 20:42

Its still on the fritz....

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

14310000039.5205995120 KSym/sec64QAM2
22360000039.0205995120 KSym/sec32QAM5
33010000039.5205995120 KSym/sec32QAM4
43660000039.5205995120 KSym/sec32QAM3
54960000040.5205995120 KSym/sec32QAM1
0 Kudos

risc19
Well-informed
In response to risc19

on ‎02-10-2022 19:16

And now its fine again

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

14310000040.0205995120 KSym/sec64QAM2
22360000039.0205995120 KSym/sec64QAM5
33010000039.5205995120 KSym/sec64QAM4
43660000039.5205995120 KSym/sec64QAM3
54960000040.5205995120 KSym/sec64QAM1
0 Kudos

Steven_L
Forum Team
Forum Team
In response to risc19

on ‎04-10-2022 19:42

Thanks for coming back to us @risc19 and sorry for the issues that you're having with your upload speeds.

I can see that my colleague Travis is helping out via private message, if you could respond to his latest message, we can get this looked into further for you.

Regards,

Steven_L

0 Kudos
Top