Network management method and network management device

Abstract

Provided are a network management method and a network management apparatus. 【Solution means】A network management method applied to a network management apparatus that determines the device configuration of a network device, the method including: obtaining the model and firmware version of the network device based on a plurality of network protocols; obtaining or generating a device profile based on the model and the firmware version; and generating or updating the device configuration of the network device based on the device profile. The step of generating the device profile based on the model and the firmware version further includes: determining at least one control item to be detected for the network device based on the device profile; and respectively detecting access interfaces of the at least one control item to be detected based on the plurality of network protocols and updating the device profile.

Description

Technical Field

[0001] The present invention relates to a network management method and a network management apparatus, and more particularly to a network management method and a network management apparatus that can automatically generate a device configuration of a network device using a plurality of different network protocols.

Background Art

[0002] Generally, network management software is used to manage and monitor the operating status of network devices. According to the network management software, a network administrator can collect hardware information of network devices, configure, operate, and manage network devices, monitor the performance and operating status of network devices, set warnings, and check the network topology, thereby grasping the current status of the managed network and timely discovering abnormal events in the network.

[0003] However, in order to manage various different devices, conventional network management software first needs to construct its dedicated device profile and understand the access methods of different devices, so the process is cumbersome and complex. Also, when the network device updates its version and there are changes in the interface or functions, it is necessary to reconstruct the new device profile again, which brings inconvenience. In addition, conventional network management software generally supports only the network configuration method of a single interface. For example, it supports only the interface provided by one of the network protocols such as a dedicated protocol customized by the manufacturer, the Simple Network Management Protocol (SNMP), the Network Configuration Protocol (NETCONF), or Representational State Transfer (RESTful). In this case, when applied to a specific area, a single network management software may not be able to support the configuration and operation of all control items required by the network device. For this reason, it is possible that the same network device is managed by multiple different network management softwares at the same time, or multiple network management softwares are required to control all network devices in a single field, thus increasing the complexity and inconvenience of network management. Therefore, it is necessary to improve the conventional network management technology.

Summary of the Invention

Problems to be Solved by the Invention

[0004] Therefore, the main object of the present invention is to provide a network management method and a network management device that can automatically detect network devices, determine the access interfaces of each network control item, and automatically generate the device configuration of the network devices.

Means for Solving the Problems

[0005] An embodiment of the present invention is a network management method applied to a network management device that determines the device configuration of a network device, including steps of obtaining the model and firmware version of the network device based on a plurality of network protocols, obtaining or generating a device profile based on the model and the firmware version, and generating or updating the device configuration of the network device based on the device profile. The step of generating the device profile based on the model and the firmware version further includes steps of determining at least one control item to be detected of the network device based on the device profile, and respectively detecting access interfaces of the at least one control item to be detected based on the plurality of network protocols and updating the device profile. A network management method is provided.

[0006] An embodiment of the present invention is a network management device that determines the device configuration of a network device, including a processing unit that executes program code, and a storage unit connected to the processing unit and storing the program code for instructing the processing unit to execute a network management method. The network management method includes steps of acquiring the model and firmware version of the network device based on a plurality of network protocols, acquiring or generating a device profile based on the model and the firmware version, and generating or updating the device configuration of the network device based on the device profile. The step of generating the device profile based on the model and the firmware version further includes steps of determining at least one control item to be detected of the network device based on the device profile, and detecting access interfaces of the at least one control item to be detected based on the plurality of network protocols and updating the device profile. A network management device is further provided.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Embodiments for Carrying Out the Invention

[0008] In the specification and the subsequent claims, specific terms are used to refer to specific elements. Those skilled in the art will understand that hardware manufacturers may call the same components by different nouns. In the specification and the subsequent claims, the criterion for distinguishing elements is not the difference in name, but the difference in the functions of the elements. "Comprising" as referred to throughout this specification and the subsequent claims is a non-limiting term and should be construed as "including but not limited to...".

[0009] FIG. 1 is a schematic diagram of a network system 10 according to an embodiment of the present invention. As shown in FIG. 1, the network system 10 is composed of a plurality of network management devices 100 to 102 and a plurality of network devices 120 to 122. The network management devices 100 to 102 are connected to the network devices 120 to 122 via a communication network 110 to perform communication. Here, the network devices 120 to 122 may be network connection devices such as switches, routers, bridges, gateways, etc., or terminal devices such as servers and workstations. The communication network 110 may be a local area network (LAN), a metropolitan area network (MAN), or a wide area network (WAN), but is not limited thereto. The network management devices 100 to 102 may be devices for managing and monitoring the network devices 120 to 122 or the communication network 110, and perform management functions (hereinafter collectively referred to as management) such as the configuration, operation, and monitoring of the network devices 120 to 122 via the communication network 110.

[0010] Generally, conventional network management devices support only a network management method with a single control interface. For example, they support only SNMP, only NETCONF, or only a customized proprietary protocol. In this case, when the network system 10 is applied to a special field or is a network environment that combines multiple application fields, a single network management device cannot support all the control items that need to be managed by the network devices 120 to 122. As shown in FIG. 1, some control items F1 and F2 of the network device 120 are managed via the network management device 100 that supports protocol A, while some other control items F3 must be managed separately via the network management device 101 that supports protocol B. Similarly, some control items F1 of the network device 121 are managed via the network management device 100 that supports protocol A, while the other control items F4 to F6 must be managed via the network management device 101 that supports protocol B. Some control items F4 of the network device 122 are managed via the network management device 101 that supports protocol B, while the other control items F7 to F8 must be managed via the network management device 102 that supports protocol C. In other words, the network management device 100 that supports only a single protocol A can manage only the network devices 120 and 121, the network management device 101 that supports only a single protocol B can manage only the network devices 120 to 122, and the network management device 102 that supports only a single protocol C can manage only the network device 122. In this case, multiple management devices are required to manage the network system 10, resulting in high management complexity.

[0011] In general, before managing a network device using a network management device, if the network device does not have a device profile corresponding to the network device, the device configuration required for the network device cannot be generated and managed. On the other hand, since there are a very large number of types of network devices and many differences in type, brand, model, etc., the network management device cannot manage different types, brands, and models of network devices with different device profiles. Every time a new network device is introduced into the network management device, technical staff need to create a device profile for the network device based on the specified format and parameters of the network management device. Taking Figure 1 as an example, the network management device 100 needs to have device profiles corresponding to the network devices 120 and 121 in order to manage the network devices 120 and 121. Also, when a network device updates its firmware version, the device profile in the network management device must be updated synchronously in order to continue using it. For example, when the firmware version of the network device 120 is updated, the device profiles corresponding to the network device 120 in the network management devices 100 and 101 also need to be updated synchronously. In other words, network devices with the same model but different firmware versions may provide different setting methods. Therefore, even for the same network device, different network management devices need to have different device profiles according to different firmware versions. On the other hand, when the network management device is updated, all related device profiles also need to be updated synchronously. For example, when the network management device 101 is updated (such as adding control items to support or adjusting the access method), the device profiles corresponding to the managed network devices 120 to 122 need to be adjusted again in order to continue using them. This process often requires developers to adjust the settings individually, and the work is cumbersome and complex.

[0012] In order to solve the above problems, the present invention provides a network management apparatus and method capable of reducing the complexity of network management and the burden on developers by automatically detecting access interfaces of various control items of a network apparatus and managing the network apparatus via a plurality of different network protocols. A detailed description will be given with reference to FIG. 2. FIG. 2 is a schematic diagram of a network system 20 according to an embodiment of the present invention. The network system 20 is composed of one network management apparatus 200 and a plurality of network apparatuses 120 to 122. The network management apparatus 200 is connected to the network apparatuses 120 to 122 via a communication network 110 to perform communication. Here, since the network management apparatus 200 can simultaneously support protocols A to C for network management, it is possible to monitor and manage all the network apparatuses 120 to 122 and the communication network 110 through only a single network management apparatus.

[0013] In an embodiment of the present invention, the network management device 200 obtains, by automatic detection, a network protocol applied when accessing various different control items of the network device. For example, the network management device 200 detects, according to protocols A to C, the access interfaces of all control items F1 to F3 of the network device 120, and may obtain information that control items F1 and F2 can be managed via protocol A, and control item F3 can be managed via protocol B. Similarly, the network management device 200 can manage control item F1 of the network device 121 via protocol A, manage control items F4 to F6 via protocol B, manage control item F4 of the network device 122 via protocol B, and obtain information that control items F7 and F8 can be managed via protocol C. As shown in FIG. 2, based on the information obtained by automatic detection, the network management device 200 manages control items F1 and F2 of the network device 120 and control item F1 of the network device 121 via protocol A, manages control item F3 of the network device 120, control items F4 to F6 of the network device 121, and control item F4 of the network device 122 via protocol B, and manages control items F7 and F8 of the network device 122 via protocol C. Thereby, it is possible to avoid the complicated process of creating or updating the device profile and the problem of managing different networks using a plurality of network management devices at the same time.

[0014] Note that in FIG. 2, the number of protocols supported by the network management device 200, the number of network devices managed by the network management device 200, and the number of control items included in the network devices 120 to 122 are for illustrative purposes only. The network management device 200 according to an embodiment of the present invention may be applied to the management of any number of protocols and any number of network devices. The network devices 120 to 122 may include any number of control items and are not limited thereto. In this embodiment, the protocols A to C may be, but are not limited to, the SNMP protocol based on different network management databases (Management Information Base: MIB), standard or private SNMP protocols, the NETCONF protocol based on different YANG (Yet Another Next Generation) models, different RESTful application programming interfaces (Application Programming Interface: API), dedicated protocols, and the like. The control items F1 to F8 of the network devices 120 to 122 may be the network functions of the network devices 120 to 122, and may also be, but are not limited to, the model acquisition of the network devices, interface information, network protocol (IP) configuration, virtual local area network (Virtual Local Area Network: VLAN) configuration, precise time protocol (Precise Time Protocol: PTP), and the like.

[0015] The network management method according to an embodiment of the present invention may be summarized as process 30 as shown in FIG. 3. Process 30 includes the following steps.

[0016] Step 300: Start the process.

[0017] Step 302: Obtain the model and firmware version of the network device based on a plurality of network protocols.

[0018] Step 304: Obtain or generate a device profile based on the device model and firmware version.

[0019] Step 306: Determine at least one control item to be detected for the network device based on the device profile.

[0020] Step 308: Detect the access interface of at least one control item to be detected based on multiple network protocols respectively, and update the device profile.

[0021] Step 310: Generate or update the device configuration of the network device based on the device profile.

[0022] Step 312: End the process.

[0023] According to process 30, the network management device 200 obtains the device model and firmware version of the network device based on multiple network protocols (step 302), queries the database of the network management device 200 based on the obtained device model and firmware version to obtain or generate a device profile (step 304), determines at least one control item to be detected for the network device based on the obtained or generated device profile (step 306), detects the access interface of at least one control item to be detected based on multiple network protocols supported by the network management device 200 respectively, and updates the device profile based on the detection result (step 308). Finally, the network management device 200 generates or updates the device configuration of the network device based on the device profile for management (step 310). Thus, the network management device 200 can automatically detect the network device and omit the complicated process of manually constructing the device profile.

[0024] In step 302, the network management device 200 acquires the model and firmware version of the network device according to a plurality of network protocols. First, the network management device 200 acquires connection information regarding the network device, and the connection information includes the IP of the network device and specific information necessary for connection according to a plurality of network protocols. For example, when using the SNMP protocol, the connection information includes community string passwords (public / private community strings), and when using the NETCONF protocol or the RESTful protocol, the connection information includes an account and a password. The network management device 200 needs to connect to the network device according to different network protocols and corresponding connection information until the model and firmware version of the network device are acquired.

[0025] Specifically, the network management device 200 first acquires the model and firmware version of the network device according to the first protocol among the multiple supported network protocols. When the network device is an unknown device (i.e., there is no relevant access record in the network management device 200), the first protocol is a pre-set network protocol, for example, the commonly used SNMP MIB-2, but not limited thereto. When the network device is a known device (i.e., a device managed by the network management device 200), the first protocol may be a pre-set network protocol, or may be acquired by the network management device 200 according to the device configuration of the network device. When the model and firmware version of the network device cannot be acquired by the first protocol, the network management device 200 sequentially acquires the model and firmware version of the network device according to the second protocol, the third protocol... among the multiple supported network protocols until the model and firmware version of the network device are acquired or all network protocols are tried.

[0026] Note that in this embodiment, there may be a situation where the network management device 200 fails to connect to the network device via all the supported network protocols and connection information. In this case, when the network device is an unknown device, the network management device 200 may record that the network device is an inaccessible device and terminate the process. When the network device is a known device, the network management device 200 may hold and deactivate all functions in the device configuration and terminate the process. Also, when the network device is a known device and the acquired model is different from the model recorded in the device configuration, the network management device 200 may deactivate all functions in the device configuration and terminate the process. Thereby, the network management device 200 can exclude abnormal states.

[0027] In step 304, the network management device 200 acquires or generates a device profile according to the device model and firmware version acquired in step 302. This will be described in detail with reference to FIG. 4. FIG. 4 is a process 40 of acquiring or generating a device profile according to the device model and firmware version in step 304. The process 40 includes the following steps.

[0028] Step 400: Start the process.

[0029] Step 402: Determine whether the device model has been acquired. If YES, execute step 404; if NO, execute step 416.

[0030] Step 404: Determine whether the firmware version has been acquired. If YES, execute step 406; if NO, execute step 410.

[0031] Step 406: Acquire the device profile of the network device based on the device model and firmware version, and execute step 408.

[0032] Step 408: Determine whether the device profile of the network device has been acquired. If YES, execute step 418; if NO, execute step 410.

[0033] Step 410: Acquire the device profile of a similar device based on the device model, and execute step 412.

[0034] Step 412: Determine whether the device profile of the similar device has been acquired. If YES, execute step 414; if NO, execute step 416.

[0035] Step 414: Generate the device profile of the network device based on the device profile of the similar device.

[0036] Step 416: Generate a general device profile as the device profile of the network device.

[0037] Step 418: End the process.

[0038] According to process 40, the network management device 200 acquires the device profile of the network device based on the model and firmware version of the network device. As shown in FIG. 4, the network management device 200 first determines whether the model of the network device has been acquired (step 402). If the model of the network device has not been acquired, the network management device 200 generates a general device profile as the device profile of the network device. The general device profile includes preset general control items that need to detect the access interface, and all detection results are preset to be empty (step 416). If the model of the network device has been acquired, the network management device 200 further determines whether the firmware version of the network device has been acquired (step 404). When both the model and firmware version of the network device have been acquired, the network management device 200 queries the database of the network management device 200 based on the model and firmware version to acquire a device profile in which both the model and firmware version match the network device (step 406). Next, the network management device 200 determines whether a device profile in which both the model and firmware version match the network device has been acquired (step 408). If a device profile in which both the model and firmware version match the network device has not been acquired, or if it is determined in step 404 that only the model of the network device has been acquired and the firmware version has not been acquired, the network management device 200 further queries the database based on only the model of the network device to acquire the device profile of a similar device (step 410). Next, the network management device 200 determines whether the device profile of the similar device has been acquired (step 412). If the device profile of the similar device has been acquired, the network management device 200 generates the device profile of the network device based on the device profile of the similar device (step 414).When the device profile of a similar device has not been acquired, the network management device 200 uses the general-purpose device profile as the device profile of the network device (step 416).

[0039] Briefly speaking, when no device profile in which both the model and the firmware version match the network device is obtained by search in the database of the network management device 200, the network management device 200 searches for similar devices based only on the model of the network device. Here, the similar device has the same or a similar model as the network device. Generally, a similar device having the same model as the network device and a different firmware version has control items and corresponding access interfaces that are partially similar to those of the network device. Similarly, a similar device having a model similar to that of the network device may be manufactured by the same manufacturer as the network device and generally has partially similar control items and corresponding access interfaces. Therefore, in an embodiment of the present invention, the network management device 200 can reduce the number of control items to be detected by generating the device profile of the network device based on the device profile of the similar device. On the other hand, when the model of the network device or the device profile of the similar device cannot be obtained, the network management device 200 uses the general-purpose device profile as the device profile of the network device and detects the access interfaces of all control items.

[0040] After the device profile is obtained according to process 40 in step 304, in step 306, the network management device 200 further determines at least one control item to be detected for the network device based on the device profile. In this embodiment, the device profile is used to record the network protocols supported by the access interfaces of the respective control items of the device that match the model and firmware version. The network management device 200 determines, based on the record of the device profile, at least one control item to be detected as a control item for which the supported network protocol in the device profile is not recorded. Note that when the device profile is obtained in step 406 and is a device profile that matches the device profile of the type and firmware version of the network device, it means that the network management device has identified the network device of the model and firmware version and has stored the device profile. In this case, the access interfaces used by the respective control items in the device profile are known. In other words, there are no control items to be detected in the device profile. Therefore, the network management device 200 may omit steps 306 to 308 and directly execute step 310 to generate the device configuration of the device.

[0041] In step 308, the network management device 200 respectively detects the access interfaces of at least one control item to be detected according to a plurality of network protocols, and updates the device profile based on the detection results. Note that when the device profile is generated based on the general-purpose device profile in step 416, all control items are preset so as not to have supported network protocols. In this case, the network management device 200 determines that at least one control item to be detected is all of those control items. In other words, the network management device 200 needs to detect all control items according to all supported network protocols respectively.

[0042] Finally, in step 310, the network management device 200 may generate or update the device configuration of the network device based on the device profile. Thereby, the network management device 200 can manage the network device.

[0043] In conventional network management software, the device profile is generally developed and designed from the perspective of the network device. Therefore, when a new network device is introduced into the network management software, or when the network device or the network management software is updated, technical staff need to recreate or modify the device profile, lacking flexibility in network management. In contrast, in the embodiments of the present invention, the device profile is developed and designed from the perspective of various control items (functions) of the network device. Also, by querying the database, it is possible to avoid redetecting known control items by using known information. Furthermore, by constructing the device profile by an automated detection method according to various network protocols, the network management device can be adapted to manage any network device. Thereby, the present invention can improve the drawbacks of the conventional method that requires a device profile of a network device pre-constructed for management.

[0044] A further description will be given with reference to FIG. 5. FIG. 5 is a schematic diagram of an apparatus 50 according to an embodiment of the present invention. The apparatus 50 may be used to implement a network management apparatus 200. As shown in FIG. 5, the apparatus 50 may include a processing unit 500 and a storage unit 510. The processing unit 500 may be a general-purpose processor, a microprocessor, an application specific integrated circuit (ASIC), or the like, or a combination thereof. The storage unit 510 is connected to the processing unit 500 and may be any data storage device for storing program code 512 and for the processing unit 500 to read and execute the program code 512. For example, the storage unit 510 may be a read-only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, an optical data storage device, a non-volatile storage unit, etc., but is not limited thereto.

[0045] The apparatus 50 is used to represent the elements necessary to implement the embodiments of the present invention, and those skilled in the art may make various modifications and adjustments, but are not limited thereto. For example, when the network management apparatus 200 is implemented by the apparatus 50, the processes 30 and 40 of the network management method may be compiled into the program code 512, stored in the storage unit 510, and the network management method may be executed by the processing unit 500. Further, the storage unit 510 is also used to store a database of device profiles corresponding to various models and firmware, and to store data necessary for the device configuration of each network device and the execution of the network management method, but is not limited thereto.

[0046] From the above, according to the network management method and device according to the present invention, it can be managed by various different network protocols, and by detecting the access interface of the control items of the network device, the network protocol applied to each control item can be automatically determined. As a result, the restrictive conditions for introducing new devices into network management can be reduced, and the burden caused by device updates in the conventional method can be reduced.

[0047] The above has described the preferred embodiments of the present invention. However, all those that are equally changed and modified based on the scope of the claims of the present invention belong to the scope of the present invention.

Explanation of Signs

[0048] 10: Network system 100~102: Network management device 110: Communication network 120~122: Network device A~C: Protocol F1~F8: Control item 200: Network management device 30: Process 300~312: Step 40: Process 400~418: Step 50: Device 500: Processing unit 510: Storage unit 512: Program code

Claims

1. A network management method applied to a network management device that determines a device configuration of a network device, comprising: obtaining a model and a firmware version of the network device based on a plurality of network protocols; obtaining or generating a device profile based on the model and the firmware version; generating or updating the device configuration of the network device based on the device profile; generating the device profile based on the model and the firmware version, determining at least one control item to be sensed of the network device based on the device profile; The network management method further includes: detecting an access interface of the at least one control item to be detected based on the plurality of network protocols respectively, and updating the device profile.

2. The step of acquiring a model and a firmware version of the network device includes:

2. The method of claim 1, further comprising the step of obtaining the model and firmware version of the network device based on a first protocol of the plurality of network protocols.

3. The network management method of claim 2 , wherein if the network device is an unknown device, the first protocol is a pre-configured network protocol of the plurality of network protocols.

4. The network management method according to claim 2 , wherein if the network device is a known device, the first protocol is determined based on the device configuration of the network device.

5. 3. The network management method of claim 2, further comprising the step of: if the model and the firmware version of the network device cannot be obtained based on a first protocol of the plurality of network protocols, obtaining the model and the firmware version of the network device based on a second protocol of the plurality of network protocols.

6. 2. The network management method of claim 1, further comprising: when the model of the network device cannot be obtained, generating a generic device profile as the device profile when obtaining or generating the device profile based on the model and the firmware version, and determining, based on the generic device profile, that the at least one control item to be detected of the network device are all pre-configured control items.

7. The step of obtaining or generating the device profile based on the model and the firmware version includes:

2. The network management method of claim 1, further comprising: querying a database of the network management device based on the model and the firmware version, and retrieving the device profile whose model and firmware version both match the network device.

8. 8. The network management method of claim 7, further comprising the steps of: if a device profile whose model and firmware version both match those of the network device is not obtained, querying the database based on the model to obtain a device profile of a similar device, and generating the device profile based on the device profile of the similar device, wherein the similar device has the same or similar model as the network device.

9. 9. The network management method according to claim 8, further comprising the step of: generating a generic device profile as the device profile if the device profile of the similar device has not been obtained; and determining, based on the generic device profile, that the at least one control item to be detected of the network device are all pre-configured control items.

10. 2. The network management method according to claim 1, wherein said device profile records a network protocol that can be supported by an access interface of each control item of said network device that matches said model and said firmware version.

11. 11. The network management method according to claim 10, wherein in the step of determining the at least one control item to be detected of the network device based on the device profile, the at least one control item to be detected is a control item for which a supportable network protocol is not recorded in the device profile.

12. A network management device for determining a device configuration of a network device, comprising: a processing unit for executing program code; a storage unit connected to the processing unit and having the program code stored therein for instructing the processing unit to execute a network management method; The network management method includes: obtaining a model and a firmware version of the network device based on a plurality of network protocols; obtaining or generating a device profile based on the model and the firmware version; generating or updating the device configuration of the network device based on the device profile; generating the device profile based on the model and the firmware version, determining at least one control item to be sensed of the network device based on the device profile; detecting an access interface of the at least one control item to be detected based on the plurality of network protocols, respectively, and updating the device profile.

13. The step of acquiring a model and a firmware version of the network device of the network management method includes:

13. The network management device of claim 12, further comprising obtaining the model and firmware version of the network device based on a first protocol of the plurality of network protocols.

14. 14. The network management device of claim 13, wherein if the network device is an unknown device, the first protocol is a pre-configured network protocol of the plurality of network protocols.

15. The network management device of claim 13 , wherein if the network device is a known device, the first protocol is determined based on the device configuration of the network device.

16. 14. The network management device of claim 13, wherein the network management method further includes a step of acquiring the model and the firmware version of the network device based on a second protocol of the plurality of network protocols when the model and the firmware version of the network device cannot be acquired based on a first protocol of the plurality of network protocols.

17. The network management method of claim 12, further comprising the step of: when the model of the network device cannot be obtained, generating a generic device profile as the device profile when obtaining or generating the device profile based on the model and the firmware version, and determining, based on the generic device profile, that the at least one control item to be detected of the network device is all pre-configured control items.

18. The step of obtaining or generating the device profile based on the model and the firmware version of the network management method includes: The network management device of claim 12, further comprising: querying a database of the network management device based on the model and the firmware version to retrieve the device profile whose model and firmware version both match the network device.

19. 20. The network management method of claim 18, further comprising the steps of: if a device profile in which both the model and firmware version of the network device match those of the network device is not obtained, querying the database based on the model to obtain a device profile of a similar device, and generating the device profile based on the device profile of the similar device, the similar device having the same or similar model as the network device.

20. 20. The network management device of claim 19, further comprising: if the device profile of the similar device has not been obtained, generating a generic device profile as the device profile, and determining, based on the generic device profile, that the at least one control item to be detected of the network device are all pre-configured control items.

21. 13. The network management device according to claim 12, wherein the device profile records supportable network protocols of an access interface of each control item of the network device that matches the model and firmware version.

22. 22. The network management device of claim 21, wherein in the step of determining the at least one control item to be detected of the network device based on the device profile of the network management method, the at least one control item to be detected is a control item for which a supportable network protocol is not recorded in the device profile.

Images