 Feedback
|
Table Of Contents
Release Notes for the Cisco Secure Access Control System 5.2
Installation and Upgrade Notes
Installing, Setting up and Configuring CSACS 1121
Auto-Installation of Evaluation License
Upgrading an ACS Server from 5.0 to 5.2
Resolved Issues in Cumulative Patch ACS 5.2.0.26.1
Resolved Issues in Cumulative Patch ACS 5.2.0.26.2
Resolved Issues in Cumulative Patch ACS 5.2.0.26.3
Resolved Issues in Cumulative Patch ACS 5.2.0.26.4
Resolved Issues in Cumulative Patch ACS 5.2.0.26.5
Resolved Issues in Cumulative Patch ACS 5.2.0.26.6
Resolved Issues in Cumulative Patch ACS 5.2.0.26.7
Resolved Issues in Cumulative Patch ACS 5.2.0.26.8
Resolved Issues in Cumulative Patch ACS 5.2.0.26.9
Resolved Issues in Cumulative Patch ACS 5.2.0.26.10
Resolved Issues in Cumulative Patch ACS 5.2.0.26.11
Supplemental License Agreement
Obtaining Documentation and Submitting a Service Request
Release Notes for the Cisco Secure Access Control System 5.2
Revised: November 19, 2012 OL-21576-01These release notes pertain to the Cisco Secure Access Control System (ACS), release 5.2, hereafter referred to as ACS 5.2. These release notes provide information on the features, related documentation, resolved issues, and known issues for functionality in this release.
This document contains:
•
Installation and Upgrade Notes
•
•
•
•
•
•
•
•
•
•
•
•
•
Introduction
ACS is a policy-driven access control system and an integration point for network access control and identity management.
The ACS 5.2 software runs either on a dedicated Cisco 1121 Secure Access Control System (CSACS-1121) appliance, or on a VMware server. However, ACS 5.2 continues to support CSACS-1120 appliances that you have used for ACS 5.0 and that you would like to upgrade to ACS 5.2.
This release of ACS provides new and enhanced functionality on a standard Cisco Linux-based appliance.
Throughout this documentation, CSACS-1121 refers to the appliance hardware, and ACS Server refers to the ACS software.
New and Changed Features
This release of ACS provides improved parity with 4.x. The following sections briefly describe the new and changed features in the 5.2 release:
Cryptographic Module
The cryptographic module enhancements include:
•
•
•
Support RADIUS KeyWrap
The RADIUS KeyWrap feature enhancements include:
•
–
–
In ASCII mode, enter a key length with 20 characters. In hexadecimal mode, enter a key with 40 characters.
•
The RADIUS KeyWrap feature in ACS 5.2 introduces the following three new AVPs for the Cisco AV-pair RADIUS Vendor-Specific-Attribute:
–
–
–
When RADIUS KeyWrap is enabled, ACS 5.2 allows the use of these three RADIUS KeyWrap AVPs for message exchanges and key delivery. According to the KeyWrap attribute requirements, ACS will reject all RADIUS requests that contain both RADIUS KeyWrap AVPs and the standard RADIUS Message Authenticator attribute [RFC2869].
•
•
Machine Key Zeroization
ACS 5.2 introduces a new CLI command acs zeroize-machine to trigger the zeroization. Zeroization deletes any key and sensitive files. It also deletes the running memory and the swap files.
This command securely deletes the partition on which ACS is installed. It also securely deletes the swap partition and restarts the machine to clear all information in the RAM. After the command has completed running, ACS will not function on the appliance. You have to re-install ACS on the appliance.
For more information on this command, see the CLI Reference Guide for the Cisco Secure Access Control System 5.2.
SHA-2
ACS 5.2 supports SHA-2 signatures as follows:
•
•
•
•
Only SHA2 256-bit certificate digest algorithm is supported by ACS 5.2.
CoA Port
ACS 5.2 allows you to configure Change of Authorization (CoA) port through the GUI. It is used to set up the RAIUS CoA port for session directory, for user authentication. You can launch this session directory from the Monitoring and Troubleshooting Viewer page. By default, the CoA port value is filled as 1700.
SFTP Copy
In ACS 5.2, SSH File Transfer Protocol (SFTP) is implemented by Secure Copy Protocol (SCP).
Features Not Supported
The following features are not supported in ACS 5.2:
•
•
•
•
•
Known Limitations in ACS 5.2
The following are the affected areas in ACS 5.2 as a result of FIPS certification:
SSH client
The SSH client should support the following FIPS compliant cipher suits:
•
•
•
Note
Browsers
ACS 5.2 supports the following Web Client/Browser Platforms in Windows XP Professional (Service Pack 2 and 3) and Windows Vista.
•
•
•
•
The above mentioned browsers are supported only with one of the following cipher suits:
•
•
•
You should install Windows XP SP3 to use SHA2 256-bit certificates as management certificates.
Logs
ADE logs added the following repetitive log message because of FIPS requirements:
Crypto::notifyStateTransitionInstallation and Upgrade Notes
This section provides information on the installation tasks and configuration process for ACS 5.2. This section contains:
•
•
Installing, Setting up and Configuring CSACS 1121
This section describes how to install, set up and configure the CSACS 1121 Series appliance. The CSACS 1121 Series appliance is preinstalled with the software.
To set up and configure the CSACS 1121:
Step 1
•
•
•
•
•
•
Step 2
For more details, see Installation and Upgrade Guide for the Cisco Secure Access Control System 5.2.
Step 3
For more details, see Installation and Upgrade Guide for the Cisco Secure Access Control System 5.2 and pay special attention to all the safety warnings.
Step 4
For more details on installing the CSACS 1121 Series appliance, see Installation and Upgrade Guide for the Cisco Secure Access Control System 5.2.
Step 5
Figure 1 shows the back panel of the CSACS 1121 Series appliance and the various cable connectors.
Note
For more details, see Installation and Upgrade Guide for the Cisco Secure Access Control System 5.2.
For information on installing ACS 5.2 on VMware, see Installing ACS in a VMware Virtual Machine chapter in the Installation and Upgrade Guide for the Cisco Secure Access Control System 5.2.
Figure 1 CSACS 1121 Series Appliance Rear View
The following table describes the callouts in Figure 1.
.
1
AC power receptacle
5
(Blocked) Gigabit Ethernet 1
2
(Blocked) Gigabit Ethernet
6
(In Use) Gigabit Ethernet 0
3
Serial connector
7
USB 3 connector
4
Video connector
8
USB 4 connector
Step 6
The first time you power up the appliance, you must run the setup program to configure the appliance. For more information, see Running the Setup Program.
Running the Setup Program
This section describes the setup process that configures the ACS Server.
The setup program launches an interactive CLI that prompts you for the required parameters. An administrator can use the console or a dumb terminal to configure the initial network settings and enter the initial administrator credentials for the ACS 5.2 server that is using the setup program. The setup process is a one-time configuration task.
To configure the ACS Server:
Step 1
The setup prompt appears:
Please type `setup' to configure the appliancelocalhost login:Step 2
The console displays a set of parameters. You must enter the parameters as described in Table 1.
Note
After you enter the parameters, the console displays:
localhost login: setupEnter hostname[]: acs-server-1Enter IP address[]: 209.165.200.225Enter IP default netmask[]: 255.255.255.0Enter IP default gateway[]: 209.165.200.1Enter default DNS domain[]: mycompany.comEnter Primary nameserver[]: 209.165.200.254Add/Edit another nameserver? Y/N : nEnter username [admin]: adminEnter password:Enter password again:Pinging the gateway...Pinging the primary nameserver...Do not use `Ctrl-C' from this point on...Appliance is configuredInstalling applications...Installing acs...Generating configuration...Rebooting...After the ACS server is installed, the system reboots automatically. Now, you can log in to ACS with the CLI username and password that was configured during the setup process.
You can use this username and password to log into ACS using only the CLI. To log into the GUI, you must use the predefined username ACSAdmin and password default.
When you access the GUI for the first time, you will be prompted to change the predefined password for the administrator. You can also define access privileges for other administrators who will access the GUI application.
Licensing in ACS 5.2
To operate ACS, you must install a valid license. ACS prompts you to install a valid license when you first access the web interface.
Each ACS instance (primary or secondary) in a distributed deployment requires a unique base license.
This section contains:
•
Types of Licenses
Table 2 lists the types of licenses available in ACS 5.2.
Auto-Installation of Evaluation License
If you are using a virtual machine (VM) for ACS with disk space between 60 GB and 512 GB, ACS automatically installs the evaluation license. However, you can also get the evaluation license and install it manually on the ACS server.
If you use an ACS server with less than 500 GB hard disk space, Cisco does not provide support for scalability, performance, and disk space-related issues.
For more information on installing ACS 5.2 on VMware, see Installing ACS in a VMware Virtual Machine chapter in the Installation and Upgrade Guide for the Cisco Secure Access Control System 5.2.
Upgrading an ACS Server from 5.0 to 5.2
To upgrade your ACS 5.0 server to ACS 5.2:
Step 1
backup backup-name repository repository-name
Note
Step 2
Step 3
Step 4
restore filename repository repository-name
ACS upgrades the 5.0 configuration data and Monitoring and Report Viewer data to the 5.1 format.
Step 5
backup backup-name repository repository-name
Note
Step 6
Step 7
Step 8
restore filename repository repository-name
ACS upgrades the 5.1 configuration data and Monitoring and Report Viewer data to the 5.2 format.
Applying Upgrade Patches
You can download ACS 5.2 cumulative patches from the following location: http://www.cisco.com/cisco/web/download/index.html
To download and apply the patches:
Step 1
Step 2
Step 3
Enter the following acs patch command in the EXEC mode to install the ACS patch:
acs patch install patch-name.tar.gpg repository repository-name
ACS displays the following confirmation message:
Installing an ACS patch requires a restart of ACS services.Would you like to continue? yes/noStep 4
Resolved ACS Issues
Table 3 lists the issues that are resolved in ACS 5.2.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.1
Table 4 lists the issues that are resolved in the ACS 5.2.0.26.1 cumulative patch.
You can download the ACS 5.2.0.26.1 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.2
Table 5 lists the issues that are resolved in the ACS 5.2.0.26.2 cumulative patch.
You can download the ACS 5.2.0.26.2 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.3
Table 6 lists the issues that are resolved in the ACS 5.2.0.26.3 cumulative patch.
You can download the ACS 5.2.0.26.3 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.4
Table 7 lists the issues that are resolved in the ACS 5.2.0.26.4 cumulative patch.
You can download the ACS 5.2.0.26.4 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.5
Table 8 lists the issues that are resolved in the ACS 5.2.0.26.5 cumulative patch.
You can download the ACS 5.2.0.26.5 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.6
Table 9 lists the issues that are resolved in the ACS 5.2.0.26.6 cumulative patch.
You can download the ACS 5.2.0.26.6 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.7
Table 10 lists the issues that are resolved in the ACS 5.2.0.26.7 cumulative patch.
You can download the ACS 5.2.0.26.7 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.8
Table 11 lists the issues that are resolved in the ACS 5.2.0.26.8 cumulative patch.
You can download the ACS 5.2.0.26.8 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.9
Table 12 lists the issues that are resolved in the ACS 5.2.0.26.9 cumulative patch.
You can download the ACS 5.2.0.26.9 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.10
Table 13 lists the issues that are resolved in the ACS 5.2.0.26.10 cumulative patch.
You can download the ACS 5.2.0.26.10 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Resolved Issues in Cumulative Patch ACS 5.2.0.26.11
Table 14 lists the issues that are resolved in the ACS 5.2.0.26.11 cumulative patch.
You can download the ACS 5.2.0.26.11 cumulative patch from the following location:
http://www.cisco.com/public/sw-center/index.shtml
Refer to "Applying Upgrade Patches" section for instructions on how to apply the patch to your system.
Table 14 Resolved Issues in Cumulative Patch ACS 5.2.0.26.11
CSCuc65634
Password vulnerability occurs in ACS 5 while using external LDAP store and TACACS+ protocol.
Known ACS Issues
This section lists the known issues for the ACS 5.2 release.
Table 15 lists the known issues in ACS 5.2. You can also use the Bug Toolkit on Cisco.com to find any open bugs that do not appear here.
Table 15 Known Issues in ACS 5.2
CSCtf00575
Error occurs if you select a Boolean type, Migrated User attribute.
Symptom: An error appears if you choose the Migrated User attribute with Boolean type.
Condition: This problem occurs if you select any Migrated User attributes with Boolean type.
Workaround: None.
CSCtf11100
Null pointer exception while migrating NDG
Symptom: A Nullpointer exception occurs while migrating NDG, if there are any invalid characters in keywrap.
Condition: This problem occurs if invalid characters are used in ACS 4.x NDG and migrated. A Nullpointer exception appears.
Workaround: None.
CSCtf25265
Invalid user password ranges are not reported while migrating and the migration fails.
Symptom: Invalid user password range is not reported while migration.
Condition: This problem occurs if you migrate a user with more that 32 characters and authenticate with that user. The migration will fail.
Workaround: None.
CSCtg62673
Cannot load a feature license with ampersand (&) in the company name.
Symptom: You cannot load a feature license if it has an ampersand (&) in the name. An error message does not appear for this problem.
Conditions: This problem occurs on ACS 5.0 and ACS 5.1 if the company name in the license contains an ampersand (&) character.
Workaround: Re-issue the license without an ampersand (&) in the company name.
CSCtg49699
ACS 5 fails to join AD Domain.
Symptom: If ACS was configured with an AD domain, it will fail to rejoin the domain if there are any changes in the AD infrastructure, such as IP addresses of the AD servers.
Conditions: This problem occurs if you move the ACS from one domain to another domain without clearing the AD configuration page.
It also occurs when ACS is joined with a DC in the lab and then it is moved to the production environment on the same domain. ACS will not rejoin the live DC.
Workaround:
1.
2.
3.
Make sure you still have the ACS license before doing that because after the reset, ACS will prompt you for the license.
CSCth08274
ACS 5: View does not load next page in IE if the username contains a "\u" character.
Symptom: While viewing a report an error is displayed in Internet Explorer and the navigation buttons for the report get disabled.
Conditions: The error Expected Hexadecimal Digit is displayed for users with a "\u" in the username or domain name. This happens because"\u" is a unicode escape character.
Workaround: This problem occurs only on Internet Explorer. Try using other browser like FireFox.
CSCth26298
Machine accounts with many ACE entries cause AD domain join to fail.
Symptom: ACS 5.1 cannot join a Windows AD domain.
Conditions: This problem occurs when the machine account used by ACS to join the domain contains a large number of Access Control Entries (ACE).
Workaround:
1.
2.
3.
4.
5.
This symptom only affects the Join operation.
CSCth31525
Live authentication report does not show TACACS+ data.
Symptom: The TACACS+ live authentication report is missing data on some columns, including NAS and IP address.
Conditions: This problem occurs only on ACS 5.1.
Workaround: Use one of the other available reports to view this data.
CSCte57427
ACS 5.1 - SNMP location and contact information is not saved when you reboot the system.
Symptom: The following commands in ACS 5.1 may disappear from the config after you reboot the system:
Please type `setup' to configure the appliance
localhost login:Conditions: This problem occurs in ACS 5.1 if you use spaces in the contact or location string.
For example:
localhost login: setupWorkaround: Remove any blank spaces from the configured string.
For example:
Enter hostname[]: acs-server-1CSCte98032
ACS 5 partitions are not properly aligned when installed on VMWare.
Symptom: VMWare tools report that ACS 5 partitions are not properly aligned.
Conditions: This problem occurs when you install ACS 5 on VMWare ESX 4.0.
Workaround: None.
CSCtf09891
Remote log targets does not accept classless IP format.
Symptom: You cannot set Remote Log Target using IP address 131.123.246.255 on ACS 5.1 appliance. The following error appears:
Enter IP address[]: 209.165.200.225Conditions: This problem occurs if a classless IP address is configured.
Workaround: Use classfull IP address.
CSCtf78048
[AD PERF] Discovery of host's account domain is very inefficient.
Symptom: Slow host authentications against Active Directory with host name format host/machine.domain.com.
Conditions: This problem occurs if ACS is configured to perform authentications against Active Directory and to fetch groups from Active Directory.
Workaround: Use domain machine$ host name format.
CSCtc61926
Active directory NetBIOS authentication passes when user is defined as UPN.
Symptom: User authentication passed with illegal username format.
Conditions: This problem occurs if the UPN name and the NetBIOS username are different. For example, NetBIOS username = somename and UPN = Some Name.
Workaround: Do not use the UPN form of username.
CSCtc70071
MSCHAP v2 & PEAP NetBIOS authentication fails if there are special characters in the username.
Symptom: MSCHAP v2 user authentication fails if the SAM name or NetBIOS name contains '@'.
Conditions: This problem occurs if you create a user in Active Directory and the SAM name contains '@' sign (with ADSI edit)
Workaround: Do not use '@' sign on SAM names or authenticate using the UPN name.
CSCtc36013
ESX secondaries cannot handle transactions gap during large users import.
Symptom: Secondary appliances are not updated even after the import process has completed on the primary appliances.
Conditions: Some secondary appliances are defined on VMWare ESX and the primary appliance is defined on ACS 5.1. The import is done from the primary appliance. In this case 300,000 users are imported into the primary node through the import/export utility.
Workaround: Do one of the following:
•
•
CSCtf52072
MAB inconsistent username formats for access-request and access-accept.
Symptom: When authenticating a supplicant using MAC Authentication Bypass (MAB) the Authenticator and the Authentication Server (ACS), use different formats for the username within the RADIUS Access-Request and Access-Accept messages.
Conditions: This problem occurs under the following conditions:
•
•
•
This anomaly should not have any negative impact while authenticating using MAB.
Workaround: None.
CSCte93628
An error message %AAA-3-DROPACCTFAIL: appears when you boot up a Switch.
Symptom: System accounting record is rejected by ACS with the following message on box:
Enter IP default netmask[]: 255.255.255.0
Enter IP default gateway[]: 209.165.200.1
Enter default DNS domain[]: mycompany.comConditions: This problem occurs during system accounting start after reload of the device.
Workaround: None.
CSCtf71065
If you set the debug-log to debug level, it enables debug-adclient even for unauthorized administrators.
Symptom: Unauthorized administrators can enable the debug-adclient log in CLI.
Conditions: This problem occurs if you change the debug-log command.
Workaround: None.
CSCtc34967
An incorrect message appears when ACS is configured with PEAP-GTC and the supplicant is configured with PEAP-MSCHAP.
Symptom: Authentication fails and shows an incorrect error message.
Conditions: This problem occurs when supplicant is configured as PEAP-GTP and ACS is configured to accept PEAP-MSCHAP only. Authentication fails and the following message is displayed:
Enter Primary nameserver[]: 209.165.200.254Workaround: None
CSCtc70023
Identity groups - display names are truncated after upgrade.
Symptom: If a database with 500 Identity groups is migrated from ACS 4.x and then upgraded from ACS 5.0 to 5.1, the names of the groups are truncated.
Conditions: This problem occurs only in Internet Explorer 6.0
Workaround: Use another browser such as Firefox 3.
CSCtc78550
During RADIUS authentication against AD, some messages are duplicated on the customer log.
Symptom: While running RADIUS authentication with AD as database, some messages' text is duplicated on customer log.
Conditions: Authorization message ID duplicated:
Add/Edit another nameserver? Y/N : n
Enter username [admin]: adminWorkaround: None.
CSCtg70874
Connection times out while creating server certificates.
Symptom: An error message appears while creating server certificates.
Conditions: This problem occurs if you try to create a large certificate.
Workaround: Reduce the size of the certificate.
CSCtc83623
All groups are not shown in Directory Group in LDAP.
Symptom: The LDAP group selection page shows only a maximum of 100 groups.
Conditions: This problem occurs when you search for a group and there are more than 100 groups.
Workaround: Use search criteria to filter groups.
CSCtd53402
Policy Element RADIUS attribute editing does not work.
Symptom: Attribute value does not get saved correctly when creating a RADIUS attribute.
Conditions: This problem occurs when you:
1.
2.
3.
4.
5.
6.
Three new entries are displayed.
7.
The fifth entry is wrong. The value is Decnet IV instead of 802.
Workaround: Create new profile, do not use duplicate.
CSCtg65300
User command set in users with apostrophe (') is not migrated successfully.
Symptom: ACS 4.x command sets on the user level are not migrated.
Conditions: This problem occurs when the username includes an apostrophe (').
Workaround: Manually migrate the user command set.
CSCtf19736
Not able to register to primary server with Host name.
Symptom: Cannot register to primary server.
Conditions: This problem occurs when you use the primary server host name.
Workaround: Use the primary server IP address.
CSCtd53435
Error occurs while editing a RADIUS Attribute.
Symptom: While editing a RADIUS attribute, the GUI displays the following error:
Enter password:Conditions: This problem occurs when you:
1.
2.
3.
4.
5.
Workaround: Reselect the option in the left navigation bar.
If you continue to receive the unexpected error message, close your browser and log in to ACS again.
If you still receive the unexpected error message, contact your system administrator or technical assistance.
CSCtf22214
Invalid characters appear in the migration tool and an error message is not displayed in the CLI if you enter an invalid value.
Symptom: No error message appears if you enter a wrong value for the CLI command acs config-web-interface migration.
For example,
Enter password again:It will not show that the interface is not enabled.
Conditions: This problem occurs if you use the CLI command acs config-web-interface migration, and enter a value other than [enable | disable].
Workaround: None.
CSCtg87278
ACS not able to establish SSL tunnel with LDAP server with CRL verification.
Symptom: When you use Secure LDAP and uncheck the Bypass CRL Verification if CRL is not Received check box, the authentications fail. This is because CS is not able to establish SSL tunnel.
The following errors appear:
Pinging the gateway...
Pinging the primary nameserver...
Do not use `Ctrl-C' from this point on...This happens even if all CA certificates are installed on ACS and the CRL URLs are properly configured.
Conditions: This problem occurs if you use Secure LDAP and uncheck Bypass CRL Verification if CRL is not Received.
Workaround: Select the check box Bypass CRL Verification if CRL is not Received.
CSCtc90865
Errors during PEAPv0 stress.
Symptom: When primary instance is set with Monitoring & Reports Viewer, there are no secondaries attached to it. After installation, restore a large database. The following two issues are shown during stress.
•
•
Appliance is configured
Installing applications...Conditions: This problem occurs during PEAPv0 stress.
Workaround: Use two or more ACS instances.
CSCtf77292
Evaluation of domain local groups causes authentication delays.
Symptom: Slow authentications against Active Directory.
Conditions: This problem occurs if ACS is configured to perform authentications against Active Directory and to fetch groups from Active Directory.
Workaround: None.
CSCtd54069
The ACS UI does not allow you to edit the authorization rule in case of LDAP/AD.
Symptom: The Select button is grayed out if you select AD1 from the dictionary on the Authorization Rule page.
Conditions: This problem occurs when you:
1.
2.
3.
4.
Workaround: Create new authorization rule instead of editing an existing one.
CSCtf65218
Simultaneously promoting of two secondaries when primary is offline.
Symptom: Simultaneous promotion of secondaries when primary is offline causes unexpected behavior when primary is brought online again.
Condition: This problem occurs when the secondaries have been promoted while primary was offline.
Workaround: Primary must be online when promoting secondaries.
CSCtg51846
Enum values are not shown in compound conditions in rule.
Symptom: Enum values are not shown in compound conditions in rule.
Conditions: This problem occurs in compound conditions if you add an attribute with enum values The enum values are not displayed.
Workaround:
1.
2.
3.
CSCtd49251
ADE 2120 fails AD test connection because of an NTP error.
Symptom: AD test connection fails.
Conditions: This problem occurs during normal operation when ACS and AD are up, running and the authentications are working.
If you:
1.
2.
3.
It displays the following error:
Installing acs...Workaround: Ignore the failure since authentications are working and the clocks between the ACS and AD are the same.
CSCtf64833
Filtering in service selection rule do not filter the device filter.
Symptom: Filtering in service selection rule does not work.
Conditions: This issue occurs when you go to Access Policies > Access Services > Service Selection Rules. Filtering a rule based on device filter does not work.
Workaround: None.
CSCtf71535
Wrong connection status on ACS GUI when admin user is disabled in AD.
Symptom: Wrong connection status on ACS GUI when admin user is disabled in AD.
Conditions: This problem occurs if you disable the Administrator user (used for configuring AD on ACS GUI) is disabled in AD. The authentications against AD still succeed.
Workaround: None.
CSCtg29788
No failure reason if the value for attributes mismatch.
Symptom: No failure reason if the value for attributes do not match.
Conditions: This problem occurs if you enter a wrong attribute value during authentication. The log will not show any failure reason.
Workaround: None.
CSCtg36142
Node Secret set - indication of secureid file exists does not work properly.
Symptom: The GUI indication whether the secureid file exists, does not work properly.
Conditions: This problem occurs even if you set the node secret, many hours earlier and capture and the image. The status continues to display, Not Cached.
Workaround: None.
CSCtc79341
The acs reset-config command does not remove ACS Patches.
Symptom: The acs reset-config command does not remove the installed ACS patches.
Conditions: This problem occurs if the patch contain changes to ACS database. This may cause problems with the original ACS database.
Workaround: Uninstall all ACS patches manually after running the command acs reset-config and then install them again.
CSCte09557
Restore with different CARS admin username creates problems.
Symptom: You cannot perform a Restore operation with a different CARS admin username.
Conditions: This problem occurs if you try to perform a Restore operation with a username that is not the same as the username that you used for the backup.
Workaround: Restore with the same admin username.
CSCtf27416
Incorrect information displayed while importing .csv file with null values.
Symptom: Incorrect result displayed while importing .csv file with null values.
Conditions: This problem occurs when you install ACS with 5.2 and import the .csv file configured with null values for the mandatory fields. Incorrect information is displayed.
Workaround: Enter default values in the null fields.
CSCtg71016
Cannot add the same server certificate in primary and secondary servers.
Symptom: An error appears if you add the same server certificates in both primary and secondary servers.
Conditions: This problem occurs if you add the same server certificates in both primary and secondary servers.
Workaround: None
CSCth13070
If there is no space left on the device, backup file should not be created.
Symptom: Restoring configuration from backup file, fails.
Conditions: This problem occurs if the backup file is empty or invalid. This happens when ACS machine disk does not have enough space left for the system to create the backup file.
Workaround: None.
CSCth25903
CARS setup accepts invalid characters during installation.
Symptom: During ACS installation, when CARS is being set up, ACS accepts other letters besides Y (yes) or N (no) regarding the host name.
Conditions: This problem occurs during ACS installation, CARS setup in the hostname dialog.
Workaround: Make sure to respond only by typing Y or N.
CSCtd46841
Clock/TZ/NTP/nameserver changes can damage AD functionality.
Symptom: ACS AD functionality may be severely damaged and possibly there will be little evidence visible to the user.
Conditions: This problem occurs if you apply changes to system services that AD connectivity relies upon, such as TZ, NTP and DNS settings.
Workaround: Restart ACS services after applying changes to change the TZ, NTP & DNS settings.
CSCte39351
ACS appliance SNMP agent process daemon stops.
Symptom: ACS SNMP daemon stops.
Conditions: This problem occurs when you run the following command:
Generating configuration...
Rebooting...
snmp-server contact
snmp-server locationWorkaround:
1.
2.
CSCtg32596
ACS server error while changing the log collector in a distributed deployment.
Symptom: Error in the ACS server.
Conditions: This problem occurs when you try to change the log collector in distributed deployment.
Workaround: Restart the ACS Monitoring & Reports Viewer processes.
CSCtg47711
TACACS authorization fails if the custom attribute value is more than 175.
Symptom: TACACS+ authorization fails if length for the customer attributes value exceed 175.
For example, if two custom attributes are configured and length of the value of the two custom attributes put together exceeds 175, the authorization will fail. This is also true for single custom attributes.
Conditions: This problem occurs if the length for the customer attributes value exceed 175.
Workaround: Make sure the length of value given for custom attributes does not exceed 175.
CSCtc64472
ACS Instance Health Summary - Data for details such as CPU figures are not updated.
Symptom: ACS Instance Health Summary report in ACS Monitoring & Reports Viewer does not get updated frequently.
Conditions: This problem occurs when you launch ACS Instance Health Summary report in ACS Monitoring & Reports Viewer.
Workaround: Check the status shown in tool tips for the ACS instance under ACS Health tab in the Dashboard.
CSCtc81268
Report links for authentication inactivity alarm authentication trend does not work.
Symptom: The link to Authentication Trend report given inside the alarm generated for Authentication inactivity does not work.
Conditions: This problem occurs with the link inside the alarm generated for Authentication inactivity.
Workaround: Launch the Authentication Trend report from Monitoring and Reports > Reports > Catalog > AAA Protocol > Authentication trend.
CSCtc86337
Favorite report launched from the dashboard displays an error.
Symptom: Favorite report cannot be launched from the dashboard.
Conditions: This problem may occur when you launch a favorite report that has special characters in the name from the dashboard.
Workaround: Launch the report from Monitoring and Reports > Reports > Favorites.
CSCtd36180
When you run CoA re-auth, accounting shows a stop record.
Symptom: For a given active session on ACS when CoA is run with the Re-Auth, ACS accounting records for the session display a "Stop" record followed by "Interim-Update".
Conditions: This problem occurs when the device is authenticated using MAB and then a CoA re-auth is run from the ACS Monitoring & Reports Viewer.
Workaround: None.
CSCtd44318
ACS Monitoring & Reports Viewer logs an error for non-existing service "NDAC_SGT_Service" with EAP-FAST.
Symptom: RADIUS authentication report for EAP-FAST has undefined Access Service type as "NDAC_SGT_Service".
Conditions: This problem occurs with RADIUS authentication report with EAP-FAST.
Workaround: None.
CSCtd46268
ACS Monitoring & Reports Viewer does not log records when changed from distributed to standalone.
Symptom: ACS instance that is changed in the distributed environment from a log collector to the stand alone mode, does not log any new authentication records.
Conditions: This problem occurs when you change an ACS instance from a log collector in a distributed environment to the stand alone mode.
Workaround: Restart the view processes.
CSCte20853
Traceroute information is not shown when you trace a device from Monitoring and Reports > Troubleshooting.
Symptom: Traceroute information is not shown from Monitoring and Reports > Troubleshooting.
Conditions: This problem occurs when you go to Monitoring and Reports > Troubleshooting and try to do a Traceroute for a device.
Workaround: Do the traceroute from ACS CLI.
CSCte20871
When you ping a device by DNS hostname from Monitoring and Reports > Troubleshooting, it does not work.
Symptom: When you try to ping a device by DNS hostname, it does not work.
Conditions: This problem occurs when you ping a device by DNS hostname from Monitoring and Reports > Troubleshooting. The DNS of the device and ACS are the same.
Workaround: Ping the device from ACS CLI.
CSCte84824
ACS Monitoring & Reports Viewer's Expert Troubleshooter does not compare assigned Device SGT.
Symptom: ACS Monitoring & Reports Viewer's Expert Troubleshooter does not compare Device SGT that is assigned to the device.
Conditions: This problem occurs with Device SGT.
Workaround: None.
CSCte94293
ACS Monitoring & Reports Viewer's Expert Troubleshooter does not compare IP user SGT.
Symptom: ACS Monitoring & Reports Viewer's Expert Troubleshooter does not compare IP user SGT.
Conditions: This problem occurs with IP user SGT.
Workaround: None.
CSCtf18322
Expert Troubleshooter tool's Egress Policy failed to compare the policies
Symptom: Expert Troubleshooter tool's Egress Policy does not compare the ACS policy and the policy that is on the switch.
Conditions: This problem occurs with Egress Policy.
Workaround: None.
CSCtc65305
ACS Monitoring & Reports Viewer displays ServSelect Rule # instead of Authorization Rule #.
Symptom: ACS Monitoring & Reports Viewer interchanges the service selection rule and authorization rule in the report.
Conditions: This problem occurs with service selection and authorization rule.
Workaround: None.
CSCth57441
ACS 5.1HDD failure does not prevent RT from processing incoming requests.
Symptom: A hardware failure that causes the ACS appliance's file system to be mounted in read-only, does not prevent the runtime component to load and start processing the incoming RADIUS requests.
However, if critical logging is enabled, the authentication attempts fail. The authentication attempts cannot be logged on the local hard-drive because it is mounted in read-only mode
Since the runtime process remains active but does not process the authentication requests, it prevents the AAA client from falling back to the secondary server.
Conditions: This problem occurs when ACS 5.1 appliance is running with a failed HDD and the critical logger is enabled.
Workaround: Manually shut down the failed ACS appliance until it is replaced.
CSCth62139
ACS authentication rate decreases with internal user attribute.
Symptom: ACS authentication rate decreases disproportionately to the with new internal user attributes.
Conditions: This problem occurs when you add many new attributes for users in the internal database. The sustainable authentications rate of ACS 5.1 decreases disproportionately.
For example, with 10 attributes and a single internal user, the sustainable rate can go up to 300-400 RADIUS PAP authentications per second.
By adding up to 96 attributes to that single internal user, the sustainable rate decreases to 30 RADIUS PAP authentications per second.
Workaround: None.
CSCth68051
Migrated devices cannot update the location through the import from CSV file.
Symptom: After migration from ACS 4.x the network devices cannot be updated using the File Operations update CSV.
Conditions: This problem occurs if you try to update the location or device-type. Update completes without errors, but nothing changes.
Workaround:
1.
2.
3.
After the import you will be able to update the devices through import.
CSCth72626
MS-CHAPv2 responses with bad flag values are not dropped.
Symptom: If the NAS sends an MS-CHAP-v2 response with the flags field not set to '0' (0x00), ACS 5.1 drops RADIUS access requests for MS-CHAP-v2 with the following error message:
snmp-server contact "my name"Conditions: This problem occurs if the flags in the fourth byte of the MS-CHAP-v2 response is not 0x00 (the only mandatory value allowed by RFC 2548).
Workaround: None.
CSCth72779
ACS 5 sends EAP-failure message as a challenge rather than as an access-reject.
Symptom: When a supplicant sends a bad MSCHAP message inside a PEAP tunnel ACS 5.x server responds with an EAP-failure message encapsulated in a RADIUS-challenge packet.
Conditions: This problem occurs when you are running ACS 5.x with PEAP-MSChapV2.
Workaround: None.
CSCth77468
ACS 5.1 do not include 'C' and 'V' values in MS-CHAP-v2 failure packet.
Symptom: ACS 5.1 does not include 'C' and 'V' values in MS-CHAP-v2 failure packet.
Conditions: This problem occurs while sending a RADIUS access-reject for PPP MS-CHAP-v2 authentication. ACS 5.1 includes the following values in the MS-CHAP-v2 failure:
•
•
The "cccccccccccccccccccccccccccccccc" is the ASCII representation of a hexadecimal challenge value. This field must be exactly 32 octets long
Because of this, some NASs, such as an ASA do not honor the RADIUS access-reject because of the missing values. This sends further RADIUS access-request retries.
Workaround: None.
CSCth68006
Process status not updated after restarting runtime in distributed environment.
Symptom: In distributed environment process, the status alert is generated continuously.
Conditions: This problem occurs when you:
1.
2.
3.
Workaround: Restart ACS.
CSCth66212
CLI command show tech-support displays an error message.
Symptom: The CLI command show tech-support displays the following error:
snmp-server contact my_name.Conditions: This problem occurs when you run the following commands in admin mode:
IP Address format violation.
"TPLUS: Received accounting response with status FAIL"
00:04:27: %AAA-3-DROPACCTFAIL: Accounting record dropped, send to server
failed: system
Authentication failed : 12727
15016 Selected Authorization Profile - DenyAccess
15039 Selected Authorization Profile is DenyAccess
An unexpected error has occurred.At the end file1 is created in localdisk as file1.tar.gz.
Workaround: None
CSCth66302
RADIUS authentication request rejected because of a critical logging error.
Symptom: Running stress PEAP MS-CHAPV2 against primary ACS machine fails with the following error message:
acs config-web-interface migration asdfConditions: This problem occurs when there is a large deployment setup with one primary connected to seven secondary machines.
Workaround: None.
CSCth42890
ID store names containing HTML control characters cause error while saving ID policy.
Symptom: ID store names containing HTML control characters cause error while saving ID policy changes. The following error appears:
Unknown CA - error unable to get issuer certificate locallyOK to return to the list page.Conditions: This problem occurs when you:
1.
2.
3.
4.
5.
Workaround: Do not use HTML control character percentage (%) in names of ID stores.
CSCtg87211
Primary management process fails during large user import.
Symptom: Primary management process fails during large user import.
Conditions: The problem occurs when you import more than 50,000 users in a scaled ACS deployment (7 secondaries and more).
Workaround: The management process is restarted automatically by watchdog. Repeat the import procedure.
When importing a large number of users (more than 5000) in distributed deployment it is recommended to deregister all secondary nodes and perform the import to single primary. Then re-register the secondary nodes.
CSCtl01880
User password expiry reminder message is not shown for RADIUS authentication.
Symptom: No reminder is shown for RADIUS authentication.
Condition: No reminder is shown for RADIUS authentication even when the option for reminder is enabled, if the password is not changed in N number of days.
Workaround: None.
CSCtk02959
Cannot use a % in password on CLI.
Symptom: Get error if trying to add a % in the password on the CLI.
Conditions: On the CLI, create a user with a % any where in the password.
Workaround: Do not use % in password.
CSCtn17779
ACS 5 migration utility aborts with errors on Windows 2008 64 bit
Symptom: The ACS 5 migration utility aborts with errors.
Conditions: This is seen when the migration utility runs on Windows 2008 64 bit.
Workaround: Run the utility on Windows 2003.
CSCtj81255
Two MAC addresses detected on neighbooring switch of ACS 1121 Appliance.
Symptom: Two MAC addresses are detected on the switch interface connected to an ACS 1121 Appliance although only one interface is connected on the ACS 1121 Server eth 0.
Conditions: Only one Ethernet interface, eth 0 is connected between ACS and Switch.
Workaround: Assign a static IP address to disable the DHCP function of the BMC (Baseboard Management Controller) feature using BIOS setup.
Caution
CSCua99537
Network Time Protocol Daemon (NTPD) running with ACS, sometimes, does not synchronize its clock with the windows time service.
Symptom: When AD domain is used as a NTP server, the clcok on ACS and AD does not synchronize with the windows time service.
Conditions: This problem occurs often when ACS or AD is running as a virutal machine.
Workaround: None.
Documentation Updates
Table 16 lists the updates to Release Notes for the Cisco Secure Access Control System 5.2.
Product Documentation
Note
Table 17 lists the product documentation that is available for ACS 5.2. To find end-user documentation for all the products on Cisco.com, go to: http://www.cisco.com/go/techdocs
Select Network Management > Security and Identity Management > Cisco Secure Access Control Server Products > Cisco Secure Access Control System.
Table 17 Product Documentation
License and Documentation Guide for the Cisco Secure Access Control System 5.2
http://www.cisco.com/en/US/products/ps9911/
products_documentation_roadmaps_list.htmlMigration Guide for the Cisco Secure Access Control System 5.2
http://www.cisco.com/en/US/products/ps9911/
prod_installation_guides_list.htmlUser Guide for the Cisco Secure Access Control System 5.2
http://www.cisco.com/en/US/products/ps9911/
products_user_guide_list.htmlCLI Reference Guide for the Cisco Secure Access Control System 5.2
http://www.cisco.com/en/US/products/ps9911/
prod_command_reference_list.htmlSupported and Interoperable Devices and Softwares for the Cisco Secure Access Control System 5.2
http://www.cisco.com/en/US/products/ps9911/
products_device_support_tables_list.htmlInstallation and Upgrade Guide for the Cisco Secure Access Control System 5.2
http://www.cisco.com/en/US/products/ps9911/
prod_installation_guides_list.htmlSoftware Developer's Guide for the Cisco Secure Access Control System 5.1
Note
http://www.cisco.com/en/US/products/ps9911/
products_programming_reference_guides_list.htmlRegulatory Compliance and Safety Information for the Cisco 1121 Secure Access Control System 5.1
http://www.cisco.com/en/US/products/ps9911/
prod_installation_guides_list.html
Notices
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License:
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
4.
5.
6.
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4.
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
Supplemental License Agreement
END USER LICENSE AGREEMENT SUPPLEMENT FOR CISCO SYSTEMS ACCESS CONTROL SYSTEM SOFTWARE:
IMPORTANT: READ CAREFULLY
This End User License Agreement Supplement ("Supplement") contains additional terms and conditions for the Software Product licensed under the End User License Agreement ("EULA") between you and Cisco (collectively, the "Agreement"). Capitalized terms used in this Supplement but not defined will have the meanings assigned to them in the EULA. To the extent that there is a conflict between the terms and conditions of the EULA and this Supplement, the terms and conditions of this Supplement will take precedence.
In addition to the limitations set forth in the EULA on your access and use of the Software, you agree to comply at all times with the terms and conditions provided in this Supplement. DOWNLOADING, INSTALLING, OR USING THE SOFTWARE CONSTITUTES ACCEPTANCE OF THE AGREEMENT, AND YOU ARE BINDING YOURSELF AND THE BUSINESS ENTITY THAT YOU REPRESENT (COLLECTIVELY, "CUSTOMER") TO THE AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THE AGREEMENT, THEN CISCO IS UNWILLING TO LICENSE THE SOFTWARE TO YOU AND (A) YOU MAY NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE, AND (B) YOU MAY RETURN THE SOFTWARE (INCLUDING ANY UNOPENED CD PACKAGE AND ANY WRITTEN MATERIALS) FOR A FULL REFUND, OR, IF THE SOFTWARE AND WRITTEN MATERIALS ARE SUPPLIED AS PART OF ANOTHER PRODUCT, YOU MAY RETURN THE ENTIRE PRODUCT FOR A FULL REFUND. YOUR RIGHT TO RETURN AND REFUND EXPIRES 30 DAYS AFTER PURCHASE FROM CISCO OR AN AUTHORIZED CISCO RESELLER, AND APPLIES ONLY IF YOU ARE THE ORIGINAL END USER PURCHASER.
1.
For purposes of this Supplement, the Product name(s) and the Product description(s) you may order as part of Access Control System Software are:
A. Advanced Reporting and Troubleshooting License
Enables custom reporting, alerting and other monitoring and troubleshooting features.
B. Large Deployment License
Allows deployment to support more than 500 network devices (AAA clients that are counted by configured IP addresses). That is, the Large Deployment license enables the ACS deployment to support an unlimited number of network devices in the enterprise.
C. Advanced Access License (not available for Access Control System Software 5.0, will be released with a future Access Control System Software release)
Enables TrustSec policy control functionality and other advanced access features.
2.
•
•
•
3.
Major Upgrade means a release of Software that provides additional software functions. Cisco designates Major Upgrades as a change in the ones digit of the Software version number [(x).x.x].
Minor Upgrade means an incremental release of Software that provides maintenance fixes and additional software functions. Cisco designates Minor Upgrades as a change in the tenths digit of the Software version number [x.(x).x].
4.
Please refer to the Cisco Systems, Inc., End User License Agreement.
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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Release Notes for the Cisco Secure Access Control System 5.2
© 2010 Cisco Systems, Inc. All rights reserved
