Forum Discussion
Michel_van_der_
Nimbostratus
Nov 15, 2006Persistence profile not working...
I've run into an interesting problem. As part of my code to
configure a BigIP, I (at times) use a cookie persistence. So,
my code creates a profile with LocalLB/ProfilePersistence, with
a mode of PERSISTENCE_MODE_COOKIE. Then I apply this profile
to my Virtual Server. So far so good.
However, the profile does not seem to be applied to the virtual
server, UNLESS I reboot the box. THEN it all works.
Is there something I'm missing?
2 Replies
- That is exactly the opposite of what I would think should happen. Unless you issue a System::ConfigSync::save_configuration(), the configuration should not be persisted across reboots. And, if you make the call to apply it to the virtual, it should show up in the GUI immediately.
If this persists, I would suggest you contact Tech Support as this is a system issue.
-Joe - Michel_van_der_
Nimbostratus
Sorry that I did not make it clear that I do save the
config as part of the build process.
So, it working after a reboot is not that surprising. But why does
the profile not do anything?
Some things I tried from the GUI:
- switch to built-in cookie profile -> works
- switch back to built-in cookie profile -> works
The bigip.config file looks as expected. It just seems the profile
does not get applied in memory.
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
