F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

DWiggins_116310's avatar
DWiggins_116310
Icon for Nimbostratus rankNimbostratus
Dec 09, 2013

Trouble with a remote logging iRule

So this should be a very simple iRule but I'm stumped. The purpose of this iRule was to log on a remote syslog server the external IP of any clients that connect to a specific Virtual Server. I've reviewed a number of other threads and I look to have the rule right but when its enabled on a VS it the site just goes to a connection reset error message.

 

when CLIENT_ACCEPTED {

 

log 10.33.116.27:5514 local0.info "Client Connected, IP: [IP::client_addr] to XXXXX"

 

}

 

Thanks for any thoughts you can provide.

 

3 Replies

  • Richard__Harlan's avatar
    Richard__Harlan
    Historic F5 Account
    Dec 09, 2013

    a better way to do this is the following

    when CLIENT_ACCEPTED {
    set hsl [HSL::open -proto UDP -pool ]
     HSL::send $hsl "Client Connected, IP: [IP::client_addr] to XXXXX"
}
    • DWiggins_116310's avatar
      DWiggins_116310
      Icon for Nimbostratus rankNimbostratus
      Dec 09, 2013
      I gave this a chance since the other option I had was less desirable. I setup the HSL options and pool and then added this iRule. I show logs of the F5 of the rule being successfully applied. That said I'm not seeing anything new coming into the syslog server. I'll poke at it for a little while and see if I can get it to work. As a side note, this site won't be accessed on a huge scale so in-line processing to a remote log server is completely acceptable. If I can get the syntax right would also work.
    • Richard__Harlan's avatar
      Richard__Harlan
      Historic F5 Account
      Dec 09, 2013
      If you want true remote syslog then follow this http://support.f5.com/kb/en-us/solutions/public/13000/000/sol13080.html