Table Of Contents
Release Notes for Cisco Secure ACS
Solution Engine 4.0
Full Build Numbers:
These release notes pertain to Cisco Secure Access Control Server Solution Engine release 4.0, hereafter referred to as ACS SE.
The ACS release numbering system for software includes major release, minor release, maintenance build, and interim build number in the MMM.mmm.###.BBB format. For this release, the versioning information is:
•Cisco Secure ACS 188.8.131.52 for Quanta (1113)
•184.108.40.206 for Quanta (1112)
•ACS 220.127.116.11 for HP (1111)
Elsewhere in this document where 4.0 is used, we are referring to 4.0.1. ACS major release numbering starts at 4.0.1, not 4.0.0. Use this information when working with your customer service representative.
These release notes provide:
New and Changed Information
This section contains new and changed information for ACS SE 4.0:
New Quanta 1113 Platform
The ACS SE 1113 release consists of a new hardware device that replaces the previous ACS SE 1112 device. The ACS SE 1113 device conforms to Reduction in Hazardous Substances (RoHS) directives of the European Economic Community (EEC)—Directive 73/23/EEC and Directive 89/336/EEC as amended by Directive 93/68/EEC.
New Hotfixes in ACS SE 4.0
The ACS SE base image contains the following Microsoft hotfixes:
•KB822831—BUG: Driver installation program does not install device drivers.
•KB823980—MS03-026: Buffer overrun in RPC may allow code execution.
•KB824105—MS03-034: Flaw in NetBIOS could lead to information disclosure.
•KB824146—MS03-039: A buffer overrun in RPCSS could allow an attacker to run malicious programs.
•KB828028—MS04-007: An ASN.1 vulnerability could allow code execution.
•KB828741—MS04-012: Cumulative Update for Microsoft RPC/DCOM.
•KB835732—MS04-011: Security Update for Microsoft Windows.
•KB893066—MS05-019: Vulnerabilities in TCP/IP Could Allow Remote Code Execution and Denial of Service.
For more information about these hotfixes, see the Microsoft website.
ACS Remote Agent for Windows
ACS Remote Agent for Windows is now supported on Japanese Windows 2000 and Japanese Windows 2003.
SNMP Support and CSA Integration
The following features were introduced in ACS SE 3.3:
•Support for Simple Network Management Protocol (SNMP).
•Integration of Cisco Security Agent in the ACS SE base image.
These features are described in the User Guide for Cisco Secure ACS Solution Engine.
ACS New Features
ACS contains the following new and changed features:
•New RoHS Solution Engine platform. The ACS SE 1113 release consists of a new hardware device that replaces the previous appliance hardware device (the ACS SE 1112 device). The ACS SE 1113 device conforms to Reduction in Hazardous Substances (RoHS) directives of the European Economic Community (EEC)—Directive 73/23/EEC and Directive 89/336/EEC as amended by Directive 93/68/EEC.
•Network Admission Control (NAC) Release 2.0 support—ACS acts as a policy decision point in NAC deployments. Using configurable policies, it evaluates the credentials received from the Cisco Trust Agent, determines the state of the host, and sends a per-user authorization to the network access device: access control lists (ACLs), a policy-based ACL, or a private VLAN assignment. Evaluation of the host credentials can enforce many specific policies, such as OS patch level and antivirus DAT file version. ACS records the policy evaluation results for use with your monitoring system. ACS also allows third-party audit vendors to audit hosts without the appropriate agent technology before granting network access. ACS policies can be extended with external policy servers to which ACS forwards credentials. For example, credentials specific to an antivirus vendor can be forwarded to the vendor's antivirus policy server, and audit policy requests can be forwarded to audit vendors. For more information about the new ACS features to support NAC 2.0, see Support for NAC 2.0.
•Increased number of supported devices—ACS can now support up to 35,000 devices.
•Profile-based authentication and authorization—A new feature called network access profiles allows administrators to classify access requests according to network location, membership in a network device group, protocol type, or other specific RADIUS attribute values sent by the network device through which the user connects. Authentication, access control, posture validation and authorization policies can be mapped to specific profiles. An example of a profile-based policy is the ability to apply a different access policy for wireless access versus remote Virtual Private Network (VPN) access.
•New storage infrastructure—ACS now uses an SQL database to store all the user and configuration information. The new ACS internal database improves scaling and performance, and is less reliant on the Windows Registry. The Windows Registry will be used only for application information. A new database password is required during installation. The password is stored in the Windows registry using Microsoft Crypto API. The database is encrypted by using a hash of customer-provided password and an internal password. You can use the ACS SE CLI to change the password.
•LDAP improvements—ACS caches successful external authentications (by using LDAP), allowing it to immediately look up a user during reauthentication. ACS provides improved SSL support. See LDAP Improvements, for more information.
•Japanese browser support—Supports administration of ACS by using MS Internet Explorer 6.0 SP1 and Netscape Communicator 8.0.4 with Sun Java JRE 1.5.0; or MS Internet Explorer 6.0 SP1 with Microsoft Java Virtual Machine, which is installed on Japanese Windows Operating System (JOS). This feature is supported for entering data in English (not Japanese).
•TACACS+ and RADIUS key support at group level—Ability to set a shared secret at the group level (Network Device Group).
•Purging capability for cached users in ACS—Ability to remove dynamically saved users from the ACS database via User Setup.
–Support for the Microsoft Windows Callback feature.
–Ability for external users to authenticate via an enable password.
–Certificate revocation list checking during EAP-TLS authentication.
•NTLM support—ACS can now operate with Windows NT LAN Manager (NTLM) v1, NTLM v2 (with appropriate Microsoft patches), and LAN Manager (if you require it).
•External Novell NDS database support—Support for group mappings for external Novell NDS databases is now done by using generic LDAP group set mappings.
•Extended replication support—Administrators can now replicate network access profiles and all related configuration, including:
–Posture validation settings
–AAA clients and hosts
–External database configuration
–Global authentication configuration
–Network device groups
–Shared profile components
–Additional logging attributes
•Machine Access Restrictions (MAR) Exemption Lists—You can specify which groups are allowed access to the network; regardless of whether they pass machine authentication. A MAR exemption list can be configured for specific user groups (for example, managers and administrators).
•RADIUS Authorization Component (RAC) support—Includes RADIUS authorization components as a new type of shared profile component. Shared RACs contain groups of RADIUS attributes that you can dynamically assign to user sessions based on a policy.
•Support of additional Cisco hardware devices—ACS 4.0 includes support for Cisco wireless LAN controllers and Cisco adaptive security appliances.
•Online documentation—The online documentation for ACS Solution Engine opens in a separate window, and contains all the information in the User Guide for Cisco Secure ACS Solution Engine. You can search the online documentation by using the Search button, and you can open a PDF version of the user guide.
Support for NAC 2.0
The following features support NAC 2.0:
•EAP-FAST Version 1a support for NAC phase 2—Supports an authenticated tunnel (by using the server certificate) inside of which the provisioning of PACs will occur. EAP types supported inside the tunnel include:
•Agentless host support—Support for Cisco and third-party audit servers that determine posture information about a client, without relying on the presence of a NAC-compliant Posture Agent (PA). These types of clients are also called NAC Agentless Hosts (NAH).
•Linux packages support in posture validation—Supports Linux packages for the Cisco:Host plugin. The following extended attributes are available for Linux packages:
For additional details, see Support for Linux Packages in Posture Validation.
–Support for an external audit server, which determines posture information about a host without relying on the presence of a Posture Agent (PA).
–Posture validation no longer requires NAC databases to verify compliance. The three options from which to choose for validation are:
- internal policies located in ACS
- policies defined on external servers
- policies defined on audit servers for NAC agentless hosts
–Authorization for posture validation is now configured within the Network Access Profiles feature. Posture validation no longer requires special authorization rules.
–This product release includes changes to optimize posture validation. In previous versions, ACS requested all the credentials by using the type-length-value (TLV) protocol. ACS has been optimized to request only the attributes that are required to evaluate posture validation.
The ACS authentication and authorization service, CSAuth, supports multithreading to authenticate with the LDAP external database. Multiple users can simultaneously be searched and authenticated against the LDAP server(s).
LDAP over SSL now includes the option to authenticate by using certificate database files other than the Netscape cert7.db file. This new option uses the same mechanism as other Secure Sockets Layer (SSL) installations in the ACS environment.
When ACS checks authentication and authorization of a user on the LDAP server, it uses a connection with LDAP administrator account permissions to search for the user and for the users groups on the directory subtree. ACS keeps those administrator connections open for successive use. It is possible to limit the maximum number of concurrent administrator connections per generic LDAP external database configuration (primary and secondary).
After an LDAP user is successfully authenticated to the LDAP external database, its distinguished name (DN) on the LDAP server is cached in ACS. The cached DN is used during the next authentication request of the user to save search time.
Support for Linux Packages in Posture Validation
ACS 4.0 supports Linux packages for the Cisco:Host plugin. The following extended attributes are available for Linux packages:
The following Linux packages are supported:
You can add or remove attribute packages in the NAC Attributes Management Page in the ACS SE web interface.
Extended attributes are only supported as descendants of the Cisco:Host application.
Table 1 describes the product documentation for ACS SE 4.0.
Table 1 Product Documentation Details
Document Title and Description Available Formats
Documentation Guide for Cisco Secure ACS Solution Engine
•Printed document with the product.
•PDF on the product CD-ROM.
•Orderable; see Ordering Documentation.
Release Notes for Cisco Secure ACS Solution Engine
New features, documentation updates, known problems, and resolved problems.
Installation and Setup Guide for Cisco Secure ACS Solution Engine
Details on ACS SE 1112 and ACS SE 1113 hardware and hardware installation, and initial software configuration.
•Orderable; see Ordering Documentation.
•PDF on the ACS Recovery CD-ROM.
Product online help.
Help topics for all pages in the ACS HTML interface.
Select an option from the ACS menu; the help appears in the right pane.
User Guide for the Cisco Secure ACS Solution Engine
ACS functionality and procedures for using the ACS features.
•Orderable; see Ordering Documentation.
Supported Devices Table for the Cisco Secure ACS Solution Engine
Supported devices and firmware versions for all ACS features.
Regulatory Compliance and Safety Information for the Cisco Secure ACS Solution Engine
Translated safety warnings and compliance information.
•Orderable; see Ordering Documentation.
•PDF on the ACS Recovery CD-ROM.
Installation Guide for User-Changeable Passwords
Installation and user guide for the user-changeable password add-on.
Installation and Configuration Guide for Cisco Secure ACS Remote Agents
Installation and configuration guide for ACS remote agents for remote logging.
The various databases that ACS supports provide uneven support for the various password protocols that ACS SE supports for authentication.
Note In the User Guide for Cisco Secure ACS Solution Engine 4.0, the tables that summarize database compatibility for the protocols that ACS supports state incorrectly that ACS SE supports ODBC databases. Table 2 and Table 3 correct this error.
Table 2 specifies non-EAP authentication protocol support.
Table 3 specifies EAP authentication protocol support.
This section provides information about installing and upgrading ACS SE and ACS Remote Agents:
Note You should view ACS SE only via a console by using a serial port. We do not recommend using a monitor via the VGA port. If you use a monitor via the VGA port, you will see Windows error messages when starting ACS SE. You can ignore these messages and there is no need to reboot.
Installing from the ACS SE 1111 (HP) Recovery CD
When installing from the Recovery CD for ACS SE 1111 (HP), you might encounter the following issues:
•After installation completes, the ACS SE reboots, performs some configurations, and reboots again. The configurations that occur after the first reboot take a significant amount of time, during which there is no feedback, which is normal system behavior. If, after about an hour, the CLI Initial Configuration screen does not appear, switch off the appliance, and switch it on again. Refer to CSCsc90467.
•After initial configuration ends, if you cannot access the web interface, use the CLI command, reboot, to restart the appliance. Refer to CSCsd20149.
Note These problems occur only on ACS SE 1111 (HP), after installing from the Recovery CD, when performing a full upgrade, including the appliance base image. If you are not upgrading the appliance base image, you do not need to install from the Recovery CD.
See the Supported and Interoperable Devices and Software Tables for Cisco Secure ACS Solution Engine on Cisco.com.
Upgrading and Migrating to ACS SE 4.0
You can upgrade your existing ACS SE appliance with the latest ACS software, appliance management software, and appliance base image. For detailed instructions see Installation Guide for Cisco Secure ACS Solution Engine on Cisco.com.
You can migrate from an existing ACS SE appliance (ACS SE 1111 or 1112) to the ACS SE 1113 by making a backup of the installation on the existing hardware device (SE 1111 or 1112) and then performing a restore of the installation on the new hardware device (SE 1113).
Note ACS Release 3.x is not supported on the SE 1113 platform.
If the existing ACS SE appliance has a previous software version, you must first upgrade the existing appliance to software version 4.0.
For detailed information, see Chapter 5 of the Installation and Setup Guide for the Cisco Secure ACS Solution Engine, "Upgrading and Migrating to Cisco Secure ACS Solution Engine."
ACS supports the following upgrade paths. These paths have been tested and are supported:
•ACS SE release 3.3.3 to ACS SE release 4.0.
•ACS SE, release 3.3.2 to ACS SE 4.0.
•ACS SE, release 3.3.1 to ACS SE 4.0.
•ACS SE, release 3.2.3 to ACS SE 4.0.
•ACS SE versions before ACS SE 3.2.3, first upgrade to ACS SE 3.3.3, then to ACS SE 4.0. For information about upgrading to ACS SE 3.3.3, see Release Notes for Cisco Secure ACS Solution Engine 3.3.3 on Cisco.com.
ACS supports the migration path from ACS for Windows 4.0 to ACS SE 4.0. Before performing migration, you must first upgrade ACS for Windows to version 4.0.
The following migration paths have been tested and are supported:
•Upgrade ACS for Windows, release 3.0.4, via 3.3.3, to ACS for Windows, release 4.0. Migrate to ACS SE 4.0.
•Upgrade ACS for Windows, release 3.2.3, to ACS for Windows, release 4.0. Migrate to ACS SE 4.0.
•Upgrade ACS for Windows, release 3.3.1, to ACS for Windows, release 4.0. Migrate to ACS SE 4.0.
•Upgrade ACS for Windows, release 3.3.2, to ACS for Windows, release 4.0. Migrate to ACS SE 4.0.
•Upgrade ACS for Windows, release 3.3.3, to ACS for Windows, release 4.0. Migrate to ACS SE 4.0.
For ACS SE versions before ACS SE 3.2.3, first upgrade to ACS SE 3.3.3, then to ACS SE 4.0. For information about upgrading to ACS SE 3.3.3, see Release Notes for Cisco Secure ACS Solution Engine 3.3.3 on Cisco.com.
After upgrading to ACS 4.0, you may need to perform additional configuration steps to successfully use ACS and Network Access Profiles (NAP). If you used NAC in ACS 3.3, ACS will not operate in an identical manner in ACS 4.0. For example, you must create a new set of authorization rules for Network Access Profiles that are created during the upgrade process.
Upgrading From Version 3.3
The following actions are performed automatically when you upgrade from ACS 3.3 to ACS 4.0:
1. Local and external posture policies are automatically transformed.
2. A single NAP, (configured for NAC only) is created as a process of the upgrade.
3. Each instance of the selected ACS 3.3 Network Posture Validation Database will automatically be transformed into a posture validation rule. All the rules will be associated with the NAP that was created (in step 2). All PA message and URL redirects are mapped correspondingly.
4. A RADIUS Authorization Component will be created for each mapped group. ACS populates the RAC with all attributes that were configured in the user or group setup menus, except for the posture-token Cisco-av-pair. Since ACS dynamically updates the posture-token Cisco-av-pair attribute at runtime, there is not need to configure it manually.
5. If you manually added posture validation attributes in ACS 3.3, they will be added to the ACS version 4.0 posture dictionary during the upgrade.
Tested Windows Security Patches for ACS Remote Agent
Cisco Systems officially supports and encourages the installation of all Microsoft security patches for Windows 2000 Server and Windows Server 2003 as used for ACS Remote Agent for Windows.
Cisco experience has shown that these patches do not cause any problems with the operation of ACS Remote Agent for Windows. If the installation of one of these security patches does cause a problem with ACS, please contact Cisco Technical Assistance Center (TAC) and Cisco will resolve the problem as quickly as possible.
ACS Remote Agent for Windows has been tested with the Windows Server 2003 patches documented in the following Microsoft Knowledge Base Articles:
ACS has been tested with the Windows 2000 Server patches documented in the following Microsoft Knowledge Base Articles:
This section corrects errors and omissions in the ACS user documentation:
In the User Guide for Cisco Secure ACS Solution Engine 4.0, the tables that summarize database compatibility for the protocols that ACS supports state incorrectly that ACS SE supports ODBC databases. Table 2 and Table 3 in Supported Databases correct this error.
Replication with Different Send and Receive Configurations
The user guide states that the primary ACS compares the list of database components that it is configured to send with the list of database components that the secondary ACS is configured to receive. If the secondary ACS is not configured to receive any of the components that the primary ACS is configured to send, the database replication fails.
The previous information is incorrect (bug CSCsg93907).
The primary ACS first synchronizes with the secondary ACS, and sends only the components that the secondary ACS is configured to receive. The primary ACS does not send components that the secondary ACS is not configured to receive, even if you configure the primary ACS to send those components. Thus, database replication does not fail when different send and receive configurations exist on the primary and secondary ACS.
Submit and Apply Button Changed to Apply Button
In several parts of the User Guide for Cisco Secure ACS Solution Engine 4.0, the documentation instructs the reader to click Submit + Apply to save and apply configuration changes. In release 4.0, the Apply button replaces the Submit + Apply button.
Click the Apply button to save and apply configuration changes.
Cisco issues a security advisory when security issues directly impact its products and require action to repair. For the list of security advisories for Cisco Secure on Cisco.com, see the Cisco Security Advisory: Multiple Vulnerabilities in Cisco Secure Access Control Server at:
The following problems exist in this release:
Cisco AAA Client Problems
Refer to the appropriate release notes for information about Cisco AAA client problems that might affect the operation of ACS. You can access these release notes online at Cisco.com. For NAC-specific client problems, go to http://www.cisco.com/en/US/netsol/ns466/networking_solutions_package.html.
Known Microsoft Problems
Due to a defect in the Microsoft PEAP supplicant provided in the Windows XP Service Pack 2, the PEAP supplicant cannot reauthenticate successfully with ACS. Cisco has opened case SRX040922603052 with Microsoft on this issue. Customers who are affected by this problem should open a case with Microsoft and reference this case ID. Microsoft has prepared hotfix KB885453, which resolves the issue.
Known Problems with ACS 4.0
Table 4 contains problems known to exist in ACS SE 4.0.
Table 5 contains the problems from the ACS 4.0 release that are resolved. Check the Bug Navigator on Cisco.com for any resolved bugs that may not appear here.
Table 5 Resolved Problems in ACS 4.0
Bug ID Summary Explanation
UCP 4.0 on Windows 2000 or Windows 2003 may cause a Common Gateway Interface (CGI) error.
The problem with the ACS User Changeable Password feature that operates as a CGI in IIS, under Windows 2000 SP4 (IIS 5.0) or Windows 2003 SP1 (IIS 6.0) has been fixed. Use the latest version of UCP, downloadable from CCO at:
NAF is selected automatically after deleting and creating with the same name.
This problem has been solved.
VoIP messages cause the CSRadius service to unexpectedly terminate.
CSRadius no longer terminates unexpectedly.
ACS 18.104.22.168 on the HP 1111 platform fails to get NIC configuration.
This problem has been fixed in the most recent version of ACS.
Replication timeout causes CSAuth restart without any error in ACS reports
Replication on Windows 2003 works without CSAuth problems, and logs are correct.
Restoring from software removes the appliance entry inside the proxy.
The default proxy entry for the appliance is no longer removed from the proxy table when restoring the database from the software version to an appliance.
Network Access Filter (NAF) reedit requests restart.
After editing NAF data, ACS web interface now displays a message after you click Submit and Restart to restart the services.
Errors occurs while installing ACS on a directory with special characters.
The percent sign (%) that caused the problem with ACS installing correctly is fixed in ACS 4.0.
ACS chooses wrong NDG for network access restriction (NAR) with TACACS+ or RADIUS NAS on same IP.
ACS no longer chooses the wrong NDG for NAR matching if a TACACS+ and RADIUS NAS are defined with the same IP and placed in separate NDGs, and the authentication is performed via RADIUS.
CSLog fails if a logged attribute is deleted due to replication.
The CSLog service works as expected after replication.
Days-since-last-update operator should compare to GMT.
ACS displays date and time correctly in logs and reports.
A change in the NAF is not valid until the services are restarted.
Changes in the NAF configuration take affect without restarting ACS services.
NAC attribute type change can cause NAC GUI error.
NAC errors no longer occur after an administrator changes the type of an existing NAC attribute by using CSUtil (or because of backup and restore).
Navigation bar (buttons) disappears after exiting from the Global Authentication Setup page.
The navigation bar (button bar on the left) in the ACS web interface appears successfully after exiting from the Global Authentication page.
SPC type created by EMBU DLL returns errors in Name field.
Name field limitation of 31 characters defined. Error messages no longer appear.
CSAdmin restart during replication between two ACS SW in slow link.
Replication between two ACSs in a slow link (128 KB) works successfully.
Fail to locate ACL for updating when ACL uses the same name as NAF.
NAFs with the same name no longer cause problems.
Renaming an NDG removes it from the Selected Items of NAF HTML page.
A pop-up window has been added to confirm deletion.
Action Code 211 does not return group settings to factory defaults.
Action Code 211 now works as documented in the User Guide for Cisco Secure ACS Solution Engine 4.0.
Active Directory via LDAP - Group Mappings skip first group.
Database group mappings are now correct.
Unable to edit some of the disabled accounts.
All Disabled Accounts report errors are fixed.
Authentications on a secondary ACS may fail after replication.
In environments where primary and secondary ACS servers are synchronized by using the replication feature, user authentications no longer fail for users who are defined in an external database and the Failed Attempts log no longer contains an External DB not configured error.
Multiple administrators need to be able to add, edit, and delete downloadable ACLs.
No conflicts exist when multiple administrators try to add, edit, and delete downloadable ACLs under the shared profile components.
ACS shared profile components disappear with XML error messages.
Shared profile component errors no longer occur during upgrades from ACS 3.2.3 to ACS 4.0.
ACS does not authenticate Windows 2000 users when NTLMv2 is enabled on the network.
ACS now supports NTLMv2.
Cascade replication due to user password changes do not work.
Cascade replication with password changes replicates successfully.
CSAgent (Solaris)—The appliance indicates that the RA is running when it is not running.
The appliance no longer shows the Remote Agent as running when it is not.
Dbcompact has been removed from the console commands available in ACS SE 4.0 code.
This command was deliberately removed due to the different database structure.
The ACS documentation is not clear about how to power on the ACS 1112.
The power switch is on the power LED.
The documentation describes only three states for the LED, even though another state exists. The green blinking LED state indicates that the unit is plugged in and power is available, but power is off.
Press the power LED to turn on the ACS 1112 or 1113.
The documentation on the front panel LEDs and components has been updated to correct this error. See the Installation and Setup Guide for the Cisco Secure ACS Solution Engine:
Updates for Online Help Documentation
The following errors exist in the ACS online help:
•The ACS documentation indicates that you can disable the dynamic user cache, which is incorrect.
•Support files are not matched to the number of selected days in the basic system configuration section. If you want the support information to be downloaded to include service log files that are older than the current log files, check the Collect Previous X Days logs check box and type the number of days of log files to be included. The "Current Log File" may not be today's date, rather it may be several days older than today's date.
•The online documentation for the ACS SE 1113 states that the description field for a downloadable IP ACL can contain up to 30,000 characters; however, the description can contain only 1006 characters.
•The online help for the Solution Engine states that clicking the Shutdown button powers down the appliance. Clicking the Shutdown button causes a message to appear, indicating that it is safe to power down the appliance. To power down the appliance, press the Power button on the front panel.
Omissions and errors in the ACS documentation include:
•The ACS documentation erroneously indicates that the ODBC database is supported for EAP and Non-EAP Authentication Protocol-Database Compatibility.
•We do not support distributed ACS deployments in a NAT environment. If a primary or secondary address is in NAT format, the database replication file will indicate a shared secret mismatch. The next release of the documentation will address this omission.
•LEAP is not supported when working with Network Access Profiles. You can use LEAP only if your system is operating in legacy ACS mode.
•IP-based NAR filters work only if ACS receives the Radius Calling-Station-Id (31) attribute. The Calling-Station-Id (31) must contain a valid IP address. If it does not, it will fall over to DNIS rules. This requirement was not specified in the documentation. See bug CSCsc72958.
•When creating a package.cab file that is larger than 2GB, additional .cab files are created due to the size limit of the packer. The sequence is: the first package name is package.cab; the second is package1.cab, and so on, until the N package, packageN.cab, where N is the number of packages minus one. The files are saved in the same location that is specified before the packing begins. These files are not standalone and all of them must be sent to package. Problems with the packed file (package.cab) may arise if there is not enough hard-disk space.
•Replication of the appliance configuration is not mentioned in the short help or in the User Guide for the Cisco Secure ACS Solution Engine.
•When you generate a certificate signing request or a self-signed certificate, you should enter only a file name for the private key file and certificate file, not the full directory path.
•The ACS Solution Engine automatically creates an entry called Self in the AAA Servers Table. This entry identifies the Solution Engine machine. However, in the Proxy Distribution Table and the AAA Server Table for RDMS synchronization, the ACS Solution Engine creates an entry for the hostname of the device that is running the ACS Solution Engine.
•In the System Configuration > Support page, the Collect Previous X Days logs check box applies to the number of days previous to the current service log files, which m.
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation at this URL:
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
Product Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at firstname.lastname@example.org or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to email@example.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
From this site, you can perform these tasks:
•Report security vulnerabilities in Cisco products.
•Obtain assistance with security incidents that involve Cisco products.
•Register to receive security information from Cisco.
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•Emergencies — firstname.lastname@example.org
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•Nonemergencies — email@example.com
In an emergency, you can also reach PSIRT by telephone:
•1 877 228-7302
•1 408 525-6532
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete list of Cisco TAC contacts, go to this URL:
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
•Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:
•Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:
•World-class networking training is available from Cisco. You can view current offerings at this URL:
This document is to be used in conjunction with the documents listed in the Documentation Guide for Cisco Secure ACS Solution Engine document.