In the course of this discussion the original poster has asked 2 questions. The first question was about how to enable ssh on a 2960. The first step in enabling ssh is to determine whether the 2960 supports encryption. In the output of show version look for the image name. Does the image name include "k9"? If so the switch does support encryption, and if not the switch does not support encryption and you will not be able to enable ssh.
If the device does support encryption then you will need to generate an RSA key. To enable an RSA key you will need to configure a device name different from the default device name and to configure a domain name different from the default. After you do these you can generate an RSA key and ssh will be enabled.
The second question was about using the 2960 as a client for ssh "and want to know the difference b/w login switch using TELNET and SSH(switch using in client mode)" Once ssh is enabled then a user on the switch could initiate remote connections to other devices using either telnet or ssh. If using ssh then one condition is that the remote device must have ssh enabled and must accept ssh protocol connections. If using telnet then one condition is that the remote device must accept telnet connections. Using either protocol to connect to remote devices the user must have a user name and password that the remote device would authenticate. From the user perspective there is no difference between using telnet to connect to a remote device or using ssh to connect to the remote device. From an operational perspective the difference is that the ssh traffic will be encrypted and the telnet traffic will be clear text. If someone might be able to sniff the traffic this difference could be significant.
HTH
Rick
