{"id":4296,"date":"2025-08-19T06:10:22","date_gmt":"2025-08-19T06:10:22","guid":{"rendered":"https:\/\/www.prepaway.net\/certification-training\/?p=4296"},"modified":"2025-08-19T06:10:22","modified_gmt":"2025-08-19T06:10:22","slug":"introduction-vedge-initialization-via-cli-cisco-sd-wan","status":"publish","type":"post","link":"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/","title":{"rendered":"Introduction to vEdge Initialization via CLI in Cisco SD-WAN"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">The initialization of vEdge devices in a Cisco SD-WAN infrastructure is a foundational step toward building a resilient and secure overlay network. vEdges, as the data plane components of SD-WAN, act as branch routers that ensure connectivity across geographically dispersed locations. They are responsible for handling data traffic, enforcing policies, and participating in secure communication across tunnels established between sites.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">The process of bringing up these vEdges requires attention to system configuration, secure onboarding, and interface setup. While Cisco SD-WAN supports GUI-based workflows through vManage, using CLI allows network engineers to have direct control and hands-on experience, which is crucial in real-world troubleshooting and deployment scenarios.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">This guide walks through the CLI-based initialization of vEdge devices in a structured SD-WAN lab topology. From uploading device credentials to configuring essential system parameters and network interfaces, each step contributes to the readiness of the device for full participation in the SD-WAN fabric.<\/span><\/p>\r\n<h2><b>Understanding the Lab Topology<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">This setup includes four vEdge devices, a vManage controller, a vBond orchestrator, and an internet\/MPLS cloud. Each vEdge connects to both management and transport networks and requires separate configuration for control and data plane participation.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">The vEdge devices include:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vEdge1: System-IP 10.1.1.21, Site-ID 1<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vEdge2: System-IP 192.168.5.22, Site-ID 2<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vEdge3: System-IP 172.16.4.23, Site-ID 3<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vEdge4: System-IP 10.1.4.24, Site-ID 4<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">All devices use the organization name &#8220;viptela sdwan&#8221; and point to the same vBond orchestrator at IP address 200.1.1.4.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Interfaces on each device serve two purposes:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPN0 (transport network): Uses Ge0\/0 with IP addressing and IPSec tunnel configurations.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPN512 (management): Uses Eth0 configured to receive an address via DHCP.<\/span><\/li>\r\n<\/ul>\r\n<h2><b>Uploading the Serial Number File to vManage<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Before vEdge routers can be brought online, they must be authorized by vManage. This is done using a serial number file that maps each device\u2019s credentials, including chassis number and token, to an organization and controller domain.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">To upload this file:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Access vManage via the appropriate interface.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Navigate to the configuration section and open the WAN Edge list management area.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Upload the provided serial file.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enable validation and dispatch to controllers.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Confirm the upload process.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Successful upload of this list allows vManage to accept connection attempts from the specified vEdge routers, provided their system parameters match the uploaded credentials.<\/span><\/p>\r\n<h2><b>Initializing vEdge Devices from the CLI<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Each vEdge must be configured individually. This configuration includes defining the system-wide parameters such as hostname, organization name, system IP, site ID, and vBond IP. Following that, both VPN0 and VPN512 need to be set up to enable transport and management connectivity.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Let\u2019s examine the configuration for each vEdge device.<\/span><\/p>\r\n<h2><b>Configuration of vEdge1<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Start by accessing vEdge1 via console with default login credentials.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Configure the system settings:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hostname: vEdge1<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Organization-name: viptela sdwan<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">System-IP: 10.1.1.21<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Site-ID: 1<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vBond: 200.1.1.4<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Timezone: Asia\/Kolkata<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">This setup ensures the vEdge identifies itself accurately to the SD-WAN controllers and aligns with the control-plane infrastructure.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Next, configure VPN0 using interface Ge0\/0:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IP Address: 10.1.1.1\/24<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Tunnel encapsulation: IPSec<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Services: All, NetConf, SSHD<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Default route: 10.1.1.2<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">This interface connects the vEdge to the WAN underlay and establishes secure tunnels to other SD-WAN devices.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Then configure VPN512 with interface Eth0:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IP Address: DHCP<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role: Management interface<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">This interface is used for communication with the controller layer, specifically for initial device bring-up and management access.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">After committing the configuration, verify it using the running configuration command. Confirm system parameters, VPN interface IPs, tunnel settings, and connectivity to the default gateway.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Test connectivity to the vBond orchestrator at 200.1.1.4 and ensure that the vEdge device attempts to establish control connections.<\/span><\/p>\r\n<h2><b>Configuration of vEdge2<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Access vEdge2 using the console and apply the following system configuration:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hostname: vEdge2<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Organization-name: viptela sdwan<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">System-IP: 192.168.5.22<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Site-ID: 2<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vBond: 200.1.1.4<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Timezone: Asia\/Kolkata<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">For VPN0, configure interface Ge0\/0:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IP Address: 192.168.5.2\/24<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Tunnel encapsulation: IPSec<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Services: All, NetConf, SSHD<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Default route: 192.168.5.1<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">This interface provides underlay connectivity to the Internet-Cloud router. This link is crucial for establishing IPsec tunnels and control plane communication.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">For VPN512, use interface Eth0 with DHCP client settings enabled.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Ge0\/1 is left unused for now, as it is intended for MPLS connectivity in more advanced stages.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Verify the configuration using the appropriate CLI commands. Ensure that all interface statuses are up, correct IPs are applied, and the tunnel interface is active.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Ping the local gateway and the vBond IP to validate underlay network reachability.<\/span><\/p>\r\n<h2><b>Configuration of vEdge3<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">For vEdge3, start by applying these system-level parameters:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hostname: vEdge3<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Organization-name: viptela sdwan<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">System-IP: 172.16.4.23<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Site-ID: 3<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vBond: 200.1.1.4<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Timezone: Asia\/Kolkata<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">In VPN0, configure interface Ge0\/0:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IP Address: 172.16.4.2\/24<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Tunnel encapsulation: IPSec<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Services: All, NetConf, SSHD<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Default route: 172.16.4.1<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">As before, this interface is designated for WAN traffic. It facilitates communication with the controller infrastructure and other vEdge devices.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Set up VPN512 using Eth0 with DHCP client configuration. This enables the vEdge to reach out to vManage for management and telemetry.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Ge0\/1 remains inactive, planned for MPLS connectivity in extended configurations.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Once configuration is complete, validate each section using show commands to confirm IP settings, tunnel status, and routing entries. Ping the default gateway and vBond IP to ensure both data and control paths are operational.<\/span><\/p>\r\n<h2><b>Configuration of vEdge4<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Connect to vEdge4 and initialize the system parameters:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hostname: vEdge4<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Organization-name: viptela sdwan<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">System-IP: 10.1.4.24<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Site-ID: 4<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vBond: 200.1.1.4<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Timezone: Asia\/Kolkata<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Configure VPN0 on Ge0\/0:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IP Address: 10.1.4.2\/24<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Tunnel encapsulation: IPSec<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Services: All, NetConf, SSHD<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Default route: 10.1.4.1<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">This setup enables secure underlay connectivity with adjacent routers and controllers.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Configure VPN512 on Eth0:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IP Address: DHCP<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">No shutdown<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Interface Ge0\/1 is reserved for future expansion.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Once committed, review the entire configuration using running configuration commands. Verify routing, tunnel encapsulation, and service accessibility. Ensure that the device can reach the vBond orchestrator and local gateway.<\/span><\/p>\r\n<h2><b>Verifying Connectivity and System Health<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">After all configurations are applied and committed on each vEdge, the next step is to ensure that they are attempting to establish control connections. This involves:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Verifying control status<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Checking reachability to vBond, vSmart, and vManage<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Confirming that IPsec tunnels are forming correctly<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Validating interface status (should be up\/up)<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Running trace and ping commands to test paths<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">The default route configured in VPN0 points toward the gateway, and from there, traffic is routed to the SD-WAN controllers.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">In parallel, check the vManage interface to see if the devices are listed as authorized and connected. Devices should appear with green status indicators once fully onboarded and in sync.<\/span><\/p>\r\n<h2><b>Troubleshooting Tips<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">If any of the vEdges fail to establish connections:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Confirm that system-IP, site-ID, and organization-name match the serial file.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ensure vBond IP is reachable via VPN0.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Check physical and logical status of interfaces.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Validate that the DHCP client on VPN512 received an address.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reboot the device to re-initiate the control connections.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Check logs using relevant CLI commands for deeper diagnostics.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Understanding the cause of failures during initial onboarding is essential, as many SD-WAN issues arise due to misconfigured system parameters or lack of reachability between devices.<\/span><\/p>\r\n<h2><b>Integrating Initialized vEdges into the Cisco SD-WAN Overlay<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">After the CLI-based configuration of your vEdge devices, the next phase involves integrating these devices into the SD-WAN overlay. This process is not just about basic connectivity\u2014it\u2019s about establishing secure, authenticated communication with SD-WAN controllers and verifying end-to-end readiness. Once done, each vEdge becomes a fully functioning node in your SD-WAN fabric, capable of enforcing policies and forwarding data intelligently.<\/span><\/p>\r\n<h2><b>Understanding the SD-WAN Control Plane Components<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">A robust Cisco SD-WAN deployment relies on three main controllers:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vBond Orchestrator: Acts as the gatekeeper. It authorizes new vEdges and introduces them to the control plane.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vSmart Controller: Responsible for policy distribution, routing decisions, and key management.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">vManage: The network management interface where administrators configure and monitor the entire SD-WAN environment.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Each vEdge device must form secure connections with these controllers to become operational in the overlay network.<\/span><\/p>\r\n<h2><b>Verifying Control Connections from vEdge Devices<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Once your vEdges are powered up and configured, they will begin attempting connections to the vBond orchestrator over VPN0. Once vBond verifies identity, it provides the IP addresses of the vSmart and vManage systems.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">You can check these connections via CLI. A properly functioning vEdge will display:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">An active DTLS\/TLS tunnel to vBond.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Additional tunnels to vSmart and vManage once authorized.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A control connection table showing status, uptime, and peer IPs.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">These connections are critical for configuration synchronization, policy enforcement, and overlay tunnel formation.<\/span><\/p>\r\n<h2><b>Troubleshooting vEdge Control Connectivity Issues<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">If a vEdge fails to establish control connections, it\u2019s essential to diagnose each stage of the onboarding process.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Common checks include:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Organization Name Mismatch: Ensure it matches the one used to generate the serial file.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Incorrect vBond IP: The vBond IP must be reachable over VPN0.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time Zone and Clock Issues: Time discrepancies can cause certificate mismatches.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Tunnel Misconfiguration: Ensure VPN0 is using the correct encapsulation and that interfaces are not shut down.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Missing Default Routes: Without a default or static route, control traffic can\u2019t reach controllers.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Addressing these problems at the system level ensures control connections will form as expected.<\/span><\/p>\r\n<h2><b>Device Registration in vManage<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Once a vEdge establishes initial contact with the vBond orchestrator and receives controller IPs, it will reach out to vManage. At this stage, vManage checks whether the device&#8217;s serial number and chassis ID exist in its uploaded list.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Successful registration means the device appears in the vManage device list with a valid status. If not:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The vEdge might show as pending approval.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Administrators can manually accept it if auto-approval is disabled.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Failure to appear means the serial file may not have been uploaded correctly or system information doesn\u2019t match.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Registration is mandatory before the device is allowed to receive configuration templates or participate in policy distribution.<\/span><\/p>\r\n<h2><b>Ensuring Configuration Accuracy<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">After the vEdge appears in vManage, verify that its CLI configuration matches expectations.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Critical parameters include:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">System Settings: Hostname, system-IP, site ID, and organization name must align with the serial file.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPN0 Configuration: Should include a valid IP, encryption encapsulation, and allow services like SSH and NetConf.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPN512 Configuration: Should receive a management IP address, typically via DHCP.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Static Routes: Default routes must point toward the next-hop gateway.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">All of these parameters must be in place for the vEdge to maintain reliable communication with the SD-WAN control plane.<\/span><\/p>\r\n<h2><b>Testing Control Plane Connectivity<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">With registration complete and tunnels formed, conduct control plane verification using the CLI:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Check the control connection status for each controller.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Monitor tunnel uptime, latency, and keepalive statistics.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use ping or traceroute tools from the vEdge to the controller IPs.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Look for any flapping tunnels or drop in peer status.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Well-formed control connections result in the delivery of configuration templates and routing updates to the vEdge.<\/span><\/p>\r\n<h2><b>Observing vEdge Status in vManage<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">vManage provides a dashboard where you can visually confirm:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Device health status (up\/down)<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Control connection status<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Interface status (Ge0\/0, Eth0, etc.)<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reachability of the vEdge over the management plane<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">If your vEdge shows \u201cgreen\u201d across all categories, it means it is successfully integrated and synchronized.<\/span><\/p>\r\n<h2><b>Deploying Configuration Templates (Optional)<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Once a vEdge is registered, you may choose to manage its configuration using templates from vManage:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Feature Templates: Define configurations for system, VPNs, and interfaces.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Device Templates: Apply a complete configuration to a vEdge based on feature templates.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Templates allow centralized control, consistency across devices, and simplified scaling of configurations.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">However, CLI-managed vEdges still retain full functionality and are preferable in hands-on lab or testing environments.<\/span><\/p>\r\n<h2><b>Recommended Next Steps Post-Integration<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">After a vEdge is fully operational, consider:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Applying centralized control and data policies.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Monitoring interface utilization and tunnel health.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Verifying application visibility and traffic steering.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Integration is just the beginning. Full SD-WAN functionality comes from policy deployment, redundancy planning, and proactive monitoring.<\/span><\/p>\r\n<h2><b>Finalizing vEdge Initialization and Verifying Connectivity<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">After completing the base configurations on your vEdge routers, it\u2019s essential to finalize initialization, ensure all controllers are reachable, and validate that your vEdges have successfully joined the SD-WAN overlay fabric. This final stage is just as critical as the initial setup. Proper verification avoids long-term deployment issues, ensuring a stable and secure SD-WAN operation.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">This part covers the remaining tasks: activating control connections, verifying system synchronization, troubleshooting onboarding issues, and performing post-deployment testing.<\/span><\/p>\r\n<h2><b>Establishing Secure Control Connections<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">When the vEdge router is configured correctly and powered on, it attempts to establish control connections with the SD-WAN controllers\u2014namely vBond, vSmart, and vManage.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">The communication process unfolds as follows:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The vEdge initiates contact with the vBond orchestrator, whose IP address was configured in the CLI under the system settings.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Once authenticated via the serial file and OTP (if used), vBond facilitates connections between the vEdge and the remaining controllers.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The vEdge then forms DTLS or TLS tunnels with vSmart and vManage.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">These tunnels carry routing, policy, and management data\u2014forming the control plane of your SD-WAN fabric.<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Use the CLI to monitor these connections and confirm secure establishment.<\/span><\/p>\r\n<h2><b>Verifying Control Connections Using CLI<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">This command displays the current status for:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Connection type (TLS or DTLS)<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Local and remote IPs<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Uptime and state<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Connected controller type (vSmart, vManage, or vBond)<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">A typical healthy connection shows as \u201cup\u201d for all three controllers.<\/span><\/p>\r\n<p>&nbsp;<\/p>\r\n<p><span style=\"font-weight: 400;\">This command gives you insight into the system IP, site ID, and organization name and validates whether the system has joined the overlay.<\/span><\/p>\r\n<h2><b>Troubleshooting Common vEdge Connectivity Issues<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">It\u2019s not uncommon for vEdges to encounter onboarding issues, especially in large or dynamic environments. Here&#8217;s how to approach common problems logically.<\/span><\/p>\r\n<h3><b>Check System and VPN Configurations<\/b><\/h3>\r\n<p>&nbsp;<\/p>\r\n<p><span style=\"font-weight: 400;\">Check for mismatches in organization name, site ID, system IP, and vBond IP address.<\/span><\/p>\r\n<h3><b>Validate Serial Number Authorization<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">Use this command to check the certificate and chassis number registration:<\/span><\/p>\r\n<p>&nbsp;<\/p>\r\n<p><span style=\"font-weight: 400;\">If no certificate appears or if the validity date is incorrect, it&#8217;s likely that the serial number hasn\u2019t been uploaded to vManage or there&#8217;s a time mismatch between devices.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Ensure the device\u2019s serial number is correctly uploaded to vManage and that the device is approved.<\/span><\/p>\r\n<h3><b>Sync Time with NTP<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">Time synchronization is essential for cryptographic operations. If your vEdge router\u2019s time is off, it can\u2019t establish secure connections.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">This ensures the vEdge can retrieve accurate time data from a reliable NTP server.<\/span><\/p>\r\n<h2><b>Configuring Static Routes and Testing Traffic Flow<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Once the control plane is fully established, the next step is to enable data plane traffic. Begin by configuring static routes or dynamic routing protocols, depending on your network design.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Repeat this for each WAN-facing interface. If you&#8217;re using dynamic protocols like OSPF or BGP, additional routing configuration will be required.<\/span><\/p>\r\n<p>&nbsp;<\/p>\r\n<p><span style=\"font-weight: 400;\">This confirms whether routes are being learned and advertised between vEdges and other connected peers.<\/span><\/p>\r\n<h2><b>Testing Overlay Reachability<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Once the vEdges are configured and routing is established, it\u2019s time to test reachability.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">These tools help verify that overlay tunnels are functioning and traffic can flow securely across the WAN fabric.<\/span><\/p>\r\n<p>&nbsp;<\/p>\r\n<p><span style=\"font-weight: 400;\">This displays metrics on tunnel status, uptime, drops, and latency.<\/span><\/p>\r\n<h2><b>Monitoring vEdge Performance<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Real-time monitoring helps you proactively manage device performance. Cisco vEdge CLI provides useful insights into CPU load, memory usage, and interface activity.<\/span><\/p>\r\n<h3><b>Interface Monitoring<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">This provides details on interface status, bandwidth utilization, input\/output rates, and errors.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Look for:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Interface state: should be \u201cup\u201d<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">No CRC or input\/output errors<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Balanced bandwidth usage<\/span><\/li>\r\n<\/ul>\r\n<h3><b>CPU and Memory Usage<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">This reveals information on CPU load averages, memory consumption, and system uptime.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">If CPU or memory usage is unusually high, investigate interface traffic, log files, or connected devices.<\/span><\/p>\r\n<h2><b>Leveraging Real-Time Logging for Troubleshooting<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Enable logging at different levels to understand what\u2019s happening behind the scenes. You can review logs for routing issues, control plane failures, or even physical interface errors.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">This can help identify tunnel flaps or control connection resets. Adjust log levels if you need deeper insights.<\/span><\/p>\r\n<h2><b>Best Practices for Secure and Reliable vEdge Initialization<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">As you onboard more vEdges to your SD-WAN environment, standardizing the initialization process ensures scalability and stability. Consider the following best practices:<\/span><\/p>\r\n<h3><b>Use Configuration Templates in vManage<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">Although this guide focuses on CLI-based configuration, once you\u2019re comfortable with the process, consider migrating to configuration templates in vManage for bulk provisioning. Templates reduce manual errors and maintain consistency across your deployment.<\/span><\/p>\r\n<h3><b>Back Up Configurations<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">After manually configuring a vEdge, save a copy of the configuration using:<\/span><\/p>\r\n<p>&nbsp;<\/p>\r\n<p><span style=\"font-weight: 400;\">You can then copy and paste or redirect this output to a backup file.<\/span><\/p>\r\n<h3><b>Enable Local Authentication for Recovery<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">Although SD-WAN relies heavily on centralized management, local login accounts should be configured on each vEdge to allow access in case of control plane outages.<\/span><\/p>\r\n<p>&nbsp;<\/p>\r\n<h3><b>Secure Access with ACLs and Interface Controls<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">Control access to the vEdge CLI via Access Control Lists (ACLs) or by disabling unused interfaces. This minimizes the attack surface, especially in environments where physical security can\u2019t be guaranteed.<\/span><\/p>\r\n<h2><b>Advanced Features to Explore Post-Initialization<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Once your vEdges are online and fully functional, you can start leveraging advanced SD-WAN capabilities to optimize performance and security.<\/span><\/p>\r\n<h3><b>Implement Traffic Engineering<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">With control policies and application-aware routing, you can steer traffic based on application type, SLA, or performance metrics.<\/span><\/p>\r\n<h3><b>Enable Application-Aware Routing<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">Use performance-based routing to direct business-critical applications over high-quality links and divert less critical traffic over backup paths.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">This can be configured centrally in vManage or manually using CLI control-policy configurations.<\/span><\/p>\r\n<h3><b>Deploy Segmentation with VPNs<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">Use VPN segmentation to separate corporate, guest, and management traffic. Each VPN functions like a virtual routing and forwarding (VRF) instance, enhancing security and isolation.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">Example segments:<\/span><\/p>\r\n<ul>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPN 10 \u2013 Internal applications<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPN 20 \u2013 Guest access<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPN 512 \u2013 Management<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPN 0 \u2013 Transport<\/span><\/li>\r\n<\/ul>\r\n<p><span style=\"font-weight: 400;\">Each can be configured with unique routing, security, and QoS policies.<\/span><\/p>\r\n<h2><b>Using the CLI to Update Software or Reset Configuration<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">There may be times when you need to update the vEdge image or reset the configuration to factory defaults. Both can be done from the CLI.<\/span><\/p>\r\n<h3><b>Software Upgrade via CLI<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">Place the upgrade image on the device using SCP, FTP, or USB, and install using:<\/span><\/p>\r\n<h3><b>Resetting to Factory Defaults<\/b><\/h3>\r\n<p><span style=\"font-weight: 400;\">Warning: This command will remove all saved configurations, certificates, and logs.<\/span><\/p>\r\n<h2><b>CLI Initialization Workflow<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Here\u2019s a quick recap of the steps involved in initializing a vEdge via CLI:<\/span><\/p>\r\n<ol>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Upload vEdge serial file to vManage.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Power on the vEdge and access CLI via console.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Configure system parameters: hostname, system IP, site ID, organization name, and vBond IP.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Set up VPN 0 interfaces for WAN connectivity and default routes.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Configure VPN 512 for out-of-band management.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enable NTP for time synchronization.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Verify control connections to vBond, vSmart, and vManage.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Test overlay tunnels and reachability.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Monitor performance and logs.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n\t<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Apply post-deployment security and segmentation.<\/span><span style=\"font-weight: 400;\"><br \/>\r\n<br \/>\r\n<\/span><\/li>\r\n<\/ol>\r\n<p><span style=\"font-weight: 400;\">Following this structured approach ensures that vEdges integrate smoothly into the SD-WAN fabric.<\/span><\/p>\r\n<h2><b>Final Thoughts<\/b><\/h2>\r\n<p><span style=\"font-weight: 400;\">Initializing Cisco vEdge routers using the CLI offers granular control and a deeper understanding of how SD-WAN functions. Whether you&#8217;re building a lab, running a proof-of-concept, or deploying at scale, mastering the CLI process helps reinforce core SD-WAN principles and prepares you for more complex tasks.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">By ensuring each vEdge is properly configured, tested, and secured, you lay the foundation for a resilient and high-performing SD-WAN infrastructure. While graphical interfaces like vManage simplify large-scale deployments, having command-line expertise allows you to troubleshoot and adapt quickly in dynamic environments.<\/span><\/p>\r\n<p><span style=\"font-weight: 400;\">From basic connectivity to advanced features like segmentation and traffic steering, the vEdge CLI is a powerful tool in the hands of a skilled network engineer. Keep exploring, keep verifying, and always document your configurations for future maintenance and scaling.<\/span><\/p>","protected":false},"excerpt":{"rendered":"<p>The initialization of vEdge devices in a Cisco SD-WAN infrastructure is a foundational step toward building a resilient and secure overlay network. vEdges, as the data plane components of SD-WAN, act as branch routers that ensure connectivity across geographically dispersed locations. They are responsible for handling data traffic, enforcing policies, and participating in secure communication across tunnels established between sites. The process of bringing up these vEdges requires attention to system configuration, secure onboarding, and interface setup. While Cisco SD-WAN supports GUI-based workflows through vManage, using CLI allows network engineers&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-4296","post","type-post","status-publish","format-standard","hentry","category-top-certifications"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Introduction to vEdge Initialization via CLI in Cisco SD-WAN - Prepaway.net<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Introduction to vEdge Initialization via CLI in Cisco SD-WAN - Prepaway.net\" \/>\n<meta property=\"og:description\" content=\"The initialization of vEdge devices in a Cisco SD-WAN infrastructure is a foundational step toward building a resilient and secure overlay network. vEdges, as the data plane components of SD-WAN, act as branch routers that ensure connectivity across geographically dispersed locations. They are responsible for handling data traffic, enforcing policies, and participating in secure communication across tunnels established between sites. The process of bringing up these vEdges requires attention to system configuration, secure onboarding, and interface setup. While Cisco SD-WAN supports GUI-based workflows through vManage, using CLI allows network engineers...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/\" \/>\n<meta property=\"og:site_name\" content=\"Prepaway.net\" \/>\n<meta property=\"article:published_time\" content=\"2025-08-19T06:10:22+00:00\" \/>\n<meta name=\"author\" content=\"admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"16 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/introduction-vedge-initialization-via-cli-cisco-sd-wan\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/introduction-vedge-initialization-via-cli-cisco-sd-wan\\\/\"},\"author\":{\"name\":\"admin\",\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/#\\\/schema\\\/person\\\/e0a7245a2d337c9a15a56ad088fa5797\"},\"headline\":\"Introduction to vEdge Initialization via CLI in Cisco SD-WAN\",\"datePublished\":\"2025-08-19T06:10:22+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/introduction-vedge-initialization-via-cli-cisco-sd-wan\\\/\"},\"wordCount\":3186,\"publisher\":{\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/#organization\"},\"articleSection\":[\"Top Certifications\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/introduction-vedge-initialization-via-cli-cisco-sd-wan\\\/\",\"url\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/introduction-vedge-initialization-via-cli-cisco-sd-wan\\\/\",\"name\":\"Introduction to vEdge Initialization via CLI in Cisco SD-WAN - Prepaway.net\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/#website\"},\"datePublished\":\"2025-08-19T06:10:22+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/introduction-vedge-initialization-via-cli-cisco-sd-wan\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/introduction-vedge-initialization-via-cli-cisco-sd-wan\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/introduction-vedge-initialization-via-cli-cisco-sd-wan\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Introduction to vEdge Initialization via CLI in Cisco SD-WAN\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/#website\",\"url\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/\",\"name\":\"Prepaway.net\",\"description\":\"Pass Your Certification Exam Fast\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/#organization\",\"name\":\"Prepaway.net\",\"url\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/wp-content\\\/uploads\\\/2017\\\/12\\\/logo.png\",\"contentUrl\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/wp-content\\\/uploads\\\/2017\\\/12\\\/logo.png\",\"width\":186,\"height\":38,\"caption\":\"Prepaway.net\"},\"image\":{\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/#\\\/schema\\\/person\\\/e0a7245a2d337c9a15a56ad088fa5797\",\"name\":\"admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/cabb2c6f6d481c521d4ae1af444d5943a73f71d961c761d9dce2bce34b11599b?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/cabb2c6f6d481c521d4ae1af444d5943a73f71d961c761d9dce2bce34b11599b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/cabb2c6f6d481c521d4ae1af444d5943a73f71d961c761d9dce2bce34b11599b?s=96&d=mm&r=g\",\"caption\":\"admin\"},\"url\":\"https:\\\/\\\/www.prepaway.net\\\/certification-training\\\/author\\\/admin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Introduction to vEdge Initialization via CLI in Cisco SD-WAN - Prepaway.net","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/","og_locale":"en_US","og_type":"article","og_title":"Introduction to vEdge Initialization via CLI in Cisco SD-WAN - Prepaway.net","og_description":"The initialization of vEdge devices in a Cisco SD-WAN infrastructure is a foundational step toward building a resilient and secure overlay network. vEdges, as the data plane components of SD-WAN, act as branch routers that ensure connectivity across geographically dispersed locations. They are responsible for handling data traffic, enforcing policies, and participating in secure communication across tunnels established between sites. The process of bringing up these vEdges requires attention to system configuration, secure onboarding, and interface setup. While Cisco SD-WAN supports GUI-based workflows through vManage, using CLI allows network engineers...","og_url":"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/","og_site_name":"Prepaway.net","article_published_time":"2025-08-19T06:10:22+00:00","author":"admin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"admin","Est. reading time":"16 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/#article","isPartOf":{"@id":"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/"},"author":{"name":"admin","@id":"https:\/\/www.prepaway.net\/certification-training\/#\/schema\/person\/e0a7245a2d337c9a15a56ad088fa5797"},"headline":"Introduction to vEdge Initialization via CLI in Cisco SD-WAN","datePublished":"2025-08-19T06:10:22+00:00","mainEntityOfPage":{"@id":"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/"},"wordCount":3186,"publisher":{"@id":"https:\/\/www.prepaway.net\/certification-training\/#organization"},"articleSection":["Top Certifications"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/","url":"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/","name":"Introduction to vEdge Initialization via CLI in Cisco SD-WAN - Prepaway.net","isPartOf":{"@id":"https:\/\/www.prepaway.net\/certification-training\/#website"},"datePublished":"2025-08-19T06:10:22+00:00","breadcrumb":{"@id":"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.prepaway.net\/certification-training\/introduction-vedge-initialization-via-cli-cisco-sd-wan\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.prepaway.net\/certification-training\/"},{"@type":"ListItem","position":2,"name":"Introduction to vEdge Initialization via CLI in Cisco SD-WAN"}]},{"@type":"WebSite","@id":"https:\/\/www.prepaway.net\/certification-training\/#website","url":"https:\/\/www.prepaway.net\/certification-training\/","name":"Prepaway.net","description":"Pass Your Certification Exam Fast","publisher":{"@id":"https:\/\/www.prepaway.net\/certification-training\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.prepaway.net\/certification-training\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.prepaway.net\/certification-training\/#organization","name":"Prepaway.net","url":"https:\/\/www.prepaway.net\/certification-training\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.prepaway.net\/certification-training\/#\/schema\/logo\/image\/","url":"https:\/\/www.prepaway.net\/certification-training\/wp-content\/uploads\/2017\/12\/logo.png","contentUrl":"https:\/\/www.prepaway.net\/certification-training\/wp-content\/uploads\/2017\/12\/logo.png","width":186,"height":38,"caption":"Prepaway.net"},"image":{"@id":"https:\/\/www.prepaway.net\/certification-training\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.prepaway.net\/certification-training\/#\/schema\/person\/e0a7245a2d337c9a15a56ad088fa5797","name":"admin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/cabb2c6f6d481c521d4ae1af444d5943a73f71d961c761d9dce2bce34b11599b?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/cabb2c6f6d481c521d4ae1af444d5943a73f71d961c761d9dce2bce34b11599b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/cabb2c6f6d481c521d4ae1af444d5943a73f71d961c761d9dce2bce34b11599b?s=96&d=mm&r=g","caption":"admin"},"url":"https:\/\/www.prepaway.net\/certification-training\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.prepaway.net\/certification-training\/wp-json\/wp\/v2\/posts\/4296","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.prepaway.net\/certification-training\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.prepaway.net\/certification-training\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.prepaway.net\/certification-training\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.prepaway.net\/certification-training\/wp-json\/wp\/v2\/comments?post=4296"}],"version-history":[{"count":1,"href":"https:\/\/www.prepaway.net\/certification-training\/wp-json\/wp\/v2\/posts\/4296\/revisions"}],"predecessor-version":[{"id":4297,"href":"https:\/\/www.prepaway.net\/certification-training\/wp-json\/wp\/v2\/posts\/4296\/revisions\/4297"}],"wp:attachment":[{"href":"https:\/\/www.prepaway.net\/certification-training\/wp-json\/wp\/v2\/media?parent=4296"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.prepaway.net\/certification-training\/wp-json\/wp\/v2\/categories?post=4296"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.prepaway.net\/certification-training\/wp-json\/wp\/v2\/tags?post=4296"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}