System using different tag protocol identifiers to distinguish between multiple virtual local area networks

• US 6,430,621 B1
• Filed: 12/29/1998
• Issued: 08/06/2002
• Est. Priority Date: 12/29/1998
• Status: Expired due to Term

• Current Assignee: Avaya Management L.P. (Avaya Incorporated)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Srikanth, Ayikudy K., Mehta, Rahul A.
• Primary Examiner(s): Luu, Le Hien
• Application Number:
  US09/222,045
• Time in Patent Office: 1,316 Days
• Field of Search: 370/466, 370/392, 370/389, 370/393, 709/227, 709/230, 709/238, 709/245
• US Class Current: 709/238
• 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

Abstract

A method and apparatus that provides for grouping nodes in multiple VLANs using port based VLAN grouping, and explicitly associates one of multiple VLANs with a packet transmitted by the nodes, using IEEE 802.1Q based frame tagging. A switch receives an untagged packet, filters the packet, and based on the contents of the packet, inserts a tag header with a common VLAN identifier and a unique tag protocol identifier (TPID).

Claims

1. In an internet having multiple virtual local area networks (VLANs) that are defined according to a port-based VLAN grouping scheme, a method providing for a node in the internet to communicate data over the multiple VLANs, comprising:

receiving at an ingress port of a switch a packet transmitted from the node coupled to the ingress port;

inserting a VLAN tag header in the packet to create a tagged packet, the VLAN tag header comprising a tag protocol identifier (TPID) field having a TPID value and a VLAN identifier (VID) field having a VID value identifying a first VLAN with which the ingress port is associated, the TPID value being used to identify a second VLAN; and

forwarding the tagged packet to an egress port of the switch for routing to a destination node associated with the second VLAN.

2. The method of claim 1, wherein the TPID value in the TPID field of the VLAN tag header inserted in the packet is determined by the contents of the packet upon receiving the packet at the ingress port.

3. The method of claim 2, wherein the TPID value in the TPID field of the VLAN tag header inserted in the packet is determined by the contents of a protocol type field in the packet upon receiving the packet at the ingress port.

4. The method of claim 2, wherein the TPID value in the TPID field of the VLAN tag header inserted in the packet is determined by the contents of a Media Access Control (MAC) address field in the packet upon receiving the packet at the ingress port.

5. The method of claim 4, wherein the TPID value in the TPID field of the VLAN tag header inserted in the packet is determined by the contents of a destination MAC address field in the packet upon receiving the packet at the ingress port.

6. The method of claim 2, wherein the TPID value in the TPID field of the VLAN tag header inserted in the packet is determined by the contents of a Network layer address field in the packet upon receiving the packet at the ingress port.

7. In an internet having multiple virtual local area networks (VLANs) that are defined according to a port-based VLAN grouping method, a method providing for a node in the internet to communicate data over multiple VLANs, comprising:

receiving at an ingress port of a switch a first packet transmitted from the node coupled to the ingress port;

inserting a VLAN tag header in the packet to create a first tagged packet, the VLAN tag header comprising a tag protocol identifier (TPID) field having a first TPID value and a VLAN identifier (VID) field having a first VID value identifying the VLAN with which the ingress port is associated;

forwarding the tagged packet to an egress port of the switch that is associated with the first TPID value and the VLAN identified by the first VID value;

receiving at the ingress port of the switch a second packet transmitted from the node coupled to the ingress port;

inserting a VLAN tag header in the packet to create a second tagged packet, the VLAN tag header comprising a tag protocol identifier (TPID) field having a second TPID value and a VLAN identifier (VID) field having a second VID value identifying a VLAN with which the ingress port is associated, the second TPID value capable of being used to identify a second VLAN; and

forwarding the tagged packet to an egress port of the switch that is associated with the second TPID value and the second VID value for routing to a destination node associated with the second VLAN.

8. The method of claim 7, wherein the first TPID value in the TPID field of the VLAN tag header inserted in the packet is determined by the contents of the first packet upon receiving the first packet at the ingress port and the second TPID value in the TPID field of the VLAN tag header inserted in the second packet is determined by the contents of the second packet upon receiving the second packet at the ingress port.

9. A software product stored on a machine-readable medium, for execution on a first switch connected to an internetwork having multiple virtual local area networks (VLANs) that are defined according to a port-based VLAN grouping scheme, comprising:

a first software routine to receive at an ingress port of a first switch a packet transmitted from a node coupled to the ingress port and to insert a VLAN tag header in the packet to create a tagged packet, the VLAN tag header comprising a tag protocol identifier (TPID) field having a unique TPID value identifying one of the VLANs with which an egress port chosen to receive the tagged packet is associated and a VLAN identifier (VID) field having a VID value identifying one of the VLAN with which the ingress port is associated; and

a second software routine to forward the tagged packet to the egress port of a switch that is associated with the TPID value and the VID value.

10. The software product of claim 9, further comprising a third software routine to determine the contents of the packet upon receiving the packet at the ingress port including the VLAN tag header.

11. The software product of claim 9 being executed within the first switch for forwarding the tagged packet to the switch, differing from the first switch, that is associated with the TPID value and the VID value.

12. A system comprising:

a first switch including a plurality of ports; and

a second switch including a port to receive a packet, to insert a virtual local area network (VLAN) tag header in the packet for creating a tagged packet, the VLAN tag header including (i) a VLAN identifier (VID) field having a VID value identifying a first VLAN with which the port is associated and (ii) a tag protocol identifier (TPID) field having a TPID value identifying a second VLAN with which one of the plurality of ports of the first switch chosen to receive the tagged packet is associated, the second switch to further forward the tagged packet to the chosen port of the first switch.

13. The system of claim 12, wherein the second switch is in communication with the first switch over an Internet backbone, the Internet backbone enabling transmission of the tagged packet from the second switch to the first switch.

14. The system of claim 13 further comprising a node coupled to the port of the second switch.

15. The system of claim 12, wherein the TPID value is uniquely associated with one of multiple VLANs, inclusive of the first VLAN and second VLAN, associated with the system.

16. The system of claim 12, wherein the second switch includes storage to maintain TPID values and corresponding VID values for each of the plurality of ports of the first switch.

17. The system of claim 16, wherein the storage of the second switch further maintains TPID values and corresponding VID values for all ports of the second switch.

18. The system of claim 16, wherein the storage includes a cache.