FortiNAC
NOTE: FortiNAC is now named FortiNAC-F. For post-9.4 articles, see FortiNAC-F. FortiNAC is a zero-trust network access solution that provides users with enhanced visibility into the Internet of Things (IoT) devices on their enterprise networks.
FortiKoala
Staff
Staff
Article Id 190080

Description


Unable to successfully complete SSH communication between servers.


Example 1:  Nessus2's IP address is not in the known_hosts file of cm1
root@cm1:
> ssh nessus2
The authenticity of host 'nessus2 (172.22.100.10)' can't be established.
RSA key fingerprint is 94:08:7a:74:41:a7:28:23:1e:e8:63:12:5d:24:2f:51.
Are you sure you want to continue connecting (yes/no)?

Example 2: Nessus1's correct password is not in the /root/.ssh/authorized_keys2 file of cm1
root@cm1:
> ssh nessus2
password:

 

Scope


Version: All

 

Solution


Ensure /bsc/campusMgr/bin/.sshaccountInfo file has a valid entry for every required server including itself.

If not, use the AddPassword tool to add the missing keys.

1) To set the password for SSH connections to a specific server IP, type:
AddPassword <server ip> <root cli password>

 
Note the following:
  • The only allowed symbols for CLI root passwords are ! @ # % ^ * ? _ ~ -
  • Only root CLI/SSH passwords should be entered.


2) Remove any old host entries for that server ip (if any exist).
vi /root/.ssh/known_hosts     

 
'DD' to delete the line.


3) Add the new key for that server IP.
SetSSHKey <server ip>

Related Articles

Technical Note: Troubleshooting CLI credential failure