SerenayaXIV
On our wavelength
Joined 3 years ago
User Profile
User Widgets
Contributions
Re: T3 Noise Issues (again)
Quick update on this - after some back-and-forth and some escalation to network, the issue has been seemingly resolved. Big thanks to Forum Staff Member Daniel_Et (can't @ them) for all their help, efficiency and for taking the matter seriously. Really appreciate it. Hopefully it doesn't return but the track record sadly suggests otherwise. Fingers crossed, though.Re: T3 Noise Issues (again)
For the record this is what it looks like right now and this is a "better" day after being clear for most of the last week. Doesn't look like much but it affects my particular profession quite a lot especially when there's timeouts involved. Are there any reported issues even small-scale? Unsure why this keeps happening on a weekly basis now.Re: T3 Noise Issues (again)
For context, this is today with evidence of what's actually happening according to the log. Looks very much like network to me, or something's happened in the cabinet as I'd mentioned at the top of the thread. Again apologies for having to cancel the appointment though I did wish to reschedule, but neither the app or desktop site would let me do so, but rather simply returned a "sorry, we can't run a test right now" which is... not what I wanted to do. Cancellation was the only option that worked. 31-05-2024 18:35:40 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; 31-05-2024 18:33:31 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 31-05-2024 18:33:31 critical 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 31-05-2024 18:32:23 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 31-05-2024 18:14:55 notice CM-STATUS message sent. Event Type Code: 16; 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;T3 Noise Issues (again)
Hi. Simply gonna link previous threads of us having the same issue as it's once again back. Exact same thing. I've given it nearly a week to stabilise but more days than not, T3 timeouts are occurring once again. Our entire line from cab to router is less than a year old due to an RG11 (mentioned in the threads) and new lines + splitters from router to box. Highly doubt it's a problem with us specifically. Fault line and service page not reporting any issues thus far. I also need an engineer pronto to also fix power levels since it seems network have recently done something that's put them out of balance, along with a reportedly faulty firmware update(?). If we have the 6dB attenuator in the back of the hub5 then Upstream is slightly too high (around 50dB) and Downstream 3.0 is fine (+3-4dB) but 3.1 PLC is bordering on too low (-5dB sometimes). Without it however, we're in spec on 3.1 and Upstream but 3.0 Downstream channels are bordering on too high (+9-10dB). I've currently left it out to make sure Upstream noise is not amplified by being out of spec. No change, however. This is not the cause of the noise issues (as proven by all 3 occasions below) but probably isn't helping. That way I can talk to them about this issue more in-depth too. Not amused, VM. 3rd time we've had prolonged issues with this in less than 2 years. Can put up with a bad day or 2, it happens. Not your fault. Sadly it's never just that. It's potentially weeks every time without a solution which ends up boiling down to a network issue or 3 being eventually found and fixed. https://community.virginmedia.com/t5/Networking-and-WiFi/Yet-more-issues-with-downstream-upstream/td-p/5399691 https://community.virginmedia.com/t5/Networking-and-WiFi/Intermittence-in-Downstream-Upstream/td-p/5381491 https://community.virginmedia.com/t5/Forum-Archive/Regular-Intermittent-Upstream-dropouts/td-p/5202486 Any help appreciated. Thanks.Re: Yet more issues with downstream/upstream.
Received and details sent, John. Worth to mention that the timeouts returned today in a big spike, once only. Intermittent small packet loss has returned as well in line with the "short term issue" mentioned by you guys just days ago. Certainly seems like whatever is going on, is not quite fixed. A lot of noise on the line, denoted by the constant Upstream profile changing. BQM matches up. Time Priority Description 28-01-2024 00:50:32 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; 28-01-2024 00:45:29 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; 28-01-2024 00:43:53 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; 28-01-2024 00:38:50 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; 28-01-2024 00:37:11 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; 28-01-2024 00:32:08 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; 28-01-2024 00:30:37 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; 28-01-2024 00:25:34 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; 28-01-2024 00:25:26 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; 28-01-2024 00:20:23 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; 28-01-2024 00:06:12 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; 28-01-2024 00:01:09 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; 27-01-2024 23:50:59 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-01-2024 23:47:11 notice CM-STATUS message sent. Event Type Code: 16; 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; 27-01-2024 22:59:03 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; 27-01-2024 22:54:00 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; 27-01-2024 22:45:38 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; 27-01-2024 22:40:35 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; 27-01-2024 21:46:33 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-01-2024 21:43:00 notice CM-STATUS message sent. Event Type Code: 16; 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; 27-01-2024 21:29:42 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-01-2024 21:27:54 notice CM-STATUS message sent. Event Type Code: 16; 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; 27-01-2024 21:24:42 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-01-2024 21:24:42 critical 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-01-2024 21:23:35 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-01-2024 20:41:11 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-01-2024 20:35:05 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; 27-01-2024 20:28:33 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-01-2024 20:25:53 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-01-2024 20:25:30 notice CM-STATUS message sent. Event Type Code: 16; 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; 27-01-2024 20:02:35 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 27-01-2024 19:58: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.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Re: Yet more issues with downstream/upstream.
Hi, Joe. I understand that these things take time to investigate. SNR issues especially can be... well, anywhere. My question is - Is the fault put out while it's being investigated? Or only when it's found? It's very hard to know if VM are actively working to rectify a problem apart from the fault line, but it all culminates into not knowing if we're supposed to wait it out because it will be found, or if we have to chase it until someone investigates. Judging by the weeks we have to wait for SNR issues to be found, I would guess the latter but I don't know. Maybe it's just taking that long to find it and then publicise the fault. Anyway, It's not been too bad today and yesterday. The big T3 spikes regularity constantly changes from every day to every few days. Off the back of what was explained by Matthew, that short term issue seems to be back too but isn't causing any noticeable issues for now. I am happy to book an engineer if it's seen as fit to do so still, but I don't really feel like having yet another £25 charge because nothing was actually fixed. That's also starting to feel a bit disingenuous. We're charged for calling someone out just so we can tell them it needs escalating after they confirm there's no problem here. The last couple of times I've talked to engineers they've agreed that everything's been tried here (since I have it all noted down) but they don't know what it could be because it's outside the scope of the property or is something so obscure that it'll take dozens to notice.Re: Yet more issues with downstream/upstream.
Hi, Beth. I would presume that instability was covering the minor packet loss that was permeating the last couple of days. I can see that has cleared up so thank you for that, however there was a huge spike as a result of consecutive T3 Timeouts (likely noise in the network yet again) at around 2pm. Problem is not entirely resolved and this has been the main issue on and off since October. Network SNR faults being found were the only way it stopped. Unless something was changed in the cab up the road to cause this, it is almost certainly not the property's connection as all of it is new as of the last few months in attempts to fix it, from Hub to cab. You may send an engineer if you like but I can only tell them it needs to be escalated as it won't be found here. One of them even said they knew a thing or two and that the problem could be anywhere up to the head-end. Sadly they would not respond to emails after telling me to keep in contact with evidence that they could escalate to network. I'm sorry I could not come back with good news. I would love the issue to be here because it would be fixed faster and easier, but it's evidently not after 8 engineer visits and every check in the book's been done...please help 😞
