1 / 29

SA2 report

This report provides an overview of different SA2 activities discussed during the ARM-8 meeting in Athens, including ENOC and LHC.OPN updates.

sceaser
Download Presentation

SA2 report

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. SA2 report Jules Wolfrat (SARA) ARM-8 – Athens, 2006-11-07

  2. Outline • Overview of different SA2 activities • Slides borrowed form EGEE’06 presentations: • ENOC – Mathieu Goutelle – CNRS UREC • LHC OPN – David Foster - CERN • E2ECU – Toby Rodwell - DANTE • SA1 issues ARM-8 – Athens, 2006-11-07

  3. Information sources • TNLC – Technical Network Liaison Committee • Discussion forum between NRENs and SA2 • Meetings at EGEE conferences • LHC OPN – LHC Optical Private Networks • Agenda last meeting (September 21) http://indico.cern.ch/conferenceDisplay.py?confId=a062977 ARM-8 – Athens, 2006-11-07

  4. Technical Network Liaison Committee Status of the ENOC Mathieu Goutelle (EGEE-SA2, CNRS UREC) EGEE’06 conference – Geneva, 2006-09-28

  5. First objectives • Creating a “Network Support unit” in the EGEE operational model; • Interface between NRENs, GEANT and EGEE operations • Based on the work done during EGEE: • Definition of the ENOC: tasks, requirements, tools; • Definition of the actors, interfaces and procedures; • Tests on a limited set of NRENs. • First implementation in EGEE-II: • First “iteration”; • Planned developments in the next months. ARM-8 – Athens, 2006-11-07

  6. ENOC tasks • Collect tickets from NRENs which agree to send them to the ENOC; • Forward to GGUS the ones that seem relevant (possible impact on the grid infrastructure); • Receive tickets assigned to ENOC by the GGUS TPM (1st level support); • Troubleshoot them provided that the ENOC has access to suitable monitoring tools; • Contact identified faulty domains or reassign ticket to the associated site if there is no evidence of a backbone problem (e.g. LAN issue). ARM-8 – Athens, 2006-11-07

  7. EGEE Network SupportUnits NRENs ENOC GGUS GÉANT2 Users Current ENOC status • Interface with NRENs is running like in EGEE: • ENOC receives Trouble Tickets (incident, maintenance) from GÉANT and the NRENs (currently France, Germany, Greece, Hungary, Ireland, Italy, Russia, Spain, Switzerland, and United Kingdom); • More to come: Poland, the Netherlands, Czech Republic; • Forward it to GGUS after analysis and if relevant to EGEE (using CIC portal?) • Identified as the Network Support unit in GGUS: • 2nd level support for network related issues. ARM-8 – Athens, 2006-11-07

  8. Current ENOC status (cont.) • Interface with NRENs: • Via emails: no standardization; • Languages issue: 8 different languages; • Current work on TT standardization via the TNLC (see later). • Interface with GGUS: • Use of web services, alike the (ex-)CIC portal; • This was not planned to be available so quickly (thanks to FZK for their swift work!); • Currently being tested under maximum load since the beginning of the month. • Network Operational Database: • Same function as the GOCDB for the ENOC; • Contains info (contact, available services, etc.) on the interconnections of network domains between EGEE sites; • Need now to consolidate the stored information! ARM-8 – Athens, 2006-11-07

  9. Conclusion • Currently running according to plans: • First iteration of the implementation; • Procedures are iteratively refined and enhanced; • Tools are being developed to improve the information channel and ease the processes; • Summary of issues: • Still some NRENs missing; • Consolidation of the data in the Network Operational DB; • Monitoring tools? • Support for the OPN: interim phase, runtime phase? ARM-8 – Athens, 2006-11-07

  10. TNLC Meeting LHCOPN Status David Foster Communications Systems Group Leader CERN IT-CS ARM-8 – Athens, 2006-11-07

  11. LHCOPN Architecture (2004-2006) ARM-8 – Athens, 2006-11-07

  12. ARM-8 – Athens, 2006-11-07

  13. OPN Organisation • LHCOPN Meetings 4 times a year • Organised as a sub-activity of the GDB • Current Working groups • Operations (Dante) • Monitoring (USA) • Routing (CERN) • Security (UK) • Working group evolution • Routing will become a long term technical body • Monitoring will evolve to become more technical network management including tool selection and deployment • Operations will continue to be the problem determination and resolution • Security will continue to be an advisory and policy body. ARM-8 – Athens, 2006-11-07

  14. OPN Status Summary ARM-8 – Athens, 2006-11-07

  15. Operational Status • Several links “in production” but coherent operational management across organisational domains must be organised. • Agreement has been reached to deploy one initial monitoring tool “Perfsonar” across all domains. • Workshops have been held (Dante) • Munich 19 July 06: DANTE, DFN, REDIRIS, GARR, SURFnet, NORDUnet, RENATER, CERN (and LRZ-Munich) • Toronto 18-19 September 06: DANTE, I2, ESnet, TRIUMF, Canarie, FNAL, USLHCNET • End-to-End coordination unit (E2ECU) being implemented by Dante as part of the overall NOC – Full Operation January 2007. • ENOC providing information integration with Grid Operations (EGEE-SA2) working closely with E2ECU • All operational information documented on the LHCOPN Twiki: http://lhcopn.cern.ch ARM-8 – Athens, 2006-11-07

  16. End-to-End Coordination Unit Toby Rodwell, Network Engineer, DANTE TNLC, 28th September 06, Geneva

  17. E2E Coordination Unit • Purpose • To communicate the state of international end-to-end circuits (transiting GN2) to all appropriate entities (transit domains, end-sites) • Responsibilities • Monitor (indirectly) the state of all end-to-end circuits • Receive reports from all involved entities of changes to circuits (faults, planned maintenance) • Advise all entities of known changes to circuits (learned from direct reports and E2ECU monitoring) ARM-8 – Athens, 2006-11-07

  18. Assumptions • An end-to-end circuit is considered to exist between the CPE (“Customer Premises Equipment”) at one end site and the corresponding CPE at the other end-site. • For LCG this means between the CERN access router and the corresponding Tier 1 CPE (router) • The transit NRENs deploy appropriate monitoring tools (e.g. those developed by perfSONAR) ARM-8 – Athens, 2006-11-07

  19. Caveats/Notes • The E2ECU will able to co-ordinate all trans-GÉANT2 circuits, but is currently organized with the LHC Optical Private Network (OPN) in mind • The E2ECU is not contactable by end-users – only campus network admins • The E2ECU is responsible for facilitating communications about end-to-end circuits – it is not responsible for the circuits themselves • Responsibility for the constituent circuits of an end-to-end circuit remains with the owners (NRENs, DANTE) ARM-8 – Athens, 2006-11-07

  20. E2E Coordination Unit Set Up • Appoint organization to undertake E2ECU role • Deploy Tools • Monitoring Tools • Trouble Ticket System • Database • Develop Policies and Procedures • Fault Reporting and Service restoration • Hours of Coverage • Escalation Procedures • Periodic Reports ARM-8 – Athens, 2006-11-07

  21. E2ECU Parent Organization • Communication et Systemes [CS] located in Paris • Currently providing services as GÉANT2 NOC • Organized and supervised by DANTE ARM-8 – Athens, 2006-11-07

  22. Trouble Ticket System • Extension to existing system used by GEANT2 NOC • Will be possible to send e-mails to specific community of users depending on the fault’s impact • Periodic updates • Updates to the E2ECU from the domains where the fault first occured => Then TT with latest updates forwarded to the remaining partners Note: Unlike current ENOC, E2ECU will not extract information from other domain TTs (all communication via phone, direct e-mail or web interface) ARM-8 – Athens, 2006-11-07

  23. Database • Extension to existing GÉANT2 database • Will contain information on • Links • Projects • Contact information of the network administrators • Accessible by the E2ECU • Developed by DANTE ARM-8 – Athens, 2006-11-07

  24. Fault Report and Restoration E2E Monitoring System E2ECU ENOC TT T0 Centre T1 Centre NREN B GN2 NREN A MA/MP ARM-8 – Athens, 2006-11-07

  25. Relation with ENOC • E2ECU monitor LHC connectivity (circuits) • ENOC manage the ‘service’ (ie. IP service) • For E2ECU, ENOC is treated like all other NOCs which are part of the LHC OPN • ENOC will receive updated TTs • These will be forwarded to GGUS • ENOC can contact E2ECU (for queries etc) ARM-8 – Athens, 2006-11-07

  26. Road Map • Processes being developed • Pilot E2ECU service planned for mid November • Focused on LHC support • Full set up by January 2007 • Temporary support for LHC to be provided by the ENOC ARM-8 – Athens, 2006-11-07

  27. Other SA2 activities • Common Trouble Ticket Schema • Network SLA implementation ARM-8 – Athens, 2006-11-07

  28. SA1 questions • Goal of GGUS tickets entered by ENOC? • ENOC Network operational Database • Why not part of GOC DB? • Overlap with E2ECU DB? • Different operational organisations - ENOC, E2ECU • ENOC interface to E2ECU for EGEE users and admins ARM-8 – Athens, 2006-11-07

  29. ARM-8 – Athens, 2006-11-07

More Related