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

Administration, Manager > Failover

Page 125 highlights

Chapter 4 Configuring High Availability (HA) Installing a Clean Access Manager High Availability Pair • Cisco NAC-3310 CAMs/CASs feature a 160GB hard drive or 80GB hard drive. Both of these hard drive sizes support High Availability (HA) deployments, and you can safely deploy a 160GB model in an HA pair with an 80GB model. • You can choose to "automatically configure" the eth1 interface in the Administration > CCA Manager > Failover page, but you must manually configure other (eth2 or eth3) HA interfaces with an IP address, netmask, etc. prior to configuring HA on the CAM. Refer to Configure the HA-Primary CAM, page 4-9 for details on configuring the interfaces. • The eth1 interface can be used for heartbeat packets and database synchronization. The eth0, eth1, and eth2/eth3 interfaces can be used for heartbeat packets. In addition, any available serial (COM) interface can also be used for heartbeat packets. If using more than one of these interfaces, then all the heartbeat interfaces need to fail for failover to occur. Note If you are configuring your CAM for HA, you must use eth1 for heartbeat and database synchronization. All other Ethernet interfaces (eth0 and eth2/eth3) can be used only for heartbeat packets. Note In CAM HA, when heartbeat is configured on multiple interfaces and eth1 is down, the standby CAM fails to do the database synchronization. The perfigo service is stopped on the standby CAM as the database synchronization happens only on eth1, which is down. Cisco recommends using only eth1 as heartbeat interface for CAM HA instead of using multiple HA interfaces. Note When deploying the CAM/CAS across a WAN, you must prioritize all CAM/CAS traffic and SNMP traffic, and include the eth0/eth1 IP addresses of the CAM and CAS in addition to the Service IP address for HA pairs. The prioritization can have a 256 kpbs bandwidth with roudtrip delayof 400ms. Caution The connection between HA pairs must be extremely reliable, with communication between HA pairs unimpeded. The best practice is to use a dedicated Ethernet cable. Breaking communication between HA pairs will result in two active nodes, which can have serious negative operational consequences. A key aspect of the link between HA pairs is the ability to restore that link should it go down; restoration may be fundamental to network stability, depending on your design. OL-20326-01 Cisco NAC Appliance Hardware Installation Guide 4-5

  • 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-5
Cisco NAC Appliance Hardware Installation Guide
OL-20326-01
Chapter 4
Configuring High Availability (HA)
Installing a Clean Access Manager High Availability Pair
Cisco NAC-3310 CAMs/CASs feature a 160GB hard drive or 80GB hard drive. Both of these hard
drive sizes support High Availability (HA) deployments, and you can safely deploy a 160GB model
in an HA pair with an 80GB model.
You can choose to “automatically configure” the eth1 interface in the
Administration
>
CCA
Manager > Failover
page, but you must manually configure other (eth2 or eth3) HA interfaces with
an IP address, netmask, etc. prior to configuring HA on the CAM. Refer to
Configure the
HA-Primary CAM, page 4-9
for details on configuring the interfaces.
The eth1 interface can be used for heartbeat packets and database synchronization. The eth0, eth1,
and eth2/eth3 interfaces can be used for heartbeat packets. In addition, any available serial (COM)
interface can also be used for heartbeat packets. If using more than one of these interfaces, then all
the heartbeat interfaces need to fail for failover to occur.
Note
If you are configuring your CAM for HA, you must use eth1 for heartbeat and database synchronization.
All other Ethernet interfaces (eth0 and eth2/eth3) can be used only for heartbeat packets.
Note
In CAM HA, when heartbeat is configured on multiple interfaces and eth1 is down, the standby CAM
fails to do the database synchronization. The perfigo service is stopped on the standby CAM as the
database synchronization happens only on eth1, which is down. Cisco recommends using only eth1 as
heartbeat interface for CAM HA instead of using multiple HA interfaces.
Note
When deploying the CAM/CAS across a WAN, you must prioritize all CAM/CAS traffic and SNMP
traffic, and include the eth0/eth1 IP addresses of the CAM and CAS in addition to the Service IP address
for HA pairs. The prioritization can have a 256 kpbs bandwidth with roudtrip delayof 400ms.
Caution
The connection between HA pairs must be extremely reliable, with communication between HA pairs
unimpeded. The best practice is to use a dedicated Ethernet cable. Breaking communication between HA
pairs will result in two active nodes, which can have serious negative operational consequences. A key
aspect of the link between HA pairs is the ability to restore that link should it go down; restoration may
be fundamental to network stability, depending on your design.