 Feedback
|
Table Of Contents
Release Notes for Cisco NAC Appliance,
Version 4.7(1)System and Hardware Requirements
Release 4.7(1) and Hardware Platform Support
Release 4.7(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.7(1) CAM/CAS Upgrade Compatibility Matrix
Release 4.7(1) CAM/CAS/Agent Compatibility Matrix
Release 4.7(1) Agent Upgrade Compatibility Matrix
Determining the Software Version
Enhancements in Release 4.7(1)
AD SSO Requirements for Windows 7
Cisco NAC Windows Agent Version 4.7.1.511
Mac OS X Agent Version 4.7.1.506
Cisco NAC Web Agent Version 4.7.1.504
Features Optimized/Removed in Release 4.7(1)
Supported AV/AS Product List Enhancements (Windows Version 81, Mac OS X Version 5)
Cisco NAC Appliance Supported AV/AS Product Lists
Supported Mac OS X AV/AS Product List Version Summary
Resolved Caveats - Release 4.7(1)
Resolved Caveats - Cisco NAC Agent Vers 4.7.1.511/Mac OS X Vers 4.7.1.506
New Installation of Release 4.7(1)
Paths for Upgrading to Release 4.7(1)
Upgrading from Customer-Supplied Hardware to Release 4.7(1) on a NAC-3310/3350/3390 Platform
Upgrading an Existing NAC-3310/3350/3390 Platform to Release 4.7(1)
Upgrading from a NAC-3310/3350/3390 Platform to Release 4.7(1) on a NAC-3315/3355/3395 Platform
Changes for 4.7(1) Installation/Upgrade
Features That May Change With Upgrade
General Preparation for Upgrade
Upgrade Instructions for Standalone Machines
Summary of Steps for Standalone Upgrade
Download the Install/Upgrade File
Upgrade Instructions for HA Pairs
Upgrading HA-CAM and HA-CAS Pairs
Known Issues for Cisco NAC Appliance
Known Issue with Enabling Web Login for Windows 7 Starter Edition Clients
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(3), 4.1(6), and 4.1(8)
Known Issue with Active HA CAM Web Console Following Failover
Known Issue with Cisco NAC Appliance CAM/CAS Boot Settings
Known Issues with Cisco 2200/4400 Wireless LAN Controllers (Airespace WLCs)
Known Issue for Windows Vista and IP Refresh/Renew
Enabling TLSv1 on Internet Explorer Version 6
Windows Vista and Windows 7—IE 7 and IE 8 Certificate Revocation List
HA Active-Active Situation Due to Expired SSL Certificates
Agent AV/AS Rule Troubleshooting
Debug Logging for Cisco NAC Appliance Agents
Generate Cisco NAC Agent Debug Logs
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.7(1)
Document Number OL-22767-01 Revised: September 28, 2011Contents
These release notes provide the latest cumulative release information for Cisco® NAC Appliance, Release 4.7(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. 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.7(1) and Hardware Platform Support
FIPS Compliant
You can install or upgrade to Cisco NAC Appliance Release 4.7(1) on the following FIPS-compliant Cisco NAC Appliance platforms:
•
Note
Non-FIPS
You can install or upgrade to Cisco NAC Appliance Release 4.7(1) on the following Cisco NAC Appliance platforms:
•
•
Note
Note
•
Additionally, Cisco NAC Appliance Release 4.7(1) provides substantial changes and enhancements for product hardware support, installation, and upgrade:
•
•
•
•
Note
Release 4.7(1) and Cisco NAC Profiler
Release 4.7(1) includes version 2.1.8-39 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.7(1), the upgrade script will check the version of the Collector and only upgrade it if version 2.1.8-39 is not already installed.
Refer to the Release Notes for Cisco NAC Profiler for software compatibility matrixes and additional upgrade and product information.
Note
Note
FIPS 140-2 Compliance
Note
This section describes the following topics:
•
•
•
•
•
•
Overview
Cisco NAC Appliance Release 4.7(0) introduces Federal Information Processing Standard (FIPS) 140-2 Common Criteria EAL2 compliance for new installations on new Cisco NAC-3315, NAC-3355, and NAC-3395 hardware appliance platforms. In order to provide FIPS compliance in your Cisco NAC Appliance network, both CAM(s) and CAS(s) must use the new hardware platforms and be FIPS compliant. That is, Cisco does not support deployments where a non-FIPS CAM connects to one or more FIPS CASs, or vice-versa.
To enable FIPS 140-2 compliance in Cisco NAC Appliance, the new NAC-3315, NAC-3355, and NAC-3395 feature an encryption card that handles the primary FIPS "level 2" compliance functions and manages private keys for the system.
In addition, in order to ensure FIPS compliance across the entire Cisco NAC Appliance network, users must use the latest Cisco NAC Agent version 4.7.1.15 on client machines connecting to the Cisco NAC Appliance network. Although Cisco NAC Appliance Release 4.7(0) supports older Cisco NAC Appliance Agents, users logging in with an older version of the Agent are not FIPS compliant. For more information on the latest Cisco NAC Agent, see the Release Notes for Cisco NAC Appliance, Version 4.7(0).
In Release 4.7(0), if the FIPS card in the CAM/CAS ceases to work correctly, make sure the card operation switch is set to "O" (for operational mode), as described in FIPS and SSH. If the card is still not operational, you will need to RMA the appliance with Cisco Systems and replace it with a new Cisco NAC-3315/3355/3395 platform. Refer to the "Cisco NAC Appliance RMA and Licensing" section of Cisco NAC Appliance Service Contract/Licensing Support for details. When you configure the replacement appliance, you must also ensure you configure it with the same master password and have imported any required third-party certificates before connecting the appliance to the network. For more information, see Release 4.7(1) and Hardware Platform Support.
Note
Note
Note
Capabilities, Dependencies, and Restrictions
FIPS 140-2 compliance in Release 4.7(0) introduces the following capabilities, dependencies, and restrictions:
1.
2.
a.
b.
c.
Note
3.
a.
b.
c.
Note
4.
a.
b.
c.
Note
For more information, see IPSec Considerations with FIPS.
5.
Note
6.
7.
8.
9.
10.
Note
11.
FIPS Compliance in HA Deployments
To support FIPS 140-2 compliance, HA CAMs/CASs automatically establish an IPSec tunnel to ensure all communications between the HA pair appliances remains secure across the network.
Trusted Certificates and Private Key Management with FIPS
Starting from Cisco NAC Appliance Release 4.7(0), you can no longer export private keys and you cannot generate CSRs using a FIPS compliant CAM/CAS. To adhere to strict FIPS compliance guidelines, you can only import certificates from trusted third-party resources.
Cisco NAC Appliance uses two types of keys to support FIPS compliance: Private Keys and Shared Master Keys. Both of these key types are managed and stored using the FIPS card installed in the CAM/CAS. During installation, keys are created using the CAM/CAS setup utilities, the keys are then moved to the card for security, and key-generation files and/or directories are then removed from the CAM/CAS.
This enhancement affects the following pages of the CAM web console:
•
•
•
FIPS and SSH
SSH connections between FIPS and non-FIPS CAMs/CASs are supported starting from Cisco NAC Appliance Release 4.7(0). However, if the FIPS card in a CAM/CAS fails (or is inadvertently set to the incorrect operational mode), you cannot use SSH to or from that appliance until the issue with the card is resolved.
You can verify FIPS functionality on a CAM/CAS as follows:
a.
b.
c.
d.
Installed FIPS card is nCipherInfo-FIPS file existsInfo-card is in operational modeInfo-httpd worker is in FIPS modeInfo-sshd up
Note
Installed card in the system: nCipher
System is running in FIPS mode
FIPS and the Cisco NAC Appliance SWISS Protocol
To enhance network security and adhere to FIPS 140-2 compliance, Cisco NAC Appliance encapsulates SWISS communications between client machines and CASs, including Discovery Packet transmission/acknowledgement, authentication, and posture assessment results using the HTTPS protocol.
In addition, the CAS SWISS mechanism has been enhanced to feature a new handler that uses 3DES encryption for SWISS protocol functions. Because of these changes, older versions of Cisco NAC Appliance Agents are not compatible with FIPS-compliant CAMs/CASs in Release 4.7(0).
IPSec Considerations with FIPS
Cisco NAC Appliance Release 4.7(0) uses IPSec for the following purposes:
•
•
•
•
When setting up your Cisco NAC Appliance to use IPSec, you must ensure you can set up and import certificates and configure IPSec tunnels between Cisco NAC Appliance and your external authentication resources.
For Active Directory, LDAP, and Kerberos functions with FIPS-compliant CAMs/CASs, you must ensure that hosts are running Windows 2008 Server to support secure authentication sessions between external resources and FIPS-compliant appliances.
FIPS and SNMP Configuration
Cisco NAC Appliance Release 4.7(0) provides support for SHA-1 and 3DES encryption when configuring SNMP management on a FIPS-compliant CAM.
This enhancement affects the following page of the CAM web console:
•
FIPS and Cisco Secure ACS as RADIUS Authentication Provider
You can configure a FIPS 140-2 compliant external RADIUS Authentication Provider type by setting up a secure IPSec tunnel between your Cisco NAC Appliance system and Cisco ACS 4.x in a Windows environment running Windows Server 2003 or 2008.
For specific configuration instructions, see "Add a FIPS 140-2 Compliant RADIUS Auth Provider Using an ACS Server" section of the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.7(2).
FIPS with VPN SSO
You can configure Cisco NAC Appliance to connect to and manage a Cisco ASA VPN Concentrator in a FIPS 140-2 compliant deployment.
For specific configuration instructions, see the "Configure VPN SSO in a FIPS 140-2 Compliant Deployment" section of the Cisco NAC Appliance - Clean Access Server Configuration Guide, Release 4.7(2).
FIPS with AD SSO
To maintain FIPS 140-2 compliance and support AD SSO, you must use 32-bit Windows Server 2008 with KTPass version 6.0.6001.18000, and client machines must run Windows Vista with Cisco NAC Agent version 4.7.1.15 installed. For specific configuration instructions, see the "Configure Active Directory for FIPS 140-2 Compliant AD SSO" section of the Cisco NAC Appliance - Clean Access Server Configuration Guide, Release 4.7(2).
Note
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.7(1).
Note
Cisco WLCs do not support IPSec communication with the Cisco NAC Appliance network, so you cannot provide RADIUS SSO capability to users in your FIPS 140-2 compliant environment.
Table 2 lists the IOS versions and switch platforms that are tested and known to work with the Wireless OOB feature in Release 4.7(1). If you encounter issues with WOOB support and are not 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 8.0(3)7 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
Cisco WLCs do not support IPSec communication with the Cisco NAC Appliance network, so you cannot provide RADIUS SSO capability to users in your FIPS 140-2 compliant environment.
For further details, see the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.7(2) and the Cisco NAC Appliance - Clean Access Server Configuration Guide, Release 4.7(2).
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.7(1) CAM/CAS Upgrade Compatibility Matrix
Table 4 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 4 Release 4.7(1) CAM/CAS Upgrade Compatibility Matrix
4.7(0)
4.6(1)
4.5(x) 34.7(1)
4.7(0)
4.6(1)
4.5(x)4.7(1)
1 Next generation Cisco NAC Appliance platforms (FIPS or non-FIPS Cisco NAC-3315, NAC-3355, NAC-3395) support fresh installation of Release 4.7(1) or upgrade from Release 4.7(0) to Release 4.7(1) only. You can also install or upgrade to Release 4.7(1) on the NAC-3310, NAC-3350, NAC-3390, and CCA-3140 (EOL) platforms, but they operate in non-FIPS mode only. See Hardware Support and Changes for 4.7(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.7(1) and Cisco NAC Profiler for details.
3 To upgrade from Cisco NAC Appliance Release 4.1(8) or earlier to Release 4.7(1), you must first upgrade your system to Release 4.5(x), 4.6(1), or 4.7(0) and then upgrade to Release 4.7(1).
.
Release 4.7(1) CAM/CAS/Agent Compatibility Matrix
Table 5 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 5.
For complete support information, including specific client machine operating systems supported with specific Agent versions, refer to the Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later.
Table 5 Release 4.7(1) CAM/CAS/Agent Compatibility Matrix
4.7(1)
4.7(0)4.7(1)
4.7(0)4.7.1.511 6
4.7.1.15
4.6.2.113
(All languages)N/A
N/A
4.7(1) 7
4.7(1)
4.7.1.511 6
4.7.1.154.7.1.506
4.7.0.24.7.1.504 8
4.6.2.113
4.6.0.3
4.5.2.0 9
4.5.1.0
4.5.0.04.5.0.0 9
4.1.8.0 9
4.1.6.0
4.1.3.24.1.3.0 9
4.1(3) and later
4.1(3) and later
4.7.1.506
4.7.0.2 10N/A
4.6.2.113 10
4.6.0.3 10
1 Next generation Cisco NAC Appliance platforms (FIPS or non-FIPS Cisco NAC-3315, NAC-3355, NAC-3395) support fresh installation of Release 4.7(1) or upgrade from Release 4.7(0) to Release 4.7(1) only. You can also install or upgrade to Release 4.7(1) on the NAC-3310, NAC-3350, NAC-3390, and CCA-3140 (EOL) platforms, but they operate in non-FIPS mode only. See Hardware Support and Changes for 4.7(1) Installation/Upgrade for additional details.
2 Make sure that both CAM and CAS are of same version.
3 See Enhancements in Release 4.7(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.7(1). See Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later 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.7(1) CAM/CAS network.
6 Cisco NAC Agent version 4.7.1.511 does not support Windows 7 Starter Edition. Client machines with the Windows 7 Starter Edition operating system can only perform web login to verify user credentials. For specific information on enabling web login for client machines running Windows 7 Starter Edition, see Known Issue with Enabling Web Login for Windows 7 Starter Edition Clients.
7 When upgrading the CAM from version 4.5(x) and later to Release 4.7(1), Agent files are automatically upgraded to the latest Agent version packaged with the CAM software image (e.g. Windows version 4.7.1.511 and Mac OS X version 4.7.1.506).
8 Cisco NAC Web Agent version 4.7.1.504 does not support Windows 7 Starter Edition. Client machines with the Windows 7 Starter Edition operating system can only perform web login to verify user credentials. For specific information on enabling web login for client machines running Windows 7 Starter Edition, see Known Issue with Enabling Web Login for Windows 7 Starter Edition Clients.
9 CAM/CAS Release 4.7(1) supports 4.1.3.2 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 Agent 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.
10 4.6.x.x and 4.7.1.x Windows Agents and 4.6.x.x and 4.7.x.y Mac OS X 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 Agent 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.
11 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.7(1) CAM/CAS network.
Release 4.7(1) Agent Upgrade Compatibility Matrix
Table 6 shows Cisco NAC Appliance Agent upgrade compatibility when upgrading existing versions of the persistent Agents on clients after CAM/CAS upgrade.
Note
For complete support information, including specific client machine operating systems supported with specific Agent versions, refer to the Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later.
Table 6 Release 4.7(1) Agent Upgrade Compatibility Matrix
4.7(1)
4.7(1)
4.7.0.2
4.6.0.3
4.5.x.x
4.1.3.04.7.1.506
1 Next generation Cisco NAC Appliance platforms (FIPS or non-FIPS Cisco NAC-3315, NAC-3355, NAC-3395) support fresh installation of Release 4.7(1) or upgrade from Release 4.7(0) to Release 4.7(1) only. You can also install or upgrade to Release 4.7(1) on the NAC-3310, NAC-3350, NAC-3390, and CCA-3140 (EOL) platforms, but they operate in non-FIPS mode only. See Hardware Support and Changes for 4.7(1) Installation/Upgrade for additional details.
2 See Enhancements in Release 4.7(1) for details on each version of the Windows/Mac OS X/Web Agent.
3 To remain FIPS-compliant, users logging into Cisco NAC Appliance via AD SSO must run Windows Vista and have Cisco NAC Agent version 4.7.1.15 installed on their client machine. Windows XP clients cannot perform AD SSO in a FIPS 140-2 compliant network. See FIPS with AD SSO for details.
4 Users without administrator privileges upgrading their Windows client machine from an earlier version of the Clean Access Agent (version 4.5.2.0 or 4.1.10.0 and earlier) to the Cisco NAC Agent must have the CCAAgentStub.exe Agent Stub installed on the client machine to facilitate upgrade. (Users with administrator privileges do not need this file.) After successful Cisco NAC Agent installation, the user is not required to have administrator privileges on the client machine, nor is the CCAAgentStub.exe Agent Stub file needed. For more information on Agent Stub installers and requirements/prerequisites, see the appropriate Release Notes for the specific previous version of Cisco NAC Appliance.
5 Auto-upgrade to the latest 4.7.x.x Agent is supported from any 4.1.3.2 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.
6 When upgrading the CAM from version 4.5(x) and later, Agent files are automatically upgraded to the latest Agent version packaged with the CAM software image (e.g. Windows version 4.7.1.511 and Mac OS X version 4.7.1.506).
7 CAM/CAS Release 4.7(1) supports 4.1.3.2 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 Agent 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.
8 Cisco NAC Agent version 4.7.1.511 is the only Cisco NAC Appliance Agent that supports Windows 7 operating systems.
9 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.7(1)
•
•
•
•
•
•
AD SSO Requirements for Windows 7
In current releases of Windows 7 Enterprise, Ultimate, and Professional, Microsoft has changed what encryption protocols are enabled by default for Active Directory domain authentication. In order to authenticate users via AD SSO, all Windows domain client machines must negotiate a common encryption protocol between themselves and the specific Windows AD server performing authentication.
In previous releases of Cisco NAC Appliance, the AD SSO subsystem required that the Microsoft client machine, CAS, and the authenticating Windows AD Server all use a single common (static) protocol. To ensure that AD SSO could support all customer Active Directory Networks, Cisco NAC Appliance and the AD SSO service account were required to be set to "DES_ONLY" (via KTPass) since all prior Microsoft client machines, as well as the Cisco NAC Appliance system, supported DES encryption.
With Cisco NAC Appliance Release 4.7(1), the CAS has the ability to negotiate any of the standard Kerberos encryption protocols (except for AES 256, due to export restrictions). This new option allows for much improved functionally for customers that wish to migrate between encryption standards without interruption.
For specific configuration details, see the "Configure AD SSO in a Windows 7 Environment" section of the Cisco NAC Appliance - Clean Access Server Configuration Guide, Release 4.7(2).
Cisco NAC Windows Agent Version 4.7.1.511
In Cisco NAC Appliance Release 4.7(1), the Cisco NAC Agent version 4.7.1.511 has been enhanced to feature support for the Windows 7 client machine operating systems:
•
•
•
•
•
Note
•
•
•
Refer to Release 4.7(1) CAM/CAS/Agent Compatibility Matrix for additional compatibility details.
For details on Agent functionality, refer to the "Cisco NAC Appliance Agents" chapter of the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.7(2).
Mac OS X Agent Version 4.7.1.506
In Cisco NAC Appliance Release 4.7(1), the Mac OS X Agent version 4.7.1.506 has been enhanced to feature login and posture assessment support for 32- and 64-bit Mac OS 10.6 (Snow Leopard) client machines.
Note
Cisco NAC Web Agent Version 4.7.1.504
In Cisco NAC Appliance Release 4.7(1), the Cisco NAC Web Agent version 4.7.1.504 has been enhanced to feature support for the Windows 7 client machine operating systems:
•
•
•
•
•
Note
•
•
•
For details on Agent functionality, refer to the "Cisco NAC Appliance Agents" chapter of the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.7(2).
Features Optimized/Removed in Release 4.7(1)
Agent Stub Options Removed from Installation Page
The "Agent Stub" installation options have been removed from the CAM Device Management > Clean Access > Installation web console page. (These options are deprecated legacy configuration settings for the Clean Access Agent version 4.5.2.0 and earlier.)
Supported AV/AS Product List Enhancements (Windows Version 81, Mac OS X Version 5)
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 Agent, and is used to populate AV/AS Rules and AV/AS Definition Update requirements for 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.
Note
Windows 7/Vista/XP
For Windows 7/Vista/XP AV/AS support information on the Cisco NAC Agent (version 4.7.1.511) and Cisco NAC Web Agent (version 4.7.1.506), see the Cisco NAC Appliance Release 4.7(1) Supported Windows AV/AS Products document optimized for UTF-8 character display.
Mac OS X
•
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 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.7(1) for additional details on Agent versions in this release.
Supported Mac OS X AV/AS Product List Version Summary
Table 7 summarizes enhancements made for each version update of the Supported Antivirus/Antispyware Product List for the Mac OS X Agent. See Mac OS X AV Support Chart and Mac OS X AS Support Chart for details.
Mac OS X AV Support Chart
Table 8 lists Mac OS X Supported AV Products for Release 4.7(1) of the Cisco NAC Appliance software.
Table 8 Mac OS X Antivirus Product Support Chart
Version 5, 4.7.1.506 Mac OS X Agent, CAM/CAS Release 4.7(1) (Sheet 1 of 2)
(Minimum Agent Version Needed)1avast! Antivirus
2.x
yes (4.1.4.0)
yes (4.1.4.0)
-
clamXav
0.x
yes (4.1.4.0)
yes (4.1.4.0)
yes
ClamXav
1.x
yes (4.1.4.0)
yes (4.1.4.0)
yes
ClamXav
2.x
yes (4.7.1.500)
yes (4.7.1.500)
yes
eTrust Antivirus
7.x
yes (4.1.4.0)
yes (4.1.4.0)
-
eTrust ITM Agent
8.x
yes (4.1.4.0)
yes (4.1.4.0)
-
VirusBarrier X
10.x
yes (4.1.4.0)
yes (4.1.4.0)
-
VirusBarrier X4
10.4.x
yes (4.1.4.0)
yes (4.1.4.0)
-
VirusBarrier X5
10.5.x
yes (4.1.4.0)
yes (4.7.0.0)
-
Virex 7.2
7.2.x
yes (4.1.4.0)
yes (4.1.4.0)
-
Virex 7.5
7.5.x
yes (4.1.4.0)
yes (4.1.4.0)
-
Virex 7.7
7.7.x
yes (4.1.4.0)
yes (4.1.4.0)
-
VirusScan
8.5.x
yes (4.1.4.0)
yes (4.1.4.0)
-
VirusScan
8.6.x
yes (4.1.4.0)
yes (4.1.4.0)
-
iAntiVirus
1.x
yes (4.7.0.0)
yes (4.7.0.0)
-
BitDefender
1.x
yes (4.7.1.500)
-
-
Sophos Anti-Virus
4.x
yes (4.1.4.0)
yes (4.1.4.0)
-
Norton AntiVirus
10.x
yes (4.1.4.0)
yes (4.1.4.0)
-
Norton AntiVirus
11.x
yes (4.1.4.0)
yes (4.1.4.0)
-
Norton AntiVirus
8.x
yes (4.1.4.0)
yes (4.1.4.0)
-
Norton AntiVirus
9.x
yes (4.1.4.0)
yes (4.1.4.0)
-
Trend Micro Security for Macintosh
1.x
yes (4.7.0.0)
yes (4.7.0.0)
-
Trend Micro Security for Macintosh
3.x
yes (4.1.4.0)
yes (4.1.4.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 9 lists Supported Mac OS X Antispyware Products for Release 4.7(1) of the Cisco NAC Appliance software.
Table 9 Mac OS X Antispyware Product Support Chart
Version 5, 4.7.1.506 Mac OS X Agent/CAM/CAS Release 4.7(1) (Sheet 1 of 2)
(Minimum Agent Version Needed)1MacScan
2.x
yes (4.1.4.0)
yes (4.1.4.0)
-
Trend Micro Security for Macintosh
1.x
yes (4.7.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.7(1)
Table 10 List of Open Caveats (Sheet 1 of 36)
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
Agent locks up when greyed out OK button is pressed
The 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 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 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
CSCsj46232
No
Agent should NOT pop-up during CAS HA failover
Agent pops up during CAS HA failover. The user ISD still appears in the Online User List and the client machine still appears in the Certified Devices List.
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 Agent pop-ups with Multi NIC in L2 Virtual Gateway OOB role-based VLAN
The user sees multiple 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 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 persistent 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 approximately 40 to 50 times. If the user clicks Yes to proceed enough times, the Web Agent fails to login and displays a "You will not be allowed to access the network due to internal error. Please contact your administrator." message to the user.
Workaround
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
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
"javax.naming.CommunicationException" causes no provider list
ADSSO with LDAP Lookup
If the LDAP connection to Active Directory fails during the lookup process (because the lookup takes a long time or the connection is suddenly lost), the Agent does not receive the list of authentication providers from the CAS. As a result, the user is presented with a blank provider list.
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.
There is no known workaround for this issue.
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
•
•
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
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
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 Release 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) and later.
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
CSCsx18496
No
Cisco Log Packager crashes on XP Tablet PC with Restricted User credentials
CSCsx27857
No
With session timer disabled for the Agent Temporary role, version 4.6.0.3 of the Mac OS X 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
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 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.
CSCsz88018
No
Clean Access Agent installs on Windows 7 beta, fails remediation, then sends Success to CAM
Clients running Windows 7 Beta are able to successfully download and install the Clean Access Agent and log in to the Cisco NAC Appliance network. However, AntiVirus posture assessment checks do not appear to be working and if users pass authentication, they are not cleared for network access when the AntiVirus information is not correct on the current Agent version.
This issue has been observed is a Cisco NAC Appliance Release 4.5 deployment.
Workaround
•
•
–
–
–
–
–
–
–
–
–
–
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
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.
CSCta19323
No
Memory for crash kernel message seen during 4.7.0 CD install
The message is benign, it is displayed when memory is not configured/allocated for a crash kernel to aid in crash dump. This is displayed by Red Hat and CentOS 5 releases while booting on any system.
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
CSCta35741
No
Agent not Popping up for First time for TLS not enabled on IE 6.0
If TLS 1.0 is not enabled on Microsoft Internet Explorer browsers when the user launches the Cisco NAC Agent, the Agent dialog/login screen does not appear.
Workaround
CSCta43634
No
JSF library throws duplicated ID in faces tree exception occasionally
This condition can occur if the user inadvertently double-clicks a hyperlink, resulting in the CAM web console returning an exception error.
Workaround
CSCta85491
No
Cisco API: addmac is susceptible to XSS on the CAS when using local device filter
Steps to reproduce:
1.
2.
3.
Note
CSCta97229
No
Collector Modules show "Stopping" instead of "Stopped" in Profiler UI
This issue happens when the administrator manually stops the Profiler Collector.
Workaround
CSCtb02366
No
"ANY" AS update does not work for MS Defender on 64-bit Vista
Workaround
Note
CSCtb17138
No
CAM or CAS UI not reachable after failover pair recover from network partition
If a CAM HA pair loses connectivity and connectivity is subsequently restored, in some cases the CAS service IP address is not reachable and CAM-CAS communication fails.
Workaround
Note
CSCtb30587
No
Clearing CAM CDL upon intra-subnet roaming keeps client in Access VLAN
This issue has been seen on WLC1 managing AP1 and WLC2 managing AP2 have same SSID with WLANs on both the controllers mapped to interface which are on the same subnet. (Both controllers are running version 6.0.182.0.)
Steps to reproduce:
1.
2.
However, the CAM still lists WLC1 IP address with client entry.
3.
CSCtb30691
No
Agent pops up from and active wired NIC after user is already authenticated via a wireless NIC in the same client machine
After authenticating using the wireless NIC with a higher preference than the wired NIC on the same client machine, the Agent pops up again, prompting the user to enter authentication credentials. This happens on Windows XP SP3 client machines. (This issue has not been observed in Windows XP SP2.)
Workaround
CSCtb32797
No
LDAP GSSAPI with SSL lookup and authentication fails
The Cisco NAC Appliance network returns the following message:
"Unsupported Ldap Operation ([LDAP: error code 53 - 00002029: LdapErr: DSID-0C09048A, comment: Cannot bind using sign/seal on a connection on which TLS or SSL is in effect, data 0, v1771])"
or
"Naming Error (dcchild.child.2k8.com:636; socket closed)"
Note
Note
CSCtb38026
No
Scripting error with database restore with modified DB snapshot name
If the database snapshot name is altered to include some string after the version number and before the .gz suffix like the following:
08_12_09-23-48_snapshot_VER_4_7_0_A23_upgraded_from_4-1-3.gzthe database restoration process returns a scripting error. This issue is only cosmetic and does not affect the database restore functionality.
Workaround
CSCtb43264
No
Both HA-CAS nodes stuck in active-active state
Steps to reproduce:
1.
2.
3.
4.
5.
6.
This is a dangerous scenario creating a Layer 2 broadcast loop that almost immediately brings down the network.
Workaround
•
•
CSCtb55184
No
Web Agent download fails if the CAS IP address in the trusted certificate is different from the CAS domain IP address.
This situation can occur when the CAS is in Layer 2 In-Band Real-IP gateway mode, and IP used for initial SSL cert during install is different from that imported using the web console.
Workaround
CSCtb58837
No
Database write to HA-Secondary CAM fails
Standby CAM can occasionally fall out of sync with Active under stress load condition where there is a lot of very rapid individual update to the HA-Standby appliance for a very long period of time (i.e. users logging on and off and many changes to the device filter list, for example).
Workaround
CSCtb61012
No
Web Console should show the correct status of an HA-Standby CAM/CAS
When you go into the failover section in the GUI to check the status, it only shows the other CAM or CAS as active but not the actual state of the local appliance.
Note
[root@NACM-1 bin]# ./fostate.shMy node is standby, peer node is activeCSCtb63619
No
Cannot manage a CAS over JMX
This situation can happen when there are multiple large publishing requests over a slow link connection and the system demands exceed the publishing queue. (The default max publishing queue size is set to 10.)
Workaround
1.
CATALINA_OPTS=<...>line:-DJMX.WRITELOCK.QUEUEDEPTH=<any number>For example:
CATALINA_OPTS="-server -Xms64m -Xmx${MAX}m -Dcom.ncipher.provider.announcemode=off -Dcom.ncipher.provider.enable=Signature.NONEwithRSA,Key Factory.RSA,Cipher.RSA -DJMX.WRITELOCK.QUEUEDEPTH=20"2.
CSCtb66010
No
NACAgentCFG.xml file is not preserved after CAM upgrade
The Agent configuration XML file packaged with the Cisco NAC Agent is not preserved after upgrading from Release 4.6(1) to 4.7.
Workaround
CSCtb92910
No
Need to reflect all the states of FIPS card in the UI and CLI
Currently, the web console page only reflects whether or not the FIPS card is operational, but states like maintenance or initialization are not reflected.
Workaround
Note
CSCtb95381
No
Cisco NAC Appliance certificates not signed and/or expiring soon
Cisco NAC Appliance Release 4.7.0 comes with the following files that are either not signed or expire in March 2010:
•
•
•
CSCtb98457
No
Posture Assessment requirements for Vista machines results in the user being placed in the temporary role.
This has been observed in Windows Vista Home operating systems running version 4.6.2.113 of the Cisco NAC Agent.
Workaround
CSCtc00668
No
Mac Agent trying to update Avast even though application is up-to-date
Following login, the Mac Agent pops up prompting user to update "ANY" AV.
Workaround
1.
2.
3.
CSCtc01957
No
Firefox 3.5.2 Freezes and user cannot enter user credentials
After the applet loads in the Firefox browser, the user login page locks up and the user is unable to enter login credentials.This situation can occur when a user is attempting web login with a FireFox 3.5.2 browser for the very First time.
Workaround
CSCtc41408
No
Windows 7 tray icon default should be show icon and notifications
According to Microsoft, there is no way for a program to promote itself by setting the "Show Icon and Notifications" option. This can be done only by the user and only manually. Default behavior is to hide all icons.
Workaround
CSCtc46376
No
Windows WSUS update (Microsoft rules) is not working for KB890830
When a WSUS update is performed on a new installation of Windows 7 (where no updates have been applied), and the No UI option is selected for the requirement, the WSUS update can fail.
The portion of the Windows update that fails to install is the KB890830 update (Windows Malicious Software Removal Tool, http://support.microsoft.com/?kbid=890830). This upgrade must be installed with admin privileges and there is a one time EULA that the user must accept during installation.
After KB890830 is installed, there are monthly updates that are pushed out from Microsoft on patch Tuesday. The subsequent updates of KB890830 do not require admin privileges and they work fine on a client where the user is not a member of the admin group.
If users manually install KB890830 on a client system as a non-admin user using Windows Update, they are prompted for the administrator password and then get the EULA.
Workaround
CSCtc52252
No
Cannot uninstall the Agent using MSI executable with full quiet mode selected
If you open a Command Prompt window and run the MSI install/uninstall commands using the quiet option, the command fails.
Workaround
CSCtc59248
No
The Agent does not launch if IE has never been launched or the CA certificate is not installed
The Cisco NAC Agent login window does not pop up (or takes a long time to pop up) during initial login because:
•
•
This problem could also occur when the administrator kicks the user out of the NAC Appliance network after logging in via and OOB session.
Workaround
Note
CSCtc66277
No
IP refresh takes a minute and Agent vanishes after that
This issue can come up in a network where spanning tree merge has been configured on the switch. Configuring portfast minimizes the IP refresh time.
Note
CSCtc66798
No
Agent refreshing IP continuously, even though there is no change in VLAN
The Mac OS X console displays a lot of messages saying that the Mac OS X Agent is Refreshing the client machine IP address, even though the client machine is logged in via In-Band where there is no need to look for VLAN change detection and the IP address has actually not changed at all.
Workaround
CSCtc68565
No
Web Agent does not launch using ActiveX on a client machine where the administrator UAC is "default"
When using Windows 7 as a local machine administrator and a proxy server, Internet Explorer places the CAS into the intranet settings category, which automatically disables "Protected Mode."
Workaround
CSCtc86765
No
The Cisco NAC Agent does not pop up in a VPN environment upon re-connecting to the VPN server
This issue has been observed when power cycling a SOHO (Small office home office) DSL/Cable modem router, thus terminating the VPN connection.
Workaround
CSCtc90896
No
For McAfee Total Protection 5.0, you need to change firewall setting
AV definition file update for McAfee Total Protection 5.0 does not work with the default McAfee firewall settings.
Workaround
CSCtc91616
No
Support for Internationalized characters in usernames
It is unclear if Internationalized characters are supported in usernames for NAC. For example, some internationalized characters (like è) are allowed when creating a username, but user login fails. Other character sets (like Japanese) fail when attempting to create the user in the Local DB.
CSCtc92037
No
Mac agent in L2 non-strict mode does not pop up behind NAT router.
With L2 non-strict mode and Mac client behind NAT router, Mac agent does not pop up.
CSCtd07929
No
Anchor does not forward DHCP Packets in NAC OOB with Inter Subnet Mobility
Windows 7 client machines have complete network access only for a short time following authentication and posture assessment when they then roam to a foreign WLC. The result is that the client machine is automatically moved to the quarantine VLAN, and the Cisco NAC Agent reappears prompting the user for login credentials.
CSCtd04881
No
Serbian web install shows error and installer is English
A popup window appears with an error message in Serbian, which approximately translates to, "Writing error in applied transformation. Recommend to use a valid transformation path."
After clicking OK the installer launches in English, yet the application launches and is fully functional in Serbian.
Note
CSCtd12250
No
Incorrect AntiVirus def date is displayed in CAM reports
This issue has been observed on client machines with an iAntiVirus def date of 11/05, but the CAM report displays some day in August.
Note
CSCtd14712
No
CAS info missing from new Active CAM when master secret different
When the master secret is different on two CAMs in an HA deployment, some critical CAS information may be missing on the secondary (standby) node.
Workaround
CSCtd16666
No
Mac Agent installer is not creating preference.plist file
The Mac Agent automatically creates a preference.plist file when either or both of the "Auto Popup Login Window" or "Remember Me" options are enabled for the Mac Agent. If neither of these options are enabled for the Agent, the user would have to manually produce a preferences.plist file on the Mac OS X client machine.
CSCtd23998
No
Uploading large distribution files should not corrupt the database
When files larger than 50MB are uploaded to the CAM for File Distribution requirement types, the database snapshot could become corrupted. This issue has been observed on NAC-3140 CAMs where a distribution file larger than 50MB has been uploaded.
Workaround
CSCtd37076
No
Missing "Referral" option for LDAP type
Under User Management > Auth Servers for LDAP authentication type, the "Referral" option is missing in the web console for a pull-down menu with options "Manage(Ignore)" and "Handle(Follow)".
CSCtd39544
No
In certain cases, root CA certificate is categorized as CCA cert in SSL user interface
The SSL user interface for an X509 certificate chain is used with a multi-tier hierarchy may not display the Root CA cert.
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.7.2.10 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.
CSCtj81255
No
Two MAC addresses detected on neighbooring switch of ACS 1121 Appliance.
Symptom Two MAC addresses are detected on the switch interface connected to an ACS 1121 Appliance although only one interface is connected on the ACS 1121 Server eth 0.
Conditions
Workaround
Caution
Resolved Caveats - Release 4.7(1)
Refer to Enhancements in Release 4.7(1) for additional information.
Resolved Caveats - Cisco NAC Agent Vers 4.7.1.511/Mac OS X Vers 4.7.1.506
Refer to Enhancements in Release 4.7(1) for additional information.
New Installation of Release 4.7(1)
The following steps summarize how to perform new CD software installation of Release 4.7(1) on supported Cisco NAC Appliance hardware platforms (see Release 4.7(1) and Hardware Platform Support for additional support details).
To upgrade on an existing Cisco NAC Appliance, refer to the instructions in Upgrading to Release 4.7(1).
Note
For New Installation:
With Release 4.7(1), installation occurs in two phases:
1.
2.
Step 1
Step 2
Step 3
a.
b.
c.
Note
d.
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
In order to establish the initial secure communication channel between a CAM and CAS, you must import the root certificate from each appliance into the other appliance's trusted store so that the CAM can trust the CAS's certificate and vice-versa.
Note
Note
Upgrading to Release 4.7(1)
Note
This section provides instructions for how to upgrade your existing supported Cisco NAC Appliance platform to Release 4.7(1). If you need to perform a new CD software installation, refer instead to New Installation of Release 4.7(1).
Refer to the following information prior to upgrade:
•
•
•
•
•
Caution
Note
Paths for Upgrading to Release 4.7(1)
Depending on the type of upgrade you are performing, use one of the following sets of guidelines to successfully upgrade your Cisco NAC Appliance release image, Cisco NAC Appliance hardware, or both:
•
•
•
Note
Upgrading from Customer-Supplied Hardware to Release 4.7(1) on a NAC-3310/3350/3390 Platform
Note
If you are running the Cisco NAC Appliance software (Release 4.1(x) or earlier) on a non-Cisco NAC Appliance platform, you must purchase Cisco NAC Appliance hardware before you can upgrade your system to Release 4.5(x) or later. You may additionally need to obtain proper FlexLM product licenses. Once you obtain your new Cisco NAC Appliance hardware, Cisco recommends that you:
Step 1
Step 2
Step 3
Step 4
Note
Step 5
Step 6
Upgrading an Existing NAC-3310/3350/3390 Platform to Release 4.7(1)
Note
The Release 4.7(1) .ISO installation/upgrade image only supports upgrade from Release 4.5(x), 4.6(1), and 4.7(0). If you are running an older software version (e.g. Release 4.1(8) or earlier), you must first upgrade your system to one of the supported base releases for Release 4.7(1) upgrade.
Step 1
Step 2
Step 3
Upgrading from a NAC-3310/3350/3390 Platform to Release 4.7(1) on a NAC-3315/3355/3395 Platform
Note
If you are running the Cisco NAC Appliance software (Release 4.1(x) or earlier) on a NAC-3310/3350/3390 platform and are planning to upgrade to next generation NAC-3315/3355/3395 hardware you must first upgrade your existing system to Release 4.5(x) or later before shifting to a new hardware platform. You may additionally need to obtain proper FlexLM product licenses for your new hardware before upgrading, as well. Once you obtain your next generation NAC-3315/3355/3395 hardware, Cisco recommends that you:
Step 1
Step 2
Step 3
Step 4
Step 5
Changes for 4.7(1) Installation/Upgrade
Cisco NAC Appliance Release 4.7(1) is an Early Deployment software maintenance release. 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 Release 4.7(1), note the following:
•
Hardware Considerations
•
–
Note
–
You cannot install any Cisco NAC Appliance release other than Release 4.7(0) or later on the NAC-3315, NAC-3355, and NAC-3395. and you cannot upgrade to or install Release 4.5 and later on any non-Cisco platform. See Hardware Support for additional details.
•
•
•
Warning•
Features That May Change With Upgrade
•
•
•
Upgrade Changes
Warning
Note
•
•
•
•
•
•
•
•
–
–
–
Note
•
•
•
•
•
Note
Caution
Note
General Preparation for Upgrade
Caution
•
You must upgrade your Clean Access Manager and all your Clean Access Servers concurrently. The Cisco NAC Appliance architecture is not designed for heterogeneous support (i.e., some Clean Access Servers running 4.7(1) software and some running 4.7(0), 4.6(1), or 4.5(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 Cisco NAC Appliance CAMs/CASs, and for any other server hardware platform that supports the BIOS redirection to serial port functionality.
•
The NACAgentCFG.xml Agent configuration XML file packaged with the Cisco NAC Agent is not preserved after upgrading from Release 4.6(1) to 4.7(1). You must manually re-import the Agent configuration XML file to maintain client machine login behavior.
Note
•
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.
Warning•
Once you have upgraded your software to Release 4.7(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.7(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.
Upgrade Instructions for Standalone Machines
This section describes how to upgrade standalone (i.e. non-HA) CAM/CAS machines from Release 4.5(x), 4.6(1), or 4.7(0) to Release 4.7(1), and only applies to Cisco NAC-3310/3350/3390 or Cisco NAC-3315/3355/3395 platforms.
Note
To upgrade your CAM and CAS from Release 4.5(x), 4.6(1), or 4.7(0), insert the same Cisco NAC Appliance Release 4.7(1) installation CD-ROM (.ISO) into an existing Cisco NAC Appliance CAM or CAS and perform a "clean" or "graceful" shutdown and reboot for the system. The upgrade option from the CD-ROM automatically prompts you to choose whether you want to do a fresh Install or Upgrade to Release 4.7(1). For more information, see Upgrading to Release 4.7(1) and Known Issues with Web Upgrade in Release 4.1(3), 4.1(6), and 4.1(8).
Review Changes for 4.7(1) Installation/Upgrade and General Preparation for Upgrade before proceeding with these upgrade instructions.
Summary of Steps for Standalone Upgrade
The steps to upgrade standalone 4.5(x), 4.6(1), or 4.7(0) systems are as follows:
1.
2.
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 Install/Upgrade File
To upgrade your CAM and CAS from Release 4.5(x), 4.6(1), or 4.7(0), insert the same Cisco NAC Appliance Release 4.7(1) installation CD-ROM (.ISO) into an existing Cisco NAC Appliance CAM or CAS and perform a "clean" or "graceful" shutdown and reboot for the system. The upgrade option from the CD-ROM automatically prompts you to choose whether you want to do a fresh Install or Upgrade to Release 4.7(1). For more information, see Known Issues with Web Upgrade in Release 4.1(3), 4.1(6), and 4.1(8).
Step 1
Step 2
Step 3
Note
Upgrade Your CAS
Before upgrading your CAS be sure you obtain the Cisco NAC Appliance Release 4.7(1) install/upgrade image and burn it to a CD-ROM according to the instructions in Download the Install/Upgrade File.
Step 1
Step 2
WarningStep 3
Step 4
Checking for existing installations.Clean Access Server 4.7.0 installation detected.Please choose one of the following actions:1) Install.2) Upgrade.3) Exit.2Step 5
rebootStep 6
Tip
Upgrade Your CAM
Note
Before upgrading your CAM be sure you obtain the Cisco NAC Appliance Release 4.7(1) install/upgrade image and burn it to a CD-ROM according to the instructions in Download the Install/Upgrade File.
Step 1
Step 2
WarningStep 3
Step 4
Checking for existing installations.Clean Access Server 4.7.0 installation detected.Please choose one of the following actions:1) Install.2) Upgrade.3) Exit.2Step 5
...stopping CCA Manager...Welcome to the CCA Manager migration utility....Upgrading to newer rpms of 4.7.1...done....Upgrading CCA files...doneWindows Agent version upgraded to 4.7.1.511.Mac Agent was upgraded to version 4.7.1.506.Clearing Tomcat cache...checking ssl configuration...done.[root@cam1]#Step 6
rebootStep 7
Note
Tip
Upgrade Instructions for HA Pairs
This section describes how to upgrade high-availability (HA) pairs of CAM or CAS servers from Release 4.5(x), 4.6(1), or 4.7(0) to Release 4.7(1), and only applies to Cisco NAC-3310/3350/3390 or Cisco NAC-3315/3355/3395 platforms.
If you have standalone CAM/CAS servers, refer instead to Upgrade Instructions for Standalone Machines.
Note
To upgrade your CAM and CAS from Release 4.5(x), 4.6(1), or 4.7(0), insert the same Cisco NAC Appliance Release 4.7(1) installation CD-ROM (.ISO) into an existing Cisco NAC Appliance CAM or CAS and perform a "clean" or "graceful" shutdown and reboot for the system. The upgrade option from the CD-ROM automatically prompts you to choose whether you want to do a fresh Install or Upgrade to Release 4.7(1). For more information, see Known Issues with Web Upgrade in Release 4.1(3), 4.1(6), and 4.1(8).
Note
Note
Review Changes for 4.7(1) Installation/Upgrade and General Preparation for Upgrade before proceeding with these upgrade instructions.
Upgrading HA-CAM and HA-CAS Pairs
Note
The following steps show the recommended way to upgrade an existing high-availability (failover) pair of Clean Access Managers or Clean Access Servers.
Warning
Step 1
Step 2
/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 3
Step 4
Step 5
WarningStep 6
Step 7
Checking for existing installations.Clean Access Server 4.7.0 installation detected.Please choose one of the following actions:1) Install.2) Upgrade.3) Exit.2Step 8
...stopping CCA Manager...Welcome to the CCA Manager migration utility....Upgrading to newer rpms of 4.7.1...done....Upgrading CCA files...doneWindows Agent version upgraded to 4.7.1.511.Mac Agent was upgraded to version 4.7.1.506.Clearing Tomcat cache...checking ssl configuration...done.[root@cam1]#Step 9
Step 10
Step 11
WarningStep 12
Step 13
Checking for existing installations.Clean Access Server 4.7.0 installation detected.Please choose one of the following actions:1) Install.2) Upgrade.3) Exit.2Step 14
...stopping CCA Manager...Welcome to the CCA Manager migration utility....Upgrading to newer rpms of 4.7.1...done....Upgrading CCA files...doneWindows Agent version upgraded to 4.7.1.511.Mac Agent was upgraded to version 4.7.1.506.Clearing Tomcat cache...checking ssl configuration...done.[root@cam1]#Step 15
Step 16
Step 17
Note
Step 18
/perfigo/common/bin/ ./fostate.sh
Note
Known Issues for Cisco NAC Appliance
This section describes known issues when integrating Cisco NAC Appliance:
•
•
•
•
•
•
•
•
Known Issue with Enabling Web Login for Windows 7 Starter Edition Clients
The Cisco NAC Agent and Cisco NAC Web Agent do not support Windows 7 Starter Edition. Client machines with the Windows 7 Starter Edition operating system can only perform web login to verify user credentials. The solution to simultaneously provide Cisco NAC Appliance support for web login on Windows 7 Starter Edition client machines as well as Agent login for other Windows operating systems requires the administrator to add a web login page that classifies Windows 7 Starter Edition in a "WINDOWS_ALL" operating system context. To enable web login functions for client machines running Windows 7 Starter Edition:
•
•
–
–
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(3), 4.1(6), and 4.1(8)
In Cisco NAC Appliance Release 4.7(1), web upgrade is no longer supported and cannot be used to upgrade Cisco NAC Appliances on Release 4.1(3) and later. To upgrade your Cisco NAC Appliances from Release 4.1(3) and later, you must run the upgrade script via the in-place Install/Upgrade CD method, as described in Upgrading to Release 4.7(1).
Note
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 Cisco NAC Appliance CAM/CAS Boot Settings
When performing CD software installation, if a Cisco NAC Appliance CAM/CAS 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 the Cisco NAC Appliance CAM/CAS" section of the Cisco NAC Appliance Hardware Installation Guide, Release 4.7.
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.
Troubleshooting
This section provides troubleshooting information for the following topics:
•
•
•
•
•
•
•
•
•
•
Note
Enabling TLSv1 on Internet Explorer Version 6
Cisco NAC Appliance network administrators managing the CAM/CAS via web console and client machine browsers accessing a FIPS-compliant Cisco NAC Appliance Release 4.7(0) network require TLSv1 in order to "talk" to the network, which is disabled by default in Microsoft Internet Explorer Version 6.
To locate and enable this setting in IE version 6:
Step 1
Step 2
Step 3
Step 4
Step 5
Note
Windows Vista and Windows 7—IE 7 and IE 8 Certificate Revocation List
Note
In Release 4.6(1) and later, you can use the "AllowCRLChecks" attribute in the NACAgentCFG.xml file to turn off Certificate Revocation List (CRL) checking for the Cisco NAC Agent during discovery and negotiation with the CAS. For details, see the "Cisco NAC Agent XML Configuration File Settings" section in the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.7(2).
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 this issue, perform the following actions:
Step 1
Step 2
a.
b.
HA Active-Active Situation Due to Expired SSL Certificates
HA communication for both HA-CAMs and HA-CASs is handled over IPSec tunnels to secure all communications between the two HA pair appliances. This IPSec tunnel is negotiated based on the SSL certificates uploaded to the HA pairs for both CAM and CAS. In case the SSL certificates are not trusted by the two HA peers, have expired, or are no longer valid, the HA heartbeat communication between the two HA pairs breaks down, leading both HA pair appliances to assume the Active HA-Primary) role.
For CASs deployed in VGW mode, this can potentially create a Layer 2 loop that could bring down the network. HA-CAMs with expired or invalid SSL certificates could lead to an Active-Active situation where the database is not synced between the two HA-CAM appliances. Eventually, this situation leads to the CAMs losing all recent configuration changes and/or all recent user login information following an HA-CAM failover event.
As HA communication over IPSec tunnels requires valid SSL certificates on both the CAM and CAS, the CAM-CAS communication also breaks down if the SSL certificate expires on either the CAM or CAS. This situation leads to end user authentications failures and the CAS reverting to fallback mode per CAS configuration.
Administrators can minimize HA appliance Active-Active situations due to expired SSL certificates by using SSL certificates with longer validity periods and/or using serial port connection (if available and not used to control another CAM or CAS) for HA heartbeat. However, when you configure HA-CAMs to perform heartbeat functions over the serial link and the primary eth1 interface fails because of SSL certificate expiration, the CAM returns a database error indicating that it cannot sync with its HA peer and the administrator receives a "WARNING! Closed connections to peer [standby IP] database! Please restart peer node to bring databases in sync!!" error message in the CAM web console.
Note
Note
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.
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.
Generate Cisco NAC Agent Debug Logs
To generate Cisco NAC Agent logs using the Cisco Log Packager utility, refer to the "Create Agent Log Files Using the Cisco Log Packager" section of the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.7(2).
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 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/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 Configuration Guide, Release 4.7(2) or Cisco NAC Appliance - Clean Access Server Configuration Guide, Release 4.7(2).
Recovering Root Password for CAM/CAS
Refer to the "Password Recovery" chapter of the Cisco NAC Appliance Hardware Installation Guide, Release 4.7.
Troubleshooting CAM/CAS Certificate Issues
Refer to the "Troubleshooting Certificate Issues" sections of the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.7(2) or Cisco NAC Appliance - Clean Access Server Configuration Guide, Release 4.7(2).
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
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 an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. 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.
