04-24-2023 12:45 AM
Good day! I have been working on implementing PCE-initiated LSPs from a Cisco PCE to Junos PCC for a SR-MPLS based network with multiple domains. It is working good, but for an unknown reason the color attribute of the SRTE tuple is not taken by the Juniper PCC. I have tried with Cisco PCC and it accepts the color as an attribute of the SRTE policy.
From debugs, I don't see any clue about the reason of the issue. So I would like to know if something else needs to be configured on the PCE or if there is known interoperability issue to exchange this SRTE tuple attribute.
Below configuration on the PCC side and some debugs on Cisco PCE and Junos PCC. Cisco to Cisco is working perfectly.
#PCEP Configuration on PCC (Junos)
pce pccd {
local-address 34.34.34.34;
destination-ipv4-address 100.200.100.200;
destination-port 4189;
pce-type active stateful;
lsp-provisioning;
spring-capability;
}
#PCEP message received on PCC
Mar 30 23:27:49.337245 [229] pccd_rpd_debug_lsp_info(): rx pcreq name(PCE-LATENCY) path() template() is src dest ipv6(0) src(1.1.1.1) dst(2.1.1.1) msg_trigger() type(3) state(1) control(1) flags(0x0) admin grp exclude(0) admin grp include any(0) admin grp include all(0) setup prio(0) hold prio(0) bw(0bps) metric(3100) binding type (0) binding value (0)
It shows other attributes but not the srte color.
#PCEP message send by the PCE (Last line shows the color attribute)
RP/0/RP0/CPU0:Mar 31 00:06:05.138 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_tx_msg:808 Sending Initiate to 1.1.1.1.
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9450 Size with SRP: 20
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9482 Size after adding LSP: 68
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9497 Size after adding EP: 80
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9503 Size after adding vendor-info: 104
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9517 Size after adding ASSO: 104
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9540 Size after adding ERO: 188
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9547 Size after adding metric: 200
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9902 *** ST 3, sr_ero_subobj_size = 16
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9902 *** ST 3, sr_ero_subobj_size = 16
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9902 *** ST 3, sr_ero_subobj_size = 16
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9902 *** ST 3, sr_ero_subobj_size = 16
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_send_initiate_msg:9902 *** ST 3, sr_ero_subobj_size = 16
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_add_vendor_object:8041 Added Vendor ID: 9
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_add_color_tlv:7904 Added COLOR TLV header: color: 10
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_add_preference_tlv:7930 Added PREFERENCE TLV header: preference: 100
RP/0/RP0/CPU0:Mar 31 00:06:05.139 UTC: pce_server[1143]: DBG-PCEP:[139836093351680] pce_add_vendor_object:8051 Added vendor obj Vendor-id:9, color:10, preference:100
Hope someone can help me to clarify this behaviour.
Thanks!
Solved! Go to Solution.
04-24-2023 10:34 AM
Hi @rocketnet ,
This is a vendor specific object class as per RFC7470, section 4 and therefore it makes sense that it is not supported by JUNOS.
"Added vendor obj Vendor-id:9, color:10, preference:100"
Vendor ID 9 is Cisco.
https://www.rfc-editor.org/rfc/rfc7470.html#section-4
Regards,
04-24-2023 10:34 AM
Hi @rocketnet ,
This is a vendor specific object class as per RFC7470, section 4 and therefore it makes sense that it is not supported by JUNOS.
"Added vendor obj Vendor-id:9, color:10, preference:100"
Vendor ID 9 is Cisco.
https://www.rfc-editor.org/rfc/rfc7470.html#section-4
Regards,
04-25-2023 10:22 PM
Hi Harold,
Thanks a lot for clarifying this behaviour.
Regards,
Willy
04-26-2023 06:18 AM
You are very welcome @rocketnet and thanks for the feedback
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide