Abstract: This disclosure describes techniques for improving convergence of Protocol Independent Multicast assert state information in multicast groups. A method includes forwarding, by a router, a PIM join message originating from a destination host and stores distribution tree information based on the join message. The method further includes participating, by the router, in a Protocol Independent Multicast (“PIM”) assert election among a plurality of routers and storing, by the router, PIM assert state information based on an outcome of the PIM assert election. The method further includes acquiring, by the router, routing information base (“RIB”) convergence. The method further includes triggering by the router, or causing, by the router, another router to trigger, a PIM assert among the plurality of routers. The method further includes re-converging, by the router, with PIM assert states among the plurality of routers and storing, by the router, converged PIM assert state information.

Abstract: This disclosure describes techniques for improved multicast network telemetry implemented over multilayer switches in a PIM domain. The multilayer switches may be configured to collectively certify end-to-end flow provisioning, and to publish telemetry data certifying flow provisioning from a single notifier to an external controller host. Computational workload and network traffic for streaming data related to certifying path provisioning is kept to a minimum for each flow that needs to be certified, which also keeps compounding of network traffic for many different flows to a minimum. Moreover, since controller hosts are notified upon successful provisioning but not at other times, controller hosts can trust that the telemetric data is minimally latent, and may be relied upon to enact timely actions which produce desired outcomes.

Abstract: A router node may be configured for communication of multicast traffic in a network fabric which may include a plurality of spine nodes interconnected to a plurality of leaf nodes. The router node may be configured as one of the leaf nodes and serve as a first hop router for multicast traffic. At the router node, a message for flooding the network fabric may be sent based on an indication of communication of multicast traffic for a multicast group from a source device. The message may include at least one spine node identifier of at least one preferred spine node joined to the multicast group at the router node. The message may be for indicating, to at least one of the leaf nodes, to prioritize joining to the multicast group at the at least one preferred spine node according to at least one spine node identifier.

Abstract: In one illustrative example, a network node connected in a network fabric may identify that it is established as part of a multicast distribution tree for forwarding multicast traffic from a source node to one or more host receiver devices of a multicast group. In response, the network node may propagate in the network fabric a message for advertising the network node as a candidate local source node at which to join the multicast group. The message for advertising may include data such as a reachability metric. The propagation of the message may be part of a flooding of such messages in the network fabric. The network node serving as the candidate local source node may thereafter “locally” join a host receiver device in the multicast group at the network node so that the device may receive the multicast traffic from the source node via the network node.

Abstract: This disclosure describes techniques for improved multicast network telemetry implemented over multilayer switches in a PIM domain. The multilayer switches may be configured to collectively certify end-to-end flow provisioning, and to publish telemetry data certifying flow provisioning from a single notifier to an external controller host. Computational workload and network traffic for streaming data related to certifying path provisioning is kept to a minimum for each flow that needs to be certified, which also keeps compounding of network traffic for many different flows to a minimum. Moreover, since controller hosts are notified upon successful provisioning but not at other times, controller hosts can trust that the telemetric data is minimally latent, and may be relied upon to enact timely actions which produce desired outcomes.

Abstract: This disclosure describes techniques for improving convergence of Protocol Independent Multicast assert state information in multicast groups. A method includes forwarding, by a router, a PIM join message originating from a destination host and stores distribution tree information based on the join message. The method further includes participating, by the router, in a Protocol Independent Multicast (“PIM”) assert election among a plurality of routers and storing, by the router, PIM assert state information based on an outcome of the PIM assert election. The method further includes acquiring, by the router, routing information base (“RIB”) convergence. The method further includes triggering by the router, or causing, by the router, another router to trigger, a PIM assert among the plurality of routers. The method further includes re-converging, by the router, with PIM assert states among the plurality of routers and storing, by the router, converged PIM assert state information.

Abstract: Techniques for improving convergence of Protocol Independent Multicast assert state information in multicast groups include forwarding, by a router, a PIM join message originating from a destination host and stores distribution tree information based on the join message. The method further includes participating, by the router, in a Protocol Independent Multicast (“PIM”) assert election among a plurality of routers and storing, by the router, PIM assert state information based on an outcome of the PIM assert election. The method further includes acquiring, by the router, routing information base (“RIB”) convergence. The method further includes triggering by the router, or causing, by the router, another router to trigger, a PIM assert among the plurality of routers. The method further includes re-converging, by the router, with PIM assert states among the plurality of routers and storing, by the router, converged PIM assert state information.

Abstract: In one embodiment, a first networking device associated with a switched network comprises one or more processors and one or more computer-readable media storing computer-executable instructions that, when executed, cause the one or more processors to perform acts comprising configuring, on the first networking device, a network-address-translation (NAT) rule indicating that a first multicast group is to be translated to a second multicast group. The acts further include, at least partly in response to the configuring of the NAT rule, storing the NAT rule at the first networking device, generating a message indicating the NAT rule, and sending the message to at least a second networking device associated with the switched network.

Abstract: In one embodiment, a first networking device associated with a switched network comprises one or more processors and one or more computer-readable media storing computer-executable instructions that, when executed, cause the one or more processors to perform acts comprising configuring, on the first networking device, a network-address-translation (NAT) rule indicating that a first multicast group is to be translated to a second multicast group. The acts further include, at least partly in response to the configuring of the NAT rule, storing the NAT rule at the first networking device, generating a message indicating the NAT rule, and sending the message to at least a second networking device associated with the switched network.

Abstract: A method includes identifying within a network topology, by an apparatus, a plurality of network devices; and establishing by the apparatus, a multiple tree topology comprising a first multicast tree and a second multicast tree, the first and second multicast trees operable as redundant trees for multicast traffic in the network topology, the establishing including: allocating a first of the network devices as a corresponding root of the first multicast tree, allocating a first group of intermediate devices from the network devices as first forwarding devices in the first multicast tree, allocating a second group of intermediate devices as belonging to first leaf devices in the first multicast tree, and allocating terminal devices of the network devices as belonging to the first leaf devices, and allocating a second of the network devices as the corresponding root of the second multicast tree, allocating the second group of intermediate devices as second forwarding devices in the second multicast tree, alloca

Abstract: This disclosure describes techniques for improving convergence of Protocol Independent Multicast assert state information in multicast groups. A method includes forwarding, by a router, a PIM join message originating from a destination host and stores distribution tree information based on the join message. The method further includes participating, by the router, in a Protocol Independent Multicast (“PIM”) assert election among a plurality of routers and storing, by the router, PIM assert state information based on an outcome of the PIM assert election. The method further includes acquiring, by the router, routing information base (“RIB”) convergence. The method further includes triggering by the router, or causing, by the router, another router to trigger, a PIM assert among the plurality of routers. The method further includes re-converging, by the router, with PIM assert states among the plurality of routers and storing, by the router, converged PIM assert state information.

Abstract: A router node may be configured for communication of multicast traffic in a network fabric which may include a plurality of spine nodes interconnected to a plurality of leaf nodes. The router node may be configured as one of the leaf nodes and serve as a first hop router for multicast traffic. At the router node, a message for flooding the network fabric may be sent based on an indication of communication of multicast traffic for a multicast group from a source device. The message may include at least one spine node identifier of at least one preferred spine node joined to the multicast group at the router node. The message may be for indicating, to at least one of the leaf nodes, to prioritize joining to the multicast group at the at least one preferred spine node according to at least one spine node identifier.

Abstract: A router node may be configured for communication of multicast traffic in a network fabric which may include a plurality of spine nodes interconnected to a plurality of leaf nodes. The router node may be configured as one of the leaf nodes and serve as a first hop router for multicast traffic. At the router node, a message for flooding the network fabric may be sent based on an indication of communication of multicast traffic for a multicast group from a source device. The message may include at least one spine node identifier of at least one preferred spine node joined to the multicast group at the router node. The message may be for indicating, to at least one of the leaf nodes, to prioritize joining to the multicast group at the at least one preferred spine node according to at least one spine node identifier.

Abstract: In one illustrative example, a network node connected in a network fabric may identify that it is established as part of a multicast distribution tree for forwarding multicast traffic from a source node to one or more host receiver devices of a multicast group. In response, the network node may propagate in the network fabric a message for advertising the network node as a candidate local source node at which to join the multicast group. The message for advertising may include data such as a reachability metric. The propagation of the message may be part of a flooding of such messages in the network fabric. The network node serving as the candidate local source node may thereafter “locally” join a host receiver device in the multicast group at the network node so that the device may receive the multicast traffic from the source node via the network node.

Abstract: A router node may be configured for communication of multicast traffic in a network fabric which may include a plurality of spine nodes interconnected to a plurality of leaf nodes. The router node may be configured as one of the leaf nodes and serve as a first hop router for multicast traffic. At the router node, a message for flooding the network fabric may be sent based on an indication of communication of multicast traffic for a multicast group from a source device. The message may include at least one spine node identifier of at least one preferred spine node joined to the multicast group at the router node. The message may be for indicating, to at least one of the leaf nodes, to prioritize joining to the multicast group at the at least one preferred spine node according to at least one spine node identifier.

Abstract: In one illustrative example, a network node connected in a network fabric may identify that it is established as part of a multicast distribution tree for forwarding multicast traffic from a source node to one or more host receiver devices of a multicast group. In response, the network node may propagate in the network fabric a message for advertising the network node as a candidate local source node at which to join the multicast group. The message for advertising may include data such as a reachability metric. The propagation of the message may be part of a flooding of such messages in the network fabric. The network node serving as the candidate local source node may thereafter “locally” join a host receiver device in the multicast group at the network node so that the device may receive the multicast traffic from the source node via the network node.

Abstract: In one embodiment, a method comprises identifying within a network topology, by an apparatus, a plurality of network devices; and establishing by the apparatus, a multiple tree topology comprising a first multicast tree and a second multicast tree, the first and second multicast trees operable as redundant trees for multicast traffic in the network topology, the establishing including: allocating a first of the network devices as a corresponding root of the first multicast tree, allocating a first group of intermediate devices from the network devices as first forwarding devices in the first multicast tree, allocating a second group of intermediate devices as belonging to first leaf devices in the first multicast tree, and allocating terminal devices of the network devices as belonging to the first leaf devices, and allocating a second of the network devices as the corresponding root of the second multicast tree, allocating the second group of intermediate devices as second forwarding devices in the second mu

Abstract: In one illustrative example, a network node connected in a network fabric may identify that it is established as part of a multicast distribution tree for forwarding multicast traffic from a source node to one or more host receiver devices of a multicast group. In response, the network node may propagate in the network fabric a message for advertising the network node as a candidate local source node at which to join the multicast group. The message for advertising may include data such as a reachability metric. The propagation of the message may be part of a flooding of such messages in the network fabric. The network node serving as the candidate local source node may thereafter “locally” join a host receiver device in the multicast group at the network node so that the device may receive the multicast traffic from the source node via the network node.