Softrouter protocol disaggregation
View Patent ↗A SoftRouter architecture deconstructs routers by separating the control entities of a router from its forwarding components, enabling dynamic binding between them. In the SoftRouter architecture, control plane functions are aggregated and implemented on a few smart servers which control forwarding elements that are multiple network hops away. A dynamic binding protocol performs network-wide control plane failovers. Network stability is improved by aggregating and remotely hosting routing protocols, such as OSPF and BGP. This results in faster convergence, lower protocol messages processed, and fewer route changes following a failure. The SoftRouter architecture includes a few smart control entities that manage a large number of forwarding elements to provide greater support for network-wide control. In the SoftRouter architecture, routing protocols operate remotely at a control element and control one or more forwarding elements by downloading the forwarding tables, etc. into the forwarding elements. Intra-domain routing and inter-domain routing are also included.
1. A network of devices including at least a first forwarding element (FE), a first control element (CE) and a first network element (NE), the network comprising:
a first forwarding element (FE) set including a plurality of FEs; and
a first control element (CE) for controlling the first FE set, the first CE providing one first protocol process among a plurality of protocols on behalf of each FE in the first FE set, the first CE being physically remote from the FEs in the first FE set, the first CE being dynamically bound to each FE in the first FE set such that multiple bindings may be performed
wherein the network architecture is adapted to perform a dynamic binding protocol for dynamically binding each FE to one of the CEs, wherein the dynamic binding protocol comprises a discovery protocol enabling each FE to discover one of the CEs which can manage the FE such that multiple bindings may be performed;
wherein each of said FEs is configured to request discovery of the first CE, wherein said CE is configured to respond to the respective requests for discovery of the first CE by each of the FEs in the first FE set, wherein respective responses by the first CE to discovery of the first CE by each of the FEs in the first FE set are configured for use by the FEs in the first FE set to dynamically bind with the first CE; and
wherein the first CE and the FEs in the first FE set form a first network element.
2. The network of claim 1 , wherein multiple CEs control the first FE set in the first NE.
3. The network of claim 1 , further comprising:
a second FE set including a plurality of FEs that are distinct from those in the first FE set;
a second CE for controlling the second FE set, the second CE running one second protocol process on behalf of the second FE set, the second CE being physically remote from the second FE set; and
a second NE including the second CE and the second FE set.
4. The network of claim 3 , wherein a first routing protocol process manages the FEs of the first NE and computes intra-domain routes for the FEs of the first NE.
5. The network of claim 4 , further comprising internal links and weights of the internal links that are advertised to neighbors.
6. The network of claim 4 , wherein the first NE is configured as a first protocol area and summary advertisements for the links internal to the first NE are sent and the second NE is configured as a second protocol area and summary advertisements for the links internal to the second NE are sent.
7. The of claim 4 , wherein the first NE is configured as a first protocol area and a first internal link routing protocol is used internal to the first NE and the second NE is configured as a second protocol area and a second internal link routing protocol is used internal to the second NE.
8. The network of claim 4 , wherein any control protocol or management message sent from the first CE to the second CE is first tunneled using a standard transport protocol to a particular FE in the first FE set and, then, forwarded to another particular FE in the second FE set and, finally, tunneled back to the second CE.
9. The network e of claim 4 , wherein any control protocol or management message is sent from the first CE to the second CE on behalf of any FE in the first FE set.
10. The network of claim 4 , wherein routing information is sent from the first CE to an FE in the first FE set.
11. The network architecture of claim 3 , further comprising a third CE that is dynamically bound to an FE in the first FE set as a backup-CE;
wherein the FE initiates a failover to the third CE upon a failure associated with the first CE.
12. The network of claim 3 , further comprising:
wherein the dynamic binding protocol dynamically binds particular FEs with particular CEs and for handling failovers.
13. The network of claim 3 , wherein the first CE and the second CE are implemented on a multi-blade rack server.
14. The network of claim 3 , wherein the first CE is multiple hops away from a particular FE in the first FE set.
15. A network of devices including at least a first forwarding element (FE), a first control element (CE) and a first network element (NE), the network comprising:
a plurality of forwarding elements (FEs);
a plurality of control elements (CEs),
each CE controlling a different set of the FEs than the other CEs, the CEs being physically remote from the FEs; and
a full internal border gateway protocol (I-BGP) mesh among the CEs;
wherein the network architecture is adapted to perform a dynamic binding protocol for dynamically binding each FE to one of the CEs, wherein the dynamic binding protocol comprises a discovery protocol enabling each FE to discover the one of the CEs which can manage the FE such that multiple bindings may be performed;
wherein each of said FEs is configured to periodically broadcast a solicitation message to each of its neighbors;
wherein each of the CEs is configured, if it is a neighbor of a FE broadcasting a solicitation message, to respond by advertising its identity to the FE from which the solicitation message is received;
wherein each of the FEs is configured, if it is a neighbor of a FE broadcasting a solicitation message, to respond with reachability information for all CEs already learned by that FE.
16. The network of claim 15 , further comprising intra-domain routing and inter-domain routing.
17. The network of claim 15 , wherein at least one of the CEs communicates with another network element via external BGP (E-BGP).
18. The network of claim 15 , wherein the dynamic binding protocol handles failovers.
19. The network of claim 15 , further comprising:
a plurality of core routers;
a core network connected to the core routers; and
a point-of-presence (POP) Ethernet network connected by the core routers to the core network, connected to the CEs, and connected to the FEs.
20. The network of claim 19 , further comprising:
a digital subscriber line access multiplexer (DSLAM) connected to at least one FE.
21. The network of claim 19 , further comprising at least one authentication, authorization, and accounting (AAA) server connected to the POP Ethernet network.
22. The network of claim 19 , wherein each FE is capable of initiating a failover to a backup CE upon failure of a bound CE.
23. The network of claim 19 , wherein each of the CEs provides a protocol process that manages the FEs and computes intra-domain routes for each FE.
24. The network of claim 19 , wherein at least of the CEs is multiple hops away from each FE.
25. The network of claim 19 , wherein one of the CEs communicates with another network element via external BGP (E-BGP), for all CEs already learned by that FE.