Forum Discussion
mikegray_198028
Cirrus
Sep 01, 2016persistance issue
Hi Team,
I am facing load balancing issue with a default hash persistence profile. f5 sending traffic only to one server and we don't have any irule . can some one help me on this.
ltm virtual testvip {
destination 192.168.10.1:https
ip-protocol tcp
mask 255.255.255.255
persist {
hash {
default yes
}
}
pool testvip
profiles {
testvip-clientssl {
context clientside
}
newhttp_x_forward { }
oneconnect { }
tcp-lan-optimized {
context serverside
}
tcp-wan-optimized {
context clientside
}
}
source 0.0.0.0/0
source-address-translation {
type automap
}
vs-index 715}
======================================
testvip Common 220.5M 343.2M 315.8K 253.1K 0 959 51.0K 50.7K 0 0
-- server1.test.com:8086 Common 220.5M 343.2M 315.8K 253.1K 0 959 51.0K 50.7K 0 0
-- server2.test.com:8086 Common 0 0 0 0 0 0 0 0 0 0
3 Replies
- Vijay_E
Cirrus
What do you want the persistence to do ? Using default hash persistence won't help much without understanding the logic required. Can you provide us some more information on the persistence logic required ?
- Vijay_E
Cirrus
- IainThomson85_1
Cumulonimbus
Out of curiosity - Does the F5 only see "one" IP address trying to be load balanced ?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects