CN105991332A - Alarm processing method and device - Google Patents
Alarm processing method and device Download PDFInfo
- Publication number
- CN105991332A CN105991332A CN201510088503.3A CN201510088503A CN105991332A CN 105991332 A CN105991332 A CN 105991332A CN 201510088503 A CN201510088503 A CN 201510088503A CN 105991332 A CN105991332 A CN 105991332A
- Authority
- CN
- China
- Prior art keywords
- alarm
- business
- resource
- controller management
- shared
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present invention discloses an alarm processing method and device. The method comprises: a controller receives an alarm from a network device; the controller analyzes the alarm to obtain analysis results; and the controller processes the alarm according to the analysis results. The problems are solved that the alarm process is not in time and the performance of an upper-level network device is low in the condition of having a lot of alarm processes, and therefore the alarm is effectively and timely processed.
Description
Technical field
The present invention relates to the communications field, in particular to a kind of alert processing method and device.
Background technology
In communication network, network is made up of many communication apparatus nodes, and these network nodes are called network element.Net
It is attached by communication line between Yuan, the various ways such as including fiber optic cables.Network element then dispersed distribution is respectively
Individual area, in the laboratory, communication building in city having, some network elements are in remote districts.But these nets
The equipment of unit needs to configure, and safeguards and monitors, it is impossible to often locates all to send someone on duty, thus needs one
Central site network management system, centre machine room, by telecommunication, each node on network is configured,
Safeguard and monitoring.
Can be realized by a kind of emerging network management control system by controller management network.At this
In control system, in traditional network management to the control functional independence of service resources out, be solely focused on service resources.
Controller can be by tree-shaped stratification tissue, in order to association large scale network.Wherein, direct managed network element can
With referred to as domain controller (Domain Controller, or D-Controller, referred to as DC)；And upper strata
The direct managed network element of controller (Super Controller, or S-Controller, referred to as SC),
But management domain controller, the virtual network management then being provided by domain controller again, it is achieved to real network
Management.Fig. 1 is the networking schematic diagram using controller management and control network in correlation technique, as it is shown in figure 1,
In one application scenarios, controller forms tree-like management system, and upper strata is SC, and the DC of bottom divides management
Territory, management communication network and network element.Controller is managed by interface except south orientation and the network equipment, also has
Northbound interface can allow network AP P (Application) access of application layer carry out network management, can also lead to
Cross side interface, (include: Element management system (Element Management System, letter with webmaster plane
It is referred to as EMS), NMS (Network Management System, referred to as NMS), or
Operation support system (Operation Support System, referred to as OSS)) communication management information.Network
APP is the practical business application of network, and the resource using controller to provide, the business that sends is set up, and deletes, repaiies
The request changing.And controller is set up according to the request of network AP P, delete, change business, and to business
Alarm, monitoring performance.Fig. 2 be software defined network in correlation technique (Software Defined Network,
Referred to as SDN) relation schematic diagram between network central control device and other network entities, as in figure 2 it is shown,
DC directly manages communication network, and SC manages DC, can also hand over legacy network management system simultaneously
Stream, can finally be provided to APP provides resource and service.
In network actual moving process, can be potentially encountered fault, or receive interference and communication quality declines.One
Denier sends this situation, and the network equipment will report police.Owing to the direct communication of the network equipment is close association,
One equipment or the faulty report and alarm of a part of resource, will cause network large area to produce alarm.Produce
Very many alarm amounts.For network manager, it is difficulty that real failure cause is found out in so many alarms
's.The appearance of a fault in network can cause the alarm of direct this fault of reflection, simultaneously because fault shadow
Ring and arrive other equipment or business, a series of alarm can be caused.For example, alert A and caused alarm B, accuse
Alert A is Root alarm, and alarm B is derivative alarm.
In traditional network, alarm all produces at equipment, and network controller directly will after receiving alarm
Alarm is transmitted to process the upper layer network equipment of alarm, thus in the related, does not only exist alarming processing not
In time, and in the case that alarm quantity is many, the problem that upper layer network equipment performance is low is caused.
Content of the invention
The invention provides a kind of alert processing method and device, at least to solve in correlation technique, do not only exist
Alarming processing not in time, and in the case that alarm quantity is many, causes low the asking of upper layer network equipment performance
Topic.
According to an aspect of the invention, it is provided a kind of alert processing method, comprising: controller receives and arrives
The alarm of automatic network equipment；Described alarm is analyzed drawing analysis result by described controller；Described controller
According to described analysis result, described alarm is processed.
Preferably, described controller be analyzed to described alarm obtaining described analysis result include following at least it
One: according to the alarm cause producing described alarm, analyze the business drawing described alarm whether to controller management
Produce the described analysis result of impact；Business institute according to the resource with described controller management producing described alarm
The relation between resource taking, analyzes and show that whether the described business of described controller management is produced by described alarm
The described analysis result of raw impact.
Preferably, according to the resource with described controller management producing described alarm the resource shared by business it
Between relation, analyze and show that whether the described business of described controller management is produced described in impact by described alarm
Analysis result includes one below: producing the Root Resource of described alarm not by the business institute of described controller management
Take, and also there is no the corresponding child resource of described Root Resource by the feelings shared by the business of described controller management
Under condition, determine that described alarm does not produce impact to the described business of described controller management；Producing described alarm
Root Resource not by shared by the business of described controller management, but the corresponding child resource of described Root Resource is described
In the case of shared by the business of controller management, determine the described business to described controller management for the described alarm
Produce impact；Producing the Root Resource of described alarm not by shared by the business of described controller management, described
The corresponding child resource of resource is not also by shared by the business of described controller management, but described Root Resource and/or institute
In the case that the business of the corresponding child resource of Root Resource and described controller management stated exists mapping relations, determine institute
State and alert the generation impact of the described business on described controller management；Described at the Root Resource producing described alarm
In the case of shared by the business of controller management, determine the described business to described controller management for the described alarm
Produce impact.
Preferably, described controller carries out process according to described analysis result and includes one below to described alarm:
According to described alarm cause, analyze and show that described alarm does not produce impact to the business of described controller management
In the case of, described alarm is suppressed；According to the resource producing described alarm and described controller management
The relation between resource shared by business determines that the described business to described controller management for the described alarm is not produced
In the case that life affects, described alarm is suppressed；Producing the Root Resource of described alarm not by described control
Shared by the business of device management, but the corresponding child resource of described Root Resource is by shared by the business of described controller management
With in the case of, described alarm is derived for the derivative alarm of child resource；Produce the Root Resource of described alarm not by
Shared by the business of described controller management, the corresponding child resource of described Root Resource is not also by described controller management
Business shared by, but described Root Resource and/or the corresponding child resource of described Root Resource and described controller management
Business in the case of there are mapping relations, according to described mapping relations, described alarm is derived and derives for relation
Alarm；Producing the Root Resource of described alarm by the case of shared by the business of described controller management, directly
By described alarm report to upper layer network equipment.
Preferably, in the case that derivation process is carried out to described alarm, also include: record described alarm and spread out
The incidence relation between derivative alarm after life, wherein, described derivative alarm includes: the derivative alarm of child resource and
/ or the derivative alarm of relation；Described derivative alarm and described incidence relation are reported upper layer network equipment, and/
Or provide described incidence relation for the network element device inquiry in described controller managing system.
Preferably, after described alarm is processed by described controller according to described analysis result, also include:
Change according to the state of the network element device caused by described alarm, or the object of the representative resource of described alarm
State changes, and generates described network element device or the state notifying of the described object representing resource；The institute that will generate
State network element device or the state notifying of the described object representing resource reports upper layer network equipment.
According to a further aspect in the invention, provide a kind of alarm treatment device, be applied to controller, comprising:
Receiver module, for receiving the alarm from the network equipment；Analyze module, for carrying out described alarm point
Analysis draws analysis result；Processing module, for processing to described alarm according to described analysis result.
Preferably, described analysis module includes at least one of: the first analytic unit, for according to producing institute
State the alarm cause of alarm, analyze and show whether described alarm produces described in impact on the business of controller management
Analysis result；Second analytic unit, for the industry according to the resource with described controller management producing described alarm
Relation between the shared resource of business, analyzes the described industry drawing described alarm whether to described controller management
Business produces the described analysis result of impact.
Preferably, described second analytic unit includes one below: first determines subelement, for producing institute
State the Root Resource of alarm not by shared by the business of described controller management, and also do not have described Root Resource corresponding
Child resource by the case of shared by the business of described controller management, determine described alarm to described controller
The described business of management does not produce impact；Second determination subelement, for producing the Root Resource of described alarm not
By shared by the business of described controller management, but the corresponding child resource of described Root Resource is by described controller management
Business shared by the case of, determine that described alarm produces impact to the described business of described controller management；
3rd determination subelement, for producing the Root Resource of described alarm not by shared by the business of described controller management
With, the corresponding child resource of described Root Resource also not by shared by the business of described controller management, but described money
There is the situation of mapping relations in the business of source and/or the corresponding child resource of described Root Resource and described controller management
Under, determine that described alarm produces impact to the described business of described controller management；4th determination subelement, uses
In the Root Resource in the described alarm of generation by the case of shared by the business of described controller management, determine described
The described business on described controller management for the alarm produces impact.
Preferably, described processing module includes one below: first suppresses unit, for according to described alarm
Reason, analyzes and show that the business of described controller management is not produced in the case of affect by described alarm, to described
Alarm suppresses；Second suppression unit, for according to the resource producing described alarm and described controller pipe
Relation between the resource shared by business of reason determines the described business to described controller management for the described alarm
Do not produce in the case of affect, described alarm is suppressed；First derived units, for producing described announcement
Alert Root Resource is not by shared by the business of described controller management, but the corresponding child resource of described Root Resource is by institute
In the case of stating shared by the business of controller management, described alarm is derived for the derivative alarm of child resource；Second
Derived units, for producing the Root Resource of described alarm not by shared by the business of described controller management, institute
State the corresponding child resource of Root Resource also not by shared by the business of described controller management, but described Root Resource and/
Or the business of the corresponding child resource of described Root Resource and described controller management is in the case of exist mapping relations, depend on
According to described mapping relations, described alarm is derived for the derivative alarm of relation；First reports unit, for producing
The Root Resource of described alarm is by the case of shared by the business of described controller management, directly by described alarm
Offer upper layer network equipment.
Preferably, this processing module also includes: record unit, for carrying out derivation process to described alarm
In the case of, the incidence relation between derivative alarm after recording described alarm and deriving, wherein, described derivative announcement
Police includes: the derivative alarm of child resource and/or the derivative alarm of relation；Second reports unit, for deriving described
Alarm and described incidence relation report upper layer network equipment, and/or, unit is provided, is used for providing described
Incidence relation is for the network element device inquiry in described controller managing system.
Preferably, this device also includes: generation module, for the network element device caused according to described alarm
State change, or the object of the representative resource of described alarm state change, generate described network element device or
The state notifying of the described object representing resource；Reporting module, is used for described network element device or the institute that will generate
The state notifying stating the object representing resource reports upper layer network equipment.
Preferably, described controller includes at least one of: domain controller DC, super controller SC,
Wherein, described SC is the top level control device of described DC.
By the present invention, controller is used to receive the alarm from the network equipment；Described controller is to described announcement
Police is analyzed drawing analysis result；Described alarm is processed by described controller according to described analysis result,
Solve in correlation technique, do not only exist alarming processing not in time, and in the case that alarm quantity is many, make
Become the problem that upper layer network equipment performance is low, and then reach efficiently to process in time the effect of alarm.
Brief description
Accompanying drawing described herein is used for providing a further understanding of the present invention, constitutes the part of the application,
The schematic description and description of the present invention is used for explaining the present invention, is not intended that inappropriate limitation of the present invention.
In the accompanying drawings:
Fig. 1 is the networking schematic diagram using controller management and control network in correlation technique；
Fig. 2 is the relation schematic diagram in correlation technique between SDN middle controller and other network entities；
Fig. 3 is the flow chart of alert processing method according to embodiments of the present invention；
Fig. 4 is the structured flowchart of alarm treatment device according to embodiments of the present invention；
Fig. 5 is the preferred structure block diagram analyzing module 44 in alarm treatment device according to embodiments of the present invention；
Fig. 6 is to analyze the second analytic unit 54 in module 44 in alarm treatment device according to embodiments of the present invention
Preferred structure block diagram；
Fig. 7 is the preferred structure block diagram one of processing module 46 in alarm treatment device according to embodiments of the present invention；
Fig. 8 is the preferred structure block diagram two of processing module 46 in alarm treatment device according to embodiments of the present invention；
Fig. 9 is the preferred structure block diagram of alarm treatment device according to embodiments of the present invention；
Figure 10 is the structural representation of controller alert analysis module according to embodiments of the present invention；
Figure 11 is the schematic diagram that the alarm report according to the preferred embodiment of the present invention one is processed；
Figure 12 is the schematic diagram that the alarm report according to the preferred embodiment of the present invention two is processed.
Detailed description of the invention
Below with reference to accompanying drawing and describe the present invention in detail in conjunction with the embodiments.It should be noted that do not rushing
In the case of prominent, the embodiment in the application and the feature in embodiment can be mutually combined.
Providing a kind of alert processing method in the present embodiment, Fig. 3 is at alarm according to embodiments of the present invention
The flow chart of reason method, as it is shown on figure 3, this flow process comprises the steps:
Step S302, controller receives the alarm from the network equipment, it should be noted that this network sets
The standby network element device itself that can be to produce this alarm, it is also possible to be controller equiment；
Step S304, alarm is analyzed drawing analysis result by this controller；
Step S306, alarm is processed by this controller according to analysis result.
It by above-mentioned steps, is analyzed processing to the alarm receiving by controller, solves correlation technique
In, do not only exist alarming processing not in time, and in the case that alarm quantity is many, cause upper layer network equipment
The problem of degraded performance, and then reached efficiently to process in time the effect of alarm.
Preferably, when controller is analyzed obtaining analysis result to alarm, different analysis foundations is used, point
The result of analysis also can be different, for example, it is possible to according to the alarm cause producing alarm, analyze and whether draw alarm
Business on controller management produces the analysis result of impact；Also can be according to the resource producing alarm and controller
Relation between the resource shared by business of management, analyzes and show that whether the business of controller management is produced by alarm
The analysis result of raw impact.
Relation between the resource shared by the business according to the resource and controller management that produce alarm, analyzes
When drawing the analysis result that the business whether on controller management for the alarm produces impact, one below can be included:
It is not controlled by shared by the business that device manages at the Root Resource producing alarm, and also do not have the corresponding son of Root Resource
Resource, by the case of shared by the business of controller management, determines that the business of controller management is not produced by alarm
Impact；It is not controlled by shared by the business that device manages at the Root Resource producing alarm, but the corresponding sub-money of Root Resource
Source, by the case of shared by the business of controller management, determines that alarm produces impact to the business of controller management；
Produce alarm Root Resource be not controlled by device management business shared by, the corresponding child resource of Root Resource also not by
Shared by the business of controller management, but Root Resource and/or the corresponding child resource of Root Resource and controller management
In the case that business exists mapping relations, determine that alarm produces impact to the business of controller management；Accuse producing
Alert Root Resource, by the case of shared by the business of controller management, determines the business to controller management for the alarm
Produce impact.
When alarm is processed by controller according to analysis result, according to the difference of analysis result, to this alert into
Row processes also different, is exemplified below: can carry out suppression process to alarm: for example in a case where,
According to alarm cause, analyze and show that the business of controller management is not produced in the case of affect by alarm, to announcement
Police suppresses；Again for example, in the resource shared by the business according to the resource with controller management that produce alarm
Between relation determine that the business of controller management is not produced in the case of affect by alarm, alarm is suppressed；
Derivation process can be carried out to this alarm: for example in a case where, not controlled at the Root Resource producing alarm
Shared by the business of device processed management, but the corresponding child resource of Root Resource is by the feelings shared by the business of controller management
Under condition, alarm is derived for the derivative alarm of child resource；Again for example, it is not controlled by device at the Root Resource producing alarm
Shared by the business of management, the corresponding child resource of Root Resource is also not controlled by shared by the business of device management, but root
In the case that the business of resource and/or the corresponding child resource of Root Resource and controller management exists mapping relations, depend on
According to mapping relations, alarm is derived for the derivative alarm of relation；In addition, producing the Root Resource of alarm by controller
In the case of shared by the business of management, directly by alarm report to upper layer network equipment.It should be noted that
Upper layer network equipment herein is a relative concept, for example, when controller DC receives this alarm, and should
Upper layer network equipment is i.e. the upper layer network equipment SC of this controller DC, more for example, when upper layer network equipment
When SC receives this alarm, this upper layer network equipment is i.e. the upper layer network equipment NMS of this SC.
It should be noted that in the case that derivation process is carried out to alarm, all right: record alerts and derives
After derivative alarm between incidence relation, wherein, derivative alarm includes: the derivative alarm of child resource and/or close
The derivative alarm of system；Derivative alarm and incidence relation are reported upper layer network equipment, and/or provides association to close
System is for the network element device inquiry in controller managing system.
In addition, after processing alarm according to analysis result, following process can also be included: according to announcement
The state change of alert caused network element device, or the state change of the object of the representative resource of alarm, generate
Network element device or the state notifying of object representing resource；By the network element device of generation or represent the right of resource
The state notifying of elephant reports upper layer network equipment.
Additionally providing a kind of alarm treatment device in the present embodiment, this device is used for realizing above-described embodiment and excellent
Select embodiment, carry out repeating no more of explanation.As used below, term " module " is permissible
Realize the software of predetermined function and/or the combination of hardware.Although the device described by following example preferably with
Software realizes, but hardware, or the realization of the combination of software and hardware is also may and to be contemplated.
Fig. 4 is the structured flowchart of alarm treatment device according to embodiments of the present invention, as shown in Figure 4, and this device
Can apply to controller, including the 42nd, receiver module analyzes module 44 and processing module 46, below to this dress
Put and illustrate.
Receiver module 42, for receiving the alarm from the network equipment；Analyze module 44, be connected to above-mentioned
Receiver module 42, for being analyzed drawing analysis result to alarm；Processing module 46, is connected to above-mentioned point
Analysis module 44, for processing to alarm according to analysis result.
Fig. 5 is the preferred structure block diagram analyzing module 44 in alarm treatment device according to embodiments of the present invention,
As it is shown in figure 5, this analysis module 44 includes at least one of: the 52nd, the first analytic unit second analyzes list
Unit 54, illustrates to this analysis module 44 below.
Whether the first analytic unit 52, for according to the alarm cause producing alarm, analyze and draw alarm to control
The business of device processed management produces the analysis result of impact；Second analytic unit 54, for according to generation alarm
Whether the relation between resource shared by the business of resource and controller management, analyze and draw alarm to controller
The business of management produces the analysis result of impact.
Fig. 6 is to analyze the second analytic unit 54 in module 44 in alarm treatment device according to embodiments of the present invention
Preferred structure block diagram, as shown in Figure 6, this second analytic unit 54 includes one below: first determines son
Unit the 62nd, second determination subelement the 64th, the 3rd determination subelement the 66th, the 4th determination subelement 68, below right
This second analytic unit 54 illustrates.
First determination subelement 62, for being not controlled by shared by the business that device manages at the Root Resource producing alarm
With, and there is no the corresponding child resource of Root Resource by the case of shared by the business of controller management yet, determine
Alarm does not produce impact to the business of controller management；Second determination subelement 64, for producing alarm
Root Resource is not controlled by shared by the business of device management, but the corresponding child resource of Root Resource is by the industry of controller management
In the case that business is shared, determine that alarm produces impact to the business of controller management；3rd determination subelement
66, for being not controlled by shared by the business that device manages at the Root Resource producing alarm, the corresponding sub-money of Root Resource
Source is also not controlled by shared by the business of device management, but Root Resource and/or the corresponding child resource of Root Resource and control
In the case that the business of device management exists mapping relations, determine that alarm produces impact to the business of controller management；
4th determination subelement 68, for producing the Root Resource of alarm by the feelings shared by the business of controller management
Under condition, determine that alarm produces impact to the business of controller management.
Fig. 7 is the preferred structure block diagram one of processing module 46 in alarm treatment device according to embodiments of the present invention,
As it is shown in fig. 7, this processing module 46 includes one below: the first suppression unit the 70th, the second suppression unit is the 72nd,
The 76th, first derived units the 74th, the second derived units first reports unit 78, below to this processing module 46
Illustrate.
First suppression unit 70, for according to alarm cause, analyzing the industry drawing alarm to controller management
Business does not produce in the case of impact, suppresses alarm；Second suppression unit 72, for according to generation
Relation between the resource of alarm and the resource shared by business of controller management determines alarm to controller pipe
The business of reason does not produce in the case of impact, suppresses alarm；First derived units 74, for producing
The Root Resource of raw alarm is not controlled by shared by the business of device management, but the corresponding child resource of Root Resource is by controller
In the case of shared by the business of management, alarm is derived for the derivative alarm of child resource；Second derived units 76,
For being not controlled by shared by the business that device manages at the Root Resource producing alarm, the corresponding child resource of Root Resource is also
It is not controlled by shared by the business of device management, but Root Resource and/or the corresponding child resource of Root Resource and controller pipe
In the case that the business of reason exists mapping relations, according to mapping relations, alarm is derived for the derivative alarm of relation；
First reports unit 78, for producing the Root Resource of alarm by the situation shared by the business of controller management
Under, directly by alarm report to upper layer network equipment.
Fig. 8 is the preferred structure block diagram two of processing module 46 in alarm treatment device according to embodiments of the present invention,
As shown in Figure 8, this processing module 46 is except including that above-mentioned first derives module 74 and/or first and derive module 76
Outward, also include: the 82nd, record unit second reports unit 84 and/or provide unit 86, below to this process
Module 46 illustrates.
Record unit 82, in the case of carrying out derivation process to alarm, records after alerting and being derivative
Incidence relation between derivative alarm, wherein, derivative alarm includes: the derivative alarm of child resource and/or relation are spread out
Raw alarm；Second reports unit 84, for derivative alarm and incidence relation are reported upper layer network equipment,
And/or, provide unit 86, for providing incidence relation for the network element device inquiry in controller managing system.
Fig. 9 is the preferred structure block diagram of alarm treatment device according to embodiments of the present invention, as it is shown in figure 9, should
Device, in addition to including all modules shown in Fig. 4, also includes: generation module 92 and reporting module 94, below
This device is illustrated.
Generation module 92, is connected to above-mentioned processing module 46, for the network element device caused according to alarm
State changes, or the state change of the object of the representative resource of alarm, generates network element device or represents resource
The state notifying of object；Reporting module 94, is connected to above-mentioned generation module 92, for the network element that will generate
The state notifying of equipment or the object representing resource reports upper layer network equipment.
Preferably, this controller can include at least one of: domain controller DC, super controller SC,
Wherein, SC is the top level control device of DC.It is pointed out that SC can have multiple, in terms of DC, SC
All top level control device, if also SC above SC, above be the controller of more top, this is relative
Relation.
In the network of SDN controller management and control, due to the control characteristic of SDN controller, it is only concerned business
Related resource, and due to delineation of power reason, original alarm is probably and is produced by the resource unrelated with business
, or the business generation not managed by controller, but impact can be produced on the business of controller management,
Cause business obstructed, or Quality Down.Owing to the essential core of controller is by service management, at network
Management system or control plane are not to device resource and alarm generated by service, in consideration of it, at the present embodiment
In, it is proposed that the alarm of alarm also business to be appeared as, controller to be derived affected service alarm.
In addition, in addition to alarm is derivative, controller also needs to carry out alarm traffic affecting analysis, in alarm continuation
Reports etc. are processed.
Below the program is briefly described.
Increasing an alert analysis module in network controller, Figure 10 is control according to embodiments of the present invention
The structural representation of device alert analysis module, as shown in Figure 10, this alert analysis module performs following steps
Analyzing and processing:
Step 1: produce alarm after Equipment Inspection to fault, report controller and webmaster simultaneously.
Step 2: controller is analyzed after receiving equipment alarm and processes, including the one of following several sub-steps
Individual or multiple flexible combination:
Step 2.1: classify according to alarm cause, business is not affected by part alarm cause, if received
To be one of these alarm cause, this alarm can not be processed, or is suppressed.Such alarm cause
Including but not limited to: temperature warning, voltage alarm, smoke alarm, etc. a lot, do not list one by one.Control
Device needs alarm to be processed, including but not limited to: LOS (Loss of Signal), DEG (Degraded Signal),
LOC (Loss of Connectivity/Loss of Connection), AIS (Alarm Indication Signal).
Step 2.2: analyzing alarm, discovery produces the resource of alarm, is not the resource that business takies, also not right
Resource shared by business produces impact, and such alarm also can not process, or be suppressed.Such
Resource includes but is not limited to: power module, blower module, and core bus etc. is not listed one by one.Controller needs
The alarm resource, including but not limited to: physical port, connection end points of producing to be processed, Trail termination point,
Logical terminal (LTERM) point, flow point, flow point pond.
Step 2.3: analyze alarm, discovery produces the resource of alarm, is not the resource that business directly takies, but
It is to have child resource to be taken by business under this resource, alarm can be derived the alarm of child resource shared by business,
Then controller derivative alarm report to top level control device and webmaster plane.Original alarm can be according to realizing need
Continue to report or do not report.
Step 2.4: analyze alarm, discovery produces the resource of alarm, is the resource that business takies, the announcement reporting
The alert alarm directly just belonging to business, can not do derivative, this alarm is continued to report top level control device and net
Pipe plane.
Step 2.5: analyze alarm, discovery produces the resource of alarm, does not has and the resource object of business has directly
Corresponding relation, but there are indirectly mapping relations (for example, virtualize virtualization), controller according to
This indirectly mapping relations, derive the alarm of service resources, and then controller is given derivative alarm report upper
Layer control and webmaster plane.Original alarm can be according to realizing that needs continue to report or do not report.
Step 2.6: analyze alarm, find that this alarm is network element alarming, but this alarm is not felt emerging by controller
Interest, but interested in the caused network element state change of alarm, controller suppresses or abandons this alarm, generates
State notifying, the local network element state of modification, state notifying is reported top level control device and webmaster plane.
Step 2.7: the new alarm that controller derives, the corresponding relation of original alarm and derivative alarm is recorded
Come, and provide when report and alarm, or inquiry is provided, in order to webmaster plane carries out root cause analysis, find out event
Barrier root, repairs and fixes a breakdown.
Step 3:EMS receives original alarm and after controller receives derivative alarm from equipment, can carry out this
The management such as ground preservation, display, confirmation, annotation, EMS reports NMS/OSS the two alarm.
Step 4: after top level control device receives the derivative alarm of lower floor's controller report, use the analysis of step 2
Processing method, carries out local analytics process, and result reports APP and OSS/NMS.
It after step 5:APP receives service alarm, is used for the purposes such as interface display, and evaluation the quality.
Step 6:OSS/NMS receives the original alarm that EMS reports, and derivative alarm, and from upper strata control
The derivative alarm that device processed reports, carries out comprehensive analysis, including analyze alarm association relation, root cause analysis etc., is
The network operation, safeguard, fix a breakdown, charging etc. provides basis.
By controller, the method processing is alerted to device resource, including receive the analysis after alarm, processes,
Derivative, and the method continuing to report to other system.Processing alarm for controller provides a kind of efficiently feasible,
Meet the alert processing method of service management purpose.
Produce in the business of multi-controller by one below as a example by alerting, alert analysis processing method is described.
Preferred embodiment one
Figure 11 is the schematic diagram that the alarm report according to the preferred embodiment of the present invention one is processed, as shown in figure 11,
Domain controller DC1 and DC2, zoning manages communication network, and super controller SC, as upper strata
Controller management DC1 and DC2.Connecting NE1 in two management domains, NE2 to NE6 forms communication network.
The line of NE1 to NE6 represents the business that an APP is concerned about, business A end points exists at NE1, Z end points
NE6, middle through NE2, NE3, NE4, NE5, respectively by DC1, DC2 directly manages, empty in figure
Line represents administrative relationships.DC1, DC2 and SC have the network management system of pairing respectively, it is assumed that produce at network element 1
One alarm Alarm1, other several network elements also have alarm to produce.
1st step: NE1 detects fault, and smoke detector feels that smog exceeds standard, and smoke detection module produces
Alarm alarm1, reports DC1 and EMS1 simultaneously.
2nd step: DC1 receives Alarm1 post analysis, analyzes module and is analyzed alarm cause, finds alarm1
Alarm cause be smoke alarm, belong to the alarm cause unrelated with business, then DC1 ignores this alarm.
3rd step: NE2 detects fault, and blower module discovery rotation speed of the fan is abnormal, produces alarm alarm2,
Report DC1 and EMS1 simultaneously.
4th step: DC1 receives alarm2 post analysis, analyzes module and is analyzed alarm source, finds alarm2
The resource producing is blower module, and business is unrelated, and then DC1 ignores this alarm.
The OTN optical port of the 5th step: NE1 is faulty, and OTN has Signal Degrade to alert, and produces alarm alarm3,
Report DC1 and EMS1 simultaneously.
6th step: DC1 receives alarm3 post analysis, analyzes module analysis OTN port, although this resource
Directly do not used by business, but the subchannel ODU1-1 under OTN is just used in business 1, DC1
Derive the deterioration alarm alarm4 of ODU1-1 resource, and record the corresponding relation of alarm3-alarm4,
Then DC1 reports alarm4 to SC and EMS1, and the incidence relation of subsidiary alarm3-alarm4.
7th step: EMS receives alarm1, alarm2, alarm3, alarm4 altogether.Carry out traditional
While EMS alarm management, these alarms are all reported NMS/OSS1.
8th step: SC receive alarm alarm4, analyze module discovery, due to alarm resource ODU1 and
The business 1 at place through virtualization (virtualization) and is mapped to business 2 at SC, and ODU1 is virtual
Chemical conversion LTP1.Derivative module SC derives the alarm5 of LTP1 resource, and record from alarm4
The corresponding relation of alarm4-alarm5.SC reports alarm5 to app and NMS/OSS1, and subsidiary
The incidence relation of alarm4-alarm5.
9th step: NMS/OSS1 receives alarm alarm1, alarm2, alarm3, alarm4, alarm5 altogether.
Owing to there being the derivative corresponding relation of alarm3-alarm4-alarm5, NMS/OSS1 is easy to analysis and draws
Alarm3 is Root alarm, needs to notify attendant's prosthetic appliance, fixes a breakdown.
10th step: after APP receives alarm5, learns the business 2 of oneself, creates alarm 5, business 2
Receive impact.App user is with this and Virtual network operator communication and coordination.
The alarm that similar NE3, NE4 produce, at DC2, EMS2, NMS/OSS2 are similar to
Handling process.
Preferred embodiment two
Figure 12 is the schematic diagram that the alarm report according to the preferred embodiment of the present invention two is processed, as shown in figure 12,
One of network network element NE1, the domain controller DC1 being carried out manage, simultaneously by EMS1 network management system
Management, NE1 creates an alarm a, and result treatment flow process is as follows
1st step: NE1 detects fault, has reported alarm a.
Alarm a is analyzed by the 2nd step: DC1, is analyzed according to alarm cause and alarm source, and discovery is accused
The child resource of alert a is used by business, according to analysis result, alarm a is abandoned, and has derived alarm b, then
Alarm b reports top level control device SC1, and network management system EMS1.
After 3rd step: EMS1 receives alarm a and alarm b, alarm a and b is reported to upper strata webmaster OSS1.
It after 4th step: SC1 receives the alarm b that DC1 reports, is analyzed according to alarm cause and alarm source,
The resource of discovery alarm b, after virtualization, becomes object logic obj1, and they belong to virtualized mapping
Relation, SC1 Discard alarm b, derive alarm c.SC1 reports app and OSS1 alarm c simultaneously.
5th step: app receives alarm notification, learns that abstract object obj1 in the business of oneself has alarm c,
For the purpose fixed a breakdown, app sends the request of all alarms of inquiry and incidence relation to OSS1.
6th step: OSS1, from SC1 query warning incidence relation, obtains alerting the association between b and alarm c
Relation.
7th step: OSS1 is from EMS1 query warning incidence relation.
8th step: EMS1 finds alarm a and the incidence relation of alarm b from DC1 there.It is reported to OSS1.
9th step: OSS1 collect obtain alert a, the incidence relation of b, c, report to APP.
10th step: app obtains all alarm a from inquiry response, and b, c simultaneously know that a is Root alarm.For
Notice operation maintenance personnel carries out prosthetic appliance and fixes a breakdown.
Obviously, those skilled in the art should be understood that each module of the above-mentioned present invention or each step can be used
General computing device realizes, they can concentrate in single computing device, or is distributed in multiple meter
Calculating on the network that device is formed, alternatively, they can be realized by the executable program code of computing device,
It is thus possible to be stored in storage device is performed by computing device, and in some cases, can
Perform shown or described step with the order to be different from herein, or they are fabricated to respectively each collection
Become circuit module, or the multiple module in them or step are fabricated to single integrated circuit module realize.
So, the present invention is not restricted to the combination of any specific hardware and software.
These are only the preferred embodiments of the present invention, be not limited to the present invention, for the skill of this area
For art personnel, the present invention can have various modifications and variations.All within the spirit and principles in the present invention, institute
Any modification, equivalent substitution and improvement etc. made, should be included within the scope of the present invention.
Claims (13)
1. an alert processing method, it is characterised in that include:
Controller receives the alarm from the network equipment；
Described alarm is analyzed drawing analysis result by described controller；
Described alarm is processed by described controller according to described analysis result.
2. method according to claim 1, it is characterised in that described alarm is analyzed by described controller
Obtain described analysis result and include at least one of:
According to the alarm cause producing described alarm, analyze and draw described alarm whether to controller management
Business produces the described analysis result of impact；
According between the resource producing described alarm and the resource shared by business of described controller management
Relation, analyze the institute showing that the described business whether on described controller management for the described alarm produces impact
State analysis result.
3. method according to claim 2, it is characterised in that according to produce the resource of described alarm with described
Whether the relation between resource shared by the business of controller management, analyze and draw described alarm to described
The described business of controller management produces the described analysis result of impact and includes one below:
Producing the Root Resource of described alarm not by shared by the business of described controller management, and also do not having
There is the corresponding child resource of described Root Resource by the case of shared by the business of described controller management, determine
Described alarm does not produce impact to the described business of described controller management；
Producing the Root Resource of described alarm not by shared by the business of described controller management, but described
The corresponding child resource of resource, by the case of shared by the business of described controller management, determines described alarm
Impact is produced on the described business of described controller management；
Producing the Root Resource of described alarm not by shared by the business of described controller management, described money
The corresponding child resource in source also not by shared by the business of described controller management, but described Root Resource and/or
In the case of there are mapping relations in the business of the corresponding child resource of described Root Resource and described controller management,
Determine that described alarm produces impact to the described business of described controller management；
Producing the Root Resource of described alarm by the case of shared by the business of described controller management, really
The described business on described controller management for the fixed described alarm produces impact.
4. method according to claim 3, it is characterised in that described controller is according to described analysis result pair
Described alarm carries out process and includes one below:
According to described alarm cause, analyze and show that the business to described controller management for the described alarm is not produced
In the case that life affects, described alarm is suppressed；
According to produce the described resource of alarm and the resource shared by the business of described controller management it
Between relation determine that the described business of described controller management is not produced in the case of affect by described alarm,
Described alarm is suppressed；
Producing the Root Resource of described alarm not by shared by the business of described controller management, but described
Described alarm, by the case of shared by the business of described controller management, is spread out by the corresponding child resource of resource
Raw for the derivative alarm of child resource；
Producing the Root Resource of described alarm not by shared by the business of described controller management, described money
The corresponding child resource in source also not by shared by the business of described controller management, but described Root Resource and/or
In the case of there are mapping relations in the business of the corresponding child resource of described Root Resource and described controller management,
According to described mapping relations, described alarm is derived for the derivative alarm of relation；
Producing the Root Resource of described alarm by the case of shared by the business of described controller management, directly
Connect described alarm report to upper layer network equipment.
5. method according to claim 4, it is characterised in that in the feelings carrying out derivation process to described alarm
Under condition, also include:
The incidence relation between derivative alarm after recording described alarm and deriving, wherein, described derivative announcement
Police includes: the derivative alarm of child resource and/or the derivative alarm of relation；
Described derivative alarm and described incidence relation are reported upper layer network equipment, and/or institute is provided
State incidence relation for the network element device inquiry in described controller managing system.
6. method according to any one of claim 1 to 5, it is characterised in that in described controller foundation
After described alarm is processed by described analysis result, also include:
According to the state change of the network element device caused by described alarm, or the representative resource of described alarm
Object state change, generate described network element device or the state notifying of the described object representing resource；
The state notifying of the described network element device generating or the described object representing resource is reported
Layer network device.
7. an alarm treatment device, it is characterised in that be applied to controller and include:
Receiver module, for receiving the alarm from the network equipment；
Analyze module, for being analyzed drawing analysis result to described alarm；
Processing module, for processing to described alarm according to described analysis result.
8. device according to claim 7, it is characterised in that described analysis module includes at least one of:
First analytic unit, for according to the alarm cause producing described alarm, analyzes and draws described alarm
Whether the described analysis result affecting is produced on the business of controller management；
Second analytic unit, for the business according to the resource with described controller management producing described alarm
Whether the shared relation between resource, analyze and draw described alarm described in described controller management
Business produces the described analysis result of impact.
9. device according to claim 8, it is characterised in that described second analytic unit includes one below:
First determination subelement, for producing the Root Resource of described alarm not by described controller management
Shared by business, and there is no the corresponding child resource of described Root Resource by the business of described controller management yet
In the case of shared, determine that described alarm does not produce impact to the described business of described controller management；
Second determination subelement, for producing the Root Resource of described alarm not by described controller management
Shared by business, but the corresponding child resource of described Root Resource is by shared by the business of described controller management
In the case of, determine that described alarm produces impact to the described business of described controller management；
3rd determination subelement, for producing the Root Resource of described alarm not by described controller management
Shared by business, the corresponding child resource of described Root Resource also not by shared by the business of described controller management,
But described Root Resource and/or the corresponding child resource of described Root Resource exist with the business of described controller management
In the case of mapping relations, determine that described alarm produces impact to the described business of described controller management；
4th determination subelement, for producing the Root Resource of described alarm by the industry of described controller management
In the case that business is shared, determine that described alarm produces impact to the described business of described controller management.
10. device according to claim 9, it is characterised in that described processing module includes one below:
First suppression unit, for according to described alarm cause, analyzing and drawing described alarm to described control
The business of device processed management does not produce in the case of impact, suppresses described alarm；
Second suppression unit, in the industry according to the resource with described controller management producing described alarm
Relation between the shared resource of business determines described alarm to the described business of described controller management not
In the case that generation affects, described alarm is suppressed；
First derived units, for producing the Root Resource of described alarm not by the industry of described controller management
Business is shared, but the corresponding child resource of described Root Resource is by the feelings shared by the business of described controller management
Under condition, described alarm is derived for the derivative alarm of child resource；
Second derived units, for producing the Root Resource of described alarm not by the industry of described controller management
Business is shared, the corresponding child resource of described Root Resource also not by shared by the business of described controller management,
But described Root Resource and/or the corresponding child resource of described Root Resource exist with the business of described controller management
In the case of mapping relations, according to described mapping relations, described alarm is derived for the derivative alarm of relation；
First reports unit, for producing the Root Resource of described alarm by the business of described controller management
In the case of shared, directly by described alarm report to upper layer network equipment.
11. devices according to claim 10, it is characterised in that also include:
Record unit, in the case that derivation process is carried out to described alarm, record described alarm with
The incidence relation between derivative alarm after Yan Sheng, wherein, described derivative alarm includes: child resource derives
Alarm and/or the derivative alarm of relation；
Second reports unit, for described derivative alarm and described incidence relation are reported upper layer network
Equipment, and/or, unit is provided, is used for providing described incidence relation in described controller managing system
Network element device inquiry.
12. devices according to according to any one of claim 7 to 11, it is characterised in that also include:
Generation module, for the state change of the network element device caused according to described alarm or described
The state change of the object of the representative resource of alarm, generates described network element device or the described resource that represents
The state notifying of object；
Reporting module, is used for the state of described network element device or the described object representing resource that will generate
Notice reporting is to upper layer network equipment.
13. devices according to according to any one of claim 7 to 11, it is characterised in that described controller includes
At least one of: domain controller DC, super controller SC, wherein, described SC is described DC
Top level control device.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2015100423091 | 2015-01-27 | ||
| CN201510042309 | 2015-01-27 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105991332A true CN105991332A (en) | 2016-10-05 |
Family
ID=56542308
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510088503.3A Pending CN105991332A (en) | 2015-01-27 | 2015-02-26 | Alarm processing method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105991332A (en) |
| WO (1) | WO2016119436A1 (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108183810A (en) * | 2016-12-08 | 2018-06-19 | 中兴通讯股份有限公司 | Multiple services parallel recovery method, apparatus and system under SDN frameworks |
| CN109309577A (en) * | 2017-07-27 | 2019-02-05 | 杭州达乎科技有限公司 | Alert processing method, apparatus and system for SDN network |
| WO2020093959A1 (en) * | 2018-11-06 | 2020-05-14 | 华为技术有限公司 | Method and apparatus for diagnosing root cause |
| CN111865785A (en) * | 2020-06-28 | 2020-10-30 | 烽火通信科技股份有限公司 | SR-TP tunnel signal transmission method, device, server and storage medium |
| CN115941442A (en) * | 2022-12-01 | 2023-04-07 | 中国联合网络通信集团有限公司 | Business fault analysis method and device, electronic equipment and medium |
Families Citing this family (69)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9781004B2 (en) | 2014-10-16 | 2017-10-03 | Cisco Technology, Inc. | Discovering and grouping application endpoints in a network environment |
| 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 |
| US10623264B2 (en) | 2017-04-20 | 2020-04-14 | Cisco Technology, Inc. | Policy assurance for service chaining |
| US10581694B2 (en) | 2017-05-31 | 2020-03-03 | Cisco Technology, Inc. | Generation of counter examples for network intent formal equivalence failures |
| US10554483B2 (en) | 2017-05-31 | 2020-02-04 | Cisco Technology, Inc. | Network policy analysis for networks |
| US20180351788A1 (en) | 2017-05-31 | 2018-12-06 | Cisco Technology, Inc. | Fault localization in large-scale network policy deployment |
| US10439875B2 (en) | 2017-05-31 | 2019-10-08 | 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 |
| 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 |
| US10693738B2 (en) | 2017-05-31 | 2020-06-23 | Cisco Technology, Inc. | Generating device-level logical models for a network |
| US10623271B2 (en) | 2017-05-31 | 2020-04-14 | Cisco Technology, Inc. | Intra-priority class ordering of rules corresponding to a model of network intents |
| US11469986B2 (en) | 2017-06-16 | 2022-10-11 | Cisco Technology, Inc. | Controlled micro fault injection on a 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 |
| US10574513B2 (en) | 2017-06-16 | 2020-02-25 | Cisco Technology, Inc. | Handling controller and node failure scenarios during data collection |
| US10904101B2 (en) | 2017-06-16 | 2021-01-26 | Cisco Technology, Inc. | Shim layer for extracting and prioritizing underlying rules for modeling network intents |
| 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 |
| US11150973B2 (en) | 2017-06-16 | 2021-10-19 | Cisco Technology, Inc. | Self diagnosing distributed appliance |
| US10686669B2 (en) | 2017-06-16 | 2020-06-16 | Cisco Technology, Inc. | Collecting network models and node information from a network |
| US11645131B2 (en) | 2017-06-16 | 2023-05-09 | Cisco Technology, Inc. | Distributed fault code aggregation across application centric dimensions |
| US10348564B2 (en) | 2017-06-19 | 2019-07-09 | Cisco Technology, Inc. | Validation of routing information base-forwarding information base equivalence in a network |
| US10805160B2 (en) | 2017-06-19 | 2020-10-13 | Cisco Technology, Inc. | Endpoint bridge domain subnet validation |
| US11343150B2 (en) | 2017-06-19 | 2022-05-24 | Cisco Technology, Inc. | Validation of learned routes 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 |
| US10528444B2 (en) | 2017-06-19 | 2020-01-07 | Cisco Technology, Inc. | Event generation in response to validation between logical level and hardware level |
| US10644946B2 (en) | 2017-06-19 | 2020-05-05 | Cisco Technology, Inc. | Detection of overlapping subnets in a network |
| US10505817B2 (en) | 2017-06-19 | 2019-12-10 | Cisco Technology, Inc. | Automatically determining an optimal amount of time for analyzing a distributed network environment |
| US10341184B2 (en) | 2017-06-19 | 2019-07-02 | Cisco Technology, Inc. | Validation of layer 3 bridge domain subnets in in a network |
| US10812336B2 (en) | 2017-06-19 | 2020-10-20 | Cisco Technology, Inc. | Validation of bridge domain-L3out association for communication outside a network |
| US10333787B2 (en) | 2017-06-19 | 2019-06-25 | Cisco Technology, Inc. | Validation of L3OUT configuration for communications outside a network |
| US10623259B2 (en) | 2017-06-19 | 2020-04-14 | Cisco Technology, Inc. | Validation of layer 1 interface in a network |
| US10437641B2 (en) | 2017-06-19 | 2019-10-08 | Cisco Technology, Inc. | On-demand processing pipeline interleaved with temporal processing pipeline |
| US10536337B2 (en) | 2017-06-19 | 2020-01-14 | Cisco Technology, Inc. | Validation of layer 2 interface and VLAN in a networked environment |
| US10652102B2 (en) | 2017-06-19 | 2020-05-12 | Cisco Technology, Inc. | Network node memory utilization analysis |
| US10218572B2 (en) | 2017-06-19 | 2019-02-26 | Cisco Technology, Inc. | Multiprotocol border gateway protocol routing validation |
| US10432467B2 (en) | 2017-06-19 | 2019-10-01 | Cisco Technology, Inc. | Network validation between the logical level and the hardware level of a network |
| US10700933B2 (en) | 2017-06-19 | 2020-06-30 | Cisco Technology, Inc. | Validating tunnel endpoint addresses in a network fabric |
| US10554493B2 (en) | 2017-06-19 | 2020-02-04 | Cisco Technology, Inc. | Identifying mismatches between a logical model and node implementation |
| US10560355B2 (en) | 2017-06-19 | 2020-02-11 | Cisco Technology, Inc. | Static endpoint validation |
| US10567229B2 (en) | 2017-06-19 | 2020-02-18 | Cisco Technology, Inc. | Validating endpoint configurations between nodes |
| US10567228B2 (en) | 2017-06-19 | 2020-02-18 | Cisco Technology, Inc. | Validation of cross logical groups in a network |
| US10411996B2 (en) | 2017-06-19 | 2019-09-10 | Cisco Technology, Inc. | Validation of routing information in a network fabric |
| US11283680B2 (en) | 2017-06-19 | 2022-03-22 | Cisco Technology, Inc. | Identifying components for removal in a network configuration |
| US10673702B2 (en) | 2017-06-19 | 2020-06-02 | Cisco Technology, Inc. | Validation of layer 3 using virtual routing forwarding containers in a network |
| US10587456B2 (en) | 2017-09-12 | 2020-03-10 | 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 |
| 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 |
| CN108156019B (en) * | 2017-11-29 | 2022-10-25 | 全球能源互联网研究院有限公司 | SDN-based network derived alarm filtering system and method |
| 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 |
| 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 |
| US10911495B2 (en) | 2018-06-27 | 2021-02-02 | 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 |
| US11218508B2 (en) | 2018-06-27 | 2022-01-04 | 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 |
| 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 |
| CN112073208B (en) * | 2019-05-25 | 2022-01-14 | 成都华为技术有限公司 | Alarm analysis method, device, chip system and storage medium |
| CN113055213B (en) * | 2019-12-27 | 2024-05-28 | 中兴通讯股份有限公司 | Alarm information management method, alarm information management system and server |
| CN114024828B (en) * | 2021-10-15 | 2023-05-23 | 烽火通信科技股份有限公司 | Platform side alarm suppression method, device and storage medium |
| CN113965452B (en) * | 2021-11-02 | 2023-11-03 | 烽火通信科技股份有限公司 | Equipment switching state acquisition method and device |
| CN114285726A (en) * | 2021-12-27 | 2022-04-05 | 中国联合网络通信集团有限公司 | Fault positioning method and device and computer storage medium |
| CN114389960B (en) * | 2022-01-04 | 2023-11-28 | 烽火通信科技股份有限公司 | Method and system for collecting and reporting network service performance |
| CN115396287B (en) * | 2022-08-29 | 2023-05-12 | 武汉烽火技术服务有限公司 | Fault analysis method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101409644A (en) * | 2007-10-12 | 2009-04-15 | 中兴通讯股份有限公司 | Method and system for pre-warning service quality |
| CN101917288A (en) * | 2010-08-04 | 2010-12-15 | 中兴通讯股份有限公司 | Alarm processing method and network management system |
| CN102571407A (en) * | 2010-12-30 | 2012-07-11 | 中国移动通信集团河北有限公司 | Alarm correlation analysis method and device |
| CN103378980A (en) * | 2012-04-16 | 2013-10-30 | 中兴通讯股份有限公司 | Method for correlation analysis of layer network alarm with business and device thereof |
| US20150006459A1 (en) * | 2013-06-29 | 2015-01-01 | Huawei Technologies Co., Ltd. | Alarm Correlation Analysis Method, Apparatus and System |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100375435C (en) * | 2004-06-22 | 2008-03-12 | 中兴通讯股份有限公司 | Alarm correlation analysis of light synchronous transmitting net |
| CN1992636B (en) * | 2005-12-29 | 2010-04-21 | 华为技术有限公司 | System and method for processing warning information |
| CN101183989B (en) * | 2007-12-03 | 2010-09-01 | 中兴通讯股份有限公司 | Incremental analysis method of optical synchronization transmission network alarm correlation |
| CN103596208B (en) * | 2013-11-15 | 2017-02-15 | 大唐移动通信设备有限公司 | Method and system for judging fault of network element |
-
2015
- 2015-02-26 CN CN201510088503.3A patent/CN105991332A/en active Pending
- 2015-08-12 WO PCT/CN2015/086803 patent/WO2016119436A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101409644A (en) * | 2007-10-12 | 2009-04-15 | 中兴通讯股份有限公司 | Method and system for pre-warning service quality |
| CN101917288A (en) * | 2010-08-04 | 2010-12-15 | 中兴通讯股份有限公司 | Alarm processing method and network management system |
| CN102571407A (en) * | 2010-12-30 | 2012-07-11 | 中国移动通信集团河北有限公司 | Alarm correlation analysis method and device |
| CN103378980A (en) * | 2012-04-16 | 2013-10-30 | 中兴通讯股份有限公司 | Method for correlation analysis of layer network alarm with business and device thereof |
| US20150006459A1 (en) * | 2013-06-29 | 2015-01-01 | Huawei Technologies Co., Ltd. | Alarm Correlation Analysis Method, Apparatus and System |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108183810A (en) * | 2016-12-08 | 2018-06-19 | 中兴通讯股份有限公司 | Multiple services parallel recovery method, apparatus and system under SDN frameworks |
| CN108183810B (en) * | 2016-12-08 | 2019-06-04 | 中兴通讯股份有限公司 | Multiple services parallel recovery method, apparatus and system under SDN framework |
| CN109309577A (en) * | 2017-07-27 | 2019-02-05 | 杭州达乎科技有限公司 | Alert processing method, apparatus and system for SDN network |
| WO2020093959A1 (en) * | 2018-11-06 | 2020-05-14 | 华为技术有限公司 | Method and apparatus for diagnosing root cause |
| CN111865785A (en) * | 2020-06-28 | 2020-10-30 | 烽火通信科技股份有限公司 | SR-TP tunnel signal transmission method, device, server and storage medium |
| CN115941442A (en) * | 2022-12-01 | 2023-04-07 | 中国联合网络通信集团有限公司 | Business fault analysis method and device, electronic equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016119436A1 (en) | 2016-08-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105991332A (en) | Alarm processing method and device | |
| CN105282772B (en) | Wireless network datacom device monitoring system and apparatus monitoring method | |
| EP3829080B1 (en) | Pon fault location method and device | |
| CN102447570B (en) | Monitoring device and method based on health degree analysis | |
| CN103370904B (en) | Method, network entity for the seriousness that determines network accident | |
| US7225250B1 (en) | Method and system for predictive enterprise resource management | |
| CN102308522B (en) | Method, device and system for locating network fault | |
| CN106941423A (en) | Failure cause localization method and device | |
| CN109787817A (en) | Network fault diagnosis method, device and computer readable storage medium | |
| CN103716173B (en) | A kind of method for storing monitoring system and monitoring alarm issue | |
| CN109086894A (en) | A kind of warning message centring system of facing area genco | |
| CN103840975B (en) | The management method and device of a kind of fibre system | |
| CN101667941A (en) | Method for detecting link performance and device therefor | |
| WO2013155807A1 (en) | Method and apparatus for correlation analysis of layered network alarms and services | |
| CN106533832B (en) | Network flow detection system based on distributed deployment | |
| CN111147286B (en) | IPRAN network loop monitoring method and device | |
| CN107360045A (en) | The monitoring method and device of a kind of storage cluster system | |
| Stiawan et al. | Anomaly detection and monitoring in Internet of Things communication | |
| CN109714206A (en) | Electric power monitoring system Generating Network Topology Map, network bus topological diagram | |
| CN102820993A (en) | Network resource monitoring system and network resource monitoring method | |
| CN108769289A (en) | A kind of network address resources Visualized management system | |
| CN105991337A (en) | Alarm compression method and alarm compression device | |
| CN105790972A (en) | Controller and alarm correlation processing method | |
| CN110048872A (en) | A kind of network alarm method, apparatus, system and terminal | |
| CN110752959A (en) | Intelligent substation process layer physical link fault positioning system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20161005 |