Send SD-WAN Syslog Events to Cisco Cloud
Before you begin
This procedure assumes that you are using Cisco Cloud Service Routers (CSRv) in an SD-WAN setup that you manage using the Cisco vManage dashboard.
Review the following prerequisites before performing the procedure:
-
Ensure your SecureX and CDO accounts are merged. To know how, see Merge Your CDO and SecureX Accounts.
-
Ensure you have SecureX enabled on your CDO tenant in .
-
You should have a vSphere Client with the following specifications: 6 vCPU, 10GB of memory, and 64GB disk space.
Procedure
Step 1 | Deploy an on-premises Secure Event Connector on your vSphere using a CDO Connector VM image by following the procedures in Installing an SEC Using a CDO Image. |
Step 2 | On your Cisco vManage, create a logging template that gets deployed to the Cloud Services Routers and a Unified Threat Defense (UTD) template that enables forwarding of events to the configured syslog server, which is the SEC in this case. For more information, see Cisco SD-WAN Systems and Interfaces Configuration Guide and Create Unified Security Policy Summary in the Cisco SD-WAN Security Configuration Guide. |
Step 3 | The SEC needs to be specified as a syslog server in the logging template, for it to receive events. To do this, use the CLI configuration when creating the template in vManage. For example, you can use the following commands, specifying the IP address of the SEC:
|
Step 4 | On your SEC, set an IP table rule to redirect logs from port 514 (UDP) to port 10025 (UDP), so that the SEC receives logs from vManage:
You can check if the IP table rules are updated, using the |
Step 5 | Add the following lines of code in the configuration file —
You should now start receiving SD-WAN events, which you can look at and analyze from CDO. |