Cisco ACE-4710-K9 Administration Guide - Page 285

Configuring a Probe on the Standby Member for Host Tracking, probe, peer probe, priority

Page 285 highlights

Chapter 7 Configuring Redundant ACE Appliances Configuring Tracking and Failure Detection To remove the host tracked by the standby member, enter: host1/Admin(config-ft-track-host)# no peer track-host 172.16.27.1 Configuring a Probe on the Standby Member for Host Tracking Configure one or more probes on the standby member to track the health of the gateway or host. For details about creating probes, see the Cisco 4700 Series Application Control Engine Appliance Server Load-Balancing Configuration Guide. To associate an existing probe with a gateway or host for tracking by the standby member, use the peer probe command in FT track host configuration mode. The syntax of this command is: peer probe name priority number The keyword and arguments are: • name-Identifier of an existing probe that you want to associate with a gateway or host for tracking • priority number-Specifies the priority of the probe sent by the standby member. Enter an integer from 0 to 255. The default is 0. Higher values indicate higher priorities. Assign a priority value based on the relative importance of the gateway or host that the probe is tracking. If the probe goes down, the ACE decrements the priority of the FT group on the standby member by the value of the number argument. For example, enter: host1/Admin(config-ft-track-host)# peer probe TCP_PROBE1 priority 25 To remove the tracking probe from the standby member, enter: host1/Admin(config-ft-track-host)# no peer probe TCP_PROBE1 Configuring a Priority on the Standby Member for Multiple Probes You can configure a tracking priority that the standby member of an FT group uses when multiple tracking probes are defined. To assign a priority for multiple probes on the standby member, use the peer priority command in FT track host configuration mode. The syntax of this command is: peer priority number OL-11157-01 Cisco 4700 Series Application Control Engine Appliance Administration Guide 7-33

  • 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
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418

7-33
Cisco 4700 Series Application Control Engine Appliance Administration Guide
OL-11157-01
Chapter 7
Configuring Redundant ACE Appliances
Configuring Tracking and Failure Detection
To remove the host tracked by the standby member, enter:
host1/Admin(config-ft-track-host)#
no peer track-host 172.16.27.1
Configuring a Probe on the Standby Member for Host Tracking
Configure one or more probes on the standby member to track the health of the
gateway or host. For details about creating probes, see the
Cisco 4700 Series
Application Control Engine Appliance Server Load-Balancing Configuration
Guide
. To associate an existing probe with a gateway or host for tracking by the
standby member, use the
peer
probe
command in FT track host configuration
mode. The syntax of this command is:
peer probe
name
priority
number
The keyword and arguments are:
name
—Identifier of an existing probe that you want to associate with a
gateway or host for tracking
priority
number
—Specifies the priority of the probe sent by the standby
member. Enter an integer from 0 to 255. The default is 0. Higher values
indicate higher priorities. Assign a priority value based on the relative
importance of the gateway or host that the probe is tracking. If the probe goes
down, the ACE decrements the priority of the FT group on the standby
member by the value of the
number
argument.
For example, enter:
host1/Admin(config-ft-track-host)#
peer probe TCP_PROBE1 priority 25
To remove the tracking probe from the standby member, enter:
host1/Admin(config-ft-track-host)#
no peer probe TCP_PROBE1
Configuring a Priority on the Standby Member for Multiple Probes
You can configure a tracking priority that the standby member of an FT group uses
when multiple tracking probes are defined. To assign a priority for multiple
probes on the standby member, use the
peer priority
command in FT track host
configuration mode. The syntax of this command is:
peer priority
number