Diagnostics Agents upgrade

Hello,
We would like to upgrade our Diagnostics agents to 7.11 based on http://service.sap.com/diagnostics -> Diagnostics Agent Setup Guide information.
It seems that to upgrade the agents means desinstall/reinstall them all ?
Now the queston is: is there a easy way to check the Diagnotics agent version on o.s. level
We have Diagnostics agents installed under hp-ux filesystem:
/usr/sap/DAA/
/usr/sap/DAA/exe contains the (shared) kernel
Using Root Cause analysis -> Agent Administration , wa can see that all agents versions are 7.01.6.1.20100326060452
Thank you and best regards,
Cédric Decreton

Hello Cédric Decreton
Unfortunatelly you'll need uninstall the old agents
To execute a mass installation, check this note, it'll help you a lot to install the new version in all your landscape.
1294713 Mass Deployment of SAP Diagnostics Agent 7.11
Pay attention to two points
1) Using Root Cause analysis -> Agent Administration , wa can see that all agents versions are 7.01.6.1.20100326060452
This is not the version of Diagnostics agent, this is the version of component LM-SERVICE. How it works ?
When you install the Diagnostics Agent, you must execute the authentication with the Diagnostics Server using host, port, user and password parameters. When the authentication is successful, the Diagnostics Server will deploy lots of applications in the managed system where the Diagnostics agent is installed. The LM-SERVICE is the component that store these applications. For this reason is MANDATORY and VERY IMPORTANT always have the latest patch level of your LM-SERVICE. I strongly recommend the upgrade to Solution Manager SP24 that deliver LM-SERVICE 7.01.7.0. Pay attention that yesterday was released patch level 1 of LM-SERVICE 7.01.7, and it delivers 39 important corrections. If you want stay with 7.01.6, apply the latest patch level from here.
http://service.sap.com/patches => Support Packages and Patches - Entry by Application Group => SAP Technology Components => SAP SOLUTION MANAGER => SAP SOLUTION MANAGER 7.0 EHP 1 => Entry by Component => Solution Manager JAVA Stack => # SOLMANDIAG 7.01 => # OS independent => LMSERVICE06P_2-20004805.SCA Patch 2 for SOLMANDIAG 7.01 SP06
2)
Solution manager Diagnostics agent 7.0X => /usr/sap/DAA or SMD/JXX
Solution manager Diagnostics agent 7.11 => /usr/sap/DAA or SMD/SMDAXX
thanks and best regards

Similar Messages

SCOM 2012 R2 agent upgrade fails crippling agents

Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues. Warning this issue is not for the faint of heart.
Plan:
I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2. I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters.
Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
Problem:
I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state. At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
be done. What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate. This is no problem and I am able to do this. (Note: all other methods of agent removal did not work ie:
Cleanmom.exe utility or add remove)
Task:
Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
Notes:
Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down.
Looking at the MSI log, I see a common issue among systems that had this problem.
******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
CustomAction returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Action ended 8:08:44: RemoveExistingProducts. Return value 3.
Action ended 8:08:44: INSTALL. Return value 3.
Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine. Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent.
Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
Action ended 8:08:11: FindRelatedProducts. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_OM_AGENT_FOUND.
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a 64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE). This is the point of my confusion and my suspicion as the cause of the problem I am having.
Concluding thoughts:
Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid.  Could a 32 bit agent have got on this 64 bit server based on the details of this log? Would this
cause my agents to fail the upgrade? I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
Thanks in advance if you took the time to read this and think about it. Extra points if you have any extra thoughts!
Keith

Hi,
Have you used Requirement to limit the platform when you deploy application with SCCM.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SMD Agent 7.00 or Diagnostics Agent 7.11

Hello,
Our managed systems are running on NetWeaver 7.00.
We are currently implementing SAP Solution Manager Diagnostics using SOLMAN_SETUP guided procedure.
In https://service.sap.com/swdc -
Support Packages and Patches - Entry by Application Group" SAP Technology Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0 EHP 1" Entry by Component" Agents for managed
there are 2 kinds of Diagnostcis Agents :
1. SMD Agent 7.00
2. Diagnostics Agent 7.11
Question :
Can we install a Diagnostic Agent 7.11 on our managed systems running on NetWeaver 7.00 or must we install SMD Agent 7.00 ?
Are Diagnostics Agent 7.11 supported for managed systems running on NW 7.00 ?
Best regards
PC

Hi
To avoid libraries conflicts it is highly recommended to install a Diagnostics agent which has the same kernel release
that the SAP systems already installed on the host.
Refer the doc in this [link|https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_HIER_KEY=701100035871000526434&_OBJECT=002007974700000409092009E&_SCENARIO=01100035870000000112&] Section 2.3 Managed system page no:8
Hope this helps you
regards
Naveen

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

Diagnostics Agent 7.11 vs SMD Agent 7.00

Hello,
In our SAP System environment, most of managed systems are running under SAP NW 7.0 platform.
We are currently installing SMD Agent 7.00. The installation is not finished and I was wondering if we can install Diagnostics Agent 7.11 on managed systems running on SAP NW 7.0 ?
In other terms :
SMD Agent 7.00 have to be installed only on SAP NW 7.00
Diagnostics Agents 7.11 have to be installed only on SAP NW 7.11 or also on SAP NW 7.00 ?
Thanks in advance for your feedback
Best regards
P. Cuennet

Yes you can install diagnostics agent 7.11 for a managed system 7.00
It's even possible for a managed system 6.40
Prerequisite is that your Solution Manager stack verison is 20 or higher (EHP1)
You can find the details in the installation guide for diagnostics agent 7.11 on SAP service marketplace:
[https://service.sap.com/diagnostics]

Diagnostics Agent 711 - SAP Host Agent - Installation on a cluster environm

Dear all,
We have the following architecture in our productive environment :
1. Cluster 01 is composed of 2 nodes.
   On Cluster 01, only "Database" and "Central Services" are running
   for 5 productive SAP systems.
2. Cluster 02 is composed of 6 nodes.
   On Cluster 02, only "Central Instance" and "Application Server"
   are running for 5 productive SAP systems
As read in "Diagnostics Agents installation Strategy", rules #4, slide 12 :
===================================================================
- Do not install a Diagnostics Agent on host that only run Database
or SAP Central Services.
- Install a Agent on EACH host running a Central Instance (CI)
and / or a Dialog Instance
===================================================================
For our productive environment, we do have to install Diagnostics Agents 7.11 on cluster 02 where we have CI + AS running.
Questions :
1. How do we monitor "database" and "central services" data on cluster 01 (DB + CS) as far as no "Diagnostics Agents"
   are installed ?
2. Do we have to install the new "SAP HOST AGENT" in our cluster 01 ?
3. As written in "Downloading and Installing Package SAPHOSTAGENT"
   guide, "you only need to install the host agent host taht not have
   an SAP Component". Does it mean that the new "SAP HOST AGENT"
   will have to be installed on our cluster 01 to monitor "DB+CS" data ?
4. What are for SAP a host that not have SAP Component ... ?
    "Database" and "Central Service" running for a SAP system should be consider as SAP Component or not ... ?
5. What is the difference between the new "SAP HOST AGENT" delivered by SAP today 23.11.2009
    and the "Wily Host-Level Introscope Agent"
   delivered by CA ?
Best regards
PC

Yes, it has to be installed.

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

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

Unicode Kernel Diagnostics Agent install on non_unicode kernel System.

We have some ECC 6.0 ABAP systems that do not have a unicode kernel. The diagnostics agent setup guide for Netweaver 7.0 says you should have a unicode kernel DVD for the diagnostics agent install. I was hesitant about using a unicode kernel for the SMD agent and a non-unicode kernel on the ECC 6.0 instance. I tried installing the agent with the non-unicode kernel DVD and got an error that would not let me continue. Anybody have experience with this?

Carl,
David is Right, SMD is itself an SAP Instance(to be considered a seperate system-SAP Note:1365123) with its own exe. So it shouldn't be a problem.
Regards,
Jagan

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

2012 Upgrade to R2 - Client Protection Agent Upgrade - Reboot?

MSFT states in their upgrade doc for DPM 2012 R2 "You must upgrade all of the protection agents. This might require a restart of the protected computer."
What has been your experience reboot/no reboot as I know agent upgrades during past couple years (updates) haven't required a reboot?
If have to do reboot not good as I have over 175+ production machines.
Thanks,

Hi,
DPM 2012 R2 UR3 agent update does a require a reboot and it is documented several places in the UR3
article.
Note This UR3 agent update requires you to restart protected servers in order to create or change protection groups. VM backups may fail in Windows Server 2012 R2 until the server is restarted.
Important information
We recommend that you restart the protected computer after you apply the Update Rollup 3 Agent update.
If Protected Computers are not restarted after you apply Update Rollup 3, the following things can occur:
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.
It says recommend, not required. Like I said, at least 1 agent I updated using the DPM Console went straight to OK, no reboot required. The others went to reboot required, but after removing the registry flag, worked fine. I pointed the servers are the new
DPM install (new datacenter) and was able to recreate all of the protection groups with no issues. We are only backing up Server 2012/Server 2012 R2 servers though (both hyperV and SQL clusters), so maybe the issues are for 2k8 servers.

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,

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,

Diagnostics agent config: SMD user

Hello.
I have installed a diagnostics agent, but when I start the agent, it is not able to register in the server.
My question is, how can I check the user and password of Solution Manager that has been entered in the Agent installation (smd_admin, normally)? If this user/password was mistyped during installation, how can I change it afterwards?
I have found some file with info about user and password but it is encrypted.
Thanks for your help.
Fermín.

Hello.
I have installed a diagnostics agent, but when I start the agent, it is not able to register in the server.
My question is, how can I check the user and password of Solution Manager that has been entered in the Agent installation (smd_admin, normally)? If this user/password was mistyped during installation, how can I change it afterwards?
I have found some file with info about user and password but it is encrypted.
Thanks for your help.
Fermín.

IS Diagnostics Agent Version 7.01 SR1 available?

Hi,
We have solution manager version Versions 7.0 EHP1 < SP20 so Diagnostics Agent Version 7.01 SR1 complies with the version of the Solution Manager system.
But I can not find dowload available on market pla

Looks like it is required. My version is 1.6

Diagnostics Agents upgrade

Similar Messages

Maybe you are looking for