User Guide for Cisco IPS Manager 3.0
Moving from the Unix Director or CSPM to IPS MC

Table Of Contents

Moving from the Unix Director or CSPM to IPS MC

Limitations and Restrictions: Moving from the Unix Director or CSPM to IPS MC


Moving from the Unix Director or CSPM to IPS MC


The following areas are important when migrating from Cisco Secure Policy Manager (CSPM) or Unix Director to Management Center for IPS Sensors (IPS MC):

Using existing sensor configurations

Using existing custom signatures

Migration of existing event data

Migration of existing notification scripts

Installation

Supported sensor versions

Each of these areas is further detailed in the section that follows, see Limitations and Restrictions: Moving from the Unix Director or CSPM to IPS MC.

Limitations and Restrictions: Moving from the Unix Director or CSPM to IPS MC

If you use Cisco Secure Policy Manager (CSPM) or Unix Director to manage Cisco IDS Sensors and other devices, but plan to begin using IPS MC, the following information is important.

Using Existing Sensor Configurations—In IPS MC, you can discover sensor settings, but you must enter configuration data that cannot be discovered.


Note Sensor configuration files cannot be imported into IPS MC from an existing CSPM or Unix Director installation.


Using Existing Custom Signatures—You can use existing custom signatures if you discover them with along other sensor settings, but you must enter configuration data that cannot be discovered.

Migration of Existing Event Data—IPS MC does not support the migration of event data.

Installation—You cannot install IPS MC or Monitoring Center for Security (Security Monitor) by upgrading an existing installation of CSPM or Unix Director; you must install IPS MC or Security Monitor separately, and you must install it on Windows 2000 or 2003.

Supported Sensor Versions—IPS MC and Security Monitor support sensors running IDS 4.0 and later. Sensors running software versions earlier than IDS 4.0 are not supported.