White Paper
All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 7 of 12
Step 5.2 Copy the downloaded package (IOS-S259-CLI.pkg) to the TFTP server and load the
signatures from TFTP server to Cisco IOS IPS:
copy tftp://<Server IP address>/IOS-S259-CLI.pkg idconf
training#copy tftp://10.10.10.2/IOS-S259-CLI.pkg idconf
Loading IOS-S259-CLI.pkg from 10.10.10.2 (via Vlan1): !!!
Step 5.3 Verify the version, signatures were loaded, and the active signature count using
the following command:
show ip ips signature count
training#show ip ips signature count
Cisco SDF release version S259.0
—Signature package version
Trend SDF release version V0.0
Signature Micro-Engine: multi-string
Total Signatures: 3
Enabled: 3
Retired: 3
—Skipped
Signature Micro-Engine: normalizer
Total Signatures: 9
Enabled: 8
Retired: 1
Compiled: 8
Total Signatures: 1964
Total Enabled Signatures: 736
Total Retired Signatures: 1625
Total Compiled Signatures: 338
—Total active compiled signatures
Total Signatures with invalid parameters: 1
training#
Additional Commands and References
After Cisco IOS IPS loads the signature package into memory, it starts reading signatures and
attempts to build them according to the configuration. An error message such as:
%IPS-3-INVALID_DIGITAL_SIGNATURE: Invalid Digital Signature found (key not found)
means the public crypto key is invalid. Refer to “Configuring Cisco IOS IPS Crypto Key” (Step 3) to
reconfigure the public crypto key.
