Technical data

Brocade ServerIron ADX Advanced Server Load Balancing Guide 57
53-1003441-01
Other transparent cache switching options
2
Destination NAT for TCS
If the cache server is remote (not directly connected to the ServerIron ADX), or is running in proxy
mode (client connection is terminated completely from the back-end Internet connection),
destination NAT can be configured for TCS.
When destination NAT is enabled under a cache server, the destination IP of client TCS traffic
(client-to-Internet) is translated to that of the cache server (client-to-cache). The cache server then
serves the web content from its cache, if available. If content is not available locally, the cache
server will request content from the original destination (embedded in the HTTP host header).
When destination NAT is configured under a cache group, the destination IP of TCS traffic to all
cache servers under this cache group is translated to a selected cache server's IP address. This is
applicable for a remote cache server or when a cache server is running in proxy mode (not
transparent mode).
Configuring destination NAT
Destination NAT can be configured either under a cache server or a cache group as shown in the
following commands:
For a cache server
ServerIronADX(config)#server cache-name server1 10.95.5.11
ServerIronADX(config-rs-server1)#dest-nat
ServerIronADX(config-rs-server2)#
For a cache group
ServerIronADX(config)#server cache-group 1
ServerIronADX(config-tc-1)#dest-nat
Syntax: [no] dest-nat