RENATER / TF-NOC Flash presentation February 15 th -16 th 2012 - - PowerPoint PPT Presentation

renater tf noc
SMART_READER_LITE
LIVE PREVIEW

RENATER / TF-NOC Flash presentation February 15 th -16 th 2012 - - PowerPoint PPT Presentation

RENATER / TF-NOC Flash presentation February 15 th -16 th 2012 frederic.loui@renater.fr Agenda Network NOC structure Front end Inter-NOC communication Documentation Agenda Network NOC structure Front end


slide-1
SLIDE 1

RENATER / TF-NOC

Flash presentation

frederic.loui@renater.fr

February 15th-16th 2012

slide-2
SLIDE 2

Agenda

  • Network
  • NOC structure
  • Front end
  • Inter-NOC communication
  • Documentation
slide-3
SLIDE 3

Agenda

  • Network
  • NOC structure
  • Front end
  • Inter-NOC communication
  • Documentation
slide-4
SLIDE 4

4

Networks: RENATER organization at a glance

  • RENATER is non profit organization funded by

public institution

  • 12 members + Ministry of Education and Research Network
  • Headquarters in Paris

3 spoke sites (Rennes, Montpellier, Grenoble)

  • 53 persons
slide-5
SLIDE 5

Networks: A national infrastructure, …

slide-6
SLIDE 6

Networks: some figures …

  • A national coverage with high capillarity
  • 11 900 km of Dark Fiber, 125 links , 72 POPs (NR), 84 shelters (hut)
  • Optical link : 125 lambdas at 10G over 11900 km of DF
  • 200 DWDM chassis over the French national territory.
  • 1346 ports in metropolitan area and overseas
  • 665 connected institutions
  • Traffic: Cumulated traffic rate ~ 100Gbit/s, 60 Po exchanged in 2010
  • Application services
  • 10 000 electronic certificates delivered
  • 30 000 (RMS)phone calls/year
  • Antispam: 550 000 mail accounts, 2 000 000 filtered emails / day
  • WIFI access eduroam : more than 150 operational institutions, 50 000

request/day in France

  • Mailing list diffusion « Universalistes » : 400 000 accounts
slide-7
SLIDE 7

Networks: Monitoring tools

7

  • Passive measurement
  • SNMP polling  Home made SNMP poller
  • Netflow collector  RENATER home made netflow collector
  • Active measurement
  • Cheetah beacon for active measurement. (IPv6/v6, unicast /

multicast, IPPM statistics)

  • Network Weathermap
  • YANMP (Yet Another Network Weathermap)
  • Home made SNMP/Netflow statistics portal
  • Alarm and fault reporting
  • NAGIOS
  • Network Config Checker
  • Planning / Operation
  • RENATER GIS based on OpenStreetMap
slide-8
SLIDE 8

Metropolitan backbone

8

slide-9
SLIDE 9

Overseas territories

9

slide-10
SLIDE 10

Paris area

10

slide-11
SLIDE 11

Example of scientific project

11

slide-12
SLIDE 12

12

IPPM dashboard

slide-13
SLIDE 13

13

Networks: DF Reference tools

slide-14
SLIDE 14

Agenda

  • Network
  • NOC structure
  • Front end
  • Inter-NOC communication
  • Documentation
slide-15
SLIDE 15

15

NOC Structure: Roles and coverage

  • Service Desk (24/24, 7/7)
  • 8 persons ensuring level 1 support
  • SME change manager
  • 3 subject matter experts responsible for complex change
  • Incident manager
  • Main RENATER SPOC in case of potential issues in the Network
  • Tools manager
  • Responsible for tools availability/developement mandatory to

manage the infrastructure

  • Delivery manager
  • Operational coordination within the NOC
  • Contract manager
  • Administrative/Process manager ensuring that the outsource NOC

processes and services conforms the outsourced signed contract. (SPOC for escalation)

slide-16
SLIDE 16

16

NOC Structure: Organisation

  • Outsourced NOC
  • Based in a central place
  • BCP/DRP process and site available
  • Pros and Cons
  • Cons: « Jamais mieux servi que par soi même ». Tight follow-up essential.
  • Pros: 24/24, 7/7 model not easy to adapt to public organization. Additional

support available. (BT mutualized resource) Organization structure that has a critical mass that can handle turn-over.

  • Periodic meetings
  • « Comité d’exploitation »: Operational committee
  • Operational aspect discussed
  • New technical service deployment etc.
  • « Comité de Pilotage »: Steering committee
  • Pain points discussed.
  • Contract conformance deviation.
slide-17
SLIDE 17

17

NOC Structure: Communication tool

  • With RENATER: Dedicated portal
  • Change management tool: RT queues
  • RENATER document management tool: Alfresco
  • With others partner:
  • 3rd party service provider already available specific tools
  • TT systems, Service provider portal
  • Not that much integration
slide-18
SLIDE 18

Agenda

  • Network
  • NOC structure
  • Front end
  • Inter-NOC communication
  • Documentation
slide-19
SLIDE 19

19

Front end: Our users

Users’ community :

  • Public teaching institute
  • Publics/ (with private partnership) research institute
  • Other institutions or private company (R&D activity,

Scientific Research activity)

  • 665 institutions connected
slide-20
SLIDE 20

20

Front end: Users agreement

Agreement with our users :

  • Official signed contract
  • Service description
  • Service Level Agreement (Availability, MTR etc.)
  • Tools to keep track of our customers
  • Legacy tools: Phone, Mail, IM
  • Customer portal (Statistic such as bandwidth consumption)
  • Fault handling: RT Trouble Ticket Management
slide-21
SLIDE 21

Agenda

  • Network
  • NOC structure
  • Front end
  • Inter-NOC communication
  • Documentation
slide-22
SLIDE 22

Inter-NOC communication

  • Internally
  • Legacy communication tool: Mail, Phone etc.
  • RT queues when the subject applies to RENATER’s request
  • With RENATER: Dedicated portal
  • Change management tool: RT queues
  • RENATER customers: Mailing list
  • Alfresco
  • Configuration management
  • With others:
  • 3rd party service provider already available specific tools
  • TT systems, Service provider portal
  • Not that much integration
  • Which tools are used to facilitate inter-NOC communication?
  •  That’s a good question ! Discussion ?
slide-23
SLIDE 23

Agenda

  • Network
  • NOC structure
  • Front end
  • Inter-NOC communication
  • Documentation
slide-24
SLIDE 24

24

Documentation: NOC documentation

Deliverables part of the contract

  • CMDB  POP & Inventory management
  • These

are the tools used to manage the backbone infrastructure

  • n

a daily basis (POP/Inventory/Contact management)

  • Operational process guide
  • Quick operational process guide meant to describe how to

interact with 3rd party service providers. (Escalation guide etc.)

  • Operational guide
  • Quick operational guide meant to describe specific migration

steps co-written by RENATER and NOC SME. (Subject Matter Expert)

  • Implementation guide
  • Extensive implementation guide meant to describe specific

subject/service implementation. (co-written by RENATER and NOC SME)

slide-25
SLIDE 25

25

Documentation: Tools

Tools used to manage documentation

  • CMDB management
  • Proprietary software for Hardware management & Inventory
  • Document management
  • Alfresco
  • Documention production/updates
  • Libre-Office / MS-Office suite
slide-26
SLIDE 26

26

Documentation: Best practice process

Best practice process with Outsource NOC

  • Step 1: Specification document
  • Complete definition of the network service to be deployed
  •  Responsibility: RENATER
  • Step 2: Implementation document
  • Complete document describing extensively how the service

is EFFECTIVELY configured / deployed.

  •  Responsibility: NOC
  • Step 3: Implementation/Automated verification
  • Based on the documents  effective implementation
  • Automated&periodic verification: « Home made tools NCC »
slide-27
SLIDE 27