WO2017031922A1 - 故障检测方法及装置 - Google Patents

故障检测方法及装置 Download PDF

Info

Publication number
WO2017031922A1
WO2017031922A1 PCT/CN2016/070141 CN2016070141W WO2017031922A1 WO 2017031922 A1 WO2017031922 A1 WO 2017031922A1 CN 2016070141 W CN2016070141 W CN 2016070141W WO 2017031922 A1 WO2017031922 A1 WO 2017031922A1
Authority
WO
WIPO (PCT)
Prior art keywords
network management
base station
test script
link
fault
Prior art date
Application number
PCT/CN2016/070141
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 WO2017031922A1 publication Critical patent/WO2017031922A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • 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
    • H04L41/0677Localisation of faults
    • 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
    • H04L41/069Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a fault detection method and apparatus.
  • the base station In the centralized network management architecture, the base station is usually managed by a remote network management server.
  • the network management link carries all network management data between the base station and the network management server. Once the network management link is abnormal, the base station will be in a disconnected state, and the network management system cannot operate and maintain it.
  • the technician needs to reach the fault site, and the LMT (Local Maintenance Terminal) interface of the base station is connected to the fault location. Often, technicians spend a lot of time to reach the fault site, resulting in less efficient fault location.
  • LMT Local Maintenance Terminal
  • the main object of the present invention is to provide a fault detection method and apparatus, aiming at improving the efficiency of fault location.
  • the present invention provides a fault detection method, and the fault detection method includes:
  • the base station detects the link status of the network management link between the base station and the network management system
  • the base station When detecting that the disconnection duration of the network management link reaches a preset threshold, the base station acquires and executes a test script, and generates an execution log of the test script;
  • the base station performs a network management link recovery operation
  • the base station When detecting the recovery of the network management link, the base station sends the execution log to the network management system through the network management link, so that the network management device performs fault location based on the received execution log.
  • the base station when detecting that the disconnection duration of the network management link reaches a preset threshold, acquires and executes a test script, and the step of generating an execution log of the test script includes:
  • the base station When detecting that the disconnection duration of the network management link reaches a preset threshold, the base station sends an acquisition request to other base stations connected thereto, so that the other base station returns a test script based on the acquisition request;
  • the fault detection method further includes:
  • the base station Upon receiving the test script sent by the network management, the base station replaces the stored test script with the received test script.
  • the step of the base station performing a network management link recovery operation includes:
  • the base station performs rollback on the parameter configuration operation or the upgrade operation performed last time.
  • the base station further includes:
  • the base station When the network management link is not detected to be restored within a preset time period, the base station sends the execution log to The other base stations that are connected to and communicate with the network management unit, so that the other base stations forward the received execution logs to the network management system through their own network management links.
  • the present invention further provides a fault detecting apparatus, where the fault detecting apparatus includes:
  • a detecting module configured to detect a link state of a network management link between the base station and the network management system
  • An execution module configured to acquire and execute a test script when the detection module detects that the disconnection duration of the network management link reaches a preset threshold, and generate an execution log of the test script
  • a recovery module configured to perform a network management link recovery operation
  • a sending module configured to send, by the network management link, the execution log to the network management system, when the detecting module detects the recovery of the network management link, for the network management system to perform failure based on the received execution log Positioning.
  • the execution module comprises:
  • an acquiring unit configured to: when the detecting module detects that the disconnection duration of the network management link reaches a preset threshold, send an acquisition request to another base station that is connected to the base station where the detecting node is located, for the other base station to acquire based on the acquiring Request to return a test script;
  • an execution unit configured to receive and execute a test script returned by the other base station, and generate an execution log of the test script.
  • the fault detecting device further includes:
  • a replacement module configured to replace the test script stored by the base station with the received test script when receiving the test script sent by the network management system.
  • the recovery module is further configured to roll back a parameter configuration operation or an upgrade operation performed last time on the base station where the base station is located.
  • the sending module is further configured to: when the detecting module does not detect that the network management link is restored within a preset time period, send the execution log to the base station where the base station is connected and communicate with the network management
  • the other base stations are connected to each other, and the other base stations forward the received execution logs to the network management system through their own network management links.
  • the invention detects the connection state of the network management link between the network management system and the network management system in real time, and obtains and executes a test script, generates an execution log including the fault information, and performs a network management link recovery operation when the network management link is faulty. After the network management link is restored, the generated execution log is sent to the network management system, and the network management system performs fault location based on the received execution log.
  • the invention does not require an engineering staff to spend a large amount of time to reach the fault site for fault location, and can improve the efficiency of fault location.
  • FIG. 1 is a schematic flow chart of a first embodiment of a fault detecting method according to the present invention
  • FIG. 2 is a schematic diagram of a refinement process of the execution log of the test script obtained by the base station acquiring and executing a test script when the disconnection duration of the network management link between the network management and the network management device reaches a preset threshold in FIG.
  • FIG. 3 is a schematic flowchart of a fifth embodiment of a fault detecting method according to the present invention.
  • FIG. 4 is a schematic diagram of functional modules of a first embodiment of a fault detecting apparatus according to the present invention.
  • FIG. 5 is a schematic diagram of a refinement function module of the execution module in FIG. 4.
  • FIG. 5 is a schematic diagram of a refinement function module of the execution module in FIG. 4.
  • the present invention provides a fault detection method.
  • the fault detection method includes:
  • Step S10 The base station detects a link state of the network management link between the base station and the network management system.
  • step S20 the base station acquires and executes a test script to generate an execution log of the test script when detecting that the disconnection time of the network management link with the network management system reaches a preset threshold.
  • the fault detection method provided in this embodiment may be used in the fault location of the base station network management link. For example, when the base station detects the fault of the network management link between the network and the network management system, the base station automatically loads the locally stored test script and generates the The execution log of the test script is executed, and then the link recovery operation is performed to send the generated execution log to the network management system for fault location after the network management link is restored.
  • the base station detects the connection state of the network management link between the network management and the network management system in real time, and when detecting that the disconnection duration of the network management link reaches a preset threshold, the base station determines that the network management link is in a fault state, where
  • the preset threshold may be set according to actual needs. For example, the preset threshold is preferably set to 1 hour in this embodiment.
  • the base station After determining the fault of the network management link, acquires and executes a test script, and generates an execution log of the test script.
  • the test script is a set of debug commands, and when the base station executes the test script, the execution log is generated based on the execution result of each debug command included in the test script.
  • the base station locally stores a test script for the base station to perform when the network management link is faulty to collect fault information.
  • Step S30 the base station performs a network management link recovery operation.
  • the base station after performing the test script and generating an execution log of the test script, performs a network management link recovery operation.
  • the root cause of the failure of the network management link is a software failure of the base station.
  • the base station triggers a software failure in a specific scenario during actual operation.
  • the network management link can be restored through specific operations.
  • the network management system sends a specific configuration to the base station, triggering the network management link to be faulty, and the base station can restore the network management link by backing off the base station configuration.
  • the network management link is faulty, and the network management link can be restored by retiring the base station version.
  • step S40 when detecting that the network management link is restored, the base station sends the execution log to the network management system through the network management link, so that the network management system performs fault location based on the received execution log.
  • the base station when detecting that the network management link is restored, sends an execution log generated by the test script to the network management system through the network management link, so that the network management system performs the execution based on the receiving The log locates the fault and eliminates the fault.
  • the base station detects the connection status of the network management link between the network management system and the network management system in real time, and obtains and executes a test script to generate an execution log including the fault information when the network management link is faulty.
  • the network management link recovery operation is performed, and after the network management link is restored, the generated execution log is sent to the network management system, and the network management system performs fault location based on the received execution log.
  • the invention does not require an engineering staff to spend a large amount of time to reach the fault site for fault location, and can improve the efficiency of fault location.
  • step S20 includes:
  • Step S201 when detecting that the disconnection duration of the network management link reaches a preset threshold, the base station sends an acquisition request to other base stations connected thereto, so that the other base station returns a test script based on the acquisition request;
  • Step S202 receiving and executing a test script returned by the other base station, and generating an execution log of the test script.
  • the base station when detecting that the disconnection duration of the network management link with the network management system reaches a preset threshold, the base station sends an acquisition request to other base stations connected thereto, so that the other base station returns to the test based on the acquisition request.
  • a script when the base station receives the test script returned by the other base station, executes the test script and generates an execution log of the test script.
  • the base station replaces the locally stored test script with its newly received test script when the locally stored test script is damaged and receives test scripts sent by other base stations.
  • the fault detection method further includes:
  • the base station Upon receiving the test script sent by the network management, the base station replaces the stored test script with the received test script.
  • test script of the base station can be continuously updated and optimized, so that fault information can be collected more accurately and fault location can be performed.
  • the engineering personnel can write a new test script through the network management or update and optimize the existing test script, and then distribute the updated test script to each base station under the network management through the network management.
  • the base station when receiving the test script sent by the network management, the base station replaces the locally stored test script with the received test script.
  • the step S30 includes:
  • the base station performs rollback on the parameter configuration operation or the upgrade operation performed last time.
  • the network management link between the base station and the network management system is composed of the following three parts:
  • the above three parts may be faulty, which may cause the network management link between the base station and the network management system to be faulty.
  • This embodiment is mainly directed to the foregoing (1), (2) part of the normal, (3) partial failure, that is, the failure recovery operation performed by the base station local network management link failure.
  • the root cause of the failure of the local network management link of the base station is the software failure of the base station.
  • the base station triggers a software failure in a specific scenario during actual operation.
  • the network management system sends a specific configuration command to the base station, triggering the local network management link of the base station to be faulty.
  • the local network management link of the base station is triggered to be faulty.
  • the base station after detecting the fault of the network management link between the network and the network management system, acquires and executes the test script, and after generating the execution log of the test script, performs the parameter configuration operation or the upgrade operation performed last time. Roll back to restore the network management link.
  • the base station finds that the base station performs the version upgrade operation in response to the upgrade command sent by the network management tube before the network management link fault occurs according to the recorded related information, based on the foregoing technology.
  • the description of the solution the person skilled in the art can understand that it is the version upgrade operation that triggers the local network management network link link failure, which causes the network management link between the base station and the network management system to be faulty. Therefore, the base station is related according to the record. The information is used to perform the base station version rollback operation, and the base station version is restored to the base station version before the upgrade, so that the local network management link of the base station can be restored, thereby restoring the network management link between the base station and the network management system.
  • the method further includes:
  • Step S50 When the network management link is not detected to be restored within a preset time period, the base station sends the execution log to other base stations that are connected to and connected to the network management device, for the other base stations. The received execution log is forwarded to the network management system through its own network management link.
  • the reason for the network link link disconnection between the base station and the network management may be caused by hardware reasons such as the physical link disconnection between the base station and the network management system, in addition to the software reasons described in the foregoing embodiments.
  • the fault on the hardware cannot be recovered by the operation of the software. Therefore, in order to ensure that the execution log can be fed back to the network management system, the embodiment further provides an alternative execution log sending manner.
  • the base station after performing the network management link recovery operation, the base station sends the execution log of the test script to its connection if the network management link is not restored within a preset time period.
  • the other base stations connected to the network management device are configured to forward the received execution logs to the network management system through the network management system, and the network management system performs fault location according to the received execution logs, thereby eliminating faults.
  • the preset time period may be set according to actual needs. For example, in this embodiment, the preset time period is preferably set to 15 minutes.
  • the present invention also provides a fault detecting apparatus.
  • the fault detecting apparatus includes:
  • the detecting module 10 is configured to detect a link state of a network management link between the base station and the network management system;
  • the execution module 20 is configured to: when the detecting module detects that the disconnection duration of the network management link reaches a preset threshold, acquire and execute a test script, and generate an execution log of the test script;
  • the fault detection apparatus may be used in the fault location of the base station network management link.
  • the fault detection apparatus is built in the base station, and the base station automatically loads the local storage when detecting the fault of the network management link between the network and the network management system.
  • the test script generates the execution log of the test script, and then performs a link recovery operation to send the generated execution log to the network management system for fault location after the network management link is restored.
  • the detecting module 10 detects the connection state of the network management link between the base station and the network management system in real time, and when the detecting module 10 detects that the disconnection duration of the network management link reaches a preset threshold, the executing module 20 determines the The network management link is in a fault state, and the preset threshold may be set according to actual needs.
  • the preset threshold is preferably set to 1 hour in this embodiment.
  • the execution module 20 After determining the fault of the network management link, acquires and executes a test script, and generates an execution log of the test script.
  • the test script is a set of debug commands, and when the test module 20 executes the test script, the execution log is generated based on the execution result of each debug command included in the test script.
  • the base station locally stores a test script for the execution module 20 to perform when the network management link fails to collect fault information.
  • the recovery module 30 is configured to perform a network management link recovery operation
  • the recovery module 30 performs a network management link recovery operation.
  • the root cause of the failure of the network management link is a software failure of the base station.
  • the base station triggers a software failure in a specific scenario during actual operation.
  • the network management link can be restored through specific operations.
  • the network management system sends a specific configuration to the base station, triggering the network management link to be faulty, and the base station can restore the network management link by backing off the base station configuration.
  • the network management operation upgrades the base station version
  • the network management link is faulty, and the network management link can be restored by retiring the base station version.
  • the sending module 40 is configured to: when the detecting module 10 detects that the network management link is restored, send the execution log to the network management pipe by using the network management link, so that the network management system performs the execution log based on the received Perform fault location.
  • the sending module 40 passes The network management link sends the execution log generated by the execution module to the network management system, and the network management system performs fault location based on the received execution log, thereby eliminating faults.
  • the fault detection apparatus provided in this embodiment is built in the base station to operate, so that the base station detects the connection status of the network management link between the network management and the network management system in real time, and acquires and executes the test script to generate the fault information when the network management link is faulty. And executing the network management link recovery operation, and after the network management link is restored, sending the generated execution log to the network management system, where the network management system performs fault location based on the received execution log.
  • the invention does not require an engineering staff to spend a large amount of time to reach the fault site for fault location, and can improve the efficiency of fault location.
  • the executing module 20 includes:
  • the obtaining unit 201 is configured to: when the detecting module 10 detects that the disconnection duration of the network management link reaches a preset threshold, send an acquisition request to another base station that is connected to the base station where the base station is located, for the other base station to be based on the The get request returns a test script;
  • the executing unit 202 is configured to receive and execute a test script returned by the other base station, and generate an execution log of the test script.
  • the acquiring unit 201 sends an acquisition request to another base station that is connected to the base station where the base station is connected, so that the other base station is based on the The acquisition request returns a test script.
  • the execution unit 202 receives the test script returned by the other base station, the execution unit executes the test script and generates an execution log of the test script.
  • the base station replaces the locally stored test script with its newly received test script when the locally stored test script is damaged and receives test scripts sent by other base stations.
  • the fault detecting apparatus further includes:
  • a replacement module configured to replace the test script stored by the base station with the received test script when receiving the test script sent by the network management system.
  • test script of the base station can be continuously updated and optimized, so that fault information can be collected more accurately and fault location can be performed.
  • the engineering personnel can write a new test script through the network management or update and optimize the existing test script, and then distribute the updated test script to each base station under the network management through the network management.
  • the replacement module when receiving the test script sent by the network management system, replaces the test script stored locally by the base station with the received test script.
  • the recovery module 30 is further configured to perform parameters last time for the base station where the base station is located. The configuration operation or the upgrade operation is rolled back.
  • the network management link between the base station and the network management system is composed of the following three parts:
  • the above three parts may be faulty, which may cause the network management link between the base station and the network management system to be faulty.
  • This embodiment is mainly directed to the foregoing (1), (2) part of the normal, (3) partial failure, that is, the failure recovery operation performed by the base station local network management link failure.
  • the root cause of the failure of the local network management link of the base station is the software failure of the base station.
  • the base station triggers a software failure in a specific scenario during actual operation.
  • the network management system sends a specific configuration command to the base station, triggering the local network management link of the base station to be faulty.
  • the local network management link of the base station is triggered to be faulty.
  • the execution module 20 acquires and executes the test script, and after generating the execution log of the test script, the recovery module 30 is located on the base station where the test module is located. A parameter configuration operation or an upgrade operation performed at a time is performed to roll back to restore the network management link.
  • the recovery module 30 finds that the base station that the base station sends in response to the upgrade command sent by the network management tube before the network management link failure occurs according to the recorded related information.
  • the version upgrade operation is based on the description of the foregoing technical solution. It can be understood by those skilled in the art that it is the version upgrade operation that triggers the local network management link fault of the base station, which causes the network management link between the base station and the network management system to be faulty.
  • the recovery module 30 performs the base station version rollback operation according to the related information recorded by the recording module, restores the base station version to the base station version before the upgrade, and restores the local network management link of the base station, thereby restoring the network management link between the base station and the network management system.
  • the sending module 40 is further configured to: when the detecting module 10 is within a preset time period.
  • the execution log is sent to other base stations that are connected to the base station and are connected to the network management device, so that the other base stations perform reception through the network management link of the network. The log is forwarded to the network management.
  • the reason for the network link link disconnection between the base station and the network management may be caused by hardware reasons such as the physical link disconnection between the base station and the network management system, in addition to the software reasons described in the foregoing embodiments.
  • the fault on the hardware cannot be recovered by the operation of the software. Therefore, in order to ensure that the execution log can be fed back to the network management system, the embodiment further provides an alternative execution log sending manner.
  • the sending module 40 performs the test on the execution module 20.
  • the execution log is sent to another base station that is connected to the base station and is in communication with the network management unit, so that the other base station forwards the received execution log to the network management system through its own network management link, and the network management system receives the The execution log locates the fault and eliminates the fault.
  • the preset time period may be set according to actual needs. For example, in this embodiment, the preset time period is preferably set to 15 minutes.
  • the above base station is configured to perform the above-described fault detection method.
  • the base station can include a base station controller, a base transceiver station, a power component, and a memory.
  • the base station controller can include a wireless transceiver, an antenna, and associated signal processing circuitry and the like.
  • the base transceiver station may include a wireless transmit/receive device, an antenna, a signal processing portion unique to the wireless interface, and the like.
  • the base station controller can perform all operations of the base station, such as data communication, recording operations, and the like.
  • the base station controller can include one or more processors for executing instructions to implement all or part of the steps in the above methods.
  • the memory is configured to store various types of data to support operation of the base station. Examples of such data include instructions, messages, etc. of any application or method running on a base station.
  • the memory can be implemented using any type of volatile or non-volatile memory device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM erasable programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • Power components provide power to the various components of the network optimization system.
  • non-transitory computer readable storage medium comprising instructions, such as a memory comprising instructions executable by a processor of a base station to perform the above method.
  • the non-transitory computer readable storage medium described above may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种故障检测方法,所述故障检测方法包括:基站侦测其与网管间的网管链路的链路状态;在侦测到所述网管链路的断开时长达到预设阈值时,所述基站获取并执行测试脚本,生成所述测试脚本的执行日志;所述基站执行网管链路恢复操作;在侦测到所述网管链路恢复时,所述基站通过所述网管链路将所述执行日志发送至所述网管,以供所述网管基于接收的执行日志进行故障定位。本发明还公开了一种故障检测装置。本发明能够提高故障定位的效率。

Description

故障检测方法及装置 技术领域
本发明涉及通信技术领域,尤其涉及一种故障检测方法及装置。
背景技术
在集中网管的架构中,基站通常由一个远端的网管服务器进行管理。网管链路承载了基站与网管服务器间的所有网管数据。一旦网管链路出现异常,基站就会处于脱管状态,网管无法对其进行操作和维护。目前,当基站与网管服务器之间的链路出现异常时,需要技术人员到达故障现场,使用相应设备连接基站的LMT(Local Maintenance Terminal,本地终端维护)接口,进行故障定位。通常的,技术人员需要花费大量时间才能到达故障现场,导致故障定位的效率较低。
发明内容
本发明的主要目的在于提供一种故障检测方法及装置,旨在提高故障定位的效率。
为实现上述目的,本发明提供一种故障检测方法,所述故障检测方法包括:
基站侦测其与网管间的网管链路的链路状态;
在侦测到所述网管链路的断开时长达到预设阈值时,所述基站获取并执行测试脚本,生成所述测试脚本的执行日志;
所述基站执行网管链路恢复操作;
在侦测到所述网管链路恢复时,所述基站通过所述网管链路将所述执行日志发送至所述网管,以供所述网管基于接收的执行日志进行故障定位。
优选地,所述在侦测到所述网管链路的断开时长达到预设阈值时,所述基站获取并执行测试脚本,生成所述测试脚本的执行日志的步骤包括:
在侦测到所述网管链路的断开时长达到预设阈值时,所述基站发送获取请求至与其连通的其它基站,以供所述其它基站基于所述获取请求返回测试脚本;
接收并执行所述其它基站返回的测试脚本,生成所述测试脚本的执行日志。
优选地,所述故障检测方法还包括:
在接收到所述网管发送的测试脚本时,所述基站将存储的测试脚本替换为接收到的所述测试脚本。
优选地,所述基站执行网管链路恢复操作的步骤包括:
所述基站对上一次进行的参数配置操作或升级操作进行回退。
优选地,所述基站执行网管链路恢复操作的步骤之后,还包括:
在预设时间段内未侦测到所述网管链路恢复时,所述基站将所述执行日志发送至 其连通的且与所述网管连通的其它基站,以供所述其它基站通过自身的网管链路将接收的执行日志转发至所述网管。
此外,为实现上述目的,本发明还提供一种故障检测装置,所述故障检测装置包括:
检测模块,用于侦测其所在基站与网管间的网管链路的链路状态;
执行模块,用于在所述检测模块侦测到所述网管链路的断开时长达到预设阈值时,获取并执行测试脚本,生成所述测试脚本的执行日志;
恢复模块,用于执行网管链路恢复操作;
发送模块,用于在所述检测模块侦测到所述网管链路恢复时,通过所述网管链路将所述执行日志发送至所述网管,以供所述网管基于接收的执行日志进行故障定位。
优选地,所述执行模块包括:
获取单元,用于在所述检测模块侦测到所述网管链路的断开时长达到预设阈值时,发送获取请求至与其所在基站连通的其它基站,以供所述其它基站基于所述获取请求返回测试脚本;
执行单元,用于接收并执行所述其它基站返回的测试脚本,生成所述测试脚本的执行日志。
优选地,所述故障检测装置还包括:
替换模块,用于在接收到所述网管发送的测试脚本时,将其所在基站存储的测试脚本替换为接收到的所述测试脚本。
优选地,所述恢复模块还用于对其所在基站上一次进行的参数配置操作或升级操作进行回退。
优选地,所述发送模块还用于当所述检测模块在预设时间段内未侦测到所述网管链路恢复时,将所述执行日志发送至其所在基站连通的且与所述网管连通的其它基站,以供所述其它基站通过自身的网管链路将接收的执行日志转发至所述网管。
本发明通过基站实时侦测其与网管间的网管链路的连接状态,在所述网管链路连接故障时,获取并执行测试脚本,生成包括故障信息的执行日志,以及执行网管链路恢复操作,并在所述网管链路恢复后,将生成的所述执行日志发送至网管,供所述网管基于接收的执行日志进行故障定位。相较于现有技术,本发明无需工程人员花费大量时间到达故障现场进行故障定位,能够提高故障定位的效率。
附图说明
图1为本发明故障检测方法第一实施例的流程示意图;
图2为图1中在侦测到与网管间的网管链路的断开时长达到预设阈值时,基站获取并执行测试脚本,生成所述测试脚本的执行日志的细化流程示意图;
图3为本发明故障检测方法第五实施例的流程示意图;
图4为本发明故障检测装置第一实施例的功能模块示意图;
图5为图4中执行模块的细化功能模块示意图。
本发明目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。
具体实施方式
应当理解,此处所描述的具体实施例仅仅用以解释本发明,并不用于限定本发明。
本发明提供一种故障检测方法,参照图1,在本发明故障检测方法的第一实施例中,所述故障检测方法包括:
步骤S10,基站侦测其与网管间的网管链路的链路状态;
步骤S20,在侦测到与网管间的网管链路的断开时长达到预设阈值时,所述基站获取并执行测试脚本,生成所述测试脚本的执行日志;
本实施例提供的故障检测方法可以用于基站网管链路的故障定位中,例如,基站在侦测到其与网管间的网管链路故障时,自动加载本地存储的测试脚本,并生成所述测试脚本的执行日志,然后执行链路恢复操作,以在所述网管链路恢复之后,将生成的执行日志发送至所述网管,供网管进行故障定位。
具体的,基站实时侦测其与网管间网管链路的连接状态,在侦测到所述网管链路的断开时长达到预设阈值时,基站确定所述网管链路处于故障状态,其中,所述预设阈值可根据实际需要进行设置,例如,本实施例优选将所述预设阈值设为1小时。
在确定网管链路故障后,所述基站获取并执行测试脚本,生成所述测试脚本的执行日志。其中,所述测试脚本是一系列调试命令的集合,所述基站在执行测试脚本时,基于所述测试脚本包括的各调试命令的执行结果,生成执行日志。优选地,所述基站本地存储有测试脚本,供所述基站在网管链路故障时执行以收集故障信息。
步骤S30,所述基站执行网管链路恢复操作;
本实施例中,在执行完成所述测试脚本并生成所述测试脚本的执行日志之后,所述基站执行网管链路恢复操作。通常的,导致所述网管链路故障的根本原因是基站的软件故障。基站在实际运行过程中的特定场景下会触发软件故障表现出来。在部分场景中,通过特定的操作可以将网管链路恢复。例如,网管下发特定的配置到基站,触发网管链路故障,基站可以通过回退基站配置来恢复网管链路。又例如,网管操作升级基站版本后,触发网管链路故障,可以通过回退基站版本来恢复网管链路。
步骤S40,在侦测到所述网管链路恢复时,所述基站通过所述网管链路将所述执行日志发送至所述网管,以供所述网管基于接收的执行日志进行故障定位。
本实施例中,基站在侦测到所述网管链路恢复时,通过所述网管链路将其执行所述测试脚本生成的执行日志发送至所述网管,以供所述网管基于接收的执行日志进行故障定位,进而排除故障。
本实施例提出的故障检测方法,基站实时侦测其与网管间的网管链路的连接状态,在所述网管链路连接故障时,获取并执行测试脚本,生成包括故障信息的执行日志,以及执行网管链路恢复操作,并在所述网管链路恢复后,将生成的所述执行日志发送至网管,供所述网管基于接收的执行日志进行故障定位。相较于现有技术,本发明无需工程人员花费大量时间到达故障现场进行故障定位,能够提高故障定位的效率。
进一步的,基于第一实施例,提出本发明故障检测方法的第二实施例,参照图2,在本实施例中,上述步骤S20包括:
步骤S201,在侦测到所述网管链路的断开时长达到预设阈值时,所述基站发送获取请求至与其连通的其它基站,以供所述其它基站基于所述获取请求返回测试脚本;
步骤S202,接收并执行所述其它基站返回的测试脚本,生成所述测试脚本的执行日志。
需要说明的是,本实施例与第一实施例的区别在于,考虑到基站本地存储的测试脚本损坏等因素,提供一种备选的测试脚本获取方式供基站在本地存储的测试脚本损坏时,仍能够获取所需的测试脚本。
具体的,在侦测到与网管间的网管链路的断开时长达到预设阈值时,所述基站发送获取请求至与其连通的其它基站,以供所述其它基站基于所述获取请求返回测试脚本,所述基站在接收到所述其它基站返回的测试脚本时,执行所述测试脚本并生成所述测试脚本的执行日志。优选地,所述基站在本地存储的测试脚本损坏且接收到其它基站发送的测试脚本时,将本地存储的测试脚本替换为其新接收的测试脚本。
进一步的,基于第一实施例,提出本发明故障检测方法的第三实施例,在本实施例中,所述故障检测方法还包括:
在接收到所述网管发送的测试脚本时,所述基站将存储的测试脚本替换为接收到的所述测试脚本。
容易理解的是,可以对基站的测试脚本进行不断更新优化,从而更准确的收集故障信息,进行故障定位。工程人员可以通过网管编写新的测试脚本或者是对现有的测试脚本进行更新优化,再通过网管将更新后的测试脚本分发至所述网管管辖的各个基站。本实施例中,基站在接收到所述网管发送的测试脚本时,将本地存储的测试脚本替换为接收到的所述测试脚本。
进一步的,基于第一、第二或第三实施例,提出本发明故障检测方法的第四实施例,在本实施例中,上述步骤S30包括:
所述基站对上一次进行的参数配置操作或升级操作进行回退。
需要说明的是,基站和网管间的网管链路由以下三部分组成:
(1)、网管本地网管链路
(2)、网管与基站间的承载链路
(3)、基站本地网管链路
在实际运行过程中,上述三部分均可能出现故障,进而导致基站和网管间的网管链路故障。本实施例主要针对前述(1)、(2)部分正常,(3)部分故障,即基站本地网管链路故障进行的故障恢复操作。通常的,导致基站本地网管链路故障的根本原因是基站的软件故障。基站在实际运行过程中的特定场景下会触发软件故障表现出来。例如,网管下发特定的配置指令到基站,触发基站本地网管链路故障,又例如,网管操作升级基站版本后,触发基站本地网管链路故障。
本实施例中,基站在侦测到其与网管间的网管链路故障时,获取并执行测试脚本,以及生成所述测试脚本的执行日志之后,对上一次进行的参数配置操作或升级操作进行回退,以恢复所述网管链路。
例如,基站在执行完成测试脚本并生成所述测试脚本的执行日志之后,根据记录的相关信息发现基站在所述网管链路故障前响应过网管发送的升级指令进行了版本升级操作,基于前述技术方案的描述,本领域技术人员可以理解的是,正是这次版本升级操作触发了基站本地网管链路故障,进而导致基站与网管间的网管链路故障,因此,所述基站根据记录的相关信息进行基站版本回退操作,将基站版本恢复至升级之前的基站版本,即可恢复基站本地网管链路,进而恢复基站与网管间的网管链路。
进一步的,基于第一实施例,提出本发明故障检测方法的第五实施例,参照图3,在本实施例中,上述步骤S30之后,还包括:
步骤S50,在预设时间段内未侦测到所述网管链路恢复时,所述基站将所述执行日志发送至其连通的且与所述网管连通的其它基站,以供所述其它基站通过自身的网管链路将接收的执行日志转发至所述网管。
本领域技术人员可以理解的是,基站与网管间网管链路断链的原因除了前述实施例所述的软件原因之外,还可能由基站和网管间的物理链路断链等硬件原因导致,而硬件上的故障是不能够由软件层面的操作恢复的,因此,为确保能够将所述执行日志反馈至所述网管,本实施例还提供一种备选的执行日志发送方式。
具体的,所述基站在执行网管链路恢复操作之后,若未在预设时间段内侦测到所述网管链路恢复,所述基站将其执行测试脚本的所述执行日志发送至其连通的且与所 述网管连通的其它基站,以供所述其它基站通过自身的网管链路将接收的执行日志转发至所述网管,由网管根据接收的执行日志进行故障定位,进而排除故障。其中,所述预设时间段可根据实际需要进行设置,例如,本实施例优选将所述预设时间段设为15分钟。
本发明还提供一种故障检测装置,参照图4,在本发明故障检测装置的第一实施例中,所述故障检测装置包括:
检测模块10,用于侦测其所在基站与网管间的网管链路的链路状态;
执行模块20,用于在所述检测模块侦测到所述网管链路的断开时长达到预设阈值时,获取并执行测试脚本,生成所述测试脚本的执行日志;
本实施例提供的故障检测装置可以用于基站网管链路的故障定位中,例如,故障检测装置内置于基站运行,基站在侦测到其与网管间的网管链路故障时,自动加载本地存储的测试脚本,并生成所述测试脚本的执行日志,然后执行链路恢复操作,以在所述网管链路恢复之后,将生成的执行日志发送至所述网管,供网管进行故障定位。
具体的,检测模块10实时侦测其所在基站与网管间网管链路的连接状态,在检测模块10侦测到所述网管链路的断开时长达到预设阈值时,执行模块20确定所述网管链路处于故障状态,其中,所述预设阈值可根据实际需要进行设置,例如,本实施例优选将所述预设阈值设为1小时。
在确定网管链路故障后,所述执行模块20获取并执行测试脚本,生成所述测试脚本的执行日志。其中,所述测试脚本是一系列调试命令的集合,所述执行模块20在执行测试脚本时,基于所述测试脚本包括的各调试命令的执行结果,生成执行日志。优选地,所述基站本地存储有测试脚本,供所述执行模块20在网管链路故障时执行以收集故障信息。
恢复模块30,用于执行网管链路恢复操作;
本实施例中,在执行模块20执行完成所述测试脚本并生成所述测试脚本的执行日志之后,恢复模块30执行网管链路恢复操作。通常的,导致所述网管链路故障的根本原因是基站的软件故障。基站在实际运行过程中的特定场景下会触发软件故障表现出来。在部分场景中,通过特定的操作可以将网管链路恢复。例如,网管下发特定的配置到基站,触发网管链路故障,基站可以通过回退基站配置来恢复网管链路。又例如,网管操作升级基站版本后,触发网管链路故障,可以通过回退基站版本来恢复网管链路。
发送模块40,用于在所述检测模块10侦测到所述网管链路恢复时,通过所述网管链路将所述执行日志发送至所述网管,以供所述网管基于接收的执行日志进行故障定位。
本实施例中,发送模块40在所述检测模块10侦测到所述网管链路恢复时,通过 所述网管链路将执行模块20执行所述测试脚本生成的执行日志发送至所述网管,以供所述网管基于接收的执行日志进行故障定位,进而排除故障。
本实施例提出的故障检测装置内置于基站运行,使得基站实时侦测其与网管间的网管链路的连接状态,在所述网管链路连接故障时,获取并执行测试脚本,生成包括故障信息的执行日志,以及执行网管链路恢复操作,并在所述网管链路恢复后,将生成的所述执行日志发送至网管,供所述网管基于接收的执行日志进行故障定位。相较于现有技术,本发明无需工程人员花费大量时间到达故障现场进行故障定位,能够提高故障定位的效率。
进一步的,基于第一实施例,提出本发明故障检测装置的第二实施例,参照图5,在本实施例中,所述执行模块20包括:
获取单元201,用于在所述检测模块10侦测到所述网管链路的断开时长达到预设阈值时,发送获取请求至与其所在基站连通的其它基站,以供所述其它基站基于所述获取请求返回测试脚本;
执行单元202,用于接收并执行所述其它基站返回的测试脚本,生成所述测试脚本的执行日志。
需要说明的是,本实施例与第一实施例的区别在于,考虑到基站本地存储的测试脚本损坏等因素,提供一种备选的测试脚本获取方式供执行模块20在基站本地存储的测试脚本损坏时,仍能够获取所需的测试脚本。
具体的,获取单元201在所述检测模块10侦测到所述网管链路的断开时长达到预设阈值时,发送获取请求至与其所在基站连通的其它基站,以供所述其它基站基于所述获取请求返回测试脚本,执行单元202在接收到所述其它基站返回的测试脚本时,执行所述测试脚本并生成所述测试脚本的执行日志。优选地,所述基站在本地存储的测试脚本损坏且接收到其它基站发送的测试脚本时,将本地存储的测试脚本替换为其新接收的测试脚本。
进一步的,基于第一实施例,提出本发明故障检测装置的第三实施例,在本实施例中,所述故障检测装置还包括:
替换模块,用于在接收到所述网管发送的测试脚本时,将其所在基站存储的测试脚本替换为接收到的所述测试脚本。
容易理解的是,可以对基站的测试脚本进行不断更新优化,从而更准确的收集故障信息,进行故障定位。工程人员可以通过网管编写新的测试脚本或者是对现有的测试脚本进行更新优化,再通过网管将更新后的测试脚本分发至所述网管管辖的各个基站。本实施例中,替换模块在接收到所述网管发送的测试脚本时,将其所在基站本地存储的测试脚本替换为接收到的所述测试脚本。
进一步的,基于第一、第二或第三实施例,提出本发明故障检测装置的第四实施例,在本实施例中,所述恢复模块30还用于对其所在基站上一次进行的参数配置操作或升级操作进行回退。
需要说明的是,基站和网管间的网管链路由以下三部分组成:
(1)、网管本地网管链路
(2)、网管与基站间的承载链路
(3)、基站本地网管链路
在实际运行过程中,上述三部分均可能出现故障,进而导致基站和网管间的网管链路故障。本实施例主要针对前述(1)、(2)部分正常,(3)部分故障,即基站本地网管链路故障进行的故障恢复操作。通常的,导致基站本地网管链路故障的根本原因是基站的软件故障。基站在实际运行过程中的特定场景下会触发软件故障表现出来。例如,网管下发特定的配置指令到基站,触发基站本地网管链路故障,又例如,网管操作升级基站版本后,触发基站本地网管链路故障。
本实施例中,在所述检测模块10侦测到所述网管链路故障时,执行模块20获取并执行测试脚本,以及生成所述测试脚本的执行日志之后,恢复模块30对其所在基站上一次进行的参数配置操作或升级操作进行回退,以恢复所述网管链路。
例如,恢复模块30在执行模块20执行完成测试脚本并生成所述测试脚本的执行日志之后,根据记录的相关信息发现其所在基站在所述网管链路故障前响应过网管发送的升级指令进行了版本升级操作,基于前述技术方案的描述,本领域技术人员可以理解的是,正是这次版本升级操作触发了基站本地网管链路故障,进而导致基站与网管间的网管链路故障,因此,所述恢复模块30根据记录模块记录的相关信息进行基站版本回退操作,将基站版本恢复至升级之前的基站版本,即可恢复基站本地网管链路,进而恢复基站与网管间的网管链路。
进一步的,基于第一实施例,提出本发明故障检测装置的第五实施例,在本实施例中,所述故所述发送模块40还用于当所述检测模块10在预设时间段内未侦测到所述网管链路恢复时,将所述执行日志发送至其所在基站连通的且与所述网管连通的其它基站,以供所述其它基站通过自身的网管链路将接收的执行日志转发至所述网管。
本领域技术人员可以理解的是,基站与网管间网管链路断链的原因除了前述实施例所述的软件原因之外,还可能由基站和网管间的物理链路断链等硬件原因导致,而硬件上的故障是不能够由软件层面的操作恢复的,因此,为确保能够将所述执行日志反馈至所述网管,本实施例还提供一种备选的执行日志发送方式。
具体的,在恢复模块30执行网管链路恢复操作之后,若检测模块10在预设时间段内未侦测到所述网管链路恢复时,所述发送模块40将所述执行模块20执行测试脚 本的所述执行日志发送至其所在基站连通的且与所述网管连通的其它基站,以供所述其它基站通过自身的网管链路将接收的执行日志转发至所述网管,由网管根据接收的执行日志进行故障定位,进而排除故障。其中,所述预设时间段可根据实际需要进行设置,例如,本实施例优选将所述预设时间段设为15分钟。
上述基站被配置为执行上述故障检测方法。该基站可以包括基站控制器、基站收发信机、电力组件以及存储器。该基站控制器可以包括无线收发信机、天线和有关的信号处理电路等。该基站收发信机可以包括无线发射/接收设备、天线、无线接口特有的信号处理部分等。
该基站控制器可以执行基站的全部操作,例如数据通信、记录操作等。该基站控制器可以包括一个或多个处理器,用以执行指令以实施上述方法中的所有或部分步骤。
该存储器被配置为存储各种类型的数据以支持基站的操作。这种数据的示例包括在基站上运行的任意应用或方法的指令、消息等。存储器可以使用任何类型的易失性或非易失性存储器件或其组合来实施,例如静态随机存取存储器(SRAM),电可擦除可编程只读存储器(EEPROM),可擦除可编程只读存储器(EPROM),可编程只读存储器(PROM),只读存储器(ROM),磁存储器,快闪存储器,磁盘或光盘。
电力组件为网络优化系统的各种组件提供电力。
在示例性实施例中,还提供了一种包括指令的非临时性计算机可读存储介质,例如包括指令的存储器,上述指令可由基站的处理器执行以完成上述方法。例如,上述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
以上仅为本发明的优选实施例,并非因此限制本发明的专利范围,凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换,或直接或间接运用在其他相关的技术领域,均同理包括在本发明的专利保护范围内。

Claims (10)

  1. 一种故障检测方法,其特征在于,所述故障检测方法包括:
    基站侦测其与网管间的网管链路的链路状态;
    在侦测到所述网管链路的断开时长达到预设阈值时,所述基站获取并执行测试脚本,生成所述测试脚本的执行日志;
    所述基站执行网管链路恢复操作;
    在侦测到所述网管链路恢复时,所述基站通过所述网管链路将所述执行日志发送至所述网管,以供所述网管基于接收的执行日志进行故障定位。
  2. 如权利要求1所述的故障检测方法,其特征在于,所述在侦测到所述网管链路的断开时长达到预设阈值时,所述基站获取并执行测试脚本,生成所述测试脚本的执行日志的步骤包括:
    在侦测到所述网管链路的断开时长达到预设阈值时,所述基站发送获取请求至与其连通的其它基站,以供所述其它基站基于所述获取请求返回测试脚本;
    接收并执行所述其它基站返回的测试脚本,生成所述测试脚本的执行日志。
  3. 如权利要求1所述的故障检测方法,其特征在于,所述故障检测方法还包括:
    在接收到所述网管发送的测试脚本时,所述基站将存储的测试脚本替换为接收到的所述测试脚本。
  4. 如权利要求1-3任一项所述的故障检测方法,其特征在于,所述基站执行网管链路恢复操作的步骤包括:
    所述基站对上一次进行的参数配置操作或升级操作进行回退。
  5. 如权利要求1所述的故障检测方法,其特征在于,所述基站执行网管链路恢复操作的步骤之后,还包括:
    在预设时间段内未侦测到所述网管链路恢复时,所述基站将所述执行日志发送至其连通的且与所述网管连通的其它基站,以供所述其它基站通过自身的网管链路将接收的执行日志转发至所述网管。
  6. 一种故障检测装置,其特征在于,所述故障检测装置包括:
    检测模块,用于侦测其所在基站与网管间的网管链路的链路状态;
    执行模块,用于在所述检测模块侦测到所述网管链路的断开时长达到预设阈值时,获取并执行测试脚本,生成所述测试脚本的执行日志;
    恢复模块,用于执行网管链路恢复操作;
    发送模块,用于在所述检测模块侦测到所述网管链路恢复时,通过所述网管链路将所述执行日志发送至所述网管,以供所述网管基于接收的执行日志进行故障定位。
  7. 如权利要求6所述的故障检测装置,其特征在于,所述执行模块包括:
    获取单元,用于在所述检测模块侦测到所述网管链路的断开时长达到预设阈值时,发送获取请求至与其所在基站连通的其它基站,以供所述其它基站基于所述获取请求返回测试脚本;
    执行单元,用于接收并执行所述其它基站返回的测试脚本,生成所述测试脚本的执行日志。
  8. 如权利要求6所述的故障检测装置,其特征在于,所述故障检测装置还包括:
    替换模块,用于在接收到所述网管发送的测试脚本时,将其所在基站存储的测试脚本替换为接收到的所述测试脚本。
  9. 如权利要求6-8任一项所述的故障检测装置,其特征在于,所述恢复模块还用于对其所在基站上一次进行的参数配置操作或升级操作进行回退。
  10. 如权利要求6所述的故障检测装置,其特征在于,所述发送模块还用于当所述检测模块在预设时间段内未侦测到所述网管链路恢复时,将所述执行日志发送至其所在基站连通的且与所述网管连通的其它基站,以供所述其它基站通过自身的网管链路将接收的执行日志转发至所述网管。
PCT/CN2016/070141 2015-08-27 2016-01-05 故障检测方法及装置 WO2017031922A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510536348.7A CN106488487A (zh) 2015-08-27 2015-08-27 故障检测方法及装置
CN201510536348.7 2015-08-27

Publications (1)

Publication Number Publication Date
WO2017031922A1 true WO2017031922A1 (zh) 2017-03-02

Family

ID=58099550

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/070141 WO2017031922A1 (zh) 2015-08-27 2016-01-05 故障检测方法及装置

Country Status (2)

Country Link
CN (1) CN106488487A (zh)
WO (1) WO2017031922A1 (zh)

Cited By (61)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10218572B2 (en) 2017-06-19 2019-02-26 Cisco Technology, Inc. Multiprotocol border gateway protocol routing validation
US10333787B2 (en) 2017-06-19 2019-06-25 Cisco Technology, Inc. Validation of L3OUT configuration for communications outside a network
US10333833B2 (en) 2017-09-25 2019-06-25 Cisco Technology, Inc. Endpoint path assurance
US10341184B2 (en) 2017-06-19 2019-07-02 Cisco Technology, Inc. Validation of layer 3 bridge domain subnets in in a network
US10348564B2 (en) 2017-06-19 2019-07-09 Cisco Technology, Inc. Validation of routing information base-forwarding information base equivalence in a network
US10411996B2 (en) 2017-06-19 2019-09-10 Cisco Technology, Inc. Validation of routing information in a network fabric
US10432467B2 (en) 2017-06-19 2019-10-01 Cisco Technology, Inc. Network validation between the logical level and the hardware level of a network
US10439875B2 (en) 2017-05-31 2019-10-08 Cisco Technology, Inc. Identification of conflict rules in a network intent formal equivalence failure
US10437641B2 (en) 2017-06-19 2019-10-08 Cisco Technology, Inc. On-demand processing pipeline interleaved with temporal processing pipeline
US10498608B2 (en) 2017-06-16 2019-12-03 Cisco Technology, Inc. Topology explorer
US10505816B2 (en) 2017-05-31 2019-12-10 Cisco Technology, Inc. Semantic analysis to detect shadowing of rules in a model of network intents
US10528444B2 (en) 2017-06-19 2020-01-07 Cisco Technology, Inc. Event generation in response to validation between logical level and hardware level
US10536337B2 (en) 2017-06-19 2020-01-14 Cisco Technology, Inc. Validation of layer 2 interface and VLAN in a networked environment
US10547715B2 (en) 2017-06-16 2020-01-28 Cisco Technology, Inc. Event generation in response to network intent formal equivalence failures
US10547509B2 (en) 2017-06-19 2020-01-28 Cisco Technology, Inc. Validation of a virtual port channel (VPC) endpoint in the network fabric
US10554477B2 (en) 2017-09-13 2020-02-04 Cisco Technology, Inc. Network assurance event aggregator
US10554493B2 (en) 2017-06-19 2020-02-04 Cisco Technology, Inc. Identifying mismatches between a logical model and node implementation
US10554483B2 (en) 2017-05-31 2020-02-04 Cisco Technology, Inc. Network policy analysis for networks
US10560328B2 (en) 2017-04-20 2020-02-11 Cisco Technology, Inc. Static network policy analysis for networks
US10560355B2 (en) 2017-06-19 2020-02-11 Cisco Technology, Inc. Static endpoint validation
US10567228B2 (en) 2017-06-19 2020-02-18 Cisco Technology, Inc. Validation of cross logical groups in a network
US10567229B2 (en) 2017-06-19 2020-02-18 Cisco Technology, Inc. Validating endpoint configurations between nodes
US10574513B2 (en) 2017-06-16 2020-02-25 Cisco Technology, Inc. Handling controller and node failure scenarios during data collection
US10572495B2 (en) 2018-02-06 2020-02-25 Cisco Technology Inc. Network assurance database version compatibility
US10581694B2 (en) 2017-05-31 2020-03-03 Cisco Technology, Inc. Generation of counter examples for network intent formal equivalence failures
US10587456B2 (en) 2017-09-12 2020-03-10 Cisco Technology, Inc. Event clustering for a network assurance platform
US10587621B2 (en) 2017-06-16 2020-03-10 Cisco Technology, Inc. System and method for migrating to and maintaining a white-list network security model
US10587484B2 (en) 2017-09-12 2020-03-10 Cisco Technology, Inc. Anomaly detection and reporting in a network assurance appliance
US10616072B1 (en) 2018-07-27 2020-04-07 Cisco Technology, Inc. Epoch data interface
US10623271B2 (en) 2017-05-31 2020-04-14 Cisco Technology, Inc. Intra-priority class ordering of rules corresponding to a model of network intents
US10623259B2 (en) 2017-06-19 2020-04-14 Cisco Technology, Inc. Validation of layer 1 interface in a network
US10623264B2 (en) 2017-04-20 2020-04-14 Cisco Technology, Inc. Policy assurance for service chaining
US10644946B2 (en) 2017-06-19 2020-05-05 Cisco Technology, Inc. Detection of overlapping subnets in a network
US10652102B2 (en) 2017-06-19 2020-05-12 Cisco Technology, Inc. Network node memory utilization analysis
US10659298B1 (en) 2018-06-27 2020-05-19 Cisco Technology, Inc. Epoch comparison for network events
US10673702B2 (en) 2017-06-19 2020-06-02 Cisco Technology, Inc. Validation of layer 3 using virtual routing forwarding containers in a network
US10686669B2 (en) 2017-06-16 2020-06-16 Cisco Technology, Inc. Collecting network models and node information from a network
US10693738B2 (en) 2017-05-31 2020-06-23 Cisco Technology, Inc. Generating device-level logical models for a network
US10700933B2 (en) 2017-06-19 2020-06-30 Cisco Technology, Inc. Validating tunnel endpoint addresses in a network fabric
US10797951B2 (en) 2014-10-16 2020-10-06 Cisco Technology, Inc. Discovering and grouping application endpoints in a network environment
US10805160B2 (en) 2017-06-19 2020-10-13 Cisco Technology, Inc. Endpoint bridge domain subnet validation
US10812336B2 (en) 2017-06-19 2020-10-20 Cisco Technology, Inc. Validation of bridge domain-L3out association for communication outside a network
US10812315B2 (en) 2018-06-07 2020-10-20 Cisco Technology, Inc. Cross-domain network assurance
US10812318B2 (en) 2017-05-31 2020-10-20 Cisco Technology, Inc. Associating network policy objects with specific faults corresponding to fault localizations in large-scale network deployment
US10826770B2 (en) 2018-07-26 2020-11-03 Cisco Technology, Inc. Synthesis of models for networks using automated boolean learning
US10826788B2 (en) 2017-04-20 2020-11-03 Cisco Technology, Inc. Assurance of quality-of-service configurations in a network
US10873509B2 (en) 2018-01-17 2020-12-22 Cisco Technology, Inc. Check-pointing ACI network state and re-execution from a check-pointed state
US10904101B2 (en) 2017-06-16 2021-01-26 Cisco Technology, Inc. Shim layer for extracting and prioritizing underlying rules for modeling network intents
US10904070B2 (en) 2018-07-11 2021-01-26 Cisco Technology, Inc. Techniques and interfaces for troubleshooting datacenter networks
US10911495B2 (en) 2018-06-27 2021-02-02 Cisco Technology, Inc. Assurance of security rules in a network
US11019027B2 (en) 2018-06-27 2021-05-25 Cisco Technology, Inc. Address translation for external network appliance
US11044273B2 (en) 2018-06-27 2021-06-22 Cisco Technology, Inc. Assurance of security rules in a network
US11102053B2 (en) 2017-12-05 2021-08-24 Cisco Technology, Inc. Cross-domain assurance
US11121927B2 (en) 2017-06-19 2021-09-14 Cisco Technology, Inc. Automatically determining an optimal amount of time for analyzing a distributed network environment
US11150973B2 (en) 2017-06-16 2021-10-19 Cisco Technology, Inc. Self diagnosing distributed appliance
US11218508B2 (en) 2018-06-27 2022-01-04 Cisco Technology, Inc. Assurance of security rules in a network
US11258657B2 (en) 2017-05-31 2022-02-22 Cisco Technology, Inc. Fault localization in large-scale network policy deployment
US11283680B2 (en) 2017-06-19 2022-03-22 Cisco Technology, Inc. Identifying components for removal in a network configuration
US11343150B2 (en) 2017-06-19 2022-05-24 Cisco Technology, Inc. Validation of learned routes in a network
US11469986B2 (en) 2017-06-16 2022-10-11 Cisco Technology, Inc. Controlled micro fault injection on a distributed appliance
US11645131B2 (en) 2017-06-16 2023-05-09 Cisco Technology, Inc. Distributed fault code aggregation across application centric dimensions

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108882263A (zh) * 2017-05-08 2018-11-23 中兴通讯股份有限公司 一种基站运维方法和装置
CN113778884A (zh) * 2021-09-14 2021-12-10 北京爱芯科技有限公司 一种仿真调试方法、装置、计算设备以及计算机存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011113467A1 (en) * 2010-03-15 2011-09-22 Nokia Siemens Networks Oy Relay nodes
CN102711160A (zh) * 2012-05-21 2012-10-03 中兴通讯股份有限公司 信息配置方法及装置
WO2014075233A1 (zh) * 2012-11-14 2014-05-22 华为技术有限公司 维护基站的方法、设备及系统
CN104754629A (zh) * 2013-12-31 2015-07-01 中兴通讯股份有限公司 一种基站设备自愈的实现方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011113467A1 (en) * 2010-03-15 2011-09-22 Nokia Siemens Networks Oy Relay nodes
CN102711160A (zh) * 2012-05-21 2012-10-03 中兴通讯股份有限公司 信息配置方法及装置
WO2014075233A1 (zh) * 2012-11-14 2014-05-22 华为技术有限公司 维护基站的方法、设备及系统
CN104754629A (zh) * 2013-12-31 2015-07-01 中兴通讯股份有限公司 一种基站设备自愈的实现方法及装置

Cited By (97)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11824719B2 (en) 2014-10-16 2023-11-21 Cisco Technology, Inc. Discovering and grouping application endpoints in a network environment
US11811603B2 (en) 2014-10-16 2023-11-07 Cisco Technology, Inc. Discovering and grouping application endpoints in a network environment
US10797951B2 (en) 2014-10-16 2020-10-06 Cisco Technology, Inc. Discovering and grouping application endpoints in a network environment
US11539588B2 (en) 2014-10-16 2022-12-27 Cisco Technology, Inc. Discovering and grouping application endpoints in a network environment
US10623264B2 (en) 2017-04-20 2020-04-14 Cisco Technology, Inc. Policy assurance for service chaining
US10826788B2 (en) 2017-04-20 2020-11-03 Cisco Technology, Inc. Assurance of quality-of-service configurations in a network
US10560328B2 (en) 2017-04-20 2020-02-11 Cisco Technology, Inc. Static network policy analysis for networks
US11178009B2 (en) 2017-04-20 2021-11-16 Cisco Technology, Inc. Static network policy analysis for networks
US11258657B2 (en) 2017-05-31 2022-02-22 Cisco Technology, Inc. Fault localization in large-scale network policy deployment
US10951477B2 (en) 2017-05-31 2021-03-16 Cisco Technology, Inc. Identification of conflict rules in a network intent formal equivalence failure
US10505816B2 (en) 2017-05-31 2019-12-10 Cisco Technology, Inc. Semantic analysis to detect shadowing of rules in a model of network intents
US11411803B2 (en) 2017-05-31 2022-08-09 Cisco Technology, Inc. Associating network policy objects with specific faults corresponding to fault localizations in large-scale network deployment
US11303531B2 (en) 2017-05-31 2022-04-12 Cisco Technologies, Inc. Generation of counter examples for network intent formal equivalence failures
US10623271B2 (en) 2017-05-31 2020-04-14 Cisco Technology, Inc. Intra-priority class ordering of rules corresponding to a model of network intents
US10693738B2 (en) 2017-05-31 2020-06-23 Cisco Technology, Inc. Generating device-level logical models for a network
US10439875B2 (en) 2017-05-31 2019-10-08 Cisco Technology, Inc. Identification of conflict rules in a network intent formal equivalence failure
US10812318B2 (en) 2017-05-31 2020-10-20 Cisco Technology, Inc. Associating network policy objects with specific faults corresponding to fault localizations in large-scale network deployment
US10554483B2 (en) 2017-05-31 2020-02-04 Cisco Technology, Inc. Network policy analysis for networks
US10581694B2 (en) 2017-05-31 2020-03-03 Cisco Technology, Inc. Generation of counter examples for network intent formal equivalence failures
US11463316B2 (en) 2017-06-16 2022-10-04 Cisco Technology, Inc. Topology explorer
US11102337B2 (en) 2017-06-16 2021-08-24 Cisco Technology, Inc. Event generation in response to network intent formal equivalence failures
US10904101B2 (en) 2017-06-16 2021-01-26 Cisco Technology, Inc. Shim layer for extracting and prioritizing underlying rules for modeling network intents
US10574513B2 (en) 2017-06-16 2020-02-25 Cisco Technology, Inc. Handling controller and node failure scenarios during data collection
US11563645B2 (en) 2017-06-16 2023-01-24 Cisco Technology, Inc. Shim layer for extracting and prioritizing underlying rules for modeling network intents
US11469986B2 (en) 2017-06-16 2022-10-11 Cisco Technology, Inc. Controlled micro fault injection on a distributed appliance
US11150973B2 (en) 2017-06-16 2021-10-19 Cisco Technology, Inc. Self diagnosing distributed appliance
US10587621B2 (en) 2017-06-16 2020-03-10 Cisco Technology, Inc. System and method for migrating to and maintaining a white-list network security model
US11645131B2 (en) 2017-06-16 2023-05-09 Cisco Technology, Inc. Distributed fault code aggregation across application centric dimensions
US10498608B2 (en) 2017-06-16 2019-12-03 Cisco Technology, Inc. Topology explorer
US10547715B2 (en) 2017-06-16 2020-01-28 Cisco Technology, Inc. Event generation in response to network intent formal equivalence failures
US10686669B2 (en) 2017-06-16 2020-06-16 Cisco Technology, Inc. Collecting network models and node information from a network
US11283682B2 (en) 2017-06-19 2022-03-22 Cisco Technology, Inc. Validation of bridge domain-L3out association for communication outside a network
US10554493B2 (en) 2017-06-19 2020-02-04 Cisco Technology, Inc. Identifying mismatches between a logical model and node implementation
US10652102B2 (en) 2017-06-19 2020-05-12 Cisco Technology, Inc. Network node memory utilization analysis
US10333787B2 (en) 2017-06-19 2019-06-25 Cisco Technology, Inc. Validation of L3OUT configuration for communications outside a network
US10673702B2 (en) 2017-06-19 2020-06-02 Cisco Technology, Inc. Validation of layer 3 using virtual routing forwarding containers in a network
US10623259B2 (en) 2017-06-19 2020-04-14 Cisco Technology, Inc. Validation of layer 1 interface in a network
US11750463B2 (en) 2017-06-19 2023-09-05 Cisco Technology, Inc. Automatically determining an optimal amount of time for analyzing a distributed network environment
US10700933B2 (en) 2017-06-19 2020-06-30 Cisco Technology, Inc. Validating tunnel endpoint addresses in a network fabric
US11736351B2 (en) 2017-06-19 2023-08-22 Cisco Technology Inc. Identifying components for removal in a network configuration
US10805160B2 (en) 2017-06-19 2020-10-13 Cisco Technology, Inc. Endpoint bridge domain subnet validation
US10812336B2 (en) 2017-06-19 2020-10-20 Cisco Technology, Inc. Validation of bridge domain-L3out association for communication outside a network
US10341184B2 (en) 2017-06-19 2019-07-02 Cisco Technology, Inc. Validation of layer 3 bridge domain subnets in in a network
US11595257B2 (en) 2017-06-19 2023-02-28 Cisco Technology, Inc. Validation of cross logical groups in a network
US11570047B2 (en) 2017-06-19 2023-01-31 Cisco Technology, Inc. Detection of overlapping subnets in a network
US10348564B2 (en) 2017-06-19 2019-07-09 Cisco Technology, Inc. Validation of routing information base-forwarding information base equivalence in a network
US10862752B2 (en) 2017-06-19 2020-12-08 Cisco Technology, Inc. Network validation between the logical level and the hardware level of a network
US11558260B2 (en) 2017-06-19 2023-01-17 Cisco Technology, Inc. Network node memory utilization analysis
US10873505B2 (en) 2017-06-19 2020-12-22 Cisco Technology, Inc. Validation of layer 2 interface and VLAN in a networked environment
US10873506B2 (en) 2017-06-19 2020-12-22 Cisco Technology, Inc. Validation of a virtual port channel (VPC) endpoint in the network fabric
US10880169B2 (en) 2017-06-19 2020-12-29 Cisco Technology, Inc. Multiprotocol border gateway protocol routing validation
US10567229B2 (en) 2017-06-19 2020-02-18 Cisco Technology, Inc. Validating endpoint configurations between nodes
US10411996B2 (en) 2017-06-19 2019-09-10 Cisco Technology, Inc. Validation of routing information in a network fabric
US11469952B2 (en) 2017-06-19 2022-10-11 Cisco Technology, Inc. Identifying mismatches between a logical model and node implementation
US10567228B2 (en) 2017-06-19 2020-02-18 Cisco Technology, Inc. Validation of cross logical groups in a network
US10972352B2 (en) 2017-06-19 2021-04-06 Cisco Technology, Inc. Validation of routing information base-forwarding information base equivalence in a network
US10432467B2 (en) 2017-06-19 2019-10-01 Cisco Technology, Inc. Network validation between the logical level and the hardware level of a network
US10437641B2 (en) 2017-06-19 2019-10-08 Cisco Technology, Inc. On-demand processing pipeline interleaved with temporal processing pipeline
US11438234B2 (en) 2017-06-19 2022-09-06 Cisco Technology, Inc. Validation of a virtual port channel (VPC) endpoint in the network fabric
US11063827B2 (en) 2017-06-19 2021-07-13 Cisco Technology, Inc. Validation of layer 3 bridge domain subnets in a network
US10560355B2 (en) 2017-06-19 2020-02-11 Cisco Technology, Inc. Static endpoint validation
US10528444B2 (en) 2017-06-19 2020-01-07 Cisco Technology, Inc. Event generation in response to validation between logical level and hardware level
US11102111B2 (en) 2017-06-19 2021-08-24 Cisco Technology, Inc. Validation of routing information in a network fabric
US11405278B2 (en) 2017-06-19 2022-08-02 Cisco Technology, Inc. Validating tunnel endpoint addresses in a network fabric
US11121927B2 (en) 2017-06-19 2021-09-14 Cisco Technology, Inc. Automatically determining an optimal amount of time for analyzing a distributed network environment
US10644946B2 (en) 2017-06-19 2020-05-05 Cisco Technology, Inc. Detection of overlapping subnets in a network
US11153167B2 (en) 2017-06-19 2021-10-19 Cisco Technology, Inc. Validation of L3OUT configuration for communications outside a network
US11343150B2 (en) 2017-06-19 2022-05-24 Cisco Technology, Inc. Validation of learned routes in a network
US11303520B2 (en) 2017-06-19 2022-04-12 Cisco Technology, Inc. Validation of cross logical groups in a network
US10547509B2 (en) 2017-06-19 2020-01-28 Cisco Technology, Inc. Validation of a virtual port channel (VPC) endpoint in the network fabric
US11283680B2 (en) 2017-06-19 2022-03-22 Cisco Technology, Inc. Identifying components for removal in a network configuration
US10218572B2 (en) 2017-06-19 2019-02-26 Cisco Technology, Inc. Multiprotocol border gateway protocol routing validation
US10536337B2 (en) 2017-06-19 2020-01-14 Cisco Technology, Inc. Validation of layer 2 interface and VLAN in a networked environment
US11038743B2 (en) 2017-09-12 2021-06-15 Cisco Technology, Inc. Event clustering for a network assurance platform
US10587484B2 (en) 2017-09-12 2020-03-10 Cisco Technology, Inc. Anomaly detection and reporting in a network assurance appliance
US11115300B2 (en) 2017-09-12 2021-09-07 Cisco Technology, Inc Anomaly detection and reporting in a network assurance appliance
US10587456B2 (en) 2017-09-12 2020-03-10 Cisco Technology, Inc. Event clustering for a network assurance platform
US10554477B2 (en) 2017-09-13 2020-02-04 Cisco Technology, Inc. Network assurance event aggregator
US10333833B2 (en) 2017-09-25 2019-06-25 Cisco Technology, Inc. Endpoint path assurance
US11102053B2 (en) 2017-12-05 2021-08-24 Cisco Technology, Inc. Cross-domain assurance
US10873509B2 (en) 2018-01-17 2020-12-22 Cisco Technology, Inc. Check-pointing ACI network state and re-execution from a check-pointed state
US11824728B2 (en) 2018-01-17 2023-11-21 Cisco Technology, Inc. Check-pointing ACI network state and re-execution from a check-pointed state
US10572495B2 (en) 2018-02-06 2020-02-25 Cisco Technology Inc. Network assurance database version compatibility
US10812315B2 (en) 2018-06-07 2020-10-20 Cisco Technology, Inc. Cross-domain network assurance
US11374806B2 (en) 2018-06-07 2022-06-28 Cisco Technology, Inc. Cross-domain network assurance
US11902082B2 (en) 2018-06-07 2024-02-13 Cisco Technology, Inc. Cross-domain network assurance
US11019027B2 (en) 2018-06-27 2021-05-25 Cisco Technology, Inc. Address translation for external network appliance
US11044273B2 (en) 2018-06-27 2021-06-22 Cisco Technology, Inc. Assurance of security rules in a network
US10911495B2 (en) 2018-06-27 2021-02-02 Cisco Technology, Inc. Assurance of security rules in a network
US11218508B2 (en) 2018-06-27 2022-01-04 Cisco Technology, Inc. Assurance of security rules in a network
US10659298B1 (en) 2018-06-27 2020-05-19 Cisco Technology, Inc. Epoch comparison for network events
US11888603B2 (en) 2018-06-27 2024-01-30 Cisco Technology, Inc. Assurance of security rules in a network
US11909713B2 (en) 2018-06-27 2024-02-20 Cisco Technology, Inc. Address translation for external network appliance
US11805004B2 (en) 2018-07-11 2023-10-31 Cisco Technology, Inc. Techniques and interfaces for troubleshooting datacenter networks
US10904070B2 (en) 2018-07-11 2021-01-26 Cisco Technology, Inc. Techniques and interfaces for troubleshooting datacenter networks
US10826770B2 (en) 2018-07-26 2020-11-03 Cisco Technology, Inc. Synthesis of models for networks using automated boolean learning
US10616072B1 (en) 2018-07-27 2020-04-07 Cisco Technology, Inc. Epoch data interface

Also Published As

Publication number Publication date
CN106488487A (zh) 2017-03-08

Similar Documents

Publication Publication Date Title
WO2017031922A1 (zh) 故障检测方法及装置
EP3617886B1 (en) Hot backup system, hot backup method, and computer device
CN108847982B (zh) 一种分布式存储集群及其节点故障切换方法和装置
JP6291248B2 (ja) ファームウェアアップグレードエラー検出および自動ロールバック
CN110647580A (zh) 分布式容器集群镜像管理主节点、从节点、系统及方法
CN105933407B (zh) 一种实现Redis集群高可用的方法及系统
CN107634860B (zh) 一种weblogic集群补丁批量自动升级方法
CN108429629A (zh) 设备故障恢复方法和装置
CN107404522B (zh) 一种跨节点的虚拟机集群高可用实现方法和装置
CN108459951B (zh) 测试方法和装置
WO2018006702A1 (zh) 自动化测试中的异常处理方法、装置及系统
CN111901176B (zh) 故障确定方法、装置、设备及存储介质
CN106533751B (zh) 一种sdn控制器集群合并方法及装置
CN104158843A (zh) 分布式文件存储系统的存储单元失效检测方法及装置
CN111880947A (zh) 一种数据传输方法及装置
CN103532748B (zh) 一种drbd脑裂的处理方法及装置
US10904300B2 (en) Method and device for managing user information
CN105630626B (zh) 事务备份处理方法及装置
CN111078454A (zh) 一种云平台配置恢复方法及装置
CN106411643A (zh) Bmc检测方法以及装置
CN107590647A (zh) 船舶管理系统的伺服监管系统
CN101242201B (zh) 一种主备系统维护的方法、系统和装置
CN113987065A (zh) 数据库漂移方法、系统、电子设备和存储介质
CN113179180A (zh) 一种玄武盾客户端灾难故障修复方法、装置和存储介质
CN111400094A (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: 16838191

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

Country of ref document: EP

Kind code of ref document: A1