Re: Agent Builder V6.2.3 and SNMP version
doan nguyen <[email protected]>
| Newsgroups | gmane.comp.sysutils.tivoli.general |
|---|---|
| Message-ID | <CABEUGesib7dQvCiAUKYgsvQyyp0=NE+98i5QXnGFP84jgA_zMw__1096.834234386$1359496842$gmane$org@mail.gmail.com> |
Are you doing SubNodes with your SNMP Agentbuilder agent ? I created one with no Sub Nodes doing SNMP v3 GETS against our BigIP F5 and its working ok. Doan On 1/29/13, Allen Lutz <[email protected]> wrote: > How does one get nominated for the beta? > > On Tue, Jan 29, 2013 at 10:28 AM, Julius Loman <[email protected]> wrote: > >> On Tue, Jan 29, 2013 at 02:54:08PM +0000, Anders Soderback < >> Anders.Soderback-9m31T990Z1pWk0Htik3J/[email protected]> wrote: >> > I am developing an agent with Agent Builder V6.2.3 FP1 to retrieve data >> with >> > 'SNMP get' using the SNMPv2 connection type. The target was configured >> > to >> > support SNMPv2 , but no data was retrieved. The target had to be >> configured >> > to support SNMPv1 as well. Regardless of what the configuration was set >> to on >> > the Agent Builder agent, whether it was SNMPv1, v2c or v3 the agent >> always >> > connected with SNMPv1. This could be seen capturing the network packet. >> > >> > Has anyone come across this issue? Is there a fix? >> My colleague mentioned something similar - agent in agent builder always >> retrieved data using snmpv1 (he needed snmpv3). However agent built and >> installed worked well, so it's probably only an issue with agent testing >> feature. >> >> If you have access to 6.3 beta, try using the 6.3 agentbuilder. It allows >> you >> to test whole agent, not only particular attribute group. I guess this >> issue >> might be fixed in that version. >> >> >> -- >> >> [ Julius Loman ][ [email protected] ][ http://lomo.kyberia.net ][ >> icq:35732873 ] >> >> >> _______________________________________________ >> TME10 mailing list >> [email protected] >> Unsubscribe:[email protected] >> >> > > > -- > [email protected] > 845-546-1139 > -- Regards Doan Nguyen _______________________________________________ TME10 mailing list [email protected] Unsubscribe:[email protected]