Forum Discussion
We have an LB that has 4 members, and the requests for the ip member 10.58.42.39
Team F5, We have an LB that has 4 members, and the requests for the ip member 10.58.42.39 have no return to port 8443.
RD1_VIP_AMG_PXRX_8443 RD1_POOL_AMG_PXRX_HTTPS 10.58.42.38%1:8443 10.58.42.39%1:8443 <- 10.58.42.40%1:8443 10.58.42.41%1:8443
For testing we went up on the same server ip 10.58.42.45 on the destination server (which is listening on all ports) and worked without problems.
For some reason for the given ip the package of LB instead of sending to the correct mac, it sends to a broadcast, even it putting in the arp table of the equipment:
(DFSIGD-CLB18B)(cfg-sync Changes Pending)(/S1-green-P:Active)(/Common)(tmos) show net arp
Net::Arp
Name Address HWaddress Vlan Expire-in-sec Status
10.58.42.38%1 10.58.42.38%1 00:50:56:86:6b:f3 /Common/Front-End_CLB18_API_Manage-T266 58 resolved 10.58.42.39%1 10.58.42.39%1 00:50:56:86:6d:d9 /Common/Front-End_CLB18_API_Manage-T266 10 <- resolved 10.58.42.40%1 10.58.42.40%1 00:50:56:86:3c:fa /Common/Front-End_CLB18_API_Manage-T266 278 resolved 10.58.42.41%1 10.58.42.41%1 00:50:56:86:bd:57 /Common/Front-End_CLB18_API_Manage-T266 187 resolved 10.58.42.42%1 10.58.42.42%1 00:50:56:86:da:81 /Common/Front-End_CLB18_API_Manage-T266 198 resolved 10.58.42.45%1 10.58.42.45%1 00:50:56:86:6d:d9 /Common/Front-End_CLB18_API_Manage-T266 216 <- resolved
- Leonardo_SouzaCirrocumulus
Can you explain better the problem? Is the traffic going to the pool member but not returning?
Can you run these commands (replace the <> with the correct information)?
tmsh list ltm pool tmsh list net self tmsh list net route tmsh list list net route-domain tmsh list net vlan
- Stanislas_Piro2Cumulonimbus
In your wire shark screenshot, there is an issue..
The MAC address is broadcast!!!
I guess there is an issue with the net mask configured on the f5 and 10.58.42.39 is detected as broadcast address!
- Stanislas_Piro2Cumulonimbus
Here is the question with well formatted data, when I first read the question, I missed lots of information because most of them were unreadable!
Team F5, We have an LB that has 4 members, and the requests for the ip member 10.58.42.39 have no return to port 8443.
-
RD1_VIP_AMG_PXRX_8443
-
RD1_POOL_AMG_PXRX_HTTPS
- 10.58.42.38%1:8443
- 10.58.42.39%1:8443 <-
- 10.58.42.40%1:8443
- 10.58.42.41%1:8443
-
RD1_POOL_AMG_PXRX_HTTPS
For testing we went up on the same server ip 10.58.42.45 on the destination server (which is listening on all ports) and worked without problems.
For some reason for the given ip the package of LB instead of sending to the correct mac, it sends to a broadcast, even it putting in the arp table of the equipment:
(DFSIGD-CLB18B)(cfg-sync Changes Pending)(/S1-green-P:Active)(/Common)(tmos) show net arp ------------------------------------------------------------------------------------------------- Net::Arp Name Address HWaddress Vlan Expire-in-sec Status ------------------------------------------------------------------------------------------------- 10.58.42.38%1 10.58.42.38%1 00:50:56:86:6b:f3 /Common/Front-End_CLB18_API_Manage-T266 58 resolved 10.58.42.39%1 10.58.42.39%1 00:50:56:86:6d:d9 /Common/Front-End_CLB18_API_Manage-T266 10 <- resolved 10.58.42.40%1 10.58.42.40%1 00:50:56:86:3c:fa /Common/Front-End_CLB18_API_Manage-T266 278 resolved 10.58.42.41%1 10.58.42.41%1 00:50:56:86:bd:57 /Common/Front-End_CLB18_API_Manage-T266 187 resolved 10.58.42.42%1 10.58.42.42%1 00:50:56:86:da:81 /Common/Front-End_CLB18_API_Manage-T266 198 resolved 10.58.42.45%1 10.58.42.45%1 00:50:56:86:6d:d9 /Common/Front-End_CLB18_API_Manage-T266 216 <- resolved
-
RD1_VIP_AMG_PXRX_8443
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com