MGMT interface in routing domain?
Hi, I have 2x BIG-IP LTM and DNS (GTM) and I need to install them inside customer tenant in cloud environment. Problem is that I need to have MGMT in separate routing domain because of IP overlapping. I cannot isolate data interfaces to routing domain because I'm using GTM and (as far as I know) GTM listener cannot be part of routing domain. Can I somehow move MGMT interface in routing domain? Second solution could be to dedicate some Self IP in non-default routing domain for MGMT, but in that case what with NTP service (can I use it), what with device sync (i will use device-group for config sync and failover) etc... Software version is 12.1.1 Br, Mate
Ephemeral nodes goes in wrong partition
Hello everyone, I'm trying to create a pool with auto-populated nodes. These pools & nodes are in dedicated partitions, that have its own routing domain. The problem is that epheremal nodes are created in Common partitions, which contains no routes to realize monitoring checks, so my pool go red and become unusable. Is there a way to create ephemeral nodes in the same partition than nodes they belong to ? v12.1.3.6
Floating IP responds from wrong VLAN/trunk
I have a routing issue I can't seem to figure out the cause of. I have two trunks defined, T1 on 1.1 and 1.2, and T2 on 1.3 and 1.4. Both trunks are connected to the same switch (on the same VLAN on the switch). I have two VLANs tied to the respective trunks, V1 on T1 and V2 on T2. I have two traffic groups, TG1 and TG2, with masquerade MACs. I have two routing domains, 0 and 255. I have local self IPs defined on the respective VLANs, say 10.0.0.3 on V1 and 10.0.255.3%255 on V2. I have floating self IPs, such as 10.0.0.2 on V1 and TG1, and 10.0.255.2%255 on V2 and TG2. When I ping 10.0.0.3 and 10.0.255.3 I get proper responses. No problems there. When I ping 10.0.0.2 I proper responses. When I ARP 10.0.255.2, it resolves to the MAC of TG2 and the switch it's connected to routes that MAC to T2. However, when I ping 10.0.255.2 only the first response comes back - but it comes back from T1 and with the MAC of TG1. When the second (and further) ping is sent, it's consequently (due to MAC learning) sent to T1 - which is not accepting it. Why is the ping response sent back from T1 when the request was sent to T2? Why is the floating IP in V2, TG2 and routing domain 255 not responding from the same interface as it receives the ICMP package on?