1 tnc2009:noc panel discussion dirk haex coordinator networks 09/06/2009

22
1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

Upload: janis-johnston

Post on 13-Jan-2016

219 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

1

TNC2009:NOC panel discussion

Dirk HAEXCoordinator Networks09/06/2009

Page 2: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

2

Page 3: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

3

Agenda

- BELNET in a nutshell

- Helpdesk and NOC evolution a long time ago / some time ago

lessons learned today: approach and tools

- ‘Scripted’ change management

rationales

example and advantages

Page 4: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

4

BELNET in a nutshell

15 years BELNET

- More… autonomy

employees bandwidth and resilience networks and services customer oriented

- But… change in statute necessary!

Page 5: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

5

BELNET in a nutshell

Current organisation

24x7 Helpdesk

24x7 NOC

Page 6: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

6

BELNET in a nutshell

The BELNET network

35 ROADMs4 core routers33 access routers63 x 10 Gbit/s connections

Page 7: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

7

BELNET in a nutshell

Other networks

- BNIX 3 devices, 3 x 10 Gbit/s

69 connections layer 2 platform focussed on commercial market

- FedMAN Belgian federal MAN

68 devices, 70 x 1 Gbit/s 45 connections

Page 8: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

8

Helpdesk and NOC evolutionA long time ago

- Internal Helpdesk and NOC (Business hours)

Page 9: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

9

Helpdesk and NOC evolutionSome time ago

- Internal Helpdesk & NOC (Business hours)

- 24x7 ‘Watch Service’ for the backbone

Page 10: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

10

Helpdesk and NOC evolutionIn 2006...

- First experience with NOC outsourcing- Incident and Change Management- 24/7Helpdesk and NOC for FedMAN- 3 layers: Helpdesk – NOC - BELNET

Page 11: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

11

Lessons learned (1)

- Outsourced incident management

added value? Yes!

clear procedures customer is ‘key’ close follow-up collaborative tools beware of pitfalls

Helpdesk and NOC evolution

Page 12: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

12

Lessons learned (2)

- Outsourced change management

added value? Not really

time consuming potentially dangerous

→ reputation

→ reaction from employees

Helpdesk and NOC evolution

Page 13: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

13

Today: approach and tools (1)

Helpdesk and NOC evolution

Incident Management

Outsourced (transparant)

24x7

Phone and e-mail

3 layers contact

Change Management

BELNET

Business hours

Phone and e-mail

Direct contact

Support / Advice

BELNET

Business hours

Phone and e-mail

Direct contact

Page 14: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

14

Today: approach and tools (2)

Helpdesk and NOC evolution

Page 15: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

15

Helpdesk and NOC evolutionToday: approach and tools (3)

Page 16: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

16

Helpdesk and NOC evolutionToday: approach and tools (4)

24/7 BELNET Helpdesk

BELNET customer

Monitoring

outsourced

Ticketing system

CRM

NOC

Services

Networks

Customer update

Page 17: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

17

- Change in expectations- ‘always on’ - commodity- new business models

- Take nothing for granted - 24x7 organisation is not

trivial - anticipate the workload - talk with your peers!

Helpdesk and NOC evolutionConclusions

Page 18: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

18

- Script to automate configurations

- Backbone design BGP full mesh

MPLS LSP full mesh

- Change Management IP services

PtP Ethernet services

‘Scripted’ change managementRationales

Page 19: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

19

- BELNET customer: static routing

- Before: manual configuration:

logical interface

anti-spoofing filter policer to ratelimit traffic static route

- Now: scripted! all parameters on 1 line!

‘Scripted’ change managementExample and advantages (1)

Page 20: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

20

- Concrete case: KHLEUVEN customer category

commercial bandwidth interface ptp subnet type of routing customer prefix(es)

‘Scripted’ change managementExample and advantages (2)

“ADD research 100m fe-3/0/0.0 193.191.9.16/29 static prefix=193.190.138.0/24”

Page 21: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

21

- Benefits:- Single line concept

automated configuration

uniform & consistent config

same syntax everywhere much more efficient detect config anomalies

- Smooth integration with tools

‘Scripted’ change managementExample and advantages (3)

Page 22: 1 TNC2009:NOC panel discussion Dirk HAEX Coordinator Networks 09/06/2009

22

Thank you for your attention. Any questions?