How to Set SSH User Equilance in All Storage Server in Exadata and Zero Data Loss Recovery Appliance

Many tasks in an Exadata and Zero Data Loss Recovery Appliance environment, you can do connected in one server and then, execute the operation in many servers and storage servers in one time.

But for this, as premise, all ssh connections must be done without password, using user key equivalence. One way to set this in all storage nodes, for example, is executing dbcli tool with -k parameter. Many commands used by dbcli must to have equivalence set to execute, so, the tool itself can configure it to us.

Lets see below, how to do that.

First, let’s create a file with all storage nodes servers names. Connect with root in one dbnode and then, execute racli command:

[root@zdl02dbadm01 ~]# racli list storage_cells > /radump/cell_group
[root@zdl02dbadm01 ~]# cat /radump/cell_group
Start: List of Storage Cells
zdl02celadm01
zdl02celadm02
zdl02celadm03
zdl02celadm04
zdl02celadm05
zdl02celadm06
End: List of Storage Cells
[root@zdl02dbadm01 ~]#

With a text editor, remove Start and End lines in file, so that it looks like this:

[root@zdl02dbadm01 ~]# cat /radump/cell_group
zdl02celadm01
zdl02celadm02
zdl02celadm03
zdl02celadm04
zdl02celadm05
zdl02celadm06

Now, lets execute dbcli command with -k parameter to set key equivalence on missing storage server:

root@zdl02dbadm01 ~]# dcli -l root -g /radump/cell_group -k
root@zdl02celadm04's password:
zdl02celadm01: ssh key already exists
zdl02celadm02: ssh key already exists
zdl02celadm03: ssh key already exists
zdl02celadm04: ssh key added
zdl02celadm05: ssh key already exists
zdl02celadm06: ssh key already exists

As you can see here, most of my storage servers have ssh key equivalence, except zdl02celadm04, so, the command will ask the password to set it.

Now, lets test it:

[root@zdl02dbadm01 .ssh]# ssh zdl02celadm04
Last login: Mon Nov 24 08:36:02 -03 2025 from 10.254.64.31 on ssh
Last login: Mon Nov 24 08:36:23 2025 from 10.254.64.31
[root@zdl02celadm04 ~]#