cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1832
Views
5
Helpful
11
Replies

Telemetry subscription-grpc not working on Catalys 3650

PabloP
Level 1
Level 1

Hi everyone

 I have problems configuring a subscription with grpc on the catalys 3650 switch.

Software version:Cisco IOS XE Software, Version 16.06.03

Configuration:

telemetry ietf subscription 10
encoding encode-kvgpb
filter xpath /interfaces-ios-xe-oper:interfaces/interface[name='GigabitEthernet1/0/3']/statistics
receiver ip address 10.51.141.242 57000 protocol grpc-tcp
stream yang-push
update-policy periodic 500

!

netconf-yang
!


#show telemetry ietf subscription 10 deta
Telemetry subscription detail:

Subscription ID: 10
Type: Configured
State: Invalid
Stream: yang-push
Encoding: encode-kvgpb
Filter:
Filter type: xpath
XPath: /interfaces-ios-xe-oper:interfaces/interface[name='GigabitEthernet1/0/3']/statistics
Update policy:
Update Trigger: periodic
Period: 500
Notes: Stream not supported

Receivers:
Address Port Protocol
-------------------------------------------------
10.51.141.242 57000 grpc-tcp

I have configured this subscription on catalys 9300 and it works.

I appreciate your feedback for this issue.

1 Accepted Solution

Accepted Solutions

PabloP
Level 1
Level 1

The problem was the software version, in IOS-XE 16.12.5.b works fine. Thanks all for your help.

View solution in original post

11 Replies 11

balaji.bandi
Hall of Fame
Hall of Fame

what is not working, is the telemetry data not sending ?

# show platform software yang-management process 

check some troubleshooting tips, also consider going to latest stable IOS XE.

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/prog/configuration/1612/b_1612_programmability_cg/model_driven_telemetry.html

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Hi

The problem is that the subscription State is: Invalid.

switch#show telemetry ietf subscription 10 brief
Telemetry subscription brief

ID      Type                State           Filter type
-----------------------------------------------------
10    Configured      Invalid           xpath


switch#show platform software yang-management process
confd : Running
nesd : Running
syncfd : Running
ncsshd : Running
dmiauthd : Running
vtyserverutild : Running
opdatamgrd : Running
nginx : Running
ndbmand : Running
pubd : Running

 

 

 

the reason for invalid :

Named Receiver Operation and Operational State

Named receiver objects and subscription receiver objects (that refer to the named receiver) have two different operational states. The operational states are valid or invalid. The most common reason for a named receiver to be invalid is incomplete configuration, however; it could also be due to other reasons. The operational state view of a named receiver has a field that provides a text explanation on why the receiver is invalid. When the receiver state is valid, this field is empty.

# show telemetry receiver all  

I also see your OP (looks for me some limitation here) - Cat 9300 are latest IOS Xe you may be running 17.X code I guess here)

Notes: Stream not supported

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

#show telemetry receiver all

This command is not accepted

#show telemetry ?
ietf IETF information

#show telemetry

Another observation, in the configuration is not possible put: source-address. In Catalyst 9300 this opcion is enable and the STATE is VALID.

The YANG MODELS supported:

#show platform software ndbman switch active R0 models
NDBMan Active Models

Name Revision
----------------------------------------------------------------------------------
acl-ios-xe-oper 2017-02-07
bgp-ios-xe-oper 2017-04-01
cdp-ios-xe-oper 2017-02-07
checkpoint-archive-i 2017-04-01
efp-stats-ios-xe-ope 2017-02-07
environment-ios-xe-o 2017-02-07
flow-monitor-ios-xe- 2017-04-01
ip-sla-ios-xe-oper 2017-04-01
lldp-ios-xe-oper 2017-02-07
mdt-cfg 2017-03-02
mdt-oper 2017-03-02
memory-ios-xe-oper 2017-04-01
platform-ios-xe-oper 2017-02-06
platform-sw-ios-xe-o 2017-04-01
process-cpu-ios-xe-o 2017-02-07
process-memory-ios-x 2017-02-07
trustsec-ios-xe-oper 2017-02-07
btrace-eventq 2017-01-01
ios-emul-oper-db 2016-11-01
iosxe-oper 2016-11-01

#

Hello,

it might be that 'encode-kvgpb' is not supported in your XE version. Try XML

Encoding: encode-kvgpb

Encoding: encode-xml

Doesn´t work.

switch#show telemetry ietf subscription 12 det
Telemetry subscription detail:

Subscription ID: 12
Type: Configured
State: Invalid
Stream: yang-push
Encoding: encode-xml
Filter:
Filter type: xpath
XPath: /process-cpu-ios-xe-oper:cpu-usage/cpu-utilization/five-seconds
Update policy:
Update Trigger: periodic
Period: 500
Notes: Stream not supported

Receivers:
Address               Port       Protocol
-------------------------------------------------
10.51.141.242   57000     grpc-tcp

switch#show telemetry ietf subscription 12
Telemetry subscription brief

ID      Type           State            Filter type
-----------------------------------------------------
12   Configured    Invalid         xpath

In the configuration is not possible put: source-address.  In Catalyst 9300 this opcion is enable and the STATE is VALID.

Maybe, could it be the software version?

Hello,

my bad...encode-xml does not work with grpc-tcp, only encode-kvgpb does...

EDIT: I found several examples of Telemetry in 'Everest' releases (the 16.06 you are running), and they all use XML encoding (encode-xml). XML encoding only works with gNMI and NETCONF as transport protocols, and not with gRPC, Try and figure out how to set encode-xml with either gNMI or NETCONF as transport protocol...

 

Please, Can you share de examples of Telemetry in 'Everest' releases 16.06?

PabloP
Level 1
Level 1

The problem was the software version, in IOS-XE 16.12.5.b works fine. Thanks all for your help.

Glad it was working :

that is my suggestion  ( I mean to say the version you used may be limitation) - that is the reason provided 16.12 documentation, so you can update the code to test.

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help