Ignite restoration success but unable to login to server using putty.

[RajuD]

Dear All,

I restored ignite archieve from server to client both are in same subnet.

The restoration is success. I am able to login to server using mp console but i am unable to take server session using putty.

checked below configuration are proper but still not finding what is the issue.

1) Ip address
2) gateway, subnet mask
3) nsswitch configuration file.
4) No DNS and NIS configured in the client.

No error message in /var/adm/syslog/syslog.log

Appreciate your early responce.

[Shibin_2]

Are you trying to telnet or ssh to the server?

What's the default route settings?

Are you able to ping the server from your PC and vice versa ?

[RajuD]

Are you trying to telnet or ssh to the server?

Both, but not working. Restarted the ssh & telnet service also. after entering username it is getting stuck.

What's the default route settings?
Both server client are pointing to same gateway.

Are you able to ping the server from your PC and vice versa ?
Yes

[Torsten.]

"Unable to do something ..." is always a bit meaningless without original messages etc.

I would first try from the server to contact "anything" outside, e.g. ping the gateway.


A possible reason:

Let's assume you have a server with

lan0 on 1/0/0

and you add another NIC later

lan1 on 0/0/0

this will flip if you do a restore (because it is sorted based on the H/W path), like

lan0 on 0/0/0

and

lan1 on 1/0/0

In such case the IP configuration does not match the physical installation; worth to check this!

[Shibin_2]

Agree with Torsten's view.

Btw, you said "after entering username" .. which means, you are able to telnet / ssh.

Is that user allowed to telnet / ssh ? Have you tried to login with any other user name?

[RajuD]

Hi Torten,

Thanks for your responce. I am doing testing for ignite backup /restore.

Let me explain what i did.

Configure ignite server to take backup of client. (status = sucess)

Both client and server are in same subnet say 255.255.252.0

Configured client mac address, ipaddres and gateway, subnetmask in ignite server /etc/bootptab file.

Took backup of client in ignite server by trigerring make_net_recovery

Backup completed successfully.

Before taking client system reboot for testing restoration (Took netstat -in, netstat -rn, lanscan) output.

Took reboot of client

Trigerred lanboot in EFI shell

selected lan0 and restored the client.

Restoration is success when the client came up, i rechecked the network configuration everything seems ok.

But no idea why i am not getting password prompt in putty session when i enter username?

[RajuD]

Hi,

Its applicable for all user. Please find the below output. which i tried from other server to login.


# ssh -v root@10.X.X.3
OpenSSH_5.3p1+sftpfilecontrol-v1.3-hpn13v5, OpenSSL 0.9.8l 5 Nov 2009
HP-UX Secure Shell-A.05.30.009, HP-UX Secure Shell version
debug1: Reading configuration data /opt/ssh/etc/ssh_config
debug1: Connecting to 10.2.3.51 [10.2.3.51] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/3
debug1: identity file /.ssh/identity type -1
debug1: identity file /.ssh/id_rsa type -1
debug1: identity file /.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_5.3p1+sftpfilecontrol-v1.3-hpn13v5
debug1: match: OpenSSH_5.3p1+sftpfilecontrol-v1.3-hpn13v5 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3p1+sftpfilecontrol-v1.3-hpn13v5
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: AUTH STATE IS 0
debug1: REQUESTED ENC.NAME is 'aes128-ctr'
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: REQUESTED ENC.NAME is 'aes128-ctr'
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '10.2.3.51' is known and matches the RSA host key.
debug1: Found key in /.ssh/known_hosts:3
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
Connection closed by 10.X.X.3

[RajuD]

Issue has been resolved.

Found /etc/resolve.conf file contains incorrect entries.