1 / 18

WP4 – Network implementation and operation

WP4 – Network implementation and operation. Review of WP4 Objectives. Planned Activities. A4.1 - Define operational procedures February 2006 GRNET – Costas Kotsokalis A4.2 - Define acceptance tests January 2006 – March 2006 RoEduNet – Octavian Rusu A4.3 - Deliver equipment and connections

teague
Download Presentation

WP4 – Network implementation and operation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP4 – Network implementation and operation Review of WP4 Objectives The SEEREN2 initiative is co-funded by the European Commission under the FP6 Research Infrastructures contract no. 026748

  2. Planned Activities • A4.1 - Define operational procedures • February 2006 • GRNET – Costas Kotsokalis • A4.2 - Define acceptance tests • January 2006 – March 2006 • RoEduNet – Octavian Rusu • A4.3 - Deliver equipment and connections • January 2006 – May 2006 • A4.4 - Adjust equipment configuration • January 2006 – September 2006 • GRNET – Yannis Mitsos • A4.5 - Technical support in stable operation • January 2006 – March 2007 (end of the project) • UoB – Slavko Gajin

  3. Planned effort per activities • A4.1 - Define operational procedures • A4.2 - Define acceptance tests • A4.3 - Deliver equipment and connections • A4.4 - Adjust equipment configuration • A4.5 - Technical support in stable operation

  4. Deliverables • D9 and D12 • D9 - Acceptance tests specification and network implementation (confidential) • a. RoEduNet – 4/1/2006 – Octavian Rusu, end of A4.2 - Define acceptance tests (split a and b) • b. RoEduNet – 10/1/2006 – Octavian Rusu; A4.4 - Adjust equipment configuration • D12 - SEEREN2 management framework and VNOC operations (public) • a. RoEduNet – 11/1/2006 – Octavian Rusu; start of operation for the entire topology RoEduNet – 11/1/2007 – Octavian Rusu

  5. A4.1 - Define operational procedures • Responsible person: Costas Kotsokalis – GRNET • February 2006 – March 2006 • Objectives • Define operational procedures for VNOC operation • Input • Based on SEEREN experience • Network topology • Special questionnaire about NRENs operational procedures (next week??) • Output • Information flow between participants • Access rights to equipments for participants • Access rights to monitoring tools for public and participants • TTS operation

  6. A4.1 - Define operational procedures - Virtual NOC Framework NME Help Desk Operator # SIE # APMs NOCs • NME • Network Management Entity • Yannis and Costas • HelpDesk • HelpDesk RT – email to APMs • SIE • Service Implementer Entity • SEEREN NOC • Network Operation Center • APMs • Access Port Managers • Operator • Carrier/Service Providers • PSC – Project Steering Committee PSC

  7. A4.1 - Define operational procedures – VNOC: Network Management Entity • The technical core of the management team for the entire network • proposes the main network policies, including the network evolution and upgrades of equipments and services to PSC; • performs the high level design of all services; • decides about special solutions and services by appropriate Service Implementer Entity (SIE); • coordinates the Help Desk activities • responsible for the technical integrity of the services provided on the network; • implements new services using configuration solutions provided by SIEs; • technically defines and modifies network policies; • plans network development; • operates the Help Desk, which interacts with: • APMs; • Operators, to provide fault isolation and management of the links and/or services supervised by a different authority; • SIEs, during testing period for new services. • operates the Trouble Ticket System

  8. A4.1 - Define operational procedures – VNOC: SIEs – Service Implementer Entities • Specialized task teams distributed in the service dimension • provide studies for proposed services by NME, specifying issues of interest for the network objectives and policies; • provide configuration files for network equipment to implement the proposed services; • interact with NME during service activation; • report through the Help Desk problems related to a service; • monitor service operation using network management tools during the implementation period.

  9. A4.1 - Define operational procedures – VNOC: APMs - Access Port Managers • Manager of geographically distributed teams (one for each NOC) responsible for the local NOC activities • monitor the network operation in their area of authority; • configure the local communications equipment; • monitor the implementation of the services within their NOCs; • interact with NME to maintain the centralized management system; • interact with the users at the NOC level

  10. A4.1 - Define operational procedures – VNOC: Advantages • Centralized character for network operation • all information flows through the NME • Distributed and hierarchical character achieved trough: • APMs • provide network management and user support within a geographical area of authority • SIEs • responsible for particular services implementation on the entire network. • interaction between SIEs and APMs is handled by NME providing consistency of all operations. • operation of NOCs and even the service implementation procedures are distributed and can be outsourced • Establishes the responsibilities of each unit involved in the management process • Precise split of functions to different groups and users • Can be implemented using a mix of distributed and centralized strategies • Implementation – software tools: centralized and distributed components

  11. 4A.2 – Define acceptance tests • Responsible person: Octavian RUSU - RoEduNet • February 2006 – March 2006 • Objectives • Define a set of acceptance tests for links, equipments and for the final topology • Define a procedure for the tests and establish the necessary conditions • Input • SLA • Network topology • Connectivity solutions • Equipment list for each NOC • Output • D 09a - Acceptance tests specification and network implementation 4/1/2006 • Accept the connections !

  12. Specification of Acceptance Tests • Connectivity • Basic connectivity • Bandwidth • Packet loss • Routing • BGP configuration • QoS • One way delay • Jitter • Packet reordering • Shaping ??

  13. Work Station Configuration • PC • Rude/Crude • NEW: MGEN – to be studied • Configuration: • Gigabit Ethernet network card • Switched environment or direct connection to the router • GNU/Linux operating system, kernel version 2.4.18 or later • iputils package • Python • NTP client package

  14. Connectivity End to end test for each connection Basic connectivity Classic ping command Executed from the router (extended ping) Bandwidth, Packet and QoS Using rude/crude as in SEEREN Different packet size 64, 128, 256, 512, 1024, 1280, 1500 Bytes Output No. of packets received No of packet loss Total Bytes Average delay Jitter Max jitter Throughput Various graphs Conditions to accept the connection: Based on packet loss?

  15. Routing • BGP configuration • List of BGP neighbours • To be completed… • Sofia, Belgrade and Budapest – most interesting and challenging configurations • BGP verification • sh ip bgp summary • sh ip bgp • sh ip bgp neigh A.B.C.D advertised-routes

  16. A4.3 - Deliver equipment and connections • January 2006 – May 2006 • Responsible: Third parties • Objectives • Deploying the initial configuration of links and equipment for all participating NRENs, according to the project goals • Initial configuration should pass the acceptance tests • Network monitoring tools deployment (SNMP, FlowScan etc.) • Input • Tender evaluation results • Initial configuration • Network Topology • Output • Final working topology • Final equipments configurations • Working set of management tools

  17. A4.3 - Deliver equipment and connections: Management tools • NetIS- The Network Information System - developed by AMREJ and hosted at Belgrade University Computing Center • Nagios - host, service and network monitoring software running on central management server • Looking Glass: Tools for fast web-based (read-only) access to the routers • Helpdesk and Trouble Ticket System – RT • The SEEREN Helpdesk provides services only to the SEEREN NREN NOCs. • Other Tools: • RANCID- used for the CVS repository of router configuration • SmokePing - network latency monitor which works in a way that is similar to MRTG • WeatherMap - perl tool that displays in a web page the utilization of the network links • Cricket • NEW: OpenNMS

  18. A4.4 - Adjust equipment configuration • April 2006 – September 2006 • Responsible person: Yannis Mitsos - GRNET • Objectives: • Adjusting the equipment and link configuration in order to improve performance and solve different issues and incompatibilities • Network performance analysis (traffic monitoring and optimization) • Input: • Tender evaluation results – D 06 • Network topology – D07 • Equipments type and hardware configurations • NRENs special requirements (if any) • Output: • Initial network performance analysis • Final equipments configurations • SEEREN2 management framework and VNOC operations - D12a/b

More Related