Systemwalker Centric Manager - Limit Values/Recommended Values
This document describes the limit values and the recommended values. The numbers in the diagram correspond to the ones in the table.
Note: The following abbreviations are used in this document:
- OMS: Operation Management Server
- SMS: Section Management Server
- JS: Job Server
1. Functions and Limit Values
2. Recommended Values for Efficient Operation Management
3. Polling Interval for Monitoring
4. Monitoring Interval
1. Functions and Limit Values
The table below summarizes functions and their limit values.
| Function | Description | Server/ Client (see the diagram) | Limit Value | Remarks |
|---|---|---|---|---|
| Monitoring | Maximum number of monitored log files for application monitoring. It monitors log files of applications that do not log messages in the event log or syslog. | from (3) to (4), (5) |
20 files/server | |
| Maximum number of messages to display in the Monitor Event List of the monitoring map. | (1), (3) | 100 | Redefine monitoring to display 100 or more messages in the list. | |
| Maximum number of event conditions (for filtering) defined in the Monitored Event Table window. | (1), (3), (4), (5) | 2048 | ||
| Number of messages stored in the log file. | (1), (3), (4), (5) | Unlimited.Depends on the DB size | ||
| Notification to administrator | Number of administrators to automatically notify by e-mail. | Unlimited | ||
| Failure Handling | Number of flows registered in the recovery flow. | (3) | Unlimited. Depends on the DB size |
|
| Trouble Management | Maximum number of trouble tickets registered to Helpdesk. | (3) | 10,000 (At least 720MB is required) |
Redefine Helpdesk to register 10,000 or more tickets |
| Highly-reliable system | Maximum number of mirrored Operation Management Servers (OMS). | (3) | EE: 4 | |
| Management structure | Maximum number of Operation Management Clients concurrently connected to an OMS. | (2) | - SE: 8 - EE: Solaris OS: 16 Windows: 16 - GEE: 16 |
2. Recommended Values for Efficient Operation Management
The table below summarizes the recommended value for each function. The values may not work for your environment, because they depend on the network and the server performance.
| Function | Description | Server/ Client (see the diagram) | Limit Value | Remarks |
|---|---|---|---|---|
| Resource Distribution | Number of relay servers to distribute resources from OMS | from (3) to (4) |
Recommended: 50 (for concurrent connections) |
The values may vary depending on the connection speed. Distribution to 50 or more clients may work depending on the server parameters (e.g., distribution method, resource division, number of concurrent connections) and the timing of distribution to clients. |
| Number of clients to distribute resources from relay server. | from (4) to (6) |
Recommended: 50 (for concurrent connections) |
||
| Maximum number of target clients for resource distribution. | from (3) to (5), (6) |
Unlimited | Consider deploying a relay server. | |
| Monitoring | Number of OMSs monitored by global server. | from (1) to (3) |
Recommended: 32 | Depends on the performance of the global server and the connection speed. |
| Number of Section Management Servers (SMS) monitored by an OMS. | from (3) to (4) |
Recommended: 50 | Depends on the performance of the OMS and the connection speed. | |
| Number of Job Servers (JS) monitored by an OMS | from (3) to (5) |
Recommended: 300 | Depends on the performance of the OMS and the connection speed.Test successfully monitored 3000 servers. | |
| Number of nodes monitored by an OMS. This includes nodes that are monitored by both OMS and SMS. | from (3 )(+ (4)) to (4), (5), (6) |
Recommended: 3000 | Depends on the performance of the OMS, the connection speed, and the performance of SMS, if SMS is in use. | |
| Number of interfaces monitored by an OMS (or an SMS) in network performance monitoring. | from (3) ((4)) to (5)(6) |
Recommended: 300 interfaces(all interfaces of monitored nodes) | Depends on the performance of the OMS (or SMS) and the connection speed. |
3. Polling Interval for Monitoring
OMS and SMS periodically poll information to monitor system and network status. The table below summarizes the maximum, minimum, and default polling intervals.
| Polling Type | Description | Unit | Value | ||
| Min | Default | Max | |||
| Displaying node status | The frame colors of node icons on the monitoring map indicate the operation status of nodes (e.g., Green/Blue: Running; Yellow: Stopped). | Minutes | 1 min | 60 mins | 23 hrs & 59 mins |
|---|---|---|---|---|---|
| Monitoring node status | "X" on node icons on the monitoring map indicates that the node status has changed (e.g., from "Running" to "Stopped" state, from "Stopped" to "Running" state). | Minutes | 1 min | 720 mins | 23 hrs & 59 mins |
| Monitoring MIB threshold value | Monitors abnormality in network and system performance for each MIB. | Minutes | 1 min | 10 mins | 23 hrs & 59 mins |
| Monitoring network performance abnormality | Monitors threshold defined for the traffic information. | Minutes | 1 min | 2 mins | 20 mins* |
*Available settings in minutes: 1, 2, 5, 10, 20
4. Monitoring Interval
The Systemwalker CentricMGR agent monitors server (SMS/Job Server) performance and application performance during specified intervals. The table below summarizes the maximum, minimum, and default monitoring intervals.
| Monitoring Types | Description | Unit | Value | ||
| Min | Default | Max | |||
| Monitoring server performance abnormality | Monitors thresholds defined for CPU usage, memory usage, and disk space on the server | Seconds | 60 secs | CPU/Memory:60 secs Disk:180 secs |
9999 secs |
|---|---|---|---|---|---|
| Monitoring application's operation status | The frame colors of resident process icons on the monitoring map indicate the process status (e.g., Green/Blue: Running, Yellow: Stopped). | Minutes | 1 min | 10 mins | 23 hrs & 59 mins |
| Monitoring MIB threshold value | Monitors abnormality in network and system performance for each MIB. | Minutes | 1 min | 10 mins | 23 hrs & 59 mins |
| Monitoring application performance abnormality | Monitors thresholds defined for the performance information (e.g., CPU and memory used by resident processes). | Seconds | 60 secs | 180 secs | 9999 secs |
