System Monitoring with Solution Manager Ehp1

[Former Member]

Hi,

I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.

Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.

Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.

when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:

• <SID>_RZ20_COLLECT

• <SID>_RZ20_ANALYZE

I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:

<SID>_RZ20_COLLECT_123539Error when opening an RFC connection 
Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection 
Error during remote call of SALC function: Error when opening an RFC connection 
Error during remote call of RFC1 function: Error when opening an RFC connection

I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.

Please, Could you help me?

Thanks and regards,

Tomas.

[Former Member]

Tomas can you pls help me on this.

I tried executing sapccm4x from /run directory but getting the below error.

tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 13> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01

****************************************************************************************************************************

ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30

Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.

Please change configuration with profile parameters

ipc/shm_psize_01 = -<different pool nr>

xor

ipc/shm_psize_13 = -<different pool nr>

EXITING with code 1

tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 14>

******************************************************************************************************************************

I tried changing the key01 to different pool and started the instance but it doesn't effect (the key01 is not at all changed).

Pls suggest me what to do?

Regards,

Praveen

[Former Member]

Tomas,

I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system). I downloaded the lates ccmsagent file from the market place based my target system configurations.

Herewith attaching the logs while I'm trying to check the profile parameter.

********************************************************************************************************************************************************************************

tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01

================================================================================

== Checking profile: /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01

================================================================================

***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----

---

***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o

***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000

***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000

***WARNING: Unexpected parameter: dbs/io_buf_size =100000

***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++

***WARNING: Unexpected parameter: rsau/selector1/class =35

***WARNING: Unexpected parameter: rsau/selector1/severity =2

***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0

***ERROR: Size of shared memory pool 40 too small

================================================================

SOLUTIONS: (1) Locate shared memory segments outside of pool 40

with parameters like: ipc/shm_psize_<key> =0

SOLUTION: Increase size of shared memory pool 40

with parameter: ipc/shm_psize_40 =1472000000

Shared memory disposition overview

================================================================

Shared memory pools

Key: 10 Pool

Size configured.....: 642000000 ( 612.3 MB)

Size min. estimated.: 637597428 ( 608.1 MB)

Advised Size........: 640000000 ( 610.4 MB)

Key: 40 Pool for database buffers

Size configured.....: 1048000000 ( 999.4 MB)

Size min. estimated.: 1468229308 (1400.2 MB)

Advised Size........: 1472000000 (1403.8 MB)

Shared memories inside of pool 10

Key: 1 Size: 2500 ( 0.0 MB) System administration

Key: 4 Size: 523648 ( 0.5 MB) statistic area

Key: 7 Size: 14838 ( 0.0 MB) Update task administration

Key: 8 Size: 67108964 ( 64.0 MB) Paging buffer

Key: 9 Size: 134217828 ( 128.0 MB) Roll buffer

Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer

Key: 12 Size: 6000000 ( 5.7 MB) TemSe Char-Code convert Buf.

Key: 13 Size: 200500000 ( 191.2 MB) Alert Area

Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity monitoring

Key: 17 Size: 2672386 ( 2.5 MB) Roll administration

Key: 30 Size: 37888 ( 0.0 MB) Taskhandler runtime admin.

Key: 31 Size: 4806000 ( 4.6 MB) Dispatcher request queue

Key: 33 Size: 39936000 ( 38.1 MB) Table buffer, part.buffering

Key: 34 Size: 20480000 ( 19.5 MB) Enqueue table

Key: 51 Size: 3200000 ( 3.1 MB) Extended memory admin.

Key: 52 Size: 40000 ( 0.0 MB) Message Server buffer

Key: 54 Size: 20488192 ( 19.5 MB) Export/Import buffer

Key: 55 Size: 8192 ( 0.0 MB) Spool local printer+joblist

Key: 57 Size: 1048576 ( 1.0 MB) Profilparameter in shared mem

Key: 58 Size: 4096 ( 0.0 MB) Enqueue ID for reset

Key: 62 Size: 85983232 ( 82.0 MB) Memory pipes

Shared memories inside of pool 40

Key: 2 Size: 31168040 ( 29.7 MB) Disp. administration tables

Key: 3 Size: 114048000 ( 108.8 MB) Disp. communication areas

Key: 6 Size: 1064960000 (1015.6 MB) ABAP program buffer

Key: 14 Size: 28600000 ( 27.3 MB) Presentation buffer

Key: 19 Size: 90000000 ( 85.8 MB) Table-buffer

Key: 42 Size: 13920992 ( 13.3 MB) DB TTAB buffer

Key: 43 Size: 43422392 ( 41.4 MB) DB FTAB buffer

Key: 44 Size: 8606392 ( 8.2 MB) DB IREC buffer

Key: 45 Size: 6558392 ( 6.3 MB) DB short nametab buffer

Key: 46 Size: 20480 ( 0.0 MB) DB sync table

Key: 47 Size: 13313024 ( 12.7 MB) DB CUA buffer

Key: 48 Size: 300000 ( 0.3 MB) Number range buffer

Key: 49 Size: 3309932 ( 3.2 MB) Spool admin (SpoolWP+DiaWP)

Shared memories outside of pools

Key: 18 Size: 1792100 ( 1.7 MB) Paging adminitration

Key: 41 Size: 25010000 ( 23.9 MB) DB statistics buffer

Key: 63 Size: 409600 ( 0.4 MB) ICMAN shared memory

Key: 64 Size: 4202496 ( 4.0 MB) Online Text Repository Buf.

Key: 65 Size: 4202496 ( 4.0 MB) Export/Import Shared Memory

Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring V01.0

Key: 58900130 Size: 4096 ( 0.0 MB) SCSA area

Nr of operating system shared memory segments: 9

Shared memory resource requirements estimated

================================================================

Nr of shared memory descriptors required for

Extended Memory Management (unnamed mapped file).: 64

Total Nr of shared segments required.....: 73

System-imposed number of shared memories.: 1000

Shared memory segment size required min..: 1472000000 (1403.8 MB)

System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)

Swap space requirements estimated

================================================

Shared memory....................: 2050.4 MB

..in pool 10 608.1 MB, 99% used

..in pool 40 999.4 MB, 140% used !!

..not in pool: 34.4 MB

Processes........................: 716.8 MB

Extended Memory .................: 8192.0 MB

-

---

Total, minimum requirement.......: 10959.2 MB

Process local heaps, worst case..: 1907.3 MB

Total, worst case requirement....: 12866.5 MB

Errors detected..................: 1

Warnings detected................: 9

********************************************************************************************************************************************************************************

After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.

Pls have a look at these two and let me know what could I do to proceed further.

********************************************************************************************************************************************************************************

tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01

INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x

INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf

INFO: Central Monitoring System is [SMP]. (found in config file)

additional CENTRAL system y/[n] ? :

INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.

INFO:

CCMS version 20040229, 64 bit, multithreaded, Non-Unicode

compiled at Jun 28 2010

systemid 324 (IBM RS/6000 with AIX)

relno 6400

patch text patch collection 2010/1, OSS note 1304480

patchno 335

INFO Runtime:

running on saptqa01 AIX 3 5 00069A8FD600

running with profile /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01

INFO profile parameters:

alert/MONI_SEGM_SIZE = 200000000

alert/TRACE = 1

SAPSYSTEM = 30

SAPSYSTEMNAME = TQA

SAPLOCALHOST = saptqa01

DIR_CCMS = /usr/sap/ccms

DIR_LOGGING = /usr/sap/TQA/DVEBMGS30/log

DIR_PERF = /usr/sap/tmp

INFO:

pid 4165682

INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10

INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct 3 2008, kernel 6400_20020600_254, platform 324 (IBM RS/6000 with AIX)]

segment status ENABLED

segment started at Tue Sep 14 09:35:56 2010

segment version 20040229

ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30

Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.

Please change configuration with profile parameters

ipc/shm_psize_01 = -<different pool nr>

xor

ipc/shm_psize_13 = -<different pool nr>

EXITING with code 1

[Former Member]

Hi Thomas,

you should have a look at the guides in the Service Marketplace under http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000718044&;

[Former Member]

Hi Dieter,

Thanks for your reply, but I achieved to add the systems at transaction SMSY.

Regards,

Tomas.

[Former Member]

Hi Tomas,

Have you solved this problem?

I'm in the same situation, so if you have the solution,

could you please give it to me?

Regards

[Former Member]

Hi Hideaki

what problem are you facing, is it exactly as the above ?

Have you configured your systems and solution in SMSY ?

[Former Member]

Hi Hideaki,

To add a system to transaction RZ21 in order to monitoring the alerts in Solution Manager EhP1, I went to transaction SMSY, and select the client row where the RFC are defined.

Then I press the "Assign and Check RFC Destination" button, and at the new window, I select the checkbox "Assign RFC Dest.for System Monitoring".

When I save the window, the system is added to transaction RZ21 and I can select the alerts to monitoring at transaction DSWP.

I hope it helps,

Regards,

Tomas.

[Former Member]

Hi Tomas,

Thanks for your advice.

I've already created RFCs, READ,TMW,TRUSTED,and LOGIN in SMSY,

then checked that they all work fine with 'Check RFC' botton.

But still the above error message occur when clicking the test botton in 'Add Componet Monitoring' of RZ21.

I also test the following item in RZ21, and the message '<sid>_rz20_collect successfully' is shown.

RZ21 -> Display Topology -> 'Remote SAP system' tab -> 'Test single connection' botton.

You mean that the above error message isn't shown any more in your system?

Regards

[Former Member]

Hi Hideaki,

When you press the button "Asign and Check RFC Destinations" and mark the checkbox "Assign RFC Dest. for System Monitoring" the system is created at transaction RZ21.

Please check that you have changed to edit mode (Ctrl+F1) before. If you don't do it, then the button that appears is "Check RFC Destinations" instead of "Assign and Check RFC Destinations".

Regards,

Tomas.

[Former Member]

Hi Tomas,

>When you press the button "Asign and Check RFC Destinations" and mark the checkbox "Assign

>RFC Dest. for System Monitoring" the system is created at transaction RZ21.

I delete the RFCs and related users in SMSY, and recrate them with the button 'Generate RFC',

as you told me above.

I don't know why SM_xx_READ and SM_xx_LOGIN are automatically assigned as SysMon RFC,

not <sid>_rz20_collect and <sid>_rz20_analyze created in RZ21.

According to your reply, I guess you could set the RFCs of RZ21 in SMSY.

I can change SysMon RFCs, SM_xx to <sid>_rz20_xx, on RZ21 later,

but I think it's strange that they are not synchronized between SMSY and RZ21.

Regards

[Former Member]

Hi Hideaki

Why do you want to assign <sid>_rz20_collect and <sid>_rz20_analyze for System Monitoring ?

Just use READ and TMW/TRUSTED (SMSY creation)

[Former Member]

Hi Bhudev,

I read the CEN help below, and have thought that <sid>_rz20_xx would be used as System Monitoring RFC.

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/049b260fcf2bc5e10000000a114cbd/frameset.htm

Anyway, thanks to you, I understand READ and TMW/TRUSTED are OK as System Monitoring.

Thank you.

Could you tell me if you know whether <sid>_rz20_xx are essential or not.

It seems to me that the following RZ21 procedure doesn't have any meaning.

Technical Infrastructure ->Configure Central System ->Create remote monitoring entry

Regard

[Former Member]

'<sid>_rz20_xx ' are not essential at all.

when you do 'Technical Infrastructure ->Configure Central System ->Create remote monitoring entry

there just put those two RFCs which were created in SMSY i.e. READ and TRUSTED/TMW for 'collection' and 'analysis' and the SID of the remote system

By doing this, you make that remote system to be able to seen in the screen of 'Setup System Monitoring'

[Former Member]

Thanks Tomas, your info helped me a lot.