Re: [j-nsp] gNMI on MX960

2024-03-07 Thread Ebben Aries via juniper-nsp
> I'm also getting some incomplete data when I have all the enterprise > protos loaded, hence why I posted code that shows incomplete/unparsed > protos. We can take this one offline to triage - will send you a separate mail > Are there plans to distribute the open config proto files that juniper

Re: [j-nsp] gNMI on MX960

2024-03-07 Thread Jared Mauch via juniper-nsp
Thanks this is helpful as I've had issues with output of incomplete GPB if the image does not support telemetry. I'm also getting some incomplete data when I have all the enterprise protos loaded, hence why I posted code that shows incomplete/unparsed protos. Are there plans to distribute the

Re: [j-nsp] gNMI on MX960

2024-03-07 Thread Ebben Aries via juniper-nsp
> "UNKNOWN:Error received from peer ipv4:10.4.0.78:30030 > {grpc_message:"Qos not supported", grpc_status:12, > created_time:"2024-03-07T16:20:41.756921+01:00"}" This would imply that the `qos` field is likely being populated in your request message: https://github.com/openconfig/gnmi/blob/master

Re: [j-nsp] gNMI on MX960

2024-03-07 Thread Sebastian Wiesinger via juniper-nsp
* Jared Mauch via juniper-nsp [2024-03-07 16:51]: > > What do you mean by complete? > > > [edit services analytics] > jared@Router# set sensor asdf resource ? > Possible completions: > System resource identifier string > /junos/services/health-monitor/config/ Health monitoring c

Re: [j-nsp] gNMI on MX960

2024-03-07 Thread Jared Mauch via juniper-nsp
> On Mar 7, 2024, at 10:48 AM, Sebastian Wiesinger via juniper-nsp > wrote: > > Hi Jared, > > thanks for the answer. > >> The second thing is, does your sensor path actually complete? > > What do you mean by complete? [edit services analytics] jared@Router# set sensor asdf resource ? Pos

Re: [j-nsp] gNMI on MX960

2024-03-07 Thread Sebastian Wiesinger via juniper-nsp
Hi Jared, thanks for the answer. * Jared Mauch via juniper-nsp [2024-03-07 16:41]: > I’ve been spending some time on this as well, here’s the first thing I would > ask you: > > > If you do “show version | match tele” > > What do you see? I’ve had varying results based on the platform. swie

Re: [j-nsp] gNMI on MX960

2024-03-07 Thread Jared Mauch via juniper-nsp
I’ve been spending some time on this as well, here’s the first thing I would ask you: If you do “show version | match tele” Eg: jared@Router> show version | match tele {master:0} jared@Router> vs jared@Router> show version | match tele JUNOS na telemetry [21.4R3-S5.17] {master:0} What

[j-nsp] gNMI on MX960

2024-03-07 Thread Sebastian Wiesinger via juniper-nsp
Hello everyone, I'm trying (and failing) to get gNMI running on an MX960. All I'm getting are weird errors. Has anyone successfully used gNMI subscriptions on an MX box for streaming telemetry? If so, which config did you use on the box and in the client? My config on the MX is this: set system