Hi,
Furthur to my previous email. I use the net-snmp version 5.4.1.2, which use the
agentx other than smux for snmpd to communicate with subagents.
In version 5.2.1 as smux was used, we can define 'smuxpeer OID PASS' in
snmpd.conf, then restriction of traps from a specific subagent (told by the
OID) can be imposed. snmp daemon can then decide the trap coming from a
specific subagent can be forwarded or blocked.
I was wondering if agentx can still support this. E.g. once a trap is received
by snmpd via agentx, the daemon will know the trap is coming from which
subagent? Is there a functionality inheritance in the implementation of agentx
as to the smux in our latest codes?
Thanks a lot for your help,
Henry
From: [EMAIL PROTECTED]: [email protected]; [EMAIL
PROTECTED]: How to enable/disable a trap from a subagent?Date: Thu, 18 Sep 2008
10:36:48 +1200
Hi,I have a scenario that an enterprise mib acting as a subagent. When some
events happen, the subagent will send traps to snmpd via agentx. I was
wondering if there is a directive to be defined in the snmpd.conf that it will
allow/restrict the trap from this specific subagent to be sent out/blocked by
snmp daemon?Cheers, Henry
MSN NZ Travel Get inspired - dream, research, plan and book your next holiday
online with
_________________________________________________________________
Free Windows Live software. Chat, search, share pics and more
http://get.live.com/
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
