Forum Discussion
richard_polyak
Altocumulus
Altocumulusirule or policy to match url and then update pool members port
Good afternoon, looking for some assistance it modifying the following irule we are using. The problem with this irule is it has 100's of pools to send the url to on a differnt port on the server. Th...
Paulius
MVP
MVPrichard_polyak I haven't had a chance to test the iRule sadly but it seems like it could work with one exception. In order to match the string and value field you have to create a temp variable and save your string match and then use that variable to compare the value field, your port, to the associated URI path. Would you mind sharing why you are going this route instead of keeping it the way it is?
richard_polyakPauius -
Thanks for the reply, reason is this has become very ineffieceint on the F5. Today we have everything on the /Common partion "I am in the process of converting this over to AS3 deployed via BIG-IQ" So the issue of opening the pools in the GUI is extremely slow. This is the issue trying to better utilize the resources on the F5, and since all the nodes in the 100's of pools are the exact same, I don't see any reason to have to have 100's of pools.
once this is over in it's own partition it shouldn't be an issue. But again if we have to change 1 node, I then need to touch 100's of pools. Again not very effeciant.
Thx
Rich
If you're looking for efficiency in an iRule, Kai_Wilke may be able to help.
- Paulius
richard_polyak I see what you are getting at. You could probably get away with configuring one pool with a pool member port as zero and then utilize an iRule to pick the port that you want to send traffic to. The issue that you will run into is how are you going to confirm that the respective port is alive without an associated health monitor? If this is all going to the exact same destination IP for the respective pool member node you might consider creating one pool with a pool member per server in rotation and send all traffic to the same port. If the server is using an alternate port for some tracking purposes you can insert a header field with an associated value so that you can still perform your tracking by header field and value. You should also not configure an iRule to send traffic directly to a node with an associated port because that causes additional issues on the F5. Configuring the iRule in the manner you are wanting to causes headaches that don't need to be there and a nightmare to validate if the port is accepting and responding to requests on the associated port. Your final configuration should be 1 data group with a string (uri) and a value (port number for tracking), an iRule that utilizes a switch statement to match the URI to the string value in the data-group, create a temp value to perform matching on the matching value field in the data-group for the URI match, and finally insert an HTTP header field with a value of the data-group value field value saved in your temp variable.
