CN117221112A

CN117221112A - Intelligent recovery method of pipe-removing equipment and related equipment

Info

Publication number: CN117221112A
Application number: CN202311211958.0A
Authority: CN
Inventors: 王泽伟; 胡文军; 颜昌隆
Original assignee: Fiberhome Telecommunication Technologies Co Ltd
Current assignee: Fiberhome Telecommunication Technologies Co Ltd
Priority date: 2023-09-19
Filing date: 2023-09-19
Publication date: 2023-12-12

Abstract

The invention provides an intelligent recovery method of a pipe-off device and related devices. The method comprises the following steps: when the route communication between the first equipment and the management and control center is abnormal, the first equipment generates a pre-management configuration based on the management configuration of the second equipment and sends the pre-management configuration to the second equipment; the second equipment checks the pre-management configuration to obtain a first check result; the second device sends the pre-management configuration to the management and control center so that the management and control center can check the pre-management configuration to obtain a second check result returned by the management and control center; when the first check result and the second check result are successful, the second equipment sends a check passing notification to the first equipment; and after the first equipment receives the notification that the verification is passed, configuring the pre-management configuration to the local end so as to enable the first equipment to recover the routing communication with the management and control center based on the pre-management configuration. By the method and the device, the management configuration is automatically detected and updated, so that the labor cost is greatly reduced, and the communication recovery efficiency is improved.

Description

Intelligent recovery method of pipe-removing equipment and related equipment

Technical Field

The invention relates to the technical field of communication, in particular to a method for intelligently recovering out-of-pipe equipment and related equipment.

Background

At present, after the equipment is out of management, an operator is required to log in a management and control interface, find out the out-of-management equipment, check topology information of the out-of-management equipment, inquire information of abnormal equipment, and issue management configuration again, so that communication is restored. In this way, not only the labor cost is high, but also the efficiency is low, so a technology capable of reducing the labor cost and improving the communication recovery efficiency after the equipment is taken out of the pipe is needed.

Disclosure of Invention

The invention mainly aims to provide an intelligent recovery method of a pipe-off device and related equipment, and aims to solve the problems of high labor cost and low efficiency in the recovery of communication after the pipe-off of the device in the prior art.

In a first aspect, the present invention provides a method for intelligently recovering a pipe-off device, where the method for intelligently recovering the pipe-off device includes:

when the route communication between the first equipment and the management and control center is abnormal, the first equipment acquires the management configuration of the second equipment, wherein the first equipment is adjacent to the second equipment;

the first device generates a pre-management configuration based on the management configuration of the second device and sends the pre-management configuration to the second device;

the second device checks the pre-management configuration to obtain a first check result;

The second device sends the pre-management configuration to the management and control center so that the management and control center can check the pre-management configuration to obtain a second check result returned by the management and control center;

when the first check result and the second check result are successful, the second equipment sends a check passing notification to the first equipment;

and after the first equipment receives the notification that the verification is passed, configuring the pre-management configuration to the local end so as to enable the first equipment to recover the routing communication with the management and control center based on the pre-management configuration.

Optionally, the pre-management configuration includes an IP address, and the step of generating, by the first device, the pre-management configuration based on the management configuration of the second device includes:

if the first equipment acquires the management configuration of the second equipment through the Ethernet interface, the first equipment generates the same network segment address according to the IP address of the second equipment and the destination network address in the routing information of the second equipment;

the first device randomly generates a host address based on the serial number of the first device;

and combining the same network segment address and the host address to generate an IP address.

Optionally, the step of verifying the pre-management configuration by the second device to obtain a first verification result includes:

When the second equipment receives the pre-management configuration sent by the first equipment through the Ethernet interface, the second equipment detects whether the IP address contained in the pre-management configuration and the IP address of the second equipment are identical in network segment and repeat;

if the same network segment is not repeated, a first check result is obtained successfully;

if the network segment is not the same network segment and/or is repeated, the first check result is obtained as failure.

Optionally, the pre-management configuration further includes port information, and the step of sending, by the second device, the pre-management configuration to the management and control center, so that the management and control center checks the pre-management configuration to obtain a second check result returned by the management and control center includes:

the second device sends the pre-management configuration to a management and control center;

when the port information contained in the pre-management configuration is an Ethernet interface, the management and control center detects whether the IP address contained in the pre-management configuration and the IP address of the second device are identical in network segment and repeat;

if the same network segment is not repeated, the second equipment obtains a second check result returned by the management and control center as success;

if the network segment is not the same network segment and/or is repeated, the second equipment obtains a second check result returned by the management and control center as failure.

if the first device obtains the management configuration of the second device through the non-Ethernet interface, the first device randomly generates different network segment addresses and host addresses based on the serial numbers of the first device, and combines the different network segment addresses and the host addresses to generate the IP address.

when the second equipment receives the pre-management configuration sent by the first equipment through the non-Ethernet interface, the second equipment detects whether the IP address contained in the pre-management configuration and the destination network address in the second equipment route are identical in network segment and repeat;

if the first verification result is not the same network segment and is not repeated, the first verification result is obtained successfully;

if the same network segment and/or the same network segment are repeated, the first check result is obtained as failure.

when the port information contained in the pre-management configuration is a non-Ethernet interface, the management and control center detects whether the IP address contained in the pre-management configuration and the IP addresses of other devices of the management and control center are the same network segment and are repeated;

if the network segment is not the same network segment and is not repeated, the second equipment obtains a second check result returned by the management and control center as success;

if the same network segment and/or the same network segment is repeated, the second equipment obtains a second check result returned by the management and control center as failure.

Optionally, after the step of sending the pre-management configuration to the management and control center by the second device to check the pre-management configuration by the management and control center to obtain the second check result returned by the management and control center, the method includes:

when the second verification result is failure, if the second equipment receives a first recommended IP address issued by the management and control center, the second equipment verifies the first recommended IP address to obtain a third verification result;

if the third checking result is successful, the first recommended IP address is sent to first equipment;

when the first verification result is failure and the second equipment does not receive the first recommended IP address issued by the management and control center, or the first verification result is failure and the third verification result is failure, the second equipment generates a second recommended IP address and sends the second recommended IP address to the management and control center, and the second recommended IP is verified through management and control to obtain a fourth verification result replied by the management and control center;

If the fourth checking result is successful, the second recommended IP address is sent to the first device;

and if the second equipment does not generate the second recommended IP address, returning to the step of executing the management configuration of the second equipment acquired by the first equipment until the circulation times reach the preset times.

Optionally, before the step of obtaining, by the first device, the management configuration of the second device when the routing communication between the first device and the management center is abnormal, the method includes:

detecting whether the first equipment meets a routing communication abnormal condition with the management and control center, wherein the routing communication abnormal condition with the management and control center comprises any one of the following steps:

the first device has no IP address;

the first device has an IP address but no routing information for the second device;

the first equipment has no information of the management center;

if yes, determining that the route communication between the first equipment and the management and control center is abnormal.

In a second aspect, the present invention further provides a device for intelligently recovering a pipe-off device, where the device for intelligently recovering the pipe-off device includes:

the acquisition module is used for acquiring the management configuration of the second equipment when the route communication between the first equipment and the management and control center is abnormal, wherein the first equipment is adjacent to the second equipment;

The generation module is used for generating a pre-management configuration by the first equipment based on the management configuration of the second equipment and sending the pre-management configuration to the second equipment;

the first verification module is used for verifying the pre-management configuration by the second equipment to obtain a first verification result;

the second verification module is used for sending the pre-management configuration to the management and control center by the second equipment so as to enable the management and control center to verify the pre-management configuration to obtain a second verification result returned by the management and control center;

the information transmission module is used for sending a verification passing notification to the first device by the second device when the first verification result and the second verification result are successful;

and the configuration module is used for configuring the pre-management configuration to the local end after the first equipment receives the notification of passing the verification, so that the first equipment can recover the routing communication with the management and control center based on the pre-management configuration.

In a third aspect, the present invention further provides an apparatus for intelligently recovering an out-of-pipe apparatus, where the apparatus for intelligently recovering an out-of-pipe apparatus includes a processor, a memory, and a program for intelligently recovering an out-of-pipe apparatus stored on the memory and executable by the processor, where the program for intelligently recovering an out-of-pipe apparatus, when executed by the processor, implements the steps of the method for intelligently recovering an out-of-pipe apparatus as described above.

In a fourth aspect, the present invention further provides a readable storage medium, where a program for intelligently recovering an out-of-pipe device is stored on the readable storage medium, where when the program for intelligently recovering an out-of-pipe device is executed by a processor, the steps of the method for intelligently recovering an out-of-pipe device described above are implemented.

In the invention, when the route communication between the first equipment and the management and control center is abnormal, the first equipment acquires the management configuration of the second equipment, wherein the first equipment is adjacent to the second equipment; the first device generates a pre-management configuration based on the management configuration of the second device and sends the pre-management configuration to the second device; the second device checks the pre-management configuration to obtain a first check result; the second device sends the pre-management configuration to the management and control center so that the management and control center can check the pre-management configuration to obtain a second check result returned by the management and control center; when the first check result and the second check result are successful, the second equipment sends a check passing notification to the first equipment; and after the first equipment receives the notification that the verification is passed, configuring the pre-management configuration to the local end so as to enable the first equipment to recover the routing communication with the management and control center based on the pre-management configuration. According to the invention, the first equipment which is disconnected from the management control center generates the pre-management configuration of the first equipment by learning the management configuration of the adjacent second equipment which is not disconnected from the management control center, and after the pre-management configuration generated by the first equipment is checked by the second equipment and the management control center, the second equipment and the management control center can restore the route communication with the management control center based on the pre-management configuration after the pre-management configuration is checked by the second equipment and the management control center, so that the management configuration is automatically detected and updated, the labor cost is greatly reduced, and the communication restoration efficiency is improved.

Drawings

FIG. 1 is a schematic flow chart of a first embodiment of a method for intelligent recovery of a tube-removing device according to the present invention;

FIG. 2 is a schematic diagram of a first refinement procedure of step S30 in FIG. 1;

FIG. 3 is a schematic diagram of a first refinement procedure of step S40 in FIG. 1;

FIG. 4 is a schematic diagram of a second refinement procedure of step S30 in FIG. 1;

FIG. 5 is a schematic diagram of a second refinement procedure of step S40 in FIG. 1;

FIG. 6 is a flowchart of a second embodiment of a method for intelligent recovery of a tube removal device according to the present invention;

FIG. 7 is a schematic diagram of functional modules of an embodiment of an apparatus for intelligent recovery of a pipe-off device according to the present invention;

fig. 8 is a schematic hardware structure diagram of an apparatus for intelligent recovery of a pipe-off apparatus according to an embodiment of the present invention.

The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

In a first aspect, an embodiment of the present invention provides a method for intelligently recovering a pipe-off device.

In an embodiment, referring to fig. 1, fig. 1 is a flowchart of a first embodiment of a method for intelligent recovery of a pipe-off device according to the present invention. As shown in fig. 1, the method for intelligently recovering the pipe-off equipment includes:

Step S10, when the route communication between the first equipment and the management and control center is abnormal, the first equipment acquires the management configuration of the second equipment, wherein the first equipment is adjacent to the second equipment;

in this embodiment, the routing is the activity of transmitting information from a source address to a destination address through an interconnection network, when the routing communication between the first device and the management and control center is abnormal, the first device sends a management configuration learning message to all adjacent second devices through an ethernet interface or a non-ethernet interface, the second devices capable of communicating with the management and control center reply to the learning message of the first device, and the reply message includes the management configuration of the second devices. The management configuration includes a serial number of the second device, an IP address of the second device, OSPF instance information of the second device, router-id information of the second device, domain information of the second device, port information of the second device (including domain information where the port is located), routing information of the second device, and an IP address of the management and control center.

Step S20, the first device generates a pre-management configuration based on the management configuration of the second device and sends the pre-management configuration to the second device;

in this embodiment, after receiving all the messages replied by the second devices adjacent to the management and control center through the ethernet interface or the non-ethernet interface, the first device first clears the management configuration except the self-curing information, then generates the pre-management configuration based on the management configuration of the second devices, and sends the generated pre-management configuration to the second devices. When the first device sends the generated preconditioning configuration to the second device, if the ethernet interface and the non-ethernet interface of the first device both find the same second device, the preconditioning configuration is preferably sent from the non-ethernet interface to the second device, and the ethernet interface does not send the preconditioning configuration.

The pre-management configuration includes a serial number, an IP address, OSPF instance information, router-id information, domain information, port information, domain information where the port is located, routing information, and an IP address of the management and control center. The serial number included in the pre-management configuration is the solidification information, and the serial number of the first device is directly read;

the method comprises the steps that IP addresses are included in the pre-management configuration, a first device generates a same network segment address according to a second device IP address and a destination network address in second device routing information, then a host address is randomly generated based on a sequence number of the first device, the same network segment address and the host address are combined to generate the IP address, or the first device generates different network segment addresses and host addresses randomly based on the sequence number of the first device, and then the different network segment addresses and the host address are combined to generate the IP address;

the OSPF instance information included in the pre-management configuration is consistent with the OSPF of the second device;

the router-id information included in the pre-management configuration is consistent with the IP of the first device;

the domain information included in the pre-management configuration is consistent with the domain information of the second device (the domain information of the second device port);

the pre-management configuration includes port information including an ethernet interface or a non-ethernet interface generated by the first device.

The domain information of the port included in the pre-management configuration is consistent with the domain information of the port of the first device, namely, the second device and the port connected with the first device are in the same domain, the connection port of the first device is added to the domain, the connection ports of the second device and the first device are in the same domain, if the connection port of the second device is not added with the domain, the connection port of the first device is not added with the domain, if different ports of the first device find different second devices, and destination networks in the routing information of the second devices are the same, the first device only selects one of the ports to be added with the domain.

Specifically, the first device receives, through the ethernet interface, all messages replied by the second device adjacent to the management and control center, if the management and control center IP:192.168.1.1/24;

IP of device 1: 192.168.1.2/24;

IP of device 2: 192.168.1.3/24;

management configuration of the second device:

sequence number: 123456789;

IP address: 192.168.1.4/24;

OSPF instance information: none (ethernet scenario not considered);

router-id information: none (ethernet scenario not considered);

domain information: none (ethernet scenario not considered);

port information: ethernet 1 (Ethernet interface);

Routing information: 192.168.1.0/24 (destination network address);

managed IP information: 192.168.1.1/24;

first device management configuration:

sequence number: 123456788;

IP address: temporarily no;

OSPF instance information: none (ethernet scenario not considered);

router-id information: none (ethernet scenario not considered);

domain information: none (ethernet scenario not considered);

port information: ethernet 2 (Ethernet interface);

routing information: temporarily no;

managed IP information: temporarily no;

the first device generates a pre-management configuration based on the management configuration of the second device:

sequence number: 123456788;

IP address: 192.168.1.5/24;

OSPF instance information: none (ethernet scenario not considered);

router-id information: none (ethernet scenario not considered);

domain information: none (ethernet scenario not considered);

port information: ethernet 2 (Ethernet interface);

routing information: temporarily no;

managed IP information: 192.168.1.1/24.

The first device receives all messages replied by the adjacent second devices capable of communicating with the management and control center through the non-Ethernet interface, if the IP address of the management and control center is: 192.168.1.1/24;

managing and controlling a central gateway address: 192.168.1.100;

IP address of device 1: 192.168.1.100/24;

IP address of device 2: 192.168.3.1/24;

second device management configuration:

sequence number: 123456789;

IP address: 192.168.4.1/24;

OSPF instance information: 1000;

router-id information: 192.168.4.1;

domain information: 0.0.0.0;

port information: 0/1/0/1;

location domain information: 0.0.0.0;

routing information (destination network address):

192.168.1.0/24

192.168.3.0/24

192.168.4.0/24

managed IP information: 192.168.1.1/24;

first device management configuration:

sequence number: 123456788;

IP address: temporarily no;

OSPF instance information: the method is free;

router-id information: the method is free;

domain information: the method is free;

port information: 0/1/0/2;

routing information: temporarily no;

managed IP information: temporarily no;

sequence number: 123456788;

IP address: 192.168.5.1/24;

OSPF instance information: 1000;

router-id information: 192.168.5.1;

domain information: 0.0.0.0;

port information: 0/1/0/2;

location domain information: 0.0.0.0;

routing information: temporary absence (IP validation is generated);

managed IP information: 192.168.1.1/24.

Step S30, the second equipment checks the pre-management configuration to obtain a first check result;

in this embodiment, after receiving the pre-management configuration sent by the first device through the ethernet interface or the non-ethernet interface, the second device checks the pre-management configuration, so as to obtain a first check result.

Step S40, the second equipment sends the pre-management configuration to the management and control center so that the management and control center can check the pre-management configuration to obtain a second check result returned by the management and control center;

in this embodiment, after receiving the pre-management configuration sent by the first device, the second device further sends the pre-management configuration to the management and control center, and the management and control center verifies the pre-management configuration to obtain a second verification result returned by the management and control center.

Step S50, when the first check result and the second check result are successful, the second equipment sends a check passing notification to the first equipment;

in this embodiment, when the first check result and the second check result obtained by the second device are successful, the second device sends a notification that the pre-management configuration check passes to the first device. It should be noted that, the first check result and the second check result are both successful, and the pre-management configuration check is passed. If the first check result and/or the second check result is failure, the pre-management configuration check is not passed.

Step S60, after the first device receives the notification that the verification is passed, the first device configures the pre-management configuration to the local end so that the first device can recover the routing communication with the management and control center based on the pre-management configuration.

In this embodiment, after receiving the notification that the pre-management configuration check passes, the first device configures the pre-management configuration to the local end, and because the pre-management configuration is basically ospf configuration, a route is generated through an ospf protocol, so after the synchronization of the whole routing network, the first device can recover the routing communication with the management and control center based on the pre-management configuration.

In this embodiment, when the route communication between the first device and the management and control center is abnormal, the first device obtains the management configuration of the second device, where the first device is adjacent to the second device; the first device generates a pre-management configuration based on the management configuration of the second device and sends the pre-management configuration to the second device; the second device checks the pre-management configuration to obtain a first check result; the second device sends the pre-management configuration to the management and control center so that the management and control center can check the pre-management configuration to obtain a second check result returned by the management and control center; when the first check result and the second check result are successful, the second equipment sends a check passing notification to the first equipment; and after the first equipment receives the notification that the verification is passed, configuring the pre-management configuration to the local end so as to enable the first equipment to recover the routing communication with the management and control center based on the pre-management configuration. According to the embodiment, the first device which is disconnected from the management control center generates the pre-management configuration of the first device by learning the management configuration of the adjacent second device which is not disconnected from the management control center, and after the pre-management configuration generated by the first device is checked by the second device and the management control center, the second device and the management control center can restore the route communication with the management control center based on the pre-management configuration after the pre-management configuration is checked by the second device and the management control center, so that the automatic detection and updating of the management configuration can greatly reduce the labor cost and improve the communication restoration efficiency.

Further, in an embodiment, the pre-management configuration includes an IP address, and the step of generating, by the first device, the pre-management configuration based on the management configuration of the second device includes:

In this embodiment, if the first device receives the packets replied by all the neighboring second devices through the ethernet interface, that is, the first device obtains the management configuration of all the neighboring second devices through the ethernet interface, the first device generates the same network segment address according to the IP addresses of all the second devices and the destination network address in the routing information of the second devices. Specifically, if the first device has two adjacent second devices, the IPV4 addresses of the two adjacent second devices are 192.168.2.1/24 and 192.168.2.3/24, respectively, and the destination network address in the second device routing information includes 192.168.2.0/24, then an address 192.168.2.0/24 of the same network segment as the IP address of the second device is generated.

The first device then randomly generates host addresses within 1-255 using its own serial number as a random seed, and is different from the host addresses (1, 3) of all neighboring second devices, such as 6.

The IP address 192.168.2.6/24 is generated by combining the address 192.168.2.0/24 of the same network segment as the IP address of the second device with the host address 6.

Further, referring to fig. 2, fig. 2 is a schematic diagram of a first refinement procedure of step S30 in fig. 1. As shown in fig. 2, step S30 includes:

step S301, when the second device receives the pre-management configuration sent by the first device through the Ethernet interface, the second device detects whether the IP address contained in the pre-management configuration and the IP address of the second device are in the same network segment and are repeated;

step S302, if the same network segment is not repeated, a first check result is obtained as success;

step S303, if the same network segment is not established and/or repeated, the first verification result is failure.

In this embodiment, if the second device receives the pre-management configuration sent by the first device through the ethernet interface, the second device detects whether the IP address included in the pre-management configuration and the IP address of the second device are identical to the network segment and are repeated, and if the IP address is identical to the network segment and is not repeated, the first check result is obtained successfully. If the network segment is not the same network segment and/or is repeated, the first check result is obtained as failure.

Specifically, taking the IP address of the second device as 192.168.6.1/24 as an example, if the IP address included in the pre-management configuration is 192.168.6.8/24, the second device detects that the IP address included in the pre-management configuration and the IP address of the second device are the same network segment and are not repeated, and then the first verification result is obtained as success. If the IP address contained in the pre-management configuration is 192.168.5.8/24, the second device detects that the IP address contained in the pre-management configuration and the IP address of the second device are not the same network segment, and the first verification result is failure.

It should be noted that, when the first device has a plurality of adjacent second devices capable of communicating with the management and control center, the detection results of all the second devices are that the IP address included in the pre-management configuration and the IP address of the second device are the same network segment and are not repeated, so that the first verification result is successful. If the detection result of any second device is that the IP address contained in the pre-management configuration and the IP address of the second device are not the same network segment and/or are repeated, the first verification result is obtained as failure.

Further, in an embodiment, the pre-management configuration further includes port information, referring to fig. 3, fig. 3 is a schematic diagram of a first refinement flow in step S40 in fig. 1. As shown in fig. 3, step S40 includes:

Step S401, the second device sends the pre-management configuration to a management and control center;

step S402, when the port information contained in the pre-management configuration is an Ethernet interface, the management and control center detects whether the IP address contained in the pre-management configuration and the IP address of the second device are the same network segment and are repeated;

step S403, if the same network segment is not repeated, the second equipment obtains a second check result returned by the control center as success;

step S404, if the network segment is not the same and/or the network segment is repeated, the second device obtains a second check result returned by the control center as failure.

In this embodiment, the second device sends the pre-management configuration generated by the first device to the management and control center, where the management and control center detects port information included in the pre-management configuration, and if the port information included in the pre-management configuration is an ethernet interface, the management and control center detects whether the IP address included in the pre-management configuration and the IP address of the second device are identical to each other and are repeated. If the same network segment is not repeated, the second equipment obtains a second check result returned by the management and control center, and the second check result is successful. If the network segment is not the same network segment and/or is repeated, the second equipment obtains a second check result returned by the management and control center as failure.

Specifically, taking the IP address of the second device as 192.168.6.1/24 as an example, if the IP address included in the pre-management configuration is 192.168.6.5/24, the management center detects that the IP address included in the pre-management configuration and the IP address of the second device are the same network segment and are not repeated, and the second device obtains the second check result replied by the management center as success. If the IP address contained in the pre-management configuration is 192.168.6.1/24, the management and control center detects that the IP address contained in the pre-management configuration is repeated with the IP address of the second device, and the second device obtains a second check result returned by the management and control center to be failure.

In this embodiment, if the first device receives the messages replied by all the neighboring second devices through the non-ethernet interface, that is, the first device obtains the management configuration of all the neighboring second devices through the non-ethernet interface, the first device randomly generates different network segment addresses and host addresses based on the own serial numbers. Specifically, if the first device has two adjacent second devices, the IPV4 addresses of the two adjacent second devices are 192.168.2.1/24 and 192.168.4.3/24, respectively, and the destination network addresses in the second device routing information include 192.168.2.0/24 and 192.168.4.0/24, the first device uses its own serial number as a random seed to randomly generate addresses 192.168.6.0/24 of different network segments from the IP addresses (192.168.2.1/24 and 192.168.4.3/24) of all the adjacent second devices. The first device then randomly generates a host address, such as 8, within 1-255 using its own serial number as a random seed. The IP address 192.168.6.8/24 is generated by combining the host address 8 and the segment address 192.168.6.0/24 which is different from the IP addresses of all the neighboring second devices.

Further, referring to fig. 4, fig. 4 is a schematic diagram of a second refinement procedure of step S30 in fig. 1. As shown in fig. 4, step S30 includes:

step S311, when the second device receives the pre-management configuration sent by the first device through the non-Ethernet interface, the second device detects whether the IP address contained in the pre-management configuration and the destination network address in the second device route are the same as the network segment and are repeated;

step S312, if the first verification result is not the same network segment and is not repeated, the first verification result is obtained as success;

step S313, if the same network segment and/or the same network segment is repeated, the first verification result is obtained as failure.

In this embodiment, if the second device receives the pre-management configuration sent by the first device through the non-ethernet interface, the second device detects whether the IP address included in the pre-management configuration and the destination network address in the second device route are identical to the network segment and are repeated, and if the IP address is not identical to the network segment and is not repeated, the first check result is obtained as success. If the same network segment and/or the same network segment are repeated, the first check result is obtained as failure.

Specifically, taking the IP address of the second device as 192.168.6.1/24 as an example, if the IP address included in the pre-management configuration is 192.168.6.8/24, the second device detects that the IP address included in the pre-management configuration and the IP address of the second device are the same network segment, and then obtains the first check result as failure. If the IP address contained in the pre-management configuration is 192.168.5.8/24, the second device detects that the IP address contained in the pre-management configuration and the IP address of the second device are not the same network segment and are not repeated, and the first check result is obtained as success.

Further, in an embodiment, the pre-management configuration further includes port information, and referring to fig. 5, fig. 5 is a schematic diagram of a second refinement of step S40 in fig. 1. As shown in fig. 5, step S40 includes:

step S411, the second device sends the pre-management configuration to a management and control center;

step S412, when the port information included in the pre-management configuration is a non-ethernet interface, the management and control center detects whether the IP address included in the pre-management configuration and the IP addresses of other devices in the management and control center are the same network segment and repeat;

step S413, if the second device is not the same network segment and is not repeated, the second device obtains a second check result returned by the management and control center as success;

step S414, if the same network segment and/or the same network segment is repeated, the second device obtains the second check result returned by the management and control center as failure.

In this embodiment, the second device sends the pre-management configuration generated by the first device to the management and control center, and the management and control center detects port information included in the pre-management configuration, and if the port information included in the pre-management configuration is a non-ethernet interface, the management and control center detects whether the IP address included in the pre-management configuration and the IP addresses of other devices in the management and control center are identical to the network segment and are repeated. If the IP address contained in the pre-management configuration and the IP addresses of other devices in the management and control center are not the same network segment and are not repeated, the second device obtains a second check result returned by the management and control center as success. If the IP address contained in the pre-management configuration and the IP addresses of other devices in the management and control center are the same network segment and/or are repeated, the second device obtains a second check result returned by the management and control center as failure.

Specifically, taking the example that the IP addresses of other devices in the management and control center are 192.168.2.1/24 and 192.168.3.2/24, if the IP address included in the pre-management configuration is 192.168.4.1/24, the management and control center detects that the IP address included in the pre-management configuration and the IP address of other devices in the management and control center are not the same network segment and are not repeated, and the second device obtains a second verification result returned by the management and control center to be successful. If the IP address contained in the pre-management configuration is 192.168.2.1/24, the management and control center detects that the management and control center has the IP addresses of other devices which are repeated with the IP address contained in the pre-management configuration, and the second device obtains a second check result returned by the management and control center as failure. If the IP address contained in the pre-management configuration is 192.168.3.6/24, the management and control center detects that the management and control center has the IP address of other devices with the same network segment as the IP address contained in the pre-management configuration, and the second device obtains a second check result returned by the management and control center as failure. When the IP addresses of other devices in the management and control center are multiple, the IP addresses contained in the pre-management configuration and the IP addresses of the other devices in the management and control center are not the same network segment and are not repeated, and the second device can obtain a second check result returned by the management and control center as success. If the management and control center has the IP address of any device and the IP address contained in the pre-management configuration are the same network segment and/or are repeated, the second device obtains a second check result returned by the management and control center as failure.

Further, in an embodiment, referring to fig. 6, fig. 6 is a flowchart of a second embodiment of a method for intelligent recovery of a pipe-off device according to the present invention. As shown in fig. 6, after step S40, it includes:

step S110, when the second checking result is failure, if the second equipment receives the first recommended IP address issued by the management and control center, the second equipment checks the first recommended IP address to obtain a third checking result;

step S120, if the third verification result is successful, the first recommended IP address is sent to the first device;

step S130, when the first verification result is failure and the second device does not receive the first recommended IP address issued by the management and control center, or the first verification result is failure and the third verification result is failure, the second device generates a second recommended IP address and sends the second recommended IP address to the management and control center, and the second recommended IP is verified through management and control to obtain a fourth verification result returned by the management and control center;

step S140, if the fourth verification result is successful, the second recommended IP address is sent to the first device;

and step S150, if the second device does not generate the second recommended IP address, returning to the step of executing the management configuration of the second device acquired by the first device until the cycle number reaches the preset number.

In this embodiment, when the second device obtains the second verification result returned by the management and control center as failure, it is checked whether the first recommended IP address issued by the management and control center is received, and if the second device receives the first recommended IP address issued by the management and control center, the second device verifies the first recommended IP address to obtain a third verification result.

Specifically, if the second device receives the first recommended IP address issued by the management and control center and the second device is the pre-management configuration of the first device received through the ethernet interface, the second device detects whether the first recommended IP address and the IP address of the second device are identical to the network segment and are repeated, and if the first recommended IP address and the IP address of the second device are identical to the network segment and are not repeated, a third verification result is obtained to be successful; if the first recommended IP address and the IP address of the second device are not the same network segment and/or are repeated, a third checking result is obtained as failure. If the second device receives the first recommended IP address issued by the management and control center and the second device is the pre-management configuration of the first device received through the non-Ethernet interface, the second device detects whether the first recommended IP address and the destination network address in the second device route are identical to network segments and are repeated, and if the first recommended IP address and the destination network address in the second device route are not identical to network segments and are not repeated, a third verification result is obtained to be successful; if the first recommended IP address and the destination network address in the second equipment route are the same network segment and/or are repeated, a third check result is obtained as failure.

And if the third checking result is successful, the first recommended IP address is sent to the first device, so that the first device can take the first recommended IP address as the IP address contained in the pre-management configuration.

And when the first verification result is failure, if the second equipment generates a second recommended IP address, and when the second equipment does not receive the first recommended IP address issued by the management and control center (the management and control center does not generate the first recommended IP address) or the third verification result is failure, the second recommended IP address generated by the second equipment is sent to the management and control center, and the second recommended IP is verified through management and control to obtain a fourth verification result returned by the management and control center.

And if the fourth checking result is successful, the second device sends the second recommended IP address to the first device. And when the first verification result is failure and the second equipment does not receive the first recommended IP address issued by the management and control center, or when the first verification result is failure and the third verification result is failure, the second recommended IP address generated by the second equipment is sent to the management and control center for verification, a fourth verification result replied by the management and control center is obtained, and if the fourth verification result is successful, the second equipment sends the second recommended IP address to the first equipment. Further, if the fourth verification result is failure, the second device does not generate the second recommended IP address any more, and returns to the step of executing the first device to obtain the management configuration of the second device, that is, the first device regenerates the pre-management configuration until the number of cycles reaches the preset number of times.

And when the first checking result is failure and the second equipment does not receive the first recommended IP address issued by the management and control center, or the first checking result is failure and the third checking result is failure, if the second equipment does not generate the second recommended IP address, returning to the step of executing the first equipment to acquire the management configuration of the second equipment, namely, the first equipment regenerates the pre-management configuration until the cycle number reaches the preset number.

It will be readily appreciated that when the third verification result is successful, the first recommended IP address is sent to the first device as the IP address contained in the pre-management configuration, regardless of whether the second device generates the second recommended IP address. And when the third checking result is failure or the second equipment does not receive the first recommended IP address issued by the management and control center, if the second equipment generates the second recommended IP address, the second recommended IP address is sent to the management and control center for checking, and a fourth checking result is obtained. If the fourth checking result is successful, the second device sends the second recommended IP address to the first device as the IP address contained in the pre-management configuration. I.e. the first recommended IP address has a higher priority than the second recommended IP address, which has a higher priority than the IP address generated by the first device.

Further, in an embodiment, before step S10, the method includes:

the first device has no IP address;

the first equipment has no information of the management center;

In this embodiment, whether the first device has the first device IP address is detected; the first device has an IP address but no routing information for the second device; and if the first equipment does not have any information of the management and control center, the first equipment meets the abnormal condition of the route communication with the management and control center, and the route communication between the first equipment and the management and control center is abnormal.

If the first equipment does not exist, the first equipment has no IP address; the first device has an IP address but no routing information for the second device; and if the first equipment does not have any information of the management and control center, the first equipment does not meet the abnormal condition of the route communication with the management and control center, and the route communication between the first equipment and the management and control center is determined to be normal.

In a second aspect, the embodiment of the invention further provides a device for intelligently recovering the pipe-taking-off equipment.

In an embodiment, referring to fig. 7, fig. 7 is a schematic functional block diagram of an embodiment of an apparatus for intelligent recovery of a pipe-off device according to the present invention. As shown in fig. 7, the device for intelligently recovering the pipe-off equipment includes:

an obtaining module 10, configured to obtain, when a route communication between a first device and a management center is abnormal, a management configuration of a second device by the first device, where the first device is adjacent to the second device;

a generating module 20, configured to generate a pre-management configuration by the first device based on the management configuration of the second device, and send the pre-management configuration to the second device;

a first verification module 30, configured to verify the pre-management configuration by using a second device, to obtain a first verification result;

a second verification module 40, configured to send the pre-management configuration to a management and control center by using a second device, so that the management and control center verifies the pre-management configuration to obtain a second verification result returned by the management and control center;

an information transmission module 50, configured to send a verification passing notification to the first device by the second device when the first verification result and the second verification result are successful;

and the configuration module 60 is configured to configure the pre-management configuration to the local end after the first device receives the notification of passing the verification, so that the first device resumes the routing communication with the management and control center based on the pre-management configuration.

Further, in an embodiment, the pre-management configuration includes an IP address, and the generating module 20 is configured to:

Further, in an embodiment, the first verification module 30 is configured to:

Further, in an embodiment, the pre-management configuration further includes port information, and the second checking module 40 is configured to:

Further, in an embodiment, the first verification module 30 is configured to:

Further, in an embodiment, the second checking module 40 is further configured to:

Further, in an embodiment, the device for intelligently recovering the pipe-removing device further includes a detection module, configured to:

the first device has no IP address;

the first equipment has no information of the management center;

The function implementation of each module in the device for intelligently recovering the pipe-removing equipment corresponds to each step in the method embodiment for intelligently recovering the pipe-removing equipment, and the functions and the implementation process of the device are not described in detail herein.

In a third aspect, an embodiment of the present invention provides an apparatus for intelligently recovering a pipe-out apparatus, where the apparatus for intelligently recovering a pipe-out apparatus may be a device with a data processing function, such as a personal computer (personal computer, PC), a notebook computer, a server, or the like.

Referring to fig. 8, fig. 8 is a schematic hardware structure diagram of an apparatus for intelligent recovery of a pipe-off apparatus according to an embodiment of the present invention. In an embodiment of the present invention, the device for intelligently recovering the out-of-pipe device may include a processor 1001 (e.g. a central processing unit Central Processing Unit, a CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein the communication bus 1002 is used to enable connected communications between these components; the user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard); the network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., WIreless-FIdelity, WI-FI interface); the memory 1005 may be a high-speed random access memory (random access memory, RAM) or a stable memory (non-volatile memory), such as a disk memory, and the memory 1005 may alternatively be a storage device independent of the processor 1001. Those skilled in the art will appreciate that the hardware configuration shown in fig. n is not limiting of the invention and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.

With continued reference to fig. 8, a program for intelligent recovery of the operating system, network communication module, user interface module, and out-of-management device may be included in the memory 1005 of fig. 8, which is a type of computer storage medium. The processor 1001 may call a program for intelligently recovering the pipe-removing device stored in the memory 1005, and execute the method for intelligently recovering the pipe-removing device provided by the embodiment of the invention.

In a fourth aspect, embodiments of the present invention also provide a readable storage medium.

The readable storage medium of the invention stores the program for intelligently recovering the pipe-removing equipment, wherein the program for intelligently recovering the pipe-removing equipment is executed by a processor to realize the steps of the method for intelligently recovering the pipe-removing equipment.

The method implemented when the program for intelligently recovering the pipe-removing device is executed may refer to various embodiments of the method for intelligently recovering the pipe-removing device of the present invention, and will not be described herein.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.

The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above, comprising several instructions for causing a terminal device to perform the method according to the embodiments of the present invention.

The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims

1. The intelligent recovery method of the pipe-off equipment is characterized by comprising the following steps of:

2. The method for intelligent restoration of an out-of-pipe device as set forth in claim 1, wherein the pre-management configuration includes an IP address, and wherein the first device generates the pre-management configuration based on the management configuration of the second device, comprising:

3. The method for intelligently recovering the pipe-out equipment according to claim 2, wherein the step of verifying the pre-management configuration by the second equipment to obtain a first verification result comprises the following steps:

4. The method for intelligently recovering an out-of-management device according to claim 2, wherein the pre-management configuration further includes port information, and the step of the second device sending the pre-management configuration to a management center for the management center to verify the pre-management configuration to obtain a second verification result returned by the management center includes:

5. The method for intelligent restoration of an out-of-pipe device as set forth in claim 1, wherein the pre-management configuration includes an IP address, and wherein the first device generates the pre-management configuration based on the management configuration of the second device, comprising:

6. The method for intelligently recovering the pipe-out equipment according to claim 5, wherein the step of verifying the pre-management configuration by the second equipment to obtain a first verification result comprises the following steps:

7. The method for intelligent recovery of an out-of-management device according to claim 5, wherein the pre-management configuration further includes port information, and the step of the second device sending the pre-management configuration to a management center for the management center to verify the pre-management configuration to obtain a second verification result returned by the management center includes:

8. The method for intelligently recovering an out-of-pipe device according to claim 1, wherein after the step of the second device sending the pre-management configuration to a management center for the management center to verify the pre-management configuration to obtain a second verification result returned by the management center, the method comprises:

9. The method for intelligent restoration of an out-of-pipe device according to claim 1, comprising, before the step of the first device acquiring the management configuration of the second device when the routing communication between the first device and the management center is abnormal:

the first device has no IP address;

the first equipment has no information of the management center;

10. Device that takes off tub equipment intelligence and resumes, a serial communication port, take off tub equipment intelligence and resume's device includes: