Hi,
Quick question on the use of client nat pools. Is it possible to use the same client nat pool for multiple server farms as indicated below? I suspect it shouldn't be an issue.
Using FARM-MOBS-389 as an example, any connection from a real server in the farm to its frontend IP address (130.194.11.51) should see that connection load balanced to either itself or the other member of the farm.
natpool POOL1 10.1.5.1 10.1.5.254 netmask 255.255.255.0
serverfarm FARM-MOBS-389
nat server
nat client POOL1
predictor leastconns
failaction purge
real 130.194.12.81
inservice
real 130.194.12.84
inservice
probe MOBS-389
!
serverfarm FARM-MOBS-636
nat server
nat client POOL1
predictor leastconns
failaction purge
real 130.194.12.81
inservice
real 130.194.12.84
inservice
probe MOBS-636
!
serverfarm FARM-MOBS-7777
nat server
nat client POOL1
predictor leastconns
failaction purge
real 130.194.12.81
inservice
real 130.194.12.84
inservice
probe MOBS-7777
!
serverfarm FARM-MOBS-7778
nat server
nat client POOL1
predictor leastconns
failaction purge
real 130.194.12.81
inservice
real 130.194.12.84
inservice
probe MOBS-7778
!
vserver VMOBS-PROD-389
description VIP for MOBS LDAP traffic port 389
virtual 130.194.11.51 tcp 389
serverfarm FARM-MOBS-389
persistent rebalance
inservice
!
vserver VMOBS-PROD-636
description VIP for MOBS LDAP traffic port 636
virtual 130.194.11.51 tcp 636
serverfarm FARM-MOBS-636
persistent rebalance
inservice
!
vserver VMOBS-PROD-7777
description VIP for MOBS HTTP traffic port 7777
virtual 130.194.11.51 tcp 7777
serverfarm FARM-MOBS-7777
sticky 60 group 105
persistent rebalance
inservice
!
vserver VMOBS-PROD-7778
description VIP for MOBS HTTP traffic port 7778
virtual 130.194.11.51 tcp 7778
serverfarm FARM-MOBS-7778
sticky 60 group 108
persistent rebalance
inservice
Any feed back would be useful.
thanks
Sheldon
