Table Of Contents
Release Notes for Cisco Intrusion Prevention System 6.2(2)E3
Contents
IPS 6.2(2)E3 File List
Supported Platforms
Supported Servers
ROMMON and TFTP
IPS Management and Event Viewers
New and Changed Information
Receiving Cisco IPS Active Update Bulletins
Cisco Security Center
IPv6, Switches, and Lack of VACL Capture
Before Upgrading to Cisco IPS 6.2(2)E3
Perform These Tasks
Copying and Restoring the Configuration File Using a Remote Server
Obtaining Software on Cisco.com
IPS Software Versioning
Major and Minor Updates, Service Packs, and Patch Releases
Signature/Virus Updates and Signature Engine Updates
Recovery and System Image Filenames
6.x Software Release Examples
Upgrading to Cisco IPS 6.2(2)E3
Upgrade Notes and Caveats
Upgrading to 6.2(2)E3
After Upgrading to Cisco IPS 6.2(2)E3
Comparing Configurations
Importing a New SSL Certificate
Logging In to IDM
Licensing the Sensor
Understanding the License
Service Programs for IPS Products
Obtaining and Installing the License Key
Installing or Upgrading Cisco IME
Before Installing or Upgrading IME
Cisco IME Installation and Upgrade Instructions
Restrictions and Limitations
Caveats
Resolved Caveats
Known Caveats
Related Documentation
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Intrusion Prevention System 6.2(2)E3
CDC Date September 28, 2009
Revised: October 16, 2009
Contents
•
IPS 6.2(2)E3 File List
•Supported Platforms
•Supported Servers
•ROMMON and TFTP
•IPS Management and Event Viewers
•New and Changed Information
•Receiving Cisco IPS Active Update Bulletins
•Cisco Security Center
•IPv6, Switches, and Lack of VACL Capture
•Before Upgrading to Cisco IPS 6.2(2)E3
•Upgrading to Cisco IPS 6.2(2)E3
•After Upgrading to Cisco IPS 6.2(2)E3
•Installing or Upgrading Cisco IME
•Restrictions and Limitations
•Caveats
•Related Documentation
•Obtaining Documentation and Submitting a Service Request
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.
IPS 6.2(2)E3 File List
The following files are part of Cisco IPS 6.2(2)E3:
•Readme
–IPS-6.2-2-E3.readme.txt
•Minor Version Upgrade File
–IPS-K9-6.2-2-E3.pkg
–IPS-AIM-K9-6.2-2-E3.pkg
–IPS-NME-K9-6.2-2-E3.pkg
–IPS-SSC_5-K9-6.2-2-E3.pkg
•System Image Files
–IPS-4240-K9-sys-1.1-a-6.2-2-E3.img
–IPS-4255-K9-sys-1.1-a-6.2-2-E3.img
–IPS-4260-K9-sys-1.1-a-6.2-2-E3.img
–IPS-4270_20-K9-sys-1.1-a-6.2-2-E3.img
–IDSM2-K9-sys-1.1-a-6.2-2-E3.bin.gz
–IPS-SSC_5-K9-sys-1.1-a-6.2-2-E3.img
–IPS-SSM_10-K9-sys-1.1-a-6.2-2-E3.img
–IPS-SSM_20-K9-sys-1.1-a-6.2-2-E3.img
–IPS-SSM_40-K9-sys-1.1-a-6.2-2-E3.img
–IPS-AIM-K9-sys-1.1-a-6.2-2-E3.img
–IPS-NME-K9-sys-1.1-a-6.2-2-E3.img
•Recovery Image Files
–IPS-K9-r-1.1-a-6.2-2-E3.pkg
–IPS-AIM-K9-r-1.1-a-6.2-2-E3.pkg
–IPS-NME-K9-r-1.1-a-6.2-2-E3.pkg
–IPS-SSC_5-K9-r-1.1-a-6.2-2-E3.pkg
For More Information
For the procedure for obtaining these files on Cisco.com, see Obtaining Software on Cisco.com.
Supported Platforms
Note All IPS platforms allow ten concurrent CLI sessions.
Note AIM-IPS and NME-IPS do not support the IPv6 features, because the routers in which they are installed do not send them IPv6 data. IPv6 inspection may work on IDSM-2, but we do not officially support it. There is no support for IPv6 on the management (command and control) interface. With ASA 8.2(1), AIP-SSM and AIP-SSC-5 support IPv6 features.
Cisco IPS 6.2(2)E3 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
•Intrusion Detection System Module (IDSM-2) for Catalyst 6500 series switches
•ASA-SSC-AIP-5 Series Cisco ASA Advanced Inspection and Prevention Security Services Cards (AIP-SSC-5)
•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)
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:
•VMS - Apache Server (Tomcat)
•VMS - 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.
Some TFTP servers limit the maximum file size that can be transferred to ~32 MB. Therefore, we recommend the following TFTP servers:
•For Windows:
Tftpd32 version 2.0, available at:
http://tftpd32.jounin.net/
•For UNIX:
Tftp-hpa series, available at:
http://www.kernel.org/pub/software/network/tftp/
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 upgrades, for the CLI refer to Configuring Automatic Upgrades, for IDM refer to Configuring Automatic Update, and for IME refer to Configuring Automatic Update.
IPS Management and Event Viewers
Use the following tools for configuring Cisco IPS 6.2(2)E3 sensors:
•Cisco IDM 6.2
•Cisco IME 6.2
•IPS CLI 6.2
•ASDM 5.2 and above
Use the following tools for monitoring Cisco IPS 6.2(2)E3 sensors:
•Cisco IME 6.2 and 7.0
•CWSIMS v3.3.1.v3.4 mad v3.4.1
•CIC Security Monitor 3.6
Note You may need to configure viewers that are already configured to monitor the Cisco IPS 6.1 sensors to accept a new SSL certificate for the Cisco IPS 6.2(2)E3 sensors.
New and Changed Information
Cisco IPS 6.2(2)E3 includes the following new features:
•E3 signature engine update and the S425 signature update with these new features:
–Signature date and type
The signature date represents the date at which the signature was first created. The date is stored in the format YYYYMMDD. The signature type represents the category in which a specific signature falls. Signatures are broadly classified as vulnerability, exploit, anomaly, component, or other. The default is other.
–Duplicate packet detector statistics
Duplicate packet statistics are now added to the TCP Normalizer Stage Statistics section of the show statistics virtual sensor command output. Large numbers of duplicate packets being reported by the Normalizer can aid in the detection of sensor deployment and configuration problems. Duplicate packets are often seen in situations where a single virtual sensor is monitoring two or more networks, and is seeing a TCP connection crossing two or more of these networks. In this situation you can reconfigure the sensor to monitor each network using a different virtual sensor. If both networks must be monitored by a single virtual sensor, configure the virtual sensor with the inline-TCP-session-tracking-mode parameter set to either interface-and-vlan or vlan-only.
–UDP length parameter in Atomic engines
A new parameter to match a specific UDP length was added. This engine parameter is added in the Atomic IP Advanced and Atomic IP engine for l4-protocol UDP. The purpose of this parameter is to check if UDP total length falls within a specific range.
•IDM version 7.0(2)
•Changes from CSCsu77935
The idle time algorithm of the sensor has been modified. Additional CPU has been applied to polling the NICs to decrease the polling interval and reduce latency. The CPU usage is thus reported as higher than in previous releases, including external tools such as top and ps. You will notice the additional CPU load on single-CPU platforms and on the primary CPU of multicore systems.
Because the additional CPU load reported while polling is actually available to process packets, and is reduced as inspection load goes up, it does not negatively affect the overall throughput of the IPS.
Use the show statistics virtual-sensor command to see the sensor load. It is listed under Processing Load Percentage in the output. You can also view the sensor load on the IME Device List pane.
For More Information
•For detailed information on the Normalizer engine, refer to Normalizer Engine.
•For detailed information on the Atomic IP engines, refer to Atomic Engine.
•For the procedure for using the show statistics command, refer to Displaying Statistics.
•For a description of the IME Device List pane, refer to Device List Pane.
Receiving Cisco IPS Active Update Bulletins
You can subscribe to Cisco IPS Active Update Bulletins on Cisco.com to receive e-mails when signature updates and service pack updates occur.
To receive bulletins about updates, follow these steps:
Step 1 Log in to Cisco.com.
Step 2 Under Quick Links on the right side of the window, click Security Center.
Step 3 Scroll down and under Products and Service Updates, choose Cisco IPS Active Update Bulletins.
Step 4 Click one of the Cisco IPS Active Update Bulletins.
Step 5 Under In this Issue, click Subscription Information.
Step 6 Under Subscription Information, click subscribe now.
Step 7 Fill out the required information, as follows:
a. Would you like to receive IDS Active Update Bulletin? Select Yes or No from the drop-down list.
b. Enter your first name in the First Name field.
c. Enter your last name in the Last Name field.
d. Enter the name of your company in the Company field.
e. Choose your country from the drop-down menu.
f. Enter your e-mail address in the E-mail field.
Step 8 Check the check box if you want to receive further information about Cisco products and offerings by e-mail.
Step 9 Fill in the optional information if desired.
a. Choose your job function from the drop-down list.
b. Choose your job level from the drop-down list.
c. Choose your industry or business type from the drop-down list.
d. Choose how many people your organization employs worldwide from the drop-down list.
e. Choose your company or organization type from the drop-down list.
Step 10 Click Submit.
You receive e-mail notifications of updates when they occur and instructions on how to obtain them.
Cisco Security Center
The Cisco Security Center 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. The Cisco Security Center contains the top ten intelligence reports listed by date, severity, urgency, and whether there is a new signature available to deal with the threat.
The Cisco Security Center contains a Security News section that lists security articles of interest. There are related security tools and links.
You can access the Cisco Security Center at this URL:
http://tools.cisco.com/MySDN/Intelligence/home.x
The Cisco Security Center is also a repository of information for individual signatures, including signature ID, type, structure, and description.
You can access the signature search at this URL:
http://tools.cisco.com/security/center/search.x?search=Signature
IPv6, Switches, and Lack of VACL Capture
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.
However, you can only configure up to two monitor sessions on a switch unless you use the following configuration:
•Monitor session
•Multiple trunks to one or more sensors
•Restrict per trunk port which VLANs are allowed to perform monitoring of many VLANs to more than two different sensors or virtual sensors within one IPS
The following configuration uses one SPAN session to send all of the traffic on any of the specified VLANs to all of the specified ports. Each port configuration only allows a particular VLAN or VLANs to pass. Thus you can send data from different VLANs to different sensors or virtual sensors all with one SPAN configuration line:
set trunk 4/1 on dot1q 930
set trunk 4/2 on dot1q 932
set trunk 4/3 on dot1q 960
set trunk 4/4 on dot1q 962
set span 930, 932, 960, 962 4/1-4 both
Note The SPAN/Monitor configuration is valuable when you want to assign different IPS policies per VLAN or when you have more bandwidth to monitor than one interface can handle.
For More Information
For more information on configuring SPAN/monitor on switches, refer to the following sections in Catalyst 6500 Series Software Configuration Guide, 8.7:
•Configuring SPAN, RSPAN and the Mini Protocol Analyzer
•Configuring SPAN on the Switch
•Configuring Ethernet VLAN Trunks
•Defining the Allowed VLANs on a Trunk
Before Upgrading to Cisco IPS 6.2(2)E3
This section describes the actions you should take before upgrading to Cisco IPS 6.2(2)E3. It contains the following topics:
•Perform These Tasks
•Copying and Restoring the Configuration File Using a Remote Server
•Obtaining Software on Cisco.com
•IPS Software Versioning
Perform These Tasks
Before you upgrade your sensors to Cisco IPS 6.2(2)E3, make sure you perform the following tasks:
•Check to make 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 Copying 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 IDM refer to IDM Home Window, and for IME refer to Sensor Information Gadget.
•For the procedure for downgrading signature updates on your sensor, refer to Upgrading, Downgrading, and Installing System Images.
Copying and Restoring the Configuration File Using a Remote Server
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.
Note We recommend copying the current configuration file to a remote server before upgrading.
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.
The exact format of the source and destination URLs varies according to the file. Here are the valid types:
•ftp:—Source or destination URL for an FTP network server. The syntax for this prefix is:
ftp:[//[username@] location]/relativeDirectory]/filename
ftp:[//[username@]location]//absoluteDirectory]/filename
•scp:—Source or destination URL for the SCP network server. The syntax for this prefix is:
scp:[//[username@] location]/relativeDirectory]/filename
scp:[//[username@] location]//absoluteDirectory]/filename
Note If you use FTP or SCP protocol, you are prompted for a password. If you use SCP protocol, you must also 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
•https:—Source URL for the web server. The syntax for this prefix is:
https:[[/[username@]location]/directory]/filename
Note HTTP and HTTPS prompt for a password if a username is required to access the website. If you use HTTPS protocol, the remote host must be a TLS trusted host.
The following keywords are used to designate the file location on the sensor:
•current-config—The current running configuration. The configuration becomes persistent as the commands are entered.
•backup-config—The storage location for the configuration backup.
Caution Copying a configuration file from another sensor may result in errors if the sensing interfaces and virtual sensors are not configured the same.
To back up and restore your current configuration, 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@10.1.1.1//configuration/cfg current-config
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]:
Step 4 Enter no so the sensor does not replace the existing configuration.
For More Information
For the procedure for adding trusted hosts, for the CLI refer to Adding TLS Trusted Hosts, for IDM refer to Configuring Trusted Hosts, and for 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.
Note You must be logged in to Cisco.com to download software.
Note You must have an active IPS maintenance contract and a Cisco.com password to download software.
Note You must have a license to apply signature updates.
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.
Note Major and minor updates, service packs, recovery files, signature and signature engine updates are the same for all sensors. System image files are unique per platform.
IPS Software Versioning
This section describes the various IPS software files, gives example file names, and contains the following sections:
•Major and Minor Updates, Service Packs, and Patch Releases
•Signature/Virus Updates and Signature Engine Updates
•Recovery and System Image Filenames
•6.x Software Release Examples
Major and Minor Updates, Service Packs, and Patch Releases
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
Major Update
Contains new functionality or an architectural change in the product. For example, the Cisco IPS 6.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 6.0(1) requires 5.x. With each major update there are corresponding system and recovery packages.
Note The 6.0(1) major update is only used to upgrade 5.x sensors to 6.0(1) If you are reinstalling 6.0(1) on a sensor that already has 6.0(1) installed, use the system image or recovery procedures rather than the major update.
Minor Update
Incremental to the major version. Minor updates are also base versions for service packs. The first minor update for 6.0 is 6.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 Packs
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 6.0(3) is released, and E3 is the latest engine level, the service pack is released as 6.0(3)E3.
Patch Release
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 6.0(1p1) requires 6.0(1).
Note Upgrading to a newer patch does not require you to uninstall the old patch. For example, you can upgrade from patch 6.0(1p1) to 6.0(1p2) without first uninstalling 6.0(1p1).
Signature/Virus Updates and Signature Engine Updates
Figure 2 illustrates what each part of the IPS software file represents for signature/virus updates.
Figure 2 IPS Software File Name for Signature/Virus Updates,
Signature/Virus Updates
Executable 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.
A virus component for the signature updates is packaged with the signature update. Virus updates are generated by Trend Microsystems for use by the Cisco Intrusion Containment System (Cisco ICS). Once created for use by Cisco ICS, they are later be incorporated into standard Cisco signature updates.
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
Signature Engine Updates
Executable files containing binary code to support new signature updates. Signature engine files require a specific service pack, which is also identified by the req designator.
Recovery and System Image Filenames
Figure 4 illustrates what each part of the IPS software file represents for recovery and system image filenames.
Figure 4 IPS Software File Name for Recovery and System Image Filenames
Recovery and system images contain separate versions for the installer and the underlying application. The installer version contains a major and minor version field.
Installer Major Version
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.
Installer Minor Version
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.
6.x Software Release Examples
Table 1 lists platform-independent Cisco IPS 6.x software release examples. Refer to the Readmes that accompany the software files for detailed instructions on how to install the files.
Table 1 Platform-Independent Release Examples
Release
|
Target Frequency
|
Identifier
|
Example Version
|
Example Filename
|
Signature update1
|
Weekly
|
sig
|
S353
|
IPS-sig-S353-req-E3.pkg
|
Signature engine update2
|
As needed
|
engine
|
E3
|
IPS-engine-E3-req-6.2-1.pkg
|
Service packs3
|
Semi-annually
or as needed
|
—
|
6.1(3)
|
IPS-K9-6.2-3-E3.pkg
|
Minor version update4
|
Annually
|
—
|
6.1(1)
|
IPS-K9-6.2-2-E3.pkg
Note IPS-AIM-K9-6.2-1-E3.pkg is the minor version update for AIM-IPS. IPS-NME-K-9-6.2-1-E3.pkg is the minor version update for NME-IPS.
|
Major version update5
|
Annually
|
—
|
6.0(1)
|
IPS-K9-6.0-1-E3.pkg
|
Patch release6
|
As needed
|
patch
|
6.0(1p1)
|
IPS-K9-patch-6.2-1pl-E3.pkg
|
Recovery package7
|
Annually or as needed
|
r
|
1.1-6.1(1)
|
IPS-K9-r-1.1-a-6.2-2-E3.pkg
|
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-6.2-2-E3.img
|
Maintenance partition image2
|
Annually
|
mp
|
IDSM-2
|
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
|
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
|
SSC_5
SSM_10
SSM_20
SSM_40
|
Upgrading to Cisco IPS 6.2(2)E3
This section provides information on upgrading to Cisco IPS 6.2(2)E3, and contains the following topics:
•Upgrade Notes and Caveats
•Upgrading to 6.2(2)E3
Upgrade Notes and Caveats
The following upgrade notes and caveats apply to upgrading your sensor to IPS 6.2(2)E3:
•You must have a valid Cisco Service for IPS Maintenance contract per sensor to receive and use software upgrades from Cisco.com.
•Minimum required versions:
–Appliances must be running 5.0(1) or later but less than 7.0(1).
–AIM-IPS must be running 6.0(4) or later but less than 7.0(1).
–NME-IPS must be running 6.1(1) or later but less than 7.0(1).
–AIP-SSC-5 must be running version 6.2(1).
Note Use IPS-AIM-K9-6.2-2-E3.pkg to upgrade AIM-IPS, IPS-NME-K9-6.2-2-E3to upgrade NME-IPS, and IPS-SSC_5-K9-6.2-2-E3.pkg to upgrade AIP-SSC-5. For all other supported sensors, use the IPS-K9-6.2-2-E3.pkg upgrade file.
•Using automatic update:
–If you configured automatic update for your sensor, copy the 6.2(2)E3 update files to the directory on the server that your sensor polls for updates.
–If you are using automatic update with a mixture of IPS appliances and modules (AIM-IPS, AIP-SSC-5, or NME-IPS), make sure you put all of the 6.2(2)E3 upgrade files on the automatic update server so the modules can correctly detect which file needs to be automatically downloaded and installed. If you only put the 6.2(2)E3upgrade file (IPS-K9-6.2-2-E3.pkg) on the server, the modules will download and try to install the wrong file.
–When you upgrade AIM-IPS or 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 module has been automatically updated, you can reenable heartbeat reset. If you do not disable heartbeat reset, the upgrade can fail and leave the module in an unknown state, which can require a system reimage to recover.
•Using manual update:
–When you upgrade AIM-IPS or 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 AIM-IPS or NME-IPS in an unknown state, which can require a system reimage to recover.
•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 IPS-4240, IPS-4255, IPS-4260, and IPS 4270-20, use the ROMMON to restore the system image.
–For AIM-IPS and NME-IPS, use the bootloader.
–For IDSM-2, reimage the application partition from the maintenance partition.
–For AIP-SSM and AIP-SSC-5, 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 the procedures for reimaging sensors, refer to Upgrading, Downgrading, and Installing System Images.
•For the procedure for disabling heartbeat reset, for AIP-IPS refer to Enabling and Disabling Heartbeat Reset, and for NME-IPS refer to Enabling and Disabling Hartebeest Reset.
•For more information on Cisco service contracts, see Service Programs for IPS Products.
•For the procedure for configuring automatic upgrade, refer to Configuring Automatic Upgrades.
Upgrading to 6.2(2)E3
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 (for example, IPS-K9-6.2-2-E3.pkg) to an FTP, SCP, HTTP, or HTTPS server that is accessible from your sensor.
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-6.2-2-E3.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-6.2-2-E3.pkg
Step 5 Enter the password when prompted.
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.
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 6.2(2)E3
This section provides information about what to do after you install Cisco IPS 6.2(2)E3. It contains the following topics:
•Comparing Configurations
•Importing a New SSL Certificate
•Logging In to IDM
•Licensing the Sensor
Comparing Configurations
Compare your backed up and saved 6.1 configuration with the output of the show configuration command after upgrading to 6.2(2)E3 to verify that all the configuration has been properly converted.
Caution If the configuration is not properly converted, check the caveats for Cisco IPS 6.2(2)E3. 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 a list of the caveats associated with this release, see 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 IDM refer to Configuring Trusted Hosts, and for IME refer to Configuring Trusted Hosts.
Logging In to IDM
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 IDM, follow these steps:
Step 1 Open a web browser and enter the sensor IP address:
https://sensor_ip_address
Note 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 IDM in the format https://sensor_ip_address:port (for example, https://10.1.9.201:1040).
A Security Alert dialog box appears.
Step 2 Click Yes to accept the security certificate.
The Cisco IPS Device Manager Version 6.2 window appears.
Step 3 To launch IDM, click Run IDM.
The JAVA loading message box appears.
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.
The IDM on ip_address dialog box appears.
Step 5 To create a shortcut for IDM, click Yes.
Note You must have JRE 1.5 (JAVA 5) installed to create shortcuts for IDM. If you have JRE 1.6 (JAVA 6) installed, the shortcut is created automatically.
The Cisco IDM Launcher dialog box appears.
Step 6 To authenticate IDM, enter your username and password, and click OK.
Note Both the default username and password are cisco. You were prompted to change the password during sensor initialization.
IDM begins to load.
If you change panes from Home to Configuration or Monitoring before 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 IDM appears.
Note If you created a shortcut, you can launch IDM by double-clicking the IDM shortcut icon. You can also close the Cisco IPS Device Manager Version 6.2 window. After you launch IDM, is it not necessary for this window to remain open.
Licensing the Sensor
This section describes how to obtain a license key and how to license the sensor using the CLI, IDM, or 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. 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 IDM or IME, for IDM choose Configuration > Sensor Management > Licensing, and for 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 IDM, 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 IDM, 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 IDM or 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
•IDSM-2
•NME-IPS
For ASA 5500 series adaptive security appliance products, if you purchased one of the following ASA 5500 series adaptive security appliance products that do not contain IPS, you must purchase a SMARTnet contract:
•ASA5510-K8
•ASA5510-DC-K8
•ASA5510-SEC-BUN-K9
•ASA5520-K8
•ASA5520-DC-K8
•ASA5520-BUN-K9
•ASA5540-K8
•ASA5540-DC-K8
•ASA5540-BUN-K9
Note SMARTnet provides operating system updates, access to Cisco.com, access to TAC, and hardware replacement NBD on site.
If you purchased one of the following ASA 5500 series adaptive security appliance products that ships with AIP-SSM or AIP-SSC-5 installed or if you purchased them to add to your ASA 5500 series adaptive security appliance product, you must purchase the Cisco Services for IPS service contract:
•ASA5510-AIP10-K9
•ASA5520-AIP10-K9
•ASA5520-AIP20-K9
•ASA5540-AIP20-K9
•ASA5520-AIP40-K9
•ASA5540-AIP40-K9
•ASA-SSM-AIP-10-K9=
•ASA-SSM-AIP-20-K9=
•ASA-SSM-AIP-40-K9=
•ASA5505-AIP5P-K9
•ASA5505-U-AIP5P-K9
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 purchased an ASA-5510 and then later wanted to add IPS and purchased 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 will change. 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, IDM, IME. This section describes how to obtain and install the license key, and contains the following topics:
•Using IDM or IME
•Using the CLI
Using IDM or 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 IDM or IME using an account with Administrator privileges.
Step 2 For 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.
IDM or 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 IDM or 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.
Caution You must have the correct IPS device serial number because the license key only functions on the device with that number.
Your license key will be sent to the e-mail address you specified.
Step 8 Save the license key to a hard-disk drive or a network drive that the client running IDM or IME can access.
Step 9 Log in to IDM or IME.
Step 10 For IDM choose Configuration > Sensor Management > Licensing. For 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.
For More Information
For information on Cisco service contracts, see Service Programs for IPS Products.
Using the CLI
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.
Note You cannot install an older license key over a newer license key.
The exact format of the source and destination URLs varies according to the file. Here are the valid types:
•ftp:—Source or destination URL for an FTP network server. The syntax for this prefix is:
ftp:[//[username@] location]/relativeDirectory]/filename
ftp:[//[username@]location]//absoluteDirectory]/filename
•scp:—Source or destination URL for the SCP network server. The syntax for this prefix is:
scp:[//[username@] location]/relativeDirectory]/filename
scp:[//[username@] location]//absoluteDirectory]/filename
Note If you use FTP or SCP protocol, you are prompted for a password. If you use SCP protocol, 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
•https:—Source URL for the web server. The syntax for this prefix is:
https:[[/[username@]location]/directory]/filename
Note If you use HTTPS protocol, the remote host must be a TLS trusted host.
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.
Note You must have the correct IPS device serial number because the license key only functions on the device with that number.
Your Cisco IPS Signature Subscription Service license key will be sent by e-mail to the e-mail address you specified.
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
Step 6 Verify the sensor is licensed.
Cisco Intrusion Prevention System, Version 6.2(2)E3
Signature Update S391.0 2008-04-16
Virus Update V1.2 2005-11-24
OS Version: 2.4.30-IDS-smp-bigphys
Serial Number: P300000220
Sensor up-time is 3 days.
Using 1031888896 out of 2093682688 bytes of available memory (49% usage)
system is using 17.8M out of 29.0M bytes of available disk space (61% usage)
application-data is using 52.4M out of 166.6M bytes of available disk space (33% usage)
boot is using 37.8M out of 68.5M bytes of available disk space (58% usage)
MainApp N-2007_JUN_19_16_45 (Release) 2007-06-19T17:10:20-0500 Running
AnalysisEngine N-2007_JUN_19_16_45 (Release) 2007-06-19T17:10:20-0500 Running
CLI N-2007_JUN_19_16_45 (Release) 2007-06-19T17:10:20-0500
IPS-K9-6.2-2-E3 15:36:05 UTC Thu Apr 24 2008
Recovery Partition Version 1.1 - 6.2(2)E3
Host Certificate Valid from: 25-Apr-2008 to 26-Apr-2010
Step 7 Copy your license key from a sensor to a server to keep a backup copy of the license.
sensor# copy license-key scp://user@10.89.147.3://tftpboot/dev.lic
Installing or Upgrading Cisco IME
This section describes how to install and upgrade IME, and contains the following topics:
•Before Installing or Upgrading IME
•Cisco IME Installation and Upgrade Instructions
Before Installing or Upgrading IME
IME 7.0 detects previous versions of IEV and prompts you to manually remove the older version before installing IME 7.0 or to install IME on another system. The installation program then stops.
Caution IME does not automatically uninstall IEV.
IME 7.0 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 IME 7.0.
Migrating IEV Data
To migrate IEV 5.x events to 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 IME 7.0 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 IME
To import event data in to IME, follow these steps:
Step 1 From 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 IME.
Cisco IME Installation and Upgrade Instructions
Cisco IPS Event Viewer and Cisco IOS IPS
If you have a version of Cisco IPS Event Viewer installed, the Install wizard prompts you to remove it before installing IME.
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 IME to monitor an IOS IPS device. Some of the new IME functionality including health monitoring is not supported.
Installing or Upgrading to IME 7.0
You can install IME 7.0 over IME 6.2. All alert database and user settings are preserved.
Note Make sure you close any open instances of IME 6.2 before upgrading to IME 7.0.
Caution 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.
Note You must be Administrator to install IME.
To install IME, follow these steps:
Step 1 Download the IME executable file to your computer, or start IDM in a browser window, and under Cisco IPS Manager Express, click download to install the IME executable file.
IME-7.0.1.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.
Step 3 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 4 Double-click the executable file.
The Cisco IPS Manager Express - InstallShield Wizard appears.
Step 5 Click Next to start IME installation.
Step 6 Accept the license agreement and click Next.
Step 7 Click Next to choose the destination folder, click Install to install IME, and then click Finish to exit the wizard.
The Cisco IME and Cisco IME Demo icons are now on your desktop.
For More Information
For more information about Cisco IME, refer to Installing and Using Cisco Intrusion Prevention System Manager Express 6.2.
Restrictions and Limitations
The following restrictions and limitations apply to Cisco IPS 6.2(2)E3 software and the products that run it:
•AIP-SSC-5 does not support virtualization, unretiring default retired signatures, creating custom signatures, adding signatures, cloning signatures, or anomaly detection.
•AIP-SSC-5 can take up to 20 minutes to come online when it reboots after the installation of a new system image. You must let the process complete before you can make configuration changes to AIP-SSC-5. If you try to modify and save configuration changes before the process is complete, you receive an error message.
•Anomaly detection does not support IPv6 traffic; only IPv4 traffic is directed to the anomaly detection processor.
•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.
•Rate limiting and blocking are not supported for IPv6 traffic. If a signature is configured with a block or rate limit event action and is triggered by IPv6 traffic, an alert is generated but the action is not carried out.
•IPv6 does not support the following event actions: Request Block Host, Request Block Connection, or Request Rate Limit.
•CSM and MARS do not support IPv6.
•AIM-IPS and NME-IPS do not support the IPv6 features, because the routers in which they are installed do not send them IPv6 data. IPv6 inspection may work on IDSM-2, but we do not officially support it. There is no support for IPv6 on the management (command and control) interface. With ASA 8.2(1), AIP-SSM and AIP-SSC-5 support IPv6 features.
•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.
•AIM-IPS and NME-IPS do not support virtualization.
•When you reload the router, AIM-IPS and NME-IPS also reload. To ensure that there is no loss of data on AIM-IPS or 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 AIM-IPS and NME-IPS at the same time.
•When AIM-IPS and NME-IPS are used with an IOS firewall, make sure SYN flood prevention is done by the IOS firewall.
AIM-IPS and 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 AIM-IPS and 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.
•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 AIP-SSM-10, AIP-SSM-20, and AIP-SSM-40. 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 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.
•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 IDM, they are turned into something unrecognizable and you will not be able to delete or edit the resulting object through 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 IDSM-2s 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.
•IDM and 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.
Caveats
For the most complete and up-to-date list of caveats, use the Bug Navigator Tool to refer to the caveat release notes. The Bug Navigator Tool is found at this URL:
http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl
This section lists the resolved and known caveats, and contains the following topics:
•Resolved Caveats
•Known Caveats
Resolved Caveats
The following known issues have been resolved in the 6.2(2)E3 release:
•CSCsd18827—SNMP trap should not have double quotes with the community string
•CSCsj40623—4260/4270 quad copper hw bypass has problems linking < 1000Mbps
•CSCsm24466—Jumbo frames on XL interface can cause dropped packets
•CSCsq51372—IPS:6.1.1 Iplogging out of file descriptors warning should be summarized
•CSCsu88701—correct checking for SigEventList NULL error message
•CSCsv11068—The IDCONF library must preserve non-IDCONF attributes
•CSCsv49498—ASA loses connectivity with the SSM (IPS)
•CSCsv52117—Sensor CLI does not start when remoteApp did not close tcp connections.
•CSCsv56782—sensorApp terminates while deleting database nodes
•CSCsv66660—sensorApp abort during database hashtree expire
•CSCsv69844—add RegexDepth sensorApp.conf config setting (default off)
•CSCsv74657—CLI show conf command displays hidden passwords
•CSCsv75021—event-count and alert-interval does not work correctly
•CSCsv80568—Tuning sig 1610.0 locks up the SSM
•CSCsw14574—smbadvanced abort in processdecodedtcpmessage
•CSCsw20414—Configure kernel to reboot on Kernel Panic
•CSCsw25900—IPS has bad health and welfare stats after E3 upgrade
•CSCsx17909—sensor eventStore 10 Meg size too small
•CSCsx35823—Sig 1317 with Jumbo packet may cause sensorApp abort.
•CSCsx47618—4255 unresponsive when running specific stress test
•CSCsx48178—sensorApp abort when reconfiguring signatures.
•CSCsx50254—4260/4270 speed/duplex errors in main log
•CSCsy21250—add extended sensorApp memory stats to sh st vi
•CSCsy29684—IPS 6.1.2E3: sensorApp terminates unexpectedly in UpdateTime
•CSCsy46810—Sensor hangs when issuing some cli command
•CSCsy77167—auto purge (sigEdit/sigUpdate) does not return ununsed memory
•CSCsy88163—implement sensor self-purge for memory protection (off by default)
•CSCsz28844—sensorApp aborts in InspectorServiceSnmp
•CSCsz83039—MSrpc UDP mode has unsafe iterator access
•CSCta07220—threadRef multi-thread safety violation
•CSCta23644—timer thread safety violations
•CSCta31166—iplog memory and file leak
•CSCta59839—ipsDebug utility does not run in the show tech
•CSCta63245—idprom code is not mips compatible
•CSCta67580—Kernel OOM kills sensorapp when IDM is launched after reboot
•CSCta76034—sensor needs to be able to handle udld packets
•CSCtb79056—Cannot create virtualsensor instances with non default sig instance
•CSCtb83255—SSC platform ID fails
•CSCtb89760—No such file or directory messages appearing at boot-up
Known Caveats
The following known issues are found in Cisco IPS 6.2(2)E3:
•CSCse40651—Config operation on heavily loaded system may cause unresponsive system
•CSCsg09619—IPS accepts RSA keys with exponent 3 which are vulnerable to forgery
•CSCsg26929—Interface errors when enabled in cli and ifconfig up
•CSCsg96871—AnalysisEngine InspectorServiceAICWeb::ToServiceInspect abort
•CSCsh16294—IPSVIRTUALIZATION:Physical Interface info not passed to ASA/SSM Database
•CSCsh45936—Leading Space in the uri-regex in Service-HTTP Works Ambiguously
•CSCsh50760—NAC causes high mainApp usage
•CSCsh89833—Delete event variable referenced by filter or sig from IDM
•CSCsi21029—GRE tunnels blocked by sensorApp inspection defect
•CSCsi60530—69xx firing but reporting wrong interface
•CSCsi73502—6.0(2)E1: No warning message when removing sensor used by ASA
•CSCsj14632—IP fragmented attacks through IPv4-in-IPv6 tunnel can be missed
•CSCsj35723—Sigs not alarming after default service sig sig0
•CSCsj57474—Frag traffic with dot1q headers misses a few sweep and atomic-ip sigs
•CSCsj70643—Normalizer signatures not modifying-packet-inline
•CSCsj82458—global-block-timeout allows values outside supported range
•CSCsk53813—upgrade log files are not preserved during an upgrade
•CSCsl66235—Setup errors after defaulting sensor config via IDM
•CSCsl69776—AD is not generating an alert for every worm attacker
•CSCsm37654—Signature 1220.0 does not alarm
•CSCsm37826—Signature 1300 does not always alarm on a 4260
•CSCsm37943—Tcp Timeout Sigs do not produce alarms in promic
•CSCsm46158—Critical memory condition can cause race condition
•CSCsm47102—Signature 1308 does not function
•CSCso15962—"""show interface clear"" does not clear Management interface counters"
•CSCso20750—modify-packet-inline computing incorrect checksum
•CSCso60709—Flood net Engine Sigs 69xx are not firing in promiscuous mode
•CSCso74628—AIM and NME underperforming in promiscuous mode
•CSCso98858—config change with bypass off triggers ASA failover
•CSCsq18457—Unauthenticated Ntp settings lost after recover application-partition
•CSCsq19704—meta sigs modified to replace meta-components only fire post restart
•CSCsq53214—IPS reports different sig version in CT and CLI
•CSCsr02826—Missed Packet statistic does not work on AIM/NME
•CSCsu10359—Fragmented traffic may cause false negative
•CSCsu48178—excessive https failures results in too many open files
•CSCsu86596—"Fixed UDP Engine does not properly handle start of packet (""^"") in regex"
•CSCsv01700—Analysis engine is down when Denied attackers are configured repeatedly
•CSCsv26568—IPS SNMP InterfaceGroup OID does not show correct Virtual Sensor
•CSCsv28527—4260 shows incorrect available memory
•CSCsv29654—Sig 5575 it is firing also for the return traffic
•CSCsv52117—Sensor CLI fails to start
•CSCsw20463—11005.2 tcp kazaa signature doesnt fire in servicep2p
•CSCsw50140—SSC: SSC/SSM will not sync up with NTP server time changes
•CSCsw86555—5582 false positve
•CSCsx09696—Summary alerts not getting generated for global and regular summary mode
•CSCsx21487—IPS: Sensor Becomes Unresponsive to Remote Monitoring
•CSCsx24335—socket error: 110 when copying config from ftp to ips
•CSCsx40862—Alert not generated for diff attacker & target addr for filter testcases
•CSCsx47663—Ssc getting frequent clock reset messages when under heavy loads
•CSCsx56901—cidAssert: Condition failed on SSC
•CSCsx62373—"""Cid/E errSystemError - Application """"AnalysisEngine """"terminated premature"""
•CSCsx70656—Occasional latency event or disrupted traffic flow on inline sensor.
•CSCsy18476—sensor allows creation of custom atomic ipv6 signature
•CSCsy44884—mainapp aborts while retreiving ntp config in 6.1
•CSCsy46895—IPS 6.0 SensorApp aborts
•CSCsy47529—IPS: EnetStub Producer Core in sensorApp on Jumbo Traffic
•CSCsy72736—'errSystemError unable to retrieve name for context' on fragmented traff
•CSCsy74853—Engine Flood.Host Source Ports Bug
•CSCsy80419—SSC goes Unresponsive after downloading biosdisk file
•CSCsy86272—SSC does not spring forward when ASA configured for summer time
•CSCsy87971—IPS - Can not get vlan statistic with inline vlan pair
•CSCsy93548—SSC goes unresponsive after IPS image is applied
•CSCsy93571—cidAssert after resetting SSC from the ASA
•CSCsy93579—SensorApp becomes memory critical over time.
•CSCsy93652—SSC Stuck in Recover State after biosdisk update
•CSCsy93892—SSC service account disable after loading biosdisk twice
•CSCsy96323—Alarm Context data is not complete in E3
•CSCsy96358—System Image on SSC giving cidsDump
•CSCsy96427—SSC becomes Unresponsive after downloading image
•CSCsz01229—Multistring Engine False Negative
•CSCsz02922—Unable to login to SSC after running reimaging script
•CSCsz05366—SSC stuck at grub prompt after imaging
•CSCsz07509—SSC hangs in recover state while loading IPS image
•CSCsz19556—7280.0 does not reilably alert
•CSCsz20563—SMB Advanced STL vector out of range error message
•CSCsz29539—SSC does not verify NTP server
•CSCsz32206—"""SSC remains """"Unresponsive"""" after shutdown"""
•CSCsz34935—Signature 1302.0 does not fire
•CSCsz37915—IPS creates core.txt and mainapp aborts due to notificationApp.
•CSCsz51442—sig 1225 0 only fires after 60 second delay over GRE tunnel
•CSCsz56911—NTP configuration not implemented unless the SSC is reloaded
•CSCsz57521—IPS creates core.txt and mainapp aborts due to AuthenticationApp.
•CSCsz81580—High CPU and processing load percentage = 100
•CSCsz93219—sensorApp fails in application thread
•CSCsz95342—Sensors may track the direction tcp streams improperly
•CSCsz98551—Sensor app abort on H225 traffic in InspectorServiceH225
•CSCta01262—IPS: AIP-SSM module spontaneously reboots without leaving a core
•CSCta02342—sensorApp SignatureDB refcount integrity problem
•CSCta09335—sensorApp fails when malloc returns NULL
•CSCta12368—SigID 1330-12 and 1330-18 False positive with high communications traffi
•CSCta31745—SSC status toggling between Up and Unresponse
•CSCta38577—SensorApp stops responding when adding a String signature
•CSCta40558—Small MainApp memory leak
•CSCta43555—Network Security Level not functioning
•CSCta49978—String HTTP does not calculate context buffer offset correctly for Args
•CSCta62901—IPS: AD does not match zones based on IP address longest prefix match
•CSCta72182—AIM-IPS drops several packets when upgrade
•CSCta74031—"""IPS: sensorApp crashes on libhoard.so, produces a core file"""
•CSCtb03228—AnalysisEngine NotRunning
•CSCtb03932—IDSM - loses clock sync with the NTP server
•CSCtb12160—SSC-5: IDM https sessions hung in CLOSE_WAIT
•CSCtb29314—Sensors not meeting performance numbers due to Sig update
•CSCtb31577—IPS: SDEE stops functioning
•CSCtb39179—SensorApp fails on 4270 in TcpRootNode::expireNow()
•CSCtb58224—No mgmt communications after clearing and reconfiguring host config
•CSCtb62989—"""IPS: mainApp crashes on libpthread.so.0, produces core file"""
•CSCtb68012—Jumbo frames cause idsm2 to print warning messages to system log
•CSCtb87986—"""Sig 1208 and 1204 do not fire when configuring """"specify-alert-interval"""""""
•CSCtc10186—Knowledge Base Rotation Memory Handling Needs Improvement
•CSCtc10476—Change of configurable password requirement
•CSCtc18038—SensorApp mismanages buffers when TX queue full
The following known issues are found in IDM 7.0(2)E3:
•CSCso96654—Editing EventActionRules removes all like Sig Actions
•CSCsq89977—IDM unable to edit multistring sig regex list entry
•CSCsr82134—IDM is allowing user to delete Risk Category that is in use
•CSCsu08058—Signatures Restore Default makes no changes if modified
•CSCsu21774—Better handling needed for Signature editing
•CSCsu47761—creating advanced atomic sig. results in blank main screen
•CSCsv83687—IDM SSM startup wizard does not assign interface to virtual sensor
•CSCsx42999—IDM/Unable to sort Signature by "Action"
•CSCsy52817—IDM index.html has broken image file on IE 7
Related Documentation
For more information on Cisco IPS 6.2(2)E3, 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 6.2
•Installing and Using Cisco Intrusion Prevention System Device Manager 6.2
•Installing and Using Cisco Intrusion Prevention System Manager Express 6.2
•Cisco Intrusion Prevention System Command Reference 6.2
•Configuring the Cisco Intrusion Prevention System Sensor Using the Command Line Interface 6.2
•Installing Cisco Intrusion Prevention System Appliances and Modules
•Installing and Removing Interface Cards in Cisco IPS-4260 and IPS 4270-20
•Regulatory Compliance and Safety Information for the Cisco Intrusion Prevention System 4200 Series Appliance Sensor
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0908R)
Copyright © 2008-2009 Cisco Systems, Inc. All rights reserved.
