Forum Discussion
Deb_Allen_18
Jun 25, 2007Historic F5 Account
A few suggestions from my colleagues came up over lunch (yeah, I know, I never get a break!)
First one was to force the one pool member DOWN then back UP almost immediately, which would have the same effect as the 2nd bigpipe command above, but you could do it in the GUI.
Next was the revelation that we now have bigpipe commands specific to killing the persistence entries rather than the connections themselves:
bigpipe persist node delete
orbigpipe persist pool node delete
orbigpipe persist all delete
HTH
/deb