 Written by Sam McGeown
on 23/5/2019
Written by Sam McGeown
on 23/5/2019 I ran into this UI bug the other day when I was trying to enable route redistribution on an Edge in a Secondary site of a cross-vCenter NSX deployment.
The Edge itself was deployed correctly, and configured to peer with a physical northbound router, however when I attempted to configure the route redistribution I was unable to do so.
Fortunately, the solution was simple - use the API.
Perform a GET operation to retrieve the current BGP configuration 1 GET https://{{nsxmanager}}/api/4.
I ran into this UI bug the other day when I was trying to enable route redistribution on an Edge in a Secondary site of a cross-vCenter NSX deployment.
The Edge itself was deployed correctly, and configured to peer with a physical northbound router, however when I attempted to configure the route redistribution I was unable to do so.
Fortunately, the solution was simple - use the API.
Perform a GET operation to retrieve the current BGP configuration 1 GET https://{{nsxmanager}}/api/4. Written by Sam McGeown
on 22/1/2015
Written by Sam McGeown
on 22/1/2015