Comment 1 for bug 1715510

Revision history for this message
chhandak (chhandak) wrote : Re: [Bug 1715510] Re: EVPN VXLAN: Ping to DNS server IP is failing after first packet

Hi Hari,

I have reproduced the issue. Please find the setup details below

Password (root/c0ntrail123)
Controller + TSN 10.87.69.1
TSN2 10.87.69.4
Agent 10.87.69.2
BMS 10.87.69.3 (Interface p2p1.6)

QFX:10.87.69.124 (root/Embe1mpls)

root@5b11s16:~# ping -I p2p1.6 17.17.17.2
PING 17.17.17.2 (17.17.17.2) from 17.17.17.3 p2p1.6: 56(84) bytes of data.
64 bytes from 17.17.17.2: icmp_seq=1 ttl=64 time=0.662 ms
^C
--- 17.17.17.2 ping statistics ---
4 packets transmitted, 1 received, 75% packet loss, time 3015ms
rtt min/avg/max/mdev = 0.662/0.662/0.662/0.000 ms

Thanks and Regards,
Chhandak

On 9/6/17, 6:44 PM, "<email address hidden> on behalf of Jeba Paulaiyan" <<email address hidden> on behalf of <email address hidden>> wrote:

>** Also affects: juniperopenstack/r4.0
> Importance: Undecided
> Status: New
>
>** Also affects: juniperopenstack/trunk
> Importance: High
> Assignee: Hari Prasad Killi (haripk)
> Status: New
>
>** Changed in: juniperopenstack/r4.0
> Importance: Undecided => High
>
>** Changed in: juniperopenstack/r4.0
> Assignee: (unassigned) => Hari Prasad Killi (haripk)
>
>** Changed in: juniperopenstack/r4.0
> Milestone: None => r4.0.1.0
>
>** Changed in: juniperopenstack/trunk
> Milestone: r4.0.1.0 => r4.1.0.0-fcs
>
>--
>You received this bug notification because you are a member of Contrail
>Systems engineering, which is subscribed to Juniper Openstack.
>https://bugs.launchpad.net/bugs/1715510
>
>Title:
> EVPN VXLAN: Ping to DNS server IP is failing after first packet
>
>Status in Juniper Openstack:
> New
>Status in Juniper Openstack r4.0 series:
> New
>Status in Juniper Openstack trunk series:
> New
>
>Bug description:
> Trying with EVPN VXLAN changes for TSN HA (Agent and vrouter updated)
>
> When pinging from BMS to DNS server IP, ping is failing after the
> first packet. In dropstats Flow Queue Limit Exceeded counter is
> increasing. FLow is stuck in Hold state.
>
> root@5b11s16:~#
> root@5b11s16:~# ping -I p2p1.6 1.1.1.2
> PING 1.1.1.2 (1.1.1.2) from 1.1.1.3 p2p1.6: 56(84) bytes of data.
> 64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=0.488 ms
> ^C
> --- 1.1.1.2 ping statistics ---
> 4 packets transmitted, 1 received, 75% packet loss, time 3015ms
> rtt min/avg/max/mdev = 0.488/0.488/0.488/0.000 ms
>
>
> root@5b11s14:~# dropstats | grep -v " 0$"
>
> Flow Queue Limit Exceeded 454
>
>
> Discards 687
> Cloned Original 1374
>
> Invalid NH 9
>
>
> root@5b11s14:~# dropstats | grep -v " 0$"
>
> Flow Queue Limit Exceeded 464
>
>
> Discards 695
> Cloned Original 1390
>
> Invalid NH 9
>
> root@5b11s14:~# flow -l
> Flow table(size 80609280, entries 629760)
>
> Entries: Created 4 Added 0 Deleted 3 Changed 3 Processed 3 Used Overflow entries 0
> (Created Flows/CPU: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0)(oflows 0)
>
> Action:F=Forward, D=Drop N=NAT(S=SNAT, D=DNAT, Ps=SPAT, Pd=DPAT, L=Link Local Port)
> Other:K(nh)=Key_Nexthop, S(nh)=RPF_Nexthop
> Flags:E=Evicted, Ec=Evict Candidate, N=New Flow, M=Modified Dm=Delete Marked
> TCP(r=reverse):S=SYN, F=FIN, R=RST, C=HalfClose, E=Established, D=Dead
>
> Index Source:Port/Destination:Port Proto(V)
> -----------------------------------------------------------------------------------
> 226064 1.1.1.3:5610 1 (3)
> 1.1.1.2:0
> (Gen: 4, K(nh):0, Action:H, Flags:, QOS:-1, S(nh):0, Stats:81/6804, SPort 0,
> TTL 0, Sinfo 172.16.2.1)
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/juniperopenstack/+bug/1715510/+subscriptions