Forum Discussion
Assistance with iRule using port ranges
- Dec 22, 2023
it seems because you define the tcp port as ...:0 instead of
https://clouddocs.f5.com/api/irules/pool.htmlit will be tidier if you put .52 and and .58 in separate pools so you dont need to define pool member in the irule.
you can use pool's priority group activation in each pool if you want both to be members.btw, it's better to use gui based traffic policy to avoid scripting typo
BTW, your iRule was 99% correct; it just had a slight typo:
You just needed to amend the TCP::local_port command as it is case sensitive i.e:
FROM
tcp::local_port
TO
TCP::local_port
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