 Feedback
|
Table Of Contents
Release Notes for Cisco NAC Appliance,
Version 4.6(1)System and Hardware Requirements
Release 4.6(1) and Hardware Platform Support
Release 4.6(1) and Cisco NAC Profiler
Supported Switches for Cisco NAC Appliance
Cisco NAC Appliance Wireless OOB Support
VPN and Wireless Components Supported for Single Sign-On (SSO)
Additional Support Information
Release 4.6(1) Compatibility Matrix
Release 4.6(1) CAM/CAS Upgrade Compatibility Matrix
Release 4.6(1) Agent Upgrade Compatibility Matrix
Determining the Software Version
Enhancements in Release 4.6(1)
Posture Assessment Support for 64-Bit Windows Operating Systems
Agent Localization Support for "Double-Byte" Languages
Selective Application Privilege Support for Windows Operating Systems
Accessibility Support Via the JAWS Screen Reader Interface
Agent Log Recording and Retrieval
Support for EVDO Client Machines
Optimized Windows Operating System Support
Agent Configuration XML File Upload Enhancement
Cisco Log Packager Agent Log Compiler Application
Agent Upgrade Optional When Upgrading Cisco NAC Appliance
Cisco NAC Appliance Agent Reports Enhancement
Cisco NAC Windows Agent Version 4.6.2.113
Mac OS X Clean Access Agent Version 4.6.0.3
Cisco NAC Web Agent Version 4.6.0
Administrator Web Console Enhancements to Support Cisco NAC Agent
Supported AV/AS Product List Enhancements (Windows Version 78, Mac OS X Version 3)
Cisco NAC Appliance Supported AV/AS Product Lists
Supported Mac OS X AV/AS Product List Version Summary
Resolved Caveats - Release 4.6(1)
Resolved Caveats - Agent Version 4.6.2.113
New Installation of Release 4.6(1)
Changes for 4.6(1) Installation/Upgrade
Features That May Change With Upgrade
General Preparation for Upgrade
Upgrading from Customer-Supplied Hardware to Cisco NAC Appliance Hardware Platforms
Upgrade Instructions for Standalone Machines
Copy the Upgrade File to the CAS/CAM
Run Upgrade Script on the CAM/CAS
Upgrade Instructions for HA Pairs
Upgrading HA-CAM and HA-CAS Pairs
Known Issues for Cisco NAC Appliance
Known Issue with Mass DHCP Address Deletion
Known Issue for VPN SSO Following Upgrade to Release 4.5 and Later
Known Issues with Web Upgrade in Release 4.1(x) and Earlier
Known Issues with www.perfigo.com Root CA
Known Issue with Active HA CAM Web Console Following Failover
Known Issue with Upgrading CCA-3140 Appliance from Release 4.1(6)
Known Issue with NAC-3310 Based Appliances
Known Issues with NAC-3300 Series Appliances and Serial HA (Failover) Connection
Known Issues with Cisco 2200/4400 Wireless LAN Controllers (Airespace WLCs)
Known Issue for Windows Vista and IP Refresh/Renew
Known Issues for Windows Vista and Agent Stub
Use "No UI" or "Reduced UI" Installation Option
"Interactive Services Dialog Detection" and Uninstall
Known Issues with MSI Agent Installer
Known Issue with Windows 2000 Clean Access Agent/Local DB Authentication
Known Issue with Windows XP/2000 and Windows Script 5.6
CAM-CAS Shared Secret Mismatch Following New CAS Installation
Vista/IE 7 Certificate Revocation List
Windows Vista Agent Stub Installer Error
Agent Stub Upgrade and Uninstall Error
Clean Access Agent AV/AS Rule Troubleshooting
Generating Windows Installer Log Files for Agent Stub
Debug Logging for Cisco NAC Appliance Agents
Generate Windows Agent Debug Log
Generate Mac OS X Agent Debug Log
Recovering Root Password for CAM/CAS
Troubleshooting CAM/CAS Certificate Issues
Troubleshooting Switch Support Issues
Other Troubleshooting Information
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco NAC Appliance,
Version 4.6(1)
Revised: April 7, 2011, OL-19353-01Contents
These release notes provide late-breaking and cumulative release information for Cisco® NAC Appliance, Release 4.6(1). This document describes new features, changes to existing features, limitations and restrictions ("caveats"), upgrade instructions, and related information. These release notes supplement the Cisco NAC Appliance documentation included with the distribution. Read these release notes carefully and refer to the upgrade instructions prior to installing the software.
•
System and Hardware Requirements
•
•
•
•
Cisco NAC Appliance Releases
Note
System and Hardware Requirements
This section describes the following:
•
•
•
Licensing
You must obtain and install Cisco NAC Appliance product licenses for the Clean Access Manager (CAM) and Clean Access Server (CAS) in order for your deployment to function. Install the CAM product license in the CAM License Form to initially access the CAM web admin console. Once you can access the CAM web console, upload the additional CAM HA license or CAS license(s) into the CAM (under Administration > CCA Manager > Licensing) in order to add CASs to the CAM, including the Cisco NAC network module. An OOB CAS license must be present to access the "OOB Management" module of the CAM. The Licensing page displays the types of licenses present after they are added.
Note that both CAM and CAS product licenses are generated based on the eth0 MAC address of the CAM. For High Availability (HA) pairs, you must generate an additional CAM HA license based on the eth0 MAC addresses of both Primary and Secondary CAMs and install it on the CAM whether you are adding a CAM HA-pair or CAS HA-pair.
For complete details on service contract support, obtaining new and evaluation licenses, legacy licenses and RMA, refer to Cisco NAC Appliance Service Contract / Licensing Support.
Hardware Support
This section contains the following topics:
•
•
•
Release 4.6(1) and Hardware Platform Support
Cisco NAC Appliance Release 4.5 and later only supports and can only be installed on Cisco NAC Appliance platforms CCA-3140, NAC-3310, NAC-3350, NAC-3390, and Cisco NAC Network Module (NME-NAC-K9).
Note
Additionally, Cisco NAC Appliance Release 4.6(1) provides substantial changes and enhancements for product hardware support, installation and upgrade:
•
•
•
•
See also Features Optimized/Removed for additional information.
Cisco NAC Network Module
The Cisco NAC Network Module for Integrated Services Routers (NME-NAC-K9) is a next generation service module for the Cisco 2811, 2821, 2851, 3825, and 3845 Integrated Services Routers (ISRs) that is supported starting from Cisco NAC Appliance, Release 4.1(2) and later. The Cisco NAC network module has the same software features as the Clean Access Server on a NAC-3300 series appliance, with the exception of high availability. NME-NAC-K9 does not support failover from one module to another.
Note
For further details, including software installation instructions, refer to Getting Started with Cisco NAC Network Modules in Cisco Access Routers.
Note
Release 4.6(1) and Cisco NAC Profiler
Release 4.6(1) includes version 2.1.8-37 of the Cisco NAC Profiler Collector component that resides on Clean Access Server installations. When upgrading Clean Access Server appliances (standalone or HA) to release 4.6(1), the upgrade script will check the version of the Collector and only upgrade it if version 2.1.8-37 is not already installed.
Refer to the Release Notes for Cisco NAC Profiler for software compatibility matrixes and additional upgrade and product information.
Supported Switches for Cisco NAC Appliance
Cisco NAC Appliance Wireless OOB Support
Table 1 lists the Wireless LAN Controller platforms that Cisco NAC Appliance supports for the Wireless Out-of-Band feature. Table 2 lists the recommended IOS versions for the switches used with Cisco NAC Appliance, Release 4.6(1).
Note
Table 2 lists the IOS versions and switch platforms that are tested and known to work with the Wireless OOB feature in Release 4.6(1). If you encounter issues with WOOB support and are running a minimum IOS version listed as supported for your existing hardware platform in Switch Support for Cisco NAC Appliance, you may need to upgrade the IOS on your switch to the version listed in Table 2.
See Switch Support for Cisco NAC Appliance for complete details on:
•
•
•
•
VPN and Wireless Components Supported for Single Sign-On (SSO)
Table 3 lists VPN and wireless components supported for Single Sign-On (SSO) with Cisco NAC Appliance. Elements in the same row are compatible with each other.
Table 3 VPN and Wireless Components Supported By Cisco NAC Appliance For SSO
4.5 and later
Cisco WiSM Wireless Service Module for the Cisco Catalyst 6500 Series Switches
N/A
Cisco 2200/4400 Wireless LAN Controllers (Airespace WLCs)1
N/A
Cisco ASA 5500 Series Adaptive Security Appliances, Version 8.0(3)7 or later2
AnyConnect
Cisco ASA 5500 Series Adaptive Security Appliances, Version 7.2(0)81 or later
•
•
Cisco WebVPN Service Modules for Cisco Catalyst 6500 Series Switches and Cisco 7600 Series Routers
Cisco VPN 3000 Series Concentrators, Release 4.7
Cisco PIX Firewall
1 For additional details, see also Known Issues with Cisco 2200/4400 Wireless LAN Controllers (Airespace WLCs).
2 Release 4.5 and later supports existing AnyConnect clients accessing the network via Cisco ASA 5500 Series devices running release 8.0(3)7 or later. For more information, see the Release Notes for Cisco NAC Appliance, Version 4.1(3), and CSCsi75507.
Note
For further details, see the Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide, Release 4.6(1) and the Cisco NAC Appliance - Clean Access Server Installation and Configuration Guide, Release 4.6(1).
Additional Support Information
Refer to Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later for additional details related to Windows/Mac OS X/Web Agent support.
Refer to Supported Hardware and System Requirements for Cisco NAC Appliance (Cisco Clean Access) for additional information on Cisco NAC Appliance hardware platforms and support information for Cisco NAC Appliance 4.1(x) and earlier releases.
Software Compatibility
This section describes software compatibility for releases of Cisco NAC Appliance:
•
•
•
Release 4.6(1) Compatibility Matrix
Table 4 lists Cisco NAC Appliance Manager/Server/Agent compatibility per supported release. CAM/CAS/Agent versions displayed in the same row are compatible with one another. Cisco recommends that you synchronize your software images to match those shown as compatible in Table 4.
Table 4 Release 4.6(1) CAM/CAS/Agent Compatibility Matrix
4.6(1)
4.6(1)
4.6.2.113
(All languages)N/A
N/A
4.6.1.34
(Japanese and English only)4.6(1) 6
4.6(1)
4.6.2.113
4.6.0.3
4.6.0
4.6.1.34 7
4.5.1.0
4.5.0.0 7
4.5.0.0
4.1.3.0 8
4.1.8.0 8
4.1.6.0 8
4.1.3.0 8
4.1(3) and later
4.1(3) and later
4.6.2.113 9
4.6.0.3
4.6.0
1 Cisco NAC Appliance Release 4.5 and later only supports and can only be installed on Cisco NAC Appliance platforms CCA-3140, NAC-3310, NAC-3350, NAC-3390, and Cisco NAC Network Module (NME-NAC-K9). You cannot upgrade to or install release 4.6(1) on any other platform. See Hardware Support and Changes for 4.6(1) Installation/Upgrade for additional details.
2 Make sure that both CAM and CAS are of same version.
3 See Enhancements in Release 4.6(1) for details on each version of the Windows/Mac OS X/Web Agents.
4 "Localized Server" means localized text added to administrator-configurable fields in the CAM web console that present text to the user (e.g. Agent Requirement descriptions). Some server-generated error messages may still include English text.
5 When distributed from the CAM, the Cisco NAC Agent installation dialogs are automatically localized upon installation to the local client operating system. AV/AS international product names are also supported, however AV/AS rules/requirements themselves are not localized in Release 4.6(1). Refer to Cisco NAC Windows Agent Version 4.6.2.113 for the list of languages supported for Cisco NAC Agent localization. If you only upgrade to the latest version of the Cisco NAC Agent, and leave your CAM/CAS at release 4.5(1) or earlier, the Agent operates as an English-only entity—you cannot take advantage of the native operating system localization support available to Cisco NAC Agent users who are logging in to a 4.6(1) CAM/CAS network.
6 When upgrading the CAM from version 4.1(1) and earlier, Agent files are automatically upgraded to the latest Agent version packaged with the CAM software image (e.g. 4.6.2.113). When upgrading the CAM from release 4.1(2) and later, the script will prompt you whether or not to upgrade the Agent files to the latest version. This allows administrators to schedule the Agent upgrade separately from the CAM/CAS server upgrade. Cisco recommends upgrading to the latest 4.6.2.113 Agent version as soon as possible.
7 4.6.x.x Windows/Mac OS X Clean Access Agents are supported on 4.1(3) and later CAM/CAS releases for basic compatibility (login/logout) and AV/AS product support. The maximum available AV/AS support is based on the maximum version of the Clean Access Agent Setup or Patch (upgrade) file uploaded to the CAM as well as the maximum version of the Agent on the client. See Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later for details. For full 4.5 and later features (including Mac OS X posture assessment), the 4.5.0.0 or later Agent must be run with the appropriate 4.5 or later CAM/CAS.
8 CAM/CAS release 4.6(1) supports 4.1.3.0 and later Agents for basic compatibility (login/logout) and AV/AS product support. The maximum available AV/AS support is based on the maximum version of the Clean Access Agent Setup or Patch (upgrade) file uploaded to the CAM as well as the maximum version of the Agent on the client. See Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later for details. For full 4.5 and later features (including Mac OS X posture assessment), the 4.5.0.0 or later Agent must be run with the appropriate 4.5 or later CAM/CAS.
9 If you only upgrade to the latest version of the Cisco NAC Agent, and leave your CAM/CAS at release 4.5(1) or earlier, the Agent operates as an English-only entity—you cannot take advantage of the native operating system localization support available to Cisco NAC Agent users who are logging in to a 4.6(1) CAM/CAS network.
Release 4.6(1) CAM/CAS Upgrade Compatibility Matrix
Table 5 shows CAM/CAS upgrade compatibility. You can upgrade/migrate your CAM/CAS from the previous release(s) specified to the latest release shown in the same row. When you upgrade your system software, Cisco recommends you upgrade to the most current release available whenever possible.
Table 5 Release 4.6(1) CAM/CAS Upgrade Compatibility Matrix
4.5(x)
4.1(x)
4.0(x)4.6(1)
4.5(x)
4.1(x)
4.0(x)4.6(1)
1 Cisco NAC Appliance Release 4.5 and later only supports and can only be installed on Cisco NAC Appliance platforms CCA-3140, NAC-3310, NAC-3350, NAC-3390, and Cisco NAC Network Module (NME-NAC-K9). You cannot upgrade to or install release 4.6(1) on any other platform. See Hardware Support and Changes for 4.6(1) Installation/Upgrade for additional details.
2 The Clean Access Server is shipped with a default version of the Cisco NAC Profiler Collector. See Release 4.6(1) and Cisco NAC Profiler for details.
.
Release 4.6(1) Agent Upgrade Compatibility Matrix
Table 6 shows Clean Access Agent upgrade compatibility when upgrading existing versions of the persistent Agents on clients after CAM/CAS upgrade.
Note
Refer to Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later for additional details related to Windows/Mac OS X/Web Agent support.
Table 6 Release 4.6.2.113 Agent Upgrade Compatibility Matrix
4.6(1)
4.6(1)
4.6.0.3 5
1 See Enhancements in Release 4.6(1) for details on each version of the Windows/Mac OS X/Web Agent.
2 Auto-upgrade to the latest 4.6.x.x Agent is supported from any 4.0.0.0 and later Windows Agent and any 4.1.3.0 and later Mac OS X Agent. To upgrade earlier Mac OS X Agent versions, download the Agent via web login and run the Agent installation.
3 When upgrading the CAM from version 4.1(1) and earlier, Agent files are automatically upgraded to the latest Agent version packaged with the CAM software image (e.g. 4.6.2.113). When upgrading the CAM from release 4.1(2) and later, the script will prompt you whether or not to upgrade the Agent files to the latest version. This allows administrators to schedule the Agent upgrade separately from the CAM/CAS server upgrade. Cisco recommends upgrading to the latest 4.6.2.113 Agent version as soon as possible.
4 CAM/CAS release 4.6(1) supports 4.1.3.0 and later Agents for basic compatibility (login/logout) and AV/AS product support. The maximum available AV/AS support is based on the maximum version of the Clean Access Agent Setup or Patch (upgrade) file uploaded to the CAM as well as the maximum version of the Agent on the client. See Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later for details. For full 4.5 or later features (including Mac OS X posture assessment) and 4.5 or later AV/AS product support, the 4.5.0.0 or later Agent must be run with the appropriate 4.5 or later CAM/CAS.
5 4.6.x.x Clean Access Agents are supported on 4.1(3) and later CAM/CAS releases for basic compatibility (login/logout) and AV/AS product support (Windows only). The maximum available AV/AS support is based on the maximum version of the Clean Access Agent Setup or Patch (upgrade) file uploaded to the CAM as well as the maximum version of the Agent on the client. See Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later for details. For full 4.5 or later features (including Mac OS X posture assessment) and 4.5 or later AV/AS product support, the 4.5.0.0 or later Agent must be run with the appropriate 4.5 or later CAM/CAS.
6 Cisco NAC Appliance release 4.5 and later no longer supports Windows ME/98/NT client operating systems and you cannot install the Windows Clean Access Agent version 4.5.0.0+ to Windows ME/98/NT client machines.
7 For checks/rules/requirements, version 4.1.1.0 and later Windows Agents can detect "N" (European) versions of the Windows Vista operating system, but the CAM/CAS treat "N" versions of Vista as their US counterpart.
Determining the Software Version
Clean Access Manager (CAM) Version
•
•
Clean Access Server (CAS) Version
•
•
Administration > Software Upload | Current Version•
Cisco NAC Appliance Agent Version (Windows, Mac OS, Web Agent)
•
•
Cisco Clean Access Updates
•
New and Changed Information
This section describes enhancements added to the following releases of Cisco NAC Appliance for the Clean Access Manager and Clean Access Server.
•
Enhancements in Release 4.6(1)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Posture Assessment Support for 64-Bit Windows Operating Systems
Cisco NAC Agent version 4.6.2.113 can be installed and launched on 64-bit versions of Windows XP and Windows Vista, and can perform posture assessment and remediation on client machines. Earlier releases of Cisco NAC Appliance provided only authentication support for 64-bit client operating systems.
Agent Localization Support for "Double-Byte" Languages
Cisco NAC Agent version 4.6.2.113 introduces MultiByte Character Support (MBCS) for posture assessment and remediation operations on double-byte language client machines. Version 4.6.2.113 of the Cisco NAC Agent provides localization support for Agent login, remediation and user-facing dialogs and messages for the languages listed in Table 7.
Selective Application Privilege Support for Windows Operating Systems
In Cisco NAC Appliance Release 4.6(1), to more effectively integrate with the Windows Vista operating system, different functional elements of Cisco NAC Agent have different privilege levels to support Windows Vista User Account Control (UAC).
Accessibility Support Via the JAWS Screen Reader Interface
To provide Cisco NAC Agent support for visually-impaired users, the Cisco NAC Agent is compatible with the Microsoft Job Access with Speech (JAWS) screen reader. Client machines are required to have the JAWS software installed in order to enable and use this feature.
Note
Full UTF-8 Compliance
To help provide Cisco NAC Agent localization for "double-byte" languages like Japanese, Cisco NAC Appliance Release 4.6(1) offers features UTF-8 compliance. The Cisco NAC Agent, Clean Access Manager, and Clean Access Server components all feature UTF-8 capability to seamlessly communicate localized messages between the Agent on the client machine and the Cisco NAC Appliance network.
Note
Agent Log Recording and Retrieval
Starting from Cisco NAC Appliance 4.6(1), the Windows Cisco NAC Agent records and stores local login and operation events on the client machine in the C:\Documents and Settings\All Users\Application Data\Cisco\Cisco NAC Agent\logs directory. After the first Cisco NAC Agent login session, two files reside in this directory: one backup file from the previous login session and one new file containing login and operation information from the current session. Each log file in the directory is limited to a maximum length, determined by the LogFileSize XML value in the Agent configuration file setting (see Agent Configuration XML File Upload Enhancement). The default file size is 5MB. If the log file for the current Cisco NAC Agent session grows beyond the specified file size, the first segment of Agent login and operation information automatically becomes the "backup" file in the directory and the Agent continues to record the latest entries in the current session file.
Note
Support for EVDO Client Machines
Cisco NAC Agent version 4.6.2.113 supports Windows client machines connected to the network via an Evolution Data Optimized (EVDO) connection. Traditionally, Cisco NAC Appliance could not authenticate this type of client connection, because there is no MAC address associated with client machines connecting via EVDO.
For more information, see CSCsu30467.
Optimized Windows Operating System Support
The Cisco NAC Agent version 4.6.2.113 supports the following Windows operating systems:
•
•
•
•
The Agent does not support the following Windows Operating Systems:
•
•
•
•
•
•
Agent Configuration XML File Upload Enhancement
Note
Cisco NAC Appliance Release 4.6(1) enables administrators to construct and distribute an optional Agent configuration XML file (named NACAgentCFG.xml and residing in the Agent install directory) that specifies parameter settings for the Windows Cisco NAC Agent. This XML configuration file method of setting up Agents on client machines replaces the previous Clean Access Agent configuration schema requiring Windows registry setting manipulation for custom parameters. If you previously employed Windows registry settings to adjust Clean Access Agent behavior on client machines, you must specify the same settings in the XML Agent configuration file to preserve Agent behavior using the Cisco NAC Agent.
The XML Agent configuration file is not required for Cisco NAC Agent distribution, but can be used to customize login and operation settings on the client machine. If no custom XML file is configured and installed on the client machine, the Agent creates a default XML file and uses that file to specify login and operational settings until another file is installed that overwrites those default settings.
Customization
When configuring a customized Agent configuration XML file, the administrator can choose to customize one or more (or all) settings and specify whether they should merge with or overwrite existing XML configuration settings on the client machine. In addition to providing specific values for the parameters defined below, the administrator can use the "mode" attribute in conjunction with the target XML parameter to direct the Agent to "merge" the setting with existing parameters, or simply "overwrite" existing settings.
•
•
For example, a <Locale mode="merge">German</Locale> entry in an Agent configuration XML file instructs the Agent not to change any previously-existing Locale setting on the client machine (merge instead of overwrite), but if no setting currently exists, then make the localization language German. If the example entry reads <Locale mode="overwrite">German</Locale>, then the new localized language setting for the Agent is German, regardless of whether or not any previous setting exists.
The settings available to configure for version 4.6.2.113 the Cisco NAC Agent are:
XML Agent Configuration File Parameters Replacing Previous Windows Registry Attributes
•
Note
•
•
•
•
•
•
•
New XML Agent Configuration File Parameters
•
•
•
•
•
•
•
•
•
•
For more information on these settings and their respective default values and allowable ranges, see the Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide, Release 4.6(1).
Automatic Agent Configuration XML File Updates
In Cisco NAC Appliance Release 4.6(1), the Cisco NAC Agent authentication process now includes an explicit request for Agent configuration XML file updates following SWISS discovery and negotiation. If a new XML configuration file exists at the time the Cisco NAC Agent performs authentication with Cisco NAC Appliance, the new XML file is automatically uploaded to the client machine and the settings defined in the file are automatically incorporated in Cisco NAC Agent operation according to the XML parameters configured and whether or not they are to overwrite or merge with existing settings on the client machine.
This enhancement affects the following page of the CAM administrator web console:
•
Cisco Log Packager Agent Log Compiler Application
Cisco NAC Appliance Release 4.6(1) introduces a new utility, the Cisco Log Packager, that users can launch on client machines to compile and view Agent log information to help diagnose and/or troubleshoot session login and operation issues. Once the Cisco NAC Agent is installed, users launch the Cisco Log Packager by navigating to the Windows Start menu command at Start > Program Files > Cisco > Client Utilities > Cisco Log Packager.
The Cisco Log Packager compiles several types of logs to enable Cisco NAC Appliance system administrators or other technical assistance personnel to easily locate and analyze critical information:
Table 8 Cisco Log Packager Files
CiscoSupportReportLog.txt
This text file contains client machine system information, including CPU usage and memory allocation.
ipinfo.log
This log file contains network configuration and network connection status, including client machine IP interface status, IP statistics, and the client ARP table.
NACAgentLogPlugin.log
This user-inaccessible log is one of the modules in the LogPacker component that calls the NACAgentDiags function to generate the NACAgentDiagnosticLog.txt log report.
NACAgentDiagnosticsLog.txt
This user-inaccessible text file contains diagnostic messages used to help debug AV issues.
NACAgentDiagsLogMessages.txt
This text file contains other regular log messages not used in the diagnostics output.
NACAgentLogCurrent.log
This is an encrypted log file that contains the current Cisco NAC Agent messages from the active session and is used primarily to help debug Cisco NAC Agent issues. When the system reboots or services have been restarted, the existing NACAgentLogOld.log is erased, the active NACAgentLogCurrent.log becomes the new NACAgentLogOld.log, and a new NACAgentLogCurrent.log is created.
Note
NACAgentLogOld.log
This is an encrypted log file that contains output from the previous active Cisco NAC Agent session and is also used to help debug Cisco NAC Agent issues. This file is created in one of two ways:
•
•
Note
Agent Backward-Compatibility
Cisco NAC Appliance release 4.6(1) offers backward compatibility with Windows Clean Access Agent versions 4.1.3.0 through 4.5.1.0 in addition to the most recent Agent versions available with the latest software release. Administrators can upload earlier versions of the Clean Access Agent and make them available to end users who log into Cisco NAC Appliance.
This feature also allows administrators the option to upgrade their Cisco NAC Appliance system to the latest release and "phase in" Agent upgrades for large client machine installations, rather than force Agent upgrade all at once.
Note
Agent Upgrade Optional When Upgrading Cisco NAC Appliance
When upgrading to Cisco NAC Appliance Release 4.6(1), the administrator can choose to retain their existing client version(s) instead of automatically upgrading the Agent to the version available with the latest software release.
Cisco NAC Appliance Agent Reports Enhancement
When the Cisco NAC Agent performs posture assessment on client machines with 64-bit operating systems, the Agent reports in the CAM web console now accurately display the 64-bit (as opposed to 32-bit) nature of the operating system for the particular client machine.
Note
Cisco NAC Windows Agent Version 4.6.2.113
The Cisco NAC Agent for Windows systems is a completely redesigned and enhanced client for Cisco NAC Appliance. It is intended to replace the Cisco Clean Access Agent starting from Release 4.6(1) and later. Refer to Release 4.6(1) Compatibility Matrix for additional compatibility details.
The Cisco NAC Agent version 4.6.2.113 includes the following new features for Cisco NAC Appliance Release 4.6(1):
•
•
•
•
•
•
•
Mac OS X Clean Access Agent Version 4.6.0.3
To help provide Mac OS X Clean Access Agent localization for "double-byte" languages like Japanese, Cisco NAC Appliance Release 4.6(1) offers features UTF-8 compliance. The Mac OS X Clean Access Agent, Clean Access Manager, and Clean Access Server components all feature UTF-8 capability to seamlessly communicate localized messages between the Agent on the client machine and the Cisco NAC Appliance network.
Cisco NAC Web Agent Version 4.6.0
There are no changes to the Cisco NAC Web Agent in Cisco NAC Appliance Release 4.6(1) except that the Cisco NAC Web Agent version is updated to version 4.6.0.
Administrator Web Console Enhancements to Support Cisco NAC Agent
CAM web console elements, including the Device Management > Clean Access > Clean Access Agent > Distribution and Device Management > Clean Access > General Setup > Agent Login pages, are updated to replace the Windows "Clean Access Agent" text with "NAC Agent." (Mac OS X Clean Access Agent text remains unchanged.)
Features Optimized/Removed
Cisco NAC Appliance Release 4.6(1) no longer features both a Clean Access Agent Installation package and Agent Upgrade (Patch) package. All Clean Access Agent updates are performed as "re-installations" using the full Clean Access Agent installer package.
Supported AV/AS Product List Enhancements (Windows Version 78, Mac OS X Version 3)
See Cisco NAC Appliance Supported AV/AS Product Lists for the latest AV/AS product charts.
Cisco NAC Appliance Supported AV/AS Product Lists
The Cisco NAC Appliance Supported AV/AS Product List is a versioned XML file distributed from a centralized update server and downloaded to the Clean Access Manager via Device Management > Clean Access > Updates > Update. It provides the most current matrix of supported antivirus (AV) and anti-spyware (AS) vendors and products per version of the Clean Access Agent, and is used to populate AV/AS Rules and AV/AS Definition Update requirements for Clean Access Agents that support posture assessment/remediation.
You can access AV and AS product support information from the CAM web console under Device Management > Clean Access > Clean Access Agent > Rules > AV/AS Support Info. For convenience, this section also provides the following summary and product charts. The charts list which product versions support virus or spyware definition checks and automatic update of client virus/spyware definition files via the user clicking the Update button on the Agent.
Windows Vista/XP/2000
For Windows Vista/XP/2000 AV/AS support information, see the Cisco NAC Appliance Release 4.6(1) Supported Windows Products document optimized for UTF-8 character display.
Mac OS X
•
Note
Note
Note
Note that Clean Access works in tandem with the installation schemes and mechanisms provided by supported AV/AS vendors. In the case of unforeseen changes to underlying mechanisms for AV/AS products by vendors, the Cisco NAC Appliance team will update the Supported AV/AS Product List and/or Clean Access Agent in the timeliest manner possible in order to support the new AV/AS product changes. In the meantime, administrators can always use the "custom" rule workaround for the AV/AS product (such as pc_checks/pr_ rules) and configure the requirement for "Any selected rule succeeds."Refer to Enhancements in Release 4.6(1) for additional details on Agent versions in this release.
Supported Mac OS X AV/AS Product List Version Summary
Table 9 summarizes enhancements made for each version update of the Supported Antivirus/Antispyware Product List for the Mac OS X Clean Access Agent. See Mac OS X AV Support Chart and Mac OS X AS Support Chart for details.
Mac OS X AV Support Chart
Table 10 lists Mac OS X Supported AV Products for release 4.6(1) of the Cisco NAC Appliance software.
Table 10 Mac OS X Antivirus Product Support Chart
Version 3, 4.6.0.3 Mac OS X Agent, CAM/CAS Release 4.6(1)
(Minimum Agent Version Needed)1avast! Antivirus
2.x
yes (4.5.0.0)
yes (4.5.0.0)
-
clamXav
0.x
yes (4.5.0.0)
yes (4.5.0.0)
yes
ClamXav
1.x
yes (4.5.0.0)
yes (4.5.0.0)
yes
eTrust Antivirus
7.x
yes (4.5.0.0)
yes (4.5.0.0)
-
eTrust ITM Agent
8.x
yes (4.5.0.0)
yes (4.5.0.0)
-
VirusBarrier X
10.x
yes (4.5.0.0)
yes (4.5.0.0)
-
VirusBarrier X4
10.4.x
yes (4.5.0.0)
yes (4.5.0.0)
-
VirusBarrier X5
10.5.x
yes (4.5.0.0)
-
-
Virex 7.2
7.2.x
yes (4.5.0.0)
yes (4.5.0.0)
-
Virex 7.5
7.5.x
yes (4.5.0.0)
yes (4.5.0.0)
-
Virex 7.7
7.7.x
yes (4.5.0.0)
yes (4.5.0.0)
-
VirusScan
8.5.x
yes (4.5.0.0)
yes (4.5.0.0)
-
VirusScan
8.6.x
yes (4.5.0.0)
yes (4.5.0.0)
-
Sophos Anti-Virus
4.x
yes (4.5.0.0)
yes (4.5.0.0)
-
Norton AntiVirus
10.x
yes (4.5.0.0)
yes (4.5.0.0)
-
Norton AntiVirus
11.x
yes (4.5.0.0)
yes (4.5.0.0)
-
Norton AntiVirus
8.x
yes (4.5.0.0)
yes (4.5.0.0)
-
Norton AntiVirus
9.x
yes (4.5.0.0)
yes (4.5.0.0)
-
Trend Micro Security for Macintosh
3.x
yes (4.5.0.0)
yes (4.5.0.0)
-
1 "Yes" in the AV Checks Supported columns indicates the Agent supports the AV Rule check for the product starting from the version of the Agent listed in parentheses (CAM automatically determines whether to use Def Version or Def Date for the check).
2 The Live Update column indicates whether the Agent supports live update for the product via the manual Agent Remediate button (configured by AV Definition Update requirement type). For products that support "Live Update," the Agent launches the update mechanism of the AV product when the Remediate button is clicked. For products that do not support this feature, administrators can configure a different requirement type (such as "Local Check") to present alternate update instructions to the user.
Mac OS X AS Support Chart
Table 11 lists Supported Mac OS X Antispyware Products for release 4.6(1) of the Cisco NAC Appliance software.
Table 11 Mac OS X Antispyware Product Support Chart
Version 3, 4.6.0.3 Mac OS X Agent/CAM/CAS Release 4.6(1)
(Minimum Agent Version Needed)1MacScan
2.x
yes (4.5.0.0)
yes (4.5.0.0)
-
1 "Yes" in the AS Checks Supported columns indicates the Agent supports the AS Rule check for the product starting from the version of the Agent listed in parentheses (CAM automatically determines whether to use Def Version or Def Date for the check).
2 The Live Update column indicates whether the Agent supports live update for the product via the manual Agent Remediate button (configured by AS Definition Update requirement type). For products that support "Live Update," the Agent launches the update mechanism of the AS product when the Remediate button is clicked. For products that do not support this feature, administrators can configure a different requirement type (such as "Local Check") to present alternate update instructions to the user.
Caveats
This section describes the following caveats:
•
•
•
Note
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.do
Open Caveats - Release 4.6(1)
Note
Table 12 List of Open Caveats (Sheet 1 of 29)
CSCsd03509
No
The Time Servers setting is not updated in HA-Standby CAM web console
After updating the "Time Servers" setting in HA-Primary CAM, the counterpart "Time Servers" setting for the HA-Standby CAM does not get updated in the web console even though the "Time Servers" setting is updated in the HA-Standby CAM database.
CSCsg07369
No
Incorrect "IP lease total" displayed on editing manually created subnets
Steps to reproduce:
1.
2.
3.
4.
The issue is judged to be cosmetic and does not affect DHCP functionality.
CSCsg66511
No
Configuring HA-failover synchronization settings on Secondary CAS takes an extremely long time
Once you have configured the Secondary CAS HA attributes and click Update, it can take around 3 minutes for the browser to get the response from the server. (Configuring HA-failover synchronization on the Primary CAS is nearly instantaneous.)
CSCsh77730
No
Clean Access Agent locks up when greyed out OK button is pressed
The Clean Access Agent locks up when the client machine refreshes its IP address. This only occurs when doing an IP release/renew, so the CAS must be in an OOB setup.
If the Automatically close login success screen after <x> secs option is enabled and the duration set to 0 (instantaneous) in the Clean Access > General Setup > Agent Login page and the user clicks on the greyed out OK button while the IP address is refreshing, the Clean Access Agent locks up after refreshing the IP address. The IP address is refreshed and everything else on the client machine works, but the user cannot close the Clean Access Agent without exiting via the system tray icon, thus "killing" the Agent process.
Workaround
CSCsi07595
No
DST fix will not take effect if generic MST, EST, HST, etc. options are specified
Due to a Java runtime implementation, the DST 2007 fix does not take effect for Cisco NAC Appliances that are using generic time zone options such as "EST," "HST," or "MST" on the CAM/CAS UI time settings.
Workaround
Note
CSCsj16366
No
Time sync on CAS
The CAS network module (NME-NAC-K9) appears as "not connected" in CAM web console after a router/rack power outage.
This issue has been observed on a NME-NAC-K9 running Cisco NAC Appliance release 4.5(1) installed in a Cisco 2821 ISR in Out-of-Band Real-IP Gateway mode. In addition, the CAM returns the following event log message:
"AutoConnectManager failed relinking CAM with CAS-i.p.add.rs."
Note
Workaround
CSCsk55292
No
Agent not added to system tray during boot up
When the Agent is installed on a Windows client, the Start menu is updated and Windows tries to contact AD (in some cases where the AD credentials are expired) to refresh the Start menu.
Due to the fact that the client machine is still in the Unauthenticated role, AD cannot be contacted and an approximately 60 second timeout ensues, during which the Windows taskbar elements (Start menu, System Tray, and Task Bar) are locked. As a result, the Agent displays a "Failed to add Clean Access Agent icon to taskbar status area" error message.
Workaround
•
•
CSCsl13782
No
Microsoft Internet Explorer 7.0 browser pop-ups on Windows Vista launched from the Summary Report appear behind the Summary Report window
This is also seen when you click on the Policy link in the Policy window. This issue appears on Vista Ultimate and Vista Home, but is not seen with Firefox or on Internet Explorer versions running in Windows 2000 or Windows XP.
Note
CSCsl17379
No
Multiple Clean Access Agent pop-ups with Multi NIC in L2 VGW OOB role-based VLAN
The user sees multiple Clean Access Agent login dialogs with two or more active NICs on the same client machine pointing to the Unauthenticated network access point (eth1 IP address).
After the first Clean Access Agent pops up and the user logs in, a second Agent login dialog pops up. If the user logs in to this additional Agent instantiation there are now two entries for the same system with both MAC addresses in the CAM's Certified Device List and Online Users List.
Workaround
CSCsl40626
No
Cisco NAC Web Agent should handle certificate revocation dialogs similar to Clean Access Agent
Upon logging in via the Cisco NAC Web Agent (with certificate revocation turned on or with Norton 360 installed), the user is presented with a "Revocation information for the security certificate for this site is not available. Do you want to proceed?" dialog box several times (approximately 40 to 50 times). If the user clicks Yes to proceed enough times, the Web Agent fails to login and reports "You will not be allowed to access the network due to internal error. Please contact your administrator." back to the user.
CSCsl40812
No
The Refresh Windows domain group policy after login option is not functioning for Cisco NAC Web Agent
(It is working fine with the Clean Access Agent.)
This scenario was tested configuring a GPO policy for a Microsoft Internet Explorer browser title. The browser was not refreshed as expected after login in using the Web Agent.
CSCsl75403
No
Mac OS X Agent does not detect VPN interface-fails MAC filters/L3 strict mode
This caveat addresses two issues:
1.
2.
With MacOS X client machines, there are no separate interfaces created once the client machine successfully connects to the VPN concentrator. The implementation is different on Windows where a separate interface gets created having an IP address assigned by the VPN concentrator.
Workaround
•
•
Note
CSCsl77701
No
Network Error dialog appears during CAS HA failover
When a user is logged in as ADSSO user on CAS HA system and the CAS experiences a failover event, the user sees is a pop-up message reading, "Network Error! Detail: The network cannot be accessed because your machine cannot connect to the default gateway. Please release/renew IP address manually."
This is not an error message and the user is still logged in to the system. The user simply needs to click on the Close button to continue normal operation.
CSCsl88429
No
User sees Invalid session after pressing [F5] following Temporary role time-out
When a user presses [F5] or [Refresh] to refresh the web page after the Agent Temporary role access timer has expired, the user sees an "Invalid" session message. If the user then attempts to navigate to the originally requested web address, they are prompted with the web login page again and are able to log in.
CSCsl88627
No
Description of removesubnet has "updatesubnet" in op field
The removesubnet API function description has "updatesubnet" listed in its operations field. The description should read "removesubnet."
CSCsm20254
No
CAS duplicates HSRP packets with Cisco NAC Profiler Collector Modules enabled.
Symptom HSRP duplicate frames are sent by CAS in Real-IP Gateway with Collector modules enabled. This causes HSRP issues and the default gateway to go down.
Conditions
Workaround
CSCsm20655
No
Can not do a minor upgrade for Clean Access Agent from MSI package.
When CCAAgent.msi is used and the Clean Access Agent is upgraded to a minor version (e.g. 4.1.2.1 to 4.1.2.2) the following error message will be displayed:
"Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel."
This issue occurs because the Windows Installer uses only the first three fields of the product version. When a fourth field is included in the product version, the installer ignores the fourth field. For details refer to http://msdn2.microsoft.com/en-us/library/aa370859(VS.85).aspx
Workaround
CSCsm25788
No
Avast 4.7 showing as not up to date with Cisco NAC Appliance Release 4.1(3)
User is told that Avast needs to be updated, but shows as up to date. This occurs when user is running Avast 4.7 and the Agent version is 4.1.3.0 or 4.1.3.1
Workaround
CSCsm61077
No
ActiveX fails to perform IP refresh on Windows Vista with User Account Control (UAC) turned on.
When logged in as a machine admin on Vista and using web login with IP refresh configured, IP address refresh/renew via ActiveX or Java will fail due to the fact that IE does not run as an elevated application and Vista requires elevated privileges to release and renew an IP address.
Workaround
1.
2.
3.
This is a limitation of the Windows Vista OS.Alternatively, the Cisco NAC Web Agent can be used with no posture requirements enabled.
See also Known Issue for Windows Vista and IP Refresh/Renew.
CSCso15754
No
The ClamXAV live update feature may not work the first time if a "failed" ClamXAV installation requirement immediately precedes the live update in the Mac OS X Assessment Report remediation window
If both a ClamXAV Link Distribution and a ClamXAV live update requirement are configured for Mac OS X client remediation, and the installation requirement appears right before the live definition update, then the ClamXAV live update may fail because as the installation process completes, the live update process begins and does not have a chance to read the updated ClamXAV version before launching. Therefore, if the timing is not right, users may have already started the live update while the actual ClamXAV application update tool is still copying onto the client machine.
Workaround
CSCso49473
No
SEVERE: javax.naming.CommunicationException causes no provider list
Configuration: ADSSO with LDAP Lookup
If the LDAP connection to AD drops because the lookup takes a long time or the route is lost suddenly, the Agent does not receive the list of auth providers so the user is presented with a blank provider list.
Symptom: The dropdown list of authentication providers is blank.
Conditions: LDAP server fails to respond due to network connectivity failure or a long directory search. The failure must occur after communication to the LDAP server has begun.
Workaround: None
Note
CSCso50613
No
Mac OS X Agent DHCP refresh fails if dhcp_refresh file does not exist
DHCP refresh will fail with no notice (to the user or to the logs) if the dhcp_refresh file does not exist. The dhcp_refresh tool is required for all versions of Mac OS X Agents, so it always fails if the dhcp_refresh tool is missing regardless the Mac OS version.
Workaround
1.
2.
3.
CSCso61317
No
When LDAP lookup fails for an AD SSO user, the Provider list in the Agent dialog is empty
Scenario 1
AD SSO configured with LDAP lookup
When the LDAP lookup fails for the user (some misconfiguration or not able to reach the right server to find the user), the Agent displays a login window without a Provider list. This happens because the user has already passed the login stage, but has failed the lookup stage.
Scenario 2 (less common)
The user is logged in to a machine that is not part of the domain, but the user does have an AD account.
Steps that occur:
1.
2.
3.
4.
Note
CSCsr50995
No
Agent doesn't detect Zone Alarm Security definitions correctly
Symptom: User fails posture assessment when checking for AV definitions for Zone Alarm Security Suite 7.0.
Conditions: This occurs using either the Any AV check or the Checkpoint Any check.
Workaround
CSCsr52953
No
RMI error messages periodically appear for deleted and/or unauthorized CASs in CAM event logs
Clean Access Servers connected to a CAM can periodically appear as "deleted" or "unauthorized" in the CAM event logs even though the CAS is functioning properly and has not experienced any connection issues with the Clean Access Manager. Error message examples are:
•
•
Workaround
•
•
CSCsr61106
No
Cannot upgrade CAS via CAM's web UI
An HTTP status 500 error message occurs stating "java.lang.OutofMemoryError" when upgrading the CAS via the CAM's web user interface if the CAM's memory is less than 1GB, or during CAS software upgrade via the CAM's web user interface using 4.5.0 upgrade package.
This problem is seen with non-Cisco hardware with only 512MB memory installed; i.e. Dell's 750, 850, or 860.
With 4.5.0, the problem is seen with all Cisco appliances including NAC-3140, NAC-3310, NAC-3350 & NAC-3390.
Workaround
CSCsr90712
No
Symantec Antivirus delays Clean Access Agent startup
The Agent takes a long time to pop up on a client machine with real-time antivirus scanning enabled and operating.
Workaround
Exclude the Clean Access Agent AV411 directory from Symantec Antivirus scanning. See http://service1.symantec.com/support/ent-security.nsf/docid/2002092413394848.
Note
For Vista, refer to http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008111414031848.
CSCsr95757
No
CAM intermittently stops processing SNMP MAC notification traps from the switch
This issue can occur on different edge switches. Once the problem is present, no further SNMP MAC notification traps are processed from the CAM for the switch in question.
Note
Workaround
service perfigo stopservice perfigo startThe CAM immediately starts processing the SNMP MAC notification traps from the problem switch(es).
Note
CSCsu47350
No
Invalid version number displayed in CAM backup snapshot web page
When the administrator navigates to another page in the CAM web console during the backup snapshot process, the resulting snapshot version number is invalid.
CSCsu63247
No
DHCP IP refresh not working for some Fedora core 8 client machines
DHCP IP refresh does not work on Fedora core 8 clients logging in to a Layer 3 Real-IP Gateway CAS using the current version of the Java applet. As a result, Fedora core8 clients must use web login to gain access to the Cisco NAC Appliance network.
Note
CSCsu63619
No
Out-of-Band switch port information from OUL/CDL missing upon login after upgrade
OOB switch port information in Online Users List/Certified Devices List is missing upon login after upgrading to release 4.5.
This issue occurs when the client machine has not been disconnected from the network (has not generated a MAC notification trap from the switch), and logs into the OOB network after upgrade.
Workaround
Note
CSCsu69247
No
ERROR: File type requirements does not exist
During CD installation of Cisco NAC Appliance Release 4.5, users can see the following error message in the nac_manager.log file:
"2008-09-21 19:25:55.592 -0700 ERROR com.perfigo.wlan.web.admin.DMSoftwareManager - DMSM syncDMSoftware: Directory('/perfigo/control/tomcat/webapps/packages/') for file type requirements does not exist"
This is a benign error message related to webapps packages that have been relocated in the installation script and has no impact on image installation.
CSCsu78379
No
Bandwidth settings for Receiver CAM roles should not change after Policy Sync
Steps to reproduce:
1.
2.
3.
4.
5.
6.
Note
CSCsu84848
No
CAM should set the switch port to Authentication VLAN before removing from OUL and DCL
The CAM should set the switch port to the Authentication VLAN before removing the user from Online Users List and Discovered Client List when the Switch or WLC entry is deleted from the CAM.
Workaround
CSCsu84977
No
CAS: ERROR /proc/click/intern_filter_group/failsafe
The following error message can appear to users during CD installation of Cisco NAC Appliance release 4.5 in Clean Access Servers:
"com.perfigo.wlan.jmx.Shell - /proc/click/intern_filter_group/failsafe (No such file or directory)"
This error message is related to a recently-removed file failsafe and has no impact on CD installation.
CSCsu88594
No
Removal of www.perfigo.com Root CA from GUI
The www.perfigo.com Root CA should be removed from the GUI.
With the default configuration there is no CA certificate button to offer on the web (or user) login page. The Cisco NAC Appliance administrator must configure user page content and specify whether or not to offer the Root CA along with its content from the dropdown menu (either the www.perfigo.com CA certificate or an imported third-party CA certificate—the default choice is the www.perfigo.com CA).
Workaround
CSCsu88796
No
CAM upgrade: Error message in 4.1(3)-to-4.5 upgrade details log
When upgrading the Clean Access Manager from release 4.1(3) to 4.5, users may see a benign "scriplet failed" error message listed in the upgrade details log file. This error message has no impact on upgrade to release 4.5.
CSCsu89385
No
"not a symbolic link" error message in 4.1(3)-to-4.5 CAS upgrade details log
When administrators upgrade Clean Access Servers from release 4.1(3) to release 4.5, they may see a number of "not a symbolic link" error messages in the upgrade details log. These error messages have no effect on the CAS upgrade.
Note
CSCsv18261
No
HA Failover database sync times out in event log after reboot
In Cisco NAC Appliance release 4.5, the CAM HA database copy function times out when the active CAM fails over and becomes the standby CAM. (Event log entries show that the database copy function times out.) This situation arises when the inactive CAM comes up and attempts to copy the database from the active CAM, but the database is still locked by the [now standby] CAM. This issue is not seen during normal operation and database sync because the entries are copied in real time.
Note
CSCsv18995
No
Three requirement types allow administrators to select single Windows XP/Vista operating systems when "All" is checked
When creating a new Windows Update, Launch programs, and/or Windows Server Update Services (WSUS) requirement type, and checking the "Windows XP (All)" or "Windows Vista (All)" options, the individual OS options are also still selectable (although they should not be).
Note
There is no known workaround for this issue
CSCsv20270
No
Conflicting CAM's eth1 HA heartbeat address with 4.5.0 after upgrade
The perfigo service cannot be started on the standby CAM because both the eth1 interface of HA CAMs have the same IP address: either 192.168.0.253 or 192.168.0.254.
This happens in an HA setup when one of the CAMs is upgraded from release 4.0(x) to 4.5 and the other CAM is fresh CD installed.
Workaround
CSCsv22418
No
CAS service IP not reachable after standby reboot due to race condition
The Active CAS's service IP become unreachable after standby CAS reboot.
In a rare race condition, the standby CAS temporarily becomes active for very short period of time after reboot.
Workaround
1.
2.
CSCsv78301
No
VPN SSO login does not work with VPN in managed subnet after upgrade to Cisco NAC Appliance release 4.5
Prior to release 4.5, the Clean Access Server associates the client with the VPN IP address and VPN Concentrator's MAC address after the first login. From there, the SWISS protocol only checks the IP address from the Agent and reports back to the Agent that the client is logged in (regardless of whether the client is connected via Layer 2 or Layer 3).
In release 4.5, the SWISS protocol checks the MAC address for Layer 2 clients, but the MAC address reported by the Agent (which is the real client MAC address) is different from the one the CAS gets for the client (the VPN concentrator MAC address). As a result, the SWISS protocol tells the Agent that the client machine is not logged in (due to the different MAC addresses recorded) and the Agent launches the login dialog repeatedly, never able to complete login.
Workaround
CSCsv92867
No
DB conversion tool (Latin1 to UTF8)-iconv cannot work with † format
Release 4.5 and earlier Clean Access Managers with foreign characters in the database cannot be upgraded to release 4.6(1).
Workaround
•
•
CSCsw39262
No
Agent cannot be launched when switching between users in Vista
The Cisco NAC Agent does not support Windows Fast User Switching. The effect is that the primary user is the only user that:
•
•
•
Note
Workaround
CSCsw45596
No
Username text box should be restricted with max no of characters
The Username text box is presently taking the characters such that the total size is ~5kb. It is better to have the upper bound for the Username text box to hold the number of characters that it can take.
CSCsw67476
No
Mac OS X Agent upgrade cannot be restarted once stopped
User is not able to log in again (no agent screen or icon available) when they cancel the Mac OS X Agent upgrade process.
Note
Workaround
CSCsw88911
No
Mac Agent freezes on login dialog, but remains operational
The tray icon of a Mac OS X Agent logged into a Cisco NAC Appliance OOB deployment shows Click - Focus then Click again and is hung (looks like logging in).
Workaround
CSCsw89027
No
Mac OS X Agent logs can grow too large in debug and do not clean up
When Agent logging is set to "Defect", Mac OS X Agent logs grow too large.
Workaround
CSCsx03338
No
HTTP packet to a host using reversed IP address after connection on Mac OS X client
The Mac Agent sends a packet to UDP port 80 to the reversed IP address of the client's default gateway every 5 seconds.
Note
Workaround
CSCsx05054
No
DHCP does not work with IGNORE fallback policy and CAS Failover
If CAS Fallback policy is set to IGNORE and the CAM becomes unreachable from CAS, the CAS blocks all traffic and CAS DHCP stops working.
Workaround
CSCsx05141
No
Clients cannot get IP addresses from CAS DHCP relay agent in CAS fail-open with CAS fallback scenario
Steps to reproduce this issue:
1.
2.
3.
4.
5.
Even though the administrator can see dhcrelay functioning, clients are now unable to get IP addresses through new Active CAS.
CSCsx18496
No
Cisco Log Packager crashes on XP Tablet PC with Restricted User credentials
CSCsx25557
No
NOD32 3.x Def date is not recognized by Clean Access Agent
Note
Note
CSCsx27857
No
With session timer disabled for the Agent Temporary role, version 4.6.0.3 of the Mac Agent times out
If the Temporary role timer disabled on the CAM, the Mac Agent times out right away.
Note
CSCsx29191
No
Mac OS X Agent has no `APPLE'+TAB presence
When using the Mac OS X Agent, the GUI focus can get lost and is hard to regain. This issue was observed during upgrade.
Workaround
CSCsx35438
No
Clean Access Manager read timeout reached when deleting many DHCP IPs at once
After upgrading to or installing release 4.1(8) and deleting hundreds of DHCP IPs at once, the Clean Access Server becomes unmanageable. This issue affects Clean Access Servers configured as a DHCP server on which the administrator tries to delete more than 800 DHCP IPs at once.
Workaround
CSCsx35911
No
Mac OS X Agent does not pop up for login and click-focus does not get user's attention
When the user moves from a non-Cisco NAC Appliance network to a Cisco NAC Appliance network, the Agent login dialog does not automatically appear. Click-focus can resolve the issue, but the is not generally obvious to the user. The result of this issue is that users would likely be stuck in the authentication network and/or assigned to a restricted role for the duration of their session.
Workaround
CSCsx37073
No
Cisco NAC Agent does not pop-up if authentication server name is \\
Steps to reproduce:
1.
2.
3.
4.
5.
6.
7.
Repeat the above steps with authentication server named "myKerberos" instead of \\. The CAM returns a "Clean Access Server is not properly configured. Please contact your administrator if the problem persists" error message.
Workaround
CSCsx45051
No
Agent may proceed with AV/AS auto remediation while it's not supported
For an AV/AS Definition Update Requirement Type with Automatic Remediation Type and Antivirus/Anti-Spyware Vendor Name configured as ANY, when the client fails the requirement, the Agent should automatically launch the AV (or AS) update on the AV product for which the Agent supports live update. If live update is not supported, the Agent should prompt the user to perform manual remediation. With this issue, the Agent may proceed with auto remediation on a product for which the Agent does not support live update. As a result, auto remediation will fail, and the agent will prompt user to do manual remediation.
Note
Workaround
CSCsx47987
No
Incorrect behavior when client wired/wireless NIC on same subnet as CAS
Scenario to reproduce:
•
•
•
•
As a result, the client is not able to ping the CAM or access any outside network.
CSCsx49160
No
Cisco NAC Agent shows one less authentication provider if one of the provider names is \
Steps to reproduce:
1.
2.
3.
4.
5.
6.
This time, the authentication provider list only shows Local DB—\ is missing.
Workaround
CSCsx78577
No
ClamAV not showing def date
ClamAV does not provide the definition date to the Agent.
Workaround
CSCsx80459
No
JAVA_OPTS_TO of "" seen in CAM upgrade details
When upgrading the Clean Access Manage to release 4.5(1), the additional message "Ended up with JAVA_OPTS_TO of """ may be seen in the upgrade details text displayed under Administration > CCA Manager > Software Upload. This message does not affect upgrade and is safe to ignore.
Welcome to the CCA Manager migration utility....Upgrading to newer rpms of 4.5.1...done....Upgrading CCA files...Ended up with JAVA_OPTS_TO of ""Preparing... ##################################################nac_manager ##################################################CSCsx81395
No
Sophos AV Definition rule fails even if Mac OS Agent has the latest definition
The remediation window pops up for updating the Sophos definition files on the Mac OS Agent even though Sophos is updated.
This occurs if Sophos is installed on the Mac OS client and an AV definition check for Sophos is configured on the CAM.
Workaround
CSCsx95230
No
Length of token is not printed in the ADSSO logs
When ADSSO logging is changed to DEBUG for troubleshooting purposes, the ADSSO logs display the token but not the token size.
Workaround
CSCsy00609
No
Role mapping uses cached entry on quick reconnects
Users who disconnect and immediately reconnect using different credentials (VPN group, etc.) may still be mapped to their role based on previous credentials. These same users are mapped correctly if they wait a few minutes between disconnecting and reconnecting.
This issue was reported in Cisco NAC Appliance release 4.1(6) using VPN Single Sign On (SSO) and a combination of the username and class attribute (user group) to map the user. Issue has also been observed using other criteria, such as client address, group, etc.
Workaround
Note
CSCsy32119
No
Cisco NAC Appliance CAM/CAS need ability to set port speed/duplex manually
There have been instances where switch ports are not negotiating the same as other ports on the same appliance. This is inefficient since the ports in question do not necessarily use the highest possible speed. In addition, there could be collisions, FEC, and errors on a port if there is a mismatch.
Note
CSCsy45807
No
Mac OS X Agent does not pop up using Sprint Wireless
This issue has been encountered using Sprint Wireless Novatel U727 on 2 different Mac OS X client machines.
CSCsz19346
No
Korean log packager GUI translations/buttons are garbled & some missing
Workaround
CSCsz19912
No
Log Packager CiscoSupportReport file shows ##### in place of system info
The system logs created by the log packager are showing ##### instead of actual data, as in the following examples:
04/23/2009 10:49:22 W32Time (ID=0x825a0083): NtpClient# 'CCAVPN-AD'# DNS ## ### ## ## #### ### ### ### #### #####. NtpClient# 15# ## ## #### # ### ### ### # ## ###. ##: ### #### ####. (0x80072AF9).04/23/2009 10:49:21 W32Time (ID=0x825a0083): NtpClient# 'CCAVPN-AD'# DNS ## ### ## ## #### ### ### ### #### #####. NtpClient# 15# ## ## #### # ### ### ### # ## ###. ##: ### #### ####. (0x80072AF9).This issue occurs on Japanese, Korean, and Chinese systems using Cisco Log Packager.
Note
CSCsz38970
No
Accessibility: login displays not announced
After you log into Windows, you see the ADSSO display and then the local corporate display. JAWS does not announce the Cisco NAC Agent displays.
Note
Workaround
CSCsz48766
No
MAC Agent VLAN change detection logic causes AnyConnect to disconnect
Anyconnect client constantly loses connection to VPN network when using the Mac OS X Clean Access Agent with the VlanDetectInterval set to 5 seconds.
Workaround
CSCsz48847
No
Accessibility: after successful log-in, JAWS is still on Cisco NAC Agent page
JAWS stays on The Cisco NAC Agent window even though no Agent window is displayed.
Workaround
CSCsz49147
No
Accessibility: JAWS does not announce installer after upgrade
During upgrade of the Cisco NAC Agent, the MS installer window is not announced.
Note
Workaround
CSCsz80035
No
"ANY" AV remediation for Trend Micro 17.1 fails
The AV update for Trend Micro version 17.1.1250 shows a failure in the Cisco NAC Agent window, but the update is successful.
Workaround
CSCsz83270
No
Agent file download fails at lower speed WAN links between CAS and CAM
When the Agent is uploaded to the CAM, the .tar file gets partially downloaded and removed several times on CAS before it is successfully downloaded and its contents unpacked. As a result the client does not pop-up for a long time for upgrade or fresh install from the Cisco NAC Appliance web login page.
This happens during agent upgrade or download from web page when CAS and CAM are separated by a WAN link (512kbps/256kbps).
Workaround
Note
CSCsz85892
No
Web login display Guest ID instead of Username
Steps to reproduce:
1.
2.
3.
4.
5.
CSCsz92761
No
CAM GUI and publishing behavior during DB restore
When a CAM snapshot is restored from a database, the CAM web console times out, and once refreshed, shows the associated CAS is offline as a result of triggering a database restoration.
This issue occurs when the CAM and CAS are connected via WAN links (T1/256k/512k) with several CASs experiencing at least 400ms delay.
Note
Workaround
CSCsz97199
No
McAfee AV_TotalProtectionforSmallBusiness_4_7_x upgrade to 5.0 issues
When auto-upgrading the McAfee AV_TotalProtectionforSmallBusiness_4_7_x to version 5.0 via the Cisco NAC Agent, all updates are downloaded and installed for 4.7, but then an automatic upgrade to 5.0 fails.
Note
CSCta02433
No
"Swiss Communication Logging" buttons do not work
Even though the option has been enabled in the Administrator web console page, Swiss log messages are missing from the nac_server.log file.
Workaround
CSCta03527
No
Discovery Host can not be changed by uploading XML on CAM
When adding a new XML Agent configuration file to be pushed to Agents via the CAM upload page, the Discovery Host does not get changed when using the "overwrite" option.
Workaround
CSCta12544
No
Server communication error upon web and Agent login
This issue can occur when a brand new CAS is connected to a CAM pair that has been upgraded from an older release of Cisco NAC Appliance to release 4.5 or later, resulting in unreliable communication between the CAM and CAS.
For more information, see CAM-CAS Shared Secret Mismatch Following New CAS Installation.
CSCta25247
No
Nessus scan fails on Vista
Nessus scan always fails on Vista client machines logging in with the Cisco NAC Agent. The Agent returns the following error message on the client:
"Clean Access Server is not available on the network. Please contact your administrator if the problem persists."
Note
CSCta34052
No
Java Memory leak causing CAM to crash
Customers using Kerberos or LDAP over GSSAPI see older versions of Java running out of memory due to a leak. This memory leak has been addressed in more recent versions of java. (Specifically, Java 6.)
Workaround
CSCta35376
No
If Agent Popup option disabled, Agent does not download config file
If the Agent "Popup Login Window" systray option is disabled, the Agent does not download the Agent configuration XML file from the CAM. As a result, the user cannot install configuration changes uploaded to the CAM on the client machine.
Workaround
CSCta35732
No
Deleting subnet filters causes CASs to disconnect
When you delete the subnet filter one after another from the CAM, the web console slows down and looses connection to the associated CAS.
The CAM connects to all the CASs every few minutes via serial interface and checks for heartbeats. If a CAS goes offline, the CAM tries to connect to the CAS to resume connection. However, the wait time depends on the number of CASs attached to the CAM.
Note
CSCsx52263
No
NAC Appliances always assume USA keyboard layout
When connected via Keyboard and Monitor, if a keyboard with layout other than US layout is used, the Cisco NAC Appliances do not recognize the keyboard and it is possible to erroneously enter different characters.
Workaround
CSCtg39044
No
Running Internet Explorer in offline more effects Cisco NAC Agent auto-upgrade function
When users access the network via Internet Explorer in offline mode, the Cisco NAC Agent auto-upgrade function does not work correctly for Agent versions 4.6.2.113 and earlier. The login session appropriately prompts the user to upgrade the Agent, but clicking OK brings up the login screen instead of launching the Agent installer.
Resolved Caveats - Release 4.6(1)
Note
Table 13 List of Resolved Caveats (Sheet 1 of 3)
CSCso66333
Yes
CAS/CAM time zone incorrect for Venezuela
Since the DEC 2007 change to Venezuela time zone from GMT-4:00 to GMT-4:30, Clean Access Manager and Servers continue to display the old time zone for "America/Caracas" with a half hour offset.
Note
CSCsy89640
Yes
CAM HA does not recover from partition with some linkdetect configs
CAM HA subsystem does not properly recover from network partition. After network partition is resolved, both CAM nodes in the HA pair remain active indefinitely.
To address this issue, configure linkdetect behavior so that the "ping time" HA configuration value is larger than the "dead time" value. The link detect IP must not be reachable by at least one node during the partition.
Workaround
CSCsz14431
Yes
Device Management > Clean Access > Update page needs to be updated for XML
If you go to the CAM Device Management > Clean Access > Update web console page and enable Check for Windows NAC Agent updates, Clean Update causes the NACAgentCFG.xml to be defaulted, thus any custom NACAgentCFG.xml file is lost.
Workaround
CSCsz24839
Yes
addlocaluser API function should not allow <,>," characters as username
Steps to reproduce:
1.
2.
Both the CAM web console and addlocaluser API should exhibit the same behavior.
CSCsz27928
Yes
Read-only administrator able to remove all MAC addresses with removemaclist API function
Steps to reproduce:
1.
11:11:11:11:11:11
22:22:22:22:22:22
33:33:33:33:33:33
2.
3.
Cisco NAC Appliance removes all three MAC addresses. Read-only administrators should not be able to remove MAC addresses.
CSCsv32010
Yes
Primary CAM should stop trying to sync db upon standby failure
The HA-Primary CAM continues to try to sync databases with the HA-Secondary CAM, even after it has detected a failure. This causes authentication outages.
This issue has been observed on all versions of Cisco NAC Appliance up to and including release 4.5(1).
Note
CSCsv94334
Yes
Host based filters not working on NME CAS
Host based policies do not work with the NME-NAC module in any deployment.
Workaround
CSCsx08078
Yes
User traffic passes when user is not in OUL or CDL
Part1: User authenticates through a CAS that they are supposed to be on. Then the user authenticate to another CAS with out changing their IP Address. As a result, the OUL will show 2 users with the same IP Address but on different CASs.
Part2: After Part 1 is created, clear the entry for the user IP Address that is on the incorrect CAS. The result is that the user is not in OUL or CDL and can still pass traffic through the CAS.
This issue is found during Layer 3 Web login.
Workaround
CSCsx95516
Yes
Certified Device List timer does not account for DST
The Cisco NAC Appliance CDL timer executes an hour sooner after DST takes effect.
Workaround
CSCsz17279
Yes
HTML XSS in NAC Appliance
HTML injection is possible on Cisco NAC appliance versions 4.1(x) and 4.5(x).
Additional information regarding mitigation of cross-site scripting can be found in the following document:
http://www.cisco.com/en/US/products/products_applied_mitigation_bulletin09186a008073f7b3.html
Note
Resolved Caveats - Agent Version 4.6.2.113
Refer to Enhancements in Release 4.6(1) for additional information.
New Installation of Release 4.6(1)
The following steps summarize how to perform new CD software installation of release 4.6(1) on supported Cisco NAC Appliance hardware platforms (see Release 4.6(1) and Hardware Platform Support for additional support details).
To upgrade or re-image a Cisco NAC Network Module, refer to the instructions in Getting Started with Cisco NAC Network Modules in Cisco Access Routers.
To upgrade on an existing NAC Appliance, refer to the instructions in Upgrading to Release 4.6(1).
For New Installation:
With release 4.6(1), installation occurs in two phases:
1.
2.
Step 1
Step 2
Step 3
a.
b.
Note
c.
Step 4
Step 5
Step 6
Step 7
Step 8
For additional information on configuring your deployment, including adding the CAS(s) to the CAM, refer to the following guides:•
•
Note
Note
Upgrading to Release 4.6(1)
This section provides instructions for how to upgrade your existing supported Cisco NAC Appliance platform to release 4.6(1). If you need to perform a CD software installation, refer instead to New Installation of Release 4.6(1).
Refer to the following information prior to upgrade:
•
•
•
•
Caution
Note
Changes for 4.6(1) Installation/Upgrade
Cisco NAC Appliance (Cisco Clean Access) release 4.6(1) ED and later is a major software release with Early Deployment status. Cisco strongly recommends to test new releases on a pilot system prior to upgrading your production system.
If planning to upgrade to Cisco NAC Appliance 4.6(1) ED and later, note the following:
•
Hardware Considerations
•
•
•
•
Features That May Change With Upgrade
•
•
•
Upgrade Changes
Warning
Note
•
•
•
–
–
–
Note
•
•
•
•
•
•
•
Caution
Password Changes
•
•
For additional details, see also:
•
General Preparation for Upgrade
Caution
•
You must upgrade your Clean Access Manager and all your Clean Access Servers (including NAC Network Modules) concurrently. The Cisco NAC Appliance architecture is not designed for heterogeneous support (i.e., some Clean Access Servers running 4.6(1) software and some running 4.5(x) or 4.1(x) software).
•
Depending on the number of Clean Access Servers you have, the upgrade process should be scheduled as downtime. For minor release upgrades, our estimates suggest that it takes approximately 10 to 20 minutes for the Clean Access Manager upgrade and 10 minutes for each Clean Access Server upgrade. Use this approximation to estimate your downtime window.
•
Starting with Cisco NAC Appliance release 4.1(6), the Clean Access Manager and Clean Access Server require encrypted communication. Therefore, you must upgrade CASs before the CAM that manages them to ensure the CASs have the same (upgraded) release when the CAM comes back online and attempts to reconnect to the managed CASs.
If you upgrade the Clean Access Manager by itself, the Clean Access Server (which loses connectivity to the CAM during Clean Access Manager restart or reboot) continues to pass authenticated user traffic only if the CAS Fallback Policy specifies that Cisco NAC Appliance should "ignore" traffic from client machines.
Caution
•
When connecting high availability (failover) pairs via serial cable, BIOS redirection to the serial port must be disabled for NAC-3300 series appliances, and for any other server hardware platform that supports the BIOS redirection to serial port functionality. See also Known Issues with NAC-3300 Series Appliances and Serial HA (Failover) Connection.
•
Cisco recommends creating a manual backup snapshot before and after upgrade of your CAM database. The snapshot contains CAM database configuration and CAS configuration for all CASs added to the CAM's domain. Pre- and post-upgrade snapshots allow you to revert to your previous database should you encounter problems during upgrade and preserves your upgraded database as a baseline after upgrade. Make sure to download the snapshots to another machine for safekeeping. After upgrade, delete all earlier snapshots from the CAM web console as they are no longer compatible. See Copy the Upgrade File to the CAS/CAM.
Warning
•
Once you have upgraded your software to release 4.6(1), if you wish to revert to your previous version of software, you will need to reinstall the previous version from the CD and recover your configuration based on the backup you performed prior to upgrading to 4.6(1). See Upgrade Instructions for Standalone Machines for additional details.
•
For upgrade via console/SSH, you will need your CAM and CAS root user password.
Upgrading from Customer-Supplied Hardware to Cisco NAC Appliance Hardware Platforms
If you are running the Cisco NAC Appliance software (release 4.1(x) or earlier) on a non-appliance platform, you will need to purchase Cisco NAC Appliance hardware before you can upgrade your system to Release 4.6(1). You may additionally need to obtain proper FlexLM product licenses. Once you obtain a Cisco NAC platform, Cisco recommends that you:
Step 1
Step 2
Step 3
Step 4
Step 5
Note
Upgrade Instructions for Standalone Machines
Note
This section describes how to upgrade standalone (i.e. non-HA) CAM/CAS machines from release 4.0(x)/4.1(x)/4.5(x) to release 4.6(1).
Review Changes for 4.6(1) Installation/Upgrade and General Preparation for Upgrade before proceeding with these upgrade instructions.
After you have downloaded and copied the upgrade file to the CAM/CAS, you must use the CAM/CAS CLI to extract the upgrade image files and perform the upgrade procedure as described in Run Upgrade Script on the CAM/CAS.
Summary of Steps for Standalone Upgrade
The steps to upgrade standalone 4.0(x)/4.1(x) systems are as follows:
1.
3.
4.
Create CAM DB Backup Snapshot
This section describes how to back up your current system.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Note
Download the Upgrade File
This section describes how to access and download the upgrade file to your local machine.
Note
Step 1
Step 2
Copy the Upgrade File to the CAS/CAM
This section describes how to copy the upgrade file to the Clean Access Manager and Clean Access Server(s) respectively using WinSCP, SSH File Transfer, or PSCP as described below.
Caution
If using WinSCP or SSH File Transfer
Step 1
Step 2
Step 3
Step 4
If using PSCP
Step 1
Step 2
Step 3
pscp cca_upgrade-4.6.1-NO-WEB.tar.gz root@<ipaddress_manager>:/storeStep 4
pscp cca_upgrade-4.6.1-NO-WEB.tar.gz root@<ipaddress_server>:/store
Run Upgrade Script on the CAM/CAS
This section describes how to untar the upgrade file and run the script to upgrade standalone CAM/CAS machines from release 4.0(x)/4.1(x)/4.5(x) to release 4.6(1). You will need to login with your CAM and CAS root user passwords and access the command line of the CAM or CAS machine using one of the following methods:
•
•
•
When run, the upgrade script automatically determines whether the machine is a Clean Access Manager (CAM) or Clean Access Server (CAS) and executes accordingly.
Note
Upgrade the CAM
Note
Step 1
Step 2
Step 3
cd /storeStep 4
ls -lStep 5
tar xzvf cca_upgrade-4.6.1-NO-WEB.tar.gzThe extraction process automatically places the upgrade files and necessary upgrade script in the /cca_upgrade-4.6.1 directory.
Step 6
cd cca_upgrade-4.6.1./UPGRADE.shStep 7
Please choose whether to upgrade Windows Agent to 4.6.2.113 (It's highly recommended to upgrade) (y/n)? [y]Please choose whether to upgrade Mac Agent to 4.6.0.3 (It's highly recommended to upgrade) (y/n)? [y]Step 8
...stopping CCA Manager...Welcome to the CCA Manager migration utility....Upgrading to newer rpms of 4.6.1...done....Upgrading CCA files...doneWindows Agent version upgraded to 4.6.2.113.Mac Agent was upgraded to version 4.6.0.3.Clearing Tomcat cache...checking ssl configuration...done.[root@cam127 cca_upgrade-4.6.1]#Step 9
reboot
Tip
Upgrade the CAS
Note
Step 1
Step 2
Step 3
cd /storeStep 4
ls -lStep 5
tar xzvf cca_upgrade-4.6.1-NO-WEB.tar.gzThe extraction process automatically places the upgrade files and necessary upgrade script in the /cca_upgrade-4.6.1 directory.
Step 6
cd cca_upgrade-4.6.1./UPGRADE.shStep 7
...stopping CCA Server...BaseAgent process stopped!Stopping DHCP...In Maintenance Mode...Welcome to the CCA Server migration utility....Upgrading to newer rpms of 4.6.1...done....Upgrading CCA files...doneClearing Tomcat cache...checking ssl configuration...done.[root@cas128 cca_upgrade-4.6.1]#Step 8
rebootStep 9
Tip
Upgrade Instructions for HA Pairs
This section describes how to upgrade high-availability (HA) pairs of CAM or CAS servers from release 4.0(x)/4.1(x)/4.5(x) to release 4.6(1).
If you have standalone CAM/CAS servers, refer instead to Upgrade Instructions for Standalone Machines.
Review Changes for 4.6(1) Installation/Upgrade and General Preparation for Upgrade before proceeding with these upgrade instructions.
Note
Warning
If you are using serial connection for HA, BIOS redirection to the serial port must be disabled for NAC-3300 series appliances, and for any other server hardware platform that supports the BIOS redirection to serial port functionality. See also Known Issues with NAC-3300 Series Appliances and Serial HA (Failover) Connection.
Note
Upgrading HA-CAM and HA-CAS Pairs
The following steps show the recommended way to upgrade an existing high-availability (failover) pair of Clean Access Managers or Clean Access Servers.
Warning
Note
Step 1
Step 2
Note
Step 3
Step 4
Step 5
cd /storeStep 6
ls -lStep 7
tar xzvf cca_upgrade-4.6.1-NO-WEB.tar.gzThe extraction process automatically places the upgrade files and necessary upgrade script in the /cca_upgrade-4.6.1 directory.
Step 8
cd /perfigo/common/bin/./fostate.shThe results should be either "My node is active, peer node is standby" or "My node is standby, peer node is active". No nodes should be dead. This should be done on both appliances, and the results should be that one appliance considers itself active and the other appliance considers itself in standby mode. Future references in these instructions that specify "active" or "standby" refer to the results of this test as performed at this time.
Note
•
•
Step 9
service perfigo stopStep 10
Step 11
cd /perfigo/common/bin/./fostate.shMake sure this returns "My node is active, peer node is dead" before continuing.
Step 12
a.
b.
./UPGRADE.shc.
Please choose whether to upgrade Windows Agent to 4.6.2.113 (It's highly recommended to upgrade) (y/n)? [y]Please choose whether to upgrade Mac Agent to 4.6.0.3 (It's highly recommended to upgrade) (y/n)? [y]Step 13
service perfigo stopWait until the active appliance has suspended services.
Step 14
service perfigo startStep 15
a.
b.
cd cca_upgrade-4.6.1c.
./UPGRADE.shd.
Please choose whether to upgrade Windows Agent to 4.6.2.113 (It's highly recommended to upgrade) (y/n)? [y]Please choose whether to upgrade Mac Agent to 4.6.0.3 (It's highly recommended to upgrade) (y/n)? [y]Step 16
service perfigo stopStep 17
rebootWait until it is running normally and you are able to connect to the web console.
Step 18
reboot
Note
Known Issues for Cisco NAC Appliance
This section describes known issues when integrating Cisco NAC Appliance:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Known Issue with Mass DHCP Address Deletion
An issue exists in release 4.5(1) and later where a Clean Access Server configured to be a DHCP server can become unmanageable if the administrator attempts to delete more than 800 DHCP addresses from the appliance using the Clean Access Manager web console. If you have more than 800 DHCP addresses, Cisco recommends deleting addresses in smaller blocks of no more than 800 addresses at a time.
In addition to ensuring you do not delete more than 800 DHCP addresses at a time, there are two methods to work around this potential issue.
Workaround 1
The DHCP IP delete can be done manually by connecting to the CLI and executing the following commands:
service perfigo stoprm -f /var/state/dhcp/dhcpd.leasestouch /var/state/dhcp/dhcpd.leasesservice perfigo startIf on an HA system, Cisco strongly recommends taking the CASs offline and performing the commands on both machines simultaneously, taking particular care to issue the service perfigo start on the two appliances at roughly the same time.
Workaround 2
If you experience this problem more than once, Cisco recommends changing the Clean Access Manager timeout value by editing the /perfigo/control/bin/starttomcat file and adding "-DRMI_READ_TIME_OUT=<new value>" to the end of the CATALINA_OPTS options string. (The current default value is 60 seconds, and Cisco does not recommend increasing the timeout value to any more than 300 seconds.) Please note that increasing the read time out value can likely lower the resiliency of WAN deployments, thus reversing the CAM/CAS connectivity improvements introduced when Cisco addressed caveat CSCsw20607 in the Release Notes for Cisco NAC Appliance, Version 4.5(1).
Note
For more information, see CSCsx35438.
Known Issue for VPN SSO Following Upgrade to Release 4.5 and Later
When you upgrade your Cisco NAC Appliance network employing VPN SSO to release 4.5 and later, user login does not work properly when the user VPN is part of a managed subnet on the CAS.
In release 4.5 and later, the SWISS protocol checks the MAC address for Layer 2 clients, but the MAC address reported by the Agent (which is the real client MAC address) is different from the one the CAS gets for the client (the VPN concentrator MAC address). As a result, the SWISS protocol tells the Agent that the client machine is not logged in (due to the different MAC addresses recorded) and the Agent launches the login dialog repeatedly, never able to complete login. Prior to release 4.5, the Clean Access Server associates the client with the VPN IP address and VPN Concentrator's MAC address after the first login. From there, the SWISS protocol only checks the IP address from the Agent and reports back to the Agent that the client is logged in (regardless of whether the client is connected via Layer 2 or Layer 3).
To work around this issue, remove the subnet making up the client machine address pool from the collection of managed subnets and create a Layer 3 static route on the CAS untrusted interface (eth1) with VPN concentrator's IP address as the gateway for the VPN subnet using the CAM web console Device Management > CCA Servers > Manage [CAS_IP] > Advanced > Static Routes page.
Known Issues with Web Upgrade in Release 4.1(x) and Earlier
Prior to Release 4.5, Cisco NAC Appliance provided a web upgrade feature where the product upgrade file for a new release could be uploaded and executed on the CAM and CAS machines via the CAM or CAS web console.
Starting from Release 4.5, web upgrade is no longer supported and cannot be used to upgrade Cisco NAC Appliances on 4.1(x) and 4.0(x) releases to Release 4.5 and later. To upgrade your Cisco NAC Appliances from 4.1(x) or 4.0(x) releases, you must copy the upgrade file to each appliance and run the upgrade script via the command line, as described in Upgrading to Release 4.6(1).
In the case that administrators attempt web upgrade from the 4.1(x) or 4.0(x) web consoles, the following known issues will occur:
•
•
•
Note that the two CAS web upload/upgrade errors cause no impact to the CAM database.
Starting from Release 4.5:
•
•
•
•
•
Caution
Upgrade files that are uploaded to the CAM and CAS via web console are located in different directories, depending on the software release, as listed in Table 15.
Note
Known Issues with www.perfigo.com Root CA
The Perfigo certificate authority, "EMAILADDRESS=info@perfigo.com, CN=www.perfigo.com, OU=Product, O="Perfigo, Inc.", L=San Francisco, ST=California, C=US" is used to generate temporary certificates and required for initial installation of CAM and CAS machines.
However, if the Perfigo CA remains on the CAM, it can render your Cisco NAC Appliance system vulnerable to security attacks. Before deploying your CAM and CAS(s) in a production environment, you must remove this certificate authority from the CAM and CAS databases. Cisco recommends searching for the string "www.perfigo.com" using the Filter options in the Administration > CCA Manager > SSL > Trusted Certificate Authorities CAM web console page and Administration > SSL > Trusted Certificate Authorities CAS web console page to quickly locate and remove this certificate authority from your CAM/CAS(s).
Before you can remove this CA from your CAM/CAS, you must obtain a third-party CA-signed SSL certificate and import it to your machines in order for the CAM/CAS components to work and to provide a trusted CA-signed certificate to end users.
Additionally, for any new CAM/CAS machines that you add to an existing production deployment, you will also need to remove the www.perfigo.com CA after initial installation and import a trusted CA-signed certificate.
For more information and detailed instructions on how to manage your SSL certificates when moving from a lab deployment to production-environment, see the "Manage CAM SSL Certificates" section of the Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide and the "Manage CAS SSL Certificates" section of the Cisco NAC Appliance - Clean Access Server Installation and Configuration Guide.
Cisco is working to further resolve this issue in the future by addressing the fact that currently there is no CA certificate button available on the web (or user) login page. By design, the Cisco NAC Appliance administrator must configure user page content and specify whether or not to offer the Root CA along with its content (either the www.perfigo.com CA certificate or an imported third-party CA certificate—in release 4.5 and later, the default option is still the www.perfigo.com CA) from a dropdown menu in the CAM web console pages. As the issue exists now, the administrator must change this behavior in the Administration > User Pages > Login Page > Edit > Content CAM web console page and deselect the Root CA table entry.
Known Issue with Active HA CAM Web Console Following Failover
For a brief period following a failover event, the administrator web console for the newly "active" CAM retains the limited menu/submenu options previously available while the machine was still the "standby" CAM.
To manually reproduce this scenario:
1.
2.
3.
4.
5.
To get the administrator web console to display properly, simply reload (Ctrl-refresh) the CAM HA-Service IP/hostname web page to display the full GUI for the now "active" CAM.
Known Issue with Upgrading CCA-3140 Appliance from Release 4.1(6)
If you are planning to upgrade the CCA-3140 appliance, a workaround is needed if upgrading from release 4.1.6 to release 4.5 and later. After an upgrade to Cisco NAC Appliance release 4.5 and later, the NICs on the CCA-3140 hardware are no longer recognized. This occurs when an appliance that was originally installed with version 3.6.4.4 or earlier is upgraded to 4.1.6, and subsequently upgraded to 4.5 and later.
Note
The following descriptions —CSCsv52402 Workaround and Further Problem Description—describe the workaround steps available to resolve this issue.
CSCsv52402 Workaround
Step 1
% rpm -qa | grep "tg3"If it returns nothing, then your system will not be affected.
Step 2
% rm /boot/2.6.11-perfigo-sp9% cd /store/cca_upgrade-4.6.x% ./UPGRADE.sh
Further Problem Description
If there is a bad network driver, a problem may be seen where the 'service perfigo stop' command fails prior to running the upgrade, displaying the following output:
...stopping CCA Server...BaseAgent process stopped!click: stopping router thread pid 2918click module exitingclick error: 93 elements still allocatedclick error: 457 outstanding newsUnable to handle kernel paging request at virtual address f8c4cc50printing eip:f8c4cc50*pde = 32298067Oops: 0000 [#2]To resolve this issue:
Step 1
% chkconfig --del perfigo% rebootStep 2
Step 3
% chkconfig --add perfigoStep 4
Known Issue with NAC-3310 Based Appliances
When performing CD software installation, if a NAC-3310 based appliance does not read the software on the CD ROM drive, and instead attempts to boot from the hard disk, you will need to configure the appliance BIOS settings to boot from CD ROM before attempting to re-image or upgrade the appliance from CD. For detailed steps, refer to the "Configuring Boot Settings on NAC-3310 Based Appliances "section of the Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide and Cisco NAC Appliance - Clean Access Server Installation and Configuration Guide.
Known Issues with NAC-3300 Series Appliances and Serial HA (Failover) Connection
When connecting high availability (failover) pairs via serial cable, BIOS redirection to the serial port must be disabled for NAC-3300 series appliances and any other server hardware platform that supports the BIOS redirection to serial port functionality. See Supported Hardware and System Requirements for Cisco NAC Appliance (Cisco Clean Access) for more information.
Known Issues with Switches
For complete details, see Switch Support for Cisco NAC Appliance.
Known Issues with Cisco 2200/4400 Wireless LAN Controllers (Airespace WLCs)
Due to changes in DHCP server operation with Cisco NAC Appliance release 4.0(2) and later, networks with Cisco 2200/4400 Wireless LAN Controllers (also known as Airespace WLCs) which relay requests to the Clean Access Server (operating as a DHCP server) may have issues. Client machines may be unable to obtain DHCP addresses. Refer to the "Cisco 2200/4400 Wireless LAN Controllers (Airespace WLCs) and DHCP" section of Switch Support for Cisco NAC Appliance for detailed instructions.
Note
Note
Known Issue for Windows Vista and IP Refresh/Renew
When logged in as a machine admin on Windows Vista and using web login with IP refresh configured, IP address refresh/renew via ActiveX or Java will fail due to the fact that Internet EXplorer does not run as an elevated application and Vista requires elevated privileges to release and renew an IP address.
Workaround
In order to use the IP refresh feature, you will need to:
1.
2.
3.
See also CSCsm61077.
Known Issues for Windows Vista and Agent Stub
Use "No UI" or "Reduced UI" Installation Option
When installing the 4.1.3.0 or later Clean Access Agent via stub installation on Windows Vista machines only, Cisco recommends not to use the Full UI Stub Installation Option. To avoid the appearance of 5-minute installation dialog delays caused by the Vista Interactive Service Detection Service, Cisco recommends using the No UI or Reduced UI option when configuring Stub Installation Options for Windows Vista client machines.
"Interactive Services Dialog Detection" and Uninstall
When non-admin users install/uninstall the Clean Access Agent through the Agent Stub service on Windows Vista, they will see an "Interactive Services Dialog Detection" dialog. If the user is installing, no input is required in the dialog session—it will automatically disappear. If the client machine is fast, the user may not even see the dialog appear at all, so the resulting behavior is as if the Agent gets silently installed after a few seconds. When uninstalling, however, the uninstall process does not complete until the user responds to a prompt inside the dialog.
This is expected behavior because, unlike earlier Windows operating systems, Windows Vista services run in an isolated session (session 0) from user sessions, and thus do not have access to video drivers. As a workaround for interactive services like the Agent Stub installer, Windows Vista uses an Interactive Service Detection Service to prompt users for user input for interactive services and enable access to dialogs created by interactive services. The "Interactive Service Detection Service" will automatically launch by default and, in most cases, users are not required to do anything. However, if the service is disabled for some reason, Agent installation by non-admin users will not function.
Known Issues with MSI Agent Installer
MSI File Name
The MSI installation package for each version of the full Windows Clean Access Agent (CCAAgent-<version>.msi) is available for download from the Cisco Software Download site at http://www.cisco.com/pcgi-bin/tablebuild.pl/cca-agent.
When downloading the Clean Access Agent MSI file from the Cisco Software Download site, you MUST rename the "CCAAgent-<version>.msi" file to "CCAAgent.msi" before installing it.
Renaming the file to "CCAAgent.msi" ensures that the install package can remove the previous version then install the latest version when upgrading the Agent on clients.
Minor Version Updates
You cannot upgrade minor version (4th digit) updates of the Clean Access Agent from the MSI package directly. You must uninstall the program from Add/Remove programs first before installing the new version. Refer to CSCsm20655 for details.
See also Troubleshooting for additional Agent- related information.
Known Issue with Windows 2000 Clean Access Agent/Local DB Authentication
When a user logs in via the Clean Access Agent on a Windows 2000 machine with a username/password linked to the "Local DB" provider and must validate a requirement (in a test environment, for example), the Agent returns a "The application experienced an internal error loading the SSL libraries (12157)" error message. Following the error message, the Agent remains in the login state even though it is not actually logged in and the user must either stop the process or restart the client machine for the Agent login dialog to re-appear. (Requirements are not validated and the CAM does not create an Agent report for the Windows 2000 session, so it can be difficult to determine which requirement fails.)
Known Issue with Windows XP/2000 and Windows Script 5.6
Windows Script 5.6 is required for proper functioning of the Clean Access Agent in release 3.6(x) and later. Most Windows 2000 and older operating systems come with Windows Script 5.1 components. Microsoft automatically installs the new 5.6 component on performing Windows updates. Windows installer components 2.0 and 3.0 also require Windows Script 5.6. However, PC machines with a fresh install of Windows 2000 that have never performed Windows updates will not have the Windows Script 5.6 component. Cisco Clean Access cannot redistribute this component as it is not provided by Microsoft as a merge module/redistributable.
In this case, administrators will have to access the MSDN website to get this component and upgrade to Windows Script 5.6. For convenience, links to the component from MSDN are listed below:
Filename: scripten.exe
Tip
Troubleshooting
This section provides troubleshooting information for the following topics:
•
•
•
•
•
•
•
•
•
•
•
•
Note
CAM-CAS Shared Secret Mismatch Following New CAS Installation
Following a new installation of a CAS in an existing CAM pair upgraded from a previous Cisco NAC Appliance release, the CAM-CAS communication may become unreliable, resulting in garbled HTTP communication between the CAM and CAS, like incoherent requests in CAS apache logs, for example. This could be a result of mismatched Shared Secrets on the CAM and CAS.
To discover whether or not you have a Shared Secret mismatch in your system:
Step 1
[root@cam1 ~]# cat .secretPERFIGO_SECRET=clpmUXkvroVywStep 2
[root@cas1 ~]# cat .secretPERFIGO_SECRET=clMrPFjECbmF6If the two PERFIGO_SECRET values do not match, be sure to reset your Cisco NAC Appliance Shared Secret.
For more information, see CSCta12544.
Vista/IE 7 Certificate Revocation List
Note
The "Network error: SSL certificate rev failed 12057" error can occur and prevent login for Clean Access Agent or Cisco NAC Web Agent users in either of the following cases:
1.
2.
–
–
To resolve the error, perform the following actions:
Step 1
Step 2
a.
b.
Windows Vista Agent Stub Installer Error
When initiating the Agent stub installer on the Windows Vista operating system, the user may encounter the following error message:
"Error 1722: There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor."
The possible cause is that there are remnants of a partial previous Agent stub installation present on the client machine stub. The user must take steps to remove the previous partial installation before attempting to run the Agent stub installer again.
To solve the problem:
Step 1
Step 2
Step 3
Step 4
Step 5
Agent Stub Upgrade and Uninstall Error
To resolve the situation where a user receives an "Internal error 2753:ccaagentstub.exe" message during stub installation:
Step 1
Step 2
Step 3
Note
Clean Access Agent AV/AS Rule Troubleshooting
When troubleshooting AV/AS Rules:
•
•
When troubleshooting AV/AS Rules, please provide the following information:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Generating Windows Installer Log Files for Agent Stub
Users can compile the Windows Installer logs generated by the Install Shield application when the Windows Agent is installed on a client machine using the MSI or EXE installer packages.
MSI Installer
To compile the logs generated by a Windows Agent MSI installer session as the installation takes place, enter the following at a command prompt:
ccaagent.msi /log C:\ccainst.log
This function creates an installer session log file called "ccainst.txt" in the client machine's C:\ drive when the MSI Installer installs the Agent files on the client.
EXE Installer
You can use the Windows Installer /v CLI option to pass arguments to the msiexec installer within CCAAgent_Setup.exe by entering the following at a command prompt:
CCAAgent_Setup.exe /v"/L*v \"C:\ccainst.log\""
This command saves an installation session log file called "ccainst.log" in the client machine's C:\ drive when the embedded msiexec command installs the Agent files on the client.
For more information, refer to the Windows Installer CLI reference page.
Debug Logging for Cisco NAC Appliance Agents
This section describes how to view and/or enable debug logging for Cisco NAC Appliance Agents. Refer to the following sections for steps for each Agent type:
•
•
Copy these event logs to include them in a customer support case.
Cisco NAC Web Agent Logs
The Cisco NAC Web Agent version 4.1.3.9 and later can generate logs when downloaded and executed. By default, the Cisco NAC Web Agent writes the log file upon startup with debugging turned on. The Cisco NAC Web Agent generates the following log files for troubleshooting purposes: webagent.log and webagentsetup.log. These files should be included in any TAC support case for the Web Agent. Typically, these files are located in the user's temp directory, in the form:
C:\Document and Settings\<user>\Local Settings\Temp\webagent.log
C:\Document and Settings\<user>\Local Settings\Temp\webagentsetup.log
If these files are not visible, check the TEMP environment variable setting. From a command-prompt, type "echo %TEMP%" or "cd %TEMP%".
When the client uses Microsoft Internet Explorer, the Cisco NAC Web Agent is downloaded to the C:\Documents and Settings\<user>\Local Settings\Temporary internet files directory.
Generate Windows Agent Debug Log
You can enable debug logging on the Clean Access Agent by adding a LogLevel registry value on the client with value "debug." For Windows Agents (see Enhancements in Release 4.6(1)), the event log is created in the directory %APPDATA%\CiscoCAA, where %APPDATA% is the Windows environment variable.
Note
To view and/or change the Agent LogLevel setting:
Step 1
Step 2
Step 3
Note
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
a.
b.
Step 11
Note
•
Generate Mac OS X Agent Debug Log
For Mac OS X Agents, the Agent event.log file and preference.plist user preferences file are available under <username> > Library > Application Support > Cisco Systems > CCAAgent.app. To change or specify the LogLevel setting, however, you must access the global setting.plist file (which is different from the user-level preference.plist file).
Because Cisco does not recommend allowing individual users to change the LogLevel value on the client machine, you must be a superuser or root user to alter the global setting.plist system preferences file and specify a different Agent LogLevel.
Note
To view and/or change the Agent LogLevel:
Step 1
Step 2
Step 3
Step 4
Step 5
•
•
•
•
Note
Note
Property List Editor is an application included in the Apple Developer Tools for editing .plist files. You can find it at <CD-ROM>/Developer/Applications/Utilities/Property List Editor.app.
If the setting.plist file is editable, you can use a standard text editor like vi to edit the LogLevel value in the file.
You must be the root user to edit the file.
Creating CAM DB Snapshot
See the instructions in Copy the Upgrade File to the CAS/CAM for details.
Creating CAM/CAS Support Logs
The Support Logs web console pages for the CAM and CAS allow administrators to combine a variety of system logs (such as information on open files, open handles, and packages) into one tarball that can be sent to TAC to be included in the support case. Refer to "Support Logs" sections of the Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide or Cisco NAC Appliance - Clean Access Server Installation and Configuration Guide.
Recovering Root Password for CAM/CAS
Refer to the "Recovering Root Password" section of the Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide or Password Recovery Procedure for the Cisco NAC Appliance (Cisco Clean Access).
Troubleshooting CAM/CAS Certificate Issues
Refer to the "Troubleshooting Certificate Issues" sections of the Cisco NAC Appliance - Clean Access Manager Installation and Configuration Guide or Cisco NAC Appliance - Clean Access Server Installation and Configuration Guide.
Troubleshooting Switch Support Issues
To troubleshoot switch issues, see Switch Support for Cisco NAC Appliance.
Other Troubleshooting Information
For general troubleshooting tips, see the following Technical Support webpage:
http://www.cisco.com/en/US/products/ps6128/tsd_products_support_series_home.html
Documentation Updates
Table 16 Updates to Release Notes for Cisco NAC Appliance, Release 4.6(1)
6/17/10
Added Caveats CSCtg39044 and CSCsx52263 to Open Caveats - Release 4.6(1)
7/1/09
Release 4.6(1)
Related Documentation
For the latest updates to Cisco NAC Appliance documentation on Cisco.com see:
http://www.cisco.com/en/US/products/ps6128/tsd_products_support_series_home.html
or simply http://www.cisco.com/go/cca
•
•
•
•
•
•
•
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
© 2009 Cisco Systems, Inc. All rights reserved.
