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.
After the SD-AVC Network Service has been set up, use the information in this section to check the prerequisites for Cisco devices in the network to operate with the SD-AVC Network Service. Then activate and configure SD-AVC on the devices. This activates an SD-AVC agent that operates on the devices to communicate with the SD-AVC Network Service.
After configuration is complete, verify the status of each device using the SD-AVC Dashboard. The SD-AVC Dashboard is a tool provided by the SD-AVC Network Service, and displays the details of participating devices, among other things (see Using SD-AVC).
For High Availability SD-AVC, which employs more than one SD-AVC Network Service, see SD-AVC High Availability.
The following table describes the supported platforms and requirements for network devices to operate with SD-AVC. When operating with SD-AVC, network devices run the SD-AVC agent, which manages communication between the devices and the SD-AVC Network Service.
Platform |
OS |
---|---|
Cisco ASR1001-X |
Cisco IOS XE Everest 16.6.1 or later |
Cisco ASR1002-X |
Cisco IOS XE Everest 16.6.1 or later |
Cisco ASR1001-HX |
Cisco IOS XE Everest 16.6.1 or later |
Cisco ASR1002-HX |
Cisco IOS XE Everest 16.6.1 or later |
Cisco ISR4000 Series: 4451, 4321, 4431 |
Cisco IOS XE Everest 16.6.1 or later |
Cisco Cloud Services Router CSR1000V |
Cisco IOS XE Everest 16.6.1 or later |
Cisco Route Processor RP2, operating on Cisco ASR1004, ASR1006, or ASR1013 |
Cisco IOS XE Everest 16.6.1 or later |
Cisco Route Processor RP3, operating on Cisco ASR1004, ASR1006, or ASR1013 |
Cisco IOS XE Everest 16.6.1 or later |
For connectivity requirements and procedures, see Configuring Connectivity.
Network devices participating with SD-AVC run an SD-AVC agent (see SD-AVC Architecture).
SD-AVC functionality depends on receiving application statistics from each participating network device. Application statistics are collected on each interface (on participating devices) on which one of the following is enabled: Cisco Performance Monitor, Easy Performance Monitor (ezPM), PfR policy, or Protocol Discovery
Depending on the Cisco solution in place, application statistics must be collected as follows:
IWAN solution: (No additional user configuration required) Collection of application statistics is enabled by the use of Easy Performance Monitor (ezPM) and PfR policy.
Application Assurance solution: (No additional user configuration required) Collection of application statistics is enabled by the use of Performance Monitor or Easy Performance Monitor (ezPM), and PfR policy.
EasyQoS: (Requires user configuration) Configure Protocol Discovery on WAN-side interfaces.
Use the following procedure on a device in the network to activate the SD-AVC agent, enabling the device to communicate with the SD-AVC Network Service.
Note | See System Requirements for network devices operating with SD-AVC . |
Note | The term, SD-AVC Network Service, refers to the virtual service that operates on a host device and performs SD-AVC functions, such as aggregating application data. The avc sd-service command used in this procedure does not refer to the SD-AVC Network Service. |
Activate SD-AVC.
avc sd-serviceExample:
conft#avc sd-service
Configure the segment (group of devices that share the same purpose, such as routers within the same hub).
segment ciscoExample:
(config-sd-service)#segment cisco
Enter controller mode to configure the agent to use the SD-AVC Network Service (not related to the avc sd-service command used in an earlier step).
controllerExample:
(config-sd-service)#controller
Enter the service-IP used when the SD-AVC Network Service (running on a host device) was set up.
address service-ipNote | For a high availability (HA) configuration, more than one SD-AVC Network Service is specified in this step. See SD-AVC High Availability for details. |
Example:
(config-sd-service-controller)#address 10.56.196.146
Configure VRF.
vrf vrf_mgmtExample:
(config-sd-service-controller)#vrf vrf_mgmt
The device is now configured to operate with SD-AVC, and begins:
Sending collected application data to the SD-AVC Network Service
Receiving application rules packs periodically from the SD-AVC Network Service
Using the SD-AVC Dashboard, in the Connectivity tab, confirm that the router appears in the hostname list, and that the “Exporter Health” column shows a green checkmark.
Note | If the tabs are hidden, click the menu button to display them. |
The following is an example of the CLI steps used to configure the SD-AVC agent on a device.
conft#avc sd-service (config-sd-service)#segment cisco (config-sd-service)#controller (config-sd-service-controller)#address 10.56.196.146 (config-sd-service-controller)#vrf vrf_mgmt
Use the following procedure on a device in the network to deactivate the SD-AVC agent and clear any SD-AVC agent configuration details that have been entered. This stops SD-AVC functionality on the device, and the device stops communicating with the SD-AVC network service.
Deactivate SD-AVC and remove SD-AVC agent configuration.
no avc sd-serviceExample:
conft#no avc sd-service