User equivalence in RAC

Question

This is a question regarding resetting the user equivalence on clustered hosts. Our company has a 3-node 10.2.0.3 RAC cluster running CRS w/ an ASM system for the DB (Linux64). I just finished rebuilding our Grid Control deployment on a new host (bringing it up to 10.2.0.5) and have been steadily redeploying the agents. The last boxes on the list were those associated with the production RAC cluster. During installation, you have the option to install to all 3 nodes simultaneously from a single node, however when I attempted this, I was informed that password-less ssh communication between the 3 nodes was not available. Not a big problem since I just went through the installs on each box locally and each host and its targets are now reporting to the Grid Control quite well. It even properly detects that the database is clustered.
However, a Grid critical alert continues to inform me that "User equivalence unavailable on all the nodes", and I decided to investigate the possibilities of rectifying this. Initially I tried copying appropriate files out of the ~/.ssh directory to other boxes, but that's when I discovered that the keys had been pass-phrased and neither myself nor the other DBA here know what that pass-phrase is (accurate, centrally managed password management was something I put in place when I arrived to prevent this very thing going forward - thank you KeePass)
My initial thought was to figure out which boxes currently interact with the RAC boxes, and then regenerate the keys per [note 300548.1|300548.1]. Now, I've only been working with RAC for 6 months since I switched jobs, so while I'm getting more comfortable with the tech, there's still a lot I haven't explored thus far, and we don't have a test RAC environment for me to just start trying things (it's in the pipe). The other DBA here has more experience with RAC, but hasn't actually set one up, so neither of us knows for sure what the full ramifications of resetting the keys might be. Could this effect CRS negatively or is it using its own connections through ports on the private network addresses? Aside from non-clustered boxes needing their keys updated, are there any other considerations we should be thinking about?
Thanks!

Answer 1

"User equivalence unavailable on all the nodes"After install Oracle RAC and you create phrase key (have password), you'll find it. You can ignore after install Cluster completely
But when you use "cluvfy" or etc... about RAC (dbca/netca)
you have to
$ exec /usr/bin/ssh-agent $SHELL
$ /usr/bin/ssh-add
on metalink 300548.1, they try to told us... create key with no password
$ ssh-keygen -t rsa
Now accept the default location for the key file
Enter and confirm a passphrase. (you can also press enter twice).
$ ssh-keygen -t dsa
Now accept the default location for the key file
Enter and confirm a passphrase. (you can also press enter twice).
So, When we use cluvfy" or etc... (with creating key with no password), we don't run "ssh-agent $SHELL" ...
and I think You'll not find "User equivalence unavailable on all the nodes" as well.