10-06-2021 05:30 AM
When enabling application telemetry on our 9300 switches some are reporting 'No Telemetry-applicable interfaces found!'.' Other 9300s running the same (16.12.4) or older (16.9.4) versions of IOS-XE are fine. I have had a look at the port configurations on the failing switches and can see no difference between these and the enabled switches.
Any pointers to why we are unable to enable telemetry on these switches would be appreciated.
Solved! Go to Solution.
10-11-2021 12:22 AM
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 inside the first 10 characters of the SSID name. Alternately, you can use the device's web UI to add the lan keyword.
Thats from the telemetry documentation.
10-11-2021 01:39 AM
Hi
I have added LAN to the port description but it does not work. We have other 9300 switches that have telemetry enabled that do not have LAN in the description. The issue is with switch ports, not an SSID.
The switches that do have telemetry enabled also have data & voice VLANs configured, example below.
interface GigabitEthernet1/0/10
description ***PC/IP Phone Port***
switchport access vlan 20
switchport mode access
switchport voice vlan 101
switchport port-security maximum 3
switchport port-security aging time 2
switchport port-security aging type inactivity
switchport port-security
device-tracking attach-policy IPDT_POLICY
ip flow monitor dnacmonitor input
ip flow monitor dnacmonitor output
trust device cisco-phone
auto qos voip cisco-phone
spanning-tree portfast
spanning-tree bpduguard enable
service-policy input AutoQos-4.0-CiscoPhone-Input-Policy
service-policy output AutoQos-4.0-Output-Policy
This also shows that LAN/lan is not in the description.
10-07-2021 07:59 AM
What version fo DNAC are you running?
What is the license level on the switch?
Could you share the interface configuration?
10-08-2021 01:06 AM
Hi Rasmus, thanks for responding.
DNA version is 2.2.2.5
License level is DNA Advantage.
Interface configuration is typically:
interface GigabitEthernet1/0/10
description **PC/IP Phone Port LAN**
switchport access vlan 10
switchport mode access
switchport voice vlan 201
switchport port-security maximum 3
switchport port-security aging time 2
switchport port-security aging type inactivity
switchport port-security
device-tracking attach-policy IPDT_POLICY
spanning-tree portfast
spanning-tree bpduguard enable
end
This particular switch has 24 ports. Ports 2 to 23 are configured in this way. I added 'LAN' to the port description as I read that this maybe needed. I did wonder if the port security maybe the reason as this was not set on another switch that has telemetry enabled successfully, so did remove this from one port but this did not make any difference.
Rgds
Steve
10-11-2021 12:00 AM
Hi,
I have had a few problems with telemetry on wired ports, works very well with WiFi, wired not so much so.
Try putting the description as "lan" in lower case. The other thing it could is that a voice and data port is technically a trunk, but thats conjecture.
10-11-2021 12:22 AM
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 inside the first 10 characters of the SSID name. Alternately, you can use the device's web UI to add the lan keyword.
Thats from the telemetry documentation.
10-11-2021 01:39 AM
Hi
I have added LAN to the port description but it does not work. We have other 9300 switches that have telemetry enabled that do not have LAN in the description. The issue is with switch ports, not an SSID.
The switches that do have telemetry enabled also have data & voice VLANs configured, example below.
interface GigabitEthernet1/0/10
description ***PC/IP Phone Port***
switchport access vlan 20
switchport mode access
switchport voice vlan 101
switchport port-security maximum 3
switchport port-security aging time 2
switchport port-security aging type inactivity
switchport port-security
device-tracking attach-policy IPDT_POLICY
ip flow monitor dnacmonitor input
ip flow monitor dnacmonitor output
trust device cisco-phone
auto qos voip cisco-phone
spanning-tree portfast
spanning-tree bpduguard enable
service-policy input AutoQos-4.0-CiscoPhone-Input-Policy
service-policy output AutoQos-4.0-Output-Policy
This also shows that LAN/lan is not in the description.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide