[ 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. ]
On Wed,
Dave Shield wrote:
You might do better looking at developing this as a "normal" MIB
handler (i.e. written in C) - either compiled into the main agent,
or as an AgentX subagent. That will receive all the relevant
varbinds from a single request, and allow you to work with all
three values at once.
On Wed, 2005-05-18 at 09:01, quhp wrote:
>I use a perl script as pass_persist EXEC to handle some OIDs.
>I find the perl script only handler the one field a time,
Correct.
The pass mechanism is designed to process an individual varbind.
It doesn't group related varbinds from a single reque
Hello,
I use a perl script as pass_persist EXEC to handle some OIDs.
snmpget and snmpgetnext requests work fine but I am not sure about set
requests.
The OID is about lvm (logic volume management) , i want to create a new lv
through snmp. then the command is :
snmpset -m all -v 2c -c pr
Hello,
after some difficulties in subscribing I hope this mail is send ok.
Sorry, if there were multiple copies of this question in the list.
I use a perl script as pass_persist EXEC to handle some OIDs.
snmpget and snmpgetnext requests work fine but I am not sure about set
requests.
# snmpget -v
Hello,
I use a perl script as pass_persist EXEC to handle some OIDs.
snmpget and snmpgetnext requests work fine but I am not sure about set
requests.
# snmpget -v 2c -c COMMUNITY HOST OIOD TYPE STRING
results in
# Error in packet.
# Reason: notWritable (That object does not support modification)
Hello,
I use a perl script as pass_persist EXEC to handle some OIDs.
snmpget and snmpgetnext requests work fine but I am not sure about set
requests.
# snmpget -v 2c -c COMMUNITY HOST OIOD TYPE STRING
results in
# Error in packet.
# Reason: notWritable (That object does not support modification)
