US6104696A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method for sending packets between trunk ports of network switches
Assignee: Avago Technologies International Sales Pte Ltd
•
Filing: 1999-06-30
•
Granted: 2000-08-15
•
Expires: 2019-06-30
Abstract
Abstract The present invention is directed to a system and method of sending packets between ports on trunked network switches. The method includes providing a first switch having a plurality of communication ports thereupon, and providing a second switch having a plurality of communication ports thereupon. A trunk connection is provided between the first switch and the second switch, with the trunk connection including at least two of the plurality of ports from the first switch being connected to at least two of the plurality of ports of the second switch. A rules table is provided, defining a set of rules identifying which port of the trunk connection will be used for communication. A packet is sent from a first port on the first switch to a second port on the second switch. The packet is received at an ingress submodule of the first switch, and a lookup is performed on one of a source address and a destination address of the packet based upon a lookup table provided in the ingress submodule. It is then identified that the first switch and second switch are connected with the trunk connection by a trunk bit in a lookup entry matched by the destination address. A rules tag bit in the lookup entry is then identified, and the rules tag bit is then compared to a rules table defining which trunk port of the trunk bundle will be used for communication. The rules tag determines which address bits will be used to identify a trunk port for communication. The packet is then forwarded to the destination address on the identified trunk port. The packet is then stored in memory, and then retrieved from memory with an egress unit. The egress unit then forwards the packet to the identified trunk port.
Inventors
- 👤 Shiri Kadambi
- 👤 Shekhar Ambe
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-06 08:44
CPC Classifications
H; H04; H04L; H04L12/00; H04L12/54; H04L12/56; H04L12/5601; H04L12/28; H04L12/46; H04L12/4604; H04L12/462; H04L12/4625; H04L12/4641; H04L12/4645; H04L12/467; H04L12/5602; H04L45/00; H04L45/24; H04L45/245; H04L45/74; H04L45/742; H04L47/00; H04L47/10; H04L47/12; H04L47/125; H04L47/24; H04L47/2408; H04L47/2441; H04L47/2458; H04L47/30; H04L47/50; H04L47/52; H04L47/522; H04L47/525; H04L47/62; H04L47/6205; H04L47/6215; H04L47/622; H04L47/6225; H04L47/623; H04L49/00; H04L49/10; H04L49/102; H04L49/103; H04L49/104; H04L49/105; H04L49/107; H04L49/108; H04L49/109; H04L49/30; H04L49/3081; H04L49/309; H04L49/35; H04L49/351; H04L49/352; H04L49/60; H04L49/606; H04L49/90; H04L49/901; H04L49/9047; H04L49/9057; H04L49/9063; H04L49/9068; H04L49/9073; H04L67/00; H04L67/01; H04L67/10; H04L69/00; H04L69/16; H04L69/161; H04L12/02; H04L12/16; H04L12/18; H04L12/42; H04L2012/5638; H04L2012/5646; H04L2012/5651; H04L2012/5665; H04L2012/5667; H04L2012/5678; H04L2012/5679; H04L2012/568; H04L2012/5681; H04L2012/5682; H04L2012/5683; H04L49/20; H04L49/201; H04L49/205; H04L49/25; H04L49/253; H04L49/254; H04L49/3009; H04L49/3036; H04L49/3072; H04L49/354; H04L49/602; H04L69/14; H04L69/30; H04L69/32; H04L69/322; H04L69/323; H04L69/329; Y; Y02; Y02D; Y02D30/00; Y02D30/50; Y10; Y10S; Y10S707/00; Y10S707/99931; Y10S707/99941; Y10S707/99944; Y10S707/99945
Claims Analysis
Total Claims: 21
Claim 1
Independent Claim
236 words
A method of sending packets between ports on trunked network switches, said method comprising: providing a first switch having a plurality of communication ports thereupon; providing a second switch having a plurality of communication ports thereupon; providing a trunk connection between said first switch and said second switch comprising at least two of said plurality of ports from said first switch being connected at least two of said plurality of ports of said second switch; sending a packet from a first port on said first switch to a second port on said second switch; receiving said packet at an ingress submodule of said first switch, and performing a lookup on one of a source address and destination address of the packet based upon a lookup table provided in said ingress submodule; identifying that the first switch and the second switch are connected with the trunk connection by a trunk bit in a lookup entry of the lookup table matched by the destination address; identifying a rules tag in the lookup entry; identifying a trunk group identification in the lookup entry; determining a trunk port index based upon the rules tag; applying the trunk group identification and the trunk port index to a trunk group table, thereby identifying a trunk port for communication; storing the packet in memory; and retrieving the packet from memory with an egress unit, and forwarding the packet to the identified trunk port.
Claim 2
Independent Claim
236 words
A method of sending packets between ports on trunked network switches, said method comprising: providing a first switch having a plurality of communication ports thereupon; providing a second switch having a plurality of communication ports thereupon; providing a trunk connection between said first switch and said second switch comprising at least two of said plurality of ports from said first switch being connected at least two of said plurality of ports of said second switch; sending a packet from a first port on said first switch to a second port on said second switch; receiving said packet at an ingress submodule of said first switch, and performing a lookup on one of a source address and destination address of the packet based upon a lookup table provided in said ingress submodule; identifying that the first switch and the second switch are connected with the trunk connection by a trunk bit in a lookup entry of the lookup table matched by the destination address; identifying a rules tag in the lookup entry; identifying a trunk group identification in the lookup entry; determining a trunk port index based upon the rules tag; applying the trunk group identification and the trunk port index to a trunk group table, thereby identifying a trunk port for communication; storing the packet in memory; and retrieving the packet from memory with an egress unit, and forwarding the packet to the identified trunk port.
Claim 3
Dependent Claim
36 words
A method as recited in claim 1, wherein said rules tag defines that bits of at least one of a source MAC address and a destination MAC address are used to determine the trunk port index.
Claim 4
Dependent Claim
36 words
A method as recited in claim 1, wherein said rules tag defines that bits of at least one of a source IP address and a destination IP address are used to identify the trunk port index.
Claim 5
Dependent Claim
44 words
A method as recited in claim 1, wherein said lookup table includes a plurality of entries contained therein, and wherein each entry includes a bit which indicates whether or not the entry is to be handled by a trunk group or a non-trunk group.
Claim 6
Dependent Claim
48 words
A method as recited in claim 1, said method further comprising: detecting a link failure when a trunk port fails; sending a notification message to a CPU regarding the failure; and modifying the trunk group table to reflect that the trunk port is no longer available for communication.
Claim 7
Dependent Claim
48 words
A method as recited in claim 5, further comprising: providing a trunk group port bit map table; after the notification message is sent to the CPU regarding the failure, modifying the trunk group port bit map table to reflect that the port is no longer available for communication.
Claim 8
Dependent Claim
54 words
A method as recited in claim 6, further comprising: detecting when a link which caused the link failure is reestablished; notifying the CPU regarding detection of reestablishment of the link; reconfigurating at least one of the trunk group table and the trunk group bit map table so as to reflect reestablishment of the link.
Claim 9
Dependent Claim
35 words
A method as recited in claim 1, further comprising selectively disabling at least one port of said plurality of ports, such that selected packet types are blocked from being transmitted on the selectively disabled port.
Claim 10
Dependent Claim
56 words
A method as recited in claim 8, wherein selectively disabling at least one of the ports includes a step of setting a disabling bit in a PVLAN table, whereby, so that when a packet is applied to the PVLAN table, a corresponding bit in the packet is set or unset in accordance with the PVLAN table.
Claim 11
Dependent Claim
41 words
A method as recited in claim 8, wherein selectively disabling the at least one port includes a step of disabling at least one port for a selected packet type to direct control packets to a single port of the trunk group.
Claim 12
Independent Claim
267 words
A system for sending packets between ports on trunked network switches, said system comprising: first switch means having a plurality of communication ports thereupon; second switch means having a plurality of communication ports thereupon; a trunk connection between said first switch means and said second switch means, said trunk connection comprising at least two of said plurality of ports from said first switch means being connected to at least two of said plurality of ports of said second switch means; sending means for sending a packet from a first port of said first switch means to a second port of said second switch means; an ingress submodule in said first switch means for receiving said packet and for performing an address resolution lookup on one of a source address and destination address of the packet based upon a lookup table provided in the ingress submodule; first identifying means for identifying that the first switch means and second switch means are connected with the trunk connection, said first identifying means including a trunk bit in a lookup entry of the lookup table being matched by the destination address; second identifying means for identifying a rules tag in the lookup entry; determining means for determining which rule of a series of rules will be used to define a trunk port index which is used to identify which port of the trunk connection will be used for communication; storing means for storing the packet in a memory; and retrieving means for retrieving the packet from the memory with an egress unit, and forwarding the packet to the identified trunk port.
Claim 13
Independent Claim
267 words
A system for sending packets between ports on trunked network switches, said system comprising: first switch means having a plurality of communication ports thereupon; second switch means having a plurality of communication ports thereupon; a trunk connection between said first switch means and said second switch means, said trunk connection comprising at least two of said plurality of ports from said first switch means being connected to at least two of said plurality of ports of said second switch means; sending means for sending a packet from a first port of said first switch means to a second port of said second switch means; an ingress submodule in said first switch means for receiving said packet and for performing an address resolution lookup on one of a source address and destination address of the packet based upon a lookup table provided in the ingress submodule; first identifying means for identifying that the first switch means and second switch means are connected with the trunk connection, said first identifying means including a trunk bit in a lookup entry of the lookup table being matched by the destination address; second identifying means for identifying a rules tag in the lookup entry; determining means for determining which rule of a series of rules will be used to define a trunk port index which is used to identify which port of the trunk connection will be used for communication; storing means for storing the packet in a memory; and retrieving means for retrieving the packet from the memory with an egress unit, and forwarding the packet to the identified trunk port.
Claim 14
Dependent Claim
83 words
A system as recited in claim 11, wherein said second identifying means is configured to analyze the rules tag to identify that bits of at least one of a source MAC address and a destination MAC address which are used to identify a trunk port index, said ingress module also identifying a trunk group identification in the address resolution lookup, said trunk group identification and said trunk port index being applied to a trunk group table, thereby identifying a trunk port for communication.
Claim 15
Dependent Claim
82 words
A system as recited in claim 11, wherein said second identifying means is configured to analyze the rules tag to identify that it is bits of at least one of a source IP address and a destination IP address to identify a trunk port index, said ingress module also identifying a trunk group identification in the address resolution lookup, said trunk group identification and said trunk port index being applied to a trunk group table, thereby identifying a trunk port for communication.
Claim 16
Dependent Claim
81 words
A system as recited in claim 11, wherein said second identifying means is configured to analyze the rules tag to identify that it is the last three bits of at least one of a source MAC address, a destination MAC address, a source IP address, and a destination IP address, to identify a trunk port index, and wherein said trunk port index and said trunk group identification being applied to a trunk group table, thereby identifying a trunk port for communication.
Claim 17
Dependent Claim
56 words
A system as recited in claim 12, said system further comprising: detecting means for detecting a link failure when a trunk port fails; sending means for sending a notification message to a controller regarding the failure; and modifying means for modifying the trunk group table to reflect that the port is no longer available for communication.
Claim 18
Dependent Claim
53 words
A system as recited in claim 15, said system further comprising: detecting means for detecting when a link which caused the link failure is reestablished; notifying means for notifying the sending means regarding the restoration of communication; and restoring means for restoring the trunk group table to reflect the reestablishment of the link.
Claim 19
Dependent Claim
39 words
A system as recited in claim 6, further comprising selective disabling means for selectively disabling at least one port of the plurality of ports, such that selected packet types are blocked from being transmitted on the selectively disabled port.
Claim 20
Dependent Claim
52 words
A system as recited in claim 17, wherein said selective disabling means includes setting means for setting a disabling bit in the lookup table, whereby, so that when a packet is applied to the lookup table, a corresponding bit in the packet is set or unset in accordance with the lookup table.
Claim 21
Dependent Claim
32 words
A system as recited in claim 17, wherein said selective disabling means selectively disables a plurality of ports so as to direct control packets to a single port of the trunk group.
References Cited (Backward Citations)
US5404461A
Cited
US5432783A
Cited
US5841771A
Cited
US5862136A
Cited
US5838681A
Cited
US6016310A
Cited
US5991297A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-08-15 | 2004-02-14 | 2004-08-15 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-08-15 | 2008-02-14 | 2008-08-15 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-08-15 | 2012-02-14 | 2012-08-15 | $7700.00 | Window Closed / Lapsed |