The openSM2 manager is an add-on software module in SE manager (on the management unit of an SE server) and enables central monitoring of the systems on the /390 and x86 server units, the application units (x86), storage systems, and all devices with SNMP capability. Systems outside this SE server (e.g. storage systems, devices with SNMP capability, Windows systems) can also be monitored.
The openSM2 manager includes
the agents for recording the measured data, and
the web-based user interface for performance monitoring.
The agents periodically record measured values for the monitored systems and save them in one or two databases
in an online database with limited size for current measured data, and
in an optional database for long-term archiving, whose size is only limited by the storage medium (an nfs drive).
The openSM2 manager can be configured and administrated using a browser. Measured data for the monitored systems or system groups can be evaluated, presented on the screen, or exported to csv files.
The openSM2 manager also enables systems to be monitored with user-defined rules and automatic evaluations to be sent by e-mail.
The procedure for calling up and using the openSM2 manager, along with a description of the functions, can be found in the “openSM2 (BS2000) [18 (Related publications)]” manual. The openSM2 manager provides comprehensive online help.
When used on the management unit of an SE server, the openSM2 manager uses a variable amount of resources (CPU, disk space, memory, network). The actual resource requirement depends on numerous factors.
Resource requirement for data recording
For data recording, the resource requirement depends on
the length of the measuring interval
the number and type of monitored systems (BS2000, Linux, Windows, X2000, VMware vSphere, Xen, storage systems, devices with SNMP capability)
the number of measuring objects (for each measuring object type, e.g. CPUs, disks, channels, tasks, etc.) on the monitored systems
the type and number of active SM2 monitoring programs in BS2000
recording of process data and data for partitions. When recording process data, very high data volumes occur.
In large configurations, we recommend choosing the data volume per measuring interval with caution and not selecting measuring intervals that are too short (the default settings are a good guideline for most measurements). If too much data is recorded simultaneously, (sporadic) IO bottlenecks may occur on the openSM2 partition, which can also affect other MU partitions and thus influence the performance of the entire MU.
If process data is to be recorded, we recommend combining the relevant processes into meaningful process groups, and then monitoring only the process groups and not all individual processes.
Resource requirements for presentation of measured data
The resource requirement for presentation of measured data using the web application depends on
the number of logged in users
the number of open reports per user
the number of measured variables or measuring objects per report
for reports with measuring objects, the type of hit list and the number of measuring objects in the database
for system group reports, the number of systems in the group
the length of the time axis and the number of data points
the type of data source (online or archive database).
The resource requirement for openSM2 is also influenced by:
the number and scope of automatic evaluations performed
the archiving scope
the number of systems monitored
the number and complexity of active rules
For online presentation of the measured data using the web application, it is primarily additional CPU resources that are needed. As the CPU use depends on the number of users and the reports displayed, it is important to ensure that logged in users close their online report views as soon as they no longer require them when they return to the SE manager or log out.