With this in mind, it does not make sense to skip a match rule because the server (or servers)
named in the rule are down, hot spared, or quiesced -- rather, since the server in the rule is
presumably critical to satisfying the request, it makes sense to route the request to the (for
example) down server, and have the client receive an appropriate error -- so that the request can
be retried.
If we instead were to skip a match rule because, for example, the server selected by the match
rule is down, the request would be evaluated by the next match rule -- or the default match rule.
The request, therefore, could potentially be sent to a server in the cluster that does not have the
requested content. This means that the client would receive a “not found” error, instead of an
error indicating that the appropriate server is not currently available.
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
All Rights Reserved.
399
Equalizer Administration Guide
Summary of Contents for Equalizer GX Series
Page 18: ......
Page 32: ...Overview 32 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 42: ......
Page 52: ......
Page 64: ......
Page 72: ......
Page 76: ......
Page 228: ......
Page 238: ......
Page 476: ......
Page 492: ......
Page 530: ......
Page 614: ......
Page 626: ......
Page 638: ......
Page 678: ......
Page 732: ...Using SNMP Traps 732 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 754: ......
Page 790: ......
Page 804: ......
Page 842: ......
Page 866: ......