Ignite server locks out root account via ssh????

[Paul F. Bennett]

The system that hosts our Ignite server is locking out the root account due to too many failed attempts. It does during the timeframe that the clients push a Ignite system image to the server, however, Ignite backup is successful. It appears Ignite is causing the lock out and that it is also related to ssh. Does Ignite have an ssh component that may be causing this?
HERE IS THE ERROR: Failed password for root from 10.201.x.xx port 56588 ssh2

[Turgay Cavdar]

Hi,
make_net_recovery has nothing to do with ssh. It uses NFS. Are there any other scripts running ssh on the ignite, or configured HPSIM on ignite?

[Paul F. Bennett]

I'm sure if I understand you last question but we are running HPSIM on our network but the HPSIM server is on a Windows box. The server that host the Ignite server is a HPSIM client

[Turgay Cavdar]

I think the account lock is not caused from make_net_recovery. You can easily understand this by starting make_net_recovery from client and check the client's syslog.log for any ssh connection from ignite server.

[Paul F. Bennett]

I'll give it a shot, thanks