Cisco Cisco Clean Access 3.5

Before starting, make sure that both Clean Access Servers are installed and accessible over the 
network. See 

. 

If the Clean Access Servers have already been added to the management domain of a CAM, they 
should be removed. Use the Delete button in the List of Servers tab to remove the CASes. 

Clean Access web consoles support the Internet Explorer 6.0 or above browser only. 

The Heartbeat UDP interface, if specified, is used to send UDP heartbeat traffic related to high 
availability. The interface used depends on the interfaces available on the server machine and the load 
level expected. This interface can use either the trusted interface eth0 or a dedicated interface such as 
eth2. If a dedicated interface is used, then the dedicated interfaces on both machines should be connected 
using a crossover cable. 

Servers running a CAS typically use both available interfaces (eth0 and eth1), with eth0 configured as 
the trusted network interface. The trusted network interface can be shared in most deployments. In some 
cases, an additional network interface card (NIC) can be installed to provide an additional interface (e.g. 
eth2) dedicated to UDP heartbeat. In this case, configure the IP address for the new interface.

If each machine running the CAS software has two serial ports, use one of the ports for the serial cable 
connection. By default, the first serial connector detected on the server is configured for console 
input/output (to facilitate installation and other types of administrative access). 

When high-availability mode is selected, the serial console login (ttyS0) is automatically disabled to free 
the serial port for HA mode. To re-enable ttyS0 as the console login, click the Enable button on the 
Failover tab after clicking Update and before clicking Reboot. For details, see steps 

 and 

The serial console login and HA cannot be located on the same serial port. 

Delete