Managing Software Changes (G06.25+, H06.03+, J06.03+)

What Is in a Softdoc
Managing Software Changes—427169-005
A-11
Successive PVU Softdoc Example
7. [AAL]
OSM provider processes sometimes abend just after being
started because of a delay in receiving the startup message from
the CIMOM process.
SOLN 10-040120-2546)
8. [AAL]
OSM Service Connection display flickers many times when a
state change occurs on a disk.
(SOLN 10-040505-5773)
Known Problems Remaining:
1. Redundant Power Scrub Test Failed alarm is not generated when
MOSFET, DCC, and Main Rail voltages are out of acceptable limits.
WORKAROUND: None. Periodically check the MOSFET, DCC, and Main
Rail Voltage values in the Attributes window of OSM Service
Connection to determine if they are out of limits.
(SOLN 10-040707-7680)
2. The RALPRVD process sometimes abends during normal operation
because of heap corruption inside the process.
WORKAROUND: None. The CIMOM process automatically starts a new
RALPRVD process.
(SOLN 10-040528-6502)
3. The alarm attachment file generated by OSM does not list the Part
Number, Hardware Revision, Track ID, or Serial Number of the
failed hardware component.
WORKAROUND: Get the Part Number, Hardware Revision, Track ID, and
Serial Number from the Attributes window of the OSM Service
Connection.
(SOLN 10-040617-7065)
4. All actions on a powered-down FCSA pass even though they should
fail. An FCSA remains in a powered-down state after a Replace
action is issued and before it is removed from the slot.
WORKAROUND: When an FCSA is in a powered-down state, do not
issue any action on it.
(SOLN 10-040610-6852)
5. OSM Service Connection might display incorrect information
or some actions might fail when $ZNET process is not running
on the NonStop system. It should generate an alarm indicating
that $ZNET process is not running.
WORKAROUND: Start $ZNET as a NonStop process pair for program
file $SYSTEM.SYSnn.SCP. Either a system startup script or an
SCF kernel subsystem database entry execution before OSM
startup would be typical ways to prevent the problem. Avoid
use of any scripts that stop $ZNET and do not immediately
restart $ZNET.
(SOLN 10-040726-8180)