Cisco Cisco NAC Appliance 4.5 Release Notes

The following steps summarize how to perform new CD software installation of release 4.5 on supported 
Cisco NAC Appliance hardware platforms (see 

 for 

additional support details).

To upgrade or re-image a Cisco NAC Network Module, refer to the instructions in 

. 

To upgrade on an existing NAC Appliance, refer to the instructions in 

With release 4.5, installation occurs in two phases: 

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

The admin logs in and performs the initial configuration. 

If you are going to perform a new installation but are running a previous version of Cisco Clean Access, 
Cisco recommends backing up your current Clean Access Manager installation and saving the snapshot 
on your local computer, as described in 

.

Follow the instructions on your welcome letter to obtain product license files for your installation. See 

 for details. (If you are evaluating Cisco Clean Access, visit 

 to obtain an evaluation license.) 

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

Log in to the 

. You will likely be required to provide 

your CCO credentials.

Navigate to the Cisco NAC Appliance 4.5.1 subdirectory, download the latest 4.5(1) .ISO image, 
(e.g. nac-4.5_1-K9.iso) and burn the image as a bootable disk to a CD-R.

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

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

CSCso91745

Yes

Mac OS X Agent may not pop-up or login may fail on networks with 
high latency

Round-trip network latency between client machine and the CAS should 
be 1000 ms or higher. As SWISS response timeout is 1 second, the 
Mac OS X Agent does not appear to users where the round-trip latency 
between the client machine and the CAS is 1000 ms or more.

There is no known workaround for this issue.