Changes

Page history
Update Lab01 authored by Katharina Renk's avatar Katharina Renk
Show whitespace changes
Inline Side-by-side
Labs/Lab01.md
View page @ 1c1ede25
...@@ -88,42 +88,37 @@ In here, the UUID is also visible which we need for the next step:![Lab00_mne_li ...@@ -88,42 +88,37 @@ In here, the UUID is also visible which we need for the next step:![Lab00_mne_li
**Please note that the UUID may vary.** **Please note that the UUID may vary.**
## Configuration of the switches(the UUID have to be changed according to the output from the devices) ## Configuration of the switches
### Switch 0 ### Switch 0
```bash #### Modify interface eth1
mne set 401982c5-fb98-4402-b98f-1b6d30915fc4 network-instances/network-instance[name=default]/config --file ./lab00/enable-routing.json --force-push
mne set 401982c5-fb98-4402-b98f-1b6d30915fc4 interfaces/interface[name=Ethernet1] --file ./lab00/s01-ethernet01.json --force-push
mne set 401982c5-fb98-4402-b98f-1b6d30915fc4 interfaces/interface[name=Ethernet2] --file ./lab00/s01-ethernet02.json --force-push
mne set 401982c5-fb98-4402-b98f-1b6d30915fc4 network-instances/network-instance[name=default]/protocols --file ./lab00/s01-route.json --force-push
mne set 401982c5-fb98-4402-b98f-1b6d30915fc4 network-instances/network-instance[name=default]/tables --file ./lab00/tables.json --force-push
```
### Modify interface eth1
```bash ```bash
mne path set <UUID of Switch0> interfaces/interface[name=Ethernet1] --file ./lab00/s01-ethernet01.json --force-push mne path set <UUID of Switch0> interfaces/interface[name=Ethernet1] --file ./lab00/s01-ethernet01.json --force-push
``` ```
### Modify interface eth2 #### Modify interface eth2
```bash ```bash
mne path set <UUID of Switch0> interfaces/interface[name=Ethernet2] --file ./lab00/s01-ethernet02.json --force-push mne path set <UUID of Switch0> interfaces/interface[name=Ethernet2] --file ./lab00/s01-ethernet02.json --force-push
``` ```
### Insert the routes #### Insert the routes
```bash ```bash
mne path set <UUID of Switch0> network-instances/network-instance[name=default]/protocols --file ./lab00/s01-route.json --force-push mne path set <UUID of Switch0> network-instances/network-instance[name=default]/protocols --file ./lab00/s01-route.json --force-push
``` ```
### Switch 1 ### Switch 1
### Modify interface eth1
```bash ```bash
mne set c724b95b-c751-4728-9f19-376e0d570104 network-instances/network-instance[name=default]/config --file ./lab00/enable-routing.json --force-push mne path set <UUID of Switch1> interfaces/interface[name=Ethernet1] --file ./lab00/s01-ethernet01.json --force-push
mne set c724b95b-c751-4728-9f19-376e0d570104 interfaces/interface[name=Ethernet1] --file ./lab00/s02-ethernet01.json --force-push ```
mne set c724b95b-c751-4728-9f19-376e0d570104 interfaces/interface[name=Ethernet2] --file ./lab00/s02-ethernet02.json --force-push ### Modify interface eth2
mne set c724b95b-c751-4728-9f19-376e0d570104 network-instances/network-instance[name=default]/protocols --file ./lab00/s02-route.json --force-push ```bash
mne set c724b95b-c751-4728-9f19-376e0d570104 network-instances/network-instance[name=default]/tables --file ./lab00/tables.json --force-push mne path set <UUID of Switch1> interfaces/interface[name=Ethernet2] --file ./lab00/s01-ethernet02.json --force-push
```
### Insert the routes
```bash
mne path set <UUID of Switch1> network-instances/network-instance[name=default]/protocols --file ./lab00/s01-route.json --force-push
``` ```
If you've cloned the goSDN repo from [here](https://code.fbi.h-da.de/danet/gosdn) and have all the requirements, then you can start the containerlab topology (which is defined below) using the command `make containerlab-start` from within the root of the repository
## CLI and the controller ## CLI and the controller
... ...
......