Forum Discussion
CirrostratusHow can I effectively reduce LTM VIP / Pool settings?
Hi guys.
I`m planning to reduce LTM configuration effectively.
I thought available things but not so good. are there any other method, please give me advice.
Requirements only 1 VIP and service ports are over 40 / Pool members are 4. When the health check of a specific port is down, LB should be excluded only for the corresponding server and port. In this circumstance, have to make 40 pools, 40 VIPs. and when pool member IP is changed, have to config 40 pools. and modifying with CLI also troublesome.
-
create VIP with service port * / create 1 pool with 4 members port * / create 40 alias monitors it would be nice and easy to modifying pool. but it don
s 'Availability Requirement't meet Requirement. cause of monitor -
create VIP with service port * / create 1 i-Rule / create 40 pools. i-Rule LB traffic based on dst port and LB to same service port pool. i-Rule syntax will be long. and modifying pool is troublesome.
-
similar with method 2, but when add pool members, use FQDN & auto population. and set DNS to BIGIP. it would be nice and easy to modifying pool. -> add or delete DNS ns record. but it need DNS`s help and desired to be performed independently.
is there any wonderful method, please guide me.
thank you.
eben_259100You can create 40 pools and 1 VIP with a service port of *. then switch application traffic based on TCP::local_port to the backend pools.
when CLIENT_ACCEPTED { switch -exact [TCP::local_port] { "8080" { pool 8080_pool } "8090"{ pool 8090_pool } "nnnn" { pool nnnn_pool } } }HTH
swjo_264656Hi eben.
I also think switching i-Rule.
but that also need 40 pools and hard to modifying pool members.
do you have any idea how to reduce pools?
thanks
- eben_259100
You can create just 1 pool with with members listening on all ports (*) but then, application specific health check you mentioned will not be possible. Would you be willing to tradeoff performance for manageability? Also if you decide to create one wildcard pool, the irule won't be needed.
HTH
ebenNimbostratus
You can create 40 pools and 1 VIP with a service port of *. then switch application traffic based on TCP::local_port to the backend pools.
when CLIENT_ACCEPTED { switch -exact [TCP::local_port] { "8080" { pool 8080_pool } "8090"{ pool 8090_pool } "nnnn" { pool nnnn_pool } } }HTH
- swjo_264656
Hi eben.
I also think switching i-Rule.
but that also need 40 pools and hard to modifying pool members.
do you have any idea how to reduce pools?
thanks
- eben
You can create just 1 pool with with members listening on all ports (*) but then, application specific health check you mentioned will not be possible. Would you be willing to tradeoff performance for manageability? Also if you decide to create one wildcard pool, the irule won't be needed.
HTH