Skip to main content
Cisco SD-WAN
Product Documentation
Viptela Documentation

vEdge Cloud Router

The vEdge Cloud is a virtualized version of the vEdge router, inheriting all the capabilities offered on Viptela’s physical branch routers. vEdge Cloud can be instantiated as a virtual machine (VM) on a KVM hypervisor or as a VM on a VMware ESXi hypervisor, as well as in public cloud environments, such as Amazon AWS or Google Cloud Platform. vEdge Cloud can be used as a Virtual Network Function (VNF) for a Virtual CPE (vCPE) deployment at the branch. It can also be used as a Virtual Private Cloud (VPC) Gateway for customers that have workload residing in Amazon Web Services (AWS).

Start and Configure the vEdge Cloud Router

To start the vEdge Cloud router, you create a VM instance for it on a server on which the VMware vSphere ESXi Hypervisor or the Kernel-based Virtual Machine (KVM) Hypervisor software is installed. For server requirements, see Server Hardware Requirements.

To create a vEdge Cloud VM instance, see Deploy the vEdge Routers.

To configure the vEdge Cloud router, see Configure the vEdge Routers.

vEdge Cloud Router Default Configuration

Each vEdge Cloud router has a default configuration. The default configuration file sets the default CLI prompt to vEdge#, configures OMP, and enables logging of syslog messages to a file.

The default configuration file looks like this:

vEdge# show running-config
 host-name vedge
​  auth-order local radius tacacs
  usergroup basic
   task system read write
   task interface read write
  usergroup netadmin
  usergroup operator
   task system read
  task interface read
   task policy read
   task routing read
   task security read
  user admin
   password $6$F1rfcIs0C/GI3RPc$jo/<wbr/>wlF0Ivv2aOlslWO3qEhVTFAVjpoTbz<wbr/>1EzckuzFLXvYK59JhpcqR7rtqY6pni<wbr/>eg/0m.X85SxShYxy9PQ7.r.
 no shutdown
 advertise connected
 advertise static
  authentication-type ah-sha1-hmac sha1-hmac
vpn 0
 interface ge0/0
  ip dhcp-client
   encapsulation ipsec
   no allow-service bgp
   allow-service dhcp
   allow-service dns
   allow-service icmp
   no allow-service sshd
   no allow-service netconf
   no allow-service ntp
   no allow-service ospf
   no allow-service stun
  no shutdown
vpn 512
 interface eth0
  ip dhcp-client
  no shutdown
  • Was this article helpful?