Network management method and network management apparatus

Abstract

To provide a network management method and a network management device.SOLUTION: A network management method, applied to a network management device for determining a device configuration of a network device, the method comprising: obtaining a model and a firmware version of the network device according to multiple network protocols; obtaining or generating a device profile according to the model and the firmware version; and generating or updating the device configuration of the network device according to the device profile; The step of generating the device profile according to the model and the firmware version further includes: determining at least one control item to be detected of the network device according to the device profile; and detecting the access interface of the at least one control item to be detected respectively according to the plurality of network protocols to update the device profile.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a network management method and a network management device, and more particularly to a network management method and a network management device that can use a plurality of different network protocols and automatically generate device configurations for network devices. [Background technology]

[0002] Generally, network management software is used to manage and monitor the operation status of network devices, allowing network administrators to collect hardware information of network devices, configure, operate, and manage network devices, monitor the performance and operation status of network devices, set alerts, and check network topology, thereby understanding the current status of the managed network and timely detecting abnormal events in the network.

[0003] However, in order to manage various different devices, conventional network management software must first build dedicated device profiles and understand the access methods of the different devices, which is a cumbersome and complicated process. Furthermore, when a network device undergoes a version update, if the interface or functionality changes, a new device profile must be rebuilt, which is inconvenient. Furthermore, conventional network management software typically supports only a single interface network configuration method, such as a manufacturer-customized proprietary protocol, Simple Network Management Protocol (SNMP), Network Configuration Protocol (NETCONF), or Representational State Transfer (RESTful). In this case, when applied to a specific domain, a single network management software may not be able to support the configuration and operation of all control items required for the network device. This may result in a situation where the same network device is managed by multiple different network management software programs at the same time, or multiple network management software programs are required to control all network devices in a single field, increasing the complexity and inconvenience of network management. Therefore, there is a need to improve conventional network management technologies. Summary of the Invention [Problem 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 interface of each network control item, and automatically generate the device configuration of the network devices. [Means for solving the problem]

[0005] An embodiment of the present invention provides a network management method applied to a network management device that determines the device configuration of a network device, the network management method including the steps of: acquiring a model and a 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, wherein the step of generating the device profile based on the model and the firmware version further includes the steps of determining at least one control item to be detected of the network device based on the device profile; and detecting the access interfaces of the at least one control item to be detected based on the plurality of network protocols, and updating the device profile.

[0006] An embodiment of the present invention further provides a network management device for determining a device configuration of a network device, the network management device including: a processing unit that executes program code; and a memory 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 including the steps of: acquiring a 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 including the steps of: determining at least one control item to be detected of the network device based on the device profile; and detecting the access interface of each of the at least one control item to be detected based on the plurality of network protocols, and updating the device profile. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a schematic diagram of a network system according to an embodiment of the present invention. [Figure 2] 1 is a schematic diagram of a network system according to an embodiment of the present invention. [Figure 3] FIG. 2 is a schematic diagram of a network management process according to an embodiment of the present invention. [Figure 4] FIG. 2 is a schematic diagram of a network management process according to an embodiment of the present invention. [Figure 5] 1 is a schematic diagram of an apparatus according to an embodiment of the present invention; DETAILED DESCRIPTION OF THE INVENTION

[0008] Throughout this specification and in the claims that follow, certain terms are used to refer to particular elements. Those skilled in the art will understand that hardware manufacturers may refer to the same component by different nouns. Throughout this specification and in the claims that follow, elements are distinguished by their function, not by their name. The term "comprising" as used throughout this specification and in the claims that follow is an open-ended term and should be interpreted 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 includes multiple network management devices 100-102 and multiple network devices 120-122. The network management devices 100-102 are connected to and communicate with the network devices 120-122 via a communication network 110. The network devices 120-122 may be network connection devices such as switches, routers, bridges, and gateways, or may be terminal devices such as servers and workstations. The communication network 110 may be, but is not limited to, a local area network (LAN), a metropolitan area network (MAN), or a wide area network (WAN). The network management devices 100-102 may manage and monitor the network devices 120-122 or the communication network 110, and perform management functions (hereinafter collectively referred to as "management") such as configuring, operating, and monitoring the network devices 120-122 via the communication network 110.

[0010] Generally, conventional network management devices only support a network management method with a single control interface, such as only SNMP, only NETCONF, or only a customized proprietary protocol. In this case, if the network system 10 is applied to a specialized field or is a network environment that combines multiple application fields, a single network management device cannot support all the control items that the network devices 120-122 need to manage. 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 the other control item 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-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-F8 must be managed via the network management device 102 that supports protocol C. In other words, network management device 100 supporting a single protocol A can only manage network devices 120 and 121, network management device 101 supporting a single protocol B can only manage network devices 120-122, and network management device 102 supporting a single protocol C can only manage network device 122. In this case, multiple management devices are required to manage network system 10, which increases management complexity.

[0011] In addition, before using a network management device to manage a network device, a device profile corresponding to the network device must be prepared before the network management device can be used to generate and manage the required device configuration for the network device. Meanwhile, because there are a great many types of network devices, with many differences in type, brand, and model, the network management device must have a different device profile for each type, brand, and model in order to manage different types, brands, and models of network devices using the different device profiles. Each time a new network device is introduced into the network management device, technical staff must create a device profile for the network device based on the format and parameters specified by the network management device. Taking FIG. 1 as an example, in order to manage network devices 120 and 121, the network management device 100 must have device profiles corresponding to network devices 120 and 121, respectively. Furthermore, when the firmware version of the network device is updated, the device profile in the network management device must also be updated synchronously to continue use. For example, when the firmware version of network device 120 is updated, the device profile corresponding to network device 120 in the network management devices 100 and 101 must also be updated synchronously. In other words, because network devices of the same model but with different firmware versions may provide different configuration methods, different network management devices must have different device profiles for the same network device depending on the different firmware versions. Meanwhile, when a network management device performs an update, all related device profiles must also be updated synchronously. For example, when the network management device 101 performs an update (e.g., adding supported control items or adjusting access methods), the device profiles corresponding to the managed network devices 120-122 must be re-adjusted to continue use. This process often requires developers to individually adjust the settings, making the process cumbersome and complicated.

[0012] To solve the above problems, the present invention provides a network management device and method that automatically detects the access interfaces of various control items of network devices and manages the network devices via multiple different network protocols, thereby reducing the complexity of network management and the burden on developers. This will be described in detail 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 device 200 and multiple network devices 120-122. The network management device 200 connects to and communicates with the network devices 120-122 via a communication network 110. Here, the network management device 200 can simultaneously support network management protocols A-C, making it possible to monitor and manage all of the network devices 120-122 and the communication network 110 via a single network management device.

[0013] In an embodiment of the present invention, the network management device 200 acquires, through automatic detection, the network protocols to be applied when accessing various different control items of the network devices. For example, the network management device 200 may detect the access interfaces of all control items F1 to F3 of the network device 120 according to protocols A to C, respectively, and acquire information that the network management device 200 can manage control items F1 and F2 via protocol A and control item F3 via protocol B. Similarly, the network management device 200 may acquire information that the network device 121's control item F1 can be managed via protocol A, the network device 122's control items F4 to F6 can be managed via protocol B, the network device 122's control item F4 can be managed via protocol B, and the network device 122's control items F7 to F8 can be managed via protocol C. 2, based on the information acquired by automatic detection, network management device 200 can manage control items F1 and F2 of network device 120 and control item F1 of network device 121 via protocol A, manage control item F3 of network device 120, control items F4 to F6 of network device 121, and control item F4 of network device 122 via protocol B, and manage control items F7 and F8 of network device 122 via protocol C. This avoids the cumbersome process of creating or updating device profiles and the problem of simultaneously using multiple network management devices to manage different networks.

[0014] 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-122 are for illustrative purposes only. The network management device 200 according to an embodiment of the present invention may be applied to manage any number of protocols and any number of network devices, and the network devices 120-122 may include any number of control items, but is not limited to these. In this embodiment, protocols A to C may be, but are not limited to, SNMP protocols based on different network management information bases (MIBs), standard or private SNMP protocols, NETCONF protocols based on different YANG (Yet Another Next Generation) models, different RESTful application programming interfaces (APIs), dedicated protocols, etc. The control items F1 to F8 of the network devices 120 to 122 may be network functions of the network devices 120 to 122, such as, but not limited to, obtaining the model of the network device, interface information, network protocol (IP) configuration, virtual local area network (VLAN) configuration, precise time protocol (PTP), etc.

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

[0016] Step 300: The process begins.

[0017] Step 302: Obtain the model and firmware version of the network device according to multiple network protocols.

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

[0019] Step 306: Determine at least one control item to be detected of 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 a device configuration for the network device based on the device profile.

[0022] Step 312: End the process.

[0023] According to process 30, the network management device 200 acquires the model and firmware version of a network device based on multiple network protocols (step 302), queries its database based on the acquired model and firmware version to acquire or generate a device profile (step 304), determines at least one control item to be detected for the network device based on the acquired or generated device profile (step 306), detects the access interface of each of the at least one control item to be detected based on the multiple network protocols supported by the network management device 200, 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 and manages it (step 310). This allows the network management device 200 to automatically discover network devices and eliminates the cumbersome process of manually building a device profile.

[0024] In step 302, the network management device 200 acquires the model and firmware version of a network device according to multiple network protocols. The network management device 200 first acquires connection information about the network device, including the IP address of the network device and specific information required to connect according to multiple network protocols. For example, when using the SNMP protocol, the connection information includes community strings and passwords (public / private community strings), and when using the NETCONF protocol or the RESTful protocol, the connection information includes accounts and passwords. The network management device 200 needs to connect to each network device according to different network protocols and corresponding connection information until it acquires the model and firmware version of the network device.

[0025] Specifically, the network management device 200 first acquires the model and firmware version of the network device according to a first protocol among the multiple supported network protocols. If the network device is an unknown device (i.e., the network management device 200 has no associated access record), the first protocol is a pre-configured network protocol, such as, but not limited to, the commonly used SNMP MIB-2. If 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-configured network protocol or may be acquired by the network management device 200 according to the device configuration of the network device. If the model and firmware version of the network device cannot be acquired using the first protocol, the network management device 200 may sequentially acquire the model and firmware version of the network device according to a second protocol, a third protocol, and so on among the multiple supported network protocols until the model and firmware version of the network device are acquired or until all network protocols have been tried.

[0026] In this embodiment, a situation may occur in which the network management device 200 does not successfully connect to a network device via all supported network protocols and connection information. In this case, if the network device is an unknown device, the network management device 200 may record the network device as an inaccessible device and terminate the process. If the network device is a known device, the network management device 200 may suspend and deactivate all functions in the device configuration and terminate the process. Also, if 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. This allows the network management device 200 to rule out abnormal conditions.

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

[0028] Step 400: The process begins.

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

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

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

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

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

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

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

[0036] Step 416: Generate the generic 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 obtains a device profile of a 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 obtained (step 402). If the model of the network device has not been obtained, the network management device 200 generates a generic device profile as the device profile of the network device. The generic device profile includes pre-defined general control items that require access interface detection, and all detection results are preset to empty (step 416). If the model of the network device has been obtained, the network management device 200 further determines whether the firmware version of the network device has been obtained (step 404). If both the model and firmware version of the network device have been obtained, the network management device 200 queries its database based on the model and firmware version to obtain a device profile whose model and firmware version both match those of the network device (step 406). Next, the network management device 200 determines whether a device profile whose model and firmware version both match those of the network device has been obtained (step 408). If a device profile that matches both the model and firmware version of the network device has not been obtained, or if it is determined in step 404 that only the model of the network device has been obtained but not the firmware version, the network management device 200 further queries the database based only on the model of the network device to obtain a device profile of a similar device (step 410). Next, the network management device 200 determines whether a device profile of a similar device has been obtained (step 412). If a device profile of a similar device has been obtained, the network management device 200 generates a device profile of the network device based on the device profile of the similar device (step 414).If the device profile of a similar device has not been obtained, the network management device 200 sets the generic device profile as the device profile of the network device (step 416).

[0039] Simply put, if the network management device 200 does not obtain a device profile in its database that matches the network device in both model and firmware version, the network management device 200 searches for similar devices based only on the model of the network device. Here, similar devices have the same or similar model as the network device. Generally, similar devices with the same model and different firmware version as the network device have control items and corresponding access interfaces that are partially similar to those of the network device. Similarly, similar devices with a similar model to the network device may be manufactured by the same manufacturer as the network device and generally have control items and corresponding access interfaces that are partially similar to those of the network device. 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 a device profile for the network device based on the device profile of the similar device. On the other hand, if the model of the network device or the device profile of a similar device cannot be obtained, the network management device 200 uses a generic 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, the network management device 200 further determines at least one control item of the network device to be detected based on the device profile in step 306. In this embodiment, the device profile is used to record the supportable network protocols of the access interfaces of each control item of the device that matches the model and firmware version. Based on the record in the device profile, the network management device 200 determines, as at least one control item to be detected, a control item for which a supportable network protocol is not recorded in the device profile. Note that if the device profile obtained in step 406 matches the device profile of the network device's type and firmware version, it means that the network management device has previously identified the network device of that model and firmware version and stored the device profile. In this case, the access interfaces used by each control item in the device profile are known; in other words, the device profile does not contain any control items to be detected. Therefore, the network management device 200 may omit steps 306 to 308 and directly perform step 310 to generate a device configuration for the device.

[0041] In step 308, the network management device 200 detects the access interface of at least one control item to be detected according to multiple network protocols, and updates the device profile based on the detection result. Note that when the device profile is generated based on the generic device profile in step 416, all control items are pre-configured to not have supportable network protocols. In this case, the network management device 200 determines that the at least one control item to be detected is all of the control items. In other words, the network management device 200 needs to detect all control items according to all supportable network protocols.

[0042] Finally, in step 310, the network management device 200 may generate or update a device configuration for the network device based on the device profile, thereby enabling the network management device 200 to manage the network device.

[0043] In conventional network management software, device profiles are 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 must recreate or modify the device profile, resulting in a lack of flexibility in network management. In contrast, in an embodiment of the present invention, device profiles are developed and designed from the perspective of various control items (functions) of the network device. Furthermore, by querying a database, known information can be utilized to avoid rediscovering known control items. Furthermore, by constructing device profiles using an automated detection method according to various network protocols, the network management device can be adapted to manage any network device. This improves the drawbacks of conventional methods that require pre-built device profiles for network devices to be managed.

[0044] Further description will be made 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 the network management device 200. As shown in FIG. 5 , the apparatus 50 may include a processing unit 500 and a memory unit 510. The processing unit 500 may be a general-purpose processor, a microprocessor, an application specific integrated circuit (ASIC), or a combination thereof. The memory unit 510 may be any data storage device connected to the processing unit 500, for storing program code 512, and for reading and executing the program code 512 by the processing unit 500. For example, the memory unit 510 may be, but is not limited to, 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.

[0045] The device 50 is used to represent elements necessary to realize an embodiment of the present invention, and those skilled in the art may make various modifications and adjustments, but this is not intended to be limiting. For example, when the network management device 200 is realized by the device 50, the processes 30 and 40 of the network management method may be compiled into program code 512 and stored in the storage unit 510, and the network management method may be executed by the processing unit 500. The storage unit 510 may also be 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 for executing the network management method, but this is not intended to be limiting.

[0046] As described above, the network management method and device according to the present invention can manage a variety of different network protocols, and can automatically determine the network protocol applied to each control item by detecting the access interface of the control item of the network device. This reduces the constraints on introducing new devices into network management and reduces the burden of updating devices that is required in conventional methods.

[0047] The above describes the preferred embodiment of the present invention, but all equivalent modifications and variations based on the claims of the present invention fall within the scope of the present invention. [Explanation of symbols]

[0048] 10: Network Systems 100-102: Network management device 110: Communication Network 120-122: Network equipment A~C: Protocol F1~F8: Control items 200: Network management device 30: Process 300~312: Step 40: Process 400~418: Step 50: Equipment 500: Processing section 510: Storage section 512: Program code

Claims

1. 1. A network management method applied to a network management device that determines a device configuration of a network device, comprising: acquiring a 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; 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 detected for the network device based on the device profile; the network management method further comprising: 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 the model and firmware version of the network device includes:

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

3. 3. The network management method according to claim 2, wherein if the network device is an unknown device, the first protocol is a preset network protocol from among the plurality of network protocols.

4. 3. 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 firmware version of the network device cannot be obtained based on a first protocol of the plurality of network protocols, obtaining the model and 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: if the model of the network device cannot be obtained, when obtaining or generating the device profile based on the model and the firmware version, 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 is 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 according to claim 1, further comprising the step of 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 those of 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 device profiles of similar devices, and generating the device profile based on the device profiles of the similar devices, wherein the similar devices have the same or similar model as the network device.

9. 9. The network management method according to claim 8, further comprising the step of: 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 is all pre-configured control items.

10. 2. The network management method according to claim 1, wherein the device profile records supportable network protocols for an access interface of each control item of the device that matches the model and 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, a processing unit for executing program code; a storage unit connected to the processing unit and having stored therein the program code for instructing the processing unit to execute the network management method; The network management method includes: acquiring a 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; 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 detected for 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 the model and firmware version of the network device in the network management method includes: The network management device according to claim 12 , further comprising: acquiring the model and firmware version of the network device based on a first protocol of the plurality of network protocols.

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 from 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, if the model and firmware version of the network device cannot be obtained based on a first protocol of the plurality of network protocols, obtaining the model and firmware version of the network device based on a second protocol of the plurality of network protocols.

17. 13. The network management device of claim 12, wherein the network management method further includes a step of generating a generic device profile as the device profile when acquiring or generating the device profile based on the model and the firmware version if the model of the network device cannot be acquired, 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 according to claim 12, 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 those of the network device.

19. 20. The network management method of claim 18, 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 device profiles of similar devices, and generating the device profile based on the device profiles of the similar devices, wherein the similar devices have the same or similar model as the network device.

20. 20. The network management device of claim 19, wherein the network management method further includes 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 is all pre-configured control items.

21. 13. The network management device according to claim 12, wherein the device profile records supportable network protocols for an access interface of each control item of the 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