Event Aggregation and Distribution in Web-based Management Systems

Event Aggregation and Distribution in Web-based Management Systems 네트워크연구실 정 국 상 2001/10/10

Contents 1. 배경 2. Marvel 3. Advantage 4. Event Architecture 5. Event generation 6. Event collection and aggregation 7. Event service 8. Design and Implementation

1. 배경 • Network Management를 위해 asynchronous notification에 점차 의존. • Irregular condition detection • The polling paradigm : Management Application이 Network Element의 state를 모니터할 때의 attention 양의 문제. • Event-based model : 많은 Component로부터 Event를 받아서 처리하는 하는 데서 오는 한계. = > Event 수를 reduce 해야 함. • Event generation and distribution의 구조를 Marvel의 subsystem으로 표현.

2. Marvel • Toolkit for creating web-based network management services. • Completely distributed architecture. • Multiple level administration hierarchy • 동기적, 비동기적 방법으로 underlying information을 aggregate.

2. Marvel • MARVS(Management Aggregation and Visualization Server)에 AMO(Aggregated managed Object)를 저장. • AMO : aggregated information을 저장. Attribute list.

3. Advantage • Advantage • event processing의 서로 다른 phase를 통합(event collection에서부터 event aggregation, event distribution, event visualization까지) • event의 temporal and spatial aggregation을 제공하며, aggregation 수행에 대한 user complete control을 따른다.

4. Event Architecture • Network elements layer • network element와 element management agent(EMA : event source)로 구성 • Event collection and correlation layer • READY system, event collection, filtering, correlation engine • Event brokerage, management and distribution layer • AMO는 event를 local event log facility에 add, event의 사본을 event service unit에 send.

4. Event Architecture • 등록된 consumer set에 event send. • Marvel client를 위한 navigation service를 제공. 관심 있는 event를 subscribe하도록 함. • Event visualization layer • Synchronous service • event log를 browsing, data mining.(등록 불필요) • Asynchronous service • event를 받기 위해 event broker에 등록. Event가 생기면 client에게 push.(등록 필요)

5. Event generation • EMA에서 event 생성 • SNMP, CMIP 등을 이용하여 Marvel server에 notification send.

6. Event collection and aggregation • READY : event notification service. • filtering of events • asynchronous and decoupled communication of event notifications • AMO가 event source에 대해 consumer로 등록 될 수도 있다. • benefit • event collection, filtering, aggregation이 specialized event processing engine에 의해 수행되어 client에 service하는 전반적인 response time을 향상.

7. Event service • Event broker • event repository 유지(event, source 경로 store) • 새로운 event 등록. • Client가 처음 등록될 때, bootstrap code를 받아서 event browse할 수 있고, event consumer로 등록 • 등록된 event consumer는 Push모델을 따름(consumer registry 유지)

7. Event service • Event management • suspending and resuming consumer notifications • enabling and disabling an event of a particular class • navigating through the consumer registry • adding and removing event consumers • changing the access control list of event clients • managing the repositories by adding and removing new event types, event filters and event reaction objects

7. Event service • Consumer Notification • event가 오면 consumer registry scan. • Event information 또는 Event information + event를 handling할 code를 보냄. • Event reaction object • event handling을 위해 upload/execute 할 수 있는 mobile autonomous agent. • Event reaction registry에 store.

8. Design and Implementation • Class MarvelEvent • attribute를 포함 • event identifier, event source, timestamp, time-to-live, severity • standard event format을 Marvel event structure로 convert. • Visualize() : 먼저 common event information을 display하고 부가적인 정보를 위해 display()를 call.

8. Design and Implementation • MarvelEventRegistration interface • 특정 event type, AMO에서 생성된 모든 event를 받아서 등록. • client는 interface를 통해 event delivery option을 specify. • event delivery option : reliable delivery, priority based delivery, secure delivery, confirmed delivery • Component technology : Java beans • Java Infobus : 비동기적으로 통신할 필요가 있는 component를 함께 link. • Event broker subsystem에서 사용.

Event Aggregation and Distribution in Web-based Management Systems