Diagnostics agent in managed systems

Hi Gurus,
We are trying to set up RCA in solution manager.
For this, we need to install diagnostics agents in managed systems.
But, i think those agents are already installed in out systems and am not sure of it. Can anyone please let me know how can i find if diagnostic agent is installed in managed system.
Please do clarify one more thing, we need Solution manager diagnostics in solman system and solution manager diagnostics agents in managed systems. Am i correct??
Please help me out on this.
Regards,
Ram.

Hi
I have gone through all the documents that specified earlier itself.
Our OS is IBM iSeries, so we have multiple SAP systems installed in a single LPAR.
So all the diagnostics agents for all those systems installed in that LPAR should exist in that LPAR itself.
In that way, we have DAA folder in usr/sap of that LPAR. In that DAA folder, we have mutliple folder called ADMA97, ADMA98 etc. So these ADMnn folders represent agents for each system right?. So, how to idenfify that particular agent is for which system? All i could make out is from SYS/profile folder in that DAA folder. I have checked the profiles and identified the host name related to a paricular SAP system.
As per SAP document, these diagnostic agents are automatically installed with system installation as of SAP Web AS 7.0 SR3. All our systems are above that level and i still see some diagnostic agents are not installes for some SAP systems. Is there any possibility like this? SO if i again install the missing diagnostic agents, will they be created under the same /usr/sap/DAA folder or will it create a new folder??
Hope am clear...
Awaiting your inputs and thanksin advance.
Regards,

Similar Messages

Diagnostics: Agent disappearing from system landscape

Hello,
I want to monitor my Enterprise Portal (EP7) and use Root Cause Analysis for it.
I installed the SMD Agent on EP7, diagnostics is running on SolMan (SM7).
Now the strange part:
Whenever I start the Agent on EP7, I can see it for a short time in diagnostics (e.g. in the landscape management or in the managed system setup wizard).
But shortly after (between 30 - 60 sec.), the agent disappears from diagnostics. Although it is running all the time, it does not show up anymore.
Diagnostics says, the agent is not connected resp. does not found an agent. But it's up and running (and was visible just seconds before) on EP7.
Anybody any idea, why this behaviour occurs?
Thanks and Regards,
Jan

Hi,
We have used same SIDs (the default DAA) for a few hosts in our landscape and this did not cause a problem.
But in my opinion best to use DAA, DAB, DAC etc in order to remove any room for confusion for both the humans and the systems
Regards,
Srikishan

Assign an Diagnostics Agent to two System Types

On my system I have installed SAP using a C-name but the database which is on the same server uses the physical server name. The server has the diagnostics agent installed but when I go to managed system configuration I am only able to assign that agent to one of the system types. Is there a way I can assign the agent to both the ABAP and the database systems?

Hi Mary,
Install a new diagnostic agent on your physical host.
Regards,

Should I install Diagnostic Agent on managing system itself ?

Dear All,
I am using a solution manager as an managing system .
Should I install the Diagnostic Agent on the managing system , too ?
My solution manager is 7.01 EHP1 SPS22, I find there exist a directory /usr/sap/SMD , so it seems the Disgnostic Agent is installed during the solution manager installation . But in the Work Center -> Root Cause Analysis -> Agent Administration , it returns a "service cannot be reachable " error,
"URL https://<solution manager host >:8000/webdynpro/dispatcher/sap.com/tcsmdnavigation/StandaloneApp call was terminated because the corresponding service is not available.
And in the http://<solution manager host>:50000/smd , managed system -> setup wizard , I choose the solution manager SID , and next, it show the SMD agent hasn't been found.
I re-installed the SMD agent , but the result is the same, and I've tried to install the Diagnostic Agent 7.11 and still the same.
Anyone encounter the same problem as me ??
Thanks.

Hi, David,
In Solman_Setup , The initial and Basic configuration are finished without error ( green light).
And in managed system configuration , configure system, the first step check prerequisities failed with red light; the detail error messages is as below :
It seems some kind of service not activated in SICF , but not for sure.
Service cannot be reached
What has happened?
URL https://sapsolmgr.centurydsp.com:8000/webdynpro/dispatcher/sap.com/tcsmdnavigation/StandaloneApp call was terminated because the corresponding service is not available.
Note
The termination occurred in system SM2 with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-https-c:000-u:SAPSYS-l:E-i:SAPSOLMGR_SM2_00-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team
Thanks for your reply.
Enddy.

Diagnostics Agent installation - which SID for the systems in your landscap

Hi,
I have a question in regads to installing the Diagnostics Agent on the systems in your landscape: ie. I want to install the Diagnostics Agent on all systems, and SAP suggests the system ID "DAA" as standard sid. From my experience there are no errors or exceptions when I use the system id DAA for a few or all systems.
However, will I run into problems later on (for example, when using root cause analysis, etc.)? Can I use the standard system id DAA for several systems/hosts, or should I use a seperate system ID (DAA, DAB, DAC, etc.) for each Diagnostics Agent?
thanks,
Walter

Hi,
We have used same SIDs (the default DAA) for a few hosts in our landscape and this did not cause a problem.
But in my opinion best to use DAA, DAB, DAC etc in order to remove any room for confusion for both the humans and the systems
Regards,
Srikishan

Diagnostics Agent 7.11 on iSeries

I"ve gone and got the installation master DVD and the Kernel DVD but cannot find the standalone Diagnostics Agent. Following You can download Diagnostics Agent installation DVDs from SAP Service Marketplace at: http://service.sap.com/swdc Download SAP Support Packages Entry by Application Group SAP Technology Components SAP SOLUTION MANAGER SAP SOLUTION MANAGER 7.0 EHP1 Entry by Component Agents for Managed systems DIAGNOSTICS AGENT 7.11 <choose operating system of managed> gets me to the area but I'm not seeing it for our system.
Am I missing it or has it not been released for the iSeries yet? If not, then how is anyone else getting this installed if no agent is available?
Thanks.

Hi Ryan,
the Diagnostics Agent Installation based on SAP NetWeaver 7.1 EhP1 is supporter for OS400. Unfortunately, the standalone SMD only installation kit was not release for the OS400 platform and therefore is necessary to use the standalone option found in the SAP NetWeaver 7.1 EhP1 installation media. You can follow the 711_Diag_Agent_Setup_Guide.pdf file attached in SAP note 1234387 to find the right components needed for this install.
Best regards,
Luis Gonzalez

Managed System Setup Wizard Status " ? " SPS 15

Dear All,
I have a problem with my SMD.
I have already upgrade the Solution Manager 4.0 from SPS 13 to SPS 15.
I want to setup E2E Root Cause Analysis for CRM system.
So I configured SMSY since I didn't configure SLD yet.
I've already installed SMD Agent in managed system successfully also.
When I run the Diagnostics Setup -> Managed System -> Setup WIzard,
in the Setup Parameter Step , it said that " No SMD Agent is currently available (ie not assigned). Please install an agent for jktgrhxsapc1 or unassign an existing agent in Agent Administration Why is that so ?
In the Agent Administration ( DIagnostics Administration -> Managed SYstem -> Agent Administration) found that the agent is online.
Second, In managed system setup wizard - System Selection Step, there's an unknown system with SID '???' and the status said that 'Some SMD Agent Runnning on host not belonging any successfully published solution' . Where can we find the log if we have an error when publishing solution ?
Thanks in advance,
Adhi

Hi Labinot,
I have checked the agent log looks like no error,
id loaded TTL refType
applications:com.sap.smd.agent.application.global.configuration true 0 strong
applications:com.sap.smd.agent.application.tracing true 0 strong
applications:com.sap.smd.agent.application.wilyhost true 0 strong
applications:com.sap.smd.agent.application.flightrecorderdumpscan true 0 strong
applications:com.sap.smd.agent.application.telnet true 0 strong
applications:com.sap.smd.agent.application.filesystem true 0 strong
applications:com.sap.smd.agent.application.logviewer true 0 strong
applications:com.sap.smd.agent.application.remotesetup true 0 strong
applications:com.sap.smd.agent.application.database true 0 strong
applications:com.sap.smd.agent.application.datacollector true 0 strong
applications:com.sap.smd.agent.application.runtime true 0 strong
applications:com.sap.smd.agent.application.connectors true 0 strong
applications:com.sap.smd.agent.application.wily true 0 strong
Apr 10, 2008 7:13:07 PM [Thread[SMDAgent connection thread,5,main]] Info       [p4://jktgrhxsapl1:50604] Registration done.
Apr 10, 2008 7:13:07 PM [Thread[SMDAgent connection thread,5,main]] Info       [p4://jktgrhxsapl1:50604] Agent ready.
Apr 10, 2008 7:27:25 PM [Thread[Thread-37,5,main]] Info       Returned service object :com.sap.smd.core.runtime.agent.LogService@14cee41f
Apr 10, 2008 7:27:26 PM [Thread[Thread-34,5,main]] Info       Returned service object :com.sap.smd.core.runtime.agent.LogService@14cee41f
any other idea?
-Adhi-

SMD - Diagnostic Administration -- Managed Systems takes long time

Hi All,
On SMD administration URL , http://system:50000/smd ---> Diagnostics administration ---> Agent Administration --> managed systems takes very long time.
Sometimes it never ends and keep on going...
CPU utilization is also very high...
Have anyone encountered this issue ?
We are using Solman 7.00 on Solaris, DB is oracle.
Thanks!

Reply with ur System Technical Note,
find below DOCS for Solman System Technical Config,
https://websmp103.sap-ag.de/~sapdownload/011000358700000255562007E/Sizing_Guide_SM_70_SP15.pdf
https://websmp103.sap-ag.de/~form/sapnet?_FRAME=OBJECT&_HIER_KEY=501100035870000015092&_HIER_KEY=601100035870000179416&_HIER_KEY=601100035870000179443&_HIER_KEY=701100035871000457214&#HOME
Basically SMD is mostly dependant on J2ee Heap and Abap Configuration. Set up the required Heap and T-Code ST02 paramaters properly and call the SMD again.
Regards
Srikanth Mandalapu
Edited by: srikanth mandalapu on Oct 10, 2008 12:11 AM

Managed System Configuration step Assign Diagnostics Agent

Dear Experts,
We've newly instaled solution manager system 7.0 Ehp1 via latest sp stack 25 on aix 6.1, we've completed initial and basic configuraiton successfully via solman_setup, and instaled wily introscpe on same host with solution manager system,
Now i am trying to managed system configuration for solution manager system via solman_setup step Assign Diagnostics Agent as demo link below
https://service.sap.com/~sapidb/011000358700001735062008E
I opend http://>SOLMANHOST>:<SOLMANPORT>/smd/go/ADMIN_AGENT
>> Agent Candidates Management
>> Connection Parameters
>> Custom SLD Parameters > Aply and the selected the SMD instance then trying to attached via password SMD_ADMIN
But agent registration is waiting, SMD_ADMIN user is creating when i execute intial configuration, after i change the intial password, password is correct, so why the agent state is waitng status, i also push sld Setting for all from SMD view tab,
I've also try to restart SMD agent, /usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log file after restart
Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       Starting SMDAgent ...
Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       ===> Establishing connection to server 'ms://ccisolman:8101/P4
Oct 28, 2010 11:07:28 AM [Thread[Connector,5,main]] Info       Smd connector is disabled because no SLD association and no credentials found.
Oct 28, 2010 11:07:32 AM [Thread[SLD-Registration,1,main]] Info       [SLDReg] Next try to push instance data in SLD is Thu Oct 28 23:07:32 EEST 2010
Best Regards

hi
pls chk again your sld parameters and check the correct user name, password entered in agent connection management under CUSTOM SLD(in agent candidates management)
jansi

Managed System Setup / Configure Diagnostics for Solution Manager itself

Hello,
I'm trying to run the "Managed System Setup" for the Solution Manager itself and
I got a problem in the step 4 (Diagnostics Configuration / Configure Diagnostics):
In the new opened window is only the ABAP stack displayed and the Java stack
is missing.
Does somebody know how to make the java stack visible?
From my point of view seems the configuration of the SMSY ok. The java stack is also
as "relevant" set.
The Solution Manger 7.0 EHP1 is on SP25.
Thanks in advance for your help!
Kind regards,
Joern

Hi Jorn,
I dont think its happening just because of your CR Content.
Still If you want to update it,then go to Administration Tab in SLD->>Import the latest CR Content from there.
As the latest CR Content is :SAP CR Content Version (sld/active): SAP_CR 7.6 (produced 11/17/2011)
And Jorn if you are stucked in the Diagnostic Agent registration then Go to Agent Candidate Administration->>In connection
Parameters Tab go to->>Custom SLD Connection Parameters->>Apply->>Mark the Diagnostic Agent you want to
connect->>Attach->>Give the password of the SMD_ADMIN->>Apply->>This way you will connect to the available Diagnostic
Agent.Hope this will help your problem.
Thanks & Regards
Ajitabh
Edited by: jitu001 on Dec 23, 2011 5:47 PM

Diagnostics System: Managed System Setup Wizard

Hi there!
I have installed the Host Agent and Diagnostic Agent on a test-system successfully. Now I have tried to start the Setup Wizard for managed systems (http://<hostname>:port/smd). The system collection was no problem, but the Setup Parameters. If I choose the directories of the "System Install Path", the "Instance Path" and also the "Instance Number" the following Message appears: "No Diagnostics Agent available at this time Please install or start an SMD Agent for <hostname>".
I don't know the reason, because the Diagnostic Agent is running and I think my parameters will be okay:
System Install Path: usr/sap/DAA/
Instance Path: usr/sap/DAA/SMDA97/
Instance Numer: 97
Is there a failure?
I look forward to your reply!
Best reagrds,
Andreas

Hi there!
I have found an interesting warning:
Managing System '<hostname>' is registered in the SLD but the CIM declaration is not valid, the agents cannot be attached correctly. check SLD Managing system declaration. (detail: CIM_ERR_FAILED: Cannot find SAP_BCCentralServiceInstance of SAP_J2EEEngineCluster SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="<hostname>" in SLD LR)
I think it is the reason for my problems .. Can anybody help me?
Best regards,
Andreas

Diagnostics Agent Installation in MCOD enabled systems

Hi Experts,
We are connecting MCOD anabled managed systems to Solution Mamager 7.1 SPS10.
But little confused with Dagnostics agent strategy; whether Agent-On-the-fly feature can be used in this case or not?
I am following SAP Note 1365123 - Installation of Diagnostics Agents.
Our MCOD structure is as below:
All Development systems on one physical host
All Quality systems on one physical host and
no MCOD enabled for Productive systems.
Thanks in advance,
Rahul

Hi Alexander,
Thank you for the quick reply. Can you clarify below:
MCOD database host is having 3 DB instances (of development systems) and all the 3 instances are connecting to single solution Manager system.
Does each DB instance require seperate Diag. agent or single Diag. agent will work for all the 3 instance to connect with solution manager?
Thanks in advance,
Regards,
Rahul

Solution Manage Diagnostics - error in the system setup

Hello,
I have installed SMD and I installed one system with the Setup Wizard of the SMD. According to the result of the setup, it was successful.
However, when I do a self check in SMD, I get the five following errors in the Monitored Setup node :
5 error(s) found:
No DB agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No JVM startup parameters setting status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No Roles assignment status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No SSO Setup status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No Telnet agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
Can anybody help me ?
Thank you

If you goto http://server:port/smd >>> Diagnostic Setup >>> Diagnostic System >>> Setup Wizard, do you have a message similar to:
Last Diagnostics setup wizard execution on Tue Oct 09 13:34:44 2007 :
- 0 setup steps disabled by user
- 13 setup steps succesfully executed
- 0 setup steps executed with warnings
- 0 setup steps in error
If you do, your Diagnostic server is correctly setup.
For Managed system, same thing, http://server:port/smd >>> Diagnostic Setup >>> Managed Systems >>> Setup Wizard, or check setup results to make sure it's completed.

Solution Manager Diagnostics: Agent Architecture

Hi there,
current I write a degree dissertation about Solution Manager Diagnostics. In different books, documentations and manuals I read about Agents which must be installed on the managed system. But I find no exactly description about the agents architecture. In a book about the Solution Manager is written, that the structure includes two tiers. The first tier are the core agents, but there is nothing explained about the second tier ... Is a core agent the same like a host agent?
Can anybody explain me (exactly) the differnt functions of the agents (core, host, diagnostics, wily-agent)?? Or maybe some links will be helpful.
Thanks and best regards,
Andreas

> Can anybody explain me (exactly) the differnt functions of the agents (core, host, diagnostics, wily-agent)?? Or maybe some links will be helpful.
I would start with
http://service.sap.com/diagnostics
There are lots of (detailed) documentations available.
Markus

Diagnostics agent not getting registered in Solution Manager

Hello SAP Experts,
I am using Solution Manager 7.1 SP Stack 12. I installed diagnostics agent on one of the managed systems and fired the command below for registering it in Solution manager (since I did not do this during diag agent installation):
/usr/sap/DAA/SMDA<instance no>/script/smdsetup.sh managingconf hostname:"sapms://<FQDN of Solman>" port:"81<instance no of Solman>" user:"smd_admin" pwd:"<password"
This command returned successful message. However, when I login to Solution manager and go to Agent administration, I am unable to see the above managed system diagnostics agent. Please help.
Thanks & Regards,
Kunal.

Hi Adi,
Thanks for the reply. I found the below SMDSystem.7.log at location /usr/sap/DAA/SMDA98/SMDAgent/log
Apr 24, 2014 1:21:05 PM [Thread[Connector,5,main] ] Error Failed to connect to SMD server - user: smd_admin
Apr 24, 2014 1:21:05 PM [Thread[Connector,5,main] ] Warning Connecting to SMD server ms://<hostname>/P4 failed - error counter: 1690 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: there are no access points for service: P4 registered on the message server]
Regards,
Kunal.

Diagnostics agent in managed systems

Similar Messages

Maybe you are looking for