Managed System Status Errors

[hasanajsh]

Dear experts,

In the managed system configuration of an ABAP system I am getting the errors as below.

Could you please suggest what can be done and what might be the reason for this?

Thanks,

Shkelzen

[former_member264351 · Accepted solution]

Hey,

For the issues in the first screenshot:
1. please check note 1890035 to get the info about OS from SAP Host Agent

2.  please check if note 1156442 is valid for your system, if so, apply it to ensure that your RZ70 is able to send instance name to SLD.

Best regards,

Sam Song

[hasanajsh · Accepted solution]

Hi,

I checked Note 1890035  and made the necessary changes.

I am now trying to implement note 1156442 (and 1040487), but I am confused by the popup:

What shall be chosen in this case?

Thanks!

[former_member215345 · Accepted solution]

Choose the first option, it doesn't matter in my humble opinion.

Thanks and regards,

Jayadeep P J

[hasanajsh · Accepted solution]

In this case it seems any would be ok (there was no problem) bu I was looking for some reasoning behind this.

Thanks

[hasanajsh · Accepted solution]

Sam,

The second part of your answer did the trick.

Actually, I have (for one of the systems) No FQDN issue, but the other part is gone.

[former_member264351 · Accepted solution]

so what is your current issue? No FQDN? and the issue about icm instance is gone? If so, please ensure your hosts file has the correct host definition and restart the diagnostics agent.

[hasanajsh · Accepted solution]

Yes, the others are gone.

Basically, as I understood from the note you provided, the issue was with the the release of the managed system.

The only system having the issue (No FQDN found in host 'server_name').

Actually, this system is the SAPTRANSHOST, which had actually in hosts file:

IP     server_name     SAPTRANSHOST

In DEFAULT_PROFILE this was added:

SAPLOCALHOSTFULL     FQDN

(FQDN: the full name)

So, the line in hosts was changed as:

IP     FQDN  server_name     SAPTRANSHOST

I guess this might be the issue.

Do you have any suggestion?

[former_member264351 · Accepted solution]

hi, in this case, I would recommend you to force the FQDN and IP as described in note 1626853.

[hasanajsh · Accepted solution]

Thanks Sam,

I think will have to try that one.

What surprises me is that in Agent Admin UI, the Full Host Name for the given agent is OK.

Regards

[former_member264351 · Accepted solution]

could you please go to LMDB and check the host? Is the  FQDN there correct? If only the FQDN in landscape browser is incorrect/empty, you may reload the host to LMDB cache in landscape browser.

[hasanajsh · Accepted solution]

After implementin the instructions in Note 1626853, nothing changed.

In LMDB the FQDN is empty.

In Landscape Browser, I get:
The LMDB cache is not active or not up to date.

I enabled the cache and reloaded the host (please see figure below).Still having the same situation.

Regards

[former_member264351 · Accepted solution]

hey, could you please send more screenshots to show what you did to force the FQDN in agent admin page? also, could you please restart the daa agent as well? firstly there should be the FQDN in LMDB. Also, what is the current patch level of your lm-service? Please ensure that you are using the latest patch for your current SP level. For example, patch 5 is the latest one for 7.1 sp08.

[hasanajsh · Accepted solution]

Hi,

Attached the changes.

Scope: The given Agent

job.physicalhost.force.push: true

job.physicalhost.fqdn: fqdn

job.physicalhost.ip: ip

Is that OK?

Thanks

[former_member264351 · Accepted solution]

Hi, please don't change the property job.physicalhost.force.push, I see you set it to true, please remove the custom value and let it be false as default. Then go to LMDB and check the Host's FQDN.

BR,

Sam

[hasanajsh · Accepted solution]

Hi,

OK, I put it back to default.

In LMDB still empty.

I have the option there to click: details>>properties and edit the field. Would there be any problem? Would it be overwritten by next automatic data supply?

Thanks

[former_member264351 · Accepted solution]

Interesting. I just test in my system, it works fine. you can try the steps below:

1. go to agent admin page, tab Application configuration, find your agent in the field Scope, go to the application com.sap.smd.agent.application.e2edcc

2. click Edit, then select the property, job.physicalhost.fqdn, click Remove Property,

3. remove job.physicalhost.ip as well

4. save the change

5. Edit again, use 'Add Property' to add  job.physicalhost.fqdn and  job.physicalhost.ip again. save the change.

6. go to LMDB, select hosts tab, then enter your host and check the FQDN.

Just ensure that you do the change for the correct agent which is really relevant to this host. You may try this for another agent as well to test it. It should work.

[hasanajsh]

Thank you all for the answers.

I will try to give some feedback once the issue is resolved. Still trying...:)

Best Regards

[former_member45419]

Hi

pls check this links also...

http://scn.sap.com/thread/2079770

http://scn.sap.com/thread/3154052

Regards

Nayeem

[hasanajsh]

khaja,

thanks for your efforts but your links do not seem to be much related to my issue; they are either general info or specifically different.

[former_member45419]

Hi SH,

pls refer below links ,

http://scn.sap.com/thread/3188849

Managed System Setup of BOE 4.0 system in Solman 7.1 - SAP Solution Manager Setup - SCN Wiki

Home - SAP Solution Manager Setup - SCN Wiki

Regards

Nayeem

[Former Member]

Hi Shkelzen,

Go to LMDB and open the managed system SID and check whether product instance and software component version details is reflected from SLD?

Also check the host agent version, if it is low version update the same and check the below guide for host agent upgrade guide

https://websmp204.sap-ag.de/~sapidb/012003146900000135752013E/SAP_Host_Agent_129.pdf

Rg,

karthik

[hasanajsh]

Hi karthik,

Thanks for your reply.

Host Agent version is ok.

product instance is manual while the software components are automatic, if I understand your question right.

[prakhar_saxena]

Hi

pls check below links its a very common issue

http://scn.sap.com/thread/3296055

Editing Software Component Versions (SAP Library - Enterprise Services Repository for SAP NetWeaver ...

Regards

Prakhar

[former_member183107]

Hi,

Before doing the managed system configuration please go through the below link:-

http://wiki.scn.sap.com/wiki/display/SMSETUP/Managed_System_Checklist

Generally this issue can be solved by uninstalling and installing the latest diagnostic and saphostagent.

It will take only 15-20 mins and the solution can come up as a pretty handy one.

Regards,

Himanshu

[hasanajsh]

Dear Prakhar and Himanshu,

Actually I had to install the Diag 7.2 due to restrictions in Managed system and host agent is ok, updated. the connection of Diag to Solution Manager is fine.

Thanks