To reiterate and add to my previous email…also, please realize I’m in my early
stages of learning about telemetry and Junos capabilities, so this is only what
little I’ve seen and understand about it thus far…
As a side note, the ACX7100-48L has been a challenge regarding telemetry as
well, and I’m learning that a different telemetry method using gRPC
subscription model of request/reply may yield more capabilities… and so I
wonder if the same is true regarding MX304, again, still learning…
Using the native telemetry like I do on my MX960's seems to be working somewhat
on the MX304. Not all sensors though. Also, I did have to alter a jflow
sensor reporting-rate
[edit services analytics]
'sensor my-sensor-21'
reporting-rate can't be less than 30sec for Inline Jflow Sensor on mx304!
error: configuration check-out failed
so i had to change it like this... but all others I left at reporting-rate 1
set services analytics export-profile my-exprt-prfl-jflow local-address
10.101.12.234
set services analytics export-profile my-exprt-prfl-jflow local-port 12234
set services analytics export-profile my-exprt-prfl-jflow reporting-rate 30
set services analytics export-profile my-exprt-prfl-jflow format gpb
set services analytics export-profile my-exprt-prfl-jflow transport udp
set services analytics sensor my-sensor-21 server-name my-grafana-srvr-08
set services analytics sensor my-sensor-21 server-name my-grafana-srvr-04
set services analytics sensor my-sensor-21 export-name my-exprt-prfl-jflow
set services analytics sensor my-sensor-21 resource
/junos/system/linecard/services/inline-jflow/
also, in my chronograf (like grafana) web interface, I'm not seeing the MX304
send telemetry data for some things, like these...
works... i see data auto-populating in my telem server
me@mx960> show configuration services analytics | display set | grep memo
set services analytics sensor my-sensor-2 resource
/junos/system/linecard/cpu/memory/
set services analytics sensor my-sensor-17 resource
/junos/system/linecard/npu/memory/
doesn't work, I don't see data for these sensors from mx304, but, to be clear,
mx304 does auto-sent telem data for other sensors
me@mx304> show configuration services analytics | display set | grep memo
set services analytics sensor my-sensor-2 resource
/junos/system/linecard/cpu/memory/
set services analytics sensor my-sensor-17 resource
/junos/system/linecard/npu/memory/
Aaron
> On Oct 18, 2023, at 8:48 AM, Aaron1 <aar...@gvtc.com> wrote:
>
> I have an MX304 in the lab, evaluating it at the moment. Junos: 22.2R3.15
>
> Telemetry is running and a little different than what I have on my MX960’s
>
> Also, I get a license warning when committing OSPF and LDP. We got a license
> from our account team and now we don’t see that message anymore
>
>
>
>
> Aaron
>
>> On Oct 18, 2023, at 7:40 AM, Giuliano C. Medalha via juniper-nsp
>> <juniper-nsp@puck.nether.net> wrote:
>>
>>
>> Good morning
>>
>> All good ?
>>
>> Anyone already running MX304 as an edge, using ipfix, flowspec and telemetry
>> features on the same box ?
>>
>>
>> Any problems related with that ?
>>
>> If so, what version of Junos are you using?
>>
>> Thanks
>>
>> Giuliano
>>
>>
>> WZTECH is registered trademark of WZTECH NETWORKS.
>> Copyright (c) 2023 WZTECH NETWORKS. All Rights Reserved.
>>
>> IMPORTANTE:
>> As informa??es deste e-mail e o conte?do dos eventuais documentos anexos s?o
>> confidenciais e para conhecimento exclusivo do destinat?rio. Se o leitor
>> desta mensagem n?o for o seu destinat?rio, fica desde j? notificado de que
>> n?o poder? divulgar, distribuir ou, sob qualquer forma, dar conhecimento a
>> terceiros das informa??es e do conte?do dos documentos anexos. Neste caso,
>> favor comunicar imediatamente o remetente, respondendo este e-mail ou
>> telefonando ao mesmo, e em seguida apague-o.
>>
>> CONFIDENTIALITY NOTICE:
>> The information transmitted in this email message and any attachments are
>> solely for the intended recipient and may contain confidential or privileged
>> information. If you are not the intended recipient, any review,
>> transmission, dissemination or other use of this information is prohibited.
>> If you have received this communication in error, please notify the sender
>> immediately and delete the material from any computer, including any copies.
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
