forked from ipspace/netlab-examples
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
89 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# VXLAN Bridging with OSPF | ||
|
||
This directory demonstrates what might happen when you run OSPF on VXLAN-enabled VLAN interfaces. | ||
|
||
![Lab topology](vxlan-ospf.png) | ||
|
||
The directory contains two topologies: | ||
|
||
* `topology-broken.yml` runs the same OSPF instance on physical interfaces and VLAN interfaces, resulting in recursive routing | ||
* `topology-fixed.yml` isolates tenant routing in a VRF resulting in a working network even when S1 and S2 run OSPF across a VXLAN-enabled VLAN | ||
|
||
## Changing Device Types | ||
|
||
This topology can be used with all network devices supporting VLAN, VXLAN, and OSPF configuration modules, and all virtualization providers supported by *netlab*: | ||
|
||
* To change the switch device type, use `-s groups.switch.device=xxx` CLI argument | ||
* To change the virtualization provider, use `-p` CLI argument. | ||
|
||
For example, to start the lab with Nexus 9300v switches using _libvirt_, use: | ||
|
||
``` | ||
netlab up -p libvirt -s groups.switches.device=nxos | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
--- | ||
message: | | ||
This topology demonstrates what happens when you run OSPF on | ||
"all interfaces" in a VXLAN IRB environment. | ||
provider: clab | ||
|
||
vlans: | ||
red: | ||
|
||
groups: | ||
switch: | ||
members: [ s1, s2 ] | ||
module: [ vxlan, vlan, ospf ] | ||
device: eos | ||
host: | ||
members: [ h1, h2 ] | ||
device: linux | ||
|
||
nodes: [ s1, s2, h1, h2 ] | ||
|
||
links: | ||
- h1: | ||
s1: | ||
vlan.access: red | ||
- h2: | ||
s2: | ||
vlan.access: red | ||
- s1: | ||
s2: | ||
ospf.cost: 2000 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
--- | ||
message: | | ||
This topology demonstrates how to segregate tenant routing from transport | ||
(underlay) routing in a VXLAN IRB environment. | ||
provider: clab | ||
|
||
vrfs: | ||
tenant: | ||
|
||
vlans: | ||
red: | ||
vrf: tenant | ||
|
||
groups: | ||
switch: | ||
members: [ s1, s2 ] | ||
module: [ vxlan, vlan, ospf, vrf ] | ||
device: eos | ||
host: | ||
members: [ h1, h2 ] | ||
device: linux | ||
|
||
nodes: [ s1, s2, h1, h2 ] | ||
|
||
links: | ||
- h1: | ||
s1: | ||
vlan.access: red | ||
- h2: | ||
s2: | ||
vlan.access: red | ||
- s1: | ||
s2: | ||
ospf.cost: 2000 |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.