Abstract: Multicast error detection and recovery may be provided. A join request for a multicast stream may be sent from a first network node to a second network node. The join request may be sent over a first link of a plurality of links between the first network node and the second network node. A redirect message indicating that the second network node cannot accommodate the join request may be received by the first network node from the second network node. In response to receiving the redirect message, the join request for the multicast stream may not be sent on a second link of the plurality of links by the first network node to the second network node. And in response to receiving the redirect message, an alternate upstream network node may be determined by the first network node to send the join request for the multicast stream to.

Abstract: Multicast error detection and recovery may be provided. A join request for a multicast stream may be sent from a first network node to a second network node. The join request may be sent over a first link of a plurality of links between the first network node and the second network node. A redirect message indicating that the second network node cannot accommodate the join request may be received by the first network node from the second network node. In response to receiving the redirect message, the join request for the multicast stream may not be sent on a second link of the plurality of links by the first network node to the second network node. And in response to receiving the redirect message, an alternate upstream network node may be determined by the first network node to send the join request for the multicast stream to.

Abstract: In one illustrative example, a multicast traceroute facility for a plurality of interconnected router nodes which are configured to communicate IP multicast traffic amongst hosts is described. The multicast traceroute facility may be for use in processing a multicast traceroute batch query packet which indicates a batch of multicast traceroute queries of a batch query, for identifying a plurality of traced paths for a batch of IP multicast traffic flows. Each identified traced path may be associated with one or more links, each of which has a link metric that satisfies a requested link metric (e.g. a link bandwidth). Resources for satisfying the requested link metric may be reserved for a predetermined or specified time period. The batch of IP multicast traffic flows may be established via at least some of the interconnected router nodes according to the plurality of traced paths identified from the query packet processing.

Abstract: In service flow capability updating in a guaranteed bandwidth multicast network may be provided. First, a node may determine that a bandwidth requirement of a flow has changed to a new bandwidth value. Then, in response to determining that the bandwidth requirement of the flow has changed to the new bandwidth value, an ingress capacity value may be updated in an interface usage table for a Reverse Path Forwarding (RPF) interface corresponding to the flow. The RPF interface may be disposed on a network device. Next, in response to determining that the bandwidth requirement of the flow has changed to the new bandwidth value, an egress capacity value may be updated in the interface usage table for an Outgoing Interface (OIF) corresponding to the flow. The OIF may be disposed on the network device.

Abstract: In one illustrative example, a switch for use in a network fabric which includes a plurality on interconnected switches configured to facilitate communication of IP multicast traffic amongst host devices may be provided. The switch may receive, from a controller, a global set of host policies associated with the plurality of switches of the network fabric. The switch may select, from the global set of host policies, a local subset of host policies applicable to the switch. The switch may grant or deny admission of host devices to receive or send IP multicast traffic flows in the network fabric according to the selected, local subset of host policies.

Abstract: In one example embodiment, a network node of a plurality of network nodes in a multicast path is configured to provide a multicast flow from a source of the multicast flow to a receiver of the multicast flow. The network node obtains, from the receiver in a reverse direction of the multicast path, configuration instructions specifying a configuration of the multicast flow. The network node implements the configuration of the multicast flow in accordance with the configuration instructions, and provides the configuration instructions toward the source in the reverse direction of the multicast path.

Abstract: In one illustrative example, an IP network media data router includes a spine and leaf switch architecture operative to provide IP multicast delivery of media data from source devices to receiver devices without the overhead communication with a controller. The architecture can include K spine switches, K sets of L leaf switches, M data links between each leaf switch, and a plurality of bidirectional data ports connected to each leaf switch for a guaranteed non-blocking IP multicast delivery of data. A deterministic hash function a used on both the first hop router and the last hop router to ensure the same spine node is selected for flow stitching. Accordingly, without the extra communication with a centralized controller, the right spine for establishing a multicast flow can be chosen using the deterministic hash function and the distributed resource information stored on each node.

Abstract: In one example embodiment, a network node of a plurality of network nodes in a multicast path is configured to provide a multicast flow from a source of the multicast flow to a receiver of the multicast flow. The network node obtains, from the receiver in a reverse direction of the multicast path, configuration instructions specifying a configuration of the multicast flow. The network node implements the configuration of the multicast flow in accordance with the configuration instructions, and provides the configuration instructions toward the source in the reverse direction of the multicast path.

Abstract: In one illustrative example, an IP network media data router includes a spine and leaf switch architecture operative to provide IP multicast delivery of media data from source devices to receiver devices without the overhead communication with a controller. The architecture can include K spine switches, K sets of L leaf switches, M data links between each leaf switch, and a plurality of bidirectional data ports connected to each leaf switch for a guaranteed non-blocking IP multicast delivery of data. A deterministic hash function a used on both the first hop router and the last hop router to ensure the same spine node is selected for flow stitching. Accordingly, without the extra communication with a centralized controller, the right spine for establishing a multicast flow can be chosen using the deterministic hash function and the distributed resource information stored on each node.