Forum Discussion

VFB's avatar
VFB
Icon for Cirrus rankCirrus
Sep 08, 2017

ICMP request failing

I'm running 11.6.1 on a vCMP guest with a IP forwarding server 0.0.0.0/0 as source and destination. Servers behind the LB (10.50.40.x) I cannot ping. I can ping all the way up to the transit VLAN on the F5 but none of the servers behind it. I see outputs like this in my capture:

 

443294 IP 10.194.16.20 > 10.50.40.1: ICMP echo request, id 14832, seq 13, length 64 out slot4/tmm0 lis=/Common/vs_ip_forwarding flowtype=129 flowid=570007FF4100 peerid=570007FF5400 conflags=20EA4 inslot=21 inport=44 haunit=1 priority=3 peerremote=00000000:00000000:0000FFFF:0AC21014 peerlocal=00000000:00000000:0000FFFF:0A322801 remoteport=14832 localport=8 proto=1 vlan=3262 14:34:01.439084 IP 10.194.16.20 > 10.50.40.1: ICMP echo request, id 14832, seq 14, length 64 in slot4/tmm0 lis=/Common/vs_ip_forwarding flowtype=65 flowid=570007FF5400 peerid=570007FF4100 conflags=20EA4 inslot=21 inport=44 haunit=0 priority=3 peerremote=00000000:00000000:0000FFFF:0A322801 peerlocal=00000000:00000000:0000FFFF:0AC21014 remoteport=8 localport=14832 proto=1 vlan=3273 14:34:01.439104 IP 10.194.16.20 > 10.50.40.1: ICMP echo request, id 14832, seq 14, length 64 out slot4/tmm0 lis=/Common/vs_ip_forwarding flowtype=129 flowid=570007FF4100 peerid=570007FF5400 conflags=20EA4 inslot=21 inport=44 haunit=1 priority=3 peerremote=00000000:00000000:0000FFFF:0AC21014 peerlocal=00000000:00000000:0000FFFF:0A322801 remoteport=14832 localport=8 proto=1 vlan=3262

 

5 Replies

  • Do you have a the following configuration on the IP forwarding virtual server?

     

    Service Port = 0 (All Ports)

     

    Protocol = * All Protocols

     

    Protocol Profile (Client) = fastL4

     

  • wlopez's avatar
    wlopez
    Icon for Cirrocumulus rankCirrocumulus

    Do you have a the following configuration on the IP forwarding virtual server?

     

    Service Port = 0 (All Ports)

     

    Protocol = * All Protocols

     

    Protocol Profile (Client) = fastL4

     

  • I failed over to the secondary and it started to work, which leads me to believe that after disabling arp and imp-echo, the primary hung or had a bad process. I enabled imp-echo and disabled arp, rebooted the primary, failed it back to active and it worked consistently.