Eric_Frankenfie
Aug 10, 2010Nimbostratus
Virtual Route Table for VS
Is there a way to create a separate route table for a VS?
I have devices that are local to the LTM that need to FTP to a new VS. My existing configuration requires using 10.206.173.1 as the default gateway, however the new VS requires using 10.206.0.1 as the gateway. I cannot modify the routing table because the same devices at the remote location use my existing VS via the default gateway 10.206.173.1.
I am using the following iRule to perform the SNAT on the new VS which is working.
when CLIENT_ACCEPTED {
snat 10.206.0.251
}
My issue now is that I have an asymmetrical routing situation. The SNAT (10.206.0.251) is routing out the DG (10.206.173.1) and then the return traffic is coming back on the 10.206.0.0/22 interface.
Sources: 10.206.0.135, 10.206.1.50, 10.206.173.129
VS: 10.206.1.245
Pool Members: 10.249.1.59, 10.249.1.100
I attached a diagram that may help...