NSX-T Management Plane
NSX Manager
NSX Manager is a virtual appliance that provides the graphical user interface (GUI) and the REST APIs for creating, configuring, and monitoring NSX-T Data Center components, such as logical switches, and NSX Edge services gateways.
NSX-T Control Plane
Computes all ephemeral runtime state based on configuration from the management plane, disseminates topology information reported by the data plane elements, and pushes stateless configuration to forwarding engines.
NSX-T Central Control Plane Cluster
NSX Controller is deployed as a cluster of highly available virtual appliances that are responsible for the programmatic deployment of virtual networks across the entire NSX-T Data Center architecture. The NSX-T Data Center CCP is logically separated from all data plane traffic, meaning any failure in the control plane does not affect existing data plane operations. Traffic doesn’t pass through the controller; instead the controller is responsible for providing configuration to other NSX Controller components such as the logical switches, logical routers, and edge configuration. Stability and reliability of data transport are central concerns in networking. To further enhance high availability and scalability, the NSX Controller is deployed in a cluster of three instances.
It populates rules and tables on data plane nodes.
NSX-T Data Plane
Hypervisor Transport Nodes
NSX Manager
NSX Manager is a virtual appliance that provides the graphical user interface (GUI) and the REST APIs for creating, configuring, and monitoring NSX-T Data Center components, such as logical switches, and NSX Edge services gateways.
Computes all ephemeral runtime state based on configuration from the management plane, disseminates topology information reported by the data plane elements, and pushes stateless configuration to forwarding engines.
NSX-T Central Control Plane Cluster
NSX Controller is deployed as a cluster of highly available virtual appliances that are responsible for the programmatic deployment of virtual networks across the entire NSX-T Data Center architecture. The NSX-T Data Center CCP is logically separated from all data plane traffic, meaning any failure in the control plane does not affect existing data plane operations. Traffic doesn’t pass through the controller; instead the controller is responsible for providing configuration to other NSX Controller components such as the logical switches, logical routers, and edge configuration. Stability and reliability of data transport are central concerns in networking. To further enhance high availability and scalability, the NSX Controller is deployed in a cluster of three instances.
It populates rules and tables on data plane nodes.
NSX-T Data Plane
Hypervisor Transport Nodes
- It is forwarding plane for VM's Traffic
- It Supports ESXi and KVM Hypervisors
- It is implemented as new vSwitch in ESXi and Open vSwitch in KVM
- NSX Edge provides routing services and connectivity to networks that are external to the NSX-T Data Center deployment.
- NSX Edge can be deployed as a bare metal node or as a VM.
- NSX Edge is required for establishing external connectivity from the NSX-T Data Center domain, through a Tier-0 router via BGP or static routing. Additionally, an NSX Edge must be deployed if you require network address translation (NAT) services at either the Tier-0 or Tier-1 logical routers.
- The NSX Edge gateway connects isolated, stub networks to shared (uplink) networks by providing common gateway services such as NAT, and dynamic routing. Common deployments of NSX Edge include in the DMZ and multi-tenant Cloud environments where the NSX Edge creates virtual boundaries for each tenant.
Refer
NSX-T Introduction - Part 1
No comments:
Post a Comment