Operation and maintenance method and device, computer device and storage medium

Abstract

The application relates to an operation and maintenance method and device, computer equipment, a storage medium and a computer program product. It relates to the technical field of servers and can be used in the field of financial technology or other related fields. The method comprises the following steps: acquiring state information of a logical network card and a physical network card corresponding to the logical network card in a multi-network card link; judging whether the state information of the logical network card and the physical network card is consistent; in the case that the state information of the logical network card and the physical network card is inconsistent, updating the association relationship between the logical network card and the physical network card according to the type of an operating system of the server and the aggregation mode of the logical network card; restarting a network service; and in the case that a preset checking condition is met, determining that the multi-network card link of the server is repaired. The method can improve the link bandwidth and the elasticity of link transmission.

Description

Technical Field

[0001] This application relates to the field of server technology, and in particular to an operation and maintenance method, apparatus, computer equipment, storage medium and computer program product. Background Technology

[0002] With the development of server technology, servers require increasingly larger bandwidth to handle more and more transmission tasks. Therefore, multi-NIC link aggregation technology has emerged. Multi-NIC link aggregation technology enables network link redundancy, increasing link bandwidth and the resilience of link transmission.

[0003] Current multi-NIC link aggregation technology refers to configuring the logical network ports of a server to establish the association between logical network ports and physical network ports, thereby enabling load balancing of multiple physical network ports associated with the logical network port.

[0004] However, current multi-NIC link aggregation technology suffers from unstable relationships between logical and physical NICs. As a result, physical NIC names may change intermittently during system restarts, altering the relationship between logical and physical NICs and thus reducing link bandwidth and flexibility. Summary of the Invention

[0005] Therefore, it is necessary to provide an operation and maintenance method, device, computer equipment, computer-readable storage medium, and computer program product to address the aforementioned technical problems.

[0006] Firstly, this application provides an operation and maintenance method.

[0007] The operation and maintenance method is applied to servers in a state of aggregation with multiple network interface card links, and the method includes:

[0008] Obtain the status information of the logical network interface card (NIC) and the physical NIC corresponding to the logical NIC in the multi-NIC link;

[0009] Determine whether the status information of the logical network interface card (NIC) and the physical NIC are consistent;

[0010] If the status information of the logical network interface card (NIC) and the physical NIC is inconsistent, the association between the logical NIC and the physical NIC is updated according to the operating system type of the server and the aggregation mode of the logical NIC.

[0011] Restart the network service, and if the preset verification conditions are met, confirm that the multi-NIC link repair of the server is complete.

[0012] In one embodiment, before obtaining the status information of the logical network interface card (NIC) and the physical NIC corresponding to the logical NIC in the multi-NIC link, the operation and maintenance method further includes:

[0013] If the server type is the target server type, obtain the operating system type of the server;

[0014] Determine the multi-NIC configuration file address directory based on the operating system type;

[0015] In the multi-NIC configuration file address directory, traverse all configuration files in the multi-NIC configuration file address directory to determine whether the target multi-NIC configuration file exists;

[0016] If the target multi-NIC configuration file exists, confirm that the server is in a multi-NIC link aggregation state.

[0017] In one embodiment, determining whether the status information of the logical network interface card (NIC) and the physical NIC are consistent includes:

[0018] When the status information of the logical network card is enabled, the physical network card associated with the logical network card is identified as the original physical network card;

[0019] Determine whether the status information of each original physical network card is consistent with that of the logical network card.

[0020] In one embodiment, updating the association between the logical network interface card (NIC) and the physical NIC based on the operating system type of the server includes:

[0021] When the operating system type is the first operating system type, the information of the original physical network card in the configuration information of the logical network card is updated to the information of the target physical network card to obtain the updated association relationship between the logical network card and the physical network card;

[0022] When the operating system type is the second operating system type, the association relationship with the logical network card is deleted from the configuration information of the original physical network card, and the association relationship with the logical network card is added to the configuration information of the target physical network card, so that the target physical network card is associated with the logical network card; the target physical network card is a physical network card whose status information is consistent with the logical network card and which establishes a new association relationship with the logical network card.

[0023] In one embodiment, updating the association between the logical network interface card (NIC) and the physical NIC based on the aggregation mode of the logical NIC includes:

[0024] Determine whether the aggregation mode of the logical network interface card is a primary / backup aggregation mode;

[0025] When the aggregation mode of the logical network interface card is master-slave aggregation mode, update the master physical network interface card parameter of the logical network interface card to the name of the target physical network interface card.

[0026] In one embodiment, determining that the multi-NIC link repair of the server is complete under preset verification conditions includes:

[0027] Obtain the status information of the logical network interface card and the physical network interface card corresponding to the logical network interface card;

[0028] Determine whether the status information of the logical network interface card (NIC) and the physical NIC are consistent;

[0029] If the status information of the logical network card and the physical network card are consistent, it is determined that the multi-NIC link repair of the server is complete.

[0030] In one embodiment, before determining that the multi-NIC link repair of the server is complete if the status information of the logical NIC and the physical NIC are consistent, the method further includes:

[0031] If the status information of the logical network card and the physical network card are inconsistent, determine whether the number of repairs meets the preset repair conditions;

[0032] If the number of repair attempts meets the repair conditions, repair information is fed back.

[0033] If the required number of repair attempts does not meet the repair conditions, the step of updating the association between the logical network card and the physical network card based on the server's operating system type and the aggregation mode of the logical network card is executed.

[0034] In one embodiment, if the number of repairs meets the repair condition, the step of feeding back repair information includes:

[0035] Determine if the repair fails and archive the status information of the logical network interface and the physical network interface;

[0036] Repair information is constructed based on the status information of the logical network card and the physical network card, the execution time, and the repair failure information;

[0037] The repair information is fed back so that the target user is aware of the repair information.

[0038] Secondly, this application also provides an operation and maintenance device. The operation and maintenance device is applied to a server in a multi-NIC link aggregation state, and the device includes:

[0039] The acquisition module is used to acquire the status information of the logical network interface card (NIC) and the physical NIC corresponding to the logical NIC in the multi-NIC link;

[0040] The judgment module is used to determine whether the status information of the logical network card and the physical network card are consistent;

[0041] The update module is used to update the association between the logical network card and the physical network card according to the operating system type of the server and the aggregation mode of the logical network card when the status information of the logical network card and the physical network card are inconsistent.

[0042] The determination module is used to restart network services and, under the condition that preset verification conditions are met, determine that the multi-NIC link repair of the server is complete.

[0043] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0044] Obtain the status information of the logical network interface card (NIC) and the physical NIC corresponding to the logical NIC in a multi-NIC link;

[0045] Determine whether the status information of the logical network interface card (NIC) and the physical NIC are consistent;

[0046] If the status information of the logical network interface card (NIC) and the physical NIC is inconsistent, the association between the logical NIC and the physical NIC is updated according to the operating system type of the server and the aggregation mode of the logical NIC.

[0047] Restart the network service, and if the preset verification conditions are met, confirm that the multi-NIC link repair of the server is complete.

[0048] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0049] Obtain the status information of the logical network interface card (NIC) and the physical NIC corresponding to the logical NIC in a multi-NIC link;

[0050] Determine whether the status information of the logical network interface card (NIC) and the physical NIC are consistent;

[0051] If the status information of the logical network interface card (NIC) and the physical NIC is inconsistent, the association between the logical NIC and the physical NIC is updated according to the operating system type of the server and the aggregation mode of the logical NIC.

[0052] Restart the network service, and if the preset verification conditions are met, confirm that the multi-NIC link repair of the server is complete.

[0053] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0054] Obtain the status information of the logical network interface card (NIC) and the physical NIC corresponding to the logical NIC in a multi-NIC link;

[0055] Determine whether the status information of the logical network interface card (NIC) and the physical NIC are consistent;

[0056] If the status information of the logical network interface card (NIC) and the physical NIC is inconsistent, the association between the logical NIC and the physical NIC is updated according to the operating system type of the server and the aggregation mode of the logical NIC.

[0057] Restart the network service, and if the preset verification conditions are met, confirm that the multi-NIC link repair of the server is complete.

[0058] The aforementioned operation and maintenance methods, devices, computer equipment, storage media, and computer program products acquire the status information of logical network cards (NICs) and their corresponding physical NICs in a multi-NIC link; determine whether the status information of the logical NIC and the physical NIC is consistent; if the status information of the logical NIC and the physical NIC is inconsistent, update the association between the logical NIC and the physical NIC according to the server's operating system type and the aggregation mode of the logical NIC; restart the network service, and determine that the multi-NIC link repair of the server is complete if preset verification conditions are met. Using this method, by determining whether the status information of the logical NIC and its corresponding physical NIC is consistent, it clarifies whether the association between the logical NIC and the physical NIC has changed. Then, by updating the configuration parameters of the logical NIC and the physical NIC, the correct association between the logical NIC and the physical NIC is obtained, ensuring that the physical NIC associated with the logical NIC is in the correct status, thus improving link bandwidth and link transmission flexibility. Attached Figure Description

[0059] Figure 1 This is a flowchart illustrating the operation and maintenance method in one embodiment;

[0060] Figure 2 This is a schematic diagram illustrating the relationship between logical network cards and physical network cards in one embodiment;

[0061] Figure 3 This is a flowchart illustrating the steps for confirming the multi-NIC link aggregation status in one embodiment;

[0062] Figure 4 This is a flowchart illustrating the steps for determining the status information of logical network cards and physical network cards in one embodiment;

[0063] Figure 5 This is a schematic diagram illustrating the relationship between the logical network interface card (NIC) and the physical NIC in another embodiment;

[0064] Figure 6 This is a flowchart illustrating the steps for updating association relationships in one embodiment;

[0065] Figure 7 This is a flowchart illustrating the steps for updating the parameters of the primary physical network interface card in one embodiment;

[0066] Figure 8 This is a flowchart illustrating the steps for confirming the completion of the repair in one embodiment;

[0067] Figure 9 This is a flowchart illustrating the steps for repairing the multi-NIC link again in one embodiment;

[0068] Figure 10 This is a flowchart illustrating the feedback and repair information step in one embodiment;

[0069] Figure 11 This is a structural block diagram of the operation and maintenance device in one embodiment;

[0070] Figure 12 This is a schematic diagram of a cloud bare metal server operation and maintenance method in one embodiment;

[0071] Figure 13 This is a structural block diagram of the operation and maintenance device in another embodiment;

[0072] Figure 14 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0073] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0074] In one embodiment, such as Figure 1 As shown, an operation and maintenance method is provided. This application does not limit the execution device for the operation and maintenance method; the method is described using a server as an example, and includes the following steps:

[0075] Step 102: Obtain the status information of the logical network card and the physical network card corresponding to the logical network card in the multi-NIC link.

[0076] In implementation, the server contains multiple logical network interface cards (NICs). For each logical NIC, the server retrieves the status information of that logical NIC and the status information of the physical NIC corresponding to that logical NIC from the target multi-NIC configuration file.

[0077] Specifically, during the pre-configuration of multi-link network interfaces, the server calls the `ifconfig` command to filter out the information of logical network interfaces in the target multi-link network interface configuration file, obtaining information about all physical network interfaces. The information of logical network interfaces includes parameters such as "bond, lo, and cbond to which the container belongs." Then, the server polls and enables all physical network interfaces, setting the status of properly connected physical network interfaces to "up." Next, during the verification process of multi-link network interfaces, the server retrieves the status information of each logical network interface and the status information of the corresponding physical network interface from the target multi-link network interface configuration file.

[0078] In an optional embodiment, such as Figure 2 As shown, the server has two logical network interfaces (NICs): a private network interface (bond0) and a public network interface (bond1). The server also has multiple physical NICs. The server calls the `ifconfig` command to filter out information about the logical NICs in the target multi-NIC configuration file, obtaining information about the physical NICs nic0, nic1, eth2, eth3, and eth4. Then, the server polls all physical NICs to ensure that the status of any properly connected physical NIC is enabled (up). Next, for each logical NIC, the server determines the corresponding physical NIC. Specifically, in... Figure 2 In the configuration file, the logical network interface bond0 corresponds to the physical network interface nic0 and the physical network interface nic1. Similarly, the logical network interface bond1 corresponds to the physical network interface eth2, and the physical network interface eth3 corresponds to the physical network interface eth4. For the logical network interface bond1, the server retrieves the status information of the logical network interface bond1, as well as the status information of its corresponding physical network interfaces eth2, eth3, and eth4, from the target multi-NIC configuration file.

[0079] Step 104: Determine whether the status information of the logical network card and the physical network card are consistent.

[0080] The original physical network card is the physical network card associated with the logical network card.

[0081] In implementation, the server uses the physical network interface card (NIC) associated with the current logical NIC as the original physical NIC. Then, during the server's verification of multi-link NICs, the server determines whether the status information of each original physical NIC is consistent with the status information of the logical NIC.

[0082] Step 106: If the status information of the logical network interface card (NIC) and the physical NIC is inconsistent, update the association between the logical NIC and the physical NIC according to the server's operating system type and the aggregation mode of the logical NIC.

[0083] In practice, when the status information of the logical network interface card (NIC) and the physical NIC is inconsistent, the server obtains the operating system type of the server. Then, the server updates the association between the logical NIC and the physical NIC based on the operating system type. After updating the association, the server obtains the aggregation mode of the logical NIC. If the aggregation mode of the logical NIC is the target aggregation mode, the NIC parameters of the corresponding primary physical NIC are updated after the association is updated.

[0084] Optionally, if the status information of the logical network interface card (NIC) and the original physical NIC is consistent, the server determines that the multi-NIC link is in normal condition. Then, the server terminates the operation and maintenance process.

[0085] Step 108: Restart the network service. If the preset verification conditions are met, confirm that the multi-NIC link repair of the server is complete.

[0086] The server has pre-set verification conditions.

[0087] During implementation, the server restarts the network service and initializes the status information of the logical and physical network interfaces (NICs) based on the updated association between them. The server then retrieves the status information of the logical and physical NICs. The server determines whether the status information of the logical and physical NICs meets preset verification conditions. If the status information of the logical and physical NICs meets the preset verification conditions, the server confirms that the multi-NIC link repair is complete.

[0088] Optionally, if the status information of the logical network card and the physical network card does not meet the preset verification conditions, the server executes step 106.

[0089] In the above operation and maintenance method, by determining whether the status information of the logical network interface card (NIC) and its corresponding physical NIC is consistent, it is clarified whether the association between the logical and physical NICs has changed. Then, by updating the configuration parameters of the logical and physical NICs, the correct association between the logical and physical NICs is obtained, enabling data to be transmitted based on multiple physical NICs that are in an enabled state. This ensures that the physical NIC associated with the logical NIC is in the correct state, improving link bandwidth and the flexibility of link transmission.

[0090] In one embodiment, before obtaining the status information of the logical network interface cards (NICs) and their corresponding physical NICs in a multi-NIC link, it is necessary to first determine whether the server type of the server executing the maintenance method is the target server type. If the server type is the target server type, it is determined whether the server is in a multi-NIC link aggregation state. Before step 102 is executed, such as... Figure 3 As shown, the specific processing steps of this operation and maintenance method also include:

[0091] Step 302: If the server type is the target server type, obtain the server's operating system type.

[0092] In implementation, the server has a preset target server type. The server obtains the server type of the target server. The server determines whether the server type is the target server type. If the server type is the target server type, the server obtains the operating system type of the target server.

[0093] For example, the default target server type in the server is cloud bare metal. The server obtains the server type of this server. The server determines whether the server type is cloud bare metal. If the server type is cloud bare metal, the server obtains the operating system type of this server.

[0094] Optionally, if the server type is not the target server type, the server terminates the processing flow of the operation and maintenance method.

[0095] Step 304: Determine the multi-NIC configuration file address directory based on the operating system type.

[0096] In practice, the server locates the multi-NIC configuration file address directory based on the server's operating system type.

[0097] For example, the server's operating system is Red Hat (a Linux operating system, where Linux is an operating system kernel). There are multiple configuration files in the multi-NIC configuration file directory. The server obtains the server's operating system type as Red Hat. Then, based on Red Hat, the server locates the multi-NIC configuration file directory as / etc / sysconfig / network-scripts, and obtains the multiple configuration files under that directory.

[0098] Step 306: In the multi-NIC configuration file address directory, traverse all configuration files in the multi-NIC configuration file address directory to determine whether the target multi-NIC configuration file exists.

[0099] The target multi-NIC configuration file is used to store the association between logical NICs and physical NICs.

[0100] In practice, the server iterates through all configuration files located in the multi-NIC configuration file address directory to determine if the target multi-NIC configuration file exists.

[0101] Step 308: If the target multi-NIC configuration file exists, confirm that the server is in a multi-NIC link aggregation state.

[0102] During implementation, if the target multi-NIC configuration file exists, the server confirms that it is currently in a multi-NIC link aggregation state.

[0103] Optionally, if the target multi-NIC configuration file does not exist, the server confirms that the server is not in a multi-NIC link aggregation state. Then, the server terminates the processing flow of this operation and maintenance method.

[0104] In this embodiment, by determining that the server type is the target server type and that the target multi-NIC configuration file exists, it is clear whether the server executing this operation and maintenance method has implemented multi-NIC aggregation, which facilitates the subsequent execution of this operation and maintenance method.

[0105] In one embodiment, such as Figure 4 As shown, determining whether the status information of the logical network card and the physical network card are consistent includes:

[0106] Step 402: If the status information of the logical network card is enabled, the physical network card associated with the logical network card is identified as the original physical network card.

[0107] In implementation, the status information of the logical network interface card (NIC) in a multi-NIC link is "enabled". When the status information of the logical NIC is "enabled", the server confirms that the logical NIC associated with the logical NIC is the original physical NIC.

[0108] In an optional embodiment, such as Figure 2 As shown, when the status information of the logical network interface bond1 is enabled, the server determines that the physical network interfaces eth2 and eht3 associated with the logical network interface bond1 are the original physical network interfaces.

[0109] In an optional embodiment, such as Figure 5 As shown, when the status information of the logical network interface bond1 is enabled, the server determines that the physical network interfaces eth2 and eht3 associated with the logical network interface bond1 are the original physical network interfaces.

[0110] Step 404: Determine whether the status information of each original physical network card is consistent with that of the logical network card.

[0111] In implementation, if the status information of a physical network interface card (NIC) is "enabled," it indicates that the NIC can transmit data normally. A logical NIC is associated with multiple original physical NICs. The server checks whether the status information of each original physical NIC is "enabled." If the status information of each original physical NIC is "enabled," the server confirms that the multi-NIC link is functioning correctly. If the status information of any original physical NIC is not "enabled," the server confirms that the multi-NIC link is malfunctioning.

[0112] In an optional embodiment, such as Figure 2As shown, the original physical network interfaces associated with physical network interface bond1 are eth2 and eht3. The server determines that the status information of physical network interface eth2 is enabled (up). Then, the server determines that the status information of physical network interface eht3 is enabled (up). The server confirms that the multi-NIC link is functioning normally.

[0113] In an optional embodiment, such as Figure 5 As shown, the original physical network interfaces associated with physical network interface bond1 are eth2 and eht3. The server determines that the status of physical network interface eth2 is up. Then, the server determines that the status of physical network interface eht3 is down. The server confirms that the status of the multi-NIC link is incorrect.

[0114] Optionally, if the multi-NIC link is in normal condition, the server terminates the execution process of this operation and maintenance method.

[0115] In this embodiment, by determining whether the status information of the logical network card and the corresponding physical network card are consistent, it is clear whether the association between the logical network port and the physical network port has changed, and at the same time, it is clear whether the status of the server's multi-network card link is normal, thus realizing the server's self-test.

[0116] In one embodiment, such as Figure 6 As shown, the specific process of updating the association between the logical network card and the physical network card according to the server's operating system type in step 106 includes:

[0117] Step 602: If the operating system type is the first operating system type, update the original physical network card information contained in the configuration information of the logical network card to the information of the target physical network card, and obtain the updated association relationship between the logical network card and the physical network card.

[0118] The server's operating system type is the first operating system type. The target physical network interface card (NIC) corresponds to the logical NIC, and the status information of the target physical NIC is consistent with the status information of the logical NIC.

[0119] In implementation, the logical network interface card (NIC) is set to "enabled". The server identifies the physical NIC corresponding to the logical NIC and whose status is "enabled" as the target physical NIC. Then, the server obtains its operating system type. The server determines whether this operating system type is the first operating system type. If the operating system type is the first operating system type, the server updates the original physical NIC information in the logical NIC's configuration information to the target physical NIC's information. The server then obtains the updated association between the logical NIC and the physical NIC.

[0120] In an optional embodiment, such as Figure 5 As shown, the status information of the logical network interface bond1 and the original physical network interfaces are inconsistent. The original physical network interfaces are eth2 and eth3. The server determines that the target physical network interfaces are the eth2 and eth4 physical network interfaces, which correspond to the logical network interfaces and whose status information is enabled.

[0121] The first operating system type is either SUSE (a Linux operating system) or SLSE (a Linux operating system). The server's operating system type is SUSE. The server obtains the server's operating system type as SUSE. The server determines that the operating system type is SUSE.

[0122] With the operating system type SUSE, the server updates the configuration information of the logical network interface bond1, replacing the information of the physical network interfaces eth2 and eth3 with the information of the physical network interfaces eth2 and eth4. Specifically, the server modifies the parameter (BONDING_SLAVE) defined in the logical network interface bond1 configuration file ifcfg-bond1 to "physical network interfaces (eth2, eth4) with a status of UP". The server obtains the updated association between the logical network interfaces and the physical network interfaces, as shown below:

[0123] BONDING_SLAVE0 = eth2

[0124] BONDING_SLAVE1 = eth4

[0125] Step 604: If the operating system type is the second operating system type, delete the association relationship with the logical network card in the configuration information of the original physical network card, and add the association relationship with the logical network card in the configuration information of the target physical network card, so that the target physical network card is associated with the logical network card.

[0126] The target physical network interface card (NIC) is the one whose status information is consistent with that of the logical NIC and which has established a new association with the logical NIC. The server's operating system type is a secondary operating system type.

[0127] In implementation, the logical network interface card (NIC) is set to "enabled". The server identifies the physical NIC corresponding to the logical NIC and whose status is "enabled" as the target physical NIC. Then, the server obtains its operating system type. The server determines whether this operating system type is a second operating system type. If the operating system type is a second operating system type, the server removes the association between the logical NIC and the target physical NIC from the original physical NIC's configuration information. Then, the server adds the association between the logical NIC and the target physical NIC to the target physical NIC's configuration information, thus associating the target physical NIC with the logical NIC. The server then obtains the updated association between the logical NIC and the physical NIC.

[0128] In an optional embodiment, such as Figure 5 As shown, the status information of the logical network interface bond1 and the original physical network interfaces are inconsistent. The original physical network interfaces are eth2 and eth3. The server determines that the target physical network interfaces are the eth2 and eth4 physical network interfaces, which correspond to the logical network interfaces and whose status information is enabled.

[0129] The second operating system type is Kylin (a Linux operating system), Red Hat (a Linux operating system), and CentOS (a Linux operating system). The server's operating system type is Red Hat. The server retrieves the server's operating system type as Red Hat. The server confirms that the operating system type is Red Hat.

[0130] With the operating system type Red Hat, the server removes the association between the physical network interface eth2 (eth2) and the logical network interface bond1 (eth3) from their configuration information. Specifically, the server removes the parameters (MASTER, SLAVE) from the eth2 configuration file ifcfg-eth2. Then, the server removes the parameters (MASTER, SLAVE) from the eth3 configuration file ifcfg-eth3. The complete configuration parameters for MASTER and SLAVE are shown below:

[0131] MASTER = bond1

[0132] SLAVE = yes

[0133] The server removes the original association between the physical network interface and the logical network interface. Then, the server adds the association between the eth2 physical network interface and the logical network interface bond1 to the target physical network interface eth2. Specifically, the server writes the following to the static configuration file ifcfg-eth2 of the eth2 physical network interface:

[0134] MASTER = bond1

[0135] SLAVE = yes.

[0136] The server adds an association between the target physical network interface (eth4) and the logical network interface (bond1). Specifically, the server writes MASTER=bond1 to the static configuration file ifcfg-eth4 of the eth4 physical network interface.

[0137] SLAVE = yes.

[0138] The server completes the association between the target physical network interface card (NIC) and the logical NIC.

[0139] Optionally, the preset second operating system type can be a Linux operating system other than SUSE or SLSE, such as Kylin, Red Hat, or CentOS. This application embodiment does not limit the type of the second operating system.

[0140] In this embodiment, by updating the configuration parameters of the logical network card and the physical network card, the correct association between the logical network interface and the physical network interface is obtained, so that the physical network card associated with the logical network card is a network card in the correct state, thereby improving the link bandwidth and the flexibility of link transmission.

[0141] In one embodiment, such as Figure 7 As shown, the specific process of updating the association between the logical network interface card (NIC) and the physical NIC according to the aggregation mode of the logical NIC in step 106 includes:

[0142] Step 702: Determine whether the aggregation mode of the logical network card is primary / backup aggregation mode.

[0143] In implementation, the server obtains the aggregation mode of the logical network interface card (NIC). Then, the server determines whether the aggregation mode of that NIC is a primary / backup aggregation mode.

[0144] Specifically, there are 7 aggregation modes for multiple network interface cards (NICs). An aggregation mode parameter of 1 indicates that the aggregation mode for that logical NIC is a primary / standby aggregation mode. Other aggregation mode parameters, i.e., cases where the 'mode' parameter is not 1, indicate that the aggregation mode for that logical NIC is a load balancing mode. Therefore, based on the meaning of each aggregation mode parameter, the server obtains the configuration file ifcfg-bond1 of the logical NIC. Then, the server retrieves the aggregation mode parameter 'mode' from the configuration file of that logical NIC. The server determines whether the aggregation parameter 'mode' of the logical NIC is 1. If the aggregation parameter 'mode' of the logical NIC is 1, the server determines that the aggregation mode of the logical NIC is a primary / standby aggregation mode. If the aggregation parameter 'mode' of the logical NIC is not 1, the server determines that the aggregation mode of the logical NIC is a load balancing mode.

[0145] Step 704: In the case of the logical network card's aggregation mode being master-slave aggregation mode, update the primary physical network card parameter of the logical network card to the name of the target physical network card.

[0146] The name of the target physical network interface card can be the name of any one of the multiple target physical network interfaces.

[0147] In practice, when the server determines that the aggregation mode of the logical network interface card is primary-backup aggregation mode, it updates the primary physical network interface card parameter in the configuration file of the logical network interface card to the name of the target physical network interface card.

[0148] For example, for the logical network interface bond1, the identified target physical network interfaces are eth2 and eth4. If the server determines that the aggregation mode of logical network interface bond1 is primary / standby aggregation, it updates the primary physical network interface parameter (primary parameter) in the ifcfg-bond1 configuration file of logical network interface bond1 to the name of the eth2 physical network interface. The updated configuration parameters of logical network interface bond1 are as follows:

[0149] BONDING_MODULE_OPTS='mode=1miimon=100use_carrier=1primary=eth2'

[0150] Optionally, if the aggregation mode of the logical network card is load balancing mode, the server skips step 704 and continues to execute step 108 in the above embodiment.

[0151] In this embodiment, the main physical network interface parameter in the configuration file of the logical network interface is updated to the name of the target physical network interface, thus obtaining the correct association between the logical network interface and the physical network interface, improving the link bandwidth and the elasticity of the link transmission, and realizing the self-repair of the server.

[0152] In one embodiment, such as Figure 8 As shown, step 108, which determines that the multi-NIC link repair of the server is complete under the condition that the preset verification conditions are met, includes the following specific processing steps:

[0153] Step 802: Obtain the status information of the logical network card and the physical network card corresponding to the logical network card.

[0154] In practice, the server obtains the status information of the logical network card and the status information of the physical network card corresponding to the logical network card from the target multi-NIC configuration file.

[0155] Specifically, the specific processing procedure of step 802 is consistent with that of step 102 described above. The specific processing procedure of step 102 has been specifically described in the above embodiments, and will not be repeated here in the embodiments of this application.

[0156] Step 804: Determine whether the status information of the logical network card and the physical network card are consistent.

[0157] In implementation, the server identifies the physical network interface card (NIC) associated with the logical NIC as the original physical NIC. Then, the server determines whether the status information of each original physical NIC matches the status information of the logical NIC.

[0158] Specifically, the specific processing procedure of step 804 is consistent with that of step 104 described above. The specific processing procedure of step 104 has been specifically described in the above embodiments, and will not be repeated here in the embodiments of this application.

[0159] Step 806: If the status information of the logical network card and the physical network card are consistent, it is determined that the multi-network card link repair of the server is complete.

[0160] During implementation, if the status information of the logical network interface card (NIC) and the physical NIC is consistent, the server determines that the multi-NIC link repair for that server is complete. The server then terminates the execution steps of this maintenance method.

[0161] In this embodiment, by re-determining whether the status information of the logical network card and the physical network card are consistent, the previous repair results are clarified, making it easier to execute subsequent steps based on the repair results.

[0162] In one embodiment, if inconsistencies still occur between the logical and physical network interface cards (NICs) before the status information of the logical NICs and physical NICs is made consistent, the server needs to re-repair the multi-NIC link. For example... Figure 9 As shown, before step 806 is executed, the specific processing steps of this operation and maintenance method also include:

[0163] Step 902: If the status information of the logical network card and the physical network card is inconsistent, determine whether the number of repair attempts meets the preset repair conditions.

[0164] The server has pre-configured repair conditions.

[0165] In implementation, the repair condition requires the number of repair attempts to be greater than or equal to a repair threshold. The server has a pre-set repair count. Before executing this maintenance method, this repair count is set to 0. Each time the server executes step 106, the repair count increases by 1. If the status information of the logical network interface card (NIC) and the physical NIC is inconsistent, the server determines whether the repair count is greater than or equal to the repair threshold.

[0166] Optionally, the repair threshold can be set according to requirements. The repair threshold can be set to 5, 10, etc. This embodiment of the application does not limit the repair threshold.

[0167] Step 904: If the number of repair attempts meets the repair conditions, provide repair information.

[0168] Among them, the repair information represents the basic situation of the server's self-repair.

[0169] During implementation, if the status information of the logical network interface card (NIC) and the physical NIC is inconsistent, the server will confirm the repair failure even if the repair attempt meets the required number of attempts. The server then archives the status information of both the logical and physical NICs. The server then constructs and sends out repair information.

[0170] Step 906: If the number of repair attempts does not meet the repair conditions, execute the step of updating the association between the logical network card and the physical network card based on the server's operating system type and the aggregation mode of the logical network card.

[0171] In implementation, if the repair count does not meet the repair conditions, the server executes a step to update the association between the logical network interface card (NIC) and the physical NIC based on the server's operating system type and the aggregation mode of the logical NIC. That is, if the repair count does not meet the repair conditions, the server re-repairs the multi-NIC link. The specific repair process has been described in detail in steps 602 to 704 of the above embodiments, and will not be repeated here.

[0172] In this embodiment, if the repair count does not meet the repair conditions, the association between the logical network card and the physical network card is updated again, which improves the success rate of the repair.

[0173] In one embodiment, such as Figure 10 As shown, the specific processing steps of step 904 include:

[0174] Step 1002: Determine if the repair failed and archive the status information of the logical network card and the physical network card.

[0175] During implementation, the server confirmed that repairing multi-NIC links had failed. The server then archived the status information of both logical and physical NICs in its logs.

[0176] Step 1004: Construct repair information based on the status information of logical and physical network cards, execution time, and repair failure information.

[0177] During implementation, the server constructs repair information based on the status information of logical and physical network cards, the time of execution of this maintenance method, and information on repair failures.

[0178] Step 1006: Provide feedback on the repair information so that the target user is aware of the repair information.

[0179] The target user is the user who will log in to the server next time.

[0180] In practice, the server transmits repair information to the terminal via a communication connection, so that users who log in to the server again will be aware of the repair information.

[0181] In this embodiment, if the repair fails, the status information of the logical network interface card (NIC) and physical NIC is archived in the log, and repair information is constructed. Then, the repair information is fed back to the target personnel to facilitate their identification of server problems.

[0182] In an optional embodiment, such as Figure 11 As shown, the maintenance device for executing this maintenance method includes four modules: a server network interface card (NIC) information acquisition module 1101, a multi-NIC aggregation link status analysis module 1102, a multi-NIC aggregation link anomaly self-healing module 1103, and a fault repair verification module 1104. The server NIC information acquisition module 1101 is used to execute steps 302 to 308 in the above embodiments. The multi-NIC aggregation link status analysis module 1102 is used to execute steps 102 to 104. The multi-NIC aggregation link anomaly self-healing module 1103 is used to execute step 106. The fault repair verification module 1104 is used to execute step 108. The specific processing procedures for steps 102 to 108 and steps 302 to 308 have been described in detail in the above embodiments, and will not be repeated here.

[0183] Optionally, the maintenance device includes a timing module. This timing module is used to set a fixed time for executing the maintenance method. The fixed time can be when the application services of the maintenance device are idle or when the maintenance device restarts. This embodiment does not limit the fixed time.

[0184] In an optional embodiment, such as Figure 12 The diagram illustrates a cloud bare metal server operation and maintenance method. This method includes the following steps:

[0185] Step 1201: Read the server type to determine if it is a cloud bare metal server; otherwise, end the process.

[0186] In implementation, the target server type is preset to cloud bare metal. The server reads the server type. If the server type is cloud bare metal, the server executes step 1202. If the server type is not cloud bare metal, the server terminates the execution process of this cloud bare metal server operation and maintenance method.

[0187] Step 1202: Read the operating system type and obtain the bond multi-NIC aggregation logical NIC static configuration file to determine whether to implement multi-NIC aggregation. If the bond multi-NIC aggregation logical NIC static configuration file is not obtained, the process ends.

[0188] Among them, the bond multi-NIC aggregation logical NIC static configuration file can be called the target multi-NIC configuration file.

[0189] During implementation, the server reads the operating system type of the server. Based on the operating system type, the server checks whether the target multi-NIC configuration file exists. If the server reads the bond multi-NIC aggregation logical NIC static configuration file, it indicates that the server has implemented multi-NIC aggregation, and the server executes step 1203. If the server does not read the bond multi-NIC aggregation logical NIC static configuration file, it indicates that the server has not implemented multi-NIC aggregation, and the server terminates the execution process of this cloud bare metal server operation and maintenance method.

[0190] Step 1203: Obtain all physical network cards and enable them.

[0191] During implementation, the server obtains information about all physical network cards and enables all physical network cards, setting the status information of the properly connected physical network cards to "enabled".

[0192] Step 1204: Analyze whether the bond link status of the multiple network cards is normal. If it is abnormal, pass the parameters of the physical network cards enabled by the system and call module 1103.

[0193] In implementation, the server obtains the status information of each logical network interface card (NIC) and its corresponding physical NIC. Then, the server determines whether the status information of the logical NIC and the physical NIC is consistent, thus obtaining information on whether the multi-NIC bond link status is normal. If the multi-NIC bond link status is normal, the server terminates the execution flow of this cloud bare metal server operation and maintenance method. If the multi-NIC bond link status is normal, the server calls module 1103 in the above embodiment to execute step 1205.

[0194] Step 1205: Identify the current multi-NIC bond link aggregation mode and rewrite the NIC static configuration file.

[0195] During implementation, the static configuration file of the multi-NIC aggregation logical NIC is updated according to the server's operating system type and the aggregation mode of the logical NIC, thereby obtaining the updated association between the logical NIC and the physical NIC.

[0196] Step 1206: Restart the network service and reinitialize the network card bond state to complete the fault repair.

[0197] During implementation, the server restarts the network service and initializes the status information of the logical and physical network cards based on the updated association between the logical and physical network cards.

[0198] Step 1207: Verify whether the repaired multi-NIC link status is normal, and record and archive the multi-NIC link status information.

[0199] In implementation, the server obtains the status information of the logical network interface card (NIC) and its corresponding physical NIC. The server determines whether the multi-NIC link status is normal by checking if the status information of the logical and physical NICs is consistent. If the multi-NIC link status is normal, the server records and archives the multi-NIC link status information. Then, the server terminates the execution flow of this cloud bare metal server operation and maintenance method. If the multi-NIC link status is abnormal, the server executes steps 902 to 1006 in the above embodiments. The specific processing procedures of steps 902 to 1006 have been described in detail in the above embodiments, and will not be repeated here.

[0200] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0201] Based on the same inventive concept, this application also provides an operation and maintenance device for implementing the operation and maintenance method described above. The solution provided by this device is similar to the solution described in the above method. Therefore, the specific limitations of one or more operation and maintenance device embodiments provided below can be found in the limitations of the operation and maintenance method above, and will not be repeated here.

[0202] In one embodiment, such as Figure 13 As shown, an operation and maintenance device 1300 is provided, including: an acquisition module 1301, a judgment module 1302, an update module 1303, and a determination module 1304, wherein:

[0203] The acquisition module 1301 is used to acquire the status information of the logical network card and the physical network card corresponding to the logical network card in the multi-network card link.

[0204] The judgment module 1302 is used to determine whether the status information of the logical network card and the physical network card are consistent.

[0205] The update module 1303 is used to update the association between the logical network card and the physical network card according to the operating system type of the server and the aggregation mode of the logical network card when the status information of the logical network card and the physical network card are inconsistent.

[0206] The determination module 1304 is used to restart network services and, under the condition that the preset verification conditions are met, confirms that the multi-NIC link repair of the server is complete.

[0207] In one embodiment, before the acquisition module 1301 performs the operation, the maintenance device 1300 further includes:

[0208] The first acquisition submodule is used to acquire the operating system type of the server when the server type is the target server type.

[0209] The first determining submodule is used to determine the multi-NIC configuration file address directory based on the operating system type.

[0210] The first judgment submodule is used to traverse all configuration files in the multi-NIC configuration file address directory and determine whether the target multi-NIC configuration file exists.

[0211] The first confirmation submodule is used to confirm that the server is in a multi-NIC link aggregation state if the target multi-NIC configuration file exists.

[0212] In one embodiment, the determination module 1302 includes:

[0213] The second determining submodule is used to determine the physical network card associated with the logical network card as the original physical network card when the status information of the logical network card is enabled.

[0214] The second judgment submodule is used to determine whether the status information of each original physical network card is consistent with that of the logical network card.

[0215] In one embodiment, the update module 1303 includes a first update submodule and a second update submodule. The first update submodule includes:

[0216] The third update submodule is used to update the information of the original physical network card in the configuration information of the logical network card to the information of the target physical network card when the operating system type is the first operating system type, so as to obtain the updated association relationship between the logical network card and the physical network card.

[0217] The fourth update submodule is used to, when the operating system type is the second operating system type, delete the association relationship with the logical network card in the configuration information of the original physical network card, and add the association relationship with the logical network card in the configuration information of the target physical network card, so that the target physical network card is associated with the logical network card; the target physical network card is a physical network card whose status information is consistent with the logical network card and which establishes a new association relationship with the logical network card.

[0218] In one embodiment, the update module 1303 includes a first update submodule and a second update submodule. The second update submodule includes:

[0219] The third judgment submodule is used to determine whether the aggregation mode of the logical network card is a primary / backup aggregation mode.

[0220] The fifth update submodule is used to update the primary physical network interface parameter of the logical network interface to the name of the target physical network interface when the aggregation mode of the logical network interface is primary-backup aggregation mode.

[0221] In one embodiment, the determining module 1204 includes a restart submodule and a third determining submodule. The third determining submodule includes:

[0222] The second acquisition submodule is used to acquire the status information of the logical network card and the physical network card corresponding to the logical network card.

[0223] The fourth judgment submodule is used to determine whether the status information of the logical network card and the physical network card are consistent.

[0224] The fourth determination submodule is used to determine that the multi-NIC link repair of the server is complete if the status information of the logical NIC and the physical NIC are consistent.

[0225] In one embodiment, prior to the execution of the fourth determining submodule, the maintenance device further includes:

[0226] The fifth judgment submodule is used to determine whether the number of repairs meets the preset repair conditions if the status information of the logical network card and the physical network card are inconsistent.

[0227] The first feedback submodule is used to provide feedback on repair information if the number of repairs meets the repair conditions.

[0228] The sixth update submodule is used to execute the step of updating the association between the logical network card and the physical network card according to the operating system type of the server and the aggregation mode of the logical network card if the number of repairs does not meet the repair conditions.

[0229] In one embodiment, the first feedback submodule includes:

[0230] The fifth determination submodule is used to determine if the repair has failed and to archive the status information of the logical network card and the physical network card.

[0231] A submodule is constructed to build repair information based on the status information of the logical network card and the physical network card, the execution time, and the repair failure information.

[0232] The second feedback submodule is used to provide feedback on the repair information so that the target user is aware of the repair information.

[0233] Each module in the aforementioned maintenance device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0234] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 14 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores runtime data. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements an operational method.

[0235] Those skilled in the art will understand that Figure 14 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specifically, the computer device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0236] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0237] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0238] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0239] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0240] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0241] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. An operation and maintenance method, characterized in that, The operation and maintenance method is applied to servers in a state of aggregation with multiple network interface card links, and the method includes: Obtain the status information of the logical network interface card (NIC) and the physical NIC corresponding to the logical NIC in the multi-NIC link; When the status information of the logical network card is enabled, the physical network card associated with the logical network card is identified as the original physical network card; it is then determined whether the status information of each original physical network card is consistent with that of the logical network card. When the status information of the logical network interface card (NIC) and the physical network interface card (NIC) is inconsistent, the association between the logical NIC and the physical NIC is updated according to the operating system type of the server and the aggregation mode of the logical NIC. This updating includes: if the operating system type is a first operating system type, updating the information of the original physical NIC in the configuration information of the logical NIC to the information of the target physical NIC, thus obtaining an updated association between the logical NIC and the physical NIC; if the operating system type is a second operating system type, deleting the association with the logical NIC from the configuration information of the original physical NIC, and adding the association with the logical NIC from the configuration information of the target physical NIC, thus associating the target physical NIC with the logical NIC; the target physical NIC is a physical NIC whose status information is consistent with the logical NIC and which has established a new association with the logical NIC. Restart the network service, and if the preset verification conditions are met, confirm that the multi-NIC link repair of the server is complete; The step of determining that the multi-NIC link repair of the server is complete under the condition of meeting preset verification conditions includes: Obtain the status information of the logical network interface card and the physical network interface card corresponding to the logical network interface card; Determine whether the status information of the logical network interface card (NIC) and the physical NIC are consistent; If the status information of the logical network card and the physical network card are consistent, it is determined that the multi-NIC link repair of the server is complete.

2. The method according to claim 1, characterized in that, Before obtaining the status information of the logical network interface card (NIC) and the physical NIC corresponding to the logical NIC in the multi-NIC link, the operation and maintenance method further includes: If the server type is the target server type, obtain the operating system type of the server; Determine the multi-NIC configuration file address directory based on the operating system type; In the multi-NIC configuration file address directory, traverse all configuration files in the multi-NIC configuration file address directory to determine whether the target multi-NIC configuration file exists; If the target multi-NIC configuration file exists, confirm that the server is in a multi-NIC link aggregation state.

3. The method according to claim 1, characterized in that, The step of updating the association between the logical network interface card (NIC) and the physical NIC according to the aggregation mode of the logical NIC includes: Determine whether the aggregation mode of the logical network interface card is a primary / backup aggregation mode; When the aggregation mode of the logical network interface card is master-slave aggregation mode, update the master physical network interface card parameter of the logical network interface card to the name of the target physical network interface card.

4. The method according to claim 1, characterized in that, Before determining that the multi-NIC link repair of the server is complete, if the status information of the logical NIC and the physical NIC are consistent, the method further includes: If the status information of the logical network card and the physical network card are inconsistent, determine whether the number of repairs meets the preset repair conditions; If the number of repair attempts meets the repair conditions, repair information is fed back. If the required number of repair attempts does not meet the repair conditions, the step of updating the association between the logical network card and the physical network card based on the server's operating system type and the aggregation mode of the logical network card is executed.

5. The method according to claim 4, characterized in that, If the number of repairs meets the repair conditions, repair information is fed back, including: Determine if the repair fails and archive the status information of the logical network interface and the physical network interface; Repair information is constructed based on the status information of the logical network card and the physical network card, the execution time, and the repair failure information; The repair information is fed back so that the target user is aware of the repair information.

6. A maintenance device, characterized in that, The maintenance device is applied to servers in a multi-NIC link aggregation state, and the device includes: The acquisition module is used to acquire the status information of the logical network interface card (NIC) and the physical NIC corresponding to the logical NIC in the multi-NIC link; The judgment module is used to determine the physical network card associated with the logical network card as the original physical network card when the status information of the logical network card is enabled; and to determine whether the status information of each original physical network card is consistent with that of the logical network card. An update module is used to update the association between the logical network interface card (NIC) and the physical network interface card (NIC) based on the server's operating system type and the aggregation mode of the logical NIC when the status information of the logical NIC and the physical NIC are inconsistent. The update module includes a first update submodule and a second update submodule. The first update submodule includes a third update submodule and a fourth update submodule. The third update submodule, when the operating system type is a first operating system type, updates the information of the original physical NIC in the configuration information of the logical NIC to the information of the target physical NIC, obtaining the updated association between the logical NIC and the physical NIC. The fourth update submodule, when the operating system type is a second operating system type, deletes the association with the logical NIC from the configuration information of the original physical NIC and adds the association with the logical NIC to the configuration information of the target physical NIC, thus associating the target physical NIC with the logical NIC. The target physical NIC is a physical NIC whose status information is consistent with the logical NIC and which has established a new association with the logical NIC. The determination module is used to restart the network service and, under the condition that the preset verification conditions are met, determine that the multi-NIC link repair of the server is complete; The determining module includes a restart submodule and a third determining submodule, wherein the third determining submodule includes: The second acquisition submodule is used to acquire the status information of the logical network card and the physical network card corresponding to the logical network card; The fourth judgment submodule is used to determine whether the status information of the logical network card and the physical network card are consistent; The fourth determination submodule is used to determine that the multi-NIC link repair of the server is complete if the status information of the logical NIC and the physical NIC are consistent.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images