Child pages
  • TAPI Contributions and Presentations

OS SDN Logo-01.jpg  

 

 

 

 

 

 

 

 

 

 

 

 

 

 


ONF Document Type: Contribution
 

Disclaimer

CREATIVE COMMONS ATTRIUBUTION 4.0 INTERNATIONAL PUBLIC LICENSE

By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, you are granted the Licensed Rights in consideration of your acceptance of these terms and conditions, and the Licensor grants Your such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions. For full details, explanations, and examples of the use of this License, please visit:

http://creativecommons.org/licenses/by/4.0/legalcode

 

Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority.

 

Open Networking Foundation

2275 E. Bayshore Road, Suite 103, Palo Alto, CA 94303

http://www.opennetworking.org

http://opensourcesdn.org

 


1 Introduction

2 Reference

3 Notation

4 Appendix A3: Support of Resilience

4.1 Single-domain e2e protection/restoration

4.1.1 Domain Topology

4.1.2 Single-domain e2e 1+1 protection

4.1.3 Single-domain e2e dynamic restoration

4.1.4 Single-domain e2e 1+1 protection with dynamic restoration

4.1.5 Single-domain e2e permanent 1+1 protection

4.2 Multi-domain segment protection/restoration

4.2.1 Multi-domain Topology

4.2.2 Multi-domain ConnectivityService Creation with Local Resilience

4.3 Multi-domain e2e protection/restoration

4.3.1 Multi-domain Topology

4.3.2 Multi-domain e2e linear protection

4.3.3 Multi-domain e2e dynamic restoration

4.4 Retrieving Status

5 Proposal of UpdateServiceType

6 Appendix

6.1 Single-domain e2e permanent 1+1 protection

6.2 Single-domain e2e 1+1 protection with dynamic restoration

6.3 Single-domain e2e dynamic restoration

6.4 Multi-domain e2e 1+1 linear protection

6.5 Multi-domain e2e dynamic restoration

1 Introduction .................................................................................................................... 4

2 Reference ........................................................................................................................ 4

3 Notation .......................................................................................................................... 4

4 Appendix A3: Support of Resilience ........................................................................... 4

4.1 Single-domain e2e protection/restoration .................................................................. 4

4.1.1 Domain Topology .............................................................................................. 5

4.1.2 Single-domain e2e 1+1 protection ................................................................... 5

4.1.3 Single-domain e2e dynamic restoration ........................................................... 6

4.1.4 Single-domain e2e 1+1 protection with dynamic restoration ........................... 7

4.1.5 Single-domain e2e permanent 1+1 protection ................................................. 7

4.2 Multi-domain segment protection/restoration ............................................................ 8

4.2.1 Multi-domain Topology ...................................................................................... 9

4.2.2 Multi-domain ConnectivityService Creation with Local Resilience .................... 9

4.3 Multi-domain e2e protection/restoration .................................................................. 10

4.3.1 Multi-domain Topology .................................................................................... 10

4.3.2 Multi-domain e2e linear protection ................................................................. 11

4.3.3 Multi-domain e2e dynamic restoration ........................................................... 12

4.4 Retrieving Status ..................................................................................................... 14

5 Proposal of UpdateServiceType ................................................................................ 14

6 Appendix ....................................................................................................................... 15

6.1 Single-domain e2e permanent 1+1 protection ........................................................ 15

6.2 Single-domain e2e 1+1 protection with dynamic restoration .................................. 17

6.3 Single-domain e2e dynamic restoration .................................................................. 18

6.4 Multi-domain e2e 1+1 linear protection .................................................................. 20

6.5 Multi-domain e2e dynamic restoration .................................................................... 22

List of Figures

未找到图形项目表。

Document History

Version

Date

Description of Change

00

Feb . 27, 2018

Initial version.

0 2

March.27,2018

Updated as per discussion in London interim meeting

 


1        Introduction

TAPI 2.0 resilience use cases for TAPI 2.0 FRD, modification to the original draft of TAPI 2.0 FRD is marked with change marks . Test examples are listed in the Appendix.

2        Reference

TR527_TAPI_FRS

onf2016.186_Use-Cases_MultiDomain-Protection-And-Restoration.02

onf2016.394_T-API_Protection_Use_Cas.02

onf2017.039_Multi-Layer-Protection-Use-Cases.02

onf2017.045_T-API_Protection_Model_C.00

3        Notation

4        Appendix A3: Support of Resilience

The following section provides exemplary use cases for TAPI ConnectivityServices supporting resiliency .

4.1      Single-domain e2e protection /restoration

In this single-domain end-to-end linear resilience example, the following actions take place:

  • Client configures the resilience type and resilience-related parameters when creating a ConnectivityService.
  • Client specifies any route constraints for work route and protection route separately when creating a ConnectivityService.
  • In some resilience schemes, Route may need LifecycleState to expressed, due to a Route may have encapsulated protection or other complex nesting of resilience schemes.

4.1.1      Domain Topology

The domain topology supports multiple diverse paths between the two NodeEdgePoints corresponding to the target ServiceInterfacePoints.

Single -domain e2e 1+1 protection

The 1+1 protection schema refers to the Connection of ConnectivityService switch to protect Route when the work Route fails.

ConnectivityService creation

T he client of controller request the creation of ConnectivityService with 1+1 protection protectionType and NA   r estorationPolicy of resilienceType. As shown in the figure below, the SDN Controller creates a green working path from A.1 to A.2 and a red protect path from A.1 through A.3 to A.2, both supporting a connection between NEPs 01 and 05 and ConnectivityService between SIPs SIP1 and SIP2.

 

Trigger of protection /restoration

Protection switch occurs when connection failure is detected according to the APS protocol .

Protection/restoration procedure

If protection switch occurs, The Switch of this ConnectivityService unidirectional ly   switch es to the Protect Route and the corresponding ConnectionEndPoints.

Single-domain e2e dynamic restoration

The Single-domain e2e dynamic restoration schema refers to if the work Route fails, Controller will compute and configure a new Route for the ConnectivityService .

ConnectivityService creation

T he client of controller request the creation of ConnectivityService with dynamic restoration protectionType and Per-Domain   r estorationPolicy of resilienceType . As shown in the figure below, the SDN Controller creates a green working path from A.1 to A.2 supporting a connection between NEPs 01 and 05 and ConnectivityService between SIPs SIP1 and SIP2.

Trigger of protection/ restoration

If the failure of work Route is detected, Controller will start the restoration procedure of the ConnectivityService .

Protection/restoration procedure

If restoration of the ConnectivityService occurs, Controller will Controller will compute and configure a new Route for ConnectivityService .

 

Single -domain e2e 1+1 protection   with   dynamic   restoration

The 1+1 protection with dynamic restoration schema refers to if there is no available standby Route for switch, Controller will compute and configure a new Route for the ConnectivityService .

ConnectivityService creation

T he client of controller request the creation of ConnectivityService with 1+1 protection   with   dynamic   restoration protectionType and Per-Domain   r estorationPolicy of resilienceType. As shown in the figure below, the SDN Controller creates a green working path from A.1 to A.2 and a red protect path from A.1 through A.3 to A.2, both supporting a connection between NEPs 01 and 05 and ConnectivityService between SIPs SIP1 and SIP2.

 

Trigger of protection/restoration

Protection switch occurs when connection failure is detected according to the APS protocol .

If the failure of work Route is detected and there is no there is no available standby Route for switch or switch doesn’t help, Controller will start the restoration procedure of the ConnectivityService.

Protection/restoration procedure

If protection switch occurs, The Switch of this ConnectivityService switch to the Protect Route and the corresponding ConnectionEndPoints.

If restoration of the ConnectivityService occurs, Controller will Controller will compute and configure a new Route for ConnectivityService .

 

Single -domain e2e permanent 1+1 protection

The permanent 1+1 protection schema refers to the work Route will always have a protect Route standby for backup. If the protect Route fails, Controller will compute and configure a new protect Route for the working Route.

ConnectivityService creation

T he client of controller request the creation of ConnectivityService with Permanet 1+1 Protection   protectionType and Per-Domain   r estorationPolicy of resilienceType. As shown in the figure below, the SDN Controller creates a green working path from A.1 to A.2 and a red protect path from A.1 through A.3 to A.2, both supporting a connection between NEPs 01 and 05 and ConnectivityService between SIPs SIP1 and SIP2.

 

Trigger of protection/restoration

Protection switch occurs when connection failure is detected according to the APS protocol .

If the failure of protect Route is detected, Controller will start the restoration procedure of that protect Route.

Protection/restoration procedure

If protection switch occurs, The Switch of this ConnectivityService switch to the Protect Route and the corresponding ConnectionEndPoints.

If restoration of the protect Route occurs, Controller will compute and configure a new protect Route for the working Route.

 

4.2      Multi-domain segment protection/restoration

In a multi-domain ConnectivityService, resiliency can be provided using segment linear protection/restoration within individual domains.  The additional requirements to support this are as follows:

-           Need to configure the segment protection type for multi-domain controller when creating a ConnectivityService.

For resilience of inter-domain links: combination of e2e protection and segment protection, combination of e2e restoration and segment protection.

Resiliency across the inter-domain interface can be supported by using local protection capability of the inter-domain links.

4.2.1      Multi-domain Topology

In this case an example topology of three separate domains is shown, each with its own SDN Controller and with a Multi-Domain Controller coordinating across domains. 

4.2.2      Multi-domain ConnectivityService Creation with Local Resilience

In this scenario, the MD Controller computes the domain path and requests ConnectivityService across each domain, specifying an associated Protection Type and Reversion Mode.  The interdomain SIPs are chosen such that the interdomain link supports link protection.  Within each domain, the SDN Controller for the domain creates a protected connection that includes a working and protect path.  Note that in the middle domain the ingress and egress NEPs are on the same node, so multiple paths are not available.

 

 

4.3      Multi-domain e2e protection/restoration

In this multi-domain end-to-end linear resilience example these additional actions are taken:

  • Client specifies the protection role of the ConnServiceEP when creating a ConnectivityService.
  • Client indicates routes used for work or protection after creating a ConnectivityService, in another word, routes should be specified with protection role.

The ConnectivityService in the transit domains are made aware of the protection schema

4.3.1      Multi-domain Topology

The multi-domain topology is shown below, similar to the topology in the previous example.

4.3.2      Multi-domain ConnectivityService Creation with e2e linear protection

In this scenario, the MD Controller coordinates the creation of work and protect paths across multiple domains.  It selects the SIPs to be used for the inter-domain links and uses TAPI to identify the SIPs and their roles to the domain Controllers.

ConnectivityService creation

For Domain C, the client of MD controller request the creation of ConnectivityService with 1+1 Protection   protectionType and NA   r estorationPolicy of resilienceType, and specifies that ConnectivityService EndPoint corresponding to SIP1 is the Protected interface point, while the ConnectivityServiceEndPopint corresponding to SIP3 is Work type and the ConnectivityService EndPoint corresponding to SIP4 is Protect type.  Controller A then creates two routes paths , one from SIP1 to SIP3 and one from SIP1 to SIP4.

For Domain A, MD controller request the creation of ConnectivityService with 1+1 Protection   protectionType and NA   r estorationPolicy of resilienceType,   and specifies that ConnectivityService EndPoint corresponding to SIP1 is the Protected interface point, while the ConnectivityServiceEndPopint corresponding to SIP3 is Working type and the ConnectivityService EndPoint corresponding to SIP4 is Protect type.  Controller A then creates two routes paths , one from SIP1 to SIP3 and one from SIP1 to SIP4.

For Domain B, MD controller request the creation of ConnectivityService to controller B with 1+1 Protection protectionType and NA restoration restorationPolicy of resilienceType, and specifies that the ConnectivityService EndPoint corresponding to SIP11 is the Protected interface point, while the ConnectivityService EndPoint corresponding to SIP9 is Work type and the ConnectivityService EndPoint corresponding to SIP10 is Protect type.  Controller B then creates two paths, one from SIP9 to SIP11 and one from SIP10 to SIP11.

For the transit domain D, it is possible for the MD Controller to request two related   independent ConnectivityServices, one for Working and one for Protect Route.  However there may be some benefit to Controller D to know that there is a relationship between the two Routes, so the MD Controller makes a single request to Controller D that identifies the ConnectivityService EndPoints corresponding to SIP5 and SIP7 as the Work interface points and the ConnectivityService EndPoints corresponding to SIP6 and SIP8 as the Protect interface points and Controller D creates two diverse routes paths for Working and Protect.

Once the ConnectivityServices across each domain are completed, there are two diverse end-to-end routes paths that provide Work and Protect paths for the end-to-end ConnectivityService.

Trigger of protection /restoration

Protection switch occurs when connection failure is detected   . according to the APS protocol.

P rotection/ restoration procedure

The Switch of this ConnectivityService switch to the Protect Route and the corresponding ConnectionEndPoints. Server controllers report the switch status to MD controller.

 

Multi-domain e2e dynamic restoration

In this scenario, the MD Controller coordinates the creation of one work Route across multiple domains. It selects the SIPs to be used for the inter-domain links and uses TAPI to identify the SIPs and their roles to the domain Controllers.

ConnectivityService creation

For Domain C, the client of MD controller request the creation of ConnectivityService with dynamic restoration protectionType and e2e restoration r estorationPolicy of resilienceType, and specifies that ConnectivityService EndPoint corresponding to SIP1 is the NA interface point, while the ConnectivityServic eEndPopint corresponding to SIP11 is NA type .   MD controller then selects the inter - domain SIPs for domain controllers to create the single-domain   ConnectivityService .

For Domain A, MD controller request the creation of ConnectivityService to controller A with dynamic restoration protectionType and e2e restoration restorationPolicy of resilienceType, and specifies that ConnectivityService EndPoint corresponding to SIP1 is the NA   interface point, while the ConnectivityServic eEndPopint corresponding to SIP3 is NA   type.

For Domain B, MD controller request the creation of ConnectivityService to controller B with dynamic restoration protectionType and e2e restoration restorationPolicy of resilienceType, and specifies that ConnectivityService EndPoint corresponding to SIP 9 is the NA   interface point, while the ConnectivityServic eEndPopint corresponding to SIP11 is NA   type.

For Domain D, MD controller request the creation of ConnectivityService to controller D with dynamic restoration protectionType and e2e restoration restorationPolicy of resilienceType, and specifies that ConnectivityService EndPoint corresponding to SIP 5 is the NA   interface point, while the ConnectivityServic eEndPopint corresponding to SIP7 is NA   type.

Trigger of protection/ restoration

MD controller r eceive s   the fault alarm notification   reported by domain controller, then find out the corresponding end-to-end multi-domain connectivity-service according to the fault alarm notification, and start the restoration procedure.

P rotection/ restoration procedure

MD controller send ConnectivityService update   requests   with Multi-Domain-Restore UpdateServiceType   and ConnectivityService creation requests to the server controller s according to the end-to-end multi-domain connectivity-service.  

In this case, for Domain A, MD controller request the update of ConnectivityService to controller A with Multi-Domain-Restore UpdateServiceType and specifies that ConnectivityService EndPoint corresponding to SIP1 is the Protected interface point, while the ConnectivityServiceEndPopint corresponding to SIP3 is Work type and the ConnectivityService EndPoint corresponding to SIP4 is Work-Restore type, if the Resilience Mode of the ConnectivityService is Revert. MD controller then selects the inter-domain SIPs for domain controllers to create the single-domain ConnectivityService.  

For Domain B, MD controller request the update of ConnectivityService to controller B with Multi-Domain-Restore UpdateServiceType and specifies that ConnectivityService EndPoint corresponding to SIP11 is the Protected interface point, while the ConnectivityServiceEndPopint corresponding to SIP9 is Work type and the ConnectivityService EndPoint corresponding to SIP10 is Work-Restore type, if the Resilience Mode of the ConnectivityService is Revert.

For Domain D, MD controller request the update of ConnectivityService to controller D with Multi-Domain-Restore UpdateServiceType and specifies that ConnectivityService EndPoint corresponding to SIP5 is the Work interface point   and ConnectivityService EndPoint corresponding to SIP7 is the Work interface point, while the ConnectivityServiceEndPopint corresponding to SIP6 is Work -Restore type and the ConnectivityService EndPoint corresponding to SIP8 is Work-Restore type, if the Resilience Mode of the ConnectivityService is Revert.

If the new route of the ConnectivityService pass a new domain which was not related to this ConnectivityService , MD controller should send ConnectivityService creation request to that domain controller instead of ConnectivityService update request. Like the case in the following figure , For Domain D, MD controller request the creation of ConnectivityService to controller D and specifies that ConnectivityService EndPoint corresponding to SIP6 is the Work-Restore interface point   and ConnectivityService EndPoint corresponding to SIP8 is the Work-Restore interface point.

4.4      Retrieving Status

Resilient connections are modeled as having multiple sub-connections where SwitchControl (SC) at the ConnectionEndPoint of the connection coordinates the handling of data across the sub-connections.  SC functionality is determined inherently in the type of resiliency that is requested for the connection, however SC can be queried to retrieve the current state of the connection.

5        Proposal of UpdateServiceType

NOTE: It ’s suggested to use Template approach instead of Operation according to the discussion in March London meeting.

Instead of controller judging the update type as per complex input information, Adding updateType as input will do help to the efficiency of interaction.

6        Appendix

This Appendix show the test interface examples corresponding to the use cases above.

6.1      Single -domain e2e permanent 1+1 protection

Attribute Name

Value

_endPoint 1

_serviceInterfacePoint

SIP1

R ole

SYMMETRIC

protectionRole

PROTECTED

layerProtocol

layerProtocolName =ETH

terminationDirection= BIRD IRECTIONAL

_endPoint 2

_serviceInterfacePoint

SIP2

R ole

SYMMETRIC

protectionRole

PROTECTED

layerProtocol

layerProtocolName =ETH

terminationDirection= BIRD IRECTIONAL

_schedule

N ull

_state

administrativeState=UNLOCKED

OperationalState=enabled

LifecycleState=INSTALLED

layerProtocolName

 

ETH

_connConstraint

serviceType

POINT_TO_POINT_CONNECTIVITY

requestedCapacity

c ommitted InformationRate=1000

_routeComputePolicy

-             routeObjectiveFunction= null

-             diversityPolicy=SRLG

-             opticalRoutingStrategy=null

latencyCharacteristic

N ull

_diversityExclusion

N ull

costCharacteristic

N ull

_corouteInclusion

N ull

isExclusiveService

True

_topoConstranint

_strictIncludeLink

N ull

_excludeLink

N ull

_strictIncludeNode

N ull

_avoideNode

N ull

routeConstraintType

N ull

resilience Constraint

layerProtocol

ODU

resilienceType

-             restorationPolicy= PER_DOMAIN_RESTORATION

-             protectionType=PERMANENT_

protectionSwitchDirection

BI_DIRECTIONAL

reversionMode

REVERTIVE

waitToRestoreTime

300

 

6.2      Single -domain e2e 1+1 protection with dynamic restoration

Attribute Name

 

Value

_endPoint 1

_serviceInterfacePoint

SIP1

R ole

SYMMETRIC

protectionRole

PROTECTED

layerProtocol

layerProtocolName =ETH

terminationDirection= BIRD IRECTIONAL

_endPoint 2

_serviceInterfacePoint

SIP2

R ole

SYMMETRIC

protectionRole

PROTECTED

layerProtocol

layerProtocolName =ETH

terminationDirection= BIRD IRECTIONAL

_schedule

 

N ull

_state

 

administrativeState=UNLOCKED

OperationalState=enabled

LifecycleState=INSTALLED

layerProtocolName

 

ETH

_connConstraint

serviceType

POINT_TO_POINT_CONNECTIVITY

requestedCapacity

c ommitted InformationRate=1000

_routeComputePolicy

-             routeObjectiveFunction= null

-             diversityPolicy=SRLG

-             opticalRoutingStrategy=null

latencyCharacteristic

N ull

_diversityExclusion

N ull

costCharacteristic

N ull

_corouteInclusion

N ull

isExclusiveService

True

_topoConstranint

_strictIncludeLink

N ull

_excludeLink

N ull

_strictIncludeNode

N ull

_avoideNode

N ull

routeConstraintType

N ull

resilience Constraint

layerProtocol

ODU

resilienceType

-             restorationPolicy= Per-Domain

-             protectionType= ONE_PLUS_ONE_WITH_DYNAMIC_RESTORATION

protectionSwitchDirection

BI_DIRECTIONAL

reversionMode

REVERTIVE

waitToRestoreTime

300

6.3      Single-domain e2e dynamic restoration

Attribute Name

 

Value

_endPoint 1

_serviceInterfacePoint

SIP1

R ole

SYMMETRIC

protectionRole

NA

layerProtocol

layerProtocolName =ETH

terminationDirection= BIRD IRECTIONAL

_endPoint 2

_serviceInterfacePoint

SIP2

R ole

SYMMETRIC

protectionRole

NA

layerProtocol

layerProtocolName =ETH

terminationDirection= BIRD IRECTIONAL

_schedule

 

N ull

_state

 

administrativeState=UNLOCKED

OperationalState=enabled

LifecycleState=INSTALLED

layerProtocolName

 

ETH

_connConstraint

serviceType

POINT_TO_POINT_CONNECTIVITY

requestedCapacity

c ommitted InformationRate=1000

_routeComputePolicy

-             routeObjectiveFunction= null

-             diversityPolicy=null

-             opticalRoutingStrategy=null

latencyCharacteristic

N ull

_diversityExclusion

N ull

costCharacteristic

N ull

_corouteInclusion

N ull

isExclusiveService

True

_topoConstranint

_strictIncludeLink

N ull

_excludeLink

N ull

_strictIncludeNode

N ull

_avoideNode

N ull

routeConstraintType

N ull

resilience Constraint

layerProtocol

ODU

resilienceType

-             restorationPolicy= Per-domain

-             protectionType= DYNAMIC_RESTORATION

protectionSwitchDirection

BI_DIRECTIONAL

reversionMode

REVERTIVE

waitToRestoreTime

300

6.4      Multi-domain e2e 1+1 linear protection

MD Controller->Controller A

Attribute Name

Value

_endPoint 1

_serviceInterfacePoint

SIP1

R ole

SYMMETRIC

protectionRole

PROTECTED

layerProtocol

layerProtocolName =ETH

terminationDirection= BIRD IRECTIONAL

_terminationSpec={etherType=C_TAG, accessAction=KEEP, portVid=100}

_endPoint 2

_serviceInterfacePoint

SIP3

R ole

SYMMETRIC

protectionRole

WORK

layerProtocol

layerProtocolName =ODU

terminationDirection= BIRD IRECTIONAL

connectivity SepLpSpec.

_adapterSpec={ acceptedPayloadType =OTU4, K=1.25_G, tributarySlotList=80_8000000000000000 , adaptationType=ODU_J_21 }

_endPoint 3

_serviceInterfacePoint

SIP4

R ole

SYMMETRIC

protectionRole

PROTECT

layerProtocol

layerProtocolName =ODU

terminationDirection= BIRD IRECTIONAL

connectivity SepLpSpec.

_adapterSpec={ acceptedPayloadType =OTU4, K=1.25_G, tributarySlotList=80_8000000000000000 , adaptationType=ODU_J_21 }

_schedule

N ull

_state

administrativeState=UNLOCKED

OperationalState=enabled

LifecycleState=INSTALLED

layerProtocolName

 

ETH

_connConstraint

serviceType

POINT_TO_POINT_CONNECTIVITY

requestedCapacity

c ommitted InformationRate=1000

_routeComputePolicy

-             routeObjectiveFunction= null

-             diversityPolicy=SRLG

-             opticalRoutingStrategy=null

latencyCharacteristic

N ull

_diversityExclusion

N ull

costCharacteristic

N ull

_corouteInclusion

N ull

_topoConstranint

_strictIncludeLink

N ull

_excludeLink

N ull

_strictIncludeNode

N ull

_avoideNode

N ull

routeConstraintType

N ull

resilience Constraint

layerProtocol

ODU

resilienceType

-             restorationPolicy=NA

-             protectionType= 1+1

protectionSwitchDirection

BI_DIRECTIONAL

reversionMode

REVERTIVE

waitToRestoreTime

300

 

6.5      Multi-domain e2e dynamic restoration

MD Controller->Controller A

Attribute Name

Value

_endPoint

_serviceInterfacePoint

SIP1

R ole

SYMMETRIC

protectionRole

NA

layerProtocol

layerProtocolName =ETH

terminationDirection= BIRD IRECTIONAL

_terminationSpec={etherType=C_TAG, accessAction=KEEP, portVid=100}

_endPoint

_serviceInterfacePoint

SIP3

R ole

SYMMETRIC

protectionRole

NA

layerProtocol

layerProtocolName =ODU

terminationDirection= BIRD IRECTIONAL

connectivity SepLpSpec.

_adapterSpec={ acceptedPayloadType =OTU4, K=1.25_G, tributarySlotList=80_8000000000000000 , adaptationType=ODU_J_21 }

_schedule

N ull

_state

administrativeState=UNLOCKED

OperationalState=enabled

LifecycleState=INSTALLED

layerProtocolName

ETH

_connConstraint

serviceType

POINT_TO_POINT_CONNECTIVITY

requestedCapacity

c ommitted InformationRate=1000

_routeComputePolicy

-             routeObjectiveFunction= null

-             diversityPolicy=SRLG

-             opticalRoutingStrategy=null

latencyCharacteristic

N ull

_diversityExclusion

N ull

costCharacteristic

N ull

_corouteInclusion

N ull

_topoConstranint

_strictIncludeLink

N ull

_excludeLink

N ull

_strictIncludeNode

N ull

_avoideNode

N ull

routeConstraintType

N ull

resilience Constraint

layerProtocol

ODU

resilienceType

-             restorationPolicy=END_2_END

-             protectionType=DYNAMIC_RESTORATION

protectionSwitchDirection

BI_DIRECTIONAL

reversionMode

REVERTIVE

waitToRestoreTime

300

 

The following example showing that, a fter Connection failure, MD controller request updating the ConnectivityService to Controller A with updateConnectivityService interface.

Attribute Name

Value

U uid

S ervice .uuid

_endPoint A

_serviceInterfacePoint

SIP1

R ole

SYMMETRIC

protectionRole

Protected

layerProtocol

layerProtocolName =ETH

terminationDirection= BIRD IRECTIONAL

_terminationSpec={etherType=C_TAG, accessAction=KEEP, portVid=100}

_endPoint (B)

_serviceInterfacePoint

SIP3

R ole

SYMMETRIC

protectionRole

Work

layerProtocol

layerProtocolName =ODU

terminationDirection= BIRD IRECTIONAL

connectivity SepLpSpec.

_adapterSpec={ acceptedPayloadType =OTU4, K=1.25_G, tributarySlotList=80_8000000000000000 , adaptationType=ODU_J_21 }

_ endPoint C

_serviceInterfacePoint

SIP4

R ole

SYMMETRIC

protectionRole

Restore

layerProtocol

layerProtocolName =ODU

terminationDirection= BIRD IRECTIONAL

connectivity SepLpSpec.

_adapterSpec={ acceptedPayloadType =OTU4, K=1.25_G, tributarySlotList=80_8000000000000000 , adaptationType=ODU_J_21 }

_schedule

N ull

_state

administrativeState=UNLOCKED

OperationalState=enabled

LifecycleState=INSTALLED

layerProtocolName

ETH

_connConstraint

serviceType

POINT_TO_POINT_CONNECTIVITY

requestedCapacity

c ommitted InformationRate=1000

_routeComputePolicy

-             routeObjectiveFunction= null

-             diversityPolicy=SRLG

-             opticalRoutingStrategy=null

latencyCharacteristic

N ull

_diversityExclusion

N ull

costCharacteristic

N ull

_corouteInclusion

N ull

_topoConstranint

_strictIncludeLink

N ull

_excludeLink

N ull

_strictIncludeNode

N ull

_avoideNode

N ull

routeConstraintType

N ull

resilience Constraint

layerProtocol

ODU

resilienceType

-             restorationPolicy=END_2_END

-             protectionType=DYNAMIC_RESTORATION

protectionSwitchDirection

BI_DIRECTIONAL

reversionMode

REVERTIVE

waitToRestoreTime

300