Controller 2 in example below displays as Config not in sync:
On the VD, execute the ssh-keygen command if required to freshly generate the keys, else skip this and execute only push_keys script in next step.
ssh key mismatch steps on VD:
-------------------------------
1. key generate on VD:
Administrator@SDWAN-VOAE2:~$ ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/home/Administrator/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/Administrator/.ssh/id_rsa.
Your public key has been saved in /home/Administrator/.ssh/id_rsa.pub.
The key fingerprint is:
43:a6:e1:dc:0a:b7:6d:52:e5:81:8f:20:e2:cf:5b:86 Administrator@SDWAN-VOAE2
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| . . o + o |
| . . + B = . |
| . . = S o |
| o + = . |
| E * o |
| + o |
| . |
+-----------------+
2. key push to device:
Below example shows 10.192.66.72 is Controller2 IP, versa123 is password, execute with these 2 as arguments to push keys from VD to any device:
Administrator@SDWAN-VOAE2:~$ cd .ssh/
Administrator@SDWAN-VOAE2:~/.ssh$ ls
authorized_keys id_rsa id_rsa.pub
Administrator@SDWAN-VOAE2:~/.ssh$ /opt/versa/vnms/scripts/push_keys_to_device.sh 10.192.66.72 versa123
Warning: Permanently added '10.192.66.72' (ECDSA) to the list of known hosts.
0 0
Administrator@SDWAN-VOAE2:~/.ssh$
Now Controller2 shows config sync:
