1 / 10

Circuit & LP Measurement: a few thoughts from G É ANT2

Circuit & LP Measurement: a few thoughts from G É ANT2. Michael Enrico, Maarten B ü chli, DANTE Joint Techs, Albuquerque 7 February 2006. Context (G ÉANT2 activities concerned with LPmon). JRA1 – perfSONAR Infrastructure Designed initially with layer-3 service monitoring in mind

talen
Download Presentation

Circuit & LP Measurement: a few thoughts from G É ANT2

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. Circuit & LP Measurement:a few thoughts from GÉANT2 Michael Enrico, Maarten Büchli, DANTE Joint Techs, Albuquerque 7 February 2006

  2. Context(GÉANT2 activities concerned with LPmon) JRA1 – perfSONAR Infrastructure • Designed initially with layer-3 service monitoring in mind • Now being asked to “extend” to incorporate L1/2 service monitoring JRA4 – CBF lambda usage development • Nearest term requirement • E2E (static) lambdas only(10G SONET/SDH and 10GE) • Tool(s) to be used by E2E NOC JRA3 – BoD service development • Started off with very wide remit (services & supported underlying technologies) • Now more pragmatic: E2E GE service (in the beginning) • But still expecting heterogeneous technologies & dynamism STILL EARLY DAYS! (not many answers, still lots of questions)

  3. Example CBF Pilot:DE-CH-IT • 3 countries(CH for transit only) • 3 NRENs involved • 4 legs with different equipment • 3 legs (Karlsruhe-Milano) on native WDM lambdas • Complication: Milano-Bologna dedicated lambda between production GARR routers Karlsruhe Basel 320km Manno 100km Milano Bologna 3 of 10

  4. JRA4 perspective:CBF (lambda) monitoring • Not (quality) measurement in the beginning but rather elementary status monitoring (phase 1) • Deconstruct E2E lambda into domain segments • Make a handful of parameters available (per lambda) for each segment • Still need to agree on these • Can be generic or service specific (or both) • Intention here is to enable an “E2E NOC” to troubleshoot an E2E lambda at the domain level • More detailed monitoring/troubleshooting left to domain NOC • Address quality measurement (“PM”) in phase 2

  5. Connect. Communicate. Collaborate E2E lambda service Assume back-to-back transponders at domain demarcs What about “local loops” (last WDM transponder to service demarc)

  6. Connect. Communicate. Collaborate WDM muxes at demarcs Assume all transponders have an instrumented line (WDM) and client (B&W) side line-side parameters client-side parameters

  7. Connect. Communicate. Collaborate Local loop complications • What is nature of “local loop” (access A)? • null, dark fibre, leased circuit, virtual circuit…

  8. Connect. Communicate. Collaborate Status parameters (1st stab) NOTES: • Simple status parameters • Service independent • Naming not fixed: • use words likeRx status (=up/down) orLOS (=true/false) ? • Lambda status (=ip/down/degraded?) • what constitutes “degraded”? • Dependence on capabilities of underlying transmission equipment still present • so optical power level parameters should perhaps be optional • Some parameters may need to be synthesised (correlated) from others

  9. Adding E2E PM • Defer to later stage • Not easy to be done “in-service” • Parameters likely to be service-specific • BBE, ES, SES for SONET/SDH • Frames in/out/errored for 10GE • However, not all 10GE transponders are frame aware! • Collect and correlate FEC statistics? • May not be easy to correlate(dependence on FEC algorithm)?

  10. JRA3 perspective • Collaboration with JRA1/4 • Monitoring framework similar to CBF • Single point of contact (e2e NOC) • Initially domains advertise up/down status • Later on also advertise performance info • Main focus is on interdomain gigabit ethernet services • Heterogenous underlying technologies • Technology specific parameters not relevant to e2e NOC and users. Use them to determine up/down status? • Export common set of ethernet parameters

More Related