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
|
# Ethernet VPN (EVPN)
This page explains an configuration for EVPN. Note that the feature is
still very experimental.
## Contents
- [BaGpipe](#bagpipe)
- [YABGP](#yabgp)
## <a name="bagpipe"> BaGPipe
This example uses [BaGPipe
BGP](https://github.com/Orange-OpenSource/bagpipe-bgp). GoBGP receives
routes from one BaGPipe peer and advertises it to another BaGPipe peer.
If you don't want to install [BaGPipe
BGP](https://github.com/Orange-OpenSource/bagpipe-bgp) by hand, you can use [Our BaGPipe BGP Docker
image](https://registry.hub.docker.com/u/yoshima/bagpipe-bgp/).
### Configuration
BaGPipe supports only iBGP. GoBGP peer connects to two BaGPipe
peers. Two BaGPipe peers are not connected. It's incorrect from the
perspective of BGP but this example just shows two OSS BGP
implementations can interchange EVPN messages.
```toml
[global.config]
as = 64512
router-id = "192.168.255.1"
[[neighbors]]
[neighbors.config]
neighbor-address = "10.0.255.1"
peer-as = 64512
[[neighbors.afi-safis]]
[neighbors.afi-safis.config]
afi-safi-name = "l2vpn-evpn"
[[neighbors]]
[neighbors.config]
neighbor-address = "10.0.255.2"
peer-as = 64512
[[neighbors.afi-safis]]
[neighbors.afi-safis.config]
afi-safi-name = "l2vpn-evpn"
```
The point is that route families to be advertised need to be
specified. We expect that many people are not familiar with [BaGPipe
BGP](https://github.com/Orange-OpenSource/bagpipe-bgp), the following
is our configuration files.
```bash
bagpipe-peer1:/etc/bagpipe-bgp# cat bgp.conf
[BGP]
local_address=10.0.255.1
peers=10.0.255.254
my_as=64512
enable_rtc=True
[API]
api_host=localhost
api_port=8082
[DATAPLANE_DRIVER_IPVPN]
dataplane_driver = DummyDataplaneDriver
[DATAPLANE_DRIVER_EVPN]
dataplane_driver = DummyDataplaneDriver
```
10.0.255.254 is GoBGP peer's address.
### Advertising EVPN route
As you expect, the RIBs at 10.0.255.2 peer has nothing.
```bash
bagpipe-peer2:~# bagpipe-looking-glass bgp routes
match:IPv4/mpls-vpn,*: -
match:IPv4/rtc,*: -
match:L2VPN/evpn,*: -
```
Let's advertise something from 10.0.255.1 peer.
```bash
bagpipe-peer1:~# bagpipe-rest-attach --attach --port tap42 --mac 00:11:22:33:44:55 --ip 11.11.11.1 --gateway-ip 11.11.11.254 --network-type evpn --rt 65000:77
```
Now the RIBs at 10.0.255.2 peer has the above route. The route was interchanged via GoBGP peer.
```bash
bagpipe-peer2:~# bagpipe-looking-glass bgp routes
match:IPv4/mpls-vpn,*: -
match:IPv4/rtc,*: -
match:L2VPN/evpn,*:
* EVPN:Multicast:[rd:10.0.255.1:1][etag:178][10.0.255.1]:
attributes:
next_hop: 10.0.255.1
pmsi_tunnel: PMSITunnel:IngressReplication:0:[0]:[10.0.255.1]
extended_community: [ target:65000:77 Encap:VXLAN ]
afi-safi: L2VPN/evpn
source: BGP-10.0.255.254/192.168.255.1 (...)
route_targets:
* target:65000:77
* EVPN:MACAdv:[rd:10.0.255.1:1][esi:-][etag:178][00:11:22:33:44:55][11.11.11.1][label:0]:
attributes:
next_hop: 10.0.255.1
extended_community: [ target:65000:77 Encap:VXLAN ]
afi-safi: L2VPN/evpn
source: BGP-10.0.255.254/192.168.255.1 (...)
route_targets:
* target:65000:77
```
## <a name="yabgp"> YABGP
Just like the last example, this example uses [YABGP](https://github.com/smartbgp/yabgp). GoBGP receives
routes from one YABGP peer and advertises it to another YABGP peer.
### Configuration
Gobgp configuration:
```toml
[global.config]
as = 100
router-id = "192.168.1.2"
local-address-list = ["10.79.45.72"]
[[neighbors]]
[neighbors.config]
neighbor-address = "10.75.44.10"
peer-as = 300
[[neighbors.afi-safis]]
[neighbors.afi-safis.config]
afi-safi-name = "l2vpn-evpn"
[neighbors.transport.config]
local-address = "10.79.45.72"
[neighbors.ebgp-multihop.config]
enabled = true
[[neighbors]]
[neighbors.config]
neighbor-address = "10.75.44.11"
peer-as = 200
[[neighbors.afi-safis]]
[neighbors.afi-safis.config]
afi-safi-name = "l2vpn-evpn"
[neighbors.transport.config]
local-address = "10.79.45.72"
[neighbors.ebgp-multihop.config]
enabled = true
```
`10.75.44.10` and `10.75.44.11` is the address of YABGP peers. We start two YABGP agents like this:
```bash
python yabgp/bin/yabgpd --bgp-local_as=300 --bgp-remote_addr=10.79.45.72 --bgp-remote_as=100 --bgp-local_addr=10.75.44.10 --bgp-afi_safi=evpn
```
``` bash
python yabgp/bin/yabgpd --bgp-local_as=200 --bgp-remote_addr=10.79.45.72 --bgp-remote_as=100 --bgp-local_addr=10.75.44.11 --bgp-afi_safi=evpn
```
From gobgp CMD:
``` bash
$ gobgp neighbor
Peer AS Up/Down State |#Advertised Received Accepted
10.75.44.10 300 00:01:23 Establ | 0 0 0
10.75.44.11 200 00:02:26 Establ | 0 0 0
```
### Advertising EVPN route
We can advertise EVPN routes from YABGP 10.75.44.11 through its REST API,
the `Authorization` header is `admin/admin`, and the `Content-Type` is `application/json`.
``` bash
POST http://10.75.44.11:8801/v1/peer/10.79.45.72/send/update
```
We will run this API four times, each time's POST data is:
EVPN type 1:
``` json
{
"attr":{
"1": 0,
"2": [],
"5": 100,
"14": {
"afi_safi": [25, 70],
"nexthop": "10.75.44.254",
"nlri": [{
"type": 1,
"value": {
"rd": "1.1.1.1:32867",
"esi": 0,
"eth_tag_id": 100,
"label": [10]
}
}]},
"16":[[1537, 0, 500]]
}}
```
EVPN type 2:
``` json
{
"attr":{
"1": 0,
"2": [],
"5": 100,
"14": {
"afi_safi": [25, 70],
"nexthop": "10.75.44.254",
"nlri": [
{
"type": 2,
"value": {
"eth_tag_id": 108,
"ip": "11.11.11.1",
"label": [0],
"rd": "172.17.0.3:2",
"mac": "00-11-22-33-44-55",
"esi": 0}}]},
"16":[[1536, 1, 500]]
}}
```
EVPN type 3:
``` json
{
"attr":{
"1": 0,
"2": [],
"5": 100,
"14": {
"afi_safi": [25, 70],
"nexthop": "10.75.44.254",
"nlri": [
{
"type": 3,
"value": {
"rd": "172.16.0.1:5904",
"eth_tag_id": 100,
"ip": "192.168.0.1"
}
}
]
}
}}
```
EVPN type 4:
``` json
{
"attr":{
"1": 0,
"2": [],
"5": 100,
"14": {
"afi_safi": [25, 70],
"nexthop": "10.75.44.254",
"nlri": [
{
"type": 4,
"value": {
"rd": "172.16.0.1:8888",
"esi": 0,
"ip": "192.168.0.1"
}
}
]
},
"16":[[1538, "00-11-22-33-44-55"]]
}}
```
GoBGP will received these four routes and readvertise them to peer 10.75.44.10
``` bash
$ gobgp monitor adj-in
[ROUTE] [type:A-D][rd:1.1.1.1:32867][esi:single-homed][etag:100][label:161] via 10.75.44.254 aspath [] attrs [{Extcomms: [esi-label: 8001]} {Origin: i} {LocalPref: 100}]
[ROUTE] [type:macadv][rd:172.17.0.3:2][esi:single-homed][etag:108][mac:00:11:22:33:44:55][ip:11.11.11.1][labels:[0]] via 10.75.44.254 aspath [] attrs [{Extcomms: [mac-mobility: 500, sticky]} {Origin: i} {LocalPref: 100}]
[ROUTE] [type:multicast][rd:172.16.0.1:5904][etag:100][ip:192.168.0.1] via 10.75.44.254 aspath [] attrs [{Origin: i} {LocalPref: 100}]
[ROUTE] [type:esi][rd:172.16.0.1:8888][esi:{0 [0 0 0 0 0 0 0 0 0]}][ip:192.168.0.1] via 10.75.44.254 aspath [] attrs [{Extcomms: [es-import rt: 00:11:22:33:44:55]} {Origin: i} {LocalPref: 100}]
```
``` bash
$ gobgp neighbor
Peer AS Up/Down State |#Advertised Received Accepted
10.75.44.10 300 00:21:00 Establ | 4 0 0
10.75.44.11 200 00:22:03 Establ | 0 4 4
```
|
