WO2000072513A1 - Groupement de composants extensible pour reseaux de gestion d'evenements - Google Patents

Groupement de composants extensible pour reseaux de gestion d'evenements Download PDF

Info

Publication number
WO2000072513A1
WO2000072513A1 PCT/SE2000/000815 SE0000815W WO0072513A1 WO 2000072513 A1 WO2000072513 A1 WO 2000072513A1 SE 0000815 W SE0000815 W SE 0000815W WO 0072513 A1 WO0072513 A1 WO 0072513A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
collector
cluster
events
management system
Prior art date
Application number
PCT/SE2000/000815
Other languages
English (en)
Inventor
Edwin Tse
Nicolas Gosselin
Fergus Kelledy
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to AU49623/00A priority Critical patent/AU4962300A/en
Publication of WO2000072513A1 publication Critical patent/WO2000072513A1/fr

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/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • 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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications

Definitions

  • the present invention relates in general to event management networks, and in particular, to a method and system for clustering components to produce a large- scale event management system.
  • An alarm or event management system generally provides a relatively centralized monitoring of large numbers of elements in a network.
  • event management systems are commonly used to monitor telecommunications networks, utility networks, fleet vehicle locations, and property intrusion.
  • Elements in a network such as a computer switch, a route, a port, or a trap door, are monitored for events or fault conditions.
  • the monitoring system is programmed to detect and report specified conditions or events involving the monitored elements. Once detected, an event or alarm is forwarded towards a central monitoring location, where the event or alarm is displayed on a graphical display terminal, logged into an event
  • FIGURE 1 there is illustrated a block diagram of an event management system 10 having a typical M:l :N configuration.
  • the system 10 includes a number of event reporters 12(1)-12(M) which comprise sub-systems for detecting events.
  • Each event reporter 12 is associated with one or more elements 14 in the network 10 and operates to detect events or alarm conditions that are generated at the associated elements 14.
  • the event reporters 12 report the events to a centralized event collector 16, which feeds the events to multiple event viewers 18(1)-18(N).
  • the event viewers 18 may produce commands directing an implementation of specified functions in the event management system 10. For example, a network operator at one of the event viewers 18 may issue a command to the event collector 16 to acknowledge certain alarms. As a result, the event collector 16 might broadcast the acknowledgment to all of the other event viewers 18.
  • commands from the event viewers 18 are handled using a direct synchronized call from the event viewer 18 to the event collector 16, which relies upon a different communication protocol than does the reporting of events from the event reporters 12 to the event collector 16 and from the event collector 16 to the event viewers 18.
  • the event collector 16 will eventually become overloaded. As a result, the single event collector 16 frequently acts as a
  • collector 16 is to increase the processing power of the event collector 16. Increases
  • event reporters 12 and/or event viewers 18 may also require the installation of additional interfaces for connecting the event collector 16 to the added event reporters 12 and/or event viewers 18.
  • additional interfaces for connecting the event collector 16 to the added event reporters 12 and/or event viewers 18.
  • Increasing processing power and installing additional interfaces is a time-consuming and labor-intensive process.
  • the present invention comprises a system and method for monitoring events in a large-scale event management network.
  • a plurality of clusters are interconnected
  • Each cluster includes an event collector and a plurality of event reporters.
  • the event reporters detect alarms or other conditions and convert the detected conditions into events.
  • the events are pushed to an input interface of the event collector for the cluster where the events are stored in a database.
  • the event collector also selectively pushes the events from an output interface of the event collector to other clusters selected according to a determination of which events are of significance to other clusters. Accordingly, some clusters can act as event producers while other clusters act as event consumers.
  • the event collector pushes received events from the output interface to an event viewer for displaying, logging, or correlating the event.
  • the event management network can be easily scaled and reconfigured according to potential changes or expansions of the event management network.
  • events can be easily stored in a cache that is distant from the event-generating elements and event reporters for viewing at a local event viewer.
  • each cluster has
  • the event viewers In response to received events, the event viewers issue commands that are converted into command events and pushed to the loop back ingress port.
  • the loop back ingress port pushes the command events to the event collector of the cluster, where the command event is correlated with a stored event and
  • loop back ingress port also pushes the command events to the corresponding loop back ingress ports of upstream clusters. In this manner, clusters are able to function both as event producers and event consumers.
  • FIGURE 1 is a block diagram of an event management system having a typical M:l :N configuration
  • FIGURE 2 is a block diagram of a clustered event management system in accordance with a preferred embodiment of the present invention
  • FIGURE 3 is a block diagram of a portion of a clustered event management system illustrating the use of a cluster configuration to handle remote caching in accordance with another embodiment of the present invention
  • FIGURE 4 is a block diagram of a clustered event management system in accordance with an alternative embodiment of the present invention.
  • FIGURE 5 is a timing and message flow diagram illustrating an example of the
  • Each cluster includes multiple event reporters and one event collector that are encapsulated to form a unit.
  • the cluster can include one or more event viewers for receiving events from the event collector.
  • Multiple clusters can be interconnected to form networks of various topologies for supporting large- scale event handling and local caching of events.
  • FIGURE 2 there is illustrated a block diagram of a clustered event management system 20 in accordance with a preferred embodiment of the present invention.
  • the clustered event management system 20 is arranged in a simple two-level hierarchy.
  • a Cluster C 22 includes one event collector 28 ("EC") and aplurality of event reporters 32(1)-32(N) ("ER").
  • the event reporters 32 are associated with particular monitored devices or resources (see FIGURE 1 ).
  • the event reporters 32 detect certain alarm or event conditions by receiving information from the underlying resources. Typically, such information is communicated using a proprietary protocol that is unique or specific to the vendor of the particular monitored devices or resources.
  • the event reporter 32 acts to convert the proprietary protocol into a standard format or protocol that is understandable to the event
  • CORBA Notification Service An event producer publishes to potential event consumers a list of channels that each contain different types of information. The event consumers then tune or subscribe only to those CORBA Notification Service channels that contain information that is of interest to the event consumer. Thus, the channels act to filter information so that event information is selectively transmitted to event consumers.
  • the event collector 28 When the event collector 28 receives events from the event reporters 32. the event collector 28 stores the event information. The event collector 28 also pushes the received events (as indicated at 34) to one or more event viewers 30 ("EV"), where the events can be displayed, logged, or correlated, in accordance with the desired functions of the particular system 20. For example, upon receiving an alarm, the event collector 28 can store the alarm information as part of an active alarm list in a database (not shown). At the same time, the event collector 28 forwards the alarm information to the event viewers 30. One of the event viewers 30 might take some action to correct the fault that caused the alarm. If the fault is corrected, then the event reporter 32 that
  • the alarm can be deleted from the database.
  • Each alarm stored in the list remains in the database until the event collector receives an event indicating that the alarm has been cleared.
  • Cluster A 24 and a Cluster B 26 subordinate to
  • Cluster C 22 each include an event collector 42 and 44 and a plurality of event
  • the event reporters 38 and 40 produce events and push the events to their respective event collector 42 or 44 (as indicated at 46)
  • These subordinate clusters 24 and 26 can also include one or more event viewers 48, although not every cluster needs to include its own individual event viewers 48 If an event viewer 48 is present, as m Cluster B 24, then the events received from the event reporters 38 are pushed to the event viewer 48
  • the event collector 42 of Cluster A 24 and the event collector 44 of Cluster B 26 push events downstream to the event collector 28 of Cluster C 22
  • the event collectors 42 and 44 of Cluster A 24 and Cluster B 26 push the events from output interfaces or ports, which are the same output interfaces used to push events to event viewers 48, to an input interface or port of the event collector 28 of Cluster C 22
  • Events received at the event collector 28 of Cluster C 22 from the subordinate or upstream clusters 24 and 26 are handled in the same way, and are received at the same interface, as events received at the event collector 28 of Cluster C 22 from its underlying event reporters 32 In this manner,
  • events can be received from multiple event reporters 38 or 40 by a

Abstract

L'invention concerne un système et un procédé destinés à la surveillance et à la gestion d'événements et à la construction d'un système (20) de gestion d'événements comprenant une pluralité de groupes (22, 24, 26). Chaque groupe comprend un collecteur (42) d'événements ainsi qu'une pluralité de reporteurs (38). Dans chaque groupe, des événements sont reçus (36) en provenance des reporteurs d'événements au niveau d'une interface d'entrée du collecteur d'événements. Le collecteur d'événements pousse (36) sélectivement les événements depuis une interface de sortie du collecteur d'événements vers l'interface d'entrée d'un collecteur (28) d'événements se trouvant dans un autre groupe. Dans l'un des groupes au moins, les événements sont également poussés (34) depuis l'interface de sortie du collecteur d'événements vers un consommateur (30) d'événements. En réponse, le consommateur d'événements émet des commandes (56) qui sont converties en événements de commande et poussées (54) en retour vers l'interface d'entrée du collecteur (42) d'événements dans l'un des groupes au moins.
PCT/SE2000/000815 1999-05-21 2000-04-28 Groupement de composants extensible pour reseaux de gestion d'evenements WO2000072513A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU49623/00A AU4962300A (en) 1999-05-21 2000-04-28 Scalable component clustering for event management networks

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US31673799A 1999-05-21 1999-05-21
US09/316,737 1999-05-21

Publications (1)

Publication Number Publication Date
WO2000072513A1 true WO2000072513A1 (fr) 2000-11-30

Family

ID=23230435

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2000/000815 WO2000072513A1 (fr) 1999-05-21 2000-04-28 Groupement de composants extensible pour reseaux de gestion d'evenements

Country Status (2)

Country Link
AU (1) AU4962300A (fr)
WO (1) WO2000072513A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007144300A1 (fr) * 2006-06-13 2007-12-21 Nokia Siemens Networks Gmbh & Co. Kg Modification flexible du domaine de responsabilité d'un opérateur pour la gestion de réseau
WO2012025631A1 (fr) * 2010-08-27 2012-03-01 Cassidian Sas Procédé de centralisation d'événements pour un système de gestion informatique hiérarchique à plusieurs niveaux

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5204955A (en) * 1989-12-18 1993-04-20 Hitachi, Ltd. Network management method and system
EP0822473A2 (fr) * 1996-07-31 1998-02-04 Canon Kabushiki Kaisha Système de maintenance à distance
US5742762A (en) * 1995-05-19 1998-04-21 Telogy Networks, Inc. Network management gateway
US5872931A (en) * 1996-08-13 1999-02-16 Veritas Software, Corp. Management agent automatically executes corrective scripts in accordance with occurrences of specified events regardless of conditions of management interface and management engine

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5204955A (en) * 1989-12-18 1993-04-20 Hitachi, Ltd. Network management method and system
US5742762A (en) * 1995-05-19 1998-04-21 Telogy Networks, Inc. Network management gateway
EP0822473A2 (fr) * 1996-07-31 1998-02-04 Canon Kabushiki Kaisha Système de maintenance à distance
US5872931A (en) * 1996-08-13 1999-02-16 Veritas Software, Corp. Management agent automatically executes corrective scripts in accordance with occurrences of specified events regardless of conditions of management interface and management engine

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007144300A1 (fr) * 2006-06-13 2007-12-21 Nokia Siemens Networks Gmbh & Co. Kg Modification flexible du domaine de responsabilité d'un opérateur pour la gestion de réseau
WO2012025631A1 (fr) * 2010-08-27 2012-03-01 Cassidian Sas Procédé de centralisation d'événements pour un système de gestion informatique hiérarchique à plusieurs niveaux
FR2964280A1 (fr) * 2010-08-27 2012-03-02 Eads Defence & Security Sys Procede de centralisation d’evenements pour systeme d’information hierarchique multi-niveaux
CN103109498A (zh) * 2010-08-27 2013-05-15 卡西迪安有限公司 用于对多级别层级式计算机管理系统的事件进行集中的方法
US9747142B2 (en) 2010-08-27 2017-08-29 Cassidian Sas Method for centralizing events for a multilevel hierarchical computer management system

Also Published As

Publication number Publication date
AU4962300A (en) 2000-12-12

Similar Documents

Publication Publication Date Title
US7099879B2 (en) Real-time monitoring of service performance through the use of relational database calculation clusters
US7526322B2 (en) Real-time analyst program for processing log files from network elements
EP0818096B1 (fr) Procede et appareil pour notification d'alarme basee sur des strategies de types predeterminees dans un environnement de gestion de reseau distribue
US5737319A (en) Dynamic network topology determination
US20130073913A1 (en) Business to business network management event detection and response system and method
US5864608A (en) System and method for formatting performance data in a telecommunications system
EP1361761A1 (fr) Système de gestion d'un réseau de télécommunication et procédé pour la surveillance de services
CN106411659A (zh) 一种业务数据监测方法及装置
JPH1093654A (ja) ネットワーク上の管理ステーションの動作を拡張させる汎用通知フレームワーク・システム及び方法
CN101617501A (zh) 对通信网络进行操作
CN100433647C (zh) 一种告警管理方法和系统
WO2006021151A1 (fr) Procede permettant de traiter les alertes dans un systeme de gestion centralisee de reseau et systeme de gestion centralisee de reseau correspondant
CN111949402A (zh) 数据库请求处理方法、装置、计算机设备及存储介质
US7912981B2 (en) System and method for intelligent data routing
EP1622310B1 (fr) Procédé et système de gestion pour des systèmes de gestion de réseau
CN101170441A (zh) 一种网管系统中屏蔽设备告警的方法及其装置
CN112417050A (zh) 数据同步方法和装置、系统、存储介质及电子装置
WO2000072513A1 (fr) Groupement de composants extensible pour reseaux de gestion d'evenements
US20120072545A1 (en) Remote maintenance and monitoring service framework for heterogeneous device and system
CN113407611B (zh) 一种数据集成分发平台和系统
CN215954134U (zh) 环保能源企业大规模实时数据通讯状态监控系统
KR0128850B1 (ko) 지능망서비스제어/관리시스템의메세지저장방법
US11816095B2 (en) Metrics and events infrastructure
KR950011481B1 (ko) 교환기의 프로세서간 통신망에서 노드의 경보주소 생성방법 및 경보주소 생성시스템
KR960001084B1 (ko) 교환기의 프로세서간 통신망에서 노드의 경보발생 노드 확인 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP