02-19-2024 07:04 PM
Hello, has anyone tried enabling telemetry on eWLCs? I have 5 9120s in my home and i am trying to get this up and running as i am starting to play with grafana, influx, and telegraf. I have been successful in getting my 9300 switch to stream to my collector but this AP for some reason does not establish a connection at all. I havent been able to find any relevant debugs to get an idea what is going on either.
Appreciate any feedback!
From AP:
OCE-eWLC#show telemetry ietf subscription summary
Subscription Summary
====================
Maximum supported: 128
Subscription Total Valid Invalid
-----------------------------------------------
All 1 1 0
Dynamic 0 0 0
Configured 1 1 0
Permanent 0 0 0
OCE-eWLC#show telemetry ietf subscription 1 receiver
Telemetry subscription receivers detail:
Subscription ID: 1
Name: grpc-tcp://192.168.254.252:57000
Connection: 65535
State: Disconnected
Explanation: Receiver invalid
OCE-eWLC#show telemetry ietf subscription 1 detail
Telemetry subscription detail:
Subscription ID: 1
Type: Configured
State: Valid
Stream: yang-push
Filter:
Filter type: xpath
XPath: /wireless-client-oper:client-oper-data
Update policy:
Update Trigger: periodic
Period: 500
Encoding: encode-kvgpb
Source VRF:
Source Address: 192.168.252.2
Notes: Subscription validated
Named Receivers:
Name Last State Change State Explanation
-------------------------------------------------------------------------------------------------------------------------------------------------------
grpc-tcp://192.168.254.252:57000 02/19/24 19:54:37 Disconnected Receiver invalid
OCE-eWLC#sh run | sec tele
telemetry ietf subscription 1
encoding encode-kvgpb
filter xpath /wireless-client-oper:client-oper-data
source-address 192.168.252.2
stream yang-push
update-policy periodic 500
receiver ip address 192.168.254.252 57000 protocol grpc-tcp
From 9300 Switch
OCEHomeSw# show telemetry ietf subscription 1 receiver
Telemetry subscription receivers detail:
Subscription ID: 1
Name: grpc-tcp://192.168.254.252:57000
Connection: 2200
State: Connected
Explanation:
OCEHomeSw# show telemetry ietf subscription 1 detail
Telemetry subscription detail:
Subscription ID: 1
Type: Configured
State: Valid
Stream: yang-push
Filter:
Filter type: xpath
XPath: /process-cpu-ios-xe-oper:cpu-usage/cpu-utilization/five-seconds
Update policy:
Update Trigger: periodic
Period: 500
Encoding: encode-kvgpb
Source VRF:
Source Address: 192.168.254.2
Notes: Subscription validated
Named Receivers:
Name Last State Change State Explanation
-------------------------------------------------------------------------------------------------------------------------------------------------------
grpc-tcp://192.168.254.252:57000 02/19/24 21:28:04 Connected
OCEHomeSw#sh run | sec tele
telemetry ietf subscription 1
encoding encode-kvgpb
filter xpath /process-cpu-ios-xe-oper:cpu-usage/cpu-utilization/five-seconds
source-address 192.168.254.2
stream yang-push
update-policy periodic 500
receiver ip address 192.168.254.252 57000 protocol grpc-tcp
Solved! Go to Solution.
02-21-2024 09:05 AM
I don't think it's possible to do that.
See https://www.cisco.com/c/en/us/td/docs/wireless/controller/ewc/17-9/config-guide/ewc_cg_17_9/m_ewc_network_monitoring.html
The only network monitoring supported on the Embedded Wireless Controller (EWC) is through Cisco Digital Network Architecture (DNA) Center. This is done through NETCONF using a propietary protocol for push and pull of configuration or status information.
Note |
Although you can run telemetry commands on EWC, monitoring is only supported through DNA, which is done through NETCONF. |
02-20-2024 04:14 AM
- A full list of telemetry debugging command is available below ; also go for advisory release on the eWLC if not yet done (17.9.4a)
show telemetry ietf subscription all (DNA related)
show telemetry ietf subscription 23 detail
show telemetry internal subscription all stats
show telemetry internal connection <0-4294967294> detail
show telemetry ietf subscription configured
show iox detail
M.
02-21-2024 09:05 AM
I don't think it's possible to do that.
See https://www.cisco.com/c/en/us/td/docs/wireless/controller/ewc/17-9/config-guide/ewc_cg_17_9/m_ewc_network_monitoring.html
The only network monitoring supported on the Embedded Wireless Controller (EWC) is through Cisco Digital Network Architecture (DNA) Center. This is done through NETCONF using a propietary protocol for push and pull of configuration or status information.
Note |
Although you can run telemetry commands on EWC, monitoring is only supported through DNA, which is done through NETCONF. |
02-21-2024 06:48 PM
Wow thank you for the reference. Man this is a blow. I went from a 9800cl to the EWC, looks like I need to get the CL back up and running again.
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