Network connectivity fault isolation method

Abstract

The invention relates to a network connectivity fault isolation method, which comprises the following steps of: determining whether all switch ports of a switch in a network lose connectivity or not on the basis of sending a network request message to each airborne device in the network; if all the switch ports of the switches lose connectivity, determining that the corresponding switches have switch faults; and otherwise, based on the fault information reported by the switch, determining the network connectivity fault by determining the port type of the faulted switch. Other aspects of the disclosure also include corresponding apparatus and computer program products.

Description

Technical Field

[0001] The present application relates to airborne networks, and more particularly to airborne network connectivity fault location and isolation. Background Art

[0002] The avionics core processing platform health management function includes fault detection, filtering, isolation, integration, reporting, and fault information confirmation. Fault isolation is a sub-function of the avionics core processing platform health management function, promptly transmitting located fault information to onboard maintenance and other systems.

[0003] Network interoperability failure is a typical fault type. Certain fault isolation logic is required to isolate the fault to specific devices and connections for subsequent troubleshooting.

[0004] Existing fault isolation is directly aimed at airborne equipment, and there are few isolation logic and methods specifically for network connectivity failures.

[0005] Therefore, there is a need in the art for isolation logic and methods for network connectivity faults to locate the type of network connectivity faults in the airborne network and isolate the network connectivity faults, thereby achieving the effect of locating and isolating the network connectivity faults. Summary of the Invention

[0006] One aspect of the present disclosure relates to a network connectivity fault isolation method, comprising: determining whether all switch ports of a switch in the network have lost connectivity based on sending a network request message to each airborne device in the network; if all switch ports of a switch have lost connectivity, determining that a switch fault has occurred in the corresponding switch; otherwise, determining a network connectivity fault by determining the type of the failed switch port based on fault information reported by the switch.

[0007] According to some exemplary embodiments, determining the type of a failed switch port includes determining whether the switch port includes a cascade port or a non-cascade port; and if the failed switch port includes a non-cascade port, determining that a switch-to-end system network connectivity failure has occurred; otherwise, if the failed switch port includes a cascade port, determining that a switch-to-switch network connectivity failure has occurred.

[0008] According to some exemplary embodiments, the network includes a network A and a network B, the network A includes an A-network switch, and the network B includes a B-network switch.

[0009] According to some exemplary embodiments, determining whether all switch ports of a switch in the network have lost connectivity based on sending the network request message to each onboard device in the network includes: determining whether a network response message in response to the network request message is received and whether a response duration of the network response message is greater than a preset threshold; and if the network response message is not received or the response duration of the network response message is greater than the preset threshold, determining whether all switch ports of the corresponding switch have lost connectivity.

[0010] According to some exemplary embodiments, the method further includes receiving the fault information reported by the switch, wherein the fault information includes one or more of the following: a device number, a network channel, and a switch port number parameter.

[0011] According to some example embodiments, determining the type of the failed switch port includes determining the type of the switch port according to a topology configuration table.

[0012] According to some exemplary embodiments, the method further includes determining whether any onboard device in the network has lost network connectivity to all networks simultaneously; and determining to record a device failure if any onboard device in the network has lost network connectivity to all networks simultaneously.

[0013] Another aspect of the present disclosure relates to a network connectivity fault isolation device, comprising: a connectivity management module, configured to determine whether all switch ports of a switch in the network have lost connectivity based on sending a network request message to each onboard device in the network; if all switch ports of a switch have lost connectivity, determining that a switch fault has occurred in the corresponding switch; otherwise, determining a network connectivity fault based on the type of the failed switch port based on fault information reported by the switch; and a topology configuration module, configured to determine the type of the failed switch port based on a topology configuration table.

[0014] Yet another aspect of the present disclosure includes a network connectivity fault isolation apparatus comprising a memory; and

[0015] A processor coupled to the memory is configured to determine, based on sending a network request message to each onboard device in the network, whether all switch ports of a switch in the network have lost connectivity; if all switch ports of a switch have lost connectivity, determine that a switch failure has occurred in the corresponding switch; otherwise, determine a network connectivity failure by determining a type of the failed switch port based on fault information reported by the switch.

[0016] Yet another aspect of the present disclosure includes a computer-readable medium having processor-executable instructions stored thereon, wherein when executed by a processor, the processor-readable instructions perform network connectivity fault isolation, including determining whether all switch ports of a switch in the network have lost connectivity based on sending a network request message to each airborne device in the network; if all switch ports of a switch have lost connectivity, determining that a switch fault has occurred in the corresponding switch; otherwise, determining a network connectivity fault by determining a type of the failed switch port based on fault information reported by the switch.

[0017] The present disclosure also includes other aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A schematic diagram of an onboard network according to an aspect of the present disclosure is shown.

[0019] Figure 2 A schematic diagram illustrating various connectivity issues for an onboard network according to an aspect of the present disclosure.

[0020] Figure 3 A flowchart of a method for locating and isolating a network connectivity fault according to one aspect of the present disclosure is shown.

[0021] Figure 4 A block diagram of a network connectivity fault location and isolation device according to one aspect of the present disclosure is shown. DETAILED DESCRIPTION

[0022] Figure 1 FIG. 1 shows a schematic diagram of an onboard network 100 according to an aspect of the present disclosure. Figure 1 The embodiment of the onboard network 100 shown in FIG. 1 may include, for example, a redundant network architecture. According to an exemplary embodiment, the redundant network architecture may include an A network switch 102 and a B network switch 102. As can be seen, although Figure 1 In the embodiment of the present invention, a redundant architecture consisting of two networks is described, but the present disclosure is not limited thereto and may include more or fewer networks. For example, according to an exemplary embodiment, the present disclosure may also be applicable to an architecture of a non-redundant network (ie, only a single network).

[0023] A plurality of onboard devices 104 are connected to each network 102 through corresponding end systems (ES) 106 to achieve communication. Figure 1In the exemplary onboard network 100 of FIG. 1 , onboard devices 1–4 (104) are shown to be connected to the A1 network switch 102 and the B network switch 102 respectively through corresponding end systems 106. An onboard device 104 transmits data and / or control information to another onboard device 104 through the redundant network 102 (e.g., each switch) via the end system 106. The other onboard device 104 can receive the data and / or control information from the redundant network 102 (e.g., each switch) via the end system 106 and perform corresponding processing. According to some exemplary embodiments, each onboard device 104 can simultaneously act as a transmitter and / or receiver to transmit and / or receive data and / or control information. Although Figure 1 Only four onboard devices 104 are shown, but those skilled in the art can understand and conceive that there can be more or fewer onboard devices 104 communicating through the redundant network.

[0024] Existing fault isolation is directly aimed at airborne equipment, and there are few isolation logic and methods specifically for network connectivity failures.

[0025] For example, for Figure 1 In the exemplary onboard network 100, connectivity issues may occur for various reasons, including but not limited to: switch-to-end system connectivity failure, switch-to-switch connectivity failure, and switch failure (non-connectivity failure). A switch failure is considered a device failure, not a connectivity failure. However, a switch-to-end system connectivity failure and a switch-to-switch connectivity failure are considered connectivity failures.

[0026] Figure 2 A schematic diagram illustrating various connectivity issues 200 for an onboard network according to an aspect of the present disclosure is shown.

[0027] According to an exemplary aspect, Figure 2 (a) of FIG. 3 illustrates the location of a switch-end system connectivity failure. According to an exemplary embodiment, a connection failure may occur between an end system 106 of an onboard device 104 and a switch 102 in the network. Such a failure typically only affects connectivity between the onboard device 104 and a single switch 102, and does not affect connectivity with other switches 102. If such an onboard device failure (non-connectivity failure) is located, the corresponding onboard device can be disabled and / or the failed connection can be replaced.

[0028] According to an exemplary aspect, Figure 2(b) of FIG. 3 illustrates the location of a switch-to-switch connectivity failure. According to an exemplary embodiment, a connection (not shown) between switches 102 in the network may fail. This failure typically affects connectivity between switches 102 but does not affect connectivity between switches 102 and onboard devices 104. In a redundant network, switches 102 can normally exchange information and verify each other. If such a switch-to-switch connectivity failure is located, the corresponding switching function can be disabled and / or the failed connection can be replaced.

[0029] According to an exemplary aspect, Figure 2 (c) of FIG. 4 illustrates the location where a switch failure (non-connectivity failure) may occur. According to an exemplary embodiment, a switch 102 in the network may fail. This type of failure generally affects connectivity between the switch 102 and all onboard devices 104, as well as between the switch 102 and all other switches 102, but does not affect connectivity between other switches 102 or between other switches 102 and all onboard devices 104. Manifestations of this type of failure may include, for example, a loss of connectivity across all ports of a particular switch 102. If this type of switch failure (non-connectivity failure) is located, the corresponding switch 102 may be disabled and / or the failed switch 102 may be replaced.

[0030] Figure 3 A flow chart of a network connectivity fault location and isolation method 300 according to an aspect of the present disclosure is shown. According to an exemplary embodiment, the network connectivity fault location and isolation method 300 begins at block 302 .

[0031] According to some exemplary embodiments, the network connectivity fault location and isolation method 300 may include sending a network request message to each device in the network (e.g., including but not limited to an onboard device and a switch) to receive a network response message from each device in the network at block 304. According to some exemplary embodiments, the network response message may include network connectivity information of devices in multiple networks (e.g., network A and network B).

[0032] According to some exemplary embodiments, the network connectivity fault location and isolation method 300 may include determining, at block 306 , whether a network response message is received and whether the response duration is greater than a configured response time limit threshold.

[0033] According to some exemplary embodiments, if it is determined at block 306 that a network response message is received and the response duration is not greater than the threshold, the flow of method 300 proceeds to block 314. According to some further exemplary embodiments, network connectivity fault location and isolation method 300 may determine whether a fault reaching condition is satisfied based at least in part on the network response message received at block 304.

[0034] According to some exemplary embodiments, if it is determined in block 306 that no network response message is received, or the response duration is greater than a threshold, the flow of method 300 proceeds to block 308 .

[0035] According to some exemplary embodiments, the network connectivity fault localization and isolation method 300 may include determining whether all ports of a particular switch have lost connectivity at block 308. According to some exemplary embodiments, this may be determined based on MAC port status parameters. According to some further exemplary embodiments, the network connectivity fault localization and isolation method 300 may further determine whether a fault fulfillment condition and / or fault type is satisfied based on the MAC port status parameters received at block 308.

[0036] According to some exemplary embodiments, if it is determined at block 308 that all ports of the particular switch have lost connectivity, flow of method 300 proceeds to block 316 .

[0037] According to some exemplary embodiments, if it is determined at block 308 that not all ports of the switch have lost connectivity, flow of method 300 proceeds to block 310 .

[0038] According to some exemplary embodiments, the network connectivity fault localization and isolation method 300 may include receiving fault information reported by a switch at block 310. According to some exemplary embodiments, the fault information reported by the switch may include, but is not limited to, parameters such as a device number, a network channel, and a switch port number. According to some exemplary embodiments, the network connectivity fault localization and isolation method 300 may further determine whether a fault fulfillment condition is satisfied based on the fault information reported by the switch.

[0039] According to some exemplary embodiments, the network connectivity fault location and isolation method 300 may include, at block 312, determining whether a failed switch port is a cascade port or a non-cascade port based on fault information reported by the switch. According to some exemplary embodiments, determining whether a failed switch port is a cascade port or a non-cascade port may be performed based on the fault information reported by the switch and determining whether the failed switch port is a cascade port or a non-cascade port according to a topology configuration table. According to exemplary embodiments, generally, switch-to-switch connections use cascade ports, while switch-to-end system connections use non-cascade ports.

[0040] According to some exemplary embodiments, if it is determined at block 312 that the failed switch port is a non-cascade port, flow of method 300 proceeds to block 318 .

[0041] According to some exemplary embodiments, if it is determined at block 312 that the failed switch port is a cascade port, flow of method 300 proceeds to block 320 .

[0042] According to some example embodiments, the network connectivity fault location and isolation method 300 may include, at block 314 , determining that a network connectivity fault does not exist.

[0043] According to some exemplary embodiments, the network connectivity fault location and isolation method 300 may include determining at block 316 that a switch fault (non-connectivity fault) exists. According to some exemplary embodiments, this may be combined with the above Figure 2 This corresponds to the situation described in (c).

[0044] According to some exemplary embodiments, the network connectivity fault location and isolation method 300 may include determining at block 318 that a switch-end system network connectivity fault exists. According to some exemplary embodiments, this may be combined with the above Figure 2 According to some exemplary embodiments, upon determining that a switch-end system network connectivity fault exists, a device parameter may be set and a switch-end system network connectivity fault determination message may be uploaded.

[0045] According to some exemplary embodiments, the network connectivity fault location and isolation method 300 may include determining at block 320 that a switch-to-switch network connectivity fault exists. According to some exemplary embodiments, this may be combined with the above Figure 2 According to some exemplary embodiments, after determining that a switch-to-switch network connectivity fault exists, a device parameter may be set and a switch-to-switch network connectivity fault determination message may be uploaded.

[0046] Figure 4 FIG2 is a block diagram of a network connectivity fault location and isolation apparatus 400 according to an aspect of the present disclosure. According to some exemplary embodiments, the network connectivity fault location and isolation apparatus 400 may include a connectivity management module 402 and a topology configuration module 404.

[0047] According to exemplary embodiments, the connectivity management module 402 may send a network request message to each device in the network (e.g., including but not limited to an onboard device and a switch), and receive a network response message from each device in the network. According to some exemplary embodiments, the network response message may include network connectivity information of devices in multiple networks (e.g., network A and network B).

[0048] According to some exemplary embodiments, the connectivity management module 402 may determine whether a network response message is received and whether the response duration is greater than a configured response time limit threshold.

[0049] According to some exemplary embodiments, the connectivity management module 402 may receive MAC port status parameters reported by the switch from the switch. According to exemplary embodiments, the MAC port status parameters of the switch are generally internal information of the switch and may be transmitted to the connectivity management module 402 as a message via the end system access network of the switch.

[0050] According to some exemplary embodiments, the connectivity management module 402 may determine whether all ports of the switch have lost connectivity based on the MAC port status parameters reported by the switch. According to some further exemplary embodiments, the connectivity management module 402 may further determine whether a fault condition and / or fault type is satisfied based on the MAC port status parameters reported by the switch. For example, according to an exemplary embodiment, when the connectivity management module 402 determines that all ports of the switch have lost connectivity based on the MAC port status parameters reported by the switch, the connectivity management module 402 may determine that a switch fault (non-connectivity fault) exists in the switch. According to some exemplary embodiments, this may be combined with the above Figure 2 This corresponds to the situation described in (c).

[0051] According to some exemplary embodiments, the topology configuration module 404 may determine the network connection relationship according to the topology configuration table. According to some exemplary embodiments, the topology configuration module 404 may only provide the network connection relationship to the connectivity management module 402.

[0052] As will be appreciated by those skilled in the art, although Figure 4 In the exemplary embodiment of FIG, the topology configuration module 404 is described as a separate module in the network connectivity fault location and isolation device 400, but the present disclosure is not limited thereto. For example, the functions of the topology configuration module 404 can be incorporated into the connectivity management module 402, or can be further split and combined.

[0053] According to some exemplary embodiments, the connectivity management module 402 may determine whether the faulty switch port is a cascade port or a non-cascade port based on the fault information reported by the switch and the network connection relationship loaded by the topology configuration module 404. According to exemplary embodiments, generally, switch-to-switch connections use cascade ports, while switch-to-end system connections use non-cascade ports.

[0054] According to some exemplary embodiments, the connectivity management module 402 may generate fault report information and upload it to the system platform.

[0055] According to some exemplary embodiments, the network connectivity fault location and isolation apparatus 400 may further include or be connected to an end system to access the onboard network, and communicate with switches and other devices in the onboard network through the end system.

[0056] The network interoperability fault isolation method according to various aspects of the present disclosure can isolate specific fault types according to actual usage scenarios, and realize the judgment and precise location of network connectivity faults by type.

[0057] To achieve the above objectives, the technical solutions adopted by the alternative embodiments of various aspects of the present disclosure may include setting network connectivity loss judgment conditions and setting network interoperability fault isolation logic.

[0058] According to an exemplary embodiment, a threshold for network connectivity loss determination may be set to prevent false fault alarms. Network connectivity is periodically reported based on periodic monitoring messages to determine whether connectivity is lost. If connectivity is lost and the threshold exceeds the threshold, an onboard device connectivity fault message is reported.

[0059] According to an exemplary embodiment, for the network connectivity loss judgment condition, if it is judged that there is no connectivity failure and the periodic monitoring message does not report any connectivity failure, then the network connectivity has not failed.

[0060] According to an exemplary embodiment, setting network interoperability fault isolation logic may include the following steps:

[0061] The network interoperability fault isolation logic queries the platform to see if it has received any airborne device fault messages. If so, the platform will determine whether the connectivity fault involves a faulty airborne device in conjunction with the reported airborne device connectivity fault message. If so, the platform will report the airborne device fault (not a connectivity fault).

[0062] If no onboard device fault message is received, the network interoperability fault isolation logic determines whether all onboard devices connected to the switch have a connectivity fault. If all onboard devices connected to the switch have a connectivity fault, the switch fault is reported (non-connectivity fault).

[0063] Otherwise, if not all onboard devices interconnected with the switch have connectivity faults, the network interoperability fault isolation logic further confirms whether it is a switch-end system connectivity fault. If it is a switch-end system connectivity fault, the switch-end system connectivity fault is reported; otherwise, it is another fault.

[0064] Due to the adoption of the above technical solution, the present disclosure can quickly locate network interoperability faults, facilitating subsequent handling of the faults.

[0065] According to some alternative embodiments of the present disclosure, a network interoperability fault isolation method for resolving a preset network interoperability fault may include:

[0066] First, set the following message and parameters:

[0067] Network connectivity status messages – Monitor C1;

[0068] Determination of loss of connectivity across the entire network – J1;

[0069] A network or B network connectivity loss judgment - J2;

[0070] Fault filtering threshold – n;

[0071] Platform onboard equipment failure message - E0;

[0072] Determine the network connectivity of all onboard devices interconnected with the switch - J3;

[0073] Switch-end system connectivity fault message - E1;

[0074] Switch-to-switch connectivity fault message – E2;

[0075] Airborne equipment failure message (non-connectivity failure) - E3;

[0076] Switch fault message (non-connectivity fault) - E4;

[0077] Higher priority airborne equipment failure message - E5.

[0078] Assume that a switch-to-end system connectivity fault A1 occurs between an onboard device and a switch in network A of the platform. Network connectivity is normal for all other connected devices, and no devices are faulty. To isolate and locate the fault, complete the following process:

[0079] Periodic monitoring message reporting ADN network connectivity status message Monitor C1;

[0080] The platform verifies the network connectivity status of network A and network B of each airborne device;

[0081] The platform determines whether any airborne device loses connectivity to both network A and network B at the same time. Based on the assumed fault A1, if fault A1 does not satisfy this step's judgment and other airborne devices are operating well, it proceeds to the next step.

[0082] The platform determines whether the periodic monitoring messages report any connectivity failures. Based on the assumed fault A1, the switch failure in network A meets the judgment criteria in this step, and proceeds to the next step.

[0083] The platform determines whether a higher-priority airborne device fault message already exists. Based on the assumed fault A1, the airborne device will simultaneously report the higher-priority airborne device fault message and proceed to the next step.

[0084] The platform determines whether the connectivity failure involves the faulty end system. Based on the assumed fault A1, there is no fault in the onboard equipment itself, so the platform proceeds to the next step.

[0085] The platform determines whether the fault is a switch-end system connectivity fault. Based on assumed fault A1, the switch-end system connectivity fault is reported, completing the fault isolation and location process.

[0086] The above description is merely an exemplary embodiment of the present invention. However, the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention.

[0087] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed with a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0088] The steps of the method or algorithm described in conjunction with the present disclosure can be implemented directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module can reside in any form of storage medium known in the art. Some examples of usable storage media include random access memory (RAM), read-only memory (ROM), flash memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, etc. The software module can include a single instruction or many instructions and can be distributed over several different code segments, distributed between different programs and distributed across multiple storage media. A storage medium can be coupled to a processor so that the processor can read and write information from / to the storage medium. Alternatively, a storage medium can be integrated into the processor.

[0089] The methods disclosed herein include one or more steps or actions for achieving the described method. These method steps and / or actions may be interchangeable with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of the specific steps and / or actions may be modified without departing from the scope of the claims.

[0090] The processor can execute software stored on a machine-readable medium. The processor can be implemented with one or more general and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems that can execute software. Software should be broadly interpreted to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. As an example, the machine-readable medium may include RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The machine-readable medium may be implemented in a computer program product. The computer program product may include packaging materials.

[0091] In a hardware implementation, the machine-readable medium may be a portion of the processing system that is separate from the processor. However, as will be readily appreciated by those skilled in the art, the machine-readable medium or any portion thereof may be external to the processing system. As an example, the machine-readable medium may include a transmission line, a carrier wave modulated by data, and / or a computer product separate from the wireless node, all of which may be accessed by the processor via a bus interface. Alternatively or in addition, the machine-readable medium or any portion thereof may be integrated into the processor, as may be the case with a cache and / or general register file.

[0092] The processing system can be configured as a general-purpose processing system having one or more microprocessors providing processor functionality and external memory providing at least a portion of the machine-readable medium, all linked together with other supporting circuitry via an external bus architecture. Alternatively, the processing system can be implemented as an ASIC (application-specific integrated circuit) with a processor, bus interface, user interface (in the case of an access terminal), supporting circuitry, and at least a portion of the machine-readable medium integrated into a single chip, or as one or more FPGAs (field programmable gate arrays), PLDs (programmable logic devices), controllers, state machines, gating logic, discrete hardware components, or any other suitable circuitry, or any combination of circuits capable of performing the various functionalities described throughout this disclosure. Depending on the specific application and the overall design constraints imposed on the overall system, those skilled in the art will recognize how to best implement the functionality described with respect to the processing system.

[0093] The machine-readable medium may include several software modules. These software modules include instructions that, when executed by a device (such as a processor), cause a processing system to perform various functions. These software modules may include a transmitting module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded from a hard drive into RAM. During execution of the software module, the processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When describing the functionality of a software module below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0094] If implemented in software, each function may be stored as one or more instructions or codes on or transmitted by a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any media that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer. Any connection is also properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray Disks, where disks often reproduce data magnetically, and discs reproduce data optically with lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0095] Thus, some aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored (and / or encoded) thereon instructions, which are executable by one or more processors to perform the operations described herein. In some aspects, the computer program product may include packaging materials.

[0096] It will be understood that the claims are not limited to the precise configuration and components illustrated above. Various changes, substitutions and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A network connectivity fault isolation method, comprising: determining whether all switch ports of a switch in the network have lost connectivity based on sending a network request message to each onboard device in the network; If all switch ports of a switch lose connectivity, it is determined that a switch failure has occurred on the corresponding switch; otherwise Based on the fault information reported by the switch, the network connectivity fault is determined by determining the type of switch port that has failed.

2. The method according to claim 1, wherein Determining the type of the failed switch port includes determining whether the switch port comprises a cascade port or a non-cascade port; and If the failed switch port includes a non-cascade port, it is determined that a switch-end system network connectivity failure has occurred; otherwise If the failed switch port includes a cascade port, it is determined that a switch-to-switch network connectivity failure has occurred.

3. The method according to claim 1, wherein The network includes network A and network B, wherein network A includes a network A switch, and network B includes a network B switch.

4. The method of claim 1 , wherein determining whether all switch ports of a switch in the network have lost connectivity based on sending the network request message to each onboard device in the network comprises: Determining whether a network response message in response to the network request message is received and whether a response duration of the network response message is greater than a preset threshold; as well as If the network response message is not received or the response time of the network response message is longer than a preset threshold, it is determined whether all switch ports of the corresponding switch have lost connectivity.

5. The method of claim 1, further comprising: Receive the fault information reported by the switch, where the fault information includes one or more of the following: a device number, a network channel, and a switch port number parameter.

6. The method of claim 1, wherein determining the type of the failed switch port comprises determining the switch port type based on a topology configuration table.

7. The method of claim 1, further comprising: determining whether any onboard device in the network has lost network connectivity to all networks simultaneously; as well as If an onboard device in the network loses network connectivity to all networks simultaneously, a device failure is determined to be recorded.

8. A network connectivity fault isolation device, comprising: Connectivity management module for: determining whether all switch ports of a switch in the network have lost connectivity based on sending a network request message to each onboard device in the network; If all switch ports of a switch lose connectivity, it is determined that a switch failure has occurred on the corresponding switch; otherwise Based on the fault information reported by the switch, determine the network connectivity fault according to the type of switch port where the fault occurred; as well as The topology configuration module is used to determine the type of the switch port where the fault occurs according to the topology configuration table.

9. A network connectivity fault isolation device, comprising: Memory; as well as a processor coupled to the memory, the processor being configured to: determining whether all switch ports of a switch in the network have lost connectivity based on sending a network request message to each onboard device in the network; If all switch ports of a switch lose connectivity, it is determined that a switch failure has occurred on the corresponding switch; otherwise Based on the fault information reported by the switch, the network connectivity fault is determined by determining the type of switch port that has failed.

10. A computer-readable medium having processor-executable instructions stored thereon, wherein the processor-executable instructions, when executed by a processor, perform network connectivity fault isolation, comprising: determining whether all switch ports of a switch in the network have lost connectivity based on sending a network request message to each onboard device in the network; If all switch ports of a switch lose connectivity, it is determined that a switch failure has occurred on the corresponding switch; otherwise Based on the fault information reported by the switch, the network connectivity fault is determined by determining the type of switch port that has failed.

Images