xmtopas Command
Purpose
The xmtopas daemon acts as a recording facility and is controlled through the xmtopas.cf configuration file. This daemon simultaneously provides near real-time network-based data monitoring and local recording on a given node.
Syntax
xmtopas [ -v ] [ -b UDP_buffer_size ] [ -i min_remote_interval ] [ -l remove_consumer_timeout ] [ -m supplier_timeout ] [ -p trace_level ] [ -s max_logfile_size ] [ -t keep_alive_limit ] [ -x xmtopas_execution_priority ]
Description
The xmtopas command is always started from inetd daemon. Therefore, command line options must be specified on the line defining the xmtopas command to the inetd daemon in the /etc/inetd.conf file.
- If you modify the xmtopas entry in the inetd.conf file on the Virtual IO Server (VIOS), the new entry is added after migration. You must replace the xmtopas entry to a default type, such as xmtopas -p3, before migration.
- For any dynamic configuration changes to the logical partition, the xmtopas must be restarted to reflect the changes.
Flags
| Item | Description |
|---|---|
| -v | Causes parsing information for the xmtopas recording configuration file to be written to the xmtopas log file. |
| -b UDP_buffer_size | Defines the size of the buffer used by the daemon to send and receive UDP packets. The buffer size must be specified in bytes and can be from 4,096 to 16,384 bytes. The buffer size determines the maximum number of data values that can be sent in one data_feed packet. The default buffer size is 4096 bytes, which allows for up to 124 data values in one packet. |
| -i min_remote_interval | Defines the minimum interval in milliseconds with which data feeds can be sent. Default is 500 milliseconds. A value between 100 and 5,000 milliseconds can be specified. Any value specified is rounded to a multiple of 100 milliseconds. Whichever minimum remote interval is specified causes all requests for data feeds to be rounded to a multiple of this value. For more information review the Rounding of Sampling Interval topic. |
| -l remove_consumer_timeout | Sets the time_to_live after feeding of
statistics data has ceased as described in section Life and Death
of xmtopas. Must be followed by a number of minutes. A value
of 0 (zero) minutes causes the daemon to stay alive forever. The default time_to_live is
15 minutes. This value is also used to control when to remove inactive data-consumers as described in Removing Inactive Data Consumers topic. |
| -m supplier_timeout | When a dynamic data-supplier is active, this
value sets the number of seconds of inactivity from the DDS before
the SPMI assumes the DDS is dead. When the timeout value is exceeded,
the SiShGoAway flag is set in the shared memory area and the
SPMI disconnects from the area. If this flag is not given, the timeout
period is set to 90 seconds. The size of the timeout period is kept in the SPMI common shared memory area. The value stored is the maximum value requested by any data consumer program, including the xmtopas command. |
| -p trace_level | Sets the trace level, which determines the types of events written to the /var/perf/xmtopas.log1 log file or the /var/perf/xmtopas.log2 log file. This flag must be followed by a digit from 0 to 9, with 9 being the most detailed trace level. Default trace level is 0 (zero), which disables tracing and logging of events but logs error messages. |
| -s max_logfile_size | Specifies the approximate maximum size of the log files. At least every time_to_live minutes, it is checked if the currently active log file is bigger than the max_logfile_size value. If so, the current log file is closed and logging continues to the alternate log file, which is first reset to zero length. The two log files are /var/perf/xmtopas.log1 and /var/perf/xmtopas.log2. Default maximum file size is 100,000 bytes. You cannot make the max_logfile_size value smaller than 5,000 or larger than 10,000,000 bytes. |
| -t keep_alive_limit | Sets the keep_alive_limit value must be followed by a number of seconds from 60 to 900 (1 to 15 minutes). The default is 300 seconds (5 minutes). |
| -x xmtopas_execution_priority | Sets the execution priority of the xmtopas command.
Use this option if the default execution priority of the xmtopas command
is unsuitable in your environment. Generally, the daemon should be
given as high execution priority as possible (a smaller number gives
a higher execution priority). On systems other than IBM® RS/6000® systems, the -x flag is used to set the nice priority of the xmtopas command. The nice priority is a value from -20 to 19. The default is -20. |
Files used by the xmtopas command
You can specify the following entries in the xmtopas.res file:
docec:<arguments>
docluster:cluster=<cluster configuration file>Example
docec: availmem=5 unavailmem=2
docluster: cluster=/etc/perf/xmtopasagg.cfThe following new fields are added to the docec entry in the xmtopas.res file to get the Hardware Management Console (HMC) details:
managedsys=[Managed system name under which this partition is configured]
hmc=[HMC name under which this partition is configured]If the HMC platform cannot be configured for automatic queries, the global data fields that are not available to the local partition can be set by using the following options:
availmem = [Total amount of memory allocated to all partitions, in GB]
unavailmem = [Total amount of memory unallocated from the HMC, in GB]
availprocessor = [Total number of physical processors allocated for all partitions]
unavailprocessor = [Total number of physical processors unallocated from the HMC]
poolsize = [Defined Pool Size required if HMC Processor Utilization Authority restricts access]
partitions = [Number of partitions defined on the HMC]
reconfig = [Number of seconds between checking for HMC configuration changes.
Allowed values are 30, 60, 90, 120, 180, 240, 300 seconds.
The default is 60 seconds.]Example
docec: hmc=hmcmac.in.ibm.com managedsys=cec1