Cisco NAC3350-PROF-K9 Hardware Installation Guide - Page 124

CAM High Availability Overview, For more information - web protection

Page 124 highlights

Installing a Clean Access Manager High Availability Pair Chapter 4 Configuring High Availability (HA) CAM High Availability Overview Caution CAM-CAS communication and HA-CAM and/or HA-CAS peer communication can break down and adversely affect network functionality when SSL certificates expire. Refer to the caveat CSCtb43264 in Release Notes for Cisco NAC Appliance, Version 4.8. For more information, see the "HA Active-Active Situation Due to Expired SSL Certificates" section of the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.8(3). The following key points provide a high-level summary of HA-CAM operation: • The Clean Access Manager high-availability mode is an Active/Passive two-server configuration in which a standby CAM machine acts as a backup to an active CAM machine. • The active Clean Access Manager performs all tasks for the system. The standby CAM monitors the active CAM and keeps its database synchronized with the active CAM's database. Note CAM Authorization settings are not automatically passed from one CAM to the other in an HA-pair. If you use the Authorization feature in a CAM HA-pair, follow the guidelines in the "Backing Up and Restoring CAM/CAS Authorization Settings" section of the Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.8(3) to ensure you are able to exactly duplicate your Authorization settings from one CAM to its high availability counterpart. • Clean Access Managers and Clean Access Servers use a local master secret password to encrypt and protect important data, like other system passwords. The master secret password needs to be the same for a CAM-HA pair. Similarly, the CAS-HA pair should maintain the same master secret password. Cisco recommends keeping very accurate records of assigned master secret passwords to ensure that you are able to fail over to the HA peer CAM/CAS in HA deployments. (HA-Secondary CAMs/CASs are not able to assume the "active" role following a failover event when the master secret passwords are different.) • Both CAMs share a virtual Service IP for the eth0 trusted interface. The Service IP must be used for the SSL certificate. • The Service IP address is used for all messages and requests sent to the CAM, including communication from the CAS and the administration web console. • The CAM uses its individual (eth0) IP address for all communications sent to the CAS and proxy authentication messages. • The primary and secondary CAM machines exchange UDP heartbeat packets every 2 seconds. If the heartbeat timer expires, stateful failover occurs. • HA CAMs/CASs automatically establish an IPSec tunnel to ensure all communications between the HA Pair appliances remains secure across the network. • In order to ensure an active CAM is always available, its interface (eth0) must be up. To avoid a situation where a CAM is active but is not accessible via its interface (that is, the standby CAM receives heartbeat packets from the active CAM, but the active CAM's eth0 interface fails), the link-detect mechanism allows the standby CAM to be aware of when the active CAM's eth0 interface becomes unavailable. • Both the Clean Access Manager and Clean Access Server are designed to automatically reboot in the event of a hard-drive failure, thus automatically initiating failover to the standby CAM/CAS. Cisco NAC Appliance Hardware Installation Guide 4-4 OL-20326-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176

4-4
Cisco NAC Appliance Hardware Installation Guide
OL-20326-01
Chapter 4
Configuring High Availability (HA)
Installing a Clean Access Manager High Availability Pair
CAM High Availability Overview
Caution
CAM-CAS communication and HA-CAM and/or HA-CAS peer communication can break down and
adversely affect network functionality when SSL certificates expire. Refer to the caveat CSCtb43264 in
Release Notes for Cisco NAC Appliance, Version 4.8
.
For more information, see the “HA Active-Active Situation Due to Expired SSL Certificates” section of
the
Cisco NAC Appliance - Clean Access Manager Configuration Guide, Release 4.8(3)
.
The following key points provide a high-level summary of HA-CAM operation:
The Clean Access Manager high-availability mode is an Active/Passive two-server configuration in
which a standby CAM machine acts as a backup to an active CAM machine.
The active Clean Access Manager performs all tasks for the system. The standby CAM monitors the
active CAM and keeps its database synchronized with the active CAM’s database.
Note
CAM Authorization settings are not automatically passed from one CAM to the other in an
HA-pair. If you use the Authorization feature in a CAM HA-pair, follow the guidelines in
the “Backing Up and Restoring CAM/CAS Authorization Settings” section of the
Cisco
NAC Appliance - Clean Access Manager Configuration Guide, Release 4.8(3)
to ensure you
are able to
exactly
duplicate your Authorization settings from one CAM to its high
availability counterpart.
Clean Access Managers and Clean Access Servers use a local master secret password to encrypt and
protect important data, like other system passwords. The master secret password needs to be the
same for a CAM-HA pair. Similarly, the CAS-HA pair should maintain the same master secret
password. Cisco recommends keeping very accurate records of assigned master secret passwords to
ensure that you are able to fail over to the HA peer CAM/CAS in HA deployments. (HA-Secondary
CAMs/CASs are not able to assume the “active” role following a failover event when the master
secret passwords are different.)
Both CAMs share a virtual Service IP for the eth0 trusted interface. The Service IP must be used for
the SSL certificate.
The Service IP address is used for all messages and requests sent to the CAM, including
communication from the CAS and the administration web console.
The CAM uses its individual (eth0) IP address for all communications sent to the CAS and proxy
authentication messages.
The primary and secondary CAM machines exchange UDP heartbeat packets every 2 seconds. If the
heartbeat timer expires, stateful failover occurs.
HA CAMs/CASs automatically establish an IPSec tunnel to ensure all communications between the
HA Pair appliances remains secure across the network.
In order to ensure an active CAM is always available, its interface (eth0) must be up. To avoid a
situation where a CAM is active but is not accessible via its interface (that is, the standby CAM
receives heartbeat packets from the active CAM, but the active CAM's eth0 interface fails), the
link-detect mechanism allows the standby CAM to be aware of when the active CAM's eth0 interface
becomes unavailable.
Both the Clean Access Manager and Clean Access Server are designed to automatically reboot in
the event of a hard-drive failure, thus automatically initiating failover to the standby CAM/CAS.