Virtual multicast routing for a cluster having state synchronization

• US 7,729,350 B2
• Filed: 12/30/2004
• Issued: 06/01/2010
• Est. Priority Date: 12/30/2004
• Status: Expired due to Fees

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia, Inc. (Nokia Corporation)
• Inventors: Singh, Ravi I., Bahadur, Rahul, Hunt, Peter Frederick
• Primary Examiner(s): Wilson; Robert W
• Application Number:
  US11/027,018
• Publication Number:
  US 20060146821A1
• Time in Patent Office: 1,979 Days
• Field of Search: None
• US Class Current: 370/390
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/46 Cluster building

Abstract

A system, apparatus, and method are directed to managing multicast routing using a network cluster. A cluster master actively participates in multicast control protocol communications with the cluster neighbors, while non-master member nodes, do not participate in the protocols'"'"' operation outside of the cluster. However, each cluster member maintains virtually the same protocol state, such that should the master become unavailable, another cluster member may assume the master role with minimum delay. New members to the cluster are synchronized by receiving initial protocol state information from the master. After the initial protocol state synchronization, cluster members actively monitor the network to acquire new protocol state information. In addition, cluster members exchange protocol state information between themselves that may not be obtainable off the network. Filtering of multicast data packets is performed by each cluster member, to load balance multicast data traffic across the cluster members.

Claims

1. A system, comprising:

a first network device configured to operate as a cluster master within a cluster, the first network device being configured to

direct sending of initial protocol state information to a cluster member when the cluster member is joining the cluster,

direct sending of a multicast control protocol packet to at least one network device external to the cluster,

receive a multicast data packet, and

direct forwarding of the multicast data packet towards a destination when the first network device is associated with the multicast data packet; and

a second network device configured to operate as the cluster member within the cluster, the second network device being configured to

receive the initial protocol state information from the first network device during a joining of the second network device to the cluster,

monitor the network for additional protocol state information,

employ the additional protocol state information to update a state of the second network device when additional protocol state information is received,

receive a multicast data packet,

direct forwarding of the multicast data packet towards a destination when the second network device is associated with the multicast data packet,

receive a multicast control protocol packet from the at least one network device external to the cluster, and

drop the multicast control protocol packet rather than responding to the multicast control protocol packet.

2. The system of claim 1, wherein one of the first network device and the second network device is further configured to

direct sending of a second multicast protocol state to a third network device within the cluster when the second multicast protocol state is known by the one of the first network device and the second network device and is unobtainable by the third network device within the cluster by monitoring the multicast protocol state.

3. The system of claim 2, wherein, when at least one of the first network device and the second network device fails, the other network device within the cluster assumes a workload and role of the failed network device using, at least in part, the sent second multicast protocol state.

4. The system of claim 1, wherein the second network device is further configured to determine whether the second network device is load-balanced to manage the multicast data packet when the second network device is associated with the multicast data packet.

5. The system of claim 1, wherein each of the first network device and the second network device employs a load-balancing mechanism selected from at least one of a round trip time load-balancing mechanism, a round robin load-balancing mechanism, a least connections load-balancing mechanism, a packet completion rate load-balancing mechanism, a quality of service load-balancing mechanism, a cluster topology load-balancing mechanism, a global availability load-balancing mechanism, a hops load-balancing mechanism, a hash load-balancing mechanism, a static ratios load-balancing mechanism, and a dynamic ratios load-balancing mechanism.

6. An apparatus comprising at least one processor and at least one memory including computer readable instructions, the at least one memory and the computer readable instructions configured to, with the at least one processor, cause the apparatus at least to:

selectably direct configuring of the apparatus to operate as either a member or as a master within a cluster, wherein the selection is based on the needs of the cluster,

monitor the network for protocol state information,

employ the protocol state information to update a state of the apparatus when the apparatus receives protocol state information,

receive a multicast control protocol message,

direct responding to the multicast control protocol message when the apparatus is a cluster master,

drop the multicast control protocol message rather than responding to the multicast control protocol message when the apparatus is other than the cluster master,

receive a multicast data packet, and

direct forwarding of the multicast data packet towards a destination when the apparatus is associated with the multicast data packet.

7. The apparatus of claim 6, wherein the apparatus is further caused to direct forwarding of the multicast data packet towards a resident application when the apparatus includes the resident application associated with the multicast data packet.

8. The apparatus of claim 6, wherein, when employing the additional protocol state information, the apparatus is further caused to send self protocol state information to a network device within the cluster.

9. The apparatus of claim 6, wherein the apparatus is further caused to determine whether the apparatus is load-balanced to manage the multicast data packet.

10. The apparatus of claim 6, wherein the apparatus is further caused to receive initial protocol state information from the cluster master during a joining of the cluster.

11. The apparatus of claim 6, wherein the apparatus is further caused to drop the multicast data packet when the apparatus is unassociated with the multicast data packet.

12. A method, comprising:

directing sending of initial protocol state information to a cluster member when the cluster member is joining the cluster;

directing sending, from a cluster master, of a first multicast control protocol packet to at least one network device external to the cluster;

receiving a second multicast control protocol packet from the external network device;

dropping the second multicast control protocol packet when the second multicast control protocol packet is received by the cluster member;

monitoring the network for additional protocol state information;

employing the additional protocol state information to update a state of the cluster member when additional protocol state information is received;

receiving a multicast data packet;

directing forwarding of the multicast data packet towards a destination when the cluster member is associated with the multicast data packet, receiving a multicast control protocol packet from the at least one network device external to the cluster; and

dropping the multicast control protocol packet rather than responding to the multicast control protocol packet.

13. The method of claim 12, wherein the cluster member is configured to determine whether the cluster member is load-balanced to manage the multicast data packet when the cluster member is associated with the multicast data packet.

14. The method of claim 13, wherein the cluster member is configured to employ a load-balancing mechanism selected from at least one of a round trip time load-balancing mechanism, a round robin load-balancing mechanism, a least connections load-balancing mechanism, a packet completion rate load-balancing mechanism, a quality of service load-balancing mechanism, a cluster topology load-balancing mechanism, a global availability load-balancing mechanism, a hops load-balancing mechanism, a hash load-balancing mechanism, a static ratios load-balancing mechanism, and a dynamic ratios load-balancing mechanism.

15. The method of claim 12, further comprising:

directing sending of the second multicast protocol state to another cluster member when the second multicast protocol state known by one of the cluster master and the cluster member is unobtainable by the other cluster member by monitoring the multicast protocol state.

16. The method of claim 15, wherein, when one of the cluster master and the cluster member fail, the other cluster member is configured to assume a workload and role of the failed one of the cluster master and the cluster member.

17. The method of claim 12, further comprising:

directing forwarding of the multicast data packet towards a resident application if the cluster member includes the resident application associated with the multicast data packet.

18. The method of claim 12, wherein the employing of the additional protocol state information to update the state of the cluster member further comprises updating at least one of a routing table and a filter application.

19. An apparatus, comprising:

means for selectably directing configuring of the apparatus to operate as either a member or as a master within a cluster, wherein the selection is based on the needs of the cluster;

means for monitoring a network for protocol state information;

employing means for employing the protocol state information to update a state of the apparatus when protocol state information is received;

first means for receiving a multicast control protocol message;

responding means for responding to the multicast control protocol message when the apparatus is a cluster master;

means for dropping the multicast control protocol message rather than responding to the multicast control protocol message when the network device is other than the cluster master;

second means for receiving a multicast data packet; and

means for forwarding the multicast data packet towards a destination when the apparatus is associated with the multicast data packet.

20. A method, comprising:

selectably directing configuring a network device to operate as either a member or as a master within a cluster, wherein the selection is based on the needs of the cluster;

monitoring a network for protocol state information;

employing the protocol state information to update a state of the network device when protocol state information is received;

receiving a multicast control protocol message;

directing responding to the multicast control protocol message when the network device is a cluster master;

dropping the multicast control protocol message rather than responding to the multicast control protocol message when the network device is other than the cluster master;

receiving a multicast data packet; and

directing forwarding of the multicast data packet towards a destination when the network device is associated with the multicast data packet.

21. The method of claim 20, further comprising:

directing forwarding of the multicast data packet towards a resident application when the network device includes the resident application associated with the multicast data packet.

22. The method of claim 20, wherein, when employing the additional protocol state information, the method further comprises sending self protocol state information to another network device within the cluster.

23. The method of claim 20, further comprising:

determining whether the network device is load-balanced to manage the multicast data packet.

24. The method of claim 20, further comprising:

receiving initial protocol state information from the cluster master during a joining of the cluster.

25. The method of claim 20, further comprising:

dropping the multicast data packet when the network device is unassociated with the multicast data packet.

26. A memory having a computer program embodied thereon , the program configured to control a processor to perform a process, the process comprising:

selectably directing configuring of a network device to operate as either a member or as a master within a cluster, wherein the selection is based on the needs of the cluster;

monitoring a network for protocol state information;

employing the protocol state information to update a state of the network device when protocol state information is received;

receiving a multicast control protocol message;

directing responding to the multicast control protocol message when the network device is a cluster master;

dropping the multicast control protocol message rather than responding to the multicast control protocol message when the network device is other than the cluster master;

receiving a multicast data packet; and

directing forwarding of the multicast data packet towards a destination when the network device is associated with the multicast data packet.

27. The memory of claim 26, the process further comprising:

directing forwarding of the multicast data packet towards a resident application when the network device includes the resident application associated with the multicast data packet.

28. The memory of claim 26, wherein, when employing the additional protocol state information, the process further comprises controlling the processor to sending self protocol state information to another network device within the cluster.

29. The memory of claim 26, the process further comprising:

determining whether the network device is load-balanced to manage the multicast data packet.

30. The memory of claim 26, the process further comprising:

receiving initial protocol state information from the cluster master during a joining of the cluster.

31. The memory of claim 26, the process further comprising:

dropping the multicast data packet when the network device is unassociated with the multicast data packet.

32. An apparatus comprising at least one processor and at least one memory including computer readable instructions, the at least one memory and the computer readable instructions configured to, with the at least one processor, cause the apparatus at least to:

receive initial protocol state information from a cluster master during a joining of the apparatus to the cluster,

monitor the network for additional protocol state information,

employ the additional protocol state information to update a state of the apparatus when additional protocol state information is received,

receive a multicast data packet,

direct forwarding of the multicast data packet towards a destination when the apparatus is associated with the multicast data packet,

receive a multicast control protocol packet from at least one network device external to the cluster, and

drop the multicast control protocol packet rather than responding to the multicast control protocol packet.

33. The apparatus of claim 32, wherein the apparatus is further caused to initiate sending of a second multicast protocol state to another network device within the cluster when the second multicast protocol state is known by the one of the cluster master and the apparatus and is unobtainable by the third network device within the cluster by monitoring the multicast protocol state.

34. The apparatus of claim 33, wherein, when the apparatus fails, a network device other than the apparatus within the cluster assumes a workload and role of the apparatus using, at least in part, the sent second multicast protocol state.

35. The apparatus of claim 32, wherein the apparatus is further caused to determine whether the apparatus is load-balanced to manage the multicast data packet when the apparatus is associated with the multicast data packet.

36. The apparatus of claim 32, wherein the apparatus is caused to employ a load-balancing mechanism selected from at least one of a round trip time load-balancing mechanism, a round robin load-balancing mechanism, a least connections load-balancing mechanism, a packet completion rate load-balancing mechanism, a quality of service load-balancing mechanism, a cluster topology load-balancing mechanism, a global availability load-balancing mechanism, a hops load-balancing mechanism, a hash load-balancing mechanism, a static ratios load-balancing mechanism, and a dynamic ratios load-balancing mechanism.

37. A method, comprising:

receiving initial protocol state information from a cluster master during a joining of a cluster member to the cluster;

monitoring the network for additional protocol state information;

employing the additional protocol state information to update a state of the cluster member when additional protocol state information is received;

receiving a multicast data packet;

directing forwarding of the multicast data packet towards a destination when the cluster member is associated with the multicast data packet;

receiving a multicast control protocol packet from at least one network device external to the cluster; and

dropping the multicast control protocol packet rather than responding to the multicast control protocol packet.

38. The method of claim 37, further comprising:

directing sending of a second multicast protocol state to another network device within the cluster when the second multicast protocol state is known by the one of the cluster master and the cluster member and is unobtainable by another network device within the cluster by monitoring the multicast protocol state.

39. The method of claim 38, wherein, when the cluster member fails, a network device within the cluster other than the cluster member assumes a workload and role of the cluster member using, at least in part, the sent second multicast protocol state.

40. The method of claim 37, further comprising:

determining whether the cluster member is load-balanced to manage the multicast data packet when the cluster member is associated with the multicast data packet.

41. The method of claim 37, further comprising:

employing a load-balancing mechanism selected from at least one of a round trip time load-balancing mechanism, a round robin load-balancing mechanism, a least connections load-balancing mechanism, a packet completion rate load-balancing mechanism, a quality of service load-balancing mechanism, a cluster topology load-balancing mechanism, a global availability load-balancing mechanism, a hops load-balancing mechanism, a hash load-balancing mechanism, a static ratios load-balancing mechanism, and a dynamic ratios load-balancing mechanism.

42. An apparatus, comprising:

first means for receiving initial protocol state information from a cluster master during a joining of a cluster member to the cluster;

means for monitoring the network for additional protocol state information;

means for employing the additional protocol state information to update a state of the cluster member when additional protocol state information is received;

second means for receiving a multicast data packet;

means for forwarding the multicast data packet towards a destination when the cluster member is associated with the multicast data packet;

third means for receiving a multicast control protocol packet from at least one network device external to the cluster; and

means for dropping the multicast control protocol packet rather than responding to the multicast control protocol packet.

43. A memory having a computer program embodied thereon, the program configured to control a processor to perform a process, the process comprising:

receiving initial protocol state information from a cluster master during a joining of a cluster member to the cluster;

monitoring the network for additional protocol state information;

employing the additional protocol state information to update a state of the cluster member when additional protocol state information is received;

receiving a multicast data packet;

directing forwarding of the multicast data packet towards a destination when the cluster member is associated with the multicast data packet;

receiving a multicast control protocol packet from at least one network device external to the cluster; and

dropping the multicast control protocol packet rather than responding to the multicast control protocol packet.

44. The memory of claim 43, the process further comprising:

directing sending of a second multicast protocol state to another network device within the cluster when the second multicast protocol state is known by the one of the cluster master and the cluster member and is unobtainable by another network device within the cluster by monitoring the multicast protocol state.

45. The memory of claim 44, wherein, when the cluster member fails, a network device within the cluster other than the cluster member assumes a workload and role of the cluster member using, at least in part, the sent second multicast protocol state.

46. The memory of claim 43, the process further comprising:

determining whether the cluster member is load-balanced to manage the multicast data packet when the cluster member is associated with the multicast data packet.

47. The memory of claim 43, the process further comprising:

employing a load-balancing mechanism selected from at least one of a round trip time load-balancing mechanism, a round robin load-balancing mechanism, a least connections load-balancing mechanism, a packet completion rate load-balancing mechanism, a quality of service load-balancing mechanism, a cluster topology load-balancing mechanism, a global availability load-balancing mechanism, a hops load-balancing mechanism, a hash load-balancing mechanism, a static ratios load-balancing mechanism, and a dynamic ratios load-balancing mechanism.