Forum Discussion
NimbostratusSimple iRule logging problem
Hi, I have created a simple logging rule to monitor pool and node availability, but it doesn't seem to work. Well, the output is not something expected. Here is the iRule:
when HTTP_REQUEST {
log local0. "Pool status [LB::server pool] [LB::status pool [LB::server pool] member 10.10.10.10 8080 ]"
log local0. "Node status [LB::status node 10.10.10.10]" }
But when I look at the logs, they are down:
Wed Oct 29 10:32:48 EET 2014 info slot1/big1 tmm4[12513] Rule /partition1/LOG_TEST : Node status down
Wed Oct 29 10:32:48 EET 2014 info slot1/big1 tmm4[12513] Rule /partition1/LOG_TEST : Pool status /partition1/prod1_8080_pool down
If I looks at the GUI, the pool and node are up an running. What might be the problem here?
Br, Sami
3 Replies
- What type of monitor do you have on the node and pool?
samppa_81183Does it make any difference? First I used custom tcp/8080 monitoring for pool, but I just changed it to custom https/8080 monitoring. In both cases monitoring is successful and the status is green. Node used simple icmp. This is how it looks in tmsh: --------------------------------------------------------------------- Ltm::Pool: /partition1/prod1_8080_pool --------------------------------------------------------------------- Status Availability : available State : enabled Reason : The pool is available Monitor : /partition1/custom_https_monitor Minimum Active Members : 0 Current Active Members : 2 Total Requests : 291 Current Sessions : 0 Traffic ServerSide Bits In 2.5M Bits Out 4.8M Packets In 2.6K Packets Out 1.7K Current Connections 8 Maximum Connections 16 Total Connections 240- samppa_81183
I found out why it didn't work; it was because of the route domain. I need to specify RD also in iRule.
