ZTP Process Overview–Pure Play Viptela operating system

When using vEdge, it will use ZTP, the following steps are:

1. Router reaches out to ztp.viptela.com
2. Public Validator will then redirect to the appropriate Validator.
3. Then the whitelist/blacklist approval process before receiving the device config from Manager.
4. Full config and registration is then completed.

Cisco Plug-and-Play Process Overview

1. Customer or Partner creates an order on Cisco Commerce Workspace (CCW) and the order will belong to th Smart Account.
2. Cisco team defines the Org name and deploys the SD-WAN Controllers in the Public Cloud, by default you will receive one Manager, Controller and Validator. The one Validator and Controller in a secondary region.
3. The Smart Account info and overlay info is synchronised to the PnP Connect Service and ZTP servers even though ZTP belongs to vEdge only.
4. PnP belongs to cEdge only.
5. WAN edges whether its cEdge or vEdge will learn the IP address of the Validator.
6. Manager will synchronise Smart Account information directly from the PnP Connect service which in turn will download the WAN Edge allowed list.
7. WAN Edge connects to the Validator and begins the on boarding process.

I use to do this all the time and never really understood what it’s for. Well I do now!

• Compute and Data – Includes all services that are required for Manager, includes services for Application, statistics, configuration, messaging, and coordination. This persona should be used for a standalone node, and for the first node in a vManage cluster.
• Compute: Includes services that are used for the application, configuration, messaging, and coordination. This persona does not include services that are used for statistics. A node with this persona cannot operate as a standalone node and must be part of a vManage cluster.
• Data: Includes only services that are used for the application and statistics. A node with this persona cannot operate as a standalone node and must be part of a vManage cluster.

• Statistics Database: Stores statistics from all the Cisco Catalyst SD-WAN devices in the network.
• Configuration Database: Stores all the device and feature templates and configurations for all the Cisco Catalyst SD-WAN devices in the network.
• Messaging Server: Distributes messages and shares state among all the Cisco SD-WAN Manager cluster members.

Tenancy Models

• Per Overlay Tenancy – where the controllers are shared except for the Wan edge which is dedicated per customer
• Per VPN Tenancy – where controllers and WAN edges are share but PVN segments are dedicated per customer.

SD-WAN Multitenancy vSmart Resilience

When a tenant shares the Controller, Manager will choose the lease two loaded Controllers and assigns them to the tenant. In v20.9.1, you can choose which Controllers the tenant can use. This acts in Active-active customers and only 2 Controllers per tenant. Each pair of Controllers can serve 24 tenants.

Follow these steps to deploy the SD-WAN controllers in a cloud:

1. First, create information about the customer and overlay network in Cisco Commerce to seamlessly integrate Cisco Plug and Play (PnP) into the solution.
2. To establish the network automatically, complete the setup on Cisco PnP. Certificates use the DigiCert CA infrastructure, and customers are not required to maintain the CA. Certain IP prefixes in the setup must be allowed explicitly for permission to access the setup. Also, this information is required in the overlay setup. The final bring-up of the overlay requires some networking configuration.
3. The controllers check whether a connecting WAN Edge device belongs to the network. To allow this operation, the customer supplies a list of WAN Edge routers in the viptela file format, which includes the serial numbers of the WAN Edge routers. The customer must supply this list to allow the WAN Edge routers to join the overlay.

Elastic IPs means the IP address belongs to the customer only and stays with the customer.