Yes you can leverage API calls during Failover Activity. Ideally below mentioned points are mainly considered
- Promote NSX manager
- Redeploy Universal Controller Cluster
- Update the controller state
- Redeploy DLR
Based on the design you might need firewall/route changes which can also be pushed via API calls .Please refer to below Cross -VC guide to understand overall design approach . Once you are clear with design scenarios , please refer to API guide and understand how to fetch NSX manager/Controller status etc to start of with . Those are pretty much GET calls and later you can move on to PUT/PUSH operations for each activity . For eg GET /api/2.0/universalsync/configuration/nsxmanagers on a primary NSX Manager will list secondary NSX Managers configured on the primary NSX Manager and same operation on a secondary NSX Manager, it will list information about the secondary NSX Manager and the primary NSX Manager it is associated with.
Thank you We are actually are in an active-active local egress setup. So for a failover we only need to.
Unlink secondary from primary
promote the now transit to primary
deploy new controller cluster
Goimg to both sites a bit more work.
I need to research more. It sounds doable!