CN113259162B

CN113259162B - Network fault determination method and device, electronic equipment and storage medium

Info

Publication number: CN113259162B
Application number: CN202110519508.2A
Authority: CN
Inventors: 丁炎; 苏建明; 蒋家堂; 张胜
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-05-08
Filing date: 2021-05-08
Publication date: 2022-09-16
Anticipated expiration: 2041-05-08
Also published as: CN113259162A

Abstract

The disclosure provides a network fault determination method and device, electronic equipment and a storage medium, and can be used in the technical field of cloud computing and can also be used in other fields except the technical field of cloud computing. The network fault determination method comprises the following steps: generating temporary static routing information, wherein the temporary static routing information comprises a target gateway IP address of the first VTEP device; generating a routing table entry according to the temporary static routing information, wherein the routing table entry comprises a target routing path from the second VTEP device to the first VTEP device; transmitting the routing table entry to a second VTEP device; according to the routing table item, sending a network operation and maintenance message to the second VTEP device so as to send the network operation and maintenance message to the preset IP address of the external network through the second VTEP device; and receiving a maintenance result message returned by the second VTEP equipment according to the target routing path so as to determine that no fault exists from the first VTEP equipment to the network with the preset IP address of the external network.

Description

Network fault determination method and device, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of cloud computing technologies, and in particular, to a network fault determination method and apparatus, an electronic device, a computer-readable storage medium, and a computer program product.

Background

At present, when a Spine-Leaf network architecture is adopted for networking in an integral framework of mainstream cloud data center hardware network device networking in the industry, Leaf device distributed gateway configuration can be adopted for better adapting to the fact that virtual machines and containers in computing resources can be subjected to cross-Leaf device hot migration.

In the course of implementing the disclosed concept, the inventors found that there are at least the following problems in the related art: when traffic is sent to a Leaf gateway from north to south, the traffic is difficult to ensure that the traffic can be sent to expected Leaf equipment because of ECMP or only one network segment route is preferred, and the defects of networking configuration cause that network operation and maintenance personnel cannot accurately position network faults when carrying out network state troubleshooting.

Disclosure of Invention

In view of the above, the present disclosure provides a network fault determination method and apparatus, an electronic device, a computer-readable storage medium, and a computer program product.

One aspect of the present disclosure provides a network fault determination method, including:

generating temporary static routing information, wherein the temporary static routing information comprises a target gateway IP address of the first VTEP device;

generating a routing table entry according to the temporary static routing information, wherein the routing table entry comprises a target routing path from the second VTEP device to the first VTEP device;

transmitting the routing table entry to a second VTEP device;

according to the routing table item, sending a network operation and maintenance message to the second VTEP device so as to send the network operation and maintenance message to the preset IP address of the external network through the second VTEP device;

and receiving a maintenance result message returned by the second VTEP equipment according to the target routing path so as to determine that no fault exists from the first VTEP equipment to the network with the preset IP address of the external network.

According to an embodiment of the present disclosure, further comprising,

when generating temporary static routing information: generating preset time information, wherein the preset time information is used for representing the duration of the first preset delay time;

after generating the temporary static routing information: and the network operation and maintenance message is sent to the second VTEP equipment after the temporary static routing information is generated and the first preset delay time is waited.

According to the embodiment of the present disclosure, after the generating the temporary static routing information: and waiting for a second preset delay time so as to cancel the temporary static routing information after the second preset delay time.

According to an embodiment of the present disclosure, wherein the second preset delay time is greater than the first preset delay time.

According to an embodiment of the present disclosure, wherein the generating of the preset time information includes one of:

inputting an extended command line on a first VTEP device to generate preset time information;

expanding the management information base to generate preset time information;

and calling a Netconf interface for expansion so as to generate preset time information.

According to an embodiment of the present disclosure, wherein generating the temporary static routing information includes one of:

inputting an extended command line on the first VTEP device to generate temporary static routing information;

expanding the management information base to generate temporary static routing information;

and calling a Netconf interface for expansion to generate temporary static routing information.

According to an embodiment of the present disclosure, wherein generating the routing table entry according to the temporary static routing information includes:

generating an EVPN table according to the temporary static routing information;

and generating a routing table entry according to the EVPN table, wherein the routing table entry is a BGP routing table entry.

Another aspect of the present disclosure provides a network fault determination apparatus including a first generation module, a second generation module, a transmission module, and a reception module.

The first generating module is used for generating temporary static routing information, wherein the temporary static routing information comprises a target gateway IP address of the first VTEP device;

a second generating module, configured to generate a routing table entry according to the temporary static routing information, where the routing table entry includes a target routing path from the second VTEP device to the first VTEP device;

the transmission module is used for transmitting the routing table item to the second VTEP device;

the sending module is used for sending the network operation and maintenance message to the second VTEP device according to the routing table entry so as to send the network operation and maintenance message to the preset IP address of the external network through the second VTEP device;

and the receiving module is used for receiving the maintenance result message returned by the second VTEP equipment according to the target routing path so as to determine that no fault exists from the first VTEP equipment to the network with the preset IP address of the external network.

According to an embodiment of the present disclosure, the network failure determining apparatus further includes:

a third generating module, configured to generate preset time information when the temporary static routing information is generated, where the preset time information is used to represent a duration of the first preset delay time;

and the first monitoring module is used for waiting for a first preset delay time according to the preset time information after the temporary static routing information is generated so as to generate a routing table item within the first preset delay time, and sending a network operation and maintenance message to the second VTEP device after the temporary static routing information is generated and the first preset delay time is waited.

According to an embodiment of the present disclosure, the network failure determining apparatus further includes: and the second monitoring module is used for waiting for a second preset delay time after the temporary static routing information is generated so as to cancel the temporary static routing information after the second preset delay time.

According to an embodiment of the present disclosure, the second preset delay time is greater than the first preset delay time.

expanding the management information base to generate preset time information;

According to an embodiment of the present disclosure, the second generating module includes a first generating unit and a second generating unit.

The first generating unit is used for generating an EVPN table according to the temporary static routing information;

and the second generating unit is used for generating a routing table entry according to the EVPN table, wherein the routing table entry is a BGP routing table entry.

Another aspect of the present disclosure provides an electronic device including: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the network fault determination method as above.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the network fault determination method as above when executed.

Another aspect of the present disclosure provides a computer program product comprising computer executable instructions for implementing the network fault determination method as above when executed.

According to the embodiment of the disclosure, by expanding the Leaf-VTEP node device at the protocol control plane, that is, configuring and pre-generating a piece of temporary static routing information including the target gateway IP address of the first VTEP device, pre-generating a high-priority route from the second VTEP device to the first VTEP device path according to the temporary static routing information, and notifying the second VTEP device of the routing information, the second VTEP device can find the target gateway IP address of the next hop according to the target routing path when forwarding the packet to the first VTEP device, so that the repair result packet can be returned to the desired first VTEP device according to the desired forwarding path in the backhaul. Therefore, the network operation and maintenance personnel can further directly use the gateway IP address of the first VTEP device to directly perform operations such as operation and maintenance, and the like, so as to quickly eliminate the network problem.

By using the method of the embodiment of the disclosure, the defects of distributed gateway networking of Leaf equipment in operation and maintenance under a Spine-Leaf network architecture are overcome, and network operation and maintenance personnel are allowed to directly enable tenant real service gateway IP to perform fault troubleshooting operations such as Ping/Tracert (namely testing the connectivity of a target network/determining the path from the service gateway IP to a target address) and the like under the distributed gateway networking architecture, so that network troubleshooting can be rapidly performed, and the network operation and maintenance cost and the fault positioning time of an SDN data center can be simplified.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

fig. 1 schematically illustrates an exemplary system architecture to which the network fault determination methods and apparatus of the present disclosure may be applied;

fig. 2 is a diagram schematically illustrating EVPN information transferred through BGP routing in the related art;

FIG. 3 schematically illustrates a flow chart of a network fault determination method according to an embodiment of the present disclosure;

fig. 4 schematically illustrates a flow chart of a network fault determination method according to another embodiment of the present disclosure;

FIG. 5 schematically illustrates a diagram of extending relevant MIB nodes, in accordance with an embodiment of the disclosure;

FIG. 6 illustrates a flow chart of a network fault determination method according to an embodiment of the present disclosure;

fig. 7 schematically illustrates a block diagram of a network fault determination apparatus according to an embodiment of the present disclosure; and

fig. 8 schematically shows a block diagram of an electronic device for implementing a network fault determination method according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Before the embodiments of the present disclosure are explained in detail, the system structure and the application scenario related to the method provided by the embodiments of the present disclosure are described as follows.

Fig. 1 schematically illustrates an exemplary system architecture 100 to which the network fault determination methods and apparatus of the present disclosure may be applied. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, the system architecture 100 according to the embodiment is based on a cloud data center SDN network architecture, and in an application scenario of the present disclosure, is based on an SDN data center, which uses a Spine-Leaf distributed gateway networking architecture.

As shown in fig. 1, a Neutron service process of an Openstack cloud platform 101 interfaces with an SDN controller 102 through a Reset-API interface to deliver a cloud platform tenant virtual service network. The SDN controller 102 connects each managed switch/router in the whole SDN data center network to each other through a Netconf/Openflow interface in the south, and issues the tenant virtual service network to a corresponding network node, so as to implement relevant configuration issuing of the underlay/overlay service network and relevant operation and maintenance monitoring of the service network. And the NMS network management system acquires data related to operation and maintenance monitoring of the network in the data center through the SNMP/Netconf interface. The SDN controller 102 is a control center of the system, and is responsible for generating an internal switching path and a boundary service route of a network and processing a network state change event, each managed switch/router in the SDN data center network is responsible for forwarding user data, and forwarding entries required in a forwarding process are generated by the SDN controller 102.

The system architecture 100 based on the Spine-Leaf architecture comprises Border-VTEP nodes 103, Spine-VTEP nodes 104 and Leaf-VTEP nodes 105 in an EVPN routing protocol control plane, wherein a plurality of virtual servers 106 are hung under each Leaf-VTEP node.

Each Leaf-VTEP node 105 and each Borde-VTEP node 103 under the Spine-Leaf architecture run an MP-BGP/EVPN routing protocol, automatic configuration of an Overlay Vxlan network and automatic online and table item learning of tenant virtual machine, container and other types of computing resources are achieved by transmitting two, three and five types of routes, and two, three layers of east-west flow forwarding and north-south flow forwarding of various types of computing resources in an SDN data center are achieved through an EVPN routing protocol control plane.

In the network operation and maintenance, in order to determine a failed network, it is necessary to determine whether a network between a target Leaf-VTEP device and an external network device has a failure through a Ping/Tracert operation (i.e., testing connectivity of the target network and/or determining a path from a service gateway IP to a target address). Specifically, a Ping/Tracert message may be sent to the external network through the target Leaf-VTEP node 105 device, where the Ping/Tracert message is as follows: and forwarding the path of the Leaf-VTEP node 105 → the Spine-VTEP node 104 → the Border-VTEP node → the router 107 → the extranet 108, and judging whether the network between the target Leaf-VTEP device and the extranet device has a fault according to the receiving condition of the Ping/Tracert reply message. Taking the execution of the Ping operation as an example, if a Ping reply message can be received, it can be proved that no fault exists in the part of the network, otherwise, a fault exists in the part of the network; the aim of quickly eliminating the network problem or quickly positioning the network fault can be achieved by replying the message.

It should be noted that the network fault determination method and apparatus disclosed in the present disclosure may be used in the field of cloud computing technology, and may also be used in other fields besides the field of cloud computing technology.

In the related technology, a Spine-Leaf network architecture can be adopted for networking in an SDN hardware network, an SDN controller issues EVPN route configuration through a Netconf interface of a network device, an EVPN protocol of the network device automatically discovers the position of a computing resource accessed to an SDN data center network, and after learning message information such as Mac/ARP of the computing resource through the EVPN route, issues a VXLAN tunnel and related two-layer and three-layer forwarding table entries to guide traffic forwarding of the computing resource in the SDN network.

When the whole networking framework of the hardware network equipment of the cloud data center adopts a Spine-Leaf network architecture for networking,

in order to better adapt to the fact that virtual machines and containers in computing resources can be migrated across Leaf devices, distributed gateway configuration of the Leaf devices can be adopted, the same distributed gateway can be configured for each tenant network on a whole network Leaf VETP node, namely three layers of gateways corresponding to the same tenant and same network segment on the Leaf devices are configured to be the same IP and Mac addresses, so that the fact that the IP addresses of the gateways do not need to be modified and ARP table item information does not need to be refreshed after the virtual machines and the containers are migrated across the Leaf devices is guaranteed, and flow interruption time after the virtual machines and the containers are migrated across the Leaf devices is greatly shortened.

Fig. 2 schematically shows EVPN information transferred through BGP routing in the related art. As shown in fig. 2, EVPN information transferred by BGP route is illustrated, taking tenant a with two virtual machines (VM-1, VM-2) as an example:

each Leaf-VETP node is configured with an IP address of 10.0.0.1/24, and a Mac address of 1234-1234, so that the configuration enables VM-1 or VM-2 to perform unrestricted migration on the Leaf-VETP nodes of the whole network, without reconfiguring the gateway IP address of the virtual machine VM after cross-Leaf migration, and because the Mac addresses of the distributed gateways are all the same, the virtual machine VM can communicate without learning ARP information of the gateway again after hot migration.

For example, the IP address and Mac address of the three-layer distributed gateway of tenant a on the Leaf-VETP node are both 10.0.0.1 and 1234-1234. According to the definition of RFC 7432, referring to the contents of the VRF table (virtual routing table) in fig. 2, Leaf-1 and Leaf-2 advertise EVPN routing information via BGP as follows:

the Leaf-1 node advertises to the BGP neighbor through Type-2(RFC defined second Type route) route, and VM-1 learns on line:

Type-2

IP＝10.0.0.11

Mac＝1111-1111-1111

next hop RD 19.11.10.8

Leaf-1 advertises to BGP neighbors through Type-5 (fifth Type of routing defined by RFC), and the gateway route of tenant a is:

Type-5

IP＝10.0.0.0

Mask＝255.255.255.0

next hop RD 19.11.10.8

Leaf-2 announces to BGP neighbor through Type-2 route, VM-2 goes online and learns:

Type-2

IP＝10.0.0.22

Mac＝2222-2222-2222

next hop RD 19.11.10.8

Leaf-2 announces to BGP neighbor through Type-5 route, and the gateway route of tenant A is:

Type-5

IP＝10.0.0.1

Mac＝1234-1234-1234

next hop RD 19.11.10.9

On the Border-VTEP node Border-1, for the route of the tenant A gateway (IP ═ 10.0.0.1), two identical next hop IP addresses of Leaf-1 and Leaf-2 are learned from the Type-5 network segment route.

When a network operation and maintenance person tries to perform network troubleshooting on a target Leaf-VTEP node where a target virtual machine VM is located by using a service gateway of the target virtual machine VM as a source IP, for example, when the target Leaf-VTEP node device sends a Ping/Tracert packet (Ping/Tracert outer network arbitrary IP) to an outer network, a backhaul packet from a Border-VTEP node to the Leaf-VTEP node may be randomly forwarded to the same or different Leaf devices (ECMP equivalent route) because two identical next hops occur, so that backhaul traffic may not be all correctly forwarded to a desired Leaf-VTEP node device (i.e., an originating device performing Ping/Tracert operation) and a failure troubleshooting operation cannot be performed by using the service gateway IP address, or in such an operation and maintenance scenario, when the network operation and maintenance person performs network state troubleshooting by using the service gateway IP address configured by computing resources, the defects of networking configuration are overcome by temporarily increasing configuration IP addresses and releasing and adjusting routing information, and the method is very inconvenient in actual operation and maintenance use scenes.

Based on the above problem, embodiments of the present disclosure provide a network fault determination method to solve the above technical problem. According to the embodiment of the disclosure, Leaf-VTEP node equipment is expanded on the protocol control plane, so that fault troubleshooting operation of a tenant real service gateway IP is directly performed under a distributed gateway networking architecture.

FIG. 3 schematically illustrates a flow chart of a network fault determination method according to an embodiment of the present disclosure; as shown in fig. 3, the method includes operations S301 to S305.

In operation S301, temporary static routing information is generated, wherein the temporary static routing information includes a destination gateway IP address of the first VTEP device.

In operation S302, a routing table entry is generated according to the temporary static routing information, where the routing table entry includes a target routing path from the second VTEP device to the first VTEP device.

In operation S303, the routing table entry is transmitted to the second VTEP device.

In operation S304, the network operation and maintenance message is sent to the second VTEP device according to the routing table entry, so that the network operation and maintenance message is sent to the preset IP address of the external network through the second VTEP device.

In operation S305, a repair result message returned by the second VTEP device according to the target routing path is received, so as to determine that there is no failure in the network from the first VTEP device to the external network preset IP address.

According to the embodiment of the disclosure, the EVPN routing protocol control plane based on the spin-Leaf architecture system comprises Border-VTEP nodes, spin-VTEP nodes and Leaf-VTEP nodes, wherein each Leaf-VTEP node hangs a plurality of virtual server VMs. In the above operation, the first VTEP device is a Leaf-VTEP node device, and the second VTEP device is a Border-VTEP node device.

When a network operation and maintenance person tries to perform network troubleshooting on a first VTEP device (Leaf-VTEP node device) where a target virtual server VM is located by using a service gateway of the virtual server VM as a source IP, in order to determine a fault network, whether a fault exists in a network between the first VTEP device (Leaf-VTEP node device) and an external network device is judged by sending a network operation and maintenance message to the external network. For example, a first VTEP device (Leaf-VTEP node device) sends a Ping/Tracert packet to an external network device with an IP address preset by the external network (i.e., performs Ping/Tracert operation) to perform network fault location.

Specifically, the Ping/Tracert message (network operation and maintenance message) is as follows: forwarding paths of a first VTEP device (Leaf-VTEP node device) → a second VTEP device (Border-VTEP node device) → an external network preset IP address, and receiving a maintenance result message (Ping/Tracert reply message). And finally, judging whether the network with the IP address preset from the first VTEP device to the external network has a fault or not according to the receiving condition of the maintenance result message.

In the related art, the repair result message (i.e., the Ping/Tracert reply message from the second VTEP device to the first VTEP device) is forwarded according to the dynamic routing path automatically generated by the row MP-BGP/EVPN routing protocol, and because the corresponding triple-layer gateways on each first VTEP device are configured to have the same IP and Mac addresses, due to the existence of equivalent routes, the repair result message may not be able to perform troubleshooting using the service gateway IP addresses because two identical next hops may not be correctly forwarded to the desired first VTEP device (i.e., the originating device performing the Ping/Tracert operation).

Therefore, according to the embodiment of the present disclosure, in operation S301, configuring and pre-generating a piece of temporary static routing information including the destination gateway IP address of the first VTEP device may solve this problem, and in operation S302, generating a routing table entry according to the temporary static routing information, that is, pre-generating a high-priority route from the second VTEP device to the first VTEP device, and in operation S303, transmitting the routing table entry to the second VTEP device, that is, notifying the routing information to the second VTEP device, so that the second VTEP device can find the destination gateway IP address of the next hop according to the destination routing path when forwarding the packet to the first VTEP device, and can enable the repair result packet to return to the desired first VTEP device according to the desired forwarding path, that is, the destination routing path from the second VTEP device to the first VTEP device during the backhaul.

Based on this, in operation S305, it may be determined whether a network from the first VTEP device to the external network preset IP address has a fault according to the receiving condition of the maintenance result message. Taking the Ping operation as an example, if a Ping reply message can be received, it can be proved that no fault exists in the part of the network, and if no fault exists in the part of the network, the fault exists in the part of the network, and the purpose of quickly removing the network problem or quickly positioning the network fault can be achieved through the reply message.

Therefore, according to the embodiment of the disclosure, by expanding the Leaf-VTEP node device at the protocol control plane, that is, configuring and pre-generating a piece of temporary static routing information including the destination gateway IP address of the first VTEP device, pre-generating a high-priority route from the second VTEP device to the first VTEP device according to the temporary static routing information, and notifying the second VTEP device of the routing information, the second VTEP device can find the destination gateway IP address of the next hop according to the destination routing path when forwarding the packet to the first VTEP device, so that the repair result packet can be returned to the desired first VTEP device according to the desired forwarding path in the backhaul. Therefore, the network operation and maintenance personnel can further directly use the gateway IP address of the first VTEP device to directly perform operations such as operation and maintenance, and the like, so as to quickly eliminate the network problem.

Fig. 4 schematically shows a flow chart of a network failure determination method according to another embodiment of the present disclosure.

According to an embodiment of the present disclosure, when generating temporary static routing information: and generating preset time information, wherein the preset time information is used for representing the duration of the first preset delay time. And after generating the temporary static routing information: and waiting for a first preset delay time according to the preset time information. As shown in fig. 4, the method includes operations S401 to S405.

In operation S401, temporary static routing information and preset time information are generated, where the temporary static routing information includes a target gateway IP address of the first VTEP device, and the preset time information is used to characterize a duration of the first preset delay time.

In operation S402, a routing table entry is generated according to the temporary static routing information within a first preset delay time, where the routing table entry includes a target routing path from the second VTEP device to the first VTEP device.

In operation S403, the routing table entry is transmitted to the second VTEP device.

In operation 404, after waiting for the first preset delay time according to the preset time information, the network operation and maintenance message is sent to the second VTEP device according to the routing table entry, so that the network operation and maintenance message is sent to the preset IP address of the external network through the second VTEP device.

In operation S405, a repair result message returned by the second VTEP device according to the target routing path is received, so as to determine that there is no failure in the network from the first VTEP device to the external network preset IP address.

According to the embodiment of the disclosure, in the method shown in fig. 4, while the temporary static routing information is generated, the preset time information for representing the duration of the first preset delay time is also generated, because the network operation and maintenance packet cannot be immediately sent after the temporary static routing information is generated, the high-priority route according to the temporary static routing information is not yet in effect, if the network operation and maintenance packet is immediately sent, the return reply packet is also forwarded according to the originally default dynamic routing path, and it cannot be guaranteed that the return reply packet can be forwarded to the expected first VTEP device.

Therefore, according to the embodiment of the present disclosure, it is necessary to generate the preset time information in advance, that is, to set the first preset delay time, and wait for the first preset delay time, so as to generate the routing table entry within the first preset delay time, and send the network operation and maintenance overhaul packet to the second VTEP device after generating the temporary static routing information and waiting for the first preset delay time, which may ensure that the high-priority route according to the temporary static routing information may take effect, and further ensure that the return reply packet may be forwarded to the expected first VTEP device.

According to the embodiment of the present disclosure, after the generating the temporary static routing information: and waiting for a second preset delay time so as to cancel the temporary static routing information after the second preset delay time, wherein the second preset delay time is greater than the first preset delay time.

According to the embodiment of the disclosure, the high-priority route generated in advance according to the temporary static route information and routed from the second VTEP device to the first VTEP device is only used for network operation and maintenance, and after the network operation and maintenance is completed, the generated temporary static route information needs to be cancelled in a normal working state, so that the network device forwards the data traffic according to the normal route. Moreover, the first preset delay time is used for generating a routing table entry in the time period so that the temporary routing takes effect, and the second preset delay time is required to ensure that the execution of the network operation and maintenance operation is completed, that is, in the second preset delay time period, the operation to be completed includes: and generating a routing table entry to enable the temporary route to take effect, sending a network operation and maintenance message and receiving a maintenance result message returned according to the target routing path, wherein the second preset delay time is longer than the first preset delay time.

Therefore, in the embodiment of the present disclosure, after the temporary static routing information is generated, the second preset delay time is waited, and after the second preset delay time, the temporary static routing information is automatically cancelled, so that the network device is ensured to forward the data traffic according to a normal route.

expanding the management information base to generate preset time information;

According to the embodiment of the disclosure, the methods for generating the preset time information, or generating the temporary static routing information, or simultaneously generating the temporary static routing information and the preset time information are the same. Hereinafter, a method of generating temporary static routing information and preset time information at the same time is taken as an example for explanation, and embodiments of the present disclosure include, but are not limited to, the methods described in the following examples.

According to the embodiment of the disclosure, taking the implementation of Ping/Tracert operation for network operation and maintenance as an example, two optional parameters, namely gateway and delay, are added to the Ping/Tracert function, and the method is implemented by expanding the corresponding SNMP and Netconf interface packaging formats.

Specifically, generating the temporary static routing information and the preset time information includes:

(1) and inputting an extended command line on the first VTEP device, and adding two optional parameters of gateway and delay to the Ping/Tracert function to generate temporary static routing information and preset time information.

Such as: Ping/Tracert-vpn-instance A-gateway X.X.X.X-delay xx seconds Y.Y.Y.Y.Y.Y.

The newly added gateway parameter (x.x.x.x) is used to fill in the gateway IP address on the Leaf-VETP node corresponding to the tenant service, where, for example, IP is 10.0.0.1, that is, used to generate the temporary static routing information.

The newly added delay parameter (xx seconds) is used for generating preset time information, namely the duration of the first preset delay time, and notifying the VETP node to fill the time parameter in the timer, for example, setting the duration of the first preset delay time to be 1 second.

In the above command line, "y.y.y", denotes an arbitrary IP address of the external network, such as 168.1.0.1.

(2) A Management Information Base (MIB) is extended to generate temporary static routing information and preset time information. That is, MIB extension is implemented on the gateway and delay parameters, and SNMP (network management protocol) setting operation is allowed to be performed through the MIB, for example, as shown in fig. 5, fig. 5 schematically shows a schematic diagram of extending relevant MIB nodes according to an embodiment of the present disclosure.

Examples of setting SNMP (network management protocol) related parameters are as follows: (wherein xx.xx.xx.xx.xx.xxx indicates that the extended gateway parameter corresponds to an OID (Object Identifier) value, and xx.xx.xx.xx.xx.yyy indicates an OID value corresponding to the extended delay parameter)

Remote SNMP Agent

z.z.z.z (user setting)

……

OID to Set

xx.xx.xx.xx.xxx

Value to Set

x.x.x.x

OID to Set

xx.xx.xx.xx.yyy

Value to Set

zz (user setting)

(3) And calling a Netconf interface for expansion so as to generate temporary static routing information and preset time information. That is, for the Netconf interface extension implementation corresponding to the gateway parameter and the delay parameter, the Netconf interface is allowed to complete the relevant operations of the method according to the embodiment of the present disclosure, and the Netconf extension implementation is as follows.

Request XML Structure example:

<Ping>

…

</PingParameters>

</IPV4ping>

</Ping>

wherein, the fields of "< Gateway > </Gateway >" and "< Delay > </Delay >" are fields implemented in the Netconf interface extension of the embodiment of the present disclosure.

According to the embodiment of the disclosure, because the extension is only performed on the Leaf VETP node local machine in the manner of inputting the extension command line on the first VTEP device, the EVPN route advertisement between the VETP devices conforms to the EVPN Type 5 route packet encapsulation format defined by RFC 7432, for the SDN data center deployed in the ground, if the network operation and maintenance function of the embodiment of the disclosure needs to be realized, only the device software upgrading or modification needs to be performed on the Leaf-VETP node, and for the Border-VETP device with higher cost, the upgrading and modification are not required, so that the early investment cost is greatly reduced.

In addition, according to the embodiment of the present disclosure, a Management Information Base (MIB) is extended, or a Netconf interface is called to extend, that is, multiple external service modes and external service interfaces are extended, and an MIB and an XML extended encapsulation interface corresponding to a network operation and maintenance method corresponding to the embodiment of the present disclosure are defined, so that a capability of linking with other operation and maintenance management components is further provided, and two network device management protocols currently mainstream in the industry, namely, Netconf and SNMP, are supported. After the network management software and the SDN Controller software in the whole data center system perform corresponding function extension, network operation and maintenance personnel can provide the operation and maintenance functions realized by the method in a UI interface operation mode of the NMS network management software and the SDN Controller, so that the operation and maintenance time and cost are further simplified and shortened.

generating an EVPN table according to the temporary static routing information;

Fig. 6 illustrates a flow chart of a network failure determination method according to an embodiment of the present disclosure. The method of the embodiment of the present disclosure is exemplified below with reference to fig. 6.

(1) The operation and maintenance personnel generate temporary static routing information and preset time information on the target Leaf-VTEP device, and can realize the setting and generation of the temporary static routing information including the target gateway IP address of the target Leaf-VTEP device and the time duration preset time information used for representing the first preset delay time by directly logging in to a device controller station, inputting an extension command line on the target Leaf-VTEP device, or calling an SNMP Set (setting) by NMS (network management system) to expand MIB (management information base) or calling a Netconf interface by an SDN (software defined network) controller to expand. Taking the execution of the Ping/Tracert operation for network operation and maintenance as an example, two optional parameters, namely gateway and delay, are added to the Ping/Tracert function, the gateway parameter is used for filling the gateway IP address on the Leaf-VETP node corresponding to the tenant service, and the delay parameter is used for filling the duration of the first preset delay time.

(2) And generating a routing table entry according to the temporary static routing information within the first preset delay time, wherein the routing table entry comprises a target routing path from the second VTEP device to the first VTEP device. The method specifically comprises the following steps:

first, an EVPN table, i.e., an EVPN table to which gateway newly added parameters are advertised (gateway IP addresses are inserted into the EVPN table), is generated based on temporary static routing information. Meanwhile, a timer is started locally according to the delay parameter time so as to inform the message assembly and sending of the Ping/Tracert detection data message after the timer is overtime.

Then, a BGP routing table entry is generated according to the EVPN table, namely, the fifth BGP protocol message of the EVPN is spliced. Gateway parameters are extracted from the EVPN table, EVPN 5 type routes are assembled according to service IP addresses according to a message format defined by RFC 7432, a BGP table is informed, and finally the route management module sends a BGP Update message to inform each BGP neighbor of the route information.

Meanwhile, a timer is started according to a second preset delay time (for example, the time is set to be delay parameter x 4 times), so that a BGP (withdrawal) message is sent after the timer expires, and the temporary static routing information of the service gateway for operation and maintenance positioning notified in the previous step is automatically withdrawn.

(3) And (4) notifying the routing table items (through a BGP Update message) to other VETP devices of the whole network, including a target Border-VTEP node device and other Leaf-VTEP and Border-VTEP node devices.

(4) Other VETP nodes in the SDN data center network equipment automatically add and delete detailed routes of a service gateway through received BGPUpdate/withdraw messages, guide Ping/Trace messages to carry out backhaul forwarding, and determine whether a network from target Leaf-VTEP equipment to an external network preset IP address has a fault or not according to the receiving condition of maintenance result messages.

Another aspect of the present disclosure provides a network fault determination apparatus, and fig. 7 schematically illustrates a block diagram of a network fault determination apparatus 700 according to an embodiment of the present disclosure. The network fault determination apparatus 700 may be used to implement the method described with reference to fig. 3.

As shown in fig. 7, the apparatus includes a first generating module 701, a second generating module 702, a transmitting module 703, a transmitting module 704, and a receiving module 705.

The first generating module 701 is configured to generate temporary static routing information, where the temporary static routing information includes a destination gateway IP address of the first VTEP device. A second generating module 702, configured to generate a routing table entry according to the temporary static routing information, where the routing table entry includes a target routing path from the second VTEP device to the first VTEP device. A transmitting module 703 is configured to transmit the routing table entry to the second VTEP device. A sending module 704, configured to send the network operation and maintenance message to the second VTEP device according to the routing table entry, so as to send the network operation and maintenance message to the preset IP address of the external network through the second VTEP device. The receiving module 705 is configured to receive a maintenance result message returned by the second VTEP device according to the target routing path, so as to determine that there is no failure in the network from the first VTEP device to the external network preset IP address.

According to the embodiment of the disclosure, the temporary static routing information is generated by the first generation module 701, so that the Leaf-VTEP node device is expanded on the protocol control plane, that is, a piece of temporary static routing information containing the IP address of the target gateway of the first VTEP device is configured and generated in advance; a route with high priority from the second VTEP device to the first VTEP device is generated in advance according to the temporary static route information by the second generating module 702, and the route information is notified to the second VTEP device by the transmitting module 703, so as to instruct the second VTEP device to find the target gateway IP address of the next hop according to the target route when forwarding the packet to the first VTEP device, and enable the repair result packet to return to the desired first VTEP device according to the desired forwarding path during backhaul. Therefore, network operation and maintenance personnel can further directly use the gateway IP address of the first VTEP device to directly perform operations such as operation and maintenance, and the purpose of quickly eliminating network problems or quickly positioning network faults is achieved.

According to an embodiment of the present disclosure, the network failure determining apparatus 700 further includes a third generating module and a first monitoring module.

The third generating module is configured to generate preset time information when the temporary static routing information is generated, where the preset time information is used to represent a duration of the first preset delay time. And the first monitoring module is used for waiting for a first preset delay time according to the preset time information after the temporary static routing information is generated so as to generate a routing table item within the first preset delay time, and sending a network operation and maintenance message to the second VTEP device after the temporary static routing information is generated and the first preset delay time is waited.

According to an embodiment of the present disclosure, the network failure determining apparatus 700 further includes: and the second monitoring module is used for waiting for a second preset delay time after the temporary static routing information is generated so as to cancel the temporary static routing information after the second preset delay time.

expanding the management information base to generate preset time information;

The first generating unit is used for generating an EVPN table according to the temporary static routing information; and a second generating unit, configured to generate a routing table entry according to the EVPN table, where the routing table entry is a BGP routing table entry.

Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

For example, any plurality of the first generating module 701, the second generating module 702, the transmitting module 703, the sending module 704 and the receiving module 705 may be combined and implemented in one module/unit/sub-unit, or any one of the modules/units/sub-units may be split into a plurality of modules/units/sub-units. Alternatively, at least part of the functionality of one or more of these modules/units/sub-units may be combined with at least part of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to an embodiment of the present disclosure, at least one of the first generating module 701, the second generating module 702, the transmitting module 703, the sending module 704, and the receiving module 705 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or in a suitable combination of any of them. Alternatively, at least one of the first generating module 701, the second generating module 702, the transmitting module 703, the sending module 704 and the receiving module 705 may be at least partly implemented as a computer program module, which when executed may perform a corresponding function.

Fig. 8 schematically shows a block diagram of an electronic device for implementing a network fault determination method according to an embodiment of the present disclosure. The electronic device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 8, an electronic device 800 according to an embodiment of the present disclosure includes a processor 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. The processor 801 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 801 may also include on-board memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flows according to embodiments of the present disclosure.

In the RAM 803, various programs and data necessary for the operation of the electronic apparatus 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 802 and/or the RAM 803. Note that the programs may also be stored in one or more memories other than the ROM 802 and RAM 803. The processor 801 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 800 may also include input/output (I/O) interface 805, input/output (I/O) interface 805 also connected to bus 804, according to an embodiment of the present disclosure. The system 800 may also include one or more of the following components connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that the computer program read out therefrom is mounted on the storage section 808 as necessary.

According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program, when executed by the processor 801, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 802 and/or RAM 803 described above and/or one or more memories other than the ROM 802 and RAM 803.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method provided by embodiments of the present disclosure, which, when the computer program product is run on an electronic device, is adapted to cause the electronic device to carry out the method of network failure determination provided by embodiments of the present disclosure.

The computer program, when executed by the processor 801, performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, and the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via communication section 809, and/or installed from removable media 811. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In situations involving remote computing devices, the remote computing devices may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to external computing devices (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. A network fault determination method, comprising:

generating temporary static routing information, wherein the temporary static routing information comprises a target gateway IP address of a first VTEP device, and the first VTEP device is a leaf-VTEP node device;

generating a routing table entry according to the temporary static routing information, wherein the routing table entry comprises a target routing path from a second VTEP device to the first VTEP device;

transmitting the routing table entry to the second VTEP device;

sending a network operation and maintenance message to the second VTEP device according to the routing table entry so as to send the network operation and maintenance message to an external network preset IP address through the second VTEP device;

2. The method of claim 1, further comprising,

while the generating temporary static routing information: generating preset time information, wherein the preset time information is used for representing the duration of a first preset delay time;

after the generating of the temporary static routing information: and waiting for the first preset delay time according to the preset time information so as to generate the routing table entry within the first preset delay time, and sending a network operation and maintenance message to the second VTEP device after generating the temporary static routing information and waiting for the first preset delay time.

3. The method of claim 2, further comprising, after the generating temporary static routing information:

waiting for a second preset delay time so as to cancel the temporary static routing information after the second preset delay time.

4. The method of claim 3, wherein the second preset delay time is greater than the first preset delay time.

5. The method of claim 2, wherein the generating preset time information comprises one of:

inputting an extended command line on the first VTEP device to generate the preset time information;

expanding a management information base to generate the preset time information;

and calling a Netconf interface for expansion so as to generate the preset time information.

6. The method of claim 1, wherein the generating temporary static routing information comprises one of:

inputting an extended command line on the first VTEP device to generate the temporary static routing information;

expanding a management information base to generate the temporary static routing information;

and calling a Netconf interface for expansion to generate the temporary static routing information.

7. The method of claim 1, wherein generating a routing table entry from the temporary static routing information comprises:

generating an EVPN table according to the temporary static routing information;

and generating the routing table entry according to the EVPN table, wherein the routing table entry is a BGP routing table entry.

8. A network fault determination apparatus comprising:

a first generating module, configured to generate temporary static routing information, where the temporary static routing information includes a target gateway IP address of a first VTEP device, where the first VTEP device is a leaf-VTEP node device;

a second generating module, configured to generate a routing table entry according to the temporary static routing information, where the routing table entry includes a target routing path from a second VTEP device to the first VTEP device;

a transmission module, configured to transmit the routing table entry to the second VTEP device;

a sending module, configured to send a network operation and maintenance message to the second VTEP device according to the routing table entry, so as to send the network operation and maintenance message to an external network preset IP address through the second VTEP device;

and the receiving module is used for receiving a maintenance result message returned by the second VTEP device according to the target routing path so as to determine that no fault exists between the first VTEP device and the network of the preset IP address of the external network.

9. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-7.

10. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 7.