![]() ![]() In today's model, the data plane operates on rigid infrastructure-centric entities such as LUNs or storage volumes. The virtual data plane also applies whatever policy has been selected to the objects in the virtual datastore. It is responsible for forwarding the traffic.While data services are provided by a physical array or implemented in software, the virtual data plane abstracts the services and presents them to the policy-driven control plane (which we will speak about in the next section) for use. The data plane is handled by the NSX Virtual Switch. Their focus is on the learning and decision making. They determine where to send traffic, but none of that traffic actually passes through the Controllers. ![]() #CONTROLPLANE VS DATAPLANE MAC#They learn about the hosts, the IP and MAC mappings, they learn the connectivity status of the components, and they learn routes via the Logical Router Control VM. It is handled by a cluster of NSX Controllers. ![]() This way, instead of configuring each component individually, NSX devices can be configured from a single point. Instead of each component having its very own management plane, management is decoupled from the device and handled centrally by NSX Manager. The management plane is a function of NSX Manager. NSX separates the planes using different components. Each plane is found within the confines of the switch. The difference is that in a physical switch, all three live under the same roof. The management plane is for configuration, the control plane is where the learning takes place, and the data plane is responsible for forwarding the traffic. With NSX, we have the same planes and they have the same functions. The thinking part has already been accomplished by the control plane and the decisions it made are recorded in the MAC table and STP topology. But the data plane doesn't have to think it just does the work. It switches frames from the input interface to an output interface (which is why it's called a switch). However, it's the data plane that does the real work in moving the frames. Now the switch knows exactly where to forward the traffic. #CONTROLPLANE VS DATAPLANE FREE#The end result of all this learning is a MAC table of learned hosts and ports and a loop free topology. The switch learns the topology, figures out which ports should be forwarding and which should be blocking. If the primary path fails, the corresponding blocked port transitions to forwarding. STP's job is to identify physical loops and block specific interfaces that ultimately eliminate all loops, giving a single path from one point to any other point within the Layer 2 domain. Another example of learning in the control plane is Spanning Tree Protocol. That information is then recorded in the MAC table. It learns the MAC addresses and the location of the devices, reading the Ethernet headers to find the source MAC and making note of which interface the frame arrived on. You can think of the control plane as the brains of the operation. The learning occurs in the control plane. The switch will dynamically learn the MAC addresses assigned to the hosts within that domain. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |