Each RPKI Priority can store one (1) RPKI server's connection information. You can connect to the remote RPKI server through TCP or SSH. Use SSH to create encrypted connection to the remote RPKI server. Use TCP if you do not require that the connection to the remote server be encrypted.
Warning
Every time the server ssh command or the server tcp command is run, there is a possibility that your CLI console response may become slow. This is due to the SLX-OS performing CPU intensive tasks of caching ROAs from the remote RPKI server and then revalidating RPKI state for all existing prefixes. This has been observed in systems with fully scaled routes in RIB-in when adding a server in the highest RPKI priority group. Adding servers in the lower priority groups does not cause this issue.
This slowdown is also possible when the connection to the existing RPKI server fails and the system fails over to the server with the next priority.