[NETVIRT-239] Primary NAPT switch role information is not updated to any Stand-by switch when the primary NAPT is rebooted Created: 04/Nov/16  Updated: 19/Oct/17  Resolved: 10/Nov/16

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug
Reporter: Satish Dutt Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 7091

 Description   

EFFECT:
Once a Primary switch is selected for a VRF, if this switch is lost all communication for that VRF (SNAT) is also lost, and there is not updated to any other switch.
For example a VM configured with SNAT in compute-0-5 can not communicate using SNAT if the primary switch compute is lost.
In the tests done primary switch was compute-0-6. While compute-0-6 is being rebooted or lost communication VMs using SNAT in any other compute can not communicate. switch Primary role is not updated to other switch.
Once compute-0-6 is back into service it takes the primery switch role and SNAT communication is restablished.

DESCRIPTION:
When Primary switch in the VRF is lost, the information is not updated to any other switch in the cloud.


Generated at Wed Feb 07 20:21:03 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.