Piotr_Lewandows
Jun 05, 2017Altostratus
FQDN node and icmp monitor
Hi,
I am just playing around with creating FQDN based nodes (v13.0.0HF2). I wonder what this error message means after standard icmp monitor is assigned to parent (non ephemeral) node:
Jun 5 10:31:52 bigiptest err bigd[13757]: 01060114:3: Cannot schedule :53 interval 0 timeout 1.
It's followed by this entries (and in GUI ephemeral nodes are marked with green dot)
Jun 5 10:31:53 bigiptest notice bigd[13757]: 01060143:5: Node /Common/lamp4-20_nd-10.1.20.14 address 10.1.20.14 session status enabled by monitor
Jun 5 10:31:53 bigiptest notice bigd[13757]: 01060141:5: Node /Common/lamp4-20_nd-10.1.20.14 monitor status up [ /Common/icmp: UP ] [ was checking for 0hr:7mins:12sec ]
Jun 5 10:31:53 bigiptest notice bigd[13757]: 01060143:5: Node /Common/lamp4-20_nd-10.1.20.16 address 10.1.20.16 session status enabled by monitor
Jun 5 10:31:53 bigiptest notice bigd[13757]: 01060141:5: Node /Common/lamp4-20_nd-10.1.20.16 monitor status up [ /Common/icmp: UP ] [ was checking for 0hr:2mins:7sec ]
Using standard icmp configuration:
ltm monitor icmp icmp {
adaptive disabled
interval 5
time-until-up 0
timeout 16
}
and interwal for querying DNS set to 60s - so much higher than interval and timeout in monitor
fqdn {
address-family ipv4
autopopulate enabled
down-interval 5
interval 60
name lamp4-20.test.com
}
Is my config somehow broken? Should icmp monitor setting be set to higher timeout than fqdn interval?
Piotr