cinkler@bute a21: resilience strategies in mmm networks qor: quality of resilience by tibor cinkler...
TRANSCRIPT
cinkler@BUTE
A21: Resilience Strategies in MMM Networks QoR: Quality of Resilience
By Tibor Cinkler
NOBEL WP2 May 18 Berlin 2cinkler@BUTE
Three Topics:
• Activities and Workplane WP2 A21: 15 min, May 18 14:00
“Resilience Strategies in 3M Networks”
• Technical presentations May 18 16:00
“On Quality of Resilience (QoR)”
• Technical presentations May 18 16:00
“Brief explanation of BUTE SW tool for inter-domain and intra-domain routing”
NOBEL WP2 May 18 Berlin 3cinkler@BUTE
1. “Resilience Strategies in MMM Networks”: Activities and work-plan of WP2 A21
Protection/restoration in multi-layer/domain/service networks
M5: Glossary for Resilience
M6: QoR: Quality of Resilience– Definition of required levels of Resilience / Reliability / Protection / Restoration
– Classification of Services According their QoR requirements
M7: Reference network for 3M resilienceNoE e-Photon/ONe (and IP NOBEL) European Reference Network
Topology, resources, traffic
NOBEL WP2 May 18 Berlin 4cinkler@BUTE
1. “Resilience Strategies in 3M Networks”: Activities and work-plan of WP2 A21
M8: Overview of Resilience Mechanisms in MultiLayer networks
- How GMPLS/ASTN supports resilience? (Ctrl and Mngmnt)
- Proposals for potential extension of the Ctrl plane to better support resilience
- Resilience at different layers (Study IST LIONs documents) including IP, Ethernet, ...
- Interoperation and interactions between layers
- Traffic Grooming for more efficient resilience
- End-to-end (path), link, span, segment, p-cycle, RPR
- within and between domains (Overview of PNNI, BGP-4, etc.)
- protection, restoration, MPLS Fast Rerouting
NOBEL WP2 May 18 Berlin 5cinkler@BUTE
1. “Resilience Strategies in 3M Networks”: Activities and work-plan of WP2 A21
M11:
Overview of Resilience Mechanisms in Multi-LAYER Multi-DOMAIN
Networks
M11:
Overview and Evaluation of Routing Mechanisms in Multi-LAYER
Multi-DOMAIN Networks static or dynamic (on-line, real-time)
D17
NOBEL WP2 May 18 Berlin 6cinkler@BUTE
1. “Resilience Strategies in 3M Networks”: Activities and work-plan of WP2 A21
M18: Evaluation of Various Resilience Strategies in Multi-LAYER Networks
Evaluation Criteria:– How complex the calculation is? (OPEX)– Amount of resources (capacity) required (CAPEX)– Speed of reaction (<50ms?)– Availability improvement (Protects Against Single or Multiple Simultaneous
Failures)
Availability Studies
M20: Evaluation of Various Resilience Strategies in Multi-DOMAIN Networks
Same Evaluation Criteria
M22: Finalising the Deliverable D27 on Resilience (and TE) in MMM networks.
NOBEL WP2 May 18 Berlin 7cinkler@BUTE
Contribution to Deliverables
• D12, D15, D17, D27, D31
• D17: Preliminary report on new methods for route management (intra- and inter-domain), and accurate statistical models for evaluating the impact on QoS (March 2005) [led by P15: T-Systems]
– D17 will describe new methods for route management (intra- and inter-domain), so that the QoS performance figures are taken into account in the routing decisions. On the other hand, accurate statistical models based on user’s traffic characterization and modelling will be defined in order to be used in traffic engineering and resilience studies
• D27: Final report on traffic engineering & resilience strategies for NOBEL solutions (October 2005) [led by P22: IMEC]
– D27 will describe efficient QoS assurance and resilience solutions to optimise network resources based on the statistical models previously described in D17. Survivability studies will investigate resilience strategies in multi-layer/domain/service networks (such as optical restoration/protection, MPLS Fast Reroute, etc.) and their interworking. On the other hand traffic/network engineering studies will be focused on solutions to optimise utilisation of network resources, QoS assurance and congestions avoidance.
NOBEL WP2 May 18 Berlin 8cinkler@BUTE
Reference Network1. With Graph Maker
• Freely available with source
NOBEL WP2 May 18 Berlin 9cinkler@BUTE
NOBEL WP2 May 18 Berlin 10cinkler@BUTE
2. yEd: more features, but no sourceextended GraphML
NOBEL WP2 May 18 Berlin 11cinkler@BUTE
E-Tools needed: 1. repository & VC
• Repository instead of attachments v/vo Version control– BSCW http://bscw.gmd.de/
– http://ausweb.scu.edu.au/aw03/papers/cassidy/paper.html
– Microsoft Exchange, Windows 2003
– WIKI, TWIKI http://twiki.org/cgi-bin/view/TWiki/WebHome
– WinCVS www.wincvs.org, cvs www.cvshome.org
– Code Versioning System web repository http://cvs.dyne.org/viewcvs.cgi/
– IBM Informics
– Savannah: http://bebas.vlsm.org/v01/software/SourceForge/savannah.html
– Total Commander with an scp plug-in
NOBEL WP2 May 18 Berlin 12cinkler@BUTE
E-Tools needed 2.VoIP
Windows Messanger (Built in into Windows XP)• Net Meeting -> Office Live Meeting www.placeware.com penzert
Yahoo Messanger 5.6 http://messenger.yahoo.com/ conference Call with WebCam (for: Windows Mac Linux)
• Private Chat Room can be easily created! A lot of advertyisment...• Yahoo! Business Messenger 2.0 (with WEB conferencing) for money
PicoPhone 1.63 http://www.vitez.it/picophone/index.html
Speak Freely 7.6a http://speak-freely.sourceforge.net/ (for: Windows Mac Linux)
Skype 0.97.0.6 http://www.skype.com/ • For conference Call!!! Up to 5 parties only :( • P2P, Windows only (XP or 2000), Typically goes trough Firewalls, No video available!
ICQ 2003b http://web.icq.com/ (http://www.icq.com/icqtour/)• PC to PC (ICQ Phone), Video Chat, SMS kuldesre is van lehetoseg, Phone to PC call (this
is a novelty!)
NOBEL WP2 May 18 Berlin 13cinkler@BUTE
NOBEL WP2 May 18 Berlin 14cinkler@BUTE
Second Topic:
• Activities and workplane WP2 A21: 15 min, May 18 14:00
“Resilience Strategies in 3M Networks”
• Technical presentations May 18 16:00
“On Quality of Resilience (QoR)”
• Technical presentations May 18 16:00
“Brief explanation of BUTE SW tool for inter-domain and intra-domain routing”
NOBEL WP2 May 18 Berlin 15cinkler@BUTE
2. Partners Interested in QoR
1. TIlab, It, [email protected],
2. Marconi, De, [email protected]
3. AGH, Pl: Krzysztof [email protected]
4. BUTE, Hu: Tibor [email protected], Janos [email protected]
5. Siemens, De: [email protected]
6. FT, Fr: [email protected]
7. Alcatel, Fr: [email protected]
8. T-Systems, De: [email protected]
9. UPC, Es: Salvatore [email protected]
10. Telenor, No: [email protected]
11. IMEC, Be: [email protected]
(All A21 partners except Ericsson and Lucent)
NOBEL WP2 May 18 Berlin 16cinkler@BUTE
2. QoR: Quality of Resilience
Based on:
• R. Clemente, L. Serra, G.D’Orazio G. Cosmo: “A Framework for Class of Service Definition in GMPLS-based Meshed ASTN”, DRCN 2003
• M. Barry, S. Bodamer, J. Späth, M. Jäger, R. Hülsermann: “A Classification Model for Network Survivability Mechanisms”, ITG 2004
• J.F. Lobo, M.L.G. Osma, Eds.: Internal Report Work Package 2: “Common understanding of key aspects inside WP2” (Glossary)
• D. Colle, Ed.: NOBEL Dictionary: Resilience related terminology
• D. Colle, I. Lievens, M. Pickavet: IMEC Contribution to A2.1 – Overview on Resilience Mechanisms
NOBEL WP2 May 18 Berlin 17cinkler@BUTE
CoS and QoR
• QoS: Class of Service• QoR is part of QoS• Tradeoff between availability and amount of required resources
(OPEX&CAPEX)– For a new connection:
• No resilience at all• Protection against a single failure• Restoration
• Multiple Layers and Multiple Domains• Availability level for a connection
– Against multiple failures: 0, 1, 2, 3
– Shorter out-of-service: < 50ms < nx100ms < nxSecond < nxHours
NOBEL WP2 May 18 Berlin 18cinkler@BUTE
Number of failures at a time
• Number of failures:– A single link fails [1L]– A single node fails [1N]– Two links (very much influenced by which two?!) [2L]
• If two links adjacent to a single node then it is covered by the upper (1N) case
– A link and a node (not adjacent!) [L+N]• If adjacent then covered by 1N
– Three links [3L]• If adjacent, then covered by either 1N or L+N
– For Multi-Domain case:• Are failures in different domains?• Are Inter-Domain Links affected?
– Multi-Layer case
NOBEL WP2 May 18 Berlin 19cinkler@BUTE
Out-of-Service
• Out-of-Service Time:– Detection
– Localisation
– Routing
– Allocation
– Assignment
– Switching
– Reverting !!!
• Faster recovery (shorter out-of-service): < 50ms (protection) [P]
< nx100ms (fast (pre-planned) restoration) [FR]
< nxSecond (restoration) [R]
< nxHours (repair)
NOBEL WP2 May 18 Berlin 20cinkler@BUTE
Trade-offs
• Trade-off: number of failures, requested resources and speed:– P+P+P or P+FR + R or P+Repair
• Protecting: Paths -> Subnetworks (domains) -> Segments –> Links-> Easier and faster to recover after multiple failures!!!
-> More resources needed
A part of working paths protected onlyRCR: Restorable Connection-Count Ratio
For aggregated (lower layer traffic streams)
RBR: Restorable Bandwidth RatioFor Best Effort elastic traffic
NOBEL WP2 May 18 Berlin 21cinkler@BUTE
Fairness?
• How can we guarantee availability if we give Resilience Priority (RP) to certain connections of an aggregated stream? What if all are “platinum”?
• Is it allowed to take the protection resources of a single-failure-protected connection if needed by a higher RP connection?
• What about the working resources of an unprotected path, that was not affected by failure?
NOBEL WP2 May 18 Berlin 22cinkler@BUTE
Other Open Questions
• What is the availability of a protection path? (OoS: Out of Service)• What is the blocking probability of a protection path?• Can a protection path be established after a certain waiting time?• Should the Availability (e.g., 99.999%) counted for one year or
some other period?• Global and local (e.g., Within a routing domain) reconfiguration
performed by the MP?
NOBEL WP2 May 18 Berlin 23cinkler@BUTE
Third Topic:
• Activities and workplane WP2 A21: 15 min, May 18 14:00
“Resilience Strategies in 3M Networks”
• Technical presentations May 18 16:00
“On Quality of Resilience (QoR)”
• Technical presentations May 18 16:00
“Brief explanation of BUTE SW tool for inter-domain and intra-domain routing”