WO2008056838A1 - System and method for controlling network traffic - Google Patents

System and method for controlling network traffic Download PDF

Info

Publication number
WO2008056838A1
WO2008056838A1 PCT/KR2006/004657 KR2006004657W WO2008056838A1 WO 2008056838 A1 WO2008056838 A1 WO 2008056838A1 KR 2006004657 W KR2006004657 W KR 2006004657W WO 2008056838 A1 WO2008056838 A1 WO 2008056838A1
Authority
WO
WIPO (PCT)
Prior art keywords
switch
frame
state information
switches
switch state
Prior art date
Application number
PCT/KR2006/004657
Other languages
French (fr)
Inventor
Chang Hwan Cho
Tae Boong Jeon
Original Assignee
Chang Hwan Cho
Tae Boong Jeon
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Chang Hwan Cho, Tae Boong Jeon filed Critical Chang Hwan Cho
Priority to PCT/KR2006/004657 priority Critical patent/WO2008056838A1/en
Publication of WO2008056838A1 publication Critical patent/WO2008056838A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. local area networks [LAN], wide area networks [WAN]
    • H04L12/46Interconnection of networks
    • H04L12/4604LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462LAN interconnection over a bridge based backbone
    • H04L12/4625Single bridge functionality, e.g. connection of two networks over a single bridge
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements

Abstract

Disclosed are system and method for controlling a network traffic. According to the invention, all switches connected with the same VLAN are allowed to share an inherent ID of each switch, a port ID connecting the switches and information about a bandwidth so as to calculate an optimized path that each switch is connected to other switches. For doing so, each switch is systematically structured to comprise a computation module capable of structuring a neighbor relation with other switches, a computation module capable of exchanging/sharing the switch state D/B with the other switches, and synchronizing a corresponding switch state D/B, a computation module capable of creating/updating a switching table, and a computation module capable of switching and flooding a received data frame through an optimized path with reference to the created/updated switching table.

Description

Description

SYSTEM AND METHOD FOR CONTROLLING NETWORK

TRAFFIC

Technical Field

[1] The present invention relates to a system for controlling a network traffic path, and more particularly to a network traffic controlling system allowing all switches consisting a network to individually determine the best switching path, rather than to determine switching path by a single root switch as the prior art. In addition, the invention relates to a network traffic controlling method using such network traffic controlling system. Background Art

[2] As shown in Fig. 1, according to the prior art, a switch network 5 comprises multiple witches 1, 2, 3, 4 connected together and multiple end terminals Ie, If, 2e, 2f, 3e, 3f, 4e, 4f connected to each of the switches 1, 2, 3, 4. In this case, for example, personal computers, servers, routers and the like are used as the end terminals Ie, If, 2e, 2f, 3e, 3f, 4e, 4f.

[3] At this time, each of the switches 1, 2, 3, 4 has ports Ia, Ib, 2a, 2b, 3a, 3b, 4a, 4b for connection with the end terminals Ie, If, 2e, 2f, 3e, 3f, 4e, 4f and ports Ic, Id, 2c, 2d, 3c, 3d, 4c, 4d for connection with other switches.

[4] Conventionally, in order to prevent a frame loop in advance, which can occur in frame switching, a particular switch, for example the switch 1 of the whole switches 1, 2, 3, 4 is selected as a root switch. Accordingly, all frame switching paths of the other switches 2, 3, 4 are determined in reference to the switch 1.

[5] However, when the frame switching operations of the switches 2, 3, 4 are determined by the switch 1, i.e., root switch, there occur many inefficient and unreasonable situations.

[6] For example, under circumstances that switching paths of the whole network are built around the switch 1, frames from switch 3 to switch 4 take a far and inefficient route through <switch 3-switch 1 -switch 2-switch 4> even though there exists a near path made through the ports 3d, 4d.

[7] In other words, according to the single root switch based topology of the prior art, it is highly probable that each of the switches 2, 3, 4 cannot use an optimized switching path when switching frames and is forced to use an inefficient flooding path when flooding frames.

[8] For another example, each of the switches 2, 3, 4 is forced to delay a long time for activation of an alternate port so as to prevent a frame loop from occurring, when its primary link is down. As a result, communications between end terminals 2e, 2f, 3e, 3f, 4e, 4f connected to switches 2, 3, 4 are discontinued for a long time.

[9] In other words, according to the root switch based topology of the prior art, when there occurs a failure in a primary port, each of the switches 2, 3, 4 is forced to delay a long time for activation of a alternate port, concerning about an occurrence of a frame loop.

[10] For still another example, when an ill-intentioned user makes a manipulation of illegally setting another specific switch, for example the switch 4 as a false root switch, rather than the legal root switch, i.e., switch 1, the other switches 1, 2, 3 knowing nothing about it switch all traffics around the switch 4. Under such circumstance, if the switch 4 is inferior to the existing switch 1, each of the switches 1, 2, 3 forms the worst topology in an instant.

[11] In addition, under situation that a switching path is determined in reference to the false root switch, i.e., the switch 4, if an ill-intentioned user connects an monitoring tool to the switch 4 and maliciously monitors all frames passing through the switch 4, users using each of the end terminals Ie, If, 2e, 2f, 3e, 3f suffer such serious damage that the user s information is leaked to the ill-intentioned user or modified or damaged.

[12] In other words, according to the single root switch based structure of the prior art, the user (each of the switches) cannot efficiently cope with security infringement of a network using a non-authenticated false root switch or similar tool or program.

[13] Further, when a switching path of a whole network is determined in reference to the switch 1, each of the switches 2, 3, 4 cannot use multiple paths leading to the same destination because it is worried about an occurrence of the frame loop. Accordingly, switching path load balancing in the same VLAN cannot be achieved.

[14] In other words, according to the root switch based topology of the prior art, each of the switches 2, 3, 4 cannot use redundant paths when forwarding frames because it is worried about the occurrence of the frame loop. Disclosure of Invention Technical Problem

[15] Accordingly, the present invention has been made to solve the above problems. An object of the invention is to allow all switches connected with a same VLAN to share the information regarding <a unique ID of each switch>, <port ID connecting the switches>, < bandwidth of ports connecting switches> and the like in order for each of the switches to provide <a method allowing all switches constituting a system to use best switching paths when switching frames between the switches>, <a method allowing all switches constituting a system to use an optimized flooding path in which a frame loop does not occur, when flooding frames between the switches>, <a method of activating alternate ports without delay in case of a failure of the primary port connecting the switches>, <a method capable of preventing a security infringement of a switch network using a non-authenticated switch or similar tool or program> and <a method capable of a load balancing using redundant links when forwarding frames between switches>. Technical Solution

[16] In order to achieve the above object, there is provided a network traffic controlling system comprising:

[17] multiple switches connected to each other;

[18] multiple ports individually mounted to each of the switches and providing links between switches or between switch and its attached end terminals; and

[19] a switching control module individually mounted to each of the switches, real-time exchange switch state information with other switches whenever switch status is changed, and selecting ports based on the switch state information to forward a frame from directly connected end terminals or other switches depending on characteristics of the frame.

[20] According to another aspect of the invention, there is provided a network traffic controlling method being processed by a switching control module individually mounted to each of the switches connected to other switches through ports, the method comprising steps of:

[21] building a neighborship according to frames transmitted from certain neighbor switch among other switches;

[22] synchronizing switch state information, wherein switch state information retained, with other switches whenever the switch state is changed;

[23] updating and creating a switching table depending on the information of the synchronized switch state information; and

[24] processing a data frame, wherein after a data frame is received, the received data frame is switched or flooded to ports connecting to the destination depending on characteristics of the data frame, with reference to the switching table. Brief Description of the Drawings

[25] The above and other objects, features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[26] FlG. 1 is a conceptional view showing a network traffic controlling system according to the prior art;

[27] FlG. 2 is a conceptional view showing a network traffic controlling system according to an embodiment of the invention; [28] FlG. 3 is a conceptional view showing a detailed structure of a switching control module arranged to each switch according to an embodiment of the invention; [29] FlG. 4 is a conceptional view showing a format of a frame according to an embodiment of the invention; [30] FlG. 5 is a conceptional view showing a format of a hello frame according to an embodiment of the invention; [31] FIGS. 6 to 9 are conceptional views showing data storing states of each neighbor switch D/B arranged to switch 1 to switch 4 according to an embodiment of the invention; [32] FlG. 10 is a conceptional view showing a format of a switch state information frame according to an embodiment of the invention;

[33] FlG. 11 is a conceptional view showing a data storing state of each switch state information D/B arranged to switch 1 to switch4 according to an embodiment of the invention; [34] FIGS. 12 to 15 are conceptional views showing data storing states of each switching tables arranged to switchl to switch4 according to an embodiment of the invention; [35] FIGS. 16 to 19 are conceptional views showing data storing states of each MAC address tables arranged to switchl to switch4 according to an embodiment of the invention; [36] FlG. 20 is a flow chart sequentially showing a network traffic controlling method according to an embodiment of the invention; [37] FlG. 21 is a flow chart sequentially showing a process of forming a neighborship according to an embodiment of the invention; [38] FIGS. 22 and 23 are flow charts sequentially showing a process of forwarding/ receiving switch state information according to an embodiment of the invention; [39] FlG. 24 is a conceptional view showing a format of a acknowledgement frame according to an embodiment of the invention; and [40] FlG. 25 is a flow chart sequentially showing a process of creating a switching table according to an embodiment of the invention.

Mode for the Invention [41] Hereinafter, a preferred embodiment of the present invention will be described with reference to the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. [42] As shown in Fig. 2, a network traffic controlling system 100 according to an embodiment of the invention is a systematically structured system comprising multiple switches 110, 120, 130, 140 connected to each other and multiple end terminals 115, 116, 125, 126, 135, 136, 145, 146 arranged to each of the switches 110, 120, 130, 140.

[43] At this time, ports 111, 112, 121, 122, 131, 132, 141, 142 each connects end terminals 115, 116, 125, 126, 135, 136, 145, 146 to switches 110, 120, 130, 140, and ports 113, 114, 123, 124, 133, 134, 143, 144 each connects other switches.

[44] Hereinafter, for convenience sake, it is assumed that IDs of the switches 100, 120,

130, 140 are respectively 1, 2, 3 and 4, each speed (bandwidth) of the ports 111, 112, 121, 122, 131, 132, 141, 142 connecting the switches 110, 120, 130, 140 each other is all 100 Mbps, and VLAN 1 is set to all ports 111, 112, 121, 122, 131, 132, 141, 142 connecting the switches 110, 120, 130, 140 each other.

[45] Under structure of the network traffic controlling system 100 according to an embodiment of the invention, switching control modules 10, 30, 50, 70, which are inherent to the invention, are further arranged in each of the switches 110, 120, 130, 140, as shown in Fig. 2.

[46] In this case, the switching control modules 10, 30, 50, 70 are individually mounted to each switch 110, 120, 130, 140, and perform functions of real-time exchanging switch state information retained by the other switches whenever the information is changed and selecting the ports 111, 112, 121, 122, 131, 132, 141, 142, 113, 114, 123, 124, 133, 134, 143, 144 based on the switch state information to forward frames received from end terminals directly connected to it or from other switches depending on characteristics of the frames.

[47] As described above, when synchronization of the switch state information is completed, all switches 110, 120, 130, 140 connected with a same VLAN can perceive IDs of the other switches, IDs of the ports connecting the switches each other and bandwidth of the ports. As a result, each of the switches 110, 120, 130, 140 can independently determine best frame switching path, rather than determine a frame path around a single root switch as the prior art.

[48] Under such structure, each of the switching control module 10, 30, 50, 70 according to the invention, for example, the switching control module 10 takes such structure that a switching controller 11, a frame processing unit 12 controlled by the switching controller 11, a neighbor switch control unit 13, a switch state information control unit 15, a switching table control unit 17, a media access control (MAC) address table control unit 19 and the like are systematically combined as shown in Fig. 3 (since functions and process executions of individual constituting elements contained in each of the switches are all the same, function and process execution of each constituting element will be described on the basis of the switchl).

[49] At this time, the switching controller 11 of the switching control module 10 performs functions of controlling a process of forming neighborships with neighbor switches directly connected to the self-switch 1 110, a process of synchronizing switch state information, a process of maintaining a switching table 18 according to the switch state information, and a process of switching or flooding frames depending on the information of the switching table 18.

[50] Under such situations, the frame processing unit 12 which is controlled by the switching controller 11 receives a frame through the ports 111, 112, 113, 114 and then examines the header of the received frame to check information like source switch ID, destination switch ID, source MAC address, destination MAC address, Hop limit, error occurrence and so on. If there is an abnormality, the frame processing unit discards a corresponding frame. If there is no abnormality, the frame processing unit pass control for the frame to the neighbor switch control unit 13, the switch state information control unit 15, the MAC address table control unit 19 and the like, depending on the frame type (control frame, data frame and the like).

[51] Further, the frame processing unit 12 creates a frame header appropriate for each frame type, and switches or floods the frame.

[52] In this case, in all frames exchanged between switches 110, 120, 130, 140, frame type, destination switch ID, source switch ID and Hop limit fields are located next to the source MAC address of an Ethernet frame header, as shown in Fig. 4.

[53] The frame type indicates whether the current frame is a control frame or a data frame, and the Hop limit field is used to prevent frame loops. In this case, the Hop limit count is reduced by one whenever the frame passes though each of the switches. Under such situations, the frame processing unit 12 discards the frame with the value of the Hop limit is 0 (zero), thereby preventing a frame loop that may possibly occur.

[54] In the mean time, the neighbor switch control unit 13 controlled by the switching controller 11 serves to build neighborships with other switches depending on contents of a hello frame (for example, whether or not the self switch ID is recorded in a neighbor switch list item of the hello frame) and records, updates and manages the result to the neighbor switch D/B 14.

[55] In this case, the contents of the ahead hello frame are located in data field of the

Ethernet frame, with the information (for example, type, frame length, authentication password, neighbor switch list and the like) as shown in Fig. 5.

[56] Under such situations that the neighbor switch control unit 13 performs the functions, each neighbor switch D/B 14 stored in each of the switches 110, 120, 130, 140 maintain information such as neighbor switch ID, port ID to be connected to the neighbor switch, VLAN ID the port belongs to and the like, as shown in Figs. 6 to 9 (Fig. 6 shows the neighbor switch D/B contents of the switchl, Fig. 7 shows the neighbor switch D/B contents of the switch2, Fig. 8 shows the neighbor switch D/B contents of the switch3, and Fig. 9 shows the neighbor switch D/B contents of the switch4).

[57] In addition, the switch state information control unit 15 controlled by the switching controller 11 serves to update and manage the switch state information recorded in the switch state information D/B 16, depending on changed contents of the state information frame of the self-arranged switch 110 (i.e., switchl) or the switch state information frame received (transmitted) from the other switches 120, 130, 140 (for example, whether received switch state information is new or not, compared to the already stored information).

[58] In this case, the contents of the ahead switch state information frame are located in data field of the Ethernet frame, with the information (for example, type, frame length, authentication password, frame number, acknowledgement number, created switch ID, other switch ID, port ID, created sequence number, bandwidth and the like) as shown in Fig. 10.

[59] When the switch state information control unit 15 performs the functions, the switch state information stored in the switch state information D/B 16 of each switches 110, 120, 130, 140 can be synchronized to maintain all the information such as VLAN ID, originating switch ID, neighbor switch ID, port ID, bandwidth, sequence number and the like to be same, as shown in Fig. 11.

[60] After <the updating procedure of the switch state information D/B 16> is processed, the switch state information control unit 15 again determines whether there exists a neighbor switch to which the switch state information should be sent, among the neighbor switches connected with the same VLAN ID. If there exists a corresponding neighbor switch, the switch state information control unit further processes a procedure of sending the switch state information to each of the neighbor switches, with reference to the ahead neighbor switch D/B 14.

[61] As a result, all the switches connected with the same VLAN can have identical information such as <switch ID>, <port ID connecting the switches each other>, < bandwidth> and the like, through the information synchronization procedure> of the invention.

[62] In the mean time, the switching table control unit 17 controlled by the switching controller 11 applies the Dijkstra algorithm based on the contents recorded in the above described switch state information D/B 16 to determine <the best paths to another switch through a specific VLAN> and to update the switching table 18.

[63] As a result that each switching table control unit 17 performs the functions thereof, the switching tables 18 of the switches 110, 120, 130, 140, which are finally created, can maintain <the information for the best path (path cost, output port) to the destination switch>, as shown in Figs. 12 to 15 (Fig. 12 shows contents of the switching table of the switchl, Fig. 13 shows contents of the switching table of the switch2, Fig. 14 shows contents of the switching table of the switch3 and Fig. 15 shows contents of the switching table of the switch4).

[64] In addition, when a frame is received via the ports 111, 112, 113, 114, the MAC address table control unit 19 controlled by the switching controller 11 checks the source MAC address of the frame and updates the MAC address table 20.

[65] At this time, if the source MAC address of the frame does not exist in the MAC address table 20, the MAC address table control unit 19 processes a procedure of recording an ID of the VLAN to which the frame belongs, an ID of the switch from which the frame is first originated, a corresponding MAC address, the number of the port having received the frame and the like to the MAC address table 20.

[66] However, if the source MAC address of the frame exists in the MAC address table

20, the MAC address table control unit 19 resets aging timer of the MAC address.

[67] Assuming that the MAC addresses of the end terminals 115, 116 connected to the switchl 110 are 1515.1515.1515 and 1616.1616.1616, the MAC addresses of the end terminals 125, 126 connected to the switch2 120 are 2525.2525.2525 and 2626.2626.2626, the MAC addresses of the end terminals 135, 136 connected to the switch3 130 are 3535.3535.3535 and 3636.3636.3636, the MAC addresses of the end terminals 145, 146 connected to the switch4 140 are 4545.4545.4545 and 4646.4646.4646, and all the end terminals transmit frames, the MAC address tables of the switches 110, 120, 130, 140 have the recorded information as shown in Figs. 16 to 19 (Fig. 16 shows contents of the MAC address table of the switchl, Fig. 17 shows contents of the MAC address table of the switch2, Fig. 18 shows contents of the MAC address table of the switch3 and Fig. 19 shows contents of the MAC address table of the switch4).

[68] Hereinafter, a network traffic controlling method of the invention using the network traffic controlling system 100 having the above described structure will be specifically explained.

[69] As shown in Fig. 20, under circumferences that the invention is embodied, the switching controllers of the switching control module 10, 30, 50, 70 mounted to the switches 110, 120, 130, 140, for example the switching controller 11 mounted to the switchl 110 processes a forming neighborship procedure by updating the neighbor switch D/B 14, based on the information of the frame (for example, hello frame as shown in Fig. 5) received from the neighbor switches, for example the switch2 120 and the switch3 130 (SlOO).

[70] In this case, as shown in Fig. 21, the switching controller 11 first initializes the neighbor switch D/B 14 using the neighbor switch control unit 13, and then sends hello frame periodically to all activated ports (SlOl) and determines whether hello frames sent by the neighbor switches 120, 130 are received or not (S102). [71] At this time, if the hello frames from the neighbor switches 120, 130 are received, the switching controller 11 determines whether the password in the hello frame is identical with the already registered password of the corresponding neighbor switches 120, 130 using the neighbor switch control unit 13 and discards the frames when the passwords are different from each other (in embodying the invention, when it is desired to use authentication password for diverse control frames which are transmitted/received between neighbor switches, for example hello frame, switch state information frame, acknowledgement frame and the like, the processing manner thereof is the same as that described above and thus descriptions of the case of using the password will be omitted for convenience sake).

[72] However, when the password in the hello frames received from the neighbor switches 120, 130 is identical with registered password of the neighbor switches 120, 130 or a password is not used, the switching controller 11 processes a procedure of adding the ID of the neighbor switch (i.e., neighbor switch having transmitted the hello frame) to the neighbor switch list in the hello frame which will be sent from that time on.

[73] Subsequently, the switching controller 11 determines whether its switch ID is in the neighbor switch list of the hello frame received from other switches(S104). If the switch ID of the received switch is included in the neighbor switch list of the hello frame received from the other, the controller considers the other switch as a neighbor switch and records the corresponding switch information to the neighbor switch D/B 14 using the neighbor switch control unit 13 (S105). As a result, the neighbor switch information stored in the neighbor switch D/B 14 of each switch 110, 120, 130, 140 can maintain the recorded information as shown in Figs. 6 to 9 (for example, neighbor switch ID, port number connecting the neighbor switch, VLAN number connected to the neighbor switch and the like).

[74] In the mean time, when the process of forming neighborship is completed through the above procedures, the switching controller 11 processes a procedure of synchronizing the switch state information with the other switches 120, 130, 140 (SIlO).

[75] In this case, as shown in Fig. 22, the switching controller 11 checks the state changes such as new neighborship, receipt of new switch state information frame from neighbor switch, addition of VLAN's, change of bandwidth and the like, using the switch state information control unit 15 and thus determines whether the switch state information is updated or not (Sill).

[76] At this time, if it is determined that the switch state information is changed, the switching controller 11 updates the changed information to the switch state information D/B 14 using the switch state information control unit 15 (Sl 12) and then determines whether there exists a switch to which the new switch state information should be sent, among the neighbor switches connected with the same VLAN (Sl 13).

[77] If there exists a remaining switch except the switch having sent the switch state information, the switching controller 11 forwards the ahead new switch state information to the other switch, for example switch2 120 or switch3 130 (Sl 14).

[78] Subsequently, the switching controller 11 determines the receipt of acknowledgement frames from the other switches 120, 130 having received the ahead switch state information frames, using the switch state information control unit 15.

[79] In this case, the acknowledgement frame includes information such as frame type, authentication password, acknowledgement number and the like as shown in Fig. 24.

[80] At this time, acknowledgement frames are not received from the other neighbor switches 120, 130 having received the ahead switch state information frames within retransmit interval, the switching controller 11 retransmits the same switch state information frame for a predetermined count. Nevertheless, if acknowledgement frames are not received from the other neighbor switches 120, 130, the controller resets the existing neighbor relations with the switches 120, 130.

[81] However, if acknowledgement frames are received from the other neighbor switches 120, 130 having received the ahead switch state information frames, the switching controller 11 determines whether there is remaining switch state information having not been transmitted in the switch state information D/B 16. When there exists, it repeatedly transmits the remaining switch state information.

[82] After sending all the new switch state information to the specific neighbor switches connected with the same VLAN through the above procedures, the switch control controller 11 checks whether there exists a remaining neighbor switch to which the new switch state information should be sent (Sl 15). If there exists, it sends the new switch state information.

[83] In the mean time, when receiving the switch state information frame, the switch control controller 11 processes a procedure based a flowchart as shown in Fig. 23.

[84] In this case, the switch control controller 11 first determines whether the switch state information frame is received from the other neighbor switches 120, 130 through the frame processing unit 12 (S 121).

[85] At this time, when the switch state information frame is received from the other neighbor switches 120, 130, the switch control controller 11 transmits acknowledgement frame (refer to Fig. 24) to the switch which sent the switch state information frame and then determines whether the information in the switch state information frame is new compared to that of the already stored in the switch state information D/B 16 (S 122). If it is new, the controller stores the new information in the switch state information D/B (S 123).

[86] At this time, if it is determined that the information of the received switch state in- formation frame is same as the switch state information already stored in its switch state information D/B 16, the switch control controller 11 ignores the received information (S124).

[87] However, if it is determined that the data in the switch state information frame is old compared to the switch state information already stored in its switch state information D/B 16, the switch control controller 11 sends its switch state information frame to the neighbor switch so that the neighbor switches 120, 130 can retain the newest information (S 125).

[88] As a result, when the above process of synchronizing the switch state information is completed, all the switches connected with the same VLAN will have the identical switch state information D/B 16, as shown in Fig. 11.

[89] With the synchronized switch state information, each of the switches 110, 120, 130,

140 can independently determine best switching paths, rather than determine frame paths by a single root switch.

[90] Needless to say, under the situations that the independent frame switching path is structured, all the switches 110, 120, 130, 140 connected with the same VLAN can independently switch or flood frames using the synchronized switching state information retained by itself, without the need of the single root switch. As a result, optimized switching and flooding paths are built without a frame loop.

[91] In case of active link failure, under the situations that the independent frame switching path is determined, each of the switches 110, 120, 130, 140 can activate alternate ports immediately without an occurrence of a frame loop. As a result, the end terminals 115, 116, 125, 126, 135, 136, 145, 146 connected to the switches 110, 120,130, 140 can resume communication in the shortest time.

[92] Additionally, under the information share management structure of each of the switches 110, 120, 130, 140 connected with the same VLAN, even when an ill- intentioned user tries an illegal operation using a non-authenticated switch or similar tool or program, each of the switches 110, 120, 130, 140 serves as a separate root switch and can thus independently operate. Accordingly, it is possible to normally progress the frame switching procedure given to itself, without a particular effect.

[93] Needless to say, since each of the switches 110, 120, 130, 140 builds an optimized path according to an independent determination even when an illegal operations is tried with the non-authenticated switch or similar tool or program, the user can easily prevent such serious damages that the information of the user is leaked to an ill- intentioned user or modified or damaged by the ill-intentioned user.

[94] Further, when the information of the switches 110, 120, 130, 140 are share- managed, each of the switches 110, 120, 130, 140 uses multiple paths toward the same destination. Accordingly, a very effective load balancing switch path can be built. [95] Meanwhile, when the switch state information synchronizing step (Sl 10) is completed through the above processes, the switching controller 11 processes a switching table updating step of updating/recording the recorded information of the switching table 18, based on the information of the switch state information stored in the switch state D/B 16 (S 130).

[96] In this case, as shown in Fig. 25, the switching controller 11 first selects the switch state information for the first VLAN ID, and again selects the first switch ID from the selected switch state information (S 132). Then, the controller applies Dijkstra algorithm to the selected switch state information and calculates <the best paths to the corresponding destination switch through a specific VLAN from the current switch (i.e., switchl)> based on the algorithm (S133) and then records the calculated result to the switching table 18.

[97] After that, when there exists another switch belonging to the same VLAN, the controller repeats the procedures of calculating <the best paths to the selected destination switches> and recording the paths to the switching table (S131, S 132, S133, S134).

[98] When the switching path calculation for a specific VLAN is completed through the above procedures, the switching controller 11 determines whether there exists another VLAN in the switch state information D/B (S 136). If there exists, the controller repeats the procedures of calculating the best paths for all the destination switches through the same procedures (S 131, S 132, S 133, S 134, S 135, S 136) to create the switching table 18 to which all <the best paths from the current switch to each destination switch through each VLAN assigned to the current switch> are recorded.

[99] When the above procedures are completed, each switching table created in the respective switches can maintain <the recorded information having the best path (port cost, output port) from the self switch to the destination switch through the VLAN included therein>, as shown in Figs. 12 to 15.

[100] In the mean time, when the switching table creating process as described above is completed, all the switches 110, 120, 130, 140 arranged to the system 100 of the invention are ready to transmit/receive data frames.

[101] At this time, the manner of forwarding data frames to the destination is divided into switching and flooding. In a narrow sense, the switching is meant to transmit the data frame to specific ports only and the flooding is meant to transmit the received data frame to all the ports except the port having received the frame among the ports assigned to the same VLAN.

[102] When the destination MAC address of the received data frame is a unicast address and present in the MAC address table, each of the switches 110, 120, 130, 140 switches the corresponding frame. When the destination MAC address of the received frame is broadcast or multicast address or is a frame having a unicast MAC address that is not present in the MAC address table, the switches 110, 120, 130, 140 flood the frame.

[103] Under such situations, as shown in Fig. 20, when the switching controller 11 of each switch, for example the switch 1 110 receives a data frame through the specific ports 111, 112, 113, 114, it checks the source MAC address using the MAC address table control unit 19 (S 150) and updates the recorded information of the MAC address table 20 according to the MAC address information of the frame (S 151).

[104] At this time, if the source MAC address recorded to the frame is an address not present in the MAC address table 20, the MAC address table control unit 19 processes a procedure of recording VLAN ID to which the frame is assigned, switch ID from which the frame is first transmitted, a corresponding MAC address, port number having received the frame and the like to the MAC address table 20.

[105] However, if the source MAC address of the frame is present in the MAC address table 20, the MAC address table control unit 19 resets aging timer of the corresponding MAC address.

[106] When the updating procedure of the MAC address table 20 using the source MAC address of the received frame is completed through the above process, the switching controller 11 checks the destination MAC address of the current data frame using the frame processing unit 12 and thus determines whether the current data frame should be flooded or not (S 161).

[107] At this time, if the current data frame should not be flooded (i.e., the current frame should be switched because the destination MAC address is present in the MAC address table), the switching controller 11 processes a procedure of forwarding the data frame to a port leading to the destination through the frame processing unit 12 with reference to the MAC address table 20 (S 162).

[108] However, if the current data frame should be flooded, the switching controller again determines whether the current data frame is <a frame originated from end terminal attached to it> or <a frame originated from other switch> using the frame processing unit 12 (S 163).

[109] At this time, if the flooding frame is <a frame received from other switch>, the switching controller 11 refers to the source switch ID and the switching table 18 through the frame processing unit 12 and floods the frame only when it is received through a best port leading to the source switch (S 165) or discards the frame (S 164).

[110] When there exist multiple best ports leading to the specific source switch, the switching controller 11 selects the port having the lowest port ID as a best port.

[Ill] However, if a flooding frame is received from <the end terminal directly connected to the switch (i.e., switchl)>, the switching controller 11 transmits the frame to all ports except a receiving port among the ports assigned to the same VLAN (S 165).

[112] Needless to say, under such structure of the invention, since the switching controller

11 determines whether the flooding frame should be received or discarded with reference to the source switch ID of the flooding frame and the switching table 18, each data frame (for example, flooding frame) can use <an best flooding path without an occurrence of a frame loop.> Industrial Applicability

[113] As described above, according to the invention, since all the switches arranged to the system of the invention share all information about the whole system, it is possible to induce each switch to independently determine and use a best frame switching path. Also, a topology of activated switch network can be intuitively checked, so that it is possible to easily induce the setting, maintenance and troubleshooting processes. In addition, when there occurs a network failure, it is possible to induce so that a alternate path can be used immediately and an internal security infringement of a weak switch network can be prevented. Additionally, an optimized load balancing is embodied, so that it is possible to induce the expensive computation resources such as link connecting the ports or switches to be used to the utmost.

[114] While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made thereto without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

Claims
[1] A network traffic controlling system comprising: multiple switches connected to each other; multiple ports individually mounted to each of the switches and providing links between corresponding switches and end terminals or links between corresponding switches and the other switches; and a switching control module individually mounted to each of the switches, realtime exchanging switch state information retained by the other switches whenever the information is changed, and selecting ports based on the switch state information to forward frames transmitted from end terminals or the other switches depending on the frame types.
[2] The system according to claim 1, wherein the switching control module comprises: a switching controller wholly controlling a process of building neighborship with neighbor switches directly connected, a process of exchanging and updating the switch state information, a process of recording and updating a switching table depending on the the switch state information, and a process of switching or flooding a frame depending on the switching table; a neighbor switch control unit controlled by the switching controller and forming neighborship, depending on contents of frames transmitted from the neighbor switches; a switch state information control unit controlled by the switching controller and updating switch state information already recorded, depending on a change of state information of a self assigned switch or contents of frames transmitted from the other switches; a switching table control unit controlled by the switching controller and updating a switching table based on the switch state information; and a frame processing unit connected to the switching controller, checking whether there is an abnormality in each of the frames received through the ports, creating a frame header appropriate for the frame, and then switching or flooding a corresponding frame to a port connecting to a destination with reference to the switching table.
[3] The system according to claim 2, further comprising a media access control
(MAC) address table control unit controlled by the switching controller and updating the MAC address table, correspondingly to a source MAC address recorded to each frame received through the port.
[4] A network traffic controlling method being progressed by a switching control module individually mounted to each switches connected to other switches through ports, the method comprising steps of: building a neighborship according to frames transmitted from certain neighbor switches among the other switches; synchronizing switch state information, wherein switch state information retained by the other switches is real-time exchanged whenever the information is changed; updating a switching table according to the synchronized switch state information; and processing a data frame, wherein after a data frame is received, the received data frame is switched or flooded to a port connecting to a destination depending on the frame types, with reference to the switching table.
[5] The method according to claim 4, wherein the step of building the neighborship comprises sub-steps of: determining whether a hello frame is received from the neighbor switches while sending a self hello frame to all activated ports; when the hello frame is received from the neighbor switches, determining whether a self switch ID is included in the neighbor switch list of the received hello frame; and when the self switch ID is included in the neighbor switch list of the hello frame, recording information of a neighbor switch having transmitted the hello frame to a neighbor switch D/B.
[6] The method according to claim 5, wherein the step of building neighborship further comprises sub-steps of: when the hello frame is received from the neighbor switches, determining whether a password in the hello frame is identical with a password of the corresponding neighbor switch already registered; and when the password in the hello frame is different from the password of the corresponding neighbor switch already registered, discarding the corresponding hello frame.
[7] The method according to claim 5, wherein the step of building neighborship further comprises a sub-step of: when the hello frame is received from the neighbor switches, adding an ID of a neighbor switch having transmitted the hello frame to a neighbor switch list of a self hello frame to be transmitted subsequently.
[8] The method according to claim 4, wherein the step of synchronizing the switch state information comprises sub-steps of: checking/determining whether the switch state information is changed or not; when the switch state information is changed, recording the changed information to the switch state information D/B; determining whether there exists a switch to which the switch state information should be sent among the neighbor switches connected with a same VLAN ID as a VLAN K) set to itself; and when there exists the neighbor switch to which the switch state information should be sent, sending the switch state information to a corresponding neighbor switch.
[9] The method according to claim 4, wherein the step of synchronizing the switch state information comprises sub-steps of: determining whether the switch state information is received from the other switches; when the switch state information is received, determining whether the received switch state information is new compared to that of the already stored in the switch state information D/B; when the received information is new compared to the information already stored in the switch state information D/B, updating the information already stored in the switch state information D/B, when the recorded information of the switch state information is same as the information already stored in the switch state information D/B, ignoring the corresponding switch state information, and when the recorded information of the switch state information is old compared to the information already stored in the switch state information D/B, sending current switch's switch state information to the other switch to induce retained information of the corresponding switch to be modified.
[10] The method according to claim 4, wherein the step of updating/creating the switching table comprises sub-steps of: selecting switch state information of another switch having a specific VLAN ID among the synchronized switch state information, calculating a Dijkstra algorithm with regard to the selected switch state information to calculate the fastest path from the current switch to the selected switch via the selected VLAN; recording the fastest path from the current switch to the selected switch via the selected VLAN to the switching table; and repeatedly performing the procedures of calculating the Dijkstra algorithm and recording the fastest path to the switching table with regard to state information of still another switches having still another ID to create a final switching table having the fastest path from the current switch to all the other destination switches via all the other VLANs included therein. [11] The method according to claim 4, wherein the step of processing the data frame comprises sub-steps of: checking a media access control (MAC) address of the data frame to determine whether the data frame is subject to switching or flooding; when the data frame is to be switched, forwarding the data frame to a port con necting to a destination, with reference to a MAC address table; when the data frame is to be flooded, determining whether the frame is originated from an end terminal connected to the current switch or a frame originated from other switch; when the data frame is a frame originated from an end terminal, forwarding the frame to all other switches arranged to the same VLAN as the receiving port; and when the data frame is a frame originated from another switch, further determining whether it is received through an optimized port with reference to a source switch ID of the frame and the switching table and when the frame is received through the optimized port, transmitting the frame to other ports arranged to a same VLAN as the receiving port.
PCT/KR2006/004657 2006-11-08 2006-11-08 System and method for controlling network traffic WO2008056838A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/KR2006/004657 WO2008056838A1 (en) 2006-11-08 2006-11-08 System and method for controlling network traffic

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/KR2006/004657 WO2008056838A1 (en) 2006-11-08 2006-11-08 System and method for controlling network traffic

Publications (1)

Publication Number Publication Date
WO2008056838A1 true WO2008056838A1 (en) 2008-05-15

Family

ID=39364638

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2006/004657 WO2008056838A1 (en) 2006-11-08 2006-11-08 System and method for controlling network traffic

Country Status (1)

Country Link
WO (1) WO2008056838A1 (en)

Cited By (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2940952A1 (en) * 2014-04-30 2015-11-04 Brocade Communications Systems, Inc. Method and system for facilitating switch virtualization in a network of interconnected switches
US9270572B2 (en) 2011-05-02 2016-02-23 Brocade Communications Systems Inc. Layer-3 support in TRILL networks
US9374301B2 (en) 2012-05-18 2016-06-21 Brocade Communications Systems, Inc. Network feedback in software-defined networks
US9401818B2 (en) 2013-03-15 2016-07-26 Brocade Communications Systems, Inc. Scalable gateways for a fabric switch
US9401872B2 (en) 2012-11-16 2016-07-26 Brocade Communications Systems, Inc. Virtual link aggregations across multiple fabric switches
US9413691B2 (en) 2013-01-11 2016-08-09 Brocade Communications Systems, Inc. MAC address synchronization in a fabric switch
US9450870B2 (en) 2011-11-10 2016-09-20 Brocade Communications Systems, Inc. System and method for flow management in software-defined networks
US9455935B2 (en) 2010-06-08 2016-09-27 Brocade Communications Systems, Inc. Remote port mirroring
US9461911B2 (en) 2010-06-08 2016-10-04 Brocade Communications Systems, Inc. Virtual port grouping for virtual cluster switching
US9461840B2 (en) 2010-06-02 2016-10-04 Brocade Communications Systems, Inc. Port profile management for virtual cluster switching
US9485148B2 (en) 2010-05-18 2016-11-01 Brocade Communications Systems, Inc. Fabric formation for virtual cluster switching
US9524173B2 (en) 2014-10-09 2016-12-20 Brocade Communications Systems, Inc. Fast reboot for a switch
US9544219B2 (en) 2014-07-31 2017-01-10 Brocade Communications Systems, Inc. Global VLAN services
US9548873B2 (en) 2014-02-10 2017-01-17 Brocade Communications Systems, Inc. Virtual extensible LAN tunnel keepalives
US9548926B2 (en) 2013-01-11 2017-01-17 Brocade Communications Systems, Inc. Multicast traffic load balancing over virtual link aggregation
US9565099B2 (en) 2013-03-01 2017-02-07 Brocade Communications Systems, Inc. Spanning tree in fabric switches
US9565028B2 (en) 2013-06-10 2017-02-07 Brocade Communications Systems, Inc. Ingress switch multicast distribution in a fabric switch
US9565113B2 (en) 2013-01-15 2017-02-07 Brocade Communications Systems, Inc. Adaptive link aggregation and virtual link aggregation
US9602430B2 (en) 2012-08-21 2017-03-21 Brocade Communications Systems, Inc. Global VLANs for fabric switches
US9608833B2 (en) 2010-06-08 2017-03-28 Brocade Communications Systems, Inc. Supporting multiple multicast trees in trill networks
US9628336B2 (en) 2010-05-03 2017-04-18 Brocade Communications Systems, Inc. Virtual cluster switching
US9628407B2 (en) 2014-12-31 2017-04-18 Brocade Communications Systems, Inc. Multiple software versions in a switch group
US9628293B2 (en) 2010-06-08 2017-04-18 Brocade Communications Systems, Inc. Network layer multicasting in trill networks
US9626255B2 (en) 2014-12-31 2017-04-18 Brocade Communications Systems, Inc. Online restoration of a switch snapshot
US9660939B2 (en) 2013-01-11 2017-05-23 Brocade Communications Systems, Inc. Protection switching over a virtual link aggregation
US9699117B2 (en) 2011-11-08 2017-07-04 Brocade Communications Systems, Inc. Integrated fibre channel support in an ethernet fabric switch
US9699029B2 (en) 2014-10-10 2017-07-04 Brocade Communications Systems, Inc. Distributed configuration management in a switch group
US9699001B2 (en) 2013-06-10 2017-07-04 Brocade Communications Systems, Inc. Scalable and segregated network virtualization
US9716672B2 (en) 2010-05-28 2017-07-25 Brocade Communications Systems, Inc. Distributed configuration management for virtual cluster switching
US9729387B2 (en) 2012-01-26 2017-08-08 Brocade Communications Systems, Inc. Link aggregation in software-defined networks
US9736085B2 (en) 2011-08-29 2017-08-15 Brocade Communications Systems, Inc. End-to end lossless Ethernet in Ethernet fabric
US9742693B2 (en) 2012-02-27 2017-08-22 Brocade Communications Systems, Inc. Dynamic service insertion in a fabric switch
US9769016B2 (en) 2010-06-07 2017-09-19 Brocade Communications Systems, Inc. Advanced link tracking for virtual cluster switching
US9800471B2 (en) 2014-05-13 2017-10-24 Brocade Communications Systems, Inc. Network extension groups of global VLANs in a fabric switch
US9807007B2 (en) 2014-08-11 2017-10-31 Brocade Communications Systems, Inc. Progressive MAC address learning
US9807005B2 (en) 2015-03-17 2017-10-31 Brocade Communications Systems, Inc. Multi-fabric manager
US9806949B2 (en) 2013-09-06 2017-10-31 Brocade Communications Systems, Inc. Transparent interconnection of Ethernet fabric switches
US9807031B2 (en) 2010-07-16 2017-10-31 Brocade Communications Systems, Inc. System and method for network configuration
US9848040B2 (en) 2010-06-07 2017-12-19 Brocade Communications Systems, Inc. Name services for virtual cluster switching
US9887916B2 (en) 2012-03-22 2018-02-06 Brocade Communications Systems LLC Overlay tunnel in a fabric switch
US9912614B2 (en) 2015-12-07 2018-03-06 Brocade Communications Systems LLC Interconnection of switches based on hierarchical overlay tunneling
US9912612B2 (en) 2013-10-28 2018-03-06 Brocade Communications Systems LLC Extended ethernet fabric switches
US9942097B2 (en) 2015-01-05 2018-04-10 Brocade Communications Systems LLC Power management in a network of interconnected switches
US10003552B2 (en) 2015-01-05 2018-06-19 Brocade Communications Systems, Llc. Distributed bidirectional forwarding detection protocol (D-BFD) for cluster of interconnected switches
US10038592B2 (en) 2015-03-17 2018-07-31 Brocade Communications Systems LLC Identifier assignment to a new switch in a switch group
US10171303B2 (en) 2015-09-16 2019-01-01 Avago Technologies International Sales Pte. Limited IP-based interconnection of switches with a logical chassis
US10237090B2 (en) 2016-10-28 2019-03-19 Avago Technologies International Sales Pte. Limited Rule-based network identifier mapping
US10277464B2 (en) 2012-05-22 2019-04-30 Arris Enterprises Llc Client auto-configuration in a multi-switch link aggregation

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5521905A (en) * 1993-07-22 1996-05-28 Kakusai Denshin Denwa Co., Ltd. Adaptive traffic control apparatus and method for controlling connection of arriving calls
US6453351B1 (en) * 1993-09-13 2002-09-17 Hitachi, Ltd. Traffic control method and network control system
US20060291480A1 (en) * 2005-06-23 2006-12-28 Chang Hwan Cho System and method for controlling network traffic

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5521905A (en) * 1993-07-22 1996-05-28 Kakusai Denshin Denwa Co., Ltd. Adaptive traffic control apparatus and method for controlling connection of arriving calls
US6453351B1 (en) * 1993-09-13 2002-09-17 Hitachi, Ltd. Traffic control method and network control system
US20060291480A1 (en) * 2005-06-23 2006-12-28 Chang Hwan Cho System and method for controlling network traffic

Cited By (62)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9628336B2 (en) 2010-05-03 2017-04-18 Brocade Communications Systems, Inc. Virtual cluster switching
US9485148B2 (en) 2010-05-18 2016-11-01 Brocade Communications Systems, Inc. Fabric formation for virtual cluster switching
US9942173B2 (en) 2010-05-28 2018-04-10 Brocade Communications System Llc Distributed configuration management for virtual cluster switching
US9716672B2 (en) 2010-05-28 2017-07-25 Brocade Communications Systems, Inc. Distributed configuration management for virtual cluster switching
US9461840B2 (en) 2010-06-02 2016-10-04 Brocade Communications Systems, Inc. Port profile management for virtual cluster switching
US9769016B2 (en) 2010-06-07 2017-09-19 Brocade Communications Systems, Inc. Advanced link tracking for virtual cluster switching
US9848040B2 (en) 2010-06-07 2017-12-19 Brocade Communications Systems, Inc. Name services for virtual cluster switching
US9608833B2 (en) 2010-06-08 2017-03-28 Brocade Communications Systems, Inc. Supporting multiple multicast trees in trill networks
US9455935B2 (en) 2010-06-08 2016-09-27 Brocade Communications Systems, Inc. Remote port mirroring
US9461911B2 (en) 2010-06-08 2016-10-04 Brocade Communications Systems, Inc. Virtual port grouping for virtual cluster switching
US9628293B2 (en) 2010-06-08 2017-04-18 Brocade Communications Systems, Inc. Network layer multicasting in trill networks
US9807031B2 (en) 2010-07-16 2017-10-31 Brocade Communications Systems, Inc. System and method for network configuration
US10348643B2 (en) 2010-07-16 2019-07-09 Avago Technologies International Sales Pte. Limited System and method for network configuration
US9270572B2 (en) 2011-05-02 2016-02-23 Brocade Communications Systems Inc. Layer-3 support in TRILL networks
US9736085B2 (en) 2011-08-29 2017-08-15 Brocade Communications Systems, Inc. End-to end lossless Ethernet in Ethernet fabric
US9699117B2 (en) 2011-11-08 2017-07-04 Brocade Communications Systems, Inc. Integrated fibre channel support in an ethernet fabric switch
US10164883B2 (en) 2011-11-10 2018-12-25 Avago Technologies International Sales Pte. Limited System and method for flow management in software-defined networks
US9450870B2 (en) 2011-11-10 2016-09-20 Brocade Communications Systems, Inc. System and method for flow management in software-defined networks
US9729387B2 (en) 2012-01-26 2017-08-08 Brocade Communications Systems, Inc. Link aggregation in software-defined networks
US9742693B2 (en) 2012-02-27 2017-08-22 Brocade Communications Systems, Inc. Dynamic service insertion in a fabric switch
US9887916B2 (en) 2012-03-22 2018-02-06 Brocade Communications Systems LLC Overlay tunnel in a fabric switch
US9374301B2 (en) 2012-05-18 2016-06-21 Brocade Communications Systems, Inc. Network feedback in software-defined networks
US9998365B2 (en) 2012-05-18 2018-06-12 Brocade Communications Systems, LLC Network feedback in software-defined networks
US10277464B2 (en) 2012-05-22 2019-04-30 Arris Enterprises Llc Client auto-configuration in a multi-switch link aggregation
US9602430B2 (en) 2012-08-21 2017-03-21 Brocade Communications Systems, Inc. Global VLANs for fabric switches
US9401872B2 (en) 2012-11-16 2016-07-26 Brocade Communications Systems, Inc. Virtual link aggregations across multiple fabric switches
US10075394B2 (en) 2012-11-16 2018-09-11 Brocade Communications Systems LLC Virtual link aggregations across multiple fabric switches
US9548926B2 (en) 2013-01-11 2017-01-17 Brocade Communications Systems, Inc. Multicast traffic load balancing over virtual link aggregation
US9774543B2 (en) 2013-01-11 2017-09-26 Brocade Communications Systems, Inc. MAC address synchronization in a fabric switch
US9413691B2 (en) 2013-01-11 2016-08-09 Brocade Communications Systems, Inc. MAC address synchronization in a fabric switch
US9660939B2 (en) 2013-01-11 2017-05-23 Brocade Communications Systems, Inc. Protection switching over a virtual link aggregation
US9807017B2 (en) 2013-01-11 2017-10-31 Brocade Communications Systems, Inc. Multicast traffic load balancing over virtual link aggregation
US9565113B2 (en) 2013-01-15 2017-02-07 Brocade Communications Systems, Inc. Adaptive link aggregation and virtual link aggregation
US9565099B2 (en) 2013-03-01 2017-02-07 Brocade Communications Systems, Inc. Spanning tree in fabric switches
US9871676B2 (en) 2013-03-15 2018-01-16 Brocade Communications Systems LLC Scalable gateways for a fabric switch
US9401818B2 (en) 2013-03-15 2016-07-26 Brocade Communications Systems, Inc. Scalable gateways for a fabric switch
US9699001B2 (en) 2013-06-10 2017-07-04 Brocade Communications Systems, Inc. Scalable and segregated network virtualization
US9565028B2 (en) 2013-06-10 2017-02-07 Brocade Communications Systems, Inc. Ingress switch multicast distribution in a fabric switch
US9806949B2 (en) 2013-09-06 2017-10-31 Brocade Communications Systems, Inc. Transparent interconnection of Ethernet fabric switches
US9912612B2 (en) 2013-10-28 2018-03-06 Brocade Communications Systems LLC Extended ethernet fabric switches
US9548873B2 (en) 2014-02-10 2017-01-17 Brocade Communications Systems, Inc. Virtual extensible LAN tunnel keepalives
US10355879B2 (en) 2014-02-10 2019-07-16 Avago Technologies International Sales Pte. Limited Virtual extensible LAN tunnel keepalives
EP3288228A1 (en) * 2014-04-30 2018-02-28 Brocade Communications Systems, Inc. Method and system for facilitating switch virtualization in a network of interconnected switches
CN105049360A (en) * 2014-04-30 2015-11-11 博科通讯系统有限公司 Method and system for facilitating switch virtualization in network of interconnected switches
EP2940952A1 (en) * 2014-04-30 2015-11-04 Brocade Communications Systems, Inc. Method and system for facilitating switch virtualization in a network of interconnected switches
US10063473B2 (en) 2014-04-30 2018-08-28 Brocade Communications Systems LLC Method and system for facilitating switch virtualization in a network of interconnected switches
US10044568B2 (en) 2014-05-13 2018-08-07 Brocade Communications Systems LLC Network extension groups of global VLANs in a fabric switch
US9800471B2 (en) 2014-05-13 2017-10-24 Brocade Communications Systems, Inc. Network extension groups of global VLANs in a fabric switch
US9544219B2 (en) 2014-07-31 2017-01-10 Brocade Communications Systems, Inc. Global VLAN services
US9807007B2 (en) 2014-08-11 2017-10-31 Brocade Communications Systems, Inc. Progressive MAC address learning
US10284469B2 (en) 2014-08-11 2019-05-07 Avago Technologies International Sales Pte. Limited Progressive MAC address learning
US9524173B2 (en) 2014-10-09 2016-12-20 Brocade Communications Systems, Inc. Fast reboot for a switch
US9699029B2 (en) 2014-10-10 2017-07-04 Brocade Communications Systems, Inc. Distributed configuration management in a switch group
US9628407B2 (en) 2014-12-31 2017-04-18 Brocade Communications Systems, Inc. Multiple software versions in a switch group
US9626255B2 (en) 2014-12-31 2017-04-18 Brocade Communications Systems, Inc. Online restoration of a switch snapshot
US10003552B2 (en) 2015-01-05 2018-06-19 Brocade Communications Systems, Llc. Distributed bidirectional forwarding detection protocol (D-BFD) for cluster of interconnected switches
US9942097B2 (en) 2015-01-05 2018-04-10 Brocade Communications Systems LLC Power management in a network of interconnected switches
US9807005B2 (en) 2015-03-17 2017-10-31 Brocade Communications Systems, Inc. Multi-fabric manager
US10038592B2 (en) 2015-03-17 2018-07-31 Brocade Communications Systems LLC Identifier assignment to a new switch in a switch group
US10171303B2 (en) 2015-09-16 2019-01-01 Avago Technologies International Sales Pte. Limited IP-based interconnection of switches with a logical chassis
US9912614B2 (en) 2015-12-07 2018-03-06 Brocade Communications Systems LLC Interconnection of switches based on hierarchical overlay tunneling
US10237090B2 (en) 2016-10-28 2019-03-19 Avago Technologies International Sales Pte. Limited Rule-based network identifier mapping

Similar Documents

Publication Publication Date Title
CA2555545C (en) Interface bundles in virtual network devices
CN104488238B (en) A system and method in a network environment, the cluster link aggregation control
US8194534B2 (en) Blade server system with at least one rack-switch having multiple switches interconnected and configured for management and operation as a single virtual switch
US7120683B2 (en) Single switch image for a stack of switches
US8503329B2 (en) Signaling of attachment circuit status and automatic discovery of inter-chassis communication peers
JP5131651B2 (en) Load distribution system, the load distribution method, and a program
CN101682442B (en) Dynamic load balancing for layer-2 link aggregation
US7355965B2 (en) Apparatus and method for rapid detection of unidirectional breaks in a network ring
US20090323518A1 (en) Ring rapid spanning tree protocol
JP4769869B2 (en) The methods and routers on the movement of the protocol process (migration)
US20060104298A1 (en) Congestion control in a network
JP4840236B2 (en) Network system and the node device
US20060168279A1 (en) Apparatus and method for providing multi protocol label switching (MPLS)-based virtual private network (VPN)
JP4796184B2 (en) Edge node redundant system
US20090245137A1 (en) Highly available virtual stacking architecture
US20100329110A1 (en) Method for reconvergence after failure in a dual-homing network environment
US9184983B2 (en) Cross-stratum optimization protocol
CA2566005C (en) Protected switching ring
US20090274155A1 (en) Technique for providing interconnection between communication networks
US7065059B1 (en) Technique for restoring adjacencies in OSPF in a non-stop forwarding intermediate node of a computer network
US8593987B2 (en) System and method for providing network route redundancy across layer 2 devices
EP1633089A1 (en) Router and network connecting method
CN102007729B (en) Connectivity fault management traffic indication extension
US7965621B2 (en) Method and arrangement for failure handling in a network
US7672227B2 (en) Loop prevention system and method in a stackable ethernet switch system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 06812493

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC OF 270809

122 Ep: pct application non-entry in european phase

Ref document number: 06812493

Country of ref document: EP

Kind code of ref document: A1