Re: [j-nsp] Telemetry in the ACX7100-48L

[Aaron Gould via juniper-nsp]

I'm starting to wonder if this has something to do with different 
telemetry models/methodologies.  Forgive me as I forget the correct 
terminology, but, I think the MX960 sending native telem models, seems 
to be always-on... and I'm wondering if the ACX7100 is more based on the 
grpc subscription model, whereas the collector needs to subscribe to the 
agent/sensor running on the ACX7100, then the telemetry data is 
streamed, and possibly in openconfig format.




___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] Telemetry in the ACX7100-48L

[Aaron Gould via juniper-nsp]

Anyone done telemetry in the ACX7100-48L?  Before I start talking about 
the ACX7100, I'll say that I do have MX960's successfully sending 
telemetry data to this collector, and it automatically displays in the 
web gui front-end.  (I actually use chronograf instead of grafana)


Now, the ACX7100... I've tried various things... I can only get this 
sensor resource string to produce any sort of telemetry data.


I see the data arriving at my telemetry collector machine (TIG stack), 
but not showing up on the web interface (chronograf)


...config on ACX7100-48L

set services analytics streaming-server my-grafana-srvr-netmon08 
remote-address 172.122.14.159
set services analytics streaming-server my-grafana-srvr-netmon08 
remote-port 5
set services analytics export-profile my-exprt-prfl local-address 
10.11.12.237

set services analytics export-profile my-exprt-prfl local-port 12237
set services analytics export-profile my-exprt-prfl reporting-rate 1
set services analytics export-profile my-exprt-prfl format gpb
set services analytics export-profile my-exprt-prfl transport udp
set services analytics sensor my-sensor-23 server-name 
my-grafana-srvr-netmon08

set services analytics sensor my-sensor-23 export-name my-exprt-prfl
set services analytics sensor my-sensor-23 resource 
/lacp/interfaces/interface/members/member/state/counters/lacp-in-pkts



...seen on my telem collector

ngrep host 10.11.12.237

U 10.11.12.237:12237 -> 172.122.14.159:5 #218
  ..eng-lab-7100-2.."..my-sensor-23:/lacp/interfaces/inte
  rface/members/member/state/counters/lacp-in-pkts/:/lacp/int
  erfaces/interface/members/member/state/counters/lacp-in-pkt
  s/:re0/lacpd($0.18.@...2..+..(..%...ae100.e
  t-0/0/49..w

I'm wondering if this has something to do with maybe my MX960's sending 
native/vendor-specific Juniper telemetry data, but the ACX7100 may not 
belike I think it's OpenConfig version of telem data.  And so maybe 
my collector isn't displaying it and maybe there are more than one 
issue I'm having, unsure.


I've tried these other formats and i didn't see any data arrive at the 
collector at all...



me@acx7100# set services analytics export-profile my-exprt-prfl format ?
Possible completions:
  gpb  Use gpb format
  gpb-gnmi Use gnmi format for gpb messages
  gpb-sdm  Use gpb self-describing-message format
  json-gnmi    Use gnmi format for json messages
[edit]

i've tried remote-port 50020, and nothing...


--
-Aaron

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp