]>
Commit | Line | Data |
---|---|---|
1556b768 AD |
1 | [[chapter_pvesdn]] |
2 | Software Defined Network | |
3 | ======================== | |
4 | ifndef::manvolnum[] | |
5 | :pve-toplevel: | |
6 | endif::manvolnum[] | |
7 | ||
ee6e18c4 TL |
8 | The **S**oftware **D**efined **N**etwork (SDN) feature allows one to create |
9 | virtual networks (vnets) at datacenter level. | |
1556b768 | 10 | |
ee6e18c4 TL |
11 | WARNING: SDN is currently an **experimental feature** in {pve}. This |
12 | Documentation for it is also still under development, ask on our | |
13 | xref:getting_help[mailing lists or in the forum] for questions and feedback. | |
14 | ||
15 | ||
4e652aba | 16 | [[pvesdn_installation]] |
ee6e18c4 TL |
17 | Installation |
18 | ------------ | |
19 | ||
20 | To enable the experimental SDN integration, you need to install | |
21 | "libpve-network-perl" package | |
1556b768 AD |
22 | |
23 | ---- | |
24 | apt install libpve-network-perl | |
25 | ---- | |
26 | ||
ee6e18c4 TL |
27 | You need to have `ifupdown2` package installed on each node to manage local |
28 | configuration reloading without reboot: | |
1556b768 AD |
29 | |
30 | ---- | |
31 | apt install ifupdown2 | |
32 | ---- | |
33 | ||
a6af82c7 AD |
34 | You need to add |
35 | ---- | |
36 | source /etc/network/interfaces.d/* | |
37 | ---- | |
38 | at the end of /etc/network/interfaces to have the sdn config included | |
39 | ||
40 | ||
ee6e18c4 TL |
41 | Basic Overview |
42 | -------------- | |
43 | ||
44 | The {pve} SDN allows separation and fine grained control of Virtual Guests | |
45 | networks, using flexible software controlled configurations. | |
46 | ||
8ac25ffe TL |
47 | Separation consists of zones, a zone is it's own virtual separated network area. |
48 | A 'VNet' is a type of a virtual network connected to a zone. Depending on which | |
49 | type or plugin the zone uses it can behave differently and offer different | |
50 | features, advantages or disadvantages. | |
51 | Normally a 'VNet' shows up as a common Linux bridge with either a VLAN or | |
52 | 'VXLAN' tag, but some can also use layer 3 routing for control. | |
53 | The 'VNets' are deployed locally on each node, after configuration was committed | |
60ed554f | 54 | from the cluster-wide datacenter SDN administration interface. |
ee6e18c4 TL |
55 | |
56 | ||
1556b768 | 57 | Main configuration |
a6af82c7 | 58 | ~~~~~~~~~~~~~~~~~~ |
1556b768 | 59 | |
ee6e18c4 TL |
60 | The configuration is done at datacenter (cluster-wide) level, it will be saved |
61 | in configuration files located in the shared configuration file system: | |
62 | `/etc/pve/sdn` | |
1556b768 | 63 | |
a6af82c7 | 64 | On the web-interface SDN feature have 3 main sections for the configuration |
1556b768 | 65 | |
ee6e18c4 | 66 | * SDN: a overview of the SDN state |
1556b768 | 67 | |
ee6e18c4 | 68 | * Zones: Create and manage the virtual separated network Zones |
1556b768 | 69 | |
a6af82c7 AD |
70 | * VNets: Create virtual network bridges + subnets management. |
71 | ||
72 | And some options: | |
1556b768 | 73 | |
8ac25ffe | 74 | * Controller: For complex setups to control Layer 3 routing |
1556b768 | 75 | |
3093e62d | 76 | * Sub-nets: Used to defined ip networks on VNets. |
a6af82c7 | 77 | |
3093e62d | 78 | * IPAM: Allow to use external tools for IP address management (guest IPs) |
a6af82c7 | 79 | |
3093e62d TL |
80 | * DNS: Allow to define a DNS server api for registering a virtual guests |
81 | hostname and IP-addresses | |
1556b768 | 82 | |
4e652aba | 83 | [[pvesdn_config_main_sdn]] |
a6af82c7 | 84 | |
1556b768 AD |
85 | SDN |
86 | ~~~ | |
87 | ||
ee6e18c4 TL |
88 | This is the main status panel. Here you can see deployment status of zones on |
89 | different nodes. | |
1556b768 | 90 | |
ee6e18c4 | 91 | There is an 'Apply' button, to push and reload local configuration on all |
60ed554f | 92 | cluster nodes. |
1556b768 AD |
93 | |
94 | ||
a6af82c7 AD |
95 | [[pvesdn_local_deployment_monitoring]] |
96 | Local Deployment Monitoring | |
97 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
98 | ||
99 | After applying the configuration through the main SDN web-interface panel, | |
100 | the local network configuration is generated locally on each node in | |
101 | `/etc/network/interfaces.d/sdn`, and with ifupdown2 reloaded. | |
102 | ||
103 | You can monitor the status of local zones and vnets through the main tree. | |
104 | ||
105 | ||
4e652aba | 106 | [[pvesdn_config_zone]] |
1556b768 | 107 | Zones |
a6af82c7 | 108 | ----- |
1556b768 | 109 | |
ee6e18c4 | 110 | A zone will define a virtually separated network. |
1556b768 | 111 | |
ee6e18c4 | 112 | It can use different technologies for separation: |
1556b768 | 113 | |
ee6e18c4 | 114 | * VLAN: Virtual LANs are the classic method to sub-divide a LAN |
1556b768 | 115 | |
ee6e18c4 | 116 | * QinQ: stacked VLAN (formally known as `IEEE 802.1ad`) |
1556b768 | 117 | |
ee6e18c4 | 118 | * VXLAN: (layer2 vxlan) |
1556b768 | 119 | |
a6af82c7 AD |
120 | * Simple: Isolated Bridge, simple l3 routing bridge (NAT) |
121 | ||
ee6e18c4 | 122 | * bgp-evpn: vxlan using layer3 border gateway protocol routing |
1556b768 AD |
123 | |
124 | You can restrict a zone to specific nodes. | |
125 | ||
ee6e18c4 TL |
126 | It's also possible to add permissions on a zone, to restrict user to use only a |
127 | specific zone and only the VNets in that zone | |
1556b768 | 128 | |
a6af82c7 AD |
129 | Common options |
130 | ~~~~~~~~~~~~~~ | |
1556b768 | 131 | |
3093e62d TL |
132 | The following options are available for all zone types. |
133 | ||
a6af82c7 AD |
134 | nodes:: Deploy and allow to use a VNets configured for this Zone only on these |
135 | nodes. | |
9e773815 | 136 | |
3093e62d | 137 | ipam:: Optional, if you want to use an ipam tool to manage ips in this zone |
1556b768 | 138 | |
3093e62d | 139 | dns:: Optional, dns api server. |
1556b768 | 140 | |
3093e62d | 141 | reversedns:: Optional, reverse dns api server. |
1556b768 | 142 | |
3093e62d TL |
143 | dnszone:: Optional, dns domain name. Use to register hostname like |
144 | `<hostname>.<domain>`. The dns zone need to be already existing in dns server. | |
1556b768 AD |
145 | |
146 | ||
a6af82c7 AD |
147 | [[pvesdn_zone_plugin_simple]] |
148 | Simple Zones | |
149 | ~~~~~~~~~~~~ | |
1556b768 | 150 | |
a6af82c7 AD |
151 | This is the simplest plugin, it will create an isolated vnet bridge. |
152 | This bridge is not linked to physical interfaces, VM traffic is only | |
153 | local to the node(s). | |
154 | It can be also used for NAT or routed setup. | |
1556b768 | 155 | |
4e652aba | 156 | [[pvesdn_zone_plugin_vlan]] |
ee6e18c4 TL |
157 | VLAN Zones |
158 | ~~~~~~~~~~ | |
1556b768 | 159 | |
a6af82c7 AD |
160 | This plugin will reuse an existing local Linux or OVS bridge, |
161 | and manage VLANs on it. | |
ee6e18c4 TL |
162 | The benefit of using SDN module, is that you can create different zones with |
163 | specific VNets VLAN tag, and restrict Virtual Machines to separated zones. | |
1556b768 | 164 | |
ee6e18c4 | 165 | Specific `VLAN` configuration options: |
1556b768 | 166 | |
a91b3e7f | 167 | bridge:: Reuse this local bridge or OVS switch, already |
ee6e18c4 | 168 | configured on *each* local node. |
1556b768 | 169 | |
4e652aba | 170 | [[pvesdn_zone_plugin_qinq]] |
ee6e18c4 TL |
171 | QinQ Zones |
172 | ~~~~~~~~~~ | |
1556b768 | 173 | |
ee6e18c4 TL |
174 | QinQ is stacked VLAN. The first VLAN tag defined for the zone |
175 | (so called 'service-vlan'), and the second VLAN tag defined for the vnets | |
1556b768 | 176 | |
8ac25ffe | 177 | NOTE: Your physical network switches must support stacked VLANs! |
1556b768 | 178 | |
ee6e18c4 | 179 | Specific QinQ configuration options: |
1556b768 | 180 | |
4e652aba TL |
181 | bridge:: A local VLAN-aware bridge already configured on each local node |
182 | ||
183 | service vlan:: The main VLAN tag of this zone | |
184 | ||
ee6e18c4 TL |
185 | mtu:: Due to the double stacking of tags you need 4 more bytes for QinQ VLANs. |
186 | For example, you reduce the MTU to `1496` if you physical interface MTU is | |
187 | `1500`. | |
1556b768 | 188 | |
4e652aba | 189 | [[pvesdn_zone_plugin_vxlan]] |
ee6e18c4 TL |
190 | VXLAN Zones |
191 | ~~~~~~~~~~~ | |
1556b768 | 192 | |
ee6e18c4 TL |
193 | The VXLAN plugin will establish a tunnel (named overlay) on top of an existing |
194 | network (named underlay). It encapsulate layer 2 Ethernet frames within layer | |
195 | 4 UDP datagrams, using `4789` as the default destination port. You can, for | |
196 | example, create a private IPv4 VXLAN network on top of public internet network | |
197 | nodes. | |
198 | This is a layer2 tunnel only, no routing between different VNets is possible. | |
1556b768 | 199 | |
ee6e18c4 | 200 | Each VNet will have use specific VXLAN id from the range (1 - 16777215). |
1556b768 | 201 | |
ee6e18c4 | 202 | Specific EVPN configuration options: |
1556b768 | 203 | |
4e652aba TL |
204 | peers address list:: A list of IPs from all nodes through which you want to |
205 | communicate. Can also be external nodes. | |
206 | ||
207 | mtu:: Because VXLAN encapsulation use 50bytes, the MTU need to be 50 bytes | |
208 | lower than the outgoing physical interface. | |
1556b768 | 209 | |
4e652aba | 210 | [[pvesdn_zone_plugin_evpn]] |
ee6e18c4 TL |
211 | EVPN Zones |
212 | ~~~~~~~~~~ | |
1556b768 | 213 | |
ee6e18c4 | 214 | This is the most complex of all supported plugins. |
1556b768 | 215 | |
ee6e18c4 TL |
216 | BGP-EVPN allows one to create routable layer3 network. The VNet of EVPN can |
217 | have an anycast IP-address and or MAC-address. The bridge IP is the same on each | |
218 | node, with this a virtual guest can use that address as gateway. | |
1556b768 | 219 | |
ee6e18c4 TL |
220 | Routing can work across VNets from different zones through a VRF (Virtual |
221 | Routing and Forwarding) interface. | |
1556b768 | 222 | |
ee6e18c4 | 223 | Specific EVPN configuration options: |
1556b768 | 224 | |
ee6e18c4 TL |
225 | VRF VXLAN Tag:: This is a vxlan-id used for routing interconnect between vnets, |
226 | it must be different than VXLAN-id of VNets | |
1556b768 | 227 | |
ee6e18c4 TL |
228 | controller:: an EVPN-controller need to be defined first (see controller |
229 | plugins section) | |
1556b768 | 230 | |
a6af82c7 AD |
231 | |
232 | Exit Nodes:: This is used if you want to defined some proxmox nodes, as | |
233 | exit gateway from evpn network through real network. This nodes | |
234 | will announce a default route in the evpn network. | |
235 | ||
ee6e18c4 TL |
236 | mtu:: because VXLAN encapsulation use 50bytes, the MTU need to be 50 bytes |
237 | lower than the outgoing physical interface. | |
1556b768 AD |
238 | |
239 | ||
a6af82c7 AD |
240 | [[pvesdn_config_vnet]] |
241 | VNets | |
242 | ----- | |
243 | ||
244 | A `VNet` is in its basic form just a Linux bridge that will be deployed locally | |
245 | on the node and used for Virtual Machine communication. | |
246 | ||
247 | VNet properties are: | |
248 | ||
249 | ID:: a 8 characters ID to name and identify a VNet | |
250 | ||
251 | Alias:: Optional longer name, if the ID isn't enough | |
252 | ||
253 | Zone:: The associated zone for this VNet | |
254 | ||
255 | Tag:: The unique VLAN or VXLAN id | |
256 | ||
257 | VLAN Aware:: Allow to add an extra VLAN tag in the virtual machine or | |
258 | container vNIC configurations or allow the guest OS to manage the VLAN's tag. | |
259 | ||
260 | [[pvesdn_config_subnet]] | |
261 | ||
3093e62d TL |
262 | Sub-Nets |
263 | ~~~~~~~~ | |
264 | ||
265 | A sub-network (subnet or sub-net) allows you to define a specific IP network | |
266 | (IPv4 or IPv6). For each VNET, you can define one or more subnets. | |
1556b768 | 267 | |
3093e62d | 268 | A subnet can be used to: |
a6af82c7 | 269 | |
3093e62d TL |
270 | * restrict IP-addresses you can define on a specific VNET |
271 | * assign routes/gateway on a VNET in layer 3 zones | |
272 | * enable SNAT on a VNET in layer 3 zones | |
273 | * auto assign IPs on virtual guests (VM or CT) through IPAM plugin | |
274 | * DNS registration through DNS plugins | |
a6af82c7 | 275 | |
3093e62d TL |
276 | If an IPAM server is associated to the subnet zone, the subnet prefix will be |
277 | automatically registered in the IPAM. | |
a6af82c7 AD |
278 | |
279 | ||
280 | Subnet properties are: | |
281 | ||
282 | ID:: a cidr network address. Ex: 10.0.0.0/8 | |
283 | ||
284 | Gateway:: ip address for the default gateway of the network. | |
3093e62d TL |
285 | On layer3 zones (simple/evpn plugins), it'll be deployed on the vnet. |
286 | ||
a6af82c7 | 287 | Snat:: Optional, Enable Snat for layer3 zones (simple/evpn plugins) for this subnet. |
3093e62d TL |
288 | The subnet source ip will be natted to server outgoing interface/ip. |
289 | On evpn zone, it's done only on evpn gateway-nodes. | |
a6af82c7 AD |
290 | |
291 | Dnszoneprefix:: Optional, add a prefix to domain registration, like <hostname>.prefix.<domain> | |
292 | ||
293 | ||
a6af82c7 AD |
294 | [[pvesdn_config_controllers]] |
295 | Controllers | |
296 | ----------- | |
297 | ||
298 | Some zone types need an external controller to manage the VNet control-plane. | |
299 | Currently this is only required for the `bgp-evpn` zone plugin. | |
8ac25ffe | 300 | |
4e652aba | 301 | [[pvesdn_controller_plugin_evpn]] |
ee6e18c4 TL |
302 | EVPN Controller |
303 | ~~~~~~~~~~~~~~~ | |
1556b768 | 304 | |
ee6e18c4 TL |
305 | For `BGP-EVPN`, we need a controller to manage the control plane. |
306 | The currently supported software controller is the "frr" router. | |
307 | You may need to install it on each node where you want to deploy EVPN zones. | |
1556b768 AD |
308 | |
309 | ---- | |
a6af82c7 | 310 | apt install frr frr-pythontools |
1556b768 AD |
311 | ---- |
312 | ||
ee6e18c4 | 313 | Configuration options: |
1556b768 | 314 | |
4e652aba | 315 | asn:: A unique BGP ASN number. It's highly recommended to use private ASN |
ee6e18c4 TL |
316 | number (64512 – 65534, 4200000000 – 4294967294), as else you could end up |
317 | breaking, or get broken, by global routing by mistake. | |
1556b768 | 318 | |
a6af82c7 | 319 | peers:: An ip list of all nodes where you want to communicate for the EVPN (could be also |
ee6e18c4 | 320 | external nodes or route reflectors servers) |
1556b768 | 321 | |
1556b768 | 322 | |
a6af82c7 AD |
323 | [[pvesdn_controller_plugin_BGP]] |
324 | BGP Controller | |
325 | ~~~~~~~~~~~~~~~ | |
1556b768 | 326 | |
a6af82c7 AD |
327 | The bgp controller is not used directly by a zone. |
328 | You can used it to configure frr to manage bgp peers. | |
1556b768 | 329 | |
3093e62d | 330 | For BGP-evpn, it can be use to define a different ASN by node, so doing EBGP. |
1556b768 | 331 | |
a6af82c7 | 332 | Configuration options: |
1556b768 | 333 | |
a6af82c7 | 334 | asn:: A unique BGP ASN number. It's highly recommended to use private ASN |
3093e62d TL |
335 | number from the range (64512 - 65534) or (4200000000 - 4294967294), as else |
336 | you could end up breaking, or get broken, by global routing by mistake. | |
a6af82c7 | 337 | |
3093e62d TL |
338 | peers:: An IP list of peers you want to communicate with for the underlying |
339 | BGP network. | |
a6af82c7 | 340 | |
3093e62d | 341 | ebgp:: If your peer's remote-AS is different, it's enabling EBGP. |
a6af82c7 | 342 | |
3093e62d | 343 | node:: The node of this BGP controller |
a6af82c7 | 344 | |
3093e62d TL |
345 | loopback:: If you want to use a loopback or dummy interface as source for the |
346 | evpn network. (for multipath) | |
a6af82c7 AD |
347 | |
348 | ||
349 | [[pvesdn_config_ipam]] | |
3093e62d | 350 | IPAMs |
a6af82c7 AD |
351 | ----- |
352 | IPAM (IP address management) tools, are used to manage/assign ips on your devices on the network. | |
353 | It can be used to find free ip address when you create a vm/ct for example (not yet implemented). | |
354 | ||
355 | An IPAM is associated to 1 or multiple zones, to provide ip addresses for all subnets defined in this zone. | |
356 | ||
357 | ||
358 | [[pvesdn_ipam_plugin_pveipam]] | |
3093e62d TL |
359 | {pve} IPAM plugin |
360 | ~~~~~~~~~~~~~~~~~ | |
a6af82c7 | 361 | |
3093e62d TL |
362 | This is the default internal IPAM for your proxmox cluster if you don't have |
363 | external ipam software | |
a6af82c7 AD |
364 | |
365 | [[pvesdn_ipam_plugin_phpipam]] | |
3093e62d | 366 | phpIPAM plugin |
a6af82c7 AD |
367 | ~~~~~~~~~~~~~~ |
368 | https://phpipam.net/ | |
369 | ||
3093e62d TL |
370 | You need to create an application in phpipam, and add an api token with admin |
371 | permission | |
a6af82c7 | 372 | |
3093e62d | 373 | phpIPAM properties are: |
a6af82c7 | 374 | |
3093e62d TL |
375 | url:: The REST-API endpoint: `http://phpipam.domain.com/api/<appname>/` |
376 | token:: An API access token | |
377 | section:: An integer ID. Sections are group of subnets in phpIPAM. Default | |
378 | installations use `sectionid=1` for customers. | |
a6af82c7 AD |
379 | |
380 | [[pvesdn_ipam_plugin_netbox]] | |
3093e62d | 381 | Netbox IPAM plugin |
a6af82c7 | 382 | ~~~~~~~~~~~~~~~~~~ |
3093e62d TL |
383 | |
384 | NetBox is an IP address management (IPAM) and data center infrastructure | |
385 | management (DCIM) tool, see the source code repository for details: | |
a6af82c7 AD |
386 | https://github.com/netbox-community/netbox |
387 | ||
3093e62d | 388 | You need to create an api token in netbox |
a6af82c7 AD |
389 | https://netbox.readthedocs.io/en/stable/api/authentication |
390 | ||
3093e62d | 391 | NetBox properties are: |
a6af82c7 | 392 | |
3093e62d TL |
393 | url:: The REST API endpoint: `http://yournetbox.domain.com/api` |
394 | token:: An API access token | |
a6af82c7 AD |
395 | |
396 | [[pvesdn_config_dns]] | |
3093e62d | 397 | DNS |
a6af82c7 | 398 | --- |
3093e62d TL |
399 | |
400 | The DNS plugin in {pve} SDN is used to define a DNS API server for registration | |
401 | of your hostname and IP-address. A DNS configuration is associated with one or | |
402 | more zones, to provide DNS registration for all the sub-net IPs configured for | |
403 | a zone. | |
a6af82c7 AD |
404 | |
405 | [[pvesdn_dns_plugin_powerdns]] | |
3093e62d | 406 | PowerDNS plugin |
a6af82c7 AD |
407 | ~~~~~~~~~~~~~~~ |
408 | https://doc.powerdns.com/authoritative/http-api/index.html | |
409 | ||
3093e62d | 410 | You need to enable the webserver and the API in your PowerDNS config: |
1556b768 | 411 | |
40f4dfc2 | 412 | ---- |
a6af82c7 AD |
413 | api=yes |
414 | api-key=arandomgeneratedstring | |
415 | webserver=yes | |
416 | webserver-port=8081 | |
40f4dfc2 | 417 | ---- |
40f4dfc2 | 418 | |
a6af82c7 AD |
419 | Powerdns properties are: |
420 | ||
3093e62d TL |
421 | url:: The REST API endpoint: http://yourpowerdnserver.domain.com:8081/api/v1/servers/localhost |
422 | key:: An API access key | |
423 | ttl:: The default TTL for records | |
1556b768 | 424 | |
1556b768 | 425 | |
a6af82c7 AD |
426 | Examples |
427 | -------- | |
428 | ||
4e652aba | 429 | [[pvesdn_setup_example_vlan]] |
ee6e18c4 | 430 | VLAN Setup Example |
a6af82c7 | 431 | ~~~~~~~~~~~~~~~~~~ |
1556b768 | 432 | |
ee6e18c4 TL |
433 | TIP: While we show plain configuration content here, almost everything should |
434 | be configurable using the web-interface only. | |
435 | ||
436 | Node1: /etc/network/interfaces | |
1556b768 | 437 | |
1556b768 AD |
438 | ---- |
439 | auto vmbr0 | |
440 | iface vmbr0 inet manual | |
ee6e18c4 TL |
441 | bridge-ports eno1 |
442 | bridge-stp off | |
443 | bridge-fd 0 | |
1556b768 AD |
444 | bridge-vlan-aware yes |
445 | bridge-vids 2-4094 | |
446 | ||
447 | #management ip on vlan100 | |
448 | auto vmbr0.100 | |
449 | iface vmbr0.100 inet static | |
450 | address 192.168.0.1/24 | |
451 | ||
452 | source /etc/network/interfaces.d/* | |
1556b768 AD |
453 | ---- |
454 | ||
ee6e18c4 | 455 | Node2: /etc/network/interfaces |
1556b768 AD |
456 | |
457 | ---- | |
458 | auto vmbr0 | |
459 | iface vmbr0 inet manual | |
ee6e18c4 TL |
460 | bridge-ports eno1 |
461 | bridge-stp off | |
462 | bridge-fd 0 | |
1556b768 AD |
463 | bridge-vlan-aware yes |
464 | bridge-vids 2-4094 | |
465 | ||
466 | #management ip on vlan100 | |
467 | auto vmbr0.100 | |
468 | iface vmbr0.100 inet static | |
469 | address 192.168.0.2/24 | |
470 | ||
471 | source /etc/network/interfaces.d/* | |
472 | ---- | |
473 | ||
ee6e18c4 | 474 | Create a VLAN zone named `myvlanzone': |
1556b768 AD |
475 | |
476 | ---- | |
ee6e18c4 | 477 | id: myvlanzone |
1556b768 AD |
478 | bridge: vmbr0 |
479 | ---- | |
480 | ||
ee6e18c4 TL |
481 | Create a VNet named `myvnet1' with `vlan-id` `10' and the previously created |
482 | `myvlanzone' as it's zone. | |
1556b768 AD |
483 | |
484 | ---- | |
485 | id: myvnet1 | |
486 | zone: myvlanzone | |
487 | tag: 10 | |
488 | ---- | |
489 | ||
ee6e18c4 TL |
490 | Apply the configuration through the main SDN panel, to create VNets locally on |
491 | each nodes. | |
1556b768 | 492 | |
ee6e18c4 | 493 | Create a Debian-based Virtual Machine (vm1) on node1, with a vNIC on `myvnet1'. |
1556b768 | 494 | |
ee6e18c4 | 495 | Use the following network configuration for this VM: |
1556b768 AD |
496 | |
497 | ---- | |
498 | auto eth0 | |
499 | iface eth0 inet static | |
ee6e18c4 | 500 | address 10.0.3.100/24 |
1556b768 AD |
501 | ---- |
502 | ||
ee6e18c4 TL |
503 | Create a second Virtual Machine (vm2) on node2, with a vNIC on the same VNet |
504 | `myvnet1' as vm1. | |
505 | ||
506 | Use the following network configuration for this VM: | |
507 | ||
1556b768 AD |
508 | ---- |
509 | auto eth0 | |
510 | iface eth0 inet static | |
ee6e18c4 | 511 | address 10.0.3.101/24 |
1556b768 AD |
512 | ---- |
513 | ||
ee6e18c4 | 514 | Then, you should be able to ping between both VMs over that network. |
1556b768 AD |
515 | |
516 | ||
4e652aba TL |
517 | [[pvesdn_setup_example_qinq]] |
518 | QinQ Setup Example | |
a6af82c7 | 519 | ~~~~~~~~~~~~~~~~~~ |
ee6e18c4 TL |
520 | |
521 | TIP: While we show plain configuration content here, almost everything should | |
522 | be configurable using the web-interface only. | |
523 | ||
524 | Node1: /etc/network/interfaces | |
525 | ||
1556b768 AD |
526 | ---- |
527 | auto vmbr0 | |
528 | iface vmbr0 inet manual | |
ee6e18c4 TL |
529 | bridge-ports eno1 |
530 | bridge-stp off | |
531 | bridge-fd 0 | |
1556b768 AD |
532 | bridge-vlan-aware yes |
533 | bridge-vids 2-4094 | |
534 | ||
535 | #management ip on vlan100 | |
536 | auto vmbr0.100 | |
537 | iface vmbr0.100 inet static | |
538 | address 192.168.0.1/24 | |
539 | ||
540 | source /etc/network/interfaces.d/* | |
541 | ---- | |
542 | ||
ee6e18c4 | 543 | Node2: /etc/network/interfaces |
1556b768 AD |
544 | |
545 | ---- | |
546 | auto vmbr0 | |
547 | iface vmbr0 inet manual | |
ee6e18c4 TL |
548 | bridge-ports eno1 |
549 | bridge-stp off | |
550 | bridge-fd 0 | |
1556b768 AD |
551 | bridge-vlan-aware yes |
552 | bridge-vids 2-4094 | |
553 | ||
554 | #management ip on vlan100 | |
555 | auto vmbr0.100 | |
556 | iface vmbr0.100 inet static | |
557 | address 192.168.0.2/24 | |
558 | ||
559 | source /etc/network/interfaces.d/* | |
560 | ---- | |
561 | ||
ee6e18c4 | 562 | Create an QinQ zone named `qinqzone1' with service VLAN 20 |
1556b768 AD |
563 | |
564 | ---- | |
565 | id: qinqzone1 | |
566 | bridge: vmbr0 | |
567 | service vlan: 20 | |
568 | ---- | |
569 | ||
ee6e18c4 | 570 | Create another QinQ zone named `qinqzone2' with service VLAN 30 |
1556b768 AD |
571 | |
572 | ---- | |
573 | id: qinqzone2 | |
574 | bridge: vmbr0 | |
575 | service vlan: 30 | |
576 | ---- | |
577 | ||
ee6e18c4 TL |
578 | Create a VNet named `myvnet1' with customer vlan-id 100 on the previously |
579 | created `qinqzone1' zone. | |
1556b768 AD |
580 | |
581 | ---- | |
582 | id: myvnet1 | |
583 | zone: qinqzone1 | |
584 | tag: 100 | |
585 | ---- | |
586 | ||
ee6e18c4 TL |
587 | Create a `myvnet2' with customer VLAN-id 100 on the previously created |
588 | `qinqzone2' zone. | |
1556b768 AD |
589 | |
590 | ---- | |
591 | id: myvnet2 | |
99a0bbe4 | 592 | zone: qinqzone2 |
1556b768 AD |
593 | tag: 100 |
594 | ---- | |
595 | ||
ee6e18c4 TL |
596 | Apply the configuration on the main SDN web-interface panel to create VNets |
597 | locally on each nodes. | |
1556b768 | 598 | |
ee6e18c4 | 599 | Create a Debian-based Virtual Machine (vm1) on node1, with a vNIC on `myvnet1'. |
1556b768 | 600 | |
ee6e18c4 | 601 | Use the following network configuration for this VM: |
1556b768 AD |
602 | |
603 | ---- | |
604 | auto eth0 | |
605 | iface eth0 inet static | |
606 | address 10.0.3.100/24 | |
607 | ---- | |
608 | ||
ee6e18c4 TL |
609 | Create a second Virtual Machine (vm2) on node2, with a vNIC on the same VNet |
610 | `myvnet1' as vm1. | |
611 | ||
612 | Use the following network configuration for this VM: | |
613 | ||
1556b768 AD |
614 | ---- |
615 | auto eth0 | |
616 | iface eth0 inet static | |
617 | address 10.0.3.101/24 | |
618 | ---- | |
619 | ||
ee6e18c4 TL |
620 | Create a third Virtual Machine (vm3) on node1, with a vNIC on the other VNet |
621 | `myvnet2'. | |
622 | ||
623 | Use the following network configuration for this VM: | |
1556b768 AD |
624 | |
625 | ---- | |
626 | auto eth0 | |
627 | iface eth0 inet static | |
628 | address 10.0.3.102/24 | |
629 | ---- | |
630 | ||
ee6e18c4 TL |
631 | Create another Virtual Machine (vm4) on node2, with a vNIC on the same VNet |
632 | `myvnet2' as vm3. | |
633 | ||
634 | Use the following network configuration for this VM: | |
635 | ||
1556b768 AD |
636 | ---- |
637 | auto eth0 | |
638 | iface eth0 inet static | |
639 | address 10.0.3.103/24 | |
640 | ---- | |
641 | ||
ee6e18c4 TL |
642 | Then, you should be able to ping between the VMs 'vm1' and 'vm2', also |
643 | between 'vm3' and 'vm4'. But, none of VMs 'vm1' or 'vm2' can ping the VMs 'vm3' | |
644 | or 'vm4', as they are on a different zone with different service-vlan. | |
1556b768 | 645 | |
1556b768 | 646 | |
4e652aba | 647 | [[pvesdn_setup_example_vxlan]] |
ee6e18c4 | 648 | VXLAN Setup Example |
a6af82c7 | 649 | ~~~~~~~~~~~~~~~~~~~ |
ee6e18c4 | 650 | |
4e652aba TL |
651 | TIP: While we show plain configuration content here, almost everything should |
652 | be configurable using the web-interface only. | |
653 | ||
1556b768 | 654 | node1: /etc/network/interfaces |
ee6e18c4 | 655 | |
1556b768 AD |
656 | ---- |
657 | auto vmbr0 | |
658 | iface vmbr0 inet static | |
659 | address 192.168.0.1/24 | |
660 | gateway 192.168.0.254 | |
ee6e18c4 TL |
661 | bridge-ports eno1 |
662 | bridge-stp off | |
663 | bridge-fd 0 | |
1556b768 AD |
664 | mtu 1500 |
665 | ||
666 | source /etc/network/interfaces.d/* | |
667 | ---- | |
668 | ||
669 | node2: /etc/network/interfaces | |
670 | ||
671 | ---- | |
672 | auto vmbr0 | |
673 | iface vmbr0 inet static | |
674 | address 192.168.0.2/24 | |
675 | gateway 192.168.0.254 | |
ee6e18c4 TL |
676 | bridge-ports eno1 |
677 | bridge-stp off | |
678 | bridge-fd 0 | |
1556b768 AD |
679 | mtu 1500 |
680 | ||
681 | source /etc/network/interfaces.d/* | |
682 | ---- | |
683 | ||
684 | node3: /etc/network/interfaces | |
685 | ||
686 | ---- | |
687 | auto vmbr0 | |
688 | iface vmbr0 inet static | |
689 | address 192.168.0.3/24 | |
690 | gateway 192.168.0.254 | |
ee6e18c4 TL |
691 | bridge-ports eno1 |
692 | bridge-stp off | |
693 | bridge-fd 0 | |
1556b768 AD |
694 | mtu 1500 |
695 | ||
696 | source /etc/network/interfaces.d/* | |
697 | ---- | |
698 | ||
ee6e18c4 TL |
699 | Create an VXLAN zone named `myvxlanzone', use the lower MTU to ensure the extra |
700 | 50 bytes of the VXLAN header can fit. Add all previously configured IPs from | |
701 | the nodes as peer address list. | |
1556b768 AD |
702 | |
703 | ---- | |
704 | id: myvxlanzone | |
705 | peers address list: 192.168.0.1,192.168.0.2,192.168.0.3 | |
706 | mtu: 1450 | |
707 | ---- | |
708 | ||
ee6e18c4 TL |
709 | Create a VNet named `myvnet1' using the VXLAN zone `myvxlanzone' created |
710 | previously. | |
1556b768 AD |
711 | |
712 | ---- | |
713 | id: myvnet1 | |
714 | zone: myvxlanzone | |
715 | tag: 100000 | |
716 | ---- | |
717 | ||
ee6e18c4 TL |
718 | Apply the configuration on the main SDN web-interface panel to create VNets |
719 | locally on each nodes. | |
1556b768 | 720 | |
ee6e18c4 | 721 | Create a Debian-based Virtual Machine (vm1) on node1, with a vNIC on `myvnet1'. |
1556b768 | 722 | |
ee6e18c4 | 723 | Use the following network configuration for this VM, note the lower MTU here. |
1556b768 AD |
724 | |
725 | ---- | |
726 | auto eth0 | |
727 | iface eth0 inet static | |
728 | address 10.0.3.100/24 | |
729 | mtu 1450 | |
730 | ---- | |
731 | ||
ee6e18c4 TL |
732 | Create a second Virtual Machine (vm2) on node3, with a vNIC on the same VNet |
733 | `myvnet1' as vm1. | |
734 | ||
735 | Use the following network configuration for this VM: | |
736 | ||
1556b768 AD |
737 | ---- |
738 | auto eth0 | |
739 | iface eth0 inet static | |
740 | address 10.0.3.101/24 | |
741 | mtu 1450 | |
742 | ---- | |
743 | ||
ee6e18c4 | 744 | Then, you should be able to ping between between 'vm1' and 'vm2'. |
1556b768 AD |
745 | |
746 | ||
4e652aba TL |
747 | [[pvesdn_setup_example_evpn]] |
748 | EVPN Setup Example | |
a6af82c7 | 749 | ~~~~~~~~~~~~~~~~~~ |
ee6e18c4 | 750 | |
1556b768 AD |
751 | node1: /etc/network/interfaces |
752 | ||
753 | ---- | |
754 | auto vmbr0 | |
755 | iface vmbr0 inet static | |
756 | address 192.168.0.1/24 | |
757 | gateway 192.168.0.254 | |
758 | bridge-ports eno1 | |
759 | bridge-stp off | |
760 | bridge-fd 0 | |
761 | mtu 1500 | |
762 | ||
763 | source /etc/network/interfaces.d/* | |
764 | ---- | |
765 | ||
766 | node2: /etc/network/interfaces | |
767 | ||
768 | ---- | |
769 | auto vmbr0 | |
770 | iface vmbr0 inet static | |
771 | address 192.168.0.2/24 | |
772 | gateway 192.168.0.254 | |
773 | bridge-ports eno1 | |
774 | bridge-stp off | |
775 | bridge-fd 0 | |
776 | mtu 1500 | |
777 | ||
778 | source /etc/network/interfaces.d/* | |
779 | ---- | |
780 | ||
781 | node3: /etc/network/interfaces | |
782 | ||
783 | ---- | |
784 | auto vmbr0 | |
785 | iface vmbr0 inet static | |
786 | address 192.168.0.3/24 | |
787 | gateway 192.168.0.254 | |
788 | bridge-ports eno1 | |
789 | bridge-stp off | |
790 | bridge-fd 0 | |
791 | mtu 1500 | |
792 | ||
793 | source /etc/network/interfaces.d/* | |
794 | ---- | |
795 | ||
ee6e18c4 | 796 | Create a EVPN controller, using a private ASN number and above node addreesses |
a6af82c7 | 797 | as peers. |
1556b768 AD |
798 | |
799 | ---- | |
800 | id: myevpnctl | |
801 | asn: 65000 | |
802 | peers: 192.168.0.1,192.168.0.2,192.168.0.3 | |
1556b768 AD |
803 | ---- |
804 | ||
ee6e18c4 | 805 | Create an EVPN zone named `myevpnzone' using the previously created |
a6af82c7 AD |
806 | EVPN-controller Define 'node1' and 'node2' as exit nodes. |
807 | ||
1556b768 AD |
808 | |
809 | ---- | |
810 | id: myevpnzone | |
811 | vrf vxlan tag: 10000 | |
812 | controller: myevpnctl | |
813 | mtu: 1450 | |
a6af82c7 | 814 | exitnodes: node1,node2 |
1556b768 AD |
815 | ---- |
816 | ||
a6af82c7 | 817 | Create the first VNet named `myvnet1' using the EVPN zone `myevpnzone'. |
1556b768 AD |
818 | ---- |
819 | id: myvnet1 | |
820 | zone: myevpnzone | |
821 | tag: 11000 | |
8ac25ffe | 822 | mac address: 8C:73:B2:7B:F9:60 #random generate mac address |
1556b768 AD |
823 | ---- |
824 | ||
a6af82c7 AD |
825 | Create a subnet 10.0.1.0/24 with 10.0.1.1 as gateway |
826 | ---- | |
827 | id: 10.0.1.0/24 | |
828 | gateway: 10.0.1.1 | |
829 | ---- | |
830 | ||
ee6e18c4 TL |
831 | Create the second VNet named `myvnet2' using the same EVPN zone `myevpnzone', a |
832 | different IPv4 CIDR network and a different random MAC address than `myvnet1'. | |
1556b768 AD |
833 | |
834 | ---- | |
835 | id: myvnet2 | |
836 | zone: myevpnzone | |
837 | tag: 12000 | |
1556b768 AD |
838 | mac address: 8C:73:B2:7B:F9:61 #random mac, need to be different on each vnet |
839 | ---- | |
840 | ||
a6af82c7 AD |
841 | Create a different subnet 10.0.2.0/24 with 10.0.2.1 as gateway |
842 | ---- | |
843 | id: 10.0.2.0/24 | |
844 | gateway: 10.0.2.1 | |
845 | ---- | |
846 | ||
847 | ||
ee6e18c4 TL |
848 | Apply the configuration on the main SDN web-interface panel to create VNets |
849 | locally on each nodes and generate the FRR config. | |
1556b768 AD |
850 | |
851 | ||
ee6e18c4 | 852 | Create a Debian-based Virtual Machine (vm1) on node1, with a vNIC on `myvnet1'. |
1556b768 | 853 | |
ee6e18c4 | 854 | Use the following network configuration for this VM: |
1556b768 AD |
855 | |
856 | ---- | |
857 | auto eth0 | |
858 | iface eth0 inet static | |
859 | address 10.0.1.100/24 | |
860 | gateway 10.0.1.1 #this is the ip of the vnet1 | |
861 | mtu 1450 | |
862 | ---- | |
863 | ||
ee6e18c4 TL |
864 | Create a second Virtual Machine (vm2) on node2, with a vNIC on the other VNet |
865 | `myvnet2'. | |
866 | ||
867 | Use the following network configuration for this VM: | |
868 | ||
1556b768 AD |
869 | ---- |
870 | auto eth0 | |
871 | iface eth0 inet static | |
872 | address 10.0.2.100/24 | |
873 | gateway 10.0.2.1 #this is the ip of the vnet2 | |
874 | mtu 1450 | |
875 | ---- | |
876 | ||
877 | ||
878 | Then, you should be able to ping vm2 from vm1, and vm1 from vm2. | |
879 | ||
ee6e18c4 | 880 | If you ping an external IP from 'vm2' on the non-gateway 'node3', the packet |
a6af82c7 | 881 | will go to the configured 'myvnet2' gateway, then will be routed to the exit |
ee6e18c4 TL |
882 | nodes ('node1' or 'node2') and from there it will leave those nodes over the |
883 | default gateway configured on node1 or node2. | |
1556b768 | 884 | |
ee6e18c4 TL |
885 | NOTE: Of course you need to add reverse routes for the '10.0.1.0/24' and |
886 | '10.0.2.0/24' network to node1, node2 on your external gateway, so that the | |
887 | public network can reply back. | |
1556b768 | 888 | |
ee6e18c4 TL |
889 | If you have configured an external BGP router, the BGP-EVPN routes (10.0.1.0/24 |
890 | and 10.0.2.0/24 in this example), will be announced dynamically. |