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

Connect the Clean Access Manager Machines

Page 128 highlights

Installing a Clean Access Manager High Availability Pair Chapter 4 Configuring High Availability (HA) • The HA-Primary CAM is fully configured for runtime operation. This means that connections to authentication sources, policies, user roles, access points, and so on, are all specified. This configuration is automatically duplicated in the HA-Secondary (standby) CAM. • If you use the Authorization feature in a CAM HA-pair, follow the guidelines in "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. (CAM Authorization settings are not automatically passed from one CAM to the other in an HA-pair.) • Both Clean Access Managers are accessible on the network (try pinging them to test the connection). • The machines on which the CAM software is installed have at least one free Ethernet port (eth1) and at least one free serial port. Use the specification manuals for the server hardware to identify the serial port (ttyS0 or ttyS1) on each machine. • In Out-of-Band deployments, Port Security is not enabled on the switch interfaces to which the CAS and CAM are connected. This can interfere with CAS HA and DHCP delivery. The following procedures require you to reboot the Clean Access Manager. At that time, its services will be briefly unavailable. You may want to configure an online CAM when downtime has the least impact on your users. Note Cisco NAC Appliance web admin consoles support the Internet Explorer 6.0 or above browser. Connect the Clean Access Manager Machines There are two types of connections between HA-CAM peers: one for exchanging runtime data relating to the Clean Access Manager activities and one for the heartbeat signal. In High Availability, the Clean Access Manager always uses the eth1 interface for both data exchange and heartbeat UDP exchange. When the UDP heartbeat signal fails to be transmitted and received within a certain time period, the standby system takes over. In order to provide an extra measure of heartbeat redundancy, Cisco recommends you use more Ethernet interfaces in addition to eth1 (mandatory) interface for heartbeat exchange. In order for a failover to occur, all configured heartbeat interfaces must report heartbeat exchange failure. (The eth0 and eth2/eth3 can be used for additional heartbeat interfaces.) Note, however, that the eth1 connection between the CAM peers is mandatory. Physically connect the peer Clean Access Managers as follows: • Use a crossover cable to connect the eth1 Ethernet ports of the Clean Access Manager machines. This connection is used for the heartbeat UDP interface and data exchange (database mirroring) between the failover peers. • Use null modem serial cable to connect the serial ports (highly recommended). • Optionally connect eth2 and/or eth3 interfaces on the CAM to counterpart interfaces on the HA peer using either crossover cables or via an in-line switch. (Remember: you must configure these interfaces manually before configuring your CAM for HA). Note For serial cable connection for HA, the serial cable must be a "null modem" cable. For details, refer to http://www.nullmodem.com/NullModem.htm. Cisco NAC Appliance Hardware Installation Guide 4-8 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-8
Cisco NAC Appliance Hardware Installation Guide
OL-20326-01
Chapter 4
Configuring High Availability (HA)
Installing a Clean Access Manager High Availability Pair
The HA-Primary CAM is fully configured for runtime operation. This means that connections to
authentication sources, policies, user roles, access points, and so on, are all specified. This
configuration is automatically duplicated in the HA-Secondary (standby) CAM.
If you use the Authorization feature in a CAM HA-pair, follow the guidelines in “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. (CAM Authorization
settings are not automatically passed from one CAM to the other in an HA-pair.)
Both Clean Access Managers are accessible on the network (try pinging them to test the connection).
The machines on which the CAM software is installed have at least one free Ethernet port (eth1) and
at least one free serial port. Use the specification manuals for the server hardware to identify the
serial port (ttyS0 or ttyS1) on each machine.
In Out-of-Band deployments, Port Security is not enabled on the switch interfaces to which the CAS
and CAM are connected. This can interfere with CAS HA and DHCP delivery.
The following procedures require you to reboot the Clean Access Manager. At that time, its services will
be briefly unavailable. You may want to configure an online CAM when downtime has the least impact
on your users.
Note
Cisco NAC Appliance web admin consoles support the Internet Explorer 6.0 or above browser.
Connect the Clean Access Manager Machines
There are two types of connections between HA-CAM peers: one for exchanging runtime data relating
to the Clean Access Manager activities and one for the heartbeat signal. In High Availability, the Clean
Access Manager
always
uses the eth1 interface for both data exchange and heartbeat UDP exchange.
When the UDP heartbeat signal fails to be transmitted and received within a certain time period, the
standby system takes over. In order to provide an extra measure of heartbeat redundancy, Cisco
recommends you use more Ethernet interfaces in addition to eth1 (mandatory) interface for heartbeat
exchange. In order for a failover to occur, all configured heartbeat interfaces must report heartbeat
exchange failure. (The eth0 and eth2/eth3 can be used for additional heartbeat interfaces.) Note,
however, that the eth1 connection between the CAM peers is mandatory.
Physically connect the peer Clean Access Managers as follows:
Use a crossover cable to connect the eth1 Ethernet ports of the Clean Access Manager machines.
This connection is used for the heartbeat UDP interface and data exchange (database mirroring)
between the failover peers.
Use null modem serial cable to connect the serial ports (highly recommended).
Optionally connect eth2 and/or eth3 interfaces on the CAM to counterpart interfaces on the HA peer
using either crossover cables or via an in-line switch. (Remember: you must configure these
interfaces manually before configuring your CAM for HA).
Note
For serial cable connection for HA, the serial cable must be a “null modem” cable. For details,
refer to
.