Active Stateful PCE¶
The PCEP extension for Stateful PCE brings a visibility of active LSPs to PCE, in order to optimize path computation, while considering individual LSPs and their interactions. This requires state synchronization mechanism between PCE and PCC. Moreover, Active Stateful PCE is capable to address LSP parameter changes to the PCC.
Configuration¶
This capability is enabled by default. No additional configuration is required.
Speaker Entity identifier¶
The Speaker Entity Identifier is an optional TLV that may be included in the OPEN Object when a PCEP speaker wishes to determine if state synchronization can be skipped when a PCEP session is restarted.
URL: /rests/data/network-topology:network-topology/topology=pcep-topology/node=43.43.43.43
Method: PUT
Content-Type: application/xml
Request Body:
1<node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
2 <node-id>43.43.43.43</node-id>
3 <session-config xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep">
4 <speaker-entity-id-value xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep:sync:optimizations:config">AQIDBA==</speaker-entity-id-value>
5 </session-config>
6</node>
@line 2: address - A PCC IP address.
@line 4: Speaker Entity Identifier - The Speaker Entity identifier assigned to PCEP Node.
Content-Type: application/json
Request Body:
1{
2 "node": {
3 "node-id": "43.43.43.43",
4 "topology-topology-pcep:session-config": {
5 "topology:pcep:sync:optimizations:config:speaker-entity-id-value": "AQIDBA=="
6 }
7 }
8}
@line 3: address - A PCC IP address.
@line 5: Speaker Entity Identifier - The Speaker Entity identifier assigned to PCEP Node.
MD5 authentication configuration¶
The OpenDaylight PCEP implementation supports TCP MD5 for authentication. The sample configuration below shows how to set authentication password for a particular PCC.
URL: /rests/data/network-topology:network-topology/topology=pcep-topology/node=43.43.43.43
Method: PUT
Content-Type: application/xml
Request Body:
1<node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
2 <node-id>43.43.43.43</node-id>
3 <session-config xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep">
4 <password>topsecret</password>
5 </session-config>
6</node>
@line 2: address - A PCC IP address.
@line 4: password - MD5 authentication phrase.
Content-Type: application/json
Request Body:
1{
2 "node": {
3 "node-id": "43.43.43.43",
4 "network-topology-pcep:session-config": {
5 "password": "topsecret"
6 }
7 }
8}
@line 3: address - A PCC IP address.
@line 5: password - MD5 authentication phrase.
LSP State Database¶
The LSP State Database (LSP-DB) contains an information about all LSPs and their attributes. The LSP state is synchronized between the PCC and PCE. First, initial LSP state synchronization is performed once the session between PCC and PCE is established in order to learn PCC’s LPSs. This step is a prerequisite to following LSPs manipulation operations.
LSP State Synchronization.¶
LSP-DB API¶
path-computation-client
+--ro reported-lsp* [name]
+--ro name string
+--ro path* [lsp-id]
| +--ro lsp-id rsvp:lsp-id
| +--ro ero
| | +--ro processing-rule? boolean
| | +--ro ignore? boolean
| | +--ro subobject*
| | +--ro loose boolean
| | +--ro (subobject-type)?
| | +--:(as-number-case)
| | | +--ro as-number
| | | +--ro as-number inet:as-number
| | +--:(ip-prefix-case)
| | | +--ro ip-prefix
| | | +--ro ip-prefix inet:ip-prefix
| | +--:(label-case)
| | | +--ro label
| | | +--ro uni-directional boolean
| | | +--ro (label-type)?
| | | +--:(type1-label-case)
| | | | +--ro type1-label
| | | | +--ro type1-label uint32
| | | +--:(generalized-label-case)
| | | | +--ro generalized-label
| | | | +--ro generalized-label binary
| | | +--:(waveband-switching-label-case)
| | | +--ro waveband-switching-label
| | | +--ro end-label uint32
| | | +--ro start-label uint32
| | | +--ro waveband-id uint32
| | +--:(srlg-case)
| | | +--ro srlg
| | | +--ro srlg-id srlg-id
| | +--:(unnumbered-case)
| | | +--ro unnumbered
| | | +--ro router-id uint32
| | | +--ro interface-id uint32
| | +--:(exrs-case)
| | | +--ro exrs
| | | +--ro exrs*
| | | +--ro mandatory? boolean
| | | +--ro attribute enumeration
| | | +--ro (subobject-type)?
| | | +--:(as-number-case)
| | | | +--ro as-number
| | | | +--ro as-number inet:as-number
| | | +--:(ip-prefix-case)
| | | | +--ro ip-prefix
| | | | +--ro ip-prefix inet:ip-prefix
| | | +--:(label-case)
| | | | +--ro label
| | | | +--ro uni-directional boolean
| | | | +--ro (label-type)?
| | | | +--:(type1-label-case)
| | | | | +--ro type1-label
| | | | | +--ro type1-label uint32
| | | | +--:(generalized-label-case)
| | | | | +--ro generalized-label
| | | | | +--ro generalized-label binary
| | | | +--:(waveband-switching-label-case)
| | | | +--ro waveband-switching-label
| | | | +--ro end-label uint32
| | | | +--ro start-label uint32
| | | | +--ro waveband-id uint32
| | | +--:(srlg-case)
| | | | +--ro srlg
| | | | +--ro srlg-id srlg-id
| | | +--:(unnumbered-case)
| | | +--ro unnumbered
| | | +--ro router-id uint32
| | | +--ro interface-id uint32
| | +--:(path-key-case)
| | +--ro path-key
| | +--ro pce-id pce-id
| | +--ro path-key path-key
| +--ro lspa
| | +--ro processing-rule? boolean
| | +--ro ignore? boolean
| | +--ro hold-priority? uint8
| | +--ro setup-priority? uint8
| | +--ro local-protection-desired? boolean
| | +--ro label-recording-desired? boolean
| | +--ro se-style-desired? boolean
| | +--ro session-name? string
| | +--ro include-any? attribute-filter
| | +--ro exclude-any? attribute-filter
| | +--ro include-all? attribute-filter
| | +--ro tlvs
| | +--ro vendor-information-tlv*
| | +--ro enterprise-number? iana:enterprise-number
| | +--ro (enterprise-specific-information)?
| +--ro bandwidth
| | +--ro processing-rule? boolean
| | +--ro ignore? boolean
| | +--ro bandwidth? netc:bandwidth
| +--ro reoptimization-bandwidth
| | +--ro processing-rule? boolean
| | +--ro ignore? boolean
| | +--ro bandwidth? netc:bandwidth
| +--ro metrics*
| | +--ro metric
| | +--ro processing-rule? boolean
| | +--ro ignore? boolean
| | +--ro metric-type uint8
| | +--ro bound? boolean
| | +--ro computed? boolean
| | +--ro value? ieee754:float32
| +--ro iro
| | +--ro processing-rule? boolean
| | +--ro ignore? boolean
| | +--ro subobject*
| | +--ro loose boolean
| | +--ro (subobject-type)?
| | +--:(as-number-case)
| | | +--ro as-number
| | | +--ro as-number inet:as-number
| | +--:(ip-prefix-case)
| | | +--ro ip-prefix
| | | +--ro ip-prefix inet:ip-prefix
| | +--:(label-case)
| | | +--ro label
| | | +--ro uni-directional boolean
| | | +--ro (label-type)?
| | | +--:(type1-label-case)
| | | | +--ro type1-label
| | | | +--ro type1-label uint32
| | | +--:(generalized-label-case)
| | | | +--ro generalized-label
| | | | +--ro generalized-label binary
| | | +--:(waveband-switching-label-case)
| | | +--ro waveband-switching-label
| | | +--ro end-label uint32
| | | +--ro start-label uint32
| | | +--ro waveband-id uint32
| | +--:(srlg-case)
| | | +--ro srlg
| | | +--ro srlg-id srlg-id
| | +--:(unnumbered-case)
| | | +--ro unnumbered
| | | +--ro router-id uint32
| | | +--ro interface-id uint32
| | +--:(exrs-case)
| | | +--ro exrs
| | | +--ro exrs*
| | | +--ro mandatory? boolean
| | | +--ro attribute enumeration
| | | +--ro (subobject-type)?
| | | +--:(as-number-case)
| | | | +--ro as-number
| | | | +--ro as-number inet:as-number
| | | +--:(ip-prefix-case)
| | | | +--ro ip-prefix
| | | | +--ro ip-prefix inet:ip-prefix
| | | +--:(label-case)
| | | | +--ro label
| | | | +--ro uni-directional boolean
| | | | +--ro (label-type)?
| | | | +--:(type1-label-case)
| | | | | +--ro type1-label
| | | | | +--ro type1-label uint32
| | | | +--:(generalized-label-case)
| | | | | +--ro generalized-label
| | | | | +--ro generalized-label binary
| | | | +--:(waveband-switching-label-case)
| | | | +--ro waveband-switching-label
| | | | +--ro end-label uint32
| | | | +--ro start-label uint32
| | | | +--ro waveband-id uint32
| | | +--:(srlg-case)
| | | | +--ro srlg
| | | | +--ro srlg-id srlg-id
| | | +--:(unnumbered-case)
| | | +--ro unnumbered
| | | +--ro router-id uint32
| | | +--ro interface-id uint32
| | +--:(path-key-case)
| | +--ro path-key
| | +--ro pce-id pce-id
| | +--ro path-key path-key
| +--ro rro
| | +--ro processing-rule? boolean
| | +--ro ignore? boolean
| | +--ro subobject*
| | +--ro protection-available? boolean
| | +--ro protection-in-use? boolean
| | +--ro (subobject-type)?
| | +--:(ip-prefix-case)
| | | +--ro ip-prefix
| | | +--ro ip-prefix inet:ip-prefix
| | +--:(label-case)
| | | +--ro label
| | | +--ro uni-directional boolean
| | | +--ro (label-type)?
| | | | +--:(type1-label-case)
| | | | | +--ro type1-label
| | | | | +--ro type1-label uint32
| | | | +--:(generalized-label-case)
| | | | | +--ro generalized-label
| | | | | +--ro generalized-label binary
| | | | +--:(waveband-switching-label-case)
| | | | +--ro waveband-switching-label
| | | | +--ro end-label uint32
| | | | +--ro start-label uint32
| | | | +--ro waveband-id uint32
| | | +--ro global? boolean
| | +--:(unnumbered-case)
| | | +--ro unnumbered
| | | +--ro router-id uint32
| | | +--ro interface-id uint32
| | +--:(path-key-case)
| | +--ro path-key
| | +--ro pce-id pce-id
| | +--ro path-key path-key
| +--ro xro
| | +--ro processing-rule? boolean
| | +--ro ignore? boolean
| | +--ro flags bits
| | +--ro subobject*
| | +--ro mandatory? boolean
| | +--ro attribute enumeration
| | +--ro (subobject-type)?
| | +--:(as-number-case)
| | | +--ro as-number
| | | +--ro as-number inet:as-number
| | +--:(ip-prefix-case)
| | | +--ro ip-prefix
| | | +--ro ip-prefix inet:ip-prefix
| | +--:(label-case)
| | | +--ro label
| | | +--ro uni-directional boolean
| | | +--ro (label-type)?
| | | +--:(type1-label-case)
| | | | +--ro type1-label
| | | | +--ro type1-label uint32
| | | +--:(generalized-label-case)
| | | | +--ro generalized-label
| | | | +--ro generalized-label binary
| | | +--:(waveband-switching-label-case)
| | | +--ro waveband-switching-label
| | | +--ro end-label uint32
| | | +--ro start-label uint32
| | | +--ro waveband-id uint32
| | +--:(srlg-case)
| | | +--ro srlg
| | | +--ro srlg-id srlg-id
| | +--:(unnumbered-case)
| | +--ro unnumbered
| | +--ro router-id uint32
| | +--ro interface-id uint32
| +--ro of
| | +--ro processing-rule? boolean
| | +--ro ignore? boolean
| | +--ro code of-id
| | +--ro tlvs
| | +--ro vendor-information-tlv*
| | +--ro enterprise-number? iana:enterprise-number
| | +--ro (enterprise-specific-information)?
| +--ro class-type
| +--ro processing-rule? boolean
| +--ro ignore? boolean
| +--ro class-type class-type
+--ro metadata
+--ro lsp
| +--ro processing-rule? boolean
| +--ro ignore? boolean
| +--ro tlvs
| | +--ro lsp-error-code
| | | +--ro error-code? uint32
| | +--ro lsp-identifiers
| | | +--ro lsp-id? rsvp:lsp-id
| | | +--ro tunnel-id? rsvp:tunnel-id
| | | +--ro (address-family)?
| | | +--:(ipv4-case)
| | | | +--ro ipv4
| | | | +--ro ipv4-tunnel-sender-address inet:ipv4-address
| | | | +--ro ipv4-extended-tunnel-id rsvp:ipv4-extended-tunnel-id
| | | | +--ro ipv4-tunnel-endpoint-address inet:ipv4-address
| | | +--:(ipv6-case)
| | | +--ro ipv6
| | | +--ro ipv6-tunnel-sender-address inet:ipv6-address
| | | +--ro ipv6-extended-tunnel-id rsvp:ipv6-extended-tunnel-id
| | | +--ro ipv6-tunnel-endpoint-address inet:ipv6-address
| | +--ro rsvp-error-spec
| | | +--ro (error-type)?
| | | +--:(rsvp-case)
| | | | +--ro rsvp-error
| | | +--:(user-case)
| | | +--ro user-error
| | +--ro symbolic-path-name
| | | +--ro path-name? symbolic-path-name
| | o--ro vs-tlv
| | | +--ro enterprise-number? iana:enterprise-number
| | | +--ro (vendor-payload)?
| | +--ro vendor-information-tlv*
| | | +--ro enterprise-number? iana:enterprise-number
| | | +--ro (enterprise-specific-information)?
| | +--ro path-binding
| | x--ro binding-type? uint8
| | x--ro binding-value? binary
| | +--ro (binding-type-value)?
| | +--:(mpls-label)
| | | +--ro mpls-label? netc:mpls-label
| | +--:(mpls-label-entry)
| | +--ro label? netc:mpls-label
| | +--ro traffic-class? uint8
| | +--ro bottom-of-stack? boolean
| | +--ro time-to-live? uint8
| +--ro plsp-id? plsp-id
| +--ro delegate? boolean
| +--ro sync? boolean
| +--ro remove? boolean
| +--ro administrative? boolean
| +--ro operational? operational-status
+--ro path-setup-type
+--ro pst? uint8
The LSP-DB is accessible via RESTCONF.
The PCC’s LSPs are stored in the pcep-topology while the session is active.
In a next example, there is one PCEP session with PCC identified by its IP address (43.43.43.43) and one reported LSP (foo).
URL: /rests/data/network-topology:network-topology/topology=pcep-topology/node=pcc%3A%2F%2F43.43.43.43
Method: GET
Response Body:
1<node>
2 <node-id>pcc://43.43.43.43</node-id>
3 <path-computation-client>
4 <ip-address>43.43.43.43</ip-address>
5 <state-sync>synchronized</state-sync>
6 <stateful-tlv>
7 <stateful>
8 <lsp-update-capability>true</lsp-update-capability>
9 </stateful>
10 </stateful-tlv>
11 <reported-lsp>
12 <name>foo</name>
13 <lsp>
14 <operational>up</operational>
15 <sync>true</sync>
16 <plsp-id>1</plsp-id>
17 <create>false</create>
18 <administrative>true</administrative>
19 <remove>false</remove>
20 <delegate>true</delegate>
21 <tlvs>
22 <lsp-identifiers>
23 <ipv4>
24 <ipv4-tunnel-sender-address>43.43.43.43</ipv4-tunnel-sender-address>
25 <ipv4-tunnel-endpoint-address>39.39.39.39</ipv4-tunnel-endpoint-address>
26 <ipv4-extended-tunnel-id>39.39.39.39</ipv4-extended-tunnel-id>
27 </ipv4>
28 <tunnel-id>1</tunnel-id>
29 <lsp-id>1</lsp-id>
30 </lsp-identifiers>
31 <symbolic-path-name>
32 <path-name>Zm9v</path-name>
33 </symbolic-path-name>
34 </tlvs>
35 </lsp>
36 <ero>
37 <subobject>
38 <loose>false</loose>
39 <ip-prefix>
40 <ip-prefix>201.20.160.40/32</ip-prefix>
41 </ip-prefix>
42 </subobject>
43 <subobject>
44 <loose>false</loose>
45 <ip-prefix>
46 <ip-prefix>195.20.160.39/32</ip-prefix>
47 </ip-prefix>
48 </subobject>
49 <subobject>
50 <loose>false</loose>
51 <ip-prefix>
52 <ip-prefix>39.39.39.39/32</ip-prefix>
53 </ip-prefix>
54 </subobject>
55 </ero>
56 </reported-lsp>
57 </path-computation-client>
58</node>
@line 2: node-id The PCC identifier.
@line 4: ip-address IP address of the PCC.
@line 5: state-sync Synchronization status of the PCC’s LSPs. The synchronized indicates the State Synchronization is done.
@line 8: lsp-update-capability - Indicates that PCC allows LSP modifications.
@line 12: name - Textual representation of LPS’s name.
@line 14: operational - Represent operational status of the LSP:
down - not active.
up - signaled.
active - up and carrying traffic.
going-down - LSP is being torn down, resources are being released.
going-up - LSP is being signaled.
@line 15: sync - The flag set by PCC during LSPs State Synchronization.
@line 16: plsp-id - A PCEP-specific identifier for the LSP. It is assigned by PCC and it is constant for a lifetime of a PCEP session.
@line 17: create - The false indicates that LSP is PCC-initiated.
@line 18: administrative - The flag indicates target operational status of the LSP.
@line 20: delegate - The delegate flag indicates that the PCC is delegating the LSP to the PCE.
@line 24: ipv4-tunnel-sender-address - Contains the sender node’s IP address.
@line 25: ipv4-tunnel-endpoint-address - Contains the egress node’s IP address.
@line 26: ipv4-extended-tunnel-id - The Extended Tunnel ID identifier.
@line 28: tunnel-id - The Tunnel ID identifier.
@line 29: lsp-id - The LSP ID identifier.
@line 32: path-name - The symbolic name for the LSP.
@line 36: ero - The Explicit Route Object is encoding the path of the TE LSP through the network.
Response Body:
1{
2 "node": {
3 "node-id": "pcc://43.43.43.43",
4 "path-computation-client": {
5 "ip-address": "43.43.43.43",
6 "state-sync": "synchronized",
7 "stateful-tlv": {
8 "stateful": {
9 "lsp-update-capability": true
10 }
11 },
12 "reported-lsp": {
13 "name": "foo",
14 "lsp": {
15 "operational": "up",
16 "sync": true,
17 "plsp-id": 1,
18 "create": false,
19 "administrative": true,
20 "remove": false,
21 "delegate": true,
22 "tlvs": {
23 "lsp-identifiers": {
24 "ipv4": {
25 "ipv4-tunnel-sender-address": "43.43.43.43",
26 "ipv4-tunnel-endpoint-address": "39.39.39.39",
27 "ipv4-extended-tunnel-id": "39.39.39.39"
28 },
29 "tunnel-id": 1,
30 "lsp-id": 1
31 },
32 "symbolic-path-name": {
33 "path-name": "Zm9v"
34 }
35 }
36 },
37 "ero": [
38 {
39 "loose": false,
40 "ip-prefix": {
41 "ip-prefix": "201.20.160.40/32"
42 }
43 },
44 {
45 "loose": false,
46 "ip-prefix": {
47 "ip-prefix": "195.20.160.39/32"
48 }
49 },
50 {
51 "loose": false,
52 "ip-prefix": {
53 "ip-prefix": "39.39.39.39/32"
54 }
55 }
56 ]
57 }
58 }
59 }
60}
@line 3: node-id The PCC identifier.
@line 5: ip-address IP address of the PCC.
@line 6: state-sync Synchronization status of the PCC’s LSPs. The synchronized indicates the State Synchronization is done.
@line 9: lsp-update-capability - Indicates that PCC allows LSP modifications.
@line 13: name - Textual representation of LPS’s name.
@line 15: operational - Represent operational status of the LSP:
down - not active.
up - signaled.
active - up and carrying traffic.
going-down - LSP is being torn down, resources are being released.
going-up - LSP is being signaled.
@line 16: sync - The flag set by PCC during LSPs State Synchronization.
@line 17: plsp-id - A PCEP-specific identifier for the LSP. It is assigned by PCC and it is constant for a lifetime of a PCEP session.
@line 18: create - The false indicates that LSP is PCC-initiated.
@line 19: administrative - The flag indicates target operational status of the LSP.
@line 21: delegate - The delegate flag indicates that the PCC is delegating the LSP to the PCE.
@line 25: ipv4-tunnel-sender-address - Contains the sender node’s IP address.
@line 26: ipv4-tunnel-endpoint-address - Contains the egress node’s IP address.
@line 27: ipv4-extended-tunnel-id - The Extended Tunnel ID identifier.
@line 29: tunnel-id - The Tunnel ID identifier.
@line 30: lsp-id - The LSP ID identifier.
@line 33: path-name - The symbolic name for the LSP.
@line 37: ero - The Explicit Route Object is encoding the path of the TE LSP through the network.
LSP Delegation¶
The LSP control delegations is an mechanism, where PCC grants to a PCE the temporary right in order to modify LSP attributes. The PCC can revoke the delegation or the PCE may waive the delegation at any time. The LSP control is delegated to at most one PCE at the same time.
Returning a Delegation.¶
Following RPC example illustrates a request for the LSP delegation give up:
URL: /rests/operations/network-topology-pcep:update-lsp
Method: POST
Content-Type: application/xml
Request Body:
1<input>
2 <node>pcc://43.43.43.43</node>
3 <name>foo</name>
4 <arguments>
5 <lsp xmlns:stateful="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful">
6 <delegate>false</delegate>
7 <administrative>true</administrative>
8 <tlvs>
9 <symbolic-path-name>
10 <path-name>Zm9v</path-name>
11 </symbolic-path-name>
12 </tlvs>
13 </lsp>
14 </arguments>
15 <network-topology-ref xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology">/topo:network-topology/topo:topology[topo:topology-id="pcep-topology"]</network-topology-ref>
16</input>
@line 2: node The PCC identifier.
@line 3: name The name of the LSP.
@line 6: delegate - Delegation flag set false in order to return the LSP delegation.
@line 10: path-name - The Symbolic Path Name TLV must be present when sending a request to give up the delegation.
Content-Type: application/json
Request Body:
1{
2 "input": {
3 "node": "pcc://43.43.43.43",
4 "name": "foo",
5 "arguments": {
6 "lsp": {
7 "delegate": false,
8 "administrative": true,
9 "tlvs": {
10 "symbolic-path-name": {
11 "path-name": "Zm9v"
12 }
13 }
14 }
15 },
16 "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]"
17 }
18}
@line 3: node The PCC identifier.
@line 4: name The name of the LSP.
@line 7: delegate - Delegation flag set false in order to return the LSP delegation.
@line 11: path-name - The Symbolic Path Name TLV must be present when sending a request to give up the delegation.
LSP Update¶
The LSP Update Request is an operation where a PCE requests a PCC to update attributes of an LSP and to rebuild the LSP with updated attributes. In order to update LSP, the PCE must hold a LSP delegation. The LSP update is done in make-before-break fashion - first, new LSP is initiated and then the old LSP is torn down.
Active Stateful PCE LSP Update.¶
Following RPC example shows a request for the LSP update:
URL: /rests/operations/network-topology-pcep:update-lsp
Method: POST
Content-Type: application/xml
Request Body:
1<input xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep">
2 <node>pcc://43.43.43.43</node>
3 <name>foo</name>
4 <arguments>
5 <lsp xmlns="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful">
6 <delegate>true</delegate>
7 <administrative>true</administrative>
8 </lsp>
9 <ero>
10 <subobject>
11 <loose>false</loose>
12 <ip-prefix>
13 <ip-prefix>200.20.160.41/32</ip-prefix>
14 </ip-prefix>
15 </subobject>
16 <subobject>
17 <loose>false</loose>
18 <ip-prefix>
19 <ip-prefix>196.20.160.39/32</ip-prefix>
20 </ip-prefix>
21 </subobject>
22 <subobject>
23 <loose>false</loose>
24 <ip-prefix>
25 <ip-prefix>39.39.39.39/32</ip-prefix>
26 </ip-prefix>
27 </subobject>
28 </ero>
29 </arguments>
30 <network-topology-ref xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology">/topo:network-topology/topo:topology[topo:topology-id="pcep-topology"]</network-topology-ref>
31</input>
@line 2: node The PCC identifier.
@line 3: name The name of the LSP to be updated.
@line 6: delegate - Delegation flag set true in order to keep the LSP control.
@line 7: administrative - Desired administrative status of the LSP is active.
@line 9: ero - This LSP attribute is changed.
Content-Type: application/json
Request Body:
1{
2 "input": {
3 "node": "pcc://43.43.43.43",
4 "name": "foo",
5 "arguments": {
6 "lsp": {
7 "delegate": true,
8 "administrative": true
9 },
10 "ero": {
11 "subobject": [
12 {
13 "loose": false,
14 "ip-prefix": {
15 "ip-prefix": "200.20.160.41/32"
16 }
17 },
18 {
19 "loose": false,
20 "ip-prefix": {
21 "ip-prefix": "196.20.160.39/32"
22 }
23 },
24 {
25 "loose": false,
26 "ip-prefix": {
27 "ip-prefix": "39.39.39.39/32"
28 }
29 }
30 ]
31 }
32 },
33 "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]"
34 }
35}
@line 3: node The PCC identifier.
@line 4: name The name of the LSP to be updated.
@line 7: delegate - Delegation flag set true in order to keep the LSP control.
@line 8: administrative - Desired administrative status of the LSP is active.
@line 10: ero - This LSP attribute is changed.
PCE-initiated LSP Setup¶
The PCEP Extension for PCE-initiated LSP Setup allows PCE to request a creation and deletion of LSPs.
Configuration¶
This capability is enabled by default. No additional configuration is required.
LSP Instantiation¶
The PCE can request LSP creation. The LSP instantiation is done by sending an LSP Initiate Message to PCC. The PCC assign delegation to PCE which triggered creation. PCE-initiated LSPs are identified by Create flag.
LSP instantiation.¶
Following RPC example shows a request for the LSP initiation:
URL: /rests/operations/network-topology-pcep:add-lsp
Method: POST
Content-Type: application/xml
Request Body:
1<input xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep">
2 <node>pcc://43.43.43.43</node>
3 <name>update-tunel</name>
4 <arguments>
5 <lsp xmlns="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful">
6 <delegate>true</delegate>
7 <administrative>true</administrative>
8 </lsp>
9 <endpoints-obj>
10 <ipv4>
11 <source-ipv4-address>43.43.43.43</source-ipv4-address>
12 <destination-ipv4-address>39.39.39.39</destination-ipv4-address>
13 </ipv4>
14 </endpoints-obj>
15 <ero>
16 <subobject>
17 <loose>false</loose>
18 <ip-prefix>
19 <ip-prefix>201.20.160.40/32</ip-prefix>
20 </ip-prefix>
21 </subobject>
22 <subobject>
23 <loose>false</loose>
24 <ip-prefix>
25 <ip-prefix>195.20.160.39/32</ip-prefix>
26 </ip-prefix>
27 </subobject>
28 <subobject>
29 <loose>false</loose>
30 <ip-prefix>
31 <ip-prefix>39.39.39.39/32</ip-prefix>
32 </ip-prefix>
33 </subobject>
34 </ero>
35 </arguments>
36 <network-topology-ref xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology">/topo:network-topology/topo:topology[topo:topology-id="pcep-topology"]</network-topology-ref>
37</input>
@line 2: node The PCC identifier.
@line 3: name The name of the LSP to be created.
@line 9: endpoints-obj - The END-POINT Object is mandatory for an instantiation request of an RSVP-signaled LSP. It contains source and destination addresses for provisioning the LSP.
@line 15: ero - The ERO object is mandatory for LSP initiation request.
Content-Type: application/json
Request Body:
1{
2 "input": {
3 "node": "pcc://43.43.43.43",
4 "name": "update-tunel",
5 "arguments": {
6 "lsp": {
7 "delegate": true,
8 "administrative": true
9 },
10 "endpoints-obj": {
11 "ipv4": {
12 "source-ipv4-address": "43.43.43.43",
13 "destination-ipv4-address": "39.39.39.39"
14 }
15 },
16 "ero": {
17 "subobject": [
18 {
19 "loose": false,
20 "ip-prefix": {
21 "ip-prefix": "201.20.160.40/32"
22 }
23 },
24 {
25 "loose": false,
26 "ip-prefix": {
27 "ip-prefix": "195.20.160.39/32"
28 }
29 },
30 {
31 "loose": false,
32 "ip-prefix": {
33 "ip-prefix": "39.39.39.39/32"
34 }
35 }
36 ]
37 }
38 },
39 "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]"
40 }
41}
@line 3: node The PCC identifier.
@line 4: name The name of the LSP to be created.
@line 10: endpoints-obj - The END-POINT Object is mandatory for an instantiation request of an RSVP-signaled LSP. It contains source and destination addresses for provisioning the LSP.
@line 16: ero - The ERO object is mandatory for LSP initiation request.
LSP Deletion¶
The PCE may request a deletion of PCE-initiated LSPs. The PCE must be delegation holder for this particular LSP.
LSP deletion.¶
Following RPC example shows a request for the LSP deletion:
URL: /rests/operations/network-topology-pcep:remove-lsp
Method: POST
Content-Type: application/xml
Request Body:
1<input xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep">
2 <node>pcc://43.43.43.43</node>
3 <name>update-tunel</name>
4 <network-topology-ref xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology">/topo:network-topology/topo:topology[topo:topology-id="pcep-topology"]</network-topology-ref>
5</input>
@line 2: node The PCC identifier.
@line 3: name The name of the LSP to be removed.
Content-Type: application/json
Request Body:
1{
2 "input": {
3 "node": "pcc://43.43.43.43",
4 "name": "update-tunel",
5 "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]"
6 }
7}
@line 3: node The PCC identifier.
@line 4: name The name of the LSP to be removed.
PCE-initiated LSP Delegation¶
The PCE-initiated LSP control is delegated to the PCE which requested the initiation. The PCC cannot revoke delegation of PCE-initiated LSP. When PCE returns delegation for such LSP or PCE fails, then the LSP become orphan and can be removed by a PCC after some time. The PCE may ask for a delegation of the orphan LSP.
Orphan PCE-initiated LSP - control taken by PCE.¶
Following RPC example illustrates a request for the LSP delegation:
URL: /rests/operations/network-topology-pcep:update-lsp
Method: POST
Content-Type: application/xml
Request Body:
1<input>
2 <node>pcc://43.43.43.43</node>
3 <name>update-tunel</name>
4 <arguments>
5 <lsp xmlns:stateful="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful">
6 <delegate>true</delegate>
7 <administrative>true</administrative>
8 <tlvs>
9 <symbolic-path-name>
10 <path-name>dXBkYXRlLXR1bmVs</path-name>
11 </symbolic-path-name>
12 </tlvs>
13 </lsp>
14 </arguments>
15 <network-topology-ref xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology">/topo:network-topology/topo:topology[topo:topology-id="pcep-topology"]</network-topology-ref>
16</input>
@line 2: node The PCC identifier.
@line 3: name The name of the LSP.
@line 6: delegate - Delegation flag set true in order to take the LSP delegation.
@line 10: path-name - The Symbolic Path Name TLV must be present when sending a request to take a delegation.
Content-Type: application/json
Request Body:
1{
2 "input": {
3 "node": "pcc://43.43.43.43",
4 "name": "update-tunel",
5 "arguments": {
6 "lsp": {
7 "delegate": true,
8 "administrative": true,
9 "tlvs": {
10 "symbolic-path-name": {
11 "path-name": "dXBkYXRlLXR1bmVs"
12 }
13 }
14 }
15 },
16 "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]"
17 }
18}
@line 3: node The PCC identifier.
@line 4: name The name of the LSP.
@line 7: delegate - Delegation flag set true in order to take the LSP delegation.
@line 11: path-name - The Symbolic Path Name TLV must be present when sending a request to take a delegation.
Segment Routing¶
The PCEP Extensions for Segment Routing (SR) allow a stateful PCE to compute and initiate TE paths in SR networks. The SR path is defined as an order list of segments. Segment Routing architecture can be directly applied to the MPLS forwarding plane without changes. Segment Identifier (SID) is encoded as a MPLS label.
Configuration¶
This capability is enabled by default. In order to disable it, a configuration should be changed as follows:
URL: /rests/data/pcep-segment-routing-app-config:pcep-segment-routing-app-config
Method: PUT
Content-Type: application/xml
Request Body:
1<pcep-segment-routing-config xmlns="urn:opendaylight:params:xml:ns:yang:controller:pcep:segment-routing-app-config">
2 <sr-capable>false</sr-capable>
3</pcep-segment-routing-config>
@line 2: sr-capable - True if capability is supported.
Content-Type: application/json
Request Body:
1{
2 "pcep-segment-routing-app-config:pcep-segment-routing-config": {
3 "sr-capable": false
4 }
5}
@line 3: sr-capable - True if capability is supported.
IANA code points¶
In PCEP-SR draft version 6, SR Explicit Route Object/Record Route Object subobjects IANA code points change was proposed. In order to use the latest code points, a configuration should be changed as follows:
URL: /rests/data/pcep-segment-routing-app-config:pcep-segment-routing-config
Method: PUT
Content-Type: application/xml
Request Body:
1<pcep-segment-routing-config xmlns="urn:opendaylight:params:xml:ns:yang:controller:pcep:segment-routing-app-config">
2 <iana-sr-subobjects-type>true</iana-sr-subobjects-type>
3</pcep-segment-routing-config>
@line 2: iana-sr-subobjects-type - True if IANA code points should be used.
Content-Type: application/json
Request Body:
1{
2 "pcep-segment-routing-app-config:pcep-segment-routing-config": {
3 "iana-sr-subobjects-type": true
4 }
5}
@line 3: iana-sr-subobjects-type - True if IANA code points should be used.
LSP Operations for PCEP SR¶
The PCEP SR extension defines new ERO subobject - SR-ERO subobject capable of carrying a SID.
sr-ero-type
+---- c-flag? boolean
+---- m-flag? boolean
+---- sid-type? sid-type
+---- sid? uint32
+---- (nai)?
+--:(ip-node-id)
| +---- ip-address inet:ip-address
+--:(ip-adjacency)
| +---- local-ip-address inet:ip-address
| +---- remote-ip-address inet:ip-address
+--:(unnumbered-adjacency)
+---- local-node-id uint32
+---- local-interface-id uint32
+---- remote-node-id uint32
+---- remote-interface-id uint32
Following RPC example illustrates a request for the SR-TE LSP creation:
URL: /rests/operations/network-topology-pcep:add-lsp
Method: POST
Content-Type: application/xml
Request Body:
1<input xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep">
2 <node>pcc://43.43.43.43</node>
3 <name>sr-path</name>
4 <arguments>
5 <lsp xmlns="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful">
6 <delegate>true</delegate>
7 <administrative>true</administrative>
8 </lsp>
9 <endpoints-obj>
10 <ipv4>
11 <source-ipv4-address>43.43.43.43</source-ipv4-address>
12 <destination-ipv4-address>39.39.39.39</destination-ipv4-address>
13 </ipv4>
14 </endpoints-obj>
15 <path-setup-type xmlns="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful">
16 <pst>1</pst>
17 </path-setup-type>
18 <ero>
19 <subobject>
20 <loose>false</loose>
21 <sid-type xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">ipv4-node-id</sid-type>
22 <m-flag xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">true</m-flag>
23 <sid xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">24001</sid>
24 <ip-address xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">39.39.39.39</ip-address>
25 </subobject>
26 </ero>
27 </arguments>
28 <network-topology-ref xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology">/topo:network-topology/topo:topology[topo:topology-id="pcep-topology"]</network-topology-ref>
29</input>
@line 16: path-setup-type - Set 1 for SR-TE LSP
@line 21: ipv4-node-id - The SR-ERO subobject represents IPv4 Node ID NAI.
@line 22: m-flag - The SID value represents an MPLS label.
@line 23: sid - The Segment Identifier.
Content-Type: application/json
Request Body:
1{
2 "input": {
3 "node": "pcc://43.43.43.43",
4 "name": "sr-path",
5 "arguments": {
6 "lsp": {
7 "delegate": true,
8 "administrative": true
9 },
10 "endpoints-obj": {
11 "ipv4": {
12 "source-ipv4-address": "43.43.43.43",
13 "destination-ipv4-address": "39.39.39.39"
14 }
15 },
16 "path-setup-type": {
17 "pst": 1
18 },
19 "ero": {
20 "subobject": {
21 "loose": false,
22 "sid-type": "ipv4-node-id",
23 "m-flag": true,
24 "sid": 24001,
25 "ip-address": "39.39.39.39"
26 }
27 }
28 },
29 "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]"
30 }
31}
@line 17: path-setup-type - Set 1 for SR-TE LSP
@line 22: ipv4-node-id - The SR-ERO subobject represents IPv4 Node ID NAI.
@line 23: m-flag - The SID value represents an MPLS label.
@line 24: sid - The Segment Identifier.
Following RPC example illustrates a request for the SR-TE LSP update including modified path:
URL: /rests/operations/network-topology-pcep:update-lsp
Method: POST
Content-Type: application/xml
Request Body:
1<input xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep">
2 <node>pcc://43.43.43.43</node>
3 <name>update-tunnel</name>
4 <arguments>
5 <lsp xmlns="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful">
6 <delegate>true</delegate>
7 <administrative>true</administrative>
8 </lsp>
9 <path-setup-type xmlns="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful">
10 <pst>1</pst>
11 </path-setup-type>
12 <ero>
13 <subobject>
14 <loose>false</loose>
15 <sid-type xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">ipv4-node-id</sid-type>
16 <m-flag xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">true</m-flag>
17 <sid xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">24002</sid>
18 <ip-address xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">200.20.160.41</ip-address>
19 </subobject>
20 <subobject>
21 <loose>false</loose>
22 <sid-type xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">ipv4-node-id</sid-type>
23 <m-flag xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">true</m-flag>
24 <sid xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">24001</sid>
25 <ip-address xmlns="urn:opendaylight:params:xml:ns:yang:pcep:segment:routing">39.39.39.39</ip-address>
26 </subobject>
27 </ero>
28 </arguments>
29 <network-topology-ref xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology">/topo:network-topology/topo:topology[topo:topology-id="pcep-topology"]</network-topology-ref>
30</input>
Content-Type: application/json
Request Body:
1{
2 "input": {
3 "node": "pcc://43.43.43.43",
4 "name": "foo",
5 "arguments": {
6 "lsp": {
7 "delegate": true,
8 "administrative": true
9 },
10 "path-setup-type": {
11 "pst": 1
12 },
13 "ero": {
14 "subobject": [
15 {
16 "loose": false,
17 "sid-type": "ipv4-node-id",
18 "m-flag" : true,
19 "sid": 24002,
20 "ip-address": "200.20.160.41"
21 },
22 {
23 "loose": false,
24 "sid-type": "ipv4-node-id",
25 "m-flag" : true,
26 "sid": 24001,
27 "ip-address": "39.39.39.39"
28 }
29 ]
30 }
31 },
32 "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]"
33 }
34}
LSP State Synchronization Optimization Procedures¶
This extension bring optimizations for state synchronization:
State Synchronization Avoidance
Incremental State Synchronization
PCE-triggered Initial Synchronization
PCE-triggered Re-synchronization
Configuration¶
This capability is enabled by default. No additional configuration is required.
State Synchronization Avoidance¶
The State Synchronization Avoidance procedure is intended to skip state synchronization if the state has survived and not changed during session restart.
State Synchronization Skipped.¶
Incremental State Synchronization¶
The Incremental State Synchronization procedure is intended to do incremental (delta) state synchronization when possible.
Incremental Synchronization Procedure.¶
PCE-triggered Initial Synchronization¶
The PCE-triggered Initial Synchronization procedure is intended to do let PCE control the timing of the initial state synchronization.
PCE-triggered Initial State Synchronization Procedure.¶
Following RPC example illustrates a request for the initial synchronization:
URL: /rests/operations/network-topology-pcep:trigger-sync
Method: POST
Content-Type: application/xml
Request Body:
1<input xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep">
2 <node>pcc://43.43.43.43</node>
3 <network-topology-ref xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology">/topo:network-topology/topo:topology[topo:topology-id="pcep-topology"]</network-topology-ref>
4</input>
Content-Type: application/json
Request Body:
1{
2 "input": {
3 "node": "pcc://43.43.43.43",
4 "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]"
5 }
6}
PCE-triggered Re-synchronization¶
The PCE-triggered Re-synchronization: To let PCE re-synchronize the state for sanity check.
PCE-triggered Re-synchronization Procedure.¶
Following RPC example illustrates a request for the LSP re-synchronization:
URL: /rests/operations/network-topology-pcep:trigger-sync
Method: POST
Content-Type: application/xml
Request Body:
1<input xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep">
2 <node>pcc://43.43.43.43</node>
3 <name>update-lsp</name>
4 <network-topology-ref xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology">/topo:network-topology/topo:topology[topo:topology-id="pcep-topology"]</network-topology-ref>
5</input>
@line 3: name - The LSP name. If this parameter is omitted, re-synchronization is requested for all PCC’s LSPs.
Content-Type: application/json
Request Body:
1{
2 "input": {
3 "node": "pcc://43.43.43.43",
4 "name": "update-lsp",
5 "network-topology-ref": "/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\"pcep-topology\"]"
6 }
7}
@line 4: name - The LSP name. If this parameter is omitted, re-synchronization is requested for all PCC’s LSPs.