Solution manager Diagnostiocs Agent start up at server reboot

[Former Member]

Hello, We are running solution  manager 7.1   and have SMD agent  installed on the child systems with on-the-fly option. Is there a way to set up the SMD agent to start up automatically on a server reboot , or do  you have to create a script for it?  

[former_member206167]

You have to add an entry su -c daaadm startsap SMDA97 to file /etcinit.d

Hope this helps

[Former Member]

Hi Kenneth,

If the SMD Agents are on Windows, you can enable Auto startup at the Services level.

If the SMD Agents are on UNIX, ensure the instance profile of the SMD Agents have the parameter at the end of the instance profile -

Autostart = 1

Regards

Deepak

[Former Member]

is the  

Autostart = 1   in lowercase?    autostart=1 

[Former Member]

Correction  I see in profile that the

Autostart =1 is already set , However SMD did not start last  2 times  server as rebooted

SAPSYSTEMNAME = SMD
SAPSYSTEM = 97
INSTANCE_NAME = SMDA97
DIR_CT_RUN = $(DIR_EXE_ROOT)/$(OS_UNICODE)/hpia64
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/SMD_SMDA97_grrapi22
SETENV_00 = DIR_LIBRARY=$(DIR_LIBRARY)
SETENV_01 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_02 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_03 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
SETENV_04 = PATH=$(DIR_EXECUTABLE):%(PATH)
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
_CPARG0 = list:$(DIR_CT_RUN)/sdiagag.lst
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)
_CPARG1 = list:$(DIR_CT_SAPJVM)/sapjvm_6.lst
_CPARG2 = source:$(DIR_CT_SAPJVM)
Execute_01 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG1) $(_CPARG2)
#-----------------------------------------------------------------------
# JStart configuration
#-----------------------------------------------------------------------
SAPJVM_VERSION = 6.1.047
DIR_SAPJVM = $(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_6
jstartup/vm/home = $(DIR_SAPJVM)
jstartup/bootstrap = no
alert/disable_j2ee_monitoring = 1
jstart/checkVersion = false
#-----------------------------------------------------------------------
# Start SMD Agent
#-----------------------------------------------------------------------
_JC = jc.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_02 = local rm -f $(_JC)
Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/jstart$(FT_EXE) $(_JC)
Start_Program_00 = local $(_JC) pf=$(_PF)

SAPGLOBALHOST = grrapi22
smd/agent/type = 710
jstartup/instance_properties=$(DIR_INSTANCE)/smdagentgroup.properties
Autostart = 1

[Reagan]

As far as I know the parameter Autostart = 1 is valid only for Windows systems.

On Unix/Linux you can modify the /etc/init.d file to start the SMD automatically.

Regards

RB

[bxiv]

If this is a Windows server, can you verify the Windows Service is not only set to Automatic but it is in fact starting on its own.

I recently had an issue that was due to a Windows Domain policy not allowing the SMD created user accounts to be authorized to start services on their own.

[Former Member]

Kenneth,

The parameter is Autostart=1.

However, what you need to check is whether the relevant sapstartsrv service starts up after the reboot. if not then check Note 823941 - SAP start service on Unix platforms.

Once the sapstartsrv service for the SMD Agents starts (mentioned in /usr/sap/sapservices), this would then startup the SMD Agent.

Regards

Deepak

[Former Member]

Thanks , do you have an example of this  entry in init.d  ?

[Former Member]

Thanks, but  this is hp_ux server

[Reagan]

Check these links and create a start script under /sbin/init.d for SMD

http://help.sap.com/saphelp_nw04/helpdata/en/6d/f16ae31a380142acb0584da3e1085a/content.htm

http://scn.sap.com/community/unix/blog/2012/08/07/startstop-sap-along-with-your-unix-server-startsto...

There are examples provided for HP-UX and I believe for HP-UX the path is /sbin/init.d

Regards

RB

[Former Member]

We do have the agent defined in sapservices file

SHLIB_PATH=/usr/sap/SMD/SMDA97/exe:$SHLIB_PATH; export SHLIB_PATH; /usr/sap/SMD/SMDA97/exe/sapstartsrv pf=/usr/sap/SMD/SYS/profile/SMD_SMDA97_grrapi22 -D -u

smdadm

[Former Member]

Hi,

   Which it is the file path to modify the parameter "autostart" the diagnostic agent?

Best Regards,

Matias Prado

[former_member118647]

Hello Kenneth,

In case you have scheduled downtimes of the ABAP stack(solman), you might need to switch on the Maintenance mode on solution manager Java Stack, and switch it off when the Abap stack is back to normal work/availability.This will avoid having this shutdown situation.Restarting the agents if you don't have any credential issues will solve the problem.

Also, the Solman 7.1 Sp05 introduced a new way of authentications for the SMDAgent. As of this release the agents can connect to the Solman using certificates, so user and password are not necessary. This should avoid this issue.In this case, the agent will retry the connection and you don't have to manually do it.This is configured ion Solution Manager configuration / system preparation/ configure connectivity/4.4 setup authentication policy foragents   > use authentication via certificate.

Regards,

suhel