Service-Side BGP and Route Redistribution Loops
Two edges at one site can loop prefixes between BGP and OMP. Cisco documents SoO plus a shared site-id as the brake. Our edges are different sites and report BGP not active.
GUIDES MEET PRACTICE
Clear networking guides and 68 CCNA browser labs. Learn the concepts, practice IOS-style commands, and check your work as you go.
One lab free. No account, installation, or hardware needed.

A browser simulation of selected IOS behavior. It does not run an IOS image.
EXPLORE THE LIBRARY
Models, addresses, and the basics that connect everything.
↗ 02Switching & VLANsBuild and troubleshoot Layer 2 networks.
↗ 03RoutingUnderstand forwarding decisions and paths.
↗ 04Security & accessExplore controls, authentication, and firewalls.
↗ 05WirelessFrom WLAN fundamentals to controller operations.
↗ 06Linux & toolsDiagnose and verify from the command line.
↗FREE FIELD REFERENCES
A free PingLabz account unlocks the Linux, ASA, BGP, and OSPF PDFs. Choose the guide you need and keep it close while you practice.
GO FURTHER WITH PRO
Pro unlocks 60 build labs, six troubleshooting labs, and the campus Mega Lab. Follow guided exercises, try IOS-style commands, and check your configuration as you go.
SELECTED READING
Keep learning
Two edges at one site can loop prefixes between BGP and OMP. Cisco documents SoO plus a shared site-id as the brake. Our edges are different sites and report BGP not active.
VPN 10 already advertises each C8000v LAN into OMP as a connected route. OSPF would face a campus IGP; I did not add a process because this lab has no LAN OSPF speaker.
Shared SD-WAN templates need variables for system-ip, site-id, and LAN addresses. I mapped our two C8000v edges into a CSV-shaped table and did not attach it.
Configuration groups bundle system, transport, and service profiles. I mapped our running C8000v CLI onto that 20.18 stack and did not deploy a group onto either working edge.
A device template is a table of contents for feature templates. I mapped our C8000v CLI, including VPN 10, onto that catalog and did not attach anything to the live edges.
CLI templates, feature templates, and configuration groups are three ways to store the same SD-WAN config. Our C8000v edges still report vManaged false. I compared the models and left the overlay untouched.
PnP Connect is the cloud phone book that gives a factory edge its Validator and organization name. This Catalyst SD-WAN 20.18 lab typed those values instead. I did not use a Smart Account.
vEdge Cloud passed its last date of support on 31 May 2026. A C8000v 17.18 still prints a vEdge banner. I did not boot a vEdge; this post steers new work to IOS XE controller mode.
One IOS XE image holds Autonomous and Controller modes. I read Controller-Managed on a C8000v 17.18 in a Catalyst SD-WAN 20.18 fabric and left the mode unchanged. Cisco documents that enable wipes startup config.
C8000v controller mode rejects tclsh. Transfer the public root instead, install it with the SD-WAN root-chain command, and keep device-certificate installation in the Manager so its inventory stays consistent.
Onboard C8000v 17.18.02 into an SD-WAN 20.18.2.1 fabric using a manual enterprise CA. Tested transport configuration, root installation, activation, certificate staging, and OMP and BFD checks.
The C8000v CSV upload failed. Local PAYG identity generation and a manual list push worked. This SD-WAN 20.18 casebook explains the bootstrap token, certificate serial, and final-push check.