Forum Discussion
CirrusMigrate to new default gateway
Hello, we are making some changes to our network and one of those changes is firewalls, so we now have to use a new default gateway.
I can change the default gateway on the unit itself, but we are trying to move to the new gateway slowly just in case something was to go wrong. so we want to configure the virtual servers one at a time to use the new gateway, and according to what the support engineer told me the best way to do this is via an iRule.
he can't write one for me, and of course that makes sense, so I need some help with such iRule. it's going to be the same for all virtual servers, because we are switching from one gateway to another.
I would like to be able to assign the iRule the virtual server and then from that point on the virtual server would use the new gateway only.
any help is greatly appreciated.
You might want to look at the
command. See:nexthophttps://devcentral.f5.com/wiki/iRules.nexthop.ashx
This should be something you can easily test.
Another thing that could be of use is 'Auto last hop'. See:
Stanislas_Piro2Cumulonimbus
Do you want to manage route to pool members or to respond clients?
Bigip use auto last hop for clientside routing. It means that the routing configuration is not used to send packets back to the client.
The last hop MAC address (firewall MAC address) is stored in connection table and used for response.
So all you have to manage is serverside connections.
It’s not recommended to use irule based routing because monitor will still use system routing
The best solution is to configure temp destination routing pool members by pool members (or network by network)
