Method for configuring network controller and computing device
By receiving and storing packet identification messages from the Management Control Center, parsing and initializing NCSI services, the complexity and compatibility issues caused by setting Package ID by hardware Pin pins is solved, and a wider configuration function is achieved.
Patent Information
- Application Number
- CN202510402395.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-31
- Publication Date
- 2025-07-18
AI Technical Summary
In the prior art, the management control center equipment sets the Package ID value of the network controller by adjusting the voltage level by the hardware Pin pin, which increases the complexity and cost of hardware design and limits the compatibility and scalability of the system.
The network controller receives the data packet identification message set by the management control center, parses and stores it in non-volatile memory, initializes the NCSI service, and determines whether to receive NCSI protocol data based on the data packet identification value, reducing dependence on hardware modification.
It reduces hardware design complexity, saves costs, improves system compatibility and scalability, and makes the configuration function use scenarios more extensive.
Smart Images

Figure CN120342866A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of software development, and particularly relates to a method for configuring a network controller and a computing device. Background Art
[0002] In the fields of computing and server management, a management control center (BMC, Baseboard Management Controller) is used to monitor hardware status, perform remote management, and control the operation of a server. In the prior art, the management control center device adjusts the voltage level through hardware pins (Pin pins) to set the value of a packet identifier (Package ID). The current technical solution requires considering adding Pin pins during the hardware design process, which increases the complexity of the hardware design and has weak compatibility, adding additional design requirements and thus increasing the design complexity. Moreover, there are also requirements for the management control center device, and Pin pins need to be reserved to connect to the Pin pins used to set the Package ID in the network controller, so that the network controller can set the Package ID through the Pin pins. This results in that the management control center device without reserved Pin pins cannot configure the Package ID and cannot work properly in the scenario of multiple network controllers.
[0003] Therefore, a technical solution is needed that can reduce the complexity of the hardware design, save design costs, reduce the dependence on hardware modification, and improve the overall compatibility and scalability of the system, making the usage scenarios of the configuration function more extensive. Summary of the Invention
[0004] The present invention aims to provide a method for configuring a network controller and a computing device, which can reduce the complexity of the hardware design, save design costs, reduce the dependence on hardware modification, and improve the overall compatibility and scalability of the system, making the usage scenarios of the configuration function more extensive.
[0005] According to one aspect of the present invention, there is provided a method for configuring a network controller, the method comprising:
[0006] The network controller receives a message for setting a packet identifier from the management control center through a first network interface, and the packet identifier is used to identify the network controller;
[0007] The network controller parses the message for setting the packet identifier to obtain a packet identifier value;
[0008] The network controller stores the packet identifier value in a non-volatile memory and notifies the management control center of a successful setting message;
[0009] The network controller initializes the NCSI service according to the packet identification value;
[0010] After the initialization of the NCSI service is completed, the network controller starts to receive and process subsequent NCSI protocol data, where the network controller determines whether to receive the NCSI protocol data according to the packet identification value.
[0011] According to some embodiments, the network controller parses the set packet identification message according to the message format, and the message format includes a command type, an identification direction, a message length, and a message content;
[0012] The command type identifies the message task content;
[0013] The identification direction is a request direction and a response direction;
[0014] The message length represents the length of the message content;
[0015] The length of the message content is determined according to the actual message content.
[0016] According to some embodiments, when the command type is set packet identification and the identification direction is the request direction, the message content is the packet identification value;
[0017] When the command type is set packet identification and the identification direction is the response direction, the message content is the command execution result.
[0018] According to some embodiments, the network controller stores the packet identification value in a non-volatile memory, including:
[0019] Storing the packet identification value at the starting offset of N bytes in the non-volatile memory, where N is less than 512.
[0020] According to some embodiments, the network controller determines whether to receive the NCSI protocol data according to the packet identification value, including:
[0021] When the packet identification value in the packet header of the NCSI protocol data is the same as the packet identification value stored in the non-volatile memory, the network controller responds to the NCSI protocol data.
[0022] According to some embodiments, the network controller determines whether to receive the NCSI protocol data according to the packet identification value, further including:
[0023] When the packet identification value in the packet header of the NCSI protocol data is different from the packet identification value stored in the non-volatile memory, the network controller rejects the response to the NCSI protocol data.
[0024] According to some embodiments, the packet identification in the same networking environment of the network controller is unique.
[0025] According to another aspect of the present invention, there is provided a network chip, including a processor and a memory, where a computer program is stored on the memory, and when the processor runs the computer program stored on the memory, the method described in any one of the above is implemented.
[0026] According to another aspect of the present invention, there is provided a network interface card, which includes the network chip described above and a plurality of interfaces, and the network chip communicates externally through the plurality of interfaces.
[0027] According to another aspect of the present invention, there is provided a computing device, including: the network interface card described above and a central processing unit, where the network interface card is used to process data or communicate externally, and the central processing unit is used to process the data scheduled by the network interface card.
[0028] According to an embodiment of the present invention, the network controller receives a message for setting a packet identification sent from a management control center through a first network interface, and the ability to set the packet identification through the network interface can reduce the complexity of the hardware design and save the hardware design cost. The network controller parses the message for setting the packet identification, obtains the packet identification value and stores it in the non-volatile memory, ensuring the security of the data and making it not easy to be lost, providing a persistent and reliable storage method for the packet identification value. After the network controller notifies the management control center of the successful setting message, it initializes the NCSI service, and after the initialization is completed, the network controller processes the subsequent NCSI protocol data received through the NCSI network interface. By performing data network transmission at the software level, the present invention can effectively reduce the dependence on hardware modification and improve the overall compatibility and scalability of the system, making the usage scenario of the function of configuring the packet identification more extensive.
[0029] It should be understood that the above general description and the following detailed description are only exemplary and do not limit the present invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments.
[0031] Figure 1 A flowchart showing a method for configuring a network controller according to an exemplary embodiment.
[0032] Figure 2 A schematic diagram showing the communication between a network controller and a management control center according to an exemplary embodiment.
[0033] Figure 3 A schematic diagram showing the definition of a non-volatile memory storage area according to an exemplary embodiment.
[0034] Figure 4 A block diagram showing a computing device according to an exemplary embodiment. Detailed implementation manners
[0035] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments can be implemented in various forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. Like reference numerals in the figures denote like or similar parts, and thus their repetitive description will be omitted.
[0036] In addition, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of the embodiments of the present invention. However, those skilled in the art will realize that the technical solutions of the present invention can be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. may be employed. In other cases, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the present invention.
[0037] The block diagrams shown in the drawings are only functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0038] The flowcharts shown in the drawings are only illustrative and do not necessarily include all the contents and operations / steps, nor do they necessarily have to be executed in the described order. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to the actual situation.
[0039] It should be understood that although terms such as first, second, and third may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another. Thus, the first component discussed below may be referred to as the second component without departing from the teachings of the concept of the present invention. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.
[0040] Those skilled in the art can understand that the drawings are only schematic diagrams of the exemplary embodiments, and the modules or processes in the drawings are not necessarily essential for implementing the present invention. Therefore, they cannot be used to limit the protection scope of the present invention.
[0041] Traditionally, in order to set certain specific parameters or identifiers, such as Package ID, the BMC may need to use hardware pins. These pins can be connected to different voltage levels, allowing the system to identify the corresponding settings or states based on the applied voltage.
[0042] For example, in the traditional technical solution, the NCSI (Network Controller Sideband Interface) management control center (i.e., BMC) sets the Package ID value by adjusting the voltage level through hardware pins. For example, in NVIDIA's Bulefiled-3 series, 2 pins are used in the NCSI function management interface for setting, namely PKG_ID0 and PKG_ID1. The correspondence between the values of PKG_ID0 and PKG_ID1 and the Package ID value is shown in Table 1:
[0043] Table 1
[0044] PKG_ID1 PKG_ID0 PackageID 0 0 0 0 1 1 1 0 2 1 1 3
[0045] This method requires that additional pins must be considered during hardware design, which increases the complexity of the circuit board design. With the change of requirements or the introduction of new hardware versions, more pins may be needed to support new configurations, which poses challenges to the existing design and limits the flexibility and backward compatibility of the system. Each additional pin means an increased demand for precious circuit board space, which is particularly critical in highly integrated designs. Although this hardware pin-based method is direct and effective, it gradually shows its limitations in modern server designs, especially in the context of pursuing higher flexibility and maintainability. Therefore, the industry trend is towards more flexible solutions.
[0046] Therefore, the present invention proposes a method for configuring packet identifiers, which can reduce the complexity of hardware design, save design costs, reduce the dependence on hardware modification, and improve the overall compatibility and scalability of the system, making the usage scenarios of the configuration function more extensive.
[0047] The exemplary embodiments of the present invention will be described below with reference to the drawings.
[0048] Figure 1 A flowchart of a method for configuring a network controller according to an exemplary embodiment is shown.
[0049] See Figure 1 In S101, the network controller receives, through a first network interface, a setup data packet identification message from a management control center, where the data packet identification is used to identify the network controller.
[0050] According to some embodiments, the network controller parses the setup data packet identification message according to a message format, where the message format includes a command type, an identification direction, a message length, and a message content.
[0051] According to some embodiments, the command type identifies the message task content; the identification direction is a request direction and a response direction; the message length represents the length of the message content; and the length of the message content is determined according to the actual message content.
[0052] According to some embodiments, the message format transmitted between the network controller and the management control center through the first network interface is defined in Table 2:
[0053] Table 2
[0054] CMD_ID(31bit) Direct(1bit) Length(2 bytes) Payload(of variable length)
[0055] In the message format, the length of the CMD_ID field occupies 31 bits, and its meaning is the command type, which identifies the operation to be performed by the message. For example, CMD_ID = 0x1 represents setting the PackageID, and CMD_ID = 0x2 represents querying the temperature. The length of the Direct field occupies 1 bit, and its meaning is to identify the message direction. Direct = 0x0 represents that the message is in the request direction, and Direct = 0x1 represents that the message is in the response direction. The length of the Length field occupies 2 bytes, which identifies the length of the message content, that is, the length of the Payload. The length of the Payload field depends on the length of the specific message content and is not of a fixed length. Payload is the specific content of the message.
[0056] According to some embodiments, when the command type is setting the data packet identification and the identification direction is the request direction, the message content is the data packet identification value; when the command type is setting the data packet identification and the identification direction is the response direction, the message content is the command execution result.
[0057] For the Payload content in the Set PackageID request message, it is the Package ID value and only occupies 1B in size. For the Payload content in the Set PackageID response message, it is whether the command execution is successful and occupies 1B in size, where 0 represents success, and other values represent failures for different reasons.
[0058] According to some embodiments, the BMC can transmit message data for configuring the Package ID through any transmission interface with the network controller. After receiving the message, the network controller stores the Package ID in a storage device to prevent information loss after a restart.
[0059] According to some embodiments, the interfaces between the BMC and the network controller can be RMII, UART, I2C, etc., and the devices for storing the Package ID in the network controller can be Flash (flash memory) and eeprom (Electrically Erasable Programmable Read-Only Memory), etc. The selection criterion for the interface is that messages can be transmitted between the BMC and the network controller through this interface, and the selection criterion for the memory is that the network controller can read and write to this memory and the information is not lost after power-off.
[0060] See Figure 2 , in this invention, taking the I2C interface and Flash memory as examples, it is designed that the interfaces between the BMC and the network controller transmit messages for setting the Package ID through the I2C interface, and the network controller stores the Package ID information in the Flash.
[0061] According to some embodiments, the network controller receives the message for configuring the Package ID sent by the BMC through the first network interface (I2C interface). For example, if the Package ID is set to 2, then in the message format, CMD_ID = 0x1, Direct = 0x0, Length = 0x1, Payload = 0x2, and the content is shown in Table 3:
[0062] Table 3
[0063] Address 1B 2B 3B 4B 5B Content 0x00 0x02 0x00 0x01 0x02
[0064] According to some embodiments, the packet identifier of network devices in the same networking environment is unique. The Package IDs of different network devices in the same network must be different.
[0065] The Package ID value is a necessary value for the device. If the Package ID value is not set, the default value will be adopted. To distinguish the Package IDs of each device, it is necessary to ensure that the Package ID values of different devices are different. If there is only one device, then the Package ID value does not need to be set and the default value can be adopted. If there are two or more devices at the same time and the Package IDs of the two devices are both the default value 0 and cannot be distinguished, then the functions of the management control center will be unavailable.
[0066] In S103, the network controller parses the setting data packet identification message to obtain the data packet identification value.
[0067] According to some embodiments, the network controller receives an I2C message, parses the message according to the message format, and obtains the value of PackageID. For example, in S101, a message with the message format of CMD_ID = 0x1, Direct = 0x0, Length = 0x1, Payload = 0x2 is received, and the value of the Package ID parsed is 2.
[0068] In S105, the network controller stores the data packet identification value in a non-volatile memory and notifies the management control center of the successful setting message.
[0069] According to some embodiments, the data packet identification value is stored at the starting offset of N bytes in the non-volatile memory, where N is less than 512. Refer to Figure 3 , the network controller stores the Package ID value at a specified location in the flash memory (Flash), that is, at the starting offset of 256B - 260B of the Flash storage.
[0070] According to some embodiments, after the network controller stores the Package ID value in the Flash successfully, it will send a response message to notify the BMC of the message that the Package ID value has been set successfully. In the message, CMD_ID = 0x1, Direct = 0x1, Length = 0x1, Payload = 0x0, and the content is shown in Table 4:
[0071] Table 4
[0072] Address 1B 2B 3B 4B 5B Content 0x00 0x03 0x00 0x01 0x00
[0073] According to some embodiments, the network controller stores the value of the Package ID in the Flash to prevent information loss after a restart. The Flash memory can retain data even after a power outage, can save information without continuous power supply, and is suitable for long-term storage.
[0074] According to some embodiments, compared with traditional mechanical hard disks (HDDs), the Flash memory has faster read and write speeds, can significantly improve the system response speed and data transmission efficiency. The Flash memory has lower power consumption, is small in size and light in weight, is convenient to be integrated into various devices, and can save device space. The Flash memory has a lower failure rate, more stable data storage, and supports multiple erase and write operations, and is suitable for application scenarios that require frequent data updates.
[0075] In S107, the network controller initializes the NCSI service according to the data packet identification value.
[0076] According to some embodiments, after the network controller successfully stores the Package ID value in the Flash, it will re-initialize the NCSI-related services.
[0077] In S109, after the network controller completes the initialization of the NCSI service, it starts to receive and process subsequent NCSI protocol data. Among them, the network controller determines whether to receive the NCSI protocol data according to the packet identification value.
[0078] According to some embodiments, when the packet identification value in the header of the NCSI protocol data is the same as the packet identification value stored in the non-volatile memory, the network controller responds to the NCSI protocol data. When the packet identification value in the header of the NCSI protocol data is different from the packet identification value stored in the non-volatile memory, the network controller refuses to respond to the NCSI protocol data.
[0079] According to some embodiments, after the initialization of the NCSI-related services is completed, the network controller will receive and process the NCSI control commands whose Package ID value in the header sent by the BMC is the same as the Package ID setting value stored in the Flash, and refuses to respond to those NCSI control commands whose Package ID value does not match the current setting value.
[0080] According to some embodiments, the NCSI network interface can adopt multiple network interfaces, such as the RMII (Reduced Media Independent Interface) interface.
[0081] According to some embodiments, the network controller first loads the Package ID when starting up. When the network controller starts up and the Package ID has not been set, the default value is used for initialization. If the value of the Package ID has been set previously, the network controller can obtain the set Package ID value without restarting. For example, in step S107, when initializing the NCSI-related services, the network controller obtains the value of the Package ID from the Flash. After the network controller is initialized, it starts to receive and process the NCSI protocol data whose Package ID in the header is the same as the Package ID value stored in the Flash.
[0082] According to some embodiments, the network controller initializes NCSI-related services based on the Package ID value. When initializing the NCSI service, the Package ID value is obtained from different addresses. The difference between the present invention and the existing general solution is that the existing general solution obtains the Package ID value from a hardware Pin, while the present solution reads it from Flash. The present invention can reduce the complexity of hardware design, save design costs, reduce the dependence on hardware modification, and improve the overall compatibility and scalability of the system, making the usage scenarios of the configuration function more extensive.
[0083] The present invention also provides a network chip, such as a DPU chip, including a processor and a memory. A computer program is stored on the memory. When the processor runs the computer program stored on the memory, the method for configuring a network controller as described in any one of the embodiments is implemented.
[0084] The present invention also provides a network interface card. The network interface card includes the network chip as described above and a plurality of interfaces. Among them, the interfaces can include PCI / PCIE interfaces, UART interfaces, SPI interfaces, USB interfaces, network interfaces, etc. The network chip communicates externally through the plurality of interfaces.
[0085] The present invention also provides a computing device, including: the network interface card as described above and a central processing unit. The network interface card is used to process data or communicate externally, and the central processing unit is used to process the data dispatched by the network interface card.
[0086] Figure 4 A block diagram of a computing device according to an exemplary embodiment of the present invention is shown.
[0087] As Figure 4 shown, the computing device 30 includes a processor 12 and a memory 14. The computing device 30 may further include a bus 22, a network interface card 16, and an I / O interface 18. The processor 12, the memory 14, the network interface card 16, and the I / O interface 18 can communicate with each other through the bus 22.
[0088] The processor 12 may include one or more general-purpose CPUs (Central Processing Unit, processors), microprocessors, or application-specific integrated circuits, etc., for executing relevant program instructions. According to some embodiments, the computing device 30 may further include a high-performance display adapter (GPU) 20 for accelerating the processor 12.
[0089] The memory 14 may include machine system-readable media in the form of volatile memory, such as random access memory (RAM), read-only memory (ROM), and / or cache memory. The memory 14 is used to store one or more programs containing instructions as well as data. The processor 12 can read the instructions stored in the memory 14 to execute the methods according to the embodiments of the present invention described above.
[0090] The computing device 30 can also communicate with one or more networks through the network interface card 16. The network interface card 16 can be a DPU intelligent network card.
[0091] The bus 22 can include an address bus, a data bus, a control bus, etc. The bus 22 provides a path for exchanging information between components.
[0092] It should be noted that in the specific implementation process, the computing device 30 may further include other components necessary for normal operation. In addition, those skilled in the art can understand that the above devices may also only include the components necessary to implement the solution of the embodiments of this specification, and do not necessarily include all the components shown in the figure.
[0093] The present invention also provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps of the above method are implemented. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, DVDs, CD-ROMs, microdrives, and magneto-optical disks, ROM, RAM, EPROM, EEPROM, DRAM, VRAM, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), network storage devices, cloud storage devices, or any type of medium or device suitable for storing instructions and / or data.
[0094] The embodiments of the present invention also provide a computer program product, which includes a computer program that can be operated to cause a computer to execute some or all of the steps of any one of the methods described in the above method embodiments.
[0095] Those skilled in the art can clearly understand that the technical solutions of the present invention can be implemented by means of software and / or hardware. The "units" and "modules" in this specification refer to software and / or hardware that can independently complete or cooperate with other components to complete specific functions, where the hardware can be, for example, a field programmable gate array, an integrated circuit, etc.
[0096] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.
[0097] In the above embodiments, the descriptions of the respective embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0098] In several embodiments provided by the present invention, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection to each other can be through some service interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical or other form.
[0099] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place, or can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0100] In addition, the functional units in each embodiment of the present invention can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.
[0101] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in each embodiment of the present invention.
[0102] In the above embodiments, each embodiment is described with emphasis on different aspects. For parts not detailed in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.
[0103] The above has specifically shown and described exemplary embodiments of the present invention. It should be understood that the present invention is not limited to the detailed structures, arrangements, or implementation methods described herein; rather, the present invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims
1. A method for configuring a network controller, the method comprising: The network controller receives a setup data packet identification message from a management control center through a first network interface, and the data packet identification is used to identify the network controller; The network controller parses the setup data packet identification message to obtain a data packet identification value; The network controller stores the data packet identification value in a non-volatile memory and notifies the management control center of a setup success message; The network controller initializes the NCSI service according to the data packet identification value; After the initialization of the NCSI service is completed, the network controller starts to receive and process subsequent NCSI protocol data, wherein the network controller determines whether to receive the NCSI protocol data according to the data packet identification value.
2. The method according to claim 1, wherein The network controller parses the setup data packet identification message according to a message format, and the message format includes a command type, an identification direction, a message length, and a message content; The command type identifies the message task content; The identification direction is a request direction and a response direction; The message length represents the length of the message content; The length of the message content is determined according to the actual message content.
3. The method according to claim 2, characterized in that, When the command type is setup data packet identification and the identification direction is the request direction, the message content is the data packet identification value; When the command type is setup data packet identification and the identification direction is the response direction, the message content is the command execution result.
4. The method according to claim 1, wherein The network controller storing the data packet identification value in the non-volatile memory includes: Storing the data packet identification value at a starting offset of N bytes in the non-volatile memory, where N is less than 512.
5. The method according to claim 1, characterized in that, The network controller determining whether to receive the NCSI protocol data according to the data packet identification value includes: When the data packet identification value in the packet header of the NCSI protocol data is the same as the data packet identification value stored in the non-volatile memory, the network controller responds to the NCSI protocol data.
6. The method according to claim 5, characterized in that, The network controller determining whether to receive the NCSI protocol data according to the data packet identification value further includes: When the data packet identification value in the packet header of the NCSI protocol data is different from the data packet identification value stored in the non-volatile memory, the network controller refuses to respond to the NCSI protocol data.
7. The method according to claim 1, wherein The data packet identification of the network controller in the same networking environment is unique.
8. A network chip, comprising a processor and a memory, characterized in that, A computer program is stored on the memory, and when the processor runs the computer program stored on the memory, the method according to any one of claims 1 to 7 is implemented.
9. A network interface card, characterized in that, The network interface card includes the network chip according to claim 8 and a plurality of interfaces, and the network chip communicates externally through the plurality of interfaces.
10. A computing device, characterized in that, Comprising: The network interface card according to claim 9 and a central processing unit, the network interface card is used to process data or communicate externally, and the central processing unit is used to process the data dispatched by the network interface card.