GTM iRule and log local0. crashing BIG-IP
Hi, I have iRule like that attached to Wide IP: when DNS_REQUEST { check where LDNS is, if below true it is in DR1 if { [active_members location_pl] < 1 } { log local0. "Active members in \"location_pl\" - [active_members location_pl]" check if there are any active members in DR1 pool/location if { [active_members dr_a_pl] > 0 } { pool dr_a_pl log local0. "Active members in \"dr_a_pl\" - [active_members dr_a_pl], selected pool [LB::server pool]" log local0. "Switching to DR1" } else { Use DC1 pool pool dc_a_pl } } } When executed it is immediately crashing my BIG-IP VE v13.0.0HF2 - failover etc. When all log local0. is changed to log local2. everything works OK. From GTM command reference for log command it seems that there should be no problem using ltm log instead of gtm - am I wrong or it's kind of bug? PiotrGTM and Topology? Possible without iRule?
Hi, I wonder if such scenario is possible to achieve without creating GTM iRule: Host asking for FQDN to connect to bunch of servers. This host can be in DC1 or DR1 depending on diiferent factors, it's migrated using VMware HA. It keeps same IP, number of hops is the same etc. - so no obvious way to figure out in which DC host actually is. It will probably be fixed by creating some external monitor - not important now. If host is in given DC it should receive IPs only of target servers in this DC If there is no active server left in this DC, but there are active in other DC then IPs from other DC should be returned. I have no idea right now how to achieve it using just configuration objects without iRule - any ideas welcome here. I can't use Topology on Wide IP level, as there is no change that can be detected - same IP for DNS requests. If Global Availability will be used then it should dynamically change order based on DC in which host is running at the given time. So... Piotr