Hi Ashwini,
The most likely problem here would be mis-configuration. Please check your Policy to ensure that the target account has been added specifically for the SSH Access Method (or TCP/UDP Service used for SSH). We have seen issues in the past where users put the target account in the Policy under "Passwords" but this is not used for auto connect, it is only for actually 'viewing' the password.
This KB doc explains the steps required for auto-connect:
PAM 2.X: HOW-TO: Set up a device for RDP or SSH with automa - CA Knowledge
PAM 3.X: HOW-TO: Set up a device for RDP or SSH with automa - CA Knowledge
If this doesn't help, it is also possible that your appliance/cluster is in a bad state. You should check for a message box at the top of the page when you login to see if there are any reported cluster problems, Credential Manager problems, or the DB is locked. If you see any messages like this, they are likely the cause. If you do find a message, you can post it here and we can try to provide advice on moving forward.
Regards,
Christian Lutz
Sr. Support Engineer
CA Technologies - North America