TIG stack for telemetry

dfjok53 — Wed, 24 Jan 2024 14:35:11 GMT

Hi there,

I have set up a TIG stack to display telemetry from a C3850 (16.12.1). I did an ietf subscription to my instance, it connected fine and I could see the measurement in my influx db.

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/process-cpu-ios-xe-oper:cpu-utilization/process-cpu-ios-xe-oper:one-minute
Update policy:
Update Trigger: periodic
Period: 1000
Encoding: encode-kvgpb
Source VRF:
Source Address: xx.xx.xx.xx
Notes:

Receivers:
Address Port Protocol Protocol Profile
-----------------------------------------------------------------------------------------
xx.xx.xx.xx 57000 grpc-tcp

Influx:

Cisco-IOS-XE-process-cpu-oper:cpu-usage/cpu-utilization
cpu
disk
diskio
kernel
mem
processes
swap
system

The issue I have now is any subsequent subscription I do is always in status disconnected.

Subscription ID: 2
Type: Configured
State: Valid
Stream: yang-push
Filter:
Filter type: xpath
XPath: /interfaces-ios-xe-oper:interfaces
Update policy:
Update Trigger: periodic
Period: 1000
Encoding: encode-kvgpb
Source VRF:
Source Address: 10.1.50.3
Notes:

Receivers:
Address Port Protocol Protocol Profile
-----------------------------------------------------------------------------------------
10.37.137.237 57000 grpc-tcp

Telemetry subscription receivers detail:

Subscription ID: 1
Address: 10.37.137.237
Port: 57000
Protocol: grpc-tcp
Profile:
State: Connected
Explanation:

ARC-3850-1# sh telemetry ietf subscription 2 receiver
Telemetry subscription receivers detail:

Subscription ID: 2
Address: 10.37.137.237
Port: 57000
Protocol: grpc-tcp
Profile:
State: Disconnected
Explanation:

Jan 24 14:06:11.887: %MDT_SUBSCRIPTION-4-TERMINATED: Switch 1 R0/0: pubd: Subscription terminated (stream yang-push, id 2, client xx.xx.xx.xx:57000): run-time error.

I'd rally appreciate any info/pointers as o why this might be happening.

Regards

Re: TIG stack for telemetry

bigevilbeard — Thu, 25 Jan 2024 11:46:15 GMT

I wonder if you have a limit in resources on this switch? As your first ietf subscription remains connected while subsequent subscriptions disconnect points towards resource limitations or configuration issues with the telemetry infrastructure on your C3850 maybe.

Re: TIG stack for telemetry

dfjok53 — Fri, 26 Jan 2024 10:03:47 GMT

Not sure what's happening but think it's the xpath. I thought what you said too so I applied them in different order and the same one worked. I stripped back the path (although it wasn't saying invalid) and that let it move into a connected state. I will do a bit more over the next few days and if I find anything worth sharing I will pop it in here. Thanks for your input

topic Re: TIG stack for telemetry in Network Platform API

TIG stack for telemetry

Re: TIG stack for telemetry

Re: TIG stack for telemetry