WO2016184025A1 - 一种设备管理方法和装置 - Google Patents

一种设备管理方法和装置 Download PDF

Info

Publication number
WO2016184025A1
WO2016184025A1 PCT/CN2015/092200 CN2015092200W WO2016184025A1 WO 2016184025 A1 WO2016184025 A1 WO 2016184025A1 CN 2015092200 W CN2015092200 W CN 2015092200W WO 2016184025 A1 WO2016184025 A1 WO 2016184025A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
springboard
management server
network management
network
Prior art date
Application number
PCT/CN2015/092200
Other languages
English (en)
French (fr)
Inventor
王亚辉
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016184025A1 publication Critical patent/WO2016184025A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0272—Virtual private networks

Definitions

  • This document relates to, but is not limited to, the field of network management technology, and in particular, to a device management method and apparatus.
  • the management device generally uses the Simple Network Management Protocol (SNMP) protocol.
  • SNMP Simple Network Management Protocol
  • UDP User Datagram Protocol
  • MIB Management Information Base
  • the network management server also needs to maintain its own database. When it needs to be changed, both need to be changed, and the workload is huge.
  • the network management server and the device cannot establish a UDP connection and the device cannot be managed by using the SNMP protocol
  • other protocols are generally used to implement network device management, for example, using a routing protocol (open shortest path first protocol OSPF, intermediate system to intermediate)
  • OSPF open shortest path first protocol
  • ISIS intermediate system to intermediate
  • This method requires the creation of an independent network management domain, which has complicated configuration, high maintenance and training costs, and maintenance personnel.
  • the disadvantages of high technical requirements indirectly reduce the popularity of the network management; for example, the network management protocol based on the virtual private network (VPN) enables the network management server to manage the entire network device.
  • VPN virtual private network
  • This method requires a VPN environment to be created, and the disadvantage is that only the same network can be managed.
  • a private network device if you need to manage the public network device, you need to publish the public network route to the private network.
  • the configuration problem is also difficult.
  • the device needs to support the VPN protocol. The popularity is not high and the use is inconvenient.
  • the management device solution has a technical problem of complicated configuration, high cost, inconvenient use, and low popularity. question.
  • the embodiment of the invention provides a device management method and device, which can solve the problem that the management device solution has complicated configuration, high cost, inconvenient use, and low popularity when the network management server and the device cannot establish a UDP connection. problem.
  • An embodiment of the present invention provides a device management method, including the following steps:
  • the network management server detects whether the device has a springboard that can log in to the device.
  • the network management server logs in to the device by using the springboard
  • the network management server performs data interaction with the device through the springboard to implement management of the device.
  • the step of the network management server performing data interaction with the device by using the springboard to implement the device management includes:
  • the network management server sends a data synchronization request to the device by using the springboard;
  • the network management server generates configuration data of the device
  • the network management server sends the configuration data to the device by using the springboard.
  • the step of the network management server receiving, by using the springboard, the device data returned by the device in response to the data synchronization request includes:
  • the network management server parses the data packet to obtain device data.
  • the step of the network management server receiving the data packet returned by the device forwarded by the springboard in response to the data synchronization request includes:
  • the network management server receives the Telnet protocol data packet returned by the device forwarded by the springboard in response to the data synchronization request by using a Telnet protocol (Remote Terminal Protocol).
  • Telnet protocol Remote Terminal Protocol
  • the device management method further includes:
  • the network management server stores the device data in a corresponding database according to the type of the device data.
  • the step of the network management server sending the configuration data to the device by using the springboard includes:
  • the network management server processes the configuration data into a data message that can be transmitted on the springboard and identified by the device;
  • the network management server sends the data packet to the springboard, and the springboard forwards the configuration data to the device.
  • the step of the network management server processing the configuration data into a data message that can be transmitted on the springboard and identified by the device includes:
  • the network management server When the network management server, the device, and the springboard all support the Telnet protocol, the network management server encapsulates the configuration data into a Telnet protocol data packet.
  • Another embodiment of the present invention provides a device management method, including the following steps:
  • the device accepts the login of the network management server through the springboard of the device;
  • the device performs data interaction with the network management server through the springboard to implement management of the device by the network management server.
  • the step of performing data interaction between the device and the network management server by using the springboard includes:
  • the device receives the data synchronization request sent by the network management server through its springboard;
  • the device receives configuration data sent by the network management server by using the springboard.
  • the step of the device sending the corresponding device data to the network management server by using the springboard in response to the data synchronization request includes:
  • the device acquires corresponding device data in response to the data synchronization request
  • the device processes the device data into a data message that can be transmitted on the springboard and recognized by the network management server;
  • the device sends the processed data packet to the network management server through the springboard.
  • the step of the device processing the device data into a data message that can be transmitted on the springboard and recognized by the network management server includes:
  • the device When the stencil, the device, and the network management server support the Telnet protocol, the device encapsulates the device data into a Telnet protocol data packet;
  • the device sends the data packet to the network board through the Telnet protocol, and the data packet is forwarded to the network management server by using the Telnet protocol.
  • the data packet includes: identifier information of the packet content type and a packet body, where the packet body carries the device data and a protocol type indicating the packet.
  • the step of the device receiving the configuration data sent by the network management server by using the springboard includes:
  • the device parses the Telnet protocol data packet to obtain configuration data.
  • the embodiment of the present invention further provides a device management apparatus, which is applied to a network management server, and includes: a detection module, a login module, and a management module;
  • the detecting module is configured to detect, when the network management server cannot directly log in to the device, whether the device has a springboard that can log in to the device;
  • the login module is configured to log in to the device by using the springboard when the detecting module detects that the device has a springboard that can log in to the device;
  • the management module is configured to perform data interaction with the device through the springboard to implement management of the device.
  • the management module is configured to:
  • the configuration data is sent to the device through the springboard.
  • the embodiment of the present invention further provides another device management apparatus, which is applied to a device, including: a login module and a data transmission module;
  • the login module is configured to accept login of the network management server through the springboard of the device;
  • the data transmission module is configured to perform data interaction with the network management server through the springboard to implement management of the device by the network management server.
  • the data transmission module is configured to:
  • the embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the above method.
  • the device management method of the embodiment of the present invention includes: when the network management server cannot directly log in to the device, detecting whether the device has a springboard that can log in to the device; if yes, the network management server logs in to the device through the springboard.
  • the network management server performs data interaction with the device through the jumper to implement management of the device; the device management method in the embodiment of the present invention is in the network management service. If the device cannot be connected to the device, you can use the device's springboard to log in to the device and connect to the device. The device can be managed through the springboard. It is applicable to the management of all devices with springboards.
  • the device management method of the embodiment of the present invention does not need to change the device much, and only needs to provide a corresponding interface, simple configuration, low maintenance and training cost, low technical requirements for maintenance personnel, and low cost. It is easy to use and further enhances the popularity of the program.
  • FIG. 1 is a schematic flowchart of a device management method according to Embodiment 1 of the present invention.
  • FIG. 2 is a schematic flowchart of another device management method according to Embodiment 1 of the present invention.
  • FIG. 3 is a schematic flowchart of data synchronization according to Embodiment 1 of the present invention.
  • FIG. 4 is a schematic flowchart of a warehousing operation according to Embodiment 1 of the present invention.
  • FIG. 5 is a schematic diagram of a format of a data packet according to Embodiment 1 of the present invention.
  • FIG. 6 is a schematic flowchart of decoding a message according to Embodiment 1 of the present invention.
  • FIG. 7 is a schematic flowchart of configuring device data according to Embodiment 1 of the present invention.
  • FIG. 8 is a schematic flowchart of a device management method according to Embodiment 2 of the present invention.
  • FIG. 9 is a schematic flowchart of data synchronization according to Embodiment 3 of the present invention.
  • FIG. 10 is a schematic structural diagram of a device management apparatus according to Embodiment 4 of the present invention.
  • FIG. 11 is a schematic structural diagram of another device management apparatus according to Embodiment 4 of the present invention.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the embodiment provides a device management.
  • the method as shown in Figure 1, includes the following steps:
  • Step 101 When the network management server cannot directly log in to the device, the network management server detects whether the device has a springboard that can log in to the device. If yes, step 102 is performed. If not, step 104 is performed.
  • the network management server when the network management server needs to manage the device, the network management server first detects whether the device to be managed can directly log in. If the device can directly log in, the network management server directly logs in to the device for management. If you log in to the device directly, you can further detect whether the device has a springboard that can log in to the device.
  • the springboard of the device in this embodiment may be a primary springboard, a secondary springboard, or a multi-level springboard of the device.
  • Step 102 The network management server logs in to the device through the springboard.
  • the network management server logs in to the device through the springboard, and the network management server establishes a connection with the device through the springboard, so that the network management server and the device are indirectly reachable.
  • the network management server can remotely log in to the device through the primary, secondary, or multi-level springboard.
  • Step 103 The network management server performs data interaction with the device through the springboard to implement management of the device, and the process ends.
  • the device management in this embodiment may include: data synchronization or data configuration; and of course, other management of the device may be performed.
  • the process of synchronizing the network management server with the device data may include:
  • the network management server sends a data synchronization request to the device through the springboard;
  • the network management server receives, by the springboard, device data returned by the device in response to the data synchronization request.
  • the network management server sends a data synchronization request to the device's springboard, and then the device's springboard forwards the data synchronization request to the device. After receiving the data synchronization request, the device sends the corresponding device data to the springboard, which is forwarded by the springboard.
  • Network management server sends a data synchronization request to the device's springboard, and then the device's springboard forwards the data synchronization request to the device. After receiving the data synchronization request, the device sends the corresponding device data to the springboard, which is forwarded by the springboard.
  • the device obtains the corresponding device data in response to the data synchronization request, and then processes the device data into a data packet and sends the data packet to the springboard (for example, encoding the device data to encapsulate the data packet), and forwarding the data packet to the network management server by the springboard.
  • the process of the network management server in the embodiment receiving the device data returned by the device in response to the data synchronization request by using the springboard may include:
  • the network management server parses the data packet to obtain device data (optionally, the network management server decodes the data packet to obtain corresponding device data).
  • the device when the network management server, the device, and the springboard support the Telnet protocol, the device encapsulates the corresponding device data into a Telnet protocol data packet.
  • the device sends the data packet to the springboard through the Telnet protocol.
  • the data packet is forwarded to the network management server by using the Telnet protocol.
  • the network management server receives the Telnet protocol data packet returned by the device forwarded by the springboard in response to the data synchronization request.
  • the device when the network management server, the device, and the springboard support other communication protocols, the device may encapsulate the device data into a corresponding communication protocol packet, and the network management server receives the springboard through the communication protocol and conforms to the communication. Protocol message.
  • the network management server generates configuration data of the device
  • the network management server sends the configuration data to the device by using the springboard.
  • the network management server configures the corresponding configuration data in the configuration database, and then sends the configuration data to the springboard, which is forwarded to the device by the springboard.
  • the configuration data may be transmitted by using the data packet. Therefore, the process of the network management server sending the configuration data to the device by using the springboard in the embodiment includes:
  • the network management server processes the configuration data into a data message that can be transmitted on the springboard and identified by the device;
  • the network management server sends the data packet to the springboard, and the springboard forwards the configuration data to the device.
  • the process of processing, by the network management server, the configuration data into data packets that can be transmitted on the springboard and recognized by the device includes: :
  • the network management server encapsulates the configuration data into a Telnet protocol data packet.
  • the network management server, the device, and the springboard exchange data through the same communication protocol (for example, the Telnet protocol).
  • the Telnet protocol for example, the Telnet protocol
  • the first communication protocol may be used to exchange data between the network management server and the device
  • the second communication protocol may be used to exchange data between the device and the springboard.
  • the springboard increases the communication protocol conversion function to implement The management of the device by the network management server; when the network management server or device sends data, the data needs to be encapsulated into corresponding protocol packets.
  • Step 104 It is determined that the management of the device fails.
  • the device when the network management server and the device are unable to establish a connection, the device can be connected to the device through the springboard of the device, and the device is managed through the springboard, and is applicable to the management of all devices with the springboard. Since the general equipment has a springboard, the popularity is high.
  • the device management method of the embodiment of the present invention does not need to change a lot of equipment, and only needs to provide a corresponding interface, simple configuration, low maintenance and training cost, and maintenance personnel. The technical requirements are not high, the cost is reduced, and the use is convenient, which further improves the popularity of the program.
  • the device management method in this embodiment needs only all devices to support the standard Telnet protocol.
  • the network management system and the device need to implement the functions of encoding and decoding to manage the device, and implement device management across the network.
  • the network management system manages the equipment of the B internal network, the B internal network management manages the A external network equipment, the A external network management manages the B external network equipment, and the B external network management manages the A external network equipment, which solves the network management deployment subject to the equipment environment.
  • the problem is to improve the ease of use of the network management.
  • this embodiment provides a device management method, including the following steps:
  • Step 201 The network management server detects whether the device to be managed can directly log in. If not, step 202 is performed, and if yes, step 205 is performed.
  • Step 202 The network management server detects whether the device has a springboard, and if so, step 203 is performed, and if not, step 206 is performed;
  • Step 203 The network management server detects whether the device's springboard can remotely log in to the device, and if so, step 204 is performed, and if not, step 206 is performed;
  • Step 204 The network management server remotely logs in to the device through the springboard, and performs data interaction with the device through the springboard to implement management of the device, and the process ends.
  • performing data interaction between the board and the device to implement device management includes: synchronizing data with the device through a springboard or configuring the device through a springboard.
  • the data synchronization process and the process of configuring the device can be referred to the above description.
  • Step 205 The network management server directly logs in to the device to manage the device, and the process ends.
  • Step 206 It is determined that the management of the device fails, and the process ends.
  • the embodiment further provides a method for data synchronization between a network management server and a device, including the following steps:
  • Step 301 When the network management server cannot directly log in to the device, check whether the device has a springboard that can log in to the device. If yes, go to step 302. If no, go to step 307.
  • Step 302 The network management server logs in to the device through the springboard.
  • Step 303 The network management server sends a data synchronization request to the device by using the springboard.
  • Step 304 The network management server receives, by using the Telnet protocol, the Telnet protocol data packet returned by the device forwarded by the springboard in response to the data synchronization request.
  • the device obtains the corresponding device data, and then the device data is encapsulated into a network management server, the springboard, and the device support the Telnet protocol data packet to be sent to the springboard, and the data packet is sent by the springboard. Forward to the network management server.
  • Step 305 The network management server parses the Telnet protocol data packet to obtain device data.
  • the network management server decodes the data packet to obtain device data.
  • Step 306 The network management server stores the device data, and the process ends.
  • Step 307 It is determined that the data synchronization fails, and the process ends.
  • the network management server and the device perform data synchronization, after obtaining the device data, the network management server further needs to store the device data; the device data may be stored in the corresponding database, and the ground may be based on the type of the device data. It is stored in the corresponding database.
  • the device data fed back by the device may include: status data and/or configuration data of the device; wherein the status data may include: basic status data, protocol status data, and alarm monitoring Data, configuration data may include: basic configuration data, protocol configuration data, and maintenance configuration data.
  • the process of performing the warehousing operation after the network management server obtains the device data fed back by the device includes:
  • Step 401 Determine whether the device data is status data or configuration data. If it is configuration data, execute step 402. If it is status data, execute step 408.
  • Step 402 Determine whether the configuration data is basic configuration data. If yes, execute step 403. If no, execute step 404.
  • Step 403 Update the basic configuration database according to the device data, and the process ends.
  • Step 404 Determine whether the configuration data is protocol configuration data. If yes, go to step 405. If no, go to step 406.
  • Step 405 The database is configured according to the device data update protocol, and the process ends.
  • Step 406 Determine whether the configuration data is maintenance configuration data. If yes, go to step 407. If no, go to step 414.
  • Step 407 Update the maintenance database according to the device data, and the process ends.
  • Step 408 Determine whether the status data is basic state data. If yes, execute step 409. If no, execute step 410.
  • Step 409 Update the basic state database according to the device data, and the process ends.
  • Step 410 Determine whether the status data is protocol status data. If yes, execute step 411. If no, execute step 412.
  • Step 411 Update the protocol status database according to the device data, and the process ends.
  • Step 412 Determine whether the status data is alarm monitoring data. If yes, go to step 413. If no, go to step 414.
  • Step 413 Update the alarm monitoring database according to the device data, and the process ends.
  • Step 414 It is determined that the storage fails, and the process ends.
  • the order of determining whether the configuration data is basic configuration data, protocol configuration data, or maintenance data configuration may be set according to actual conditions, and is not limited to the determination shown in FIG. 4 .
  • Order; also when the received device data is status data, The order in which the status data is judged to be the basic status data, the protocol status data, or the alarm monitoring data may be set according to actual conditions and is not limited to the determination order shown in FIG.
  • the device When the device constructs the data packet, it can distinguish the type of the device data (for example, whether the device data is configuration data or state data) and the type of the protocol; optionally, the identifier information of the packet content type and the packet body can be distinguished.
  • the message body carries the device data and a protocol type indicating the message.
  • the format of the Telnet data packet is as follows: the packet start tag, the packet header (used to mark the device data carried by the packet as status data or configuration data), and the packet body 1 ... the message body n (the message body definition protocol type) and the message end tag bit (that is, the message transmission is completed).
  • Step 601 Determine whether the message start flag is received, if yes, go to step 602, if no, go to step 608;
  • Step 602 Determine whether a packet header tag is received. If yes, go to step 603. If no, go to step 609.
  • Step 603 Decode the packet header flag to determine whether the device data carried in the packet is status data or configuration data. If the status data is the status data, go to step 604. If the configuration data is configured, go to step 610.
  • Step 604 Determine whether the packet body carrying the status data is received. If yes, go to step 605. If no, go to step 609.
  • Step 605 Decode the packet body carrying the state data to obtain the state data.
  • Step 606 Determine whether the message tail tag is received. If yes, go to step 607.
  • Step 607 The state data is stored in the corresponding database, and the process ends.
  • Step 608 The decoding fails and the process ends.
  • Step 609 An error is reported and the process ends.
  • Step 610 Determine whether the packet body carrying the configuration data is received. If yes, go to step 611. If no, go to step 609.
  • Step 611 Decode the packet body carrying the configuration data to obtain configuration data.
  • Step 612 Determine whether the message tail tag is received. If yes, go to step 613.
  • Step 613 The configuration data is stored in the corresponding database, and the process ends.
  • the network management server can also send configuration data to the device through the springboard to implement the configuration device, as shown in FIG. 7, which is a process for configuring data to the device, including :
  • Step 701 The network management server generates configuration data of the device.
  • Step 702 The network management server processes the configuration data into a data message that can be transmitted on the springboard and recognized by the device.
  • the network management server When the network management server, the device, and the springboard all support the Telnet protocol, the network management server encapsulates the configuration data into a Telnet protocol data packet.
  • the format of the data packet refer to Figure 5.
  • Step 703 The network management server sends the data packet to the springboard, and the configuration data is forwarded by the network board to the device.
  • the device management method in this embodiment only needs to use the Telnet protocol to manage devices, and can implement device management across networks.
  • the method has the advantages of simplicity, convenience, low cost, and high popularity.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the embodiment provides a device management method, including the following steps:
  • Step 801 The device accepts the login of the network management server through the springboard of the device.
  • the device can receive the login of the network management server through the springboard, that is, the device connects to the network management server through the springboard.
  • Step 802 The device performs data interaction with the network management server through the springboard to implement management of the device by the network management server.
  • the management of the device in this embodiment includes: data synchronization and configuration device data.
  • Step 802 includes: receiving, by the device, a data synchronization request sent by the network management server by using the springboard;
  • the device receives configuration data sent by the network management server through the springboard.
  • the process on the device side includes:
  • the device acquires corresponding device data in response to the data synchronization request
  • the device processes the device data into a data message that can be transmitted on the springboard and recognized by the network management server;
  • the device sends the processed data packet to the network management server through the springboard.
  • the device can collect configuration information, protocol information, and monitoring information of the device in real time to form a database. After receiving the data synchronization request, the device obtains corresponding device data and feeds back to the network management server.
  • the device processes the device data into a datagram that can be transmitted on the springboard and recognized by the network management server.
  • the process of the text includes:
  • the device encapsulates the device data into a Telnet protocol data packet
  • the device sends the data packet to the network board through the Telnet protocol, and the data packet is forwarded to the network management server by using the Telnet protocol.
  • the database formed by the device collecting information in real time can be a Telnet information database.
  • the data packet encapsulated by the device in this embodiment may include: identifier information of the packet content type and a packet body, where the packet body carries the device data and a protocol type indicating the packet.
  • identifier information of the packet content type may be included in the packet encapsulated by the device in this embodiment.
  • the packet body carries the device data and a protocol type indicating the packet.
  • the process on the device side includes:
  • the device receives the data packet sent by the network management server forwarded by the springboard;
  • the device parses the data packet to obtain configuration data.
  • the network management server can send the configuration data to the device through the springboard to implement the configuration of the device.
  • the network management server can encapsulate the configuration data into a data packet and send the data packet to the device.
  • the device forwards the data packet to the device. After the text is decoded to obtain configuration data.
  • the data packet encapsulated on the network management side may include: identifier information of the content type of the packet and a packet body, where the packet body carries The device data and the protocol type indicating the message. For the specific format of the message, refer to FIG. 5 in the first embodiment.
  • the network management server When the stencil, the device, and the network management server support the Telnet protocol, the network management server encapsulates the configuration data into Telnet data packets and sends the data packets to the device.
  • the Telnet protocol forwards the data packets to the device.
  • the device receives the Telnet protocol data packet sent by the network management server that is forwarded by the network board through the Telnet protocol, and then parses the Telnet protocol data packet to obtain configuration data.
  • the device when the network management server and the device are unable to establish a connection, the device can be connected to the device through the springboard of the device, and the device is managed through the springboard, and is applicable to the management of all devices with the springboard. Since the general equipment has a springboard, the popularity is high.
  • the device management method of the embodiment of the present invention does not need to change a lot of equipment, and only needs to provide a corresponding interface, simple configuration, low maintenance and training cost, and maintenance personnel. The technical requirements are not high, the cost is reduced, and the use is convenient, which further improves the popularity of the program.
  • the device management method in this embodiment requires only all devices to support the standard Telnet protocol.
  • the network management system and the device need to implement the functions of encoding and decoding to manage the device and implement device management across the network.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • This embodiment provides a network management system, including: a network management server, a managed device, and a device springboard.
  • the network management server, the device, and the springboard all support the Telnet protocol.
  • the data synchronization process of the network management system includes, as shown in FIG. Show:
  • Step 901 The device collects information required for network management, such as configuration information, monitoring information, and protocol information, and stores the information in the Telnet information database.
  • information required for network management such as configuration information, monitoring information, and protocol information
  • Step 902 The network management server detects whether the device can directly log in to the device. If not, step 903 is performed, and if yes, step 907 is performed.
  • Step 903 The network management server detects whether the device has a springboard that can log in to itself. If yes, step 904 is performed, and if no, step 908 is performed.
  • the network management controller in the server first checks whether the device can directly log in, if Direct login, direct data synchronization request, if you can not log in directly, check whether there is a springboard, remotely log in to the device through the first, second or multi-level springboard, and then synchronize the data.
  • Step 904 The network management server logs in to the device through the springboard, and sends a data synchronization request to the device through the springboard.
  • Step 905 The device extracts the corresponding information from the Telnet information base according to the data synchronization request, and encodes the extracted information into a data packet suitable for transmission by using the Telnet protocol, and sends the data packet to the network management server through the springboard.
  • the device encoder encodes the Telnet information base information into a data message suitable for transmission by using Telnet.
  • the device encoder constructs a data packet, and the data packet needs to be distinguished from the protocol unit and the classification information (such as the configuration information or the state information).
  • Each protocol type is classified into a data dictionary to facilitate later expansion, and the final encoding becomes The format of the data message that can be transmitted over Telnet.
  • Step 906 After receiving the data packet, the network management server decodes the data packet to obtain the corresponding information, and stores the obtained information in the corresponding database, and the process ends.
  • the network management decoder decodes the data packet. After the packet is successfully decoded, each parameter of the packet is parsed by the network management controller and cached in the memory for use. The network management controller parses the valid data cached in the memory, and then performs the data storage operation. As shown in FIG. 4, it first checks whether the message is status data or configuration data according to the data packet format. If it is status data, check whether it is the basis. Data status, if it is to update the basic state database, if not, continue to check, whether it is the protocol status and alarm monitoring data, and enter the corresponding database after the check.
  • Step 907 The network management server directly logs in to the device for data synchronization, and the process ends.
  • Step 908 The data synchronization fails and the process ends.
  • the process of configuring the device data in the network management system is as follows: the data is configured in the configuration database, and the configuration data is compiled into a data format that can be transmitted on the springboard and recognized by the device collector, for example, the Telnet protocol. The text format is then sent to the device via a springboard.
  • the network management system of this embodiment can implement A external network management to manage B internal network equipment, B internal network management to manage A external network equipment, A external network management to manage B external network equipment, and B external network management to manage external network. Ready. Only all devices need to support the standard Telnet protocol. The network management and devices need to implement encoding and decoding. The goal of managing devices across subnets has been achieved, which solves the problem that the network management is subject to the device environment and improves the ease of use of the network management.
  • the embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the above method.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • this embodiment provides a device management apparatus, which is applied to a network management server side, and includes: a detection module, a login module, and a management module;
  • the detecting module is configured to detect, when the network management server cannot directly log in to the device, whether the device has a springboard that can log in to the device;
  • the login module is configured to log in to the device by using the springboard when the detecting module detects that the device has a springboard that can log in to the device;
  • the management module is configured to perform data interaction with the device through the springboard to implement management of the device.
  • the management module is configured to:
  • the configuration data is sent to the device through the springboard.
  • this embodiment further provides another device management apparatus, which is applied to the device side, and includes: a login module and a data transmission module;
  • the login module is configured to accept login of the network management server through the springboard of the device;
  • the data transmission module is configured to perform data interaction with the network management server through the springboard to implement management of the device by the network management server.
  • the data transmission module is configured to:
  • the device management device of the embodiment when the network management server and the device cannot establish a connection, the device can be connected to the device through the springboard of the device, and the device is managed by using a springboard, and is applicable to management of all devices with the springboard. Since the general equipment has a springboard, the popularity is high. In addition, the device management apparatus according to the embodiment of the present invention does not need to change the equipment much, and only needs to provide a corresponding interface, simple configuration, low maintenance and training cost, and maintenance personnel. The technical requirements are not high, the cost is reduced, and the use is convenient, which further improves the popularity of the program.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • each device/function module/functional unit in the above embodiment When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the network management server cannot be connected to the device, you can use the device's springboard to log in to the device and connect to the device.
  • the device can be used to manage all devices with a springboard. Both have springboards, so the popularity is high; in addition, the above technical solutions do not need to make major changes to the equipment, only the equipment provides corresponding interfaces, the configuration is simple, and the maintenance and training costs are low, and the technical requirements for maintenance personnel are not high, and the reduction is low. The cost and ease of use further enhance the popularity of the program.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种设备管理方法和装置。所述设备管理方法包括：在网管服务器无法直接登录设备时，检测所述设备是否存在可登录所述设备的跳板（101）；若存在，所述网管服务器通过所述跳板登录到所述设备上（102）；所述网管服务器通过所述跳板与所述设备进行数据交互实现对所述设备管理（103）。上述技术方案能够解决在网管服务端和设备无法建立用户数据包协议（UDP）连接的情况下，管理设备方案存在配置复杂、成本较高、使用不便以及普及程度低的技术问题。

Description

一种设备管理方法和装置 技术领域
本文涉及但不限于网管技术领域，尤其涉及一种设备管理方法和装置。
背景技术
管理设备目前一般使用简单网络管理(Simple Network Management Protocol，SNMP)协议，但是SNMP协议必须要网管服务器和设备可达，即有用户数据报协议(User Datagram Protocol，UDP)连接，才能读取或者改写设备数据。此外，设备需要维护管理信息数据库(Management Information Base，MIB)，网管服务器同时也需要维护自己的数据库，需要变更时，两者都需要改动，工作量巨大。
然而，当网管服务器和设备不可达即无法建立UDP连接时，使用SNMP协议便无用处，无法实现对设备的管理。因此，需要一种新方案来管理非直连的网元。
针对网管服务器和设备无法建立UDP连接导致无法使用SNMP协议对设备管理的情况下，目前一般采用其他协议来实现对网络设备管理，例如使用路由协议(开放式最短路径优先协议OSPF、中间系统到中间系统协议ISIS等)创建全互通的路由网络使网管服务器可达，从而管理全网设备，然而这种方式需要创建独立的网络管理域，存在着配置复杂，维护及培训成本高，对维护人员的技术要求高的缺点，间接降低了网管的普及程度；又例如使用基于虚拟专用网络(VPN)的网络管理协议使网管服务器管理全网设备，这种方式需要创建VPN环境，缺点是只能管理同一私网的设备，如需管理公网设备，还需要把公网路由发布到私网上，同样也存在配置困难的问题，需要设备支持VPN协议，普及程度不高，使用不方便。
因此，相关技术中，在网管服务端和设备无法建立UDP连接的情况下，管理设备方案存在配置复杂、成本较高、使用不便以及普及程度低的技术问 题。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种设备管理方法和装置，能够解决如何避免在网管服务端和设备无法建立UDP连接的情况下，管理设备方案存在配置复杂、成本较高、使用不便以及普及程度低的技术问题。
本发明实施例提供一种设备管理方法，包括如下步骤：
在网管服务器无法直接登录设备时，网管服务器检测所述设备是否存在可登录所述设备的跳板；
若存在，所述网管服务器通过所述跳板登录到所述设备上；
所述网管服务器通过所述跳板与所述设备进行数据交互实现对所述设备管理。
可选地，所述网管服务器通过所述跳板与所述设备进行数据交互实现对所述设备管理的步骤包括：
所述网管服务器通过所述跳板将数据同步请求发送给设备；
所述网管服务器通过所述跳板接收所述设备响应所述数据同步请求返回的设备数据；
或者
所述网管服务器生成所述设备的配置数据；
所述网管服务器通过所述跳板将所述配置数据发送给所述设备。
可选地，所述网管服务器通过所述跳板接收所述设备响应所述数据同步请求返回的设备数据的步骤包括：
所述网管服务器接收所述跳板转发的所述设备响应所述数据同步请求返回的数据报文；
所述网管服务器对所述数据报文进行解析得到设备数据。
可选地，所述网管服务器接收所述跳板转发的所述设备响应所述数据同步请求返回的数据报文的步骤包括：
所述网管服务器通过Telnet协议(远程终端协议)接收所述跳板转发的所述设备响应所述数据同步请求返回的Telnet协议数据报文。
可选地，在得到设备数据之后，所述设备管理方法还包括：
所述网管服务器根据所述设备数据的类型将所述设备数据存储至对应的数据库中。
可选地，所述网管服务器通过所述跳板将所述配置数据发送给所述设备的步骤包括：
所述网管服务器将所述配置数据处理成可在所述跳板上传输且被所述设备识别的数据报文；
所述网管服务器将所述数据报文发送给所述跳板由所述跳板将配置数据转发给所述设备。
可选地，所述网管服务器将所述配置数据处理成可在所述跳板上传输且被所述设备识别的数据报文的步骤包括：
当所述网管服务器、所述设备和所述跳板均支持Telnet协议时，所述网管服务器将所述配置数据封装成Telnet协议数据报文。
本发明实施例还提供了另一种设备管理方法，包括如下步骤：
设备接受网管服务器通过所述设备的跳板的登录；
所述设备通过所述跳板与网管服务器进行数据交互以实现网管服务器对所述设备的管理。
可选地，所述设备通过所述跳板与网管服务器进行数据交互的步骤包括：
设备通过其跳板接收到网管服务器发送的数据同步请求；
所述设备响应所述数据同步请求将对应的设备数据通过所述跳板发送给所述网管服务器；
或者
所述设备通过所述跳板接收所述网管服务器发送的配置数据。
可选地，所述设备响应所述数据同步请求将对应的设备数据通过所述跳板发送给所述网管服务器的步骤包括：
所述设备响应所述数据同步请求获取对应的设备数据；
所述设备将所述设备数据处理成可在所述跳板上传输且被所述网管服务器识别的数据报文；
所述设备将处理后的数据报文通过所述跳板发送给所述网管服务器。
可选地，所述设备将所述设备数据处理成可在所述跳板上传输且被所述网管服务器识别的数据报文的步骤包括：
当所述跳板、所述设备以及所述网管服务器均支持Telnet协议时，所述设备将所述设备数据封装成Telnet协议数据报文；
所述设备通过Telnet协议将所述数据报文发送给所述跳板，由所述跳板通过Telnet协议将所述数据报文转发给所述网管服务器。
可选地，所述数据报文包括：报文内容类型的标识信息和报文体，所述报文体携带所述设备数据以及指示报文的协议类型。
可选地，所述设备通过所述跳板接收所述网管服务器发送的配置数据的步骤包括：
所述设备通过Telnet协议接收所述跳板转发的所述网管服务器发送的Telnet协议数据报文；
所述设备对所述Telnet协议数据报文进行解析得到配置数据。
本发明实施例还提供了一种设备管理装置，应用于网管服务器，包括：检测模块、登录模块和管理模块；
所述检测模块，设置为在网管服务器无法直接登录设备时，检测所述设备是否存在可登录所述设备的跳板；
所述登录模块，设置为在检测模块检测到设备存在可登录所述设备的跳板时，通过所述跳板登录到所述设备上；
所述管理模块，设置为通过所述跳板与所述设备进行数据交互实现对所述设备管理。
可选地，所述管理模块，是设置为：
通过所述跳板将数据同步请求发送给设备；
通过所述跳板接收所述设备响应所述数据同步请求返回的设备数据；
或者
生成所述设备的配置数据；
通过所述跳板将所述配置数据发送给所述设备。
本发明实施例还提供了另一种设备管理装置，应用于设备，包括：登录模块和数据传输模块；
所述登录模块，设置为接受网管服务器通过所述设备的跳板的登录；
所述数据传输模块，设置为通过所述跳板与网管服务器进行数据交互以实现网管服务器对所述设备的管理。
可选地，所述数据传输模块，是设置为：
通过设备的跳板接收到网管服务器发送的数据同步请求；
响应所述数据同步请求将对应的设备数据通过所述跳板发送给所述网管服务器；
或者
通过所述跳板接收所述网管服务器发送的配置数据。
本发明实施例还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行上述的方法。
本发明实施例的有益效果是：
本发明实施例的设备管理方法包括：在网管服务器无法直接登录设备时，检测所述设备是否存在可登录所述设备的跳板；若存在，所述网管服务器通过所述跳板登录到所述设备上；所述网管服务器通过所述跳板与所述设备进行数据交互实现对所述设备管理；本发明实施例的设备管理方法在网管服务 器与设备无法建立连接情况下，可以通过设备的跳板来登录设备与设备连接，通过跳板来对设备进行管理，适用于对所有具有跳板的设备的管理，而由于目前一般设备都具有跳板，因此普及程度高；另外采用本发明实施例的设备管理方法无需对设备变更很多只需设备提供相应的接口、配置简单，并且维护及培训成本低、对维护人员的技术要求也不高降低了成本且使用方便，进一步提升了方案普及程度。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为本发明实施例一提供的一种设备管理方法的流程示意图；
图2为本发明实施例一提供的另一种设备管理方法的流程示意图；
图3为本发明实施例一提供的一种数据同步的流程示意图；
图4为本发明实施例一提供的一种入库操作的流程示意图；
图5为本发明实施例一提供的一种数据报文的格式的示意图；
图6为本发明实施例一提供的一种解码报文的流程示意图；
图7为本发明实施例一提供的一种配置设备数据的流程示意图；
图8为本发明实施例二提供的一种设备管理方法的流程示意图；
图9为本发明实施例三提供一种数据同步的流程示意图；
图10为本发明实施例四提供的一种设备管理装置的结构示意图；
图11为本发明实施例四提供的另一种设备管理装置的结构示意图。
本发明的实施方式
下面通过具体实施方式结合附图对本发明作进一步详细说明。
实施例一：
在网管服务端和设备无法建立UDP连接的情况下，管理设备方案存在配置复杂、成本较高、使用不便以及普及程度低的技术问题；为了解决该技术问题，本实施例提供了一种设备管理方法，如图1所示，包括如下步骤：
步骤101：在网管服务器无法直接登录设备时，网管服务器检测所述设备是否存在可登录所述设备的跳板，若是，则执行步骤102，若否，则执行步骤104。
可选地，在网管服务器需要对设备进行管理时，网管服务器首先检测需要管理的设备是否可以直接登录，如果可直接登录，网管服务器直接登录该设备进行管理，如果设备不可直接登录即网管服务器无法直接登录设备，则进一步检测设备是否存在可登录所述设备的跳板。
本实施例中设备的跳板可以为设备的一级跳板、二级跳板或者多级跳板。
步骤102：所述网管服务器通过所述跳板登录到所述设备上。
本实施例中网管服务器通过跳板登录到设备包括：网管服务器通过跳板与设备建立连接，使得网管服务器和设备间接可达。本实施例中网管服务器可以通过一级，二级或者多级跳板远程登陆到设备上。
步骤103：所述网管服务器通过所述跳板与所述设备进行数据交互实现对所述设备管理，流程结束。
本实施例中对设备管理可以包括：数据同步或者数据配置；当然还可以是对设备进行其他的管理。
可选地，网管服务器与设备数据同步的过程可以包括：
网管服务器通过所述跳板将数据同步请求发送给设备；
网管服务器通过所述跳板接收所述设备响应所述数据同步请求返回的设备数据。
本实施例中网管服务器将数据同步请求发送给设备的跳板，然后由设备的跳板将数据同步请求转发给设备，设备在接收到数据同步请求后将对应的设备数据发送给跳板，由跳板转发给网管服务器。
在实际应用中，设备响应数据同步请求获取对应的设备数据，然后将设备数据处理成数据报文发送给跳板(例如对设备数据进行编码将其封装成数据报文)，由跳板转发给网管服务器；此时，本实施例中所述网管服务器通过所述跳板接收所述设备响应所述数据同步请求返回的设备数据的过程可以包括：
所述网管服务器接收所述跳板转发的所述设备响应所述数据同步请求返回的数据报文；
所述网管服务器对所述数据报文进行解析得到设备数据(可选地，网管服务器对数据报文进行解码得到对应的设备数据)。
在本实施例中，当网管服务器、设备和跳板均支持Telnet协议的情况下，设备会将对应的设备数据封装成Telnet协议数据报文；设备通过Telnet协议将该数据报文发送给跳板，然后由跳板通过Telnet协议将该数据报文转发给网管服务器，也即网管服务器通过Telnet协议接收所述跳板转发的所述设备响应所述数据同步请求返回的Telnet协议数据报文。
应当理解的是，本实施例中在网管服务器、设备和跳板均支持其他通讯协议的情况下，设备可以将设备数据封装成对应通讯协议报文，网管服务器通过通讯协议接收跳板转发的符合该通讯协议的报文。
本实施例中网管服务器对设备进行数据配置的过程包括：
所述网管服务器生成所述设备的配置数据；
所述网管服务器通过所述跳板将所述配置数据发送给所述设备。
本实施例中网管服务器在配置数据库中配置对应的配置数据，然后将配置数据发送给跳板，由跳板转发给设备。
可选地，配置数据可以采用数据报文来传输，因此，本实施例中网管服务器通过所述跳板将所述配置数据发送给所述设备的过程包括：
所述网管服务器将所述配置数据处理成可在所述跳板上传输且被所述设备识别的数据报文；
所述网管服务器将所述数据报文发送给所述跳板由所述跳板将配置数据转发给所述设备。
当所述网管服务器、所述设备和所述跳板均支持Telnet协议时，所述网管服务器将所述配置数据处理成可在所述跳板上传输且被所述设备识别的数据报文的过程包括：
所述网管服务器将所述配置数据封装成Telnet协议数据报文。
也即，网管服务器、设备、跳板之间通过相同的通讯协议(例如Telnet协议)进行数据交互。
应当理解的是，在本实施例中网管服务器与设备之间可以采用第一通讯协议交互数据，设备与跳板之间可以采用第二通讯协议交互数据，此时跳板增加通讯协议转换功能，以实现网管服务器对设备的管理；此时网管服务器或者设备在发送数据时，需要将数据封装成对应的协议报文。
步骤104：判定对设备管理失败。
本实施例的设备管理方法在网管服务器与设备无法建立连接情况下，可以通过设备的跳板来登录设备与设备连接，通过跳板来对设备进行管理，适用于对所有具有跳板的设备的管理，而由于目前一般设备都具有跳板，因此普及程度高；另外采用本发明实施例的设备管理方法无需对设备变更很多只需设备提供相应的接口、配置简单，并且维护及培训成本低、对维护人员的技术要求也不高降低了成本且使用方便，进一步提升了方案普及程度。
可选地，应用本实施例的设备管理方法只需要所有设备支持标准的Telnet协议，网管和设备需要实现编码和解码的功能就可以管理设备，以及实现跨网络的设备管理，例如可以实现A外网网管管理B内网的设备，B内网网管管理A外网设备，A外网网管管理B外网设备，B外网网管管理A外网设备达，解决了网管部署中受制于设备环境的问题，提高了网管的易用性。
根据上述的描述，如图2所示，本实施例提供了一种设备管理方法，包括如下步骤：
步骤201：网管服务器检测需要管理的设备是否可以直接登录，如否，则执行步骤202，若是，则执行步骤205。
步骤202：网管服务器检测设备是否存在跳板，若是，则执行步骤203，若否，则执行步骤206；
步骤203：网管服务器检测设备的跳板是否可以远程登录设备，若是，则执行步骤204，若否，则执行步骤206；
步骤204：网管服务器通过跳板远程登录到设备上，且通过跳板与设备进行数据交互实现对设备的管理，流程结束。
可选地，通过跳板与设备进行数据交互实现对设备的管理包括：通过跳板与设备进行数据同步或者通过跳板配置设备。数据同步过程和配置设备的过程可以参考上述的描述。
步骤205：网管服务器直接远程登录到设备上对设备进行管理，流程结束。
步骤206：判定对设备的管理失败，流程结束。
如图3所示，本实施例还提供了一种网管服务器与设备进行数据同步的方法，包括如下步骤：
步骤301：在网管服务器无法直接登录设备时，检测所述设备是否存在可登录所述设备的跳板，若是，则执行步骤302，若否，则执行步骤307。
步骤302：网管服务器通过所述跳板登录到所述设备上。
步骤303：网管服务器通过所述跳板发送数据同步请求至所述设备。
步骤304：网管服务器通过Telnet协议接收所述跳板转发的所述设备响应所述数据同步请求返回的Telnet协议数据报文。
可选地，在设备接收到数据同步请求后进行响应，获取对应的设备数据然后将设备数据封装成网管服务器、跳板和设备均支持Telnet协议数据报文发送给跳板，由跳板将该数据报文转发给网管服务器。
步骤305：网管服务器对Telnet协议数据报文进行解析得到设备数据。
可选地，网管服务器在接收到Telnet协议数据报文后，对该数据报文进行解码获取设备数据。
步骤306：网管服务器存储设备数据，流程结束。
步骤307：判定数据同步失败，流程结束。
在本实施例中网管服务器与设备进行数据同步的情况下，在得到设备数据之后，网管服务器还需要存储设备数据；可以将设备数据存入到对应的数据库，地，可以根据设备数据的类型将其存入到对应的数据库。
在数据同步时，设备反馈的设备数据可以包括：设备的状态数据和/或配置数据；其中状态数据可以包括：基础状态数据、协议状态数据和告警监控 数据，配置数据可以包括：基本配置数据、协议配置数据和维护配置数据。
如图4所示，在网管服务器获取设备反馈的设备数据之后进行入库操作的过程包括：
步骤401：判断设备数据为状态数据还是配置数据，若为配置数据，则执行步骤402，若为状态数据，则执行步骤408。
步骤402：判断配置数据是否基本配置数据，若是，则执行步骤403，若否，则执行步骤404。
步骤403：根据设备数据更新基本配置数据库，流程结束。
步骤404：判断配置数据是否为协议配置数据，若是，则执行步骤405，若否，则执行步骤406。
步骤405：根据设备数据更新协议配置数据库，流程结束。
步骤406：判断配置数据是否为维护配置数据，若是，则执行步骤407，若否，则执行步骤414。
步骤407：根据设备数据更新维护数据库，流程结束。
步骤408：判断状态数据是否基础状态数据，若是，则执行步骤409，若否，则执行步骤410。
步骤409：根据设备数据更新基础状态数据库，流程结束。
步骤410：判断状态数据是否为协议状态数据，若是，则执行步骤411，若否，则执行步骤412。
步骤411：根据设备数据更新协议状态数据库，流程结束。
步骤412：判断状态数据是否为告警监控数据，若是，则执行步骤413，若否，则执行步骤414。
步骤413：根据设备数据更新告警监控数据库，流程结束。
步骤414：判定入库失败，流程结束。
在本实施例中当接收到的设备数据为配置数据时，判断配置数据是否为基本配置数据、协议配置数据或维护数据配置的顺序可以根据实际情况来设定，不仅限于图4所示的判断顺序；同样在接收到的设备数据为状态数据时， 判断状态数据是否为基础状态数据、协议状态数据或者告警监控数据的顺序可以根据实际情况来设定不仅限于图4所示的判断顺序。
在设备构造数据报文时可以区分设备数据的类型(例如区分设备数据是配置数据还是状态数据)和协议的类型；可选地，可以通过报文内容类型的标识信息和报文体进行区分，所述报文体携带所述设备数据以及指示报文的协议类型。如图5所示为Telnet协议数据报文的格式，该数据报文包括：报文开始标记位、报文头(用于标记报文携带的设备数据是状态数据还是配置数据)、报文体1……报文体n(报文体定义协议类型)、报文结束标记位(即表示报文传输完毕)。网管服务器在接收到如图5所述格式的报文之后，对数据报文进行解码的过程如图6所示：
步骤601：判断是否接收到报文开始标记位，若是，执行步骤602，若否，执行步骤608；
步骤602：判断是否接收到报文头标记，若是，执行步骤603，若否，则执行步骤609。
步骤603：解码报文头标记判断报文携带的设备数据是状态数据还是配置数据，若为状态数据，则执行步骤604，若为配置数据，则执行步骤610。
步骤604：判断是否接收到携带状态数据的报文体，若是，则执行步骤605，若否，则执行步骤609。
步骤605：解码携带状态数据的报文体获取状态数据。
步骤606：判断是否接收到报文尾标记，若是，执行步骤607。
步骤607：将状态数据存入对应的数据库，流程结束。
步骤608：解码失败，流程结束。
步骤609：报错，流程结束。
步骤610：判断是否接收到携带配置数据的报文体，若是，则执行步骤611，若否，则执行步骤609。
步骤611：解码携带配置数据的报文体获取配置数据。
步骤612：判断是否接收到报文尾标记，若是，执行步骤613。
步骤613：将配置数据存入对应的数据库，流程结束。
以上主要介绍的网管服务器与设备数据同步的过程，然而本实施例中网管服务器还可以通过跳板向设备发送配置数据实现配置设备，如图7所示，为一种对设备配置数据的过程，包括：
步骤701：网管服务器生成所述设备的配置数据。
步骤702：所述网管服务器将所述配置数据处理成可在所述跳板上传输且被所述设备识别的数据报文。
当所述网管服务器、所述设备和所述跳板均支持Telnet协议时，所述网管服务器将所述配置数据封装成Telnet协议数据报文。其中数据报文的格式可参考图5。
步骤703：所述网管服务器将所述数据报文发送给所述跳板由所述跳板将配置数据转发给所述设备。
本实施例的设备管理方法只需要使用Telnet协议就可以管理设备，可以实现跨网络的设备管理，该方法具有简单、方便、成本低、普及程度高等优点。
实施例二：
如图8所示，本实施例提供了一种设备管理方法，包括如下步骤：
步骤801：设备接受网管服务器通过所述设备的跳板的登录。
本实施例中设备可以接收网管服务器通过跳板的登录，也即设备通过跳板与网管服务器连接。
步骤802：所述设备通过所述跳板与网管服务器进行数据交互以实现网管服务器对所述设备的管理。
本实施例中对设备的管理包括：数据同步和配置设备数据。步骤802包括：设备通过其跳板接收到网管服务器发送的数据同步请求；
所述设备响应所述数据同步请求将对应的设备数据通过所述跳板发送给所述网管服务器；
或者
设备通过所述跳板接收所述网管服务器发送的配置数据。
本实施例中设备与网管服务器进行数据同步时，设备侧的过程包括：
所述设备响应所述数据同步请求获取对应的设备数据；
所述设备将所述设备数据处理成可在所述跳板上传输且被所述网管服务器识别的数据报文；
所述设备将处理后的数据报文通过所述跳板发送给所述网管服务器。
在本实施例中设备可以实时收集设备的配置信息、协议信息、监控信息等形成一数据库；在接收所到数据同步请求后从该数据库中获取对应的设备数据反馈给网管服务器。
可选地，当所述跳板、所述设备以及所述网管服务器均支持Telnet协议时，所述设备将所述设备数据处理成可在所述跳板上传输且被所述网管服务器识别的数据报文的过程包括：
所述设备将所述设备数据封装成Telnet协议数据报文；
所述设备通过Telnet协议将所述数据报文发送给所述跳板，由所述跳板通过Telnet协议将所述数据报文转发给所述网管服务器。
此时设备实时收集信息形成的数据库可以为Telnet信息库。
可选地，本实施例中设备封装的数据报文可以包括：报文内容类型的标识信息和报文体，所述报文体携带所述设备数据以及指示报文的协议类型。报文的具体格式可参考实施例一中的图5。
在网管服务器配置设备的过程中，设备侧的过程包括：
设备接收所述跳板转发的网管服务器发送的数据报文；
设备对数据报文进行解析获取配置数据。
本实施例中网管服务器可以通过跳板向设备发送配置数据以实现对设备的配置，可选地，网管服务器可以将配置数据封装成数据报文发送给跳板由跳板转发给设备，设备接收到数据报文后进行解码获取配置数据。网管侧封装的数据报文可以包括：报文内容类型的标识信息和报文体，所述报文体携 带所述设备数据以及指示报文的协议类型。报文的具体格式可参考实施例一中的图5。
当所述跳板、所述设备以及所述网管服务器均支持Telnet协议时，网管服务器会将配置数据封装成Telnet协议数据报文发送给跳板，由跳板通过Telnet协议将数据报文转发给设备，所述设备通过Telnet协议接收所述跳板转发的所述网管服务器发送的Telnet协议数据报文，然后对所述Telnet协议数据报文进行解析得到配置数据。
本实施例的设备管理方法在网管服务器与设备无法建立连接情况下，可以通过设备的跳板来登录设备与设备连接，通过跳板来对设备进行管理，适用于对所有具有跳板的设备的管理，而由于目前一般设备都具有跳板，因此普及程度高；另外采用本发明实施例的设备管理方法无需对设备变更很多只需设备提供相应的接口、配置简单，并且维护及培训成本低、对维护人员的技术要求也不高降低了成本且使用方便，进一步提升了方案普及程度。
进一步地，应用本实施例的设备管理方法只需要所有设备支持标准的Telnet协议，网管和设备需要实现编码和解码的功能就可以管理设备，以及实现跨网络的设备管理。
实施例三：
本实施例提供了一种网管系统，包括：网管服务器、被管理的设备和设备的跳板，其中网管服务器、设备、跳板均支持Telnet协议；该网管系统进行数据同步的过程包括，如图9所示：
步骤901：设备收集配置信息、监控信息、协议信息等网管需要的信息，存储到Telnet信息库。
步骤902：网管服务器检测是否能直接登录设备，若否，则执行步骤903，若是，则执行步骤907。
步骤903：网管服务器检测设备是否存在可登录其自身的跳板，若是，则执行步骤904，若否，执行步骤908。
可选的地，服务器中网管控制器先检查设备是否可以直接登陆，如果可 以直接登陆，直接进行数据同步请求，如果无法直接登陆，检查是否存在跳板，通过一级，二级或者多级跳板远程登陆到设备上，再进行数据同步。
步骤904：网管服务器通过所述跳板登录到设备，并通过跳板将数据同步请求发送给设备。
步骤905:设备根据数据同步请求从Telnet信息库提取对应的信息，并将提取信息编码为适合通过Telnet协议传输的数据报文，将数据报文通过跳板发送给网管服务器。
可选的地，设备编码器把Telnet信息库信息编码为适合通过Telnet传输的数据报文。设备编码器构造传输数据报文，数据报文在构造时需要区分协议单元和分类信息(如区分配置信息或者状态信息)，每种协议类型分类标记，形成数据字典，便于后期扩展，最终编码成为可以在Telnet上传输的数据报文格式。
步骤906：网管服务器接收到数据报文后，解码数据报文获取对应信息，并将获取的信息存储到对应的数据库中，流程结束。
网管解码器解码数据报文，报文解码成功后通过网管控制器解析报文的每项参数，缓存到内存中待用。网管控制器解析缓存到内存中的有效数据，再进行数据入库动作，如图4所示，根据数据报文格式先检查报文是状态数据还是配置数据，如果是状态数据，检查是否是基础数据状态，如果是更新基础状态数据库，如果不是，继续进行检查，是否是协议状态和告警监控数据，检查完毕后进入相应的数据库中。
步骤907：网管服务器直接登录设备进行数据同步，流程结束。
步骤908：数据同步失败，流程结束。
本实施例中网管系统配置设备数据的过程为：在配置数据库中完成数据的配置，将配置数据通过网管编码器编译成可以在跳板上传输并被设备采集器识别的数据格式，例如Telnet协议报文格式，然后将数据报文通过跳板发送给设备。
本实施例的网管系统可以实现A外网网管管理B内网的设备，B内网网管管理A外网设备，A外网网管管理B外网设备，B外网网管管理A外网设 备。只需要所有设备支持标准的Telnet协议，网管和设备需要实现编码和解码的功能。达成了跨子网管理设备的目的，解决了网管部署中受制于设备环境的问题，提高了网管的易用性。
本发明实施例还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行上述的方法。
实施例四：
如图10所示，本实施例提供了一种设备管理装置，应用于网管服务器侧，包括：检测模块、登录模块和管理模块；
所述检测模块，设置为在网管服务器无法直接登录设备时，检测所述设备是否存在可登录所述设备的跳板；
所述登录模块，设置为在检测模块检测到设备存在可登录所述设备的跳板时，通过所述跳板登录到所述设备上；
所述管理模块，设置为通过所述跳板与所述设备进行数据交互实现对所述设备管理。
可选地，所述管理模块，是设置为：
通过所述跳板将数据同步请求发送给设备；
通过所述跳板接收所述设备响应所述数据同步请求返回的设备数据；
或者
生成所述设备的配置数据；
通过所述跳板将所述配置数据发送给所述设备。
如图11所示，本实施例还提供了另一种设备管理装置，应用于设备侧，包括：登录模块和数据传输模块；
所述登录模块，设置为接受网管服务器通过所述设备的跳板的登录；
所述数据传输模块，设置为通过所述跳板与网管服务器进行数据交互以实现网管服务器对所述设备的管理。
可选地，所述数据传输模块，是设置为：
通过设备的跳板接收到网管服务器发送的数据同步请求；
响应所述数据同步请求将对应的设备数据通过所述跳板发送给所述网管服务器；
或者
通过所述跳板接收所述网管服务器发送的配置数据。
本实施例的设备管理装置在网管服务器与设备无法建立连接情况下，可以通过设备的跳板来登录设备与设备连接，通过跳板来对设备进行管理，适用于对所有具有跳板的设备的管理，而由于目前一般设备都具有跳板，因此普及程度高；另外采用本发明实施例的设备管理装置无需对设备变更很多只需设备提供相应的接口、配置简单，并且维护及培训成本低、对维护人员的技术要求也不高降低了成本且使用方便，进一步提升了方案普及程度。
以上内容是结合具体的实施方式对本发明所作的进一步详细说明，不能认定本发明的具体实施只局限于这些说明。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的各装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的各装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。 上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
上述技术方案在网管服务器与设备无法建立连接情况下，可以通过设备的跳板来登录设备与设备连接，通过跳板来对设备进行管理，适用于对所有具有跳板的设备的管理，而由于目前一般设备都具有跳板，因此普及程度高；另外上述技术方案无需对设备进行较大变更，只需设备提供相应的接口、配置简单，并且维护及培训成本低、对维护人员的技术要求也不高，降低了成本且使用方便，进一步提升了方案普及程度。

Claims (21)

  1. 一种设备管理方法，包括如下步骤：
    在网管服务器无法直接登录设备时，网管服务器检测所述设备是否存在可登录所述设备的跳板；
    若存在，所述网管服务器通过所述跳板登录到所述设备上；
    所述网管服务器通过所述跳板与所述设备进行数据交互实现对所述设备管理。
  2. 如权利要求1所述的设备管理方法，其中，所述网管服务器通过所述跳板与所述设备进行数据交互实现对所述设备管理的步骤包括：
    所述网管服务器通过所述跳板将数据同步请求发送给设备；
    所述网管服务器通过所述跳板接收所述设备响应所述数据同步请求返回的设备数据。
  3. 如权利要求1所述的设备管理方法，其中，所述网管服务器通过所述跳板与所述设备进行数据交互实现对所述设备管理的步骤包括：
    所述网管服务器生成所述设备的配置数据；
    所述网管服务器通过所述跳板将所述配置数据发送给所述设备。
  4. 如权利要求2所述的设备管理方法，其中，所述网管服务器通过所述跳板接收所述设备响应所述数据同步请求返回的设备数据的步骤包括：
    所述网管服务器接收所述跳板转发的所述设备响应所述数据同步请求返回的数据报文；
    所述网管服务器对所述数据报文进行解析得到设备数据。
  5. 如权利要求4所述的设备管理方法，其中，所述网管服务器接收所述跳板转发的所述设备响应所述数据同步请求返回的数据报文的步骤包括：
    所述网管服务器通过Telnet协议接收所述跳板转发的所述设备响应所述数据同步请求返回的Telnet协议数据报文。
  6. 如权利要求4所述的设备管理方法，所述设备管理方法还包括：
    在得到设备数据之后，所述网管服务器根据所述设备数据的类型将所述设备数据存储至对应的数据库中。
  7. 如权利要求3所述的设备管理方法，其中，所述网管服务器通过所述跳板将所述配置数据发送给所述设备的步骤包括：
    所述网管服务器将所述配置数据处理成可在所述跳板上传输且被所述设备识别的数据报文；
    所述网管服务器将所述数据报文发送给所述跳板由所述跳板将配置数据转发给所述设备。
  8. 如权利要求7所述的设备管理方法，其中，所述网管服务器将所述配置数据处理成可在所述跳板上传输且被所述设备识别的数据报文的步骤包括：
    当所述网管服务器、所述设备和所述跳板均支持Telnet协议时，所述网管服务器将所述配置数据封装成Telnet协议数据报文。
  9. 一种设备管理方法，包括如下步骤：
    设备接受网管服务器通过所述设备的跳板的登录；
    所述设备通过所述跳板与网管服务器进行数据交互以实现网管服务器对所述设备的管理。
  10. 如权利要求9所述的设备管理方法，其中，所述设备通过所述跳板与网管服务器进行数据交互的步骤包括：
    设备通过其跳板接收到网管服务器发送的数据同步请求；
    所述设备响应所述数据同步请求，将对应的设备数据通过所述跳板发送给所述网管服务器。
  11. 如权利要求9所述的设备管理方法，其中，所述设备通过所述跳板与网管服务器进行数据交互的步骤包括：
    所述设备通过所述跳板接收所述网管服务器发送的配置数据。
  12. 如权利要求10所述的设备管理方法，其中，所述设备响应所述数据同步请求将对应的设备数据通过所述跳板发送给所述网管服务器的步骤包 括：
    所述设备响应所述数据同步请求获取对应的设备数据；
    所述设备将所述设备数据处理成可在所述跳板上传输且被所述网管服务器识别的数据报文；
    所述设备将处理后的数据报文通过所述跳板发送给所述网管服务器。
  13. 如权利要求12所述的设备管理方法，其中，所述设备将所述设备数据处理成可在所述跳板上传输且被所述网管服务器识别的数据报文的步骤包括：
    当所述跳板、所述设备以及所述网管服务器均支持Telnet协议时，所述设备将所述设备数据封装成Telnet协议数据报文；
    所述设备通过Telnet协议将所述数据报文发送给所述跳板，由所述跳板通过Telnet协议将所述数据报文转发给所述网管服务器。
  14. 如权利要求12或13所述的设备管理方法，其中，所述数据报文包括：
    报文内容类型的标识信息和报文体，所述报文体携带所述设备数据以及指示报文的协议类型。
  15. 如权利要求11所述的设备管理方法，其中，所述设备通过所述跳板接收所述网管服务器发送的配置数据的步骤包括：
    所述设备通过Telnet协议接收所述跳板转发的所述网管服务器发送的Telnet协议数据报文；
    所述设备对所述Telnet协议数据报文进行解析得到配置数据。
  16. 一种应用于网管服务器的设备管理装置，包括：检测模块、登录模块和管理模块；
    所述检测模块，设置为在网管服务器无法直接登录设备时，检测所述设备是否存在可登录所述设备的跳板；
    所述登录模块，设置为在检测模块检测到设备存在可登录所述设备的跳板时，通过所述跳板登录到所述设备上；
    所述管理模块，设置为通过所述跳板与所述设备进行数据交互实现对所述设备管理。
  17. 如权利要求16所述的设备管理装置，其中，所述管理模块，是设置为：
    通过所述跳板将数据同步请求发送给设备；
    通过所述跳板接收所述设备响应所述数据同步请求返回的设备数据；
    或者
    生成所述设备的配置数据；
    通过所述跳板将所述配置数据发送给所述设备。
  18. 一种应用于设备的设备管理装置，包括：登录模块和数据传输模块；
    所述登录模块，设置为接受网管服务器通过所述设备的跳板的登录；
    所述数据传输模块，设置为通过所述跳板与网管服务器进行数据交互以实现网管服务器对所述设备的管理。
  19. 如权利要求18所述的设备管理装置，所述数据传输模块，是设置为：
    通过设备的跳板接收到网管服务器发送的数据同步请求；
    响应所述数据同步请求，将对应的设备数据通过所述跳板发送给所述网管服务器；
    或者
    通过所述跳板接收所述网管服务器发送的配置数据。
  20. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1～8中任一项所述的方法。
  21. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求9～15中任一项所述的方法。
PCT/CN2015/092200 2015-05-20 2015-10-19 一种设备管理方法和装置 WO2016184025A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510260210.9 2015-05-20
CN201510260210.9A CN106301827A (zh) 2015-05-20 2015-05-20 一种设备管理方法和装置

Publications (1)

Publication Number Publication Date
WO2016184025A1 true WO2016184025A1 (zh) 2016-11-24

Family

ID=57319251

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/092200 WO2016184025A1 (zh) 2015-05-20 2015-10-19 一种设备管理方法和装置

Country Status (2)

Country Link
CN (1) CN106301827A (zh)
WO (1) WO2016184025A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113794584A (zh) * 2021-08-15 2021-12-14 新华三信息安全技术有限公司 一种网络管理方法及设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108259229B (zh) * 2017-12-25 2021-03-23 新华三技术有限公司 一种设备管理方法、装置及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030140132A1 (en) * 2002-01-22 2003-07-24 Yves-Andre Champagne Method and apparatus for updating network device configuration information in a network management system
CN102215133A (zh) * 2011-06-21 2011-10-12 德讯科技股份有限公司 基于rdp远程协议跳板机审计数据定位回放系统及方法
CN102413000A (zh) * 2011-12-23 2012-04-11 华为数字技术有限公司 客户端上线的方法、dhcp服务器及网管系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030140132A1 (en) * 2002-01-22 2003-07-24 Yves-Andre Champagne Method and apparatus for updating network device configuration information in a network management system
CN102215133A (zh) * 2011-06-21 2011-10-12 德讯科技股份有限公司 基于rdp远程协议跳板机审计数据定位回放系统及方法
CN102413000A (zh) * 2011-12-23 2012-04-11 华为数字技术有限公司 客户端上线的方法、dhcp服务器及网管系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113794584A (zh) * 2021-08-15 2021-12-14 新华三信息安全技术有限公司 一种网络管理方法及设备
CN113794584B (zh) * 2021-08-15 2023-04-14 新华三信息安全技术有限公司 一种网络管理方法及设备

Also Published As

Publication number Publication date
CN106301827A (zh) 2017-01-04

Similar Documents

Publication Publication Date Title
US20170244792A1 (en) Power-Line Carrier Terminal Control Apparatus, System, and Method
CN110247784B (zh) 确定网络拓扑结构的方法和装置
CN105207853B (zh) 一种局域网监控管理方法
WO2020135575A1 (zh) 一种获取网络拓扑的系统、方法和服务器
US20230247388A1 (en) Communication system, method and device for miniature intelligent sensor
CN111083161A (zh) 数据传输的处理方法及装置、物联网设备
EP2262185A1 (en) Method and system for forwarding data among private networks
CN108964962B (zh) 一种控制视联网终端的方法和系统
CN111490893B (zh) 一种网络转发模型的建立方法、装置及系统
CN104639385B (zh) 检测l2vpn网络用户侧接口连通性的方法及设备
WO2018010616A1 (zh) 基于链路层的网络管理
US20160087907A1 (en) Communication device, communication system, and communication method
WO2014000698A1 (zh) 基于ip层的网络拓扑识别方法和设备
WO2015196636A1 (zh) 一种报文采集方法、系统、网络设备及网管中心
WO2016044990A1 (zh) 网络拓扑确定方法和装置、集中式网络状态信息存储设备
KR102547701B1 (ko) 네트워크 토폴로지 발견 방법, 디바이스, 및 시스템
US20140301226A1 (en) Apparatus and method for network monitoring and packet inspection
WO2016184025A1 (zh) 一种设备管理方法和装置
US9948497B2 (en) System for and method of automatically discovering and configuring NIDs
US8972543B1 (en) Managing clients utilizing reverse transactions
US20150261875A1 (en) HTML Network Service Tags Used with Web Browsers for Controlling Network Elements
CN100484101C (zh) 一种以太网传输IPv6报文方法、系统与装置
WO2015070763A1 (zh) X2接口的自建立方法及装置
WO2017005118A1 (zh) 维持通信连接的方法、装置、终端及服务器
WO2016070679A1 (zh) 用于同步网络状态的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15892403

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15892403

Country of ref document: EP

Kind code of ref document: A1