lab01-basic-CLOS
Task
1. Build a CLOS topology based on the provided diagram.
2. Allocate IP address space for the underlay network.
3. Document the implementation plan, including:
◦ Addressing scheme
◦ Network diagram
◦ Configuration details (if applied to physical devices)
Network diagram
The lab is built using the following role-based device mapping host- linux, leaf - frr, spine - arista
Underlay IP Address Allocation
• Underlay addressing follows the format 10.x.y.z, where:
◦ x = Data Center ID
◦ y = Spine switch ID
◦ z = Sequential host address per leaf connection
• Host addressing uses the 172.16.x.z/24 format, where:
◦ x = Leaf switch ID
◦ z = Sequential host address
◦ Each leaf switch uses .1 as its own IP in the corresponding subnet
• Loopback addressing uses 192.168.a.b/32, where:
◦ a = 1 for spine switches
◦ a = 2 for leaf switches
◦ b = Spine or leaf ID (assigned sequentially)
Interconnect table
Spine-1
Eth1
10.1.1.1/30
Leaf-1
Eth8
10.1.1.2/30
Spine-1
Eth2
10.1.1.5/30
Leaf-2
Eth8
10.1.1.6/30
Spine-1
Eth3
10.1.1.9/30
Leaf-3
Eth8
10.1.1.10/30
Spine-2
Eth2
10.1.2.1/30
Leaf-1
Eth9
10.1.2.2/30
Spine-2
Eth2
10.1.2.5/30
Leaf-2
Eth9
10.1.2.6/30
Spine-2
Eth3
10.1.2.9/30
Leaf-3
Eth9
10.1.2.10/30
Host-1
Eth1
172.16.1.2/24
Leaf-1
Eth1
172.16.1.1/24
Host-2
Eth1
172.16.2.2/24
Leaf-2
Eth1
172.16.2.1/24
Host-3
Eth1
172.16.3.2/24
Leaf-3
Eth1
172.16.3.1/24
Host-4
Eth1
172.16.4.2/24
Leaf-3
Eth2
172.16.4.1/24
loopback table
Spine-1
192.168.1.1
Spine-2
192.168.1.2
Leaf-1
192.168.2.1
Leaf-2
192.168.2.2
Leaf-3
192.168.2.2
Notes
Once the overlay is deployed, we’ll place all hosts into a single subnet to emulate Layer 2 connectivity.
Launching a lab in the Netlab
Since a samurai has only the path — we do everything in netlab-tools
File Topology For quick reference, here’s the inline listing:
Validating
Pinging hosts or leaf switches from each other is pointless at this stage, since there are no routing entries on the devices.
Last updated