Routing

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
Back to discussions
Expand all | Collapse all

SR, source-routing-path-template, l2circuit

  • 1.  SR, source-routing-path-template, l2circuit

    This message was posted by a user wishing to remain anonymous
    Posted 01-25-2024 06:36
    This message was posted by a user wishing to remain anonymous

    Hi,
    I am lab-ing some setup and need some advice  (pointing to the right documentation/examples). 

    it could be that my mind is wrong, so let me describe the goal I am looking to achieve: 

    I am looking to have a pseudo-wire (l2circuit), build over SR and the possibility to map it to a preferable LSP 

    The idea I have in my lab mind is as follows:

    - I do have a well-known l2circuit based on the RSVP (as label distribution). There is a very clear and easy-to-implement mechanism to "map" the l2circuit to an LSP (based on the community).


    set policy-options policy-statement L2C term 1 from protocol l2circuit
    set policy-options policy-statement L2C term 1 from community 100:100
    set policy-options policy-statement L2C term 1 then install-nexthop lsp vMX1-vMX3-vMX5-vMX8
    set policy-options policy-statement L2C term 1 then install-nexthop lsp LSP1
    set policy-options policy-statement L2C term 2 from protocol l2circuit
    set policy-options policy-statement L2C term 2 from community 200:200
    set policy-options policy-statement L2C term 2 then install-nexthop lsp vMX1-vMX2-vMX4-vMX6-vMX8
    set policy-options policy-statement L2C term 2 then install-nexthop lsp LSP2

    set protocols l2circuit neighbor 1.1.1.8 interface xe-0/0/7.100 virtual-circuit-id 100
    set protocols l2circuit neighbor 1.1.1.8 interface xe-0/0/7.100 community 100:100
    set protocols l2circuit neighbor 1.1.1.8 interface xe-0/0/7.200 virtual-circuit-id 200
    set protocols l2circuit neighbor 1.1.1.8 interface xe-0/0/7.200 community 200:200

    It's all working as expected.

    - Now I am looking to a similar approach but, having a SR as label-distribution.  The only possibility I found so far is

    to use the following term 

    set policy-options policy-statement l2c term 1 from protocol l2circuit
    set policy-options policy-statement l2c term 1 from community 100:100
    set policy-options policy-statement l2c term 1 then source-routing-path-template vMX8-template1
    set policy-options policy-statement l2c term 2 from protocol l2circuit
    set policy-options policy-statement l2c term 2 from community 200:200
    set policy-options policy-statement l2c term 2 then source-routing-path-template vMX8-template2

    where the template is just a set of constraints (similar to SR-TE path definition). 

    My idea was that this template would be used to create a LSP to a "    signalled/discovered/configured" l2circuit neighbor  - obviously it does not work.

    Any ideas or comments are very welcome!

    Thank you