| Attachment | Size |
|---|---|
 traffic.PNG | 81.79 KB |
| signal.PNG | 65.45 KB |
Hi,
we are using the old cacti system for monitoring signal and BW parameters from modems. We are using this for over 15 years with THG 541 modems.
But we are on Docsis 3 now and using Ubee EVW32C modems.
We are using this OIDs.
print F "mdm\@$modemIP:.1.3.6.1.2.1.10.127.1.1.1.1.6.3\n"; # dspower
print F "mdm\@$modemIP:.1.3.6.1.2.1.10.127.1.1.4.1.5.3\n"; # snr
print F "mdm\@$modemIP:.1.3.6.1.2.1.10.127.1.2.2.1.3.2\n"; # uspower
print F "mdm\@$modemIP:.1.3.6.1.2.1.2.2.1.10.2\n"; # ifInOctets
print F "mdm\@$modemIP:.1.3.6.1.2.1.2.2.1.16.2\n"; # ifOutOctets
I notice some "issues" related to BW graphs. I am attaching the pictures.
You could see that the signal graphs are OK, but the BW graphs have pretty much interruptions.
We have also done some diagnostics with "pings" for a while behind the modem and there was no packet loss, even when the interruptions on the BW graphs appear. So I assume that this is not what customers could "detect" but I not 100% sure.
Does anybody have some advice or a similar experience?
Thanks and advance, 0603
I would start by switching to the 64 bit counter versions of the bandwidth oids
ifHCInOctets - 1.3.6.1.2.1.31.1.1.1.6
ifHCOutOctets - 1.3.6.1.2.1.31.1.1.1.10
these counters will not wrap as fast, with the 32 bit counters you are currently polling, the downstream especially will wrap fairly quickly.
I haven't seen a proper working counters on the cable modem.
What you'll need to do is look at DOCS3-QOS. There you'll find traffic per Service Flow. You can then combine all downstream/upstream service flows or display graphs per service flow. There is also a better way to do it via IPDR. If you're interested in QOS or IPDR please leave your email in the comment and I'll contact you.
I haven't seen a proper working counters on the cable modem.
What you'll need to do is look at DOCS3-QOS. There you'll find traffic per Service Flow. You can then combine all downstream/upstream service flows or display graphs per service flow. There is also a better way to do it via IPDR. If you're interested in QOS or IPDR please leave your email in the comment and I'll contact you.
Please take a look at this two links and the attached picture
https://snapshot.raintank.io/dashboard/snapshot/6Ed9nmxqRQA0cK8n9M6G6HLf...
https://snapshot.raintank.io/dashboard/snapshot/FHo3PoPuxYA1d2p8yUl3Xb30...
these look nice - can you share the templates ?
https://github.com/l-n-monitoring/CM-RT-GRAPH
Interested in your set up. We use observium and cacti, but it would incredible to get that kind of detail.
contact me: jobacare@gmail.com