How to package signatures back to *.pkg file after they are customized

Unanswered Question
Jun 2nd, 2009

Hi folks!

I have an unusual task to reduce the number of signatures to deploy them to IOS router. The point is it is 871 router with only 128MB of RAM much of it is utilized and the router actually runs low on memory. I would like to minimize the number of active signatures from the basic set to only critical ones. So, the idea is deploy a basic set to a reference router, retire those signatures I don't need and then package everything back to a pkg file that will be pushed to about 80 production routers at the remote locations.

Thanks a lot for any ideas or suggestions.

Eugene

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Router memory and resource constraints prevent a router from loading all Cisco IOS IPS signatures. Thus, it is recommended that you load only a selected set of signatures that are defined by the categories. Because the categories are applied in a "top-down" order, you should first retire all signatures, followed by "unretiring" specific categories. Retiring signatures enables the router to load information for all signatures, but the router will not build the parallel scanning data structure.

Retired signatures are not scanned by Cisco IOS IPS, so they will not fire alarms. If a signature is irrelevant to your network or if you want to save router memory, you should retire signatures, as appropriate.

http://www.cisco.com/en/US/docs/ios/sec_data_plane/configuration/guide/sec_ips5_sig_fs_ue.html#wp1064428

Actions

This Discussion