You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm honestly not sure if this is an issue with go-bigip or the iControl REST interface, but when I do a replace-all-with pool modification via tmsh, the new pool members have the following availability / states:
| Availability : unknown
| State : enabled
| Reason : Pool member service checking is enabled, but result is not available yet
| Monitor Status : checking
| Session Status : enabled
This is what I would expect; the BigIP hasn't performed a health check, yet. But for some reason when I do an UpdatePoolMembers via go-bigip, the new pool members have the following availability / states:
| Availability : available
| State : enabled
| Reason : Pool member is available
| Monitor Status : up
| Session Status : enabled
Is this expected? Why the difference?
The text was updated successfully, but these errors were encountered:
I'm honestly not sure if this is an issue with go-bigip or the iControl REST interface, but when I do a replace-all-with pool modification via tmsh, the new pool members have the following availability / states:
| Availability : unknown
| State : enabled
| Reason : Pool member service checking is enabled, but result is not available yet
| Monitor Status : checking
| Session Status : enabled
This is what I would expect; the BigIP hasn't performed a health check, yet. But for some reason when I do an UpdatePoolMembers via go-bigip, the new pool members have the following availability / states:
| Availability : available
| State : enabled
| Reason : Pool member is available
| Monitor Status : up
| Session Status : enabled
Is this expected? Why the difference?
The text was updated successfully, but these errors were encountered: