For incoming traps, can Spectrum (be configured to) use the source IP address in the IP header, rather than the Agent Address inside the Trap's PDU, for determining the source device for posting the event to the device's model?
Context: large Spectrum about to be deployed in environment with all devices beyond a static NAT layer which translates IP header source and dest IPs (but not the Agent address inside trap PDU of course). There are overlapping IPs between all the 100 or so customer networks beyond the NAT. We shall be modelling all devices using their public (NAT'ted) addresses therefore. ( We know to discover using seedlist etc not range autodiscovery). SNMP versions in use for traps at the moment are 1 and 2c. If answer to main question above is no, any thoughts on best solution? TrapExploder with 'nat' action? (but will need an individual 'filter....nat IP' entry per every device that's out there - so 1000s of lines in the cf file to maintain!) *Sourceforge looperng? **Ncomtech's trapfwd? Supplementary question: Does Spectrum handle SNMPv3 traps - InformRequests ? Does anyone know? We did some tests and it seems to ignore them... Any input gratefully received! Cheers Dan. *http://www.ncomtech.com/trapfwd.html **http://sourceforge.net/projects/looper/files/looperng/2.0b1/ Dan White Senior Consultant Service Assurance [Devoteam] Tel. : +44 (0)20 7288 2822 [email protected]<mailto:[email protected]> [http://www.devoteam.com/images/environment.gif]Please consider the environment - do you really need to print this email ? --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
<<inline: image001.png>>
<<inline: image002.gif>>
![http://www.devoteam.com/images/environment.gif]Please](http://www.devoteam.com/images/environment.gif]Please){kind=link}