Juniper Openstack

[R2.20.37] TSN HA: After TSN switch over it is taking long time for QFX to get programmed with TSN IP

Bug #1461875 reported by chhandak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.20
Fix Committed
Medium
Unassigned
Juniper Openstack r2.20-fcs
Trunk
Fix Committed
Medium
Unassigned
Juniper Openstack r3.0-fcs

Bug Description

After switching over for TSN HA, QFX has to get programmed with new TSN IP for each logical switch. It is taking very long time for the QFX to get programmed with all the entry for 8K VN.

Till then all the entry is stuck in Sync wait state in OVSDB Introspect.

Sync wait(5)
001611fe-fa13-4029-915c-4f2d23d350b9
bng-contrail-qfx51-2

Observed 5 sec of delay between in each transaction in QFX. Here we have total 8K VN in setup.

TCPDUMP
----------------
17:42:03.342745 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 3857810505:3857810947(442) ack 1931335165 win 33304 <nop,nop,timestamp 5758480 36496981>
17:42:03.353712 In IP 192.168.22.210.4321 > 192.168.22.253.49295: P 1:406(405) ack 442 win 1781 <nop,nop,timestamp 36498242 5758480>
17:42:03.354312 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 442:916(474) ack 406 win 33304 <nop,nop,timestamp 5758491 36498242>
17:42:03.354466 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 916:1038(122) ack 406 win 33304 <nop,nop,timestamp 5758491 36498242>
17:42:03.365670 In IP 192.168.22.210.4321 > 192.168.22.253.49295: . ack 1038 win 1781 <nop,nop,timestamp 36498244 5758491>
17:42:08.395698 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 1038:1480(442) ack 406 win 33304 <nop,nop,timestamp 5763481 36498244>
17:42:08.406965 In IP 192.168.22.210.4321 > 192.168.22.253.49295: P 406:811(405) ack 1480 win 1781 <nop,nop,timestamp 36499505 5763481>
17:42:08.409959 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 1480:1954(474) ack 811 win 33304 <nop,nop,timestamp 5763495 36499505>
17:42:08.410474 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 1954:2076(122) ack 811 win 33304 <nop,nop,timestamp 5763495 36499505>
17:42:08.422898 In IP 192.168.22.210.4321 > 192.168.22.253.49295: . ack 2076 win 1781 <nop,nop,timestamp 36499509 5763495>
17:42:08.422947 In IP 192.168.22.210.4321 > 192.168.22.253.49295: P 811:1216(405) ack 2076 win 1781 <nop,nop,timestamp 36499509 5763495>
17:42:08.425291 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 2076:2550(474) ack 1216 win 33304 <nop,nop,timestamp 5763510 36499509>
17:42:08.425508 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 2550:2672(122) ack 1216 win 33304 <nop,nop,timestamp 5763510 36499509>
17:42:08.437270 In IP 192.168.22.210.4321 > 192.168.22.253.49295: . ack 2672 win 1781 <nop,nop,timestamp 36499512 5763510>
17:42:13.396668 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 2672:3114(442) ack 1216 win 33304 <nop,nop,timestamp 5768430 36499512>
17:42:13.407609 In IP 192.168.22.210.4321 > 192.168.22.253.49295: P 1216:1621(405) ack 3114 win 1781 <nop,nop,timestamp 36500755 5768430>
17:42:13.408170 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 3114:3588(474) ack 1621 win 33304 <nop,nop,timestamp 5768441 36500755>
17:42:13.408371 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 3588:3710(122) ack 1621 win 33304 <nop,nop,timestamp 5768441 36500755>
17:42:13.419598 In IP 192.168.22.210.4321 > 192.168.22.253.49295: . ack 3710 win 1781 <nop,nop,timestamp 36500758 5768441>
17:42:18.449626 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 3710:4152(442) ack 1621 win 33304 <nop,nop,timestamp 5773431 36500758>
17:42:18.460650 In IP 192.168.22.210.4321 > 192.168.22.253.49295: P 1621:2026(405) ack 4152 win 1781 <nop,nop,timestamp 36502018 5773431>
17:42:18.461837 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 4152:4626(474) ack 2026 win 33304 <nop,nop,timestamp 5773443 36502018>
17:42:18.464518 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 4626:4748(122) ack 2026 win 33304 <nop,nop,timestamp 5773446 36502018>
17:42:18.479234 In IP 192.168.22.210.4321 > 192.168.22.253.49295: . ack 4748 win 1781 <nop,nop,timestamp 36502025 5773443>
17:42:18.479272 In IP 192.168.22.210.4321 > 192.168.22.253.49295: P 2026:2431(405) ack 4748 win 1781 <nop,nop,timestamp 36502025 5773443>
17:42:18.480028 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 4748:5222(474) ack 2431 win 33304 <nop,nop,timestamp 5773461 36502025>
17:42:18.480223 Out IP 192.168.22.253.49295 > 192.168.22.210.4321: P 5222:5344(122) ack 2431 win 33304 <nop,nop,timestamp 5773461 36502025>
17:42:18.490795 In IP 192.168.22.210.4321 > 192.168.22.253.49295: . ack 5344 win 1781 <nop,nop,timestamp 36502026 5773461>

Tags: bms qfx vrouter
chhandak (chhandak)
tags: added: bms qfx vrouter
Changed in juniperopenstack:
assignee: brett (bms) → nobody
Revision history for this message
chhandak (chhandak) wrote :

Logs saved at http://mayamruga.englab.juniper.net/bugs/1461875

Nagabhushana R (bhushana)
Changed in juniperopenstack:
importance: Undecided → High
importance: High → Critical
Ashish Ranjan (aranjan-n)
information type: Proprietary → Public
Revision history for this message
chhandak (chhandak) wrote :

We haven't seen the problem in recent build.
There is one fix from contrail side which does the ovsdb transaction in
bulk. After this fix got introduced we haven't hit the problem.
Without that fix we have reproduced the problem to Sudarsan once.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.