Telemetry is not working as expected on the device. The device is establishing connection but tool doesn't seem to be able to collect information from the device.
LOGS:
root@switch> show chassis alarms
No alarms currently active
services { ssh { root-login allow; max-sessions-per-connection 32; sftp-server; } xnm-clear-text; extension-service { request-response { grpc { ssl { address 192.168.0.1; port 50051; local-certificate JTI; } } } } netconf { ssh; } }
{master:0}
root@switch> show system connections | match 50051
tcp4 0 0 192.168.0.1.50051 192.168.0.10.59820 ESTABLISHED tcp4 0 0 192.168.0.1.50051 192.168.0.10.57430 ESTABLISHED tcp4 0 0 192.168.0.1.50051 *.* LISTEN
root@switch > show ephemeral-configuration instance junos-analytics >>>>> no information
root@switch >
root@switch> show agent sensors >>>>>>>>>>>> getting error for the processes
error: peer_daemon: bad daemon: agentd
Telemetry for junos cli is not supported on EX4300. Below is the document for reference:
https://apps.juniper.net/feature-explorer/feature/4332?fn=gRPC%20support%20for%20the%20Junos%20Telemetry%20Interface
We have confirmed it as we need to have the below processes to run Telemetry on Junos. We checked on different ex4300s. We saw the same results.
root@switch> start shell
% cd /usr/sbin/
% ls -ltr agent*
ls: No match.
% ls -ltr na-grpcd
ls: na-grpcd: No such file or directory
% ls -ltr jsd
lrwxr-xr-x 1 root wheel 30 Mar 26 09:33 jsd -> /packages/mnt/jsd/usr/sbin/jsd
% exit
exit
root@switch> show system processes | match na-grpcd
root@switch> show system processes | match agentd
It has also been tested on different software versions and the results are same.
+++++++++++++++++++++++++++++++++++++