Forum Discussion

Stefan_Klotz's avatar
Stefan_Klotz
Icon for Cumulonimbus rankCumulonimbus
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's avatar
    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 :)

lnxgeek's avatar
lnxgeek
Icon for MVP rankMVP
Feb 14, 2026

Hi Stefan

From where do you test the connectivity?

I have seen scenarios where the tcpdump didn't "work" in the tenant (aka no packages caught) but the VS working just fine.

From what you are describing you are doing nothing wrong, all seems to be by the book and the software versions you are using should have fixed weird vlan problems.

What I would do is setup a proper VS configuration with pool members, that way you are making a better test and the traffic will move through the device the way it is designed.