Differences between revisions 19 and 20
Revision 19 as of 2019-05-23 05:41:30
Size: 842
Editor: localhost
Comment:
Revision 20 as of 2019-05-28 06:43:17
Size: 1196
Editor: localhost
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:

== Notes ==
  * All NSX Edge services run on the active appliance. The primary appliance maintains a heartbeat with the standby appliance and sends service updates through an internal interface. If a heartbeat is not received from the primary appliance within the specified time (default value is 15 seconds), the primary appliance is declared dead.

NSX requirement

  • No matter the size of the NSX deployment, VMware requires that each NSX Controller cluster contain three controller nodes. Having a different number of controller nodes is not supported.
  • The cluster requires that each controller's disk storage system has a peak write latency of less than 300ms, and a mean write latency of less than 100ms. If the storage system does not meet these requirements, the cluster can become unstable and cause system downtime.

NSX check

  • Log in to the NSX Controller CLI.

get control-cluster status

show control-cluster status
show control-cluster connections
  • Log in to the NSX Manager CLI.

# nsx-manager
show logical-switch list all
get management-cluster status

Notes

  • All NSX Edge services run on the active appliance. The primary appliance maintains a heartbeat with the standby appliance and sends service updates through an internal interface. If a heartbeat is not received from the primary appliance within the specified time (default value is 15 seconds), the primary appliance is declared dead.

désert/VMware/NSX (last edited 2019-11-03 09:22:18 by merlin)