Enable Cisco SD-AVC Cloud Connector, through Cisco Catalyst SD-WAN Manager Release 20.13.x

Information about enabling Cisco SD-AVC Cloud Connector, through Cisco Catalyst SD-WAN Manager Release 20.13.x.

Before Cisco vManage Release 20.10.1, enabling Cloud Connector required client ID and client secret credentials. From Cisco vManage Release 20.10.1, it requires a cloud gateway URL and OTP. An advantage to using an OTP is that, in contrast to a client secret, it does not expire. See the following table for details about the credentials required for different releases, upgrade scenarios, and hosting options.
Cisco SD-AVC Cloud Connector is a necessary component for Cloud onRamp for SaaS to manage Office 365 traffic according to the Office 365 traffic category.

Before you begin

Table 1. Requirements to Enable SD-AVC Cloud Connector
Releases	Cisco SD-WAN Manager Hosting	Requirements to Enable Cloud Connector
Cisco vManage Release 20.3.1 to Cisco vManage Release 20.9.x	All hosting options	Required credentials: Client ID Client secret (As explained in the procedure, open the Cisco API Console page to create Cloud Connector credentials if you do not already have credentials.) Note When you receive a message in Cisco SD-WAN Manager indicating that SD-AVC credentials are expiring, return to the Cisco API Console and create new Cloud Connector credentials. Other requirements: Enable SD-AVC in cluster management, as described here.
Upgrade an existing instance to Cisco vManage Release 20.10.1 from an earlier release	All hosting options	Note In this scenario, the SD-AVC components operate differently than in earlier releases. Consequently, running the request nms all status command on the Cisco SD-WAN Manager instance shows that the “NMS SDAVC server” component is not enabled. This is expected behavior, and does not indicate any problem with SD-AVC. Note that the “NMS SDAVC gateway” component shows as enabled.
	Cisco-hosted	Required credentials: Cloud gateway URL: Use: https://datamanagement-us-01.sdwan.cisco.com/validate_sdavc/ OTP: Use the Cisco Catalyst SD-WAN Portal to get the OTP. See the Cisco Catalyst SD-WAN Portal Configuration Guide for details. Other requirements: Enable SD-AVC in cluster management, as described here.
	Self-managed, hosted in a public cloud, a private cloud, or on-premises	Required credentials: If Cloud Connector was already enabled at the time of the upgrade, the client ID and client secret credentials continue to work until the client secret expires. When the client secret expires, an alarm appears in Cisco SD-WAN Manager to indicate the expiration. At this point, enabling Cloud Connector requires the cloud gateway URL and OTP. Use datamanagement-us-01.sdwan.cisco.com for the URL, and open a TAC case to get the OTP. See the procedure in this section for information about opening a TAC case. If Cloud Connector was not enabled at the time of the upgrade, enabling Cloud Connector requires the cloud gateway URL and OTP. Use datamanagement-us-01.sdwan.cisco.com for the URL, and open a TAC case to get the OTP. See the procedure in this section for information about opening a TAC case. Other requirements: Before enabling the Cloud Connector, enable SD-AVC in cluster management, as described here.
Fresh installation of Cisco vManage Release 20.10.1 and later	Cisco-hosted	Required credentials: Cloud Connector is enabled by default, without requiring manual entry of credentials. You can use the Cisco Catalyst SD-WAN Portal to view the OTP if needed. See the Cisco Catalyst SD-WAN Portal Configuration Guide for details. Other requirements: Enable SD-AVC in cluster management, as described here. Notes: In this scenario, the SD-AVC components operate differently than in earlier releases. Consequently, running the request nms all status command on the Cisco SD-WAN Manager instance shows that the “NMS SDAVC server” component is not enabled. This is expected behavior, and does not indicate any problem with SD-AVC. Note that the “NMS SDAVC gateway” component shows as enabled.
	Self-managed, hosted in a public cloud, a private cloud, or on-premises	Required credentials: Cloud gateway URL: Use https://datamanagement-us-01.sdwan.cisco.com/validate_sdavc/ OTP: Open a TAC case to get the OTP. See the procedure in this section for information about opening a TAC case. Other requirements: Enable SD-AVC in cluster management, as described here.

Procedure

	1.	From the Cisco SD-WAN Manager menu, choose Administration > Settings.
	2.	Click SD-AVC and enable Cloud Connector. (If you are using Cisco vManage Release 20.10.x, Cisco vManage Release 20.11.x, or Cisco Catalyst SD-WAN Manager Release 20.12.x, click Edit and enable Cloud Connector.) (In Cisco vManage Release 20.9.x and earlier releases, the option is called SD-AVC Cloud Connector. In these releases, click Edit and enable Cloud Connector.) Note If Cisco SD-WAN Manager is cloud-hosted by Cisco, this option does not appear and Cloud Connector is enabled automatically.
	3.	Do one of these: If you need to enter the cloud gateway URL, use: datamanagement-us-01.sdwan.cisco.com If you need to use the Cisco Catalyst SD-WAN Portal to get the OTP, see the Cisco Catalyst SD-WAN Portal Configuration Guide for details. If you need to open a TAC case to receive the OTP, open https://mycase.cloudapps.cisco.com/case. The workflow for receiving the OTP requires these: Entitlement information. Smart Account. Virtual Account. The organization name configured in Cisco SD-WAN Manager. Cisco SD-WAN Manager geographic location: Americas, European Union (EU), or Asia-Pacific (APAC). Technology: Use Cisco Catalyst SD-WAN On-Prem for an on-prem installation or Cisco Catalyst SD-WAN - Cisco-Hosted for a Cisco-hosted installation. SubTechnology: Use SDWAN Cloud Infra. This step applies to Cisco vManage Release 20.10.1 and later, and is handled automatically if Cisco SD-WAN Manager is Cisco-hosted. Refer to the information that precedes these steps for details about the requirements for enabling the SD-AVC Cloud Connector in different scenarios. As noted there, enable SD-AVC in cluster management before enabling the Cloud Connector.
	4.	(For Cisco vManage Release 20.9.x and earlier releases) Enter these credentials: Client ID Note Click (i) for Client ID and open the Cisco API Console page in a browser window to create Cloud Connector credentials if you do not already have credentials. Client Secret Organization Name: Use the descriptive name that you entered on the Cisco API Console page in the Name of your application field.
	5.	(Releases earlier than Cisco vManage Release 20.10.1) For Affinity, you can select a geographical location for storing the Cloud Connector data. For organizations located in Europe, it is recommended to change the location to Europe, in accordance with EU General Data Protection Regulation (GDPR) regulations.
	6.	For Telemetry, you can optionally disable the collection of telemetry data. Note If Cisco SD-WAN Manager is cloud-hosted by Cisco, this option does not appear and telemetry is enabled automatically.

Before you begin

Procedure

What to do next