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

Con the HA-Primary Clean Access Server, a. Access the HA-Primary CAS Directly

Page 147 highlights

Chapter 4 Configuring High Availability (HA) Installing a Clean Access Server High Availability Pair Configure the HA-Primary Clean Access Server The general sequence to configure the HA-Primary CAS is as follows: a. Access the HA-Primary CAS Directly, page 4-27 b. Configure the Host Information for the HA-Primary CAS, page 4-27 c. Configure HA-Primary Mode and Update, page 4-28 d. Configure the SSL Certificate, page 4-32 e. Reboot the HA-Primary CAS, page 4-33 f. Add the CAS to the CAM Using the Service IP, page 4-33 When done, continue to Configure the HA-Secondary Clean Access Server, page 4-34. a. Access the HA-Primary CAS Directly Each Clean Access Server has its own web admin console that allows configuration of certain limited Administration settings directly on the CAS. The CAS direct access web console must be used to configure CAS pairs for HA. To access the HA-Primary Clean Access Server's direct access web admin console: 1. Open a web browser and type the IP address of the trusted (eth0) interface of the CAS in the URL/address field, as follows: https:///admin (for example, https://172.16.1.2/admin). 2. Accept the temporary certificate and log in as user admin with the web console password specified during initial configuration. Note • In order to copy and paste values to/from configuration forms, Cisco recommends keeping both web consoles open for each CAS (primary and secondary). See also a. Access the HA-Secondary CAS Directly, page 4-34. • To ensure security, Cisco recommends changing the initial password of the CAS. b. Configure the Host Information for the HA-Primary CAS 3. Click the Network Settings link, then the DNS tab. 4. In the Host Name field, type the host name for the HA-Primary CAS. Make sure there is a domain in the Host Domain field, such as cisco.com. If necessary, add one and click Update. Note When configuring HA, it is mandatory to specify a Host Name for each machine in the HA-pair. The Host Name is case-sensitive and cannot be an IP address. Host Names are needed later for the Local Host Name and Peer Host Name fields of the HA Primary and HA Secondary configuration. The Local Host Name and Peer Host Name do not need to be resolvable via DNS; however, they are case-sensitive and need to match the Host Names you have specified for the machines. OL-20326-01 Cisco NAC Appliance Hardware Installation Guide 4-27

  • 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-27
Cisco NAC Appliance Hardware Installation Guide
OL-20326-01
Chapter 4
Configuring High Availability (HA)
Installing a Clean Access Server High Availability Pair
Configure the HA-Primary Clean Access Server
The general sequence to configure the HA-Primary CAS is as follows:
a. Access the HA-Primary CAS Directly, page 4-27
b. Configure the Host Information for the HA-Primary CAS, page 4-27
c. Configure HA-Primary Mode and Update, page 4-28
d. Configure the SSL Certificate, page 4-32
e. Reboot the HA-Primary CAS, page 4-33
f. Add the CAS to the CAM Using the Service IP, page 4-33
When done, continue to
Configure the HA-Secondary Clean Access Server, page 4-34
.
a. Access the HA-Primary CAS Directly
Each Clean Access Server has its own web admin console that allows configuration of certain limited
Administration settings directly on the CAS. The CAS direct access web console must be used to
configure CAS pairs for HA.
To access the HA-Primary Clean Access Server’s direct access web admin console:
1.
Open a web browser and type the IP address of the trusted (eth0) interface of the CAS in the
URL/address field, as follows:
https://<primary_CAS_eth0_IP_address>/admin
(for example,
).
2.
Accept the temporary certificate and log in as user
admin
with the web console password specified
during initial configuration.
Note
In order to copy and paste values to/from configuration forms, Cisco recommends keeping both web
consoles open for each CAS (primary and secondary). See also
a. Access the HA-Secondary CAS
Directly, page 4-34
.
To ensure security, Cisco recommends changing the initial password of the CAS.
b. Configure the Host Information for the HA-Primary CAS
3.
Click the
Network Settings
link, then the
DNS
tab.
4.
In the
Host Name
field, type the host name for the HA-Primary CAS. Make sure there is a domain
in the
Host Domain
field, such as cisco.com. If necessary, add one and click
Update
.
Note
When configuring HA, it is mandatory to specify a Host Name for each machine in the HA-pair.
The Host Name is case-sensitive and cannot be an IP address. Host Names are needed later for
the
Local Host Name
and
Peer Host Name
fields of the HA Primary and HA Secondary
configuration. The
Local Host Name
and
Peer Host Name
do not need to be resolvable via
DNS; however, they are case-sensitive and need to match the Host Names you have specified for
the machines.