Skip to end of metadata
Go to start of metadata

Overview

 


Introduction 

It is important to note that there are 2 types of data collected for Hardware Capacity.

  1. Performance Data - e.g. CPU and Memory utilization data.  

  2. Configuration Data - e.g. OS information, CPU type.
    Hardware Capacity data shown in the EWA is measuring CPU and Memory utilization data. This is known as Performance Data.
    It is also collecting system information about the host such as hardware manufacturer, CPU type etc. This is known as Configuration Data.

Example of an EWA report with issues detected in Hardware Capacity Checks:

Refer to the SAP Note below for a more detailed explanation of the Hardware Capacity Analysis.
SAP Note 1309499 - Hardware Capacity Analysis in SAP Services.

Important: These correction measures apply to both ABAP and JAVA systems.


Performance Data 

How is Performance Data collected and stored?

Performance data is initially collected by the SAP Host Agent from the relevant host. From there, it is passed onto the relevant Persistence storage. The primary storage being either:

  1. Solution Manager BW, or
  2. Central Performance History (CPH)
Solution Manager BW Data Flow:
CPH Performance Data Flow:

SAP Host Agent (collects Memory / CPU) 
→ Diagnostics Agent
(SMD)
Wily Introscope Extractor Framework
→ Solution Manager BW
(Persistence Data)
→ EWA
reads the data from BW.

For corrective actions related to data stored in BW, refer to Symptom 1

SAP Host Agent (collects Memory / CPU) 
→ CCMS Agent - Central Performance History (Data is stored here)
SDCCN
EWA reads the data from SDCCN data download.

For corrective actions related to data stored in CPH, refer to Symptom 2

Symptom 1: Performance Data is showing as blank instead of 'OK'.


  • In the EWA report, you find the message: "Hardware Capacity checks could not be run successfully due to missing data. See SAP Note 1309499."

  • You also notice that the Performance Data is showing as blank instead of 'OK'.

Prerequisite:

NEW - Refer to 2813036 - Performance Data missing in EarlyWatch Alert (EWA) report


You are using Solution Manager BW as the data source for the EWA.

Solution Manager BW Data Flow:

SAP Host Agent (collects Memory / CPU) -> Diagnostics Agent (SMD) - Solution Manager BW (Persistence Data) -> EWA reads the data from BW.

Steps to take: Start by validating if Performance Data exist in the Solution Manager BW since this is where the EWA reads the data. 

Validation in Host Analysis:

  1. Connect to Solution Manager and run solman_workcenter.

  2. Select Root Cause Analysis - Host Analysis.

  3. Select the relevant host and then click on 'Host Analysis'.

  4. In the TimeFrame tab, select 'Last Week' to use the same range as the latest EWA week report. Click on Apply Filter.

  5. If no data is found for CPU or Paging, then the EWA is correct in reporting no Performance Data exist for the specific time. Note: You can always select TimeFrame of Today to check if data has start to populate in the BW. If you have data for 'Today', then it is possible that the subsequent EWA will be fine.

 Validation of Wily Introscope: 

  1. From solman_workcenter - Root Cause Analysis - Host Analysis, and click 'CA Introscope Web View'. For 7.2 systems, 'CA Introscope' is directly under the Root Cause Analysis tile.

  2. Click 'Start Introscope' and login.

  3. Navigate to the Investigator tab, and expand *SuperDomain*.

  4. Find and expand the relevant host effected. Ensure that the folder SAP OsCol is present and that performance data is also present in its sub folders.

If the relevant host and its data is present, then check if the new OS collection is active, which uses CIM data instead of SAPOSCOL. This is indicated by the CPU_Virtualization folder being present within SAP OsCol. The old collection is active if the folders CPU_Virtualization_Host/CPU_Virtualization_Virtual_System are present. For non-ABAP systems, the Wily data in Solution Manager BW is the only source for PowerVM data, so the old OS collection should be active.

Note: This change occurs due to a new default in Solution Manager that becomes active after a new Managed System setup run. Follow the corrective actions below to change it back.

Corrective Action:
  1. For Solution Manager 7.2 < SP7, implement SAP Note 2534907 and then follow the steps to activate BW content in solman_setup.

  2. Since all data depends on the SAP Host Agent, it is important that you are using SAP Host Agent 7.21 AND at the latest patch level. Many corrections can be implemented by merely updating this agent. Refer to SAP Note 2130510 - SAP Host Agent 7.21. Check if data is then collected in the BW area of Solution Manager.

    Note: You can check the version of your SAP Host Agent by running:
    Solman_Setup - Managed System Configuration - select the SID - Assign Diagnostics Agent - Agent Assignment - Check All Host Agent.

    The version and patch level will be listed. Compare this to the one available on the SMP.


  3. Ensure that the Managed System Configuration for the specific system is done correctly without any errors shown.

  4. Refer to the WIKI link - https://wiki.scn.sap.com/wiki/x/NINIGQ  -> section Alert for Hardware Capacity

  5. It is also recommended to update to the latest ST-SER Support Package and also ensure the Service Content is updated using transaction ags_update.


  6. To enable OS data collection from SAPOsCol for ABAP and non-ABAP systems, perform the following for the agent(s) effected: 

    1. Navigate to the Solution Manager Work Center - SAP Solution Manager Administration -  Agents Administration

    2. Highlight the host and click on Agent Admin - Selected Agent.

    3. Within the Agent Administration application navigate to the "Application Configuration" tab. In the left hand "Agent Applications" list, select "com.sap.smd.agent.application.e2emai.std.collectors" 

    4. On the right hand side, change "SAPHostControl.CIMProvider.capabilities.check.enabled" to false and save the changes. 

    5. Restart the diagnostic agent instances and check Wily again to ensure the old folders are present.

      Set the value to 'false'

      Below is a screenshot taken from Wily showing a host with SAPOSCOL and a host with CIMProvider. It is important that the host data collection is reverted back to SAPOSCOL using the steps above.

Symptom 2: No CPU virtualization data is available for at least one IBM PowerVM shared pool LPAR (SPLPAR).

Prerequisite:

You are using Central Performance History (CPH) as the data source for the EWA.

CPH Performance Data Flow:

SAP Host Agent (collects Memory / CPU) -> CCMS Agent - Central Performance History (Data is stored here) -> SDCCN - EWA reads the data from SDCCN data download.

Corrective Action:
  1. CCMS data is stored in a Central Performance History (CPH) area so it is important that you start there. For configuration of CPH, refer to SAP Note 1147334 - CPH setup for OS data & also SAP Note 2164753 - CCMS Monitoring of non-SAP Server (eg. Standalone DB)

  2. Once you are in RZ23N - Click on 'Overview of Available Data'. Select the relevant ID under 'System ID'.

  3. In here you are looking to ensure that ALL the required MTEs for EWA data collection is listed and configured properly.

    What are the MTEs that must be configured?
    Refer to the section Appendix: MTE classes necessary for ST06 / OS07N and SAP Support Services in SAP Note 1147334 - CPH setup for OS data.

    As outlined in Note 1147334, it is recommended to use the schema  SAP Solution Manager Hourly for the Hourly resolution with at least 45 days of data.

    Below are screenshots taken from a properly configured system for CPH.

    Screenshot 1: MTE using the recommended Schema. RZ23N - Assign Procedure.



    Screenshot 2: MTE in RZ23N - Overview of Available Data. If you are missing these MTE the CPH configuration is incomplete. In addition, the EWA will not show Hardware Capacity Performance data if the relevant MTEs are not shown here.



    Screenshot 3: An MTE showing the proper Resolution of Hourly and available data. If you have a blank screen here the EWA will also not be showing Hardware Capacity Performance data.


    Screenshot 4: Performance data available in RZ23N.



  4. Next step is to validate that the SDCCN user on the managed system has the correct authorization. Ensure that the user running the SDCCN task has at least the role SAP_SDCCN_EXE and the additional authorization for S_DEVELOP as outlined in SAP Note 763561 - Service Data Control Center (SDCCN)  - FAQ.

  5. In SM59 of the managed system, ensure that the SID RFC is working fine. Run SM59 and then select the SID RFC. Example, if the SID is PRD, then there should be an RFC 'PRD'. Open this RFC - Utilities - Test - Authorization Test. Ensure the test is successful.

  6. Since all data depends on the SAP Host Agent, it is important that you are using SAP Host Agent 7.21 AND at the latest patch level. Many corrections can be implemented by merely updating this agent. Refer to SAP Note 2130510  - SAP Host Agent 7.21.

  7. Review and check if SAP Note 2602215 - SDCC: CCMS_CREATE_COMP_DOWNLOAD Exception NO_DATA_AVAILABLE is applicable.

  8. Ensure that the Managed System Configuration for the specific system is done correctly without any errors shown.

It is also recommended to update to the latest ST-SER Support Package and also ensure the Service Content is updated using transaction ags_update. 

Additional Steps for Virtual Systems such as IBM / VMWARE

If you are using Shared Pool LPARs (SPLPAR)  you have to configure LPAR for SAP Monitoring. In ST06 / OS07N - Pool Utilization Authority (PUA) must be set to Granted. Refer to the attached PDF in SAP Note 1309499 for the detailed steps. OS07N / ST06 must show Granted.

If you are using VMWARE, refer to the attached PDF 'VMWARE Monitoring Setup' from SAP Note 1309499  to complete the monitoring setup steps. This will ensure that data collection is available for the EWA. OS07N / ST06 must show ACTIVE.

Screenshot from ST06/OS07N  showing Pool Utilization Authority & VMWare Monitoring Setup with the correct status.

IBM



VMWARE



Screenshot from transaction DSA showing a database host with PUA not enabled.

 


Configuration Data 

Symptom 3: OS not detected.

Corrective Action: 

NEW:  Refer to 2813029 - EWA - OS not detected (Hardware Utilization Data Chapter)

  1. Ensure that the SAP parameter SAPDBHOST has a host name set and not the FQDN. Example, host123456 and NOT host123456.domain.xx.
    • You can modify the parameter SAPDBHOST in RZ10 → Default Profile → Extended Maintenance → Display → Edit

  2. Update the SAP Host Agent to the latest version AND patch level.  Refer to SAP Note 2130510 - SAP Host Agent 7.21.

    1. Use the command prompt, run saposcol -d and then <enter>.

    2. Type ask Hardware <enter>.

    3. Type ask HardwareXML <enter>.

    4. Open the ASCII file and XML file and ensure that the configuration file has data such OS information, CPU type.  If no such information exist then there is an issue with the Host Agent.


  3. Ensure you check solman_setup - Managed System Configuration - ensure all the lights are GREEN.

  4. Check in transaction DSA if errors are shown under Landscape Server Information (LSI) - XML Data (Download / CCDB) for SMD Agent relevant data.

    Below a CCDB_ERROR is shown for a specific host.

    If you are on Solution Manager ST 7.1 SP14 or higher, check SAP KBA  2453973 - Early Watch Alert (EWA) Report section "Hardware Capacity" wrong values-SAP Solution Manager 7.1.

    For Solution Manager ST 7.2 , apply the note below that is relevant for your SP level.
    SAP Note
    2380768 - RCA Template for Solution Manager 7.20 SP03
    SAP Note 2677925 - RCA Template for Solution Manager 7.20 SP06
    SAP Note 2677887 - RCA Template for Solution Manager 7.20 SP07
    SAP Note 2731985 - RCA Template for Solution Manager 7.20 SP08
    SAP Note 2867874 - RCA Template for Solution Manager 7.20 SP09
    SAP Note 2868071 - RCA Template for Solution Manager 7.20 SP10

    After uploading the templates, go to the Managed System Configuration and run the step Extractor Setup in step Finalize Configuration.

    Lastly, follow the steps from SAP note 1259109 - Latest version of configuration file config.xml.


  5. Navigate to Solution Manager Work Center - Root Cause Analysis - System Analysis - Change Reporting and check if the hardware data is shown.

 

Additional resources:

2660453 - Early Watch Alert (EWA) Report section "Hardware Configuration" wrong values - SAP Solution Manager 7.2



Understanding the Data Reported in EWA

 

  • No labels