2.2.2 Resource collection function

(a) Collection status function management

Status is managed from the start to the end of resource collection. You can browse the collection status using the Resource Configuration window. Figure 2-11 shows the connection statuses managed by SSO and the collection status change triggers when the collection status Impossibility is disabled during a new installation. Figure 2-12 shows the connection statuses managed by SSO and the collection status change triggers when the collection status Impossibility is not disabled. For how to disable the collection status Impossibility, see ssocollectd and ssocolmng in 5. Commands.

Figure 2‒11: Transitions in collection status when collection status "Impossibility" is disabled

1. The following events occurred simultaneously when collection started:

   • The start time specified at the start of collection (or, if not specified, the current time) was reached.

   • No collection time period was specified, or the current time fell within the specified collection time period.

2. Either of the following events occurred at the start of collection:

   • The start time specified at the start of collection (or, if not specified, the current time) was not reached.

   • The current time was outside the specified collection time period.

3. The current time was outside the specified collection time period.

4. Any of the following events occurred:

   • An SNMP error response was received.

   • SNMP request issuance or SNMP response reception failed.

   • The resources to be collected were not supported.

   • Writing of the collected data to the database failed.

5. Any of the following events occurred:

   • SSO stopped or paused.^#2

   • Collection was stopped either through the Resource Configuration window or by the ssocolstop command.

   • The end time specified at collection response reception or collection start was exceeded.

6. At reception of a collection response, a normal response was received.

7. Same as 5.

8. Any of the following events occurred:

   • The start time specified at collection start was reached.

   • The current time was within the specified collection time period.

   • Collection restarted due to SSO startup.^#3

9. Any of the following events occurred:

   • SSO stopped or paused.^#2

   • Collection was stopped either through the Resource Configuration window or by the ssocolstop command.

   • The end time specified at collection start was reached.

10. Same as 1.

11. Same as 2.

    Alternatively, collection to be restarted at SSO startup^#3 did not restart because SSO start processing was in progress.

12. Same as 3.

#1

When the resource status is Postponing, the collection interval is changed to 30 minutes by default. When normal collection resumes, the collection interval reverts to the preselected setting. If the preselected collection interval is 30 minutes or greater, the above collection interval change does not take place. The collection interval for the Postponing status can be defined in the ssocollectd action definition file. For details about the ssocollectd action definition file, see 6.3.9 ssocollectd action definition file (ssocollectd.def).

#2

If collection stops because SSO stopped or the ssocolmng daemon process paused, the Completed collection status change event is not issued. Also, if collection ends because the ssocolmng daemon process paused, no resource status change event is issued.

#3

Collection that stopped because SSO stopped or the ssocolmng daemon process paused can be restarted when SSO starts. In this case, the Collecting and Standing by collection status change events are not issued.

Figure 2‒12: Transitions in collection status when collection status "Impossibility" is not disabled

1. The following events occurred simultaneously when collection started:

   • The start time specified at the start of collection (or, if not specified, the current time) was reached.

   • No collection time period was specified, or the current time fell within the specified collection time period.

2. Either of the following events occurred at the start of collection:

   • The start time specified at the start of collection (or, if not specified, the current time) was not reached.

   • The current time was outside the specified collection time period.

3. The current time was outside the specified collection time period.

4. A noSuchName, genErr, or timeOut SNMP error has been received.

5. Any of the following events occurred:

   • An SNMP error other than noSuchName, genErr, or timeOut has been received.

   • Issuance of an SNMP request or reception of an SNMP response failed.

   • The resources to be collected were not supported.

   • Writing of the collected data to the database failed.

6. Any of the following events occurred:

   • SSO stopped or paused. ^#2

   • Collection was stopped either through the Resource Configuration window or by the ssocolstop command.

   • The end time specified at collection response reception or collection start was exceeded.

7. At reception of a collection response, a normal response was received.

8. Same as 6.

9. Same as 1.

10. Same as 2.

11. Any of the following events occurred:

    • The start time specified at collection start was reached.

    • The current time was within the specified collection time period.

    • Collection restarted due to SSO startup.^#3

12. Any of the following events occurred:

    • SSO stopped or paused.^#2

    • Collection was stopped either through the Resource Configuration window or by the ssocolstop command.

    • The end time specified at collection start was reached.

13. Same as 1.

14. Same as 2.

    Alternatively, collection to be restarted at SSO startup^#3 did not restart because SSO start processing was in progress.

15. Same as 3.

#1

When the resource status is Postponing, the collection interval is changed to 30 minutes by default. When normal collection resumes, the collection interval reverts to the preselected setting. If the preselected collection interval is 30 minutes or greater, the above collection interval change does not take place. The collection interval for the Postponing status can be defined in the ssocollectd action definition file. For details about the ssocollectd action definition file, see 6.3.9 ssocollectd action definition file (ssocollectd.def).

#2

If collection stops because SSO stopped or the ssocolmng daemon process paused, the Completed collection status change event is issued. Also, if collection ends because the ssocolmng daemon process paused, no resource status change event is issued.

#3

Collection that stopped because SSO stopped or the ssocolmng daemon process paused can be restarted when SSO starts. In this case, the Collecting and Standing by collection status change events are not issued.

When the collection status changes, SSO can issue a collection status change event. For details on events, see G. Events.

(b) Checking the interval of regular resource collection

Check whether resources have been collected at the specified collection interval.

The following figure shows the status transitions for the resource collection delay status.

Figure 2‒13: Figure Status transitions for the resource collection delay status

To view the resource collection delay status, use the ssocolshow -ds command. For details about the ssocolshow command, see 5. Commands ssocolshow.

If the resource collection delay status changes while the collection status is Collecting, an audit log is output.

(a) Resource directory

The collection database is created for each server in the resource directory for collected resources. The resource directory is the directory that SSO creates for each resource. For the names of resource directories, see E. Resource IDs.

(b) Collection database name

Collection database consists of data files (.log) for collected data storage, information files (.inf) for database information storage, and instance files (.ins) for instance information storage. JP1/Cm2/SSO determines the collection database name according to the naming rules. The collection database naming rules are stated below:

database-identification

Indicates the collection database type.

0: Master database (The IP address of the monitoring server is IPv4.)

1: Copy database (The IP address of the monitoring server is IPv4.)

2: Master database (The IP address of the monitoring server is IPv6.)

3: Copy database (The IP address of the monitoring server is IPv6.)

monitoring-manager-name

Indicates the IP address of the monitoring manager that has collected the resources and created the master database.

monitoring-server-name

Indicates the IP address of the monitoring server that is targeted for resource collection.

serial-number

If the monitoring manager name and monitoring server name are duplicated in a copy database, a five-digit serial number (from 00001 to 99998) is automatically appended. For a copy database that is created when the size of the master database reaches the maximum, 99999 (fixed value) is appended as the serial number. For details on the maximum size of a master database, see 6.3.8 ssocolmng action definition file (ssocolmng.def).

If, for instance, moitoring manager (IP address: 123.45.67.10) collects the resources of moinitoring server (IP address: 123.45.67.20), the files having the following names are created:

• Data file: sso_0123045067010123045067020.log

• Information file: sso_0123045067010123045067020.inf

• Instance file: sso_0123045067010123045067020.ins

When the above master database is copied, a copy database that has the following file names is created:

• Data file: sso_112304506701012304506702000001.log

• Information file: sso_112304506701012304506702000001.inf

• Instance file: sso_112304506701012304506702000001.ins

If, for instance, moitoring manager (IP address: 123.45.67.10) collects the resources of moinitoring server (IP address: 1234:567:89:a::20), the files having the following names are created:

• Data file: sso_2123045067010123405670089000a0000000000000020.log

• Information file: sso_2123045067010123405670089000a0000000000000020.inf

• Instance file: sso_2123045067010123405670089000a0000000000000020.ins

When the above master database is copied, a copy database that has the following file names is created:

• Data file: sso_3123045067010123405670089000a000000000000002000001.log

• Information file: sso_3123045067010123405670089000a000000000000002000001.inf

• Instance file: sso_3123045067010123405670089000a000000000000002000001.ins

However, if a copy database with serial number 00001 already exists, the copy database is created with serial number 00002.

For details on how to copy a database, see ssoextractlog in 5. Commands.

(c) Collection database size

The size of one entry in the collection database can be calculated by the following formula:

(subresource count x 31 + 3) x instance count + total length of character strings of all instance names + 12 (bytes)

The data file size of the collection database can be calculated by the following formula:

One-entry size x collection count

The maximum sizes of the collection databases that SSO can handle are as follows.

Unit	Maximum size
Per data file	Less than 2 gigabytes
Per resource directory	Less than 4 terabytes
Total database capacity	Less than 4 terabytes

The collection database monotonically increases in size until the maximum value (calculated by the expression shown above) is reached. For details on this monotonic increase, see (e) Collection database maintenance. For details on the maximum size of a collection database, see 6.3.8 ssocolmng action definition file (ssocolmng.def).

(d) Collection database monitoring

The collection database size monitoring command (ssodbcheck) allows you to monitor the collection database size. In situations where the collection database size is monitored, it can be output into a text file, or an event can be issued when the preselected threshold is exceeded. For details on events, see G. Events.

(e) Collection database maintenance

The resource collection database grows until it reaches the maximum size. (For the formula for estimating the file size of a collection database, see (c) Collection database size. For details on the maximum size of a collection database, see 6.3.8 ssocolmng action definition file (ssocolmng.def).) Partial deletion by using the ssoextractlog or ssodbdel commands, or partial deletion of data through a dialog box takes time in proportion to the size of the collection database. Therefore, if the collection data is saved periodically, make sure that you periodically delete the collected data (either by deleting all the data or partially deleting the data for a specific period) in order to secure a sufficient amount of free space on the disk.

For how to delete collection data, see 4.5 Resource Data Reference window and ssodbdel in 5. Commands.

The following is an example of periodic deletion of collection data.

Example:

This example shows how to delete the collection data collected up until the last weekend by executing the following command every weekend:

ssodbdel -all -stop BDATE 7

Note, however, that if the free space in the file system of the collection database is already insufficient (less than the size of the largest data file in the collection database), you must delete all the data in the collection database. Partial deletion of the data for a specific period is not possible. To check the data file size of the collection database, execute the ssoextractlog -list command, and then check Size in the information output to the standard output. Alternatively, check Size (KBytes) in the collection data list in the Resource Data Reference window.

For details on the ssoextractlog command, see ssoextractlog in 5. Commands. For details on the Resource Data Reference window, see 4.5 Resource Data Reference window.