Hi Erwin, and Everyone,
Many thanks, Erwin, for your helpful and detailed answer (and also for kindly 
sharing your CLI mechanism for automatically generating a trapx config file 
from the Spectrum SSdb - looks great!).
I was pleased to hear your experience that your TrapExploders can cope with 
possibly 1000s of filter lines in their .cf config file.
I do have a couple of extra questions - (This thread is turning into a 
TrapExploder topic!...)


(1)    I believed that a 'filter.... nat xxxx' would need to be supplemented 
with another filter...action line to actually forward the trap, as the nat 
action just does the NAT'ing change and nothing else. (A comment that's in the 
default trapexploder.cf file says "Note that this action only does the address 
conversion.").
So do you have a line like:
filter * * * * * * forward spectroserveraddress
near the end of your .cf to make sure the NAT'ed traps actually do get sent on 
to your Spectrum server(s)!  ?


(2)    For performance reasons, is it not a good idea to prevent TrapExploder 
from needing to work its way down through the whole list of possible source 
addresses?... so maybe something like the following entries for each device?...
filter * "207\.209\.133\.62$" * * * * nat 207.209.133.62
filter * "207\.209\.133\.62$" * * * * forward spectroserveraddress
filter * "207\.209\.133\.62$" * * * * break

...Although I now realise this would actually make the file 3 times as long, 
too!.

Had no answer yet (nor from Support) re handling of SNMPv3 informrequests.  
Anyone know?

Many thanks again,
Cheers
Dan.


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>>

Reply via email to