Forum Discussion

crosson_16669's avatar
crosson_16669
Icon for Nimbostratus rankNimbostratus
Sep 11, 2012

LB_FAILED. Specific reasons for the failure

Is it possible to see what triggers an LB_FAILED event.

 

 

when LB_FAILED {

 

log0. "LB Failed because of [::ERRORS::XYZ] "

 

}

 

I see nothing in the documentation to support troubleshooting in this way. Is there anything we can use?

 

application delivery
dev
devops
iRules

5 Replies

Sort By
  • hooleylist's avatar
    hooleylist
    Icon for Cirrostratus rankCirrostratus
    Sep 11, 2012
    In 11.0+ you can use [event info]:

     

     

    https://devcentral.f5.com/wiki/iRules.event.ashx

     

    event info

     

     

    Returns a string describing why this event was fired (v11+ only). Added to support LB::queue/LB_QUEUED so limited to LB_FAILED currently, but is anticipated that this will become more generalized in the future.

     

     

    Aaron
  • brad_11480's avatar
    brad_11480
    Icon for Nimbostratus rankNimbostratus
    Apr 01, 2016
    i tried this and nothing came back log local0. "load balance error: [event info]". any ideas?? I had set the member through a 'node 11.22.33.44 443' command. it has worked until today.
  • brad_11480's avatar
    brad_11480
    Icon for Nimbostratus rankNimbostratus
    Apr 01, 2016
    more info.. the message I got was: Load balance FAILED!? node: 52.36.150.63:443 reason: -- for the command in LB_FAILED: log local0. "Load balance FAILED!? node: [LB::server addr]:[LB::server port] reason: -[event info]-" so it has a server and port but still fails.
  • Ernesto_Mayol_2's avatar
    Ernesto_Mayol_2
    Icon for Nimbostratus rankNimbostratus
    Jan 08, 2018

    Any other suggestions on this one? It is very frustrating not being able to determine why the LB_Failed event was raised. event info is not returning anything for me either and I am in version 12.x. What is more, I am printing the status of the selected LB Node on the LB_Failed event and is coming back as up. Any help would be REALLY appreciated.