Cannot receive flow data via telemetry from Cisco ISR 4321
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2022 12:29 PM
We have a Cisco ISR4321/K9 (v16.12.2s) in our lab. I noticed the following image on the management dashboard of the ISR.
We are collecting netflow from this system. Nbarv2 is enabled. Our goal is to collect the data above via telemetry. We checked the list of yangs supported on this platform using netconf xml api. Cisco-IOS-XE-flow-monitor-oper is listed. So we configured the following lines on the router:
telemetry ietf subscription 11
encoding encode-kvgpb
filter xpath /flow-monitor-ios-xe-oper:flow-monitors/flow-monitor-ios-xe-oper:flow-monitor
source-address 10.20.XX.XX
stream yang-push
update-policy on-change
receiver ip address XX.XX.XX.XX 57000 protocol grpc-tcp
We receive the telemetry data via telegraf agent. We can see the messages coming in. However, the content only consists of a single fields called "time_collected".
Are we using the correct yang?
Thank for the help in advance.
- Labels:
-
ISR 4000 Series
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2023 03:38 PM - edited 12-27-2023 03:40 PM
Try changing the update policy to periodic. On-change is sadly not supported by all data models.
Also, your xpath doesn't seem valid. Here is the tree view of your YANG model to assist you in creating the correct xpath:
module: Cisco-IOS-XE-flow-monitor-oper
+--ro flow-monitors
+--ro flow-monitor* [name]
| +--ro name string
| +--ro time-collected? uint64
| +--ro flows
| +--ro flow* [source-address destination-address interface-input is-multicast vrf-id-input source-port destination-port ip-tos ip-protocol]
| +--ro source-address string
| +--ro destination-address string
| +--ro interface-input string
| +--ro is-multicast string
| +--ro vrf-id-input int64
| +--ro source-port int64
| +--ro destination-port int64
| +--ro ip-tos string
| +--ro ip-protocol int64
| +--ro interface-output? string
| +--ro bytes? int64
| +--ro packets? int64
