[BGPCEP-459] PCErr not generated by configuring 32-pcep.xml file to not advertise stateful capability

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

We are trying to test PCEP error type 19 and value 5 by configuring the “32-pcep.xml”(snapshot below) file to not advertise the stateful PCE capability.

Referring to the “Capability advertisement” section below, on not advertising the PCE capability the PCE should generate PCErr type 19 and value 5 but it did not do it in this case.

Please find attached PCAP files that captures the communication happening between PCE and PCC. The file that includes “xrv” in its name was captured with XRv being the PCC and the one without it was done using the PCC mock tool.

Snippet of the configuration in the 32-pcep.xml:

############################################################################

<module>
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:pcep:stateful07:cfg">prefix:stateful-capability</type>
<name>stateful-capability</name>
<stateful>false</stateful>
<initiated>false</initiated>
<active>false</active>
<triggered-initial-sync>false</triggered-initial-sync>
<triggered-resync>false</triggered-resync>
<delta-lsp-sync-capability>false</delta-lsp-sync-capability>
<include-db-version>false</include-db-version>
</module>

############################################################################

. Capability Advertisement

During PCEP Initialization Phase, PCEP Speakers (PCE or PCC)
advertise their support of stateful PCEP extensions. A PCEP Speaker
includes the "Stateful PCE Capability" TLV, described in
Section 7.1.1, in the OPEN Object to advertise its support for PCEP

Crabbe, et al. Expires September 21, 2016 [Page 10]
________________________________________

Internet-Draft PCEP Extensions for Stateful PCE March 2016

stateful extensions. The Stateful Capability TLV includes the 'LSP
Update' Flag that indicates whether the PCEP Speaker supports LSP
parameter updates.

The presence of the Stateful PCE Capability TLV in PCC's OPEN Object
indicates that the PCC is willing to send LSP State Reports whenever
LSP parameters or operational status changes.

The presence of the Stateful PCE Capability TLV in PCE's OPEN message
indicates that the PCE is interested in receiving LSP State Reports
whenever LSP parameters or operational status changes.

The PCEP extensions for stateful PCEs MUST NOT be used if one or both
PCEP Speakers have not included the Stateful PCE Capability TLV in
their respective OPEN message. If the PCEP Speaker on the PCC
supports the extensions of this draft but did not advertise this
capability, then upon receipt of PCUpd message from the PCE, it MUST
generate a PCErr with error-type 19 (Invalid Operation), error-value
2 (Attempted LSP Update Request if the stateful PCE capability was
not advertised)(see Section 8.5) and it SHOULD terminate the PCEP
session. If the PCEP Speaker on the PCE supports the extensions of
this draft but did not advertise this capability, then upon receipt
of a PCRpt message from the PCC, it MUST generate a PCErr with error-
type 19 (Invalid Operation), error-value 5 (Attempted LSP State
Report if active stateful PCE capability was not advertised) (see
Section 8.5) and it SHOULD terminate the PCEP session.

OpenDaylight JIRA

[BGPCEP-459] PCErr not generated by configuring 32-pcep.xml file to not advertise stateful capability