Forum Discussion
CumulonimbusPartially reachabilty issues with VS in F5OS tenant
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 :)
CumulonimbusThe thing is, that I see packets correctly with tcpdump within the tenant, the moment, where the VS is working. And I just see them on F5OS-level, the moment, where it is not working. I'm trying to reach the VS (via browser or ping) from outside the LB. At the time when the issue occurs, I can ping the VS from within the LB/tenant.
In the meantime, I've created a normal VS including a pool and poolmember in a second partition/route domain, but on the same tenant, and here I don't see any disruptions so far. I also created such a iRule-based VS with the same static website and also for this I can't replicate the issue.
So I'm still wondering, if I made maybe any small mistake in the other partition/route domain (any maybe in others as well), which would then have any negative impact during/after migration of services onto the new platform.
That's why I want to verify where this behavior comes from, meaning some kind of "normal" behavior or some corrupt configuration.
Thank you!
Regards,
Stefan :)
