cancel
Showing results for 
Search instead for 
Did you mean: 

Broadband Status

javedsaleem
On our wavelength

Below are my Hub 5 Stats.....lots of Pre RS Errors....what could be causing it ?

Cable Modem StatusItem Status Comments

Acquired Downstream Channel(Hz)330000000Locked
Ranged Upstream Channel(Hz)46200000Ranged
Provisioning StateOnlineOperational
107 REPLIES 107

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000044.55120QAM 641
143100000455120QAM 642
236600000455120QAM 643
33010000044.85120QAM 644
42360000044.35120QAM 645

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA00161

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
61038.52KQAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA2007400000000

Network Log

Time Priority Description
09-11-2023 17:17:54noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-11-2023 17:17:54warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-11-2023 16:14:42noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-11-2023 16:14:42warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-11-2023 11:06:07criticalReceived 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;
09-11-2023 11:02:52criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-11-2023 02:58:41errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-11-2023 16:05:05warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-11-2023 16:05:05noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-11-2023 15:03:03noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-11-2023 15:03:03warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-11-2023 16:46:02errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-11-2023 15:02:29noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-11-2023 15:00:13noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 22:31:56noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 22:28:55noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 20:42:19noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 20:39:56noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 09:21:05warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 09:21:05noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 09:21:01noticeREGISTRATION COMPLETE - Waiting for Operational status
01-11-2023 09:20:56warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 09:20:56warningDynamic Range Window violation
01-11-2023 09:20:55warningREG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 09:20:55warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 09:20:55warningDynamic Range Window violation
01-11-2023 09:20:50noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 09:20:43warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 09:20:41noticeHonoring MDD; IP provisioning mode = IPv4
01-11-2023 09:20:26criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-11-2023 09:20:26criticalCable Modem Reboot because of - HW or Power-On Reset
29-10-2023 06:46:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
 
 

Hi @javedsaleem 👋.

Thanks for reaching back out to us. Apologies for the issues that you are having with your Hub. We can certainly assist you, we would need to bring you in for a private message to discuss this and resolve. 

Please look out for the envelope on the top right of your web browser or if you are using a mobile device, it will be located under your profile icon.
 

Thanks.
 

Sabrina

I had an engineer come out early this week. On the last visit they forgot to change one of the old connections. The changed this and now the broadband seems to work a lot better.

Anyway, they suggested a internal rewire, but did not state whether the the cable will replaced from the brown box, outside the house,  all the way up to the router or just the part of the cable which is in the house.

 

I rang up to enquire but VM staff were not able to tell me anything.

 

Can you please look into this and find out what part of the wire will be replaced.

 

Thanks

Hi Javedsaleem 👋🏼.

Thank you for posting and welcoming you back onto the community forum 😊.

It also depends on what needs replacing internally.

I can have a look into this for you, so I can further investigate I will have to private message you. 

Please watch out for the envelope ✉.

Thank you.  

Ari - Forum Team


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


After convincing VM to rewire the inside of the house, the end result, is significant a improvement in the quality of the broadband.....but only after I had constantly requested it.

 

Errors still appear, but are less. I think the outside needs rewiring and then we will have no more errors.

 

I can across this post, which suggests old infrastructure can cause issues.....

https://riproar.com/perplexed-by-dbc-req-mismatch-between-calculated-value-for-p1-6hi-compared-to-cc...

 

 

You would think VM Staff and Engineers are competent in the job they do.....alas that is not the case.

 

I am a Novice in this area, but determination, led me to identify possible causes and suggest solutions that made a significant positive resolution.

Hi @javedsaleem thanks for your reply here, and sorry you are still having issues with your service at the moment.

We can see that you've been discussing things with Arissa over PM, so if you still need help with this then please reach out to her directly and she will do her best to help you further, I hope this helps!
Many thanks

Tom_W