SrikantRajeev
asked on
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.
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.
ASKER
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.
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.
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.
ASKER
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.
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.
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
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
ASKER
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.
Looking for a document where it is clearly mentioning that there is no need for VLAN in the future if we use NSX.
Not litteraly no, not that I know of at least...
In the design document you can find this:
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.
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.
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks
Maybe this might make it more clear.