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

Link-Detect Interfaces, Active/Standby Status, etc/ha.d/linkdetect.conf, linkdetect.conf, etc/ha.d

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 165 highlights

Chapter 4 Configuring High Availability (HA) Useful CLI Commands for HA log_badpack warntime debug debugfile logfile watchdog node node false 10 0 /var/log/ha-debug /var/log/ha-log /dev/watchdog rjcas_1 rjcas_2 Link-Detect Interfaces The /etc/ha.d/linkdetect.conf file is useful if your network topology restricts configuring external (pingable) interfaces for Link-detect functionality between your CAS HA pair appliances. This file specifies the CAS network interfaces (eth0, eth1, or both) to monitor for Link-detect functionality. If a monitored interface loses connectivity with its associated external interface, the active CAS fails over and the standby CAS assumes the active role. To create and/or update the linkdetect.conf file in the CAS: Step 1 Step 2 Step 3 Step 4 Step 5 Log in to the CAS direct console CLI and direct console as the root user. Navigate to the /etc/ha.d/ directory on the CAS. Using a standard text editor (like vi), edit the linkdetect.conf file so that it contains the interface names you want to monitor, or (if the linkdetect.conf file does not currently exist on the CAS) add the linkdetect.conf file to this directory. Verify the contents of the file: [root@rjcas_1 ha.d]# more linkdetect.conf # The following network interfaces will be monitored for link healthiness # The active CAS will change to standby mode when any link failure is detected # eth0 eth1 Enable the new function by stopping and restarting CAS services with the service perfigo stop and service perfigo start commands. In the above linkdetect.conf file example, both the eth0 and eth1 interfaces on the CAS are monitored for network connectivity. Note Any other CAS interfaces specified in the linkdetect.conf file (like eth2 or eth3, for example) are ignored for purposes of Link-detect behavior. Active/Standby Status The following example shows how to use the CLI to determine the runtime status (active or standby) of each CAS in the HA pair. You can find the fostate.sh command in the /perfigo/common/bin/ directory on new and upgraded CASs. 1. Cd to /perfigo/common/bin/, and run the fostate.sh script on the first CAS: [root@rjcas_1 bin]# ./fostate.sh OL-20326-01 Cisco NAC Appliance Hardware Installation Guide 4-45

  • 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-45
Cisco NAC Appliance Hardware Installation Guide
OL-20326-01
Chapter 4
Configuring High Availability (HA)
Useful CLI Commands for HA
log_badpack
false
warntime
10
debug
0
debugfile
/var/log/ha-debug
logfile
/var/log/ha-log
watchdog
/dev/watchdog
node
rjcas_1
node
rjcas_2
Link-Detect Interfaces
The
/etc/ha.d/linkdetect.conf
file is useful if your network topology restricts configuring external
(pingable) interfaces for Link-detect functionality between your CAS HA pair appliances. This file
specifies the CAS network interfaces (eth0, eth1, or both) to monitor for Link-detect functionality. If a
monitored interface loses connectivity with its associated external interface, the active CAS fails over
and the standby CAS assumes the active role.
To create and/or update the
linkdetect.conf
file in the CAS:
Step 1
Log in to the CAS direct console CLI and direct console as the root user.
Step 2
Navigate to the
/etc/ha.d/
directory on the CAS.
Step 3
Using a standard text editor (like vi), edit the linkdetect.conf file so that it contains the interface names
you want to monitor, or (if the linkdetect.conf file does not currently exist on the CAS) add the
linkdetect.conf file to this directory.
Step 4
Verify the contents of the file:
[root@rjcas_1 ha.d]#
more linkdetect.conf
# The following network interfaces will be monitored for link healthiness
# The active CAS will change to standby mode when any link failure is detected
#
eth0
eth1
Step 5
Enable the new function by stopping and restarting CAS services with the
service perfigo stop
and
service perfigo start
commands.
In the above
linkdetect.conf
file example, both the eth0 and eth1 interfaces on the CAS are monitored
for network connectivity.
Note
Any other CAS interfaces specified in the
linkdetect.conf
file (like eth2 or eth3, for example) are
ignored for purposes of Link-detect behavior.
Active/Standby Status
The following example shows how to use the CLI to determine the runtime status (active or standby) of
each CAS in the HA pair. You can find the fostate.sh command in the
/perfigo/common/bin/
directory
on new and upgraded CASs.
1.
Cd to
/perfigo/common/bin/
, and run the fostate.sh script on the first CAS:
[root@rjcas_1 bin]#
./fostate.sh