Complete Lab Fixes - L2 and L3 VXLAN Fully Operational #14

Merged

Damien merged 87 commits from fix-bgp-and-mlag into main 2025-11-30 10:24:29 +00:00

Conversation 0 Commits 87 Files Changed 23 +2632 -74

Damien commented 2025-11-30 10:07:01 +00:00

Owner

Copy Link

Summary

This PR merges all fixes and improvements from the troubleshooting journey to make the Arista EVPN-VXLAN lab fully operational with both L2 and L3 VXLAN connectivity.

What's Changed

🎯 Major Achievements

• ✅ L2 VXLAN fully operational - host1 ↔ host3 connectivity verified
• ✅ L3 VXLAN fully operational - host2 ↔ host4 connectivity verified (VRF gold)
• ✅ LACP bonding working - dual-homed hosts with proper Port-Channel negotiation
• ✅ All BGP/EVPN sessions established - complete underlay and overlay working

🔧 Infrastructure Fixes

BGP & Routing

• Added ip routing command to all spine and leaf switches
• Fixed duplicate BGP network statements on leaf3, leaf4, leaf7, leaf8
• Activated EVPN neighbors on spine switches
• Added loopback network advertisements to BGP

MLAG Configuration

• Configured MLAG peer-link in trunk mode (not access) for VLAN 4090/4091
• Added dual-active detection via management interface
• Configured virtual router MAC for MLAG pairs

Switch Port Configuration

• Port-Channel1 configured in trunk mode on all leaf switches
• Added switchport trunk allowed vlan for host VLANs (34, 40, 78)
• Removed no shutdown from Port-Channel interfaces

🖥️ Host Networking - Complete Redesign

Image Change

• Old: alpine:latest (had bonding syntax issues)
• New: ghcr.io/hellt/network-multitool (networking tools pre-installed)

LACP Bonding Configuration

Proper LACP setup following network-multitool best practices:

- ip link add bond0 type bond mode 802.3ad
- ip link set dev bond0 type bond xmit_hash_policy layer3+4
- ip link set dev eth1 down
- ip link set dev eth2 down
- ip link set eth1 master bond0
- ip link set eth2 master bond0
- ip link set dev eth1 up
- ip link set dev eth2 up
- ip link set dev bond0 type bond lacp_rate fast
- ip link set dev bond0 up

VLAN Configuration

• L2 VXLAN hosts (host1, host3): VLAN 40 tagged on bond0
• L3 VXLAN hosts (host2, host4): VLANs 34 and 78 tagged on bond0

Routing Strategy

• Kept management default route (172.16.0.254 via eth0)
• Added specific routes for L3 VXLAN networks instead of default routes:
  • host2: ip route add 10.78.78.0/24 via 10.34.34.1
  • host4: ip route add 10.34.34.0/24 via 10.78.78.1

📁 Files Changed

Switch Configurations (Updated)

• configs/spine1.cfg - Added ip routing, EVPN activation
• configs/spine2.cfg - Added ip routing, EVPN activation
• configs/leaf1.cfg - Port-Channel trunk mode, VLAN config
• configs/leaf2.cfg - Port-Channel trunk mode, VLAN config
• configs/leaf3.cfg - Added ip routing, loopback ads, Port-Channel config
• configs/leaf4.cfg - Added ip routing, loopback ads, Port-Channel config
• configs/leaf5.cfg - Port-Channel trunk mode, VLAN config
• configs/leaf6.cfg - Port-Channel trunk mode, VLAN config
• configs/leaf7.cfg - Added ip routing, loopback ads, Port-Channel config
• configs/leaf8.cfg - Added ip routing, loopback ads, Port-Channel config

Topology (Updated)

• evpn-lab.clab.yml - Updated all host configurations with network-multitool image and proper LACP/VLAN setup

Documentation (New)

• hosts/README.md - Host interface configuration guide
• hosts/host1_interfaces - Interface file for host1 (not currently used, kept for reference)
• hosts/host2_interfaces - Interface file for host2 (not currently used, kept for reference)
• hosts/host3_interfaces - Interface file for host3 (not currently used, kept for reference)
• hosts/host4_interfaces - Interface file for host4 (not currently used, kept for reference)

Testing & Verification

✅ L2 VXLAN (VLAN 40)

host1 (10.40.40.101) → host3 (10.40.40.103)
- Connectivity: VERIFIED ✓
- VXLAN tunnel: VTEP1 ↔ VTEP3
- MAC learning: Working via EVPN Type-2

✅ L3 VXLAN (VRF gold)

host2 (10.34.34.102) → host4 (10.78.78.104)
- Connectivity: VERIFIED ✓
- Ping results: 0% packet loss, TTL=62
- Routing: Via EVPN Type-5 through fabric

✅ Infrastructure Status

• BGP Underlay: All sessions ESTAB
• EVPN Overlay: All neighbors ESTAB
• MLAG: All 4 pairs operational
• Port-Channels: LACP negotiated on all hosts

Related Issues

Fixes #1 - Lab deployment and configuration fixes
Fixes #2 - BGP EVPN neighbors stuck in Connect state
Fixes #3 - Ready for deployment with EVPN activation
Fixes #4 - Lab convergence in progress
Fixes #5 - BGP EVPN neighbors stuck in Active state
Fixes #11 - Host LACP bonding configuration
Fixes #13 - L3 VXLAN default route issue

Key Technical Learnings

1. Arista EOS requires explicit ip routing before BGP can function
2. MLAG peer-link must be trunk mode to allow VLAN 4090/4091 traversal
3. VLAN tagging location matters - hosts tag, switches use trunk mode
4. network-multitool image superior to Alpine for LACP bonding
5. Specific routes better than default routes when management network present
6. LACP rate fast ensures quick negotiation with Arista switches

Deployment

After merging, deploy with:

cd ~/arista-evpn-vxlan-clab
sudo containerlab destroy -t evpn-lab.clab.yml --cleanup
sudo containerlab deploy -t evpn-lab.clab.yml

No manual post-deployment configuration needed - everything works from initial deployment!

Breaking Changes

⚠️ Host image changed from alpine:latest to ghcr.io/hellt/network-multitool
⚠️ Host configuration completely redesigned - old exec commands replaced

Reviewers

@Damien - Please review and merge when ready

---

This PR represents the complete troubleshooting journey and brings the lab to production-ready status with full L2 and L3 VXLAN functionality. 🚀

## Summary This PR merges all fixes and improvements from the troubleshooting journey to make the Arista EVPN-VXLAN lab fully operational with both L2 and L3 VXLAN connectivity. ## What's Changed ### 🎯 Major Achievements - ✅ **L2 VXLAN fully operational** - host1 ↔ host3 connectivity verified - ✅ **L3 VXLAN fully operational** - host2 ↔ host4 connectivity verified (VRF gold) - ✅ **LACP bonding working** - dual-homed hosts with proper Port-Channel negotiation - ✅ **All BGP/EVPN sessions established** - complete underlay and overlay working ### 🔧 Infrastructure Fixes #### BGP & Routing - Added `ip routing` command to all spine and leaf switches - Fixed duplicate BGP network statements on leaf3, leaf4, leaf7, leaf8 - Activated EVPN neighbors on spine switches - Added loopback network advertisements to BGP #### MLAG Configuration - Configured MLAG peer-link in trunk mode (not access) for VLAN 4090/4091 - Added dual-active detection via management interface - Configured virtual router MAC for MLAG pairs #### Switch Port Configuration - Port-Channel1 configured in **trunk mode** on all leaf switches - Added `switchport trunk allowed vlan` for host VLANs (34, 40, 78) - Removed `no shutdown` from Port-Channel interfaces ### 🖥️ Host Networking - Complete Redesign #### Image Change - **Old:** `alpine:latest` (had bonding syntax issues) - **New:** `ghcr.io/hellt/network-multitool` (networking tools pre-installed) #### LACP Bonding Configuration Proper LACP setup following network-multitool best practices: ```yaml - ip link add bond0 type bond mode 802.3ad - ip link set dev bond0 type bond xmit_hash_policy layer3+4 - ip link set dev eth1 down - ip link set dev eth2 down - ip link set eth1 master bond0 - ip link set eth2 master bond0 - ip link set dev eth1 up - ip link set dev eth2 up - ip link set dev bond0 type bond lacp_rate fast - ip link set dev bond0 up ``` #### VLAN Configuration - **L2 VXLAN hosts (host1, host3):** VLAN 40 tagged on bond0 - **L3 VXLAN hosts (host2, host4):** VLANs 34 and 78 tagged on bond0 #### Routing Strategy - Kept management default route (172.16.0.254 via eth0) - Added **specific routes** for L3 VXLAN networks instead of default routes: - host2: `ip route add 10.78.78.0/24 via 10.34.34.1` - host4: `ip route add 10.34.34.0/24 via 10.78.78.1` ### 📁 Files Changed #### Switch Configurations (Updated) - `configs/spine1.cfg` - Added ip routing, EVPN activation - `configs/spine2.cfg` - Added ip routing, EVPN activation - `configs/leaf1.cfg` - Port-Channel trunk mode, VLAN config - `configs/leaf2.cfg` - Port-Channel trunk mode, VLAN config - `configs/leaf3.cfg` - Added ip routing, loopback ads, Port-Channel config - `configs/leaf4.cfg` - Added ip routing, loopback ads, Port-Channel config - `configs/leaf5.cfg` - Port-Channel trunk mode, VLAN config - `configs/leaf6.cfg` - Port-Channel trunk mode, VLAN config - `configs/leaf7.cfg` - Added ip routing, loopback ads, Port-Channel config - `configs/leaf8.cfg` - Added ip routing, loopback ads, Port-Channel config #### Topology (Updated) - `evpn-lab.clab.yml` - Updated all host configurations with network-multitool image and proper LACP/VLAN setup #### Documentation (New) - `hosts/README.md` - Host interface configuration guide - `hosts/host1_interfaces` - Interface file for host1 (not currently used, kept for reference) - `hosts/host2_interfaces` - Interface file for host2 (not currently used, kept for reference) - `hosts/host3_interfaces` - Interface file for host3 (not currently used, kept for reference) - `hosts/host4_interfaces` - Interface file for host4 (not currently used, kept for reference) ## Testing & Verification ### ✅ L2 VXLAN (VLAN 40) ``` host1 (10.40.40.101) → host3 (10.40.40.103) - Connectivity: VERIFIED ✓ - VXLAN tunnel: VTEP1 ↔ VTEP3 - MAC learning: Working via EVPN Type-2 ``` ### ✅ L3 VXLAN (VRF gold) ``` host2 (10.34.34.102) → host4 (10.78.78.104) - Connectivity: VERIFIED ✓ - Ping results: 0% packet loss, TTL=62 - Routing: Via EVPN Type-5 through fabric ``` ### ✅ Infrastructure Status - BGP Underlay: All sessions ESTAB - EVPN Overlay: All neighbors ESTAB - MLAG: All 4 pairs operational - Port-Channels: LACP negotiated on all hosts ## Related Issues Fixes #1 - Lab deployment and configuration fixes Fixes #2 - BGP EVPN neighbors stuck in Connect state Fixes #3 - Ready for deployment with EVPN activation Fixes #4 - Lab convergence in progress Fixes #5 - BGP EVPN neighbors stuck in Active state Fixes #11 - Host LACP bonding configuration Fixes #13 - L3 VXLAN default route issue ## Key Technical Learnings 1. **Arista EOS requires explicit `ip routing`** before BGP can function 2. **MLAG peer-link must be trunk mode** to allow VLAN 4090/4091 traversal 3. **VLAN tagging location matters** - hosts tag, switches use trunk mode 4. **network-multitool image** superior to Alpine for LACP bonding 5. **Specific routes better than default routes** when management network present 6. **LACP rate fast** ensures quick negotiation with Arista switches ## Deployment After merging, deploy with: ```bash cd ~/arista-evpn-vxlan-clab sudo containerlab destroy -t evpn-lab.clab.yml --cleanup sudo containerlab deploy -t evpn-lab.clab.yml ``` No manual post-deployment configuration needed - everything works from initial deployment! ## Breaking Changes ⚠️ **Host image changed** from `alpine:latest` to `ghcr.io/hellt/network-multitool` ⚠️ **Host configuration completely redesigned** - old exec commands replaced ## Reviewers @Damien - Please review and merge when ready --- **This PR represents the complete troubleshooting journey and brings the lab to production-ready status with full L2 and L3 VXLAN functionality.** 🚀

Damien added 85 commits 2025-11-30 10:07:02 +00:00

Fix: Add 'ip routing' command to enable BGP on spine1 7fd9a81013

Fix: Add 'ip routing' command to enable BGP on spine2 830853dfb2

Document all fixes applied in fix-bgp-and-mlag branch e1fb8e27f5

Fix: Add ip routing command to leaf3, leaf4, leaf7, leaf8 ... a6754de9d6

Critical fix to enable BGP initialization on all leaf switches.
Without this command, BGP stays disabled and EVPN neighbors
cannot establish sessions.

Remove redundant comment about IP routing 2aea6a3e7e

Fix: Update all leafs - Port-Channel1 to ACCESS mode ... 5cc976e218

- Changed switchport mode from trunk to access on all leafs
- Updated switchport access vlan statements for each VLAN
- Leaf1/2/5/6: VLAN 40 (L2 VXLAN)
- Leaf3/4: VLAN 34 (L3 VXLAN)
- Leaf7/8: VLAN 78 (L3 VXLAN)

This enables proper untagged traffic handling for host connections.

Fix: Add loopback network advertisements to IPv4 AF on leaf3,4,7,8 ... 1275f27637

Added network statements for loopback addresses in IPv4 address family:
- Leaf3/4: network 10.0.250.13/32, 10.0.250.14/32, 10.0.255.12/32
- Leaf7/8: network 10.0.250.17/32, 10.0.250.18/32, 10.0.255.14/32

This ensures EVPN BGP sessions establish properly on redeploy.
Previously these were only in the VRF gold section.

Fix: Configure hosts to properly tag VLANs for leaf port-channels b6daa30283

Add comprehensive end-to-end testing guide with VLAN tagging fixes c795d1c541

Document VLAN tagging issue and fix in detail e5a4f5c9e5

Add comprehensive testing checklist for deployment validation 573a2af942

Add comprehensive summary of fix-bgp-and-mlag branch changes d27d72440c

Fix: EVPN address family properly activated on spine1 5dada61b2c

Fix: EVPN address family properly activated on spine2 27717bc7de

Document critical BGP EVPN activation bug fix 1f6bd4f978

Fix: Remove duplicate network advertisements in leaf3 BGP config 70d6bb0b8f

Fix: Remove duplicate network advertisements in leaf4 BGP config b9b4fcd163

Fix: Remove duplicate network advertisements in leaf7 BGP config 862d2260bc

Fix: Remove duplicate network advertisements in leaf8 BGP config aef7ce6b6e

Fix: Move network statements to main IPv4 address-family in leaf3 9113a11100

Fix: Move network statements to main IPv4 address-family in leaf4 8ca36c2214

Fix: Move network statements to main IPv4 address-family in leaf7 abfac1ea9f

Fix: Move network statements to main IPv4 address-family in leaf8 16c8de57f2

Fix MLAG peer-link on leaf3: change to trunk mode ae06beb9b5

Fix MLAG peer-link on leaf4: change to trunk mode 3be174807e

Fix MLAG peer-link on leaf7: change to trunk mode e7e8dad6ce

Fix MLAG peer-link on leaf8: change to trunk mode b586035895

Fix MLAG peer-link on leaf1: change to trunk mode 387ba23809

Fix MLAG peer-link on leaf2: change to trunk mode f87a403560

Fix MLAG peer-link on leaf5: change to trunk mode be3c0d50d8

Fix MLAG peer-link on leaf6: change to trunk mode a027145204

Fix host bond interfaces - bring up eth slaves before adding to bond 0a23b0ddeb

Simplify hosts: remove bonding, use single-homed connections f6c9a15653

Revert to dual-homing with LACP for all hosts ... 13bb234971

- All hosts now dual-homed to MLAG pairs using LACP bonding
- host1: connects to leaf1 (eth1) and leaf2 (eth2) - VLAN 40
- host2: connects to leaf3 (eth1) and leaf4 (eth2) - VLAN 34  
- host3: connects to leaf5 (eth1) and leaf6 (eth2) - VLAN 40
- host4: connects to leaf7 (eth1) and leaf8 (eth2) - VLAN 78
- Each host creates bond0 with LACP (mode 802.3ad)
- Proper MAC address assignment per host

Restore LACP mode for Port-Channel1 on leaf1 ... f6ad61ab2e

- Changed channel-group 1 from 'mode on' to 'mode active' for LACP
- Changed Port-Channel1 from access to trunk mode
- Added switchport trunk allowed vlan 40
- This matches the host1 LACP bond configuration

Restore LACP mode for Port-Channel1 on leaf2 ... 68bc4e95f7

- Changed channel-group 1 from 'mode on' to 'mode active' for LACP
- Changed Port-Channel1 from access to trunk mode
- Added switchport trunk allowed vlan 40
- This matches the host1 LACP bond configuration

Restore LACP mode for Port-Channel1 on leaf3 ... 2b93fd1385

- Changed channel-group 1 from 'mode on' to 'mode active' for LACP
- Changed Port-Channel1 from access to trunk mode
- Added switchport trunk allowed vlan 34
- This matches the host2 LACP bond configuration

Restore LACP mode for Port-Channel1 on leaf4 ... 90644633ea

- Changed channel-group 1 from 'mode on' to 'mode active' for LACP
- Changed Port-Channel1 from access to trunk mode
- Added switchport trunk allowed vlan 34
- This matches the host2 LACP bond configuration

Restore LACP mode for Port-Channel1 on leaf5 ... 812d30fcd8

- Changed channel-group 1 from 'mode on' to 'mode active' for LACP
- Changed Port-Channel1 from access to trunk mode
- Added switchport trunk allowed vlan 40
- This matches the host3 LACP bond configuration

Restore LACP mode for Port-Channel1 on leaf6 ... e7ee8df0e5

- Changed channel-group 1 from 'mode on' to 'mode active' for LACP
- Changed Port-Channel1 from access to trunk mode
- Added switchport trunk allowed vlan 40
- This matches the host3 LACP bond configuration

Restore LACP mode for Port-Channel1 on leaf7 ... 82b0fa95b4

- Changed channel-group 1 from 'mode on' to 'mode active' for LACP
- Changed Port-Channel1 from access to trunk mode
- Added switchport trunk allowed vlan 78
- This matches the host4 LACP bond configuration

Restore LACP mode for Port-Channel1 on leaf8 ... da1fffdb17

- Changed channel-group 1 from 'mode on' to 'mode active' for LACP
- Changed Port-Channel1 from access to trunk mode
- Added switchport trunk allowed vlan 78
- This matches the host4 LACP bond configuration

Add 'no shutdown' to Port-Channel1 on leaf1 ... 326638fc8d

CRITICAL FIX: Port-Channel1 was administratively down.
Added 'no shutdown' command to enable the interface.

Add 'no shutdown' to Port-Channel1 on leaf2 b2f23fd803

Add 'no shutdown' to Port-Channel1 on leaf3 6efadaf510

Add 'no shutdown' to Port-Channel1 on leaf4 57b5766ac0

Add 'no shutdown' to Port-Channel1 on leaf5-8 ... 2e2c4e677c

Batch update: Adding 'no shutdown' to all remaining Port-Channel1 interfaces

Add 'no shutdown' to Port-Channel1 on leaf6 8b837ac2fa

Add 'no shutdown' to Port-Channel1 on leaf7 05e8970753

Add 'no shutdown' to Port-Channel1 on leaf8 - ALL CONFIGS COMPLETE bcf76e4cac

Fix leaf1: Add LACP fallback to Port-Channel1 for dual-homing 50434e7cc7

Fix leaf2: Add LACP fallback to Port-Channel1 for dual-homing 413960b8e0

Add LACP fallback configuration to leaf configs ba3ed79363

Add comprehensive EVPN-VXLAN troubleshooting guide fb682fdb19

Update troubleshooting guide ... c3aef36a8e

Improve formatting and add details for clarity.

Fix command syntax - remove invalid 'show mlag interfaces Port-Channel1' 34b6b7bdd6

Fix host bonding: use mode 4 instead of mode 802.3ad for Alpine Linux 31b52d2417

Add host1 network interfaces config with LACP bonding 9ddf594862

Add host2 network interfaces config with LACP bonding for VLAN 34 7c5d65558b

Add host3 network interfaces config with LACP bonding for VLAN 40 25cc7a4dae

Add host4 network interfaces config with LACP bonding for VLAN 78 3eedb0786c

Update topology to use binds for host interface configuration ... 383a631d92

Replace exec commands with binds mounting /etc/network/interfaces files.
This provides cleaner, more maintainable configuration that properly
handles LACP bonding and VLAN tagging on Alpine Linux hosts.

All hosts now:
- Mount their interface config from hosts/ directory
- Install required packages (ifupdown, bonding, vlan)
- Load kernel modules (bonding, 8021q)
- Bring up interfaces with ifup -a

Add comprehensive host interface configuration documentation ... 417b3fc245

Document the persistent interface file approach using binds, explaining:
- Dual-homing architecture with LACP bonding
- VLAN tagging configuration on hosts
- Interface file format and parameters
- Deployment process and requirements
- Testing and troubleshooting procedures

Add README for hosts directory explaining interface configuration files c0f680a0b6

Fix host1 interface config for ifupdown-ng syntax ... 2016863228

Changed to ifupdown-ng compatible bonding syntax:
- bond-slaves → bond-members
- bond-mode 4 → bond-mode 802.3ad
- bond-lacp-rate 1 → bond-lacp-rate fast
- Removed bond-slaves directive (handled by bond-members)
- Removed vlan-raw-device (ifupdown-ng auto-detects from interface name)

Fix host2 interface config for ifupdown-ng syntax 358c0c188b

Fix host3 interface config for ifupdown-ng syntax 6bc86b28be

Fix host4 interface config for ifupdown-ng syntax aa26ad716e

Add 'use bond' directive to enable bonding executor ... 0f3b8f6dff

The bonding executor must be explicitly enabled with 'use bond' 
for ifupdown-ng to create the bond interface properly.
Requires 'bonding' package installed.

Tested and verified working:
- bond0 created with LACP (802.3ad) mode
- eth1 and eth2 enslaved to bond0  
- VLAN interface bond0.40 working
- MLAG showing active-full on switches

Add 'use bond' directive for host2 aa6fbbd2f3

Add 'use bond' directive for host3 b270f4f683

Add 'use bond' directive for host4 aaca77d4d3

Simplify interface file to only configure bond0 ... d32c6fd6a2

VLAN interface creation will be handled by exec commands in topology
since ifupdown-ng can't reliably create VLAN sub-interfaces on bonds.
Removed 'inet manual' to allow bond0 to come up automatically.

Simplify host2 interface file to only configure bond0 17a3bb63a3

Simplify host3 interface file to only configure bond0 89d3e0dac0

Simplify host4 interface file to only configure bond0 15158c2bb1

Hybrid approach: ifupdown for bond0, ip commands for VLAN interfaces ... 428ce8e80f

Interface files handle bond0 creation with LACP via ifupdown-ng.
VLAN sub-interfaces created via ip link commands in exec due to
ifupdown-ng limitations with VLAN interfaces on bonds.

This combines the best of both approaches:
- Persistent bond configuration in /etc/network/interfaces
- Reliable VLAN interface creation via ip commands

Add 'up' command to explicitly bring bond0 up 101143cc59

Configure interfaces for bonding and VLANs ... 43a90805ef

Adds bonding and VLAN configuration to host interfaces files and
configures the clab yaml to load the modules.

Fix host1 IP address to 10.40.40.101 (was incorrectly set to 10.34.34.102) 4405c75cdb

Add VLAN 34 configuration for host2 a93d5e4b9f

Add VLAN 40 configuration for host3 c81c117ef4

Remove redundant VLAN creation commands from exec - interface files handle this 59c4031d13

Fix host4 - add missing VLAN 78 configuration 57477167f1

Configure Linux hosts for LACP bonding and VLANs ... d0db291ede

Use a network-multitool image and configure LACP bonding and VLANs using
the `ip` command.

Damien added 1 commit 2025-11-30 10:07:16 +00:00

Fix static routes for inter-VLAN reachability 3e7759b655

Damien added 1 commit 2025-11-30 10:21:08 +00:00

Remove FIXES_APPLIED.md - info documented in issues 8cf952231e

Damien merged commit 1080bf07bb into main 2025-11-30 10:24:29 +00:00

Damien deleted branch fix-bgp-and-mlag 2025-11-30 10:24:30 +00:00

Damien referenced this issue from a commit 2025-11-30 10:24:31 +00:00

Complete Lab Fixes - L2 and L3 VXLAN Fully Operational (#14)

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

Damien

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Damien/arista-evpn-vxlan-clab#14