• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 119
  • Last Modified:

NSX Design

Attached is the current NSX network design.
I have L2 Switch connecting to the L3 Core switch. The ESXi hosts with NSX are connecting to the L2 switch.
OSPF is running between the L3 Core switch & the NSX.

In the near future I will be running short of the L2 switch ports where the ESXi hosts are connected.
For this I have 2 options

Option 1: Setup 2 more L2 switches parallel to the existing & connect the same to the L3 core switches. Similar to the existing setup.
Option 2: Setup 2 more L2 switches below the existing L2 switches & connect the ESXi hosts to the new L2 switches.

Would like to know which option is the best considering the pros & cons.
NSX_Design.png
0
SrikantRajeev
Asked:
SrikantRajeev
1 Solution
 
giltjrCommented:
What you are showing is a physical diagram and what appears to be a single IP subnet (x.x.x.0/22)

In order to understand what may be best we (at least I do) would need to understand your L2 and L3 setup better.  As an example.  If you really only have a single subnet (x.x.x.0/22) that would imply a single L2 network.  If you have a single L2 and L3 network, why are you running OSPF?
0
 
harbor235Commented:
The issue with option 2 is that as you add  more ESXi hosts to the new switches you are limited to two uplinks to the layer 3 core. So depending on the utilization and how you have the network setup this could cause over subscription of the uplinks. So in general option 2 does not scale.

Depending on the utilization of the uplinks and the class of layer 2 switch that you are using, you may be able to use option 2, but why not connect right to the L3 core with new switches? So the answer is it depends on what the ESXi hosts are doing, how much capacity is available, etc .....


harbor235 ;}
0
 
giltjrCommented:
Without knowing more about the setup, I would say that option #1 should allow you more growth with out affecting performance.  It depends on how much traffic from the ESX hosts actually has to go to the core.

If go with option#2 and you have a lot of traffic that goes from the ESX servers to the core, you will be increasing the amount of traffic that is flowing on the connections between your two existing L2 switched and your core.  As harbor235 stated, this may not affect you at all depending on current utilization of those links.

The only downside I can think of with option #1 is that you could need more ports on your cores.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
gheistCommented:
OSPF is not relevant in a single L3 IP subnet
0
 
SrikantRajeevAuthor Commented:
Is there any document or design guide from vmware regarding how to scale the NSX design.
0
 
giltjrCommented:
Based on what little we know, you current "NSX" network is basically a single large flat L2 network that that your cores are part of.  

In my opinion, your best bet would be to get two more L2 switches and basically setup them up exactly like your current L2 switches.  So that you have all 4 switched connected directly to your cores and all 4 switches have the same VLAN's.  Then connect any new ESX hosts to the new switches, or even move some current ESX hosts to the new switches.

Basically choose option #1.

I'm still not sure why you have OSPF in the mix, as based on your diagram it is not needed at all.  Your core routers are in the same L3 network as NSX, which means your core already knows about that subnet.
0
 
SrikantRajeevAuthor Commented:
Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now