Forum Discussion

The-messenger's avatar
The-messenger
Icon for Cirrostratus rankCirrostratus
Jun 18, 2020

HTTP Connections Dropped after moving 14.1.2

I've seen this question before but no answers. After moving to 14.1.2 LTM logs are filled with these errors"

Jun 16 15:02:20 dc1-ltm-01 err tmm[18694]: 011f0007:3: http_process_state_cx_wait - Invalid action:0x100011 clientside (CLIENT-IP -> VIRUTALSERVER-IP:443) ((null connflow)) (Client side: vip=VIRTUALSERVER-NAME profile=http pool=POOL-NAME client_ip=CLIENT-ip)

 

The client might see Unknown error or Connection reset.

 

I think a change in 14.1.2 with an iRule that has specific coding is the cause but one of the Virtual servers affected for me is Exchange, where I'm using the Exchange2016 iapp, there are several iRules that the iapp creates.

I have a case on this but no help so far.

14.1.2
application delivery
iRules
LTM
    • The-messenger's avatar
      The-messenger
      Icon for Cirrostratus rankCirrostratus
      Jun 18, 2020

      Thanks for the response. Looking at the Exchange 2016 iapp, there is an irule with HTTP::redirect but it is the last action in the irule. Here's the irule.

      priority 900
when HTTP_REQUEST {
    if { ([HTTP::uri] == "/") } {
        HTTP::redirect https://[HTTP::host]/owa/
    }
}

      I would expect F5 to update the Exchange iapp, if it were not compatible with 14.1.2, from the information in this support article it doesn't appear that there is a problem.

  • Lidev's avatar
    Lidev
    Icon for Nacreous rankNacreous
    Jun 18, 2020

    Indeed, there is no problem if you choose to apply the workaround it might be works again.

    • The-messenger's avatar
      The-messenger
      Icon for Cirrostratus rankCirrostratus
      Jun 18, 2020

      I don't think this iRule is a problem, is it?

      The document offered states:

      HTTP iRule commands that inspect HTTP state after the commands HTTP::respond, HTTP::redirect and HTTP::retry will now return errors instead of returning corrupt data.

      one example workaround is to move the HTTP::redirect to the last action in the irule.

       

      It's already the last action in this iRule. I don't think this iRule is an example of a problem.

      • Lidev's avatar
        Lidev
        Icon for Nacreous rankNacreous
        Jun 18, 2020

        Sorry i read your previous anwser too fast. if the redirect is the last action, you right this iRule is not the issue.