WO2016202013A1 - 日志获取方法和装置、以及网管服务器 - Google Patents

日志获取方法和装置、以及网管服务器 Download PDF

Info

Publication number
WO2016202013A1
WO2016202013A1 PCT/CN2016/075664 CN2016075664W WO2016202013A1 WO 2016202013 A1 WO2016202013 A1 WO 2016202013A1 CN 2016075664 W CN2016075664 W CN 2016075664W WO 2016202013 A1 WO2016202013 A1 WO 2016202013A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
log
handheld terminal
port
management server
Prior art date
Application number
PCT/CN2016/075664
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 WO2016202013A1 publication Critical patent/WO2016202013A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5046Resolving address allocation conflicts; Testing of addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications

Definitions

  • This document relates to, but is not limited to, the field of communications, and more particularly to a log acquisition method and apparatus, and a network management server.
  • the O&M personnel can collect the logs of the device and analyze the logs to locate the problem of the device and recover the fault for the location problem.
  • the NMS server When a communication failure occurs on the device, the NMS server cannot obtain logs of the device through network communication with the device. The O&M personnel must obtain logs from the site.
  • the operation and maintenance personnel When connecting a portable computer and a device, the operation and maintenance personnel need to have a certain understanding of the device, and can select a suitable port for communication. If the operation and maintenance personnel do not have enough understanding of the device, the log of the faulty device may not be obtained quickly. Extend the time for troubleshooting.
  • the operation and maintenance personnel need to manually query the IP address list on the network management server, and set an IP address that does not conflict with the existing IP address for the faulty device according to the IP address list, so that the faulty device can pass the new device. Set the IP address to communicate with the laptop.
  • the O&M personnel can set the IP address of the faulty device based on experience. It is easy for the set IP address to conflict with the existing IP address due to the negligence of the operation and maintenance personnel, which may cause a secondary fault.
  • the operation and maintenance personnel need to have a certain understanding of the faulty equipment, and the operation and maintenance personnel need to set a suitable IP address for the faulty equipment.
  • the requirements for the operation and maintenance personnel are high, and it is easy to operate and maintain.
  • the difference in capabilities between personnel causes the log to be acquired for too long.
  • the operation and maintenance personnel need to carry the portable computer with them, which also increases the labor intensity of the operation and maintenance personnel.
  • the embodiment of the invention provides a log obtaining method and device, and a network management server, which can easily and quickly obtain logs of the faulty device and reduce the labor intensity of the operation and maintenance personnel.
  • the embodiment of the present invention provides a log obtaining method, where the log obtaining method includes:
  • the handheld terminal acquires identity ID information corresponding to the device
  • the handheld terminal obtains the rack map data corresponding to the device from the network management server according to the ID information corresponding to the device; wherein the rack map data includes port information corresponding to the device;
  • the handheld terminal selects a port for connecting according to the rack map data, and obtains an IP address corresponding to the port from the network management server according to the selected port;
  • the handheld terminal establishes a communication connection with the device according to the IP address, and acquires a log corresponding to the device.
  • the log obtaining method further includes:
  • the handheld terminal sends the obtained log to the network management server.
  • the identity ID information corresponding to the acquiring device includes:
  • the ID information corresponding to the device is obtained from the two-dimensional code data.
  • the obtaining the IP address corresponding to the port from the network management server according to the selected port includes:
  • the handheld terminal selects one of the ports according to the user's selection, and sends the corresponding port number to the gateway server;
  • the network management server determines, according to the port number, whether the corresponding port can be used for management, and when the corresponding port can be used for management, generates an IP address that does not conflict with the existing address, and sends the IP address to the handheld terminal;
  • the handheld terminal receives the IP address sent by the network management server.
  • the establishing a communication connection with the device according to the IP address includes:
  • the log corresponding to the acquiring device includes:
  • the handheld terminal acquires a time period and a type corresponding to the log that the user needs to obtain, and obtains a corresponding log from the device according to the input time period and type.
  • the embodiment of the invention further provides a log obtaining method, the method comprising:
  • the network management server receives the ID information corresponding to the device sent by the handheld terminal, obtains the corresponding rack map data according to the ID information, and sends the rack map data to the handheld terminal.
  • the rack map data includes the port corresponding to the device. information;
  • the network management server receives the port number sent by the handheld terminal, generates a corresponding IP address, and sends the generated IP address to the handheld terminal.
  • the log obtaining method further includes:
  • the network management server receives a log of the device sent by the handheld terminal.
  • the network management server receives the port number sent by the handheld terminal, and generates a corresponding IP address, including:
  • the network management server determines, according to the port number, whether the corresponding port can be used for management, and when the corresponding port can be used for management, generates an IP address that does not conflict with the existing address.
  • An embodiment of the present invention further provides a device fault diagnosis apparatus, which is disposed on a handheld terminal, where the device fault diagnosis apparatus includes:
  • An ID obtaining unit is configured to obtain identity ID information corresponding to the device
  • the rack map obtaining unit is configured to obtain the rack map data corresponding to the device from the network management server according to the ID information corresponding to the device, where the rack map data includes port information corresponding to the device;
  • An IP address obtaining unit configured to select a port for connection according to rack map data, and Obtain the IP address corresponding to the port from the network management server according to the selected port.
  • the log obtaining unit is configured to establish a communication connection with the device according to the IP address, and obtain a log corresponding to the device.
  • it also includes:
  • the log uploading unit is configured to send the obtained log to the network management server.
  • the ID obtaining unit includes:
  • the two-dimensional code scanning module is configured to scan a two-dimensional code on the device, and obtain two-dimensional code data corresponding to the two-dimensional code;
  • the ID acquisition module is configured to verify whether the format of the two-dimensional code data is correct. When the format of the two-dimensional code is correct, the ID information corresponding to the device is obtained from the two-dimensional code data.
  • the IP address obtaining unit includes:
  • the port sending module is configured to select one of the ports according to the user's selection, and send the corresponding port number to the gateway server;
  • the IP address obtaining module is configured to receive an IP address sent by the network management server.
  • the log obtaining unit includes:
  • the WIFI hotspot establishing module is configured to create a WIFI hotspot according to the IP address and the network connection information configured on the network adapter, so that the network adapter automatically connects to the WIFI hotspot when scanning the WIFI hotspot;
  • the network adapter is connected to the device through a port selected by the handheld terminal.
  • the log obtaining unit further includes:
  • the log obtaining module is configured to obtain a time period and a type corresponding to the log that the user needs to obtain, and obtain a corresponding log from the device according to the input time segment and type.
  • An embodiment of the present invention further provides a network management server, where the network management server includes:
  • the rack map query unit is configured to receive the ID information corresponding to the device sent by the handheld terminal, obtain the corresponding rack map data according to the ID information, and send the rack map data to the handheld terminal; wherein the rack map The data includes port information corresponding to the device;
  • the IP address generating unit is configured to receive the port number sent by the handheld terminal, and generate a corresponding IP address. Address and send the generated IP address to the handheld terminal.
  • it also includes:
  • a log collection unit configured to receive a log of a device sent by the handheld terminal.
  • the IP address generating unit is configured to: determine, according to the port number, whether the corresponding port can be used for management, and generate an IP that does not conflict with the existing address when the corresponding port is used for management. address.
  • 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 technical solution provided by the embodiment of the present invention includes: the handheld terminal acquires the identity ID information corresponding to the device; the handheld terminal acquires the rack image data corresponding to the device from the network management server according to the ID information corresponding to the device;
  • the rack map data includes port information corresponding to the device; the handheld terminal selects a port for connecting according to the rack map data, and obtains an IP address corresponding to the port from the network management server according to the selected port; the handheld terminal is configured according to the The IP address establishes a communication connection with the device, and obtains a log corresponding to the device; the handheld terminal sends the obtained log to the network management server.
  • the operation and maintenance personnel obtain the log of the faulty device through a handheld terminal such as a mobile phone or a tablet computer, and do not need to carry a portable computer with a larger weight, thereby reducing the labor intensity of the operation and maintenance personnel;
  • the handheld terminal obtains the rack map data corresponding to the device from the network management server.
  • the rack map data includes the port information corresponding to the device. Therefore, the operation and maintenance personnel perform network connection according to the port information provided by the rack map data.
  • the communication connection can be quickly completed, so that the log of the device can be quickly obtained, the time for device fault location is reduced, the efficiency of fault recovery is improved, and the capability of the operation and maintenance personnel is reduced. The requirements reduce the difficulty of operation and maintenance work;
  • IP address corresponding to the port through the network management server, so that the selected IP address ensures that it does not conflict with the existing IP, avoids the occurrence of secondary faults, and can obtain the IP address faster and reduce the device fault.
  • the time of positioning, and the requirements for the ability of the operation and maintenance personnel are reduced, and the difficulty of the operation and maintenance work is also reduced.
  • FIG. 1A is a schematic flowchart of a log obtaining method according to an embodiment of the present invention.
  • FIG. 1B is a schematic diagram of device connection in a log obtaining method according to an embodiment of the present invention.
  • 2A is a schematic flowchart of acquiring identity ID information corresponding to a device
  • 2B is a schematic flowchart of obtaining an IP address corresponding to a port from a network management server
  • FIG. 3 is a schematic diagram of an exemplary rack structure diagram according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart diagram of another log obtaining method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of generating an IP address by a network management server
  • FIG. 6 is a schematic structural diagram of a device fault diagnosis apparatus according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a network management server according to an embodiment of the present invention.
  • an embodiment of the present invention provides a log obtaining method, where the log obtaining method includes:
  • Step 110 The handheld terminal acquires identity ID information corresponding to the device.
  • Step 120 The handheld terminal acquires the rack map data corresponding to the device from the network management server according to the ID information corresponding to the device, where the rack map data includes port information corresponding to the device.
  • Step 130 The handheld terminal selects a port for connecting according to the rack map data, and obtains an IP address corresponding to the port from the network management server according to the selected port.
  • Step 140 The handheld terminal establishes a communication connection with the device according to the IP address, and acquires a log corresponding to the device.
  • Step 150 The handheld terminal sends the obtained log to the network management server.
  • the device in the embodiment of the present invention may optionally be a management device.
  • the log obtaining method of the embodiment of the present invention is particularly applicable to the following scenario: the device has been taken out of the network management server, but the device is not completely faulty, and the connection can still be accessed through the direct connection network cable. For example, if the routing configuration is incorrect, the device cannot be accessed; if the device is faulty, the network is faulty; if the device service configuration conflicts, the network is faulty; if the device address is duplicated, the traffic is blocked; if the device gateway is modified, the management fails.
  • the log obtaining method of the embodiment of the present invention can also be used to collect network element log information that is normally connected to the network management system. For devices with normal network management connections, this method can collect logs of devices at a faster rate. And it is conveniently transmitted to the R&D engineer or manufacturer of the network management server or device through the mobile terminal.
  • FIG. 1B is a schematic diagram of device connection in a log obtaining method according to an embodiment of the present invention.
  • the handheld terminal 100 is connected to the network management server 300 through the mobile network 200, and the network management server 300 is connected to the device 400, and the device 400 passes.
  • the network adapter 500 is connected to the handheld terminal 100.
  • the identifier information corresponding to the acquiring device includes:
  • Step 1101 Scan a 2-dimensional bar code on the device, and obtain two-dimensional code data corresponding to the two-dimensional code;
  • step 1102 it is verified whether the format of the two-dimensional code data is correct. Verify that the format of the QR code data is correct, that is, check whether the device ID information can be extracted from the two-dimensional code.
  • Step 1103 When the format of the two-dimensional code is correct, the ID information corresponding to the device is obtained from the two-dimensional code data.
  • step 1104 when the format of the two-dimensional code data is incorrect, the handheld terminal sends an error message to the user and ends.
  • a corresponding two-dimensional code picture is generated according to the device ID, and the two-dimensional code picture is pasted on the device, so that when the operation and maintenance personnel reach the site, the handheld terminal can be scanned.
  • the two-dimensional code used is QR-code, and the format of information storage in the two-dimensional code is as follows:
  • DEVICEINFO ID: device ID information
  • IP device IP address
  • QR code indicates ID.
  • the handheld terminal can obtain the corresponding text data by scanning the two-dimensional code, and obtain the above information stored in the two-dimensional code.
  • the ID information of the device is obtained by scanning the two-dimensional code.
  • the ID information of the device may be pasted on the device, and the operation and maintenance personnel may read the ID information on the device and input the data to the handheld terminal. in.
  • the WIFI hotspot is established by the handheld terminal, and the faulty device is connected to the WIFI hotspot established by the handheld terminal through the network adapter, thereby establishing a communication connection between the handheld terminal and the device.
  • the handheld terminal may obtain the rack image data corresponding to the device from the network management server.
  • the rack image data includes the port information corresponding to the device, and the port information includes the port description, name, rate, and the like.
  • the rack map data further includes a single board panel diagram, and the single board panel diagram includes information about the distribution of ports on the rack.
  • the network management server pre-stores ID information of all devices and corresponding rack map data.
  • the handheld terminal After receiving the rack map data sent by the network management server, the handheld terminal generates a rack structure map according to the rack map data, and displays the rack structure map, so that the user can quickly understand the device when the device is familiar with the device.
  • FIG. 3 which is a schematic diagram of an exemplary rack structure diagram, and shown in FIG. 3, the equipment in the rack diagram includes 4 Port, the QR code next to the port is a two-dimensional code that includes the ID information of the device, and is consistent with the two-dimensional code posted on the device.
  • step 130 from the network management server Obtaining the IP address corresponding to the port includes:
  • Step 1301 The handheld terminal selects one of the ports according to the user's selection, and sends the corresponding port number to the gateway server.
  • Step 1302 The network management server determines, according to the port number, whether the corresponding port can be used for management.
  • step 1303 when the corresponding port is available for management, an IP address that does not conflict with the existing address is generated, and the IP address is sent to the handheld terminal, and step 1305 is performed.
  • Step 1304 When the corresponding port is unavailable for management, the network management server may send an error prompt message to the handheld terminal, and the process ends.
  • the network management server queries whether the port is a management port. If it is a management port, it considers that the corresponding port can be used for management. If it is not a management port, check the IP address or the VLAN to which the device is configured, and determine whether the port is connected. To the management address of the device, if the port can be connected to the management address of the device, the corresponding port can be considered to be managed.
  • the IP address includes a host address and a network address. For example, among the 32-bit IP addresses, the first 24 bits represent the network address, and the last 8 bits represent the host address. If the network addresses of the two terminals are the same, the two terminals are in the same network segment and can communicate with each other. The host addresses are different and no conflict occurs. For example, the IP addresses of the two terminals are 192.168.1.20 and 192.168.1.21, respectively, where the 192.168.1 bit network address and the last 20 and 21 bit host addresses can communicate between the two terminals without conflict.
  • the network management server can add 1 to the host address of the IP address of the faulty device according to the IP address of the faulty device, and verify whether the IP address after adding 1 conflicts with the IP address in the existing network segment. If the IP addresses in the network segment do not conflict, the IP address after the first network segment is sent to the handheld terminal as the generated IP address. If the IP address conflicts with the existing network segment, the IP address continues to be added until the existing IP address is added. The IP address in the network segment does not conflict, and the IP address that does not conflict is sent to the handheld terminal as the generated IP address. In the process of adding 1, if the host address reaches the maximum value, it is judged from 0. If there is still no address that does not conflict after traversing all the addresses of the network segment, an error message is sent to the handheld terminal.
  • the IP address of the faulty device is 192.168.1.20
  • the network management server adds 1 to the host address.
  • Obtaining 192.168.1.21 the network management server verifies that 192.168.1.21 conflicts with the IP address in the existing network segment. If it does not conflict with the IP address in the existing network segment, 192.168.1.21 is sent as the generated IP address. If the handheld terminal conflicts with the IP address in the existing network segment, it continues to increment until it does not conflict with the IP address in the existing network segment.
  • step 1305 the handheld terminal receives the IP address sent by the network management server.
  • step 140 establishing a communication connection with the device according to the IP address includes:
  • the network adapter After the operation and maintenance personnel select the port to be connected through the handheld terminal, the network adapter needs to be plugged into the port, and the network adapter will automatically scan the surrounding WIFI hotspot and the wireless network.
  • the handheld terminal is connected according to the IP address and the network connection configured on the network adapter,
  • the network adapter When the information is created in the WIFI hotspot, the network adapter will automatically connect to the WIFI hotspot created by the handheld terminal.
  • the network connection information refers to the user name and password of the WIFI hotspot, and the user name and password of the WIFI hotspot need to be set on the network adapter, so that the network adapter can realize the automatic connection after the hotspot is generated.
  • a wireless router that supports wireless client mode on the market. It requires at least one wired network interface of RG45 and is configured in client mode, that is, it can actively connect to collect the created WIFI hotspots, and does not route after connection. The function does not work with DHCP.
  • the network adapter can use a wireless router such as the ZTE PW50.
  • the log corresponding to the acquiring device includes:
  • the handheld terminal acquires a time period and a type corresponding to the log that the user needs to obtain, and obtains a corresponding log from the device according to the input time period and type.
  • the user selects the time period and type of the log to be uploaded on the terminal log collection module of the handheld terminal.
  • the time period determines which time period the log is uploaded.
  • the types of logs include: syslog, alarm, running log, operation log, current system process information, current system configuration, current version information, and board information.
  • the handheld terminal can establish an FTP client and copy the log of the file class from the device through the FTP client.
  • the specific uploading log can be determined according to the operation and maintenance database and the type of the device in the handheld terminal.
  • the log may be uploaded to the gateway server according to the user's selection, or the default device, or according to whether other preset conditions are met.
  • 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.
  • Another log obtaining method according to the embodiment of the present invention includes:
  • Step 210 The network management server receives the ID information corresponding to the device sent by the handheld terminal, acquires the corresponding rack map data according to the ID information, and sends the rack map data to the handheld terminal.
  • the rack map data includes the device. Corresponding port information.
  • the network management server pre-stores ID information of all devices in its management scope and its corresponding rack structure diagram.
  • Step 220 The network management server receives the port number sent by the handheld terminal, generates a corresponding IP address, and sends the generated IP address to the handheld terminal.
  • Step 230 The network management server receives a log of the device sent by the handheld terminal.
  • the network management server receives the port number sent by the handheld terminal, and generates a corresponding IP address, including:
  • Step 221 The network management server determines, according to the port number, whether the corresponding port can be used for management.
  • the network management server queries whether the port is a management port. If it is a management port, it considers that the corresponding port can be used for management. If it is not a management port, check the IP address or the VLAN to which the device is configured, and determine whether the port is connected. To the management address of the device, if the port can be connected to the management address of the device, the corresponding port can be considered to be managed.
  • Step 222 When the corresponding port is available for management, generate a conflict with the existing address IP address.
  • the network management server can add 1 to the host address of the IP address of the faulty device according to the IP address of the faulty device, and verify whether the IP address after adding 1 conflicts with the IP address in the existing network segment. If the IP addresses in the network segment do not conflict, the IP address after the first network segment is sent to the handheld terminal as the generated IP address. If the IP address conflicts with the existing network segment, the IP address continues to be added until the existing IP address is added. The IP address in the network segment does not conflict, and the IP address that does not conflict is sent to the handheld terminal as the generated IP address. In the process of adding 1, if the host address reaches the maximum value, it is judged from 0. If there is still no address that does not conflict after traversing all the addresses of the network segment, an error message is sent to the handheld terminal.
  • Step 223 When the corresponding port is unavailable for management, send an error prompt report to the handheld terminal.
  • step 240 may be further included, the network management server analyzes the log of the device, and locates the device fault.
  • the network management server checks the working status of the device for the running status of the device. If the working status is abnormal, the corresponding abnormal status is found in the NMS operation and maintenance database. The network management server prepares the root cause of the last critical alarms of the syslog and alarm information analysis devices. The network management server records the result and the log storage directory to the maintenance record of the network management server.
  • the network management server may send the current working state analysis result and the alarm root cause analysis result to the handheld terminal.
  • the handheld terminal may display the current working state analysis result and the alarm root cause analysis result to the user.
  • 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.
  • FIG. 6 is a device fault diagnosis apparatus according to an embodiment of the present invention. Schematic diagram of the structure, the device fault diagnosis device includes:
  • the ID obtaining unit 10 is configured to acquire identity ID information corresponding to the device.
  • the rack map obtaining unit 20 is configured to acquire the rack map data corresponding to the device from the network management server according to the ID information corresponding to the device, where the rack map data includes port information corresponding to the device;
  • the IP address obtaining unit 30 is configured to select a port for connecting according to the rack map data, and obtain an IP address corresponding to the port from the network management server according to the selected port;
  • the log obtaining unit 40 is configured to establish a communication connection with the device according to the IP address, and obtain a log corresponding to the device;
  • the log uploading unit 50 is configured to send the obtained log to the network management server.
  • the ID obtaining unit includes 10:
  • the two-dimensional code scanning module 11 is configured to scan a two-dimensional code on the device, and obtain two-dimensional code data corresponding to the two-dimensional code;
  • the ID obtaining module 12 is configured to verify whether the format of the two-dimensional code data is correct. When the format of the two-dimensional code is correct, the ID information corresponding to the device is obtained from the two-dimensional code data.
  • the IP address obtaining unit 30 includes:
  • the port sending module 31 is configured to select one of the ports according to the user's selection, and send the corresponding port number to the gateway server;
  • the IP address obtaining module 32 is configured to receive an IP address sent by the network management server.
  • the log obtaining unit 40 includes:
  • the WIFI hotspot establishing module 41 is configured to create a WIFI hotspot according to the IP address and the network connection information configured on the network adapter, so that the network adapter automatically connects to the WIFI hotspot when scanning the WIFI hotspot;
  • the network adapter is connected to a port selected by the handheld terminal on the device.
  • the log obtaining unit 40 further includes:
  • the log obtaining module 42 is configured to acquire a time period and a type corresponding to the log that the user needs to obtain, and obtain a corresponding log from the device according to the input time segment and type.
  • FIG. 7 is a schematic structural diagram of a network management server according to an embodiment of the present invention, where the network management server includes:
  • the rack map query unit 60 is configured to receive ID information corresponding to the device sent by the handheld terminal, obtain corresponding rack image data according to the ID information, and send the rack map data to the handheld terminal; wherein the rack is The figure data includes port information corresponding to the device;
  • the IP address generating unit 70 is configured to receive the port number sent by the handheld terminal, generate a corresponding IP address, and send the generated IP address to the handheld terminal;
  • the log collecting unit 80 is configured to receive a log of the device sent by the handheld terminal.
  • the IP address generating unit is configured to: according to the port number, determine whether the corresponding port can be used for management, and when the corresponding port can be used for management, generate a conflict with the existing address. IP address.
  • each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function.
  • the invention is not limited to any specific form of combination of hardware and software.
  • the above technical solution prevents the operation and maintenance personnel from carrying the portable computer when acquiring the log of the faulty device,
  • the labor intensity of the operation and maintenance personnel is reduced; the log of the equipment can be quickly obtained, the time for equipment fault location is reduced, the efficiency of fault recovery is improved, the requirements for the operation and maintenance personnel are reduced, and the operation and maintenance work is reduced.
  • Difficulty; the ability to implement the selected IP address ensures that it does not conflict with the existing IP, avoids the occurrence of secondary faults, and can obtain the IP address more quickly, reducing the time for device fault location.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种日志获取方法和装置、以及网管服务器,所述日志获取方法包括:手持终端获取设备对应的身份标识ID信息;手持终端根据设备对应的ID信息,从网管服务器处获取设备对应的机架图数据;其中,所述机架图数据包括设备对应的端口信息;手持终端根据机架图数据,选择一个用于连接的端口,并根据选择的端口,从网管服务器处获取端口对应的IP地址;手持终端根据所述IP地址与设备建立通信连接,并获取设备对应的日志。上述技术方案能够帮助运维人员快速获取故障的设备的日志,并且降低运维人员的劳动强度。

Description

日志获取方法和装置、以及网管服务器 技术领域
本文涉及但不限于通信领域,尤指一种日志获取方法和装置、以及网管服务器。
背景技术
在设备出现通信故障时,运维人员可以收集设备的日志,并对日志进行分析,从而定位设备的问题所在,并针对定位的问题进行故障的恢复。
在设备出现通信故障时,网管服务器无法通过与设备之间的网络通信获取到设备的日志,需要运维人员去现场获取日志。
运维人员到达现场时,需要携带便携电脑之类的计算机设备,通过网线将设备连接至便携电脑,并通过便携电脑收集设备上的日志。
在连接便携电脑和设备时,需要运维人员对设备有一定的理解,能够选择合适的通信用的端口,如果运维人员对设备的理解不够,可能会无法快速的获得故障的设备的日志,延长故障修复的时间。
另外,在上述过程中,运维人员需要手动查询网管服务器上的IP地址列表,根据IP地址列表,为故障的设备设置与现有的IP地址不冲突的IP地址,使得故障的设备能够通过新设置的IP地址和便携电脑进行通信。
上述过程中,运维人员可以根据经验对故障的设备设置IP地址,很容易由于运维人员的疏忽导致设置的IP地址与现有的IP地址冲突,可能导致二次故障。
因此,目前的日志的收集工作中,需要运维人员对故障设备有一定的了解,并且需要运维人员为故障的设备设置合适的IP地址,对运维人员的要求较高,容易由于运维人员之间的能力差别造成日志的获取时间过长,此外,运维人员需要随身携带便携电脑,也增加了运维人员的劳动强度。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提出了一种日志获取方法和装置、以及网管服务器,能够简单、快速获取故障的设备的日志,并且降低运维人员的劳动强度。
本发明实施例提出了一种日志获取方法,所述日志获取方法包括:
手持终端获取设备对应的身份标识ID信息;
手持终端根据设备对应的ID信息,从网管服务器处获取设备对应的机架图数据;其中,所述机架图数据包括设备对应的端口信息;
手持终端根据机架图数据,选择一个用于连接的端口,并根据选择的端口,从网管服务器处获取端口对应的IP地址;
手持终端根据所述IP地址与设备建立通信连接,并获取设备对应的日志。
可选地,在所述手持终端根据所述IP地址与设备建立通信连接,并获取设备对应的日志之后,所述日志获取方法还包括:
手持终端将获取的日志发送给网管服务器。
可选地,所述获取设备对应的身份标识ID信息包括:
扫描设备上的二维码,并获取二维码对应的二维码数据;
验证二维码数据的格式是否正确,当二维码的格式正确时,从二维码数据中获取设备对应的ID信息。
可选地,所述根据选择的端口,从网管服务器处获取端口对应的IP地址包括:
手持终端根据用户的选择,选择端口中的一个,并将对应的端口号发送给网关服务器;
网管服务器根据所述端口号,判断对应的端口是否能够用于管理,当对应的端口可以用于管理时,生成一个与现有地址不冲突的IP地址,并将IP地址发送给手持终端;
手持终端接收网管服务器发送的IP地址。
可选地,所述根据所述IP地址与设备建立通信连接包括:
根据所述IP地址和网络适配器上配置的网络连接信息,创建WIFI热点,以使得网络适配器在扫描到所述WIFI热点时,自动连接至所述WIFI热点;其中,所述网络适配器通过手持终端所选择的端口连接至设备上。
可选地,所述获取设备对应的日志包括:
手持终端获取用户输入的需要获取的日志对应的时间段和类型,并根据输入的时间段和类型从设备上获取对应的日志。
本发明实施例还提出了一种日志获取方法,所述方法包括:
网管服务器接收手持终端发送的设备对应的ID信息,根据ID信息获取对应的机架图数据,并将所述机架图数据发送给手持终端;其中,所述机架图数据包括设备对应的端口信息;
网管服务器接收手持终端发送的端口号,生成对应的IP地址,并将生成的IP地址发送给手持终端。
可选地,在所述网管服务器接收手持终端发送的端口号,生成对应的IP地址,并将生成的IP地址发送给手持终端之后,所述日志获取方法还包括:
网管服务器接收手持终端发送的设备的日志。
可选地,所述网管服务器接收手持终端发送的端口号,生成对应的IP地址包括:
网管服务器根据所述端口号,判断对应的端口是否能够用于管理,当对应的端口可以用于管理时,生成一个与现有地址不冲突的IP地址。
本发明实施例还提出了一种设备故障诊断装置,设置在手持终端上,所述设备故障诊断装置包括:
ID获取单元,设置为获取设备对应的身份标识ID信息;
机架图获取单元,设置为根据设备对应的ID信息,从网管服务器处获取设备对应的机架图数据;其中,所述机架图数据包括设备对应的端口信息;
IP地址获取单元,设置为据机架图数据,选择一个用于连接的端口,并 根据选择的端口,从网管服务器处获取端口对应的IP地址;
日志获取单元,设置为手持终端根据所述IP地址与设备建立通信连接,并获取设备对应的日志。
可选地,还包括:
日志上传单元,设置为将获取的日志发送给网管服务器。
可选地,所述ID获取单元包括:
二维码扫描模块,设置为扫描设备上的二维码,并获取二维码对应的二维码数据;
ID获取模块,设置为验证二维码数据的格式是否正确,当二维码的格式正确时,从二维码数据中获取设备对应的ID信息。
可选地,所述IP地址获取单元包括:
端口发送模块,设置为根据用户的选择,选择端口中的一个,并将对应的端口号发送给网关服务器;
IP地址获取模块,设置为接收网管服务器发送的IP地址。
可选地,所述日志获取单元包括:
WIFI热点建立模块,设置为根据所述IP地址和网络适配器上配置的网络连接信息,创建WIFI热点,以使得网络适配器在扫描到所述WIFI热点时,自动连接至所述WIFI热点;其中,所述网络适配器通过手持终端所选择的端口连接至设备上。
可选地,所述日志获取单元还包括:
日志获取模块,设置为获取用户输入的需要获取的日志对应的时间段和类型,并根据输入的时间段和类型从设备上获取对应的日志。
本发明实施例还提出了一种网管服务器,所述网管服务器包括:
机架图查询单元,设置为接收手持终端发送的设备对应的ID信息,根据ID信息获取对应的机架图数据,并将所述机架图数据发送给手持终端;其中,所述机架图数据包括设备对应的端口信息;
IP地址生成单元,设置为接收手持终端发送的端口号,生成对应的IP地 址,并将生成的IP地址发送给手持终端。
可选地,还包括:
日志收集单元,设置为接收手持终端发送的设备的日志。
可选地,所述IP地址生成单元是设置为:根据所述端口号,判断对应的端口是否能够用于管理,当对应的端口可以用于管理时,生成一个与现有地址不冲突的IP地址。
本发明实施例还提供了一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,所述计算机可执行指令用于执行上述的方法。
与相关技术相比,本发明实施例提供的技术方案包括:手持终端获取设备对应的身份标识ID信息;手持终端根据设备对应的ID信息,从网管服务器处获取设备对应的机架图数据;其中,所述机架图数据包括设备对应的端口信息;手持终端根据机架图数据,选择一个用于连接的端口,并根据选择的端口,从网管服务器处获取端口对应的IP地址;手持终端根据所述IP地址与设备建立通信连接,并获取设备对应的日志;手持终端将获取的日志发送给网管服务器。通过本发明实施例的方案:
1、运维人员通过手机或平板电脑之类的手持终端获取故障的设备的日志,不用携带重量更大的便携电脑,减少了运维人员的劳动强度;
2、手持终端从网管服务器处获取设备对应的机架图数据,其中机架图数据包括设备对应的端口信息,因此,运维人员根据机架图数据提供的端口信息进行网络连接,在运维人员对设备了解较少的情况下,依然可以快速的完成通信连接,从而快速获取到设备的日志,减少了设备故障定位的时间,提高了故障恢复的效率;并且降低了对运维人员的能力的要求,降低了运维工作执行的难度;
3、通过网管服务器处获取端口对应的IP地址,使得选择的IP地址确保不与现有的IP冲突,避免了出现二次故障的情况,并且能够较快速的获取IP地址,减小了设备故障定位的时间,并且降低了对运维人员的能力的要求,也降低了运维工作执行的难度。
在阅读并理解了附图和详细描述后,可以明白其他方面。
附图概述
图1A为本发明实施例提出的一种日志获取方法的流程示意图;
图1B为本发明实施例提出的一种日志获取方法中的设备连接示意图;
图2A为获取设备对应的身份标识ID信息的流程示意图;
图2B为从网管服务器处获取端口对应的IP地址的流程示意图;
图3为本发明实施例提出的一种示例性的机架结构图的示意图;
图4为本发明实施例提出的另一种日志获取方法的流程示意图;
图5为网管服务器生成IP地址的流程示意图;
图6为本发明实施例提出的一种设备故障诊断装置的结构示意图;
图7为本发明实施例提出的一种网管服务器的结构示意图。
本发明的实施方式
为了便于本领域技术人员的理解,下面结合附图对本发明实施例作进一步的描述,并不能用来限制本发明的保护范围。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的各种方式可以相互组合。
参见图1A,本发明实施例提出了一种日志获取方法,该日志获取方法包括:
步骤110,手持终端获取设备对应的身份标识ID信息;
步骤120,手持终端根据设备对应的ID信息,从网管服务器处获取设备对应的机架图数据;其中,所述机架图数据包括设备对应的端口信息;
步骤130,手持终端根据机架图数据,选择一个用于连接的端口,并根据选择的端口,从网管服务器处获取端口对应的IP地址;
步骤140,手持终端根据所述IP地址与设备建立通信连接,并获取设备对应的日志。
可选的,在步骤140之后,还包括:步骤150,手持终端将获取的日志发送给网管服务器。
本发明实施例中的设备可选的是一种管理设备。本发明实施例提出的日志获取方法尤其适用于如下场景,设备已经在网管服务器上脱管,但是设备没有完全故障,仍然可以通过直连网线进行连接访问的情况。例如:路由配置错误导致设备无法访问;设备部分板卡故障网络瘫痪;设备业务配置冲突导致网络故障;设备地址重复导致路通;设备网关被修改错误导致管理不通等情况。
本发明实施例提出的日志获取方法也可以用于收集与网管连接正常的网元日志信息。对于网管连接正常的设备,采用此方法可以较快的速度收集设备的日志。并且通过移动终端方便地传递给网管服务器或设备的研发工程师或厂商。
参见图1B,为本发明实施例提出的一种日志获取方法中的设备连接示意图,如图1B,手持终端100通过移动网络200连接至网管服务器300,网管服务器300连接至设备400,设备400通过网络适配器500连接至手持终端100。
可选地,参见图2A,步骤110中,所述获取设备对应的身份标识ID信息包括:
步骤1101,扫描设备上的二维码(2-dimensional bar code),并获取二维码对应的二维码数据;
步骤1102,验证二维码数据的格式是否正确。验证二维码数据的格式是否正确,即检查从二维码中是否可以提取设备ID信息。
步骤1103,当二维码的格式正确时,从二维码数据中获取设备对应的ID信息。
步骤1104,当二维码数据的格式不正确时,手持终端向用户发出错误提示信息,并结束。
本发明实施例中,需要根据设备ID,生成对应的二维码图片,并将二维码图片粘贴在设备上,这样当运维人员达到现场时,可以使用手持终端扫描 设备上粘贴的二维码。可选地,采用的二维码为QR-code,二维码中信息存储的格式如下:
DEVICEINFO:ID:设备ID信息;
IP:设备IP地址;
VERSION:设备版本;
QRCORDID:二维码标示ID。
手持终端通过扫描二维码,可以获取对应的文本数据,并获取二维码中存储的上述信息。
本实施例中,通过扫描二维码的方式获取设备的ID信息,此外,也可以将设备的ID信息粘贴在设备上,运维人员可以通过读取设备上的ID信息,并输入到手持终端中。
本发明实施例中,通过手持终端建立WIFI热点,故障的设备通过网络适配器连接至手持终端建立的WIFI热点,从而建立手持终端与设备之间的通信连接。
步骤120中,手持终端在获取设备对应的ID信息之后,可以从网管服务器处获取设备对应的机架图数据,机架图数据包括设备对应的端口信息,端口信息包括端口描述、名称、速率等相关的参数,可选地,机架图数据还包括单板面板图,单板面板图包括端口在机架上的分布的相关信息。通过获取机架图数据,用户能够获知设备的端口的分布和相关信息,从而顺利完成设备和手持终端之间的通信连接。
其中,网管服务器预先存储所有设备的ID信息及其对应的机架图数据。手持终端在接收到网管服务器发送的机架图数据之后,根据机架图数据生成机架结构图,并对机架结构图进行展示,从而使得用户在熟悉设备的情况下,也能够快速了解设备的端口的相关情况,通过查看机架结构图并选择对应的端口,参见图3,为一种示例性的机架结构图的示意图,结合图3所示,该机架图中表示设备包括4个端口,端口旁边的二维码为包括设备的ID信息的二维码,和设备上张贴的二维码一致。
可选地,参见图2B,步骤130中,所述根据选择的端口,从网管服务器 处获取端口对应的IP地址包括:
步骤1301,手持终端根据用户的选择,选择端口中的一个,并将对应的端口号发送给网关服务器;
步骤1302,网管服务器根据所述端口号,判断对应的端口是否能够用于管理;
步骤1303,当对应的端口可以用于管理时,生成一个与现有地址不冲突的IP地址,并将IP地址发送给手持终端,执行步骤1305。
步骤1304,当对应的端口不能用于管理时,网管服务器可以将错误提示消息发送给手持终端,流程结束。
可选地,网管服务器查询该端口是否为管理端口,如果为管理端口则认为对应的端口是否能够用于管理,如果不是管理端口,检查设备配置的IP地址或所属的VLAN,判断此端口是否连接到设备的管理地址,如果此端口可以连接到设备的管理地址,则认为对应的端口可以管理。
其中,IP地址包括主机地址和网络地址,例如,32位的IP地址中,前24位代表网络地址,后8位代表主机地址。如果两个终端的网络地址相同,说明两个终端在同一网段,之间可以通信,主机地址不同,不会发生冲突。例如,两个终端的IP地址分别为192.168.1.20和192.168.1.21,其中192.168.1位网络地址,最后的20和21位主机地址,上述两个终端之间可以通信,也不会发生冲突。
网管服务器可以根据故障的设备的IP地址,将故障的设备的IP地址的主机地址加1,并验证加1之后的IP地址是否与现有的网段中的IP地址冲突,如果与现有的网段中的IP地址不冲突,则将加1之后的IP地址做为生成的IP地址发送给手持终端,如果与现有的网段中的IP地址冲突,则继续加1,直至与现有的网段中的IP地址不发生冲突,并将不发生冲突的IP地址作为生成的IP地址发送给手持终端,在加1过程中,如果主机地址达到最大值,则从0开始判断。如果遍历网段所有的地址之后依然没有不发生冲突的地址,则将错误提示消息发送给手持终端。
例如,故障的设备的IP地址为192.168.1.20,网管服务器将主机地址加1, 得到192.168.1.21,网管服务器验证192.168.1.21是否与现有的网段中的IP地址冲突,如果与现有的网段中的IP地址不冲突,则将192.168.1.21做为生成的IP地址发送给手持终端,如果与现有的网段中的IP地址冲突,则继续加1,直至与现有的网段中的IP地址不发生冲突。
步骤1305,手持终端接收网管服务器发送的IP地址。
步骤140中,根据IP地址与设备建立通信连接包括:
根据所述IP地址和网络适配器上配置的网络连接信息,创建WIFI热点,以使得网络适配器在扫描到所述WIFI热点时,自动连接至所述WIFI热点;其中,所述网络适配器连接至设备上通过手持终端所选择的端口。
运维人员通过手持终端选择需要连接的端口之后,需要将网络适配器插接至该端口,网络适配器将自动扫描周围的WIFI热点和无线网络,当手持终端根据IP地址和网络适配器上配置的网络连接信息创建WIFI热点时,网络适配器会自动连接至手持终端创建的WIFI热点。其中,网络连接信息是指WIFI热点的用户名和密码,需要在网络适配器上设置WIFI热点的用户名和密码,这样网络适配器能够实现热点生成之后的自动连接。
对于网络适配器,可以使用市面上支持无线客户端模式的无线路由器,要求至少有一个RG45的有线网络接口,并且配置为客户机模式,即能够主动连接收集创建的WIFI热点,并连接后不进行路由功能不进行DHCP工作,例如,网络适配器可以采用中兴PW50等无线路由器。
本发明实施例中,步骤140中,所述获取设备对应的日志包括:
手持终端获取用户输入的需要获取的日志对应的时间段和类型,并根据输入的时间段和类型从设备上获取对应的日志。
用户在手持终端的终端日志收集模块上选择需要上传日志的时间段和类型。时间段决定上传哪些时间段的日志。日志的类型包括:syslog、告警、运行日志、操作日志、当期系统进程信息、当前系统配置、当前版本信息、板卡信息等。
不同的时间段和类型的选择对故障定位的准确性有很大的影响,但是如果上传日志过多不仅拷贝缓慢,而且对检查故障也比较困难。最好用户能够 对日志有一个预先的判断。可以设置缺省上传3天内的全部日志信息。
手持终端可以建立FTP的客户端,并通过FTP客户端从设备上拷贝文件类的日志。通过telnet、SNMP、QX、Netconf等协议获取配置和运行状态类的数据。其中,具体通过何种协议上传日志可以根据手持终端中的运维数据库以及设备的类型决定。
在手持终端获取故障的设备的日志之后,可以根据用户的选择,或者默认的设备,或根据是否满足其他的预设条件,将日志上传给网关服务器。
本发明实施例还提供了一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,所述计算机可执行指令用于执行上述的方法。
基于与上述方法实施例相同或相似的构思,本发明实施例还提供另一种日志获取方法,参见图4,本发明实施例提出的另一种日志获取方法包括:
步骤210,网管服务器接收手持终端发送的设备对应的ID信息,根据ID信息获取对应的机架图数据,并将所述机架图数据发送给手持终端;其中,所述机架图数据包括设备对应的端口信息。
其中,网管服务器预先存储其管理范围内所有设备的ID信息及其对应的机架结构图。
步骤220,网管服务器接收手持终端发送的端口号,生成对应的IP地址,并将生成的IP地址发送给手持终端;
步骤230,网管服务器接收手持终端发送的设备的日志。
其中,参见图5,步骤220中,所述网管服务器接收手持终端发送的端口号,生成对应的IP地址包括:
步骤221,网管服务器根据所述端口号,判断对应的端口是否能够用于管理。可选地,网管服务器查询该端口是否为管理端口,如果为管理端口则认为对应的端口是否能够用于管理,如果不是管理端口,检查设备配置的IP地址或所属的VLAN,判断此端口是否连接到设备的管理地址,如果此端口可以连接到设备的管理地址,则认为对应的端口可以管理。
步骤222,当对应的端口可以用于管理时,生成一个与现有地址不冲突 的IP地址。
网管服务器可以根据故障的设备的IP地址,将故障的设备的IP地址的主机地址加1,并验证加1之后的IP地址是否与现有的网段中的IP地址冲突,如果与现有的网段中的IP地址不冲突,则将加1之后的IP地址做为生成的IP地址发送给手持终端,如果与现有的网段中的IP地址冲突,则继续加1,直至与现有的网段中的IP地址不发生冲突,并将不发生冲突的IP地址做为生成的IP地址发送给手持终端,在加1过程中,如果主机地址达到最大值,则从0开始判断。如果遍历网段所有的地址之后依然没有不发生冲突的地址,则将错误提示消息发送给手持终端。
步骤223,当对应的端口不能用于管理时,向手持终端发送错误提示报告。
在步骤230之后,还可以包括步骤240,网管服务器分析设备的日志,并定位设备故障。
其中,网管服务器针对设备运行状态日志信息对设备工作状态进行检查,如果工作状态异常,在网管运维数据库中找到对应的异常状态,则得出运行状态错误的结论。网管服务器准备syslog和告警信息分析设备最后几个关键告警的根原因。网管服务器将此结果和日志存放目录记录到网管服务器的维护记录中。
网管服务器在得到当前工作状态分析结果和告警根原因分析结果之后,可以将当前工作状态分析结果和告警根原因分析结果发送给手持终端。
手持终端接收当前工作状态分析结果和告警根原因分析结果之后,可以将当前工作状态分析结果和告警根原因分析结果显示给用户。
本发明实施例还提供了一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,所述计算机可执行指令用于执行上述的方法。
基于与上述方法实施例相同或相似的构思,本发明实施例还提供一种设备故障诊断装置,设置在手持终端上,参见图,6,为本发明实施例提出的一种设备故障诊断装置的结构示意图,该设备故障诊断装置包括:
ID获取单元10,设置为获取设备对应的身份标识ID信息;
机架图获取单元20,设置为根据设备对应的ID信息,从网管服务器处获取设备对应的机架图数据;其中,所述机架图数据包括设备对应的端口信息;
IP地址获取单元30,设置为根据机架图数据,选择一个用于连接的端口,并根据选择的端口,从网管服务器处获取端口对应的IP地址;
日志获取单元40,设置为根据所述IP地址与设备建立通信连接,并获取设备对应的日志;
日志上传单元50,设置为将获取的日志发送给网管服务器。
本发明实施例中,所述ID获取单元包括10:
二维码扫描模块11,设置为扫描设备上的二维码,并获取二维码对应的二维码数据;
ID获取模块12,设置为验证二维码数据的格式是否正确,当二维码的格式正确时,从二维码数据中获取设备对应的ID信息。
本发明实施例中,所述IP地址获取单元30包括:
端口发送模块31,设置为根据用户的选择,选择端口中的一个,并将对应的端口号发送给网关服务器;
IP地址获取模块32,设置为接收网管服务器发送的IP地址。
本发明实施例中,所述日志获取单元40包括:
WIFI热点建立模块41,设置为根据所述IP地址和网络适配器上配置的网络连接信息,创建WIFI热点,以使得网络适配器在扫描到所述WIFI热点时,自动连接至所述WIFI热点;其中,所述网络适配器连接至设备上通过手持终端所选择的端口。
本发明实施例中,所述日志获取单元40还包括:
日志获取模块42,设置为获取用户输入的需要获取的日志对应的时间段和类型,并根据输入的时间段和类型从设备上获取对应的日志。
基于与上述实施例相同或相似的构思,本发明实施例还提供一种网管服 务器,参见图7,为本发明实施例提出的一种网管服务器的结构示意图,该网管服务器包括:
机架图查询单元60,设置为接收手持终端发送的设备对应的ID信息,根据ID信息获取对应的机架图数据,并将所述机架图数据发送给手持终端;其中,所述机架图数据包括设备对应的端口信息;
IP地址生成单元70,设置为接收手持终端发送的端口号,生成对应的IP地址,并将生成的IP地址发送给手持终端;
日志收集单元80,设置为接收手持终端发送的设备的日志。
本发明实施例中,所述IP地址生成单元是设置为:根据所述端口号,判断对应的端口是否能够用于管理,当对应的端口可以用于管理时,生成一个与现有地址不冲突的IP地址。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成,所述程序可以存储于计算机可读存储介质中,如只读存储器、磁盘或光盘等。可选地,上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地,上述实施例中的各模块/单元可以采用硬件的形式实现,例如通过集成电路来实现其相应功能,也可以采用软件功能模块的形式实现,例如通过处理器执行存储于存储器中的程序/指令来实现其相应功能。本发明不限制于任何特定形式的硬件和软件的结合。
需要说明的是,以上所述的实施例仅是为了便于本领域的技术人员理解而已,并不用于限制本发明的保护范围,在不脱离本发明的发明构思的前提下,本领域技术人员对本发明所做出的任何显而易见的替换和改进等均在本发明的保护范围之内。
工业实用性
上述技术方案避免了运维人员获取故障设备的日志时携带便携电脑,减 少了运维人员的劳动强度;能够快速获取到设备的日志,减少了设备故障定位的时间,提高了故障恢复的效率;并且降低了对运维人员的能力的要求,降低了运维工作执行的难度;能够实现选择的IP地址确保不与现有的IP冲突,避免了出现二次故障的情况,并且能够较快速的获取IP地址,减小了设备故障定位的时间。

Claims (20)

  1. 一种日志获取方法,所述日志获取方法包括:
    手持终端获取设备对应的身份标识ID信息;
    手持终端根据设备对应的ID信息,从网管服务器处获取设备对应的机架图数据;其中,所述机架图数据包括设备对应的端口信息;
    手持终端根据机架图数据,选择一个用于连接的端口,并根据选择的端口,从网管服务器处获取端口对应的网络协议IP地址;
    手持终端根据所述IP地址与设备建立通信连接,并获取设备对应的日志。
  2. 根据权利要求1所述的日志获取方法,所述日志获取方法还包括:
    在所述手持终端根据所述IP地址与设备建立通信连接,并获取设备对应的日志之后,手持终端将获取的日志发送给网管服务器。
  3. 根据权利要求1所述的日志获取方法,其中,所述获取设备对应的身份标识ID信息包括:
    扫描设备上的二维码,并获取二维码对应的二维码数据;
    验证二维码数据的格式是否正确,当二维码的格式正确时,从二维码数据中获取设备对应的ID信息。
  4. 根据权利要求1所述的日志获取方法,其中,所述根据选择的端口,从网管服务器处获取端口对应的IP地址包括:
    手持终端根据用户的选择,选择端口中的一个,并将对应的端口号发送给网关服务器;
    网管服务器根据所述端口号,判断对应的端口是否能够用于管理,当对应的端口可以用于管理时,生成一个与现有地址不冲突的IP地址,并将IP地址发送给手持终端;
    手持终端接收网管服务器发送的IP地址。
  5. 根据权利要求1所述的日志获取方法,其中,所述根据所述IP地址与设备建立通信连接包括:
    根据所述IP地址和网络适配器上配置的网络连接信息,创建WIFI热点,以使得网络适配器在扫描到所述WIFI热点时,自动连接至所述WIFI热点;其中,所述网络适配器通过手持终端所选择的端口连接至设备上。
  6. 根据权利要求1~5中任一项所述的日志获取方法,其中,所述获取设备对应的日志包括:
    手持终端获取用户输入的需要获取的日志对应的时间段和类型,并根据输入的时间段和类型从设备上获取对应的日志。
  7. 一种日志获取方法,所述方法包括:
    网管服务器接收手持终端发送的设备对应的身份标识ID信息,根据ID信息获取对应的机架图数据,并将所述机架图数据发送给手持终端;其中,所述机架图数据包括设备对应的端口信息;
    网管服务器接收手持终端发送的端口号,生成对应的网络协议IP地址,并将生成的IP地址发送给手持终端。
  8. 根据权利要求7所述的日志获取方法,所述日志获取方法还包括:
    在所述网管服务器接收手持终端发送的端口号,生成对应的IP地址,并将生成的IP地址发送给手持终端之后,网管服务器接收手持终端发送的设备的日志。
  9. 根据权利要求7所述的日志获取方法,其中,所述网管服务器接收手持终端发送的端口号,生成对应的IP地址包括:
    网管服务器根据所述端口号,判断对应的端口是否能够用于管理,当对应的端口可以用于管理时,生成一个与现有地址不冲突的IP地址。
  10. 一种设备故障诊断装置,设置在手持终端上,所述设备故障诊断装置包括:
    身份标识ID获取单元,设置为获取设备对应的身份标识ID信息;
    机架图获取单元,设置为根据设备对应的ID信息,从网管服务器处获取设备对应的机架图数据;其中,所述机架图数据包括设备对应的端口信息;
    IP地址获取单元,设置为据机架图数据,选择一个用于连接的端口,并 根据选择的端口,从网管服务器处获取端口对应的网络协议IP地址;
    日志获取单元,设置为手持终端根据所述IP地址与设备建立通信连接,并获取设备对应的日志。
  11. 根据权利要求10所述的设备故障诊断装置,还包括:
    日志上传单元,设置为将获取的日志发送给网管服务器。
  12. 根据权利要求10所述的设备故障诊断装置,其中,所述ID获取单元包括:
    二维码扫描模块,设置为扫描设备上的二维码,并获取二维码对应的二维码数据;
    ID获取模块,设置为验证二维码数据的格式是否正确,当二维码的格式正确时,从二维码数据中获取设备对应的ID信息。
  13. 根据权利要求10所述的设备故障诊断装置,其中,所述IP地址获取单元包括:
    端口发送模块,设置为根据用户的选择,选择端口中的一个,并将对应的端口号发送给网关服务器;
    IP地址获取模块,设置为接收网管服务器发送的IP地址。
  14. 根据权利要求10所述的设备故障诊断装置,其中,所述日志获取单元包括:
    WIFI热点建立模块,设置为根据所述IP地址和网络适配器上配置的网络连接信息,创建WIFI热点,以使得网络适配器在扫描到所述WIFI热点时,自动连接至所述WIFI热点;其中,所述网络适配器通过手持终端所选择的端口连接至设备上。
  15. 根据权利要求10~14中任一项所述的设备故障诊断装置,所述日志获取单元还包括:
    日志获取模块,设置为获取用户输入的需要获取的日志对应的时间段和类型,并根据输入的时间段和类型从设备上获取对应的日志。
  16. 一种网管服务器,所述网管服务器包括:
    机架图查询单元,设置为接收手持终端发送的设备对应的身份标识ID信息,根据ID信息获取对应的机架图数据,并将所述机架图数据发送给手持终端;其中,所述机架图数据包括设备对应的端口信息;
    网络协议IP地址生成单元,设置为接收手持终端发送的端口号,生成对应的IP地址,并将生成的IP地址发送给手持终端。
  17. 根据权利要求16所述的网管服务器,还包括:
    日志收集单元,设置为接收手持终端发送的设备的日志。
  18. 根据权利要求16所述的网管服务器,其中,所述IP地址生成单元是设置为:根据所述端口号,判断对应的端口是否能够用于管理,当对应的端口可以用于管理时,生成一个与现有地址不冲突的IP地址。
  19. 一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,所述计算机可执行指令用于执行权利要求1~6中任一项所述的方法。
  20. 一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,所述计算机可执行指令用于执行权利要求7~9中任一项所述的方法。
PCT/CN2016/075664 2015-06-18 2016-03-04 日志获取方法和装置、以及网管服务器 WO2016202013A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510342332.2A CN106331189B (zh) 2015-06-18 2015-06-18 日志获取方法和装置、以及网管服务器
CN201510342332.2 2015-06-18

Publications (1)

Publication Number Publication Date
WO2016202013A1 true WO2016202013A1 (zh) 2016-12-22

Family

ID=57544975

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/075664 WO2016202013A1 (zh) 2015-06-18 2016-03-04 日志获取方法和装置、以及网管服务器

Country Status (2)

Country Link
CN (1) CN106331189B (zh)
WO (1) WO2016202013A1 (zh)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109740202A (zh) * 2018-12-17 2019-05-10 广州天越电子科技有限公司 一种实现传输规划图纸数字化生成的方法
CN110635946A (zh) * 2019-09-20 2019-12-31 深圳市微目腾科技术有限公司 一种兼容多种网络协议的支持多端诊断的网络诊断系统及方法
CN112311609A (zh) * 2020-11-27 2021-02-02 珠海读书郎网络教育有限公司 一种儿童电话手表无网络环境下异常日志拉取的方法
CN113030142A (zh) * 2020-10-12 2021-06-25 佛山格捷锐信息技术有限公司 手持式xrf光谱仪元素光谱图数据同步方法和装置
CN113282558A (zh) * 2021-05-25 2021-08-20 深圳Tcl新技术有限公司 日志收集方法、装置、存储介质及电子设备
CN114244889A (zh) * 2021-12-17 2022-03-25 深圳Tcl新技术有限公司 一种日志获取方法、装置、终端、智能设备及存储介质
CN114301765A (zh) * 2021-12-29 2022-04-08 中国电信股份有限公司 故障定位方法、装置、计算机可读介质及电子设备
CN114363300A (zh) * 2020-09-27 2022-04-15 中兴通讯股份有限公司 用于单向dvb媒体终端的远程维护方法、媒体终端及服务器
WO2024049605A1 (en) * 2022-08-27 2024-03-07 Apple Inc. Cellular voice and service diagnostic test system for wireless devices

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109067576A (zh) * 2018-07-30 2018-12-21 北京交通大学 基于移动终端应用的铁路信息系统的维护系统和方法
CN110351117A (zh) * 2019-05-24 2019-10-18 上海毅云网络科技有限公司 一种服务器运维管理方法
CN110855526B (zh) * 2019-11-20 2022-03-29 北京百分点科技集团股份有限公司 检测数据源连接的方法、装置、存储介质及电子设备
CN111836340B (zh) * 2020-07-08 2023-06-09 上海金智晟东电力科技有限公司 柱上馈线终端的交互式运维方法及系统
CN112000560A (zh) * 2020-08-07 2020-11-27 山东云缦智能科技有限公司 终端日志获取方法及终端日志获取系统
CN112768046A (zh) * 2021-01-27 2021-05-07 深圳市智莱科技股份有限公司 数据处理方法、医疗管理系统和终端
CN113269536A (zh) * 2021-06-18 2021-08-17 张威 一个基于二维码的施工日志系统及使用方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130136130A1 (en) * 2011-11-30 2013-05-30 Murata Machinery, Ltd. Relay server and relay communication system
CN103840953A (zh) * 2012-11-21 2014-06-04 中兴通讯股份有限公司 远程日志实时获取方法及系统
CN104023213A (zh) * 2014-06-23 2014-09-03 浙江宇视科技有限公司 一种基于二维码的交互式服务方法和系统
CN104394009A (zh) * 2014-10-29 2015-03-04 中国建设银行股份有限公司 一种故障信息的处理方法及装置
CN104506667A (zh) * 2014-12-22 2015-04-08 迈普通信技术股份有限公司 一种分配端口资源的方法及装置、用户认证管理的装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102438259A (zh) * 2011-09-09 2012-05-02 华南农业大学 一种无干扰式手机远程可用性测试系统及其测试方法
CN103236951B (zh) * 2013-05-13 2015-09-23 沈越 一种光网络资源的分配标识方法及系统
CN104065521B (zh) * 2014-07-18 2017-09-29 国家电网公司 一种电力网络设备日志和配置文件的采集、分析和发布系统及其方法
CN104331731A (zh) * 2014-11-21 2015-02-04 国家电网公司 基于二维码技术进行网络与设备识别的方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130136130A1 (en) * 2011-11-30 2013-05-30 Murata Machinery, Ltd. Relay server and relay communication system
CN103840953A (zh) * 2012-11-21 2014-06-04 中兴通讯股份有限公司 远程日志实时获取方法及系统
CN104023213A (zh) * 2014-06-23 2014-09-03 浙江宇视科技有限公司 一种基于二维码的交互式服务方法和系统
CN104394009A (zh) * 2014-10-29 2015-03-04 中国建设银行股份有限公司 一种故障信息的处理方法及装置
CN104506667A (zh) * 2014-12-22 2015-04-08 迈普通信技术股份有限公司 一种分配端口资源的方法及装置、用户认证管理的装置

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109740202A (zh) * 2018-12-17 2019-05-10 广州天越电子科技有限公司 一种实现传输规划图纸数字化生成的方法
CN109740202B (zh) * 2018-12-17 2023-01-17 广州天越电子科技有限公司 一种实现传输规划图纸数字化生成的方法
CN110635946A (zh) * 2019-09-20 2019-12-31 深圳市微目腾科技术有限公司 一种兼容多种网络协议的支持多端诊断的网络诊断系统及方法
CN110635946B (zh) * 2019-09-20 2022-08-09 深圳市富视康智能股份有限公司 一种兼容多种网络协议的支持多端诊断的网络诊断系统及方法
CN114363300A (zh) * 2020-09-27 2022-04-15 中兴通讯股份有限公司 用于单向dvb媒体终端的远程维护方法、媒体终端及服务器
CN113030142A (zh) * 2020-10-12 2021-06-25 佛山格捷锐信息技术有限公司 手持式xrf光谱仪元素光谱图数据同步方法和装置
CN112311609A (zh) * 2020-11-27 2021-02-02 珠海读书郎网络教育有限公司 一种儿童电话手表无网络环境下异常日志拉取的方法
CN113282558A (zh) * 2021-05-25 2021-08-20 深圳Tcl新技术有限公司 日志收集方法、装置、存储介质及电子设备
CN114244889A (zh) * 2021-12-17 2022-03-25 深圳Tcl新技术有限公司 一种日志获取方法、装置、终端、智能设备及存储介质
CN114301765A (zh) * 2021-12-29 2022-04-08 中国电信股份有限公司 故障定位方法、装置、计算机可读介质及电子设备
WO2024049605A1 (en) * 2022-08-27 2024-03-07 Apple Inc. Cellular voice and service diagnostic test system for wireless devices

Also Published As

Publication number Publication date
CN106331189A (zh) 2017-01-11
CN106331189B (zh) 2020-10-16

Similar Documents

Publication Publication Date Title
WO2016202013A1 (zh) 日志获取方法和装置、以及网管服务器
US10038594B2 (en) Centralized management of access points
CN112600716B (zh) 设备配置方法、配置装置及管理设备
US7860016B1 (en) Method and apparatus for configuration and analysis of network routing protocols
CN109039788B (zh) 网络设备的端口配置方法、装置和存储介质
US8738761B2 (en) Method and system to capture and playback network activity
US20150026322A1 (en) Configuring a network device
EP3145136B1 (en) Network switch, device management system, and device management method thereof
US9893968B1 (en) Troubleshooting network paths in a distributed computing environment
CN103138988A (zh) 网络故障的定位处理方法及装置
WO2012139461A1 (zh) 一种数据采集方法、装置及系统
US20210392045A1 (en) Device Configuration Method, System, and Apparatus
US20130042020A1 (en) Quick Network Path Discovery
CN112463281A (zh) 远程协助方法、装置、系统、电子设备及存储介质
JP6124612B2 (ja) エンジニアリング装置およびエンジニアリング方法
US10560348B2 (en) Network access device for facilitating the troubleshooting of network connectivity problems
CN114513419A (zh) 安全策略配置方法及系统
US8656011B2 (en) Method and management apparatus for detecting communication apparatus coupled to communication network
CN103841286B (zh) 信息处理设备和信息处理方法
JP2017183969A (ja) ネットワーク装置、コンフィグ交換方法、保守交換方法、コンフィグ交換プログラム、および保守交換プログラム
CN105808418B (zh) 测试机注册方法、装置及系统
Cisco Release Notes for Cisco ONS 15200 SNM Software, 1.1(3)
Cisco Release Notes for Cisco Aironet Access Points and 350 Series Bridges
JP2017017577A (ja) 接続情報照合装置
CN104579757A (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: 16810754

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: 16810754

Country of ref document: EP

Kind code of ref document: A1