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

Failover Events, New Server, etc/ha.d/linkdetect.conf

Get Cisco NAC3350-PROF-K9 - NAC Profiler Server PDF manuals and user guides View all Cisco NAC3350-PROF-K9 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 141 highlights

Chapter 4 Configuring High Availability (HA) Figure 4-10 Active CAS in an HA-Pair Installing a Clean Access Server High Availability Pair Note If a CAS was previously configured and added to the CAM as a standalone CAS, it must be deleted prior to configuring it for HA. After HA configuration is complete on both CASs, the Service IP is then entered in the New Server form to add the HA-CAS pair to the CAM. Note To ensure heartbeat redundancy, Cisco recommends configuring optional Heartbeat UDP Interface 2 or 3 between the HA CASs in your deployment. Failover Events • If multiple heartbeat UDP interfaces are configured, then they must all fail for the standby system to take over. See Physical Connection, page 4-22 for additional details. • If the CAS is unable to communicate with the CAM: - Users that are already connected will not be affected. - New users will not be able to log in. • You can configure link-based failover. Two IP addresses that are external to the CAS are configured for Link-detect: one on the trusted network, the other on the untrusted network. - The active and standby CAS will send ICMP ping packets via eth0 to the IP address on the trusted network. - The active and standby CAS will send ICMP ping packets via eth1 to the IP address on the untrusted network. Note If your network topology restricts Link-detect functionality between your CAS HA pair appliances, you can also use the /etc/ha.d/linkdetect.conf file to enforce Link-detect behavior on your eth0 and/or eth1 interfaces. See Link-Detect Interfaces, page 4-45 for more details. The status of these ping packets is communicated between the CASs via the heartbeat signal: - If the active and standby CAS can ping both external IPs, no failover occurs - If the active and standby CAS cannot ping either of the external IPs, no failover occurs - If the active CAS cannot ping either of the external IPs, but the standby CAS can ping them, failover occurs • 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. OL-20326-01 Cisco NAC Appliance Hardware Installation Guide 4-21

  • 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-21
Cisco NAC Appliance Hardware Installation Guide
OL-20326-01
Chapter 4
Configuring High Availability (HA)
Installing a Clean Access Server High Availability Pair
Figure 4-10
Active CAS in an HA-Pair
Note
If a CAS was previously configured and added to the CAM as a standalone CAS, it must be deleted prior
to configuring it for HA. After HA configuration is complete on both CASs, the Service IP is then
entered in the
New Server
form to add the HA-CAS pair to the CAM.
Note
To ensure heartbeat redundancy, Cisco recommends configuring optional Heartbeat UDP Interface 2 or
3 between the HA CASs in your deployment.
Failover Events
•
If multiple heartbeat UDP interfaces are configured, then they must all fail for the standby system
to take over. See
Physical Connection, page 4-22
for additional details.
•
If the CAS is unable to communicate with the CAM:
–
Users that are already connected will not be affected.
–
New users will not be able to log in.
•
You can configure link-based failover. Two IP addresses that are external to the CAS are configured
for Link-detect: one on the trusted network, the other on the untrusted network.
–
The active and standby CAS will send ICMP ping packets via eth0 to the IP address on the
trusted network.
–
The active and standby CAS will send ICMP ping packets via eth1 to the IP address on the
untrusted network.
Note
If your network topology restricts Link-detect functionality between your CAS HA pair
appliances, you can also use the
/etc/ha.d/linkdetect.conf
file to enforce Link-detect behavior
on your eth0 and/or eth1 interfaces. See
Link-Detect Interfaces, page 4-45
for more details.
The status of these ping packets is communicated between the CASs via the heartbeat signal:
–
If the active and standby CAS can ping both external IPs, no failover occurs
–
If the active and standby CAS cannot ping either of the external IPs, no failover occurs
–
If the active CAS cannot ping either of the external IPs, but the standby CAS can ping them,
failover occurs
•
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.