Forum Discussion
joel_hendrickso
Jul 29, 2009Historic F5 Account
We have found the cause of this problem and put in a fix that will be in the next release, scheduled for the week of august 10th (2 weeks from now).
If a pool member with port 4444 is discovered, any state changes (such as enable/disable/up/down) to that pool member will cause the service to crash. This has to do with the way that Big-IP translates some ports when it notifies us of state updates (in this case, 4444="KRB524").
There is no workaround at this point besides restarting the service.