Network bridge with multicast forwarding table

• US 5,608,726 A
• Filed: 04/25/1995
• Issued: 03/04/1997
• Est. Priority Date: 04/25/1995
• Status: Expired due to Term

• Current Assignee: Enterasys Networks Incorporated (Extreme Networks, Inc.)
• Original Assignee: Cabletron Systems Incorporated (Extreme Networks, Inc.)
• Inventors: Virgile, Kenneth
• Primary Examiner(s): BLUM, RUSSELL
• Application Number:
  US08/428,403
• Time in Patent Office: 679 Days
• Field of Search: 370/60, 370/79, 370/85.13, 370/85.14, 370/94.1, 370/94.3
• US Class Current: 370/401
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 12/1886 with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains

Abstract

A system and method are disclosed for routing multicast packets in a subnetwork so as to conserve bandwidth in at least some of the network segments or collision domains of the subnetwork. In particular, multicast packets are only retransmitted in the network segments that are on a path to a host that is a member of the multicast group of hosts to which the multicast packet is destined.

Claims

1. In a hierarchical communications network comprising:

a plurality of interconnected routers and

a plurality of subnetworks connected to said routers, wherein each of said subnetworks comprises;

one or more network segments, and

one or more bridges interconnecting said network segments and

connecting each said subnetwork to one or more of said routers, and

wherein each network segment comprises one or more hosts, a process for providing multicast communication comprising the steps of;

transmitting from a selected one of said hosts on a route to a destination one of said routers a multicast control packet indicating a multicast group to which said host belongs,

receiving said multicast control packet at a bridge on said route to said destination router,

using said multicast control packet, updating a multicast forwarding table entry in a multicast forwarding table corresponding to said multicast group at said bridge,

retransmitting said multicast control packet from said bridge on said route to said destination router,

using said multicast control packet, updating a routing table at said destination router, and

at said bridge, retransmitting multicast message packets destined to said indicated multicast group according to said updated multicast forwarding table maintained at said bridge.

2. The process of claim 1, further comprising the step of:

in response to receiving the multicast control packet, updating said multicast forwarding table entry corresponding to said indicated multicast group to indicate a network segment of said host from which said multicast control packet was received.

3. The process of claim 2, further comprising the step of:

in response to receiving the multicast control packet, updating said multicast forwarding table entry corresponding to said particular multicast group by adding a network segment of said host from which said multicast control packet was received.

4. The process of claim 2, further comprising the step of:

in response to receiving the multicast control packet, updating said multicast forwarding table entry corresponding to said particular multicast group by removing an indication of a network segment of said host from which said multicast control packet was received, when said host was formerly the only host contained in said network segment that was also a member of said particular multicast group.

5. The process of claim 1, further comprising the steps of:

receiving a multicast message packet at said bridge via one of a plurality of I/O interfaces of said bridge,

using a destination address of the received multicast message packet as an index, retrieving a corresponding entry from said multicast forwarding table maintained at said bridge, and

retransmitting said multicast message packet from each I/O interface associated with the retrieved corresponding entry from said multicast forwarding table, other then said one I/O interface of said plurality of I/O interfaces via which said multicast message packet was received; and

when no entry exists for said destination address, retransmitting said received multicast message packet from each I/O interface of said plurality of I/O interfaces except for said one I/O interface via which said multicast message packet was received.

6. The process of claim 1, wherein a route from a particular bridge of a subnetwork to a particular host that is a member of a particular multicast group includes at least one intervening network segment connected directly to said particular bridge, said process comprising the steps of:

receiving at said particular bridge a multicast message packet destined to said particular multicast group, and

retransmitting said multicast message packet in said at least one intervening network segment.

7. The process of claim 1, wherein each entry of said multicast forwarding table corresponds to a different multicast group and wherein each table entry indicates only those I/O interfaces connected to network segments on a route to a host that is a member of said corresponding multicast group.

8. A bridge in a hierarchical communications network comprising:

a plurality of I/O interfaces for transmitting packets to, and for receiving packets from, routers and network segments attached to said bridge, said plurality of I/O interfaces including one I/O interface connected to each of said routers and one I/O interface connected to each of said network segments, and

a processor connected to said I/O interfaces, for receiving a multicast control packet transmitted from a host of one of said network segments to one destination router of said routers via a route including said bridge, for updating a multicast forwarding table entry in a multicast forwarding table in said bridge corresponding to a multicast group of said multicast control packet, for causing said I/O interface connected to said destination router of said multicast control packet to retransmit said multicast control packet, and for causing said I/O interfaces to retransmit multicast message packets destined to said multicast group according to said multicast forwarding table.

9. The bridge of claim 8, further comprising:

a bus interconnecting said I/O interfaces and said processor, and

a memory connected to said bus for storing said multicast forwarding table.

10. A network bridge, comprising:

at least two I/O interfaces to each receive and transmit data packets; and

a processor operatively coupled to the at least two I/O interfaces;

wherein the processor comprises;

means for receiving any data packet received by any of the at least two I/O interfaces;

means for identifying the received data packet as a multicast control packet destined for a device other than the network bridge;

means for identifying the I/O interface on which the identified multicast control packet arrived;

means for identifying a multicast group from the multicast control packet; and

means for updating a multicast forwarding table entry associated with the determined multicast group.

11. The network bridge as recited in claim 10, wherein the processor further comprises:

means for determining a source of the identified multicast control packet; and

the updating means further comprises;

means for associating the determined source with the determined multicast group and the I/O interface on which the multicast control packet arrived.

12. The network bridge as recited in claim 11, further comprising a memory operatively coupled to the processor for storing the updated multicast forwarding table.

13. The network bridge as recited in claim 10, further comprising:

means for retrieving the multicast forwarding table entry as a function of the determined multicast group;

whereby a multicast message destined for the determined multicast group will be retransmitted according to the multicast forwarding table entry associated with the determined multicast group.