本文探讨了NSX网关在不同部署环境下的配置细节，包括针对多个虚拟化平台及vSphere的不同设置。覆盖了网关如何作为VXLAN段的入口与出口，如何为不同VXLAN段指定特定网关，以及网关的集群配置方式等问题。
Gordon sent me a whole list of NSX gateway questions:
•Do you need a virtual gateway for each VXLAN segment or can a gateway be the entry/exit point across multiple VXLAN segments?
•Can you setup multiple gateways and specify which VXLAN segments use each gateway?
•Can you cluster gateways together (Active/Active) or do you setup them up as Active/Standby?
The answers obviously depend on whether you’re deploying NSX for multiple hypervisors or NSX for vSphere . Let’s start with the former.
Gateways in NSX for multiple hypervisors release 4.0
NSX gateways are implemented on NSX gateway transport nodes which run on bare-metal servers or in dedicated VMs. NSX also supports third-party L2 gateways (VTEPs) with VXLAN encapsulation.
Each gateway node can run multiple instances of L2 or L3 gateway services (but not both). Each L2 gateway service can bridge between numerous overlay networks and VLANs (there must be a 1:1 mapping between an overlay network segment and an outside VLAN), each L3 gateway service can route between numerous logical networks and a single uplink.
Each gateway service can run on two gateway nodes in Active/Standby mode.
Gateways in NSX for vSphere release 6.0
Control plane of every NSX gateway is always implemented in a VM running NSX Edge software. Data plane of L2 gateways and distributed routers is implemented in loadable kernel modules, data plane of NSX Edge services gateway is implemented within the VM (like the traditional vShield Edge).
Each L2 gateway instance (NSX Edge VM running as L2 gateway) can bridge a single VXLAN segment to a VLAN segment. Multiple L2 gateway instances can run on the same vSphere host.
NSX Edge router (running just the control plane) can have up to eight uplinks and up to 1000 internal (VXLAN-based) interfaces. NSX Edge services gateway (with data plane implemented within the VM) can have up to ten interfaces (the well-known vSphere limit on the number of interfaces of a single VM). Multiple NSX Edge routers or NSX Edge services gateways can run on the same vSphere host.
Each NSX Edge instance can run in Active/Standby HA mode.
In theory you might have more than one NSX Edge instance connecting a VXLAN segment with the outside world, but even if the NSX Manager software allows you to configure that, I wouldn’t push my luck.
Gordon sent me a whole list of NSX gateway questions:
•Do you need a virtual gateway for each VXLAN segment or can a gateway be the entry/exit point across multiple VXLAN segments?
•Can you setup multiple gateways and specify which VXLAN segments use each gateway?
•Can you cluster gateways together (Active/Active) or do you setup them up as Active/Standby?
The answers obviously depend on whether you’re deploying NSX for multiple hypervisors or NSX for vSphere . Let’s start with the former.
Gateways in NSX for multiple hypervisors release 4.0
NSX gateways are implemented on NSX gateway transport nodes which run on bare-metal servers or in dedicated VMs. NSX also supports third-party L2 gateways (VTEPs) with VXLAN encapsulation.
Each gateway node can run multiple instances of L2 or L3 gateway services (but not both). Each L2 gateway service can bridge between numerous overlay networks and VLANs (there must be a 1:1 mapping between an overlay network segment and an outside VLAN), each L3 gateway service can route between numerous logical networks and a single uplink.
Each gateway service can run on two gateway nodes in Active/Standby mode.
Gateways in NSX for vSphere release 6.0
Control plane of every NSX gateway is always implemented in a VM running NSX Edge software. Data plane of L2 gateways and distributed routers is implemented in loadable kernel modules, data plane of NSX Edge services gateway is implemented within the VM (like the traditional vShield Edge).
Each L2 gateway instance (NSX Edge VM running as L2 gateway) can bridge a single VXLAN segment to a VLAN segment. Multiple L2 gateway instances can run on the same vSphere host.
NSX Edge router (running just the control plane) can have up to eight uplinks and up to 1000 internal (VXLAN-based) interfaces. NSX Edge services gateway (with data plane implemented within the VM) can have up to ten interfaces (the well-known vSphere limit on the number of interfaces of a single VM). Multiple NSX Edge routers or NSX Edge services gateways can run on the same vSphere host.
Each NSX Edge instance can run in Active/Standby HA mode.
In theory you might have more than one NSX Edge instance connecting a VXLAN segment with the outside world, but even if the NSX Manager software allows you to configure that, I wouldn’t push my luck.
•Do you need a virtual gateway for each VXLAN segment or can a gateway be the entry/exit point across multiple VXLAN segments?
•Can you setup multiple gateways and specify which VXLAN segments use each gateway?
•Can you cluster gateways together (Active/Active) or do you setup them up as Active/Standby?
The answers obviously depend on whether you’re deploying NSX for multiple hypervisors or NSX for vSphere . Let’s start with the former.
Gateways in NSX for multiple hypervisors release 4.0
NSX gateways are implemented on NSX gateway transport nodes which run on bare-metal servers or in dedicated VMs. NSX also supports third-party L2 gateways (VTEPs) with VXLAN encapsulation.
Each gateway node can run multiple instances of L2 or L3 gateway services (but not both). Each L2 gateway service can bridge between numerous overlay networks and VLANs (there must be a 1:1 mapping between an overlay network segment and an outside VLAN), each L3 gateway service can route between numerous logical networks and a single uplink.
Each gateway service can run on two gateway nodes in Active/Standby mode.
Gateways in NSX for vSphere release 6.0
Control plane of every NSX gateway is always implemented in a VM running NSX Edge software. Data plane of L2 gateways and distributed routers is implemented in loadable kernel modules, data plane of NSX Edge services gateway is implemented within the VM (like the traditional vShield Edge).
Each L2 gateway instance (NSX Edge VM running as L2 gateway) can bridge a single VXLAN segment to a VLAN segment. Multiple L2 gateway instances can run on the same vSphere host.
NSX Edge router (running just the control plane) can have up to eight uplinks and up to 1000 internal (VXLAN-based) interfaces. NSX Edge services gateway (with data plane implemented within the VM) can have up to ten interfaces (the well-known vSphere limit on the number of interfaces of a single VM). Multiple NSX Edge routers or NSX Edge services gateways can run on the same vSphere host.
Each NSX Edge instance can run in Active/Standby HA mode.
In theory you might have more than one NSX Edge instance connecting a VXLAN segment with the outside world, but even if the NSX Manager software allows you to configure that, I wouldn’t push my luck.
Gordon sent me a whole list of NSX gateway questions:
•Do you need a virtual gateway for each VXLAN segment or can a gateway be the entry/exit point across multiple VXLAN segments?
•Can you setup multiple gateways and specify which VXLAN segments use each gateway?
•Can you cluster gateways together (Active/Active) or do you setup them up as Active/Standby?
The answers obviously depend on whether you’re deploying NSX for multiple hypervisors or NSX for vSphere . Let’s start with the former.
Gateways in NSX for multiple hypervisors release 4.0
NSX gateways are implemented on NSX gateway transport nodes which run on bare-metal servers or in dedicated VMs. NSX also supports third-party L2 gateways (VTEPs) with VXLAN encapsulation.
Each gateway node can run multiple instances of L2 or L3 gateway services (but not both). Each L2 gateway service can bridge between numerous overlay networks and VLANs (there must be a 1:1 mapping between an overlay network segment and an outside VLAN), each L3 gateway service can route between numerous logical networks and a single uplink.
Each gateway service can run on two gateway nodes in Active/Standby mode.
Gateways in NSX for vSphere release 6.0
Control plane of every NSX gateway is always implemented in a VM running NSX Edge software. Data plane of L2 gateways and distributed routers is implemented in loadable kernel modules, data plane of NSX Edge services gateway is implemented within the VM (like the traditional vShield Edge).
Each L2 gateway instance (NSX Edge VM running as L2 gateway) can bridge a single VXLAN segment to a VLAN segment. Multiple L2 gateway instances can run on the same vSphere host.
NSX Edge router (running just the control plane) can have up to eight uplinks and up to 1000 internal (VXLAN-based) interfaces. NSX Edge services gateway (with data plane implemented within the VM) can have up to ten interfaces (the well-known vSphere limit on the number of interfaces of a single VM). Multiple NSX Edge routers or NSX Edge services gateways can run on the same vSphere host.
Each NSX Edge instance can run in Active/Standby HA mode.
In theory you might have more than one NSX Edge instance connecting a VXLAN segment with the outside world, but even if the NSX Manager software allows you to configure that, I wouldn’t push my luck.
扫一扫
1157
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
