WO2021042674A1 - 一种端口状态的配置方法及网络设备 - Google Patents

一种端口状态的配置方法及网络设备 Download PDF

Info

Publication number
WO2021042674A1
WO2021042674A1 PCT/CN2020/074970 CN2020074970W WO2021042674A1 WO 2021042674 A1 WO2021042674 A1 WO 2021042674A1 CN 2020074970 W CN2020074970 W CN 2020074970W WO 2021042674 A1 WO2021042674 A1 WO 2021042674A1
Authority
WO
WIPO (PCT)
Prior art keywords
port
layer
tunnel
local area
data message
Prior art date
Application number
PCT/CN2020/074970
Other languages
English (en)
French (fr)
Inventor
陈凯林
Original Assignee
厦门网宿有限公司
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 厦门网宿有限公司 filed Critical 厦门网宿有限公司
Priority to EP20861929.6A priority Critical patent/EP4009592A1/en
Publication of WO2021042674A1 publication Critical patent/WO2021042674A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/12—Shortest path evaluation
    • H04L45/123—Evaluation of link metrics
    • 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/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • 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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/55—Prevention, detection or correction of errors
    • H04L49/552—Prevention, detection or correction of errors by ensuring the integrity of packets received through redundant connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/65—Re-configuration of fast packet switches

Definitions

  • This application relates to the field of Internet technology, and in particular to a method for configuring port status and network equipment.
  • STP Shorting Tree Protocol
  • RSTP Rapid Spanning Tree Protocol
  • the port of the network device can be in a variety of different states. Taking RSTP as an example, the state of a network port can be divided into a forwarding state (Forwarding) or a blocking state (Blocking or Discarding), and the state of these ports can usually have a corresponding relationship with the type of the port.
  • Root Port and Designated Port (DP) are usually in the forwarding state, and other ports (Alternate Port, AP) except the root port and designated ports can be in the blocking state, which can ensure When data packets are transmitted in network equipment, avoid transmission loops.
  • RP Root Port
  • DP Designated Port
  • Fig. 1 may include multiple switches on both sides of the communication, and switches on different sides can be connected through a Layer 2 tunnel.
  • switch 1 is the root bridge
  • each port on switch 1 is DP
  • the port connected to switch 1 is RP
  • the two ports connected to the layer 2 tunnel on switch 2 are DP.
  • switch 3 and switch 4 are connected to the Layer 2 tunnel, only the port connected to the right of Layer 2 tunnel 1 is RP, and the other three ports are APs, and are connected to switch 4 on switch 3
  • the port is DP, and on switch 4, the port connected to switch 3 is RP.
  • the DP can be in the forwarding state. In this way, of the four second-tier tunnels, only the second-tier tunnel 1 is actually unblocked.
  • switch 1 and switch 2 When switch 1 and switch 2 receive the same data message, they will send out the data message from each port, but only the data message transmitted by layer 2 tunnel 1 will be received by switch 3. 4 The transmitted data message will be discarded, so that the repeated reception of the same data message can be avoided.
  • it is sent through four links at the same time, which will cause four times the data traffic. Therefore, according to the current port state configuration method, traffic will be wasted.
  • the purpose of some embodiments of the present application is to provide a port state configuration method and network equipment, which can avoid traffic waste in the data transmission process.
  • one aspect of the present application provides a port status configuration method.
  • the method includes identifying the port type of the current port connected to the Layer 2 tunnel, and if the current port is a designated port, setting the designated port The initial state of is set to the blocking state, and if the designated port is connected to the root port through a layer 2 tunnel, the blocking state of the designated port is adjusted to the forwarding state; if the current port is the root port, the root port The initial state of is set to the forwarding state, and a notification message used to characterize the identity of the root port is sent to the opposite port through the root port; if the current port is other than the designated port and the root port For other ports, set the initial state of the other ports to the blocked state.
  • another aspect of the present application also provides a network device, the network device includes a port connected to a layer 2 tunnel, wherein, if the port is a designated port, the initial state of the designated port is set Is a blocking state, and if the designated port is connected to the root port through a Layer 2 tunnel, the blocking state of the designated port is adjusted to the forwarding state; if the port is a root port, the initial state of the root port is set to Forwarding status, and send a notification message for characterizing the identity of the root port to the opposite port through the root port; if the port is a port other than the designated port and the root port, the The initial state of the other ports is set to the blocked state.
  • the technical solution provided by this application can identify the type of the port for the port connected to the layer 2 tunnel on the network device. If the port is a designated port, the initial state of the designated port can be set to a blocked state instead of the forwarding state in the prior art. Later, if it is determined that the designated port is connected to the root port through a Layer 2 tunnel, the blocking state of the designated port is adjusted to the forwarding state. If the port is a root port, then the initial state of the root port can be set to the forwarding state. In addition, the root port can also send a notification message for characterizing the identity of the root port to the opposite port. In the prior art, the root port does not send the notification message to the opposite port.
  • the designated port can learn that the opposite port is the root port, thereby adjusting Specifies the port status of the port. If the port is other than the designated port and the root port, the initial state of the port can be set to the blocked state.
  • Figure 1 after the above port status configuration method, the designated port on the left side of Layer 2 tunnel 1 is connected to the root port, so the designated port is adjusted to the forwarding state, and the root on the right side of Layer 2 tunnel 1 The port itself is in the forwarding state, so the Layer 2 tunnel 1 can transmit data packets normally.
  • the ports on the left side of the Layer 2 tunnel 2-4 are all designated ports, the ports on the right are all other ports, so that the designated ports on the left side of the Layer 2 tunnel 2-4 remain blocked. In this way, data packets will only be transmitted through the Layer 2 tunnel 1 and will not be transmitted on other Layer 2 tunnels, thereby solving the problem of traffic waste.
  • Figure 1 is an application example of a network structure
  • Figure 2 is a schematic diagram of connections between network devices in an embodiment of the present application.
  • FIG. 3 is a schematic diagram of steps of a method for configuring port status in an embodiment of the present application
  • FIG. 4 is a schematic diagram of the connection between the network device and the switch in an embodiment of the present application.
  • FIG. 5 is a schematic diagram of the first structure of a two-layer dedicated line network system in an embodiment of the present application.
  • Fig. 6 is a schematic diagram of the second structure of the Layer 2 dedicated line network system in an embodiment of the present application.
  • This application provides a port state configuration method, which can be applied to network devices that support STP or RSTP.
  • the method may include the following steps.
  • S1 Identify the port type of the current port connected to the Layer 2 tunnel. If the current port is a designated port, set the initial state of the designated port to the blocking state, and if the designated port passes through the Layer 2 tunnel and the root port Connected, adjusting the blocking state of the designated port to the forwarding state.
  • network devices can be connected through a Layer 2 tunnel, so as to establish a Layer 2 dedicated line network between different geographic locations.
  • multiple network devices can be distributed in different geographic locations, and any network device can establish a Layer 2 tunnel with other network devices on the opposite side.
  • One or more ports can be deployed on the network device, and these ports can be connected to different Layer 2 tunnels respectively.
  • the network devices can send BPDU (Bridge Protocol Data Unit) messages to each other to determine whether the network device is a root bridge or a non-root bridge.
  • BPDU Bridge Protocol Data Unit
  • the initial state of the port and the switching of the state can be improved.
  • the port type of the current port connected to the layer 2 tunnel can be identified from the network device. It should be noted that not all ports in the network device are connected to the Layer 2 tunnel. Some ports may also be connected to other network devices such as switches. This embodiment can be improved only for the ports connected to the Layer 2 tunnel.
  • the port type of each port on the network device can be determined by STP or RSTP. By obtaining the determination result of STP or RSTP, the port type of the current port connected to the Layer 2 tunnel can be identified.
  • the current port may be any port connected to the layer 2 tunnel on the network device.
  • the initial state of the designated port in the prior art is often the forwarding state.
  • the initial state of the designated port can be set to the blocked state.
  • the state of the designated port often does not change during normal data transmission.
  • the blocking state of the designated port can be adjusted to the forwarding state.
  • network device 1 can be used as a root bridge, and network devices 2 to 4 can all be used as non-root bridges.
  • STP or RSTP can determine the port type of each port on the network device when implementing network convergence.
  • the ports on the network device 1 can be designated ports, and the port on the network device 3 is connected to the layer 2 tunnel 1.
  • the port can be used as the root port, and the network device 3 is connected to the layer 2 tunnel Port 4 can be used as other ports.
  • the two ports connecting the layer 2 tunnel 2 and the layer 2 tunnel 4 on the network device 2 may be designated ports, and the two ports connecting the layer 2 tunnel 2 and the layer 2 tunnel 3 on the network device 4 may be other ports.
  • the initial states of these four ports are set to the blocked state. Since the port on the right side of the Layer 2 tunnel 1 is the root port, the port on the left side of the Layer 2 tunnel 1 is connected to the root port, so the state of the port is adjusted to the forwarding state. Finally, of the four ports on the left side of the layer 2 tunnel, only the port on the network device 1 connected to the layer 2 tunnel 1 is in the forwarding state, and the other three ports are all in the blocking state.
  • the initial state of the root port can be set to the forwarding state.
  • the root port in the prior art usually does not send BPDU packets.
  • the state of the designated port since the state of the designated port needs to be adjusted according to whether the opposite side is the root port, the state of the root port is set to forwarding. In the state, it is also necessary to send a notification message for characterizing the identity of the root port to the opposite port through the root port.
  • the notification message may be the above-mentioned BPDU message, and the BPDU message has a Port Role field, which is filled with an identifier that characterizes the identity of the root port.
  • the designated port on the opposite side can determine that the port on the opposite side is the root port by identifying the content in the port role field of the notification message.
  • the designated port after the designated port receives the notification message used to characterize the identity of the root port from the opposite port through the connected layer 2 tunnel, it can determine that the designated port is connected to the root port through the layer 2 tunnel, so that the designated port can be connected to the root port
  • the state of the port is adjusted from the blocking state to the forwarding state.
  • the root port may send the aforementioned notification message to the opposite port according to a specified time period.
  • the specified time period may be preset, for example, the specified time period may be 2 seconds.
  • a communication failure may occur in the layer 2 tunnel currently in use. In this case, it is necessary to select a spare layer 2 tunnel from the remaining layer 2 tunnels, and continue data transmission through the selected layer 2 tunnel. For example, when a communication failure occurs in the Layer 2 tunnel 1, the Layer 2 tunnel 2 can be selected to continue communication. In this case, the port connected to the Layer 2 tunnel 1 in the network device 1 cannot normally receive the notification message from the opposite root port.
  • the forwarding state of the designated port can be restored to the blocking state.
  • the designated duration may be preset, for example, the designated duration may be 4 seconds.
  • the initial state of the other ports can be set to the blocked state.
  • the foregoing manner of configuring the port status can be used as a custom function
  • the custom function can be pre-configured in the network device, and the custom function can be actively turned on or off.
  • the port state configuration can be performed in a manner in the prior art, and when the custom function is turned on, the port state configuration can be performed in the manner described above in this application.
  • the custom function can also be enabled only for some ports in the network device. For example, in the system architecture shown in Figure 4, network devices on the opposite side can be connected through a Layer 2 tunnel, and network devices on the same side can be connected to a switch.
  • the above-mentioned custom function can be turned on only for the ports connected to the Layer 2 tunnel, and the custom function can be turned off for the ports not connected to the Layer 2 tunnel.
  • the initial state of the port can be set to the forwarding state instead of the blocking state.
  • the port not connected to the Layer 2 tunnel is the root port, there is no need to periodically send notification messages to the opposite port. The reason for this treatment is that if the above-mentioned custom function is also enabled on the port connected to the switch, the system will be paralyzed.
  • network device 1 For example, suppose that network device 1 is the root bridge at this time, then the ports on network device 1 are all designated ports, and the port connecting network device 2 and the switch is the root port. If the ports connecting network device 1, network device 2 and switch 1 are all enabled with the above-mentioned custom function, then both the designated port and the root port can be in the forwarding state at this time. However, if network device 2 suddenly fails, the port connected to the switch on network device 1 cannot receive the notification message from the opposite port. In this case, network device 1 will also be connected to the switch The port is re-adjusted to the blocking state, which will cause when the network device 2 fails, the data forwarding function of the port will also be closed along with the network device 1.
  • the above-mentioned port state configuration method can be applied to the POP server in the two-layer dedicated line network system as shown in FIG. 5.
  • the system may include a system switch and a POP server.
  • a two-layer dedicated line network can be used to transmit data messages between different customer service servers. These customer service servers can be distributed in different cities, or in the same city at a geographically distant location.
  • multiple Layer 2 tunnels can be established between POP servers on different sides, and the system switch can be connected to each POP server on the same side.
  • each POP server can run OVS (OpenVirtualSwitch, open virtual switch) or other software with similar functions, through which the POP server can be configured to realize a Layer 2 dedicated line network.
  • OVS OpenVirtualSwitch, open virtual switch
  • a communication protocol for implementing a two-layer private line network can be opened on each POP server, and the communication protocol can be, for example, stp or rstp.
  • the priority can be set for the POP server, and the link cost value can be assigned to each port of the POP server.
  • the above-mentioned priority and link cost values can be numerical values, where the smaller the numerical value, the higher the priority can be, and the larger the numerical value, the larger the link cost value can be.
  • the assigned priority and link cost value can be used to determine the port type of each port on the POP server. Specifically, for ports connected to different Layer 2 tunnels, different link cost values can be assigned, and ports on both sides of the same Layer 2 tunnel can be assigned the same link cost value. For example, in Figure 5, there are a total of four Layer 2 tunnels established, then these four Layer 2 tunnels can correspond to four different link cost values (for example, 100, 110, 120, and 130, respectively), and for Layer 2 tunnel 1, Both ports on both sides can be configured with a link cost value of 100.
  • the root bridge can be filtered out first according to the priority of each POP server. Specifically, the POP server with the highest priority can be used as the root bridge. If there are multiple POP servers with the highest priority, the POP server with the smallest bridge ID can be selected as the root bridge. Among them, the bridge ID can be the sum of the priority and the MAC address of the POP server. After the root bridge is selected, the port type of each port on the root bridge can be a designated port.
  • the port type of each port on other POP servers can be determined. Specifically, for the current POP server, the link cost value between each port and the root bridge can be determined, and the port with the lowest link cost value is used as the root port. If there are many ports with the lowest link cost value Then, the port with the lowest port ID can be used as the root port. Among them, the port ID can be the sum of the priority of the POP server and the port number.
  • the designated port on the POP server can be determined. Specifically, for a communication link, if one of the ports on both sides of the communication link is the root port, the other port can be used as the designated port. If there is no root port on both sides of the communication link, then one of the two ports can be selected as the designated port. In practical applications, the port with the smallest link cost between the two ports and the root bridge can be identified first, and the port with the smallest link cost can be used as the designated port. If the link cost values are the same, the designated port can be determined according to the priority of the POP server where the port is located. The port with the higher priority can be used as the designated port. If the priority is still the same, the designated port can be determined according to the bridge ID of the POP server where the port is located. The port with the smallest bridge ID can be used as the designated port.
  • the root port and designated port can be determined on each POP server through the above method.
  • the status of each port can be configured in the manner described in steps S1 to S5.
  • For a target Layer 2 tunnel if the ports on both sides of the target Layer 2 tunnel are in the forwarding state, then the target Layer 2 tunnel is in the forwarding state, and data packets can be normally transmitted through the target Layer 2 tunnel. And if any port of the target Layer 2 tunnel is in a blocked state, then the target Layer 2 tunnel is in a blocked state, and the Layer 2 tunnel in the blocked state cannot send data packets from one POP server to another POP server.
  • multiple layer 2 tunnels established between POP servers on different sides can ensure that only one layer 2 tunnel is in the forwarding state at the same time, thereby avoiding data packets from passing through different layer 2 tunnels.
  • the tunnel repeats the transmission.
  • the priority of each POP server can be exactly the same at this time. In this case, there is no need to configure the priority of each POP server, but the port type of each port is determined by the link cost value and the MAC address.
  • the port connecting the POP server and the system switch may also be assigned a link cost value.
  • the link cost value of the port connecting the POP server and the system switch can be set lower, and the POP server can be connected to the opposite POP server.
  • the link cost value of the port is set higher.
  • the link cost value of the port connecting the POP server 1 and the system switch in FIG. 5 may be 1, and the link cost value of the layer 2 tunnel 1 may be 100.
  • the communication protocol running on the POP server can be based on the assigned link cost value from the remaining Select a target Layer 2 tunnel from the available Layer 2 tunnels, and place the target Layer 2 tunnel in a forwarding state, so as to continue to transmit data packets through the target Layer 2 tunnel.
  • the Layer 2 tunnel with the smallest link cost value can be selected from the remaining available Layer 2 tunnels as the target Layer 2 tunnel. In this way, it can always be ensured that the Layer 2 tunnel currently in the forwarding state is the available Layer 2 tunnel.
  • the link cost value in the tunnel is the smallest. Through the switching method of this two-layer tunnel, the stability of data transmission can be improved.
  • system switches usually have their own MAC address learning function, which can automatically identify the MAC address in the data message, and establish an association relationship between the identified MAC address and the port that receives the data message, thereby constructing the MAC address Forwarding table (forwarding database, fdb table).
  • forwarding database fdb table
  • the system switch can avoid sending the same data message to multiple different POP servers.
  • the layer 2 tunnel may be switched, if the system switch only forwards the data message to a connected POP server according to the fdb table, then the POP server may not be able to receive the data through the layer 2 tunnel.
  • the data message is sent to the POP server on the opposite side.
  • the system automatically switches to the Layer 2 tunnel 2.
  • the system switch still sends data packets to the POP server 1 according to the fdb table, it will cause the data packet The document cannot be transmitted to the opposite side.
  • the MAC address learning function in the system switch can be turned off. In this way, when the system switch receives a data message, the destination MAC address in the data message is not learned. Therefore, the system switch can use the flood method to forward the data message to each POP server connected to the system switch. Then each POP server will try to forward the received data message through the Layer 2 tunnel.
  • the data message is transmitted from the first customer service server to the second customer service server through the first system switch, so the first system switch can receive the data from the first customer Data packets of the business server.
  • the first system switch can be connected to multiple customer service servers that belong to the same first geographic location. Therefore, in order to distinguish data packets sent by different customer service servers, the first system switch can be The data message adds an outer vlan identifier, which can be used to characterize the client to which the currently received data message belongs.
  • QinQ function also called Stacked VLAN or Double VLAN function
  • the first system switch in order for the first system switch to forward the data message sent by the first customer service server to the connected POP server 1 and POP server 2, it can set the target port connected to the POP server 1 and POP server 2. Configure the above-mentioned outer VLAN ID. In this way, from the perspective of the first system switch, the port connected to the first customer service and the target port connected to the POP server 1 and POP server 2 can be in the same vlan, so that the first customer service server sends The data message can finally be sent to POP server 1 and POP server 2 for processing.
  • the first system switch may also configure the above-mentioned target port as a port type used to reserve the outer VLAN identifier, for example, it may be a trunk type. In this way, the first system switch can send the data message carrying the outer VLAN identifier to the connected POP server 1 and POP server 2 through the target port.
  • the POP server after the POP server receives the data message carrying the outer VLAN ID, it can identify the outer VLAN ID in it to determine the client to which the current data message belongs to determine the transmission data In this way, the pop server can assign corresponding Layer 2 tunnels to different clients based on different outer VLAN IDs. This not only realizes data isolation between different clients, supports multi-client scenarios, but also realizes The reuse of pop servers saves hardware costs.
  • the POP server 1 and the POP server 3 can be connected through a Layer 2 tunnel 1.
  • the data packets transmitted on the Layer 2 tunnel usually need to be pure Ethernet packets.
  • the POP server 1 needs to strip off the outer VLAN identifier carried in the data message, so as to restore the Ethernet message sent by the first client service server Finally, the restored Ethernet packet can be sent to the POP server 3 through the pre-created Layer 2 tunnel.
  • the first interface corresponding to the outer VLAN ID may be created in the POP server in advance, for receiving the corresponding outer VLAN ID data packet, and for stripping the outer VLAN ID.
  • the first interface can be created in multiple ways.
  • a multi-layer nested VLAN interface can be created in the Linux system, and the created multi-layer nested VLAN interface can be used as the above-mentioned first interface.
  • eth0 can represent the physical network card used to receive the data message
  • a virtual network card eth0.200 can be created for the data message with the outer VLAN ID of 200, which is used to receive the data message
  • the first interface is dedicated to receiving data packets with an outer VLAN ID of 200.
  • the virtual network card can be set with the same id as the above outer VLAN ID, so a virtual network card named eth0.200 is obtained.
  • the outer vlan identification can be stripped, and the outer vlan identification is determined to be 200, and the stripped data message is sent to the name eth0. 200 virtual network card, so you can achieve the stripping of the outer VLAN ID.
  • the first pop server obtains the mapping relationship between the source mac address in the data message and the first interface through the self-learning capability of the fdb (forwarding database, forwarding data) table.
  • the POP server 1 when the POP server 1 creates a Layer 2 tunnel connected to the POP server 3, it can also have multiple implementation modes.
  • the POP server 1 can use the vxlan interface in the Linux system to create a vxlan tunnel, and the vxlan tunnel can be used as the created Layer 2 tunnel.
  • both POP server 1 and POP server 3 can create interfaces of type vxlan through ovs, and the layer 2 tunnel formed through these two interfaces can be used as a layer 2 tunnel.
  • the vxlan interface created in the above-mentioned linux system, or the interface of type vxlan in ovs, can be used as the second interface in the POP server 1 for connecting to the layer 2 tunnel.
  • the POP server 1 may create a target bridge (bridge), and use the aforementioned first interface and second interface as the two ports of the target bridge, thereby realizing the process of bridging the two interfaces.
  • the target network bridge can be created through a linux system or an ovs system or other methods, which is not limited in this application.
  • the first POP server can obtain the mapping relationship between the source mac address in the data message and the second interface through the self-learning capability of the fdb table.
  • one or more customer switches can be added between the first system switch and the customer service server. For example, at least one customer switch can be added for each customer. These customer switches can be connected to the customer service server and the first system switch respectively. Connected, where the customer switch and the first switch are logically connected directly to the port, for example, directly connected through a network cable, or established through a dedicated line connection.
  • the first client switch can receive data packets sent by each client service server.
  • different client service servers may be divided into different network segments.
  • the first customer switch can add an inner VLAN ID to the received data packet and send it to the first system switch.
  • the inner VLAN ID can be used to characterize the customer service that sends the data packet.
  • the first customer switch After the data message passes through the first customer switch, it carries the inner VLAN ID. After being received by the first system switch, the outer VLAN ID can be added in the same manner as described above. It should be noted that, in this case, the first system switch can assign different outer VLAN IDs to each connected customer switch, and add the same as the current customer switch to the data message sent by the current customer switch. Matching outer VLAN ID. In this way, through the combination of the inner VLAN ID and the outer VLAN ID, the line channel used to transmit the data message can be uniquely determined, including the interface on the POP server and the corresponding Layer 2 tunnel.
  • the data message sent by the first customer service server is a pure Ethernet message.
  • the Ethernet message does not carry the inner VLAN ID and the outer VLAN ID.
  • the first customer switch does not need to add the inner VLAN ID, so that the first customer switch can send the customer service server The data message is directly sent to the first system switch.
  • the POP server if the data message forwarded by the first system switch carries both the inner VLAN ID and the outer VLAN ID, the POP server also needs to have the function of stripping the inner VLAN ID and the outer VLAN ID. Specifically, the POP server can still add openflow to ovs in the above-mentioned manner, and execute strip_vlan or similar functions through the added openflow, so as to realize the stripping function of the inner and outer VLAN IDs. In addition, the POP server can also create a multi-layer nested vlan interface in the Linux system, and realize the function of stripping the inner and outer vlan identifiers through the created multi-layer nested vlan interface. Specifically, combine the following application examples:
  • the first virtual network card eth0.200 can be created for the data message carrying the outer VLAN ID 200 through the physical network card eth0, which is the first virtual network used to receive the data message Interface; and according to the inner VLAN ID 400 to be stripped, the first virtual network card eth0.200 is used to create a second virtual network card eth0.200.400 for the data message carrying the inner VLAN ID 400, which is used to receive the datagram The second virtual network interface of the text.
  • the data message received by the physical network card is stripped of the outer VLAN identifier
  • the data message received by the first virtual network card is stripped of the inner VLAN
  • the second virtual network card can be received by the second virtual network card, so as to realize the process of peeling off the inner and outer VLAN IDs.
  • the virtual network interface of the POP server receives the data message, it can obtain the mapping relationship between the source mac address in the data message and each virtual network interface through the self-learning capability of the fdb table.
  • the POP server can receive the data message carrying the outer VLAN ID and the inner VLAN ID, and strip the outer VLAN ID and the inner VLAN ID carried, and finally restore the data sent by the customer service server Ethernet message, and send the Ethernet message to another POP server through a Layer 2 tunnel.
  • the virtual network interface created in the POP server can also have the function of stripping the inner VLAN ID, and the second virtual network interface still needs to be bridged with the above-mentioned second interface, so that the data message of the customer service server can pass The second layer tunnel for transmission.
  • each device deployed in the second geographic location in FIG. 5 and FIG. 6, when processing data packets sent by the second customer service server, the realized function can be similar to that of each device located in the first geographic location.
  • the correspondence is consistent, so I won’t repeat them here.
  • the functions implemented by the devices at the first geographic location and the second geographic location are the same, it does not mean that the devices on both sides need to adopt completely the same configuration.
  • the inner VLAN ID added by the first customer switch can be different from the inner VLAN ID added by the second customer switch
  • the outer VLAN ID added by the first system switch can be different from the outer VLAN ID added by the second system switch .
  • the POP server 1 When the POP server 1 receives a data message from the POP server 3, the data message is a pure Ethernet message. At this time, the POP server 1 can perform the opposite operation to the above process, add the outer VLAN ID to the received data message, and send the data message with the outer VLAN ID added to the first system switch, and subsequently , The first system switch may strip the received data message from the outer VLAN identifier, and then feed it back to the first customer service server.
  • the POP server 1 can add the inner VLAN ID to the received data message, and then continue to add the outer VLAN ID, and add The data message with the outer VLAN ID and the inner VLAN ID is sent to the first system switch.
  • the first system switch can send the data message carrying the inner vlan identifier to the first customer switch after stripping off the outer vlan identifier.
  • the first customer switch After the first customer switch receives the data message with the outer VLAN ID stripped, if the data message carries the inner VLAN ID, then the first customer switch can strip the received data message after the inner VLAN ID , Provide the restored Ethernet message to the first customer service server.
  • the interface for forwarding data packets can be determined based on the fdb table, and when the corresponding interface is reached, the corresponding vlan identification can be added, so that not only can the corresponding identification be added to the data packet, but also the transmission to The transmission path of the data message of the customer service server is the same as the transmission path of the data message sent from the customer service server, so that the data message can smoothly reach the customer service server.
  • the processing method for the Ethernet packet may be similar to the above-mentioned method.
  • the POP server 3 can add an outer VLAN ID with an id of 300 and an inner VLAN with an id of 500 to the received Ethernet packet, and the second system switch can strip the outer VLAN with an id of 300.
  • Layer VLAN ID the second customer switch can strip the inner VLAN ID with an id of 500.
  • This application also provides a network device, the network device includes a port connected to a layer 2 tunnel, wherein, if the port is a designated port, the initial state of the designated port is set to a blocked state, and if the port is a designated port
  • the designated port is connected to the root port through a Layer 2 tunnel, and the blocking state of the designated port is adjusted to the forwarding state; if the port is a root port, the initial state of the root port is set to the forwarding state, and the root port is passed through
  • the port sends a notification message used to characterize the identity of the root port to the opposite port; if the port is a port other than the designated port and the root port, the initial state of the other port is set to be blocked status.
  • the technical solution provided by this application can identify the type of the port for the port connected to the layer 2 tunnel on the network device. If the port is a designated port, the initial state of the designated port can be set to a blocked state instead of the forwarding state in the prior art. Later, if it is determined that the designated port is connected to the root port through a Layer 2 tunnel, the blocking state of the designated port is adjusted to the forwarding state. If the port is a root port, then the initial state of the root port can be set to the forwarding state. In addition, the root port can also send a notification message for characterizing the identity of the root port to the opposite port. In the prior art, the root port does not send the notification message to the opposite port.
  • the designated port can learn that the opposite port is the root port, thereby adjusting Specifies the port status of the port. If the port is other than the designated port and the root port, the initial state of the port can be set to the blocked state.
  • Figure 1 after the above-mentioned port status configuration method, the designated port on the left side of Layer 2 tunnel 1 is connected to the root port, so the designated port is adjusted to the forwarding state, and the root port on the right side of Layer 2 tunnel 1 It is in the forwarding state, so the Layer 2 tunnel 1 can transmit data packets normally.
  • the ports on the left side of the Layer 2 tunnel 2-4 are all designated ports, the ports on the right are all other ports, so that the designated ports on the left side of the Layer 2 tunnel 2-4 remain blocked. In this way, data packets will only be transmitted through the Layer 2 tunnel 1 and will not be transmitted on other Layer 2 tunnels, thereby solving the problem of traffic waste.
  • each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be realized by hardware.
  • the above technical solution essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM/RAM, magnetic A disc, an optical disc, etc., include a number of instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute the methods described in each embodiment or some parts of the embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种端口状态的配置方法及网络设备，其中，所述方法包括：识别与二层隧道相连的当前端口的端口类型，若所述当前端口为指定端口，将所述指定端口的初始状态置为阻塞状态，并且若所述指定端口通过二层隧道与根端口相连，将所述指定端口的阻塞状态调整为转发状态(S1)；若所述当前端口为根端口，将所述根端口的初始状态置为转发状态，并通过所述根端口向对侧的端口发送用于表征根端口身份的通知报文(S3)；若所述当前端口为除所述指定端口和所述根端口之外的其它端口，将所述其它端口的初始状态置为阻塞状态(S5)。

Description

一种端口状态的配置方法及网络设备
交叉引用
本申请引用于2019年9月4日递交的名称为“一种端口状态的配置方法及网络设备”的第201910831977.0号中国专利申请，其通过引用被全部并入本申请。
技术领域
本申请涉及互联网技术领域，特别涉及一种端口状态的配置方法及网络设备。
背景技术
目前，为了在网络结构发生变化时，能快速收敛网络，通常可以采用STP(Spanning Tree Protocol，生成树协议)或者RSTP(Rapid Spanning Tree Protocol，快速生成树协议)。在采用STP或者RSTP时，网络设备的端口可以处于多种不同的状态。以RSTP为例，网络端口的状态可以分为转发状态(Forwarding)或者阻塞状态(Blocking或者Discarding)，这些端口的状态通常可以与端口的类型具备对应关系。例如，根端口(Root Port，RP)和指定端口(Designated Port，DP)通常都是处于转发状态，而除根端口和指定端口外的其它端口(Alternate Port，AP)可以处于阻塞状态，这样可以保证数据报文在网络设备中传输时，避免出现传输环路。
请参阅图1所示的一个网络结构的应用示例，在图1中可以包括通信双方的多个交换机，不同侧的交换机可以通过二层隧道相连。按照RSTP进行端口状态的配置后，交换机1为根桥，交换机1上的各个端口均为DP，交换机2上，与交换机1相连的端口为RP，交换机2与二层隧道相连的两个端口为DP。而交 换机3和交换机4与二层隧道连接的端口中，只有与二层隧道1右侧的连接的端口是RP，其它的三个端口都是AP，并且在交换机3上，与交换机4相连的端口为DP，而在交换机4上，与交换机3相连的端口为RP。其中，DP均可以处于转发状态。这样，四条二层隧道中，实际上只有二层隧道1是通畅的。交换机1和交换机2在接收到同一份数据报文时，会将数据报文从各个端口向外发出，只不过只有二层隧道1传输的数据报文会被交换机3接收，二层隧道2至4传输的数据报文都会被丢弃，这样可以避免同一份数据报文的重复接收。然而，针对这同一份数据报文，是通过了四条链路同时发送，这样会造成四倍的数据流量。因此，按照目前的端口状态的配置方法，会造成流量浪费的情况。
发明内容
本申请部分实施例的目的在于提供一种端口状态的配置方法及网络设备，能够避免数据传输过程中的流量浪费情况。
为实现上述目的，本申请一方面提供一种端口状态的配置方法，所述方法包括：识别与二层隧道相连的当前端口的端口类型，若所述当前端口为指定端口，将所述指定端口的初始状态置为阻塞状态，并且若所述指定端口通过二层隧道与根端口相连，将所述指定端口的阻塞状态调整为转发状态；若所述当前端口为根端口，将所述根端口的初始状态置为转发状态，并通过所述根端口向对侧的端口发送用于表征根端口身份的通知报文；若所述当前端口为除所述指定端口和所述根端口之外的其它端口，将所述其它端口的初始状态置为阻塞状态。
为实现上述目的，本申请另一方面还提供一种网络设备，所述网络设备中包含与二层隧道相连的端口，其中，若所述端口为指定端口，将所述指定端口的初始状态置为阻塞状态，并且若所述指定端口通过二层隧道与根端口相连，将所述指定端口的阻塞状态调整为转发状态；若所述端口为根端口，将所述根端口的初始状态置为转发状态，并通过所述根端口向对侧的端口发送用于表征 根端口身份的通知报文；若所述端口为除所述指定端口和所述根端口之外的其它端口，将所述其它端口的初始状态置为阻塞状态。
由上可见，本申请提供的技术方案，针对网络设备上与二层隧道相连的端口，可以识别端口的类型。如果该端口为指定端口，可以将该指定端口的初始状态置为阻塞状态，而并非是现有技术中的转发状态。后续，如果判定指定端口通过二层隧道与根端口相连，才将指定端口的阻塞状态调整为转发状态。如果该端口为根端口，那么可以将根端口的初始状态置为转发状态，除此之外，还可以通过根端口向对侧的端口发送用于表征根端口身份的通知报文。而在现有技术中，根端口并不会向对侧的端口发送该通知报文，在本申请中按照这种方式进行改进后，可以使得指定端口能够获知对侧端口为根端口，从而调整指定端口的端口状态。如果端口为除指定端口和根端口之外的其它端口，可以将该端口的初始状态置为阻塞状态。继续以图1为例，通过上述的端口状态的配置方法后，二层隧道1左侧的指定端口由于与根端口相连，那么该指定端口被调整为转发状态，二层隧道1右侧的根端口本身就处于转发状态，因此二层隧道1是可以正常传输数据报文的。而二层隧道2-4左侧的端口尽管都是指定端口，但右侧的端口都是其它端口，使得二层隧道2-4左侧的指定端口的状态都依然保持阻塞状态。这样，数据报文只会通过二层隧道1进行传输，而不会在其它的二层隧道上传输，从而解决了流量浪费的问题。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是一个网络结构的应用示例；
图2是本申请实施例中网络设备之间的连接示意图；
图3是本申请实施例中端口状态的配置方法步骤示意图；
图4是本申请实施例中网络设备与交换机之间的连接示意图；
图5是本申请实施例中二层专线网络系统的第一结构示意图；
图6是本申请实施例中二层专线网络系统的第二结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施例详细描述。
本申请提供一种端口状态的配置方法，该方法可以应用于支持STP或者RSTP的网络设备中。请参阅图2和图3，所述方法可以包括以下步骤。
S1：识别与二层隧道相连的当前端口的端口类型，若所述当前端口为指定端口，将所述指定端口的初始状态置为阻塞状态，并且若所述指定端口通过二层隧道与根端口相连，将所述指定端口的阻塞状态调整为转发状态。
在本实施例中，网络设备之间可以通过二层隧道进行连接，从而在不同的地理位置之间建立二层专线网络。如图2所示，多个网络设备可以分布于不同的地理位置，任一网络设备，可以与对侧的其它网络设备之间建立二层隧道。在网络设备上可以部署一个或者多个端口，这些端口可以分别与不同的二层隧道相连。
在本实施例中，当网络拓扑确定之后，网络设备可以通过互相发送BPDU(网桥协议数据单元，Bridge Protocol Data Unit)报文，从而确定网络设备是根桥还是非根桥，后续可以确定出网络设备上的各个端口的端口类型。这些端口类型可以包括根端口(RP)、指定端口(DP)和其它端口(AP)。
在本实施例中，为了避免流量浪费，在确定出网络设备上的各个端口的端口类型后，可以对端口的初始状态以及状态的切换进行改进。具体地，首先可以从网络设备中识别与二层隧道相连的当前端口的端口类型。需要说明的是，网络设备中的端口并不一定全部与二层隧道相连，有一些端口还可能与交换机 等其它网络设备相连，本实施例可以仅针对与二层隧道相连的端口进行改进。网络设备上的各个端口的端口类型，可以由STP或者RSTP确定，通过获取STP或者RSTP的确定结果，从而可以识别出与二层隧道相连的当前端口的端口类型。所述当前端口，可以是网络设备上与二层隧道相连的任一端口。
在本实施例中，若当前端口的端口类型为指定端口，现有技术中的指定端口，初始状态往往都是转发状态，而在本实施例中，可以将指定端口的初始状态置为阻塞状态。在现有技术中，指定端口的状态在正常的数据传输过程中，往往不会改变，而在本实施例中，对于初始状态为阻塞状态的指定端口而言，如果在判定该指定端口通过二层隧道与根端口相连的情况下，那么可以将该指定端口的阻塞状态调整为转发状态。
结合图2，在网络拓扑确定后，根据STP或者RSTP进行根桥和非根桥的选取后，网络设备1可以作为根桥，网络设备2至4均可以作为非根桥。同时，STP或者RSTP在实现网络收敛时，可以确定出网络设备上各个端口的端口类型。具体地，网络设备1上的端口可以均为指定端口，网络设备3上连接二层隧道1的端口，由于距离根桥最近，因此该端口可以作为根端口，而网络设备3上连接二层隧道4的端口可以作为其它端口。网络设备2上连接二层隧道2和二层隧道4的两个端口可以是指定端口，网络设备4上连接二层隧道2和二层隧道3的两个端口可以是其它端口。确定出各个端口的端口类型之后，按照本实施例上述的操作方式，二层隧道左侧的四个端口由于都是指定端口，因此这四个端口的初始状态都被置为阻塞状态。而由于二层隧道1右侧的端口为根端口，因此二层隧道1左侧的端口由于与根端口相连，因此该端口的状态被调整为转发状态。最终，二层隧道左侧的四个端口，仅有网络设备1上与二层隧道1相连的端口是处于转发状态，其它3个端口都处于阻塞状态。
S3：若所述当前端口为根端口，将所述根端口的初始状态置为转发状态，并通过所述根端口向对侧的端口发送用于表征根端口身份的通知报文。
在本实施例中，如果当前端口为根端口，那么可以将根端口的初始状态 置为转发状态。此外，现有技术中的根端口通常不会发送BPDU报文，而在本实施例中，由于指定端口的状态需要根据对侧是否为根端口来调整，因此在将根端口的状态置为转发状态时，还需要通过根端口向对侧的端口发送用于表征根端口自身身份的通知报文。在实际应用中，该通知报文可以是上述的BPDU报文，在BPDU报文中具备Port Role(端口角色)字段，该字段中填充表征根端口身份的标识。这样，对侧的指定端口通过识别该通知报文的端口角色字段中的内容，从而可以确定出对侧的端口为根端口。这样，指定端口通过相连的二层隧道接收到对侧的端口发来的用于表征根端口身份的通知报文后，便可以判定该指定端口通过二层隧道与根端口相连，从而可以将指定端口的状态从阻塞状态调整为转发状态。
在一个实施例中，根端口可以按照指定时间周期向对侧的端口发送上述的通知报文。该指定时间周期可以是预先设置的，例如，该指定时间周期可以是2秒。在本实施例中，在数据传输过程中，当前正在使用的二层隧道可能会发生通信故障。在这种情况下，需要从剩余的二层隧道中选择一条备用的二层隧道，并通过选择的二层隧道继续进行数据传输。例如，当二层隧道1发生通信故障时，可以选用二层隧道2继续进行通信。在这种情况下，网络设备1中连接二层隧道1的端口便无法正常接收到对侧根端口发来的通知报文。鉴于此，若调整为转发状态的指定端口在指定时长内未接收到对侧的端口发来的通知报文，那么可以将该指定端口的转发状态重新恢复为阻塞状态。其中，该指定时长可以是预先设置的，例如，该指定时长可以是4秒。
S5：若所述当前端口为除所述指定端口和所述根端口之外的其它端口，将所述其它端口的初始状态置为阻塞状态。
在本实施例中，如果当前端口为除指定端口和根端口之外的其它端口，那么可以将其它端口的初始状态置为阻塞状态。通过上述多个步骤的操作，图2中的四个网络设备，仅有二层隧道1两侧的端口处于转发状态，与其它二层隧道相连的端口均处于阻塞状态。这样，数据报文只会从一个端口发出，从而避 免了流量浪费的情况。
在一个实施例中，上述配置端口状态的方式可以作为一种自定义功能，该自定义功能可以预先配置于网络设备中，并且该自定义功能可以被主动开启或者关闭。当该自定义功能被关闭时，可以采用现有技术中的方式进行端口状态的配置，而当该自定义功能被开启时，可以采用本申请上述步骤的方式进行端口状态的配置。此外，该自定义功能还可以仅针对网络设备中的部分端口启用。例如，图4所示的系统架构中，对侧的网络设备之间可以通过二层隧道相连，而同侧的网络设备可以与交换机相连。在这种情况下，可以仅针对与二层隧道相连的端口开启上述的自定义功能，而针对未与二层隧道相连的端口，可以关闭该自定义功能。这样，针对未与二层隧道相连的端口，若所述端口为指定端口，那么可以将该端口的初始状态置为转发状态，而不是阻塞状态。同时，如果未与二层隧道相连的端口为根端口，也无需向对侧的端口定期发送通知报文。这样处理的原因在于，如果在与交换机相连的端口上也开启上述的自定义功能，会导致系统陷入瘫痪。举例来说，假设网络设备1此时为根桥，那么网络设备1上的端口都是指定端口，网络设备2与交换机相连的端口就是根端口。如果网络设备1、网络设备2与交换机1相连的端口也都开启了上述的自定义功能，那么此时指定端口和根端口都可以处于转发状态。但是，如果网络设备2突然发生了故障，那么网络设备1上与交换机相连的端口便无法接收到对侧端口发来的通知报文，在这种情况下，网络设备1也会将与交换机相连的端口重新调整为阻塞状态，这样就导致当网络设备2发生故障时，会连带着网络设备1同样关闭端口的数据转发功能，这样，从交换机发来的数据报文便无法向后传输，从而导致整个二层专线网络陷入瘫痪。因此，针对未与二层隧道相连的端口不能开启上述的自定义功能，而是采用现有技术中的方式进行端口状态的配置。
在一个具体应用示例中，上述的端口状态的配置方法，可以应用于如图5所示的二层专线网络系统中的POP服务器中。请参阅图5，所述系统中可以包括 系统交换机和POP服务器。通常而言，二层专线网络可以用于传输不同的客户业务服务器之间的数据报文，这些客户业务服务器可以分布于不同的城市，或者分布于同一城市相距较远的地理位置。在本申请中，为了提高二层专线网络的稳定性，在不同侧的POP服务器之间，可以建立多条二层隧道，系统交换机可以和同侧的各个POP服务器相连。
在实际应用中，各个POP服务器中可以运行OVS(OpenVirtualSwitch，开放式虚拟交换机)或者其它具备类似功能的软件，通过该软件可以对POP服务器进行配置，从而实现二层专线网络。具体地，可以在各个POP服务器上开启用于实现二层专线网络的通信协议，该通信协议例如可以是stp或者rstp。通过开启的通信协议，可以为POP服务器设置优先级(Priority)，并且可以为POP服务器的各个端口分配链路开销值。在实际应用中，上述的优先级和链路开销值可以是数值，其中，数值越小，优先级可以越高，而数值越大，链路开销值可以越大。分配的优先级和链路开销值，可以用于确定POP服务器上各个端口的端口类型。具体地，对于连接不同二层隧道的端口而言，可以分配不同的链路开销值，而同一个二层隧道两侧的端口，可以分配相同的链路开销值。例如，图5中共建立了四条二层隧道，那么这四条二层隧道可以对应不同的四个链路开销值(例如分别为100、110、120、130)，而对于二层隧道1而言，其两侧的两个端口均可以配置数值为100的链路开销值。
在一个实施例中，首先可以根据各个POP服务器的优先级，筛选出根桥(Root Bridge)。具体地，可以将优先级最高的POP服务器作为根桥，若优先级最高的POP服务器有多个，那么可以将桥ID最小的POP服务器选为根桥。其中，桥ID可以是优先级和POP服务器的MAC地址之和。在选出根桥之后，根桥上各个端口的端口类型均可以是指定端口。
在本实施例中，当选取出根桥之后，可以确定其它POP服务器上各个端口的端口类型。具体地，对于当前的POP服务器而言，可以确定出各个端口与根桥之间的链路开销值，并且将链路开销值最低的端口作为根端口，如果链路 开销值最低的端口有多个，那么可以将端口ID最低的端口作为根端口。其中，端口ID可以是POP服务器的优先级和端口号之和。
在本实施例中，在确定出POP服务器上的根端口后，可以确定POP服务器上的指定端口。具体地，对于一条通信链路而言，如果该通信链路的两侧端口中有一个是根端口，那么另一个端口便可以作为指定端口。而如果该通信链路的两侧端口中都没有根端口，那么可以从这两个端口中选取一个作为指定端口。在实际应用中，首先可以识别这两个端口中与根桥之间的链路开销值最小的端口，并将该链路开销值最小的端口作为指定端口。而如果链路开销值一致，那么可以根据端口所在的POP服务器的优先级来确定指定端口。优先级较高的那个端口可以作为指定端口。而如果优先级依然一致，那么可以根据端口所在的POP服务器的桥ID来确定指定端口。桥ID最小的端口可以作为指定端口。
这样，通过上述的方式，可以在各个POP服务器上确定出根端口和指定端口。对于各个端口的状态，可以按照步骤S1至S5中描述的方式进行配置。对于一条目标二层隧道而言，若该目标二层隧道的两侧端口均处于转发状态，那么该目标二层隧道便处于转发状态，通过该目标二层隧道可以正常传输数据报文。而如果该目标二层隧道的任一端口处于阻塞状态，那么该目标二层隧道便处于阻塞状态，阻塞状态下的二层隧道无法将数据报文从一个POP服务器发送至另一个POP服务器。这样，不同侧的POP服务器之间建立的多条二层隧道，经过上述的方式操作之后，可以保证在同一时刻，仅有一条二层隧道处于转发状态，从而避免数据报文通过不同的二层隧道重复传输。
需要说明的是，有时候二层专线网络的通信两侧可以是对称的网络结构，那么此时各个POP服务器的优先级可以是完全相同的。在这种情况下，可以无需配置各个POP服务器的优先级，而是通过链路开销值和MAC地址来确定各个端口的端口类型。
在一个实施例中，POP服务器与系统交换机相连的端口，也可以分配链路开销值。而且，为了使得系统交换机发出的数据报文能够正常到达相连的各个 POP服务器，可以将POP服务器与系统交换机相连的端口的链路开销值设置地低一些，而将POP服务器与对侧POP服务器相连的端口的链路开销值设置地高一些。这样，对于任一POP服务器而言，与系统交换机相连的端口可以比与对侧的POP服务器相连的端口具备较低的链路开销值。例如，图5中POP服务器1与系统交换机相连的端口的链路开销值可以是1，而二层隧道1的链路开销值可以是100。
在本实施例中，如果POP服务器发生故障，或者网络环境发生波动，导致当前处于转发状态的二层隧道不可用，那么运行于POP服务器上的通信协议可以根据分配的链路开销值，从剩余的可用的二层隧道中选取一条目标二层隧道，并将所述目标二层隧道置于转发状态，从而通过该目标二层隧道继续传输数据报文。具体地，可以从剩余的可用的二层隧道中选取链路开销值最小的二层隧道作为上述的目标二层隧道，这样，始终可以保证当前处于转发状态的二层隧道，是可用的二层隧道中链路开销值最小的。通过这种二层隧道的切换方式，能够提高数据传输的稳定性。
在实际应用中，系统交换机通常自带MAC地址学习功能，该功能可以自动识别数据报文中的MAC地址，并将识别得到MAC地址与接收数据报文的端口建立关联关系，从而构建得到MAC地址转发表(forwarding database，fdb表)。通过该fdb表，系统交换机可以避免将同一份数据报文发送至多个不同的POP服务器。然而，在本实施例中，由于二层隧道可能会发生切换，如果系统交换机按照fdb表仅仅将数据报文转发至相连的一个POP服务器，那么可能该POP服务器无法通过二层隧道将接收到的数据报文发送至对侧的POP服务器。例如，图5中的二层隧道1发生了故障，系统自动切换至了二层隧道2，此时，如果系统交换机依然根据fdb表将数据报文发送至POP服务器1，那么将导致该数据报文无法传输至对侧。鉴于此，在本实施例中，可以关闭系统交换机中的MAC地址学习功能。这样，当系统交换机接收到数据报文时，该数据报文中的目的MAC地址没有被学习，因此系统交换机可以采用flood的方式，数据报文转发至与 该系统交换机相连的各个POP服务器处，那么各个POP服务器会尝试通过二层隧道转发接收到的数据报文。根据上文的描述，在同一时刻只有一条二层隧道是处于转发状态，因此只会有一份数据报文被转发至对侧的POP服务器，其它的数据报文均由于二层隧道处于阻塞状态而无法发送至对侧的POP服务器，从而保证了数据报文不会重复传输。
请参阅图5，在一个实施例中，数据报文从第一客户业务服务器传输至第二客户业务服务器的过程中，会经过第一系统交换机，故第一系统交换机可以接收到来自第一客户业务服务器的数据报文。在实际应用中，第一系统交换机可以与同属于第一地理位置的多台客户业务服务器相连，因此，为了区分不同的客户业务服务器发来的数据报文，第一系统交换机可以为接收到的数据报文添加外层vlan标识，该外层vlan标识可以用于表征当前接收到的数据报文归属的客户。在实际应用中，可以预先将第一系统交换机上，与第一客户业务服务器相连的端口配置QinQ功能(也称为Stacked vlan或Double vlan功能)，并且在第一系统交换机上，可以针对不同的客户业务服务器，预先分配不同的外层vlan标识。这样，当该端口接收到来自第一客户业务服务器的数据报文后，可以在该数据报文中添加与第一客户业务服务器相匹配的外层vlan标识。
在本实施例中，第一系统交换机为了能将第一客户业务服务器发来的数据报文转发至相连的POP服务器1和POP服务器2，可以将与POP服务器1和POP服务器2相连的目标端口配置上述的外层vlan标识。这样，从第一系统交换机的角度来看，与第一客户业务相连的端口和与POP服务器1和POP服务器2相连的目标端口，可以处于同一个vlan内，从而使得第一客户业务服务器发送的数据报文，最终能够被送往POP服务器1和POP服务器2进行处理。此外，第一系统交换机还可以将上述的目标端口配置为用于保留外层vlan标识的端口类型，例如，可以是trunk类型。这样，第一系统交换机便可以通过所述目标端口，将携带上述外层vlan标识的数据报文发送至相连的POP服务器1和POP服务器2。
在本实施例中，POP服务器在接收到携带所述外层vlan标识的数据报文后，可以通过识别其中的外层vlan标识，从而判定当前的数据报文所归属的客户，以确定传输数据报文的二层隧道，如此一来，pop服务器可基于不同的外层vlan标识为不同的客户分配对应的二层隧道，不仅可实现不同客户间的数据隔离，支持多客户场景，而且实现了pop服务器的复用，节省硬件成本。如图5所示，POP服务器1与POP服务器3之间可以通过二层隧道1相连，该二层隧道上传输的数据报文，通常需要是纯净的以太网报文。鉴于此，POP服务器1在识别出接收到的数据报文所归属的客户后，需要将该数据报文中携带的外层vlan标识剥离，从而还原出第一客户业务服务器发送的以太网报文，最终，可以将还原出的以太网报文通过预先创建的二层隧道发送至POP服务器3处。
在一个实施例中，可以预先在POP服务器中创建与外层vlan标识对应的第一接口，用于接收相应的外层vlan标识数据报文，并用于剥离外层vlan标识的。在实际应用中，可以通过多种方式来创建该第一接口。举例来说，可以在linux系统中创建多层嵌套的vlan接口，并将创建的该多层嵌套的vlan接口作为上述的第一接口。具体地，请参阅以下应用示例：
ip link add eth0.200 link eth0 type vlan id 200
其中，eth0可以表示用于接收数据报文的物理网卡，那么通过该物理网卡，可以为外层vlan标识为200的数据报文创建一个虚拟网卡eth0.200，即用于接收该数据报文的第一接口，专门用于接收外层vlan标识为200的数据报文，该虚拟网卡可以设置与上述外层vlan标识相同的id，因此得到名称为eth0.200的虚拟网卡。
当上述的物理网卡eth0接收到携带外层vlan标识的数据报文后，可以将外层vlan标识剥离，确定外层vlan标识为200后，并将剥离后的数据报文发送给名称为eth0.200的虚拟网卡，这样便可以实现对外层vlan标识的剥离。同时，第一pop服务器通过fdb(forwarding database，转发数据)表的自学习能力，获得了数据报文中的源mac地址与第一接口的映射关系。
当然，在实际应用中，还可以具备其它更多的方式来实现外层vlan标识的剥离功能。例如，可以在当使用ovs(openswitch，开放式虚拟交换机)软件来创建目标网桥时，也可以在ovs网桥中添加openflow，并通过添加的openflow来执行strip_vlan(移除数据报文中的vlan标识)或者类似功能的动作，从而实现外层vlan标识的剥离。
在本实施例中，POP服务器1在创建与POP服务器3相连的二层隧道时，也可以具备多种实现方式。例如，POP服务器1可以使用linux系统中的vxlan接口，来创建vxlan隧道，该vxlan隧道便可以作为创建的二层隧道。又例如，POP服务器1和POP服务器3上均可以通过ovs创建类型为vxlan的接口，通过这两个接口形成的二层隧道便可以作为二层隧道。上述的linux系统中创建的vxlan接口，或者ovs中类型为vxlan的接口，便可以作为POP服务器1中用于连接二层隧道的第二接口。
在本实施例中，为了使得POP服务器1接收到的数据报文，能够通过二层隧道发送至POP服务器3，需要将上述的第一接口和第二接口进行桥接。具体地，POP服务器1可以创建目标网桥(bridge)，并将上述的第一接口和第二接口作为该目标网桥的两个端口，从而实现将两个接口进行桥接的过程。在实际应用中，该目标网桥可以通过linux系统或者ovs系统或者其它的方式来创建，本申请对此并不做限定。同样的，当数据报文通过第二接口进行转发后，第一POP服务器可通过fdb表的自学习能力，获得了数据报文中的源mac地址与第二接口的映射关系。
在本申请一个实施例中，考虑到如果同一客户有多个不同网段的客户业务服务器均需要创建二层专线，或者第一地理区域中存在多个不同客户的客户业务服务器情况下，那么该些客户业务服务器与第一系统交换机之间便需要建立多条通信线路，这样无疑会增加第一系统交换机的负担。鉴于此，可以在第一系统交换机和客户业务服务器之间，增加一个或者多个客户交换机，例如，为每个客户增设至少一个客户交换机，这些客户交换机可以分别与客户业务服 务器和第一系统交换机相连，其中客户交换机与第一交换机之间在逻辑上是端口直连的，例如，直接通过网线连接，或者通过建立专线连接。
具体地，请参阅图6，以一个客户交换机为例来阐述本申请的方案。第一客户端交换机可以接收各个客户业务服务器发来的数据报文，在实际应用中，不同的客户业务服务器可能会被划分至不同的网段中，为了区分不同网段内的客户业务服务器发来的数据报文，第一客户交换机可以为接收到的数据报文添加内层vlan标识，并将其发送至第一系统交换机，该内层vlan标识可以用于表征发送数据报文的客户业务服务器归属的网。
数据报文通过第一客户交换机后，携带内层vlan标识，被第一系统交换机接收后，可以按照上述的方式，继续添加外层vlan标识。需要说明的是，在这种情况下，第一系统交换机可以为相连的各个客户交换机分配互不相同的外层vlan标识，并为当前客户交换机发来的数据报文添加与所述当前客户交换机相匹配的外层vlan标识。这样，通过内层vlan标识和外层vlan标识相组合的方式，能够唯一地确定出用于传输数据报文的线路通道，包含POP服务器上的接口及对应的二层隧道。
如图6所示，第一客户业务服务器发出的数据报文是纯净的以太网报文，该以太网报文中不会携带内层vlan标识和外层vlan标识，在经过第一客户交换机后，可以添加id为400的内层vlan标识，在经过第一系统交换机后，可以继续添加id为200的外层vlan标识。
当然，如果与第一客户交换机相连的客户业务服务器均处于同一个vlan内，那么第一客户交换机也可以不添加内层vlan标识，这样，第一客户交换机可以将所述客户业务服务器发来的数据报文直接发送至第一系统交换机。
在一个实施例中，如果第一系统交换机转发的数据报文同时携带内层vlan标识和外层vlan标识，那么POP服务器也需要具备剥离内层vlan标识和外层vlan标识的功能。具体地，POP服务器仍然可以通过上述的方式，在ovs中添加openflow，并通过添加的openflow来执行strip_vlan或者类似功能的 动作，从而实现内外层vlan标识的剥离功能。此外，POP服务器也可以在linux系统中创建多层嵌套的vlan接口，并通过创建的该多层嵌套的vlan接口来实现内外层vlan标识的剥离功能。具体地，结合下述的应用示例：
ip link add eth0.200 link eth0 type vlan id 200
ip link add eth0.200.400 link eth0.200 type vlan id 400
可见，可以根据待剥离的外层vlan标识200，通过物理网卡eth0为携带外层vlan标识200的数据报文创建第一虚拟网卡eth0.200，即用于接收该数据报文的第一虚拟网络接口；并根据待剥离的内层vlan标识400，通过所述第一虚拟网卡eth0.200为携带内层vlan标识400的数据报文创建第二虚拟网卡eth0.200.400，即用于接收该数据报文的第二虚拟网络接口。
这样，所述物理网卡接收到的数据报文被剥离掉外层vlan标识后，可以被所述第一虚拟网卡接收，并且所述第一虚拟网卡接收到的数据报文被剥离掉内层vlan标识后，可以被所述第二虚拟网卡接收，从而实现内外层vlan标识剥离的过程。同时，POP服务器的上述虚拟网络接口在接收到数据报文之后，可通过fdb表的自学习能力，获得了数据报文中的源mac地址与各虚拟网络接口的映射关系。
由上可见，POP服务器可以接收携带外层vlan标识和内层vlan标识的数据报文，并剥离携带的所述外层vlan标识和所述内层vlan标识，最终可以还原出客户业务服务器发送的以太网报文，并将该以太网报文通过二层隧道发送至另一个POP服务器。此外，在POP服务器中创建的虚拟网络接口，也可以具备剥离内层vlan标识的功能，并且第二虚拟网络接口依然需要与上述第二接口进行桥接，从而使得客户业务服务器的数据报文能够通过二层隧道进行传输。
在本实施例中，图5和图6中部署于第二地理位置处的各个设备，在处理第二客户业务服务器发送的数据报文时，实现的功能可以与第一地理位置处的各个设备对应一致，这里便不再赘述。需要说明的是，尽管第一地理位置处和第二地理位置处的设备实现的功能一致，但不表示这两侧的设备需要采用完 全相同的配置。例如，第一客户交换机添加的内层vlan标识可以与第二客户交换机添加的内层vlan标识不同，以及第一系统交换机添加的外层vlan标识可以与第二系统交换机添加的外层vlan标识不同。
当POP服务器1接收到POP服务器3发来的数据报文时，该数据报文是纯净的以太网报文。此时，POP服务器1可以执行与上述过程相反的操作，为接收到的所述数据报文添加外层vlan标识，并将添加了外层vlan标识的数据报文发送至第一系统交换机，后续，第一系统交换机可以将接收到的数据报文剥离外层vlan标识后，反馈给第一客户业务服务器。
如果第一系统交换机和第一客户业务服务器之间存在第一客户交换机，那么POP服务器1可以为接收到的所述数据报文添加内层vlan标识后，继续添加外层vlan标识，并将添加了外层vlan标识和内层vlan标识的数据报文发送至第一系统交换机。这样，第一系统交换机可以在剥离掉外层vlan标识后，将携带内层vlan标识的数据报文发送至第一客户交换机。该第一客户交换机接收到剥离了外层vlan标识的数据报文后，若该数据报文中携带内层vlan标识，那么第一客户交换机可以将接收到的数据报文剥离内层vlan标识后，将还原得到的以太网报文提供给第一客户业务服务器。
上述的添加和剥离vlan标识的具体实现方式，均可以参照前述实施例中的描述，通过linux系统或者ovs或者其它类似的方式来实现，这里便不再赘述。在一实际应用中，可基于fdb表来确定转发数据报文的接口，并在到达对应的接口时，添加对应的vlan标识，从而不仅能为数据报文添加对应的标识，还能保证发往客户业务服务器的数据报文的传输路径与发送来自该客户业务服务器的数据报文的传输路径相同，进而使得数据报文能顺利到达客户业务服务器。
需要说明的是，POP服务器3接收到POP服务器1发来的以太网报文后，针对该以太网报文的处理方式，可以与上述的方式类似。例如，在图6中，POP服务器3可以将接收到的以太网报文添加id为300的外层vlan标识和id为500 的内层vlan标识，第二系统交换机则可以剥离id为300的外层vlan标识，第二客户交换机则可以剥离id为500的内层vlan标识。
本申请还提供一种网络设备，所述网络设备中包含与二层隧道相连的端口，其中，若所述端口为指定端口，将所述指定端口的初始状态置为阻塞状态，并且若所述指定端口通过二层隧道与根端口相连，将所述指定端口的阻塞状态调整为转发状态；若所述端口为根端口，将所述根端口的初始状态置为转发状态，并通过所述根端口向对侧的端口发送用于表征根端口身份的通知报文；若所述端口为除所述指定端口和所述根端口之外的其它端口，将所述其它端口的初始状态置为阻塞状态。
由上可见，本申请提供的技术方案，针对网络设备上与二层隧道相连的端口，可以识别端口的类型。如果该端口为指定端口，可以将该指定端口的初始状态置为阻塞状态，而并非是现有技术中的转发状态。后续，如果判定指定端口通过二层隧道与根端口相连，才将指定端口的阻塞状态调整为转发状态。如果该端口为根端口，那么可以将根端口的初始状态置为转发状态，除此之外，还可以通过根端口向对侧的端口发送用于表征根端口身份的通知报文。而在现有技术中，根端口并不会向对侧的端口发送该通知报文，在本申请中按照这种方式进行改进后，可以使得指定端口能够获知对侧端口为根端口，从而调整指定端口的端口状态。如果端口为除指定端口和根端口之外的其它端口，可以将该端口的初始状态置为阻塞状态。以图1为例，通过上述的端口状态的配置方法后，二层隧道1左侧的指定端口由于与根端口相连，那么该指定端口被调整为转发状态，二层隧道1右侧的根端口本身就处于转发状态，因此二层隧道1是可以正常传输数据报文的。而二层隧道2-4左侧的端口尽管都是指定端口，但右侧的端口都是其它端口，使得二层隧道2-4左侧的指定端口的状态都依然保持阻塞状态。这样，数据报文只会通过二层隧道1进行传输，而不会在其它的二层隧道上传输，从而解决了流量浪费的问题。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同 相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，针对网络设备实施例来说，均可以参照前述方法的实施例的介绍对照解释。
通过以上的实施例的描述，本领域的技术人员可以清楚地了解到各实施例可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
以上所述仅为本申请的较佳实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (13)

  1. 一种端口状态的配置方法，所述方法包括：
    识别与二层隧道相连的当前端口的端口类型，若所述当前端口为指定端口，将所述指定端口的初始状态置为阻塞状态，并且若所述指定端口通过二层隧道与根端口相连，将所述指定端口的阻塞状态调整为转发状态；
    若所述当前端口为根端口，将所述根端口的初始状态置为转发状态，并通过所述根端口向对侧的端口发送用于表征根端口身份的通知报文；
    若所述当前端口为除所述指定端口和所述根端口之外的其它端口，将所述其它端口的初始状态置为阻塞状态。
  2. 根据权利要求1所述的方法，其中，若所述指定端口通过相连的二层隧道接收到对侧的端口发来的用于表征根端口身份的通知报文，判定所述指定端口通过二层隧道与根端口相连。
  3. 根据权利要求1所述的方法，其中，所述根端口按照指定时间周期向对侧的端口发送所述通知报文；所述方法还包括：
    若调整为转发状态的指定端口在指定时长内未接收到对侧的端口发来的通知报文，将所述指定端口的转发状态恢复为阻塞状态。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    针对未与二层隧道相连的端口，若所述端口为指定端口，将所述端口的初始状态置为转发状态。
  5. 根据权利要求1所述的方法，其中，所述方法应用于POP服务器中，所述POP服务器与同侧的系统交换机相连，不同侧的POP服务器之间通过二层隧道相连；所述方法还包括：
    为所述POP服务器的各个端口分配链路开销值，其中，连接不同的二层隧道的端口具备不同的链路开销值；
    在同一时刻，仅有一条二层隧道处于转发状态，若处于转发状态的二层隧 道不可用，根据分配的链路开销值，从剩余的可用的二层隧道中选取一条目标二层隧道，并将所述目标二层隧道置于转发状态。
  6. 根据权利要求5所述的方法，其中，所述方法还包括：
    所述系统交换机接收来自客户业务服务器的数据报文，并为所述数据报文添加外层虚拟局域网标识，所述外层虚拟局域网标识用于表征所述数据报文归属的客户；其中，在所述系统交换机上，与POP服务器相连的目标端口配置有所述外层虚拟局域网标识，并且所述目标端口被配置为用于保留所述外层虚拟局域网标识的端口类型，以使得所述系统交换机通过所述目标端口，将携带所述外层虚拟局域网标识的数据报文发送至相连的POP服务器；
    所述POP服务器在接收到携带所述外层虚拟局域网标识的数据报文后，剥离所述外层虚拟局域网标识，以还原出所述客户业务服务器发送的数据报文，并通过二层隧道将还原得到的所述数据报文发送至对侧的POP服务器。
  7. 根据权利要求6所述的方法，其中，所述客户业务服务器和所述系统交换机之间还通过客户交换机相连；所述方法还包括：
    所述客户交换机接收各个所述客户业务服务器发来的数据报文，并且若所述客户业务服务器被划分至不同的网段中，所述客户交换机为接收到的数据报文添加内层虚拟局域网标识，所述内层虚拟局域网标识用于表征接收到的数据报文归属的网段；
    所述客户端交换机将携带所述内层虚拟局域网标识的数据报文发送至相连的系统交换机。
  8. 根据权利要求7所述的方法，其中，所述方法还包括：
    所述系统交换机为相连的各个客户交换机分配互不相同的外层虚拟局域网标识，并为当前客户交换机发来的数据报文添加与所述当前客户交换机相匹配的外层虚拟局域网标识；
    所述POP服务器在接收到携带外层虚拟局域网标识和内层虚拟局域网标识的数据报文后，剥离携带的所述外层虚拟局域网标识和所述内层虚拟局域网标识。
  9. 根据权利要求6至8中任一所述的方法，其中，所述方法还包括：
    在所述POP服务器中预先创建用于剥离外层虚拟局域网标识和内层虚拟局域网标识的第一接口，以及用于连接二层隧道的第二接口，其中，所述第一接口和所述第二接口进行桥接。
  10. 根据权利要求9所述的方法，其中，所述方法还包括：
    所述POP服务器在创建所述第一接口时，根据待剥离的外层虚拟局域网标识，通过物理网卡创建携带所述外层虚拟局域网标识的第一虚拟网卡，并根据待剥离的内层虚拟局域网标识，通过所述第一虚拟网卡，创建携带所述内层虚拟局域网标识的第二虚拟网卡；其中，所述物理网卡接收到的数据报文被剥离掉外层虚拟局域网标识后，被所述第一虚拟网卡接收，并且所述第一虚拟网卡接收到的数据报文被剥离掉内层虚拟局域网标识后，被所述第二虚拟网卡接收。
  11. 根据权利要求6所述的方法，其中，所述方法还包括：
    所述POP服务器在接收到对侧的POP服务器发来的数据报文后，为接收到的所述数据报文添加外层虚拟局域网标识，并将添加了外层虚拟局域网标识的数据报文发送至相连的系统交换机；
    所述系统交换机将接收到的数据报文剥离外层虚拟局域网标识后，反馈给所述客户业务服务器。
  12. 根据权利要求11所述的方法，其中，所述客户业务服务器和所述系统交换机之间还通过客户交换机相连；所述方法还包括：
    所述POP服务器为接收到的所述数据报文添加内层虚拟局域网标识，并将添加了外层虚拟局域网标识和内层虚拟局域网标识的数据报文发送至相连的系统交换机；
    所述客户交换机在接收到相连的系统交换机发来的剥离了外层虚拟局域网标识的数据报文后，若接收到的所述数据报文中还携带内层虚拟局域网标识，所述客户交换机将接收到的所述数据报文剥离内层虚拟局域网标识后，提供给相连的客户业务服务器。
  13. 一种网络设备，所述网络设备中包含与二层隧道相连的端口，其中，若所述端口为指定端口，将所述指定端口的初始状态置为阻塞状态，并且若所述指定端口通过二层隧道与根端口相连，将所述指定端口的阻塞状态调整为转发状态；若所述端口为根端口，将所述根端口的初始状态置为转发状态，并通过所述根端口向对侧的端口发送用于表征根端口身份的通知报文；若所述端口为除所述指定端口和所述根端口之外的其它端口，将所述其它端口的初始状态置为阻塞状态。
PCT/CN2020/074970 2019-09-04 2020-02-12 一种端口状态的配置方法及网络设备 WO2021042674A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20861929.6A EP4009592A1 (en) 2019-09-04 2020-02-12 Method for configuring port state and network device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910831977.0A CN110719219B (zh) 2019-09-04 2019-09-04 一种端口状态的配置方法及网络设备
CN201910831977.0 2019-09-04

Publications (1)

Publication Number Publication Date
WO2021042674A1 true WO2021042674A1 (zh) 2021-03-11

Family

ID=69209603

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/074970 WO2021042674A1 (zh) 2019-09-04 2020-02-12 一种端口状态的配置方法及网络设备

Country Status (3)

Country Link
EP (1) EP4009592A1 (zh)
CN (1) CN110719219B (zh)
WO (1) WO2021042674A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110719219B (zh) * 2019-09-04 2021-09-14 厦门网宿有限公司 一种端口状态的配置方法及网络设备
CN111585797B (zh) * 2020-04-27 2023-04-07 深圳震有科技股份有限公司 以太网链路切换方法、装置、设备及计算机可读存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030016624A1 (en) * 1998-05-04 2003-01-23 Bare Ballard C. Path recovery on failure in load balancing switch protocols
CN102143057A (zh) * 2010-12-14 2011-08-03 华为数字技术有限公司 一种生成树协议中阻塞端口指定方法和装置
CN102571520A (zh) * 2011-12-31 2012-07-11 北京格林伟迪科技有限公司 一种在环网中实现快速收敛的方法
CN107294856A (zh) * 2016-03-31 2017-10-24 华为技术有限公司 确定拓扑变化的方法、设备及系统
CN110120891A (zh) * 2019-05-13 2019-08-13 北京东土军悦科技有限公司 组网中阻止链路回切的方法、装置、网络设备及存储介质
CN110719219A (zh) * 2019-09-04 2020-01-21 厦门网宿有限公司 一种端口状态的配置方法及网络设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6987740B1 (en) * 2000-09-11 2006-01-17 Cisco Technology, Inc. STP root guard
US7076594B2 (en) * 2000-12-22 2006-07-11 Cisco Technology, Inc. Apparatus and method for preventing one way connectivity loops in a computer network
CN101110820B (zh) * 2007-09-04 2011-04-20 杭州华三通信技术有限公司 一种处理生成树协议报文的方法和交换机
CN101771570B (zh) * 2010-02-08 2012-05-23 杭州华三通信技术有限公司 一种状态切换方法及装置
CN108512751B (zh) * 2017-02-28 2021-02-23 华为技术有限公司 一种端口状态处理方法以及网络设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030016624A1 (en) * 1998-05-04 2003-01-23 Bare Ballard C. Path recovery on failure in load balancing switch protocols
CN102143057A (zh) * 2010-12-14 2011-08-03 华为数字技术有限公司 一种生成树协议中阻塞端口指定方法和装置
CN102571520A (zh) * 2011-12-31 2012-07-11 北京格林伟迪科技有限公司 一种在环网中实现快速收敛的方法
CN107294856A (zh) * 2016-03-31 2017-10-24 华为技术有限公司 确定拓扑变化的方法、设备及系统
CN110120891A (zh) * 2019-05-13 2019-08-13 北京东土军悦科技有限公司 组网中阻止链路回切的方法、装置、网络设备及存储介质
CN110719219A (zh) * 2019-09-04 2020-01-21 厦门网宿有限公司 一种端口状态的配置方法及网络设备

Also Published As

Publication number Publication date
CN110719219A (zh) 2020-01-21
CN110719219B (zh) 2021-09-14
EP4009592A1 (en) 2022-06-08

Similar Documents

Publication Publication Date Title
EP3525405B1 (en) Packet sending method and network device
US7751329B2 (en) Providing an abstraction layer in a cluster switch that includes plural switches
US10097372B2 (en) Method for resource optimized network virtualization overlay transport in virtualized data center environments
JP4778062B2 (ja) プロバイダ・リンク状態ブリッジング
US8694664B2 (en) Active-active multi-homing support for overlay transport protocol
US8059638B2 (en) Inter-node link aggregation system and method
US8817593B2 (en) Method and apparatus providing failover for a point to point tunnel for wireless local area network split-plane environments
US11329845B2 (en) Port mirroring over EVPN VXLAN
EP2533475B1 (en) Method and system for host route reachability in packet transport network access ring
US8861338B2 (en) Routed split multilink trunking for IPv6
EP3641241A1 (en) Node protection for bum traffic for multi-homed node failure
EP4016928A1 (en) Layer 2 leased line network system, configuration method, and device
EP3465982B1 (en) Bidirectional multicasting over virtual port channel
US11601335B2 (en) Methods and systems for neighbor-acknowledged graceful insertion/removal protocol
CN112422307A (zh) Evpn和vpls共存双活的方法、设备及系统
US8612626B2 (en) Group member detection among nodes of a network
WO2021042674A1 (zh) 一种端口状态的配置方法及网络设备
WO2021042675A1 (zh) 一种二层专线网络系统及配置方法
US11025708B1 (en) Group load balancing for virtual router redundancy
CN114205293B (zh) 路径确定方法、装置、电子设备及存储介质
WO2024093306A1 (zh) 通信方法及装置

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: 20861929

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020861929

Country of ref document: EP

Effective date: 20220302