Table of Contents
Advertisement
Chapter 4
Configuring High Availability (HA)
[Primary] Local MAC Address (untrusted-side interface): Filled in by default; the MAC address
•
of the eth1 interface for the HA-Primary CAS.
You may want to copy and paste the [Primary] Local Host Name, [Primary] Local Serial No, and
Note
•
[Primary] Local MAC Address (trusted/untrusted) values into a text file. These values are
necessary later when configuring the HA-Secondary CAS.
•
To enter the HA-Secondary CAS information into the form for the HA-Primary CAS, copy and paste
the corresponding fields from the HA-Secondary CAS web console.
[Secondary] Peer Host Name: Type the host name for the HA-Secondary CAS peer ("rjcas_2" in
•
this example). The Secondary Peer Host Name is case-sensitive and must exactly match the Host
Name specified in the peer machine DNS tab (under Administration > Network Settings > DNS |
Host Name).
•
[Secondary] Peer MAC Address (trusted-side interface): This is the peer MAC address from the
trusted (eth0) side of the HA-Secondary CAS.
•
[Secondary] Peer MAC Address (untrusted-side interface): This is the peer MAC address from
the untrusted (eth1) side of the HA-Secondary CAS.
Heartbeat UDP Interface 1: This setting specifies eth0 as a failover IP interface on the CAS. If a
•
dedicated Ethernet connection is not available,
[Secondary] Heartbeat IP Address on eth0: The IP address of the trusted interface (eth0) of the
•
HA-Secondary CAS.
Heartbeat UDP Interface 2: This setting specifies eth1 as a failover IP interface on the CAS. If you
•
configure your CAS HA system to use eth0 as the primary failover heartbeat connection, you can
also use the eth1 interface as a redundant heartbeat monitor.
[Secondary] Heartbeat IP Address on eth1: The IP address of the untrusted interface (eth1) of the
•
HA-Secondary CAS.
•
Heartbeat UDP Interface 3: Options are N/A, eth2, or eth3. If a dedicated Ethernet connection is
not available, Cisco recommends using eth0 or another Ethernet interface for the Heartbeat UDP
interface when configuring a Clean Access Server in HA mode.
Note
[Secondary] Heartbeat IP Address on Interface 3: The IP address of the tertiary failover heartbeat
•
link configured on the HA-Secondary CAS.
Note
OL-20326-01
Before you can specify either the eth2 or eth3 interfaces to be Heartbeat UDP Interface 3, you
must manually configure the interface using the CAS CLI. There are no eth2 or eth3
configuration settings (IP address, netmask, etc.) available via the CAS web console. For
instructions, see
Configuring Additional NIC Cards, page
You must configure at least one of the additional Ethernet interfaces on the HA-Primary CAS to
connect to a peer interface on the Secondary CAS in order to support HA behavior. In an HA
scenario, The Ethernet interface you configure serves as the medium for data sync between the
Primary and Secondary CAS.
Installing a Clean Access Server High Availability Pair
3-37.
Cisco NAC Appliance Hardware Installation Guide
4-31
Hide quick links:
Advertisement
Table of Contents
