Projects › EIGRP for a Three-Store Retailer: Authenticated Peering and Stub Branches
EIGRP for a Three-Store Retailer: Authenticated Peering and Stub Branches
A retailer's head office (HQ-RTR, with the point-of-sale server) connects to two stores over metro Ethernet. The links and LANs are addressed, nothing routes, and the store tills cannot reach the POS server. The previous provider ran EIGRP with no authentication, which an audit flagged. Bring up EIGRP AS 100 across all three sites, keep hellos off the shop-floor LANs, authenticate every WAN adjacency with MD5, and make the stores stub routers so a lost route at HQ never sends queries into them. Then translate the result into named mode, the form newer platforms use.
Difficulty: intermediate · Time: about 55 minutes
Why it matters
EIGRP is still common in Cisco retail and branch estates. Stub routing and authenticated peering are what keep a hub-and-spoke EIGRP network stable and trustworthy at scale, and they are what an engineer is asked about when inheriting one.
Technologies
- EIGRP
- EIGRP Stub
- Authentication
- Passive Interfaces
- EIGRP Named Mode
Related projects
- Multi-Area OSPFv2 Network with Area 0 Backbone & Stub Routing
- Branch-to-Cloud WAN Fabric Deployment via Cisco SD-WAN
- Route-Based Site-to-Site VPN: Tunnel Interface and eBGP, with IKEv2 Design
- WAN-Edge QoS for Voice and Video: Classify, Queue, Apply
- Cisco SD-WAN Direct Internet Access (DIA) with Enterprise Firewall
- Dual-Circuit Branch: Floating Static Failover with a Pinned Probe Route
- DMVPN Phase 3: Hub-and-Spoke with On-Demand Spoke-to-Spoke Tunnels
- Small Office Internet Gateway with NAT Overload (PAT)