OSM Migration Guide (G06.27+)

OSM Server-Based Components

OSM Migration Guide—527273-013

3-4

Configuring Automatic Data Collection

For T0682G06 AAC and later, OSM has enhanced automatic data collection

capabilities. If enabled, OSM automatically collects diagnostic data whenever a

hardware failure causes a Problem Incident Report (IR) to be created.

Automatic data collection is enabled by an OSM Service Connection system-level

action (Enable/Disable Automation of Data Collection), and is configured through a

combination of OSMCONF file settings and Service Connection actions. You can copy

the following settings from the OSMINI file included with T0682 AAC (or later) into your

existing OSMCONF file. (To create an OSMCONF file from the OSMINI, or to put OSM

configuration file changes into effect when OSM processes are already running, see

Creating and Using an OSMCONF File.)

The following data collection configuration is now done through OSM Service

Connection actions (under the System object) rather than OSMCONF file settings:

•

Set Data Collection Volume – specifies a volume in which to collect diagnostic

data. The default volume is $SYSTEM.

•

Set Days to persist for Diagnostic Data – specifies how long the data files remain in

the collection volume before they are automatically deleted (default is 28 days).

The current automatic data collection settings are displayed as System object

attributes, under the “Data Collection Services” heading (on the Attributes tab):

•

Automatic Data Collection State (Enabled or Disabled)

•

Diagnostic Data Collection Volume

•

Days to Persist Collected Diagnostic Data

ADC-related

OSMCONF Parameters Purpose/Effect

Possible

Values Default

AdcDelayTimeInMin

Delay time (in minutes) between the time

that the initial Problem IR is received and

data collection begins. The purpose is to

conduct a single data collection for all