MinoDC
Enthusiast
Enthusiast

Add Standalone NSX-v as Secondary

Jump to solution

Hi to all.

I've this infrastructure:

1 VCSA 6.5 U3 with NSX 6.4.4 in standalone mode in SiteA

1 VCSA 6.5 U3 with NSX 6.4.4 in standalone mode in SiteB

Each NSX has its own configuration (Edge-DLR-LB-Firewall Rule and other)

Now we should convert this configuration in a single NSX multi-site configuration.

I thinked run this task :

  1. In SiteB remove all NSX Controller
  2. In SiteA change NSX from Standalone to Primary
  3. On  New Primary NSX in SiteA , add Secondary NSX Manager and select NSX in SiteB
  4. Add NSX Universal Controller in SiteA
  5. Create/Configure Universal Parameter/Object ( Segment-ID ; Transport Zone; DLR ...)

The my doubts/questions are:

  • When i remove all NSX Controller in SiteB, the network traffic In/Out and Inside NSX continue to work or will I have to provide a maintenance window?
  • After adding NSX in SiteB as Secondary, will the "Global" objects (Edge-DLR-LB-Firewall Rule and other) still works in SiteB , or do i need to take actions before adding NSX as secondary manager ?

Thanks a lot to all for suggestions on this task...

1 Solution

Accepted Solutions
RShankar22
VMware Employee
VMware Employee
  • When i remove all NSX Controller in SiteB, the network traffic In/Out and Inside NSX continue to work or will I have to provide a maintenance window?
      • Ideally there is no impact to traffic even when your controller cluster is DOWN/Unavailable. As you are deleting the controller and creating Universal controller, better to take a DOWNTIME.
  • After adding NSX in SiteB as Secondary, will the "Global" objects (Edge-DLR-LB-Firewall Rule and other) still works in SiteB , or do i need to take actions before adding NSX as secondary manager ?
      • Local Objects has no relation with Universal Objects.

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

View solution in original post

0 Kudos
5 Replies
RShankar22
VMware Employee
VMware Employee
  • When i remove all NSX Controller in SiteB, the network traffic In/Out and Inside NSX continue to work or will I have to provide a maintenance window?
      • Ideally there is no impact to traffic even when your controller cluster is DOWN/Unavailable. As you are deleting the controller and creating Universal controller, better to take a DOWNTIME.
  • After adding NSX in SiteB as Secondary, will the "Global" objects (Edge-DLR-LB-Firewall Rule and other) still works in SiteB , or do i need to take actions before adding NSX as secondary manager ?
      • Local Objects has no relation with Universal Objects.

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

View solution in original post

0 Kudos
MinoDC
Enthusiast
Enthusiast

Hi RShankar22​ ,

thank for your reply.

  • When i remove all NSX Controller in SiteB, the network traffic In/Out and Inside NSX continue to work or will I have to provide a maintenance window?
    • Ideally there is no impact to traffic even when your controller cluster is DOWN/Unavailable. As you are deleting the controller and creating Universal controller, better to take a DOWNTIME.
      • OK, perfect, Thanks.

  • After adding NSX in SiteB as Secondary, will the "Global" objects (Edge-DLR-LB-Firewall Rule and other) still works in SiteB , or do i need to take actions before adding NSX as secondary manager ?
    • Local Objects has no relation with Universal Objects.
      • So after adding NSX Manager as secondary, all the objects  (Edge-DLR-LB-Firewall Rule and other) that existed before (when NSX Manager was as standalone), will they still work?

Thanks again.

0 Kudos
MinoDC
Enthusiast
Enthusiast

any news, please....thanks to all.

0 Kudos
mauricioamorim
VMware Employee
VMware Employee
  • So after adding NSX Manager as secondary, all the objects  (Edge-DLR-LB-Firewall Rule and other) that existed before (when NSX Manager was as standalone), will they still work?

Answer here is: Yes, making the standalone manager secondary does not affect previously created objects.

MinoDC
Enthusiast
Enthusiast

thanks.

0 Kudos