Leaf1, Leaf2, Leaf5, Leaf6: Working correctly (Established) ✓
Leaf3, Leaf4, Leaf7, Leaf8: Still in Active state - need lab redeploy
Root Cause
Leaf3, Leaf4, Leaf7, Leaf8 configs in repository already have the EVPN activation fix, but the running lab instances have old configs that don't have it.
After redeploy, all EVPN neighbors should be Established immediately.
Fixed Configs
spine1.cfg: EVPN activation added
spine2.cfg: EVPN activation added
leaf3.cfg: EVPN activation present
leaf4.cfg: EVPN activation present
leaf7.cfg: EVPN activation present
leaf8.cfg: EVPN activation present
evpn-lab.clab.yml: Host VLAN tagging fixed
## Status
- Spine1 & Spine2: EVPN activation fix applied ✓
- Leaf1, Leaf2, Leaf5, Leaf6: Working correctly (Established) ✓
- Leaf3, Leaf4, Leaf7, Leaf8: Still in Active state - need lab redeploy
## Root Cause
Leaf3, Leaf4, Leaf7, Leaf8 configs in repository already have the EVPN activation fix, but the **running lab instances have old configs** that don't have it.
## Solution
**Redeploy the lab** to load the updated configs:
```bash
cd ~/arista-evpn-vxlan-clab
sudo containerlab destroy -t evpn-lab.clab.yml --cleanup
sudo containerlab deploy -t evpn-lab.clab.yml
```
After redeploy, all EVPN neighbors should be Established immediately.
## Fixed Configs
- spine1.cfg: EVPN activation added
- spine2.cfg: EVPN activation added
- leaf3.cfg: EVPN activation present
- leaf4.cfg: EVPN activation present
- leaf7.cfg: EVPN activation present
- leaf8.cfg: EVPN activation present
- evpn-lab.clab.yml: Host VLAN tagging fixed
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Status
Root Cause
Leaf3, Leaf4, Leaf7, Leaf8 configs in repository already have the EVPN activation fix, but the running lab instances have old configs that don't have it.
Solution
Redeploy the lab to load the updated configs:
After redeploy, all EVPN neighbors should be Established immediately.
Fixed Configs