2009/1/21 Ragnar Moller <ragnar.mol...@ericsson.com>:
> Our problematic traps from a natted ip, 12.155.xxx.xxx which shops up as the
> source on the IP level.
> But inside the snoop (snp layer) there is a field called "agent addr", this
> fiels
> is different from the one above, showing a local lan address 192.168.xxx.xxx
You may need to investigate whether your firewall can support NAT mangling
within the SNMP packets. See RFC 2962 for some more information about this.
> - What is the real purpose of the field "agent addr"
>From RFC 1157 - section 4.1.6:
The form of the Trap-PDU is:
Trap-PDU ::=
:
agent-addr -- address of object generating
NetworkAddress, -- trap
> - Is the field mandatory
For SNMPv1 trap PDU's yes.
> - Is there a difference between snmpv1 and snmpv2c regarding this field
The SNMPv2-Trap2-PDU (as used by both SNMPv2c and SNMPv3)
does *not* include an agent-addr field. This is specific to SNMPv1 traps.
However SNMPv2 notifications may include a "snmpTrapAddress" varbind,
containing the agent-addr field value. This is specifically for use when
receiving SNMPv1 traps and forwarding them as SNMPv2 notifications.
> - In general, should there not be a configuration for the NMS to use one
> or the other a) use address in IP layer or b) use address in SNMP layer
> - In particular is an NMS surch as HPOV capable of this
That's a question for the HPOV people.
Our project is more aimed at SNMP agents and simple/dedicated applications.
We don't pretend to provide a full NMS.
Dave
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
