1 / 3

Signal Degrade (SD), Survivability Framework and Recovery Mechanisms

Signal Degrade (SD), Survivability Framework and Recovery Mechanisms. Nurit Sprecher, Nokia Siemens Networks Nurit.sprecher@nsn.com. SD in context of survivability framework. A recovery action may be triggered by multiple events (“elements of control”)

junius
Download Presentation

Signal Degrade (SD), Survivability Framework and Recovery Mechanisms

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. Signal Degrade (SD), Survivability Framework and Recovery Mechanisms Nurit Sprecher, Nokia Siemens Networks Nurit.sprecher@nsn.com

  2. SD in context of survivability framework • A recovery action may be triggered by multiple events (“elements of control”) • In-band OAM indication of a failure or degradation • Operator’s commands • Network failure detection (e.g. loss of light, etc.) • Control plane error notification messages • Signal degrade (SD) can be a trigger • SD reported by lower layer or by section OAM can be useful. • But some SD is a property of traffic rather than path (e.g. congestion) and cannot be reported until LSP in use • How can we know if protection LSP is free of SD in 1:1? • Even with extra traffic the traffic pattern does not reliably match the protected traffic and SD might not be apparent • It is not the job of the Surv Fwk to define what SD is or how to measure it • It is not the job of Surv Fwk to define interactions between network conditions (that is policy)

  3. SD in context of protection mechanisms: questions • Should SD be treated as a failure (absolute indication)? • If so, when SD is declared on a working path but not on the protection path, recovery action should be taken. • Should the level of degradation be reported, to ensure that recovery happens only if the protection path performs significantly better than the working path (quantitative comparison)? In such a case the protection function should be configured with the threshold. • In m:n, when priority between the path is considered, what are the criteria for judging the priority between paths that have SD and SF conditions?

More Related