> It will be ideal for the case when T0 is acting as Active-Active Routing/Switching functionality and T1 is serving for SR services. Otherwise there will be undesired traffic path through Active Edge which won’t give us the benefit and make unnecessary East-West traffic. > It is very important to understand in the production setup, if there is SR service requirement then only map T1 to edge cluster. The northbound IP of the transit-segment (DR-SR) will be same across the T1 component.(In the below topology it is 169.254.0.1.The transist-segment-vxlan(between DR and SR) will be auto generated by the system.The SR service as per the service are being started the components will start on the Edge, in Active/Standby mode where one Edge will be able to receive the data plane traffic.The DR service will be instantiated on Transport nodes which includes ESXi and Edge.In the following topology we have show 2 segments part of same T1 router/gateway ( 10.1.1.0/24 and 20.1.1.0/24 ).But now when we choose Edge Cluster it will also i nstantiate the SR service on related Edge-Cluster. In such scenarios the traffic path will via the Edge cluster and the deployment of T1 Edge can be only Active/Standby.Īs we know the DR component will be instantiated on every Transport Node as per the workload availability, which will function for the East-West communication. In this scenario we will walk through what will be the role of Edge deployed.Īs per the design decison one should choose to have Edge Cluster mapped to T1 when we need to consume the SR services, such as Gateway-Firewall, NAT, IPSec Services. In our previous blog we went through the Distributed routing which gives routing features, and is highly available. NSX-T Series: Part 15 – NSX-T Segment with T1 Gateway without EDGE Cluster NSX-T Series: Part 14 – NSX-T Segment without IP Subnet/Gateway NSX-T Series: Part 13 – NSX-T EDGE Deploy Part-2 NSX-T Series: Part 12 – NSX-T EDGE Deploy Part-1 NSX-T Series: Part 11– NSX-T Multi-Tier Routing NSX-T Series: Part 9 – NSX-T Logical Switching Services NSX-T Series: Part 8 – NSX-T Logical Switching Use Cases NSX-T Series: Part 7 – NSX-T ESXi Transport Node NSX-T Series: Part 6 – NSX-T Uplink Profile NSX-T Series: Part 5 – NSX-T N-VDS and VDS 7.0
#SHAHRZAD SERIES PART 16 SERIES#
NSX-T Series : Part 4 – Transport Zones and Use cases for Multi-Transport Zone NSX-T Series : Part 3 – Planning NSX VXLAN NSX-T Series : Part 2 – Adding Compute Manager NSX-T Series : Part 1 -Architecture and Deploy If you want to start from beginning you can refer my previous part of the Series: In this part we will explore the traffic behaviour when a NSX-T Segment T1 Gateway with EDGE Cluster(SR, and in this scenario we will explore design decision which should be followed in production environment.
0 kommentar(er)
