operational procedures and management in viola - dfn · operational procedures and management in...

Operational Procedures and Management in VIOLA 1/1 Günter Bürkel30.03.2005 T-Systems

Operational Procedures and Management in VIOLA

T-Systems are responsible for operational procedures and network management within theVIOLA consortium.VIOLA is a test bed for network approaches as well as a platform for application tests. One ofthe design goals of operational procedures is to minimize dependencies between applicationand network layers. Therefore coordination between application users, network test staff andT-Systems’ SMC (System Management Centre) is required. SMC is operating the VIOLAnetwork in close contact with users, fibre providers and equipment manufacturers. The SMCis focussing on Incident Management, Configuration Management, Maintenances, NetworkChanges, Release Management and SLA-Management.

The VIOLA network is complex and heterogeneous. The VIOLA transmission paths arebased on lambdas from Deutsche Telekom and several fibre providers. Network equipment isprovided by ADVA and Alcatel for WDM, Alcatel and Siemens for SDH, Alcatel andRiverstone for Ethernet switches.T-Systems SMC operates five different management systems as each manufacturercontributes one or more.

In-band management is difficult in such a heterogeneous environment. Furthermore VIOLA issupposed to change its topology in the next years. Therefore T-Systems have set up an out-band management with IP-Sec- and GRE- tunnelling over the existing G-WiN.

The network management will be in cooperation with FhG, University of Bonn andForschungszentrum Jülich while network tests are running.

Operational Procedures andManagement in VIOLABerlin, 27. April 2005

Seite 1

operational procedures and management inVIOLAGünter Bürkel, T-Systems,27.04.2005

Operational Procedures and Management in VIOLAVIOLA-Workshop,Berlin, 27. April 2005

! Günter BürkelT-Systems International GmbHHansastrasse 41D-90441 Nürnberg (Nuremberg)

[email protected]

Seite 2


Operational Procedures and Management VIOLA – challenges for Operations and Management

! Strike a balance between routineapplication use and network research

! Testbed with

• Lambdas from T-Com

• Fibres from T-Com, Gasline andothers

• Five different network managementsystems

• Transmission equipment from ADVA,Alcatel, Siemens, Sycamore andRiverstone

FZJülich

UniversitätBonn

FhG IMKSt. Augustin

FhG SCAISt. Augustin

CAESARBonn

FHBRS

RWTHAachen

UniversitätErlangen

T-ComNürnberg

Seite 3


Operational Procedures and Management VIOLA – challenges for Operations and Management

Net Management Center

Service Desk

Customer Network Manager

Reporter

Outband Management

eTTS

Configuration Management

Incident Management

ChangeManagementCarrier

Equipment Manufacturer

Major Changes

Maintenance

Release Management

Minor Changes

Operational Concept

T-Com

VDCN

??

???

?

?

?

Seite 4


Operational Procedures and ManagementSpecialised VIOLA Network Management

! SMC

! T-Systems’ “System ManagementCenter”

! Manages Routers and Ethernetswitches

! Responsible for (within VIOLA) :

• Alcatel 7750 SR

• Riverstone XGS 15008

• CISCO VDCN-routers

! NMC

! T-Com’s “Net Management Center“

! Manages WDM and SDHequipment

! Responsible for (within VIOLA) :

• ADVA FSP3000 and FSP1500

• Alcatel 1678 MCC

• Siemens hiT 7070 andSN16000

Seite 5


Operational Procedures and Management Specialised VIOLA Network Management

! System Management Center (SMC)

! T-Systems, Nuremberg

! Specialised in packet orientedservices

! Net Management Center (NMC)

! T-Com, Bamberg

! Specialised in circuit orientedservices

Seite 6


Operational Procedures and ManagementVIOLA Data Communication Network (VDCN)

! Out of band managementusing existing G-WiNstructures

! IPSec and GRE-tunneling toaddress security concerns

! Five management servers

! Additional monitoringpossible at FhG, FZ Jülichand University of Bonn

T-Com Nürnberg

VDCNSMC FZ Jülich

Uni Bonn

CAESAR

FhG

FH BRS

Uni Erlangen

G-

WiN

NMC

Terminal Server Router

Seite 7


Operational Procedures and ManagementOperational Processes

! T-Systems’ “Customer NetworkManager” (KNM) is responsiblefor operations processes inVIOLA

! Basis for operations is the“VIOLA Operations Concept”:

• Description of operationsprocesses

• List of contact persons

• List of authorised reporters

• List of networkcomponents

Seite 8



! T-Systems uses six main processes for operations:

• Incident ManagementProcess to clear fault

• Configuration Management

• Change Management

• Release Management

• SLA-Management

• Escalation Management

Seite 9


Operational Procedures and ManagementIncident Management

! Reporters are:

• SMC or NMC Operators

• T-Systems’ KNM

• “Reporters” at all VIOLAlocations

! T-Systems’ Service Desk isthe central gate for authorisedreports

! The Service Desk uses T-Systems’ “extended TroubleTicket System” (eTTS) fordocumentation

Reports FaultConfirms TT Closure(Phone, Fax, Web)

WDM, SDHT-Com loop

SwitchRouter

optical fibres

RiverstoneAlcatel

AlcatelSiemens

Service Desk T-Systems• Opens TT• Assigns responsible service area• Prepares documentation• Closes TT

Reporter

T-SystemsSMC

T-Com NMC

CarrierA, B ...

Seite 10


Operational Procedures and Management T-Systems’ extended Trouble Ticket System (eTTS)

Seite 11





• Configuration ManagementDocumentation of required configuration and inventory data

• Change Management


• SLA-Management


Seite 12


Operational Procedures and ManagementConfiguration Management

! Documentation ofrequired configurationsand inventory data

! Incident Managementusing eTTS and T-Systems’ databasesystem

! Backup of currentconfiguration

TSI - SMC NürnbergFH Bonn-Rhein-Siegr08juRiverstone 15008Switch

T-Com NMC BambergUni Erlangens70erSiemens hiT 7070Multiplexer

T-Com NMC BambergRWTH Aachenv15ju2FSP 1500 (RWTH Aachen)Multiplexer

T-Com NMC BambergFZ Jülichv15juADVA FSP 1500Multiplexer

T-Com NMC BambergFZ Jülicha78juAlcatel 1678 MCCMultiplexer

T-Com NMC BambergFZ Jülicha96juAlcatel 1996 Metro SPANWDM Gerät

TSI - SMC NürnbergFZ Jülicha50juAlcatel 7750 SRSwitch

TSI - SMC NürnbergFZ Jülichr08juRiverstone 15008Switch

TSI - SMC NürnbergCaesar Bonnr08caRiverstone 15008Switch

TSI - SMC NürnbergUni Bonna50bnAlcatel 7750 SRSwitch

TSI - SMC NürnbergUni Bonnr08bnRiverstone 15008Switch

T-Com NMC BambergUni Bonnv30bnADVA FSP 3000WDM Gerät

T-Com NMC BambergUni Bonna78bnAlcatel 1678 MCCMultiplexer

T-Com NMC BambergUni Bonns70bnSiemens hiT 7070Multiplexer

T-Com NMC BambergTSI SMC Nürnbergs16nuSiemens SN16000Multiplexer

T-Com NMC BambergDFN-Verein Frankfurtv15sa2FSP 15000 (Geant Ffm)Multiplexer

T-Com NMC BambergFhG St. Augustina78saAlcatel 1678 MCCMultiplexer

T-Com NMC BambergFhG St. Augustins70saSiemens hiT 7070Multiplexer

T-Com NMC BambergFhG St. Augustinv15saADVA FSP 15000Multiplexer

T-Com NMC BambergFhG St. Augustina96saAlcatel 1696 Metro SPANWDM Gerät

T-Com NMC BambergFhG St. Augustinv30saADVA FSP 3000WDM Gerät

TSI - SMC NürnbergFhG St. Augustina50saAlcatel 7750 SRSwitch

TSI - SMC NürnbergFhG St. Augustinr08sa2Riverstone 15008 SCAISwitch

TSI - SMC NürnbergFhG St. Augustinr08saRiverstone 15008 IMKSwitch

Provider /VerantwortlicherStandort

Host-nameGerätenameGerätetyp

Hardwarekomponenten im eTTS

Seite 13


Operational Procedures and ManagementConfiguration Management

T-Com NMC Bmbg 91100 91310 9 99W Faserpaar T-Com Nbg FAU Erlangen

T-Com NMC Bmbg 22410 91100 1 404 STM64 FhG-IMK T-Com Nbg

FhG 22410 22410 fhg1 99W Faserpaar FhG-SCAI FhG-IMK

SWB 22800 22410 swb1 99W Faserpaar Uni bonn FhG-IMK

Gasline 24610 22410 gas1 99W Faserpaar FZJ FhG-IMK

Gasline 69003 22410 gas1 99W Faserpaar DFN-Frau FhG-IMK

FH BRS 22410 22410 brs1 99W Faserpaar FH BRS FhG-IMK

caesar 22800 22800 cae2 99W Faserpaar caeser Uni Bonn

caesar 22800 22800 cae1 99W Faserpaar caeser Uni Bonn

FZJ 24100 24610 fzj1 99W Faserpaar RWTH Aachen FZJ

Provider/ Verantwort- licher ONKZ B ONKZ A

Ordnungs- nummer

Leitungs- schlüssel- zahl Leitungsart Endpunkt B Endpunkt A

Leitungskomponenten im eTTS

Seite 14






• Change ManagementProcess for maintenance and network changes


• SLA-Management


Seite 15


Operational Procedures and ManagementChange Management

Change Management

Minor Changesvirtual connections

Network ChangesMaintenance

Major Changesstructural changes

•Scheduled maintenance window on Wednesday10:00 to 14:00•Announced 2 days in advance

•non scheduled•announced seven days in advance

Seite 16


Operational Procedures and ManagementChange Management

CarriersManufacturers VIOLA Consortium

SMC / NMC

SMC / NMC CarriersManufacturers

FhG Birlinghoven

VIOLA SharePointServer and Email

announcement

checkup

monitoring

implementation

initialisation

VIOLA Consortium

Seite 17






• Change ManagementProcess for maintenance and network changes

• Release ManagementImplementation and Certification of new hardware and software

• SLA-ManagementService level agreements and Operational Availability Statistics

• Escalation Management1. Customer Network Manager 2. VIOLA Consortium

Seite 18


Operational Procedures and ManagementSummary

! T-Systems is responsiblefor operational proceduresand management in aheterogeneous researchtestbed

! NMC and SMC areresponsible for the stabilityof operations

! Operations ensures fairallocation of resources forthe requirements ofapplication users and thoseof network testing

Thank you.

operational procedures and management in viola - dfn · operational procedures and management in...

Documents