[SNMP4J] Running TestAgent with SNMPv2c

[Eugene R. Snider]

The only change I found necessary to work well in a v2c environment was 
to modify the notification originator and make the following change in 
the agent class. It may not be elegant but it works.

I've attached the V2CNoificationOriginator class I used. I simply took 
the existing originator and removed everything that wasn't v2c. The 
traps have been tested with a variety of managers including openView and 
unleashedSNMP with success.

I experienced no challenges with the agent responding to v2c managers.

Gene

        /*
        notificationOriginator = new NotificationOriginatorImpl(session,
                vacmMIB, snmpv2MIB.getSysUpTime(), snmpTargetMIB,
                snmpNotificationMIB);
        */       
        notificationOriginator = new V2CNotificationOriginator(session,
                vacmMIB, snmpv2MIB.getSysUpTime(), snmpTargetMIB,
                snmpNotificationMIB);


Frank Fock wrote:
> Hi,
>
> Miroslav wrote:
>>
>> is it possible to run the TestAgent with SNMPv2c only?
>
> Yes, but you will have to modify the code of it
> or change its VACM configuration (which can
> make SNMPv2c not accessible also it is built into
> the agent).
>
>> Would it be possible to get rid of the VACM and USM configuration
>> then to have a minimal SNMPv2c agent? What are the necessary steps?
>
> You need the VACM. The USM can be dropped - simply
> remove any code referring to it.
>
>> I assume that VACM and USM are V3 specific, but if not implementing
>> these methods, the agent does not respond to any SNMP requests.
>
> VACM is not SNMPv3 specific.
>
> Best regards,
> Frank
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: V2CNotificationOriginator.java
URL: <http://oosnmp.net/pipermail/snmp4j/attachments/20071201/967d3246/attachment.ksh>