Forum Discussion
SNAT and Next hop based on Node address
Hello Paulius,
The reason for not having a static route is we have clients coming from different interfaces.
The second thing is we do not have HTTP traffic coming to this VIP. we have TCP traffic (SQL).
What else we can have other than HTTP_REQUEST?
when CLIENT_ACCEPTED priority 500 {
set DEFAULT_POOL [LB::server pool]
}
when <> priority 500 {
if { [active_members [LB::server pool]] == 0} {
snatpool SNAT_REP
pool DBS5G_REP_REMOTE
nexthop /DBS/DBS_CLIENT_174 10.219.30.65
} else {
pool ${DBS5G_REP_LOCAL}
}
}
vbhugra The following iRule should work for the SQL communication.
when CLIENT_ACCEPTED priority 500 {
set DEFAULT_POOL [LB::server pool]
if { [active_members [LB::server pool]] == 0} {
snatpool SNAT-<VS_IP>
pool POOL-ServerBehindRouter
} else {
pool ${DEFAULT_POOL}
}
}
I do not see why you cannot have the permanent route in place even if traffic is coming from different interfaces because the way the F5 reaches it will always be the same direction.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com