Method for automatically detecting input and configuration consistency of A664 network

Abstract

According to the A664 network input and configuration consistency automation detection method, for the A664 network configuration process, data comparison is carried out on consistency among user input ICD, topology and tool output configuration, and the correctness of A664 network configuration is guaranteed. Through information extraction of user input ICD, topology and tool output configuration, correctness checking of the user input ICD, topology and tool output configuration is carried out. Through data comparison between ICD and topology, ICD and configuration and topology and configuration, consistency check is carried out, correctness of user input and correctness of tool output configuration are verified, correctness and consistency check of ICD, topology and tool output configuration input by a user are carried out, consistency and correctness of input files are improved, correctness of output configuration is ensured, and user experience is improved. And correctness guarantee is provided for A664 network configuration.

Description

Technical Field

[0001] This invention belongs to the technical field of computer communication methods, and particularly relates to an automated detection method for A664 network input and configuration consistency. Background Technology

[0002] To ensure low latency and high determinism, the A664 commercial aircraft network employs a fixed configuration, which determines the network's data transmission and reception behavior. As input files for network planning, the ICD (Internet Data Center) and network topology determine the network's data transmission capabilities. Inconsistent inputs will lead to errors in automatic network planning, and in severe cases, may prevent automatic planning altogether.

[0003] In addition, after importing ICD and network topology, most tools offer automatic and manual configuration planning functions. The overlap of these two operations may introduce errors, posing risks to the correctness of configuration files and the normal operation of devices, and affecting network performance and communication quality.

[0004] In view of this, the present invention is hereby proposed. Summary of the Invention

[0005] The automated detection method for A664 network input and configuration consistency provided by this invention avoids output file errors caused by inconsistencies between ICD, topology files, and the entire network XML configuration file resulting from the alternating use of manual user operation and automatic generation. This ensures the accuracy of network planning information and proactively prevents the introduction of unnecessary faults. The technical solution of this invention has many beneficial effects, as described below: An automated detection method for A664 network input and configuration consistency is provided, applicable to the detection of A664 network configuration in airborne avionics systems. The A664 network input files include a network topology file and an ICD file, and the A664 network configuration includes an A664 configuration table. The detection method includes... S101: Based on the network topology file and ICD file, a consistency check is performed using a cross-comparison method to generate consistency check results; S102: Based on the consistency check result, determine whether to start the automatic generation function of the avionics system network configuration tool to generate the A664 configuration table. If yes, the A664 configuration table can be generated; otherwise, the operation ends. S103: After generating the A664 configuration table and before the avionics system network configuration tool outputs the full network A664 configuration file, perform a consistency check on the ICD file, network topology file, and A664 configuration table, and generate the check results; S104: Based on the check results, determine whether to automatically generate a network-wide A664 configuration file, and output the consistency check results to the user-specified directory.

[0006] Compared with the prior art, the technical solution provided by the present invention has the following beneficial effects: This method compares the consistency between user-input ICD, topology, and tool-output configurations to ensure the correctness of A664 network configuration. Specifically, it extracts information from the user-input ICD, topology, and tool-output configurations, checks their correctness, and performs consistency checks through data comparisons between ICD and topology, ICD and configuration, and topology and configuration. This verifies the correctness of both user input and tool-output configurations. By checking the correctness and consistency of user-input ICD, topology, and tool-output configurations, this method improves the consistency and correctness of input files, ensures the correctness of output configurations, and provides a guarantee of correctness for A664 network configuration. Attached Figure Description

[0007] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0008] Figure 1 This is a flowchart of the present invention. Detailed Implementation

[0009] The following specific examples illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that, in the absence of conflict, the following embodiments and features in the embodiments can be combined with each other. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0010] It should be noted that various aspects of embodiments within the scope of the appended claims are described below. It will be apparent that the aspects described herein can be embodied in a wide variety of forms, and any particular structure and / or function described herein is merely illustrative. Based on this invention, those skilled in the art will understand that one aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement the device and / or practice the method. Additionally, this device and / or method can be implemented using structures and / or functionalities other than one or more of the aspects set forth herein.

[0011] It should also be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. The drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0012] Furthermore, specific details are provided in the following description to facilitate a thorough understanding of the examples. However, those skilled in the art will understand that aspects can be practiced without these specific details. To enable those skilled in the art to better understand the invention, the invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined as "first" and "second" may explicitly or implicitly include one or more of that feature. In the description of the invention, unless otherwise stated, "a plurality of" means two or more.

[0013] like Figure 1 The automated detection method for A664 network input and configuration consistency shown is applicable to the detection of A664 network configuration in airborne avionics systems. A664 network input files include network topology files and ICD files, while A664 network configuration includes A664 configuration tables, typically in XML format. The detection method includes... S101: Based on the network topology file and ICD file, a consistency check is performed using a cross-comparison method to generate consistency check results; S102: Based on the consistency check results, determine whether to activate the automatic generation function of the avionics system network configuration tool to generate the A664 configuration table. If yes, the A664 configuration table can be generated; otherwise, the process ends. S103: After generating the A664 configuration table and before the avionics system network configuration tool outputs the entire network A664 configuration file, perform a consistency check on the ICD file, network topology file, and A664 configuration table, and generate the check results; for example, use a cross-comparison method. The purpose is to prevent users from introducing errors through manual operation of the A664 configuration table, which could lead to inconsistencies between the information in the A664 configuration table and the input information (including the ICD file and topology file), affecting network operation performance and communication quality. S104: Based on the check results, determine whether to automatically generate a network-wide A664 configuration file (usually a binary format file) and output the consistency check results to the user-specified directory.

[0014] This method supports consistency checks on ICD files and topology files, and determines whether to generate an A664 configuration table based on the check results, ensuring the correctness of the A664 configuration table. Before generating the entire network configuration file, the ICD file, topology file, and A664 configuration table undergo consistency checks to avoid errors caused by inconsistencies introduced by manual modifications or cross-modifications. This method provides cross-checking of ICD files, topology files, and A664 configuration tables, thereby reducing the risk of introducing errors into the A664 configuration table and the A664 entire network configuration file through manual operations, and improving the correctness and reliability of A664 device configuration.

[0015] In one embodiment, a typical A664 network consists of two types of devices: A664 switches and A664 end systems. These devices are connected via physical links, and each device has one or more partitions. The network topology file defines all devices in the A664 network, the connections between them, and a list of partitions on each device. The consistency check in S101 using a cross-comparison method includes… (1) Parse the network topology file, in which a topology partition list is established. According to the partition name principle, the partition name is unique in the topology partition list and is not repeated. The topology partition list includes the partition name, the node name of the A664 network and the device type of the A664 network. (2) Parse the ICD file, where an ICD list is created. The ID of the ICD is unique and not repeated in the ICD list. The ICD list includes the ID of the ICD, the source partition name, and the destination partition list. (3) Verify whether the source partition name and destination partition list in the ICD list are included in the topology partition list and completely cover it. If yes, pass the consistency check. If no, if the source partition name and destination partition list in the ICD list are not included in the topology partition list, report an error. Or, if the source partition name and destination partition list in the ICD list do not completely cover the topology partition list, report a warning.

[0016] In one embodiment, determining whether to enable the automatic A664 configuration table generation function based on the consistency check results of the network topology file and ICD file includes: (1) If an error is reported in the consistency check of the network topology file and the ICD file, the function of automatically generating the A664 configuration table shall not be allowed to start; (2) If a warning is reported during the consistency check of the network topology file and the ICD file, the warning information will be sent back to the user, who will then determine whether to allow the warning to proceed with subsequent operations. (3) If the consistency check of the network topology file and ICD file passes, the function of automatically generating the A664 configuration table is allowed to be started.

[0017] In one embodiment, the consistency check of the ICD file, network topology file, and A664 configuration table in S103 includes, After generating the A664 configuration table and before the avionics system network configuration tool outputs the full network A664 configuration file, in order to ensure the correctness of the generated configuration file and reduce the impact of inconsistencies in input on device configuration files, a consistency check is performed on the ICD file, network topology file, and full network A664 configuration file. The steps are as follows: (1) Parse the network topology file, including the creation of a network topology table. The network topology table includes all switch devices, end system devices, device connection relationships, and device partition list in the A664 network, as shown in Table 3. (2) Parse the ICD file, including creating an ICD list, which includes the ICD ID, source partition name, destination partition list, and updating it, as shown in Table 4; (3) Parse the entire network A664 configuration file and establish an A664 configuration information list. The A664 configuration information list includes the partition list of all A664 end system devices, the list of sending communication ports, the list of receiving communication ports, the list of sending VL and the list of receiving VL, including the VL list of all switch devices; (4) Verify whether the end system device list and switch device list in the A664 configuration information list are included in the network topology table and completely cover it. If yes, pass the consistency check. If no, if there are end system devices or switch devices in the A664 configuration information list that are not included in the network topology table, report an error. Or, if the end system device list and switch device list in the A664 configuration information list do not completely cover the network topology table, report a warning. (5) Verify whether the source partition name and destination partition list in the A664 configuration information list are included in the network topology table and completely cover it. If yes, pass the consistency check. If no, if the source partition name and destination partition list in the A664 configuration information list are not included in the network topology table, report an error. Or, if the source partition name and destination partition list in the A664 configuration information list do not completely cover the network topology table, report a warning. (6) Verify the unique correspondence between the A664 communication port in the A664 configuration table and the ICD in the ICD file. If they correspond, verify the correspondence between the A664 communication port attributes in the A664 configuration table and the ICD attributes in the ICD file. If not, if the ICDID of an A664 communication port in the A664 configuration table is empty, report a warning and record the warning information. Or, if an ICD in the ICD list cannot be matched or an A664 sending communication port cannot be found in the A664 configuration information table, report an error and record the error information. (7) Verify the BAG allocation of the VL used by the A664 communication port in the A664 configuration table, whether the BAG of the VL meets the transmission bandwidth requirements of the communication port, and whether the VL forwarding table of the switch device is consistent with the topology connection relationship in the network topology file.

[0018] In one embodiment, S104 determines whether to initiate the configuration file generation function based on the consistency check results of the ICD file, network topology file, and A664 configuration table. (1) If an error is reported in the consistency check of the ICD file, network topology file and A664 configuration table, the configuration file generation function shall not be allowed to start; (2) If no errors or warnings are reported in the consistency check of the ICD file, network topology file and A664 configuration table, the user shall decide whether to allow the configuration file generation function to be started; (3) If no errors or warnings are reported in the consistency check of the ICD file, network topology file and A664 configuration table, the configuration file generation function can be started.

[0019] In one embodiment, S105 supports outputting all inspection results, (1) Record all warning and error messages, including the object to be checked, the warning list, and the error list. See Table 5 for details. (2) The user selects the output path or uses the default output path; (3) The tool outputs the inspection result information table to the path selected by the user.

[0020] For example: The first step, before starting the automatic A664 configuration table generation function, is to perform a consistency check on the network topology file and ICD file to ensure the consistency of the input files, reduce the impact of incorrect input information on configuration planning, and avoid errors. The steps are as follows: (1) Parse the network topology file and create a topology partition list. This list includes the partition name, the name of the node to which it belongs, and the type of the device to which it belongs. Each partition in the topology file must be unique in this list and must not be repeated. See Table 1 for the specific definitions; (2) Parse the ICD file and create an ICD list, which includes the ICDID, source partition name, and destination partition list. The ICD in the ICD file must be unique in this list and not repeated. See Table 2 for specific definitions; (3) Verify the consistency between the source and destination partition lists in the ICD file and the partition lists in the network topology file, as follows: a) If for each source partition and each destination partition of each ICD information in Table 2, no topology partition information can be found in Table 1 that satisfies the condition that the partition name in the topology partition information is the source partition or destination partition of the ICD information, then an error is reported and the error message is recorded: The partition used by the ICD [ICDID] [SourcePartition or DestationPartition] is not configured in the topology; b) If for each topology partition information in Table 1, no ICD information can be found in Table 2 that satisfies the condition that the partition name in the topology partition information is the source partition or destination partition of the ICD information, then a warning is issued and the warning message is recorded: The partition [PartitionName] in the topology is not used in the ICD; c) If for each source partition and each destination partition of each ICD information in Table 2, at least one topology partition information can be found in Table 1, satisfying that the partition name in the topology partition information is the source partition or destination partition of the ICD information, and for each topology partition information in Table 1, at least one ICD information can be found in Table 2, satisfying that the partition name in the topology partition information is the source partition or destination partition of the ICD information, then the verification passes.

[0021] Table 1 List of Topological Partitions

[0022] Table 2 ICD List

[0023] The second step, based on the consistency check results of the network topology file and ICD file, determines whether to enable the automatic generation of the A664 configuration table, including the following steps: (1) If an error is reported in the consistency check of the network topology file and the ICD file, the function of automatically generating the A664 configuration table shall not be allowed to start; (2) If a warning is reported during the consistency check of the network topology file and the ICD file, the warning information will be sent back to the user, who will then determine whether to allow the warning to proceed with subsequent operations. Specifically, a) If the user confirms that it is acceptable, allow the automatic generation of the A664 configuration table function to be started; b) The function of automatically generating the A664 configuration table should not be enabled if the user does not accept it.

[0024] (3) If the consistency check of the network topology file and ICD file passes, the function of automatically generating the A664 configuration table is allowed to be started.

[0025] The third step involves activating the automatic generation function of the entire network A664 configuration table, which automatically generates the entire network A664 configuration file. Before outputting the actual device configuration files used by the network switches and end systems, a consistency check is performed on the ICD file, network topology file, and the entire network A664 configuration file to ensure the correctness of the generated configuration files and reduce the impact of input inconsistencies on device configuration files. The steps are as follows: (1) Parse the ICD file and create an ICD list. The specific definitions are shown in Table 1. (2) Parse the network topology file and create a network topology table. See Table 3 for the specific definitions. (3) Parse the entire network A664 configuration file and establish an A664 configuration information list. See Table 4 for specific definitions. (4) Verify that the device list, including end systems and switches, in the network topology file and the A664 configuration table are consistent, as follows: a) If any switch or end system in the network topology table cannot be found in the switch list or end system list of the A664 configuration information table, an error will be reported and the error message will be recorded: No device [EndSystemName or SwitchName] was found in the A664 configuration table. b) If any switch or end system in the A664 configuration information table cannot be found in the switch list or end system list of the network topology table, a warning will be issued and the warning message will be recorded: A device [EndSystemName or SwitchName] not defined in the network topology file was found in the A664 configuration table. c) If the end system and switch device list in the A664 configuration table are completely consistent with the end system and switch device list in the network topology file, then the verification passes.

[0026] (5) Verify that the partition lists of end systems and switches in the network topology file and the A664 configuration table are consistent, as follows: a) If the partition name or partition IP of the switch in the network topology table is different from that of the corresponding switch in the A664 configuration information table, an error will be reported and the error message will be recorded: The partition of the switch device [SwitchName] in the A664 configuration table is inconsistent with the partition configuration in the network topology file; b) If an end system in the network topology file has a partition, but a partition cannot be found in the partition list of the corresponding end system in the A664 configuration table, and the partition name and partition IP are the same, then an error will be reported and the error message will be recorded: The partition [PartitionName] of the end system device [EndSystemName] in the topology file was not found in the A664 configuration table; c) If an end system in the A664 configuration information table has a corresponding end system in the network topology table, but a partition under that end system cannot be found in the partition list of the corresponding end system in the network topology table, and the partition name and partition IP are the same, then a warning is reported and the warning message is recorded: In the A664 configuration, the end system device [EndSystemName] has a partition [PartitionName] that is not defined in the network topology file; d) If the partition list in the A664 configuration table is exactly the same as the partition list in the network topology file, then the verification passes.

[0027] (6) Verify the correspondence between the A664 communication port in the A664 configuration table and the ICD in the ICD file, as follows: a) If an ICD in the ICD list cannot find an A664 transmission communication port in the A664 configuration information table, such that the ICDID of the A664 transmission communication port is equal to the ICDID of the ICD, then an error will be reported and the error message will be recorded: The corresponding A664 communication port for the ICD [ICDID] cannot be found in the A664 configuration table; b) If the ICDID of an A664 communication port in the A664 configuration table is empty, a warning will be reported and the warning message will be logged: The ICD file does not have an ICD corresponding to the A664 sending communication port [PortId] in the A664 configuration table.

[0028] c) If the ICD in the ICD file corresponds one-to-one with the A664 communication port in the A664 configuration table, then the verification passes.

[0029] (7) Verify the correspondence between the A664 communication port attributes in the A664 configuration table and the ICD attributes in the ICD file, as follows: a) A corresponding set of A664 transmit communication ports and ICDs should meet the following requirements. The SourcePartition of the VL corresponding to the A664 transmit communication port should be the same as the SourcePartition of the ICD.

[0030] The DstPartitions of the VL corresponding to the A664 transmit communication port should be completely consistent with the destination partition list of the ICD.

[0031] The MessageSize of the A664's communication port is the same as the Size of the ICD; When the MessageType of the ICD is Periodic, the PortType of the A664 transmission communication port should be Sample; when the MessageType of the ICD is Event, the PortType of the A664 transmission communication port should be Queue. When sampling, the PortType of the A664 transmitting communication port should be the same as the MessagePeriod of the ICD.

[0032] b) If any of the conditions in a) are not met, an error should be reported and the error message should be recorded: In the A664 configuration table, the attribute name in the A664 sending communication port [PortId] is inconsistent with the ICD [ICDID].

[0033] c) The test passes when all conditions in a) are met.

[0034] (8) Verify whether the BAG allocation of the VL used by the A664 communication port in the A664 configuration table meets the transmission bandwidth requirements of the communication port, as follows: a) For each transmit VL, obtain all A664 transmit communication ports under this VL. b) Obtain the BAG of the VL and the SamplingPeriod for each A664 communication port; c) Calculate the transmission rate of VL: 1 / BAG; d) Calculate the sum of the transmission rates of all A664 communication ports: ∑(1 / SamplingPeriod); e) If the transmission rate of VL in the A664 configuration table is less than the sum of the transmission rates of the A664 communication ports, an error will be reported and the error message will be recorded: In the A664 configuration table, the BAG allocation of VL[VLID] does not meet the transmission requirements of the A664 communication port. f) If the transmission rate of VL in the A664 configuration table is greater than twice the sum of the transmission rates of the A664 communication ports, a warning will be issued and the warning message will be recorded: In the A664 configuration table, the BAG allocation of VL[VLID] exceeds twice the transmission requirements of the A664 communication port. g) If the transmission rate of VL in the A664 configuration table is not less than the sum of the transmission rates of the A664 communication ports, and not greater than twice the sum of the transmission rates of the A664 communication ports, then the verification passes. (9) Verify that the VL forwarding table of the switch device in the A664 configuration table is consistent with the topology connection relationship in the network topology file, as follows: a) If in the A664 configuration table, switch 1 has VLi in its VL forwarding table and its output port contains port p1, and in the network topology table, the device connected to port p1 of switch 1 is switch 2, and the peer device port number is p2, then switch 2 should have VLi in its VL forwarding table and its input port should be p2. b) If the network topology table and A664 configuration information table do not meet the requirements of a), an error will be reported and the error message will be recorded: In the A664 configuration table, the forwarding table of VL [VLID] on switch [device name of switch 1] and [device name of switch 2] is inconsistent with the connection relationship in the network topology file; c) If the network topology table and A664 configuration information table meet the requirements of a), then the verification passes.

[0035] Table 3 Network Topology Table

[0036] Table 4 A664 Configuration Information List

[0037] The fourth step, based on the consistency check results of the ICD file, network topology file, and A664 configuration table, determines whether to enable the configuration file generation function, as follows: (1) If an error is reported in the consistency check of the ICD file, network topology file and A664 configuration table, the configuration file generation function shall not be allowed to start; (2) If no errors are reported in the consistency check of the ICD file, network topology file, and A664 configuration table, but a warning is reported, then: a) Feedback all warning messages to the user. If the user confirms that all warnings are acceptable, allow the automatic generation of the A664 configuration table function to be started. b) Otherwise, the function to automatically generate the A664 configuration table is not allowed to be started; c) If no errors or warnings are reported during the consistency check of the ICD file, network topology file, and A664 configuration table, then the configuration file generation function can be started.

[0038] Fifth step: Output all inspection results.

[0039] (1) Record all warning and error messages, including the object being checked, the warning list, and the error list. See Table 5 for details. (2) The user selects the output path or uses the default output path; (3) The tool outputs the inspection result information table to the path selected by the user.

[0040] Table 5 Inspection Result Information Table

[0041] The product provided by this invention has been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this invention. The descriptions of the embodiments above are merely for the purpose of helping to understand the core ideas of this invention. It should be noted that those skilled in the art can make various improvements and modifications to the invention without departing from the principles of the invention, and these improvements and modifications also fall within the protection scope of the invention claims.

Claims

1. An automated detection method for A664 network input and configuration consistency, applicable to the detection of A664 network configuration in airborne avionics systems, characterized in that, The A664 network input file includes a network topology file and an ICD file; the A664 network configuration includes an A664 configuration table; and the detection method includes... S101: Based on the network topology file and ICD file, a consistency check is performed using a cross-comparison method to generate consistency check results; S102: Based on the consistency check result, determine whether to start the automatic generation function of the avionics system network configuration tool to generate the A664 configuration table. If yes, the A664 configuration table can be generated; otherwise, the operation ends. S103: After generating the A664 configuration table and before the avionics system network configuration tool outputs the full network A664 configuration file, perform a consistency check on the ICD file, network topology file, and A664 configuration table, and generate the check results; S104: Based on the check results, determine whether to automatically generate a network-wide A664 configuration file, and output the consistency check results to the user-specified directory.

2. The detection method according to claim 1, characterized in that, The consistency check performed in S101 using the cross-comparison method includes, The network topology file is parsed, in which a topology partition list is established. According to the partition name principle, the partition name is unique in the topology partition list. The topology partition list includes the partition name, the node name of the A664 network, and the device type of the A664 network. Parse the ICD file, which involves creating an ICD list. The ICD ID is unique within the ICD list. The ICD list includes the ICD ID, the source partition name, and the destination partition list. Verify that the source partition name and destination partition list in the ICD list are included in and completely cover the topology partition list. If yes, the consistency check passes. If no, an error is reported if the source partition name and destination partition list in the ICD list are not included in the topology partition list, or if the source partition name and destination partition list in the ICD list do not completely cover the topology partition list.

3. The detection method according to claim 2, characterized in that, Based on the consistency check results of the network topology file and ICD file, the decision on whether to enable the automatic A664 configuration table generation function includes: (1) If an error is reported in the consistency check of the network topology file and the ICD file, the function of automatically generating the A664 configuration table shall not be allowed to start; (2) If a warning is reported during the consistency check of the network topology file and the ICD file, the warning information will be sent back to the user, who will then determine whether to allow the warning to proceed with subsequent operations. (3) If the consistency check of the network topology file and ICD file passes, the function of automatically generating the A664 configuration table is allowed to be started.

4. The detection method according to claim 3, characterized in that, The consistency check of the ICD file, network topology file, and A664 configuration table in S103 includes, After generating the A664 configuration table and before the avionics system network configuration tool outputs the full network A664 configuration file, a consistency check is performed on the ICD file, network topology file, and full network A664 configuration file. The steps are as follows: (1) Parse the network topology file, wherein a network topology table is established, which includes all switch devices, end system devices, device connection relationships and device partition list in the A664 network; (2) Parse the ICD file, including creating an ICD list, which includes the ICD ID, source partition name, destination partition list, and updating it; (3) Parse the entire network A664 configuration file and establish an A664 configuration information list, which includes a list of partitions of all A664 end system devices, a list of sending communication ports, a list of receiving communication ports, a list of sending VLs and a list of receiving VLs; (4) Verify whether the end system device list and switch device list in the A664 configuration information list are included in the network topology table and completely cover it. If yes, pass the consistency check. If no, if there are end system devices or switch devices in the A664 configuration information list that are not included in the network topology table, report an error. Or, if the end system device list and switch device list in the A664 configuration information list do not completely cover the network topology table, report a warning. (5) Verify whether the source partition name and destination partition list in the A664 configuration information list are included in the network topology table and completely cover it. If yes, pass the consistency check. If no, if the source partition name and destination partition list in the A664 configuration information list are not included in the network topology table, report an error. Or, if the source partition name and destination partition list in the A664 configuration information list do not completely cover the network topology table, report a warning. (6) Verify the unique correspondence between the A664 communication port in the A664 configuration table and the ICD in the ICD file. If they correspond, verify the correspondence between the A664 communication port attributes in the A664 configuration table and the ICD attributes in the ICD file. If not, if the ICDID of an A664 communication port in the A664 configuration table is empty, report a warning and record the warning information. Or, if an ICD in the ICD list cannot be matched with an A664 sending communication port in the A664 configuration information table, report an error and record the error information. (7) Verify the BAG allocation of the VL used by the A664 communication port in the A664 configuration table, whether the BAG of the VL meets the transmission bandwidth requirements of the communication port, and whether the VL forwarding table of the switch device is consistent with the topology connection relationship in the network topology file.

5. The detection method according to claim 4, characterized in that, Based on the consistency check results of the ICD file, network topology file, and A664 configuration table, S104 determines whether to enable the configuration file generation function, including: (1) If an error is reported in the consistency check of the ICD file, network topology file and A664 configuration table, the configuration file generation function shall not be allowed to start; (2) If no errors or warnings are reported in the consistency check of the ICD file, network topology file and A664 configuration table, the user shall decide whether to allow the configuration file generation function to be started; (3) If no errors or warnings are reported in the consistency check of the ICD file, network topology file and A664 configuration table, the configuration file generation function can be started.

6. The detection method according to claim 5, characterized in that, S105 supports outputting all inspection results, including (1) Record all warning and error messages, including the objects to be checked, the warning list, and the error list; (2) The user selects the output path or uses the default output path; (3) The tool outputs the inspection result information table to the path selected by the user.

Images