Table Of Contents
Cisco PIX Security Appliance Release Notes Version 7.1(2)
Maximum Recommended Configuration File Size
Cisco VPN Software Interoperability
Cisco VPN Client Interoperability
Cisco Easy VPN Remote Interoperability
Determining the Software Version
Upgrading to a New Software Release
Important Notes in Release 7.1
Maximum Security Contexts and VLANs Supported
Readme Document for the Conduits and Outbound List Conversion Tool 1.2
Features not Supported in Version 7.1
Resolved Caveats - Release 7.1(2)
Software Configuration Tips on the Cisco TAC Home Page
Obtaining Documentation and Submitting a Service Request
Cisco PIX Security Appliance Release Notes Version 7.1(2)
March 2006Contents
This document includes the following sections:
•
Obtaining Documentation and Submitting a Service Request
Introduction
Note
The PIX 501, PIX 506/506E, and PIX 520 security appliances are not supported in software Version 7.1.
The Cisco PIX 500 series security appliance delivers unprecedented levels of defense against threats to the network with deeper web inspection and flow-specific analysis, improved secure connectivity through end-point security posture validation and voice and video over VPN support. It also provides enhanced support for intelligent information networks through improved network integration, resiliency, and scalability. This release introduces significant enhancements to all major functional areas, including: firewalling and inspection services, VPN services, network integration, high-availability services, and management/monitoring.
For more information on all the new features, see New Features
Additionally, the security appliance software supports ASDM. ASDM is a browser-based, Java applet used to configure and monitor the software on the security appliances. ASDM is loaded from the security appliance, then used to configure, monitor, and manage the device.
System Requirements
The sections that follow list the system requirements for operating a security appliance.
Note
The PIX 501, PIX 506/506E, and PIX 520 security appliances are not supported in software Version 7.1.
Memory Requirements
If you are using a PIX 515/515E running PIX Version 6.2/6.3, you need to upgrade your memory before performing an upgrade to PIX Version 7.0. PIX Version 7.0 requires at least 64 MB of RAM for Restricted (R) licenses and 128 MB of RAM for Unrestricted (UR) and Failover (FO) licenses. The following security appliance platforms require at least 64 MB of RAM. Table 1 lists Flash memory requirements for Version 7.1.
Table 1 Flash Memory Requirements
Security Appliance Model Flash Memory Required in Version 7.1PIX 515/515E
16 MB
PIX 525
16 MB
PIX 535
16 MB
For more information on minimum memory requirements, see the "Minimum Memory Requirements" section in the Guide for Cisco PIX 6.2 and 6.3 Users Upgrading to Cisco PIX Software Version 7.0.
Software Requirements
Version 7.1(2) requires the following:
1.
The minimum software version required before performing an upgrade to PIX Version 7.1 is PIX Version 7.0. If you are running a PIX release prior to PIX Version 6.2, you must first upgrade to PIX Version 6.2 or PIX Version 6.3 before you can begin the upgrade to PIX Version 7.0.
To upgrade your PIX software image, go to the following website:
http://www.cisco.com/public/sw-center/index.shtml
2.
For information on specific licenses supported on each model of the security appliance, go to the following website:
http://www.cisco.com/go/license/index.html
3.
If you are upgrading from a previous PIX version, save your configuration and write down your activation key and serial number. For new installation requirements, see the following website:
http://www.cisco.com/public/sw-center/index.shtml
Maximum Recommended Configuration File Size
For the PIX 525 and PIX 535, the maximum supported configuration file size is 2 MB for Version 7.1(2). For the PIX 515/515E, the maximum supported configuration file size is 1 MB for Version 7.1(2). If you are using ASDM, we recommend no more than a 500 KB configuration file because larger configuration files can interfere with the performance of ASDM on your workstation.
While configuration files up to 2 MB are supported on the PIX 525 and PIX 535, be aware that such large configuration files can reduce system performance. For example, a large configuration file is likely to noticeably slow execution times in the following situations:
•
While executing commands such as the write terminal and show running-config commands
•
Failover (the configuration synchronization time)
•
During a system reload
Cisco VPN Software Interoperability
Cisco VPN Client Interoperability
Cisco Easy VPN Remote Interoperability
Determining the Software Version
Use the show version command to verify the software version installed on your security appliance.
Upgrading to a New Software Release
If you have a Cisco.com (CDC) login, you can obtain software from the following website:
If you want to upgrade or downgrade from Version 7.0.(x) to 7.1(x) and vice versa You must follow the steps below because older versions of the security appliance images does not recognize new ASDM images, new security appliance images does not recognize old ASDM images.
To upgrade from Version 7.0.(x) to 7.1(x), you must perform the following steps:
Step 1
Load the new Version 7.1(x) image from the following website:
http://www.cisco.com/public/sw-center/index.shtml
Step 2
Reload the device so that it will start using the Version 7.1(x) image.
Step 3
Copy new ASDM Version 5.1(x) image from the following website:
http://www.cisco.com/public/sw-center/index.shtml
To downgrade from Version 7.1(x) to 7.0.(x), you must perform the following steps:
Step 1
Load the earlier Version 7.0(x) image from the following website:
http://www.cisco.com/public/sw-center/index.shtml
Step 2
Reload the device so that it will be use the Version 7.0(x) image.
Step 3
Copy the ASDM Version 5.0(x) image from the following website:
http://www.cisco.com/public/sw-center/index.shtml
New Features
Version 7.1(2) includes several caveat resolutions.
Important Notes
Important Notes in Release 7.1
This section lists important notes related to Version 7.1(2).
Maximum Security Contexts and VLANs Supported
The maximum security contexts supported in release 7.1(2) for the PIX 535 are 50 tiers. The maximum number of VLANs supported are 150. For more information on the feature support for each platform license, see the "Platform Feature Licenses" section in the Cisco Security Appliance Command Line Configuration Guide.
IKE Delete-with-Reason
IKE syslogs for Delete-with-Reason do not contain the reason text unless the clients support this feature. Currently the VPN 3002 Version 4.7 and PIX 501 Version 6.3(4) hardware clients do not support this feature.
Note
The PIX 501security appliance is not supported in software Version 7.1.
User Upgrade Guide
Before upgrading to Version 7.1(2), read the Guide for Cisco PIX 6.2 and 6.3 Users Upgrading in Cisco PIX Software Version 7.0. This guide also includes information about deprecated features and other changes in the Cisco PIX Software Version7.0. For a list of deprecated features, and user upgrade information, go to the following URL:
http://www.cisco.com/en/US/docs/security/asa/asa70/pix_upgrade/upgrade/guide/pixupgrd.html
CautionIf you share the Stateful Failover update link with a link for regular traffic such as your inside interface, you must change your configuration before upgrading. Do not upgrade until you have corrected your configuration, as this is not a supported configuration and Version 7.1(2) treats the LAN failover and Stateful Failover update interfaces as special interfaces. If you upgrade to Version 7.1(2) with a configuration that shares an interface for both regular traffic and the Stateful Failover updates, configuration related to the regular traffic interface will be lost after the upgrade. The lost configuration may prevent you from connecting to the security appliance over the network.
Readme Document for the Conduits and Outbound List Conversion Tool 1.2
The security appliance Outbound/Conduit Conversion tool assists in converting configurations with outbound or conduit commands to similar configurations using ACLs. ACL-based configurations provide uniformity and leverage the powerful ACL feature set. ACL based configurations provide the following benefits:
•
ACE insertion capability - System configuration and management is greatly simplified by the ACE insertion capability that allows users to add, delete or modify individual ACEs.
•
Outbound ACLs and Time-based ACLs - Gives administrators improved flexibility for defining access control policies by adding support for outbound ACLs and time-based ACLs.
•
Enabling/Disabling of ACL Entries - Provides a convenient troubleshooting tool that allows administrators to test and fine-tune ACLs, without the need to remove and replace ACL entries.
Features not Supported in Version 7.1
The following features are not supported in Version7.1(2) release:
•
PPPoE
•
L2TP over IPSec
•
PPTP
MIB Supported
For information on MIB Support, go to:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Downgrade to Previous Version
To downgrade to a previous version of the operating system software (software image), use the downgrade command in privileged EXEC mode.
For more information and a complete description of the command syntax, see the Cisco Security Appliance Command Reference.
CautionDo not load a previous version of software if your PIX security appliance is currently running PIX Version 7.0 or later. Loading a software image from monitor mode, on a PIX security appliance that has a PIX Version 7.0 file system, results in unpredictable behavior and is not supported. We strongly recommend that you use the downgrade command from a running PIX Version 7.0 image that facilitates the downgrade process.
Caveats
The following sections describe the caveats for the 7.1(2) release.
For your convenience in locating caveats in Cisco's Bug Toolkit, the caveat titles listed in this section are drawn directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation may be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
•
Commands are in boldface type.
•
Product names and acronyms may be standardized.
•
Spelling errors and typos may be corrected.
Note
If you are a registered cisco.com user, view Bug Toolkit on cisco.com at the following website:
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.do
Open Caveats - Release 7.1(2)
Resolved Caveats - Release 7.1(2)
Related Documentation
Use this document in conjunction with the PIX Firewall and Cisco VPN client Version 3.x documentation at the following websites:
•
http://www.cisco.com/en/US/partner/products/sw/secursw/ps2120/tsd_products_support_series_home.html
•
http://www.cisco.com/en/US/partner/products/sw/secursw/ps2308/tsd_products_support_series_home.html
Software Configuration Tips on the Cisco TAC Home Page
The Cisco Technical Assistance Center has many helpful pages. If you have a CDC account you can visit the following websites for assistance:
TAC Troubleshooting, Sample Configurations, Hardware Info, Software Installations and more:
http://www.cisco.com/en/US/partner/support/tsd_most_requested_tools.html
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.
![]()


