Forum Discussion
Hannes_Rapp
May 24, 2016Nimbostratus
A few questions, I'm trying to narrow the search area.
Can you confirm your issue is that as you're trying to ping the Floating-SelfIP (172.19.68.5) from one of the VMs in same network, there's no response? If yes, have you tried using tcpdump on BigIP yet - do you see ICMP echo requests coming in, and if not, do you see any ARP who-is requests? Is the situation any better with the Local-SelfIP (172.19.68.4) - does it respond to ICMP as intended?
- Grayson_149410May 24, 2016NimbostratusNeither the Self IP (.4) nor the Float IP (.5) are able to be pinged from those VMs. I am seeing on another server on the same VLAN sending requests to the LTM and I see this: 13:56:40.754585 ARP, Request who-has 172.19.68.20 tell 172.19.68.4,
- Grayson_149410May 24, 2016NimbostratusAlso to add, I just ran a capture and I am seeing ARP requests for both the Self and Float: 14:02:54.822595 ARP, Request who-has 172.19.68.4 tell 172.19.68.32, length 130 in slot1/tmm0 lis= flowtype=0 flowid=0 peerid=0 conflags=0 inslot=63 inport=55 haunit=0 priority=0 peerremote=00000000:00000000:00000000:00000000 peerlocal=00000000:00000000:00000000:00000000 remoteport=0 localport=0 proto=0 vlan=0 14:02:55.782239 ARP, Request who-has 172.19.68.5 tell 172.19.68.32, length 130 in slot1/tmm0 lis= flowtype=0 flowid=0 peerid=0 conflags=0 inslot=63 inport=55 haunit=0 priority=0 peerremote=00000000:00000000:00000000:00000000 peerlocal=00000000:00000000:00000000:00000000 remoteport=0 localport=0 proto=0 vlan=0
- Hannes_RappMay 24, 2016NimbostratusIt could be a VLAN tag-mismatch problem. What happens if you temporarily set Prod_HC_Web VLAN as "untagged" on 1.3 tmm interface? Does it change anything ?