OSM Migration Guide (G06.25+)

OSM Server-Based Components
OSM Migration Guide—527273-008
3-5
Other OSM Server Processes
Other OSM Server Processes
This section describes the other OSM server processes that are started by the OSM
persistent processes described in the preceding section. For each of these processes,
the process name is dynamically assigned.
$SYSTEM.SYSnn.RALPRVD and $SYSTEM.SYSnn.RALPRVNP
Launched by $ZCMOM, these Resource Access Layer Providers are responsible for:
•
Interacting with SP and subsystems such as Storage, SLSA, etc., to gather
attributes and states for system resources
•
Executing all actions on OSM objects
•
Triggering Incident Analysis to generate and clear alarms
RALPRVD is used for initial discovery, initial incident analysis, event processing and all
action execution that require a super-group user.
RALPRVNP is used for action executions that do not require a super-group
permission.
The maximum number that can run simultaneously is 48:
•
Maximum of eight RALPRVD processes for event processing
•
Maximum of eight RALPRVD processes for refresh or reanalyze action processing
•
Maximum of eight RALPRVD processes for short-term super-group action
processing (Start/Stop disk, etc.)
•
Maximum of eight RALPRVD processes for long-term super-group action
processing (Firmware Update, Validate Checksum, etc.)
•
Maximum of eight RALPRVNP processes for short-term non-super-group action
processing (Responsive Test, etc.)
•
Maximum of eight RALPRVNP processes for long-term non-super-group action
processing (None at this time)
$SYSTEM.SYSnn.EVNTPRVD
Launched by $ZCMOM, the Event Listener Provider is responsible for retrieving SP
and EMS events.
The maximum number that can run simultaneously is one.
$SYSTEM.SYSnn.IAPRVD
Launched by $ZCMOM, the Incident Analysis Provider is responsible for state
propagation and generation of incident reports (IRs)
The maximum number that can run simultaneously is one.