CN114221899B

CN114221899B - Fault processing method and device

Info

Publication number: CN114221899B
Application number: CN202111441269.XA
Authority: CN
Inventors: 葛健楠
Original assignee: New H3C Technologies Co Ltd Hefei Branch
Current assignee: New H3C Technologies Co Ltd Hefei Branch
Priority date: 2021-11-30
Filing date: 2021-11-30
Publication date: 2024-03-08
Anticipated expiration: 2041-11-30
Also published as: CN114221899A

Abstract

The present disclosure relates to the field of network communications technologies, and in particular, to a fault handling method and device. The method is applied to a distributed elastic network interconnection DRNI system, and comprises the following steps: acquiring the link number of non-fault links included in each DR interface of the DR equipment of the opposite terminal and the DR interface liveness calculation weight value; when IPL link faults are detected, calculating a weight value based on the link number of non-fault links and DR interface liveness of each DR interface of the opposite-end DR equipment, calculating the first DR interface liveness of the opposite-end DR equipment, and calculating the second DR interface liveness of the opposite-end DR equipment; and adjusting the roles of the DR equipment based on the first DR interface activity degree of the opposite-end DR equipment and the second DR interface activity degree of the opposite-end DR equipment.

Description

Fault processing method and device

Technical Field

The present disclosure relates to the field of network communications technologies, and in particular, to a fault handling method and device.

Background

DRNI (Distributed Resilient Network Interconnect, distributed elastic network interconnect): the cross-device link aggregation technology is used for virtualizing two physical devices into one device at the aggregation level to realize the cross-device link aggregation, thereby providing device-level redundancy protection and traffic load sharing.

And the Device A and the Device B form load sharing and jointly transmit traffic, wherein the Device A is a master Device and the Device B is a slave Device. After IPL fault, DRNI provides MAD mechanism in order to prevent slave device from continuing to forward traffic, and interface on slave device is set to DRNI MAD DOWN state when DR system is split, so as to avoid traffic error forwarding and reduce influence on service as much as possible.

If the DR aggregation 1 link 1 on the master device has failed before the IPL fails, the available member ports of the DR aggregation 1 on the master device are less than the DR aggregation port 1 on the slave device, and at this time, there is still an optimization space for the DRNI MAD DOWN interface on the slave device.

Disclosure of Invention

The application provides a fault processing method and device, which are used for solving the problem that service is affected due to poor performance of main DR equipment when an IPL link is in fault in the prior art.

In a first aspect, the present application provides a fault handling method applied to a distributed resilient network interconnect DRNI system, the method including:

acquiring the link number of non-fault links included in each DR interface of the DR equipment of the opposite terminal and the DR interface liveness calculation weight value;

when IPL link faults are detected, calculating a weight value based on the link number of non-fault links and DR interface liveness of each DR interface of the opposite-end DR equipment, calculating the first DR interface liveness of the opposite-end DR equipment, and calculating the second DR interface liveness of the opposite-end DR equipment;

and adjusting the roles of the DR equipment based on the first DR interface activity degree of the opposite-end DR equipment and the second DR interface activity degree of the opposite-end DR equipment.

Optionally, the step of obtaining the link number of the non-fault links included in each DR interface of the opposite DR device and the DR interface activity calculating weight value includes:

and receiving an expanded DRCPDU message sent by the opposite terminal DR equipment, wherein the expanded DRCPDU message carries the link number of non-fault links included by each DR interface of the opposite terminal DR equipment and a DR interface activity calculation weight value.

Optionally, the extended DRCPDU packet is defined with a new TLV field, where a Value field of the new TLV field includes a linked list of each DR interface and a weight Value calculated by each DR interface activity.

Optionally, calculating the weight value based on the number of links of the non-failure links included in each DR interface of the opposite DR device and the DR interface activity level, and calculating the first DR interface activity level of the opposite DR device includes:

calculating weight values based on the number of active member ports of each DR group of the opposite terminal equipment and the DR interface liveness of the corresponding DR group, and respectively calculating the DR interface liveness of each DR group;

and taking the sum of the DR interface liveness of each DR group as the DR interface liveness of the opposite terminal equipment.

Optionally, the step of adjusting the role of the DR device based on the first DR interface activity of the peer DR device and the second DR interface activity of the peer DR device includes:

when the master and slave roles of the DR devices are adjusted, the priority of each DR device is calculated by taking the activity of the DR interface of each DR device as one of calculation factors, and the DR device with the high priority is taken as the master DR device and the DR device with the low priority is taken as the slave DR device.

In a second aspect, the present application provides a fault handling apparatus for use in a distributed resilient network interconnect, DRNI, system, the apparatus comprising:

an obtaining unit, configured to obtain the number of links of the non-failure link included in each DR interface of the opposite DR device and a DR interface activity calculation weight value;

a calculating unit, configured to calculate, when an IPL link failure is detected, a weight value based on the number of links of non-failure links included in each DR interface of the opposite DR device and DR interface liveness, calculate a first DR interface liveness of the opposite DR device, and calculate a second DR interface liveness of the first DR interface;

and the adjusting unit is used for adjusting the roles of the DR equipment based on the first DR interface activity level of the opposite-end DR equipment and the second DR interface activity level of the opposite-end DR equipment.

Optionally, when acquiring the number of links of the non-fault links included in each DR interface of the opposite DR device and the DR interface activity calculating weight value, the acquiring unit is specifically configured to:

Optionally, when calculating the first DR interface activity of the peer DR device based on the number of links of the non-faulty links included in each DR interface of the peer DR device and the DR interface activity calculating weight, the calculating unit is specifically configured to:

Optionally, when the role of the DR device is adjusted based on the first DR interface activity of the peer DR device and the second DR interface activity of the peer DR device, the adjusting unit is specifically configured to:

In a third aspect, an embodiment of the present application provides a fault handling apparatus, including:

a memory for storing program instructions;

a processor for invoking program instructions stored in said memory, performing the steps of the method according to any of the first aspects above in accordance with the obtained program instructions.

In a fourth aspect, embodiments of the present application also provide a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the steps of the method according to any one of the first aspects.

As can be seen from the foregoing, the fault handling method provided by the embodiment of the present application is applied to a distributed resilient network interconnect DRNI system, and the method includes: acquiring the link number of non-fault links included in each DR interface of the DR equipment of the opposite terminal and the DR interface liveness calculation weight value; when IPL link faults are detected, calculating a weight value based on the link number of non-fault links and DR interface liveness of each DR interface of the opposite-end DR equipment, calculating the first DR interface liveness of the opposite-end DR equipment, and calculating the second DR interface liveness of the opposite-end DR equipment; and adjusting the roles of the DR equipment based on the first DR interface activity degree of the opposite-end DR equipment and the second DR interface activity degree of the opposite-end DR equipment.

By adopting the fault processing method provided by the embodiment of the application, when the IPL link fault is detected, the DR equipment with better performance in the current main-standby DR equipment is determined to be the new main DR equipment, so that the higher performance of the system after the fault can be ensured, and the service flow can be ensured to be the best performance.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description will briefly describe the drawings that are required to be used in the embodiments of the present application or the description in the prior art, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may also be obtained according to these drawings of the embodiments of the present application for a person having ordinary skill in the art.

FIG. 1 is a detailed flowchart of a fault handling method according to an embodiment of the present disclosure;

fig. 2 is a schematic structural diagram of a fault handling apparatus according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of another fault handling apparatus according to an embodiment of the present application.

Detailed Description

The terminology used in the embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to any or all possible combinations including one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in embodiments of the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. Depending on the context, furthermore, the word "if" used may be interpreted as "at … …" or "at … …" or "in response to a determination".

Exemplary, referring to fig. 1, a detailed flowchart of a fault handling method according to an embodiment of the present application is provided, where the method is applied to a distributed resilient network interconnect (Distributed Resilient Network Interconnect, DRNI) system, and the method includes the following steps:

step 100: and acquiring the link number of non-fault links included in each DR interface of the DR equipment of the opposite terminal and the DR interface activity degree to calculate the weight value.

In this embodiment of the present application, a command line drni activity weight-value command may be added in advance under a DR interface of a DR device, so as to configure the activity computing weight of the DR interface. Default configuration on DR device: drni activity weight-value 1. The higher the configuration value, the more important the user considers the traffic carried by the DR interface. The types of the services carried under the same DR interface are the same, and theoretically, the DR interface liveness calculation weight configuration is required to be the same.

In practical application, the DR device may transmit the dr_activity_weight_value of each DR interface to the neighbor DR device (the peer DR device) through the IPL link based on the preset transmission period, and then the home terminal DR device may also receive the dr_activity_weight_value of each DR interface of the peer DR device transmitted through the IPL link based on the preset transmission period. Meanwhile, each DR device may also transmit the number of links currently available to each DR interface to the peer DR device through the IPL link.

In this embodiment of the present application, when obtaining the number of links of the non-failure link included in each DR interface of the opposite DR device and the DR interface activity calculation weight value, a preferred implementation manner is:

Preferably, the extended DRCPDU packet is defined with a new TLV field, where the Value field of the new TLV field includes a linked list of each DR interface and a weight Value calculated by the activity of each DR interface.

Specifically, the dr_activity_weight_value is transmitted to the neighboring DRNI device through the following two TLVs, and the same set of DR interfaces takes a configuration maximum Value for calculating the DR Activity.

+TYPE 24–New Home Ports Informatin TLV

+TYPE 25-New Neighbor Ports Information TLV

The message format is as follows:

New Home Ports Information TLV

TLV Type: the local port information type has a value of 24.TLV Length: the data length (type and length fields without header) of the subsequent local port information is represented, and the value of this field is 5+4×pn (the number of active aggregation ports). type+Length is 2 bytes total, with the upper 6 bits representing Type and the lower 10 bits representing Length.

Dr_activity_weight_value: the DR interface activity calculation weight is represented by 1 byte, the upper 3 bits represent weight values 0-7, the lower 5 bits are reserved, and the default is 0.

Home_DR_Aggregate_information: the DR interface information of the local DRNI System is 2 bytes in total, the high 2 bits indicate System Number, the low 14 bits indicate DRNI GROUP ID, and the default is 0.

New_Home_Opter_Partner_Aggregater_Key: and an operation KEY used when interacting LACP messages with the opposite terminal.

Active_home_ports: and (3) a linked list of Active aggregation member ports in the local DRNI system is arranged according to the ascending order of the priority of the Active aggregation ports (Active ports) and the Port IDs during encapsulation.

New Neighbor Ports Information

TLV Type: the local port information type has a value of 25.TLV Length: the data length (type and length fields without header) of the subsequent local port information is represented, and the value of this field is 5+4×pn (the number of active aggregation ports). type+Length is 2 bytes total, with the upper 6 bits representing Type and the lower 10 bits representing Length.

Neighbor_dr_agregator_information: the DR interface information of the neighboring DRNI System is 2 bytes, the upper 2 bits indicate System Number, the lower 14 bits indicate DRNI GROUP ID, and the default is 0.

Neighbor_operator_partner_agager_key: the neighbor DRNI is used for operating the KEY when interacting LACP messages with the opposite terminal.

Active_home_ports: and (3) a linked list of Active aggregation member ports in the neighbor DRNI system is arranged according to the ascending order of the priority of the Active aggregation ports (Active ports) and the Port IDs during encapsulation.

Step 110: when IPL link failure is detected, calculating a weight value based on the link number of non-failure links and DR interface liveness of each DR interface of the opposite-end DR equipment, calculating the first DR interface liveness of the opposite-end DR equipment, and calculating the second DR interface liveness of the opposite-end DR equipment.

In this embodiment of the present application, when calculating the weight value based on the number of links and the DR interface liveness of the non-faulty links included in each DR interface of the opposite DR device, and calculate the first DR interface liveness of the opposite DR device, a preferred implementation manner is:

calculating weight values based on the number of active member ports of each DR group of the opposite terminal equipment and the DR interface liveness of the corresponding DR group, and respectively calculating the DR interface liveness of each DR group; and taking the sum of the DR interface liveness of each DR group as the DR interface liveness of the opposite terminal equipment.

For example, DR interface liveness is calculated according to user configuration in the following manner:

DR Activity＝(Active Port*Weight Value)+(…)+(Active Port*Weight Value)

examples are as follows:

the DR group 2 active member port of the DR equipment 1 of the System Number 1 is 3, and the weight value is 1; the DR group 3 active member port is 3, and the weight value is 2;

the DR group 2 active member port of the DR equipment 2 of the System Number 2 is 4, and the weight value is 1; the DR group 3 active member port is 3, and the weight value is 3.

The DRNI systems DR group 3 at two sides are different in configuration weight value, and after DRCPDU messages are interacted, 3 is found to be needed to be taken as the calculation weight. DR device 1 calculates DR activity= (3*1) + (3*3) =12. DR device 2 calculates DR activity= (4*1) + (3*3) =13.

Therefore, the DR interface of the DR equipment of System Number 2 has higher activity.

	System Number	1	2
				DR group ID
2	Active Port	3	4
					Weight Value	1	1
3	Active Port	3	3
					Weight Value	3	3
	DR Activity	12	13

Step 120: and adjusting the roles of the DR equipment based on the first DR interface activity degree of the opposite-end DR equipment and the second DR interface activity degree of the opposite-end DR equipment.

In this embodiment of the present application, when adjusting the role of the DR device based on the first DR interface activity of the opposite DR device and the second DR interface activity of the opposite DR device, a preferred implementation manner is:

Specifically, when the IPL fails and the Keepalive link UP interacts with the Keepalive message to calculate the device role through the Keepalive link, the following factors are compared in sequence:

(1) Comparing the states of all DR ports of the equipment, wherein one end with a workable DR port is superior;

(2) Comparing the roles before calculation, and if one end is Primary and the other end is None, optimizing the Primary end;

(3) Comparing the DRNI MAD DOWN state, if one end has an interface in the DRNI MAD DOWN state and the other end does not have an interface in the DRNI MAD DOWN state, the end of the interface in the DRNI MAD DOWN state is not optimal;

(4) The health condition of the equipment is compared, and the smaller the health value is, the better the health value is.

(5) Comparing the activity of the DR interface, wherein the larger the numerical value is, the more active and the better the DR system is;

(6) Comparing the role priority of the equipment, wherein the higher the role priority is, the better the role priority is;

(7) The smaller and the better the device bridge MAC is compared.

The above factors are compared in order, and the character at one end with the best result is calculated as Primary, and the character at the other end is second.

An exemplary embodiment of a fault handling apparatus according to the present application is shown in fig. 2, and the apparatus is applied to a distributed resilient network interconnect DRNI system, and includes:

an obtaining unit 20, configured to obtain the number of links of the non-failure link included in each DR interface of the opposite DR device and a DR interface activity calculation weight value;

a calculating unit 21, configured to calculate, when an IPL link failure is detected, a first DR interface activity level of the opposite DR device based on a link number of non-failure links included in each DR interface of the opposite DR device and a DR interface activity level, and calculate a second DR interface activity level of the opposite DR device;

and the adjusting unit 22 is configured to adjust the role of the DR device based on the first DR interface activity of the peer DR device and the second DR interface activity of the peer DR device.

Optionally, when acquiring the number of links of the non-failure link included in each DR interface of the peer DR device and the DR interface activity calculating weight value, the acquiring unit 20 is specifically configured to:

Optionally, when calculating the first DR interface activity of the peer DR device based on the number of links of the non-faulty links included in each DR interface of the peer DR device and the DR interface activity calculating weight, the calculating unit 21 is specifically configured to:

Optionally, when the role of the DR device is adjusted based on the first DR interface activity of the peer DR device and the second DR interface activity of the peer DR device, the adjusting unit 22 is specifically configured to:

The above units may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), or one or more microprocessors (digital singnal processor, abbreviated as DSP), or one or more field programmable gate arrays (Field Programmable Gate Array, abbreviated as FPGA), or the like. For another example, when a unit is implemented in the form of a processing element scheduler code, the processing element may be a general purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processor that may invoke the program code. For another example, the units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

Further, in the fault handling apparatus provided in the embodiments of the present application, from a hardware level, a hardware architecture schematic diagram of the fault handling apparatus may be shown in fig. 3, and the fault handling apparatus may include: a memory 30 and a processor 31,

the memory 30 is used for storing program instructions; the processor 31 invokes the program instructions stored in the memory 30 to execute the above-described method embodiments in accordance with the obtained program instructions. The specific implementation manner and the technical effect are similar, and are not repeated here.

Optionally, the present application further provides a DR device comprising at least one processing element (or chip) for performing the above-described method embodiments.

Optionally, the present application also provides a program product, such as a computer readable storage medium, storing computer executable instructions for causing the computer to perform the above-described method embodiments.

Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that may contain or store information, such as executable instructions, data, or the like. For example, a machine-readable storage medium may be: RAM (Radom Access Memory, random access memory), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), a solid state drive, any type of storage disk (e.g., optical disk, dvd, etc.), or a similar storage medium, or a combination thereof.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present application.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Moreover, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The foregoing description of the preferred embodiments of the present invention is not intended to limit the invention to the precise form disclosed, and any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention are intended to be included within the scope of the present invention.

Claims

1. A method for fault handling, applied to a distributed resilient network interconnect, DRNI, system, the method comprising:

based on the first DR interface activity degree of the opposite terminal DR equipment and the second DR interface activity degree of the opposite terminal DR equipment, taking the DR interface activity degree of each DR equipment as one of calculation factors, calculating the priority of each DR equipment, taking the DR equipment with high priority as a main DR equipment, and taking the DR equipment with low priority as a standby DR equipment.

2. The method of claim 1, wherein the step of obtaining the number of links of the non-failed links included in each DR interface of the peer DR device and the DR interface activity calculation weight value comprises:

3. The method of claim 2, wherein the extended DRCPDU message defines a new TLV field, and wherein a Value field of the new TLV field includes a linked list of each DR interface and a weight Value for each DR interface activity calculation.

4. The method of any of claims 1-3, wherein calculating the first DR interface activity of the peer DR device based on a number of links of non-failed links included in each DR interface of the peer DR device and DR interface activity calculation weight value comprises:

calculating weight values based on the number of active member ports of each DR group of the opposite DR equipment and the DR interface liveness of the corresponding DR group, and respectively calculating the DR interface liveness of each DR group;

and taking the sum of the DR interface liveness of each DR group as the DR interface liveness of the opposite-end DR equipment.

5. A fault handling apparatus for use in a distributed resilient network interconnect, DRNI, system, the apparatus comprising:

and the adjusting unit is used for calculating the priority of each DR device by taking the DR interface activity of each DR device as one of calculation factors based on the first DR interface activity of the opposite DR device and the second DR interface activity of the opposite DR device, and taking the DR device with the higher priority as a main DR device and the DR device with the lower priority as a standby DR device.

6. The apparatus of claim 5, wherein when acquiring the number of links of the non-failure links included in each DR interface of the peer DR device and the DR interface activity calculating weight value, the acquiring unit is specifically configured to:

7. The apparatus of claim 6, wherein the extended DRCPDU message defines a new TLV field, wherein a Value field of the new TLV field includes a linked list of each DR interface and a weight Value for each DR interface activity calculation.

8. The apparatus as claimed in any one of claims 5 to 7, wherein when calculating the first DR interface activity of the peer DR device based on a link number of non-failed links included in each DR interface of the peer DR device and a DR interface activity calculation weight value, the calculating unit is specifically configured to: