Technical data

Configuring Automatic Data Collection
For T0682H02 AAM 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 through the Enable/Disable Automation of Data Collection
action, located under the system object in the OSM Service Connection. It is configured through
a combination of OSMCONF file settings and Service Connection actions. To customize the
OSMCONF file default settings, you can create an OSMCONF file from the OSMINI included
with T0682H02 AAM or later, or copy the following settings from the OSMINI file into your existing
OSMCONF file. For more information, see “Creating and Using an OSMCONF File”.
DefaultPossible ValuesPurpose/Effect
ADC-related OSMCONF
Parameters
155 to 60Delay time (in minutes) between the time that the
initial Problem IR is received and data collection
AdcDelayTimeInMin
begins. The purpose is to conduct a single data
collection for all related Problem IRs.
121 to 60Time (in hours), prior to when the Problem IR is
generated, that the data collection will collect
EMS events from $ZLOG and $0.
AdcEventTimeinHrs
ONON/OFFEnables ability to send a Diagnostic Data IR to
the OSM Notification Director. (Not visible in
EnableNDData
OSM ND version T0632 AAK; however, Problem
IRs also provide the location of collected data
files in ZZAA alarm details.)
55 to 120Specifies the time period (in minutes), after the
initial Problem IR is created, that ZZAA and ZZPS
files will be collected.
AdcFilColTimeinMin
The following data collection configuration is done through OSM Service Connection actions,
located under the System object (rather than through OSMCONF file settings, as done in early
S-series releases):
• 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 (the default is 28 days).
* There is also an OSM Service Connection action called Collect Diagnostic Data, which collects
data manually at the time you perform the action. The actions used to specify data collection volume
and data file persistence also apply to the diagnostic data collected by this manual action.
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
Disabling Alarm and Attribute Suppression Persistence
With OSM version T0682 H02 ABX and later, suppression of alarms and problem attributes is
persistent by default. That means alarms or attributes suppressed in the OSM Service Connection
remain suppressed even after the OSM server has been stopped and restarted. Persistence is not
available in OSM versions prior to T0682 H02 ABX, meaning that all suppressed values revert to
unsuppressed when the current OSM server session is ended.
Optional OSM Configuration 21