icmp monitor
2 TopicsFQDN 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? Piotr500Views0likes2CommentsMonitoring backend servers externally via ICMP
I have a simple setup in a test environment v13.1.1.2, with a virtual server and an associated pool with one member: ltm node /Common/10.1.20.11 { address 10.1.20.11 } ltm pool /Common/pool_http { members { /Common/10.1.20.11:80 { address 10.1.20.11 } } } ltm virtual /Common/http_virtual { destination /Common/10.1.10.20:80 ip-protocol tcp mask 255.255.255.255 pool /Common/pool_http profiles { /Common/http { } /Common/profile_analytics { } /Common/tcp { } } source 0.0.0.0/0 translate-address enabled translate-port enabled } I would like ICMP packets sent from my machine 10.1.10.1 to the virtual IP 10.1.10.20 to be forwarded to the backend server 10.1.20.11, and I would like to receive the replies. If I look at the VIP configuration (Local Traffic ›› Virtual Servers : Virtual Address List ›› 10.1.10.20) I can see the "ICMP echo" configuration option, and the help section suggests the following: "Specifies how the system sends responses to Internet Control Message Protocol (ICMP) echo requests on a per-virtual address basis. When enabled, the BIG-IP system intercepts ICMP echo request packets and responds to them directly. When disabled, the BIG-IP system passes ICMP echo requests through to the backend servers." This does not happen (as verified with tcpdump), and if I understand K16885 correctly, then the instructions above are actually incorrect as the article says: "To prevent the BIG-IP system from responding to ICMP echo packets, you must disable ICMP Echo at the virtual address level." So what method would you recommend to achieve my goal?275Views0likes1Comment