Stacked network switch configuration

• US 7,593,403 B2
• Filed: 09/21/2004
• Issued: 09/22/2009
• Est. Priority Date: 05/21/1999
• Status: Expired due to Fees

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Kalkunte, Mohan, Ambe, Shekhar, Kadambi, Shiri
• Primary Examiner(s): Phunkulh; Bob A
• Application Number:
  US10/945,115
• Publication Number:
  US 20050036488A1
• Time in Patent Office: 1,827 Days
• Field of Search: None
• US Class Current: 370/392
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 12/42 Loop networks
• CPC Class Codes: H04L 12/46 Interconnection of networks
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 12/4645 Details on frame tagging routing of packets H04L45/00; support for virtual LAN H04L49/354
• CPC Class Codes: H04L 12/467 Arrangements for supporting untagged frames, e.g. port-based VLANs
• CPC Class Codes: H04L 12/56 Packet switching systems
• CPC Class Codes: H04L 12/5602 Bandwidth control in ATM Networks, e.g. leaky bucket
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 45/245 Link aggregation, e.g. trunking
• CPC Class Codes: H04L 45/742 Route cache; Operation thereof
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/2458 Modification of priorities while in transit
• CPC Class Codes: H04L 47/43 Assembling or disassembling of packets, e.g. segmentation and reassembly [SAR]
• CPC Class Codes: H04L 47/50 Queue scheduling
• CPC Class Codes: H04L 47/56 implementing delay-aware scheduling
• CPC Class Codes: H04L 47/6205 Arrangements for avoiding head of line blocking
• CPC Class Codes: H04L 49/254 : Centralised controller, i.e. arbitration or scheduling
• CPC Class Codes: H04L 49/3009 : Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 49/3081 : ATM peripheral units, e.g. policing, insertion or extraction
• CPC Class Codes: H04L 49/351 : for local area network [LAN], e.g. Ethernet switches
• CPC Class Codes: H04L 49/354 : for supporting virtual local area networks [VLAN]
• CPC Class Codes: H04L 49/602 : Multilayer or multiprotocol switching, e.g. IP switching
• CPC Class Codes: H04L 49/90 : Buffering arrangements
• CPC Class Codes: H04L 49/901 : using storage descriptor, e.g. read or write pointers
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/14 : Multichannel or multilink protocols
• CPC Class Codes: H04L 69/16 : Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 : Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields

Abstract

A method of handling packets includes inserting a stack-specific tag into a packet, then processing the packet in a stack of network switches in accordance with tag information in the stack-specific tag. The stack-specific tag is then removed from the packet.

Claims

1. A method of handling packets, said method comprising:

inserting a stack-specific tag into a packet; and

processing the packet in a stack of network switches on a single chip in accordance with tag information in the stack-specific tag,

wherein each of the network switches is interconnected with others of the network switches through an interstack connection and wherein said stack-specific tag includes information relating to at least one of stack count, trunk group information, and mirroring information, and

wherein the processing further comprises passing the packet to a destination network switch through the interstack connection based on the tag information.

2. A method as recited in claim 1, wherein the processing further comprises forwarding the packet to a mirroring port in accordance with mirroring information in the stack-specific tag.

3. A method as recited in claim 2, wherein the forwarding to the mirroring ingress port includes selectively forwarding the packet to a destination port in accordance with the mirroring information.

4. A method as recited in claim 3, wherein the mirroring information includes a first field containing a mirroring indicator and a second field containing a destination indicator indicating whether the packet is to be sent to the destination port.

5. A method as recited in claim 1, wherein the processing further comprises processing trunk group information in the stack-specific tag, wherein said trunk group information controls port selection among network switches in the stack.

6. A method as recited in claim 5, wherein the processing further comprises processing information relating to a trunk group associated with a source port.

7. A method as recited in claim 5, wherein the processing further comprises processing information relating to a trunk group associated with a destination port.

8. A method as recited in claim 5, wherein said processing includes processing information in the stack-specific tag regarding whether one of a source port and a destination port is part of a trunk group, and processing information regarding selected communication ports associated with the trunk group.

9. A method as recited in claim 8, wherein said processing further comprises processing information regarding selected communication ports associated with the trunk groups including specific trunk group information and specific trunk port selection information.

10. A method as recited in claim 1, said method further comprising:

comparing at least one of a source address and a destination address of the packet to contents of an address lookup table;

learning a new source address that is not contained in the address lookup table; and

broadcasting packets containing destination addresses that are not contained in the address lookup table to a plurality of ports.

11. A method as recited in claim 10, wherein the learning of new source addresses comprises storing source address information in the address lookup table when the source address information is not already contained therein.

12. A method as recited in claim 10, wherein the comparing of at least one of the source and destination address comprises comparing destination address information in the packet to the address lookup table, and when the destination address is not contained in the lookup table, broadcasting the packet to the plurality of ports.

19. A method as recited in claim 1, wherein said processing comprises forwarding the packet in a unidirectional manner in a loop through the stack of network switches, wherein said stack is configured as a simplex ring.

20. A method as recited in claim 10, wherein said learning of the new source address includes learning trunk group information.

21. A method as recited in claim 8, wherein said processing includes processing information that prevents the packet from being sent to multiple ports of a same trunk group.

22. A method as recited in claim 1, wherein said processing comprises forwarding the packet on a bi-directional stack link to a port on another switch of the stack of network switches.

23. A method as recited in claim 22, wherein said processing comprises sequentially forwarding the packet to each switch of the stack of network switches, in a plurality of hops, until the packet has reached a destination port or has been sent to each switch of the stack of network switches.

24. A method as recited in claim 10, wherein said broadcasting of packets includes forwarding packets onto a bi-directional stack link port connecting to two switches of the stack of network switches.

25. A method as recited in claim 1, said method further comprising:

comparing at least one of a source address and a destination address of the packet to contents of an address lookup table, wherein

said processing comprises forwarding the packet to a destination port identified by a match on the destination address in the address lookup table.

27. A method as recited in claim 12, wherein the learning of the new source address includes learning trunk group information.

28. A method as recited in claim 5, wherein said trunk group information controls port selection by preventing the packet from being sent to multiple ports of a same trunk group.

13. A method of handling packets, said method comprising:

inserting a stack-specific tag into a packet; and

processing the packet in a stack of network switches on a single chip in accordance with tag information in the stack-specific tag,

wherein said stack-specific tag includes information relating to at least one of stack count, trunk group information, and mirroring information, and

wherein the processing further comprises passing the packet to a destination network switch through an interstack connection based on the tag information.

14. A method as recited in claim 13, wherein said processing of the packet includes forwarding the packet on a stack link to a port of another switch of the stack of network switches.

15. A method as recited in claim 14, further comprising:

modifying a stack count field, wherein the stack-count field is included in said stack-specific tag, and wherein the stack-count field contains information regarding a maximum number of hops necessary for the packet to make one loop through the stack.

16. A method comprising:

inserting a stack-specific tag into a packet;

processing the packet in a stack of network switches in accordance with tag information in the stack-specific tag; and

sequentially forwarding the packet to each switch in the stack of network switches and, in a plurality of hops, modifying a stack count field for each hop until the stack count reaches a predetermined value, wherein

each of the network switches is interconnected with others of the network switches through an interstack connection and wherein said stack-specific tag includes information relating to at least one of the stack count, trunk group information, and mirroring information.

17. A method as recited in claim 16, wherein the modifying of the stack count field comprises decrementing the stack count by one.

18. A method as recited in claim 17, wherein the predetermined value is zero.

26. A method of handling packets, said method comprising:

inserting a stack-specific tag into a packet; and

processing the packet in a stack of network switches on a single chip in accordance with tag information in the stack-specific tag,

wherein said processing includes blocking incoming ports such that when an incoming packet is forwarded out of any switch in the stack of network switches, it cannot be forwarded to a same port on which the packet came in, and

wherein the processing further comprises passing the packet to a destination network switch through the interstack connection based on the tag information.

29. A network switch for processing packets, said network switch comprising:

a tag insertion unit configured to insert a stack-specific tag into a packet; and

a processing unit configured to process the packet in a stack of network switches on a single chip of the network switch in accordance with tag information in the stack-specific tag,

wherein each of the network switches in the stack is interconnected with others of the network switches through an interstack connection and wherein said stack-specific tag includes information relating to at least one of stack count, trunk group information, and mirroring information, and

wherein the processing unit is further configured to pass the packet to a destination network switch through the interstack connection based on the tag information.

30. A network switch as recited in claim 29, wherein the processing unit is configured to process the packet by forwarding the packet to a mirroring port in accordance with mirroring information in the stack-specific tag.

31. A network switch as recited in claim 30, wherein the processing unit is configured to selectively forward the packet to a destination port in accordance with the mirroring information.

32. A network switch as recited in claim 31, wherein the mirroring information includes a first field containing a mirroring indicator and a second field containing a destination indicator indicating whether the packet is sent to the destination port.

33. A network switch as recited in claim 29, wherein the stack-specific tag includes trunk group information, and wherein the processing unit is configured to utilizes the trunk group information to control port selection among network switches in the stack.

34. A network switch as recited in claim 33, wherein the processing unit is configured to process information relating to a trunk group associated with a source port.

35. A network switch as recited in claim 33, wherein the processing unit is configured to process information relating to a trunk group associated with a destination port.

36. A network switch as recited in claim 33, wherein the processing unit is configured to process information in the stack-specific tag regarding whether one of a source port and a destination port is part of a trunk group, and to process information regarding selected communication ports associated with the trunk group.

37. A network switch as recited in claim 36, wherein said processing unit is configured to process information regarding selected communication ports associated with the trunk groups, including specific trunk group information and specific trunk port selection information.

38. A network switch as recited in claim 29, said network switch further comprising:

an address lookup table; and

a comparing unit configured to compare a source address and a destination address with addresses contained in the lookup table, wherein

the network switch is configured to learn new source addresses of packets that are not contained in the address table, and to broadcast packets containing destination addresses which are not contained in the address lookup table to a plurality of ports.

39. A network switch as recited in claim 38, wherein the address lookup table is configured to learn new addresses by storing new source address information in the lookup table when the source address information is not already contained therein.

40. A network switch as recited in claim 38, wherein the comparing unit is configured to compare destination address information in the packet to the address lookup table, and when the destination address information is not contained in the lookup table, the packet is broadcast to the plurality of ports.

41. A network switch as recited in claim 29, said network switch further comprising:

a stack link port configured to connect the network switch to other switches in the stack of network switches, wherein

the processing unit is configured to forward an incoming packet to the stack link port when a destination port for the incoming packet is located on another switch of the stack of network switches.

48. A network switch as recited in claim 29, said network switch comprising at least one bi-directional stacking port configured to be connected with at least one other network switch in the stack of network switches.

49. A network switch as recited in claim 48, wherein said processing unit is configured to forward the packet on the bi-directional stacking port.

50. A network switch as recited in claim 48, further comprising:

a removing unit configured to remove the stack-specific tag from packets which are destined for ports other than the bi-directional stacking port.

42. A network switch for processing packets, said network switch comprising:

a tag insertion unit configured to insert a stack-specific tag into a packet; and

a processing unit configured to process the packet in a stack of network switches on a single ship of the network switch in accordance with tag information in the stack-specific tag,

wherein said stack-specific tag includes information relating to at least one of stack count, trunk group information, and mirroring information, and

wherein the processing unit is configured to pass the packet to a destination network switch through a interstack connection based on the tag information.

43. A network switch as recited in claim 42, wherein said processing unit is configured to forward the packet on a stack link to a port of another switch of the stack of network switches.

44. A network switch as recited in claim 43, wherein said processing unit is configured to modify a stack count field before forwarding the packet, and wherein the stack count field is included in said stack-specific tag and the stack count field contains information regarding a maximum number of hops necessary for the packet to make one loop through the stack.

45. A network switch, comprising:

a tag insertion unit configured to insert a stack-specific tag into a packet; and

a processing unit configured to process the packet in a stack of network switches in accordance with tag information in the stack-specific tag, wherein

said stack-specific tag includes information relating to at least one of stack count, trunk group information, and mirroring information, and

said processing unit is configured to sequentially forward the packet to a next switch in the stack of network switches, and to modify a stack count field unless the stack count field has reached a predetermined value.

46. A network switch as recited in claim 45, wherein the processing unit is configured to modify the stack count field by decrementing the stack count by one.

47. A network switch as recited in claim 46, wherein the predetermined value is zero.