6QM inter-domain architecture 6QM Workshop and Final Review, Berlin - - PowerPoint PPT Presentation

6QM inter-domain architecture

6QM Workshop and Final Review, Berlin December 14-15, 2004 elisa.boschi@hitachi-eu.com boschi@fokus.fraunhofer.de

OUTLINE

• Need for End-to-End measurements
• Requirements
• Monitoring configuration
• Data export
• 6QM architecture
• Components in detail
• Security (AAA)

E2E measurement

H2 AS2 H1 AS3 AS1 AS4 F C A I G B

START END

“Each domain” monitor its network and knows the next step… H1 only knows:

• the destination of the flow
• the management point of its

domain …but not details of the other networks

Inter-domain measurement requirements

• Common data format

– How to compare data – IPFIX

• Configuration protocol

– How to share data among ISPs – SMS

• Common measurement framework and

common metrics

– Measurement tools are often ISP specific – OpenIMP and most of all common metrics

• And of course: cooperation between ISPs!

Monitoring configuration

• Specification of Monitoring Service (SMS)
• The configuration process splits the

document into a

– Intra-domain SMS – Inter-domain SMS sent to “next hop”

• Different configuration granularity

SMS

– ID – Scope source – destination (changing every time) – SRC controller – Collector – Flow identification filter (Complex field) – Metric – Time schedule – Report schedule

– Periodically – At the end of the monitoring process – In alarm mode (notification threshold) – Random mode – Real time mode – Custom mode

– Reporting document type {IPFIX template,Custom, …} – Options

• Sampling

– Method – parameters

• Completeness
• Refinement
• Random shipment
• Overload behaviour
• Flow expiration (given time interval, FIN or RST bit in a TCP connection)

SMS splitting

X1

(A.1 A.2) local

src: A SMS ID: X2 scope: B.3 C.6 X3

(B.3 B.4) local

X4

(C.5 C.6) forwarded

A B C 1 6 2 3 4 5

SMS X A.1 C.6 SMS X4 B.4 C.6 SMS X2 B.3 C.6 src: GUI SMS ID: X scope: A.1 C.6 X2

(B.3 C.6) forwarded

Nested SMSs

ID SMS ID: 1 Scope

• SMS ID: 1.1
• SMS ID: 1.2

SRC controller Collector Flow identification Metric OWD Time schedule Report schedule Reporting document type Options

• Granularity:

endpoint ID SMS ID: 1.1 Scope

• Source
• destination

SRC controller Collector Flow identification Metric pkt header Time schedule Report schedule Reporting document type Options

• Granularity:

endpoint ID SMS ID: 1.2 Scope

• source
• destination

SRC controller Collector Flow identification Metric pkt header Time schedule Report schedule Reporting document type Options

• Granularity:

endpoint

Data export

IPFIX SMS

controller meter

IPFIX

6QM initial functional architecture

capture analyze capture generate capture capture analyze Passive Meter Passive Meter Active Meter Active Meter analyze generate analyze 6QM Measurement Manager

Store control & management Info

IPFIX Collector Calculate

Monitor meters Interface

GUI

WAN LAN LAN Store result User Generate task

Data Flow Control

Test packet User traffic 6QM Evaluator

Inter-domain Controller + Collectors

Get IPFIX data Requests Other domains... Results

CONTROLLER

Measurement management Management tables

SMS interpreter CORE CONTROLLER forwarder

SECURITY CHECKER

AAA server SMS SMS

COLLECTOR

DATA (IPFIX)

IPFIX DATA (local)

Collector and composer

DATA (IPFIX)

Exporter

SMS copies

AAA

ISP A ISP B AAA (A) AAA (B)

CONTROLLER

DB

REQUEST K DATA (K) CONTROLLER

1 2 6 3 4 5

COLLECTOR COLLECTOR

7 8

Thank you…