This process is commonly referred to as “route once, switch many.” It occurs at switch speed, not at the slower router speed. If so, the SE rewrites the pertinent packet info as if it had been processed by the router and then switches the packet. The SE maintains a cache about these flows and can determine whether or not a given packet is part of an established session. In a Cisco MLS network, the initial packet in a session is routed via the RP, but all subsequent packets in that particular session are switched by the SE. As an example, a flow could be an HTTP session between a source browser and a target server. A flow can be defined as a stream of packets from the same source to the same destination using the same application. This aside, there is one very simple concept that makes it all possible: the flow. The SE performs the switching function, the RP performs the routing function, and the MLS protocol provides for communication between these two devices. Typically for wire-speed routing in the Cisco Switch world Cisco requires three entities to implement multilayer switching: the switching engine (SE), the route processor (RP), and the MLS protocol. I am familiar with how CISCO does in on their MLS devices. Are you sure that mention switchip doesn't have that am not familiar with that specific switch chip so I am in part writing out of ignorance of that specific chip.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |