METHOD FOR PRUNING A MULTICAST BRANCH, PROTOCOL INDEPENDENT MULTICAST ROUTER, AND LAYER-2 EXCHANGE

• US 20130201988A1
• Filed: 09/30/2011
• Published: 08/08/2013
• Est. Priority Date: 09/30/2010
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hangzhou H3C Technologies Co Ltd (Tsinghua Holdings Co., Ltd.)
• Inventors: Zhou, Di, Liu, Yu, Chen, Qianye, Chen, Xusheng
• Granted Patent: US 9,497,034 B2
• Time in Patent Office: Days
• US Class Current: 370/390
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18

Abstract

According to an example, a multicast source may be connected to a first hop Protocol Independent Multicast (PIM) router via one or multiple layer-2 switches that has PIM functions. A first hop PIM router may receive a multicast flow initiated by the multicast source, send a PIM prune message via a port from which the multicast flow is received in response to a determination that the multicast flow is not to be received, or the first hop PIM router may receive a PIM prune message for a multicast flow from a downstream PIM router or a multicast group leave message for a multicast flow from a client connected to the first hop PIM router and delete a port via which the PIM prune message.

Claims

1-9. -9. (canceled)

10. A layer-2 exchange with Protocol Independent Multicast (PIM) snooping functions, for deployment between a multicast source and a first hop PIM router, the layer-2 exchange comprising:

a first module to receive a PIM prune message for a multicast flow, to add a port from which the PIM prune message is received into a PIM snooping entry corresponding to the multicast flow as a prune port and to stop forwarding the multicast flow via the prune port in response to a determination that an upstream neighbor address in the PIM prune message is not in a list of PIM routers that are maintained by PIM snooping functions of the exchange.

11. The exchange of claim 10, wherein the first module is further to set a prune time for the prune port, and to begin forwarding the multicast flow to the prune port when the prune time expires.

12. The exchange of claim 10, wherein the first module is further to set a lifetime value that is smaller than the lifetime value of the multicast routing table entry of the multicast flow corresponding to the PIM prune message in the first hop PIM router;

to set the prune port as a temporary router port when the lifetime value of the prune port expires, and to set the temporary router port as a router port if a PIM prune message for the multicast flow is not received within a pre-defined period of time, or to set the temporary router port as a prune port and reset the lifetime value of the prune port if a PIM prune message for the multicast flow is received.

13. The exchange of claim 10, wherein, the first module is further to, in response to a determination that the upstream neighbor address in the PIM prune message is not in a list of PIM routers using PIM snooping functions of the exchange and a PIM snooping entry has not been established for the multicast flow in the exchange, establish a PIM snooping entry for the multicast flow , to set an empty list as an upstream neighbor list in the PIM snooping entry, to add all ports connected to PIM neighbors except upstream ports into a downstream egress port list in the PIM snooping entry, to perform the adding of the prune port into the PIM snooping entry corresponding to the multicast flow;

and

to determine whether the multicast flow corresponding to the PIM prune message is to be forwarded based on PIM snooping entries and multicast group management entries in the layer-2 exchange, forwarding no PIM prune message if the multicast flow corresponding to the PIM prune message is to be forwarded, or forwarding the PIM prune message in the direction of the multicast source if the multicast flow corresponding to the PIM prune message is not to be forwarded.

14. The exchange of claim 10, wherein the first module is further to directly perform the adding of the prune port into the PIM snooping entry corresponding to the multicast flow in response to a determination that an upstream neighbor address in the PIM prune message is not in a list of PIM routers using PIM snooping functions of the exchange and a PIM snooping entry has been established for the multicast flow in the exchange;

and

to determine whether there the multicast flow corresponding to the PIM prune message is to be forwarded based on PIM snooping entries and multicast group management entries in the layer-2 exchange, forwarding no PIM prune message if the multicast flow corresponding to the PIM prune message is to be forwarded, or forwarding the PIM prune message in the direction of the multicast source if the multicast flow corresponding to the PIM prune message is not to be forwarded.

15. The exchange of claim 10, further comprising:

a second module to receive a PIM join message for a multicast flow;

in response to a determination that the upstream neighbor address in the message is not in a list of PIM routers that are maintained by PIM snooping functions of the exchange, to determine whether there is another port other than the port from which the PIM join message is received is to receive the multicast flow based on PIM snooping entries and multicast group management snooping entries in the exchange in response to a determination that there is a PIM snooping entry for the multicast flow corresponding to the PIM join message in the exchange and the port receiving the PIM join message is a prune port in the PIM snooping entry, to forward no PIM join message when there is another port that is to receive the multicast flow, or to forward the PIM join message in the direction of the multicast source if there is no other port that is to receive the multicast flow.

16. The exchange of claim 15, wherein the second module is further to delete a mark which labels the port from which the PIM join message is received as a prune port and to set the port as a router port, and to delete the PIM snooping entry corresponding to the multicast flow if the downstream egress port list of the PIM snooping entry does not include a prune port and the upstream neighbor list is empty.

17. The exchange of claim 10, further comprising:

a third module to receive a multicast group join message for a multicast flow, to add a port from which the multicast group join message is received into a multicast group management snooping entry corresponding to the multicast flow as a membership port, and to forward the multicast group join message to all router ports, prune ports and upstream neighbors in the PIM snooping entry except the port from which the multicast group join message is received.

18. A method for pruning a multicast branch in a network comprising a multicast source connected to a first hop PIM router via at least one layer-2 exchange with Protocol Independent Multicast (PIM) snooping functions, said method comprising:

receiving, by the first hop PIM router, a multicast flow initiated by the multicast source, sending a PIM prune message via a port from which the multicast flow is received in response to a determination that the multicast flow is not to be received;

or

receiving, by the first hop PIM router, a PIM prune message for a multicast flow from a downstream PIM router or a multicast group leave message for a multicast flow from a client connected to the first hop PIM router, deleting a port via which the PIM prune message or the multicast group leave message is received from an egress port list corresponding to the multicast flow, and sending a PIM prune message addressed to the multicast source via the port from which the multicast flow is received in response to a determination that the multicast flow is not to be received.

19. The method of claim 18, further comprising:

receiving, by one of the at least one layer-2 exchange, the PIM prune message from the first hop PIM router, adding a port from which the PIM prune message is received into a PIM snooping entry corresponding to the multicast flow as a prune port and stopping forwarding of the multicast flow via the prune port when determining an upstream neighbor address in the PIM prune message is not in a list of PIM routers which are maintained by PIM snooping functions of the exchange.

20. A Protocol Independent Multicast (PIM) router, connected to a multicast source via at least one layer-2 exchange, comprising:

a first module to receive a multicast flow initiated by the multicast source, to determine whether the multicast flow is to be received, to send a prune indication to a second module in response to a determination that the multicast flow is not to be received;

or, to receive a PIM prune message for the multicast flow from a downstream PIM router or a multicast group leave message for the multicast flow from a client connected to the PIM router, to delete a port via which the PIM prune message or the multicast group leave message is received from an egress port list corresponding to the multicast flow, to determine whether there the multicast flow is to be received, to send a prune indication to a second module in response to a determination that the multicast flow is not to be received; and

the second module to receive the prune indication, and to send a PIM prune message addressed to the multicast source via the port from which the multicast flow is received.

21. The PIM router of claim 20, wherein when the PIM router adopts PIM-SSM, or adopts PIM-SM and is not a Designated Router (DR), or adopts bi-directional PIM and is not a DR,

the first module comprises:

a first sub module to receive the multicast flow and send information of the multicast flow to a second sub module; and

wherein the second sub module is to receive the information of the multicast flow from the first sub module, to determine that the multicast flow is not to be received and to send the prune indication to the second module in response to a determination that a multicast routing table entry has not been established for the multicast flow in the PIM router or in response to a determination that a multicast routing table entry has been established for the multicast flow but an egress port list of the multicast routing table entry is empty.

22. The PIM router of claim 20, wherein when the PIM router adopts PIM-SM and is a DR,

the first module comprises:

a first sub module to receive the multicast flow and send information of the multicast flow to a second sub module; and

wherein the second sub module is;

to receive the information of the multicast flow from the first sub module, to determine that the multicast flow is not to be received and to send the prune indication to the second module in response to a determination that a multicast routing table entry has been established for the multicast flow but an egress port list of the multicast routing table entry is empty;

or

to determine that the multicast flow is not to be received and to send the prune indication to the second module after receiving a source register stop message from an RP and determining that an egress port list of the multicast routing table entry is empty.

23. The PIM router of claim 20, wherein when the PIM router adopts PIM-DM, the first module comprises:

a first sub module to receive the multicast flow and send information of the multicast flow to a second sub module; and

wherein the second sub module is;

to receive the information of the multicast flow from the first sub module, to determine that the multicast flow is not to be received and to send the prune indication to the second module in response to a determination that a multicast routing table entry has been established for the multicast flow but all egress ports in the multicast routing table entry are prune ports;

or to receive a PIM prune message from a downstream PIM neighbor and to add the port from which the PIM prune message is received into an egress port list of the multicast routing table entry as a prune port;

to receive a PIM graft message from a downstream PIM neighbor and to add the port from which the PIM graft message is received into an egress port list of the multicast routing table entry as a forwarding port;

to determine that the multicast flow is not to be received and to send the prune indication to the second module after determining that all ports connected to the downstream PIM neighbors have been added into the egress port list of the multicast routing table entry and that all egress ports in the multicast routing table entry are prune ports.

24. The PIM router of claim 20, wherein when the PIM router adopts PIM-SM or PIM-SSM, the PIM router further comprises:

a third module to receive a PIM join message for the multicast flow sent by a downstream PIM router, and to send a PIM join message in the direction of the multicast source;

or

when the PIM router adopts PIM-SM or PIM-SSM or PIM-DM, the PIM router further comprises;

a third module to receive a multicast group join message for the multicast flow sent by a client connected to PIM router, and to send a PIM join message in the direction of the multicast source.

25. The PIM router of claim 24, wherein the third module is further to:

determine whether a multicast routing table entry has been established for the multicast flow in the PIM router after receiving the PIM join message from the downstream PIM router or the multicast group join message from the client, to add a port from which the PIM join message or the multicast group join message is received into an egress port list in the multicast routing table entry, and to perform the sending the PIM join message in the direction of the multicast source.

26. The PIM router of claim 20, further comprising:

when the PIM router adopts PIM-SM and is not a DR, or adopts bi-directional PIM and is not a DR,

a fourth module to send a PIM join message in the direction of a multicast source of each multicast flow according to a multicast routing table entry corresponding to the multicast flow when the first hop PIM router was not a DR and becomes a DR.

27. The PIM router of claim 20, further comprising:

when the PIM router adopts PIM-DM,

a fifth module to receive a PIM graft message for the multicast flow from a downstream PIM neighbor, and to send a PIM join message in the direction of the multicast source.

28. The PIM router of claim 27, wherein the fifth module is further to:

determine whether a multicast routing table entry corresponding to the multicast flow has been established in the PIM router after receiving a PIM graft message for the multicast flow from a downstream PIM neighbor, to add the port from which the PIM graft message is received into an egress port list of the multicast routing table entry and to send a PIM join message in the direction of the multicast source when determining the multicast routing table entry has been established and the egress port list of the multicast routing table entry is empty.

29. A method for pruning a multicast branch, said method comprising:

receiving, by a layer-2 exchange, a PIM prune message for a multicast flow;

adding, by the layer-2 exchange, a port from which the PIM prune message is received into a PIM snooping entry corresponding to the multicast flow as a prune port and stopping forwarding the multicast flow via the prune port in response to a determination that an upstream neighbor address in the PIM prune message is not in a list of PIM routers that are maintained by PIM snooping functions of the exchange.

30. The method of claim 29, further comprising:

establishing, by the layer-2 exchange, a PIM snooping entry for the multicast flow in response to a determination that a PIM snooping entry has not been established for the multicast flow in the layer-2 exchange, adding all ports connected to PIM neighbors except upstream ports and prune ports into the PIM snooping entry; and

forwarding, by the layer-2 exchange, the PIM prune message in the direction of the multicast source in response to a determination that the multicast flow corresponding to the PIM prune message is not to be forwarded.

31. The method of claim 29, further comprising:

receiving, by the layer-2 exchange, a PIM join message for a multicast flow;

deleting, by the layer-2 exchange, a mark which labels the port from which the PIM join message is received as a prune port after forwarding the PIM join message in the direction of the multicast source, and labeling the port as a router port;

deleting, by the layer-2 exchange, the PIM snooping table entry corresponding to the multicast flow in response to a determination that the PIM snooping table entry does not include a prune port; and

forwarding, by the layer-2 exchange, the PIM join message in the direction of the multicast source in response to a determination that there is no other port that is to receive the multicast flow.