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

Clean Access Server, HA CAS Configuration Status, Heartbeat/Link-Based Connections

Page 164 highlights

Useful CLI Commands for HA Chapter 4 Configuring High Availability (HA) [root@rjcam_2 ~]# This CAM is the standby CAM in the HA-pair. Clean Access Server The following are useful files to know about for HA on the CAS: • HA CAS Configuration Status (/etc/ha.d/perfigo.conf) • Heartbeat/Link-Based Connections (/etc/ha.d/ha.cf) • Link-Detect Interfaces (/etc/ha.d/linkdetect.conf) • Active/Standby Status (/perfigo/common/bin/fostate.sh) HA CAS Configuration Status The /etc/ha.d/perfigo.conf file shows a variety of configuration information for an HA-CAS, including hostname (rjcas_1), peer hostname (rjcas_2), HA mode (Primary), heartbeat interface (UDP/serial), and Link-detect interface information: [root@rjcas_1 ha.d]# more perfigo.conf #linux-ha #Mon Aug 28 18:50:15 PDT 2006 WIRELESS_SERVICEIP=10.10.20.4 PING_DEAD=25 HOSTNAME=rjcas_1 HA_DEAD=15 PEERGUSSK= PEERMAC=00\:16\:35\:BF\:FE\:67 PEERHOSTNAME=rjcas_2 TRUSTED_PINGNODE=10.10.40.100 UNTRUSTED_PINGNODE=10.10.20.100 HAMODE=PRIMARY PEERMAC0=00\:16\:35\:BF\:FE\:66 PEERHOSTIP=10.10.50.2 HA_FAILBACK=off HA_UDP=eth2 WIRED_SERVICEIP=10.10.20.4 HA_SERIAL=ttyS0 Heartbeat/Link-Based Connections The /etc/ha.d/ha.cf file shows additional information about the heartbeat and link-based connections: [root@rjcas_1 ha.d]# more ha.cf # Generated by make-hacf-ss.pl udpport 694 ucast eth2 10.10.50.2 baud 19200 serial /dev/ttyS0 keepalive 2 deadtime 15 deadping 25 auto_failback off apiauth default uid=root respawn hacluster /usr/lib64/heartbeat/ipfail ping 10.10.20.100 ping 10.10.40.100 4-44 Cisco NAC Appliance Hardware Installation Guide 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-44
Cisco NAC Appliance Hardware Installation Guide
OL-20326-01
Chapter 4
Configuring High Availability (HA)
Useful CLI Commands for HA
[root@rjcam_2 ~]#
This CAM is the standby CAM in the HA-pair.
Clean Access Server
The following are useful files to know about for HA on the CAS:
HA CAS Configuration Status
(
/etc/ha.d/perfigo.conf
)
Heartbeat/Link-Based Connections
(
/etc/ha.d/ha.cf
)
Link-Detect Interfaces
(
/etc/ha.d/linkdetect.conf
)
Active/Standby Status
(
/perfigo/common/bin/fostate.sh
)
HA CAS Configuration Status
The
/etc/ha.d/perfigo.conf
file shows a variety of configuration information for an HA-CAS, including
hostname (rjcas_1), peer hostname (rjcas_2), HA mode (Primary), heartbeat interface (UDP/serial), and
Link-detect interface information:
[root@rjcas_1 ha.d]#
more perfigo.conf
#linux-ha
#Mon Aug 28 18:50:15 PDT 2006
WIRELESS_SERVICEIP=10.10.20.4
PING_DEAD=25
HOSTNAME=rjcas_1
HA_DEAD=15
PEERGUSSK=
PEERMAC=00\:16\:35\:BF\:FE\:67
PEERHOSTNAME=rjcas_2
TRUSTED_PINGNODE=10.10.40.100
UNTRUSTED_PINGNODE=10.10.20.100
HAMODE=PRIMARY
PEERMAC0=00\:16\:35\:BF\:FE\:66
PEERHOSTIP=10.10.50.2
HA_FAILBACK=off
HA_UDP=eth2
WIRED_SERVICEIP=10.10.20.4
HA_SERIAL=ttyS0
Heartbeat/Link-Based Connections
The
/etc/ha.d/ha.cf
file shows additional information about the heartbeat and link-based connections:
[root@rjcas_1 ha.d]# more ha.cf
# Generated by make-hacf-ss.pl
udpport
694
ucast
eth2 10.10.50.2
baud
19200
serial
/dev/ttyS0
keepalive
2
deadtime
15
deadping
25
auto_failback
off
apiauth
default uid=root
respawn
hacluster /usr/lib64/heartbeat/ipfail
ping
10.10.20.100
ping
10.10.40.100