Preventing traffic flooding to the root of a multi-point to multi-point label-switched path tree with no receivers

• US 8,804,718 B2
• Filed: 04/23/2008
• Issued: 08/12/2014
• Est. Priority Date: 04/23/2008
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Wijnands, IJsbrand, Boers, Arjen
• Primary Examiner(s): Cho, Un C
• Assistant Examiner(s): COSTIN, JEREMY M
• Application Number:
  US12/108,197
• Publication Number:
  US 20090271467A1
• Time in Patent Office: 2,302 Days
• Field of Search: 370/390, 370/400, 370/432, 370/270, 370/312, 709220-221, 709227-229, 725/118
• US Class Current: 370/390
• CPC Class Codes: H04L 12/1886 with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/48 Routing tree calculation
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]

Abstract

A method is provided for pruning an MP2MP tree. The method includes (a) in a first node of an MP2MP LSP tree, the MP2MP LSP tree including a plurality of nodes, determining whether the first node has only a single replication branch for the MP2MP LSP tree, the single replication branch representing a downstream path to only a second node of the plurality of nodes, (b) in response to determining that the first node has only a single replication branch for the MP2MP LSP tree, sending a message to the second node indicating that the second node should refrain from sending upstream traffic towards the first node, and (c) in response to determining that the first node does not have only a single replication branch for the MP2MP LSP tree, refraining from sending a message to the second node indicating that the second node should refrain from sending upstream traffic of the MP2MP LSP tree towards the first node. Apparatus are also provided for use in practicing certain embodiments.

Claims

1. A method comprising:

in a first node of a multipoint-to-multipoint (MP2MP) label switched path (LSP) tree, the MP2MP LSP tree including a plurality of nodes, upon receiving a withdraw message from a third node, determining whether the first node has only a single replication branch for the MP2MP LSP tree, the single replication branch representing a downstream path to only a second node of the plurality of nodes;

in response to determining that the first node has only the single replication branch for the MP2MP LSP tree, sending a message to the second node indicating that the second node should refrain from sending upstream traffic of the MP2MP LSP tree towards the first node, thereby preventing forwarding of upstream traffic for the MP2MP LSP tree to the first node; and

in response to determining that the first node has more than one replication branch for the MP2MP LSP tree, refraining from sending the message to the second node indicating that the second node should refrain from sending upstream traffic of the MP2MP LSP tree towards the first node.

2. The method of claim 1 wherein the method further comprises:

subsequently determining, in the first node, whether the first node has a second replication branch for the MP2MP LSP tree, the second replication branch representing a path to the third node of the plurality of nodes;

in response to determining that the first node has a second replication branch for the MP2MP LSP tree, sending a message to the second node indicating that the second node should henceforth send upstream traffic towards the first node; and

in response to determining that the first node does not have a second replication branch for the MP2MP LSP tree, refraining from sending a message to the second node indicating that the second node should henceforth send upstream traffic towards the first node.

3. The method of claim 2:

wherein the method further comprises in response to determining that the first node has only the single replication branch for the MP2MP LSP tree, storing connection information for the second node in memory; and

wherein sending the message to the second node indicating that the second node should henceforth send upstream traffic towards the first node includes retrieving the connection information for the second node from memory.

4. The method of claim 2 wherein determining whether the first node has the second replication branch is performed in response to receiving, at the first node, a request for a label mapping.

5. The method of claim 1 wherein determining whether the first node has only a single replication branch is performed in response to receiving, at the first node, the withdraw message indicating that the first node should refrain from sending traffic towards the third node of the plurality of nodes.

6. A first node comprising:

a plurality of network interfaces; and

a controller, the controller being constructed and arranged to;

upon receiving a withdraw message from a third node within a multipoint-to-multipoint (MP2MP) label switched path (LSP) tree including a plurality of nodes, determine whether the first node of the MP2MP (LSP) tree has only a single replication branch for the MP2MP LSP tree, the single replication branch representing a downstream path to only a second node of the plurality of nodes;

in response to determining that the first node has only the single replication branch for the MP2MP LSP tree, send a message over a network interface of the plurality of network interfaces to the second node indicating that the second node should refrain from sending upstream traffic towards the first node, thereby preventing forwarding of upstream traffic for the MP2MP LSP tree to the first node; and

in response to determining that the first node has more than one replication branch for the MP2MP LSP tree, refrain from sending the message over a network interface of the plurality of network interfaces to the second node indicating that the second node should refrain from sending upstream traffic towards the first node.

7. The first node of claim 6 wherein the controller is further constructed and arranged to:

subsequently determine whether the first node has a second replication branch for the MP2MP LSP tree, the second replication branch representing a path to the third node of the plurality of nodes;

in response to determining that the first node has a second replication branch for the MP2MP LSP tree, send a message to the second node indicating that the second node should henceforth send upstream traffic towards the first node; and

in response to determining that the first node does not have a second replication branch for the MP2MP LSP tree, refrain from sending a message to the second node indicating that the second node should henceforth send upstream traffic towards the first node.

8. The first node of claim 7 wherein:

the first node further includes memory;

the controller is further constructed and arranged to in response to determining whether the first node has only the single replication branch for the MP2MP LSP tree, store connection information for the second node in the memory; and

the controller, when sending the message to the second node indicating that the second node should henceforth send upstream traffic towards the first node, is constructed and arranged to retrieve the connection information for the second node from the memory.

9. The first node of claim 7 wherein the controller is constructed and arranged to determine whether the first node has a second replication branch in response to receiving, over a network interface of the plurality of network interfaces, a request for a label mapping.

10. The first node of claim 6 wherein the controller is constructed and arranged to determine whether the first node has only a single replication branch in response to receiving, over a network interface of the plurality of network interfaces, the withdraw message indicating that the first node should refrain from sending traffic towards the third node of the plurality of nodes.

11. The first node of claim 6 wherein the controller is a microprocessor programmed to perform the claimed operations.

12. The first node of claim 6 wherein the controller is a set of circuitry configured to perform the claimed operations.