VMware NSX

With NSX would like to know for different VM's does it require to assign VLANs to it.
In traditional network we assign VLAN & IP Address to each VM.
With NSX is only IP Address & VNI no is sufficient. Is there no concept of VLAN no to be assigned.
Please let me know.
LVL 1
SrikantRajeevAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Zephyr ICTCloud ArchitectCommented:
I'm not entirely sure I get your question, but I'll try to give an answer on a part of it ... NSX use VXLAN, not to compare with normal VLAN, but there is a way to bind the VXLAN with a VLAN used on your physical network ... This is called L2 bridging.

Maybe this might make it more clear.
0
SrikantRajeevAuthor Commented:
not exactly
Without NSX for any VM creation we assign VLAN & its corresponding IP Address from it segment.
with NSX we assign only IP Address & its corresponding VNI . No VLAN is required for this.


With NSX we eliminate the requirement of assigning VLAN numbers.

Am i correct.
0
Zephyr ICTCloud ArchitectCommented:
With NSX we eliminate the requirement of assigning VLAN numbers.

You eliminate the use of VLAN numbers like in the traditional sense yes, VNI interfaces are sort of similar like VLAN interfaces in that sense that they keep network traffic separated... So in that sense you are right.
0
What were the top attacks of Q1 2018?

The Threat Lab team analyzes data from WatchGuard’s Firebox Feed, internal and partner threat intelligence, and a research honeynet, to provide insightful analysis about the top threats on the Internet. Check out our Q1 2018 report for smart, practical security advice today!

SrikantRajeevAuthor Commented:
Yeah thanks.
In my current scenario I have L2 architecture where we define all the VLANs & Its corresponding IP Address in the L3 core switch.
So for any new segment which is getting added in the network we normally create its corresponding VLAN & its IP segment.

Now we are planning to move to NSX.
So in this case any segment which is inside NSX will be assigned IP Address & the VMs will be part of a VNI. [ No more VLAN numbering needs to be done]

Above is my understanding.
0
Zephyr ICTCloud ArchitectCommented:
Yes, that seems like a good understanding... VNI is a part of VXLAN and it takes care of the traditional VLAN tasks so to say...

This is a nice document to get a better understanding of VXLAN, should it be needed, it's for when you use ASA's but it can shed some light on certain things even if you're not working with ASA's
0
SrikantRajeevAuthor Commented:
Its there any document where it is mentioning that VLANs can be eliminated when VXLAN is in use.
Looking for a document where it is clearly mentioning that there is no need for VLAN in the future if we use NSX.
0
Zephyr ICTCloud ArchitectCommented:
Not litteraly no, not that I know of at least...

In the design document you can find this:

It is central to network virtualization because it enables logical networks that are independent of physical constructs such as VLANs

Source

Chances are you're not going to find it literally written anywhere because of the need to provide legacy VLAN compatibility and the fact that native VLAN doesn't exist on NSX, just the ability to map them with VXLAN.
0
SrikantRajeevAuthor Commented:
VMware is naming VLAN into VNI numbering.
So instead of managing the VLAN we need to manage the VNI
This is my understanding.
I  feel it will be similar to managing VLAN
Any thoughts.
0
Zephyr ICTCloud ArchitectCommented:
VMware is naming VLAN into VNI numbering.
So instead of managing the VLAN we need to manage the VNI
This is my understanding.
I  feel it will be similar to managing VLAN
Any thoughts.

That's what I wanted to say, but you worded it better ;-)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SrikantRajeevAuthor Commented:
Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

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.