Health Monitor being sourced from Management interface causing async routing
I have a health monitor that is being sourced from the management interface - this was discovered by accident when i was doing a TCPDUMP on the vlan interface the traffic should have been sourced from. example vlan 10 interface on f5 10.0.0.1 destination ip address of device being monitored = 10.0.0.6 when i did a tcpdump on the vlan to troubleshoot a separate problem i didnt see the traffic - i could see other health monitor traffic using the vlan for devices on the subnet and i know the routing and connectivity is working fine. Wondering what reason there would be for the health monitor not to use the vlan associated with the subne t and use the management ip address to source the health traffic. FYI the health monitor is working and responding as expected but would just like the traffic to use the correct path - via the connected vlan instead of sending around the world and through various firewalls to reach its destination (lucky the firewalls are permitting the traffic. Thanks
Something wierd with mac address' that I cant explain on my i2600 Series F5 LTM HA
We have 2 F5 LTM i2600 series physical devices running v13.1.3.2.We have 4 X 1G interfaces and 2 X 10GBFiber interfaces.One of the 1GB interfaces is patched and is used for the Management IP.Both 10GBFiber interfaces are patched and used for our Internal and External vlan. The weird thing I cant explain is why my Internal & External Vlans are using the mac address of 2 of the 1GB ports that are not patched, respectively. FYI..These F5s have been in use for 18 months without issues. I attached a screenshot. The only reason I noticed this is because we were adding a VPN in our environment and were tracing the traffic from the F5 during troubleshooting.The networking team was seeing a mac address that I told them couldn't be because the port was not patched.When I started looking deeper, I found that they were right. So my question is why is the F5 using a mac address belonging to a disconnected Interface for another connected interface that has its own mac address? Can anyone explain this behavior.
