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?
Route Domains HA & Traffic Groups
Running Big-IP 17.5 on a pair of r4600's. On a pair of tenants, we're running a parent-child route domain setup. We're doing this not for IP overlap but for routing purposes. The virtual server addresses are in the default route domain which is the parent route domain. This is basically the "outside" vlan. The HA-Sync vlan is also here. Pool member are in the new child route domain, RD1. This is basically the "inside" vlan. All Self IPs for both route domains are in the same traffic groups (traffic-group-1 & traffic-group-local-only). Questions: HA: If we use the HA-Sync vlan and the self IP for the "inside" vlan, will we have any issue even though they exist in different route domains? Should I move the HA-Sync vlan to RD1? Traffic Groups: Is there an issue with all the self IPs from both route domains being in the same traffic groups? Thanks in advanced.
BIG-IP : determine active device
F5 BIG-IP Virtual Edition v11.4.1 (Build 635.0) LTM on ESXi Via iControl API : How to determine if a specific device is operating in active or standby mode for an active-standby sync-failover device-group ? For a floating traffic-group ? Alternately, for device-group or traffic-group , how to determine active device ?
Persistence records across traffic groups
Hello All, I'm trying to setup an irule that persist on an UIE key across different Virtual Servers. In other words I would like to have traffic on one VS to persist on the basis of persist records created by another VS. It seemed a perfect fit for "Match Across Virtuals". Everything seems to work fine as long as the two VS belongs to the same traffic group, but if I move one of them to a different traffic-group in order to achieve active-active behaviour, it stops working. Now I'm wondering if this was supposed to work in the first place or is to be considered as a bug. Thanks, Andrea
Viprion Network Failover - Multicast
Hi im currently setting up two Viprion chassis at different datacenter with multiple VCMP in HA mode According to the standard each VCMP is advised to have one unicast HA Vlan and one multicast or unicast mesh address By default multicast address communication is over Management physical port So can multicast address be setup on separate physical port rather than management port ?Viprion Traffic Group
Hi We have two viprion chassis at different datacentre in HA. Each chassis is connected to two different switches for redundancy. Each chassis is running three VCMP which is in HA between each other through its respective traffic group we have a separate traffic group for each VCMP HA between two chassis and we are having some issues with traffic group management When one of the redundant link on switch fails, the traffic group failover to the standby before the spanning tree moves the other redundant link on switch from Block to Forward. RSTP takes around 6 sec for this change. only two VCMP is reacting this away, third vcmp's traffic group will not failover during spanning tree calculation VCMP without problem shows below log: HA Connection with peer 192.168.22.2:32768 for traffic-group /Common/traffic-group-1 lost. VCMP with problem shows below log: HA Connection with peer 192.168.22.18:32768 for traffic-group /Common/traffic-group-1 closing. what is the difference between two logs? Is there an confguration to control the traffic group failover timeout to prevent failover before spanning tree re-convergence.
Limit in traffic group in BIG IP LTM
Hi I'm the manager load balancing platform, This platform has 15 traffic group and i need the new application deployment. I will create the new group for internal traffic and external traffic, for Relation with floating self IP and IP. I have a question, Is there any limit on the amount of trafic gruop that can have a Balancer?