VMware Networking Community
LPriotto
Contributor
Contributor
Jump to solution

How does NSX-V relate to SDN?

I know that VMWARE has its own apis and own virtual switches implemented. I read in an article that NSX is based on the SDN model, I know NSX-V does not use openflow, but I did not understand what the article meant.

The fact that NSX uses controllers, in addition it splits into control plane, data plan and management, does this mean that NSX follows the SDN model?

Thank you!

Tags (2)
Reply
0 Kudos
1 Solution

Accepted Solutions
Sreec
VMware Employee
VMware Employee
Jump to solution

First and foremost SDN&Openflow are not the same. We can have a SDN model without openflow protocol,this is exactly what NSX-v is doing,however openflow is one of building block of SDN. In a openflow deployment - controllers and switches communicate via openflow protocol and build their flow table(Can be proactive also ) to update,delete ,add flows .Below picture depicts NSX architecture.

pastedImage_0.png

1)Communication between NSX manager and vCenter Server is through vSphere API (VIM API )

2)Communication between NSX manager and Controller – HTTPS ( query and config )

3)Communication between NSX manager and Edge – VIX API Guest VM running on a host(

  • VIX is used for vShield/NSX Edge if ESXi host is not prepared otherwise is would be message bus

4)Edge and Controller – HTTPS

Note: ESXi hosts and NSX Edge Logical Router VMs learn network information, which is then reported to the Controller via User World Agent (UWA) residing on each host, also Learnt Routes are pushed to the Controller cluster for distribution and controllers send routing updates to ESXI host and kernel module and later kernel module on host handles the data plane traffic.

Below figure is showing few SDN controllers and their relation with ODL (opendaylight)

pastedImage_3.png

So NSX-v certainly leverage SDN architecture,however there is no openflow protocol communication between Management/Control/data plane. 

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 6x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered

View solution in original post

Reply
0 Kudos
2 Replies
Sreec
VMware Employee
VMware Employee
Jump to solution

First and foremost SDN&Openflow are not the same. We can have a SDN model without openflow protocol,this is exactly what NSX-v is doing,however openflow is one of building block of SDN. In a openflow deployment - controllers and switches communicate via openflow protocol and build their flow table(Can be proactive also ) to update,delete ,add flows .Below picture depicts NSX architecture.

pastedImage_0.png

1)Communication between NSX manager and vCenter Server is through vSphere API (VIM API )

2)Communication between NSX manager and Controller – HTTPS ( query and config )

3)Communication between NSX manager and Edge – VIX API Guest VM running on a host(

  • VIX is used for vShield/NSX Edge if ESXi host is not prepared otherwise is would be message bus

4)Edge and Controller – HTTPS

Note: ESXi hosts and NSX Edge Logical Router VMs learn network information, which is then reported to the Controller via User World Agent (UWA) residing on each host, also Learnt Routes are pushed to the Controller cluster for distribution and controllers send routing updates to ESXI host and kernel module and later kernel module on host handles the data plane traffic.

Below figure is showing few SDN controllers and their relation with ODL (opendaylight)

pastedImage_3.png

So NSX-v certainly leverage SDN architecture,however there is no openflow protocol communication between Management/Control/data plane. 

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 6x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
Reply
0 Kudos
LPriotto
Contributor
Contributor
Jump to solution

Thanks so Much Sreec!!

now it's clearer for me!

Reply
0 Kudos