Network equipment management method

Abstract

The invention provides a network equipment management method, which comprises the following steps of: connecting a server with gateway equipment in a target local area network, and communicating with the gateway equipment by utilizing terminal equipment; the method comprises the following steps: sending a grade division instruction message to gateway equipment through terminal equipment, and performing grade division on the gateway equipment and switching equipment directly and indirectly connected with the gateway equipment to obtain a network topological graph of which root equipment is the gateway equipment; selecting one switching device from the network topological graph as a target device to carry out proxy configuration issuing and proxy reporting, and after the root device completes proxy configuration issuing and proxy reporting, managing the to-be-managed network device through the server; therefore, each network device is prevented from sending the generated message to the server, the burden of the server is reduced, a technician can conveniently manage the to-be-managed network device through the server, and the management efficiency of the network device is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of network equipment management, and in particular to a network equipment management method. Background Art

[0002] Traditional network management platforms use network management protocols (snmp, tr069, mqtt, netconf, etc.) to remotely control a single device. If a remote or cloud-based network management platform needs to control a device in a certain network, the network between the network management server and the managed device must be unobstructed, otherwise control will not be possible, resulting in the device being out of management.

[0003] When technicians configure a network of a certain scale through the network management platform, it is inevitable that the network between the device and the server will be interrupted due to configuration errors. For example, modifying the default VLAN of the port, configuring the routing table or routing protocol, configuring 802.1X and other functions will cause the network connection between the device and the server to be interrupted. Although the physical connection has not been changed, users can no longer manage and configure the device through the network management platform. At this time, technicians need to go to the site to access the unmanaged device through the serial port line to perform local configuration.

[0004] In addition, in the early stage of user network construction, after the physical connection cables between network devices are connected, the devices are all factory configured by default. There will definitely be IP address conflicts or no IP addresses, no routing tables, no DHCP-Server, etc. This will cause the devices in the network to be unable to communicate with each other through IP. Similarly, a single device cannot establish a connection with the server. Technical personnel are required to use serial cables or log in to the local web to make relevant configurations on each device in order to establish network connections between them.

[0005] Traditional network management requires technicians to go to the equipment site to solve network connection problems when network configuration errors occur or in the early stages of network construction. This is so that the equipment can communicate with each other and access the Internet. Remote operation is not possible and the equipment can only be operated one by one, which is inefficient.

[0006] Traditional network management methods require all devices in the LAN to periodically send heartbeat messages to the server to maintain connection with the server and report network status. If there are many devices in the LAN, the export bandwidth will be occupied and the burden on the server will be increased. Similarly, if the network topology in the LAN changes, the traditional network management method requires all devices to interact with the server again, which will also generate more messages to communicate with the server, greatly increasing the burden on the server and requiring higher bandwidth for the server. Summary of the invention

[0007] The present invention provides a network device management method, the purpose of which is to improve the management efficiency of network devices without increasing the burden on servers.

[0008] In order to achieve the above object, the present invention provides a network device management method, comprising: Step 1: Connect the server to the gateway device in the target local area network, establish a data transmission channel, and use the terminal device to communicate with the gateway device; Step 2: Send a level classification instruction message to the gateway device through the terminal device, classify the gateway device and the switching devices directly and indirectly connected to the gateway device, and obtain a network topology map, in which the root device of the network topology map is the gateway device; Step 3, select a switching device as the target device in the network topology diagram, send the NTTDP agent downlink message to the target switching device through the terminal device and the root device, the target device parses the received NTTDP agent downlink message, maps the message content to the network management protocol processing flow for configuration downlink, and sends the NTTDP agent response message to the server through the root device self-data transmission channel to complete the proxy configuration downlink; Step 4: The terminal device and the root device send the proxy reporting instruction to the switching devices at each level in the network topology diagram step by step. After receiving the proxy reporting instruction, the switching devices at each level encapsulate their own link status and device information into a response message and report it to the root device. The root device summarizes the link status and device information of the switching devices at each level and reports them to the server through the data transmission channel to complete the proxy reporting; Step 5: After the root device completes the proxy configuration delivery and proxy reporting, the server manages the managed network device through the data transmission channel. The managed network device is a gateway device or a switching device in the network topology diagram.

[0009] Specifically, the terminal device sends a classification instruction message to the gateway device, and the gateway device and the switching devices directly and indirectly connected to the gateway device are classified to obtain a network topology diagram, in which the root device of the network topology diagram is the gateway device, including: Sending a level classification instruction message to the gateway device through the terminal device; The gateway device sends a topology discovery message carrying its own level information to the switching devices directly and indirectly connected to the gateway device according to the level classification instruction message; For each switching device directly or indirectly connected to the gateway device, the switching device generates its own level based on the number of connection hops with the gateway device; The network topology diagram is formed according to the level of each switching device, and the gateway device is used as the root device in the network topology diagram.

[0010] Further, the network topology diagram includes a plurality of switching devices directly connected to the root device.

[0011] Furthermore, the network topology diagram includes at least one switching device directly connected to the root device and at least one next-level switching device connected to the root device through the switching device.

[0012] More specifically, step 3 includes: Select a switching device as the target device in the network topology diagram, and send a proxy command to the root device through the terminal device; The root device encapsulates the proxy delivery instruction into an NTTDP proxy delivery message and delivers it to the target switching device; After the target device parses the received NTTDP agent sent message, it maps the message content to the network management protocol processing flow for configuration and sends it, and forwards the NTTDP agent response message to the root device; After the root device parses the NTTDP proxy response message, it encapsulates the response message into a network management protocol message and sends it to the server through the data transmission channel to complete the proxy configuration delivery.

[0013] Furthermore, the instructions sent by the agent are filled with the physical information of the target switching device.

[0014] Specifically, the root device encapsulates the proxy delivery instruction into an NTTDP proxy delivery message and delivers it to the target switching device, including: The root device encapsulates the proxy delivery instruction into an NTTDP proxy delivery message according to the hierarchical relationship table and the MAC-PORT information table, and sends the NTTDP proxy delivery message to the switching device directly connected to the root device; The switching device directly connected to the root device parses the message sent by the NTTDP agent. When the physical information filled in the message sent by the NTTDP agent is consistent with the physical information of the switching device directly connected to the root device, the switching device is the target switching device and stops sending the message sent by the NTTDP agent. When the physical information filled in the NTTDP agent sent message is not consistent with the physical information of the switching device directly connected to the root device, the NTTDP agent sent message is sent to the next-level switching device until it is sent to the target switching device.

[0015] More specifically, step 4 includes: The terminal device sends the proxy reporting instruction to the root device, and the root device sends the proxy reporting instruction step by step to the lowest switching device in the network topology diagram; After receiving the proxy reporting instruction, the switching devices at all levels in the network topology diagram encapsulate their own link status and device information into a response message, and report the response message to the root device; The root device summarizes the link status and device information of the switching devices at all levels in the network topology diagram, and reports the summary results to the server through the data transmission channel to complete the proxy reporting.

[0016] Furthermore, device information includes connection ports and its own physical information.

[0017] The above scheme of the present invention has the following beneficial effects: The present invention connects a server with a gateway device in a target local area network, and uses a terminal device to communicate with the gateway device; sends a level division instruction message to the gateway device through the terminal device, and performs level division on the gateway device and the switching device directly and indirectly connected to the gateway device, so as to obtain a network topology diagram in which the root device is the gateway device; selects a switching device as a target device in the network topology diagram, and sends an NTTDP agent downlink message to the target switching device through the terminal device and the root device; after the target device parses the received NTTDP agent downlink message, it maps the message content to the network management protocol processing flow for configuration downlink, and sends the NTTDP agent response message to the server through the root device, so as to complete the proxy configuration downlink; and sends the NTTDP agent downlink message to the server through the terminal device and the root device. An agent reporting instruction is sent to each level of switching equipment in the network topology diagram step by step. After receiving the agent reporting instruction, the switching equipment at each level encapsulates its own link status and device information into a response message and reports it to the root device. The root device summarizes the link status and device information of the switching equipment at each level and reports them to the server in a unified manner to complete the agent reporting; after the root device completes the agent configuration issuance and agent reporting, the managed network device is managed through the server; compared with the prior art, the present invention interacts with the server through the root device, completes the agent configuration issuance and agent reporting through the root device, prevents each network device from sending the generated message to the server, reduces the burden on the server, facilitates the technical personnel to manage the managed network device through the server, and improves the management efficiency of the network device.

[0018] Other beneficial effects of the present invention will be described in detail in the subsequent specific implementation section. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 It is a schematic diagram of a flow chart of an embodiment of the present invention; Figure 2 A schematic diagram of a network topology diagram in an embodiment of the present invention; Figure 3 A dynamic change diagram of the level division in an embodiment of the present invention; Figure 4 A schematic diagram of the process of issuing proxy configuration in an embodiment of the present invention; Figure 5The figure is a schematic diagram of the process of agent reporting in an embodiment of the present invention. DETAILED DESCRIPTION

[0020] In order to make the technical problems, technical solutions and advantages to be solved by the present invention clearer, the following will be described in detail with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0021] In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicating the orientation or positional relationship, are based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first", "second", and "third" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance.

[0022] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "installation", "connection" and "connection" should be understood in a broad sense, for example, it can be a locking connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0023] In addition, the technical features involved in the different embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0024] The invention aims at solving the existing problems and provides a network equipment management method.

[0025] like Figure 1 As shown, an embodiment of the present invention provides a network device management method, including: Step 1: Connect the server to the gateway device in the target local area network, establish a data transmission channel, and use the terminal device to communicate with the gateway device; Step 2: Send a level classification instruction message to the gateway device through the terminal device, classify the gateway device and the switching devices directly and indirectly connected to the gateway device, and obtain a network topology map, in which the root device of the network topology map is the gateway device; Step 3, select a switching device as the target device in the network topology diagram, send the NTTDP agent downlink message to the target switching device through the terminal device and the root device, the target device parses the received NTTDP agent downlink message, maps the message content to the network management protocol processing flow for configuration downlink, and sends the NTTDP agent response message to the server through the root device self-data transmission channel to complete the proxy configuration downlink; Step 4: The terminal device and the root device send the proxy reporting instruction to the switching devices at each level in the network topology diagram step by step. After receiving the proxy reporting instruction, the switching devices at each level encapsulate their own link status and device information into a response message and report it to the root device. The root device summarizes the link status and device information of the switching devices at each level and reports them to the server through the data transmission channel to complete the proxy reporting; Step 5: After the root device completes the proxy configuration delivery and proxy reporting, the server manages the managed network device through the data transmission channel. The managed network device is a gateway device or a switching device in the network topology diagram.

[0026] In the embodiment of the present invention, the terminal device may be a computing device such as a mobile phone, a desktop computer, a notebook, a palm computer, etc.

[0027] Specifically, the terminal device sends a level division instruction message to the gateway device, and the gateway device and the switching devices directly and indirectly connected to the gateway device are divided into levels to obtain a network topology diagram. The root device of the network topology diagram is the gateway device, including: Sending a level classification instruction message to the gateway device through the terminal device; The gateway device sends a topology discovery message carrying its own level information to the switching devices directly and indirectly connected to the gateway device according to the level classification instruction message; For each switching device directly or indirectly connected to the gateway device, the switching device generates its own level based on the number of connection hops with the gateway device; The network topology diagram is formed according to the level of each switching device, and the gateway device is used as the root device in the network topology diagram.

[0028] Specifically, the network topology diagram includes multiple switching devices directly connected to the root device, such as Figure 2 As shown, in the embodiment of the present invention, taking device A, device B, and device C as an example, the process of level division includes: 1. Use a mobile phone to send a discovery message to the NTTDP device connected to the same gateway; 2. When Device A receives the discovery message HTTP_LE_INFORM, it regards itself as the root device with a root depth level of level = 2, and sends a message NTTDP_LE_INFORM (Port = 2122, Class = 4, Type = 1, Level = 2) for notifying the LE startup and transmitting the Level value to all ports that have completed the NTTDP inquiry along all paths; 3. After receiving the NTTDP_LE_INFORM message sent by Device A, Device B enables its own Level Enable, parses the received Level(A) = 2, stores it in the Level Port of the port entry where this message is received, and then compares Level(A) with its own Level(B) = 128 (default value). If Level(A) < Level(B), then Level(B) = Level(A) + 1, that is, Device B becomes a subordinate of Device A. At this time, the value of Level(B) changes, and it continues to send NTTDP_LE_INFORM (Port = 2122, Class = 4, Type = 1, Level = Level(B) = 2 + 1 = 3) to all ports that have completed the NTTDP inquiry after connection.

[0029] When the lower-level Device C receives the message from Device B, it will perform the operation as described in 3 above, resulting in Level(C) = Level(B) + 1 = 4. Then Device C becomes a subordinate of Device B. At the same time, Device A will also receive the NTTDP_LE_INFORM sent by B and will also record Level(B) in the Level Port of the corresponding port. However, since Level(A) < Level(B), the value of Level(A) will not change, and it will not continue to send NTTDP_LE_REQUEST messages.

[0030] During the process of level division, the dynamic changes are as Figure 3 shown, and the change process is as follows: Level convergence detection: The timer scans the Level Port values of each port, and calculates whether the environment where the device is located converges in combination with its own Level value. There are three cases in total: Convergence: Can execute subsequent functions, Level Update = 0; Silence: Disconnect from other devices and do not send messages externally to achieve convergence, do not execute subsequent operations, LevelUpdate = 1; Exception: The level does not match the surrounding environment. Send NTTDP_LE_REPLY (Port = 2122, Class = 4, Type = 2) to notify the linkup port device to send the message NTTDP_LE_REQUEST for requesting Inform update to the surrounding devices when the non-root device is in an abnormal state until convergence is achieved, and Level Update = 1; Port LinkUp and LinkDown: When a new LinkUp occurs on the device port and the NTTDP inquiry is completed, NTTDP_LE_INFORM will be sent to form a new level relationship, and the original relationship will also be updated with the Level convergence detection; when the NTTDP inquiry times out after a LinkDown occurs on the device port, the device will detect whether the LinkDown port is its upper-level exit (Level Port < Level). If so, the Level value will be changed to the default value, and the message NTTDP_LE_DELETE (Port = 2122, Class = 4, Type = 3, Level = 0) will be sent to notify its lower-level exits (Level Port > Level) when the non-root device leaves the environment (such as disconnecting the connection), so that the lower-level devices will also change their own Level values to the default value, and the lower-level devices will continue to notify their own lower-level devices.

[0031] If device A does not continuously receive HTTP messages from the mobile phone during the period of being the root device, it will send NTTDP_LE_CLEAN (Port = 2122, Class = 4, Type = 4, Level = default) for timing out to close the global LE function and clear all paths to notify all devices in the environment to return to the default state.

[0032] Specifically, the network topology diagram includes at least one switching device directly connected to the root device and at least one next-level switching device connected to the root device through the switching device.

[0033] Specifically, step 3 includes: Select a switching device as the target device in the network topology diagram and send a proxy download instruction to the root device through the terminal device; The root device encapsulates the proxy download instruction into an NTTDP proxy download message and sends it to the target switching device; After parsing the received NTTDP proxy download message, the target device maps the message content to the network management protocol processing flow for configuration download and forwards the NTTDP proxy response message to the root device; After the root device parses the NTTDP proxy response message, it encapsulates the response message into a network management protocol message and sends it to the server through the data transmission channel to complete the proxy configuration delivery.

[0034] like Figure 4 As shown, the embodiment of the present invention takes four network devices as an example, namely device A, device B, device C, and device D. Device A is connected to device B, and devices B, device C, and device D are connected to each other in pairs. The proxy configuration delivery process is specifically as follows: The mobile phone sends a discovery message to the NTTDP device connected to the same gateway, and sends a configuration message HTTP_CF_INFORM; After receiving the message, device A turns on the level classification function (Level) to identify itself as the root device, and sends an LE message to its neighbors to generate a level; Root device A turns on the proxy submit function and notifies its neighbors. Each device forms a port table entry NTTDP Proxy Port. At this time, the root device does not need to upload the environment topology information to the server. Root device A parses the information in the configuration message (DstDev Mac, Packet), and first checks whether Dst-Mac is its own Mac address; if so, it passes the Packet information to the tr069 process for processing, and returns a success message to the mobile phone after the processing is completed; if not, it compares DstDev Mac with the Mac information in the NTTDP Proxy Port table under each of its own ports; if the retrieval is successful, it sends a message NTTDP_CF_REQUEST (Port=2122, Class=6, Type=1, DstDev Mac, Configuration Data) to the port peer device B, which is used to pass the target MAC information to the lower-level device and carries the configuration information to be implemented; if the retrieval fails, it directly returns a failure message to the mobile phone; After receiving the NTTDP_CF_REQUEST message, device B parses the information in the message (DstDev Mac, Configuration Data) and first checks whether DstDev Mac is its own Mac address. If so, it passes the Packet information to the tr069 process for processing, and returns the NTTDP_CF_REPLY (Port=2122, Class=6, Type=2, Result=1) message to the superior after the processing is completed. If not, DstDev Mac is compared with the Mac information in the NTTDP Proxy Port table under each of its own ports; if the retrieval is successful, it sends the NTTDP_CF_REQUEST (Port=2122, Class=6, Type=1, Dst-Mac, Configuration Data) message to the port peer device C; if the retrieval fails, it returns the NTTDP_CF_REPLY (Port=2122, Class=6, Type=2, Result=2) message used to return the execution status of the configuration to the superior device.

[0035] After receiving the NTTDP_CF_REQUEST message, device C repeats the above operation; After receiving the NTTDP_CF_REPLY message, the non-root device forwards it to the superior; after receiving the NTTDP_CF_REPLY message, the root device A replies to the mobile phone whether it is successful or not.

[0036] Specifically, the instructions sent by the agent are filled with the physical information of the target switching device.

[0037] Specifically, the root device encapsulates the proxy delivery instruction into an NTTDP proxy delivery message and sends it to the target switching device, including: The root device encapsulates the proxy delivery instruction into an NTTDP proxy delivery message according to the hierarchical relationship table and the MAC-PORT information table, and sends the NTTDP proxy delivery message to the switching device directly connected to the root device; The switching device directly connected to the root device parses the message sent by the NTTDP agent. When the physical information filled in the message sent by the NTTDP agent is consistent with the physical information of the switching device directly connected to the root device, the switching device is the target switching device and stops sending the message sent by the NTTDP agent. When the physical information filled in the NTTDP agent sent message is not consistent with the physical information of the switching device directly connected to the root device, the NTTDP agent sent message is sent to the next-level switching device until it is sent to the target switching device.

[0038] Specifically, step 4 includes: The terminal device sends the proxy reporting instruction to the root device, and the root device sends the proxy reporting instruction step by step to the lowest switching device in the network topology diagram; After receiving the proxy reporting instruction, the switching devices at all levels in the network topology diagram encapsulate their own link status and device information into a response message, and report the response message to the root device; The root device summarizes the link status and device information of the switching devices at all levels in the network topology diagram, and reports the summary results to the server through the data transmission channel to complete the proxy reporting.

[0039] like Figure 5 As shown, the embodiment of the present invention takes four network devices as an example, namely device A, device B, device C, and device D. Device A is connected to device B, device B is connected to device C, and device B is connected to device D. The proxy reporting process is specifically as follows: Use the mobile phone to send a discovery message to the NTTDP device connected to the same gateway; After receiving the HTTP_PR_INFORM message for notifying neighbors that the proxy function is enabled, device A enables the Level function, regards itself as the root device, and sends a NTTDP_PR_REQUEST (Port=2122, Class=5, Type=1) message to device B to notify that Proxy Enable=1 is enabled. Device B performs the same operation to notify devices C and D. In a stable level environment (Level Update=1), the lower-level device will summarize the configuration information of each port that has completed the Neighbor Search (Search Upa date=1) into the NTTDP Proxy Buf, and send NTTDP_PR_SUBMIT (Prot=2122, Class=5, Type=2, Proxy DevNode, Proxy Link Node) to report its own configuration once to the upper-level device with the smallest port number, and report again when its own configuration information changes. The upper-level device receives the NTTDP_PR_SUBMIT message from the lower-level device that reports the non-root device proxy information to the root device along the Level path, and forwards it to its own upper level; forwarding at each level, the final message is sent to the root device for summary.

[0040] When receiving NTTDP_PR_SUBMIT, all devices will record the Mac in the message data into the port table entry NTTDP Proxy Port to record which subordinates the port has.

[0041] After receiving the NTTDP_PR_SUBMIT messages from each device, the root device aggregates the Proxy DevNode and ProxyLink Node information and uploads the latest information after the HTTP request.

[0042] Specifically, device information includes connection ports and its own physical information.

[0043] The embodiment of the present invention first connects a server to a gateway device in a target local area network, and uses a terminal device to communicate with the gateway device; sends a level division instruction message to the gateway device through the terminal device, and divides the gateway device and the switching devices directly and indirectly connected to the gateway device into levels, so as to obtain a network topology diagram in which the root device is the gateway device; selects a switching device as a target device in the network topology diagram, and sends the NTTDP agent downlink message to the target switching device through the terminal device and the root device; after the target device parses the received NTTDP agent downlink message, it maps the message content to the network management protocol processing flow for configuration and downlink, and sends the NTTDP agent response message to the server through the root device to complete the proxy configuration downlink; through the terminal The device and the root device send proxy reporting instructions to the switching devices at all levels in the network topology diagram step by step. After receiving the proxy reporting instructions, the switching devices at all levels encapsulate their own link status and device information into a response message and report it to the root device. The root device summarizes the link status and device information of the switching devices at all levels and reports them to the server in a unified manner to complete the proxy reporting; after the root device completes the proxy configuration issuance and proxy reporting, the managed network device is managed through the server; compared with the prior art, the embodiment of the present invention interacts with the server through the root device, completes the proxy configuration issuance and proxy reporting through the root device, prevents each network device from sending the generated message to the server, reduces the burden on the server, and facilitates the technical personnel to manage the managed network device through the server.

[0044] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A network device management method, characterized in that: include: Step 1, connecting the server to a gateway device in a target local area network, establishing a data transmission channel, and using a terminal device to communicate with the gateway device; Step 2, sending a hierarchical classification instruction message to the gateway device through the terminal device, classifying the gateway device and the switching devices directly and indirectly connected to the gateway device, and obtaining a network topology map, wherein the root device of the network topology map is the gateway device; Step 3, selecting a switching device as a target device in the network topology diagram, sending the NTTDP proxy message to the target switching device through the terminal device and the root device, the target device parses the received NTTDP proxy message, maps the message content to the network management protocol processing flow for configuration sending, and sends the NTTDP proxy response message to the server through the root device from the data transmission channel to complete the proxy configuration sending; Step 4, issuing a proxy reporting instruction through the terminal device and the root device to the switching devices at each level in the network topology diagram step by step, after receiving the proxy reporting instruction, the switching devices at each level encapsulate their own link status and device information into a response message and report it to the root device, the root device summarizes the link status and device information of the switching devices at each level and reports them to the server through the data transmission channel, thereby completing the proxy reporting; Step 5: After the root device completes the proxy configuration sending and proxy reporting, the server manages the managed network device through the data transmission channel, and the managed network device is a gateway device or a switching device in the network topology diagram.

2. The network device management method according to claim 1, characterized in that: Sending a level division instruction message to the gateway device through the terminal device, performing level division on the gateway device and the switching devices directly and indirectly connected to the gateway device, and obtaining a network topology map, wherein the root device of the network topology map is the gateway device, including: Sending a level classification instruction message to the gateway device through the terminal device; The gateway device sends a topology exploration message carrying its own level information to the switching devices directly and indirectly connected to the gateway device according to the level classification instruction message; For each switching device directly or indirectly connected to the gateway device, the switching device generates its own level based on the number of connection hops with the gateway device; The network topology diagram is formed according to the level of each switching device, and the network topology diagram takes the gateway device as the root device.

3. The network device management method according to claim 2, characterized in that: The network topology diagram includes a plurality of switching devices directly connected to the root device.

4. The network device management method according to claim 2, characterized in that: The network topology diagram includes at least one switching device directly connected to the root device and at least one next-level switching device connected to the root device through the switching device.

5. The network device management method according to claim 2, characterized in that: The step 3 comprises: Selecting a switching device as a target device in the network topology diagram, and sending an agent issuing instruction to the root device through the terminal device; The root device encapsulates the proxy sending instruction into an NTTDP proxy sending message and sends it to the target switching device; After parsing the received NTTDP proxy sent message, the target device maps the message content to the network management protocol processing flow for configuration and sends it, and forwards the NTTDP proxy response message to the root device; After parsing the NTTDP proxy response message, the root device encapsulates the response message into a network management protocol message and sends it to the server through the data transmission channel, thereby completing the proxy configuration delivery.

6. The network device management method according to claim 5, characterized in that: The proxy sends instructions filled with the physical information of the target switching device.

7. The network device management method according to claim 6, characterized in that: The root device encapsulates the proxy delivery instruction into an NTTDP proxy delivery message and delivers it to the target switching device, including: The root device encapsulates the proxy sending instruction into an NTTDP proxy sending message according to the hierarchical relationship table and the MAC-PORT information table, and sends the NTTDP proxy sending message to the switching device directly connected to the root device; The switching device directly connected to the root device parses the message sent by the NTTDP agent. When the physical information filled in the message sent by the NTTDP agent is consistent with the physical information of the switching device directly connected to the root device, the switching device is the target switching device and stops sending the message sent by the NTTDP agent. When the physical information filled in the NTTDP proxy sent message is not consistent with the physical information of the switching device directly connected to the root device, the NTTDP proxy sent message is sent to the next level switching device until it is sent to the target switching device.

8. The network device management method according to claim 7, characterized in that: The step 4 comprises: Sending a proxy reporting instruction to the root device through a terminal device, and the root device sending the proxy reporting instruction step by step to the lowest switching device in the network topology diagram; After receiving the proxy reporting instruction, the switching devices at all levels in the network topology diagram encapsulate their own link status and device information into a response message, and report the response message to the root device; The root device summarizes the link status and device information of the switching devices at each level in the network topology diagram, and uniformly reports the summary results to the server through the data transmission channel to complete the proxy reporting.

9. The network device management method according to claim 8, characterized in that: The device information includes connection ports and its own physical information.

Images