Hey guys! Your info is priceless. I have been making in-depth hard copy guides to distribute to my new and seasoned technicians alike in the Comcast Xfinity market of the Deep South region. Alabama to be exact. I am enjoying nerding out with you guys, and y'all have made my unpublished side-project easier
I'm still confused whether many of these issues you describe in Nimble...I mean OpenVault...are actually service affecting, or just reducing the "robustness" (or whatever you've called it before?) but not actually noticeable by the customer. My next call today says "intermittent TV issues. Nimble: RxMER Correlation: RxMER-260-(node redacted) OFDM 1 In House Issue RxMER-260-(node redacted) OFDM 2 In House Issue Downstream Failed Parameters : MER [OFDM 2] Upstream Failed Parameters : MR Level, CM US MER, CMTS Rx Pwr Spectra Impairment : Adjacency, Wave RF Level: looks good" Remotely checked RF levels and only one OFDM at 987 MHz was slightly out of thresholds at -10. I refreshed it, and it's green now at -9.7. They're on our IP based TV boxes, which have had a known software issue for the past few months involving freezing, black screen, looping. This often makes me wonder how many calls are actually RF related, or even service affecting. This job, I tell ya 😐
Hi @grabasandwich - you raise an interesting discussion topic of proactive vs reactive that we are working on right now. Often times we identify impairments that are not subscriber impacting, as you indicate. However, given some time they will be subscriber impacting. But that doesn't help if you are more focused on putting out fires. We will be pushing out a release early this summer that gives a priority to each correlation group as to their priority, such as "Critical", "High", "Medium" and "Low". The critical and high priority correlation groups will be subscriber impacting, while the medium and low will be proactive. So if you see a Critical or High correlation group you will know that when you visit that customer or outside plant issue, you are actually improving the customer experience immediately rather than in the future. I'll look forward to your feedback. 👍
DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=9c:c9:eb:8b:3f:a8;CMTS-MAC=00:17:10:88:ec:0b;CM-QOS=1.1;CM-VER=3.1; US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=9c:c9:eb:8b:3f:a8;CMTS-MAC=00:17:10:88:ec:0b;CM-QOS=1.1;CM-VER=3.1; Any idea what are these?
Hi @DarkHarb, there are a could of error messages here. But likely not critical ones as long as the modem gracefully recovers. These likely are just "log" messages, unless you are experiencing issues. DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value" - This error is related to the Downstream Bounded Channel Request (DBC-REQ). The modem is detecting a mismatch between the calculated value for a specific parameter (P1.6hi) and the value provided by the CCAP US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 12 13" - This message suggests that there's been a change in the Upstream (US) profile assignment. The upstream channel (US Chan ID) 8 has had its profile changed from 11 13 to 12 13. In DOCSIS 3.1, profiles are used to adapt the modulation when impairments occur, possible examples are loose or damaged wiring in our your home network, drop cable or outside plant.
DBC-REQ: Dynamic Bonding Change Request, this is a mechanism the CMTS uses to ask the modem to adjust its transmission properties (frequency, power, modulation order, timing etc.) within its TCS, or its receiver properties within its RCS- this is a standard mechanic to keep the modem transmitting /receiving optimally for the plant conditions. Seems you have a mismatch in expected vs. measured power, so the CMTS is asking the modem to make some adjustment to its receive channel set, so that the measurement aligns with expectations. This isnt anything unusual, unless its happening a LOT, then it might indicate there's something wrong with the plant. The US profile assignment change is your CMTS telling your modem to drop down an interval-usage-code (IUC / Upstream modulation profile). I.e. there's too low of an SNR, or too many lost codewords post-FEC for your modem to sustain a high-order modulation in the upstream, drop down one order and continue transmitting. The CMTS is always testing to see if your modem is using an optimal setting to maximise bandwidth, whilst minimising errors. This is part of that.
@@Harb000 If its happening a lot, and you experience performance issues (i.e. packetloss, latency/jitter, low capacity), then it might indicate a fault in the outside plant. Your provider will need to take a closer look, its impossible to tell what the root-cause might be from modem logs :)
![[UNCUT] "บอสณวัฒน์" แฉ! แหล่งซุกเงินแก๊งบอส ขยันผิดที่ไม่กี่ปีก็เข้าคุก l คนดังนั่งเคลียร์ l17ต.ค.67](http://i.ytimg.com/vi/BL56qIfXYZM/mqdefault.jpg)
Hey guys! Your info is priceless. I have been making in-depth hard copy guides to distribute to my new and seasoned technicians alike in the Comcast Xfinity market of the Deep South region. Alabama to be exact. I am enjoying nerding out with you guys, and y'all have made my unpublished side-project easier
Hi Wesley thanks for watching and for the feedback. I hope you let your team know about our show and they join us live too 👍
I have no QAM with either of you guys,... I sure hope you guys do another live session, and I hope to join nex time!
LOL that's a good one. @TheRealflorin Looking forward to it!
I'm still confused whether many of these issues you describe in Nimble...I mean OpenVault...are actually service affecting, or just reducing the "robustness" (or whatever you've called it before?) but not actually noticeable by the customer.
My next call today says "intermittent TV issues. Nimble: RxMER Correlation: RxMER-260-(node redacted) OFDM 1 In House Issue RxMER-260-(node redacted) OFDM 2 In House Issue Downstream Failed Parameters : MER [OFDM 2] Upstream Failed Parameters : MR Level, CM US MER, CMTS Rx Pwr Spectra Impairment : Adjacency, Wave RF Level: looks good"
Remotely checked RF levels and only one OFDM at 987 MHz was slightly out of thresholds at -10. I refreshed it, and it's green now at -9.7.
They're on our IP based TV boxes, which have had a known software issue for the past few months involving freezing, black screen, looping. This often makes me wonder how many calls are actually RF related, or even service affecting.
This job, I tell ya 😐
Hi @grabasandwich - you raise an interesting discussion topic of proactive vs reactive that we are working on right now. Often times we identify impairments that are not subscriber impacting, as you indicate. However, given some time they will be subscriber impacting. But that doesn't help if you are more focused on putting out fires. We will be pushing out a release early this summer that gives a priority to each correlation group as to their priority, such as "Critical", "High", "Medium" and "Low". The critical and high priority correlation groups will be subscriber impacting, while the medium and low will be proactive. So if you see a Critical or High correlation group you will know that when you visit that customer or outside plant issue, you are actually improving the customer experience immediately rather than in the future. I'll look forward to your feedback. 👍
Is this SNR as it relates to the Shannon-Hartley theorem? If a SNR is really high then channel capacity can be high.
Yep, one in the same.
Lets get started lol sick burn there lol.
It’s a long time joke between us 😂
DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=9c:c9:eb:8b:3f:a8;CMTS-MAC=00:17:10:88:ec:0b;CM-QOS=1.1;CM-VER=3.1;
US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=9c:c9:eb:8b:3f:a8;CMTS-MAC=00:17:10:88:ec:0b;CM-QOS=1.1;CM-VER=3.1; Any idea what are these?
Hi @DarkHarb, there are a could of error messages here. But likely not critical ones as long as the modem gracefully recovers. These likely are just "log" messages, unless you are experiencing issues.
DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value" - This error is related to the Downstream Bounded Channel Request (DBC-REQ). The modem is detecting a mismatch between the calculated value for a specific parameter (P1.6hi) and the value provided by the CCAP
US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 12 13" - This message suggests that there's been a change in the Upstream (US) profile assignment. The upstream channel (US Chan ID) 8 has had its profile changed from 11 13 to 12 13. In DOCSIS 3.1, profiles are used to adapt the modulation when impairments occur, possible examples are loose or damaged wiring in our your home network, drop cable or outside plant.
@@Volpefirm no issues I was just wondering what they’re
DBC-REQ: Dynamic Bonding Change Request, this is a mechanism the CMTS uses to ask the modem to adjust its transmission properties (frequency, power, modulation order, timing etc.) within its TCS, or its receiver properties within its RCS- this is a standard mechanic to keep the modem transmitting /receiving optimally for the plant conditions. Seems you have a mismatch in expected vs. measured power, so the CMTS is asking the modem to make some adjustment to its receive channel set, so that the measurement aligns with expectations. This isnt anything unusual, unless its happening a LOT, then it might indicate there's something wrong with the plant.
The US profile assignment change is your CMTS telling your modem to drop down an interval-usage-code (IUC / Upstream modulation profile). I.e. there's too low of an SNR, or too many lost codewords post-FEC for your modem to sustain a high-order modulation in the upstream, drop down one order and continue transmitting. The CMTS is always testing to see if your modem is using an optimal setting to maximise bandwidth, whilst minimising errors.
This is part of that.
@@charliemoz It's happening alot so much that's all that appears.
@@Harb000 If its happening a lot, and you experience performance issues (i.e. packetloss, latency/jitter, low capacity), then it might indicate a fault in the outside plant. Your provider will need to take a closer look, its impossible to tell what the root-cause might be from modem logs :)