The customer has two sets of routers and one location has replaced the other. So basically router pair "A" has been relocated to replace router pair "B." This means that router pair "A" will need to be renamed to router pair "B."

hardware swap required.

Below are the steps/recommendations -

Before starting, verify the asset state in the conductor and note it.

Stop 128T and salt minion in the router -

systemctl stop 128T

systemctl stop salt-minion

Change the host name (follow KB98801 [juniper.net]):

https://supportportal.juniper.net/s/article/SSR-Changing-the-asset-id-for-a-SSR-router 

Change/verify the minion_id on router -

cat /etc/salt/minion_id

Start 128T and salt minion on router -

systemctl start 128T

systemctl start salt-minion

From Conductor -

• Check conductor, "show assets" should show the new name as a pending device
• edit router node that currently shows down,
  • Locate and modify asset to the new name and commit

Verify Conductor UI -

Conductor -> Authority -> configured Associated Asset ID ,which needs to be matched with minion_id of router (/etc/salt/minion_id)

Verify the PDC SSH keys match -

Check the contents of /etc/128technology/ssh/pdc_ssh_key.pub on the router. The public key in this file must be included in /etc/128technology/ssh/authorized_keys of the conductor.

Validate the to the salt key to the conductor -

a) Salt-minion systemd service status is active (running), but the conductor asset status is Disconnected.

b) At this point we should check t128-salt-key

c) Asset ID for the router should be in accepted keys. If it is under denied or rejected keys, we must follow the below process.

Conductor - t128-salt-key -f <asset-id>

Router - systemctl stop salt-minion; toggle to the folder -> cd /etc/salt/pki/minion , Remove the file -> rm -rf minion_master.pub

Conductor - t128-salt-key -d <asset-id> ( both conductors in case of HA)

Router - systemctl start salt-minion

Post modifying router name if you observe lots of errors -

You can run the command create config autogenerated before running validate. This will delete the generated config and regenerate it and also update all the config elements to reflect the new name.

See https://www.juniper.net/documentation/us/en/software/session-smart-router/docs/cli_reference/#create-config-autogenerated

Note - In some cases if we still see events/messages with the old router name before rebooting. Reboot may be required for such cases.