Powershell: Clearing a bad route advertisement rule from NSX-T logical router/gateway created via policy API.

Basically ran into a weird issue where a T1 was not advertising a very specific subnet when configured on segment.  Come to find out when looking at the advanced networking section of that T1, there was a route advertisement rule that denied that subnet from being advertised up.  Since the T1 was created via the policy API, you cannot simply delete it via UI.

Have no idea how that route advertisement rule even got there, but something tells me a bug exists.  Unfortunately have no idea how to reproduce it.
[Update: I have a hypothesis on how it got there now.  When you instantiate a DHCP server via the policy engine, whatever network you place on and attach to a T1 shows up here.  This is likely why the network was here.  What seems to have happened is that deletion of the DHCP server did not happen cleanly and left that artifact there.]

Long story short, you have to call the API to do so.  Here is a powershell snippet to be able to do so.


Popular posts from this blog

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Azure VMware Solution: NSX-T Active/Active T0 Edges...but