|
|
These release notes pertain to Cisco Secure Access Control Server for Windows 2000/NT Servers (Cisco Secure ACS) version 3.0.4.
Cisco Secure ACS provides authentication, authorization, and accounting (AAA—pronounced "triple A") services to network devices that function as AAA clients, such as a network access server, PIX Firewall, or router. A AAA client is any such device that provides AAA client functionality and uses one of the AAA protocols supported by Cisco Secure ACS.
Cisco Secure ACS helps centralize access control and accounting, in addition to router and switch access management. With Cisco Secure ACS, network administrators can quickly administer accounts and globally change levels of service offerings for entire groups of users. Although using an external user database is optional, Cisco Secure ACS supports many popular user databases, enabling companies to use the knowledge gained from and the investment already made in building their corporate user databases.
Cisco Secure ACS supports Cisco AAA clients such as the Cisco 2509, 2511, 3620, 3640, AS5200 and AS5300, AS5800, the Cisco PIX Firewall, Cisco Aironet Access Point wireless networking devices, Cisco VPN 3000-series Concentrators, and Cisco VPN 5000-series Concentrators. It also supports third-party devices that can be configured with Terminal Access Controller Access Control System (TACACS+) or Remote Access Dial-In User Service (RADIUS) protocols. Cisco Secure ACS treats all such devices as AAA clients. Cisco Secure ACS uses the TACACS+ and RADIUS protocols to provide AAA services that ensure a secure environment. For more information about support for TACACS+ and RADIUS in Cisco Secure ACS, see the Cisco Secure ACS for Windows 2000/NT Servers User Guide.
Installing Cisco Secure ACS 3.0 for Windows 2000/NT Servers provides information about the following subjects:
Cisco Secure ACS for Windows 2000/NT Servers User Guide provides detailed information about configuring and using Cisco Secure ACS. This guide is available from Cisco.com or on the product CD.
We have added several major and minor features to Cisco Secure ACS 3.0.
The major features added to Cisco Secure ACS are as follows:
 |
Note Cisco VPN 3000-series Concentrators and Cisco IOS will support MS CHAP password aging in upcoming releases. |
The minor features added to Cisco Secure ACS are as follows:
To supplement the documentation, white papers about using and deploying various protocols and AAA clients are posted at the following URL:
http://www.cisco.com/warp/public/cc/pd/sqsw/sq/prodlit/index.shtml.
For information about installing Cisco Secure ACS, see Installing Cisco Secure ACS 3.0 for Windows 2000/NT Servers.
Before Cisco Secure ACS 3.0.1, support for CRYPTOCard token servers used the vendor-proprietary interface provided with the CRYPTOCard token server. Beginning with Cisco Secure ACS 3.0.1, we support CRYPTOCard token servers using a standard RADIUS interface.
If you upgrade to Cisco Secure ACS 3.0 and had configured CRYPTOCard authentication in the previous installation of Cisco Secure ACS, the installation program prompts you for information about the CRYPTOCard RADIUS server. With this information, the installation program replaces the older CRYPTOCard configuration with a new one that uses the RADIUS interface of the CRYTPOCard easyRADIUS server. To use the RADIUS interface of the CRYPTOCard server, be sure the CRYPTOCard easyRADIUS server is installed on a CRYPTOCard Windows server. For more information about CRYPTOCard easyRADIUS, see CRYPTOCard documentation.
We tested running Cisco Secure ACS and the CRYPTOCard easyRADIUS server on the same Windows server. Testing occurred on Windows NT 4.0 with Service Pack 6 and Windows 2000 with Service Pack 2. We used CRYPTOCard easyRADIUS server versions 5.0 and 5.1. However, we recommend that you do not run the CRYPTOCard easyRADIUS server on the same Windows server that runs Cisco Secure ACS. If you choose to do so, be sure that Cisco Secure ACS and CRYPTOCard easyRADIUS use different ports to receive RADIUS requests.
You can change the UDP ports used by the CRYPTOCard RADIUS server by editing its services file, usually located in c:\WINNT\system32\drivers\etc. For more information about the UDP ports used by the CRYPTOCard RADIUS server and how to change them, see your CRYPTOCard documentation.
The evaluation version of Cisco Secure ACS 3.0 provides full functionality for 90 days after the date of installation. This allows you to use all features of Cisco Secure ACS 3.0 while determining if it meets your needs. The evaluation version of Cisco Secure ACS 3.0 will be available 30 days after the release of the commercial version of Cisco Secure ACS 3.0.
You can distinguish the evaluation version of Cisco Secure ACS 3.0 from the commercial version in the following ways:
When the evaluation period has elapsed, the CSRadius and CSTacacs services fail to start. You will receive a message upon accessing the administrative interface notifying you that your evaluation period has elapsed.
Please contact your Cisco Sales Representative(s) to inquire about purchasing the commercial version of Cisco Secure ACS. To purchase the commercial version of Cisco Secure ACS 3.0 online, use Part Number CSACS-3.0 at the following URL:
http://www.cisco.com/pcgi-bin/cm/welcome.pl
After purchasing a commercial version of Cisco Secure ACS 3.0, you can upgrade your Cisco Secure ACS server from the evaluation version to the commercial version by installing the commercial version over the evaluation version. For information on installing Cisco Secure ACS 3.0, follow the instructions in Installing Cisco Secure ACS 3.0 for Windows 2000/NT Servers.
The following topics are limitations and restrictions that apply to Cisco Secure ACS 3.0.4.
Cisco Secure ACS has not been interoperability tested with other Cisco software. Other than for the software and operating system versions listed in this document, we performed no interoperability testing. Using untested software with Cisco Secure ACS may cause undesired results. For the best performance of Cisco Secure ACS, we recommend that you use the versions of software and operating systems listed in this document.
We tested upgrading to Cisco Secure ACS 3.0.4 from Cisco Secure ACS 3.0.3.
We used the version of Microsoft CA certificate server included with Windows 2000 Server to test EAP-TLS certificate requests.
To administer all features included in Cisco Secure ACS 3.0.4, we recommend that you use the English-language edition of Microsoft Internet Explorer version 6.0 SP1 for Microsoft Windows. For previous releases of Cisco Secure ACS 3.0, we also tested Netscape Communicator version 7.0 for Microsoft Windows; however we tested Cisco Secure ACS 3.0.4 solely with Microsoft Internet Explorer.
We did not test other versions of these browsers, nor did we test web browsers by other manufacturers.
|
Note To use a web browser to access the Cisco Secure ACS HTML interface, configure your web browser as follows: |
We tested the RADIUS token server external user database feature in Cisco Secure ACS version 3.0.4 using RSA ACE/Server version 5.0.
We tested Cisco Secure ACS version 3.0.2 with the following token server software:
|
Note Cisco Secure ACS 3.0.2 supports CRYPTOCard, ActivCard, and Vasco token servers using RADIUS. |
For information about CRYPTOCard support, see Changes to CRYPTOCard Support.
We used Netscape iPlanet Directory Server version 4.2 to test standard LDAP database support.
Because we made no changes to Novell support, we did not conduct Novell testing with Cisco Secure ACS version 3.0.4. We tested Cisco Secure ACS version 3.0.2 with the following Novell software:
We used Windows 2000 with Service Pack 4 and Windows NT 4.0 with Service Pack 6 to test Cisco Secure ACS version 3.0.4 for Windows authentication.
|
Note Cisco Secure ACS only supports English language versions of Windows and its Service Packs. |
Because we made no changes to CiscoSecure Authentication Agent support, we did not conduct CiscoSecure Authentication Agent testing with Cisco Secure ACS version 3.0.4. With Cisco Secure ACS 3.0.2, we tested CiscoSecure Authentication Agent on the following client platform operating systems:
We did not test the CiscoSecure Authentication Agent on the following client platform operating systems:
This section identifies caveats and issues for Cisco Secure ACS.
Refer to the appropriate release notes for information about hardware caveats that might affect Cisco Secure ACS. You can access these release notes online at the following URLs.
http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/
http://www.cisco.com/univercd/cc/td/doc/product/software/
http://www.cisco.com/univercd/cc/td/doc/product/vpn/vpn3000/
http://www.cisco.com/univercd/cc/td/doc/product/vpn/vpn3002/
http://www.cisco.com/univercd/cc/td/doc/product/aggr/vpn5000/
http://www.cisco.com/univercd/cc/td/doc/product/wireless/
http://www.cisco.com/univercd/cc/td/doc/product/lan/
|
Note Caveats are printed word-for-word as they appear in our caveat tracking system. |
Caveats are printed word-for-word as they appear in our bug tracking system.
|
Note Caveats are printed word-for-word as they appear in our bug tracking system. |
This section identifies known caveats and issues with Cisco Secure ACS 3.0.4.
If you use Internet Explorer 5.5 or Netscape 4.7 and refresh or reload the frame when viewing Interface Configuration: TACACS+(Cisco IOS), you receive the following error message:
Workaround/Solution: Click Interface Configuration: TACACS+(Cisco IOS) and continue editing the TACACS+ settings.
In Cisco Secure ACS 3.0, this behavior does not occur with Internet Explorer 5.5.
A PPTP tunnel using a Cisco VPN 3000-series concentrator and MS-CHAP version 2 fails. The VPN concentrator indicates that authentication passed; however, tunnel establishment fails. When using the MS-CHAP version 1 method with the same configuration, tunnel establishment succeeds. When using the concentrator's internal user database with MS-CHAP version 2, tunnel establishment succeeds.
Workaround/Solution: There are few steps which needs to be filled when configuring Cisco Secure ACS to support PPTP Tunnel in MS-CHAP version 2 (and version 1) authentication methods:
Setup two users at least on Cisco Secure ACS, one as a tunnel user and the others as the authenticated users. The tunnel user and its password should be the same as the tunnel group name on the concentrator and its password.
The authenticated users must include the following settings in Cisco Secure ACS, as well:
Use the Windows 2000 PPTP client and establish the PPTP tunnel via MS-CHAP V2 authentication method.
When Installing Cisco Secure ACS, you may see the following error:
followed by several other errors, such as:
Workaround/Solution: Delete pdh.dll from the Windows system32 directory, then restart the installation.
Windows 2000 groups for remote domains cannot be seen by Cisco Secure ACS running on a Windows NT 4.0 member server.
Workaround/Solution: On the Cisco Secure ACS server, configure all Cisco Secure ACS services to run using a domain administrator account for the domain of which the server is a member. For more information about additional configuration required to run Cisco Secure ACS 3.0 on a Windows NT 4.0 member server, see Installing Cisco Secure ACS 3.0 for Windows 2000/NT Servers.
The services associated with Cisco Secure ACS are:
If you use Netscape Navigator v.4.7 to access the HTML interface, adding an administrator to Cisco Secure ACS can cause 100% CPU utilization for over a minute. This in turn can cause the CSRadius service to pause until the browser resumes normal operation. The fault lies in the Netscape browser rather than Cisco Secure ACS.
Workaround/Solution: Once the 100% CPU utilization has begun, wait until browser operation returns to normal. This should be less than five minutes. To avoid the behavior altogether, use a tested version of Microsoft Internet Explorer. See the Tested Web Browser Versions section of the Release Notes for Cisco Secure Access Control Server for Windows 2000/NT Servers
When a Novell NDS database configuration in Cisco Secure ACS has a context list greater than 4095 characters long, editing the NDS configuration page results in incorrect HTMLin the browser interface.
Workaround/Solution: Use a context list no longer than 4096 characters.
Customer is experiencing problems adding the user fields (3,4,5) to the RADIUS accounting file.
When he renames these fields in the User Attributes in Interface Configuration, and then attempts to add them to the RADIUS Accounting log, the changes do not appear in the log.
To reproduce this problem, follow these steps:
1. Change the names of Real Name, User field 2, User field 3, or any of the User Defined Fields in Interface Configuration.
2. In System Configuration, select Logging, and then select CSV Radius Accounting.
3. Add one (or more) of the changed fields to the right column.
5. Select the CSV Radius Accounting log again.
6. The field you just moved to the right column will no longer be in the right column, but will appear in the left column once more.
Workaround/Solution: After renaming a user-defined attribute, restart all Cisco Secure ACS services from the Windows Control Panel. Once the services have been restarted, the CSV RADIUS Accounting configuration screen shows the renamed attributes and remembers their selection when the page is submitted.
In the System Configuration section, settings made on the IP Address Recovery page and the Date Format Control page are not restored from backup.
Workaround/Solution: Manually configure the IP Address Recovery and Date Format Control pages.
The CSLog service crashes when you modify ODBC logging configuration during ODBC logging operations.
Workaround/Solution: Do not change logging configuration while Cisco Secure ACS is authenticating users.
Changes to user-defined fields in user records do not appear to replicate. After the user-defined fields are changed in the Interface Configuration section on the primary Cisco Secure ACS server and replication succeeds, the secondary Cisco Secure ACS server does not display the changes to the user-defined fields in the HTML interface.
Workaround/Solution: The changes to the user-defined fields do replicate successfully; however, to see the changes on the secondary Cisco Secure ACS server, restart the CSAdmin service.
Changes to HTTP Port Allocation settings do not appear to replicate. After the HTTP Port Allocation settings are changed on the Access Policy Setup page in the Administration Control section on the primary Cisco Secure ACS server and replication succeeds, the secondary Cisco Secure ACS server does not display the changes to the HTTP Port Allocation settings in the HTML interface.
Workaround/Solution: The changes to the HTTP Port Allocation settings do replicate successfully; however, to see the changes on the secondary Cisco Secure ACS server, restart the CSAdmin service.
In the System Configuration section, settings made on the VoIP Account Configuration page are not restored from backup. Neither are these settings preserved during reinstallation of Cisco Secure ACS 3.0 or upgrading to a later build of Cisco Secure ACS 3.0.
Workaround/Solution: Manually configure the VoIP Accounting Configuration page.
Customer is experiencing problems adding the user fields (3,4,5) to the RADIUS accounting file. When he renames these fields in the User Attributes in Interface Configuration, and then attempts to add them to the RADIUS Accounting log, the changes do not appear in the log.
To reproduce this problem, follow these steps:
1. Change the names of Real Name, User field 2, User field 3, or any of the User Defined Fields in Interface Configuration.
2. In System Configuration, select Logging, and then select CSV Radius Accounting.
3. Add one (or more) of the changed fields to the right column.
5. Select the CSV Radius Accounting log again.
6. The field you just moved to the right column will no longer be in the right column, but will appear in the left column once more.
Workaround/Solution: After renaming a user-defined attribute, restart all Cisco Secure ACS services from the Windows Control Panel.
Once the services have been restarted, the CSV RADIUS Accounting configuration screen shows the renamed attributes and remembers their selection when the page is submitted.
An AAA server cannot be deleted from the "(Not Assigned) AAA Servers" table if the "Synchronize" table in the "Synchronization Partners" is empty. An error message "x.x.x.x can not be deleted since it is an synchronization partner" is displayed.
Workaround/Solution: Move any AAA server to the Synchronize table, then delete the desired AAA server.
Changes to the order of the Replication Partners, under Database Replication is not saved when submitting changes. When you get into the Database Replication window, the servers are shown in alphabetical order and not in the order desired. The database replication is also done in alphabetical order, so in the order shown by the GUI after submitting changes.
Workaround/Solution: There is no workaround.
When the character \ is added in the AAA client name, eg: cis\co, ACS crashes.
Workaround/Solution: Do not use the backslash character in AAA client names.
After setting up command Authorization Sets in ACS 3.0, and specifying authorization for config-commands in NAS. Customer specifies to permit cmd=interface cmd-arg=permit FastEthernet 0
Issuing this config command fails as it expect the "0" as a separate argument. But after adding a cmd-arg="permit 0" all interface commands are allowed - not just on FastEthernet.
Workaround/Solution: None at this time.
Authentication services CSRadius and CSTacacs might crash when ACS 2.6.3.2 is installed on windows 2000 with service pack 1 and when safeword is used on a separate unix box. All users are safeword users.
Workaround/Solution: None at this time. We tested Cisco Secure ACS 3.0 on Windows 2000 Server using an English-language version of Service Pack 2. Apply Service Pack 2 may alleviate the issue.
Customer has run into a limitation on replication partners of 20. You can configure more, but the 21st partner in the list but it will not work - the master will say that it's not responding.
Workaround/Solution: If you delete one of the servers higher up in the list, thus moving the problem server into slot number 20, replication works.
Cannot delete the NAS. Giving the error:
Cannot delete AAA server, AAA server is a Synchronization Partner
Workaround/Solution: Need to go into the registry and delete the host.
Command authorization appears to fail on all AAA clients when the applicable command authorization set is configured to be applied to the <Default> network device group (NDG).
This is correct behavior. The <Default> NDG corresponds to the "Not Assigned" NDG in Network Configuration. If the AAA client on which the user is attempting to issue commands is not in the "Not Assigned" NDG and there is no command authorization set that does apply to the AAA client, Cisco Secure ACS denies authorization for the command.
Workaround/Solution: If you intend to apply a command authorization set to all AAA clients, assign it once per every NDG rather than solely to the <Default> NDG. There is currently no single option that applies a command authorization set to all NDGs.
EAP-MD5 Authentication fails when AAA Client use RADIUS (Cisco Aironet) as an authentication method.
Workaround/Solution: When RADIUS (IETF) is being used EAP-MD5 authentication operates properly.
Cisco Secure ACS accepts empty and therefore invalid PIX ACLs. There are two ways this can occur. In the first, you can submit only a space in the PIX ACL. In the second, you can delete the contents of a previously submitted, valid PIX ACL and resubmit it successfully.
Workaround/Solution: None at this time.
Users authenticating with CryptoCard incorrectly receive a password prompt in addition to the username, challenge, and response prompts.
Workaround/Solution: Users can enter any string at the password prompt and press Enter, then continue CryptoCard authentication normally.
The "Previous" button disappears when using the User Setup page in the Cisco Secure ACS HTML interface.
Currently, Cisco Secure ACS cannot provide the ability to page backwards.
Workaround/Solution: Use the browser back button.
Cisco Secure ACS 2.6.4, 3.0.2, and 3.1.1 all log an incorrect value in TACACS+ Accounting for the "disc-cause" attribute. If you set up a PPP session to do an idle timeout, when it disconnects you will get "CLID-Authentication-Failure" in the TACACS+ Accounting log for "disc-cause" - but the TACACS+ documentation for IOS says that the value "4" is Idle timeout.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fsecur_c/fappendx/scftacat.htm#20164
If you attempt to upgrade to Cisco Secure ACS 3.0.3 from 3.0.2.5 and abort installation of 3.0.3 before it is complete, using the clean.exe application that comes with 3.0.2.5 does not remove all related file system directories or registry keys.
Workaround/Solution: Manually edit the registry to remove HKLM:SOFTWARE/Cisco/CiscoAAAv3.0 entries. Manually delete remaining Cisco Secure ACS 3.0 subdirectories.
Occasionally updated components are not replicated to the third replication partner in a replication cascade. This happens because replication pre-checks on the second partner indicate incorrectly that outbound replication is not required for the third partner in the cascade. This occurs because the pre-checks performed by the second replication partner happen before replication is completed from the first replication partner.
Workaround/Solution: On the following replication cycle, the unreplicated component will be replicated from the second replication partner to the third replication partner.
This behavior occurs after upgrading Cisco Secure ACS from 3.0.2.5 to 3.0.3 and when Cisco Secure ACS is running on a member server. Users whose accounts reside in a Windows 2000 user database and whose accounts are configured to enforce a password change at next login are disconnected after providing the new password.
When Cisco Secure ACS authenticates a Windows 2000 user from native trusted domain, MS-CHAP password changing doesn't work even though authentication via MS-CHAPv2 works properly.
EAP-TLS Authentication fails after successful Restore process. Seems that the problem is related to Private Keys decryption failing after restore. The following error is presented in CSAuth log after a successful restore process:
The problem occurs when using restore from a dump file created during backup on other machine.
It also occurs when the dump file was backed up, ACS was uninstalled and then Installed and restored from a dump file.
Workaround/Solution: None at this time.
In the web GUI a black bar can sometimes appear in the page background when the page being displayed is very large (such as a list of several hundred NAS entries in Network Configuration). This is purely cosmetic and will not affect the server functionality, although it may make it difficult to read some information. The location of the bar may not be consistent on all servers as it's location depends completely on how the browser renders the page.
Workaround: Rename the page_background.gif file so that it does not get displayed. This will make the top line of the page unreadable (where it says "Select" or "Help") but will eliminate the black bars in the page. The page_background.gif file is located under C:\Program Files\CiscoSecure ACS v3.x\CSAdmin\WWW\images by default.
After an ACS 3.0 server hangs (because of a hung/failed CSauth process) the WAPs trying to use this failed server should at some point timed out and failed over to another ACS server. This failover does not happen.
With AAA Accounting for exec sessions configured on a NAS, a user shows up in the Logged-In User report on ACS. With Accounting also configured for going into enable mode, the user no longer appears in the Logged-In User report after authenticating successfully.
Using MS-Text-Driver and accountaction.csv files to maintain user DB according: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/csnt30/user/s.htm#2110
randomly skips or truncated data. Syntax of accountaction file is correct. Sometimes error message is logged like:
Re-running csdbsync (without changing accountaction.csv file) mostly solves this problem (correct imported, no error message on cli/logg-file). It also has happened during re-running, that csauth stopped and windows violation message box appeared.
In RFC 2246, the Server Hello has 4 bytes of gmt_unix_time and 28 bytes of random data. But, Server Hello from CiscoSecureACS has 4 bytes of garbage(00 00 00 00), 4 bytes of gmt_unix_time and 24 bytes of random data. Some clients may fail in authentication.
Workaround: There is no workaround.
The cisco-nas-port attribute should be available in the VoIP accounting log.
Network Model within Registry grows and causes inconsistent behavior of AAA operations.
Conditions: The reason the Network Model is growing so large is that the packets do not have a traditional NAS-PORT value, and only in some cases do they contain the cisco VSA for nas-port (string version). Without a NAS-PORT the network model creates a port using the username.
Password change fails for RADIUS-based MS-CHAP v2 password change when the username submitted is not domain qualified. This happens regardless of whether ACS is installed on a domain controller or member server. RADIUS-based MS-CHAP v2 password change is supported only with Windows external user databases.
Workaround: Require users to provide domain-qualified usernames at login.
ACS server stops authenticating new requests when the ACS replication is initiated.
When Cisco Secure ACS is performing EAP-TLS authentications under a heavy load, some sessions that should end based on timeout values are ended with an Access Reject message instead. Under a lighter load, Cisco Secure ACS correctly responds with timeout messages instead of Access Reject.
Workaround: If you use multiple Cisco Secure ACS servers, try to load balance peak authentication load. This can be done by configuring AAA clients to use different Cisco Secure ACS servers.
NAS--------proxy RADIUS ACS----------authenticating RADIUS server
Symptom: If the NAS is sending a username (IETF attribute 1) in a RADIUS access-request packet, which contains upper- and lower-case letters, the proxy ACS RADIUS will forward this access-request packet to the authenticating RADIUS server with all upper-case letters changed to lower-case letters
Conditions: - This is observed only when prefix stripping is configured on the proxy RADIUS ACS and the username contains the prefix to be stripped by the proxy RADIUS ACS. - This is not observed when suffix stripping or no stripping takes place.
Workaround: Do not use upper-case letters in the username attribute, when performing prefix stripping
When an external RADIUS database attempts to specify a user's group using Cisco IOS/PIX RADIUS attribute 1, [009\001] cisco-av-pair, and the group number specified is greater than 499, Cisco Secure ACS fails the user authentication and logs a seemingly unrelated error related to Group 100 and network access restrictions (even if no NARs are applied to the user).
RADIUS group specification requires that the assignment in the cisco-av-pairattribute use the following format:
where N is the Cisco Secure ACS group number (0 through 499) to which Cisco Secure ACS should assign the user.
Workaround: Ensure that the external RADIUS server database only specifies a group number between 0 and 499.
After upgrading to 3.0.4, if you use a backup created by an older version of ACS, such as from 3.0.3, Cisco VPN 3000 RADIUS VSAs added in 3.0.4 disappear. The old backup file replaces the VSA configuration with a version that predates the addition of or changes to Cisco VPN 3000 VSAs 29, 61-68, and 75.
Workaround: Reinstall 3.0.4 and reconfigure the missing Cisco VPN 3000 RADIUS attributes.
Misconfigured ODBC logging creates errors in CSLog and can result in a memory leak.
Workaround: Configure ODBC logging correctly or disable ODBC logging.
The following documents directly support Cisco Secure ACS:
You can find other product literature, including white papers, data sheets, and product bulletins, at the following URL:
http://www.cisco.com/warp/public/cc/pd/sqsw/sq/prodlit/index.shtml.
In addition to these documents, online documentation is provided within the Cisco Secure ACS user interface. The entire Cisco Secure ACS documentation set is also available at the following URL:
http://www.cisco.com/warp/public/cc/pd/sqsw/sq/
Cisco provides several ways to obtain documentation, 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 on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_ launch.html
All users can order annual or quarterly subscriptions through the online Subscription Store:
http://www.cisco.com/go/subscription
Click Subscriptions & Promotional Materials in the left navigation bar.
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
http://www.cisco.com/en/US/partner/ordering/index.shtml
You can submit e-mail comments about technical documentation to bug-doc@cisco.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:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.
The Cisco TAC website (http://www.cisco.com/tac ) provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year.
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:
http://tools.cisco.com/RPF/register/register.do
Using the online TAC Case Open Tool (http://www.cisco.com/tac/caseopen ) is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer.
For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
To open a case 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 listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—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.
Priority 2 (P2)—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.
Priority 3 (P3)—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.
Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
http://www.cisco.com/go/iqmagazine
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_ protocol_journal.html
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the Related Documentation section.
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Posted: Thu Oct 16 12:18:23 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
