DX Unified Infrastructure Management

We have deployed RSP probe 4.03.Windows servers have been discovered, but when trying to discover one of the linux server we are getting error message mentioned below:

Also attached plink command from probe server to the server in question.

Robot version 7.63

Nimsoft Version 7.5

Support suggested for trying lower versioin of rsp probe version 2.60, 2.66, 2.68 or 2.80.

But while deploying these probes getting error "Dependency Not found"

Does probe 2.60, 2.66, 2.68 or 2.80 is supported by robot version 7.63.

===========================================================================

cmd_discover_host: (discover_host) - called from 172.16.1.159/35073

Jul 27 13:23:22:468 [2800] rsp: GetConnection: Get DB connection

Jul 27 13:23:22:468 [2800] rsp: GetConnection: Connection object found in Pool

Jul 27 13:23:22:468 [2800] rsp: thrDiscoverHost: Timeout set by callback, 400 seconds

Jul 27 13:23:22:468 [2800] rsp: thrDiscoverHost: Called with hostname=129.1.3.50

Jul 27 13:23:22:468 [2800] rsp: thrDiscoverHost: Hostname resolved to suse-test-srv

Jul 27 13:23:22:468 [2800] rsp: thrDiscoverHost: Detecting the IP address for the specified host

Jul 27 13:23:22:484 [2800] rsp: sockClose:0000000002A23D80:172.16.1.160/55073

Jul 27 13:23:23:498 [2800] rsp: sockConnect - connect to suse-test-srv 48000 failed 10061

Jul 27 13:23:23:498 [2800] rsp: thrDiscoverHost: Discovering OS

Jul 27 13:23:23:498 [2800] rsp: connect_ssh: do ssh_connect for host suse-test-srv

Jul 27 13:23:23:560 [2800] rsp: authenticate: try to authenticate

Jul 27 13:23:23:622 [2800] rsp: authenticate: authenticate methods: 20

Jul 27 13:23:23:622 [2800] rsp: Authentication failed for host suse-test-srv

Jul 27 13:23:23:622 [2800] rsp: thrDiscoverHost: Connection attempt with suse-test-srv failed.

Jul 27 13:23:23:622 [2800] rsp: Time taken in discovering suse-test-srv=1

Jul 27 13:23:23:622 [2800] rsp: SREPLY: status = 3(invalid argument) ->172.16.1.159/35073

Jul 27 13:23:23:622 [2800] rsp: do_disconnect: starting disconnect

Jul 27 13:23:23:622 [2800] rsp: do_disconnect: no connection

Hello. Prashant.

Regarding SuSE 11 and RSP probe, there are 2 things please take care them.

1. RSP 4.03 is not able to discover SuSE 11 because our OS defection code (the file name is "OS.lua") does not recognize Kernel 3.X.

   The problem was fixed with RSP 5.01. I'd recommend that you try the latest RSP probe (as of today 5.10)

2. SuSE is using keyboard interactive SSH, unfortunately it is not something that RSP works well with.

Please configre SSH Mode as our documentation mentions.

rsp (Remote System Probe) Release Notes - CA Unified Infrastructure Management Probes - CA Wiki

Note: The rsp probe supports only password-based and key based authentication.

Keyboard-Interactive and authentication less method are not supported.

If the UNIX-based remote server is not password-based or key-based authentication enabled, the rsp probe is not able to discover the remote host.

Hope it helps.

Yu Ishitani

Hi Yu Isitani,

Thanks for your response to the issue.

I tried installing rsp probe 5.10 but getting dependency error.

I have robot version 7.63 running, does it has any dependency for the rsp probe 5.10, its only version 4.03 I am able to deploy successfully.

I checked the dependency for both the packages and found no difference.

Dependency Error:

Installed Packages on the Probe Server:

Not able to figure out the dependency required by version 5.10

Hello, Prashant.

I am sorry that I'm not sure if rsp 5.10 has dependency.

If it is development environment, is it possible to see how it goes if you upgrade ROBOT to the latest (7.80) ?

Thanks

Yu Ishitani

Hello. Prashant.

I have received your response through community admin.

Thanks for attaching CA software logs.

This is problematic logs. It indicates that RSP is having issue with SuSE side SSH daemon.

Please read the doc and change SSH config as necessary basis.

Aug 4 10:05:32:956 [3012] rsp: authenticate: try to authenticate
Aug 4 10:05:33:002 [3012] rsp: authenticate: authenticate methods: 20
Aug 4 10:05:33:002 [3012] rsp: Authentication failed for host <REMOTE DEVICE HOST NAME>

rsp (Remote System Probe) Release Notes - CA Unified Infrastructure Management Probes - CA Wiki

Note: The rsp probe supports only password-based and key based authentication.

Keyboard-Interactive and authentication less method are not supported.

If the UNIX-based remote server is not password-based or key-based authentication enabled, the rsp probe is not able to discover the remote host.

TO Community Users

We'd like to ask you spend a minute to be careful before sharing CA Product logs in the community.

If you want to share CA software logs in the community, it may include some sensitive properties such as IP Address or hostname.

An additional effort of masking or removing them will be highly regarded since the community is public thread.

Thanks

Yu Ishitani

Hi Yu Ishitani,

Below is my sshd config details, path for it is /etc/ssh on the server attached.

Let me know if any details needs to be corrected as I am novice on the linux side.

Hello. Prashant.

Let me give you an example from my SuSE box where I can successfully discover from RSP probe.

I guess the following 3 lines will change behavior. (NOTE - I'm not responsible for affects brought by SSH config changes. Consult System Admin before change)

PermitRootLogin yes (Default value - Comment out)

PasswordAuthentication yes (Default value - no)

PermitEmptyPasswords no (Default value - Comment out)

Thanks

Yu Ishitani

Hello. Prashant.

I've received your comment below via community admin. I'm glad if that helps.

> The solution suggested worked.

I have 2 requests.

1. Would you please make an update as reply to thread, not email response ? Your email response just goes to community admin but not reflected as reply to thread. It is proper usage of the community.

2. If your problem have been resolved, mark the thread as resolved. It is also proper usage of the community so that everyone can see what resolved the issue.

Thanks

Yu Ishitani

Hi Yu Ishitani,

Solution suggested worked.

Many thanks for your help and suggestions.

Regards

Prashant

rsp probe 5.10 and changes to the sshd_config resolved the issue.

Many thanks to Yu Ishitani for the suggestion and resolving the issue.

Regards

Prashant