To enable the ipv6 support for the agent I included below line in snmpd.conf
agentaddress udp:161,tcp:161,udp6:161,tcp6:161
When I start the agent as snmpd -f -L I get below message
getaddrinfo: Name or service not known
Further when I issue the snmpget command with ipv6 address as specified in
HI,
I could successfully register the context in snmpd with prefix and "" as
context.
I could register one context this way, but failing for the other, below is
the code snippet
DEBUGMSGTL(("dot1qBase",
"Initializing dot1qVlanVersionNumber scalar integer.
Default value = %d\
Hi,
Can net-snmp perl module be used to support the multiple instances of same
MIB(scalar)?
I want to implement the Bridge MIB which is designed for one bridge to
support multiple bridges.
Can I get some pointers to make the basic net-snmp (C module) support
dynamic context names OR
any way to s
My intention wasn't the demand for dynamic context names.
On Thu, Aug 27, 2009 at 12:59 PM, Dave Shield wrote:
> 2009/8/26 Deepali Singalkar :
> > When is the support for dynamic context names expected?
>
> When someone writes the necessary code.
>
> Remember, t
Thanks for clarification!
When is the support for dynamic context names expected?
On Wed, Aug 26, 2009 at 10:47 PM, Wes Hardaker <
harda...@users.sourceforge.net> wrote:
> >>>>> On Wed, 26 Aug 2009 12:53:01 +0530, Deepali Singalkar <
> deepali.singalk...@g
Hi,
I am develoing a AgentX subagent for virtual devices.
Here I need to support same MIB tree for multiple virtual devices from same
subagent.
I tried setting the contextname in /usr/local/share/snmp/snmpd.conf file
with the defContextName directive.
It fails with the error message unknown token
