Guest

Cisco IPS 4200 Series Sensors

Release Notes for Cisco Intrusion Prevention System 7.0(2)E4

  • Viewing Options

  • PDF (596.1 KB)
  • Feedback
Release Notes for Cisco Intrusion Prevention System 7.0(2)E4

Table Of Contents

Release Notes for Cisco Intrusion Prevention System 7.0(2)E4

Contents

IPS 7.0(2)E4 File List

Supported Platforms

Supported Servers

ROMMON and TFTP

IPS Management and Event Viewers

New and Changed Information

The Sensor and Jumbo Packet Frame Size

MySDN Decommissioned

Cisco IPS Device Manager

Global Correlation and the Produce Alert Event Action

Component Signatures With Risk Rating Set to 0

Configuring Appliances for UDLD Support

Cisco Security Intelligence Operations

Before Upgrading to Cisco IPS 7.0(2)E4

Perform These Tasks

Backing Up and Restoring the Configuration File Using a Remote Server

Obtaining Software on Cisco.com

IPS Software Versioning

Software Release Examples

Upgrading to Cisco IPS 7.0(2)E4

Upgrade Notes and Caveats

Upgrading to IPS 7.0(2)E4

After Upgrading to Cisco IPS 7.0(2)E4

Comparing Configurations

Importing a New SSL Certificate

Logging In to the IDM

Licensing the Sensor

Understanding the License

Service Programs for IPS Products

Obtaining and Installing the License Key

Installing or Upgrading Cisco IME and Migrating Data In to the IME

Restrictions and Limitations

Recovering the Password

Understanding Password Recovery

Recovering the Appliance Password

Using the GRUB Menu

Using ROMMON

Recovering the IDSM2 Password

Recovering the AIP SSM Password

Recovering the AIM IPS Password

Recovering the NME IPS Password

Disabling Password Recovery

Verifying the State of Password Recovery

Troubleshooting Password Recovery

Resolved Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Intrusion Prevention System 7.0(2)E4


Published: March 29, 2010, OL-21671-01

Revised: October 28, 2013

Contents

IPS 7.0(2)E4 File List

Supported Platforms

Supported Servers

ROMMON and TFTP

IPS Management and Event Viewers

New and Changed Information

The Sensor and Jumbo Packet Frame Size

MySDN Decommissioned

Cisco IPS Device Manager

Global Correlation and the Produce Alert Event Action

Component Signatures With Risk Rating Set to 0

Configuring Appliances for UDLD Support

Cisco Security Intelligence Operations

Before Upgrading to Cisco IPS 7.0(2)E4

Upgrading to Cisco IPS 7.0(2)E4

After Upgrading to Cisco IPS 7.0(2)E4

Installing or Upgrading Cisco IME and Migrating Data In to the IME

Restrictions and Limitations

Recovering the Password

Resolved Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request

IPS 7.0(2)E4 File List

The following files are part of Cisco IPS 7.0(2)E4:

Service Pack Upgrade Files

IPS-K9-7.0-2-E4.pkg

IPS-AIM-K9-7.0-2-E4.pkg

IPS-NME-K9-7.0-2-E4.pkg

CSM Service Package Files

IPS-CS-MGR-AIM-K9-7.0-2-E4.zip

IPS-CS-MGR-NME-K9-7.0-2-E4.zip

IPS-CS-MGR-K9-7.0-2-E4.zip

System Image Files

IPS 4240-K9-sys-1.1-a-7.0-2-E4.img

IPS 4255-K9-sys-1.1-a-7.0-2-E4.img

IPS 4260-K9-sys-1.1-a-7.0-2-E4.img

IPS-4270_20-K9-sys-1.1-a-7.0-2-E4.img

IPS-IDSM2-K9-sys-1.1-a-7.0-2-E4.bin.gz

IPS-SSM_10-K9-sys-1.1-a-7.0-2-E4.img

IPS-SSM_20-K9-sys-1.1-a-7.0-2-E4.img

IPS-SSM_40-K9-sys-1.1-a-7.0-2-E4.img

IPS-AIM-K9-sys-1.1-a-7.0-2-E4.img

IPS-NME-K9-sys-1.1-a-7.0-2-E4.img

Recovery Image Files

IPS-K9-r-1.1-a-7.0-2-E4.pkg

IPS-AIM-K9-r-1.1-a-7.0-2-E4.pkg

IPS-NME-K9-r-1.1-a-7.0-2-E4.pkg

Engine Update Files

IPS-engine-E4-req-7.0-2.pkg

IPS-CS-MGR-engine-E4-req-7.0-2.zip

Engine Update Readme

IPS-engine-E4.readme.txt

For More Information

For the procedure for obtaining these files on Cisco.com, see Obtaining Software on Cisco.com.

For the procedure for installing the major upgrade file, see Upgrading to IPS 7.0(2)E4.

For the procedure for installing system image files, refer to Installing System Images.

For the procedure for installing recovery image files, refer to Recovering the Application Partition.

Supported Platforms


Note All IPS platforms allow ten concurrent CLI sessions.



Note The AIM IPS and the NME IPS do not support the IPv6 features, because the router in which they are installed does not send them IPv6 data. IPv6 inspection may work on the IDSM2, but we do not officially support it. There is no support for IPv6 on the management (command and control) interface.


Cisco IPS 7.0(2)E4 is supported on the following platforms:

IPS 4240 Series Sensor Appliances

IPS 4255 Series Sensor Appliances

IPS 4260 Series Sensor Appliances

IPS 4270-20 Series Sensor Appliances

WS-SVC-IDSM2 Series Intrusion Detection System Modules (IDSM2)

ASA-SSM-AIP-10 Series Cisco ASA Advanced Inspection and Prevention Security Service Modules (AIP SSM-10)

ASA-SSM-AIP-20 Series Cisco ASA Advanced Inspection and Prevention Security Service Modules (AIP SSM-20)

ASA-SSM-AIP-40 Series Cisco ASA Advanced Inspection and Prevention Security Service Modules (AIP SSM-40)

Intrusion Prevention System Advanced Integration Modules (AIM IPS)

Intrusion Prevention System Network Modules (NME IPS)

For More Information

For detailed information on each IPS appliance, refer to Installing Cisco Intrusion Prevention System Appliances and Modules 7.0.

Supported Servers

The following FTP servers are supported for IPS software updates:

WU-FTPD 2.6.2 (Linux)

Solaris 2.8

Sambar 6.0 (Windows 2000)

Serv-U 5.0 (Windows 2000)

MS IIS 5.0 (Windows 2000)

The following HTTP/HTTPS servers are supported for IPS software updates:

CMS - Apache Server (Tomcat)

CMS - Apache Server (JRun)

ROMMON and TFTP

ROMMON uses TFTP to download an image and launch it. TFTP does not address network issues such as latency or error recovery. It does implement a limited packet integrity check so that packets arriving in sequence with the correct integrity value have an extremely low probability of error. But TFTP does not offer pipelining so the total transfer time is equal to the number of packets to be transferred times the network average RTT. Because of this limitation, we recommend that the TFTP server be located on the same LAN segment as the sensor. Any network with an RTT less than a 100 milliseconds should provide reliable delivery of the image. Be aware that some TFTP servers limit the maximum file size that can be transferred to ~32 MB.

For More Information

For the procedure for downloading IPS software updates from Cisco.com, see Obtaining Software on Cisco.com.

For the procedure for configuring automatic updates, for the CLI refer to Configuring Automatic Updates, for the IDM refer to Configuring Automatic Update, and for the IME refer to Configuring Automatic Update.

IPS Management and Event Viewers

Use the following tools for configuring Cisco IPS 7.0(2)E4 sensors:

Cisco IDM 7.0.3

IDM 7.0.3 is included within the IPS 7.0(2)E4 files.

Cisco IME 7.0.2

IME now supports 10 devices.

IPS CLI 7.0.2

ASDM 5.2 and later

CSM 3.3 and later


Note We recommend that ASDM users upgrade to ASDM 6.3 or later. The Java VM upper memory limit of ASDM 6.3 has been increased. Older versions of ASDM may not have enough available memory for the IDM and 7.0(3) to function properly.


Use the following tools for monitoring Cisco IPS 7.0(2)E4 sensors:

Cisco IME 7.0.2

The IME now supports 10 devices.


Note The current versions of the IME work with the E4 engine upgrade, but do not correctly display the new values allowed in the Retired signature field. An updated version of the IME is in progress and will be released shortly after the E4 engine update. The current versions of the IME also do not have the expanded memory capability for the Java VM and may cause problems when you tune signatures.


CSM 4.0 and later


Note You may need to configure viewers that are already configured to monitor the Cisco IPS 6.2 sensors to accept a new SSL certificate for the Cisco IPS 7.0(2)E4 sensors.


New and Changed Information

Cisco IPS 7.0(2)E4 includes the new E4 signature engine.

The E4 signature engine update includes signature update 480, which is not available for separate download. The E4 signature engine update contains the following new features:

Port-agnostic HTTP inspection

The IPS now allows inspection of HTTP on any port. The Service HTTP engine now contains a parameter (ALLPORTS) that aids you in configuring inspection of HTTP on any port.

Meta engine enhancements

The purpose of the Meta engine is to detect a specified payload from an attacker and a corresponding payload from the victim. It is also used to inspect streams at different offsets. The Meta engine supports the AND and OR logical operators. ANDNOT capability has been added to the Meta engine. This clause is a negative clause used to complement the existing positive clause-based signatures. The previous signature format had the following form:

IF (A and B and C) then Alarm; alternatively, IF (A or B or C) then Alarm is also 
supported; where A, B, and C are meta component signatures.
 
   

The addition of the negative clause allows for the following logic:

IF (A and/or B) AND NOT (C and/or D) then Alarm.
 
   

The (C and/or D) is the negative clause and is satisfied if (C and D) [alternatively (C or D)] do not occur before the Meta Reset Interval time expires.

A component of the positive clause must occur before the negative clause(s) to establish the Meta tracking state. The Meta engine cannot track the lack of past behavior.The state of the negative clause is evaluated when the Meta Reset Interval time expires.

Signature load thresholding

The retired attribute of a signature has been changed to support the variable loading of signatures based on platform. A signature can be retired or active with additional values that include low memory retired (low-mem-retired) and medium memory retired (medium-mem-retired). Low memory retired platforms have less that 1 GB of maximum sensor memory, and include the following sensors: IPS 4215, AIM IPS, NME IPS, AIP SSM-10, AIP SSM-20, and AIP SSM-40. Medium memory retired platforms have at least 1 GB and less than 4 GB of maximum sensor memory, and include the following sensors: IDSM2, IPS 4240, IPS 4255, IPS 4260, and IPS 4270-20. Platforms with 4GB and higher maximum sensor memory are considered high memory platforms. As the signatures are loaded, the value of retired is evaluated based on the platform loading the signatures.

The Retired parameter has the following new options:

True—Retired on all platforms.

Medium Memory Retired—Signature is retired on all medium and low memory platforms.

Low Memory Retired—Signature is retired on low memory platforms.

False—Signature is not retired on any platform.

Three new String engines that provide support for future IPS hardware and software releases—String ICMP XL, String TCP XL, and String UDP XL.

These signature engines provide optimized operation for new hardware and are not operational in the E4 update. If you try to use them, you will receive an error message.

Signature definition support for three new IOS IPS engines—Service FTP V2, Service HTTP V2, and Service SMTP V1.

These signature engines provide a protocol decode engine tuned for IOS IPS. If you try to use these engines, you receive an error message.

The Service DNS engine has been enhanced to provide domain name matching.

A new parameter, FQDN (Fully Qualified Domain Name) has been added in the Specify Block parameter to enable this capability. FQDN matching uses a case insensitive substring matching algorithm instead of regular expressions. Because it matches on substrings, you must take care in constructing the FQDN parameter.

For example, an FQDN parameter of "cisco.com" will match any domain name lookup for computers in the "cisco.com" domain, but it will also match the "sanfrancisco.com" domain as well. Including the "." as in ".cisco.com" will eliminate the obvious false positive, but remember that the shorter the FQDN string, the higher the likelihood of a false positive. You can write a simple signature as a custom signature in the Service DNS engine by setting the protocol to UDP, setting FQDN to yes, and then setting the FQDN string to cisco.com.


Caution The FQDN match is performed on DNS queries for "A records" (DNS Type 1 query) only. DNS responses are not matched, nor are other types of queries, such as MX records.

The P2P inspection engine has been enhanced to detect the Share P2P software popular in Japan.

For More Information

For detailed information on the Service HTTP engine, refer to Service HTTP Engine.

For detailed information on the Meta engine, refer to Meta Engine.

The Sensor and Jumbo Packet Frame Size

For IPS standalone appliances with 1 G and 10 G fixed or add-on interfaces, the maximum jumbo frame size is 9216 bytes.


Note A jumbo frame is an Ethernet packet that is larger than the standard maximum of 1518 bytes (including Layer 2 header and FCS).


MySDN Decommissioned

Because MySDN has been decommissioned, the URL in older versions of the IDM and the IME is no longer functional. If you are using IPS 6.0 or later, we recommend that you upgrade your version of the IDM and the IME.

You can upgrade to the following versions to get the functioning MySDN URL:

IDM 7.0.3

IME 7.0.3

IPS 7.0(4)E4, which contains IDM 7.0.4

If you are using version IPS 5.x, you must look up signature information manually at this URL:

http://tools.cisco.com/security/center/search.x

For More Information

For detailed information on MySDN, for the IDM refer to MySDN and for the IME refer to MySDN.

Cisco IPS Device Manager

A new version of the IDM is bundled with the E4 engine update, IDM 7.0.3. We have modified the IDM to correctly display and edit the additional values allowed in the Retired parameter field of a signature. We have also modified the IDM and its associated ASDM Launcher application to increase the upper memory limit that Java VM uses. With this change you can display and tune more signatures in the IDM.


Note We recommend that ASDM users upgrade to ASDM 6.3 or later. The Java VM upper memory limit of ASDM 6.3 has been increased. Older versions of ASDM may not have enough available memory for IDM7.0.3 to function properly.



Note After upgrading to the E4 signature engine, disconnect and restart any open IDM sessions to make sure that your system downloads and uses the latest IDM application from the sensor.


For More Information

For more information about the new values allowed in the Retired parameter for a signature, see New and Changed Information.

Global Correlation and the Produce Alert Event Action

A Produce Alert event action is added for an event under the following conditions:

Global correlation has increased the risk rating of an event.

Global correlation has added either the Deny Packet Inline or Deny Attacker Inline event action.

Adding the Produce Alert event action ensures that all events being denied by global correlation result in alerts that you can view through your monitoring tool. This prevents global correlation from denying events that you do not know about.


Note This feature only applies to global correlation inspection where the traffic is allowed if no specific signature is matched. It does not apply to reputation filtering where the packet is denied before signature analysis, and no alerts are generated when packets are denied by reputation filtering.


For More Information

For more information on global correlation, for the CLI, refer to Configuring Global Correlation, for the IDM refer to Configuring Global Correlation, and for the IME refer to Configuring Global Correlation.

For more information on event actions, refer to Event Actions.

Component Signatures With Risk Rating Set to 0

Component signatures are not independent signatures, they are pieces of a Meta signature. The Signature Type option is marked as Component. Since these signatures are not independent signatures, the risk rating when triggered is automatically set to 0. The risk rating is applicable to the Meta signature rather than the component signatures. This prevents the component signatures from causing denial of packets by either event action overrides or global correlation. Event action overrides and global correlation are applied against the Meta signature rather than the component signature.


Note Some component signatures in the Meta signatures are valuable as both independent signatures and component signatures. These signatures are not marked as Signature Type Component and instead are marked with the Signature Type set to either Vulnerability, Exploit, Anomaly, or Other. The risk rating for these signatures is calculated and is not set to 0.


For More Information

For more information on the Meta signature engine, refer to Meta Engine.

For more information on configuring Meta signatures, refer to Example Meta Engine Signature.

For more information on risk rating, refer to Calculating the Risk Rating.

Configuring Appliances for UDLD Support

UniDirectional Link Detection (UDLD) is a protocol that Cisco switches use to prevent spanning-tree forwarding loops and to prevent single direction links in switched networks. IPS appliances configured in inline VLAN pair mode are now able to respond to UDLD packets received from the switch. You can enable UDLD protocol on the switch so that the switch can detect when the appliance has entered an error state in which packets are being sent to the appliance, but the appliance is no longer sending packets back to the switch. Before UDLD support was available, spanning tree and EtherChannel configurations were unable to detect certain appliance failures, which resulted in either spanning-tree loops or the switch not using alternate routes for the packets.


Note No special configuration is necessary on the appliance. Configure the appliance for inline VLAN pairs and make sure its interfaces are enabled.


To configure a Catalyst 6500 series switch to use UDLD with an appliance configured in inline VLAN pair mode, follow these steps:


Step 1 Log in to the console.

Step 2 Globally enable UDLD in aggressive mode and prevent the switch from automatically restoring an interface that has been disabled by UDLD.

switch(config)# udld aggressive
switch(config)# no errdisable recovery cause udld
switch(config)# errdisable detect cause udld
switch(config)# udld message time 7
 
   

Step 3 Configure the switch interface connected to the sensor interface for UDLD aggressive mode.

switch(config)# interface gigabitethernet slot/port
switch(config-if)# udld port aggressive
 
   

Repeat Step 3 for each switch interface connected to the sensor interface.

Step 4 If UDLD disables a switch port, you must correct the sensor error and recover the switch interface manually. To recover the switch interface, shut down the interface, and then reenable it.

switch(config)# interface gigabit ethernet slot/port
switch(config-if)# shutdown
switch(config-if)# no shutdown

For More Information

For more information on UDLD, refer to the Cisco IOS documentation.

For the procedure for configuring inline VLAN pairs on appliances, for the CLI refer to Configuring Inline VLAN Pair Mode, for the IDM refer to Configuring Inline VLAN Pairs, and for the IME refer to Configuring Inline VLAN Pairs.

Cisco Security Intelligence Operations

The Cisco Security Intelligence Operations site on Cisco.com provides intelligence reports about current vulnerabilities and security threats. It also has reports on other security topics that help you protect your network and deploy your security systems to reduce organizational risk.

You should be aware of the most recent security threats so that you can most effectively secure and manage your network. Cisco Security Intelligence Operations contains the top ten intelligence reports listed by date, severity, urgency, and whether there is a new signature available to deal with the threat.

Cisco Security Intelligence Operations contains a Security News section that lists security articles of interest. There are related security tools and links.

You can access Cisco Security Intelligence Operations at this URL:

http://tools.cisco.com/security/center/home.x

Cisco Security Intelligence Operations is also a repository of information for individual signatures, including signature ID, type, structure, and description.

You can search for security alerts and signatures at this URL:

http://tools.cisco.com/security/center/search.x

Before Upgrading to Cisco IPS 7.0(2)E4

This section describes the actions you should take before upgrading to Cisco IPS 7.0(2)E4. It contains the following topics:

Perform These Tasks

Backing Up and Restoring the Configuration File Using a Remote Server

Obtaining Software on Cisco.com

IPS Software Versioning

Software Release Examples

Perform These Tasks

Before you upgrade your sensors to IPS 7.0(2)E4, make sure you perform the following tasks:

Made sure you have a valid Cisco Service for IPS service contract per sensor so that you can apply software upgrades.

Created a backup copy of your configuration.

Saved the output of the show version command.

If you need to downgrade a signature update, you will know what version you had, and you can then apply the configuration you saved when you backed up your configuration.

For More Information

For more information on how to obtain a valid Cisco Service for IPS service contract, see Service Programs for IPS Products.

For the procedure for creating a backup copy of your configuration, see Backing Up and Restoring the Configuration File Using a Remote Server.

For the procedure for finding your Cisco IPS software version, for the CLI refer to Displaying Version Information, for the IDM refer to IDM Home Window, and for the IME refer to Sensor Information Gadget.

For the procedure for downgrading signature updates on your sensor, refer to Upgrading, Downgrading, and Installing System Images.

Backing Up and Restoring the Configuration File Using a Remote Server


Note We recommend copying the current configuration file to a remote server before upgrading.


Use the copy [/erase] source_url destination_url keyword command to copy the configuration file to a remote server. You can then restore the current configuration from the remote server. You are prompted to back up the current configuration first.

The following options apply:

/erase—Erases the destination file before copying.

This keyword only applies to the current-config; the backup-config is always overwritten. If this keyword is specified for destination current-config, the source configuration is applied to the system default configuration. If it is not specified for the destination current-config, the source configuration is merged with the current-config.

source_url—The location of the source file to be copied. It can be a URL or keyword.

destination_url—The location of the destination file to be copied. It can be a URL or a keyword.

current-config—The current running configuration. The configuration becomes persistent as the commands are entered.

backup-config—The storage location for the configuration backup.

The exact format of the source and destination URLs varies according to the file. Here are the valid types:

ftp:—Source URL for an FTP network server. The syntax for this prefix is:

ftp://[[username@]location][/relativeDirectory]/filename

ftp://[[username@]location][//absoluteDirectory]/filename


Note You are prompted for a password.


scp:—Source URL for the SCP network server. The syntax for this prefix is:

scp://[[username@]location][/relativeDirectory]/filename

scp://[[username@]location][//absoluteDirectory]/filename


Note You are prompted for a password. You must add the remote host to the SSH known hosts list.


http:—Source URL for the web server. The syntax for this prefix is:

http://[[username@]location][/directory]/filename


Note The directory specification should be an absolute path to the desired file.


https:—Source URL for the web server. The syntax for this prefix is:

https://[[username@]location][/directory]/filename


Note The directory specification should be an absolute path to the desired file. The remote host must be a TLS trusted host.



Caution Copying a configuration file from another sensor may result in errors if the sensing interfaces and virtual sensors are not configured the same.

Backing Up the Current Configuration to a Remote Server

To back up your current configuration to a remote server, follow these steps:


Step 1 Log in to the CLI using an account with administrator privileges.

Step 2 Back up the current configuration to the remote server.
sensor# copy current-config scp://user@192.0.2.0//configuration/cfg current-config
Password: ********
Warning: Copying over the current configuration may leave the box in an unstable state.
Would you like to copy current-config to backup-config before proceeding? [yes]:
 
   
Step 3 Enter yes to copy the current configuration to a backup configuration.
cfg            100% |************************************************| 36124       00:00 
 
   

Restoring the Current Configuration From a Backup File

To restore your current configuration from a backup file, follow these steps:


Step 1 Log in to the CLI using an account with administrator privileges.

Step 2 Back up the current configuration to the remote server.
sensor# copy scp://user@192.0.2.0//configuration/cfg current-config
Password: ********
Warning: Copying over the current configuration may leave the box in an unstable state.
Would you like to copy current-config to backup-config before proceeding? [yes]:
 
   
Step 3 Enter yes to copy the current configuration to a backup configuration.
cfg            100% |************************************************| 36124       00:00 
 
   
Warning: Replacing existing network-settings may leave the box in an unstable state.
Would you like to replace existing network settings 
(host-ipaddress/netmask/gateway/access-list) on sensor before proceeding? [no]: 
sensor#
 
   

Step 4 Enter no to retain the currently configured hostname, IP address, subnet mask, management interface, and access list. We recommend you retain this information to preserve access to your sensor after the rest of the configuration has been restored.


For More Information

For the procedure for adding trusted hosts, for the CLI refer to Adding TLS Trusted Hosts, for the IDM refer to Configuring Trusted Hosts, and for the IME refer to Adding Trusted Hosts.

Obtaining Software on Cisco.com

You can find major and minor updates, service packs, signature and signature engine updates, system and recovery files, firmware upgrades, and Readmes on the Download Software site on Cisco.com. Signature updates are posted to Cisco.com approximately every week, more often if needed. Service packs are posted to Cisco.com as needed. Major and minor updates are also posted periodically. Check Cisco.com regularly for the latest IPS software.

You must have an account with cryptographic access before you can download software. You set this account up the first time you download IPS software from the Download Software site. You can sign up for IPS Alert Bulletins to receive information on the latest software releases.


Note You must be logged in to Cisco.com to download software. You must have an active IPS maintenance contract and a Cisco.com password to download software. You must have a sensor license to apply signature updates.



Caution The BIOS on Cisco IPS sensors is specific to Cisco IPS sensors and must only be upgraded under instructions from Cisco with BIOS files obtained from the Cisco website. Installing a non-Cisco or third-party BIOS on Cisco IPS sensors voids the warranty.

Downloading IPS Software

To download software on Cisco.com, follow these steps:


Step 1 Log in to Cisco.com.

Step 2 From the Support drop-down menu, choose Download Software.

Step 3 Under Select a Software Product Category, choose Security Software.

Step 4 Choose Intrusion Prevention System (IPS).

Step 5 Enter your username and password.

Step 6 In the Download Software window, choose IPS Appliances > Cisco Intrusion Prevention System and then click the version you want to download.


Note You must have an IPS subscription service license to download software.


Step 7 Click the type of software file you need. The available files appear in a list in the right side of the window. You can sort by file name, file size, memory, and release date. And you can access the Release Notes and other product documentation.

Step 8 Click the file you want to download. The file details appear.

Step 9 Verify that it is the correct file, and click Download.

Step 10 Click Agree to accept the software download rules. The first time you download a file from Cisco.com, you must fill in the Encryption Software Export Distribution Authorization form before you can download the software.

Fill out the form and click Submit. The Cisco Systems Inc. Encryption Software Usage Handling and Distribution Policy appears.

Read the policy and click I Accept. The Encryption Software Export/Distribution Form appears.

If you previously filled out the Encryption Software Export Distribution Authorization form, and read and accepted the Cisco Systems Inc. Encryption Software Usage Handling and Distribution Policy, these forms are not displayed again. The File Download dialog box appears.

Step 11 Open the file or save it to your computer.

Step 12 Follow the instructions in the Readme to install the update.


For More Information

For more information about IPS maintenance contracts, see Service Programs for IPS Products.

For the procedure for obtaining and installing a sensor license, see Obtaining and Installing the License Key.

IPS Software Versioning

When you download IPS software images from Cisco.com, you should understand the versioning scheme so that you know which files are base files, which are cumulative, and which are incremental.

Major Update

A major update contains new functionality or an architectural change in the product. For example, the Cisco IPS 7.0 base version includes everything (except deprecated features) since the previous major release (the minor update features, service pack fixes, and signature updates) plus any new changes. Major update 7.0(1) requires 5.1(6) and later. With each major update there are corresponding system and recovery packages.


Note The 7.0(1) major update is used to upgrade 5.1(6) and later sensors to 7.0(1) If you are reinstalling 7.0(1) on a sensor that already has 7.0(1) installed, use the system image or recovery procedures rather than the major update.


Minor Update

A minor update is incremental to the major version. Minor updates are also base versions for service packs. The first minor update for 7.0 is 7.1(1). Minor updates are released for minor enhancements to the product. Minor updates contain all previous minor features (except deprecated features), service pack fixes, signature updates since the last major version, and the new minor features being released. You can install the minor updates on the previous major or minor version (and often even on earlier versions). The minimum supported version needed to upgrade to the newest minor version is listed in the Readme that accompanies the minor update. With each minor update there are corresponding system and recovery packages.

Service Pack

A service pack is cumulative following a base version release (minor or major). Service packs are used for the release of defect fixes with no new enhancements. Service packs contain all service pack fixes since the last base version (minor or major) and the new defect fixes being released. Service packs require the minor version. The minimum supported version needed to upgrade to the newest service pack is listed in the Readme that accompanies the service pack. Service packs also include the latest engine update. For example, if service pack 7.0(3) is released, and E4 is the latest engine level, the service pack is released as 7.0(3)E4.

Patch Release

A patch release is used to address defects that are identified in the upgrade binaries after a software release. Rather than waiting until the next major or minor update, or service pack to address these defects, a patch can be posted. Patches include all prior patch releases within the associated service pack level. The patches roll into the next official major or minor update, or service pack.

Before you can install a patch release, the most recent major or minor update, or service pack must be installed. For example, patch release 7.0(1p1) requires 7.0(1).


Note Upgrading to a newer patch does not require you to uninstall the old patch. For example, you can upgrade from patch 7.0(1p1) to 7.0(1p2) without first uninstalling 7.0(1p1).


Figure 1 illustrates what each part of the IPS software file represents for major and minor updates, service packs, and patch releases.

Figure 1 IPS Software File Name for Major and Minor Updates, Service Packs, and Patch Releases

Signature Update

A signature update is a package file containing a set of rules designed to recognize malicious network activities. Signature updates are released independently from other software updates. Each time a major or minor update is released, you can install signature updates on the new version and the next oldest version for a period of at least six months. Signature updates are dependent on a required signature engine version. Because of this, a req designator lists the signature engine required to support a particular signature update.

Figure 2 illustrates what each part of the IPS software file represents for signature updates.

Figure 2 IPS Software File Name for Signature Updates

Signature Engine Update

A signature engine update is an executable file containing binary code to support new signature updates. Signature engine files require a specific service pack, which is also identified by the req designator.

Figure 3 illustrates what each part of the IPS software file represents for signature engine updates.

Figure 3 IPS Software File Name for Signature Engine Updates

Recovery and System Image Files

Recovery and system image files contain separate versions for the installer and the underlying application. The installer version contains a major and minor version field. The major version is incremented by one of any major changes to the image installer, for example, switching from .tar to rpm or changing kernels. The minor version can be incremented by any one of the following:

Minor change to the installer, for example, a user prompt added.

Repackages require the installer minor version to be incremented by one if the image file must be repackaged to address a defect or problem with the installer.

Figure 4 illustrates what each part of the IPS software file represents for recovery and system image files.

Figure 4 IPS Software File Name for Recovery and System Image Files

Software Release Examples

Table 1 lists platform-independent Cisco IPS 7.x software release examples.

Table 1 Platform-Independent Release Examples 

Release
Target Frequency
Identifier
Example Version
Example Filename

Signature update1

Weekly

sig

S369

IPS-sig-S369-req-E4.pkg

Signature engine update2

As needed

engine

E4

IPS-engine-E4-req-7.0-1.pkg

Service packs3

Semi-annually
or as needed

7.0(3)

IPS-K9-7.0-3-E4.pkg

Minor version update4

Annually

7.1(1)

IPS-K9-7.1-1-E4.pkg

Note IPS-AIM-K9-7.1-1-E4.pkg is the minor version update for AIM IPS. IPS-NME-K-9-7.1-1-E4.pkg is the minor version update for NME IPS.

Major version update5

Annually

7.0(1)

IPS-K9-7.0-1-E4.pkg

Patch release6

As needed

patch

7.0(1p1)

IPS-K9-patch-7.0-1pl-E4.pkg

Recovery package7

Annually or as needed

r

1.1-7.0(1)

IPS-K9-r-1.1-a-7.0-1-E4.pkg

1 Signature updates include the latest cumulative IPS signatures.

2 Signature engine updates add new engines or engine parameters that are used by new signatures in later signature updates.

3 Service packs include defect fixes.

4 Minor versions include new minor version features and/or minor version functionality.

5 Major versions include new major version functionality or new architecture.

6 Patch releases are for interim fixes.

7 The r 1.1 can be revised to r 1.2 if it is necessary to release a new recovery package that contains the same underlying application image. If there are defect fixes for the installer, for example, the underlying application version may still be 7.1(1), but the recovery partition image will be r 1.2.


Table 2 describes platform-dependent software release examples.

Table 2 Platform-Dependent Release Examples 

Release
Target Frequency
Identifier
Supported Platform
Example Filename

System image1

Annually

sys

Separate file for each sensor platform

IPS-4240-K9-sys-1.1-a-7.0-1-E4.img

Maintenance partition image2

Annually

mp

IDSM2

c6svc-mp.2-1-2.bin.gz

Bootloader

As needed

bl

AIM IPS
NME IPS

pse_aim_x.y.z.bin
pse_nm_x.y.z.bin
(where x, y, z is the release number)

Mini-kernel

As needed

mini-kernel

AIM IPS
NME IPS

pse_mini_kernel_1.1.10.64.bz2

1 The system image includes the combined recovery and application image used to reimage an entire sensor.

2 The maintenance partition image includes the full image for the IDSM2 maintenance partition. The file is installed from but does not affect the IDSM2 application partition.


Table 3 describes the platform identifiers used in platform-specific names.

Table 3 Platform Identifiers

Sensor Family
Identifier

IPS 4240 series

4240

IPS 4255 series

4255

IPS 4260 series

4260

IPS 4270-20 series

4270_20

IDS module for Catalyst 6K

IDSM2

IPS network module

AIM
NME

adaptive security appliance modules

SSM_10
SSM_20
SSM_40


Upgrading to Cisco IPS 7.0(2)E4

This section provides information on upgrading to Cisco IPS 7.0(2)E4, and contains the following topics:

Upgrade Notes and Caveats

Upgrading to IPS 7.0(2)E4

Upgrade Notes and Caveats

The following upgrade notes and caveats apply to upgrading your sensor to IPS 7.0(2)E4:

You must have a valid Cisco Service for IPS Maintenance contract per sensor to receive and use software upgrades from Cisco.com.

The minimum required version for upgrading to 7.0(2)E4 is 5.1(8)E2 or later.

Use IPS-AIM-K9-7.0-2-E4.pkg to upgrade the AIM IPS and IPS-NME-K9-7.0-2-E4 to upgrade the NME IPS. For all other supported sensors, use the IPS-K9-7.0-2-E4.pkg upgrade file.

You cannot upgrade 7.0(2)E3 to 7.0(2)E4 using the IPS-K9-7.0-2-E4.pkg upgrade file. You must use the engine update file, IPS-engine-E4-req-7.0-2.pkg.

The sensor goes in to the configured bypass mode during the update as the inspection software is stopped, replaced, and restarted. The sensor automatically exits bypass mode and resumes traffic inspection upon completion of the new inspection software startup and configuration. The engine update procedure normally installs the update without rebooting the sensor. However, if an error is detected during the update, the installation process attempts to reboot the sensor in order to leave the sensor in an operational state.

After you upgrade any IPS software on your sensor, you must restart the IDM to see the latest software features.

Using automatic update:

If you are using automatic update with a mixture of AIM IPS, NME IPS, and other IPS appliances or modules, make sure you put both the 7.0(2)E4 upgrade file (IPS-K9-7.0-2-E4.pkg), the AIM IPS upgrade file (IPS-AIM-K9-7.0-2-E4.pkg), and the NME IPS upgrade file (IPS-NME-K9-7.0-2-E4) on the automatic update server so that the AIM IPS and the NME IPS can correctly detect which file needs to be downloaded and installed. If you only put the 7.0(2)E4 upgrade file (IPS-K9-7.0-2-E4.pkg) on the server, the AIM IPS and the NME IPS will download and try to install the wrong file.

When you upgrade the AIM IPS or the NME IPS using automatic update, you must disable heartbeat reset on the router before placing the upgrade file on your automatic update server. After the AIM IPS and the NME IPS have been automatically updated, you can reenable heartbeat reset. If you do not disable heartbeat reset, the upgrade can fail and leave the AIM IPS and the NME IPS in an unknown state, which can require a system reimage to recover.

If you are using automatic update from an FTP or SCP server with a mixture of platforms that are supported by IPS 7.0(2)E4 as well as platforms that are not supported by IPS 7.0(2)E4, we recommend that you create a separate automatic update directory 7.0(2)E4 files. Modify the automatic update configuration for sensors supporting IPS 7.0(2)E4 to point to the new directory. Placing the 7.0(2)E4 files in the automatic update directory for those sensors not supporting IPS 7.0(2)E4 results in those sensors constantly downloading the update and generating errors during the attempted update.

Using manual update:

If you want to manually update your sensor, copy the 7.0(2)E4 update files to the directory on the server that your sensor polls for updates.

When you upgrade the AIM IPS or the NME IPS using manual upgrade, you must disable heartbeat reset on the router before installing the upgrade. You can reenable heartbeat reset after you complete the upgrade. If you do not disable heartbeat reset, the upgrade can fail and leave the AIM IPS or the NME IPS in an unknown state, which can require a system reimage to recover.

Global correlation health status defaults to red and changes to green after a successful global correlation update. Successful global correlation updates require a DNS server or an HTTP proxy server. Because DNS and HTTP proxy server configuration features are new to IPS 7.0, they are unconfigured after an upgrade from 5.x or 6.x to 7.0(2)E4. As a result, global correlation health and overall sensor health status are red until you configure a DNS or HTTP proxy server on the sensor. If the sensor is deployed in an environment where a DNS or HTTP proxy server is not available, you can address the red global correlation health and overall sensor health status by disabling global correlation and configuring sensor health status not to include global correlation health status.

If you install an update on your sensor and the sensor is unusable after it reboots, you must reimage your sensor. You can reimage your sensor in the following ways:

For all sensors, use the recover command.

For the IPS 4240, IPS 4255, IPS 4260, and IPS 4270-20, use the ROMMON to restore the system image.

For the AIM IPS and NME IPS, use the bootloader.

For the IDSM2, reimage the application partition from the maintenance partition.

For the AIP SSM, reimage from the adaptive security appliance using the hw-module module 1 recover configure/boot command.


Caution When you install the system image for your sensor, all accounts are removed and the default account and password are reset to cisco.

For More Information

For more information on Cisco Service for IPS Maintenance contracts, see Service Programs for IPS Products.

For the procedure for configuring automatic update, refer to Configuring Automatic Upgrades.

For the procedure for manually updating your sensor, refer to Upgrading the Sensor.

For the procedures for reimaging sensors, refer to Installing System Images.

For the procedure for disabling heartbeat reset, for the AIM IPS refer to Enabling and Disabling Heartbeat Reset, and for the NME IPS refer to Enabling and Disabling Heartbeat Reset.

For the procedure for disabling global correlation, for the CLI refer to Disabling Global Correlation, for the IDM refer to Disabling Global Correlation, and for the IME refer to Disabling Global Correlation.

For the procedure for configuring sensor health to exclude global correlation health, for the CLI refer to Configuring Health Status Information, for the IDM refer to Configuring Sensor Health, and for the IME refer to Configuring Sensor Health.

Upgrading to IPS 7.0(2)E4


Caution You must log in to Cisco.com using an account with cryptographic privileges to download software. The first time you download software on Cisco.com, you receive instructions for setting up an account with cryptographic privileges.


Caution Do not change the filename. You must preserve the original filename for the sensor to accept the update.

To upgrade the sensor, follow these steps:


Step 1 Download the appropriate file to an FTP, SCP, HTTP, or HTTPS server that is accessible from your sensor.


Note Use IPS-AIM-K9-7.0-2-E4.pkg to upgrade the AIM IPS and IPS-NME-K9-7.0-2-E4 to upgrade the NME IPS. For all other supported sensors, use the IPS-K9-7.0-2-E4.pkg upgrade file.



Caution You must upgrade IPS 7.0(2)E3 to IPS 7.0(2)E4 using the engine upgrade file (IPS-engine-E4-req-7.0-2.pkg) because you are upgrading the engine only. You cannot use the IPS-K9-7.0-2-E4.pkg upgrade file to upgrade from 7.0(2)E3 to 7.0(2)E4. Engine updates may or may not cause the sensor to reboot.

Step 2 Log in to the CLI using an account with administrator privileges.

Step 3 Enter configuration mode.

sensor# configure terminal
 
   

Step 4 Upgrade the sensor.

sensor(config)# upgrade url/IPS-K9-7.0-2-E4.pkg
 
   

The URL points to where the update file is located, for example, to retrieve the update using FTP, enter the following:

sensor(config)# upgrade ftp://username@ip_address//directory/IPS-K9-7.0-2-E4.pkg
 
   

Step 5 Enter the password when prompted.

Enter password: ********
 
   

Step 6 Enter yes to complete the upgrade.


Note Major updates, minor updates, and service packs may force a restart of the IPS processes or even force a reboot of the sensor to complete installation.



Note The operating system is reimaged and all files that have been placed on the sensor through the service account are removed.


Step 7 Verify your new sensor version:

sensor# show version
Application Partition:
 
   
Cisco Intrusion Prevention System, Version 7.0(2)E4
 
   
Host:                                                         
    Realm Keys          key1.0                                
Signature Definition:                                         
    Signature Update    S480.0                   2010-03-24   
OS Version:             2.4.30-IDS-smp-bigphys                
Platform:               IPS 4240-K9                           
Serial Number:          ABC1234DEFG 
Licensed, expires:      19-Feb-2011 UTC                       
Sensor up-time is 55 min.
Using 1420378112 out of 1984548864 bytes of available memory (71% usage)
system is using 17.4M out of 38.5M bytes of available disk space (45% usage)
application-data is using 44.8M out of 166.8M bytes of available disk space (28% usage)
boot is using 41.6M out of 68.6M bytes of available disk space (64% usage)
application-log is using 123.5M out of 513.0M bytes of available disk space (24% usage)
 
   
 
   
MainApp            B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   
2009-10-15T08:09:06-0500   Running   
AnalysisEngine     BE-BEAU_E4_2010_MAR_25_02_09_7_0_2   (Ipsbuild)   
2010-03-25T02:11:05-0500   Running   
CollaborationApp   B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   
2009-10-15T08:09:06-0500   Running   
CLI                B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   
2009-10-15T08:09:06-0500             
 
   
Upgrade History:
 
   
  IPS-K9-7.0-2-E4   04:00:07 UTC Thu Mar 25 2010   
        
Recovery Partition Version 1.1 - 7.0(2)E4
 
   

For More Information

For the procedure for locating software on Cisco.com and obtaining an account with cryptographic privileges, see Obtaining Software on Cisco.com.

After Upgrading to Cisco IPS 7.0(2)E4

This section provides information about what to do after you install IPS 7.0(2)E4. It contains the following topics:

Comparing Configurations

Importing a New SSL Certificate

Logging In to the IDM

Licensing the Sensor

Comparing Configurations

Compare your backed up and saved IPS configuration with the output of the show configuration command after upgrading to 7.0(2)E4 to verify that all the configuration has been properly converted.


Caution If the configuration is not properly converted, use the Bug Navigator tool to check the list of caveats associated with your release, or check Cisco.com for any upgrade issues that have been found. Contact the TAC if no DDTS refers to your situation.

For More Information

For the URL for the Bug Navigator tool and a list of the resolved caveats associated with this release, see Resolved Caveats.

Importing a New SSL Certificate

If necessary import the new SSL certificate for the upgraded sensor in to each tool being used to monitor the sensor.

For More Information

For the procedures for configuring TLS/SSL, for the CLI refer to Configuring TLS, for the IDM refer to Configuring Trusted Hosts, and for the IME refer to Configuring Trusted Hosts.

Logging In to the IDM

The IDM is a web-based, Java Web Start application that enables you to configure and manage your sensor. The web server for IDM resides on the sensor. You can access it through Internet Explorer or Firefox web browsers.

To log in to the IDM, follow these steps:


Step 1 Open a web browser and enter the sensor IP address. A Security Alert dialog box appears.

https://sensor_ip_address
 
   

Note The IDM is already installed on the sensor.



Note The default IP address is 192.168.1.2/24,192.168.1.1, which you change to reflect your network environment when you initialize the sensor. When you change the web server port, you must specify the port in the URL address of your browser when you connect to the IDM in the format https://sensor_ip_address:port (for example, https://10.1.9.201:1040).


Step 2 Click Yes to accept the security certificate. The Cisco IPS Device Manager Version 7.0 window appears.

Step 3 To launch the IDM, click Run IDM. The JAVA loading message box appears, and then the Warning - Security dialog box appears.

Step 4 To verify the security certificate, check the Always trust content from this publisher check box, and click Yes. The JAVA Web Start progress dialog box appears, and then the IDM on ip_address dialog box appears.

Step 5 To create a shortcut for the IDM, click Yes. The Cisco IDM Launcher dialog box appears.


Note You must have JRE 1.5 (JAVA 5) installed to create shortcuts for the IDM. If you have JRE 1.6 (JAVA 6) installed, the shortcut is created automatically.


Step 6 To authenticate the IDM, enter your username and password, and click OK. The IDM begins to load. If you change panes from Home to Configuration or Monitoring before the IDM has complete initialization, a Status dialog box appears with the following message:

Please wait while IDM is loading the current configuration from the sensor.
 
   

The main window of the IDM appears.


Note Both the default username and password are cisco. You were prompted to change the password during sensor initialization.



Note If you created a shortcut, you can launch the IDM by double-clicking the IDM shortcut icon. You can also close the The Cisco IPS Device Manager Version 7.0 window. After you launch the IDM, is it not necessary for this window to remain open.



For More Information

For more information about security and the IDM, refer to The IDM and Certificates.

For the procedure for initializing the sensor, refer to Initializing the Sensor.

Licensing the Sensor

This section describes how to obtain a license key and how to license the sensor using the CLI, the IDM, or the IME. It contains the following topics:

Understanding the License

Service Programs for IPS Products

Obtaining and Installing the License Key

Understanding the License

Although the sensor functions without the license key, you must have a license key to obtain signature updates and use the Global Correlation features. To obtain a license key, you must have the following:

Cisco Service for IPS service contract—Contact your reseller, Cisco service or product sales to purchase a contract.

Your IPS device serial number—To find the IPS device serial number in the IDM or the IME, for the IDM choose Configuration > Sensor Management > Licensing, and for the IME choose Configuration > sensor_name > Sensor Management > Licensing, or in the CLI use the show version command.

Valid Cisco.com username and password

Trial license keys are also available. If you cannot get your sensor licensed because of problems with your contract, you can obtain a 60-day trial license that supports signature updates that require licensing.

You can obtain a license key from the Cisco.com licensing server, which is then delivered to the sensor. Or, you can update the license key from a license key provided in a local file. Go to http://www.cisco.com/go/license and click IPS Signature Subscription Service to apply for a license key.

You can view the status of the license key in these places:

IDM Home window Licensing section on the Health tab

IDM Licensing pane (Configuration > Licensing)

IME Home page in the Device Details section on the Licensing tab

License Notice at CLI login

Whenever you start the IDM, the IME, or the CLI, you are informed of your license status—whether you have a trial, invalid, or expired license key. With no license key, an invalid license key, or an expired license key, you can continue to use the IDM, the IME, and the CLI, but you cannot download signature updates.

If you already have a valid license on the sensor, you can click Download on the License pane to download a copy of your license key to the computer that the IDM or the IME is running on and save it to a local file. You can then replace a lost or corrupted license, or reinstall your license after you have reimaged the sensor.

Service Programs for IPS Products

You must have a Cisco Services for IPS service contract for any IPS product so that you can download a license key and obtain the latest IPS signature updates. If you have a direct relationship with Cisco Systems, contact your account manager or service account manager to purchase the Cisco Services for IPS service contract. If you do not have a direct relationship with Cisco Systems, you can purchase the service account from a one-tier or two-tier partner.

When you purchase the following IPS products you must also purchase a Cisco Services for IPS service contract:

IPS 4240

IPS 4255

IPS 4260

IPS 4270-20

AIM IPS

IDSM2

NME IPS

When you purchase an ASA 5500 series adaptive security appliance product that does not contain IPS, you must purchase a SMARTnet contract.


Note SMARTnet provides operating system updates, access to Cisco.com, access to TAC, and hardware replacement NBD on site.


When you purchase an ASA 5500 series adaptive security appliance product that ships with AIP SSM installed, or if you purchase it to add to your ASA 5500 series adaptive security appliance product, you must purchase the Cisco Services for IPS service contract.


Note Cisco Services for IPS provides IPS signature updates, operating system updates, access to Cisco.com, access to TAC, and hardware replacement NBD on site.


For example, if you purchase an ASA 5510 and then later want to add IPS and purchase an ASA-SSM-AIP-10-K9, you must now purchase the Cisco Services for IPS service contract. After you have the Cisco Services for IPS service contract, you must also have your product serial number to apply for the license key.


Caution If you ever send your product for RMA, the serial number changes. You must then get a new license key for the new serial number.

Obtaining and Installing the License Key

You can install the license key through the CLI, the IDM, or the IME. This section describes how to obtain and install the license key, and contains the following topics:

Using the IDM or the IME

Using the CLI

Using the IDM or the IME


Note In addition to a valid Cisco.com username and password, you must also have a Cisco Services for IPS service contract before you can apply for a license key.


To obtain and install the license key, follow these steps:


Step 1 Log in to the IDM or the IME using an account with administrator privileges.

Step 2 For the IDM choose Configuration > Sensor Management > Licensing. For IME choose Configuration > sensor_name > Sensor Management > Licensing. The Licensing pane displays the status of the current license. If you have already installed your license, you can click Download to save it if needed.

Step 3 Obtain a license key by doing one of the following:

Click the Cisco.com radio button to obtain the license from Cisco.com. The IDM or the IME contacts the license server on Cisco.com and sends the server the serial number to obtain the license key. This is the default method. Go to Step 4.

Click the License File radio button to use a license file. To use this option, you must apply for a license key at this URL: www.cisco.com/go/license. The license key is sent to you in e-mail and you save it to a drive that the IDM or the IME can access. This option is useful if your computer cannot access Cisco.com. Go to Step 7.

Step 4 Click Update License, and in the Licensing dialog box, click Yes to continue. The Status dialog box informs you that the sensor is trying to connect to Cisco.com. An Information dialog box confirms that the license key has been updated.

Step 5 Click OK.

Step 6 Go to www.cisco.com/go/license.

Step 7 Fill in the required fields. Your license key will be sent to the e-mail address you specified.


Caution You must have the correct IPS device serial number because the license key only functions on the device with that number.

Step 8 Save the license key to a hard-disk drive or a network drive that the client running the IDM or the IME can access.

Step 9 Log in to the IDM or the IME.

Step 10 For the IDM choose Configuration > Sensor Management > Licensing. For the IME choose Configuration > sensor_name > Sensor Management > Licensing.

Step 11 Under Update License, click the License File radio button.

Step 12 In the Local File Path field, specify the path to the license file or click Browse Local to browse to the file.

Step 13 Browse to the license file and click Open.

Step 14 Click Update License.


Using the CLI


Note You cannot install an older license key over a newer license key.


Use the copy source-url license_file_name license-key command to copy the license key to your sensor.

The following options apply:

source-url—The location of the source file to be copied. It can be a URL or keyword.

destination-url—The location of the destination file to be copied. It can be a URL or a keyword.

license-key—The subscription license file.

license_file_name—The name of the license file you receive.

The exact format of the source and destination URLs varies according to the file. Here are the valid types:

ftp:—Source URL for an FTP network server. The syntax for this prefix is:

ftp://[[username@]location][/relativeDirectory]/filename

ftp://[[username@]location][//absoluteDirectory]/filename


Note You are prompted for a password.


scp:—Source URL for the SCP network server. The syntax for this prefix is:

scp://[[username@]location][/relativeDirectory]/filename

scp://[[username@]location][//absoluteDirectory]/filename


Note You are prompted for a password. You must add the remote host to the SSH known hosts list.


http:—Source URL for the web server. The syntax for this prefix is:

http://[[username@]location][/directory]/filename


Note The directory specification should be an absolute path to the desired file.


https:—Source URL for the web server. The syntax for this prefix is:

https://[[username@]location][/directory]/filename


Note The directory specification should be an absolute path to the desired file. The remote host must be a TLS trusted host.


Installing the License Key

To install the license key, follow these steps:


Step 1 Apply for the license key at this URL: www.cisco.com/go/license.


Note In addition to a valid Cisco.com username and password, you must also have a Cisco Services for IPS service contract before you can apply for a license key.


Step 2 Fill in the required fields. Your Cisco IPS Signature Subscription Service license key will be sent by e-mail to the e-mail address you specified.


Note You must have the correct IPS device serial number because the license key only functions on the device with that number.


Step 3 Save the license key to a system that has a web server, FTP server, or SCP server.

Step 4 Log in to the CLI using an account with administrator privileges.

Step 5 Copy the license key to the sensor.

sensor# copy scp://user@10.89.147.3://tftpboot/dev.lic license-key
Password: *******
 
   

Step 6 Verify the sensor is licensed.

sensor# show version
Application Partition:
 
   
Cisco Intrusion Prevention System, Version 7.0(2)E4
 
   
Host:                                                         
    Realm Keys          key1.0                                
Signature Definition:                                         
    Signature Update    S480.0                   2010-03-24   
OS Version:             2.4.30-IDS-smp-bigphys                
Platform:               ASA-SSM-20                            
Serial Number:          ABC1234DEFG 
License expired:        22-Feb-2010 UTC                       
Sensor up-time is 35 min.
Using 1023135744 out of 2093600768 bytes of available memory (48% usage)
system is using 17.4M out of 38.5M bytes of available disk space (45% usage)
application-data is using 44.7M out of 166.6M bytes of available disk space (28% usage)
boot is using 41.6M out of 68.5M bytes of available disk space (64% usage)
application-log is using 123.5M out of 513.0M bytes of available disk space (24% usage)
 
   
 
   
MainApp            B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   
2009-10-15T08:09:06-0500   Running   
AnalysisEngine     BE-BEAU_E4_2010_MAR_25_02_09_7_0_2   (Ipsbuild)   
2010-03-25T02:11:05-0500   Running   
CollaborationApp   B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   
2009-10-15T08:09:06-0500   Running   
CLI                B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   
2009-10-15T08:09:06-0500             
 
   
Upgrade History:
 
   
  IPS-K9-7.0-2-E4   04:00:07 UTC Thu Mar 25 2010   
        
Recovery Partition Version 1.1 - 7.0(2)E4
 
   
Host Certificate Valid from: 28-Mar-2010 to 28-Mar-2012
 
   
sensor#
 
   

Installing or Upgrading Cisco IME and Migrating Data In to the IME

This section describes how to install and upgrade the IME, and how to migrate date from IEV or a previous version of the IME.

Cisco IEV, Cisco IOS IPS, and CSM

If you have a version of Cisco IPS Event Viewer installed, the Install wizard prompts you to remove it before installing the IME.

The IME event monitoring is also supported in IOS-IPS versions that support the Cisco IPS 5.x/6.x signature format. We recommend IOS-IPS 12.4(15)T4 if you intend to use the IME to monitor an IOS IPS device. Some of the new IME functionality including health monitoring is not supported.


Caution Do not install the IME on top of existing installations of CSM. You must uninstall CSM before installing the IME. Do not install CSM on top of existing installations of the IME.

Installation Notes and Caveats

Observe the following when installing or upgrading the IME:

You can install the IME  over all versions of the IME but not over IEV. All alert database and user settings are preserved.

The IME  detects previous versions of IEV and prompts you to manually remove the older version before installing the IME or to install the IME on another system. The installation program then stops.

Make sure you close any open instances of the IME before upgrading the IME.

Disable any anti-virus or host-based intrusion detection software before beginning the installation, and close any open applications. The installer spawns a command shell application that may trigger your host-based detection software, which causes the installation to fail.

You must be administrator to install the IME.

The IME coexists with other instances of the MySQL database. If you have a MySQL database installed on your system, you do NOT have to uninstall it before installing the IME.

Installing or Upgrading to the IME

To install the IME, follow these steps:


Step 1 Download the IME executable file to your computer, or start the IDM in a browser window, and under Cisco IPS Manager Express, click download to install the IME executable file. IME-7.0.2.exe is an example of what the IME executable file might look like.

Step 2 Double-click the executable file. The Cisco IPS Manager Express - InstallShield Wizard appears. You receive a warning if you have a previous version of Cisco IPS Event Viewer installed. Acknowledge the warning, and exit installation. Remove the older version of IEV, and then continue IME installation.

Step 3 Click Next to start IME installation.

Step 4 Accept the license agreement and click Next.

Step 5 Click Next to choose the destination folder, click Install to install the IME, and then click Finish to exit the wizard. The Cisco IME and Cisco IME Demo icons are now on your desktop.



Note The first time you start the IME, you are prompted to set up a password.


Migrating IEV Data

To migrate IEV 5.x events to the IME, you must exit the installation and manually export the old events by using the IEV 5.x export function to move the data to local files. After installing IME 7.0, you can import these files to the new IME system.


Note The IME does not support import and migration functions for IEV 4.x.


To export event data from IEV 5.x to a local file:


Step 1 From IEV 5.x, choose File > Database Administration > Export Database Tables.

Step 2 Enter the file name and select the table(s).

Step 3 Click OK. The events in the selected table(s) are exported to the specified local file.


Importing IEV Event Data In to the IME

To import event data in to the IME, follow these steps:


Step 1 From the IME, choose File > Import.

Step 2 Select the file exported from IEV 5.x and click Open. The contents of the selected file are imported in to the IME.


For More Information

For more information about Cisco IME, refer to Cisco Intrusion Prevention System Manager Express Configuration Guide for IPS 7.0.

Restrictions and Limitations

The following restrictions and limitations apply to Cisco IPS 7.0(2)E4 software and the products that run it:

For IPS 5.0 and later, you can no longer remove the cisco account. You can disable it using the no password cisco command, but you cannot remove it. To use the no password cisco command, there must be another administrator account on the sensor. Removing the cisco account through the service account is not supported. If you remove the cisco account through the service account, the sensor most likely will not boot up, so to recover the sensor you must reinstall the sensor system image.

Anomaly detection does not support IPv6 traffic; only IPv4 traffic is directed to the anomaly detection processor.

IPv6 does not support the following event actions: Request Block Host, Request Block Connection, or Request Rate Limit.

The AIM IPS and the NME IPS do not support the IPv6 features, because the router in which they are installed does not send them IPv6 data. IPv6 inspection may work on IDSM2, but we do not officially support it. There is no support for IPv6 on the management (command and control) interface.

VACLs on Catalyst switches do not have IPv6 support. The most common method for copying traffic to a sensor configured in Promiscuous mode is to use VACL capture. If you want to have IPv6 support, you can use SPAN ports.

ICMP signature engines do not support ICMPv6, they are IPv4-specific, for example, the Traffic ICMP signature engine. ICMPv6 is covered by the Atomic IP Advanced signature engine.

The AIM IPS and the NME IPS do not support virtualization.

When you reload the router, the AIM IPS and the NME IPS also reload. To ensure that there is no loss of data on the AIM IPS or the NME IPS, make sure you shut down the module using the shutdown command before you use the reload command to reboot the router.

Do not deploy IOS IPS and the AIM IPS and the NME IPS at the same time.

When the AIM IPS and the NME IPS are used with an IOS firewall, make sure SYN flood prevention is done by the IOS firewall.

The AIM IPS and the NME IPS and the IOS firewall complement abilities of each other to create security zones in the network and inspect traffic in those zones. Because the AIM IPS and the NME IPS and the IOS firewall operate independently, sometimes they are unaware of the activities of the other. In this situation, the IOS firewall is the best defense against a SYN flood attack.

Cisco access routers only support one IDS/IPS per router.

On IPS sensors with multiple processors (for example, the IPS 4260 and IPS 4270-20), packets may be captured out of order in the IP logs and by the packet command. Because the packets are not processed using a single processor, the packets can become out of sync when received from multiple processors.

An IPS appliance can support both promiscuous and inline monitoring at the same time; however you must configure each physical interface in either promiscuous or inline mode. The sensor must contain at least two physical sensing interfaces to perform both promiscuous and inline monitoring. The exceptions to this are the AIP SSM-10, the AIP SSM-20, and the AIP SSM-40. The AIP SSM can support both promiscuous and inline monitoring on its single physical back plane interface inside the adaptive security appliance. The configuration on the main adaptive security appliance can be used to designate which packets/connections should be monitored by the AIP SSM as either promiscuous or inline.

When deploying an IPS sensor monitoring two sides of a network device that does TCP sequence number randomization, we recommend using a virtual senor for each side of the device.

After you upgrade any IPS software on your sensor, you must restart the IDM to see the latest software features.

The IDM does not support any non-English characters, such as the German umlaut or any other special language characters. If you enter such characters as a part of an object name through the IDM, they are turned into something unrecognizable and you will not be able to delete or edit the resulting object through the IDM or the CLI.

This is true for any string that is used by CLI as an identifier, for example, names of time periods, inspect maps, server and URL lists, and interfaces.

You can only install eight IDSM2s per switch chassis.

When SensorApp is reconfigured, there is a short period when SensorApp cannot respond to any queries. Wait a few minutes after reconfiguration is complete before querying SensorApp for additional information.

The IDM and the IME launch MySDN from the last browser window you opened, which is the default setting for Windows. To change this default behavior, in Internet Explorer, choose Tools > Internet Options, and then click the Advanced tab. Scroll down and uncheck the Reuse windows for launching shortcuts check box.

For More Information

For more information on interoperability between modules, refer to Interoperability With Other IPS Modules.

For more information about IPv6, switches, and lack of VACL capture, see IPv6, Switches, and Lack of VACL Capture.

Recovering the Password

For most IPS platforms, you can now recover the password on the sensor rather than using the service account or reimaging the sensor. This section describes how to recover the password for the various IPS platforms. It contains the following topics:

Understanding Password Recovery

Recovering the Appliance Password

Recovering the IDSM2 Password

Recovering the AIP SSM Password

Recovering the AIM IPS Password

Recovering the NME IPS Password

Disabling Password Recovery

Verifying the State of Password Recovery

Troubleshooting Password Recovery

Understanding Password Recovery

Password recovery implementations vary according to IPS platform requirements. Password recovery is implemented only for the cisco administrative account and is enabled by default. The IPS administrator can then recover user passwords for other accounts using the CLI. The cisco user password reverts to cisco and must be changed after the next login.


Note Administrators may need to disable the password recovery feature for security reasons.


Table 4 lists the password recovery methods according to platform.

Table 4 Password Recovery Methods According to Platform 

Platform
Description
Recovery Method

4200 series sensors

Stand-alone IPS appliances

GRUB prompt or ROMMON

AIP SSM

ASA 5500 series adaptive security appliance modules

ASA CLI command

IDSM2

Switch IPS module

Password recovery image file

AIM IPS
NME IPS

Router IPS modules

Bootloader command


For More Information

For more information on when and how to disable password recovery, see Disabling Password Recovery.

Recovering the Appliance Password

This section describes the two ways to recover the password for appliances. It contains the following topics:

Using the GRUB Menu

Using ROMMON

Using the GRUB Menu

For the 4200 series appliances, the password recovery is found in the GRUB menu, which appears during bootup. When the GRUB menu appears, press any key to pause the boot process.


Note You must have a terminal server or direct serial connection to the appliance to use the GRUB menu to recover the password.


To recover the password on appliances, follow these steps:


Step 1 Reboot the appliance. The following menu appears:

GNU GRUB version 0.94 (632K lower / 523264K upper memory)
-------------------------------------------
0: Cisco IPS
1: Cisco IPS Recovery
2: Cisco IPS Clear Password (cisco)
-------------------------------------------
 
   
    Use the ^ and v keys to select which entry is highlighted.
    Press enter to boot the selected OS, 'e' to edit the
    Commands before booting, or 'c' for a command-line.
 
   
    Highlighted entry is 0:
 
   

Step 2 Press any key to pause the boot process.

Step 3 Choose 2: Cisco IPS Clear Password (cisco). The password is reset to cisco. You can change the password the next time you log into the CLI.


For More Information

For more information on connecting an appliance to a terminal server, refer to Connecting an Appliance to a Terminal Server.

Using ROMMON

For the IPS 4240 and the IPS 4255 you can use the ROMMON to recover the password. To access the ROMMON CLI, reboot the sensor from a terminal server or direct connection and interrupt the boot process.


Note After recovering the password, you must reset the confreg to 0, otherwise, when you try to upgrade the sensor, the upgrade fails because when the sensor reboots, it goes to password recovery (confreg 0x7) rather than to the upgrade option.


To recover the password using the ROMMON CLI, follow these steps:


Step 1 Reboot the appliance.

Step 2 To interrupt the boot process, press ESC or Control-R (terminal server) or send a BREAK command (direct connection).

The boot code either pauses for 10 seconds or displays something similar to one of the following:

Evaluating boot options

Use BREAK or ESC to interrupt boot

Step 3 Enter the following commands to reset the password.

confreg 0x7
boot
 
   

Sample ROMMON session:

Booting system, please wait...
CISCO SYSTEMS
Embedded BIOS Version 1.0(11)2 01/25/06 13:21:26.17
...
Evaluating BIOS Options...
Launch BIOS Extension to setup ROMMON
Cisco Systems ROMMON Version (1.0(11)2) #0: Thu Jan 26 10:43:08 PST 2006
Platform IPS 4240-K9
Use BREAK or ESC to interrupt boot.
Use SPACE to begin boot immediately.
Boot interrupted. 
Management0/0
Link is UP
MAC Address:000b.fcfa.d155
Use ? for help.
rommon #0> confreg 0x7
Update Config Register (0x7) in NVRAM...
rommon #1> boot
 
   

Step 4 Enter the following command to reset the confreg value to 0:

confreg 0
 
   

Recovering the IDSM2 Password

To recover the password for the IDSM2, you must install a special password recovery image file. This installation only resets the password, all other configuration remains intact. The password recovery image is version-dependent and can be found on the Cisco Download Software site. For IPS 6.x, download WS-SVC-IDSM2-K9-a-6.0-password-recovery.bin.gz. For IPS 7.x, download WS-SVC-IDSM2-K9-a-7.0-password-recovery.bin.gz.

FTP is the only supported protocol for image installations, so make sure you put the password recovery image file on an FTP server that is accessible to the switch. You must have administrative access to the Cisco 6500 series switch to recover the password on the IDSM2.

During the password recovery image installation, the following message appears:

Upgrading will wipe out the contents on the hard disk.
Do you want to proceed installing it [y|n]:
 
   

This message is in error. Installing the password recovery image does not remove any configuration, it only resets the login account.

Once you have downloaded the password recovery image file, follow the instructions to install the system image file but substitute the password recovery image file for the system image file. The IDSM2 should reboot into the primary partition after installing the recovery image file. If it does not, enter the following command from the switch:

hw-module module module_number reset hdd:1

Note The password is reset to cisco. Log in to the CLI with username cisco and password cisco. You can then change the password.


For More Information

For the procedures for reimaging IDSM2, refer to Installing the IDSM2 System Image.

For more information on downloading Cisco IPS software, see Obtaining Software on Cisco.com.

Recovering the AIP SSM Password

You can reset the password to the default (cisco) for the AIP SSM using the CLI or the ASDM. Resetting the password causes it to reboot. IPS services are not available during a reboot.


Note To reset the password, you must have ASA 7.2.2 or later.


Use the hw-module module slot_number password-reset command to reset the password to the default cisco. If the module in the specified slot has an IPS version that does not support password recovery, the following error message is displayed:

ERROR: the module in slot <n> does not support password recovery.

Resetting the Password Using the CLI

To reset the password on the AIP SSM, follow these steps:


Step 1 Log into the adaptive security appliance and enter the following command to verify the module slot number:

asa# show module
Mod Card Type                                    Model              Serial No.
--- -------------------------------------------- ------------------ -----------
  0 ASA 5510 Adaptive Security Appliance         ASA5510            JMX1135L097
  1 ASA 5500 Series Security Services Module-40  ASA-SSM-40         JAF1214AMRL
 
   
Mod MAC Address Range                 Hw Version   Fw Version   Sw Version
--- --------------------------------- ------------ ------------ ---------------
  0 001b.d5e8.e0c8 to 001b.d5e8.e0cc  2.0          1.0(11)2     8.4(3)
  1 001e.f737.205f to 001e.f737.205f  1.0          1.0(14)5     7.0(7)E4
 
   
Mod SSM Application Name           Status           SSM Application Version
--- ------------------------------ ---------------- --------------------------
  1 IPS                            Up               7.0(7)E4
 
   
Mod Status             Data Plane Status     Compatibility
--- ------------------ --------------------- -------------
  0 Up Sys             Not Applicable
  1 Up                 Up
 
   

Step 2 Reset the password for module 1.

asa# hw-module module 1 password-reset
Reset the password on module in slot 1? [confirm]
 
   

Step 3 Press Enter to confirm.

Password-Reset issued for slot 1.
 
   

Step 4 Verify the status of the module. Once the status reads Up, you can session to the AIP SSM.

asa# show module 1
Mod Card Type                                    Model              Serial No. 
--- -------------------------------------------- ------------------ -----------
  1 ASA 5500 Series Security Services Module-40  ASA-SSM-40         JAF1214AMRL
 
   
Mod MAC Address Range                 Hw Version   Fw Version   Sw Version     
--- --------------------------------- ------------ ------------ ---------------
  1 001e.f737.205f to 001e.f737.205f  1.0          1.0(14)5     7.0(7)E4
 
   
Mod SSM Application Name           Status           SSM Application Version
--- ------------------------------ ---------------- --------------------------
  1 IPS                            Up               7.0(7)E4
 
   
Mod Status             Data Plane Status     Compatibility
--- ------------------ --------------------- -------------
  1 Up                 Up         
 
   
 
   

Step 5 Session to the AIP SSM.

asa# session 1
Opening command session with slot 1.
Connected to slot 1. Escape character sequence is 'CTRL-^X'.
 
   

Step 6 Enter the default username (cisco) and password (cisco) at the login prompt.

login: cisco 
Password: cisco
 
   
You are required to change your password immediately (password aged) 
Changing password for cisco. 
(current) password: cisco
 
   

Step 7 Enter your new password twice.

New password: new password
Retype new password: new password
 
   
***NOTICE*** 
This product contains cryptographic features and is subject to United States and local 
country laws governing import, export, transfer and use. Delivery of Cisco cryptographic 
products does not imply third-party authority to import, export, distribute or use 
encryption. Importers, exporters, distributors and users are responsible for compliance 
with U.S. and local country laws. By using this product you agree to comply with 
applicable laws and regulations. If you are unable to comply with U.S. and local laws, 
return this product immediately. 
 
   
A summary of U.S. laws governing Cisco cryptographic products may be found at: 
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html 
 
   
If you require further assistance please contact us by sending email to export@cisco.com. 
 
   
***LICENSE NOTICE*** 
There is no license key installed on this IPS platform. The system will continue to 
operate with the currently installed signature set. A valid license must be obtained in 
order to apply signature updates. Please go to http://www.cisco.com/go/license to obtain a 
new license or install a license. 
aip_ssm#
 
   

Using the ASDM

To reset the password in the ASDM, follow these steps:


Step 1 From the ASDM menu bar, choose Tools > IPS Password Reset.


Note This option does not appear in the menu if there is no IPS present.


Step 2 In the IPS Password Reset confirmation dialog box, click OK to reset the password to the default (cisco). A dialog box displays the success or failure of the password reset. If the reset fails, make sure you have the correct ASA and IPS software versions.

Step 3 Click Close to close the dialog box. The sensor reboots.


Recovering the AIM IPS Password

To recover the password for the AIM IPS, use the clear password command. You must have console access to the AIM IPS and administrative access to the router.

To recover the password for the AIM IPS, follow these steps:


Step 1 Log in to the router.

Step 2 Enter privileged EXEC mode on the router.

router> enable
 
   

Step 3 Confirm the module slot number in your router.

router# show run | include ids-sensor
interface IDS-Sensor0/0
router#
 
   

Step 4 Session in to the AIM IPS.

router# service-module ids-sensor slot/port session
 
   

Example

router# service-module ids-sensor 0/0 session
 
   

Step 5 Press Control-shift-6 followed by x to navigate to the router CLI.

Step 6 Reset the AIM IPS from the router console:

router# service-module ids-sensor 0/0 reset
 
   

Step 7 Press Enter to return to the router console.

Step 8 When prompted for boot options, enter *** quickly. You are now in the bootloader.

Step 9 Clear the password.

ServicesEngine boot-loader# clear password
 
   

The AIM IPS reboots. The password is reset to cisco. Log in to the CLI with username cisco and password cisco. You can then change the password.


Recovering the NME IPS Password

To recover the password for the NME IPS, use the clear password command. You must have console access to the NME IPS and administrative access to the router.

To recover the password for the NME IPS, follow these steps:


Step 1 Log in to the router.

Step 2 Enter privileged EXEC mode on the router.

router> enable
 
   

Step 3 Confirm the module slot number in your router.

router# show run | include ids-sensor
interface IDS-Sensor1/0
router#
 
   

Step 4 Session in to the NME IPS.

router# service-module ids-sensor slot/port session
 
   

Example

router# service-module ids-sensor 1/0 session
 
   

Step 5 Press Control-shift-6 followed by x to navigate to the router CLI.

Step 6 Reset the NME IPS from the router console.

router# service-module ids-sensor 1/0 reset
 
   

Step 7 Press Enter to return to the router console.

Step 8 When prompted for boot options, enter *** quickly. You are now in the bootloader.

Step 9 Clear the password.

ServicesEngine boot-loader# clear password
 
   

The NME IPS reboots. The password is reset to cisco. Log in to the CLI with username cisco and password cisco. You can then change the password.


Disabling Password Recovery


Caution If you try to recover the password on a sensor on which password recovery is disabled, the process proceeds with no errors or warnings; however, the password is not reset. If you cannot log in to the sensor because you have forgotten the password, and password recovery is set to disabled, you must reimage your sensor.

Password recovery is enabled by default. You can disable password recovery through the CLI or the IDM.

Disabling Password Recovery Using the CLI

To disable password recovery in the CLI, follow these steps:


Step 1 Log in to the CLI using an account with administrator privileges.

Step 2 Enter global configuration mode.

sensor# configure terminal
 
   

Step 3 Enter host mode.

sensor(config)# service host
 
   

Step 4 Disable password recovery.

sensor(config-hos)# password-recovery disallowed
 
   

Disabling Password Recovery Using the IDM

To disable password recovery in the IDM, follow these steps:


Step 1 Log in to the CLI using an account with administrator privileges.

Step 2 Choose Configuration > Sensor Setup > Network. The Network pane appears.

Step 3 To disable password recovery, uncheck the Allow Password Recovery check box.


For More Information

If you are not certain about whether password recovery is enabled or disabled, see Verifying the State of Password Recovery.

For more information on reimaging sensors, refer to Upgrading, Downgrading, and Installing System Images.

Verifying the State of Password Recovery

Use the show settings | include password command to verify whether password recovery is enabled.

To verify whether password recovery is enabled, follow these steps:


Step 1 Log in to the CLI.

Step 2 Enter service host submode.

sensor# configure terminal
sensor (config)# service host
sensor (config-hos)# 
 
   

Step 3 Verify the state of password recovery by using the include keyword to show settings in a filtered output.

sensor(config-hos)# show settings | include password
   password-recovery: allowed <defaulted>
sensor(config-hos)#
 
   

Troubleshooting Password Recovery

To troubleshoot password recovery, pay attention to the following:

You cannot determine whether password recovery has been disabled in the sensor configuration from the ROMMON prompt, GRUB menu, switch CLI, or router CLI. If password recovery is attempted, it always appears to succeed. If it has been disabled, the password is not reset to cisco. The only option is to reimage the sensor.

You can disable password recovery in the host configuration. For the platforms that use external mechanisms, such as the AIM IPS and NME IPS bootloader, ROMMON, and the maintenance partition for the IDSM2, although you can run commands to clear the password, if password recovery is disabled in the IPS, the IPS detects that password recovery is not allowed and rejects the external request.

To check the state of password recovery, use the show settings | include password command.

When performing password recovery on the IDSM2, you see the following message: Upgrading will wipe out the contents on the storage media. You can ignore this message. Only the password is reset when you use the specified password recovery image.

For More Information

For more information on reimaging sensors, refer to Upgrading, Downgrading, and Installing System Images.

For the procedure for disabling password recovery, see Disabling Password Recovery.

For the procedure for verifying the state of password recovery, see Verifying the State of Password Recovery.

Resolved Caveats

The following known issues have been resolved in Cisco IPS 7.0(2)E4:

CSCse94001—ENGINE: improve telnet option parsing as anti-evasion measure

CSCsg20728—Actions do not appear in alerts when modify-packet-inline is configured

CSCsm37654—Signature 1220.0 does not alarm

CSCso66999—Automatic Ack limiter

CSCsq92185—E2 engine upgrade causes sensor to hang

CSCsr95290—Caret support for regex in atomic-ip

CSCsu86596—Fixed UDP Engine does not properly handle start of packet ("^") in regex

CSCsv07624—Engine service pack installs on a sensor of equal maj.min(sp) level

CSCsv22395—SMB-Advanced should have a generic handler for unrecognized smb commands

CSCsv98672—AIC Enforce Content Types false positive

CSCsw20463—11005.2 tcp kazaa signature doesnt fire in servicep2p

CSCsw67575—SMBAdvanced slowdown on file copy

CSCsw70331—Implement the IOS Lightweight Engines typedef

CSCsw86555—5582 false positve

CSCsx20458—Sig 1300.0 firing incorrectly

CSCsy30036—Inspect HTTP traffic on all ports

CSCsy30176—Meta engine enhancements for E4

CSCsy74853—Engine Flood.Host Source Ports Bug

CSCsy96323—Alarm Context data is not complete in E3

CSCsz01229—Multistring Engine False Negative

CSCsz15601—Create engine-p2p signatures for Share P2P Application

CSCsz34935—Signature 1302.0 does not fire

CSCsz65453—Add regex table split support to HTTP engine

CSCsz95342—Sensors may track the direction tcp streams improperly

CSCta12368—1330.12 and 1330.18 false positives with high volume traffic

CSCta38577—SensorApp stops responding when adding a String signature

CSCta49978—String HTTP does not calculate context buffer offset correctly for Args

CSCtc18038—SensorApp mismanages buffers when TX queue full

CSCtc43996—Engine P2P may not properly check boundaries

CSCtc61972—Ares P2P signature does not fire

CSCtd92090—idsm2 misfiring 1330 17,19,23

CSCtf31408—Engine Update installer can leave sensor in incomplete state

CSCtf40209—Signature Obsoletes from "backport" engines are being processed

CSCtf47008—sensorApp signatureDB corruption when processing same Src/Dst packets

Related Documentation

For more information on Cisco IPS, refer to the following documentation found at this URL:

http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/tsd_products_support_series_home.html

Documentation Roadmap for Cisco Intrusion Prevention System

Cisco Intrusion Prevention System Device Manager Configuration Guide

Cisco Intrusion Prevention System Manager Express Configuration Guide

Cisco Intrusion Prevention System Command Reference

Cisco Intrusion Prevention System Sensor CLI Configuration Guide

Cisco Intrusion Prevention System Appliance and Module Installation Guide

Installling and Removing Interface Cards in Cisco IPS-4260 and IPS 4270-20

Regulatory Compliance and Safety Information for the Cisco Intrusion Detection and Prevention System 4200 Series Appliance Sensor

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.

Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.