Forum Discussion
8 Replies
Sort By
- hooleylistCirrostratusHi Simon,
- tewner_91303NimbostratusIs this still the only way to restart HSL? Has this been changed in V11? It would be a pity to bring everything down (or perform a fail-over) to restart one service....
- nitassEmployeewhat's the issue you are having?
- tewner_91303NimbostratusI restarted our Syslog server, and HSL hasn't logged since. I'm about to go restart TMM.
- nitassEmployeeare you using tcp?
- tewner_91303NimbostratusUDP on 10.2.0
- nitassEmployeei run nc -l -u -p 514 as syslog server.
[root@Edelweiss:Active] config b version|grep -iA 1 version BIG-IP Version 10.2.0 1707.0 Final Edition [root@Edelweiss:Active] config b virtual bar list virtual bar { snat automap pool foo destination 172.28.17.77:http ip protocol tcp rules myrule profiles { http {} tcp {} } } [root@Edelweiss:Active] config b rule myrule list rule myrule { when CLIENT_ACCEPTED { set hsl [HSL::open -proto UDP -pool syslogp] } when HTTP_REQUEST { Log HTTP request as local7.info; see RFC 3164 Section 4.1.1 - "PRI Part" for more info HSL::send $hsl "<190>[clock format [clock seconds] -gmt 8] [IP::local_addr] [HTTP::uri]" } } [root@Edelweiss:Active] config b pool syslogp list pool syslogp { members 192.168.206.96:shell {} }
- HamishCirrocumulusYou might want to update to something later than 10.2.0. I had similar problems with HSL last year... Later is better...
HSL with tcp has it's own set of challenges BTW... I had to do a 'bigstart restart tmm' quite a few times when stress testing. That's the only way to get it to work again IIRC...