Forum Discussion
NimbostratusSSL offload
NacreousSSL offload is independant of port. We use 443 for user convenience on the client side.
When it comes to iRules you start your processing with the settings on the virtual server as your baseline. Then you process Local Traffic Policies, then iRules in that order. They can update the template. Then when all that is finished the F5 uses the updated template.
As for persistence if you select a pool using an iRule and not a pool member it will follow any matching persistence record for that pool. If their is none it will load balance as per the pool configuration. If you use an iRule to select a pool member it will overide any persistence and use it, for some persistence configurations this will also trigger an update of the persistence record to the new pool member. Note: This can only happen at the beginning of a connection. After that it will ignore any future selection as the F5 load balances per connection. If you want per request load balancing you need to enable one connect.
NacreousYou dont have to use the drop down box on the right, you can just type in the port number. Assign an SSL profile and it will work. The 'other' just means its not on a recognised port. The names on the right are just labels that are matched to the port numbers you type in. Standard ports are known, everything else is other. They are not protocol definitions for the virtual server.
