[2.2 TSN use case] BUM traffic re-route takes 90 sec in some scenario
Bug #1479198 reported by
Nobuhiko Nagataki
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Nipa | |||
Trunk |
Fix Committed
|
High
|
Nipa |
Bug Description
In the following multicast tree for BUM forwarding, IP connectivity to vRouter-1 could be lost due to server uplink down and so on.
TOR -- TSN -- vRouter-1 -- vRouter-2
XMPP hold-time is the way to detect vRouter--1 go away in this scenario.
After 90 sec (XMPP hold-time expire), multicast tree is re-calculated.
Until recalculation, BUM forwarding is dropped for VM connected to vRouter-2.
It is desired to reduce 10 sec from 90sec.
information type: | Proprietary → Public |
tags: | added: bms vrouter |
Changed in juniperopenstack: | |
importance: | Undecided → High |
assignee: | nobody → Hari Prasad Killi (haripk) |
tags: | added: customer |
Changed in juniperopenstack: | |
assignee: | Hari Prasad Killi (haripk) → Nipa (nipak) |
tags: | added: releasenote |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/12733
Submitter: Nipa Kumar (<email address hidden>)