1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
|
.. _segment-routing:
###############
Segment Routing
###############
Segment Routing (SR) is a network architecture that is similar to source-routing
. In this architecture, the ingress router adds a list of segments, known as
SIDs, to the packet as it enters the network. These segments represent different
portions of the network path that the packet will take.
The SR segments are portions of the network path taken by the packet, and are
called SIDs. At each node, the first SID of the list is read, executed as a
forwarding function, and may be popped to let the next node read the next SID of
the list. The SID list completely determines the path where the packet is
forwarded.
Segment Routing can be applied to an existing MPLS-based data plane and defines
a control plane network architecture. In MPLS networks, segments are encoded as
MPLS labels and are added at the ingress router. These MPLS labels are then
exchanged and populated by Interior Gateway Protocols (IGPs) like IS-IS or OSPF
which are running on most ISPs.
.. note:: Segment routing defines a control plane network architecture and
can be applied to an existing MPLS based dataplane. In the MPLS networks,
segments are encoded as MPLS labels and are imposed at the ingress router.
MPLS labels are exchanged and populated by IGPs like IS-IS.Segment Routing
as per RFC8667 for MPLS dataplane. It supports IPv4, IPv6 and ECMP and has
been tested against Cisco & Juniper routers.however,this deployment is still
EXPERIMENTAL for FRR.
IS-IS SR Configuration
----------------------
Segment routing (SR) is used by the IGP protocols to interconnect network
devices, below configuration shows how to enable SR on IS-IS:
.. note:: ``Known limitations:``
No support for level redistribution (L1 to L2 or L2 to L1)
No support for binding SID
No support for SRLB
Only one SRGB and default SPF Algorithm is supported
.. cfgcmd:: set protocols isis segment-routing global-block high-label-value
<label-value>
Set the Segment Routing Global Block i.e. the label range used by MPLS to
store label in the MPLS FIB for Prefix SID. Note that the block size may
not exceed 65535.
.. cfgcmd:: set protocols isis segment-routing global-block low-label-value
<label-value>
Set the Segment Routing Global Block i.e. the low label range used by MPLS to
store label in the MPLS FIB for Prefix SID. Note that the block size may
not exceed 65535.
.. cfgcmd:: set protocols isis segment-routing local-block high-label-value
<label-value>
Set the Segment Routing Local Block i.e. the label range used by MPLS to
store label in the MPLS FIB for Prefix SID. Note that the block size may
not exceed 65535.Segment Routing Local Block, The negative command always
unsets both.
.. cfgcmd:: set protocols isis segment-routing local-block <low-label-value
<label-value>
Set the Segment Routing Local Block i.e. the low label range used by MPLS to
store label in the MPLS FIB for Prefix SID. Note that the block size may
not exceed 65535.Segment Routing Local Block, The negative command always
unsets both.
.. cfgcmd:: set protocols isis segment-routing maximum-label-depth <1-16>
Set the Maximum Stack Depth supported by the router. The value depend of
the MPLS dataplane.
.. cfgcmd:: set protocols isis segment-routing prefix <address> index value
<0-65535>
A segment ID that contains an IP address prefix calculated by an IGP in the
service provider core network. Prefix SIDs are globally unique, this value
indentify it
.. cfgcmd:: set protocols isis segment-routing prefix <address> index
<no-php-flag | explicit-null| n-flag-clear>
this option allows to configure prefix-sid on SR. The ‘no-php-flag’ means NO
Penultimate Hop Popping that allows SR node to request to its neighbor to
not pop the label. The ‘explicit-null’ flag allows SR node to request to its
neighbor to send IP packet with the EXPLICIT-NULL label. The ‘n-flag-clear’
option can be used to explicitly clear the Node flag that is set by default
for Prefix-SIDs associated to loopback addresses. This option is necessary
to configure Anycast-SIDs.
.. opcmd:: show isis segment-routing node
Show detailed information about all learned Segment Routing Nodes
.. opcmd:: show isis route prefix-sid
Show detailed information about prefix-sid and label learned
.. note:: more information related IGP - :ref:`routing-isis`
OSPF SR Configuration
----------------------
Segment routing (SR) is used by the IGP protocols to interconnect network
devices, below configuration shows how to enable SR on OSPF:
.. cfgcmd:: set protocols ospf parameters opaque-lsa
Enable the Opaque-LSA capability (rfc2370), necessary to transport label
on IGP
.. cfgcmd:: set protocols ospf segment-routing global-block high-label-value
<label-value>
Set the Segment Routing Global Block i.e. the label range used by MPLS to
store label in the MPLS FIB for Prefix SID. Note that the block size may
not exceed 65535.
.. cfgcmd:: set protocols ospf segment-routing global-block low-label-value
<label-value>
Set the Segment Routing Global Block i.e. the low label range used by MPLS to
store label in the MPLS FIB for Prefix SID. Note that the block size may
not exceed 65535.
.. cfgcmd:: set protocols ospf segment-routing local-block high-label-value
<label-value>
Set the Segment Routing Local Block i.e. the label range used by MPLS to
store label in the MPLS FIB for Prefix SID. Note that the block size may
not exceed 65535.Segment Routing Local Block, The negative command always
unsets both.
.. cfgcmd:: set protocols ospf segment-routing local-block <low-label-value
<label-value>
Set the Segment Routing Local Block i.e. the low label range used by MPLS to
store label in the MPLS FIB for Prefix SID. Note that the block size may
not exceed 65535.Segment Routing Local Block, The negative command always
unsets both.
.. cfgcmd:: set protocols ospf segment-routing maximum-label-depth <1-16>
Set the Maximum Stack Depth supported by the router. The value depend of
the MPLS dataplane.
.. cfgcmd:: set protocols ospf segment-routing prefix <address> index value
<0-65535>
A segment ID that contains an IP address prefix calculated by an IGP in the
service provider core network. Prefix SIDs are globally unique, this value
indentify it
.. cfgcmd:: set protocols ospf segment-routing prefix <address> index
<no-php-flag | explicit-null| n-flag-clear>
this option allows to configure prefix-sid on SR. The ‘no-php-flag’ means NO
Penultimate Hop Popping that allows SR node to request to its neighbor to
not pop the label. The ‘explicit-null’ flag allows SR node to request to its
neighbor to send IP packet with the EXPLICIT-NULL label. The ‘n-flag-clear’
option can be used to explicitly clear the Node flag that is set by default
for Prefix-SIDs associated to loopback addresses. This option is necessary
to configure Anycast-SIDs.
.. note:: more information related IGP - :ref:`routing-ospf`
Configuration Example
---------------------
we described the configuration SR ISIS / SR OSPF using 2 connected with them to
share label information.
Enable IS-IS with Segment Routing (Experimental)
================================================
**Node 1:**
.. code-block:: none
set interfaces loopback lo address '192.168.255.255/32'
set interfaces ethernet eth1 address '192.0.2.1/24'
set protocols isis interface eth1
set protocols isis interface lo
set protocols isis net '49.0001.1921.6825.5255.00'
set protocols isis segment-routing global-block high-label-value '599'
set protocols isis segment-routing global-block low-label-value '550'
set protocols isis segment-routing prefix 192.168.255.255/32 index value '1'
set protocols isis segment-routing prefix 192.168.255.255/32 index explicit-null
set protocols mpls interface 'eth1'
**Node 2:**
.. code-block:: none
set interfaces loopback lo address '192.168.255.254/32'
set interfaces ethernet eth1 address '192.0.2.2/24'
set protocols isis interface eth1
set protocols isis interface lo
set protocols isis net '49.0001.1921.6825.5254.00'
set protocols isis segment-routing global-block high-label-value '599'
set protocols isis segment-routing global-block low-label-value '550'
set protocols isis segment-routing prefix 192.168.255.254/32 index value '2'
set protocols isis segment-routing prefix 192.168.255.254/32 index explicit-null
set protocols mpls interface 'eth1'
This gives us MPLS segment routing enabled and labels for far end loopbacks:
.. code-block:: none
Node-1@vyos:~$ show mpls table
Inbound Label Type Nexthop Outbound Label
----------------------------------------------------------------------
552 SR (IS-IS) 192.0.2.2 IPv4 Explicit Null <-- Node-2 loopback learned on Node-1
15000 SR (IS-IS) 192.0.2.2 implicit-null
15001 SR (IS-IS) fe80::e87:6cff:fe09:1 implicit-null
15002 SR (IS-IS) 192.0.2.2 implicit-null
15003 SR (IS-IS) fe80::e87:6cff:fe09:1 implicit-null
Node-2@vyos:~$ show mpls table
Inbound Label Type Nexthop Outbound Label
---------------------------------------------------------------------
551 SR (IS-IS) 192.0.2.1 IPv4 Explicit Null <-- Node-1 loopback learned on Node-2
15000 SR (IS-IS) 192.0.2.1 implicit-null
15001 SR (IS-IS) fe80::e33:2ff:fe80:1 implicit-null
15002 SR (IS-IS) 192.0.2.1 implicit-null
15003 SR (IS-IS) fe80::e33:2ff:fe80:1 implicit-null
Here is the routing tables showing the MPLS segment routing label operations:
.. code-block:: none
Node-1@vyos:~$ show ip route isis
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
f - OpenFabric,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
I 192.0.2.0/24 [115/20] via 192.0.2.2, eth1 inactive, weight 1, 00:07:48
I>* 192.168.255.254/32 [115/20] via 192.0.2.2, eth1, label IPv4 Explicit Null, weight 1, 00:03:39
Node-2@vyos:~$ show ip route isis
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
f - OpenFabric,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
I 192.0.2.0/24 [115/20] via 192.0.2.1, eth1 inactive, weight 1, 00:07:46
I>* 192.168.255.255/32 [115/20] via 192.0.2.1, eth1, label IPv4 Explicit Null, weight 1, 00:03:43
Enable OSPF with Segment Routing (Experimental):
================================================
**Node 1**
.. code-block:: none
set interfaces loopback lo address 10.1.1.1/32
set interfaces ethernet eth0 address 192.168.0.1/24
set protocols ospf area 0 network '192.168.0.0/24'
set protocols ospf area 0 network '10.1.1.1/32'
set protocols ospf parameters opaque-lsa
set protocols ospf parameters router-id '10.1.1.1'
set protocols ospf segment-routing global-block high-label-value '1100'
set protocols ospf segment-routing global-block low-label-value '1000'
set protocols ospf segment-routing prefix 10.1.1.1/32 index explicit-null
set protocols ospf segment-routing prefix 10.1.1.1/32 index value '1'
**Node 2**
.. code-block:: none
set interfaces loopback lo address 10.1.1.2/32
set interfaces ethernet eth0 address 192.168.0.2/24
set protocols ospf area 0 network '192.168.0.0/24'
set protocols ospf area 0 network '10.1.1.2/32'
set protocols ospf parameters opaque-lsa
set protocols ospf parameters router-id '10.1.1.2'
set protocols ospf segment-routing global-block high-label-value '1100'
set protocols ospf segment-routing global-block low-label-value '1000'
set protocols ospf segment-routing prefix 10.1.1.2/32 index explicit-null
set protocols ospf segment-routing prefix 10.1.1.2/32 index value '2'
This gives us MPLS segment routing enabled and labels for far end loopbacks:
.. code-block:: none
Node-1@vyos:~$ show mpls table
Inbound Label Type Nexthop Outbound Label
-----------------------------------------------------------
1002 SR (OSPF) 192.168.0.2 IPv4 Explicit Null <-- Node-2 loopback learned on Node-1
15000 SR (OSPF) 192.168.0.2 implicit-null
15001 SR (OSPF) 192.168.0.2 implicit-null
Node-2@vyos:~$ show mpls table
Inbound Label Type Nexthop Outbound Label
-----------------------------------------------------------
1001 SR (OSPF) 192.168.0.1 IPv4 Explicit Null <-- Node-1 loopback learned on Node-2
15000 SR (OSPF) 192.168.0.1 implicit-null
15001 SR (OSPF) 192.168.0.1 implicit-null
Here is the routing tables showing the MPLS segment routing label operations:
.. code-block:: none
Node-1@vyos:~$ show ip route ospf
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
f - OpenFabric,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
O 10.1.1.1/32 [110/0] is directly connected, lo, weight 1, 00:03:43
O>* 10.1.1.2/32 [110/1] via 192.168.0.2, eth0, label IPv4 Explicit Null, weight 1, 00:03:32
O 192.168.0.0/24 [110/1] is directly connected, eth0, weight 1, 00:03:43
Node-2@vyos:~$ show ip route ospf
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
f - OpenFabric,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
O>* 10.1.1.1/32 [110/1] via 192.168.0.1, eth0, label IPv4 Explicit Null, weight 1, 00:03:36
O 10.1.1.2/32 [110/0] is directly connected, lo, weight 1, 00:03:51
O 192.168.0.0/24 [110/1] is directly connected, eth0, weight 1, 00:03:51
|
