Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual Page 103

  • Download
  • Add to my manuals
  • Print
  • Page
    / 136
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 102
ServerIron ADX Advanced Server Load Balancing Guide 91
53-1002435-01
Sample configurations
2
Policy based caching configuration
The following configuration implements the topology described in Figure 22.
Asymmetric TCS (FastCache)
Traffic in typical TCS configurations passes through the ServerIron ADX both from the client to the
cache and from the cache to the client. The ServerIron ADX uses the cache responses to the client
to diagnose the health of the cache server.
If the cache server responds to the client requests the ServerIron ADX redirects to the cache server,
the ServerIron ADX knows that the cache server is healthy. However, if the cache server stops
sending replies to the client requests, the ServerIron ADX assumes that the cache server is down
and stops redirecting requests to that cache server.
Some configurations are asymmetric—traffic from the cache server to the client does not pass back
through the ServerIron ADX. For example, caches that support multiple NICs might at the same
time support only one default gateway. Figure 23 shows a configuration in which a cache server’s
default gateway is configured to go to the customer access router (RAS) instead of the ServerIron
ADX. In this configuration, the ServerIron ADX does not see cache responses to client requests.
Because the ServerIron ADX does not see responses coming from the cache server, the ServerIron
ADX assumes that the cache server is down and stops redirecting requests to that cache server.
You can override this behavior by enabling the FastCache feature. This feature configures the
ServerIron ADX to continue redirecting client requests to a cache server even though the ServerIron
ADX does not see responses from the cache server. You enable the feature individually for real
servers.
ServerIronADX(config)#server cache-name ch1 40.40.40.100
ServerIronADX(config-rs-ch1)#port http
ServerIronADX(config-rs-ch1)#exit
ServerIronADX(config)#server cache-name ch2 40.40.40.101
ServerIronADX(config-rs-ch2)#port http
ServerIronADX(config-rs-ch2)#exit
ServerIronADX(config)#server cache-name ch3 40.40.40.102
ServerIronADX(config-rs-ch3)#port http
ServerIronADX(config-rs-ch3)#exit
ServerIronADX(config)#server cache-name ch4 40.40.40.103
ServerIronADX(config-rs-ch4)#port http
ServerIronADX(config-rs-ch4)#exit
ServerIronADX(config)#server cache-group 1
ServerIronADX(config-tc-1)#cache-name ch1
ServerIronADX(config-tc-1)#cache-name ch2
ServerIronADX(config-tc-1)#filter-acl 101
ServerIronADX(config-tc-1)#exit
ServerIronADX(config)# server cache-group 2
ServerIronADX(config-tc-2)#cache-name ch3
ServerIronADX(config-tc-2)#cache-name ch4
ServerIronADX(config-tc-2)#filter-acl 102
ServerIronADX(config-tc-2)#exit
ServerIronADX(config)# server cache-bypass 103
ServerIronADX(config)# access-list 101 permit tcp any host 1.1.1.1
ServerIronADX(config)# access-list 102 permit tcp any host 1.1.1.2
ServerIronADX(config)# access-list 103 permit tcp any host 1.1.1.3
Page view 102
1 2 ... 98 99 100 101 102 103 104 105 106 107 108 ... 135 136

Comments to this Manuals

No comments