LTM-ASM deployment senerios

Hi Guy,

You must create a wildcard(0.0.0.0) "ip forwarding" virtual server, then you can create policy where you want to forward the traffic. Or you can do it with iRule. I wrote two sample iRule:

use this for just looking the client network to redirect the traffic

when CLIENT_ACCEPTED {
if {([IP::addr [IP::client_addr]/24 equals 10.10.10.0]) or ([IP::addr [IP::client_addr]/24 equals 11.11.11.0])}
{
forward the traffic to the first route
pool pool_firstRoute
} elseif {([IP::addr [IP::client_addr]/24 equals 40.40.40.0]) or ([IP::addr [IP::client_addr]/24 equals 41.41.41.0]) }
{
forward the traffic to the second route
pool pool_secondRoute
} else {
forward the traffic to the default route
forward
}
}

use this for more specific conditions

when CLIENT_ACCEPTED {
switch -glob "src:[IP::client_addr] dst:[IP::local_addr] dport:[TCP::local_port]"
"src:10.10.10.10 dst:20.20.20.20 dport:80" -
"src:11.11.11.11 dst:20.20.20.20 dport:80" -
"src:12.12.12.12 dst:3.3.3.3 dport:443"
{
forward the traffic to the first route
pool pool_firstRoute
}
"src:40.40.40.40 dst:20.20.20.20 dport:80" -
"src:41.41.41.41 dst:20.20.20.20 dport:80" -
"src:42.42.42.42 dst:3.3.3.3 dport:443"
{
forward the traffic to the second route
pool pool_secondRoute
}
default
{
forward the traffic to the default route
forward
}
}