MAC-BASED REDISTRIBUTION IN MULTI-AREA NETWORKS
Provided herein are systems and methods for providing a MAC-based redistribution policy between networks in a multi-area network. A network can have a boundary node that communicates to neighboring networks. Boundary nodes can receive policy updates that identify which services are redistributable across network boundaries. Boundary nodes can receive a packet for a service, translate the packet's encapsulation, and forward the packet across the boundary towards a destination node. Boundary nodes can forward the packet such that it originates in the second network from a virtual node.
1 . A method for providing a service redistribution policy for a multi-area network, the method comprising:
receiving, in a node of a first network in the multi-area network, a packet from a host for a service, wherein the packet has a destination in a second network in the multi-area network that is across one or more boundaries between the first network and the second network;
identifying, in the node, a route from the first network to the second network in a routing table;
assigning, in the node, the route to the service; and
forwarding, from the first network to the second network, the service based on the route.
2 . The method of claim 1 , further comprising configuring the service to be redistributable in a single direction from the first network across the one or more boundaries towards the second network.
3 . The method of claim 2 , further comprising:
receiving, in the node, a different packet from a different host for the service, wherein the packet has a destination across the one or more boundaries from the second network to the first network; and
discarding the packet at the node based on the service being redistributable in the single direction from the first network across the one or more boundaries towards the second network.
4 . The method of claim 1 , further comprising configuring the service to be redistributable in a first direction from the first network across the one or more boundaries towards the second network and in a second direction from the second network across the one or more boundaries towards the first network.
5 . The method of claim 1 , further comprising:
receiving, at a boundary node on at least one of the one or more boundaries, the route from a control plane for the multi-area network, wherein the control plane generated the route based on the service being configured to be at least one of:
redistributable in a first direction from the first network across the one or more boundaries towards the second network and in a second direction from the second network across the one or more boundaries towards the first network; and
redistributable in a direction from the first network across the one or more boundaries towards the second network; and
installing the route in the routing table for the boundary node.
6 . The method of claim 5 , further comprising configuring the boundary node as a virtual node.
7 . The method of claim 1 , further comprising:
redistributing, from the node, the route from the first network across at least one of the one or more boundaries to a different boundary node in a different network; and
updating a different routing table for the different boundary node by installing the route in the different routing table.
8 . A boundary node on a boundary between a first network and a second network in a multi-area network, the boundary node configured to:
receive a packet from a host for a service, wherein the packet has a destination in the second network;
identify a route from the first network to the second network in a routing table;
assign the route to the service; and
forward the packet to the destination in the second network based on the route.
9 . The boundary node of claim 8 , wherein the boundary node is further configured to enable the service to be redistributable in a single direction from the first network across the boundary to the second network.
10 . The boundary node of claim 8 , wherein the boundary node is further configured to enable the service to be redistributable in a first direction from the first network across the boundary to the second network and in a second direction from the second network across boundary to the first network.
11 . The boundary node of claim 8 , wherein the boundary node is further configured to:
receive the route from a control plane for the multi-area network, wherein the control plane generated the route based on the service being configured to be at least one of:
redistributable in a first direction from the first network across boundary to the second network and in a second direction from the second network across boundary to the first network; and
redistributable in a direction from the first network across the boundary to the second network; and
install the route in the routing table for the boundary node.
12 . The boundary node of claim 8 , wherein the boundary node is a virtual node.
13 . The boundary node of claim 8 , wherein the boundary node is further configured to redistribute the route from the first network across boundary to the a different boundary node in the second network.
14 . A non-transitory computer readable storage medium having computer readable code thereon, the non-transitory computer readable storage medium including instructions configured to cause a computer system to perform operations, comprising:
receiving a packet from a host for a service in a node of a first network in the multi-area network, wherein the packet has a destination in a second network in the multi-area network that is across one or more boundaries between the first network and the second network;
identifying a route from the first network to the second network in a routing table;
assigning the route to the service; and
forwarding, from the first network to the second network, the service based on the route.
15 . The non-transitory computer readable storage medium of claim 14 , the operations further comprising configuring the service to be redistributable in a single direction from the first network across the one or more boundaries towards the second network.
16 . The non-transitory computer readable storage medium of claim 15 , the operations further comprising:
receiving, in the node, a different packet from a different host for the service, wherein the packet has a destination across the one or more boundaries from the second network to the first network;
discarding the packet at the node based on the service being redistributable in the single direction from the first network across the one or more boundaries towards the second network.
17 . The non-transitory computer readable storage medium of claim 14 , the operations further comprising configuring the service to be redistributable in a first direction from the first network across the one or more boundaries towards the second network and in a second direction from the second network across the one or more boundaries towards the first network.
18 . The non-transitory computer readable storage medium of claim 14 , the operations further comprising:
receiving, at a boundary node on at least one of the one or more boundaries, the route from a control plane for the multi-area network, wherein the control plane generated the route based on the service being configured to be at least one of:
redistributable in a first direction from the first network across the one or more boundaries towards the second network and in a second direction from the second network across the one or more boundaries towards the first network; and
redistributable in a direction from the first network across the one or more boundaries towards the second network; and
installing the route in the routing table for the boundary node.
19 . The non-transitory computer readable storage medium of claim 14 , the operations further comprising configuring the boundary node as a virtual node.
20 . The non-transitory computer readable storage medium of claim 14 , the operations further comprising:
redistributing, from the node, the route from the first network across at least one of the one or more boundaries to a different boundary node in a different network; and
updating a different routing table for the different boundary node by installing the route in the different routing table.