Why a course about the future starts with history
A network team that meets Cisco SD-WAN today will see at least two generations of names on the same screen. A tool tip may say Manager, a log message may say vmanage, and the router prompt may belong to IOS XE. The history is short, and knowing it turns the naming into a lookup table rather than confusion.
The timeline in outline
- Viptela builds an SD-WAN product. Viptela was a company that sold an SD-WAN solution with its own router (vEdge) and three software components for management, control and orchestration.
- Cisco acquires Viptela. This happened in 2017 according to widely published announcements. Cisco then sold the product as Cisco SD-WAN.
- Cisco adds SD-WAN to IOS XE. SD-WAN software is made available on IOS XE routers, so that existing Cisco platforms can join the same fabric. The Cisco term for these is often cEdge, short for Cisco edge.
- Platform families change. Newer hardware and virtual platforms, such as the Catalyst 8000 family, carry the IOS XE SD-WAN software.
- Renaming. The product has been rebranded, with Catalyst appearing in its name, and the controller components were given plain-language names in place of the v-names.
Check dates and exact release numbers in Cisco's own release notes. This lesson deliberately avoids giving release years beyond the acquisition, because version names and their dates are easy to misquote.
On small screens, swipe sideways or focus the diagram and use the arrow keys.
On small screens, swipe sideways or focus the diagram and use the arrow keys.
Old names and current names
On small screens, swipe sideways or focus the diagram and use the arrow keys.
The original names often survive inside the product. CLI keywords, peer type columns and log messages may still say vsmart, vmanage or vbond. When the screen and the documentation disagree on a name, the function column in the table settles which component is meant.
On small screens, swipe sideways or focus the diagram and use the arrow keys.
Two kinds of WAN Edge
Both can join the same fabric, but they are not the same software and the day-to-day experience differs.
On small screens, swipe sideways or focus the diagram and use the arrow keys.
On small screens, swipe sideways or focus the diagram and use the arrow keys.
The OMP route exchange, TLOC concept and tunnel model are the same idea in both. The commands differ, and so do some feature names, so a command in a guide for one type may not exist, or may look different, on the other. This course uses IOS XE SD-WAN commands and labels every output as an example.
Reading the two vocabularies side by side
- show omp routes in older guides is similar to show sdwan omp routes on an IOS XE router. Check the exact command in your own release.
- vsmart in a peer type column is the Controller.
- vedge in an inventory list can mean a Viptela router, or a general word for edge in older text. Look at the model.
- Controller here means an SD-WAN Controller, not a wireless LAN controller or any other kind.
How the pieces map to the lab used in this course
The course lab has one Manager (10.255.0.10), one Controller (CTRL-01, 10.255.0.11), one Validator (VAL-01, 10.255.0.12), two hubs (HUB-01 10.255.1.1 and HUB-02 10.255.1.2) and two branches (BR-01 10.255.2.1 and BR-02 10.255.2.2). These are system IPs from a teaching plan. Site IDs 10, 20, 101 and 102 in examples are likewise examples, not requirements.
Changes to expect
Product names, feature names and menus keep moving. The architecture, a central brain with distributed edges that tunnel over any transport, has moved much more slowly. When a lesson, a guide or an exam question uses an unfamiliar name, ask three things: which plane does it belong to, which of the four components is it, and which release is the document written for.
Mistakes with names and generations
- Treating vEdge and IOS XE SD-WAN as the same software. The fabric idea is the same; the commands and features can differ.
- Searching only for the new name. Useful older articles and bug reports use the v-names.
- Copying a command from a guide for the wrong platform. Check which edge type the guide covers.
- Quoting dates from memory. Release and support dates change; use Cisco's notices.
Test yourself on the names
A guide says to check the vSmart for the OMP routes of a site. Which current component is that?
Which statement about the history of Cisco SD-WAN is the best supported?
An engineer pastes a command from a vEdge guide into an IOS XE SD-WAN router and it is rejected. What is the most likely reason?