> ## Content Index > Fetch the complete content index at: https://www.pinglabz.com/llms.txt > Use this file to discover other available public pages before exploring further. # vEdge in 2026: Onboarding and Why It's End-of-Life - URL: https://www.pinglabz.com/cisco-vedge-2026/ - Published: 2026-11-06T04:40:51.000Z - Updated: 2026-11-06T04:40:51.000Z - Description: 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. - Author: Jaime - Tags: SD-WAN, Cisco Search an old SD-WAN tutorial and the first edge you meet is a vEdge Cloud. Search `show sdwan system status` on a current Catalyst 8000v and the banner still says vEdge Operating System Software. Those two facts are easy to mix up, and in 2026 they send people down a path Cisco has already closed. This post separates the old Viptela OS vEdge family from the IOS XE edge you should build now. I did not boot a vEdge in this lab. The onboarding steps and the calendar dates come from Cisco's own documents. What I did capture is how a Catalyst 8000v on IOS XE 17.18.02 still prints the word "vEdge" while it runs in a Cisco Catalyst SD-WAN 20.18.2.1 fabric, built in my home lab. This is part of the [Cisco SD-WAN series](https://www.pinglabz.com/cisco-sd-wan/). Previous: [Autonomous vs Controller Mode on IOS XE](https://www.pinglabz.com/controller-mode-ios-xe/). Next: [Zero-Touch / PnP Onboarding Explained](https://www.pinglabz.com/sd-wan-ztp/). For SD-WAN Manager (formerly vManage) and the other old names, see the [name map](https://www.pinglabz.com/vmanage-vsmart-vbond-names/). ## The problem: the name outlived the product "vEdge" started as Viptela's WAN edge: the vEdge 100, 1000, 2000, and 5000 hardware, plus vEdge Cloud for hypervisors. Those boxes run Viptela OS, not IOS XE. Their CLI uses `vpn 0` and `ge0/0`, not `vrf` and `GigabitEthernet`. Cisco's current virtual edge is the Catalyst 8000v running IOS XE in Controller mode. That is the platform this series onboarded. The confusion comes from leftover labels. On edge1 right now: ``` edge1#show sdwan system status Viptela (tm) vEdge Operating System Software Controller Compatibility: 20.18 Version: 17.18.02.0.4112 Personality: vEdge Model name: C8000V Device role: cEdge-SDWAN ``` The output is trimmed. The banner and the `Personality: vEdge` line look like a Viptela OS router. The model and device role say otherwise: this is a C8000V playing the SD-WAN edge role, which older software called cEdge. `show version` on the same box is the clearer signal: ``` Cisco IOS XE Software, Version 17.18.02 Router operating mode: Controller-Managed cisco C8000V (VXE) processor ``` If your router prints IOS XE and `Controller-Managed`, you do not have a vEdge, no matter what the personality field says. Follow the [C8000v onboarding post](https://www.pinglabz.com/onboard-c8000v-controller-mode/), not a Viptela OS guide. [![Retired vEdge Cloud and Viptela OS with last support 31 May 2026 beside this lab C8000v showing leftover Personality vEdge but Device role cEdge-SDWAN](https://storage.ghost.io/c/ff/28/ff28db4a-11e1-4835-b928-158974cf96c1/content/images/2026/11/cisco-vedge-2026.png)](https://storage.ghost.io/c/ff/28/ff28db4a-11e1-4835-b928-158974cf96c1/content/images/2026/11/cisco-vedge-2026.png?ref=pinglabz.com) ## What Cisco ended, and when These dates come from Cisco's end-of-sale bulletins and the 20.9 vEdge release notes. I am not restating a lab result. **vEdge Cloud** (bulletin EOL14892): - End-of-sale: 2 May 2023 - End of software maintenance: 31 March 2025 - End of service-contract renewal: 31 May 2026 - Last date of support: 31 May 2026 - Last software train: 20.9.x - Listed replacement: Catalyst 8000V (Cisco DNA subscription `L-DNA-C8000V`) As of this writing in November 2026, vEdge Cloud is past its last date of support. **Select vEdge hardware** (the 100-series, 1000, 2000, 5000 family covered by the select-products bulletin): - End-of-sale: 2 May 2023 - End of software maintenance: 1 May 2024 - End of vulnerability and security support: 1 May 2026 - Last date of support: 30 April 2028 The hardware can still be under contract into 2028\. It does not get new software trains. Cisco's 20.9 vEdge release notes also say that Control Components Release 20.9.x is the last supported control-component version for Cisco vEdge devices. The last vEdge software train is 20.9.x. A later Manager such as 20.18.1 documents a device-version compliance rule that supports devices up to N-2 long-lived releases and does not support older versions in the overlay. I did not add a vEdge to this 20.18.2.1 fabric, so I cannot tell you whether Manager would accept one. I can tell you I would not start a new overlay on that platform. A related 20.18.1 change: Cisco SD-WAN Manager now treats ISR 1100 and ISR 1100X routers as IOS XE by default when it recognizes them, instead of assuming Viptela OS. Some of those platforms could run either image historically. Check which OS the box actually boots before you follow a vEdge procedure. ## How vEdge onboarding worked (docs, not this lab) Cisco's WAN Edge onboarding guide describes two automated paths and a manual path. I did not replay them here. For a **physical vEdge**, Zero-Touch Provisioning (ZTP) was the factory path. The router took an address with the Dynamic Host Configuration Protocol (DHCP) on its ZTP-capable WAN port, resolved Cisco's ZTP hostname (`ztp.viptela.com` in the 2020 guide; later documents also say `ztp.cisco.com`), and learned the Validator address and organization name. After that, the edge authenticated with its chassis and serial and built control connections the same way any other edge does. For **vEdge Cloud**, there was no factory chassis sticker. You created the device in SD-WAN Manager, took the generated chassis number and a one-time token, and activated the virtual machine with Cisco's documented command: ``` request vedge-cloud activate chassis-number token ``` I did not run that command. On the C8000v we used a different activation verb and a pay-as-you-go identity, as the [serial-list post](https://www.pinglabz.com/sd-wan-serial-list-upload/) and the [onboarding post](https://www.pinglabz.com/onboard-c8000v-controller-mode/) describe. The day-zero CLI is also a different language: | Task | Viptela OS vEdge (docs) | IOS XE Controller mode (this lab) | | ------------------ | -------------------------------- | ------------------------------------ | | Enter config | config then commit | config-transaction then commit | | WAN VPN | vpn 0 | VRF 0 under sdwan / tunnel-interface | | Interface names | ge0/0 | GigabitEthernet2, GigabitEthernet3 | | Mode choice | None. It is always Viptela OS | Autonomous vs Controller mode | | Virtual activation | request vedge-cloud activate ... | PAYG / chassis activation for C8000v | Trust works the same idea in both families: the edge needs a root it shares with the controllers, and the controllers need the edge's chassis and serial on the authorized list. The files and commands differ. Pasting a vEdge `vpn 0` snippet onto a C8000v will not configure the transports. ## Where to go instead If you are building a lab or a new site in 2026, use IOS XE in Controller mode: 1. Confirm the mode, as in the [Autonomous vs Controller Mode post](https://www.pinglabz.com/controller-mode-ios-xe/). 2. Install an enterprise root if you are not using Cisco's cloud certificate path. See [Enterprise root CA for SD-WAN without a Smart Account](https://www.pinglabz.com/sd-wan-enterprise-root-ca/). 3. Authorize the chassis and serial. See [Uploading the WAN edge serial list manually](https://www.pinglabz.com/sd-wan-serial-list-upload/). 4. Bring the C8000v into the overlay. See [Onboard a Catalyst 8000v 17.18 in controller mode](https://www.pinglabz.com/onboard-c8000v-controller-mode/). The next post explains the cloud Plug and Play path that a factory IOS XE box would use instead of all that typing. ## What breaks - **Following a vEdge Cloud tutorial on a C8000v.** `request vedge-cloud activate` is the wrong verb. Interface names and VPN syntax will not match. - **Trusting \`Personality: vEdge\` as the platform.** On our C8000v that field is `vEdge` while `show version` says IOS XE and `Device role` says `cEdge-SDWAN`. - **Planning a new overlay around vEdge Cloud.** Cisco's last date of support was 31 May 2026\. The last software train is 20.9.x. - **Mixing an old vEdge into a 20.18 fabric without checking compatibility.** Cisco published both a 20.9 last-supported-controller note and a 20.18 device-version compliance rule. I did not test the mix. - **Assuming every ISR 1100 is a vEdge.** In 20.18.1, Manager defaults to recognizing those platforms as IOS XE. Boot the image you think you have. ## Key takeaways - vEdge means Viptela OS: the old hardware family and vEdge Cloud. It is not the same thing as a Catalyst 8000v, even when `show sdwan system status` still prints a vEdge banner. - vEdge Cloud's last date of support was 31 May 2026\. Select vEdge hardware is end-of-sale, with last support listed through 30 April 2028, and no software train beyond 20.9.x. - Cisco lists Catalyst 8000V as the replacement for vEdge Cloud. That is the edge this series uses. - I did not onboard a vEdge in this lab. The activation command and ZTP hostnames above are from Cisco's documents. - If your router runs IOS XE 17.18 in Controller mode, ignore the leftover vEdge personality string and stay on the C8000v path.