CN109379234B - Message forwarding processing method and system based on Hybrid switch - Google Patents

Message forwarding processing method and system based on Hybrid switch Download PDF

Info

Publication number
CN109379234B
CN109379234B CN201811462071.8A CN201811462071A CN109379234B CN 109379234 B CN109379234 B CN 109379234B CN 201811462071 A CN201811462071 A CN 201811462071A CN 109379234 B CN109379234 B CN 109379234B
Authority
CN
China
Prior art keywords
vlan
message
forwarding
layer
port
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201811462071.8A
Other languages
Chinese (zh)
Other versions
CN109379234A (en
Inventor
高小添
刘敬一
金利
王力
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Centec Communications Co Ltd
Original Assignee
Suzhou Centec Communications Co Ltd
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 Suzhou Centec Communications Co Ltd filed Critical Suzhou Centec Communications Co Ltd
Priority to CN201811462071.8A priority Critical patent/CN109379234B/en
Publication of CN109379234A publication Critical patent/CN109379234A/en
Application granted granted Critical
Publication of CN109379234B publication Critical patent/CN109379234B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/825—Involving tunnels, e.g. MPLS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/30—Peripheral units, e.g. input or output ports

Abstract

The invention provides a message forwarding processing method and a system based on a Hybrid switch, wherein the method comprises the following steps: s101: after the message reaches the Hybrid switch, judging whether the interface enables the Hybrid mode, if so, jumping to the step S102; if not, the traditional two-layer and three-layer forwarding is carried out. S102: and judging whether the message hits the interface configuration Protected-vlan, if so, performing traditional two-layer and three-layer forwarding, and if not, skipping to the step S103. S103: and judging whether the message hits an Openflow layer flow table, if so, entering a step S104, and if not, performing traditional two-layer and three-layer forwarding. S104: and judging whether the flow table behavior is a Normal logic behavior, if so, performing traditional two-layer and three-layer forwarding, and if not, performing forwarding according to the behavior corresponding to the Openflow flow table.

Description

Message forwarding processing method and system based on Hybrid switch
Technical Field
The invention relates to a communication technology, in particular to a message forwarding processing method and system based on a Hybrid switch.
Background
Openflow solves the problems encountered by the current network facing new services by creating a new network interconnection concept, and the core idea of the Openflow is to convert the packet forwarding process originally controlled by a switch/router into independent processes respectively completed by an Openflow and a control server (controller). An SDN (software defined network) network scenario based on flow table forwarding is purely Openflow, and is often used in a data center, core packet transmission, and other network scenarios particularly requiring centralized control. In this scenario, for a newly arriving data flow, the switch typically: if the forwarding flow table for the data flow is not in the current switch, the data packet is sent to the controller, and the controller determines the next operation of the data packet. If existing, the existing data is sent to the destination point directly according to the original sending path. Wherein the controller is connected to the switch via a management link.
The switch using the pure Openflow protocol is used, the realized forwarding process is that the received message is analyzed and then goes to the flow table to be matched, if the received message is matched with the flow table, the corresponding represented action is executed or recorded, then the next table entry is continued until all the table entries are finally gone or no subsequent table entry needs to be matched, and all the actions are decided and then executed. The Openflow process flow of the prior art is shown in fig. 1.
The disadvantages of the prior art are as follows:
(1) the management link and the service link are separately wired, so that the operation cost is high;
(2) the management channel has no redundancy protection, and once a link failure occurs, the equipment has the risk of pipe disconnection;
(3) and lack of effective detection mechanisms, such as link, packet loss rate, and delay detection. The detection strategy is issued only by depending on the controller, so that the accuracy and the timeliness are poor, and the CPU resource of the equipment is occupied;
(4) the command line issuing and the northbound interface of the switch are not uniform, usually, a service channel is issued by a controller or manually by virtue of an Openflow protocol, DB information related to OVSDB is issued by virtue of OVSDB or manually, and a related command of the switch is issued by virtue of the command line.
Disclosure of Invention
In order to solve the problems, the invention provides a message forwarding processing method and system based on a Hybrid switch.
The specific scheme provided by the invention is as follows:
a message forwarding processing method based on a Hybrid switch comprises the following steps:
s101: after the message reaches the Hybrid switch, judging whether the interface enables the Hybrid mode, if so, jumping to the step S102; if not, performing the traditional two-layer and three-layer forwarding;
s102: judging whether the message hits the interface configuration Protected-vlan, if so, performing traditional two-layer and three-layer forwarding, and if not, skipping to the step S103;
s103: judging whether the message hits an Openflow layer flow table or not, if so, entering a step S104, and if not, performing traditional two-layer and three-layer forwarding;
s104: and judging whether the flow table behavior is a Normal logic behavior, if so, performing traditional two-layer and three-layer forwarding, and if not, performing forwarding according to the behavior corresponding to the Openflow flow table.
Further, the step 102 specifically includes:
judging whether the interface is configured with Protected-vlan,
if so, judging whether the message carries Vlan or not;
if the carrier is carried, judging whether the Vlan carried by the message hits the interface configuration Protected-Vlan;
if yes, the traditional two-layer and three-layer forwarding is carried out.
Further, the method further includes a Hybrid ingress port module forwarding process, which specifically includes:
s201: judging whether the ingress port starts the action of the traditional port on filtering the Vlan, if not, jumping to the step S203; if yes, jumping to step S202;
s202: filtering the Vlan carried by the message according to the port configuration, and directly discarding the message if the Vlan carried by the message is judged to be discarded; if the judgment is passed, jumping to step S203;
s203: and judging whether the port enables an Add Native Vlan switch, if so, marking the Untag message with the Native Vlan of the port, otherwise, not marking the Untag message with the Native Vlan of the port, and entering the next step of processing after the step is executed.
Further, the method further includes a Hybrid egress port module forwarding process, which specifically includes:
after the message reaches the exit module, if the message is forwarded to the exit in the traditional way, the step S303 is skipped to; if the flow table is forwarded to the outlet for the Openflow, jumping to step S301;
s301: judging whether the output port starts the Vlan filtering function or not, and if not, jumping to the step S304; if yes, jumping to step S303;
s303: filtering the Vlan carried by the message according to the traditional port, and directly discarding the message if the Vlan carried by the message is judged to be discarded; if the judgment is passed, jumping to step S305;
s305: judging whether the Openflow flow table processing reaches an exit module, if so, jumping to the step S304; otherwise, jumping to step S306;
s304: judging whether tunnel encapsulation operation exists in the flow table or not, and if not, avoiding the message from being influenced by the traditional port form; if yes, jumping to step S306;
s306: if the Native Vlan at the output port is the same as the Vlan carried by the message, the message Vlan is stripped; if the Native Vlan at the output port is different from the Vlan carried by the message, the Vlan carried by the message is forwarded.
A message forwarding system based on a Hybrid switch comprises:
the first judging unit is used for judging whether the interface enables the Hybrid mode or not after the message reaches the Hybrid switch, and if so, the second judging unit is entered; if not, performing the traditional two-layer and three-layer forwarding;
the second judging unit is used for judging whether the message hits the interface configuration Protected-vlan, if so, the traditional two-layer and three-layer forwarding is carried out, and if not, the message enters the third judging unit;
a third judging unit, configured to judge whether the packet hits the Openflow layer flow table, if yes, a fourth judging unit, and if not, perform conventional two-layer and three-layer forwarding;
and the fourth judging unit is used for judging whether the flow table behavior is a Normal logic interface, if so, performing traditional two-layer and three-layer forwarding, and if not, performing forwarding according to the behavior corresponding to the Openflow flow table.
Further, the second determining unit is specifically configured to:
judging whether the interface is configured with Protected-vlan,
if so, judging whether the message carries Vlan or not;
if the carrier is carried, judging whether the Vlan carried by the message hits the interface configuration Protected-Vlan;
if yes, the traditional two-layer and three-layer forwarding is carried out.
Further, the system further comprises:
a fifth judging unit: the judgment unit is used for judging whether the input port starts the action of the traditional port on the Vlan filtering, and if not, the input port enters the sixth judgment unit; if yes, entering a Vlan filtering unit;
the Vlan filtering unit is used for filtering the Vlan carried by the message according to the port configuration, and directly discarding the message if the Vlan is judged to be discarded; if the judgment is passed, entering a sixth judgment unit;
and the sixth judging unit is used for judging whether the port enables the Add Native V1an switch, if so, marking the Untag message with the Native Vlan of the port, and if not, marking the Untag message with the Native Vlan of the port, and after the step is executed, entering the next step of processing.
Further, the system further comprises:
a forwarding mode determining unit, configured to determine a message forwarding mode, and if the message is forwarded to an exit in a conventional manner, enter the Vlan filtering unit; if the Openflow flow table is forwarded to the outlet, entering a seventh judging unit;
a seventh judging unit, configured to judge whether the output port has the Vlan filtering function turned on, and if not, enter the eighth judging unit; if yes, entering a Vlan filtering unit;
the V1an filtering unit is used for filtering the Vlan carried by the message according to the traditional port, and directly discarding the message if the Vlan carried by the message is judged to be discarded; if the judgment is passed, jumping to a ninth judgment unit;
a ninth judging unit: judging whether the Openflow flow table processing reaches an exit module, if so, skipping to an eighth judging unit; otherwise, jumping to a forwarding unit;
an eighth judging unit, configured to judge whether a tunnel encapsulation operation exists in the flow table, and if not, the packet is not affected by a traditional port form; if yes, jumping to a forwarding unit;
the forwarding unit is used for stripping the Native Vlan of the output port if the Native Vlan is the same as the Vlan carried by the message; if the Native Vlan at the output port is different from the Vlan carried by the message, the Vlan carried by the message is forwarded.
The method solves the inherent deficiency of pure Openflow in the aspect of service detection by introducing the traditional OAM related technology; and moreover, OVSDB related configuration information and a traditional command line are unified, an RPC-API northbound interface is supported, the northbound interface of the switch is uniformly scheduled, and the out-of-control caused by the weakness of a management network is avoided. On the basis of the forwarding function of the openflow switch, the invention integrates various forwarding mechanisms of the traditional switch, makes up for the defects of two old switch forwarding frames, and constructs a forwarding frame which is more flexible and can be compatible with the old forwarding mode.
Drawings
Fig. 1 is a schematic diagram of a switch processing flow of a conventional pure Openflow protocol.
Fig. 2 is a schematic flow diagram of a Hybrid overall forwarding architecture according to an embodiment of the present invention.
Fig. 3 is a schematic diagram of a forwarding flow of a Hybrid ingress port module according to an embodiment of the present invention.
Fig. 4 is a schematic diagram of a forwarding flow of a Hybrid egress port module according to an embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments.
The Hybrid switch provided by the invention makes a brand-new definition on a forwarding concept and a command line, particularly the concept of a Hybrid interface, and deeply fuses a traditional network technology and an SDN network technology. The in-band management is supported, and the interface configuration and forwarding logic are very flexible; the OVSDB related configuration information and the traditional command line are unified, an RPC-API northbound interface is supported, and the northbound interface of the switch is uniformly scheduled.
The following is a brief description of the Hybrid switch forwarding framework, which explains the Hybrid switch forwarding logic, and is divided into three major parts: the system comprises a Hybrid integral forwarding framework, a Hybrid input port module forwarding framework and a Hybrid output port module forwarding framework.
Fig. 2 is a schematic flow diagram of a Hybrid overall forwarding architecture, and the Hybrid overall forwarding flow includes the following steps:
s101: judging whether the interface enables the Hybrid mode: after the message enters the device, if the interface enables the Hybrid mode, jumping to step S102; if the interface does not enable the Hybrid mode, the Traditional two-three layer forwarding (Bridge/Route routing mode, that is, query the table entry such as FDB/ARP/Route to perform forwarding) is performed.
S102: judging whether the message hits the Protected-vlan: if the interface is configured with Protected-Vlan, whether the message carries Vlan or not and whether the Vlan carried by the message hits the interface configuration Protected-Vlan or not are judged. If hit, the conventional two-three layer forwarding is performed, and if miss, the process jumps to step S103.
S103: judging whether the message hits a Flow Table (Openflow layer Flow Table) or not: if the message can match the existing flow table in the device, the step S104 is entered, and if no flow table is matched, the traditional two-layer and three-layer forwarding is performed.
S104: judging whether the flow table behavior is a Normal logic interface: if the flow table behavior is a Normal logic interface, the traditional two-layer and three-layer forwarding is carried out, and if the flow table behavior is not sent to the Normal logic behavior, the forwarding is carried out according to the flow table behavior.
Fig. 3 is a schematic diagram of a forwarding flow of the Hybrid ingress port module, where the forwarding flow of the Hybrid ingress port module includes the following steps:
s201: judging whether the input port opens a Vlan-Filter (the traditional port performs the filtration on the Vlan): after the message enters the device, if the Vlan-filter is in a disable state, jumping to step S203; and if the enable is available, skipping to the step S202 according to the processing behavior of the traditional port to the Vlan message.
S202: filtering the message according to a Traditional port (Traditional Mode Vlan-Filter): filtering the Vlan carried by the message according to the port configuration, and directly discarding the message if the Vlan carried by the message is judged to be discarded; if the determination is passed, it jumps to step S203.
S203: judging whether the port enables an Add Native Vlan switch: if the port enables the function, the Untag message marks the Native Vlan of the port, if the port does not enable the function, the Untag message does not mark the Native Vlan of the port, and the next step of processing is performed after the step is executed.
The AddMetaVlan switch mainly solves the problem that whether an original message is influenced by the editing behavior of a traditional port Vlan or not when an Openflow flow table is forwarded, namely whether a port Native Vlan is added or not after an Untag message enters equipment or not can be selected. For example: eth-0-1 is a message inlet, Eth-0-2 is an outlet, and Native vlans of the two ports are inconsistent. If the incoming message is Untag, the Native Vlan100 of Eth-0-1 is carried when the message is forwarded from Eth-0-2, which affects the forwarding behavior of the Openflow flow table, so that the switch is added to control the situation. The ingress add native Vlan only affects Vlan editing, and does not affect a forwarding processing mechanism. For example: the interface configures hybrid mode and turns off the switch. The Native Vlan at the input port is 100, the Native Vlan at the output port is 200, and both the interfaces allow forwarding of the messages of the Native vlans 100 and 200. At this time, the unog message entered by the ingress port can be normally forwarded to the egress port, and only the ingress Native Vlan100 is not carried during forwarding.
Fig. 4 is a schematic diagram of a forwarding flow of a Hybrid egress port module, where the forwarding flow of the Hybrid egress port module includes the following steps:
determination of Device processing method (Device Process): the message reaches the exit module, if the message is forwarded to the exit in the traditional mode, the step S303 is skipped to; if the flow table is forwarded to the egress for Openflow, the process jumps to step S301.
S301: judging whether the output port opens the Vlan Filter: forwarding the Openflow flow table to an outlet, and if the outlet Vlan-Filter is in a disable state, jumping to the step S304; and if the interface Vlan-Filter is determined to be in the enable state, jumping to step S303.
S303: filtering the message according to a Traditional port (Traditional mode Vlan-Filter): filtering the Vlan carried by the message according to the port configuration, and directly discarding the message if the Vlan carried by the message is judged to be discarded; if the determination is passed, step S305 is skipped.
S305: determining whether Openflow Flow Table processing (Flow Table) arrives at the egress module: if it is determined that the flow table processing has arrived, jumping to step S304; if it is determined as the conventional processing, the process proceeds to step S306.
S304: judging whether a Tunnel Encapsulation operation (Tunnel Encapsulation) exists in the flow table: if the tunnel encapsulation operation is judged to be absent, the message is not influenced by the traditional port form; if it is determined that the tunnel encapsulation operation is performed, the process proceeds to step S306.
S306: the egress port is affected by the legacy port morphology: if the Native Vlan at the output port is the same as the Vlan carried by the message, the message Vlan is stripped; if the Native Vlan at the output port is different from the Vlan carried by the message, the Native Vlan can carry the message Vlan to forward.
Wherein, Tunnel Encapsulation means: and forwarding the tunnel encapsulation operation to an output port through an Openflow flow table, and judging whether the tunnel encapsulation operation exists. Simple stream forwarding: not related to tunnel packaging actions such as Mpls/Gre/Vxlan and the like. Such as modifying message source object Mac/Ip, editing message Vlan, etc. (see openflow protocol specifically). Non-simple stream forwarding: the flow table relates to tunnel encapsulation operations such as Mpls/Gre/Vxlan. The VLAN-carrying message forwarded by the simple stream is not influenced by the attribute of the output port; the Vlan-carrying message forwarded by the non-simple stream is affected by the attributes of the egress port. For example: through simple stream processing, the message with the Vlan100 is forwarded out from the Eth-0-1 port, and the message is not influenced by the attribute of the Access port and forwarded by the Vlan 100; through the non-simple stream processing, the message with Vlan100 will be affected by the Access port attribute, and the Vlan100 will be stripped and forwarded.
The method solves the inherent deficiency of pure Openflow in the aspect of service detection by introducing the traditional OAM related technology; and moreover, OVSDB related configuration information and a traditional command line are unified, an RPC-API northbound interface is supported, the northbound interface of the switch is uniformly scheduled, and the out-of-control caused by the weakness of a management network is avoided.
On the basis of the forwarding function of the openflow switch, the invention integrates various forwarding mechanisms of the traditional switch, makes up for the defects of two old switch forwarding frames, and constructs a forwarding frame which is more flexible and can be compatible with the old forwarding mode.
The foregoing describes only a few embodiments of the present invention, which are more specific and detailed, and therefore should not be construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (4)

1. A message forwarding processing method based on a Hybrid switch is characterized by comprising the following steps:
s101: after the message reaches the Hybrid switch, judging whether the interface enables the Hybrid mode, if so, jumping to the step S102; if not, performing the traditional two-layer and three-layer forwarding;
s102: judging whether the message hits the interface configuration Protected-vlan, if so, performing traditional two-layer and three-layer forwarding, and if not, skipping to the step S103;
s103: judging whether the message hits an Openflow layer flow table or not, if so, entering a step S104, and if not, performing traditional two-layer and three-layer forwarding;
s104: judging whether the flow table behavior is sent to Normal logic behavior, if so, performing traditional two-layer and three-layer forwarding, if not, performing forwarding according to the behavior corresponding to the Openflow flow table,
the method further comprises a Hybrid ingress port module forwarding process, which specifically comprises the following steps:
s201: judging whether the ingress port starts the action of the traditional port on filtering the Vlan, if not, jumping to the step S203; if yes, jumping to step S202;
s202: filtering the Vlan carried by the message according to the port configuration, and directly discarding the message if the Vlan carried by the message is judged to be discarded; if the judgment is passed, jumping to step S203;
s203: judging whether the port enables an Add Native Vlan switch or not, if so, marking the Untag message with the Native Vlan of the port, if not, marking the Untag message with the Native Vlan of the port, executing the step, then entering the next step of processing,
the method further comprises a Hybrid output port module forwarding flow, and specifically comprises the following steps:
after the message reaches the exit module, if the message is forwarded to the exit in the traditional way, the step S303 is skipped to; if the flow table is forwarded to the outlet for the Openflow, jumping to step S301;
s301: judging whether the output port starts the Vlan filtering function or not, and if not, jumping to the step S304; if yes, jumping to step S303;
s303: filtering the Vlan carried by the message according to the traditional port, and directly discarding the message if the Vlan carried by the message is judged to be discarded; if the judgment is passed, jumping to step S305;
s305: judging whether the Openflow flow table processing reaches an exit module, if so, jumping to the step S304; otherwise, jumping to step S306;
s304: judging whether tunnel encapsulation operation exists in the flow table or not, and if not, avoiding the message from being influenced by the traditional port form; if yes, jumping to step S306;
s306: if the Native Vlan at the output port is the same as the Vlan carried by the message, the message Vlan is stripped; if the Native Vlan at the output port is different from the Vlan carried by the message, the Vlan carried by the message is forwarded.
2. The method according to claim 1, wherein the step 102 specifically comprises:
judging whether the interface is configured with Protected-vlan,
if so, judging whether the message carries Vlan or not;
if the carrier is carried, judging whether the Vlan carried by the message hits the interface configuration Protected-Vlan;
if yes, the traditional two-layer and three-layer forwarding is carried out.
3. A message forwarding processing system based on a Hybrid switch is characterized by comprising:
the first judging unit is used for judging whether the interface enables the Hybrid mode or not after the message reaches the Hybrid switch, and if so, the second judging unit is entered; if not, performing the traditional two-layer and three-layer forwarding;
the second judging unit is used for judging whether the message hits the interface configuration Protected-vlan, if so, the traditional two-layer and three-layer forwarding is carried out, and if not, the message enters the third judging unit;
a third judging unit, configured to judge whether the packet hits the Openflow layer flow table, if yes, a fourth judging unit, and if not, perform conventional two-layer and three-layer forwarding;
a fourth judging unit, configured to judge whether the flow table behavior is a Normal logic behavior, if so, perform conventional two-layer or three-layer forwarding, otherwise, perform forwarding according to a behavior corresponding to the Openflow flow table,
the system further comprises:
a fifth judging unit: the judgment unit is used for judging whether the input port starts the action of the traditional port on the Vlan filtering, and if not, the input port enters the sixth judgment unit; if yes, entering a Vlan filtering unit;
the Vlan filtering unit is used for filtering the Vlan carried by the message according to the port configuration, and directly discarding the message if the Vlan is judged to be discarded; if the judgment is passed, entering a sixth judgment unit;
a sixth judging unit, configured to judge whether the port enables the Add Native Vlan switch, if so, mark the Untag message with the Native Vlan of the port, if not, mark the Untag message with no Native Vlan of the port, and enter the next step of processing after the step is executed,
the system further comprises:
a forwarding mode determining unit, configured to determine a message forwarding mode, and if the message is forwarded to an exit in a conventional manner, enter the Vlan filtering unit; if the Openflow flow table is forwarded to the outlet, entering a seventh judging unit;
a seventh judging unit, configured to judge whether the output port has the Vlan filtering function turned on, and if not, enter the eighth judging unit; if yes, entering a Vlan filtering unit;
the Vlan filtering unit is used for filtering the Vlan carried by the message according to the traditional port, and directly discarding the message if the Vlan carried by the message is judged to be discarded; if the judgment is passed, jumping to a ninth judgment unit;
a ninth judging unit: judging whether the Openflow flow table processing reaches an exit module, if so, skipping to an eighth judging unit; otherwise, jumping to a forwarding unit;
an eighth judging unit, configured to judge whether a tunnel encapsulation operation exists in the flow table, and if not, the packet is not affected by a traditional port form; if yes, jumping to a forwarding unit;
the forwarding unit is used for stripping the Native Vlan of the output port if the Native Vlan is the same as the Vlan carried by the message; if the Native Vlan at the output port is different from the Vlan carried by the message, the Vlan carried by the message is forwarded.
4. The system of claim 3, wherein the second determination unit is specifically configured to:
judging whether the interface is configured with Protected-vlan,
if so, judging whether the message carries Vlan or not;
if the carrier is carried, judging whether the Vlan carried by the message hits the interface configuration Protected-Vlan;
if yes, the traditional two-layer and three-layer forwarding is carried out.
CN201811462071.8A 2018-11-30 2018-11-30 Message forwarding processing method and system based on Hybrid switch Active CN109379234B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811462071.8A CN109379234B (en) 2018-11-30 2018-11-30 Message forwarding processing method and system based on Hybrid switch

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811462071.8A CN109379234B (en) 2018-11-30 2018-11-30 Message forwarding processing method and system based on Hybrid switch

Publications (2)

Publication Number Publication Date
CN109379234A CN109379234A (en) 2019-02-22
CN109379234B true CN109379234B (en) 2021-10-01

Family

ID=65376699

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811462071.8A Active CN109379234B (en) 2018-11-30 2018-11-30 Message forwarding processing method and system based on Hybrid switch

Country Status (1)

Country Link
CN (1) CN109379234B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110971526B (en) * 2020-01-06 2021-10-29 苏州盛科通信股份有限公司 Flow table expansion method and device for FDB (fully drawn bus) resources of hybrid switch

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105450532A (en) * 2014-09-28 2016-03-30 杭州华三通信技术有限公司 Three-layer forwarding method and three-layer forwarding device in software defined network
CN105790988A (en) * 2014-12-23 2016-07-20 中兴通讯股份有限公司 Implementation method and device of operation, administration and management function
CN105814943A (en) * 2013-10-17 2016-07-27 瑞典爱立信有限公司 VPNv4 ROUTE CONTROL FOR LTE X2 SON USING UNIQUE ROUTE TARGETS

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105814943A (en) * 2013-10-17 2016-07-27 瑞典爱立信有限公司 VPNv4 ROUTE CONTROL FOR LTE X2 SON USING UNIQUE ROUTE TARGETS
CN105450532A (en) * 2014-09-28 2016-03-30 杭州华三通信技术有限公司 Three-layer forwarding method and three-layer forwarding device in software defined network
CN105790988A (en) * 2014-12-23 2016-07-20 中兴通讯股份有限公司 Implementation method and device of operation, administration and management function

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"OpenFlow Switch Specification Version 1.5.1(Protocol version 0x06)";OPEN NETWORKING FOUNDATION;《OpenFlow Switch Specification》;20150326;第19-20页 *

Also Published As

Publication number Publication date
CN109379234A (en) 2019-02-22

Similar Documents

Publication Publication Date Title
EP2544409B1 (en) Generic monitoring packet handling mechanism for OpenFlow 1.1
US9178811B2 (en) Method, apparatus and system for generating label forwarding table on ring topology
US8588236B2 (en) Virtual network management server and network system
EP2490375B1 (en) Method and device for link protection in virtual private local area network
US8527674B2 (en) Data packet switching
US7653057B1 (en) Preventing forwarding of a packet to a control plane
US20030037162A1 (en) Spanning tree protocol traffic in a transparent LAN
EP2135393B1 (en) Ethernet spanning tree provision
CN101877677B (en) Tunnel switching method and system for multi-protocol label switching services
US20160301571A1 (en) Method and Device for Monitoring OAM Performance
US9973349B2 (en) Relay system and switching device
CN107566237B (en) Data message processing method and device
US20120236866A1 (en) Communication system and communication device
US20120219003A1 (en) Node, a monitoring management method used for it, and a transfer system, an input circuit and an output circuit using it
US20070217438A1 (en) Ring node device and method of connecting terminal to ring node device
EP3534571B1 (en) Service packet transmission method, and node apparatus
EP2728797B1 (en) Message processing method, device and system
CN105337884A (en) Method and device for achieving multistage message editing service control on the basis of logic port
EP2897328B1 (en) Method, system and apparatus for establishing communication link
EP1944918A1 (en) A method and system for realizing the consistency of the virtual circuit status
CN109379234B (en) Message forwarding processing method and system based on Hybrid switch
CN102843282B (en) A kind of message processing method and system
CN107995119B (en) Method and system for realizing STP (spanning Tree protocol) of three or more layers of network equipment based on port model
WO2016101582A1 (en) Method for configuring and implementing operations, administration and maintenance function, and forwarding device
EP2619952B1 (en) Pseudo-wire providing an in-band control channel using an offset

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information

Address after: 215000 unit 13 / 16, 4th floor, building B, No.5 Xinghan street, Suzhou Industrial Park, Jiangsu Province

Applicant after: Suzhou Shengke Communication Co.,Ltd.

Address before: 215000 unit 13 / 16, 4th floor, building B, No.5 Xinghan street, Suzhou Industrial Park, Jiangsu Province

Applicant before: CENTEC NETWORKS (SU ZHOU) Co.,Ltd.

CB02 Change of applicant information
GR01 Patent grant
GR01 Patent grant