Private VLAN edge across multiple switch modules

[0001] The invention relates to an apparatus, system and method to implement a protected port feature in a network, such as a Virtual Local Area Network (VLAN). The protected port feature may be referred to as Private VLAN Edge.

[0002] A protected port feature may be desirable in a network in which the transmission of information to and between endpoints needs to be controlled. In certain situations, it is preferable that some endpoints receive more or less information than others. Similarly, it may be desirable to limit or restrict the flow of information to one or more endpoints. The protected port feature identifies ports as being either protected or unprotected and thereby determines how data is transmitted to or between these ports.

[0003] The protected port feature may be supported in a Local Area Network (LAN) that includes a conventional switch. The endpoints are connected to each other through the local, common switch. The switch is able to control the transmission of data transmitted to endpoints connected to its local ports. A LAN or VLAN that includes two or more conventional switches does not support the protected port feature.

[0004] The invention will become more readily apparent from the following detailed description of a preferred embodiment of the invention which proceeds with reference to the accompanying drawings.

[0013] A Virtual Local Area Network (VLAN) is a network that is configured to associate multiple end users situated in one or more local area networks irrespective of their physical location. For example, two or more VLAN may be configured to share at least some common endpoints, servers and switches that may reside in one or more physical locations. In this manner, a single endpoint may belong to one or more VLAN. Configuring a VLAN can accomplish a number of objectives, including: intelligent management of broadcast services; isolating ports, or end-users, connected from one VLAN from data transmitted in a second VLAN; and resource sharing, among others.

[0014] FIG. 1 shows a block diagram of two VLAN connecting multiple switches. A VLAN 10 is configured to include a central processing unit (CPU) 50, a first switch 110, a second switch 120 and a third switch 130. A second VLAN 20 is configured to include the CPU 50, the second switch 120 and a fourth switch 140. It can be seen from this example that both VLAN 10 and 20 are configured to include the CPU 50 and switch 120. The first switch 110 may therefore be isolated from data transmitted on VLAN 20, and the fourth switch 140 may be isolated from data transmitted on VLAN 10. The switches shown in FIG. 1 may each be implemented using different switch ASIC (Application Specific Integrated Circuit), including switches developed by different vendors. Network processing devices, such as switches, routers, and bridges, may be configured to select a path or circuit for sending data to its destination. A network processing device may also determine a route, or transmission path, for data in some applications.

[0015] The VLANs 10 and 20 may be configured to include any endpoints, or work stations, that are identified according to a department or work group. For example VLAN 10 may include endpoints that are identified as part of an Engineering department, whereas the second VLAN 20 may include endpoints that are identified as part of a Purchasing department. Endpoints can also be configured into both VLAN 10 and VLAN 20 and may therefore view and share information with other endpoints in the Engineering department, the Purchasing department, or both. For example, an endpoint connected to the switch 120 may communicate with other endpoints associated with VLAN 10 or VLAN 20. Endpoints that are associated with only one VLAN may only be able to view and share information with one department. For example, an endpoint connected to the switch 130 may not be able to communicate with other endpoints associated with VLAN 20.

[0016] Switches 110, 120 and 130 may include processors, logic, or circuitry that operate on or provide a processing capability of data transmitted from the endpoints. For example, switch 110 may include protected port logic (PPL) 1115, switch 120 may include a PPL 125, and switch 130 may include a PPL 135. VLAN 110 is shown as including switches which all include protected port logic, whereas VLAN 120 is shown as including switch 140 that does not include protected port logic, as well as switch 120 that does include protected port logic PPL 125. Protected port logic may be provided by a central processing unit (CPU) 50 or some other processor, server or protected port logic device in the VLAN, rather than by each switch.

[0017] FIG. 2 illustrates example data transmission paths between endpoints Host A, Host B. Host C and Host D in VLAN 10. The endpoints may be computers, terminals, servers, network devices or end users, for example. Endpoints may indicate a specific location or address for accessing a service using a protocol and data format. The endpoints are shown as being indirectly connected to each other in the VLAN 10. A transmission protocol may be configured to provide transmission paths, such as transmission path 30, which allow data to be transmitted in either direction as between some of the two endpoints, such as endpoints Host A and Host B. Transmission path 40 between Host A and Host C is shown with an “X” to signify that data transmitted between these two endpoints may be dropped before reaching a destination. The transmission protocol may allow data to be forwarded between some of the endpoints, such as Host A and Host C, whereas data is dropped between other endpoints, such as Host A and Host C.

[0018] FIG. 3 illustrates an example block diagram of the VLAN 10 of FIG. 2 including a backplane switch 150, CPU 50 and switches 110, 120 and 130. Switches 110, 120 and 130 are shown indirectly coupled to each other through the backplane switch 150. Backplane switch 150 may be a backplane interconnect such as a backplane Ethernet switch. Switch 110 is shown connected to an endpoint (Host A) through a protected port 115, and switch 120 is shown connected to an endpoint (Host B) through a non-protected port 125. Switch 130 is connected to an endpoint (Host C) through a protected port 135, and is also connected to a further endpoint (Host D) through a non-protected port 137. CPU 50 in VLAN 10 may be connected directly or through an Ethernet switch (not shown) to the backplane switch 150. CPU 50 may be a server, shared database or other type of processor.

[0019] Any of Host A, Host B, Host C or Host D may be a source endpoint or a destination endpoint of a data transmission, such as data packet 100, sent on VLAN 10. For example, Host A may be a source endpoint for the data packet 100 sent to Host B. Host B may be a source endpoint for a broadcast data transmission sent to all the other endpoints in VLAN 10 that includes Host A, Host C and Host D. Data packet 100 is generally understood to include any type of data (voice, video, etc), and may be included in an Ethernet frame, for example, transmitted between two or more endpoints. As used herein, a transmission of the data packet includes a transmission of an Ethernet frame, token ring frame, or other network frame which may include data and identification fields.

[0020] A protected port status of the ports 115, 125, 135 and 137 may be used to determine a transmission protocol between endpoints. The transmission protocol may be used to isolate one or more access ports from data transmitted by a source endpoint. Port isolation, or private VLAN edge, may be accomplished transparent to the backplane switch 150, as will be discussed further. A protected port may identify an associated endpoint that will not receive certain data transmissions on a particular VLAN. A non-protected port may identify an associated endpoint that will generally receive all of the information that is broadcast on a particular VLAN, as well as receive any data from a source endpoint that identifies the associated endpoint as a destination endpoint.

[0021] In one embodiment, the protected port feature may be supported by means of connecting two or more switches, such as switches 110 and 120, in a stacked connection and providing a vendor specific tag that is carried from one switch to the other. The vendor specific tag is used by the switches to determine a transmission protocol that is to be applied to the data. Switches provided in the stacked connection may include the same switch ASIC.

[0022] FIG. 4 illustrates a table 500 showing an example transmission protocol based on a protected status of a source port 515 and a destination port 525. The transmission protocol may be configured to determine whether or not to forward a data packet sent from the source port 515 to the destination port 525. According to FIG. 4, data transmitted from a protected source port to a protected destination port is not forwarded. Data transmitted from a protected source port to a non-protected destination port is forwarded. Data transmitted from a non-protected source port to a protected destination port is forwarded. Data transmitted from a non-protected source port to a non-protected destination port is forwarded.

[0023] Therefore, according to FIG. 4, a data packet is forwarded to the destination port 525 for all combinations of protected port status except where the source port 515 and the destination port 525 are both identified as being protected. Of course, different transmission protocols are contemplated and claimed herein, including logic that forwards or drops data transmission according to different combinations of protected port status. For example, an alternative transmission protocol may drop all data packets that are sent to a destination port that is identified as protected, irrespective of the protected port status of the source port.

[0024] The transmission protocol may be carried out or processed within one or more of the switches 110, 120 and 130, the CPU 50, or any other processor or server associated with the network. A data transmission from a first switch associated with a first access port may be sent to a second switch associated with a second access port. The second switch may compare a protected port status of the first and second access ports to determine if the data transmission should be forwarded to a destination endpoint or dropped. A data transmission broadcast to all of the endpoints in a VLAN may be processed by each of the switches to determine a port comparison separately from the other switches.

[0025] FIG. 5 illustrates an example pictorial representation of an Ethernet frame 200 including data 260 that may be transmitted in a VLAN. Ethernet frame 200 has a data header that includes a destination address field 210, a source address field 220, a VLAN tag 230 and a type/length field 250. The destination address 210 identifies a destination endpoint and may include a layer-two address, such as a Media Access Control (MAC) address, of the destination endpoint. Layer-two may be specified with reference to the Institute of Electrical and Electronic Engineers (IEEE) industry standard IEEE 802.3. The source field 220 identifies a source endpoint and may include a MAC address of the source endpoint. The data packet 100 described with reference to FIG. 3, may be transported in the Ethernet frame 200 and include data 260 and one or more other fields of Ethernet frame 200.

[0026] The VLAN tag 230 of FIG. 5 includes fields for Tag Protocol Identifier (TPID), priority, Canonical Format Indicator (CFI) and VLAN Identifier (VID). A TPID field 231 may identify Ethernet frame 200 according to the Institute of Electrical and Electronic Engineers (IEEE) industry standard IEEE 802.1Q, for example, and in one application is set to a value of 0×8100. A priority field 233 represents a priority of Ethernet frame 200, and may be set according to a priority identified by the industry standard IEEE 802.1p. A CFI field 235 is used for layer-three services or applications, and is not used or required for conventional layer-two services or applications, in which case it may be set to zero. A VID field 237 may be used to identify a VLAN associated with Ethernet frame 200.

[0027] Ethernet frame 200 of FIG. 4 also includes a Frame Check Sequence (FCS) field 290. The FCS field 290 may be used to validate or ensure a data transmission was completed without any data loss.

[0028] Ethernet frame 200 may be sent from a first endpoint, such as Host A of FIG. 2, over a first port, such as protected port 115, to a first switch, such as switch 110. The first switch 110 modifies Ethernet frame 200 shown in FIG. 4 to include layer-two information (LFI) that is used in the protected port transmission protocol. Certain fields in Ethernet frame 200 may be modified, in addition to adding the layer-two information, and this is discussed in more detail below.

[0029] FIG. 6 illustrates an example pictorial representation of an Ethernet frame 300 having an LFI tag 370 including the layer-two information added by the first switch 110. Ethernet frame 300 may be transmitted from the first switch 110 to one or both switches 120 and 130 shown in FIG. 3. Data 360 of Ethernet frame 300 may contain the same data as data 260 included in Ethernet frame 200. Similarly, destination address field 310, source field 320, and FCS field 390 of Ethernet frame 300 may include the same information as the destination address field 210, the source field 220, and the FCS field 290, respectively, of Ethernet frame 200. The data packet 100 described with reference to FIG. 3, may be transported in the Ethernet frame 300 and include the data 360 and one or more other fields of Ethernet frame 300.

[0030] A transient CFI field 335 in Ethernet frame 300 corresponds to the original CFI field 235 of Ethernet frame 200. Transient CFI field 335 may be modified from original CFI field 235 to include a feature information tag, or data link tag. The feature information tag status is identified as valid when the LFI tag 370 is inserted into Ethernet frame 300 by a switch or other device. For example, a bit in the transient CFI field 335 may be set to on to indicate when the feature information tag is valid. As used herein, a bit in any of the fields described hereafter may be set to on, or true, to indicate a valid value, whereas a bit may be set to off, or false, to indicate an invalid value.

[0031] The LFI tag 370 of Ethernet frame 300 includes a Tag ID field 371, which may provide an identification or ownership of the LFI tag 370. For example, the Tag ID field 371 may include an Internet Assigned Numbers Authority (IANA) Enterprise Number, or identify a transmission protocol or switch that is compatible with the LFI tag 370. A tag valid field 373 and a feature valid field 377 in the LFI tag 370 may be used to indicate information that is contained in Ethernet frame 300, including other fields in the LFI tag 370 discussed herein. The legacy CFI field 375 in the LFI tag 370 may be used to store a legacy CFI value read from the original CFI field 235 of Ethernet frame 200. A protected port field 380 may be used to indicate the protected port status of a port associated with a switch, such as protected port 115 and the first switch 110. The other field 385 may include additional information that may be used for other transportation protocols or Ethernet frame identifications. In one embodiment (not shown), the LFI tag 370 is included at or near the beginning of the Ethernet frame 300, or before the data 360.

[0032] FIG. 7 illustrates an example pictorial representation of a further modified Ethernet frame 400 without the LFI tag 370. Data 460 in Ethernet frame 400 may include the same data as data 360 included in Ethernet frame 300 and data 260 included in Ethernet frame 200. Similarly, destination address field 410, source field 420, and FCS field 490 of Ethernet frame 400 may include the same information as the destination address fields 210 and 310, the source fields 220 and 320, and the FCS fields 290 and 390, respectively, of Ethernet frames 200 and 300. The data packet 100 described with reference to FIG. 3, may be transported in the Ethernet frame 400 and include the data 460 and one or more other fields of Ethernet frame 400.

[0033] A switch associated with the destination endpoint may remove the LFI tag 370 from Ethernet frame 300 to provide Ethernet frame 400 which is then forwarded to the destination endpoint. For example, switch 120 may receive Ethernet frame 300 from switch 110, remove the LFI tag 370, and transmit Ethernet frame 400 to the destination endpoint, such as Host B. Ethernet frame 400 may therefore include the same data and fields as Ethernet frame 200 shown in FIG. 5, such that the format of Ethernet frame 200 modified by switch 110 is restored by switch 120 in Ethernet frame 400. In this manner, data packet 100 may also be transmitted between switches 110 and 120.

[0034] FIG. 8 illustrates an example flow chart of a method for transmitting data over the VLAN. As previously mentioned, data may be transmitted between multiple switches independently interconnected over a backplane switch. The data transmission of a data packet is herein described making reference to the flow chart illustrated in FIG. 8, and the example VLAN 10 shown in FIG. 3

[0035] At operation 605, a first switch such as switch 110 receives Ethernet frame 200 shown in FIG. 5, including the VLAN tag 230, over a port such as the protected port 115. The VLAN tag 230 may be formatted according to an industry standard IEEE 802.1Q. At operation 610, switch 110 reads the original CFI field 235 in the VLAN tag 230 to obtain a legacy CFI value.

[0036] At operation 615, a first switch such as switch 110 inserts the LFI tag 370 to create Ethernet frame 300 shown in FIG. 6. The LFI tag 370 may be referred to as a feature information tag, or a data link tag. The LFI tag 370 includes a legacy CFI field 375 which may store the legacy CFI value that is read from the original CFI field 235 of Ethernet frame 200. The LFI tag 370 also includes the protected port field 380, which specifies a port attribute. The protected port field 380 may include the protected port status of the port associated with switch 110. In this example, protected port field 380 would indicate a protected port status as being valid for the protected port 115. If the port associated with the first switch 110 is not protected, then the protected port field 380 would indicate a value of invalid, or non-protected status.

[0037] At operation 620, the transient CFI field 335 of Ethernet frame 300 is modified to include a feature information tag status. The feature information tag status is set to valid to indicate that the LFI tag has been inserted by a switch, such as switch 110.

[0038] At operation 625, a first switch such as switch 110 transmits Ethernet frame 300 across a backplane switch, such as backplane switch 150, to one or more switches, such as switch 120 or switch 130 in FIG. 3. As previously indicated, the data packet 100 may be transmitted to a single destination endpoint or broadcast to multiple endpoints in a VLAN. Fields located in the LFI tag 370 are transparent to the backplane switch 150.

[0039] At operation 630, a second switch such as switch 120 receives Ethernet frame 300. Switch 120 reads the transient CFI field 335 in Ethernet frame 300 to determine if the feature information tag status is valid. The feature information tag status is valid if the LFI tag 370 was inserted by switch 110. If the feature information tag status is valid, then switch 120 proceeds to operation 635. If the feature information tag status is invalid, then the second switch proceeds to operation 650 and forwards the data packet 100 without further processing. In one embodiment, switch 120 may remove the LFI tag 370 when the transient CFI field 335 includes an invalid feature information tag status.

[0040] If switch 120 receives Ethernet frame 200 instead of Ethernet frame 300, it may read the original CFI field 235. Typically, the original CFI field 235 is not used in layer-two data transmissions, and the associate bit is set to off, for example. In one embodiment, switch 120 is able to interpret the value in the original CFI field 235 of an Ethernet frame 200 as providing an invalid feature information tag status when the LFI tag 370 is not present, and therefore proceed to operation 650 and forward the data packet 100 without further processing.

[0041] Data packets sent from a protected port and a non-protected port may each include the L FI tag 370. If a bit in the original CFI field 235 is set, then switch 120 may determine to forward the data packet 100 without further processing if the LFI tag 370 is not detected, or if the bit is not set in the feature valid field 377. Further processing of the Ethernet frame 300, including a valid bit in the transient CFI field 335 and the LFI tag 370, may be performed by switch 120.

[0042] At operation 635, a second switch such as switch 120 reads the LFI tag 370 including the legacy CFI field 375. Switch 120 may therefore read the legacy CFI value from the legacy CFI field 375. In addition switch 120 may read the tag ID field 371, tag valid field 373, feature valid field 377, protected port field 380 and the other field 385.

[0043] In one embodiment, such as in a backplane switching environment, an LFI tag such as LFI tag 370 is added to any Ethernet frame having a CFI bit set, for example, in CFI field 235 or CFI field 335 of FIGS. 5 and 6, respectively. Switch 120 may assume that when a CFI bit is set in CFI field 235 or CFI field 335, that the LFI tag 370 has been inserted into the Ethernet frame 200 or Ethernet frame 300, respectively. If the Ethernet frame 200 comes to switch 120 with the CFI bit set in the CFI field 235, the LFI tag 370 may not include any feature information, in which case the bit in the feature valid field 377 in LFI tag 370 would not be set. In the case of receiving the Ethernet frame 200 without the bit in the feature valid field 377 being set, the switch 120 may proceed to operation 650 and forward the data packet 100 without further processing. Ethernet frames 200 and 300, both including a valid CFI bit and LFI tag 370, may therefore be processed according to the value included in the feature valid field 377.

[0044] At operation 640, a second switch such as switch 120 modifies the transient CFI field 335 in Ethernet frame 300 to restore the legacy CFI value included in the original CFI field 225.

[0045] At operation 645, a second switch such as switch 120 analyzes the information stored in the LFI tag 370. Switch 120 may analyze the data contained in the tag ID field 371 and the feature valid field 377, for example, to determine a transmission protocol. Switch 120 may analyze the data contained in the protected port field 380 to compare the protected port status of a sending port, such as port 115 and a destination port, such as port 125. Switch 120 may then decide to forward or drop the data packet 100 according to the port comparison. Switch 120 may refer to a table such as table 500 shown in FIG. 4 to decide a transmission protocol. In the present example, the sending or source port 515 is identified as protected port 115, and the receiving or destination port 525 is identified as non-protected port 125. According to table 500, a data packet transmitted between a protected source port 515 and a non-protected destination port is forwarded to the destination endpoint.

[0046] At operation 650, a second switch such as switch 120 forwards the data packet 100 to a destination endpoint. Before the data packet 100 is forwarded to the destination endpoint, switch 120 may remove or delete the LFI tag 370 of Ethernet frame 300. With the LFI tag 370 removed and the transient CFI field 335 restored with the legacy CFI value provided in the original CFI field 225, the Ethernet frame has been modified as Ethernet frame 400 in FIG. 7.

[0047] Ethernet frame 400 in FIG. 7 may include the same data and fields as Ethernet frame 200 shown in FIG. 4. In this manner, the data packet 100 included in Ethernet frame 200 and sent by the source endpoint, such as Host A in FIG. 3, may be more easily processed by a destination endpoint, such as Host B, that receives the data packet 100 included in Ethernet frame 400. Ethernet frames 200 and 400 may be indistinguishable by the source and destination endpoints.

[0048] At operation 660, a switch may drop the data packet 100 if both sending and destination ports included in the port comparison are identified as protected ports. For example, a data packet is transmitted by Host A connected to switch 110 in FIG. 3 to one of the destination endpoints connected to switch 130. Switch 130 includes two ports, protected port 135 and non-protected port 137. According to the example transmission protocol identified in table 500 of FIG. 4, a data packet transmitted from Host A to Host C would be dropped because the sending port identified as protected port 115 and the destination port identified as protected port 135, are both protected ports. On the other hand, a data packet transmitted from Host A to Host D would be forwarded because the destination port identified as non-protected port 131, is not a protected port. According to the transmission protocol identified in table 500 of FIG. 4, a data packet is forwarded to any destination port that is identified as being non-protected.

[0049] Table 500 in FIG. 4 may be provided as an algorithm or included in a database. For example, the database may be included in the CPU 50 shown in FIG. 3, or in some other processor or server. Data packets that are broadcast over the VLAN may be independently analyzed by more than one switch according to the same or different transmission protocols. Data included in Ethernet frame 200 and Ethernet frame 300 may be transmitted across the same VLAN. Switches in the VLAN are able to distinguish different types of Ethernet frames according to information stored in the original CFI field 235 or the transient CFI field 335. According to one embodiment, switches are able to provide a protected port, or private VLAN edge, feature for data packets included in Ethernet frame 300.

[0050] The LFI tag 370 includes fields which may be used to provide additional data or instructions for data transmission. Other types of layer-two features and transmission protocols may be implemented accordingly. VLANs and systems including more or fewer endpoints and switches than shown in FIG. 3 may implement the methods described herein, and the above examples are provided for illustrative purposes only.

[0051] The system described above can use dedicated processor systems, micro controllers, programmable logic devices, or microprocessors that perform some or all of the operations. Some of the operations described above may be implemented in software and other operations may be implemented in hardware.

[0052] For the sake of convenience, the operations are described as various interconnected functional blocks or distinct software modules. This is not necessary, however, and there may be cases where these functional blocks or modules are equivalently aggregated into a single logic device, program or operation with unclear boundaries. In any event, the functional blocks and software modules or features of the flexible interface can be implemented by themselves, or in combination with other operations in either hardware or software.

[0053] Having described and illustrated the principles of the invention in a preferred embodiment thereof, it should be apparent that the invention may be modified in arrangement and detail without departing from such principles. We claim all modifications and variation coming within the spirit and scope of the following claims.