1. Connect. Communicate. Collaborate Place your organisation logo in this area End-to-End Coordination Unit Marian Garcia, Operations Manager, DANTE LHC Meeting, 21 st September 06, Utrecht

2. Connect. Communicate. Collaborate E2E Coordination Unit Role Active monitoring of an Inter Domain OPN (Optical Private Network) and management of the information flow related to the status of the end to end connection. For doing so –information can be gathered from the Inter domain monitoring tools provided or directly from the entities involved. –information will be periodically relayed to all the relevant parties

3. Connect. Communicate. Collaborate E2E Coordination Unit Set Up Entity appointed for the role Process Definition –Fault Report and Service restoration –Hours of Coverage –Escalation Procedures –Periodic Reports Tools to develop –Monitoring Tools –Trouble Tickets System –Data Base

4. Connect. Communicate. Collaborate Entity Appointed for the Role Communication et Systemes [CS] located in Paris Currently providing services as GEANT2 NOC Organized and supervised by DANTE

5. Connect. Communicate. Collaborate Fault Report and Restoration Network admin in T0 Centre NREN A NREN BGN2 Network admin in T1 Centre E2ECU Inter domain Monitoring Tools TT ENOC

6. Connect. Communicate. Collaborate Process Operational procedures are being drafted Fault Reports or Maintenances specifications –Via a web interface in the GEANT2 site –Via a dedicated phone number (TBE) –Via e-mail address (e2ecu@noc.geant2.net)e2ecu@noc.geant2.net Communication back to the entities involved –Via phone or e-mail in case of queries –E-mailed Trouble Tickets for relaying updated information

7. Connect. Communicate. Collaborate Process II Coverage –From 8.00 – 22.00 Monday to Friday –From 9.00 – 18.00 Saturday to Sunday Escalation Procedures: From the entities involved in a project to the E2ECU and vice versa! Monthly Reports to be provided describing the e2e links availability and tickets opened related to each specific project

8. Connect. Communicate. Collaborate Relation with ENOC While E2ECU will take care of the LHC connectivity, ENOC will take care of the ‘service’ (ie. IP service) For E2ECU, ENOC is a NOC to add to the list of NOCs belonging to the LHC project –It will receive updated TTs => These can then been forwarded to GGUS –It can contact E2ECU for queries

9. Connect. Communicate. Collaborate Monitoring Tools Each network domain shall use PerfSonar interface to store network status information Applications developed by JRA4 access that information and show the list of faulty circuits Further development is needed to integrate those outputs with more general applications used by the E2ECU: –Compatible with NAGIOS –Dashboards showing alarms correlated and with priorities that the help desk engineer can acknowledge

10. Connect. Communicate. Collaborate Trouble Ticket System Extension of the already existing system used by GEANT2 NOC Able 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 occurs in the first place => Then TT with the last updates forwarded to the remaining partners –E2ECU will not extract information from other domain TTs => information exchange via phone, e-mail or web interface

11. Connect. Communicate. Collaborate Data Base Containing information relating –Links –Projects –Contact information of the network administrators Accessible by the E2ECU Developed by DANTE

12. Connect. Communicate. Collaborate Time Scales Processes under development Pilot E2ECU service by Mid November => Focused in LHC support Full set up by January 2007 => Meanwhile temporal support provided by the ENOC

13. Connect. Communicate. Collaborate QUESTIONS?