Guest

Cisco NAC Appliance (Clean Access)

Release Notes for Cisco NAC Appliance, Version 4.7(0)

  • Viewing Options

  • PDF (792.2 KB)
  • Feedback
Release Notes for Cisco NAC Appliance, Version 4.7(0)

Table Of Contents

Release Notes for Cisco NAC Appliance,
Version 4.7(0)

Contents

Cisco NAC Appliance Releases

System and Hardware Requirements

Licensing

Hardware Support

Release 4.7 and Hardware Platform Support

Release 4.7 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

Software Compatibility

Release 4.7(0) CAM/CAS Upgrade Compatibility Matrix

Release 4.7(0) Compatibility Matrix

Release 4.7(0) Agent Upgrade Compatibility Matrix

Determining the Software Version

New and Changed Information

Enhancements in Release 4.7(0)

FIPS 140-2 Compliance

New Hardware Platform Support

Cisco NAC Appliance Operating System

Cisco NAC Appliance WAN Deployment Enhancements

Cisco NAC Windows Agent Version 4.7.1.15

Mac OS X Agent Version 4.7.0.2

Cisco NAC Web Agent Version 4.7.0

Features Optimized/Removed

Supported AV/AS Product List Enhancements (Windows Version 80, Mac OS X Version 4)

Cisco NAC Appliance Supported AV/AS Product Lists

Supported Mac OS X AV/AS Product List Version Summary

Mac OS X AV Support Chart

Mac OS X AS Support Chart

Caveats

Open Caveats - Release 4.7(0)

Resolved Caveats - Release 4.7(0)

Resolved Caveats - Cisco NAC Agent Version 4.7.1.15/Mac OS X Version 4.7.0.2

New Installation of Release 4.7(0)

Upgrading to Release 4.7(0)

Changes for 4.7(0) Installation/Upgrade

Hardware Considerations

Features That May Change With Upgrade

Upgrade Changes

Password Changes

General Preparation for Upgrade

Upgrading from Customer-Supplied Hardware to Cisco NAC Appliance Hardware Platforms

Upgrade Instructions for Standalone Machines

Create CAM DB Backup Snapshot

Download the Install/Upgrade File

Upgrade Your CAM

Upgrade Your CAS

Upgrade Instructions for HA Pairs

Upgrading HA-CAM and HA-CAS Pairs

Known Issues for Cisco NAC Appliance

Known Issue with Mass DHCP Address Deletion

Known Issue for VPN SSO Following Upgrade to Release 4.5 and Later

Known Issues with Web Upgrade in Release 4.1(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 Switches

Known Issues with Cisco 2200/4400 Wireless LAN Controllers (Airespace WLCs)

Known Issue for Windows Vista and IP Refresh/Renew

Troubleshooting

Enabling TLSv1 on Internet Explorer Version 6

Vista/IE 7 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

Cisco NAC Web Agent Logs

Generate Mac OS X Agent Debug Log

Creating CAM/CAS Support Logs

Recovering Root Password for CAM/CAS

Troubleshooting CAM/CAS Certificate Issues

Troubleshooting Switch Support Issues

Other Troubleshooting Information

Documentation Updates

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco NAC Appliance,
Version 4.7(0)


Document Number OL-19675-01 Revised: September 28, 2011

Contents

These release notes provide the latest cumulative release information for Cisco® NAC Appliance, Release 4.7. 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.

Cisco NAC Appliance Releases

System and Hardware Requirements

Software Compatibility

New and Changed Information

Cisco NAC Appliance Supported AV/AS Product Lists

Caveats

New Installation of Release 4.7(0)

Upgrading to Release 4.7(0)

Known Issues for Cisco NAC Appliance

Troubleshooting

Documentation Updates

Obtaining Documentation and Submitting a Service Request

Cisco NAC Appliance Releases

Cisco NAC Appliance Version
Availability

4.7(0) ED

September 29, 2009



Note Cisco recommends you deploy Cisco NAC Appliance Release 4.7(0) in test network before deploying in a production network.


System and Hardware Requirements

This section describes the following:

Licensing

Hardware Support

Supported Switches for Cisco NAC Appliance

VPN and Wireless Components Supported for Single Sign-On (SSO)

Additional Support Information

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 and Hardware Platform Support

Release 4.7 and Cisco NAC Profiler

Supported Switches for Cisco NAC Appliance

Release 4.7 and Hardware Platform Support

You can install or upgrade to Cisco NAC Appliance Release 4.7(0) on the following Cisco NAC Appliance platforms:

NAC-3315, NAC-3355, and NAC-3395—FIPS or non-FIPS platforms

NAC-3310, NAC-3350, NAC-3390, CCA-3140 (EOL)—non-FIPS only platforms


Note Cisco NAC-3315, NAC-3355, NAC-3395 platforms (FIPS or non-FIPS) support installation/upgrade of Release 4.7(0) and later only.



Note Cisco NAC Appliance release 4.7(0) does not support the Cisco NAC Network Module (NME-NAC-K9).


If the FIPS card in a 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.

Additionally, Cisco NAC Appliance Release 4.7(0) provides substantial changes and enhancements for product hardware support, installation, and upgrade:

A single product installation CD (.ISO) provides the option to perform CD installation on all supported appliance platforms. The installation package detects whether a CAS, CAM or SuperCAM was previously installed along with the software version.

To upgrade your CAM and CAS from 4.6(1), 4.5(x), or 4.1(3) and later releases, insert the same Cisco NAC Appliance Release 4.7(0) 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(0). For more information, see Upgrading to Release 4.7(0) and Known Issues with Web Upgrade in Release 4.1(3), 4.1(6), and 4.1(8).

The installation/upgrade CD does not execute if attempting to launch it on a non-supported platform. Refer to Changes for 4.7(0) Installation/Upgrade for additional details.

Legacy customers on non-appliance platforms who wish to upgrade to release 4.7(0) will need to purchase a supported platform to install the release 4.7(0) software. Refer to Upgrading from Customer-Supplied Hardware to Cisco NAC Appliance Hardware Platforms for additional details.

See also New Hardware Platform Support and Features Optimized/Removed for additional information.


Note You must run the same software version on all CAM/CAS appliances in your network.


Release 4.7 and Cisco NAC Profiler

Release 4.7(0) 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(0), 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 If currently running a Cisco NAC Profiler Server version other than 2.1.8-39, you will need to sync the Collector component version running on the NAC Server to same version as the Profiler Server for compatibility.



Note Cisco NAC Profiler and Cisco NAC Guest Server are not supported in FIPS-compliant deployments in Release 4.7(0).


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(0).

Table 1 Recommended WLC Platforms to Support Wireless OOB in Release 4.7

Cisco Wireless LAN Controller Model
Cisco Wireless LAN Controller Version
Cisco NAC Appliance Version

Cisco 4400 Series Wireless LAN Controllers

5.1

4.5 and later

Cisco 2000 Series Wireless LAN Controllers

Cisco Catalyst 3750G Integrated Wireless LAN Controller

Cisco Catalyst 6500/7600 Series Wireless Services Module (WiSM)

Cisco Wireless LAN Controller Module



Note Starting from Release 4.5, administrators can update the object IDs (OIDs) of supported WLC platforms by performing a CAM update (under Device Management > Clean Access > Updates).

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(0). If you encounter issues with WOOB support and are running a minimum IOS version listed as supported for your existing hardware platform in Switch Support for Cisco NAC Appliance, you may need to upgrade the IOS on your switch to the version listed in Table 2.

Table 2 Switch IOS Versions Tested and Known to Work for WOOB in Release 4.7

Device Model
Recommended IOS Version

Catalyst 2960

12.2(35)SE5

Catalyst 3560/ 3560-E

12.2(25)SEE3

Catalyst 3750/ 3750-E

12.2(25r)SEE4

Catalyst 4500

12.2(31)SGA

Catalyst 6500

12.2(33)SXH1
12.2(33)SXH2a


See Switch Support for Cisco NAC Appliance for complete details on:

All switch models and NME service modules that support Out-of-Band (OOB) deployment

Switches/NMEs that support VGW VLAN mapping

Known issues with switches/WLCs

Troubleshooting information

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

Cisco NAC Appliance Version
VPN Concentrator/Wireless Controller
VPN Clients

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 SSL VPN Client (Full Tunnel)

Cisco VPN Client (IPSec)

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 Only the SSL Tunnel Client mode of the Cisco WebVPN Services Module is currently supported.

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(0) CAM/CAS Upgrade Compatibility Matrix

Release 4.7(0) Compatibility Matrix

Release 4.7(0) Agent Upgrade Compatibility Matrix

Release 4.7(0) 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(0) CAM/CAS Upgrade Compatibility Matrix

Clean Access Manager 1
Clean Access Server 1 , 2
Upgrade From:
To:
Upgrade From:
To:

4.6(1)
4.5(x)
4.1(3) or later

4.7(0)

4.6(1)
4.5(x)
4.1(3) or later

4.7(0)

1 The Cisco NAC-3315, NAC-3355, and NAC-3395 appliances (both FIPS and non-FIPS) support installation/upgrade of Release 4.7(0) and later only. You can also install or upgrade to Release 4.7 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(0) 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 and Cisco NAC Profiler for details.


.

Release 4.7(0) 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.

Table 5 Release 4.7(0) CAM/CAS/Agent Compatibility Matrix 

Clean Access Manager 1 , 2
Clean Access
Server 1 , 2
Cisco NAC Appliance Agents 3
Windows
Mac OS X
Web Agent
FIPS 140-2 Compliant

4.7(0)

4.7(0)

4.7.1.15 4

N/A

N/A

Non-FIPS
Localized Server 5
Localized Agent 6

4.7(0)

4.7(0)

4.7.1.15
4.6.2.113
(All languages)

N/A

N/A

4.6.1.34
(Japanese and English only)

English-Only Server
English-Only Agent

4.7(0) 7

4.7(0)

4.7.1.15

4.7.0.2

4.7.0

4.6.2.113
4.6.1.34 8

4.5.2.0
4.5.1.0

4.5.0.0 8

4.5.0.0

4.1.3.0 9

4.1.8.0 9

4.1.6.0 9

4.1.3.0 9

English-Only Server
English-Only Agent

4.1(3) and later

4.1(3) and later

4.7.1.15 10

N/A

N/A

1 The Cisco NAC-3315, NAC-3355, and NAC-3395 appliances (both FIPS and non-FIPS) support installation/upgrade of Release 4.7(0) and later only. You can also install or upgrade to Release 4.7 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(0) Installation/Upgrade for additional details.

2 Make sure that both CAM and CAS are of same version.

3 See Enhancements in Release 4.7(0) for details on each version of the Windows/Mac OS X/Web Agents.

4 To remain FIPS-compliant, users logging into Cisco NAC Appliance via AD SSO must run Windows Vista and have the latest 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.

5 "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.

6 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. 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 CAM/CAS network.

7 When upgrading the CAM from version 4.1(1) and earlier, Agent files are automatically upgraded to the latest Agent version packaged with the CAM software image (e.g. 4.7.1.15). When upgrading the CAM from release 4.1(2) and later, the script will prompt you whether or not to upgrade the Agent files to the latest version. This allows administrators to schedule the Agent upgrade separately from the CAM/CAS server upgrade. Cisco recommends upgrading to the latest 4.7.1.15 Agent version as soon as possible.

8 4.6.x.x and 4.7.1.x Windows Agents and 4.6.x.x and 4.7.0.x 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.

9 CAM/CAS release 4.7(0) supports 4.1.3.0 and later Agents for basic compatibility (login/logout) and AV/AS product support. The maximum available AV/AS support is based on the maximum version of the 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 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 CAM/CAS network.


Release 4.7(0) 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 Auto-upgrade does not apply to the temporal Cisco NAC Web Agent, since it is updated on the CAM under Device Management > Clean Access > Updates > Update.


Refer to Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later for additional details related to Windows/Mac OS X/Web Agent support.

Table 6 Release 4.7(0) Agent Upgrade Compatibility Matrix

Clean Access Manager 1
Clean Access Server 1
Cisco NAC Appliance Agent 2
Upgrade From Cisco NAC Appliance Agent:
To Latest Compatible Cisco NAC Windows Agent:
Upgrade From Cisco Mac OS Agent
To Latest Compatible Mac OS X Version:

4.7(0)

4.7(0)

4.6.2.113
4.6.1.34
4.5.x.x 3
4.1.3.2 4 , 5 , 6

4.7.1.15 7 ,8 , 9

4.6.0.3
4.5.x.x
4.1.3.0

4.7.0.2 8

1 FIPS-compliant CAM/CAS Appliances only support new installations of Cisco NAC Appliance Release 4.7. You cannot upgrade to release 4.7 from earlier versions of Cisco NAC Appliance in FIPS appliances.

2 See Enhancements in Release 4.7(0) for details on each version of the Windows/Mac OS X/Web Agent.

3 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.

4 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.

5 When upgrading the CAM from version 4.1(1) and earlier, Agent files are automatically upgraded to the latest Agent version packaged with the CAM software image (e.g. 4.7.1.15). When upgrading the CAM from release 4.1(2) and later, the script will prompt you whether or not to upgrade the Agent files to the latest version. This allows administrators to schedule the Agent upgrade separately from the CAM/CAS server upgrade. Cisco recommends upgrading to the latest 4.7.1.15 Agent version as soon as possible.

6 CAM/CAS release 4.7(0) supports 4.1.3.0 and later Agents for basic compatibility (login/logout) and AV/AS product support. The maximum available AV/AS support is based on the maximum version of the 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.

7 To remain FIPS-compliant, users logging into Cisco NAC Appliance via AD SSO must run Windows Vista and have the latest 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.

8 4.6.x.x and 4.7.1.x Windows Agents and 4.6.x.x and 4.7.0.x 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 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.

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

SSH or console to the machine and type: cat /perfigo/build

CAM web console: Administration > CCA Manager > Software Upload | Current Version

Clean Access Server (CAS) Version

SSH or console to the machine and type cat /perfigo/build

CAS web console (https://<CAS_eth0_IP_address>/admin):
Administration > Software Upload | Current Version

CAM web console: Device Management > CCA Servers > List of Servers > Manage [CAS_IP] > Misc > Upgrade Logs | Current Version

Cisco NAC Appliance Agent Version (Windows, Mac OS, Web Agent)

CAM web console: Monitoring > Summary

Agent taskbar menu: right-click About for Agent version; right-click Properties for AV/AS software installed and Discovery Host (used for L3 deployments).

Cisco Clean Access Updates

CAM web console: Device Management > Clean Access > Updates > Summary

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(0)

Enhancements in Release 4.7(0)

FIPS 140-2 Compliance

New Hardware Platform Support

Cisco NAC Appliance WAN Deployment Enhancements

Cisco NAC Windows Agent Version 4.7.1.15

Mac OS X Agent Version 4.7.0.2

Cisco NAC Web Agent Version 4.7.0

Features Optimized/Removed

Supported AV/AS Product List Enhancements (Windows Version 80, Mac OS X Version 4)

FIPS 140-2 Compliance

This section describes the following topics:

Overview

Capabilities, Dependencies, and Restrictions

FIPS Compliance in HA Deployments

Trusted Certificates and Private Key Management with FIPS

FIPS and SSH

FIPS and the Cisco NAC Appliance SWISS Protocol

IPSec Considerations with FIPS

FIPS and SNMP Configuration

FIPS and Cisco Secure ACS as RADIUS Authentication Provider

FIPS with VPN SSO

FIPS with AD SSO

Overview

Cisco NAC Appliance Release 4.7 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.


Note Cisco NAC Profiler and Cisco NAC Guest Server are not supported in FIPS-compliant deployments in Release 4.7(0).


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 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 and Hardware Platform Support.


Note Once the FIPS card is Operational on the CAM/CAS, the position of the electromagnetic switch ("O," "M," or "I") on the FIPS card does not impact the performance of the card again until you reboot either the FIPS card or the appliance.


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 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 Cisco NAC Windows Agent Version 4.7.1.15.


Note 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 network require TLSv1 in order to "talk" to the network, which is disabled by default in Microsoft Internet Explorer Version 6. Mozilla Firefox has not shown this limitation. For details, see Enabling TLSv1 on Internet Explorer Version 6.


Capabilities, Dependencies, and Restrictions

FIPS 140-2 compliance in Release 4.7 introduces the following capabilities, dependencies, and restrictions:

1. Key Management is different than in non-FIPS Release 4.7. Both CAM and CAS store their private keys in the FIPS card. This private key is used for all Cisco NAC Appliance PKI-based security solutions (i.e. SSL, SSH, and IPSec). In addition, both the CAM and CAS store a master secret in the card. The master secret is used to secure passwords/shared secrets stored in the database or on file systems. For more information, see Trusted Certificates and Private Key Management with FIPS.

2. JSSE (the equivalent of OpenSSL in Java) is used:

a. On the CAM and CAS during JMX publishing

b. On the CAS to send HTTP requests to the CAM when users are logging in

c. On the CAM when using LDAP over SSL for authentication/lookup providers


Note JSSE uses the FIPS card for SSL handshakes and data security.


3. APACHE/MOD_SSL handles HTTP/HTTPS requests from:

a. User client machines to the CAS

b. Administrators when using both the CAM and CAS web consoles

c. The CAS to the CAM when users are logging in


Note MOD_SSL uses the FIPS card during SSL handshakes only. That is, data security is performed outside of the card.


4. IPSec secures:

a. CAM and CAS HA configurations

b. RADIUS authentication calls

c. VPN establishment and maintenance tasks


Note IPSec uses the FIPS card for handshakes only. That is, data security is performed outside of the card.


For more information, see IPSec Considerations with FIPS.

5. SSH—Just like APACHE and IPSec, SSH uses the FIPS card during SSL handshakes only. For more information, see FIPS and SSH.


Note When a FIPS card goes down, existing SSH web sessions still work; however, you cannot initiate any new sessions. You are also unable to initiate new SSH sessions if the FIPS card goes into error mode and/or has been erroneously left in Initialization state. In this case, the CAM/CAS console port is the only access method.


6. JGSS—JGSS is used for Kerberos and ADSSO. JGSS uses the FIPS card for securing data.

7. SNMP V3—SNMP V3 uses the FIPS card for securing data. For more information, see FIPS and SNMP Configuration.

8. SWISS—SWISS uses the FIPS card for securing data. For more information, see FIPS and the Cisco NAC Appliance SWISS Protocol.

9. Cisco WLCs support RADIUS accounting over IPSec using pre-shared-keys (which are not FIPS compliant) for IKE authentication, and do not support Certificate-based IKE authentication (which is FIPS compliant).

10. Windows XP client machines are not FIPS 140-2 compliant due to XP limitations. You cannot use AES for XP Kerberos, and 3DES encryption is not supported on Windows XP client machines.


Note Windows 2008 Server and the Windows Vista operating system are required to support AD SS0 in a FIPS-compliant Cisco NAC Appliance deployment.


11. LDAP—You must use Windows 2008 when performing LDAP lookups using GSSAPI in a FIPS 140-2 compliant deployment.

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

In Cisco NAC Appliance Release 4.7, 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:

Administration > Clean Access Manager > SSL > x509 Certificate

Administration > Clean Access Manager > SSL > Trusted Certificate Authorities

Administration > Clean Access Manager > SSL > x509 Certification Request

FIPS and SSH

SSH connections between FIPS and non-FIPS CAMs/CASs are supported in Cisco NAC Appliance Release 4.7. 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. Ensure the FIPS card operation switch is set to "O" (for operational mode).

b. Log into the CAM console interface as root.

c. Navigate to the /perfigo/common/bin/ directory.

d. Enter ./test_fips.sh. and verify the following output:

Installed FIPS card is nCipher
Info-FIPS file exists
Info-card is in operational mode
Info-httpd worker is in FIPS mode
Info-sshd up

Note You can also verify whether or not the FIPS card is properly installed and enabled in the Clean Access Manager by looking at the CAM Monitoring > Summary page. When FIPS is operational, the following status is displayed:

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.

IPSec Considerations with FIPS

Cisco NAC Appliance Release 4.7 uses IPSec for the following purposes:

CAM and CAS HA pairs (both FIPS and non-FIPS modes)

CAS file synchronization between HA-Primary and HA-Secondary nodes

CAM and CAS RADIUS server authentication calls in FIPS mode

ASA-CAS in FIPS mode

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 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:

OOB Management > Profiles > SNMP Receiver > SNMP Trap

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 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 or later 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 You cannot perform AD SSO in a FIPS-compliant network using Cisco Wireless LAN Controllers because the WLCs do not support using IPSec to secure session initiation and tear-down, which is required in the Cisco NAC Appliance FIPS 140-2 network configuration.


New Hardware Platform Support

Cisco NAC Appliance Release 4.7 introduces 6 new hardware appliance platforms: NAC-3315, NAC-3355, and NAC-3395 (SuperCAM), with and without the FIPS 140-2 (Federal Information Processing Standard) card option.

The next generation Cisco NAC Appliances are based on the IBM System x3250 M2 (NAC-3315) and IBM System x3550 M2 (NAC-3355 and NAC-3395) server platforms. Release 4.7 is designed to enable you to configure and deploy FIPS-compliant or non-FIPS CAMs and CASs on the new platforms. Additionally, you can perform installation/upgrade to Release 4.7 on existing HP-based NAC-3310, NAC-3350, NAC-3390 platforms as well as the CCA-3140 (EOL) platform, but in non-FIPS mode only.

FIPS-compliant appliances are shipped with the encryption cards installed to support key FIPS functionality on the appliances. The non-FIPS NAC-3355 and NAC-3395(SuperCAM) platforms feature an updated Cavium SSL accelerator card (Cavium CN1120-NHB-E). Note that the next generation appliances are shipped with either the FIPS card or the SSL accelerator card (non-FIPS), if applicable to the platform Additionally, FIPS and non-FIPS appliances cannot coexist in the same deployment. That is, Cisco does not support deployments where a non-FIPS CAM connects to one or more FIPS CASs, or vice-versa.


Note Cisco NAC-3315, NAC-3355, NAC-3395 platforms (FIPS or non-FIPS) support installation/upgrade of Release 4.7(0) and later only.



Note Cisco NAC Appliance release 4.7(0) does not support the Cisco NAC Network Module (NME-NAC-K9).


For more information, see Hardware Support and the Cisco NAC Appliance Hardware Installation Guide, Release 4.7.

Cisco NAC Appliance Operating System

The underlying operating system of the Cisco NAC Appliance Clean Access Manager/Clean Access Server has been changed from Fedora Core to CentOS 5.3 to support the new appliance hardware platforms as well as additional upgrade and installation enhancements.

Cisco NAC Appliance WAN Deployment Enhancements

Cisco NAC Appliance Release 4.7 addresses several internal JMX communication-related issues, thus improving overall CAM/CAS performance in the network:

The CAM no longer waits for all CASs to be connected and synced up before accepting any web console input. Traditionally, in Cisco NAC Appliance deployments consisting of large number of geographically dispersed CASs, the CAM would take a very long time to start up as it waited for all CASs to come online.

The CAM no longer assumes that a CAS is out of sync and automatically publishes a complete reconfiguration when intermittent WAN connectivity leads to temporary communication lapses between the CAM and CAS. Before Cisco NAC Appliance Release 4.7, if the WAN link were to exhibit flakiness (i.e. connectivity becoming temporarily unavailable), the CAM would assume the CAS had gone offline and required a complete configuration, even though the CAS configuration may actually be up-to-date.

All writes to the CAS are now serialized for consistency and integrity of configuration data. In Cisco NAC Appliance releases prior to release 4.7, there is no identification and avoidance of concurrent writes to CAS. Thus, in cases where CAS might have to restart, it was possible that two threads might concurrently publish to the same CAS, resulting in network degradation.

Cisco NAC Appliance no longer employs multiple publishing code paths from the CAM when pushing configurations to the CAS.

Cisco NAC Windows Agent Version 4.7.1.15

The Cisco NAC Agent for Windows systems is a completely redesigned and enhanced client for Cisco NAC Appliance. It replaces the Windows Clean Access Agent starting from Release 4.6(1) and later. Refer to Release 4.7(0) 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.0.2

There are no new features or enhancements to the Mac OS X Agent in Cisco NAC Appliance Release 4.7(0) except that the Mac OS X Agent version is updated to version 4.7.0.2.

Cisco NAC Web Agent Version 4.7.0

There are no new features or enhancements to the Cisco NAC Web Agent in Cisco NAC Appliance Release 4.7(0) except that the Cisco NAC Web Agent version is updated to version 4.7.0.

Features Optimized/Removed

The following Cisco NAC Appliance network components are not FIPS-compliant and cannot be included in FIPS-compliant deployments:

Cisco NAC Profiler

Cisco NAC Guest Server

Windows 2000 Client Machines

Macintosh Client Machines

Cisco NAC Network Module (NME-NAC-K9)


Note Cisco NAC Appliance release 4.7(0) does not support the Cisco NAC Network Module (NME-NAC-K9).


ADSSO with Windows XP client machines

ADSSO with any Windows Server other than Windows 2008 Server

Internet Explorer browsers (for both administraotr web console and client machine network access) without TLSv1 enabled. (See Enabling TLSv1 on Internet Explorer Version 6 for details)

Optimized Windows Operating System Support

Cisco NAC Agent version 4.7.1.15 can be installed on and supports the following Windows operating systems (same as 4.6.1.113 NAC Agent support):

Windows 2000 (SP4 and later)

Windows XP (32-bit SP2 and later)

Windows XP (64-bit SP2)

Windows Vista (32- and 64-bit, SP1 and later)

Cisco NAC Agent version 4.7.1.15 cannot be installed on and does not support the following Windows Operating Systems:

Windows 95

Windows 98

Windows Millennium

Windows NT

Windows 2000 Server

Windows 2003 Server

Release 4.7(0) backward compatibility with the 4.1.3.2 and later and 4.5.0.0 and later Windows Clean Access Agent. However, note that (as is the case in release 4.6(1)) Clean Access Agent updates are performed as "re-installations" using the full Clean Access Agent installer package (e.g. CCAAgentSetup-<version>-k9.tar.gz).

The ability to use the serial interface to provide a redundant heartbeat interface connection between CAMs/CASs is being deprecated in a future Cisco NAC Appliance release. Although this element still appears in the CAM web console, Cisco strongly recommends you do not try to configure the Heartbeat Serial Interface feature on the NAC-3315/3355/3395 for the redundant HA heartbeat function. (The associated Heartbeat Timeout value remains a valid configuration point, however, for deployments using optional Heartbeat UDP Interfaces 2 and 3.) For more information, see CSCtb59540.

Cisco NAC Appliance Release 4.7(0) no longer contains the "www.perfigo.com" Certificate Authority in the .ISO or upgrade image. Administrators requiring the "www.perfigo.com" CA in the network must manually import the CA from a local machine following installation or upgrade to release 4.7(0).

Supported AV/AS Product List Enhancements (Windows Version 80, Mac OS X Version 4)

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 In some cases, the specific AV/AS vendor software requires the user to have administrator privileges on the client machine to enable updates.


Windows Vista/XP

For Windows Vista/XP AV/AS support information on the Cisco NAC Agent (version 4.7.1.15) and Cisco NAC Web Agent (version 4.7.0), see the Cisco NAC Appliance Release 4.7 Supported Windows AV/AS Products document optimized for UTF-8 character display.

Mac OS X

Supported Mac OS X AV/AS Product List Version Summary

Mac OS X AV Support Chart

Mac OS X AS Support Chart


Note Cisco recommends keeping your Supported AV/AS Product List up-to-date on your CAM (particularly if you have updated the Windows Agent Setup/Patch version or Mac OS Agent) by configuring the Update Settings under Device Management > Clean Access > Updates > Update to Automatically check for updates starting from <x> every <y> hours.



Note Where possible, Cisco recommends using AV Rules mapped to AV Definition Update Requirements when checking antivirus software on clients, and AS Rules mapped to AS Definition Update Requirements when checking anti-spyware software on clients. In the case of non-supported AV or AS products, or if an AV/AS product/version is not available through AV Rules/AS Rules, administrators always have the option of creating their own custom checks, rules, and requirements for the AV/AS vendor (and/or using Cisco provided pc_ checks and pr_rules) through Device Management > Clean Access > Clean Access Agent (use New Check, New Rule, and New File/Link/Local Check Requirement). See the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.7(2) for configuration details.

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(0) 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.

Table 7 Supported Mac OS X AV/AS Product List Versions 

Version
Enhancements

Release 4.7(0)—4.7.0.2 Mac OS X Agent

Version 4

Added AV def date support:

VirusBarrier X5, 10.5.x

Added new AV product:

iAntiVirus, 1.x

Trend Micro Security for Macintosh, 1.x

Added AS product support:

Trend Micro Security for Macintosh, 1.x


Mac OS X AV Support Chart

Table 8 lists Mac OS X Supported AV Products for release 4.7(0) of the Cisco NAC Appliance software.

Table 8 Mac OS X Antivirus Product Support Chart
Version 4,
4.7.0.2 Mac OS X Agent, CAM/CAS Release 4.7(0) 

Product Name
Product Version
AV Checks Supported
(Minimum Agent Version Needed) 1
Live Update 2 ,
Installation
Virus Definition
ALWIL Software

avast! Antivirus

2.x

yes (4.1.4.0)

yes (4.1.4.0)

-

ClamWin

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

Computer Associates International, Inc.

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)

-

Intego

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)

-

McAfee, Inc.

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)

-

PC Tools Software

iAntiVirus

1.x

yes (4.7.0.0)

yes (4.7.0.0)

-

Sophos Plc.

Sophos Anti-Virus

4.x

yes (4.1.4.0)

yes (4.1.4.0)

-

Symantec Corp.

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, Inc.

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(0) of the Cisco NAC Appliance software.

Table 9 Mac OS X Antispyware Product Support Chart
Version 4, 4.7.0.2 Mac OS X Agent/CAM/CAS Release 4.7(0) 

Product Name
Product Version
AS Checks Supported
(Minimum Agent Version Needed) 1
Live Update 2
Installation
Spyware Definition
SecureMac.com, Inc.

MacScan

2.x

yes (4.1.4.0)

yes (4.1.4.0)

-

Trend Micro

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:

Open Caveats - Release 4.7(0)

Resolved Caveats - Release 4.7(0)

Resolved Caveats - Cisco NAC Agent Version 4.7.1.15/Mac OS X Version 4.7.0.2


Note If you are a registered cisco.com user, you can view Bug Toolkit on cisco.com at the following website:

http://www.cisco.com/cgi-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(0)

Table 10 List of Open Caveats (Sheet 1 of 32)

DDTS Number
Software Release 4.7(0)
Corrected
Caveat

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. Add a Managed Subnet having at least 2500+ IP addresses (for example 10.101.0.1/255.255.240.0) using CAM web page Device Management > Clean Access Servers > Manage [IP Address] > Advanced > Managed Subnet.

2. Create a DHCP subnet with 2500+ hosts using CAM web page Device Management > Clean Access Servers > Manage [IP Address] > Network > DHCP > Subnet List > New.

3. Edit the newly created subnet using CAM web page Device Management > Clean Access Servers > Manage [IP Address] > Network > DHCP > Subnet List > Edit.

4. Click Update. The CAM displays a warning informing the administrator that the current IP Range brings IP lease total up to a number that is incorrect. The CAM counts the IP address in the subnet twice, creating the incorrect count.

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   Either uncheck the box or set that timer to a non-zero value. If it is set to anything else, and the user hits the greyed out OK button while the IP is refreshing, then the Agent window closes successfully.

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   If your CAM/CAS machine time zone setting is currently specified via the UI using a generic option such as "EST," "HST," or "MST." change this to a location/city combination, such as "America/Denver."

Note CAM/CAS machines using time zone settings specified by the "service perfigo config" script or specified as location/city combinations in the UI, such as "America/Denver" are not affected by this issue.

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   The user simply needs to close the Agent dialog and it does not pop up again.

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   There are two methods to work around this issue:

Allow AD traffic through the CAS for clients in the Unauthenticated role.

Try to start the Agent manually after the install and auto load process fails.

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 This problem only happens when a Google tool bar is installed and enabled in Internet Explorer.

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   The user can manually Disable Agent login pop-up after authentication.

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   Export the CAS's root CA certificate and install it in the trusted store on the client machine.

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. MAC filter does not work for Mac OS X client machines connected to the network in a VPN environment.

2. L3 Strict mode does not allow Mac OS X users to log in and users see a "Access to network is blocked by the administrator" message.

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   To work around these issues:

For issue 1, use IP based filters for Mac OS X client machines in VPN environment.

For issue 2, Disable L3 strict mode on the CAS.

Note This issue does not affect Windows client machines in VPN environment.

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   Real-IP Gateway and Collector modules enabled on a CAS with ETH0 and or ETH1 configured for NetWatch.

Workaround   Do not configure the CAS' ETH0 trusted interface or ETH1 untrusted interface in the NetWatch configuration settings for the CAS Collector. It is not a supported configuration.

CSCsm20655

No

Cannot do a minor upgrade for Clean Access Agent from MSI package.

When CCAAgent.msi is used and the Clean Access Agent is upgraded to a minor version (e.g. 4.1.3.1 to 4.1.3.2) the following error message will be displayed:

"Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel."

This issue occurs because the Windows Installer uses only the first three fields of the product version. When a fourth field is included in the product version, the installer ignores the fourth field. For details refer to http://msdn2.microsoft.com/en-us/library/aa370859(VS.85).aspx

Workaround   Uninstall the program from Add/Remove Programs before installing it.

CSCsm25788

No

Avast 4.7 showing as not up to date with Cisco NAC Appliance Release 4.1(3)

User is told that Avast needs to be updated, but shows as up to date. This occurs when user is running Avast 4.7 and the Agent version is 4.1.3.0 or 4.1.3.1

Workaround   Create a custom check for Avast that allows the users on without verifying the definition version.

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   In order to use the IP refresh feature, you will need to:

1. Log into the Windows Vista client as an administrator.

2. Create a shortcut for IE on your desktop.

3. Launch it by right-clicking the shortcut and running it as administrator. This will allow the application to complete the IP Refresh/Renew. Otherwise, the user will need to do it manually via Command Prompt running as administrator.

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   The user needs to perform the remediation process again because it requires a little extra time for the live update tool to be ready following ClamXAV installation. If the user clicks the Remediate button again after seeing the requirement fail in the first round of remediation tasks, it works just fine.

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 CSCso61317 is a duplicate of this caveat.

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   There are three ways to work around this issue:

1. Reinstalling the Mac OS X Agent automatically reinstalls the missing dhcp_refresh file.

2. Users can sign on to Cisco NAC Appliance via web login. The Java applet installs the dhcp_refresh tool if the Install DHCP Refresh tool into Linux/MacOS system directory option is checked under User Page > Login Page > Edit > General.

3. When using the Apple Migration Assistant, the user can try to include /sbin/dhcp_refresh in the migration list.

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. A TGT, obtained with the AD account, is granted.

2. The ST for the CAS is granted.

3. Agent passes the local account information since the user has logged in locally to the machine.

4. Authorization fails which causes the blank provider list.

Note This bug is a duplicate of CSCso49473.

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   Create a custom check for Zone Alarm Security Suite definition.

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:

"SSL Communication 2008-07-23 00:31:29 SSLManager:authorizing server failed CN=10.201.217.201, OU=Perfigo, O=Cisco Systems, L=San Jose, ST=California, C=US"

"SSL Communication 2008-07-23 00:31:29 RMISocketFactory:Creating RMI socket failed to host 10.201.217.201:java.security.cert.CertificateException: Unauthorized server CN=10.201.217.201, OU=Perfigo, O=Cisco Systems, L=San Jose, ST=California, C=US"

Workaround   

Reboot the CAS and wait for the CAM to re-establish connection.

Reboot the CAM after deleting and removing the CAS from the Authorized CCA Server list using the CAM Device Management > CCA Servers > Authorization admin web console page.

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 The step to configure Extensions can be omitted.

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 There is no perfigo-log0.log.0 information, but a tcpdump from a CAM CLI session indicates that the CAM is receiving SNMP MAC notification traps.

Workaround   To re-establish correct SNMP trap handling on the CAM, open a CAM CLI session and enter the following commends:

service perfigo stop
service perfigo start
 
        

The CAM immediately starts processing the SNMP MAC notification traps from the problem switch(es).

Note After a period of time, however, this problem may appear again.

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 There is no known workaround for this issue

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   Disconnect the client machine from the switch and reconnect. This generates the MAC linkdown notification trap from the switch to the CAM updating the Discovered Clients list with the appropriate port information for this client machine.

Note This issue is cosmetic and does not affect Cisco NAC Appliance functionality.

CSCsu69247

No

ERROR: File type requirements does not exist

During CD installation of Cisco NAC Appliance Release 4.5, users can see the following error message in the nac_manager.log file:

"2008-09-21 19:25:55.592 -0700 ERROR com.perfigo.wlan.web.admin.DMSoftwareManager - DMSM syncDMSoftware: Directory('/perfigo/control/tomcat/webapps/packages/') for file type requirements does not exist"

This is a benign error message related to webapps packages that have been relocated in the installation script and has no impact on image installation.

CSCsu78379

No

Bandwidth settings for Receiver CAM roles should not change after Policy Sync

Steps to reproduce:

1. Create role on Master CAM, r1

2. Edit Upstream and Downstream Bandwidth fields of r1 to equal 1Kbps

3. Create role on Receiver CAM, r2

4. Edit Upstream and Downstream Bandwidth fields of r2 to equal 2 Kbps

5. Select role-based Master Policies to Export and perform manual sync

6. Upstream and Downstream Bandwidth fields for role r1 on Receiver CAM are changed to -1 (not 2 Kbps and not 1 Kbps).

Note Receiver's Up/Down Kbps, Mode, Burst should either not change or should be the same as the Master.

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   Bounce the switch port to clear the OUL and DCL.

CSCsu84977

No

CAS: ERROR /proc/click/intern_filter_group/failsafe

The following error message can appear to users during CD installation of Cisco NAC Appliance release 4.5 in Clean Access Servers:

"com.perfigo.wlan.jmx.Shell - /proc/click/intern_filter_group/failsafe (No such file or directory)"

This error message is related to a recently-removed file failsafe and has no impact on CD installation.

CSCsu88594

No

Removal of www.perfigo.com Root CA from GUI

The www.perfigo.com Root CA should be removed from the GUI.

With the default configuration there is no CA certificate button to offer on the web (or user) login page. The Cisco NAC Appliance administrator must configure user page content and specify whether or not to offer the Root CA along with its content from the dropdown menu (either the www.perfigo.com CA certificate or an imported third-party CA certificate—the default choice is the www.perfigo.com CA).

Workaround   To change this behavior go to Administration > User Pages > Login Page > Edit > Content and deselect the Root CA table entry.

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 In Cisco NAC Appliance releases prior to 4.5, there is no timeout function, and the database sync takes less time to complete because the CAM does not lock the database or verify the copy function.

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 This issue is not seen on the other requirement types.

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   Change to use the manual setting for eth1 on the fresh CD installed node or re-apply the HA config on the upgraded node.

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. Increase the "Heartbeat Timeout" value from the recommended 15 seconds to 30 seconds.

2. Or, run the heartbeat interface on Interface 3 (eth2 or eth3).

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   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.

CSCsv92867

No

DB conversion tool (Latin1 to UTF8)-iconv cannot work with &#8224; 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   To upgrade from release 4.1(6) or 4.5:

Perform a fresh install of release 4.6(1) or later (recommend).

Remove any foreign characters from the database prior to upgrade.

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:

Can log into the Clean Access Server and based on the level of authentication will dictate the system's access to the network.

Will see the NAC Agent tray icon.

Will be able to re-authenticate if kicked off the network via the Clean Access Server.

Note This does not impact client machines that are part of a Windows Domain. It also does not impact users who log out before logging in as another user.

Workaround   Logging out the first user or closing the Cisco NAC Agent before Fast Switching eliminates this problem.

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 This issue has been observed when upgrading from release 4.5 to 4.6(1) and later.

Workaround   Manually start the agent which then started the upgrade portion.

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   Operationally, everything is running normally (the machine is OOB and logged in per CAM and client) just the user interface is locked up.

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   Do not compile Mac OS X Agent logs in debug mode for extended periods of time.

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 This occurs only on the Mac Agent, and is a side effect of the Vlan Change Detection feature added in Cisco NAC Appliance Release 4.1(3).

Workaround   Disable the access-to-auth vlan-detection by following the instructions at http://www.cisco.com/en/US/docs/security/nac/appliance/configuration_guide/461/cam/m_oob.html.

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   Setting the CAS Fallback policy to "Allow All" or "Block All" solves the issue. Also, if you can ensure that the active CAS does not fail over when CAM is unreachable, this situation should not happen.

CSCsx18496

No

Cisco Log Packager crashes on XP Tablet PC with Restricted User credentials

CSCsx25557

No

NOD32 3.x Def date is not recognized by Clean Access Agent

Note The support chart incorrectly showed that this version can be updated. Version 3.x is not able to be updated by the Agent. The update will have to be performed manually from the NOD32 console.

Note There is no known workaround for this issue.

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 There is no known workaround for this issue.

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   Using hot corners to show all applications. With this tool, users can find the Agent and continue the process.

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   Please see Known Issue with Mass DHCP Address Deletion.

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   Click on the upper right icon that is saying click focus and then login.

CSCsx37073

No

Cisco NAC Agent does not pop-up if authentication server name is \\

Steps to reproduce:

1. Create a Kerberos authentication server named \\ in addition to Local DB.

2. Go to Login Page > Content and check Provider Label, Local DB, \\ (def provider).

3. Let the Cisco NAC Agent pop-up. User sees \\ and Local DB as Server options. (This is as expected.)

4. Go to Login Page > Content and uncheck Local DB.

5. Let the Cisco NAC Agent pop-up again. This time, user sees only the \\ Server option. (This is also as expected.)

6. Go to User Management > Auth Servers and delete \\.

7. Close the Cisco NAC Agent window, which does not pop-up again.

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   Avoid non-alphabetic naming conventions when configuring authentication servers in Cisco NAC Appliance.

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 This issue is observed with MS Live One 2.x. Auto Remediation fails when configured for MS Live One 2.x.

Workaround   Remediate AV manually while in the temporary role.

CSCsx47987

No

Incorrect behavior when client wired/wireless NIC on same subnet as CAS

Scenario to reproduce:

Client is connected through both wired and wireless port to the same OOB CAS.

Wireless NIC IP address is on the same subnet as that of CAS.

Wired port is assigned a lower metric compared to wireless, so wired is the preferred port.

Upon login, client connects through wireless and is listed in the CAM's CDL and OUL as connected via wireless interface even though the wired network path is preferred.

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. Create a Kerberos authentication server called my_krbr.

2. Create a login page and check the Local DB and my_krbr (def provider) Provider Labels.

3. Let the Cisco NAC Agent pop-up. Both my_krbr (def provider) and the Local DB provider options are available.

4. Go to the list of Authentication Servers and rename my_krbr to \.

5. Go to the Login page. \ appears as the new Kerberos name.

6. Close the Cisco NAC Agent and let it automatically pop-up again.

This time, the authentication provider list only shows Local DB—\ is missing.

Workaround   Avoid non-alphabetic naming conventions when configuring authentication servers in Cisco NAC Appliance.

CSCsx78577

No

ClamAV not showing def date

ClamAV does not provide the definition date to the Agent.

Workaround   There is no workaround at this time. This is a known issue.

CSCsx80459

No

JAVA_OPTS_TO of "" seen in CAM upgrade details

When upgrading the Clean Access Manage to release 4.5(1), the additional message "Ended up with JAVA_OPTS_TO of """ may be seen in the upgrade details text displayed under Administration > CCA Manager > Software Upload. This message does not affect upgrade and is safe to ignore.

Welcome to the CCA Manager migration utility.
 
        
...Upgrading to newer rpms of 4.5.1...done.
...Upgrading CCA files...Ended up with JAVA_OPTS_TO of ""
Preparing...                
##################################################
nac_manager                 
##################################################

CSCsx81395

No

Sophos AV Definition rule fails even if Mac OS Agent has the latest definition

The remediation window pops up for updating the Sophos definition files on the Mac OS Agent even though Sophos is updated.

This occurs if Sophos is installed on the Mac OS client and an AV definition check for Sophos is configured on the CAM.

Workaround   There is no workaround at this time.

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   None.

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   This issue is not actually a bug. Caching behavior is configurable using the Authentication Cache Timeout setting available on the CAM User Management > Auth Servers > List/New web console page. If it is desired to never cache user login, set this timer to 0.

Note This workaround may affect CAM performance due to increased authentication traffic for multiple users logging into Cisco NAC Appliance.

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 There is no known workaround for this issue.

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   Some of the buttons are still readable. Click Collect Data > Locate File and then click Exit.

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 There is no known workaround for this issue. Log Packager is still functioning, but it is missing some non-critical system troubleshooting information.

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 This issue has been observed in a deployment where JAWS is set to run at system startup.

Workaround   You have to select the Cisco NAC Agent from the taskbar to have the Agent display announced.

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   The settings.plist file does not contain the VlanDetectInterval value by default, so Mac users must add a "VlanDetectInterval value 0" child string and then restart the Agent to address the AnyConnect connection issues.

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   Press the Windows key to go back to the Windows desktop.

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 This does not impact the upgrade process.

Workaround   A blind user will need to check the running applications in the Windows taskbar.

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   Click OK on the error display. The AV update is actually successful.

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   If agent does not get downloaded for a long time, remove the contents of /perfigo/access/apache/www/perfigo_download to start the download of the file.

Note Problem usually corrects itself after a while, but if it does not, Cisco recommends following this workaround.

CSCsz85892

No

Web login display Guest ID instead of Username

Steps to reproduce:

1. Add a Kerberos auth server named "k1."

2. Enable the Local DB and "k1" providers on the Login Page, and make "k1" the default provider.

3. Open a browser and check that Username is there and "k1" is the default provider.

4. Delete "k1" from the roster of Auth Servers.

5. Open another browser and note that the user name is now "Guest ID."

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 After the CAM completes its parallel connection at the end of the database restoration, it starts to publish to many of the CASs via serial connection.

Workaround   DBrestore happens and CAS do get connected and publishing completed.

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 There is no known workaround for this issue.

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   Manually edit the XML file on the client machine or keep using the Discovery Host address specified on the CAM.

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.

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 After a few minutes, CASs come back online.

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   The user must Exit the Cisco NAC Agent using the Windows Systray icon and launch the Agent again.

CSCta85491

No

Cisco API: addmac is susceptible to XSS on the CAS when using local device filter

Steps to reproduce:

1. Call addmac for a global device filter where the description contains <script>alert('CAS specific XSS'); </script>. No pop-up alert box is observed.

2. Call addmac for a CAS-specific local device filter where the description contains <script>alert('CAS specific XSS'); </script>.

3. Go to the CAM web console and click the manage icon for the CAS in question and then go to Filter > Devices, You should see a pop-up alert box with a CAS-specific XSS message.

Note This is not an issue for global device filters calling addmac.

CSCta97229

No

Collector Modules show "Stopping" instead of "Stopped" in Profiler UI

This issue happens when the administrator manually stops the Profiler Collector.

Workaround   Services are actually stopped. You can enter service collector status in the CAS CLI to verify the current state.

CSCtb02366

No

"ANY" AS update does not work for MS Defender on 64-bit Vista

Workaround   Set up the check using Microsoft as the AS vendor.

Note The same requirement works correctly on a Vista Home Professional PC.

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   Bring up eth0 connectivity before bringing up any other heartbeat interface.

Note Cisco strongly recommends configuring the HA Linkdetect feature on the CAM's eth0 interface. If this is done, the above issue does not occur.

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. Client is initially associated to AP1. Do a posture validation on the client and client entry is shown on WLC1.

2. Now disable AP1. The client machine is associated to AP2, the client entry is deleted from WLC1, and the client entry is now available only on WLC2. Client is now in Access VLAN and client entry shown on WLC2.

However, the CAM still lists WLC1 IP address with client entry.

3. Clear the CDL and OUL from the CAM. The client still appears in the Access VLAN, has complete access to the internet, and an error appears in the CAM's nac-manager.log file after clearing the CDL and OUL on the CAM.

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   The problem is caused by a Windows TCP/IP feature called "Dead Gateway Detection." To disable this feature, set the "EnableDeadGWDetect" registry value under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters to 0, then reboot the client machine.

CSCtb32045

No

Message while preparing root file system during installation misleading

Fresh image installation on a NAC-3395 takes at least 30 minutes for preparation.

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 Microsoft has documented this error on its support site at http://support.microsoft.com/kb/957072. Unfortunately, Windows 2008 server SP2 with the latest Windows updates as of 8/20/09 did not resolve this problem.

Note There is no known workaround for this issue.

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.gz

the database restoration process returns a scripting error. This issue is only cosmetic and does not affect the database restore functionality.

Workaround   Do not rename the database snapshot (for identification purposes, for example) after it has been created.

CSCtb43264

No

Both HA-CAS nodes stuck in active-active state

Steps to reproduce:

1. Do a fresh install of both CAS nodes and the CAM.

2. Configure high availability for the CAS HA-pair.

3. Reboot both the HA-CAS nodes at the same time.

4. Add the primary CAS to the CAM. The CAM reports the CAS to be disconnected.

5. Click Manage where the CAM web console reports "SSKEY on server does not match the value in database."

6. Click Advanced > Managed Subnet and add a managed subnet. Both CASs appear to be active-active.

This is a dangerous scenario creating a Layer 2 broadcast loop that almost immediately brings down the network.

Workaround   There are two possible remedies for this issue:

Configure a longer heartbeat timeout interval for the HA-pair.

Add an additional heartbeat Ethernet interface link (eth2, eth3).

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   Enter service perfigo restart on the CAS to resolve this issue.

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   Restart the Standby node to bring it back in sync with Active.

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 You can use the CLI to display the correct state of the HA-Secondary as follows:

[root@NACM-1 bin]# ./fostate.sh
My node is standby, peer node is active
 
        

CSCtb63619

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   Retry the operation again when the queue frees up or increase the max queue size. To increase the queue size:

1. Modify the /perfigo/control/bin/starttomcat file by adding the following at the end of the 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. Enter service perfigo restart to enable the change.

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   Upload a new NACAgentCFG.xml file.

CSCtb71856

No

Cisco API doc: Missing ssip is required for removesubnet

removesubnet API function returns "<!--error=Subnet could not be found-->". There is no mention of ssip in removesubnet description in Cisco NAC Appliance release 4.7.

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   If the CAM Monitoring > Summary page does not show that the FIPS card is operational, assume it is in one of the other states (Maintenance or Initialization). You can also manually verify the electromagnetic switch position ("O," "M," or "I") on the FIPS card, itself when you look at the back of the NAC-3315/3355/3395 chassis.

Note Once the FIPS card is Operational on the CAM/CAS, the position of the electromagnetic switch on the FIPS card does not come into play again until you reboot either the FIPS card or the appliance.

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:

CCALogin.cab Cisco certs expires 3/10 versign 6/12 (CCAWebLogin.ocx 2.3.0.0 not signed)

CiscoNACLoginFacilitator Java signature expiring in march/2010 (taweb.jar expires 3/10 please see attached file)

CCALogin.jar entry was signed on 10/3/08 1:10 PM (X.509, CN=Cisco Systems, OU=INFORMATION SECURITY, O=Cisco Systems, L=San Jose, ST=California, C=US [certificate is valid from 2/25/08 7:00 PM to 3/31/10 7:59 PM])

CSCtb98457

No

Clean access requirements for Vista machine result 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   Disable compatibility mode for Nacagent.exe. Compatibility mode can be disabled by un-checking (disabling) the "Run this program in compatibility mode for" option in the file properties for NACagent.exe.

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   To work around this issue:

1. Change the Mac OS X Agent LogLevel in the settings.plist file to "Error."

2. Log out of the Cisco NAC Appliance network, and exit the Agent to ensure the new LogLevel will take effect.

3. Log back into the network. The problem should now be gone.

CSCtc01871

No

Reports page returns error

Steps to reproduce:

1. Generate around 80 Agent reports.

2. Go to Device Management > Clean Access > Clean Access Agent > Reports.

3. Display n either 10, 25, or 100 reports and click on the Reports tab.

The Reports page displays a pop-up window with the following message:

"SubmitOnEvent: can't find button or link `reportsForm:filterButton'"

CSCtc01957

No

Firefox 3.5.2 Freezes & hence can not 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   The workaround for this issue is to minimize the Browser or open a new browser window.

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   Use a US layout keyboard or ensure that you know the key mapping if you are connecting a keyboard of different layout.

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   Only one Ethernet interface, eth 0 is connected between ACS and Switch.

Workaround   Disable BMC (Baseboard Management Controller) feature using BIOS setup.


Caution To help prevent a potential network security threat, Cisco strongly recommends physically disconnecting from the Cisco NAC console management port when you are not using it. For more details, see http://seclists.org/fulldisclosure/2011/Apr/55, which applies to the Cisco ISE, Cisco NAC Appliance, and Cisco Secure ACS hardware platforms.

Resolved Caveats - Release 4.7(0)

Table 11 List of Resolved Caveats (Sheet 1 of 5)

DDTS Number
Software Release 4.7(0)
Corrected
Caveat

CSCsu39867

Yes

Deprecated SSL Protocol Usage

During a vulnerability scan, Cisco NAC Appliance release 4.1(6) and earlier shows that is using SSLv2 or earlier.

Java uses a backward compatible SSLv2 Hello message, but the rest of the messages are all TLSv1 and SSLv3. Cisco recommends preventing Java from using these SSLV2 Hellos in order to remove any doubts.

Note There is no known workaround for this issue.

CSCsv10336

Yes

CAS does not accommodate RADIUS accounting packets greater than 8192 bytes

Cisco Clean Access Servers appear to have a 8192 byte limitation in the size of accounting packets they can successfully reassemble when performing VPN SSO. Packets exceeding 8192 bytes result in an "INFO: Accounting Packet - Stated packet length [10696] is less than physical packet length [8192]" error message.

This limitation means that VPN SSO users with a large amount of groups or other information specified within the RADIUS accounting packet are unable to use SSO and "fall back" to a different authentication mechanism.

Workaround   Set a local authentication fallback.

CSCsv49225

Yes

Unable to create a VLAN Profile when the VLAN name contains a hyphen

This problem only applies to creating a VLAN profile and not when using the name for VLAN mapping.

Note There is no known workaround for this issue.

CSCsv84296

Yes

SNMPv3 traps from switch are not interpreted by CAM if authpriv is used

Symptom   

A) Switch sends SNMPv3 TRAP with AuthNopriv, CAM can listen to the TRAP.

B) Switch sends SNMPv3 TRAP with Authpriv (MD5-DES), CAM cannot listen to the TRAP.

C) Switch sends SNMPv3 TRAP with Authpriv (MD5-DES) to a Software Trap receiver works fine.

Conditions   This condition arises when the Switch and the CAM are configured to use SNMPv3 along with authpriv.

Workaround   A temporary workaround is to use SNMPv3 with authnopriv OR use SNMPv2 altogether.

CSCsy60430

Yes

Need TLS only option for Web Services on CAM/CAS for increased Security

Web services allow cryptographically weak SSLv2 connections. SSL to CAM and CAS can run weak SSLv2. Need enhancement for TLS-only options in Browsers.

Note There is no known workaround for this issue.

CSCsz12525

Yes

Multiple OpenSSL Issues

Various OpenSSL issues have been observed in Cisco NAC Appliance CAM/CAS code base, including the following:

ASN1 printing crash (CVE-2009-0590)

Incorrect Error Checking During CMS verification (CVE-2009-0591)

Invalid ASN1 clearing check (CVE-2009-0789)

Cisco has updated the Cisco NAC Appliance code to feature OpenSSL 0.9.8k that addresses the vulnerabilities related to this topic.

CSCsz52265

Yes

LDAP user role mapping not working in some cases

LDAP user role mapping does not work properly in the following two scenarios:

1. Same user name (sAMAccountName) in multiple domains, when the domains are either in parent child relation/or child of the same parent.

2. Users present in multiple domains which are in different Forests.

Note There is no known workaround for this issue.

CSCsz56761

Yes

Memory leak in Java process when Kerberos authentication is used

A memory leak in a key Java process renders the CAM unresponsive to client authentication requests and also affects web console access.

Release 4.7.0 uses Java 6, which has fixed the GSS-API/Kerberos memory leaks seen in previous releases

CSCta02433

Yes

"Swiss Communication Logging" buttons do not work

Even though the option has been enabled in the Administrator web console page, Swiss log messages are missing from the nac_server.log file.

Workaround   The "CCA Server General Logging" and "CAS/CAM Communication Logging" options must be set to same desired log level.

CSCta06772

Yes

NAC RADIUS CAM options are available on 4.6(1) release

Note These options have been removed in release 4.7(0).

CSCta34052

Yes

Java Memory leak causing CAM to crash

Customers using Kerberos or LDAP over GSSAPI see older versions of Java running out of memory due to a leak. This memory leak has been addressed in more recent versions of java. (Specifically, Java 6.)

Workaround   While Cisco validates the use of Java 6 in Cisco NAC Appliance, customers may want to use LDAP with simple authentication over SSL.

CSCta83746

Yes

Upgrade from 4.1(8) > 4.6(1) or from 4.5 > 4.6(1) fails

If there is a large amount of report data and file distribution is enabled, the upgrade to 4.6.1 fails with a "version mismatch" error.

The release 4.7.0 upgrade process detects the failure and requests that the affected customer contact TAC.

CSCta95647

Yes

Safari 4 on Mac OS X does not appropriately load the web client Java applet

When browsing to the login page, users get a prompt to accept the certificate for the Java applet, but only see a blank screen or a dialog informing them that the Java applet could not be loaded.

Workaround   There are a few possible workarounds for this issue:

1. If the user is not in a Layer 3 environment (which requires the applet), it should be disabled. If users are on a VLAN that does not require the applet, you could create a separate user page.

2. Go to Preferences and disable Javascript in Safari 4.

3. After the necessary permissions have been secured, reload the home page to get a new web login re-direct. The applet typically loads correctly the second time around.

Note This issue does not occur in the Firefox browser.

CSCtb05027

Yes

addsubnet API Does Not Work in Cisco NAC Appliance release 4.6(1)

The addsubnet API with a specific set of assigned parameters generates an HTTP 500 error.

CSCtb59540

Yes

Need procedure to enable heartbeat on serial interface on NAC-3315/3355/3395

In addition to enabling the function using the Heartbeat Serial Interface setting in the CAM/CAS web console, the administrator also needs to configure console redirection in the chassis BIOS settings, as described in the following workaround.

Workaround   If you cannot configure either optional Heartbeat UDP Interface 2 or 3 as a redundant heartbeat interface for HA CAMs/CASs, you can use the following sections to set up the NAC-3315 and NAC-3355/3395 to use the serial port for the HA heartbeat function:

NAC-3315

1. Log into the CAM/CAS CLI and reboot the appliance.

2. During the reboot process, press "F1" to interrupt the normal boot and display the Setup menu.

3. Go to Configuration/Setup Utility > Devices and I/O Ports > Remote Console Redirection > Remote Console Serial Port and change the "Remote Console Serial Port" setting to "Disabled" under "Serial Port 1." (Use the left/right arrow keys to cycle through the options for this setting.)

4. Save the new setting and reboot the appliance for this change to take effect.

After the system reboots, you can use the serial port on the CAM/CAS to perform the heartbeat function between HA peer CAMs/CASs.

NAC-3355/3395

1. Log into the CAM/CAS CLI and reboot the appliance.

2. During the reboot process, press "F1" to interrupt the normal boot and display the Setup menu.

3. Go to System Configuration and Boot Management > System Settings > Devices and I/O Ports > Console Redirection Settings and change the "Remote Console" setting to "Disabled." (Use the up/down arrow keys to cycle through the options for this setting.)

4. Save the new setting and reboot the appliance for this change to take effect.

After the system reboots, you can use the serial port on the CAM/CAS to perform the heartbeat function between HA peer CAMs/CASs.


Resolved Caveats - Cisco NAC Agent Version 4.7.1.15/Mac OS X Version 4.7.0.2

Refer to Enhancements in Release 4.7(0) for additional information.

Table 12 List of Resolved Caveats (Sheet 1 of 2)

DDTS Number
Cisco NAC Agent Version 4.7.1.15/Mac OS X Version 4.7.0.2
Corrected
Caveat

CSCsy24791

Yes

Agent does not detect Kaspersky Anti-Virus (Russian version)

CSCta26692

Yes

McAfee 8.7/8.5 hangs when doing update with Cisco NAC Agent

The McAfee 8.7 or 8.5 update process initiated by the Cisco NAC Agent appears to fail even though it actually passes.

Workaround   Upgrade to 4.6.2.113 or later if using McAfee 8.7, or ignore the error.

CSCta35376

Yes

If Agent Popup option disabled, Agent does not download config file

If the Agent "Popup Login Window" systray option is disabled, the Agent does not download the Agent configuration XML file from the CAM. As a result, the user cannot install configuration changes uploaded to the CAM on the client machine.

Workaround   Users can manually enable the "Popup Login Window" option from the system tray.

CSCta60490

Yes

Agent does not work when EVDO, vpn, and split tunneling are used

The Cisco NAC Agent does not appear when the user is connecting to the Cisco NAC Appliance network via VPN over EVDO and split tunneling is enabled on the vpn device.

Workaround   Disable split tunneling and try logging in again.

CSCta71241

Yes

VLAN Detect does not start if probe for VLAN change fails

The user's client machine IP address is not refreshed upon moving back to the Authentication VLAN. This is a rare situation where the Agent fails to send the appropriate SWISS probe for VLAN detection.

Workaround   Manually renew the client machine IP address.

CSCta94182

Yes

DisableL3SwissDelay not implemented in the Cisco NAC Agent for release 4.6(1)

The DisableL3SwissDelay configuration entry is not available in the 4.6(1) release. There is no way for Agent to stop the back-off for L3 discovery probes.

CSCta99167

Yes

Registry check not working for REG_EXPAND_SZ type

A requirement with a registry value check whose type is "REG_EXPAND_SZ" always fails.

There is no known workaround for this issue.

CSCtb15432

Yes

Custom check for a 64-bit Vista SP1 client machine fails

"Contains: Service Pack" checks fail on 64-bit Vista SP1 client machines featuring the required registry key value:

"HKLM\SOFTWARE\Microsoft\Windows NT\Current Version\CSDVersion Service Pack 1"

Note The same check works on 32-bit Vista client machines.

CSCtb19938

Yes

Mac Agent crashes when attempting to posture assess Antivirus

When the 4.6(1) Mac Agent is used and an antivirus is installed on the system for which there is a rule set up to check, the Agent crashes (icon disappears from menu bar, user interface disappears, process terminates). This issue occurs immediately after logging in while the "Please Wait" screen is up.

Note This only occurs on PPC-based Mac OS 10.4 or 10.5 systems - does not appear to affect Intel based Macs.

There is no known workaround for this issue.

CSCtb30416

Yes

VLAN Detect does not work if Nortel VPN client is installed

Access to Authentication VLAN Change Detection does not work if Nortel VPN Client is installed. (The VPN tunnel does not have to be up.)

Workaround   There is no workaround for this issue other than uninstalling Nortel VPN Client.

CSCtb90439

Yes

Login fails when "&" character is in title of a posture requirement

Cisco NAC Agent users may log in, then be forced to authenticate again. Users may be using an audit requirement and may be missing Microsoft patch for MS09-047.

Workaround   Even though the requirement is an audit requirement, if you install the MS09-047 patch, the symptoms go away.


New Installation of Release 4.7(0)

The following steps summarize how to perform new CD software installation of release 4.7(0) on supported Cisco NAC Appliance hardware platforms (see Release 4.7 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(0).

For New Installation:

With release 4.7(0), installation occurs in two phases:

1. The software is installed from the CD, and when complete, the CD is ejected from the appliance.

2. The admin logs in and performs the initial configuration.


Step 1 If you are going to perform a new installation but are running a previous version of Cisco NAC Appliance, Cisco recommends backing up your current Clean Access Manager installation and saving the snapshot on your local computer, as described in General Preparation for Upgrade.

Step 2 Follow the instructions on your welcome letter to obtain product license files for your installation. See Licensing for details. (If you are evaluating Cisco Clean Access, visit http://www.cisco.com/go/license/public to obtain an evaluation license.)

Step 3 Install the latest version of 4.7 on each Clean Access Server and Clean Access Manager, as follows:

a. Log in to the Cisco Software Download Site at http://www.cisco.com/public/sw-center/index.shtml. You will likely be required to provide your CCO credentials.

b. Navigate to Security > Endpoint Security > Cisco Network Access Control > Cisco NAC Appliance > Cisco NAC Appliance 4.7.

c. Download the latest 4.7 .ISO image (e.g. nac-4.7_0-K9.iso) and burn the image as a bootable disk to a CD-R.


Note Cisco recommends burning the .ISO image to a CD-R using speeds 10x or lower. Higher speeds can result in corrupted/unbootable installation CDs.


d. Insert the CD into the CD-ROM drive of each installation server, and follow the instructions in the auto-run installer.

Step 4 After software installation, access the Clean Access Manager web admin console by opening a web browser and typing the IP address of the CAM as the URL. The Clean Access Manager License Form will appear the first time you do this to prompt you to install your FlexLM license files.

Step 5 Install a valid FlexLM product license file for the Clean Access Manager (either evaluation, starter kit, or individual license).

Step 6 At the admin login prompt, login with the web console username and password you configured when you installed the Clean Access Manager.

Step 7 In the web console, navigate to Administration > CCA Manager > Licensing to install any additional license files for your CASs, CAM HA pairs or CAS HA pairs. You must install the CAS license to add the CASs to the CAM and an OOB CAS license to enable OOB features on the CAM.

Step 8 For detailed steps on initial configuration, refer to the Cisco NAC Appliance Hardware Installation Guide, Release 4.7.

For additional information on configuring your deployment, including adding the CAS(s) to the CAM, refer to the following guides:

Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.7(2)

Cisco NAC Appliance - Clean Access Server Configuration Guide, Release 4.7(2)



Note Clean Access Manager 4.7(0) is bundled with version 4.7.1.15 of the Cisco NAC Agent and version 4.7.0.2 of the Mac OS X Agent.



Note Cisco NAC Appliances assume the keyboard connected to be of US layout for both direct and IP-KVM connections. Use a US layout keyboard or ensure that you know the key mapping if you are connecting a keyboard of different layout.


Upgrading to Release 4.7(0)

This section provides instructions for how to upgrade your existing supported Cisco NAC Appliance platform to release 4.7(0). If you need to perform a new CD software installation, refer instead to New Installation of Release 4.7(0).

Refer to the following information prior to upgrade:

Changes for 4.7(0) Installation/Upgrade

General Preparation for Upgrade

Upgrade Instructions for Standalone Machines

Upgrade Instructions for HA Pairs


Caution During the upgrade process, new users will not be able to log in or authenticate with Cisco NAC Appliance until the Clean Access Server reestablishes connectivity with the Clean Access Manager.


Note Cisco NAC Appliance 4.7(0) release includes Cisco NAC Profiler Collector version 2.1.8-39 by default. When upgrading the CAS to a newer Cisco NAC Appliance release, the current version of the Collector is replaced with the default version of the Collector shipped with the Cisco NAC Appliance release. For example, if you are running Release 4.6(1) and Collector 3.1.0-24, and you upgrade to NAC 4.7(0), the Collector version will be downgraded to 2.1.8-39. Refer to the Release Notes for Cisco NAC Profiler for software compatibility matrixes and additional upgrade and product information.


Changes for 4.7(0) Installation/Upgrade

Cisco NAC Appliance Release 4.7(0) is an Early Deployment software 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(0), note the following:

Hardware Considerations

Features That May Change With Upgrade

Upgrade Changes

Password Changes

Hardware Considerations

You can install Cisco NAC Appliance Release 4.7(0) on the following Cisco NAC Appliance platforms:

NAC-3315, NAC-3355, and NAC-3395 (FIPS or non-FIPS mode)


Note Cisco NAC-3315, NAC-3355, NAC-3395 platforms (FIPS or non-FIPS) support installation/upgrade of Release 4.7(0) and later only.


CCA-3140, NAC-3310, NAC-3350, and NAC-3390 (non-FIPS mode only)

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.

Cisco NAC Appliance release 4.7(0) does not support the Cisco NAC Network Module (NME-NAC-K9). If you are currently using the Cisco NAC Network Module with a previous release of Cisco NAC Appliance in your network, do not upgrade to release 4.7(0).

With release 4.7(0), there is only one product installation CD (.ISO) for all appliance platforms. The installation package determines whether the Clean Access Server, Clean Access Manager, or Super Clean Access Manager was previously installed, as well as the previous software version.

To upgrade your CAM and CAS from 4.6(1), 4.5(x), or 4.1(3) and later releases, insert the same Cisco NAC Appliance Release 4.7(0) 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(0). For more information, see Known Issues with Web Upgrade in Release 4.1(3), 4.1(6), and 4.1(8).

If performing CD software installation on a NAC-3310 based appliance which is not reading the software on the CD ROM drive, refer to Known Issue with Cisco NAC Appliance CAM/CAS Boot Settings.

Features That May Change With Upgrade

If you employed any of the previous Windows registry settings to adjust Windows Clean Access Agent behavior on client machines, you must to specify the same settings in the XML Agent configuration file to preserve Agent behavior using the Cisco NAC Agent. For more information, see the "Cisco NAC Agent XML Configuration File Settings" section of the Cisco NAC Appliance - Clean Access Manger Configuration Guide, Release 4.7(2).

For new installations of Cisco NAC Appliance Release 4.5(1) and later, the CAS Fallback behavior enhancement introduces new default values for the Detect Interval and Detect Timeout settings (20 and 300 seconds, respectively) and requires that the Detect Timeout value be at least 15 times the specified Detect Interval. If you are upgrading to release 4.5(1) and later, however, your existing values for these settings are preserved and you must specify new values for these settings to take advantage of the enhanced CAS Fallback capabilities available in release 4.5(1).

When upgrading a VPN SSO Cisco NAC Appliance network to release 4.7(0), user login does not work properly when the user VPN is part of a managed subnet on the CAS. For more information, see Known Issue for VPN SSO Following Upgrade to Release 4.5 and Later.

Upgrade Changes


Warning If your previous deployment uses a chain of SSL certificates that is incomplete, incorrect, or out of order, CAM/CAS communication may fail after upgrade to release 4.5 and later. You must correct your certificate chain to successfully upgrade. For details on how to fix certificate errors on the CAM/CAS after upgrade to release 4.5 and later, refer to the How to Fix Certificate Errors on the CAM/CAS After Upgrade Troubleshooting Tech Note.

Note To upgrade your CAM and CAS from 4.6(1), 4.5(x), or 4.1(3) and later releases, insert the same Cisco NAC Appliance Release 4.7(0) 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(0). For more information, see Known Issues with Web Upgrade in Release 4.1(3), 4.1(6), and 4.1(8).


Cisco NAC Appliance Release 4.7(0) does not support the Cisco NAC Network Module (NME-NAC-K9). If you are currently using the Cisco NAC Network Module with a previous release of Cisco NAC Appliance in your network, do not upgrade to release 4.7(0).

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(0). You must manually re-import the Agent configuration XML file to maintain client machine login behavior.

The Cisco NAC Agent does not support Nessus-based network scanning. Nessus-based network scanning capabilities only apply to web login users and Clean Access Agent (Agent version 4.5.2.0 and earlier) users for whom a combination of client network scanning and Agent login functionality has been configured.

Starting from release 4.6(1), the CAM no longer manages Clean Access Agent Patch/Upgrade files (CCAAgentUpgrade-4.x.y.z.tar.gz). If you are downgrading or replacing the current version of the Agent on the CAM, be sure you only upload Clean Access Agent installation files (CCAAgentSetup-4.x.y.z.tar.gz or CCAAgentMacOSX-4.x.y.z-k9.tar.gz) from the Cisco Software Download site.

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 CAM/CAS network.

If you are upgrading from a release 4.5(1) or earlier CAM on which you are using non-English characters in Cisco NAC Appliance (for names or user roles or custom checks/requirements for example), the non-English data may not render properly after upgrade to release 4.7(0). To work around this issue, you can do one of three things:

Translate the non-English elements to English prior to upgrade

Remove the non-English items from the CAM prior to upgrade and replace them once upgrade is complete

Perform a fresh install of release 4.7(0) and re-create all of the non-English elements after installation


Note Including non-English data on the CAM/CAS in Cisco NAC Appliance releases prior to 4.6(1) is not officially supported, although certain implementations have been successful in lab environments.


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.

Macintosh client machines require the CAS to have a name-based SSL certificate in order to communicate with Cisco NAC Appliance. Note that if you generate or import a new name-based certificate, you must reboot the CAS using the service perfigo reboot or reboot command from the CAS CLI.

When you upgrade the CAM to release 4.7(0), the installation process automatically upgrades the Agent files to the latest Cisco NAC Agent version packaged with the CAM software image (e.g. Windows Cisco NAC Agent version 4.7.1.15, and Mac OS X Agent version 4.7.0.2).

Starting from 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.

Release 4.7(0) includes version 2.1.8-39 of the Cisco NAC Profiler Collector component that resides on the CAS installations. When upgrading CAS appliances (standalone or HA) to release 4.7(0), 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 If currently running a Cisco NAC Profiler Server version other than 2.1.8-39, you will need to sync the Collector component version running on the NAC Server to same version as the Profiler Server for compatibility.



Caution New users will not be able to log in or authenticate with Cisco NAC Appliance until the Clean Access Server reestablishes connectivity with the Clean Access Manager.


Note Cisco NAC Profiler and Cisco NAC Guest Server are not supported in FIPS-compliant deployments in Release 4.7(0).


Password Changes

To offer increased security against potential unauthorized access to Cisco NAC Appliance, the CAM and CAS root admin password you specify during initial system configuration (when performing fresh install or release 4.7(0) or reconfiguring the appliance via service perfigo config) must now meet strong password standards. However, any existing CAM/CAS root passwords are preserved during upgrade.

For new installations of Cisco NAC Appliance, there is no longer a default cisco123 CAM web console password. Administrators must specify a unique password for the CAM web console. However, any existing CAM web console passwords (including the old default cisco123) are preserved during upgrade.

For additional details, see also:

Hardware Support

Known Issues for Cisco NAC Appliance

General Preparation for Upgrade


Caution Please review this section carefully before commencing any Cisco NAC Appliance upgrade.

Homogenous Clean Access Server Software Support

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 software and some running 4.6(1) or 4.5(x) software).

Upgrade Downtime Window

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.

Upgrade Clean Access Servers Before Clean Access Manager

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 New users will not be able to log in or authenticate with Cisco NAC Appliance until the Clean Access Server reestablishes connectivity with the Clean Access Manager.

High Availability (Failover) Via Serial Cable Connection

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.

Save a Local Copy of the Cisco NAC Agent Configuration XML File

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(0). You must manually re-import the Agent configuration XML file to maintain client machine login behavior.


Note If you are upgrading from a Cisco NAC Appliance release older than release 4.6(1), this upgrade preparation step does not apply.


Database Backup (Before and After Upgrade)

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 You cannot restore a CAM database from a snapshot created using a different release. For example, you cannot restore a 4.5(x) or 4.6(1) database snapshot to a 4.7(0) CAM.

Software Downgrade

Once you have upgraded your software to release 4.7(0), 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(0). See Upgrade Instructions for Standalone Machines for additional details.

Passwords

For upgrade via console/SSH, you will need your CAM and CAS root user password.

Upgrading from Customer-Supplied Hardware to Cisco NAC Appliance Hardware Platforms

If you are running the Cisco NAC Appliance software (release 4.1(x) or earlier) on a non-Cisco NAC Appliance platform, you will need to purchase Cisco NAC Appliance hardware before you can upgrade your system to release 4.7(0). You may additionally need to obtain proper FlexLM product licenses. Once you obtain a Cisco NAC platform, Cisco recommends that you:


Step 1 Back up your current system and create a backup snapshot for the software version you are running (e.g. 4.1(x) or earlier).

Step 2 Download and install the same software version on your new Cisco NAC appliance platform (e.g. 4.1(x) or earlier).

Step 3 Restore the snapshot to your new Cisco NAC Appliance.

Step 4 If necessary, upgrade your appliance to 4.0(x) or 4.1(x). Then follow the appropriate upgrade procedure to upgrade your Cisco NAC Appliance to release 4.7(0).

Step 5 Create a backup snapshot of your upgraded system.



Note If you need to upgrade from a much older version of Cisco Clean Access, you may need to perform an interim upgrade to a version that is supported for upgrade to release 4.7(0). In this case, refer to the applicable Release Notes for upgrade instructions for the interim release. Cisco recommends to always test new releases on a different system before upgrading your production system.


Upgrade Instructions for Standalone Machines


Note To upgrade your CAM and CAS from 4.6(1), 4.5(x), or 4.1(3) and later releases, insert the same Cisco NAC Appliance Release 4.7(0) 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(0). For more information, see Upgrading to Release 4.7(0) and Known Issues with Web Upgrade in Release 4.1(3), 4.1(6), and 4.1(8).


This section describes how to upgrade standalone (i.e. non-HA) CAM/CAS machines from release 4.0(x)/4.1(x)/4.5(x)/4.6(1) to release 4.7(0).

Review Changes for 4.7(0) 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.0(x)/4.1(x)/4.5(x)/4.6(1) systems are as follows:

1. Create CAM DB Backup Snapshot

2. Download the Install/Upgrade File

3. Upgrade Your CAM

4. Upgrade Your CAS

Create CAM DB Backup Snapshot

This section describes how to back up your current system.


Step 1 From the CAM web console, go to the Administration > Backup page.

Step 2 The Snapshot Tag Name field automatically populates with a name incorporating the current time and date (e.g. 07_01_09-15-47_snapshot). You can also either accept the default name or type another.

Step 3 Click Create Snapshot. The CAM generates a snapshot file and adds it to the snapshot list at the bottom of the page. The file physically resides on the CAM machine for archiving purposes. The Version field and the filename display the software version of the snapshot for convenience (e.g. 09_06_09-15-47_snapshot_VER_4_7_0.gz).

Step 4 For backup, download the snapshot to another computer by clicking the Tag Name or the Download button for the snapshot to be downloaded.

Step 5 In the file download dialog, select the Save File to Disk option to save the file to your local computer.

Step 6 After upgrade, delete all earlier snapshots from the CAM web console as they will no longer be compatible.



Note Cisco NAC Appliance creates automatic snapshots before and after software upgrades and failover events, and preserves the last 5. For further details, see "Database Recovery Tool" in the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.7(2).


Download the Install/Upgrade File

To upgrade your CAM and CAS from 4.6(1), 4.5(x), or 4.1(3) and later releases, insert the same Cisco NAC Appliance Release 4.7(0) 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(0). For more information, see Known Issues with Web Upgrade in Release 4.1(3), 4.1(6), and 4.1(8).


Step 1 Log in to the Cisco Software Download Site at http://www.cisco.com/public/sw-center/index.shtml. You will likely be required to provide your CCO credentials.

Step 2 Navigate to Security > Endpoint Security > Cisco Network Access Control > Cisco NAC Appliance > Cisco NAC Appliance 4.7.

Step 3 Download the latest 4.7 .ISO image, (e.g. nac-4.7_0-K9.iso) and burn the image as a bootable disk to a CD-R.


Note Cisco recommends burning the .ISO image to a CD-R using speeds 10x or lower. Higher speeds can result in corrupted/unbootable installation CDs.



Upgrade Your CAM

Before upgrading your CAM be sure you obtain the Cisco NAC Appliance Release 4.7(0) install/upgrade image and burn it to a CD-ROM according to the instructions in Download the Install/Upgrade File.


Step 1 Insert the CD into the CD-ROM drive of each CAM you want to upgrade.

Step 2 Perform a "clean" or "graceful" shutdown on the CAM by logging into the CAM console CLI as "root" and entering reboot.


Warning You must enter the "reboot" command in the CAM CLI to perform this upgrade. Simply power cycling the appliance does not bring up the upgrade option.

Step 3 Choose option 2 at the following prompt:

Checking for existing installations.
Clean Access Server 4.6.1 installation detected.
Please choose one of the following actions:
1) Install.
2) Upgrade.
3) Exit.
 
   
2
 
   

Step 4 Wait for the upgrade to complete. This will take several minutes

...stopping CCA Manager...
 
   
Welcome to the CCA Manager migration utility.
 
   
...Upgrading to newer rpms of 4.7.0...done.
...Upgrading CCA files...done
Windows Agent version upgraded to 4.7.1.15.
Mac Agent was upgraded to version 4.7.0.2.
Clearing Tomcat cache...checking ssl configuration...done.
[root@cam1]# 
 
   

Step 5 When upgrade is done, reboot the CAM at the prompt:

reboot

Note 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(0). You must manually re-import the Agent configuration XML file to maintain client machine login behavior.




Tip You can run cat /perfigo/build to verify the software version before and after upgrade.


Upgrade Your CAS

Before upgrading your CAS be sure you obtain the Cisco NAC Appliance Release 4.7(0) install/upgrade image and burn it to a CD-ROM according to the instructions in Download the Install/Upgrade File.


Step 1 Insert the CD into the CD-ROM drive of each CAS you want to upgrade.

Step 2 Perform a "clean" or "graceful" shutdown on the CAS by logging into the CAS console CLI as "root" and entering reboot.


Warning You must enter the "reboot" command in the CAS CLI to perform this upgrade. Simply power cycling the appliance does not bring up the upgrade option.

Step 3 Choose option 2 at the following prompt:

Checking for existing installations.
Clean Access Server 4.6.1 installation detected.
Please choose one of the following actions:
1) Install.
2) Upgrade.
3) Exit.
 
   
2
 
   

Step 4 When upgrade is done, reboot the CAS at the prompt:

reboot
 
   


Tip You can run cat /perfigo/build to verify the software version before and after upgrade.


Upgrade Instructions for HA Pairs


Note 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.


This section describes how to upgrade high-availability (HA) pairs of CAM or CAS servers from release 4.0(x)/4.1(x)/4.5(x)/4.6(1) to release 4.7(0).

If you have standalone CAM/CAS servers, refer instead to Upgrade Instructions for Standalone Machines.

Review Changes for 4.7(0) Installation/Upgrade and General Preparation for Upgrade before proceeding with these upgrade instructions.


Note To upgrade your CAM and CAS from 4.6(1), 4.5(x), or 4.1(3) and later releases, insert the same Cisco NAC Appliance Release 4.7(0) 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(0). For more information, see Known Issues with Web Upgrade in Release 4.1(3), 4.1(6), and 4.1(8).



Warning If you are using serial connection for HA, do not attempt to connect serially to the CAS during the upgrade procedure. When serial connection is used for HA, serial console/login will be disabled and serial connection cannot be used for installation/upgrade.

If you are using serial connection for HA, 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.

Note For additional details on CAS HA requirements, see also Supported Hardware and System Requirements for Cisco NAC Appliance (Cisco Clean Access).


Upgrading HA-CAM and HA-CAS Pairs

The following steps show the recommended way to upgrade an existing high-availability (failover) pair of Clean Access Managers or Clean Access Servers.


Warning Make sure to carefully execute the following procedure to prevent the CAM database from getting out of sync.

Step 1 Before upgrading your CAM/CAS HA pair, be sure you obtain the Cisco NAC Appliance Release 4.7(0) install/upgrade image and burn it to a CD-ROM according to the instructions in Download the Install/Upgrade File.

Step 2 Determine the failover state on each machine by running the fostate.sh command on each CAM/CAS in the HA pair:

/perfigo/common/bin/
./fostate.sh 
 
   

The 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 The fostate.sh command is part of the upgrade script (starting from 3.5(3)+). You can also determine which appliance is active or standby as follows:

Access the web console as described in "Accessing Web Consoles in High Availability Pairs" sections of the "Configuring High Availability" chapters in both 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).

SSH to the Service IP of the CAM/CAS pair, and type ifconfig eth0. The Service IP will always access the active CAM or CAS, with the other pair member acting as standby.


Step 3 Shut down the standby CAM/CAS.

Step 4 Insert the install/upgrade CD into the active CAM/CAS you want to upgrade.

Step 5 Perform a "clean" or "graceful" shutdown on the active CAM/CAS by entering shutdown -r now.


Warning You must enter the "shutdown -r now" command in the CAM/CAS CLI to perform this upgrade. Simply power cycling the appliance does not bring up the upgrade option.

Step 6 Choose option 2 at the following prompt:

Checking for existing installations.
Clean Access Server 4.6.1 installation detected.
Please choose one of the following actions:
1) Install.
2) Upgrade.
3) Exit.
 
   
2
 
   

Step 7 Wait for the upgrade to complete. This will take several minutes

...stopping CCA Manager...
 
   
Welcome to the CCA Manager migration utility.
 
   
...Upgrading to newer rpms of 4.7.0...done.
...Upgrading CCA files...done
Windows Agent version upgraded to 4.7.1.15.
Mac Agent was upgraded to version 4.7.0.2.
Clearing Tomcat cache...checking ssl configuration...done.
[root@cam1]# 
 
   

Step 8 After the upgrade process completes, verify the database re-population results by entering the following command:

/perfigo/common/bin/showstate.sh | grep INCORRECT
 
   

If any entries from the database population process contain "INCORRECT," you will need to manually restore database before rebooting the system.

Step 9 After the upgrade is complete, shut down the active CAM/CAS.

Step 10 Insert the install/upgrade CD into the standby CAM/CAS you want to upgrade.

Step 11 Perform a "clean" or "graceful" shutdown on the standby CAM/CAS by entering shutdown -r now.


Warning You must enter the "shutdown -r now" command in the CAM/CAS CLI to perform this upgrade. Simply power cycling the appliance does not bring up the upgrade option.

Step 12 Choose option 2 at the following prompt:

Checking for existing installations.
Clean Access Server 4.6.1 installation detected.
Please choose one of the following actions:
1) Install.
2) Upgrade.
3) Exit.
 
   
2
 
   

Step 13 Wait for the upgrade to complete. This will take several minutes

...stopping CCA Manager...
 
   
Welcome to the CCA Manager migration utility.
 
   
...Upgrading to newer rpms of 4.7.0...done.
...Upgrading CCA files...done
Windows Agent version upgraded to 4.7.1.15.
Mac Agent was upgraded to version 4.7.0.2.
Clearing Tomcat cache...checking ssl configuration...done.
[root@cam1]# 
 
   

Step 14 Verify the upgrade results by entering the following command:

/perfigo/common/bin/showstate.sh | grep INCORRECT
 
   

If any entries from the database population process contain "INCORRECT," you will need to manually restore database before rebooting the system.

Step 15 After the upgrade is complete, shut down the standby appliance.

Step 16 Reboot the active appliance and wait until it is running normally and you are able to connect to the web console.

Step 17 Reboot the standby appliance and when it is up and running normally, verify connectivity between the CAMs/CASs.


Note 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(0). You must manually re-import the Agent configuration XML file to maintain client machine login behavior.


Step 18 Verify the failover state on each machine again with the fostate.sh command on each machine:

/perfigo/common/bin/ 
./fostate.sh 

Note There will be approximately 2-5 minutes of downtime while the appliances reboot.



Known Issues for Cisco NAC Appliance

This section describes known issues when integrating Cisco NAC Appliance:

Known Issue with Mass DHCP Address Deletion

Known Issue for VPN SSO Following Upgrade to Release 4.5 and Later

Known Issues with Web Upgrade in Release 4.1(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 Switches

Known Issues with Cisco 2200/4400 Wireless LAN Controllers (Airespace WLCs)

Known Issue for Windows Vista and IP Refresh/Renew

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 stop
rm -f /var/state/dhcp/dhcpd.leases
touch /var/state/dhcp/dhcpd.leases
service perfigo start
 
   

If 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 In release 4.6(1) and later, the CAM only allows 60 seconds for a response on remote calls to the CAS. This impacts deleting hundreds of DHCP IPs at once, particularly on slower CAS hardware platforms. Cisco recommends that you do not delete any more than 3 class C address segments at once.


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, 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(0).

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. Configure the HA-CAM failover pair.

2. Issue the service perfigo stop CLI command on both HA-CAMs to stop services.

3. Issue the service perfigo start CLI command on the HA-Standby CAM to restart services.

4. As soon as the service perfigo start command finishes, access the HA-Service IP address in a browser for the administrator web console, enter authentication credentials, and click Login.

5. The CAM HA-Service IP administrator web console displays the limited menu/submenu options previously available while the machine was still the "standby" CAM.

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 For further details on configuring DHCP options, refer to the applicable version of the Cisco NAC Appliance - Clean Access Server Configuration Guide, Release 4.7(2).



Note This known issue does not affect Wireless Out-of-Band deployments because CASs are only deployed in Virtual Gateway mode, thus the CAS is not configured to perform any DHCP functions.


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. Log into the Windows Vista client as an administrator.

2. Create a shortcut for IE on your desktop.

3. Launch it by right-clicking the shortcut and running it as administrator. This will allow the application to complete the IP Refresh/Renew. Otherwise, the user will need to do it manually via Command Prompt running as administrator. This is a limitation of the Windows Vista OS.

See also CSCsm61077.

Troubleshooting

This section provides troubleshooting information for the following topics:

Enabling TLSv1 on Internet Explorer Version 6

Vista/IE 7 Certificate Revocation List

HA Active-Active Situation Due to Expired SSL Certificates

Agent AV/AS Rule Troubleshooting

Debug Logging for Cisco NAC Appliance Agents

Creating CAM/CAS Support Logs

Recovering Root Password for CAM/CAS

Troubleshooting CAM/CAS Certificate Issues

Troubleshooting Switch Support Issues

Other Troubleshooting Information


Note For additional troubleshooting information, see also New Installation of Release 4.7(0).


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 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 Got to Tools > Internet Options.

Step 2 Select the Advanced tab.

Step 3 Scroll down to locate the Use TLS 1.0 option under Security.

Step 4 Click on the checkbox to enable the Use TLS 1.0. option and click Apply.

Step 5 If necessary, close the browser and open a new one where the TLS 1.0 option should now be automatically enabled.



Note Mozilla Firefox has not shown this limitation.


Vista/IE 7 Certificate Revocation List


Note In IE 7, the "Check for server certificate revocation (requires restart)" checkbox is enabled by default under IE's Tools > Internet Options > Advanced | Security settings.

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 Manger 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. The client system is using Microsoft Internet Explorer 7 and/or Windows Vista operating system, and the certificate issued for the CAS is not properly configured with a CRL (Certificate Revocation List).

2. A temporary SSL certificate is being used for the CAS and:

The user has not imported this certificate to the trusted root store.

The user has not disabled the "Check for server certificate revocation (requires restart)" checkbox in IE.

To resolve this issue, perform the following actions:


Step 1 (Preferred) When using a CA-signed CAS SSL certificate, check the "CRL Distribution Points" field of the certificate (including intermediate or root CA), and add the URL hosts to the allowed Host Policy of the Unauthenticated/Temporary/Quarantine Roles. This will allow the Agent to fetch the CRLs when logging in.

Step 2 Or, if continuing to use temporary certificates for the CAS, the user will need to perform ONE of the following actions:

a. Import the certificate to the client system's trusted root store.

b. Disable the "Check for server certificate revocation (requires restart)" checkbox under IE's Tools > Internet Options > Advanced | Security settings.


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 Starting with Cisco NAC Appliance Release 4.7(0), the CAM or CAS generates event log messages to indicate the certificate expiry in addition to the message displayed in the CAM/CAS web console.



Note The self-signed SSL certificate expires after 90 days from the date of generation.


Agent AV/AS Rule Troubleshooting

When troubleshooting AV/AS Rules:

View administrator reports for the Agent from Device Management > Clean Access > Clean Access Agent > Reports

Or, to view information from the client, right-click the Agent taskbar icon and select Properties.

When troubleshooting AV/AS Rules, please provide the following information:

1. Version of CAS, CAM, and Agent (see Determining the Software Version).

2. Version of client OS (e.g. Windows XP SP2).

3. Version of Cisco Updates ruleset

4. Product name and version of AV/AS software from the Add/Remove Program dialog box.

5. What is failing—AV/AS installation check or AV/AS update checks? What is the error message?

6. What is the current value of the AV/AS def date/version on the failing client machine?

7. What is the corresponding value of the AV/AS def date/version being checked for on the CAM? (See Device Management > Clean Access > Clean Access Agent > Rules > AV/AS Support Info.)

8. If necessary, provide Agent debug logs as described in Debug Logging for Cisco NAC Appliance Agents.

9. If necessary, provide CAM support logs as described in Creating CAM/CAS Support Logs.

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:

Generate Cisco NAC Agent Debug Logs

Cisco NAC Web Agent Logs

Generate Mac OS X Agent Debug Log

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 Manger 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 For versions prior to 4.1.3.0, debug logging for the Mac OS X Agent is enabled under <local drive ID> > Library > Application Support > Cisco Systems | CCAAgent.app > Show Package Contents > setting.plist.


To view and/or change the Agent LogLevel:


Step 1 Open the navigator pane and navigate to <local drive ID> > Applications.

Step 2 Highlight and right-click the CCAAgent.app icon to bring up the selection menu.

Step 3 Choose Show Package Contents > Resources.

Step 4 Choose setting.plist.

Step 5 If you want to change the current LogLevel setting using Mac Property Editor (for Mac OS 10.4 and later) or any standard text editor (for Mac OS X releases earlier than 10.4), find the current LogLevel Key and replace the exiting value with one of the following:

Info—Include only informational messages in the event log

Warn—Include informational and warning messages in the event log

Error—Include informational, warning, and error messages in the event log

Debug—Include all Agent messages (including informational, warning, and error) in the event log


Note The Info and Warn entry types only feature a few messages pertaining to very specific Agent events. Therefore, you will probably only need either the Error or Debug Agent event log level when troubleshooting Agent connection issues.



Note Because Apple, Inc. introduced a binary-format .plist implementation in Mac OS 10.4, the .plist file may not be editable by using a common text editor such as vi. If the .plist file is not editable (displayed as binary characters), you either need to use the Mac Property List Editor utility from the Mac OS X CD-ROM or acquire another similar tool to edit the setting.plist file.

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

Table 13 Updates to Release Notes for Cisco NAC Appliance, Release 4.7(0)

Date
Description

9/28/11

Added HA Active-Active Situation Due to Expired SSL Certificates

6/2/11

Added CSCtj81255 to Open Caveats - Release 4.7(0)

6/17/10

Added Caveat CSCsx52263 to Open Caveats - Release 4.7(0).

5/17/10

Restricted information to Release 4.7(0) content only. Refer to http://www.cisco.com/en/US/products/ps6128/prod_release_notes_list.html for all Release 4.7(x) release notes.

9/30/09

Added note to Release 4.7 and Cisco NAC Profiler and Upgrade Changes.

9/29/09

Release 4.7(0)


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.

Cisco NAC Appliance Hardware Installation Guide, Release 4.7

Cisco NAC Appliance - Clean Access Manger Configuration Guide, Release 4.7(2)

Cisco NAC Appliance - Clean Access Server Configuration Guide, Release 4.7(2)

Support Information for Cisco NAC Appliance Agents, Release 4.5 and Later

Switch Support for Cisco NAC Appliance

Cisco NAC Appliance Service Contract / Licensing Support

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.