Thanks a lot Mike for your answers, even though you don't think highly of snmp v2c, which our customer requests (which rules out snmp v3).
The key question in this becomes "Is HPOV capable of using the source address on IP level instead of the "agent addr" field? And if it is what are the instuctions how to do so ? Mike also proposes changing the agent addr. Well, the source address is changed by a firewall, so I Guess we have to look into the firwall and see if the address on snmp level can be modified there. I'm also looking into my real source to see if I can modify it there. Ragnar -----Original Message----- From: Mike Ayers [mailto:mike_ay...@tvworks.com] Sent: mercredi 21 janvier 2009 20:20 To: Ragnar Moller; net-snmp-users@lists.sourceforge.net Subject: RE: What's the "agent addr" for ? Is it mandatory ? > From: Ragnar Moller [mailto:ragnar.mol...@ericsson.com] > Sent: Wednesday, January 21, 2009 12:56 AM > 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 > > Of course our NMS is using the field "agent addr" which is messing > things up You can't point it elsewhere? > So I would really want to know: > - What is the real purpose of the field "agent addr" Its purpose was to identify the source of the trap, as your system is trying to use it. The problem you are seeing is only one of many which led to the replacement in SNMPv3 of the agent_addr with the engineID, which identifies an SNMP agent without regard to its interfaces. > - Is the field mandatory For SNMPv1, yes. > - Is there a difference between snmpv1 and snmpv2c regarding this > field I don't know, being a dreadful snob who still calls v2c a "non-protocol". There is a difference between SNMPv1 and SNMPv3, as mentioned above (it's one of a bevy of fundamental conceptual diofferences). > - In general, should there not be a configuration for the NMS to use > one That's tricky. For older devices, the agent_addr may be your only good answer. Reconciling engineId to network addresses can be considered frustrating, even though it solves some otherwise intractable problems. > or the other a) use address in IP layer or b) use address in SNMP > layer Both (a) and (b) are agent_addr solutions, with the same risk. > - In particular is an NMS surch as HPOV capable of this It bloody well should be! Can you use SNMPv3 notifications (aka v2 traps)? HTH, Mike ------------------------------------------------------------------------------ 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
