1 / 29

Monitoring Solution for Optical GRID Architectures

Monitoring Solution for Optical GRID Architectures. A. Binczewski, L. Grzesiak , E. Kenny, M. Stroinski, R. Szuman, S. Trocha, J. Weglarz. 2nd International Workshop on Distributed Cooperative Laboratories , 16th April 2007. Outline. C urrent GRID monitoring solutions,

harlan
Download Presentation

Monitoring Solution for Optical GRID Architectures

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. Monitoring Solution for Optical GRID Architectures A. Binczewski, L. Grzesiak, E. Kenny, M. Stroinski, R. Szuman, S. Trocha, J. Weglarz 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007

  2. Outline • Current GRID monitoring solutions, • Requirements for optical GRID monitoring solution, • Lambda Monitor software, • Deployments of LM software, • Further development of LM • Conclusion 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 2/29

  3. Current GRID monitoring solutions • The available software for GRID monitoring (e.g. R-GMA, MonALISA) focuses its attention on monitoring of upper-layers only (IP and application layers). • The biggest limitation concerningthe mentioned solutions for GRID architecture monitoring is the lack of publicly available and free (open source) software with the functionality for monitoring of the physical layer (L1) of the GRID networkresources (especially for optical networks). 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 3/29

  4. Current GRID monitoring solutions • Typically GRID monitoring solutions have ignored monitoring of the physical layer of the GRID’s network resources. • As wavelengths (lambdas) become key parts of GRID network resources, the requirement to monitor them will become a crucial task. • This is a non-trivial problem for optical GRIDs based on dedicated lambdas in the next generation DWDM networks. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 4/29

  5. Requirements for optical GRID monitoring solution • Features of monitoring system dedicated to optical GRID architecture • Capable of monitoring the physical layer of the GRID optical network resources. • A user must be able to view all lambdas that are part of a particular GRID network. • Identify and localise any alarms and faults easily. Including identifying which part of the optical layer of the GRID network is faulty. • Provide detailed information on the configuration of the GRID lambdas and the physical optical characteristics and parameters of each wavelength. • Speed up and facilitate the work of the GRID NOCs. • Open Source software tool which could be developed and extended by independent GRID/network communities or R&D projects for their own purposes and special requirements. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 5/29

  6. Lambda Monitor software • Lambda Monitor (LM) is the monitoring solution which can be used for optical GRID architectures. • It is this feature that distinguishes LM from other currently available GRID monitoring tools. • This application makes it possible to monitor many lambda circuits simultaneously and to notify in a real-time of current problems occurring in the network physical layer of the optical GRID. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 6/29

  7. Lambda Monitor software • By means of this application we are capable of affirming in a quick and exact manner which part of thelambda circuit (exactly which device) causes problems. • The LM system also provides users with much detailed information about the managed circuits on both lambda and device levels. • The LM has a user-friendly web-based front end that provides a visual representation of each lambda in the network. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 7/29

  8. Lambda Monitor architecture Fig. 1. Lambda Monitor architecture and operation scheme 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 8/29

  9. Lambda Monitor architecture • The Lambda Monitor has three levels of user interface (called layers) and additionally current and historical alarms browsers. • Lambdas layer • Devices layer • Parameters layer 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 9/29

  10. Lambda Monitor architecture • Lambdas layer • The first part of the user interface called “Lambdas layer” shows the current status of the monitored lambda circuits (end-to-end), • All three possible states of the lambdas: OK state - lambda circuit works OK without any alarms Warning state - occurs when some warning type alarms are present in the lambda circuit Critical state - occurs when any of Critical alarms appeared in lambda circuit 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 10/29

  11. Lambda Monitor architecture • Figure 2 illustrates an example view of different lambda states in “Lambdas layer” interface. Fig. 2. Lambdas layer interface 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 11/29

  12. Lambda Monitor architecture • Devices layer • The second level of the user interface whichshows the current status of the DWDM devices’ interfaces terminating selected lambda. • The possible states of the devices: 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 12/29

  13. Lambda Monitor architecture • Figure 3 depicts an example view of device interfaces’ states in the “Devices layer” interface. Fig. 3.Devices layer interface 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 13/29

  14. Lambda Monitor architecture • Parameters layer • This layer presents the current values of various monitored parameters on selected device’s interface in the form of graphical tables. • In these tables users can find very detailed information about many parameters which determine and influence the operation of lambdas used by e.g. the GRID infrastructure. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 14/29

  15. Lambda Monitor architecture • The “Parameters layer” is divided into the following tables: • Trail Termination – contains parameters for optical interfaces that terminate an optical trail; • TTPLP15min - The Interface Trail Termination (TT) Physical Layer Performance (PLP) 15 Min Interval Table contains statistics collected by an interface over the last 16 intervals (15 minutes each); • TTPLP24h - The Interface Trail Termination (TT) Physical Layer Performance (PLP) 24h Interval Table contains statistics collected by an interface over the last 2 intervals (24 hours each one); • FecCurrent15min - The otuFec Current 15 Minute table - values from the FEC mechanism; • FeCurrent24h - The otuFec Current 24 Hour table - values from the FEC mechanism; • Fec15minInterval - The otuFec 15 min Interval Table contains statistics collected by the FEC mechanism for an interface over the last 16 intervals; 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 15/29

  16. Lambda Monitor architecture • Figure 4 depicts an example view of the “Parameters layer” Fig. 4.Parameters layer – TrailTermination table 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 16/29

  17. Lambda Monitor architecture • Current alarms browser - enables viewing of information about alarms that occur currently in the monitored lambda circuits (figure 5). • Alarms history browser - presents all the alarms that occurred formerly (figure 6) 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 17/29

  18. Lambda Monitor architecture Fig. 5.Current alarms browser Fig. 6.Alarms history browser 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 18/29

  19. Deployments of LM software • As part of developing new services, PSNC and HEAnet are investigating ways to provide GRID users with direct access to lambdas. • In order to achieve this, new methods of monitoring optical resources mustbe provided to the Grid community in order for the GRID community to manage their own optical resources. • As part of this evaluation, the LM system has been successfully deployed in the real environments: • the National Research and Education Network in Poland - Pionier(Polish Optical Internet) • Ireland’s National Education and Research network - HEAnet. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 19/29

  20. Deployments of LM software • Pionier network • Architecture of the Pionier network embraces 21 ADVAFSP 3000 devices which form the core of the DWDM system, • The LM has been set up to monitor 24 of the 10Gbit/s lambdas used in the Pionier national backbone 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 20/29

  21. Deployments of LM software Fig. 7.Subset of the Pionier monitored lambdas 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 21/29

  22. Deployments of LM software • HEAnet network • Architecture of the HEAnet network consists of13 ADVAFSP 3000 devices which form the core of the DWDM system. • The LM has been set up to monitor nine of the 10Gbit/s point to point wavelengths used in the HEAnet national backbone. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 22/29

  23. Deployments of LM software Fig. 8.Subset of the HEAnet monitored lambdas 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 23/29

  24. Deployments of LM software • In these two large networks deployments Lambda Monitor proved to be a reliable and suitable physical layer monitoring system for such next generation networks which can also be used and dedicated to any optical GRID architectures. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 24/29

  25. Further development of LM • One of the main advantage of LM is its open source license which will enable individual GRID users to use and modify Lambda Monitor for their own GRID applications. • Future developments of Lambda Monitor may include the ability to partition the monitored wavelengths into individual GRID user groups that would enable GRID users to see only their wavelengths. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 25/29

  26. Further development of LM • Additionally web services interface may be developed for GRID applications to directly query the status of GRID wavelengths. • This web services interface could also be used for integration into the GEANT2 joint research activity perfSONAR. • Currently the LM supportsthe ADVA DWDM system, but we plan to extend support to other DWDM systems in the near future. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 26/29

  27. Conclusion • The available software for GRID monitoring focuses its attention on monitoring of upper-layers only (IP and application layers). • Unfortunately there is a significant lack of solutions which can monitor the physical (especially optical) layer of the GRID network resources, what surely is a considerable limitation. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 27/29

  28. Conclusion • Our LM system dedicated to monitor the optical GRID architectures exemplifies proposed by us the GRID monitoring solution needed today as well as in the near future. • Lambda Monitor software can be freely developed for future needs and requirements within independent projects and by GRID community thanks to its open source nature. 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007 28/29

  29. Lambda Monitor project websitehttp://gymnocladus.man.poznan.pl Thank you for your attention! 2nd International Workshop on Distributed Cooperative Laboratories, 16th April 2007

More Related