Forum Discussion

dragonflymr's avatar
dragonflymr
Icon for Cirrostratus rankCirrostratus
May 25, 2017

Monitor not tearing down active connection

Hi,

 

That was a bit of surprise to me. VS with cookie insert persistence and OneConnect profile on v11.2.0HF7

 

Scenario:

 

  • Member is set to port 80 but monitor is monitoring port 81
  • Client has active connection downloading big file
  • During download monitor detects no response from port 81 and marks member down
  • But member port 80 is working so member is sending back responses to BIG-IP
  • Even with member marked down BIG-IP is accepting responses from this member and passing them back to client
  • Only when next request come from client (over the same connection as first one) BIG-IP is making new LB decision and choosing new member, as well as sending new cookie in reply.

Is that expected situation? I was under impression that status set by monitor is more important than actual ability to accept packets by member.

 

Piotr

 

application delivery
cookie persistence
devops
lb reselect
LTM
member down
monitor
oneconnect

2 Replies

Sort By
  • jaikumar_f5's avatar
    jaikumar_f5
    Icon for MVP rankMVP
    May 25, 2017

    This is exactly what I referred in the other Q&A

     

    When your pool member goes down, for your active connections (like Streaming ones, downloading), the persistence will not be cleared out, until the profiles time out value comes. This is where the Action On Service comes into play.

     

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    May 25, 2017

    Piotr, not sure if you've seen this before but check out this link: TCP Traffic Path Diagram - i think this addresses your point, let me know if i've misunderstood. Anyway, connection table entry and persistence, override LB mechanism and, as a consequence, pool member availability.

     

    Hope this answers your question, let me know if not.

     

    N