Forum Discussion

Cumulonimbus

Feb 12, 2026

Solved

Partially reachabilty issues with VS in F5OS tenant

As preparation of our service migration from iSeries to rSeries, we created a test-VS without a pool, but with an iRule responding with a simple static html-website. This works fine so far, but we m...

F5OS

route domain

tenant

Stefan_Klotz
Feb 17, 2026
It seems I could identify and solve the issue.
I added another VS in that partition, but with a real pool, poolmember and monitors. As of now it looks like, that the continuous traffic from the node- and pool-monitor keeps "something" alive, because all VS are always reachable. No interruptions anymore.
Ok, my initial test with just an iRule based VS was maybe not optimal, but nevertheless it would be interesting why this VS is not reacting from outside?
Has someone an explanation for this, especially in combination with the above mentioned conditions?
Thank you!

Regards,
Stefan :)

Stefan_Klotz

Cumulonimbus

Feb 17, 2026

It seems I could identify and solve the issue.
I added another VS in that partition, but with a real pool, poolmember and monitors. As of now it looks like, that the continuous traffic from the node- and pool-monitor keeps "something" alive, because all VS are always reachable. No interruptions anymore.
Ok, my initial test with just an iRule based VS was maybe not optimal, but nevertheless it would be interesting why this VS is not reacting from outside?
Has someone an explanation for this, especially in combination with the above mentioned conditions?
Thank you!

Regards,
Stefan :)