This article provides step-by-step instructions for onboarding an SSR router to a Conductor using the CLI method.
Prerequisite:
Ensure that the new SSR router has IP reachability to the Conductor. Configure the Linux interface or device interface appropriately before starting the onboarding process.
Step 1: Add the Router on the Conductor (UI)
Step 2: Configure the SSR Router (CLI)
Example: RouterA
Sample minion file for reference:
auth_safemode: trueautoload_dynamic_modules: falseenable_legacy_startup_events: falseinclude: /usr/lib/128technology/python/salt/file_roots/_beacons/*.confmaster:- 127.0.1.2master_alive_interval: 30master_tries: -1ping_interval: 0random_reauth_delay: 120recon_default: 5000recon_max: 30000recon_randomize: truetcp_authentication_retries: -1tcp_keepalive_cnt: 3tcp_keepalive_idle: 5tcp_keepalive_intvl: 10transport: tcp
Step 3: Restart Salt Minion Service# systemctl restart salt-minion.service# systemctl status salt-minion.service
Ensure the service starts successfully and connects to the Conductor.
Step 4: Verify Asset Status from ConductorOn the Conductor PCLI, run:# show assetsThe router should appear in connected or running state.
Step 5: Review Logs if Router Does Not Show as ConnectedOn the Conductor:# shell su -# cd /var/log/128technology/# tail -f automatedProvisioner.log# grep -iR "RouterA" automatedProvisioner.log
Above logs will helps to identify onboarding or Salt connectivity issues.If you face any further issues, please contact JUNIPER JTAC Support for assistance.