When customer running telemetry on crpd they may complain that the cRPD is listening for jsd on port 32767 instead of port 50051. however when they try to configure port 32767 they get the error while commit.

 

show system connections will show that cRPD is listening for jsd on port 32767

root@cRPD# run show system connections | match jsd                                    
tcp6       0      0 :::32767                :::*                    LISTEN      0          2810721    194/jsd
tcp6       0      0 127.0.0.1:51051         :::*                    LISTEN      0          2810722    194/jsd
unix  2      [ ACC ]     STREAM     LISTENING     2810720  194/jsd              /var/run/japi_jsd
unix  2      [ ACC ]     STREAM     LISTENING     2802773  194/jsd              //var/run/jsd_mgmt

when we try to define the port 32767 for telemetry it does not accept and give error while commiting.

root@cRPD# set system services extension-service request-response grpc clear-text port 32767  
error: invalid value: 32767
                ^
port value cannot be other than 50051.

Default port for JSD to listen is 32767. Initially port 50051 was added to docker exposed ports list, hoping everyone will try to use ‘50051’ itself.

By default there is restriction on cRPD to configure only port 50051 so you get error when you try to configure any other port. Once port 50051 is configure you will see JSD listening to port 50051 and coneection getting established.

root@cRPD# run show system connections | match jsd    
tcp6       0      0 :::50051                :::*                    LISTEN      0          2813470    194/jsd
tcp6       0      0 127.0.0.1:51051         :::*                    LISTEN      0          2813471    194/jsd
tcp6       0      0 10.85.209.81:50051      10.85.184.5:41716       ESTABLISHED 0          2817031    194/jsd