
In a Cisco [SD-WAN](/sd-wan) deployment, there are two types of edge devices that can be provisioned: [cEdge](/sd-wan-cedge) and [vEdge](/sd-wan-vedge).  Here are the main differences between them.

## cEdge (Cisco Integrated Services Routers)

   - **Hardware-Based:** cEdge devices are typically hardware-based and are part of Cisco's Integrated Services Routers (ISR) and Aggregation Services Routers (ASR) series.
   - **IOS XE Operating System:** They run on Cisco's IOS XE operating system, which is a more traditional Cisco operating system used in a wide range of Cisco hardware.
   - **Integration with Legacy Systems:** cEdge routers are often used in environments where there is a need to integrate with existing Cisco-based infrastructure and services.
   - **Feature Set:** They support a broad range of traditional routing features and services, in addition to SD-WAN capabilities.
   - **Unified Management:** cEdge devices can be managed through the Cisco [vManage](/sd-wan-vmanage) platform, allowing for unified management with vEdge routers in a mixed environment.

## vEdge (Versatile Edge Routers)

   - **Purpose-Built for SD-WAN:** vEdge routers are purpose-built for SD-WAN and are a part of the Viptela acquisition by Cisco.
   - **Viptela Operating System:** These devices run on the Viptela operating system, which is designed specifically for SD-WAN applications.
   - **Hardware and Software Options:** vEdge is available in both hardware form factors (such as vEdge 100, 1000, 2000 series) and as a virtual appliance (vEdge Cloud).
   - **SD-WAN Focused Features:** While they provide comprehensive SD-WAN functionalities, they might not have as broad a range of traditional routing features as cEdge devices.
   - **Management:** They are also managed through the Cisco vManage platform, providing a centralized management and orchestration solution.

While both cEdge and vEdge devices are integral parts of Cisco's SD-WAN solution and can be managed using the same management platform (vManage), they differ in their underlying technology, purpose, and integration capabilities. cEdge devices are more suited for environments that require integration with existing Cisco infrastructure and support a wider range of traditional networking features, while vEdge devices are specifically tailored for SD-WAN deployments with a focus on simplicity and efficiency in new installations.

The configuration syntax and show commands on these devices are also different. For examples, you can see the links below.

Links:

https://networklessons.com/cisco/cisco-sd-wan/cisco-sd-wan-vedge-onboarding

https://networklessons.com/cisco/cisco-sd-wan/cisco-sd-wan-cedge-onboarding

SD-WAN - vEdge vs cEdge

Rev Up To Recert

Route-Map and ACL matching

Route-map - multiple statements with sequence numbers

Route-map matching OSPF router ID

Route-map with multiple parameters in one match statement

Route-map without a match statement

Route-map

Routers - what is a loopback interface

Routing -  Difference between IGPs and EGPs

Routing - A Directed Broadcast is only detected by the last router

Routing - Administrative Distance

Routing - Cisco Performance Routing (PfR)

Routing - Distance Vector Routing Protocols

Routing - Distance-vector routing protocol use cases

Routing - Dynamic routing protocols

Routing - How the routing table is populated

Routing - IP event dampening

Routing - Injecting a Static Route

Routing - Link State Routing Protocols

Routing - Link-State vs Distance-Vector routing protocols

Routing - Link-state routing protocol use cases

Routing - OER master and border routers

Routing - PfR MC and BR on same device

Routing - Using Anycast with BGP Multipath

Routing - address-family

Routing - default gateway

Routing - default routing using DHCP

Routing - directed broadcast

Routing - fully specified route

Routing - ip default-network command

Routing - l2transport

Routing - link-local IPv6 next hop address needs exit interface

Routing - network vs redistribute connected commands

Routing - redistribute command

Routing - redistribution and the routing table

Routing - route tagging

Routing - seed metrics

Routing - what is a WAN port

Routing - what is recursive routing

Routing NX-OS passive-interface default

Routing Table

Routing in both directions

Routing what if the administrative distance is the same

Routing

SD-WAN - EVE-NG connection options

SD-WAN - cEdge

SD-WAN - vAnalytics

SD-WAN - vBond

SD-WAN - vEdge full mesh

SD-WAN - vEdge

SD-WAN - vManage

SD-WAN - vSmart

SD-WAN set TLOC color

SD-WAN

SDN - what is orchestration

SG300-10 - InterVLAN routing defaults

SNMP - Engine ID

SNMP - Index shuffling

SNMP - Simple Network Management Protocol

SNMP - Version 3 security levels

SNMP - snmp-server community and host commands

SNMP monitoring routing on a Nexus device

SNMP trap vs inform

SNMP walk

SPAN capturing control packets

SPAN multiple destination ports on Cisco IOS device

SPAN using VLANs as a source on a Nexus device

SPAN

SSH - domain-name prerequisite

SSH connectivity - troubleshooting

STP - Aging time reduction with a TCN

STP - BPDU generation and port roles

STP - BPDUGuard, BPDUFilter, and Portfast

STP - BPDUs on a switch where STP is disabled

STP - Disabling spanning-tree

STP - Dispute

STP - Learning State

STP - MST and PVST+ selecting root port

STP - MST maps groups of VLANs

STP - MST region attributes

STP - MST viewed as a single switch by PVST+

STP - Multiple Spanning Tree (MST)

STP - PVST+ and Rapid PVST+ interaction

STP - Per VLAN Spanning Tree plus (PVST+)

STP - RSTP EdgePort

STP - RSTP convergence process

STP - RSTP port roles

STP - RSTP proposal-agreement process

STP - RSTP while timer

STP - Shortest Path Bridging (SPB)

STP - Topology Change Acknowledgement (TCA)

STP - bridge priority

STP - determining the blocked port using port ID

STP - port identification

STP - port roles

STP - port states

STP - what bridge ID does the MST region use

STP - what is a topology change