Forum Discussion
Routing in a standard virtual server
- Dec 04, 2017
Two options that I know of.
Do exactly what you said you didn't want to do, create a node that is the IP address of your next hop, toss that into a pool, assign this single noded pool to your VS. Assign a ping monitor on it if you want to verify it is up. Otherwise assign no monitors to it.
Option 2, do not assign a pool to the VS and instead use an iRule to forward traffic to the next hop IP address: https://devcentral.f5.com/wiki/iRules.nexthop.ashx I usually do this option with a forwarding server instead of a standard server because I did not want a full proxy for this traffic.
Two options that I know of.
Do exactly what you said you didn't want to do, create a node that is the IP address of your next hop, toss that into a pool, assign this single noded pool to your VS. Assign a ping monitor on it if you want to verify it is up. Otherwise assign no monitors to it.
Option 2, do not assign a pool to the VS and instead use an iRule to forward traffic to the next hop IP address: https://devcentral.f5.com/wiki/iRules.nexthop.ashx I usually do this option with a forwarding server instead of a standard server because I did not want a full proxy for this traffic.
No prob!
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