Forum Discussion
MaxMedov
Cirrostratus
CirrostratusVIP Type decision
Hi, I need help deciding between choosing the best compatible type for the VIP. The needs: Customer-facing VIP that will forward client data to other VIPS. Behind this 'backend' VIP will be a few s...
Amine_Kadimi
MVP
MVPThis sounds like a good approach, all the performance consuming traffic will be handlend in frontend VIP, and backend won't have to do what was already done (waf, compression, ssl, cache...).
Performance L4 sounds OK for its lower impact on processing time unless you need oneconnect to reduce the backend connection table size, which is available in Performance HTTP.
MaxMedovCirrostratus
CirrostratusAmine_Kadimi Thank you for your answer!
On the other hand, we have client smoke scripts that initiate the client path.
If the backend VIP is without waf, compression, SSL, cache, etc., the result will not be correct enough. To imitate a client, I should send the script to the frontend VIP directly, but it will route me to the next VIP in the Pool when it site routed to another site. (the primary pool member VIP disabled)
So from that perspective, I need the Backend VIP with all the feathers.
Front VIP can be standard too, but it will do the same work twice and raise the latency
In this case, Performance HTTP /L4 will be better on the front VIP.
Between them, what do you recommend? I should receive all the possible data from the client in the end to collect logs.
- Amine_Kadimi
Using Performance L4 in the front VIP, I think you will lose the source IP, because HTTP header inserting (XFF) is not suppported
- MaxMedov
- Paulius
MaxMedov Sometimes you can choose the profile but certain features will not work or it will error when you click save or create on the virtual server page. This is similar to when you associate an HTTP profile to a 443 virtual server but don't configure a client SSL profile so when you try the virtual server it just spins.
