Telemetry on Telemetry on Nexus 3548 path attributes

[wgranada]

Good day All,

I am trying to set up telemetry on my C3548P-10GX version 10.3(3) switch, is there a complete list or something for the path? All I see is:

sw1(conf-tm-sensor)# path ?
WORD Distinguished Name
adjacency Monitor ARP, AM with IP adjacencies
environment Monitor chassis information including fan,temperature,power,storage,supervisor,linecard
interface Monitor all the interface counters and status changes
mac Monitor static and dynamic mac entries
mac-all Monitor add/delete/move activities of static/dynamic MACs in the L2 table
resources Monitor system resources like CPU utilization, memory utilization
rib Monitor RIB routes
vxlan Monitor VXLAN EVPN (VXLAN peers, VXLAN counter, VLAN counters, BGP peers data)

What I am trying to do is monitor microburst and latency trying to stream these to Chronograf.  I tried looking for docs and not finding anything really.  Any suggestion or docs that can tell me what I need?  This is my current set up but not seeing much

feature telemetry
telemetry
destination-group test1
ip address 1.2.3.5 port 57000 protocol gRPC encoding GPB
sensor-group test1
path sys/intf depth unbounded
subscription 1
dst-grp test1
snsr-grp test1 sample-interval 10000

Thank you in advance!!!

[balaji.bandi]

What is the complete model, and what kind of RAM does it have?

As I remember, it has a limitation, only the XML model with 16GB has full-blown features.

The last attempt did not work normally at 3548; then we moved to Nexus 9K, and everything was fine there.

[wgranada]

Hi Balaji

it is a cisco Nexus3500 C3548P-10GX N3K-C3548P-XL with 16G of memory

[wgranada · Accepted solution]

Ok I think I understand this now, if I am wrong please correct me but here, we go.  I will try to keep this short.

There is a github site: https://github.com/influxdata/telegraf/blob/master/plugins/inputs/cisco_telemetry_mdt/README.md

If you look at the section NX-OS Configuration Example 

This will give you a list of the different data-sources you can use to stream your path telemetry, in my case my C3548P-10GX N3K-C3548P-XL running version 10.3(3).

What I was interested in doing was streaming Micorburst information to m Chronograf. On the Cisco side you have 3 fields that you need to configure:

destination-group

sensor-group

subscription

The sensor-group is the field you need to pay attention to, so using the link above and on your cisco equipment if you go into the sensor-group and do a qustion mark for your data-source it will give you what you can stream.  In my case the version of software I am running on my 3548 switch is a hardware-accelerated platform which means it doesn't expose the data-source hardware:

data-source ?

ME DME objectstore

NATIVE NATIVE

NX-API

NX-API

YANG YANG

So that means I cannot stream microburst telemetry via the MDT, instead I can only use this like syslog/SNMP or NX-API queries.  So the only think I can do is either upgrade my software or configure some sort of NX-API query.  Hope that makes sense.

Thank you!