Show TOC

 Availability Monitoring with CCMSPING Is Functioning IncorrectlyLocate this document in the navigation structure

Problem Description

You want to use the availability agent CCMSPING to monitor the availability of systems and instances from the central monitoring system (CEN). You have therefore installed CCMSPING and configured availability monitoring as described in the documentation. However, one or more of the following problems occur during the monitoring:

The system to be monitored is not found in the availability monitoring configuration interface.

An ABAP system for which you have activated availability monitoring cannot be monitored. The value 0% is displayed for system availability, and the following error message appears in the node CCMSPING/Configuration Error:

CCMSPING.<host name>.<instance number>: For system <SysID> message server type ABAP return message Message server: Service unknown or has errors

Although the monitoring of the systems and the instances is functioning correctly for ABAP systems (attribute Instance Availability), the logon check and the monitoring of logon groups are not supplied with values.

Scenario Type:  Error analysis

NetWeaver  Component: SAPWeb AS ABAP

Valid for:     SAP NetWeaver 04 as of SP Stack 11

CCMSPING as of Patch Collection 2005/1 (You can determine the status of the agent with the command ccmsping -v)

Decision Roadmap

Most Important Tools

For configuration, use the relevant interface in transaction RZ21 (menu path Technical Infrastructure  Availability Monitoring  Configure CCMSPING Availability Mon.).

To display the availability data, use the Availability and Performance Overview Monitor in transaction RZ20 (Alert Monitor).


System Is Not Contained in the List

If you cannot find the system to be monitored on the availability monitoring configuration interface, proceed as follows:

If you are monitoring double stack systems and standalone Java systems using the Java message server, you need to manually enter the connection data yourself by choosing   Monitoring  Add System on the configuration interface. Then enter the connection data for the Java message server on the Connection Data and Monitoring Options screen.

If you are monitoring double stack systems and standalone ABAP systems using the ABAP message server, the connection data for the systems that can be monitored is, by default, copied from the sapmsg.ini file on the host on which CCMSPING is running. This file is used by SAP Logon. You can, therefore, manually add the system as described in the previous point, but you can also enter the desired system in SAP Logon on the host on which CCMSPING is running. Then upload the system into CEN by choosing the   Load System List button.

System Cannot Be Monitored

If it is not possible to monitor an ABAP system that is to be monitored, this is usually because the services file on the CCMSPING host does not contain the relevant system. This file contains the port numbers of the individual ABAP message servers. Therefore, proceed as follows:

Open the services file (on Microsoft Windows XP systems, under [Drive]:\WINDOWS\system32\drivers\etc, on UNIX systems, under /etc). The entry has the following format: sapms<SysID> <Port No.>/tcp.

The required port number usually has the format 36<system number>. Enter the corresponding line in the services file, and save the file.

Logon Check and Monitoring of Logon Groups Is Not Performed

If the logon check and the availability monitoring of logon groups are not being provided with data for any monitored ABAP systems, this is usually because the corresponding data collection method is not executed. The method is a startup method; that is, it is automatically executed during the startup of an instance. You can also force the starting of all startup methods during running operation by resetting the corresponding monitoring segment to warmup status. To do this, proceed as follows:

In CEN, start the topology display in the monitoring architecture by starting transaction RZ21, selecting Context Overview in the Topology group box, and choosing the   Display Overview button.

Search for the Availability context. You require the segment that contains this context.

Choose the Local Segments (<SysID>) tab page, and switch to change mode by choosing   (Display  Change).

Select the segment that you identified above and choose the Reset Segment in "WARMUP" Status button. Confirm the messages that appear.

Additional Information

Availability Monitoring with CCMSPING