CN112714006B - Link fault state notification method, device, equipment and medium - Google Patents

Link fault state notification method, device, equipment and medium Download PDF

Info

Publication number
CN112714006B
CN112714006B CN201911018840.XA CN201911018840A CN112714006B CN 112714006 B CN112714006 B CN 112714006B CN 201911018840 A CN201911018840 A CN 201911018840A CN 112714006 B CN112714006 B CN 112714006B
Authority
CN
China
Prior art keywords
network
target
equipment
vxlan
vtep
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
CN201911018840.XA
Other languages
Chinese (zh)
Other versions
CN112714006A (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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201911018840.XA priority Critical patent/CN112714006B/en
Publication of CN112714006A publication Critical patent/CN112714006A/en
Application granted granted Critical
Publication of CN112714006B publication Critical patent/CN112714006B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/06—Management of faults, events, alarms or notifications
    • 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]

Landscapes

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

Abstract

The application provides a link fault state notification method, a device, equipment and a medium. The method is applied to target equipment and comprises the following steps: when the link fault state changes, determining the type of a target network in the mixed networking to which the changed fault state belongs; determining other network types except the target network type in the hybrid networking, and correspondingly notifying opposite terminal equipment matched with the other network types of link fault state change according to an operation maintenance management (OAM) detection mechanism corresponding to the other network types; wherein the hybrid networking comprises at least two network types; the opposite terminal equipment comprises at least two opposite terminal equipment, and the network types between the target equipment and different opposite terminal equipment are different.

Description

Link fault state notification method, device, equipment and medium
Technical Field
The present application relates to the field of communications, and in particular, to a method, an apparatus, a device, and a medium for notifying a link failure state.
Background
VXLAN (Virtual Extensible Local Area Network, virtual expansion local area network) is a technology for solving a series of problems in cloud computing era virtualization, and adopts a MAC-in-UDP message encapsulation mode to encapsulate a two-Layer (Layer 2) message by using a three-Layer protocol, so that the expansion of a two-Layer network in a three-Layer range can be realized. With the continuous popularization and application of VXLAN, the hybrid networking of VXLAN and the existing common Ethernet (ETH for short) has become more common. However, in the prior art, there is no fault notification association between VXLAN OAM (Operation Administration AND MAINTENANCE, operation maintenance management) and common ETH OAM, so that a fault cannot be transmitted across a network during hybrid networking, and thus, end-to-end fault detection of hybrid networking cannot be achieved.
Disclosure of Invention
The application provides a link fault state notification method, a device, equipment and a medium, which are used for realizing intercommunication among OAM detection mechanisms of different types of networks in a hybrid networking, and further realizing end-to-end fault detection of the hybrid networking.
In a first aspect, an embodiment of the present application provides a link failure state notification method, which is applied to a target device, including:
when the link fault state changes, determining the type of a target network in the mixed networking to which the changed fault state belongs;
determining other network types except the target network type in the hybrid networking, and correspondingly notifying opposite terminal equipment matched with the other network types of link fault state change according to an operation maintenance management (OAM) detection mechanism corresponding to the other network types;
wherein the hybrid networking comprises at least two network types; the opposite terminal equipment comprises at least two opposite terminal equipment, and the network types between the target equipment and the opposite terminal equipment of different types are different.
In a second aspect, an embodiment of the present application provides a link failure state notification apparatus, which is applied to a target device, including:
The system comprises a target network type determining module which is used for determining the target network type in the mixed networking which is the fault state when the fault state of the link is changed;
A fault state notification module, configured to determine other network types in the hybrid network except for the target network type, and correspondingly notify, according to an operation maintenance management OAM detection mechanism corresponding to the other network types, a peer device matching the other network types that a link fault state changes;
wherein the hybrid networking comprises at least two network types; the opposite terminal equipment comprises at least two opposite terminal equipment, and the network types between the target equipment and the opposite terminal equipment of different types are different.
In a third aspect, an embodiment of the present application provides a network device, including: one or more processors; a storage means for storing one or more programs; the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the link failure state advertisement method as described in any embodiment of the present application.
In a fourth aspect, an embodiment of the present application provides a storage medium storing a computer program, where the computer program is executed by a processor to implement a link failure state notification method according to any embodiment of the present application.
In the technical solution provided in this embodiment, the hybrid networking includes at least two network types, where the target device is connected to different types of opposite end devices through different types of networks, and when the target device detects that the link failure state of the target device changes, the target network type to which the changed failure state belongs is determined, and according to OAM detection mechanisms of other network types except the target network type, the opposite end device matched with the other network types is correspondingly notified that the link failure state changes, so as to implement interworking between OAM detection mechanisms of different types of networks in the hybrid networking, and further implement end-to-end failure detection of the hybrid networking.
With respect to the above embodiments and other aspects of the application and implementations thereof, further description is provided in the accompanying drawings, detailed description and claims.
Drawings
Fig. 1 is a schematic flow chart of a link failure state notification method provided by the present application;
fig. 2 is a schematic diagram of a VXLAN hybrid networking model according to the present application;
fig. 3 is a schematic diagram of a VXLAN hybrid networking example provided in the present application;
Fig. 4 is a schematic diagram of a format of a VXLAN message provided by the present application;
Fig. 5 is a schematic structural diagram of a link failure state notification device according to the present application;
fig. 6 is a schematic structural diagram of a network device according to the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, embodiments of the present application will be described in detail hereinafter with reference to the accompanying drawings. It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be arbitrarily combined with each other.
In an exemplary embodiment, fig. 1 is a schematic flow chart of a link failure state notification method provided in the present application. The method is suitable for the situation that no fault notification association exists between OAMs corresponding to different network types in the hybrid networking, so that faults cannot be transmitted across networks in the hybrid networking scene. The method may be performed by a link failure state notification device provided by the present application, which may be implemented in software and/or hardware and integrated in a network device.
The mixed networking comprises at least two network types, the OAM detection mechanisms of different types of network deployment can be different or the same, and no fault notification association exists between the OAMs of different types of network deployment.
As shown in fig. 1, the link failure state notification method provided by the present application is applied to a target device, and includes:
And S110, when the link fault state changes, determining the type of the target network in the mixed networking to which the changed fault state belongs.
In an example, it is assumed that three network types, a network, B network, and C network, are included in the hybrid networking, and correspondingly, a network OAM, B network OAM, and C network OAM are deployed, where the a network OAM, B network OAM, and C network OAM do not have any failure notification association with each other.
The target device is an intermediate device in the hybrid network that is in network connection with at least two devices, and the device that is in network connection with the target device is referred to herein as a peer device. The opposite terminal equipment corresponding to the target equipment comprises at least two opposite terminal equipment, and the network types between the target equipment and the opposite terminal equipment of different types are different. For example, the opposite terminal device includes an opposite terminal a device, an opposite terminal B device, and an opposite terminal C device, where an a network is between the target device and the opposite terminal a device, a B network is between the target device and the opposite terminal B device, and a C network is between the target device and the opposite terminal C device.
The link failure state change detected by the target device includes a failure occurrence and a failure cancellation, wherein the failure occurrence includes a transmission failure occurrence and a reception failure occurrence, and the failure cancellation includes a transmission failure cancellation and a reception failure cancellation. Specifically, the fault state change is also related to the network type, and in the following previous examples, the fault occurrence includes: the method comprises the steps of A network side sending fault occurrence, A network side receiving fault occurrence, B network side sending fault occurrence, B network side receiving fault occurrence, C network side sending fault occurrence and C network side receiving fault occurrence, wherein fault elimination comprises the following steps: the method comprises the steps of A network side sending fault elimination, A network side receiving fault elimination, B network side sending fault elimination, B network side receiving fault elimination, C network side sending fault elimination and C network side receiving fault elimination. It should be noted that, the specific fault name is determined by the OAM detection mechanism of the network to which the fault belongs, and can be attributed to both a transmission fault and a reception fault.
When the target equipment detects that the link fault state changes, the target network type in the mixed networking to which the changed fault state belongs is determined first. For example, the target device detects that the sending error of the a network side is detected, that is, the sending failure of the a network side occurs, and the type of the target network to which the changed failure state belongs is the a network.
S120, determining other network types except the target network type in the hybrid networking, and correspondingly notifying opposite terminal equipment matched with the other network types of the change of the link fault state according to an OAM detection mechanism corresponding to the other network types.
According to the OAM detection mechanism of a certain network, the change of the link fault state is announced to the opposite terminal equipment under the network, namely, the change of the link fault state is announced to the opposite terminal equipment under the network by using an announcement mode determined by the OAM detection mechanism of the network.
Continuing the previous example, the other network types except the target network type A network in the hybrid networking are a B network and a C network. Furthermore, according to the B network OAM detection mechanism, the opposite terminal B equipment is informed that the link fault state changes, namely the opposite terminal B equipment is informed of the occurrence of faults in the sending direction, and the mode of informing the opposite terminal B equipment of the occurrence of faults in the sending direction is determined by the B network OAM detection mechanism; meanwhile, the C network OAM detection mechanism informs the opposite terminal C equipment that the link fault state changes, namely informs the opposite terminal C equipment that the sending direction fails, and the mode of informing the opposite terminal C equipment that the sending direction fails is determined by the C network OAM detection mechanism.
If the target equipment detects that the A network side of the target equipment is successfully transmitted, namely, the A network side transmits fault elimination, the target equipment notifies the opposite terminal B equipment that the link fault state changes according to a B network OAM detection mechanism, namely, notifies the opposite terminal B equipment of transmitting direction fault elimination, and notifies the opposite terminal B equipment of transmitting direction fault elimination mode to be determined by the B network OAM detection mechanism; and simultaneously, notifying the opposite terminal C equipment that the link fault state changes according to the C network OAM detection mechanism, namely notifying the opposite terminal C equipment of transmitting direction fault elimination, wherein the transmitting direction fault elimination notifying mode of the opposite terminal C equipment is determined by the C network OAM detection mechanism.
The fault occurrence and the fault elimination notification method are the same, and the difference is only that the notification content is different, and the fault occurrence is explained below, so that the fault elimination is not repeated.
Continuing the previous example, if the opposite terminal B device or the opposite terminal C device is an intermediate device of the same type as the target device, and is connected with the opposite terminal device of different types through the network of different types, the opposite terminal B device or the opposite terminal C device is correspondingly re-used as the target device, and the notification of the changed link failure state is performed, so as to notify the end device of the hybrid network, and further realize the end-to-end failure detection of the hybrid network.
In the technical solution provided in this embodiment, the hybrid networking includes at least two network types, where the target device is connected to different types of opposite end devices through different types of networks, and when the target device detects that the link failure state of the target device changes, the target network type to which the changed failure state belongs is determined, and according to OAM detection mechanisms of other network types except the target network type, the opposite end device matched with the other network types is correspondingly notified that the link failure state changes, so as to implement interworking between OAM detection mechanisms of different types of networks in the hybrid networking, and further implement end-to-end failure detection of the hybrid networking.
In an example, the hybrid network includes two network types, specifically, the hybrid network includes an ethernet network and a VXLAN, the target device is a target VTEP (VXLAN Tunnel End Point, virtual extended local area network tunnel endpoint) device, and the peer device corresponding to the target device includes a peer Layer 2 device and a peer VTEP device.
The network between the target VTEP equipment and the opposite terminal two-layer equipment is Ethernet, and the Ethernet deploys an Ethernet OAM detection mechanism; the network between the target VTEP equipment and the opposite-end VTEP equipment is VXLAN, and the VXLAN deploys a VXLAN OAM detection mechanism.
The VTEP device refers to an edge device of VXLAN, where VXLAN related processing is performed on the VTEP, for example, identifying the VXLAN to which the ethernet data frame belongs, performing two-layer forwarding, encapsulating/decapsulating on the data frame based on the VXLAN, and so on. The two-Layer device refers to a generic term for all devices supporting Layer 2OAM detection.
As shown in fig. 2, the ethernet is provided between the two-layer device 1 and the VTEP device 1, the VXLAN is provided between the VTEP device 1 and the VTEP device 2, and the ethernet is provided between the two-layer device 2 and the VTEP device 2. Assuming VETP in fig. 2 as the target VTEP device, the two-layer device 1 is an opposite-end two-layer device corresponding to the target VTEP device, and VETP is an opposite-end VTEP device corresponding to the target VTEP device.
For VTEP, there are four faults, respectively: an ethernet side reception failure (affecting VTEP to receive a message from the ethernet side), an ethernet side transmission failure (affecting VTEP to transmit a message to the ethernet side), a VXLAN side reception failure (affecting VTEP to receive a message from the VXLAN tunnel), and a VXLAN side transmission failure (affecting VTEP to transmit a message through the VXLAN tunnel).
In order to enable end-to-end fault detection between the two-tier device 1 and the two-tier device 2, OAM detection mechanisms are laid out on the ethernet and VXLAN, respectively.
The ethernet link between the two-layer device and the VTEP device deploys an ethernet OAM detection mechanism, where the deployed ethernet OAM detection mechanism may be any existing standard detection mechanism or a custom detection mechanism, as long as an ethernet side receiving failure and an ethernet side sending failure can be detected on the VTEP. The specific fault type detected by the ethernet OAM detection mechanism is determined by the deployed OAM detection mechanism, but whatever detection mechanism is used, the link fault type can be generalized to an ethernet side receiving fault and an ethernet side transmitting fault.
And a VXLAN OAM detection mechanism is deployed between the VTEP devices, wherein the deployed VXLAN OAM detection mechanism can be any existing general detection mechanism or custom detection mechanism as long as the VXLAN side receiving fault and the VXLAN side sending fault can be detected on the VTEP. The specific fault type detected by the VXLAN OAM detection mechanism is determined by the deployed OAM detection mechanism, but whatever detection mechanism is used, the link fault type can be attributed to VXLAN side reception faults and VXLAN side transmission faults.
The fault intercommunication between the Ethernet OAM and the VXLAN OAM is to notify the fault detected by the Ethernet OAM to the VXLAN and notify the fault detected by the VXLAN to the Ethernet, so that the end-to-end fault detection is realized.
In an example, when a link failure state changes, determining a target network type in a hybrid network to which the changed failure state belongs includes:
when the link fault state sent by the Ethernet side or received by the Ethernet side of the target VTEP equipment changes, determining the type of the target network in the mixed networking to which the changed fault state belongs as Ethernet.
Correspondingly, according to an operation maintenance management (OAM) detection mechanism corresponding to other network types, a corresponding notification of a link fault state change to a peer device matched with the other network types is performed, specifically:
According to the VXLAN OAM detection mechanism, the opposite-end VTEP equipment is informed of the change of the link fault state in the sending direction or the receiving direction, so that the opposite-end VTEP equipment can inform the target two-layer equipment connected with the opposite-end VTEP equipment through the Ethernet of the change of the link fault state after receiving the fault change information and detecting the change of the link fault state.
In an example, referring to fig. 2, assume that VTEP device 1 is a target VTEP device, VTEP device 2 is a peer VTEP device, and two-layer device 1 is a peer two-layer device, and two-layer device 2 is a target two-layer device. If the VTEP device 1 detects that the ethernet side receives the failure, it indicates that the capability of the VTEP device 1 to receive the message from the two-layer device 1 is affected, and the type of the target network to which the failure belongs is ethernet. Further, the other network type is VXLAN, and the VTEP device 1 needs to notify the VTEP device 2 under VXLAN that the link failure state has changed, that is, the VTEP device 1 needs to notify the VTEP device 2 of the failure information. The VTEP device 1 notifies the VTEP device 2 of the failure in the reception direction in the failure notification manner determined by the VXLAN OAM detection mechanism.
After receiving the failure information, the VTEP device 2 detects the link failure state, i.e. detects that the VXLAN side thereof receives the failure, and further needs to notify the two-layer device 2 communicating with the VTEP device via the ethernet of the failure information. The VTEP device 2 notifies the two-layer device 2 that the receiving direction has a fault in a fault notification manner determined by the ethernet OAM detection mechanism.
So far, in the case that the VTEP device 1 detects that the ethernet-side reception failure thereof occurs, the end-to-end failure detection of the two-layer device 1 to the two-layer device 2 is realized. It should be noted that, based on the current ethernet OAM detection mechanism, when the VTEP device 1 detects that the ethernet side thereof receives the fault, the two-layer device 1 may learn the fault information, and no fault is required to be notified to the two-layer device 1.
In a specific example, as shown in fig. 3, the VTEP device 1 and the VTEP device 2 are respectively connected to a two-layer device, the VTEP device 1 and the VTEP device 2 communicate through VXLAN tunnels, the VTEP device 1 and the two-layer device 1 communicate through ethernet, the VTEP device 2 and the two-layer device 2 communicate through ethernet, and the ethernet side and the VXLAN side respectively deploy different OAM detection mechanisms.
The OAM detection mechanism deployed on the Ethernet side adopts 802.1ag or Y.1731 protocol to respectively create MEPs (MAINTENANCE END Point, maintenance domain terminal nodes) on the two-layer equipment and the VTEP. The requirements regarding how VXLAN and MEP are deployed are standard protocols are not described in detail herein.
Based on the OAM detection mechanism of the ethernet side, connectivity between the VTEP device and the two-layer device is detected by sending a CCM (Continuity CHECK MESSAGE) packet between the VTEP device and the two-layer device. If the VTEP device 1 cannot receive CCM packets from the ethernet side within a 3.5-fold (3.5-fold is 802.1ag or y.1731 protocol) transmission period interval, a remote loss alarm occurs, confirming that an ethernet side reception failure is detected.
Since the ethernet-side reception failure on the VTEP device 1 is detected by the VTEP device 1, the VTEP device 1 needs to notify the VTEP device 2 of the failure of the reception direction, specifically, the VTEP device 1 notifies the VTEP device 2 of the failure of the reception direction according to the manner determined by the VXLAN OAM detection mechanism.
In the OAM detection mechanism deployed on VXLAN, when no notification of reception failure occurrence or reception failure removal or transmission failure occurrence or transmission failure removal message is given, a custom message manner may be adopted to notify of reception error message.
In an example, the link failure state of the sending direction or the receiving direction may be notified to the opposite VTEP device according to the VXLAN OAM detection mechanism, specifically:
And generating a custom message for indicating the change of the link fault state of notifying the sending direction or the receiving direction to the opposite-end VTEP equipment according to the custom VXLAN OAM detection mechanism, and sending the custom message to the opposite-end VTEP equipment.
In an example, a set flag bit of a reserved field in a header field of the custom message is used to indicate a fault state, where the fault state includes occurrence and elimination of a reception fault and occurrence and elimination of a transmission fault.
Four messages are newly defined in the VXLAN for informing the opposite terminal VTEP of receiving or transmitting faults or fault elimination.
RFC7348 specifies that the format of VXLAN messages is as shown in fig. 4, with VXLAN headers (VXLAN headers) being newly defined for the VXLAN protocol, comprising 8 bytes. Wherein, in VXLAN Header:
The flag bit (Flags) includes 8 bits, and when the "I" bit is 1, it indicates that the VXLAN identification (VXLAN ID (VNI)) in the VXLAN header is valid, and when the "I" bit is 0, it indicates that the VXLAN identification is invalid, and the remaining "R" bits remain unused, and are set to 0;
VXLAN identification (VXLAN ID (VNI)) includes 24 bits for identifying a single VXLAN;
There are two Reserved bits (Reserved), one comprising 24 bits and the other comprising 8 bits.
Specifically, forward or backward errors are communicated by utilizing the Reserved field in the VXLAN Header field.
Optionally, using VXLAN to identify the remaining bits of the following 8 bits, assuming that the remaining bits of the 8 bits are XXFI XXRI, where "I" bit is 1, indicating that a fault occurs and "I" bit is 0, indicating that the fault is eliminated; when the "F" bit is 1, it indicates a reception failure, and when the "R" bit is 1, it indicates a transmission failure; "X" indicates that the reserved bits are unused. For example: 00000011 indicates occurrence of a transmission failure, and 00000010 indicates transmission failure cancellation.
When the receiving or transmitting fault is identified in the custom message or the fault is eliminated, the content of the Original L2 Frame (Original L2 Frame) in the message is negligible.
After receiving the information for indicating the occurrence of the reception failure, the VTEP device 2 detects whether the failure state of the VTEP device 2 changes, so that the occurrence of the reception failure of the VXLAN side of the VTEP device can be detected, and further the VTEP device 2 notifies the two-layer device 2 of the failure information according to the manner determined by the ethernet OAM detection mechanism, specifically, the MEP22 on the VTEP device 2 stops sending the CCM message to the two-layer device 2. Thus, the end-to-end fault detection of the two-layer equipment 1 to the two-layer equipment 2 is realized.
It is worth noting that since the VXLAN side reception failure on the VTEP device 2 is notified by the VTEP device 1 sending a message, the VTEP device 2 does not need to notify the VTEP device 1 of the failure information.
In an example, referring to fig. 2, assume that VTEP device 1 is a target VTEP device, VTEP device 2 is a peer VTEP device, and two-layer device 1 is a peer two-layer device, and two-layer device 2 is a target two-layer device. If the VTEP device 1 detects that the ethernet side transmission failure occurs, it indicates that the capability of the VTEP device 1 to transmit a message to the ethernet will be affected, and the type of the target network to which the failure occurs is ethernet. Further, the other network type is VXLAN, and the VTEP device 1 needs to notify the VTEP device 2 under VXLAN that the link failure state has changed, that is, the VTEP device 1 needs to notify the VTEP device 2 of the failure information. The VTEP device 1 notifies the VTEP device 2 that the transmission direction has failed in a failure notification manner determined by the VXLAN OAM detection mechanism.
After receiving the failure information, the VTEP device 2 detects the link failure state, i.e. detects that the VXLAN side thereof has failed, and then needs to notify the two-layer device 2 communicating with the VTEP device via the ethernet network of the failure information. The VTEP device 2 notifies the two-layer device 2 of the occurrence of a failure in the transmission direction in a failure notification manner determined by the ethernet OAM detection mechanism.
Up to this point, in the case where the VTEP device 1 detects that its ethernet-side transmission failure occurs, the end-to-end failure detection of the two-layer device 1 to the two-layer device 2 is realized. It should be noted that, based on the current ethernet OAM detection mechanism, when the VTEP device 1 detects that the ethernet side transmission failure occurs, the two-layer device 1 may learn the failure information, and no further notification of the failure to the two-layer device 1 is required.
In a specific example, as shown in fig. 3, the VTEP device 1 and the VTEP device 2 are respectively connected to a two-layer device, the VTEP device 1 and the VTEP device 2 communicate through VXLAN tunnels, the VTEP device 1 and the two-layer device 1 communicate through ethernet, the VTEP device 2 and the two-layer device 2 communicate through ethernet, and the ethernet side and the VXLAN side respectively deploy different OAM detection mechanisms.
The OAM detection mechanism deployed on the Ethernet side adopts 802.1ag or Y.1731 protocols to respectively create MEPs on the two-layer equipment and the VTEP. The requirements regarding how VXLAN and MEP are deployed are standard protocols are not described in detail herein.
Based on an OAM detection mechanism at the Ethernet side, connectivity between the VTEP device and the two-layer device is detected by sending CCM packets between the VTEP device and the two-layer device. If the RDI (Remote Defect Indicator, remote failure indication identity) flag of the CCM message received by the VTEP device 1 is 1, then the ethernet side transmission failure is detected.
Since the ethernet-side transmission failure on the VTEP device 1 is detected by the VTEP device 1, the VTEP device 1 needs to notify the VTEP device 2 that the transmission direction is failed, specifically, the VTEP device 1 notifies the VTEP device 2 that the transmission direction is failed according to the manner determined by the VXLAN OAM detection mechanism.
In the OAM detection mechanism deployed on VXLAN, when no notification of reception failure occurrence or reception failure removal or transmission failure occurrence or transmission failure removal message is given, a custom message manner may be adopted to notify of transmission error message. Referring specifically to the new definition of four messages within VXLAN.
When the receiving or transmitting fault is identified in the custom message or the fault is eliminated, the content of the Original L2 Frame (Original L2 Frame) in the message is negligible.
After receiving the information for indicating the occurrence of the transmission failure, the VTEP device 2 detects whether the failure state of the VTEP device 2 changes, so that the occurrence of the transmission failure at the VXLAN side of the VTEP device can be detected, and further the VTEP device 2 notifies the two-layer device 2 of the failure information according to the manner determined by the ethernet OAM detection mechanism, specifically, the MEP22 on the VTEP device 2 sends the RDI flag position 1 of the CCM message to the two-layer device 2. Thus, the end-to-end fault detection of the two-layer equipment 1 to the two-layer equipment 2 is realized.
It should be noted that, since the VXLAN-side transmission failure on the VTEP device 2 is notified by the VTEP device 1 transmitting a message, the VTEP device 2 does not need to notify the VTEP device 1 of the failure information.
In an example, when the link failure state changes, the target network type in the hybrid network to which the changed failure state belongs may be determined, specifically:
when the link fault state sent by the VXLAN side of the target VTEP equipment or received by the VXLAN side is changed, the target network type in the mixed networking to which the changed fault state belongs is determined to be VXLAN.
Correspondingly, according to an operation maintenance management (OAM) detection mechanism corresponding to the other network type, a change in a link failure state is correspondingly notified to a peer device matched with the other network type, specifically:
And according to an Ethernet OAM detection mechanism, notifying the opposite terminal two-layer equipment that the link fault state of the transmitting direction or the receiving direction is changed.
When the target VTEP device detects that the transmission failure of the VXLAN side or the reception failure of the VXLAN side occurs, the type of the target network to which the occurrence belongs is determined to be VXLAN. Furthermore, other network types are ethernet, and the target VTEP device needs to notify the opposite-end two-layer device under the ethernet that the sending direction or the receiving direction has a fault according to the fault notification manner determined by the ethernet OAM detection mechanism.
Assuming that, based on the OAM detection mechanism of VXLAN deployment, when the target VTEP device detects that a VXLAN side transmission failure or VXLAN side reception failure occurs, the opposite-end VTEP device can learn that the failure occurs, and the target VTEP device does not need to notify the opposite-end VTEP device of the failure. Furthermore, the peer VTEP device may correspondingly detect that a receiving failure occurs on its VXLAN side or that a transmitting failure occurs on the VXLAN side, and notify the other two-layer device in communication with the peer VTEP device via ethernet of the failure information, so as to implement end-to-end failure detection.
Because the existing VXLAN OAM detection mechanism has no relevant standard, when the target VTEP equipment detects that the VXLAN side transmission fault or the VXLAN side receiving fault occurs, the target VTEP equipment can carry out fault notification to the opposite-end VTEP equipment so as to enable the opposite-end VTEP equipment to know that the corresponding fault occurs.
Optionally, according to an OAM detection mechanism corresponding to the other network type, notifying, correspondingly, to a peer device matching the other network type, that a link failure state changes, and further including:
According to a VXLAN OAM detection mechanism, the opposite-end VTEP equipment is informed of the change of the link fault state in the sending direction or the receiving direction, so that the opposite-end VTEP equipment can inform the target two-layer equipment connected with the opposite-end VTEP equipment through the Ethernet of the change of the link fault state after receiving the fault change information and detecting the change of the link fault state.
The target VTEP device needs to notify the opposite-end VTEP device under the VXLAN that the sending direction or the receiving direction has a fault according to the fault notification manner determined by the VXLAN OAM detection mechanism.
In an example, referring to fig. 2, assume that VTEP device 1 is a target VTEP device, VTEP device 2 is a peer VTEP device, and two-layer device 1 is a peer two-layer device, and two-layer device 2 is a target two-layer device. If the VTEP device 1 detects that a VXLAN-side reception failure occurs, it indicates that the capability of the VTEP device 1 to receive a message from the ethernet network where the two-layer device 2 is located is affected, and the type of the target network to which the failure occurs is VXLAN. Further, the other network type is ethernet, and the VTEP device 1 needs to notify the two-layer device 1 under the ethernet that the link failure state changes, that is, the VTEP device 1 needs to notify the two-layer device 1 of the failure information. The VTEP device 1 notifies the two-layer device 1 that the receiving direction has a fault in a fault notification manner determined by the ethernet OAM detection mechanism.
The VTEP device 1 also needs to notify the VTEP device 2 under VXLAN that the link failure state has changed, i.e. the VTEP device 1 needs to notify the VTEP device 2 of the failure information. The VTEP device 1 notifies the VTEP device 2 of the failure in the reception direction in the failure notification manner determined by the VXLAN OAM detection mechanism.
After receiving the fault information, the VTEP device 2 detects the link fault state, that is, it can detect that the VXLAN side sends a fault, and then notifies the two-layer device 2 of the fault information, and the VTEP device 2 notifies the two-layer device 2 of the fault in the sending direction by using the fault notification mode determined by the ethernet OAM detection mechanism. In this case, since the VTEP device 2 detects that the VXLAN-side transmission failure has occurred as notified by the VTEP device 1, the VTEP device 2 does not need to notify the VTEP device 1 of the failure information.
In a specific example, as shown in fig. 3, the VTEP device 1 and the VTEP device 2 are respectively connected to a two-layer device, the VTEP device 1 and the VTEP device 2 communicate through VXLAN tunnels, the VTEP device 1 and the two-layer device 1 communicate through ethernet, the VTEP device 2 and the two-layer device 2 communicate through ethernet, and the ethernet side and the VXLAN side respectively deploy different OAM detection mechanisms.
The OAM detection mechanism deployed on the Ethernet side adopts 802.1ag or Y.1731 protocols to respectively create MEPs on the two-layer equipment and the VTEP. The requirements regarding how VXLAN and MEP are deployed are standard protocols are not described in detail herein.
Since VXLAN OAM detection mechanisms currently have no relevant standard, here, description is made with reference to ethernet OAM detection mechanism custom OAM detection, for example, connectivity between VTEP devices is detected by continuously sending echo-request (reply-request) messages between the VTEP devices and two-layer devices, the VTEP devices send echo-request messages to each other with a fixed period, and if the sending period is 3.5 times (3.5 times is an example, not specifically limited), the VTEP device detects that the VXLAN side receives failure.
If the VTEP device 1 cannot receive the echo-request message sent by the VTEP device 2 within 3.5 times of the sending period interval, it confirms that the failure of receiving the VXLAN side is detected. The VTEP device 1 notifies the two-layer device 1 of the failure information according to the manner determined by the ethernet OAM detection mechanism, specifically, the MEP11 on the VTEP device 1 stops sending CCM packets to the two-layer device 1.
Since the VTEP device 1 detects that the occurrence of the VXLAN-side receiving failure is not notified by the VTEP device 2, the VTEP device 1 notifies the VTEP device 2 of the failure information, and notifies the VTEP device 2 itself of the VXLAN transmission failure, specifically, may refer to the foregoing example for the VXLAN custom message according to the custom VXLAN OAM detection mechanism.
After receiving the notification from the VTEP device 1, the VTEP device 2 detects that a transmission failure occurs on the VXLAN side, and notifies the two-layer device 2 of the failure information in a manner determined by the ethernet OAM detection mechanism, that is, notifies the two-layer device 2 of the transmission direction failure, specifically, the RDI flag position 1 in the CCM message sent by the MEP22 on the VTEP device 2 to the two-layer device 2. Thus, the end-to-end fault detection of the two-layer equipment 1 to the two-layer equipment 2 is realized.
In an example, referring to fig. 2, assume that VTEP device 1 is a target VTEP device, VTEP device 2 is a peer VTEP device, and two-layer device 1 is a peer two-layer device, and two-layer device 2 is a target two-layer device. If the VTEP device 1 detects that the VXLAN side transmission failure occurs, it indicates that the capability of the VTEP device 1 to transmit a message to the ethernet network where the two-layer device 2 is located is affected, and the type of the target network to which the failure occurs is VXLAN. Further, the other network type is ethernet, and the VTEP device 1 needs to notify the two-layer device 1 under the ethernet that the link failure state changes, that is, the VTEP device 1 needs to notify the two-layer device 1 of the failure information. The VTEP device 1 notifies the two-layer device 1 that the transmission direction has a fault in a fault notification manner determined by the ethernet OAM detection mechanism.
The VTEP device 1 also needs to notify the VTEP device 2 under VXLAN that the link failure state has changed, i.e. the VTEP device 1 needs to notify the VTEP device 2 of the failure information. The VTEP device 1 notifies the VTEP device 2 that the transmission direction has failed in a failure notification manner determined by the VXLAN OAM detection mechanism.
After receiving the fault information, the VTEP device 2 detects the link fault state, that is, the occurrence of the fault on the VXLAN side can be detected, and then the fault information is notified to the two-layer device 2, and the fault notification mode determined by the ethernet OAM detection mechanism of the VTEP device 2 notifies the two-layer device 2 that the receiving direction has a fault. In this case, since the VTEP device 2 detects that the VXLAN side reception failure has occurred as notified by the VTEP device 1, the VTEP device 2 does not need to notify the VTEP device 1 of the failure information.
In a specific example, as shown in fig. 3, the VTEP device 1 and the VTEP device 2 are respectively connected to a two-layer device, the VTEP device 1 and the VTEP device 2 communicate through VXLAN tunnels, the VTEP device 1 and the two-layer device 1 communicate through ethernet, the VTEP device 2 and the two-layer device 2 communicate through ethernet, and the ethernet side and the VXLAN side respectively deploy different OAM detection mechanisms.
The OAM detection mechanism deployed on the Ethernet side adopts 802.1ag or Y.1731 protocols to respectively create MEPs on the two-layer equipment and the VTEP. The requirements regarding how VXLAN and MEP are deployed are standard protocols are not described in detail herein.
Since the VXLAN OAM detection mechanism is currently not defined by a relevant standard, a custom OAM detection is adopted to describe the detection mechanism, for example, the connectivity between the VTEP devices is detected by continuously sending an echo-request (reply-request) message between the VTEP devices, the echo-request message is mutually sent between the VTEP devices in a fixed period, if the echo-request message of the opposite terminal is not received in a 3.5-time (3.5-time is an example and is not specifically limited) sending period, the VTEP device detects that a fault occurs on the VXLAN side, and notifies the opposite terminal VTEP device of a sending fault at a certain reserved flag position 1 of the echo-request message sent by the local terminal, and detects that the VXLAN side sends the fault after the opposite terminal VTEP receives the echo-request message of the reserved flag position 1.
If the VTEP device 1 receives the echo-request message of the reserved flag position 1 sent by the VTEP device 2, a VXLAN side transmission failure is detected. The VTEP device 1 notifies the two-layer device 1 of the fault information according to the manner determined by the ethernet OAM detection mechanism, specifically, the MEP11 on the VTEP device 1 sends the CCM message of the RDI flag position 1 to the two-layer device 1.
Since the VTEP device 1 detects that the VXLAN side transmission failure is not notified by the VTEP device 2 transmitting the VXLAN custom message, the VTEP device 1 notifies the VTEP device 2 of the failure information, notifies the VTEP device 2 itself that there is a VXLAN side receiving failure, and specifically may refer to the foregoing example for the VXLAN custom message according to the custom message transmission determined by the custom VXLAN OAM detection mechanism, which is not described herein again.
After receiving the notification from the VTEP device 1, the VTEP device 2 detects that a receiving failure occurs at the VXLAN side, and notifies the layer two device 2 of the failure information in a manner determined by the ethernet OAM detection mechanism, that is, notifies the layer two device 2 of the receiving direction failure, specifically, the MEP22 on the VTEP device 2 stops sending CCM messages to the layer two device 2. Thus, the end-to-end fault detection of the two-layer equipment 1 to the two-layer equipment 2 is realized.
The embodiment also provides a link failure state notification device. Fig. 5 is a schematic structural diagram of a link failure state notification device provided by the present application, where the link failure state notification device is applied to a target device, may be implemented by software and/or hardware, and is integrated in a network device. As shown in fig. 5, the apparatus includes: a target network type determination module 210 to which the fault state belongs and a fault state notification module 220. The determining module 210 is configured to determine, when the link failure state changes, a target network type in the hybrid network to which the changed failure state belongs;
A fault state notification module 220, configured to determine other network types in the hybrid network except for the target network type, and notify, according to an operation maintenance management OAM detection mechanism corresponding to the other network types, a peer device matching the other network types of a link fault state change correspondingly;
wherein the hybrid networking comprises at least two network types; the opposite terminal equipment comprises at least two opposite terminal equipment, and the network types between the target equipment and the opposite terminal equipment of different types are different.
In the technical solution provided in this embodiment, the hybrid networking includes at least two network types, where the target device is connected to different types of opposite end devices through different types of networks, and when the target device detects that the link failure state of the target device changes, the target network type to which the changed failure state belongs is determined, and according to OAM detection mechanisms of other network types except the target network type, the opposite end device matched with the other network types is correspondingly notified that the link failure state changes, so as to implement interworking between OAM detection mechanisms of different types of networks in the hybrid networking, and further implement end-to-end failure detection of the hybrid networking.
In an example, the hybrid network includes ethernet and a virtual extended local area network VXLAN; the target equipment comprises target virtual expansion local area network tunnel endpoint VTEP equipment; the opposite terminal equipment comprises opposite terminal two-layer equipment and opposite terminal VTEP equipment;
The network between the target VTEP equipment and the opposite-end two-layer equipment is an Ethernet, and an Ethernet OAM detection mechanism is deployed in the Ethernet; the network between the target VTEP equipment and the opposite-end VTEP equipment is a VXLAN, and the VXLAN deploys a VXLAN OAM detection mechanism.
In an example, the failure state belongs to the target network type determining module 210, which is specifically configured to determine that the target network type in the hybrid network to which the changed failure state belongs is ethernet when the link failure state sent by the ethernet side of the target VTEP device or received by the ethernet side changes;
Correspondingly, the failure state notification module 220 is specifically configured to notify, according to a VXLAN OAM detection mechanism, the opposite terminal VTEP device that the link failure state in the sending direction or the receiving direction changes, so that the opposite terminal VTEP device notifies, after receiving the failure change information and detecting that the link failure state changes, the target two-layer device connected to the opposite terminal VTEP device through the ethernet network that the link failure state changes.
In an example, the failure state belongs to the target network type determining module 210, which is specifically configured to determine, when the failure state of the link sent by the VXLAN side of the target VTEP device or received by the VXLAN side changes, that the target network type in the hybrid network to which the changed failure state belongs is VXLAN;
correspondingly, the failure state notification module 220 is specifically configured to notify, according to an ethernet OAM detection mechanism, the peer two-layer device that a link failure state in a transmission direction or a reception direction changes.
In an example, the failure state notification module 220 is further specifically configured to notify, according to a VXLAN OAM detection mechanism, the peer VTEP device that a link failure state in a sending direction or a receiving direction changes, so that the peer VTEP device notifies, after receiving the failure change information and detecting that the link failure state changes, the peer VTEP device that the link failure state changes to a target two-layer device connected to the peer VTEP device through an ethernet network.
In an example, the failure state notification module 220 is further specifically configured to generate, according to a custom VXLAN OAM detection mechanism, a custom message for indicating that a link failure state that notifies the peer VTEP device of a sending direction or a receiving direction changes, and send the custom message to the peer VTEP device.
In an example, a set flag bit of a reserved field in a header field of the custom message is used to indicate a fault state, where the fault state includes occurrence and elimination of a reception fault and occurrence and elimination of a transmission fault.
The link failure state notification device provided in this embodiment is used to implement the link failure state notification method according to the embodiment of the present application, and the implementation principle and technical effects of the link failure state notification device provided in this embodiment are similar to those of the link failure state notification method according to the embodiment of the present application, and are not repeated herein.
The embodiment of the application provides a network device, and fig. 6 is a schematic structural diagram of the network device. As shown in fig. 6, the network device provided by the present application includes: one or more processors 310 and a storage 320; the device may have one or more processors 310, one processor 310 being illustrated in fig. 6; the storage 320 is used to store one or more programs; the one or more programs are executed by the one or more processors 310 to cause the one or more processors 310 to implement the link failure state advertisement method as described in embodiments of the present application.
The processor 310, the storage 320 in the device may be connected by a bus or other means, for example in fig. 6.
The storage 320, which is a computer readable storage medium, may be configured to store a software program, a computer executable program, and a module, which are program instructions/modules corresponding to the link failure state notification method according to the embodiments of the present application (for example, the target network type determining module 210 and the failure state notification module 220 to which the failure state in the link failure state notification device belongs). Storage 320 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, at least one application program required for a function; the storage data area may store data created according to the use of the device, etc. In addition, storage 320 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some examples, storage 320 may further include memory located remotely from processor 310, which may be connected to the device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The embodiment of the application also provides a storage medium, wherein the storage medium stores a computer program, and the computer program realizes the link fault state notification method according to any one of the embodiments of the application when being executed by a processor.
The link fault state notification method comprises the following steps:
when the link fault state changes, determining the type of a target network in the mixed networking to which the changed fault state belongs;
determining other network types except the target network type in the hybrid networking, and correspondingly notifying opposite terminal equipment matched with the other network types of link fault state change according to an operation maintenance management (OAM) detection mechanism corresponding to the other network types;
wherein the hybrid networking comprises at least two network types; the opposite terminal equipment comprises at least two opposite terminal equipment, and the network types between the target equipment and the opposite terminal equipment of different types are different.
Optionally, the computer executable instructions, when executed by the computer processor, may also be used to perform a link failure state notification method according to any of the embodiments of the present application.
From the above description of embodiments, it will be clear to a person skilled in the art that the present application may be implemented by means of software and necessary general purpose hardware, but of course also by means of hardware, although in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a FLASH Memory (FLASH), a hard disk, or an optical disk of a computer, etc., including several instructions for causing a device (which may be a personal computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present application.
It should be noted that, in the above embodiment of the link failure state notification device, each unit and module included are only divided according to the functional logic, but not limited to the above division, so long as the corresponding function can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the present invention.
The foregoing description is only exemplary embodiments of the application and is not intended to limit the scope of the application.
It will be appreciated by those skilled in the art that the term user terminal encompasses any suitable type of wireless user equipment, such as a mobile telephone, a portable data processing device, a portable web browser or a car mobile station.
In general, the various embodiments of the application may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
Embodiments of the application may be implemented by a data processor of a mobile device executing computer program instructions, e.g. in a processor entity, either in hardware, or in a combination of software and hardware. The computer program instructions may be assembly instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages.
The block diagrams of any of the logic flows in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on a memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read Only Memory (ROM), random Access Memory (RAM), optical storage devices and systems (digital versatile disk DVD or CD optical disk), etc. The computer readable medium may include a non-transitory storage medium. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general purpose computers, special purpose computers, microprocessors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), programmable logic devices (FGPAs), and processors based on a multi-core processor architecture.
The foregoing detailed description of exemplary embodiments of the application has been provided by way of exemplary and non-limiting examples. Various modifications and adaptations to the above embodiments may become apparent to those skilled in the art without departing from the scope of the application, which is defined in the accompanying drawings and claims. Accordingly, the proper scope of the application is to be determined according to the claims.

Claims (10)

1. A link failure state advertising method, applied to a target device, comprising:
when the link fault state changes, determining the type of a target network in the mixed networking to which the changed fault state belongs;
determining other network types except the target network type in the hybrid networking, and correspondingly notifying opposite terminal equipment matched with the other network types of link fault state change according to an operation maintenance management (OAM) detection mechanism corresponding to the other network types;
wherein the hybrid networking comprises at least two network types; the opposite terminal equipment comprises at least two opposite terminal equipment, and the network types between the target equipment and the opposite terminal equipment of different types are different.
2. The method of claim 1, wherein the hybrid networking comprises ethernet and virtual extended local area network VXLAN; the target equipment comprises target virtual expansion local area network tunnel endpoint VTEP equipment; the opposite terminal equipment comprises opposite terminal two-layer equipment and opposite terminal VTEP equipment;
The network between the target VTEP equipment and the opposite-end two-layer equipment is an Ethernet, and an Ethernet OAM detection mechanism is deployed in the Ethernet; the network between the target VTEP equipment and the opposite-end VTEP equipment is a VXLAN, and the VXLAN deploys a VXLAN OAM detection mechanism.
3. The method of claim 2, wherein when the link failure state changes, determining the target network type in the hybrid network to which the changed failure state belongs comprises:
When the link fault state of the Ethernet side transmission or the Ethernet side receiving of the target VTEP equipment changes, determining that the type of the target network in the mixed networking to which the changed fault state belongs is Ethernet;
according to the operation maintenance management OAM detection mechanism corresponding to the other network types, correspondingly notifying the opposite terminal equipment matched with the other network types that the link fault state changes, comprising:
According to a VXLAN OAM detection mechanism, the opposite-end VTEP equipment is informed of the change of the link fault state in the sending direction or the receiving direction, so that the opposite-end VTEP equipment can inform the target two-layer equipment connected with the opposite-end VTEP equipment through the Ethernet of the change of the link fault state after receiving the fault change information and detecting the change of the link fault state.
4. The method of claim 2, wherein when the link failure state changes, determining the target network type in the hybrid network to which the changed failure state belongs comprises:
When the link fault state sent by the VXLAN side or received by the VXLAN side of the target VTEP equipment changes, determining the type of the target network in the mixed networking to which the changed fault state belongs as VXLAN;
according to the operation maintenance management OAM detection mechanism corresponding to the other network types, correspondingly notifying the opposite terminal equipment matched with the other network types that the link fault state changes, comprising:
And according to an Ethernet OAM detection mechanism, notifying the opposite terminal two-layer equipment that the link fault state of the transmitting direction or the receiving direction is changed.
5. The method of claim 4, wherein notifying the peer device matching the other network type of the change in the link failure state in accordance with the operation, maintenance and administration OAM detection mechanism corresponding to the other network type, further comprises:
According to a VXLAN OAM detection mechanism, the opposite-end VTEP equipment is informed of the change of the link fault state in the sending direction or the receiving direction, so that the opposite-end VTEP equipment can inform the target two-layer equipment connected with the opposite-end VTEP equipment through the Ethernet of the change of the link fault state after receiving the fault change information and detecting the change of the link fault state.
6. The method according to claim 3 or 5, wherein notifying the peer VTEP device that a link failure state of a transmission direction or a reception direction has changed according to a VXLAN OAM detection mechanism, comprises:
And generating a custom message for indicating the link fault state of the sending direction or the receiving direction of the notification to the opposite-end VTEP equipment to change according to a custom VXLAN OAM detection mechanism, and sending the custom message to the opposite-end VTEP equipment.
7. The method of claim 6, wherein the reserved field set flag bit in the header field of the custom message is used to indicate a fault condition, the fault condition including the occurrence and elimination of a reception fault and the occurrence and elimination of a transmission fault.
8. A link failure state notification apparatus, for use with a target device, comprising:
The system comprises a target network type determining module which is used for determining the target network type in the mixed networking which is the fault state when the fault state of the link is changed;
A fault state notification module, configured to determine other network types in the hybrid network except for the target network type, and correspondingly notify, according to an operation maintenance management OAM detection mechanism corresponding to the other network types, a peer device matching the other network types that a link fault state changes;
wherein the hybrid networking comprises at least two network types; the opposite terminal equipment comprises at least two opposite terminal equipment, and the network types between the target equipment and the opposite terminal equipment of different types are different.
9. A network device, comprising:
one or more processors;
a storage means for storing one or more programs;
The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the link failure state advertisement method of any of claims 1-7.
10. A storage medium storing a computer program which, when executed by a processor, implements the link failure state notification method of any of claims 1-7.
CN201911018840.XA 2019-10-24 2019-10-24 Link fault state notification method, device, equipment and medium Active CN112714006B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911018840.XA CN112714006B (en) 2019-10-24 2019-10-24 Link fault state notification method, device, equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911018840.XA CN112714006B (en) 2019-10-24 2019-10-24 Link fault state notification method, device, equipment and medium

Publications (2)

Publication Number Publication Date
CN112714006A CN112714006A (en) 2021-04-27
CN112714006B true CN112714006B (en) 2024-05-17

Family

ID=75541330

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911018840.XA Active CN112714006B (en) 2019-10-24 2019-10-24 Link fault state notification method, device, equipment and medium

Country Status (1)

Country Link
CN (1) CN112714006B (en)

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6295615B1 (en) * 1991-12-09 2001-09-25 Sprint Communications Company, L. P. Automatic restoration of communication channels
CN1838620A (en) * 2005-03-25 2006-09-27 华为技术有限公司 Method for detecting chain circuit fault between end-to-end notes in mixed network
CN1848756A (en) * 2005-04-15 2006-10-18 华为技术有限公司 Method for managing fault of Ethernet and multi-protocol tag exchange network interconnection
CN1917439A (en) * 2005-08-18 2007-02-21 华为技术有限公司 Method of fault management, and performance management in intercommunication network between Ethernet and MPLS
CN1968156A (en) * 2006-08-30 2007-05-23 华为技术有限公司 Ethernet device link failure detection method and its system
CN101145996A (en) * 2005-04-15 2008-03-19 华为技术有限公司 Failure management method for interaction between Ethernet and multi-protocol label switching network
CN101207521A (en) * 2007-12-12 2008-06-25 华为技术有限公司 Method for fault detection and convergence of Ethernet and node apparatus
CN101854565A (en) * 2009-03-31 2010-10-06 华为技术有限公司 Information transmission method, service protection method, system and devices
CN102006222A (en) * 2010-11-16 2011-04-06 中兴通讯股份有限公司 Service link switching method and service link switching device
CN102013990A (en) * 2009-09-08 2011-04-13 中兴通讯股份有限公司 End to end notification method and system for multi-segment pseudowire fault
US8386983B1 (en) * 2010-08-10 2013-02-26 Xilinx, Inc. Parallel signal routing
CN105591775A (en) * 2014-10-23 2016-05-18 华为技术有限公司 Method, device and system for network operation administration maintenance (OAM)
CN106612211A (en) * 2015-10-23 2017-05-03 华为技术有限公司 A rout detecting method, a controller and a network device in a VxLAN
CN107846342A (en) * 2016-09-20 2018-03-27 华为技术有限公司 A kind of retransmission method, equipment and the system of VXLAN messages
CN109218107A (en) * 2018-10-15 2019-01-15 迈普通信技术股份有限公司 Link switch-over method, device, the network equipment and network system
CN110266587A (en) * 2019-08-14 2019-09-20 华为技术有限公司 A kind of processing method and processing device of link-state information

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7983173B2 (en) * 2004-05-10 2011-07-19 Cisco Technology, Inc. System and method for detecting link failures
US8804534B2 (en) * 2007-05-19 2014-08-12 Cisco Technology, Inc. Interworking between MPLS/IP and Ethernet OAM mechanisms
US8897145B2 (en) * 2010-09-22 2014-11-25 Tellabs Operations, Inc. Method and apparatus for network OAM interworking
US20150326469A1 (en) * 2014-05-09 2015-11-12 Telefonaktiebolaget L M Ericsson (Publ) Oam aided explicit path report via igp

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6295615B1 (en) * 1991-12-09 2001-09-25 Sprint Communications Company, L. P. Automatic restoration of communication channels
CN1838620A (en) * 2005-03-25 2006-09-27 华为技术有限公司 Method for detecting chain circuit fault between end-to-end notes in mixed network
CN1848756A (en) * 2005-04-15 2006-10-18 华为技术有限公司 Method for managing fault of Ethernet and multi-protocol tag exchange network interconnection
CN101145996A (en) * 2005-04-15 2008-03-19 华为技术有限公司 Failure management method for interaction between Ethernet and multi-protocol label switching network
CN1917439A (en) * 2005-08-18 2007-02-21 华为技术有限公司 Method of fault management, and performance management in intercommunication network between Ethernet and MPLS
CN1968156A (en) * 2006-08-30 2007-05-23 华为技术有限公司 Ethernet device link failure detection method and its system
CN101207521A (en) * 2007-12-12 2008-06-25 华为技术有限公司 Method for fault detection and convergence of Ethernet and node apparatus
CN101854565A (en) * 2009-03-31 2010-10-06 华为技术有限公司 Information transmission method, service protection method, system and devices
CN102013990A (en) * 2009-09-08 2011-04-13 中兴通讯股份有限公司 End to end notification method and system for multi-segment pseudowire fault
US8386983B1 (en) * 2010-08-10 2013-02-26 Xilinx, Inc. Parallel signal routing
CN102006222A (en) * 2010-11-16 2011-04-06 中兴通讯股份有限公司 Service link switching method and service link switching device
CN105591775A (en) * 2014-10-23 2016-05-18 华为技术有限公司 Method, device and system for network operation administration maintenance (OAM)
CN106612211A (en) * 2015-10-23 2017-05-03 华为技术有限公司 A rout detecting method, a controller and a network device in a VxLAN
CN107846342A (en) * 2016-09-20 2018-03-27 华为技术有限公司 A kind of retransmission method, equipment and the system of VXLAN messages
CN109218107A (en) * 2018-10-15 2019-01-15 迈普通信技术股份有限公司 Link switch-over method, device, the network equipment and network system
CN110266587A (en) * 2019-08-14 2019-09-20 华为技术有限公司 A kind of processing method and processing device of link-state information

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Provider Backbone Transport Technology;ZTE;ZTE Communications;20090325(第01期);全文 *
一种基于BFD检测的IP快速重路由解决策略;伍思廉;;信息通信;20160715(第07期);全文 *
光纤传感网络链路故障自修复***设计;王艳阁;;激光杂志;20180325(第03期);全文 *

Also Published As

Publication number Publication date
CN112714006A (en) 2021-04-27

Similar Documents

Publication Publication Date Title
JP5345942B2 (en) Ethernet OAM in intermediate nodes of PBT network
US9521055B2 (en) Network connectivity management
CN107332726B (en) Communication link detection method and device
US10708132B2 (en) Technique for handling a status change in an interconnect node
CN102868569B (en) The method for testing performance of Layer3 Virtual Private Network, node and system
CN104144124B (en) Data forwarding method, Apparatus and system
CN108243114B (en) Method, equipment and system for forwarding message
CN106559280A (en) Bidirectional forwarding detection (BFD) method and device
CN107517117B (en) IP layer OAM (operation administration and maintenance) alarm method and device and network node
US20170222864A1 (en) Method and Apparatus for Implementing Operation, Administration, and Maintenance Function
CN109218107A (en) Link switch-over method, device, the network equipment and network system
CN112291116A (en) Link fault detection method and device and network equipment
US20170155522A1 (en) Communication apparatus and communication system
EP2858302A1 (en) Connectivity check method of service stream link, related apparatus and system
CN102571464B (en) Link tracking processing method and system
US20160344614A1 (en) Network Topology Discovery by Resolving Loops
US20110116384A1 (en) Network connectivity management
WO2016015606A1 (en) Method for locating port connection error and related device
CN112714006B (en) Link fault state notification method, device, equipment and medium
CN102882779A (en) VRRP (Virtual Router Redundancy Protocol) advertisement link protection method and system
CN114690680A (en) Data processing method, controller and first network equipment
US9667439B2 (en) Determining connections between disconnected partial trees
CN114401324B (en) Message forwarding method, network equipment and system
CN102711163B (en) A kind of method of IP-RAN equipment fast detecting alarm link failure
CN113489626B (en) Method and device for detecting and notifying path fault

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
GR01 Patent grant
GR01 Patent grant