Verify the deployment of SD-WAN Control Component s in AWS

Updated: July 7, 2026

Want to summarize with AI?

Provides instructions for validating the deployment of SD-WAN Control Components in AWS, ensuring all components operate as expected and the cloud installation is functional.

This topic describes how to verify the deployment of SD-WAN Control Components in AWS.

Before you begin

Infrastructure: To verify the deployment of SD-WAN Control Components in AWS, use the AWS portal to confirm that the virtual machines hosting each SD-WAN Control Component are active.

Services: To verify that Cisco Catalyst SD-WAN services are operating after deployment of the SD-WAN Control Components, follow these steps.

Procedure

	1.	Check for a successful ping to the virtual machine that hosts Cisco SD-WAN Manager .
	2.	Log in to the controller instance using AWS console with user as admin. You may be prompted to configure a new password. Once configured, verify login via SSH to the public IP of the controller.
	3.	Use SSH to connect to SD-WAN Manager, and use the request nms all status command. The output shows the status of all the SD-WAN Manager services. Confirm that the application server is active. The following excerpt of the request nms all status command output shows that the application server is active: `vmanage# request nms all status NMS service proxy Enabled: true Status: running PID:2881 for 9479s NMS service proxy rate limit Enabled: true Status: running PID:4359 for 9521s NMS application server Enabled: true Status: running PID:6131 for 9419s ...`
	4.	After installing the SD-WAN Control Components, follow the steps in Cisco SD-WAN Overlay Network Bring-Up Process to establish the control connections for the SD-WAN Control Components and to verify that each SD-WAN Control Component is operational.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.