<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><tt>Hello Kotesh,</tt></p>
<br>
<div class="moz-cite-prefix">Le 08/04/2019 à 12:08, kotesh a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAFUqOdxvteiRd-LN62HU0dA+x7M0V+y0PGB74yJemx7GiX-O1w@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div>Hi,</div>
<div><br>
</div>
<div>Could you please let us know if FRR allows to configure a
SR static tunnel with list of SIDs advertised by OSPF
protocol? If yes, could you please provide some sample config?<br>
</div>
</div>
</blockquote>
<br>
<div class="c-message__content" data-qa="message_content"><tt><span
class="c-message__body" dir="auto" data-qa="message-text">Yes
of course. For that purpose, just add a new route to the
prefix you wish and at the end, the list of MPLS labels which
correspond to the list of node SID. What it is not done is to
express the label stack with SID. I mean that, if routers are
not configured with the same SRGB, e.g. one with 20000 and
node SID 200, another one with 10000 and node SID 100, the
label stack must be express with 20200/10100 and not 200/100.<br>
<br>
</span></tt>
<div class="c-message__content" data-qa="message_content"><tt><span
class="c-message__body" dir="auto" data-qa="message-text">The
CLI is:<br>
</span></tt>
<pre><span class="c-message__body" dir="auto" data-qa="message-text"><code class="c-mrkdwn__code" data-stringify-prefix="`" data-stringify-suffix="`" data-stringify-requires-siblings="true"> ip route A.B.C.D/M w.x.y.z label a/b/c</code></span></pre>
<pre><span class="c-message__body" dir="auto" data-qa="message-text"></span></pre>
<tt><span class="c-message__body" dir="auto"
data-qa="message-text">where the label stack is formed by
labels separated by /</span></tt></div>
<div class="c-message__content" data-qa="message_content"><span
class="c-message__body" dir="auto" data-qa="message-text"><tt><br>
</tt><tt>Once perform, you could check with</tt><tt><br>
</tt><tt><br>
</tt><code class="c-mrkdwn__code" data-stringify-prefix="`"
data-stringify-suffix="`"
data-stringify-requires-siblings="true"> show ip route</code><tt><br>
</tt><tt><br>
</tt><tt>and also at the linux prompt</tt><tt><br>
</tt><tt><br>
</tt><code> </code><code class="c-mrkdwn__code"
data-stringify-prefix="`" data-stringify-suffix="`"
data-stringify-requires-siblings="true">ip route<br>
<br>
Let me know if you have any trouble or need extra help.<br>
<br>
Regards<br>
<br>
Olivier<br>
</code></span></div>
<br>
<span class="c-message__body" dir="auto" data-qa="message-text"></span></div>
<blockquote type="cite"
cite="mid:CAFUqOdxvteiRd-LN62HU0dA+x7M0V+y0PGB74yJemx7GiX-O1w@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>Thanks,<br>
</div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Kotesh babu.Chundu</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dev@lists.frrouting.org">dev@lists.frrouting.org</a>
<a class="moz-txt-link-freetext" href="https://lists.frrouting.org/listinfo/dev">https://lists.frrouting.org/listinfo/dev</a>
</pre>
</blockquote>
<br>
<PRE>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>