OSM Migration Guide (G06.29+)

OSM Server-Based Components
OSM Migration Guide—527273-018
3-4
Creation of System Inventory Files
Once the prerequisites are met, add this entry into your OSMCONF file:
PowerScrubVersion = 2
The default test interval for this new version is 7 days instead of every 24 hours ( as
was the default for the older version). HP recommends leaving the default as 7 days
unless an event requires a reduced time between scrubs.
To change the test interval for the enhanced Redundant Power Scrub test, add this
entry into your OSMCONF file:
DailyScrubTestingInterval = n
Where n is the number of days between automatic Redundant Power Scrub
tests, up to a maximum value of 30 days.
Creation of System Inventory Files
For T0682G06 AAC and later, OSM has automatic system inventory file creation
enabled by default (you no longer need to Reload Configuration Settings between
each inventory file creation, as was necessary in earlier releases). These system
inventory files are created along with Periodic Incident Reports (IRs), and are attached
to the IRs if the “Suppress Attachment files on Periodic IRs” option is deselected in the
OSM Notification Director Preferences dialog box.
To disable automatic creation of system inventory files, you must set the following
OSMCONF flag to “OFF:”
INVENTORY_STATE = ON
The ”ENABLE_INVENTORY = ON” parameter used to configure system inventory files
in earlier OSM releases no longer has any effect and should be removed from your
OSMCONF file. The current ”INVENTORY_STATE = ON” parameter can be copied to
an existing OSMCONF from the OSMINI template provided with T0682 AAC or later.
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.
For information on initiating Periodic incident reports and viewing attachment files, see
the OSM Notification Director online help.
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.
Note. A system inventory file will not be created if a Periodic IR is generated before OSM
completes system discovery.