transitvpc:preferred-path tag change/add without VPN add/deletion doesn't trigger cisco config change

[arielwq]

Add transitvpc:preferred-path key with value of CSR1 or CSR2 doesn't trigger any route-map config changes. Upon reading of the transit-vpc-poller config, it seems that updateConfigXML() method is only called during VPN creation and deletion. It would be good to have another condition to match cisco config with the transitvpc:preferred-path key value and update the xml config in the related s3 bucket to trigger necessary cisco route-map config changes.

[LucasSymons]

+1 for this, we had this same issue after we enabled zone based firewall on the CSR's and had to resolve asymmetrical routing. Was a huge pain to roll back and then rebuild all the tunnels as a lot of the VPC's are in 3rd party accounts.

[philipakash]

+1

[accessdenied12]

+1

[hvital]

Thanks for sharing your feedback. This was included to the solution roadmap and we'll post an update to this thread once we have more information.