You could use one of the following tools to generate traffic that the IPS could react too.
Open Source examples of VA tools include Nessus or Nmap. Also, Stick and Snot come to mind, as they were developed specifically to test security devices. If you like to craft packets, you could use Hping. If you want to get really fancy, you could use the Metasploit Framework...
If you prefer a commercial solution, there is the standard gamut of VA tools, or you could use something like IDS Informer or TrafficIQ. If you want to use a framework, CORE Impact will do the trick.
Any one of the above suggestions will generate traffic that an IPS will react to. Your choice will be driven by the volume and complexity of the testing you want to perform.
True, but now you've customized the sensor's configuration without necessarily proving that it was properly configured to begin with.
If the author of the original question has the intention of testing the configuration of the IPS, or more specifically observing what it does to traffic flow when it blocks, a few pings won't really accomplish it.
What I am trying to say is this - there's a big difference between testing to see that the IPS reacts and validation testing to see that the IPS reacts [i]correctly[/i].
That's why I provided a list of options, all with different purposes.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :