6.3.9 ssocollectd action definition file (ssocollectd.def)

The ssocollectd action definition file contains definitions of ssocollectd daemon process actions. If you have made any changes in this definition file, perform one of the following operations to validate these changes:

Execute the ssocollectd -r command.

Note that the changes might not become valid depending on the key that has been changed.
Restart the ssocollectd daemon process.

Organization of this subsection

(1) Format
(2) Description

(1) Format

The following is a format of the ssocollectd action definition file.

[Figure]

When coding definitions in an ssocollectd action definition file, note the following:

If the definition file includes multiple definitions for the same item, the definition written last is assumed to be valid, and those definitions preceding the last definition are ignored.
When omitting the specification of a key on a line, omit the whole line.

To Page Top

(2) Description

The next table lists the items that must be or can be defined in an ssocollectd action definition file.

Key name	Value
`snmp-address:` <<`default`>>	When operating SSO in a cluster system, specify a logical IP address for IPv4 in the IPv4 address format. By using this specification, you can use a fixed logical IP address for IPv4 as the monitoring manager IP address that is allowed to pass through the firewall located between the monitoring manager and monitored servers. If multiple logical IP addresses are available, specify the logical IP address at which the monitoring server can communicate with all monitored servers. In other cases, specify `default`. When `default` is specified, the local host IP address for IPv4 that enables communication with the monitoring server is used as the monitoring manager IP address that is allowed to pass through the firewall. If multiple local host IP addresses for IPv4 are available for this purpose, selection of the IP address that is allowed to pass through the firewall depends on the OS.
`snmp-address-v6:` <<`default`>>	When operating SSO in a cluster system, specify a logical IP address for IPv6 in the IPv6 address format. By using this specification, you can use a fixed logical IP address for IPv6 as the monitoring manager IP address that is allowed to pass through the firewall located between the monitoring manager and monitored servers. If multiple logical IP addresses are available, specify the logical IP address at which the monitoring server can communicate with all monitored servers. In other cases, specify `default`. When `default` is specified, the local host IP address for IPv6 that enables communication with the monitoring server is used as the monitoring manager IP address that is allowed to pass through the firewall. If multiple local host IP addresses for IPv6 are available for this purpose, selection of the IP address that is allowed to pass through the firewall depends on the OS.
`max-snmp-session:`^#1 <<`32`>> ((1 to 99))	Specify the number of monitored servers that concurrently communicate with the monitoring manager.
`postponing-interval:` <<`1800`>> ((10 to 86,400 seconds))	Specify the time to wait for executing the next collection after the collection status has changed to Postponing^#2. If a value less than the resource collection interval is specified, the next collection is executed according to the setting of the resource collection interval.
`postponing-retry:` <<`2`>> ((0 to 99 times))	Specify the number of retries that will be attempted before the collection status enters `postponing`.
`max-logfile-size:` <<`4`>> ((1 to 32 megabytes))	Specify the maximum size of a log file.
`logfile-num:` <<`3`>> ((1 to 10))	Specify the number of the log files.
`trace:` <<`off`>>	Specify whether to output a trace file for troubleshooting at failure occurrence. To output the trace file, specify `on`. To not output the trace file, specify `off`.
`max-tracefile-size:` <<`4`>> ((1 to 32 megabytes))	Specify the maximum size of a trace file.
`tracefile-num:` <<`3`>> ((1 to 10))	Specify the number of the trace files.
`snmp-dump:` <<`off`>>	Specify whether to output an SNMP packet dump for troubleshooting at failure occurrence. To output the SNMP packet dump, specify `on`. To not output the SNMP packet dump, specify `off`.
`max-dumpfile-size:` <<`8`>> ((0 to 99 megabytes))	Specify the maximum size of the SNMP packet dump trace file. When `0` is specified, the trace is acquired without limiting the file size.
`func-trace:` <<`on`>>	Specify whether to output a function trace for investigation of a failure. To output a function trace, specify `on`. To not output a function trace, specify `off`. Note that if `on` is specified for the `func-trace:` key, the amount of memory used by the `ssocollectd` process increases by 5 MB, and a 5-MB function trace dump file is output.

Key name

Value

snmp-address:

<<default>>

When operating SSO in a cluster system, specify a logical IP address for IPv4 in the IPv4 address format. By using this specification, you can use a fixed logical IP address for IPv4 as the monitoring manager IP address that is allowed to pass through the firewall located between the monitoring manager and monitored servers.

If multiple logical IP addresses are available, specify the logical IP address at which the monitoring server can communicate with all monitored servers.

In other cases, specify default. When default is specified, the local host IP address for IPv4 that enables communication with the monitoring server is used as the monitoring manager IP address that is allowed to pass through the firewall. If multiple local host IP addresses for IPv4 are available for this purpose, selection of the IP address that is allowed to pass through the firewall depends on the OS.

snmp-address-v6:

<<default>>

When operating SSO in a cluster system, specify a logical IP address for IPv6 in the IPv6 address format. By using this specification, you can use a fixed logical IP address for IPv6 as the monitoring manager IP address that is allowed to pass through the firewall located between the monitoring manager and monitored servers.

If multiple logical IP addresses are available, specify the logical IP address at which the monitoring server can communicate with all monitored servers.

In other cases, specify default. When default is specified, the local host IP address for IPv6 that enables communication with the monitoring server is used as the monitoring manager IP address that is allowed to pass through the firewall. If multiple local host IP addresses for IPv6 are available for this purpose, selection of the IP address that is allowed to pass through the firewall depends on the OS.

max-snmp-session:^#1

<<32>> ((1 to 99))

Specify the number of monitored servers that concurrently communicate with the monitoring manager.

postponing-interval:

<<1800>> ((10 to 86,400 seconds))

Specify the time to wait for executing the next collection after the collection status has changed to Postponing^#2. If a value less than the resource collection interval is specified, the next collection is executed according to the setting of the resource collection interval.

postponing-retry:

<<2>> ((0 to 99 times))

Specify the number of retries that will be attempted before the collection status enters postponing.

max-logfile-size:

<<4>> ((1 to 32 megabytes))

Specify the maximum size of a log file.

logfile-num:

<<3>> ((1 to 10))

Specify the number of the log files.

trace:

<<off>>

Specify whether to output a trace file for troubleshooting at failure occurrence. To output the trace file, specify on. To not output the trace file, specify off.

max-tracefile-size:

<<4>> ((1 to 32 megabytes))

Specify the maximum size of a trace file.

tracefile-num:

<<3>> ((1 to 10))

Specify the number of the trace files.

snmp-dump:

<<off>>

Specify whether to output an SNMP packet dump for troubleshooting at failure occurrence. To output the SNMP packet dump, specify on. To not output the SNMP packet dump, specify off.

max-dumpfile-size:

<<8>> ((0 to 99 megabytes))

Specify the maximum size of the SNMP packet dump trace file.

When 0 is specified, the trace is acquired without limiting the file size.

func-trace:

<<on>>

Specify whether to output a function trace for investigation of a failure. To output a function trace, specify on. To not output a function trace, specify off. Note that if on is specified for the func-trace: key, the amount of memory used by the ssocollectd process increases by 5 MB, and a 5-MB function trace dump file is output.

#1: If you change the value of this item, you must restart the ssocollectd daemon process.

#2: For the Postponing status, see Figure 2-11 and Figure 2-12.

To Page Top