LAB 20 / 20

Full Integration — All Protocols Simultaneously

MPLS VPNDMVPN Phase 3MP-BGPMulticastIPv6 / 6PEQoS

Active Nodes

20 FULL INTEGRATION Full Integration — Active: ALL 20 ROUTERS See master topology for full 20-router diagram Active Nodes: ALL 20 ROUTERS Full Integration ALL 20 ROUTERS Refer to lab.html for complete step-by-step configuration and verification commands for each active router Active Zone Inactive (dimmed) Ioannis (John) Alexander Konstas

Active routers: ALL 20 ROUTERS

Key Concepts

Integration Architecture

This final lab runs all 20 protocols simultaneously on the full topology. The MPLS backbone (Labs 01-05) provides VPN services to CE sites. Dual DMVPN regions (Labs 06-08) connect branch offices through MPLS-attached PE routers. BGP route reflection (Lab 09) scales iBGP. Communities and prefix filtering (Labs 11-12) control policy. OSPF multi-area (Lab 13) and OSPFv3 (Lab 14) run concurrently. EIGRP named mode (Lab 15) handles DMVPN routing. MPLS-TE tunnels (Lab 16) steer core traffic. Multicast (Lab 17) runs over both MPLS and DMVPN. QoS (Lab 18) marks and queues traffic end-to-end. 6PE (Lab 19) extends IPv6 across the IPv4 MPLS backbone.

Troubleshooting Methodology

In a full-integration scenario, troubleshoot from bottom up: Layer 1/2 physical connectivity → OSPF adjacencies (IGP) → LDP sessions (MPLS) → BGP sessions (overlay) → VRF routing (VPN) → DMVPN NHRP (overlay tunnels) → EIGRP over tunnels (dynamic routing) → Application reachability. Use structured isolation: ping from PE Loopback to PE Loopback (tests MPLS core), then VRF ping PE-to-CE (tests VPN), then CE-to-CE (tests end-to-end VPN). Each layer confirms the one below is working.

Verification Checklist

Complete verification requires confirming each protocol independently before testing integration points. The checklist below covers all 20 routers across all protocol domains. Run each command systematically and record expected vs actual output. Document any discrepancies — in the CCIE lab exam, partial credit is awarded per verified protocol, so thorough verification maximizes the score even if one subsystem has issues.

Full Integration Verification Checklist

show ip ospf neighbor — ALL CORE and EDGE routers
All adjacencies FULL. BFD Up. 8 OSPF neighbors total in backbone (4 CORE + 4 EDGE loopbacks).
show mpls ldp neighbor — ALL CORE and EDGE
All LDP sessions Operational. Label range 1000-9999 confirmed. MD5 auth on all sessions.
show ip bgp vpnv4 all summary
All PE routers (EDGE-1/2/3/4) and BORDER routers in Established state to RR (CORE-1/2). VPNv4 prefixes exchanged.
show ip nhrp — HUB-WC-1, HUB-EC-1
All 3 spokes per hub registered. Dynamic mappings with NBMA addresses of all spokes.
show ip eigrp neighbors — all HUB and SPK routers
Hub-to-spoke EIGRP adjacencies Up. After Phase 3 shortcuts: spoke-to-spoke neighbors may appear.
ping vrf CORP 192.168.200.1 source 192.168.100.1 — from CE-CORP-1
CE-to-CE end-to-end VPN ping success. Traffic path: CE1 → PE1 → MPLS core → PE4 → CE2.
ping 10.10.12.1 source 10.10.11.1 — from SPK-WC-1
Spoke-to-spoke via DMVPN. Initially 5 hops via hub; after Phase 3 shortcut: 2 hops direct.
show ip pim rp mapping — all routers
Consistent RP mapping across all routers. RP 10.255.1.2 for 239.0.0.0/8.
show bgp ipv6 unicast — PE routers
IPv6 prefixes from both CE sites present with labels. 6PE forwarding active.
show policy-map interface Tunnel0 — SPK-WC-1
QoS policy active. Voice priority queue showing traffic. No tail drops in priority class.

Research and direction by Ioannis (John) Konstas; compiled and finalized with AI assistance.

Initial Configs — Load These First
⬇ CORE-1-initial.cfg ⬇ CORE-2-initial.cfg ⬇ CORE-3-initial.cfg ⬇ CORE-4-initial.cfg