[BGPCEP-443] Get operation of pcep-topology returns wrong prefix mask for next-hop addresses

Sun, 3 Mar 2019 11:49:44 +0000

The actual prefix masks for the next hops used in LSP are configured for /24 not /32 as output below from running the following Get REST call. The ERO's reported during the GET operation reflects /32 for all the hops.

http://10.18.133.157:8181/restconf/operational/network-topology:network-topology/topology/pcep-topology-1

<topology xmlns="urn:TBD:params:xml:ns:yang:network-topology">
<topology-id>pcep-topology-1</topology-id>
<topology-types>
<topology-pcep xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep"></topology-pcep>
</topology-types>
<node>
<node-id>pcc://10.18.132.89</node-id>
<path-computation-client xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep">
<reported-lsp>
<name>ios_t0</name>
<path>
<lsp-id>11</lsp-id>
<lspa>
<processing-rule>false</processing-rule>
<setup-priority>7</setup-priority>
<local-protection-desired>false</local-protection-desired>
<tlvs></tlvs>
<hold-priority>7</hold-priority>
<ignore>false</ignore>
<include-any>0</include-any>
<include-all>0</include-all>
<exclude-any>0</exclude-any>
</lspa>
<lsp xmlns="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful">
<remove>false</remove>
<ignore>false</ignore>
<processing-rule>false</processing-rule>
<sync>false</sync>
<create xmlns="urn:opendaylight:params:xml:ns:yang:pcep:crabbe:initiated">false</create>
<tlvs>
<lsp-identifiers>
<ipv4>
<ipv4-extended-tunnel-id>192.168.254.3</ipv4-extended-tunnel-id>
<ipv4-tunnel-sender-address>192.168.254.6</ipv4-tunnel-sender-address>
<ipv4-tunnel-endpoint-address>192.168.254.3</ipv4-tunnel-endpoint-address>
</ipv4>
<tunnel-id>0</tunnel-id>
<lsp-id>11</lsp-id>
</lsp-identifiers>
<path-binding>
<binding-value>AAXcMAA=</binding-value>
<binding-type>0</binding-type>
</path-binding>
<symbolic-path-name>
<path-name>aW9zX3Qw</path-name>
</symbolic-path-name>
</tlvs>
<administrative>true</administrative>
<delegate>true</delegate>
<operational>up</operational>
<plsp-id>1</plsp-id>
</lsp>
<ero>
<ignore>false</ignore>
<subobject>
<ip-prefix>
<ip-prefix>10.0.0.16/32</ip-prefix>
</ip-prefix>
<loose>false</loose>
</subobject>
<subobject>
<ip-prefix>
<ip-prefix>2.2.2.14/32</ip-prefix>
</ip-prefix>
<loose>false</loose>
</subobject>
<subobject>
<ip-prefix>
<ip-prefix>100.1.1.37/32</ip-prefix>
</ip-prefix>
<loose>false</loose>
</subobject>
<subobject>
<ip-prefix>
<ip-prefix>192.168.254.3/32</ip-prefix>
</ip-prefix>
<loose>false</loose>
</subobject>
<processing-rule>false</processing-rule>
</ero>
<bandwidth>
<ignore>false</ignore>
<bandwidth>AAAAAA==</bandwidth>
<processing-rule>false</processing-rule>
</bandwidth>
</path>
</reported-lsp>
<state-sync>synchronized</state-sync>
<ip-address>10.18.132.89</ip-address>
<stateful-tlv>
<stateful xmlns="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful">
<lsp-update-capability>true</lsp-update-capability>
<initiation xmlns="urn:opendaylight:params:xml:ns:yang:pcep:crabbe:initiated">true</initiation>
</stateful>
</stateful-tlv>
</path-computation-client>
</node>
</topology>

OpenDaylight JIRA

[BGPCEP-443] Get operation of pcep-topology returns wrong prefix mask for next-hop addresses