Reach the next hop in your career.
Windows Server Lab: Active Directory, SQL Server, and IIS
How a four-server Windows lab with Active Directory, IIS, SQL Server, batch jobs, and monitoring fits together, and the operations exercises it supports.
- Nov 16CCNP ENCOR: BGP Neighbors, Next Hops, and the Best Path Algorithm29 min
- Nov 10CCNP ENCOR: Multi-Area OSPF, Stub Areas, and OSPFv335 min
- Nov 6CCNP ENCOR: EIGRP Metrics, Feasible Successors, and Variance24 min
- Oct 29CCNP ENCOR: Spanning Tree Essentials18 min
- Oct 27CCNP ENCOR: VLANs, Trunking, and EtherChannel17 min
- Sep 21From Vibe Coding to Spec-Driven Development with OpenSpec8 min
- Aug 28JNCIP-ENT Mega Lab Part 4: DC1 EVPN-VXLAN Fabric18 min
- Aug 26JNCIP-ENT Mega Lab Part 3: Metro Ethernet7 min
- Aug 24JNCIP-ENT Mega Lab Part 2: Branch WAN and Basic Multicast16 min
- Aug 19JNCIP-ENT Mega Lab Part 1: Internet Edge and Core19 min
- Aug 11JNCIP-ENT: EVPN-VXLAN Layer 3 Gateway and Multihoming13 min
- Aug 7JNCIP-ENT: EVPN-VXLAN Fabric and Layer 2 Gateway14 min
Latest
Windows Server Lab: Active Directory, SQL Server, and IIS
How a four-server Windows lab with Active Directory, IIS, SQL Server, batch jobs, and monitoring fits together, and the operations exercises it supports.
CCNP ENCOR: BGP Neighbors, Next Hops, and the Best Path Algorithm
BGP connects autonomous systems and selects the best path using next-hop reachability, weight, local preference, AS-path prepending, and MED.
CCNP ENCOR: Multi-Area OSPF, Stub Areas, and OSPFv3
OSPF builds a shared link-state database and calculates best paths across multi-area OSPFv2, stub areas, summarization, filtering, and OSPFv3.
All articles
CCNP ENCOR: EIGRP Metrics, Feasible Successors, and Variance
EIGRP forms adjacencies, calculates its composite metric, and uses DUAL, feasible successors, and variance for fast failover and unequal-cost load balancing.
CCNP ENCOR: Spanning Tree Essentials
STP prevents Layer 2 loops through root elections, path costs, and blocked links, while Rapid-PVST+ speeds convergence and MST scales across VLANs.
CCNP ENCOR: VLANs, Trunking, and EtherChannel
Cisco switching fundamentals come together in hands-on labs with VLANs and SVIs, trunking and router subinterfaces, and static and LACP EtherChannels.
From Vibe Coding to Spec-Driven Development with OpenSpec
I vibe coded for a long time and liked it, but I had no real method. After an Art of Network Engineering episode on spec-driven development, I tried OpenSpec. Here is how vibe coding, SDD, and a few other frameworks compare.
JNCIP-ENT Mega Lab Part 4: DC1 EVPN-VXLAN Fabric
Part 4 builds a self-contained data-center fabric on six vQFX switches: an OSPF underlay with ECMP loopback reachability, an EVPN iBGP overlay with both spines as route reflectors, Layer 2 stretch for two VLANs with anycast IRB gateways, a TENANT1 VRF routed with pure Type 5 over L3 VNI 9999, all-active ESI-LAG multihoming with DF election, and a four-way border handoff back into the AS 65000 enterprise core.
JNCIP-ENT Mega Lab Part 3: Metro Ethernet
Part 3 extends customer VLAN 310 from headquarters to Branch 2 through a Metro Ethernet service. The customer switches retain one VLAN, the provider maps it into service VLAN 3000 with selective Q-in-Q, Layer 2 protocol tunnelling carries customer control frames, and BR2-EDGE01 terminates the subnet on a tagged routed interface.
JNCIP-ENT Mega Lab Part 2: Branch WAN and Basic Multicast
Part 2 extends the mega lab with two different branch WAN designs. Branch 1 uses redundant eBGP sessions through a provider AS and prefers WAN-PE01 with local preference, while Branch 2 uses two routed handoffs in normal OSPF area 1 with unequal costs. A single static RP then supports one PIM sparse-mode ASM service between a source at Branch 2 and a receiver at headquarters.
JNCIP-ENT Mega Lab Part 1: Internet Edge and Core
This is the first build part of the mega lab. It has two providers peering with each other, two enterprise border routers and two core routers, all dual-stack. OSPFv2 and OSPFv3 carry the loopbacks in area 0. The provider transit links stay outside the IGP, so the border routers need next-hop-self. The core routers work as route reflectors in one cluster. Local preference selects the outbound provider, AS path prepend influences the inbound provider, and communities show which border a route entered through. The export policy finishes with a reject term, so the enterprise does not become a transit AS.
JNCIP-ENT: EVPN-VXLAN Layer 3 Gateway and Multihoming
The second EVPN lab in the JNCIP-ENT series. We take the bridged fabric from the previous lab and add Layer 3. The leaves get anycast IRB gateways with one shared virtual IP and MAC, then a tenant VRF and an L3 VNI turn the fabric into symmetric routing with Type 5 routes, so a leaf only holds the VNIs of its own subnets. Then we multihome a host to both leaves with an ESI-LAG and watch EVPN elect a designated forwarder with Type 4 and enable aliasing with Type 1.
JNCIP-ENT: EVPN-VXLAN Fabric and Layer 2 Gateway
The first EVPN lab in the JNCIP-ENT series. We build a two-spine, two-leaf IP fabric on vQFX, make the leaf loopbacks reachable with OSPF and ECMP, and run iBGP with EVPN signaling over it with both spines as route reflectors. The leaves become VXLAN tunnel endpoints and Layer 2 gateways for VLAN 100 as VNI 5100, and two hosts in the same subnet reach each other across the routed core. We verify the Type 3 routes that build the flood list and the Type 2 routes that carry the host MAC addresses.
JNCIP-ENT: Enterprise Routing Policy Construction
The fourth BGP lab in the JNCIP-ENT series. We combine the policy techniques from the earlier labs into one policy set on both border routers. We advertise an aggregate in place of the loopback /32s and suppress the specifics, filter and classify inbound routes with route filters, AS-path regular expressions and communities, then build a policy chain that advertises nothing because the marking term takes no terminating action. We correct it under commit confirmed and validate the result with test policy.
JNCIP-ENT: BGP Route Reflection and Communities
The third BGP lab in the JNCIP-ENT series. We remove one session from the IBGP full mesh to demonstrate the IBGP advertisement rule, then configure R2 as a route reflector and examine the cluster list and originator ID on the reflected route. We add a customer LAN behind R1 and a third AS behind R4, use no-advertise and no-export to stop propagation at two different boundaries, and use a custom community to drive local preference, applying path control by class rather than by prefix.


