That IPS Testing page shows you a number of things to verify that your IPS is running. In addition to that, I always like to have it actually catch something bad - or maybe something that's not bad but that looks bad like intentionally infecting a machine with something....install a back door perhaps. There are also some HTTP signatures that are fairly simple to generate hits on. I'm working on an issue right now where wew were doing just that type of testing and I installed Poison Ivy behind the ASA and it DID NOT catch it. But, the IDS is catching other issues so we're pretty sure it is inspecting traffic. We have a case open on that....seems like there isn't a signature but that's a side issue. I can't test this at the moment but how about going to http://www.somesite.com/index.htm?union%20select - I think that should trip an SQL signature. In fact, I'd like to build a library of things like that to use in testing an ids. For a snort-based ids, going to http://www.testmyids.com will give you a hit beause it's just a simple page that looks like you compromised a box.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...