Abstract: According to certain embodiments, a method by a router in a software-defined wide- area network (SDWAN) includes determining one or more replicators in the SDWAN and generating a multicast distribution tree that includes the determined one or more replicators. The method further includes receiving multicast traffic from a source and creating a (S,G) route for the received multicast traffic. The method further includes replicating the multicast traffic using the multicast distribution tree.

Abstract: According to certain embodiments, a method by a router in a software-defined wide-area network (SDWAN) includes determining one or more replicators in the SDWAN and generating a multicast distribution tree that includes the determined one or more replicators. The method further includes receiving multicast traffic from a source and creating a (S,G) route for the received multicast traffic. The method further includes replicating the multicast traffic using the multicast distribution tree.

Abstract: The present disclosure is directed to a centralized control policy for multicast replicator selection.

Abstract: According to certain embodiments, a router comprises one or more processors and one or more computer-readable non-transitory storage media. The one or more computer-readable non-transitory storage media comprise instructions that, when executed by the one or more processors, cause one or more components of the router to perform operations comprising determining an occurrence of one or more network events associated with a multicast service, generating route exchange information associated with the multicast service locally by the router based on the one or more network events, and using the route exchange information locally to configure the router.

Abstract: According to certain embodiments, a method by a router in a software-defined wide-area network (SDWAN) includes determining one or more replicators in the SDWAN and generating a multicast distribution tree that includes the determined one or more replicators. The method further includes receiving multicast traffic from a source and creating a (S,G) route for the received multicast traffic. The method further includes replicating the multicast traffic using the multicast distribution tree.

Abstract: The present disclosure is directed to a centralized control policy for multicast replicator selection.

Abstract: The present disclosure is directed to systems and methods for auto-provisioning hubs and spokes in a SD-WAN network, and includes the performance of operations and/or the steps of receiving first information from a first network hub, the first network hub one of a plurality of network hubs, the first information indicating a first set of properties associated with the first network hub; publishing the first information to a plurality of network spokes, the plurality of network spokes determining whether to subscribe to the first network hub based on the first information; receiving subscription information from a first network spoke of the plurality of network spokes, the subscription information indicating the first network spoke subscribing to the first network hub; and creating at least one dynamic control policy to establish a forwarding path for the first network spoke through the first network hub.

Abstract: The present disclosure is directed to a centralized control policy for multicast replicator selection.

Abstract: The present disclosure is directed to a centralized control policy for multicast replicator selection.

Abstract: The present disclosure is directed to systems and methods for auto-provisioning hubs and spokes in a SD-WAN network, and includes the performance of operations and/or the steps of receiving first information from a first network hub, the first network hub one of a plurality of network hubs, the first information indicating a first set of properties associated with the first network hub; publishing the first information to a plurality of network spokes, the plurality of network spokes determining whether to subscribe to the first network hub based on the first information; receiving subscription information from a first network spoke of the plurality of network spokes, the subscription information indicating the first network spoke subscribing to the first network hub; and creating at least one dynamic control policy to establish a forwarding path for the first network spoke through the first network hub.

Abstract: Techniques for updating a routing table based on a single message are described. One technique includes receiving at a first network device a node message from a second network device. The node message includes a sequence number and a list of link state(s) originated by the second network device. The first network device determines whether to withdraw one or more link states originated by the second network device and maintained in a routing table of the first network device based on the sequence number and the list of the link state(s) within the node message. The routing table is updated based on the determinations.

Abstract: Techniques for updating a routing table based on a single message are described. One technique includes receiving at a first network device a node message from a second network device. The node message includes a sequence number and a list of link state(s) originated by the second network device. The first network device determines whether to withdraw one or more link states originated by the second network device and maintained in a routing table of the first network device based on the sequence number and the list of the link state(s) within the node message. The routing table is updated based on the determinations.

Abstract: Aspects of the embodiments are directed to synchronizing at least a portion of a link-state database. A network element can lose an adjacency. The network element can transmit a request to a neighboring network element for synchronization of a link-state database. The request can include a version number of a last synchronized link-state database from the neighboring network element. The neighboring network element can determine whether the version of the link-state database is greater than or less than a copy of the link-state database stored by the neighboring network element. If the requested version number is less than the neighboring network element's link-state database version number, then the neighboring network element can send changes to the link-state database since the requested link-state database version number.

Abstract: Various systems and methods for bypassing one or more non-capable nodes. For example, one method involves a capable node determining that an adjacent node is non-capable, where capable nodes are configured to implement a data plane capability and non-capable nodes are not. The method then involves identifying a downstream node that is capable. The downstream node is on a shortest path. The method also involves generating information that identifies a tunnel to the downstream node.

Abstract: Various systems and methods for bypassing one or more non-capable nodes. For example, one method involves a capable node determining that an adjacent node is non-capable, where capable nodes are configured to implement a data plane capability and non-capable nodes are not. The method then involves identifying a downstream node that is capable. The downstream node is on a shortest path. The method also involves generating information that identifies a tunnel to the downstream node.

Abstract: In one embodiment, a first router determines whether an interface coupling the first router to one or more second routers is transit-only. When the interface is transit-only, the first router generates an Open Shortest Path First (OSPF) Link State Advertisement (LSA) that includes an address for the interface and a designated network mask. The designated network mask operates as a transit-only identification that indicates the address should not be installed in a Routing Information Base (RIB) upon receipt of the OSPF LSA at the one or more second routers. When the network is not transit-only, the first router generates an OSPF LSA that includes the address for the interface but does not include the designated network mask, to permit installation of the address in a RIB upon receipt of the OSPF LSA at the one or more second routers.

Abstract: Various systems and methods for bypassing one or more non-capable nodes. For example, one method involves a capable node determining that an adjacent node is non-capable, where capable nodes are configured to implement a data plane capability and non-capable nodes are not. The method then involves identifying a downstream node that is capable. The downstream node is on a shortest path. The method also involves generating information that identifies a tunnel to the downstream node.

Abstract: Various systems and methods for bypassing one or more non-capable nodes. For example, one method involves a capable node determining that an adjacent node is non-capable, where capable nodes are configured to implement a data plane capability and non-capable nodes are not. The method then involves identifying a downstream node that is capable. The downstream node is on a shortest path. The method also involves generating information that identifies a tunnel to the downstream node.

Abstract: Various systems and methods for bypassing one or more non-capable nodes. For example, one method involves a capable node determining that an adjacent node is non-capable, where capable nodes are configured to implement a data plane capability and non-capable nodes are not. The method then involves identifying a downstream node that is capable. The downstream node is on a shortest path. The method also involves generating information that identifies a tunnel to the downstream node.

Abstract: Aspects of the embodiments are directed to synchronizing at least a portion of a link-state database. A network element can lose an adjacency. The network element can transmit a request to a neighboring network element for synchronization of a link-state database. The request can include a version number of a last synchronized link-state database from the neighboring network element. The neighboring network element can determine whether the version of the link-state database is greater than or less than a copy of the link-state database stored by the neighboring network element. If the requested version number is less than the neighboring network element's link-state database version number, then the neighboring network element can send changes to the link-state database since the requested link-state database version number.