Network interface card (NIC) information acquisition methods, devices, servers, and storage media

Abstract

The application discloses a network card information acquisition method and device, a server and a storage medium. The method comprises the following steps: acquiring the media access control (MAC) address of each network card through an out-of-band management interface of the server based on the first information of each network card in at least one network card, wherein the first information represents the installation position of the network card in the server; acquiring the second information of each network card in the server in-band based on the acquired MAC address of each network card, wherein the second information at least comprises the logical name of the network card in the operating system deployed in the server.

Description

Technical Field

[0001] This application relates to the field of network technology, and in particular to a method, apparatus, server and storage medium for obtaining network interface card (NIC) information. Background Technology

[0002] When deploying operating systems in scenarios such as cloud platforms and private networks, configuration operations such as multi-NIC bonding require manually obtaining the logical names of the NICs before the configuration operation, which affects configuration efficiency. Summary of the Invention

[0003] To address the related technical issues, embodiments of this application provide a method, apparatus, server, and storage medium for obtaining network interface card (NIC) information.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides a method for obtaining network interface card (NIC) information, applied to a server, including:

[0006] Based on the first information of each of at least one network interface card (NIC), the Media Access Control (MAC) address of each NIC is obtained through the out-of-band management interface of the server; the first information indicates the installation location of the NIC in the server.

[0007] Based on the obtained MAC address of each network card, second information of each network card is obtained within the band of the server; the second information includes at least the logical name of the network card in the operating system deployed on the server.

[0008] In the above scheme, the second information also includes at least one of the following:

[0009] The capabilities of the network interface card;

[0010] The configuration of the network card.

[0011] In the above scheme, the first information includes the physical slot number and / or physical port number of the network card.

[0012] In the above scheme, the out-of-band management interface includes the Redfish Extensible Platform Management Application Programming Interface (API) or the Intelligent Platform Management Interface (IPMI).

[0013] The method in the above scheme further includes:

[0014] Based on the second information of each network card obtained, a binding operation is performed on the at least one network card.

[0015] The method in the above scheme further includes:

[0016] The first information is output through the out-of-band management interface of the server.

[0017] This application embodiment also provides a network interface card (NIC) information acquisition device, including:

[0018] The first acquisition unit is used to acquire the MAC address of each network card through the out-of-band management interface of the server based on the first information of each network card in at least one network card; the first information represents the installation location of the network card in the server.

[0019] The first acquisition unit is used to acquire second information of each network card within the band of the server based on the acquired MAC address of each network card; the second information includes at least the logical name of the network card in the operating system deployed on the server.

[0020] This application also provides a server, including: a first processor and a first communication interface; wherein,

[0021] The first communication interface is used to obtain the MAC address of each network card through the out-of-band management interface of the server based on the first information of each network card in at least one network card; the first information indicates the installation location of the network card in the server;

[0022] The first processor is configured to obtain second information of each network card within the server based on the obtained MAC address of each network card; the first information includes at least the logical name of the network card in the operating system deployed on the server.

[0023] This application also provides a server, including: a first processor and a first memory for storing computer programs capable of running on the processor.

[0024] Wherein, when the first processor is used to run the computer program, it executes the steps of any of the above-described network card information acquisition methods.

[0025] This application embodiment also provides a storage medium storing a computer program that, when executed by a processor, implements the steps of any of the network interface card information acquisition methods.

[0026] The network interface card (NIC) information acquisition method, apparatus, server, and storage medium provided in this application embodiment involve the server obtaining the MAC address of each NIC through its out-of-band management interface, based on the installation location of each NIC within the server. Then, based on the obtained MAC address, the server retrieves the NIC information configured within the server, such as the logical name of the NIC in the operating system, from within its own bandwidth. Based on this scheme, NIC information can be automatically obtained automatically in relevant configuration scenarios simply by intuitively determining the NIC's installation location on the server, ensuring the accuracy and efficiency of NIC information acquisition and thereby improving server configuration efficiency. Attached Figure Description

[0027] Figure 1 This is a schematic diagram illustrating the implementation process of the network card information acquisition method in an embodiment of this application;

[0028] Figure 2 This is a schematic diagram of the network card information acquisition device according to an embodiment of this application;

[0029] Figure 3 This is a schematic diagram of the server structure in an embodiment of this application. Detailed Implementation

[0030] When deploying operating systems in scenarios such as cloud platforms and private networks, configuration operations such as multi-NIC bonding require obtaining the logical names of the NICs within the corresponding operating system before further NIC configuration can proceed. Currently, the logical names of NICs are obtained manually. However, in scenarios with multiple changing factors, such as diverse product hardware and operating system selections, obtaining the logical names of NICs becomes complex and error-prone, impacting configuration efficiency.

[0031] Based on this, in various embodiments of this application, the server obtains the MAC address of each network interface card (NIC) through its out-of-band management interface, based on the installation location of each NIC within the server. Then, based on the obtained MAC address, the server retrieves the NIC information configured within the server, such as the logical name of the NIC in the operating system, from within its own bandwidth. This solution allows for automatic NIC information retrieval in relevant configuration scenarios simply by intuitively determining the NIC's installation location on the server, ensuring the accuracy and efficiency of NIC information acquisition and thus improving server configuration efficiency.

[0032] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0033] This application provides a method for obtaining network interface card (NIC) information. This method can be applied to servers, such as bare-metal servers and other servers that require NIC configuration. (Refer to...) Figure 1 The method includes:

[0034] Step 101: Based on the first information of each network card in at least one network card, obtain the MAC address of each network card through the out-of-band management interface of the server.

[0035] The first information represents the installation location of the network card in the server.

[0036] Here, the first piece of information represents the installation location of the network card in the server, including the physical slot in which the network card is installed in the server and / or the physical network port connected in the physical slot.

[0037] Considering that in a batch of servers with identical specifications, the physical slots are distributed uniformly, but the MAC addresses of the network cards deployed on each physical port of each physical slot are necessarily different, we can first obtain the MAC addresses of the network cards through the server's out-of-band management interface. Then, based on the uniqueness of the MAC address, we can obtain the logical name of the network card within the server's in-band. Specifically, we can use the server specifications as a tag to pre-store or register the distribution of physical slots and physical ports of servers with that specifications in the out-of-band management interface. In this way, the out-of-band management interface can uniquely identify a network card deployed on that server based on the server specifications and the first piece of information, thereby returning the MAC address of that network card.

[0038] The server's out-of-band management interface can be implemented through management software and a cloud platform for remote management and monitoring of the server. In one embodiment, the out-of-band management interface includes the Redfish API or IPMI.

[0039] In practical applications, it is necessary to determine which out-of-band management interface to use to obtain the MAC address of the network card based on the out-of-band management interface supported by the server.

[0040] As one implementation method, the first piece of information can be represented as a number or code to more easily and intuitively describe the physical slot in which the network card is installed in the server and / or the physical network port connected in the physical slot.

[0041] Based on this, in one embodiment, the first information includes the physical slot number and / or physical port number of the network card.

[0042] Here, the first information can also be described as the physical location number of the network interface card (NIC) in the server, which is used to uniquely identify a NIC in the server. For example, if the NIC is deployed in the second physical slot on the server backplane and connected to the first physical port on the second physical slot, then the first information of the NIC can be represented as "slot 2-1". In practical applications, the first information can also represent the physical slot number and / or physical port number corresponding to the NIC in other specified formats. For example, "slot 2-1" above can also be represented as "slot 2.1", "slot 2 / 1", "slot ba", "slotb.a" or "slot b / a", without limitation here.

[0043] Considering the diversity of physical location number descriptions, in practical applications, regular expressions can be used to map physical location numbers with different descriptions to a unified format. For example:

[0044] “slot4 / 1” is mapped to (PCIeRiser2PCIeCard4[(]SP380[)]Port1)

[0045] “slot4 / 2” is mapped to (PCIeRiser2PCIeCard4[(]SP380[)]Port2)

[0046] “slot5 / 1” is mapped to (slot5[(]SP580[)] / 1|PCIeRiser2PCIeCard5[(]SP380[)]Port1)

[0047] “slot5 / 2” is mapped to (slot5[(]SP580[)] / 2|PCIeRiser2PCIeCard5[(]SP380[)]Port2)

[0048] Understandably, each physical location number uniquely corresponds to one network interface card (NIC), which in turn uniquely corresponds to one MAC address. Therefore, based on the management functions provided by the out-of-band management interface, the out-of-band management interface can return the MAC address of the NIC according to the first reported information.

[0049] For example, for the Redfish API, the MAC address of the network interface card can be obtained using the following code statement:

[0050] First, obtain the network card model of the network card configured on the server through " / redfish / v1 / Chassis / 1 / NetworkAdapters".

[0051] Secondly, via " / redfish / v1 / Chassis / 1 / NetworkAdapters / <netcard_name> The command retrieves the physical location number of the network interface card (NIC) within the server.<netcard_name> This refers to the network card model.

[0052] Then, through:

[0053] " / redfish / v1 / Chassis / 1 / NetworkAdapters / <netcard_name> / NetworkPorts / <net port> / ”

[0054] Obtain the MAC address of the network card corresponding to the physical location number, where, <netport>This is the physical location number of the network card.

[0055] Step 102: Based on the obtained MAC address of each network card, obtain the second information of each network card within the band of the server.

[0056] The second information includes at least the logical name of the network card in the operating system deployed on the server.

[0057] Here, based on the MAC address of each network card returned by the out-of-band management interface, the network card information matching the MAC address can be queried in the server's in-band, including the logical name of the network card, so as to be used for further configuration in the server's operating system based on the logical name of the network card.

[0058] In practical applications, you can obtain detailed information about the network card by executing the "lshw -c network" command in the in-band operating system, including the network card's MAC address and its logical name in the in-band operating system.

[0059] For example, by executing the "lshw -c network" command in the in-band operating system, the following information is obtained:

[0060]

[0061] Here, "logical name:eno2" is the logical name of the network card in the operating system within the band, and "serial:08:3a:88:15:f4:9c" is the MAC address of the network card.

[0062] In one embodiment, the first information further includes at least one of the following:

[0063] The capabilities of the network interface card;

[0064] The configuration of the network card.

[0065] See the following example of network card capability feedback:

[0066]

[0067] See the following network card configuration feedback example:

[0068]

[0069]

[0070] In this embodiment of the application, the obtained network card information can be used for multi-NIC bonding in scenarios such as Network Functions Virtualization (NFV) and private network physical slot information binding.

[0071] In one embodiment, the method further includes:

[0072] Based on the first information of each network card obtained, a binding operation is performed on the at least one network card.

[0073] The following application examples further illustrate the binding of multiple network interface cards (NICs).

[0074] The network interface card (NIC) can have different configuration information on different operating system platforms. For example, as shown in Table 1, the NIC for the first physical port in the second physical slot on the server backplane, i.e., the NIC with physical port number "slot2-1", is configured with the logical name "ens6f0" in operating system OS1, and "enp189s2f0" in operating system OS2. The physical port number is the first piece of information corresponding to the NIC.

[0075] Table 1

[0076]

[0077] In this application example, network interface card 1 (NIC 1) and network interface card 2 (NIC 2) need to be bound. As shown in Table 2, NIC 1 and NIC 2 are bound on the management side by configuring the logical name "ens6f0" for NIC 1 and the logical name "ens16f1" for NIC 2; NIC 1 and NIC 2 are bound on the service side by configuring the logical name "ens16f0" for NIC 1 and the logical name "ens6f1" for NIC 2.

[0078] Table 2

[0079] Network card 1 Network card 2 Management side - bond ens6f0 ens16f1 Business side - bond ens16f0 ens6f1

[0080] In related technologies, when binding network interface cards (NICs) in the management plane and the service plane, it is necessary to obtain the logical names of NIC 1 and NIC 2 in the management plane and the service plane, respectively. However, based on the solution of this application embodiment, it is only necessary to determine the physical port numbers of NICs 1 and NIC 2 according to their installation locations in the server. As shown in Table 3, when binding NICs in the management plane, NIC 1 is located on the first physical port in the first physical slot on the server backplane, with the corresponding physical port number "slot1-1". NIC 2 is located on the second physical port in the second physical slot on the server backplane, with the corresponding physical port number "slot2-2". Based on the physical port number "slot1-1", the logical name of NIC 1 in the management plane, "ens6f0", can be obtained; based on the physical port number "slot2-2", the logical name of NIC 2 in the management plane, "ens16f1", can be obtained. Similarly, when binding network interface cards (NICs) in the service plane, NIC 1 is located on the first physical port of the second physical slot on the server backplane, with the corresponding physical port number "slot2-1". NIC 2 is located on the second physical port of the first physical slot on the server backplane, with the corresponding physical port number "slot1-2". Then, through the out-of-band management interface, the logical name "ens16f0" of NIC 1 in the management plane can be obtained based on the physical port number "slot2-1", and the logical name "ens6f1" of NIC 2 in the management plane can be obtained based on the physical port number "slot1-2".

[0081] Table 3

[0082] Network card 1 Network card 2 Management side - bond slot1-1 Slot2-2 Business side - bond Slot2-1 Slot 1-2

[0083] In practical applications, during out-of-band management, the Baseboard Management Controller (BMC) can only obtain physical information such as the MAC address of the network card, and cannot obtain the configuration information of the network card in the operating system. Therefore, in one embodiment, the method further includes:

[0084] The second information is output through the out-of-band management interface of the server.

[0085] The following application examples further illustrate the output of the second information by the out-of-band management interface.

[0086] In this embodiment, the operating system configuration can be intuitively performed based on the network interface card's (NIC) installation location on the server backplane, according to the server being used. Specifically, the NIC's installation location, including physical slot information and physical port information, is dynamically resolved out-of-band to obtain the actual NIC MAC address. This allows for the acquisition of more NIC information matching the MAC address within the server's in-band. Based on this embodiment, the product's compatibility with diverse server selections and various operating systems is improved, facilitating automated delivery. In this embodiment, the physical installation location of the NIC and its logical name are associated with its MAC address. Based on this association, more NIC information, including NIC configuration and capabilities, can be mapped, effectively applied to the server's operating system configuration process. Furthermore, the obtained NIC information can be output through the out-of-band management interface, enabling the server's out-of-band management to dynamically acquire in-band NIC information, expanding the application scenarios of this solution.

[0087] To implement the network card information acquisition method of this application embodiment, this application embodiment also provides a network card information acquisition device, which is set on a server, such as... Figure 2 As shown, the device includes:

[0088] The first acquisition unit 201 is used to acquire the MAC address of each network card through the out-of-band management interface of the server based on the first information of each network card in at least one network card; the first information indicates the installation location of the network card in the server.

[0089] The second acquisition unit 202 is used to acquire second information of each network card within the band of the server based on the acquired MAC address of each network card; the second information includes at least the logical name of the network card in the operating system deployed on the server.

[0090] In one embodiment, the second information further includes at least one of the following:

[0091] The capabilities of the network interface card;

[0092] The configuration of the network card.

[0093] In one embodiment, the first information includes the physical slot number and / or physical port number of the network card.

[0094] In one embodiment, the out-of-band management interface includes the Redfish API or IPMI.

[0095] In one embodiment, the device further includes:

[0096] The binding unit is used to perform a binding operation on the at least one network card based on the second information of each network card obtained.

[0097] In one embodiment, the device further includes:

[0098] The output unit is used to output the second information through the out-of-band management interface of the server.

[0099] In practical applications, the first acquisition unit 201 and the output unit can be implemented by the communication interface in the network card information acquisition device; the second acquisition unit and the binding unit can be implemented by the processor in the network card information acquisition device.

[0100] It should be noted that the network card information acquisition device provided in the above embodiments is only illustrated by the division of the above program modules when acquiring network card information. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the network card information acquisition device provided in the above embodiments and the network card information acquisition method embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0101] Based on the hardware implementation of the above program modules, and in order to implement the server-side method of this application embodiment, this application embodiment also provides a server, such as... Figure 3 As shown, server 300 includes:

[0102] The first communication interface 301 is capable of exchanging information with other network nodes;

[0103] The first processor 302 is connected to the first communication interface 301 to enable information interaction with other network nodes and to execute the methods provided by one or more of the aforementioned server-side technical solutions when running a computer program. The computer program is stored in the first memory 303.

[0104] Specifically, the first communication interface 301 is used to obtain the MAC address of each network card through the out-of-band management interface of the server based on the first information of each network card in at least one network card; the first information indicates the installation location of the network card in the server;

[0105] The first processor 302 is configured to obtain second information of each network card within the server based on the obtained MAC address of each network card; the second information includes at least the logical name of the network card in the operating system deployed on the server.

[0106] In one embodiment, the second information further includes at least one of the following:

[0107] The capabilities of the network interface card;

[0108] The configuration of the network card.

[0109] In one embodiment, the first information includes the physical slot number and / or physical port number of the network card.

[0110] In one embodiment, the out-of-band management interface includes the Redfish API or IPMI.

[0111] In one embodiment, the first processor 302 is further configured to:

[0112] Based on the second information of each network card obtained, a binding operation is performed on the at least one network card.

[0113] In one embodiment, the first communication interface 301 is further configured to:

[0114] The second information is output through the out-of-band management interface of the server.

[0115] It should be noted that the specific processing procedures of the first processor 302 and the first communication interface 301 can be understood by referring to the above method.

[0116] Of course, in practical applications, the various components in server 300 are coupled together through bus system 304. It can be understood that bus system 304 is used to implement communication between these components. In addition to a data bus, bus system 304 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 3 The general designated all buses as Bus System 304.

[0117] The first memory 303 in this embodiment is used to store various types of data to support the operation of the server 300. Examples of such data include any computer program used to operate on the server 300.

[0118] The methods disclosed in the above embodiments of this application can be applied to the first processor 302, or implemented by the first processor 302. The first processor 302 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 302. The first processor 302 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 302 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 303. The first processor 302 reads the information in the first memory 303 and completes the steps of the aforementioned method in combination with its hardware.

[0119] In an exemplary embodiment, server 300 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned methods.

[0120] It is understood that the first memory 303 in this application embodiment can be volatile memory or non-volatile memory, or both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); the magnetic surface memory can be disk storage or magnetic tape storage. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0121] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a first memory 303 storing a computer program, which can be executed by the first processor 302 of the server 300 to complete the steps described in the aforementioned server-side method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0122] It should be noted that "first," "second," etc., are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0123] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0124] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0125] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.< / netport>

Claims

1. A method for obtaining information of a network card, characterized in that, The application is applied to a server, and comprises: obtaining, through an out-of-band management interface of the server, a media access control (MAC) address of each network card based on first information of each network card in the at least one network card; the first information represents an installation position of the network card in the server; obtaining, in-band of the server, second information of each network card based on the obtained MAC address of each network card; the second information at least includes a logical name of the network card in an operating system deployed in the server.

2. The method of claim 1, wherein, The second information further includes at least one of: a capability of the network card; a configuration of the network card.

3. The method of claim 1, wherein, The first information includes a physical slot number and / or a physical network port number of the network card.

4. The method of claim 1, wherein, The out-of-band management interface includes a redfish extensible platform management application programming interface (API) or an intelligent platform management interface (IPMI).

5. The method according to any one of claims 1 to 4, characterized in that, The method further comprises: performing a binding operation on the at least one network card based on the obtained second information of each network card.

6. The method according to any one of claims 1 to 4, characterized in that, The method further comprises: outputting the second information through the out-of-band management interface of the server.

7. A network card information acquisition apparatus characterized by comprising: comprises: a first obtaining unit, configured to obtain, through an out-of-band management interface of the server, a MAC address of each network card based on first information of each network card in the at least one network card; the first information represents an installation position of the network card in the server; a first obtaining unit, configured to obtain, in-band of the server, second information of each network card based on the obtained MAC address of each network card; the second information at least includes a logical name of the network card in an operating system deployed in the server. comprises:

8. A server, characterized by a first processor and a first communication interface; wherein the first communication interface is configured to obtain, through an out-of-band management interface of the server, a MAC address of each network card based on first information of each network card in the at least one network card; the first information represents an installation position of the network card in the server; the first processor is configured to obtain, in-band of the server, second information of each network card based on the obtained MAC address of each network card; the second information at least includes a logical name of the network card in an operating system deployed in the server. comprises:

9. A server, characterized by a first processor and a first memory for storing a computer program capable of running on the processor, wherein the first processor is configured to execute the steps of the method according to any one of claims 1 to 6 when running the computer program. The computer program is executed by the processor to implement the steps of the method according to any one of claims 1 to 6.

10. A storage medium having stored thereon a computer program, characterized in that ​

Images