management issues of the ten-155 mbs tnc 2000, lisbon 23 may 2000 management issues of the ten-155...

Management issues of the TEN-155 MBS TNC 2000, Lisbon 23 May 2000

Management Issues of the TEN-155

Managed Bandwidth Service

Roberto SabatinoDANTE

TNC 2000, Lisbon 23 May 2000


Services in TEN-155

• Best Effort IP (classical):– IP connectivity for National Research

Networks– Interconnections (ABILENE, NACSIS, ESNet,

CAnet)– Native Multicast

• ATM based– VPNs– end to end BW guarantees - interdomain– for pan-European Research projects


MBS overview

• ATM PVC: VCC VPC

• CBR, VBR

• permanent, scheduled, periodic

• up to 20% of NRN access– direct connections to TEN-155 possible


What do we mean by Quality:

• Everything that can be set with ATM:– Bandwidth– Flow control– delay– jitter– delivery– availability

… that is nothing new, where is the challenge?


Coordination and Management !


Service Overview• Management Boundaries

TEN-155 POP ATEN-155 POP B

MBS VCC

IP Service VCCIP ServiceVCC

IP Service VCC

MBS VCCMBS VCC MBS VCCMBS VCC

RouterRouter

Router

ATM Switch ATM Switch ATM Switch ATM Switch

NR

N Location N

RN

Loc

atio

n

Router

TEN-155

ATM Switch ATM Switch

Direct Connection MBSVCC

Directconnectedsubscriber

ATMequipm ent

Directconnectedsubscriber

ATMequipm ent

Direct Connection MBSVCC


TEN-155

TEN-155 AT

TEN-155 NL

TEN-155 HU

TEN-155 DE

ACONET

HUNGARNET

DFN switch

ENCART NETW ORK(14-06-1999)

Ars Electronica CenterLinz

SURFNET switch

Not ready VPs

Ready VPs

C3 Budapest

ACOnet Linz POP

DFN Karlsruhe

SURFnetATM network

PVC= 0/102(4717 cell/sec, cbr)


PVC=2/640(4717 cell/sec, cbr)

ZKM Karlsruhe


PVC=111/120(4717 cell/sec, cbr)


SURFNET Rotterdam




VP=111

VP=11

PVC=11/120PVC=11/1214717 cell/sec CBR


Last update 24-08-1999 11:30 BST

PVC= 1/1284717 cell/sec CBR

V2 Rotterdam

A good Example:


Three ways of doing things

GermanyNetherlandsUK

FranceGreeceSwitzerlandBelgium

SpainItalyAustriaHungaryCERNCzech RepublicPolandLuxembourgPortugalIsraelSloveniaIreland

Nordic Countries (SE, NO, IS, DK, FI)

Service in Place, operational procedures in place covering connected institutions

Defining Service, draft procedures

No Service defined, DANTE as a “proxy agent”, agreed procedures


The Group Network Manager

• From the project paticipants or users• Collects information from user nodes,

liasing with national ASM (ATM Service Managers)– technical– administrative

• Can “make things happen”:– technical knowledge– right contacts within National

organisations


What is the service scenario?

GERMANY (DFN)NETHERLANDS (SURFNET)UNITED KINGDOM (JANET)

FRANCE (RENATER-II)GREECE (GRNET)

SW ITZERLAND (SW ITCH)BELGIUM (BELNET)

SPAIN (REDIRIS)ITALY(GARR)

AUSTRIA (ACONET)HUNGARY (HUNGARNET)

CERNCZECH REPUBLIC (CESNET)

POLAND (POL-34)LUXEMBOURG (RESTENA)

PORTUGAL (RCCN)ISRAEL (IUCC)

SLOVENIA (ARNES)IRELAND (HEANET)

NORDIC COUNTRIES(NORDUNET)

TEN-155 MBS@ DANTEGroup Netw orkManager

1 2

3

3

Users


What we do

• Receive the contact from the project• Get information about the project:

– Sites– Bandwidth– Schedule

• If we consider it feasible, create a topology map, disseminate information and wait for the NRN green flag.

Set of organisations w ith bandw idth dem and.EC funded project, research, etc

Subm ission of project requirem ents to DANTE,by m ail or using ten-155 M BS w eb site.

CoordinatorProject Inform ationEquipm ent to connectCountries involved

Project IDMail to the ASMs with project id

Agreem ent on netw ork resources usage.Arrangem ents for national connections

betw een projects equipm ent and TEN-155 POP

Docum ent w ith the projects needs and how tosatisfy them .

Request is sent to the TEN-155 ATM NOC. Resolution of resource allocation conflicts.

AG

RE

EM

EN

TP

RO

PO

SA

L

Evaluation of TEN-155 M BS for the projectnetw ork needs. Group Netw ork M anager to

read service definition and procedures.


What we do next• Once the general requirements are

accepted, we ask for implementation details:

– Information about the sites.– Technical contact.– Administrative contact.– Equipment. – Time slots.– Bandwidth profiles.

We create the plan with that, and implement it.


And “detail” means:

Project Site:

Tech contact: (the one in control of ATM config) Name Address Phone Fax Mail NOC-mail (for outages and troubleshooting)

Admin Contact: (the one "owning" the port) Name Address Phone Fax Mail

ATM port: Equipment code (if existing) Address (ATM/IP?) Location: Address Room Rack Connectors positions Vendor information: Vendor Model Hardware/software revision Features

Remarks:

PVCs and Time slots:

Origin (Port@site): End (port@site): from (UTC time): to (UTC time): Periodic? (period specification) Usage (purpose, video, IP, best effort, etc) VPi or Vci: {VP/VC} vpi (local/remote) vci (local/remote) ATM traffic capability: {dbr/sbr2/sbr3} pcr (forward/backward) cells/seg src (forward/backward) cells/seg mbs (forward/backward) cells/sec BW in mbits/sec (generic requirement) (forward/backward) Comments on config (origin/end)


Does it work?


– one project (MECCANO/ERCIM)– 3 countries (DE, FR, UK)– January to end of March ‘99– Objectives:

» “to do something simple successfully”» to establish the procedures for using the MBS» to identify issues re: interworking with NRNs» to identify issues re: internal NRN workings

We have tested in an alpha phase...


… and beta:• Objectives:

– expansion to more projects in more countries– validation of procedures– resolution of issues identified in the alpha-test

• 8 projects/groups including:– 4 EC co-funded research activities– 2 research activities between universities and

research institutions– 2 research activities within QTP/TF-TANT

• 11 countries (AT, CH, DE, ES, FR, GR, HU, IT, NL, UK, + CERN)

• April to end of June 1999


Yes, it works.


EDISON, Application #1 : Spacecraft Validation

with ‘Hardware-In-the-Loop’

Real spacecraft, integrated in France Real motion system

for space proximity operations, in Germany

Close-loop & real-time flight simulation of the spacecraft: Delay and Jitter are critical: delay under 50 ms, with 5ms tolerance


TEN-155

TE N-155 GR

TE N-155 DE

TE N-155 NL

TE N-155 CH

TE N-155 IT

VP=6

GRnet S W ITCH-CE RN

DFN

GA RR

RUS (S tuttgart)

INFN B ologna

U. Tw ente

Diff-serv Experim entTF-TANT (11-06-1999)

Uni. U trecht

TE N-155 NL

TE N-155 CH

TE N-155 E S

TE N-155 DES W ITCH

RE DIRIS

DA NTE

S URFNET

VP=7

VP=8

VP=9

VP=4

Not ready VPs

Ready VPs

VP=10 VP=11

VP=5

VP=3

VP=12

VP=2

Updated 15-09-1999 22:10 BST

DIFF-SERV experiment(QTP / TF-TANT)


Pending issues

• Set-up time around one week.• Existing bandwidth and management

limitations.• It is not “plug and play”.


Next Steps

• Keep working on improving the actual service.– Create a good “ATM Service Map”

describing the actual status and procedures in all the countries. Make it user-friendly

• Look at the next generation European projects participating in the V Framework.

• Evaluating alternative techniques to support the service (MPLS, diff-serv)


Conclusion

• TEN-155’s Managed Bandwidth Service provides end-to-end guaranteed service today.

• It works in the multi-management domain.

• It will be continued in the next generation network, GEANT

• Can set the basis for developing similar services nationally.


References

• TEN-155– http://www.dante.net

• MBS– http://www.dante.net/mbs

• QuantumTest Program– http://www.dante.net/quantum/qtp

More info: [email protected]

management issues of the ten-155 mbs tnc 2000, lisbon 23 may 2000 management issues of the ten-155...

Documents