Hi!

I assume the SNR needs to be calculated at that specific point in time and
that can take a little while. RX power is probably easier for the modem to
keep track of internally.

I tried 100 reads using a bash script:

time for (( i=0 ; i-100 ; i++ )) ; do time snmpget -v2c -c public
172.19.11.225 1.3.6.1.2.1.10.127.1.1.4.1.5.3 ; done

real    0m7.656s
user    0m3.852s
sys     0m0.384s

Here, again, SNR takes a lot longer to report:

time for (( i=0 ; i-100 ; i++ )) ; do time snmpget -v2c -c public
172.19.11.225 1.3.6.1.2.1.10.127.1.1.1.1.6.3 ; done

real    0m30.375s
user    0m3.916s
sys     0m0.400s

This particular modem is a Compal CV6181ES running an old FW image
3.0.0.0-GA-01-SH. EPC3212 modems also respond slower whne queried for SNR.
I guess we have to blame Broadcom for this :)

EPC3212 response times (script as above)

real    0m9.023s
user    0m3.860s
sys     0m0.452s

real    1m16.681s
user    0m3.772s
sys     0m0.504s

One way to reduce polling time is to send multiple queries at the same
time and let the script sort out the different answers:

snmpget 172.19.14.195 -v2c -c public 1.3.6.1.2.1.10.127.1.1.1.1.6.3
1.3.6.1.2.1.10.127.1.1.4.1.5.3

This way, I managed to get the EPC3212 to respond in 1m15 sec for both
parameters. This way you save the overhead of asking two questions and the
modem compiling two answers, but the SNR query is still time consuming.


What are you trying to acheive? You might get past the delay by having a
background program continously read the SNR from the modems and
adding/updating the data to a database (Postgres/MySQL/...) and just read
from there whenever you need. That will give you the latest data possible
at an instant.

/Fredrik



> Hi,
>
> There is two docsis OID:
>
> 1.3.6.1.2.1.10.127.1.1.4.1.5.3        // DS SNR
> and
> 1.3.6.1.2.1.10.127.1.1.1.1.6.3        // RX PWR
>
> The first oid is return the DS SNR of the modem, and the second oid
> return
> the DS receive power level of the modem.
>
> I call like this:
> snmpget -v2c -c cmread 172.16.8.190 1.3.6.1.2.1.10.127.1.1.4.1.5.3
> snmpget -v2c -c cmread 172.16.8.190 1.3.6.1.2.1.10.127.1.1.1.1.6.3
>
> In both cases there is an answer from the modem, but the "RX PWR"
> version the return time
> is much more than the "DS SNR" version.
>
> This is very strange and incomprehensible for me, what is the reason?
>
> (when i have ~3500 modems, at the "DS SNR" oid version the total query
> time is: ~50sec,
> but at the "RX PWR" oid version the total time is: ~7min !!!)
>
> Thanks
> --
> Regards:
> Sztrepka Pál
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Net-snmp-users mailing list
> Net-snmp-users@lists.sourceforge.net
> Please see the following page to unsubscribe or change other options:
> https://lists.sourceforge.net/lists/listinfo/net-snmp-users
>


------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to