Re: some problem : timeout / burst get multi-oid
[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
2008/4/28 JAW-Woei MAA <email@example.com>:[color=blue]
> In our knowledge, timeout means the period of responsive time after we set
> the packet out.
> In reality, when we work it within the net-snmp, it wouldn't need the
> responsive time if it can find host.[/color]
I'm sorry - that still doesn't make much sense.
If you're running a command such as
snmpwalk -t 3 -r 0 -v 1 -c public localhost system
then this should time out after three seconds, if the agent doesn't respond.
If that's not what you are looking for, then you're going to have to give
a lot more detail about exactly what you are trying to do.
> If continually catch oid within the attach file, all library would crash as
> it go through the No.3926 oid.
> We have to restart the net-snmp before moving to the next step.[/color]
The snmpwalk output that you posted isn't a lot of help,
without the accompanying MIBs that describe it.
It's clear that the problem arises somewhere within your
private enterprise tree. But I can't tell whether
is the last column in this table, or not.
What do the following report:
snmpgetnext ..... .188.8.131.52.4.1.86184.108.40.206.4.5
snmpgetnext ..... .220.127.116.11.4.1.8618.104.22.168.5
snmpgetnext ..... .22.214.171.124.4.1.8691.2.9
snmpgetnext ..... .126.96.36.199.4.1.8692
That should at least indicate where you should be looking
for the source of the problem.
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
Net-snmp-users mailing list
Please see the following page to unsubscribe or change other options: