Layer7 API Management

Expand all | Collapse all

can we know the exact reason of routing failures in Layer 7 ?Is there any way?

Jump to Best Answer
  • 1.  can we know the exact reason of routing failures in Layer 7 ?Is there any way?

    Posted 06-08-2017 09:03 AM

    Hi Team,

    Can we know the exact reason of routing failures in Layer 7 ?Is there any way? 

    how can we find out exact root cause whether it is connection timed out or read timed out 



  • 2.  Re: can we know the exact reason of routing failures in Layer 7 ?Is there any way?
    Best Answer

    Posted 06-08-2017 03:58 PM

    Yes you can!

     

    ${httpRouting.reasonCode}

    Returns one of the following reason codes when the HTTP routing fails:

    • -1 (Host Not Found): The Server referenced in the URL (for example, nonexistentServer.l7tech.com) cannot be reached. This code can be returned if either the host does not exist or the host is simply down.
    • -2 (Bad URL): The URL is incorrect. This could be caused by an incorrect character such as "#".
    • -3 (Connection timeout): An initial message was sent to the URL but no response was received before the connection timeout expired. The connection timeout value is defined in the assertion properties.
    • -4 (Read timeout): One of packets being received from the URL took longer than the read timeout value to be received. The read timeout value is defined in the assertion properties.
    • -5 (Undefined): An unknown type of error has occurred.
    • If successful, will return a valid HTTP Response Code

    Also note that the context variable ${audit.details.last.fullText} will also display the last audit detail, and in the case of policy failures, it will usually show you the audit record of the failure.



  • 3.  Re: can we know the exact reason of routing failures in Layer 7 ?Is there any way?

    Posted 06-09-2017 01:49 AM

    Thank you so much!!



  • 4.  Re: can we know the exact reason of routing failures in Layer 7 ?Is there any way?

    Posted 06-15-2017 01:17 PM

    you can also loop over the audit details to pare the message for event code 4042 to get some more detailed explanation, however these messages change occationally with patches.

     

    Ref: http://layer7admin.blogspot.com/2015/02/route-failure-message-fragment-v2.html