mgilbert3
4 months agoTuning in
Frequent packet loss, high pre/post RS error counts etc
https://www.thinkbroadband.com/broadband/monitoring/quality/share/7ea541f8314f0f8347708ae1d3c4c63207e4d95a
Prior to 30th August I had reported:
Downstream - high power levels. Often a lot of pre and post RS errors
Upstream - gone to often 1 or 2 only. Power level is high
30th August - engineer visited and placed a 6db forward path on to the cable. This restored the number of upstream channels
Between 30th August and 14th August I found that apart from a few latency peaks and small amount of packet loss I wasn't experiencing hte loss of service.
14th September - replacement Hub 3 > Hub 5. Prior to replacement no change in upstream channel signal power from prior validation. After the install of the Hub 5 there was a short period of packet loss after 19:00. High number of errors in downstream post and pre RS; small number of T3 timeouts on the upstream channels
Below is what I have been experiencing since:
15th September - packet loss
16th September - high latency in the evening
17th September - whilst no loss of service experienced, did get high latency and packet loss in the evening
18th September - whilst no loss of service experienced, did get some packet loss
19th September - whilst no loss of service experienced, did get high latency and packet loss
20th September - upstream power levels have increased to min 45.5 to max 50.5. Packet loss experienced leading to some buffering and short loss of service
21st September - restarted Hub 5 to reset error counts etc. Can see earlier in the afternoon packet loss and latency spikes
22nd September - packet loss for a period of time overnight. High number of pre/post RS counts and T3 timeouts. No latency or packet loss during the day
23rd September - no packet loss, odd latemcy peaks
24th September - packet loss in the evening
25th September - restarted Hub 5 to reset error counts etc. Hub was off from c. 08:20 to c. 10:00
These are the log messages I have had this morning since the restart and I'll post the downstream/upstream info in an updated post
25-09-2024 11:40:49 | notice | US 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; |
25-09-2024 11:35:46 | notice | US 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; |
25-09-2024 11:35:45 | warning | RNG-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; |
25-09-2024 11:35:19 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 11:23:24 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 11:21:25 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 11:21:14 | warning | RNG-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; |
25-09-2024 11:19:33 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 11:18:00 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 11:15:49 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 11:08:27 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 11:06:42 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 11:05:29 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 11:03:14 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 11:01:50 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 10:46:08 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 10:42:48 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2024 09:56:29 | notice | REGISTRATION COMPLETE - Waiting for Operational status |