hurtreks Absent Member.
Absent Member.
177 views

Solaris Server discovered as IP only device

Hi,
I want to discovered solaris server.It already in devices discovered list but only as IP only device. When i checked the scan log i only found this:

2009-08-31 15:14 Write 216.open ssh://10.3.227.10 maxkbs=0 agentprofileid=201
2009-08-31 15:14 Info No credentials configured for the session type: winrpc
2009-08-31 14:04 Write 1779.open ssh://10.3.227.10 maxkbs=0 agentprofileid=201
2009-08-31 14:04 Info No credentials configured for the session type: winrpc
2009-08-31 13:56 Write 970.close
2009-08-31 13:26 Write 970.open ssh://10.3.227.10 maxkbs=0 agentprofileid=201
2009-08-31 13:26 Info No credentials configured for the session type: winrpc
2009-08-31 13:20 Write 215.close
2009-08-31 12:50 Write 215.open ssh://10.3.227.10 maxkbs=0 agentprofileid=201
2009-08-31 12:50 Info No credentials configured for the session type: winrpc
2009-08-31 12:38 Write 57338.open ssh://10.3.227.10 maxkbs=0 agentprofileid=201
2009-08-31 12:38 Info No credentials configured for the session type: winrpc
2009-08-31 12:32 Write 56620.close
2009-08-31 12:02 Write 56620.open ssh://10.3.227.10 maxkbs=0 agentprofileid=201
2009-08-31 12:02 Info No credentials configured for the session type: winrpc
2009-08-31 11:56 Write 55919.close
2009-08-31 11:26 Write 55919.open ssh://10.3.227.10 maxkbs=0 agentprofileid=201
2009-08-31 11:26 Info No credentials configured for the session type: winrpc

Anybody have an idea what it is happen?

I also found that sometimes Agent Communicator is not running, is it normal?

TIA,

Stefanus
0 Likes
7 Replies
Micro Focus Expert
Micro Focus Expert

Re: Solaris Server discovered as IP only device

Stefanus,

Not having Agent Communicator running is a problem.

As for the error in the logs, do you have the appropriate SSH credentials configured in the Agent profile used for the device?

Which DDMI version are you running?

Regards,
Brindusa
0 Likes
hurtreks Absent Member.
Absent Member.

Re: Solaris Server discovered as IP only device

Hi Brindusa,

Thanks for your response.I forgot to inform that i use agentless method.I use DDMI 7.50.

TIA,

Stefanus
0 Likes
hurtreks Absent Member.
Absent Member.

Re: Solaris Server discovered as IP only device

Hi Bridusa,
i already have the appropriate SSH credentials configured in the Agent profile used for the device.

TIA,

Stefanus
0 Likes
Matthew Darwin Absent Member.
Absent Member.

Re: Solaris Server discovered as IP only device

Check the diagnostics panel in the device manager of the device in question to review the credentials that will be used to contact the device.

Look for the line that says: "Deployment credentials"
0 Likes
hurtreks Absent Member.
Absent Member.

Re: Solaris Server discovered as IP only device

Hi Matthew,

I already checked the "Deployment credentials" line in the diagnosis panel. I found that the credential used is same with the SSH credential i already configured before.The credential is same for all Solaris server.And i have 5 other Solaris server that can be scan by use this credential.

TIA,

Stefanus
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Solaris Server discovered as IP only device

Stefanus,

If the log provided is the entire deployement log from the Device Manager, looks like the session opens but there is no feedback.

You mentioned the Agent Communicator is not running sometimes. Could you please check the discovery log and the ACS wrapper log if there are any errors, especially around the time the requests go out to your Solaris machines?

Regards,
Brindusa

0 Likes
hurtreks Absent Member.
Absent Member.

Re: Solaris Server discovered as IP only device

Hi Brindusa,

I found this error from the discovery.log at around the time the request go out

2009-09-10 12:12:40,272 ovedDiscEng:IDD[7608]: WARN - Cannot(process_string) : (86557.log "This client is not connected." error error=-53
)
2009-09-10 12:12:40,272 ovedDiscEng:IDD[7608]: WARN - Cannot(process_string) : (86557.failure
)

I also attached the error i found from discovery.log when the Agent communication failed to run.

From the wrapper_acs.log i only found this error.

INFO | jvm 1 | 2009/09/10 12:54:54 | WrapperSimpleApp: Encountered an error running main: java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key acsCommandTooLarge00
INFO | jvm 1 | 2009/09/10 12:54:54 | java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key acsCommandTooLarge00

Can you help me to find out what this means?

TIA,

Stefanus
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.