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 • Inter-NOC communication • Documentation
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 4
Networks: A national infrastructure, …
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
Networks: Monitoring tools • 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 7
Metropolitan backbone 8
Overseas territories 9
Paris area 10
Example of scientific project 11
IPPM dashboard 12
Networks: DF Reference tools 13
Agenda • Network • NOC structure • Front end • Inter-NOC communication • Documentation
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) 15
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. 16
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 17
Agenda • Network • NOC structure • Front end • Inter-NOC communication • Documentation
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 19
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 20
Agenda • Network • NOC structure • Front end • Inter-NOC communication • Documentation
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 ? •
Agenda • Network • NOC structure • Front end • Inter-NOC communication • Documentation
Documentation: NOC documentation Deliverables part of the contract CMDB POP & Inventory management • • These are the tools used to manage the backbone infrastructure on 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) 24
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 25
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 » 26
Recommend
More recommend
