{"id":677,"date":"2020-12-11T16:12:22","date_gmt":"2020-12-11T15:12:22","guid":{"rendered":"http:\/\/hentati.org\/?p=677"},"modified":"2021-11-22T20:32:25","modified_gmt":"2021-11-22T19:32:25","slug":"nsx-primary-secondary","status":"publish","type":"post","link":"https:\/\/hentati.org\/index.php\/2020\/12\/11\/nsx-primary-secondary\/","title":{"rendered":"Configure Cross-vCenter NSX-V 6.4 : Primary\/Secondary Architecture"},"content":{"rendered":"

Since NSX version 6.2 we can have NSX in a vSphere environment managed by more than one vCenter system. This deployment is called cross-vCenter NSX<\/strong>.<\/span><\/p>\n

There can be one primary NSX Manager<\/strong> (runs the controller cluster)\u00a0 and up to seven secondary NSX Managers<\/strong> in a cross-vCenter NSX environment.<\/span><\/p>\n

The advantage to use this kind of architecture is NSX together with vSphere is the infrastructure that delivers on business requirements like workload mobility, resource pooling, consistent security and centralization of configuration (same Routers and Switchs on the Universal Transport Zone)<\/span><\/p>\n

We don’t need to install controller cluster to all NSX manager if we want to configure them as Secondary NSX manager, due to their role as NSX Secondary, they will use controller cluster of the Primary NSX manager on common, and thanks to this architecture, we are able to have the same configuration in all NSX manager for all virtual network equipment (DLR, LS and EDGE router) belonging to the Universal Transport Zone,<\/strong><\/span><\/p>\n

 <\/p>\n

Prerequisite:<\/strong><\/span><\/p>\n

2 vCenter on linked-mode<\/a> or standalone<\/a>\u00a0<\/span><\/p>\n

2 NSX manager each one connected to his appropriate vCenter in standalone mode (how to install NSX manager standalone Click here<\/a>)<\/span><\/p>\n

First NSX manager have controller cluster, and second NSX manager controller cluster is not installed !<\/strong><\/span><\/p>\n

 <\/p>\n

In our example, we are going to configure the primary NSX Manager and one additional secondary NSX Manager.<\/span><\/p>\n

We have 2 vCenter on linked-mode (version 6.7) and 2 NSX manager on standalone (version 6.4)<\/span><\/p>\n

\"\"<\/a><\/span><\/p>\n

 <\/p>\n

To configure an NSX Manager as the Primary:<\/strong><\/span><\/p>\n

Log into the vCenter linked to the primary NSX Manager using the vSphere Web Client.<\/span><\/p>\n

Navigate to\u00a0Home > Networking & Security > Installation<\/span>\u00a0and select the\u00a0Management<\/span>\u00a0tab.<\/span><\/p>\n

Select the NSX Manager you want to assign as the primary and click Actions<\/span>\u00a0and then\u00a0Assign Primary Role<\/span>.<\/span><\/p>\n

\"\"<\/p>\n

 <\/p>\n

The selected NSX Manager is assigned the primary role.<\/span><\/p>\n

\"\"<\/span><\/p>\n

 <\/p>\n

To configure an NSX Manager as Secondary:<\/strong><\/span><\/p>\n

Log in to the vCenter linked to the primary NSX Manager.<\/span><\/p>\n

Navigate to Home > Networking & Security > Installation and select the Management tab.<\/span><\/p>\n

Click the primary NSX Manager. Then select Actions > Add Secondary NSX Manager.<\/span><\/p>\n

\"\"<\/span><\/p>\n

 <\/p>\n

Enter the IP address, user name, and password of the secondary NSX Manager.<\/span><\/p>\n

\"\"<\/span><\/p>\n

 <\/p>\n

After successful registration the role changes from Standalone to Secondary.<\/span><\/p>\n

vCenter Server systems are in Enhanced Linked Mode, we can see the roles of all NSX Managers associated with those vCenter Server systems from the Home > Networking & Security > Installation tab.<\/span><\/p>\n

\"\"<\/span><\/p>\n

 <\/p>\n

If vCenter Server systems are in Standalone Mode, we have to connect to every vCenter to configure NSX manager, in this case we can’t configure Local Transport Zone from the same installation tab,<\/span><\/p>\n

Enjoy NSX \ud83d\ude00<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Since NSX version 6.2 we can have NSX in a vSphere environment managed by more than one vCenter system. This deployment is called cross-vCenter NSX. There can be one primary …<\/p>\n","protected":false},"author":1,"featured_media":832,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[10],"tags":[],"_links":{"self":[{"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/posts\/677"}],"collection":[{"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/comments?post=677"}],"version-history":[{"count":17,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/posts\/677\/revisions"}],"predecessor-version":[{"id":885,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/posts\/677\/revisions\/885"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/media\/832"}],"wp:attachment":[{"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/media?parent=677"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/categories?post=677"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/tags?post=677"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}