Oneconnect profile resolves the issue with routing but it breaks some other functionality with the application itself so we would rather not use it.
what is broken? have you tried oneconnect with 32 bit mask (i.e. 255.255.255.255)?
When one Connect is enabled our legacy application starts throwing errors.
I think I found a way around it by adding ONECONNECT::reuse enable in the begining of the iRule and ONECONNECT::reuse disable before it goes to the market pool.
i think class command could have better performance comparing with switch glob
Would you be able to provide an example?
Thanks!