Flows getting stuck in Hold state if icmp error received
Bug #1554236 reported by
amit surana
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
Medium
|
Anand H. Krishnan | |||
R2.21.x |
Fix Committed
|
Medium
|
Anand H. Krishnan | |||
R2.22.x |
Fix Committed
|
Medium
|
Anand H. Krishnan | |||
R3.0 |
Fix Committed
|
Medium
|
Anand H. Krishnan | |||
Trunk |
Fix Committed
|
Medium
|
Anand H. Krishnan |
Bug Description
3.0 2723
flows are getting stuck in hold state and all icmp echo requests are dropped. happening every single time.
root@csol2-
108644 2001:db8:
(Gen: 5, K(nh):25, Action:H, Flags:, S(nh):0, Stats:27/4482, SPort 0)
Topology:
VM_Left(
VM_right is pinging a v6 address that is configured on a loopback interface of VM_left (and advertised via BGP to CN; BGPaaS config).
This is a regression; used to work in a couple builds earlier.
summary: |
- IPv6 flows getting stuck in Hold state + Flows getting stuck in Hold state if icmp error received |
description: | updated |
To post a comment you must log in.
H flow seen only when service-vm is unable to route the packets from the right_vm to the left_vm. A default route was configured on the service VM, but it was pointing out the left interface (without a next-hop). As such the service-vm was trying to ARP for the destination out its left interface (even though its not directly connected). Failing to get back an ARP reply, the service-vm was sending back an ICMP destination unreachable error message back to the right_vm, which was causing the connection to go to H state.