Configure Telemetry

About Application Telemetry

Application telemetry allows you to configure global network settings on devices for monitoring and assessing their health.

Configure Syslog, SNMP Traps, NetFlow Collector Servers, and Wired Client Data Collection Using Telemetry

With Cisco DNA Center, you can configure global network settings when devices are assigned to a specific site. Telemetry polls network devices and collects telemetry data according to the settings in the SNMP server, the syslog server, the NetFlow Collector, or the wired client.

Before you begin

Create a site and assign a device to the site. See Create a Site in a Network Hierarchy.

Procedure

Step 1

In the Cisco DNA Center GUI, click the Menu icon () and choose Design > Network Settings > Telemetry.

Step 2

Expand the SNMP Traps area if it is not visible and do one of the following:

  1. Check the Cisco DNA Center as SNMP trap server check box.

  2. Check the Add an external SNMP trap server check box and enter the IP address of the external SNMP trap server.

    The selected server collects SNMP traps and messages from the network devices.
Step 3

Expand the Syslogs area if it is not visible and do one of the following:

  1. Check the Use Cisco DNA Center as syslog server check box.

  2. Check the Add an external syslog server check box and enter the IP address of the external syslog server.

Step 4

Expand the NetFlow area if it is not visible and do one of the following:

  1. Check the Use Cisco DNA Center as NetFlow collector server check box.

    The NetFlow configuration on the device interfaces is completed only when you enable application telemetry on the device. Select the NetFlow collector at the site level to configure the NetFlow destination server to the device.

  2. Check the Add an external NetFlow collector server check box and enter the IP address and port number of the NetFlow Collector server.

    The selected server is the destination server for NetFlow export from the network devices. If the NetFlow Collector is not selected, the application telemetry enablement will not work.

Step 5

Expand the Wired Client Data Collection area and check the Monitor wired clients check box.

This selection turns on IP Device Tracking (IPDT) on the access devices of the site.

By default, IPDT is disabled for the site.
Step 6

Click Save.

Criteria for Enabling Application Telemetry on Devices

Cisco DNA Center automatically enables application telemetry on all applicable interfaces or WLANs that are selected based on the new automatic interfaces or WLAN selection algorithm.

Application telemetry is pushed to WLANs that are provisioned through Cisco DNA Center.


Note

  • The conventional tagging-based algorithm is supported and has precedence over the new automatic interfaces or WLAN selection algorithm.

  • If you want to switch over from automatic selection algorithm to tagging-based algorithm, you must disable telemetry before provisioning the tagged SSIDs to the devices.

The following table provides the criteria for selecting interfaces and WLANs based on the conventional tagging-based algorithm (with keyword lan) and the new automatic selection algorithm for all the supported platforms:

Platform Conventional Tagging-Based Algorithm Supported on Cisco DNA Center 2.1.2 and Earlier Automatic Selection Algorithm Supported on Cisco DNA Center 2.1.2 and Later

Router

  • Interface description has the keyword lan.1,2

  • Is a physical interface.

  • The interface has an IP address other than the management IP address.

  • The interface has an IP address other than the management IP address.

  • The interface is not any of the following:

    • WAN

      Note 

      An interface is treated as a WAN-facing interface if it has a public IP address, and if there is a route rule with a public IP address that routes through the interface.

      In this context, a public IP address is not in a private range (for example, not in 192.168.x.x, 172.16.y.y, 10.z.z.z), or is an IP address that is not in the system's IP pools.

      Route rules can be dynamically learned. In this context, "show ip route" does not show a route to a public IP address that goes through this interface.

    • Loopback.

    • Management interface: IGABITETHERNET0, GIGABITETHERNET0/0, MGMT0, FASTETHERNET0, or FASTETHERNET1.

Switch

  • Interface description has the keyword lan.1, 2

  • Switch port is configured as an access port.

  • Command switch-mode access is configured on the switch port.

  • Is a physical interface

  • Access port does not have neighbors.

  • The interface is not any of the following:

    • Management interface: FASTETHERNET0, FASTETHERNET1, GIGABITETHERNET0/0, or MGMT0

    • LOOPBACK0, Bluetooth, App Gigabit, WPAN, Cellular, or Async

    • VSL interface.

Cisco AireOS Controller

  • WLAN profile name is tagged with the keyword lan.1, 2

  • Not a Guest SSID:

    • The type of WLAN is not Guest.

    • The name of the SSID does not contain the keyword Guest.

  • The SSID is configured in Local mode.

Cisco Catalyst 9800 Series Wireless Controller with Optimized Application Performance Monitoring (APM) profile and IOS release 16.12.1 and later.

Supported from Cisco DNA Center 2.1.2.

  • WLAN profile name is tagged with the keyword lan.1, 2

  • WLAN is configured in Local mode.

  • Not a Guest SSID:

    • The type of WLAN is not Guest.

    • The name of the SSID does not contain the keyword Guest.

  • If the SSIDs are mixed, that is Local mode, Flex mode, and Fabric mode, the Cisco Application Visibility and Control (AVC) basic record is configured. If all the SSIDs are in Local mode, the Optimized APM record is configured.

Note 
If you want to update the telemetry configuration, you must disable telemetry and then enable it after making the configuration changes.

Cisco DNA Traffic Telemetry Appliance with Optimized APM profile and IOS release 17.3 and later.

Supported from Cisco DNA Center 2.1.2.

  • Interface description has the keyword lan.1, 2

  • Is a physical interface.

  • Is a physical interface.

  • Is not a management interface: GIGABITETHERNET0, GIGABITETHERNET0/0, MGMT0, FASTETHERNET0, and FASTETHERNET1.
1 The keyword lan is case insensitive and can be separated by a space, hyphen, or underscore. In Cisco DNA Center, you can add the lan keyword in the first 10 characters of the SSID name. Alternately, you can use the device's web UI to add the lan keyword.
2 Resynchronize the network device to read the lan interface description.

Provision Application Telemetry Settings

Configure global telemetry settings as described in Configure Syslog, SNMP Traps, NetFlow Collector Servers, and Wired Client Data Collection Using Telemetry.

Procedure

Step 1

In the Cisco DNA Center GUI, click the Menu icon () and choose Provision > Inventory.

The Inventory page displays the device information gathered during the Discovery process. To view devices available in a particular site, expand the Global site in the left pane, and select the site, building, or floor.

Step 2

Choose the devices that you want to provision.
Step 3

From the Actions drop-down list, choose Telemetry and do one of the following:

Note 
The application telemetry option is enabled only if the device supports application telemetry enablement from Cisco DNA Center.

  1. Enable Application Telemetry: To configure application telemetry for the selected devices.

  2. Disable Application Telemetry: To remove the application telemetry configuration from the chosen devices.

Step 4

Click Apply.

The Application Telemetry column shows the telemetry configuration status. If you don’t see the Application Telemetry column in the default column setting, click the More icon () at the right end of the column headings and check the Application Telemetry check box.

Update Telemetry Settings to Use a New Cluster Virtual IP Address

If you are using the Cisco DNA Center application telemetry to monitor device data, and you need to change the Cisco DNA Center cluster virtual IP address (VIP), complete the following steps to change the VIP and to ensure that node telemetry data is sent to the new VIP.

Before you begin

  • Determine the version of Cisco DNA Center that you are using. You can check this by logging in to the Cisco DNA Center GUI and using the About option to view the Cisco DNA Center version number.

  • Obtain SSH client software.

  • Identify the VIP address that was configured for the 10-GB interface facing the enterprise network on the Cisco DNA Center primary node. Log in to the appliance using this address, on port 2222. To identify this port, see the rear-panel figure in the "Front and Rear Panels" section in the Cisco DNA Center Installation Guide.

  • Obtain the Linux username (maglev) and password configured on the primary node.

  • Identify the cluster VIP that you want to assign. The cluster VIP must conform to the requirements explained in the "Required IP Addresses and Subnets" section in the Cisco DNA Center Installation Guide.

Procedure

Step 1

Access the Cisco DNA Center GUI and Disable Application Telemetry at all the sites, as follows:

  1. In the Cisco DNA Center GUI, click the Menu icon () and choose Provision > Inventory > Provision.

    The Inventory page displays the device information gathered during the Discovery process. To view devices available in a particular site, expand the Global site in the left pane, and select the site, building, or floor.

  2. Choose all the sites and devices currently being monitored.

  3. From the Actions drop-down list, choose Telemetry > Disable Application Telemetry.

  4. Wait for the sites and devices to show that telemetry has been disabled.
Step 2

Use the appliance Configuration wizard to change the cluster VIP, as follows:

  1. Using an SSH client, log in to the VIP address that was configured for the 10-GB interface facing the enterprise network on the Cisco DNA Center primary node. Be sure to log in on port 2222.

  2. When prompted, enter the Linux username and password.

  3. Enter the following command to access the Configuration wizard on the primary node:

    $ sudo maglev-config update

    If you are prompted for the Linux password, enter it again.

  4. Click [Next] until the screen prompting you for the cluster virtual IP appears. Enter the new cluster VIP, then click [Next] to proceed through the remaining screens of the wizard.

    You must configure one virtual IP per configured interface. We recommend that you enter the sudo maglev-config update command so that the wizard prompts you to provide one VIP per configured interface.

    When you reach the final screen, a message appears, stating that the wizard is ready to apply your changes.

  5. Click [proceed] to apply the cluster VIP change.

    At the end of the configuration process, a success message appears and the SSH prompt reappears.
Step 3

Restart the necessary Cisco DNA Center services by entering the following series of commands at the SSH prompt: 

magctl service restart -d collector-netflow
magctl service restart -d collector-syslog
magctl service restart -d collector-trap
magctl service restart -d wirelesscollector
Step 4

Wait for all the services to restart. You can monitor the progress of the restarts by entering the following command, substituting service names as needed for the release train appropriate for your Cisco DNA Center version. 

magctl appstack status | grep -i -e collector-netflow -e collector-syslog -e collector-trap -e wirelesscollector

When all the necessary services are running, you see command output similar to the following, with a Running status for each service that has restarted successfully: 

assurance-backend  wirelesscollector-123-bc99s  1/1   Running   0   25d   <IP>   <IP>
ndp   collector-netflow-456-lxvlx   1/1   Running   0   1d   <IP>   <IP>
ndp   collector-syslog-789-r0rr1    1/1   Running   0   25d   <IP>   <IP>
ndp   collector-trap-101112-3ppllm  1/1   Running   0   25d   <IP>   <IP>
Step 5

Access the Cisco DNA Center GUI and Enable Application Telemetry to all nodes as follows:

  1. In the Cisco DNA Center GUI, click the Menu icon () and choose Provision > Inventory > Provision.

  2. Choose all the sites and devices that you want to monitor.

  3. From the Actions drop-down list, choose Telemetry > Enable Application Telemetry.

  4. Wait for the sites and devices to show that telemetry has been enabled.

Update Device Configuration Using Telemetry

You can push the configuration changes to a device irrespective of whether the device controllability is enabled or disabled.

Procedure

Step 1

In the Cisco DNA Center GUI, click the Menu icon () and choose Provision > Inventory.

The Inventory page displays the device information gathered during the Discovery process. To view devices available in a particular site, expand the Global site in the left pane, and select the site, building, or floor.

Step 2

Choose the devices that you want to update the configuration changes.
Step 3

From the Actions drop-down list, choose Telemetry > Update Telemetry Settings.

Step 4

In the Update Telemetry Settings window, do the following:

  • (Optional) Check the Force Configuration Push check box to push the configuration changes to the device. If there is no change in the configuration settings, the existing configuration is pushed again to the device.

  • Click Next.

  • Click the Now radio button or click the Later radio button and specify the date and time to update the telemetry settings.

Step 5

Click Apply.