Chapter 74 OSM Messages

The messages in this chapter are generated by the HP NonStop Open System Management (OSM) server software. The subsystem ID displayed by these messages includes OSM as the subsystem name.

1100

A Problem Incident Report has been created. IR id: IR-number Resource: resource-name Probable Cause: cause Specific Problem: problem

`resource-name`	is the name of the resource that caused the problem incident report to be created.
`IR-number`	is the number associated with the incident report. The incident report number is unique for the system.
`cause`	describes the probable cause of the incident report. The cause “Equipment malfunction” indicates that a problem has been detected in your equipment.
`problem`	describes the specific cause of the incident report. The information in this parameter augments the information in the `cause` parameter.

Cause A OSM alarm occurred, causing the generation of a problem incident report.

Effect Remote notification services are provided by HP Insight Remote Support. Problem incident reports are sent from OSM to Insight Remote Support. Event 1100 is always accompanied by an event 1102 or 1103 to indicate the success or failure of that delivery to Insight Remote Support. Insight Remote Support then attempts to send the IR to the HP support center.

Recovery Informational message only; no corrective action is needed. However, recovery might be required for the alarm that initiated this event. Recovery information for the alarm is contained in the incident report attachment file and in the alarm displayed in the OSM Service Connection.

1101

A Periodic Incident Report has been created. IR id#: IR-number

IR-number

is the number associated with the incident report. The incident report number is unique for the system.

Cause A periodic incident report was generated. Periodic incident reports are issued at specified intervals to test the dial-out path to the service provider. The default frequency for HP Insight Remote Support is once a day.

Effect Insight Remote Support receives the periodic incident reports and attempts to send them to the HP support center. To confirm that a Periodic IR was successfully received by the HP support center, there will be an auto-closed Genesis case for each successful path that was reported in that Periodic IR.

Recovery Informational message only; no corrective action is needed.

1102

An Incident Report has been successfully sent from NonStop system to the remote support console and has been attempted to be sent to the Support Center for IR id#: IR-number.

IR-number

is the number associated with the incident report. The incident report number is unique for the system.

Cause An incident report was successfully sent from OSM to HP Insight Remote Support, which in turn, attempts to send it to the HP support center.

Effect None.

Recovery Informational message only; no corrective action is needed.

1103

An Incident Report has failed to be sent to the Support Center for IR id#: IR-number, Reason: reason, From OSM console: workstation-ip-address, To Service Provider IP Address service-provider-ip-address.

`IR-number`	is the number associated with the incident report. The incident report number is unique for the system.
`reason`	describes the reason for the failure to deliver the incident report. The reason could be a failure to receive authorization for dial-out, a time-out, or incident report delivery path not configured.
`workstation-ip-address`	is the internet protocol (IP) address of the dial-out workstation.
`service-provider-ip-address`	is the internet protocol (IP) address of the service provider.

Cause An attempt to deliver an incident report from OSM to Insight Remote Support failed. The reason parameter describes the probable cause of the failure.

Effect If this error occurred for the primary path, the OSM server attempts to deliver the incident report through the backup dial-out path. If both primary and backup delivery paths fail, the incident report becomes a Pending IR and is saved on the system.

Recovery Correct the problem that is preventing delivery of your incident reports. Once resolved, and a Test Incident Report Delivery Paths action succeeds in delivering a test IR, OSM then attempts once again to deliver Pending IRs to Insight Remote Support.

1104

A Request for Software Configuration Incident Report has been created. IR id#: IR-number, Target System Serial Number: serial-number Target System Name: system-name Configuration File: file-name

`IR-number`	is the number to be assigned to the software configuration incident report. The incident report number is unique for the system.
`serial-number`	is the HP serial number of the NonStop server whose configuration has changed.
`system-name`	is the system name of the NonStop server whose configuration has changed.
`file-name`	is the full file name of the software configuration file on the NonStop server whose configuration has changed.

Cause The Distributed Systems Management/Software Configuration Manager (DSM/SCM) changed the configuration of system-name. DSM/SCM requested that the OSM server software generate a software configuration incident report to report the software configuration change to your service provider.

Effect The OSM software generates a software configuration incident report, and if authorized, forwards it to your service provider.

Recovery Informational message only; no corrective action is needed.

1105

A Software Configuration Incident Report has been created. IR id#: IR-number, Target System Serial Number: serial-number Target System Name: system-name Software Configuration File: file-name

`IR-number`	is the number assigned to the software configuration incident report. The incident report number is unique for the system.
`serial-number`	is the serial number of the NonStop server whose configuration has changed.
`system-name`	is the name of the NonStop server whose configuration has changed.
`file-name`	is the full file name of the software configuration file on the NonStop server whose configuration changed.

Cause The OSM server software generated a software configuration incident report to report to your service provider a change in the software configuration of system-name.

Effect The OSM server sends the software configuration incident report to HP Insight Remote Support.

Recovery Informational message only; no corrective action is needed.

1106

A Request for a new Service Password has been created. IR id#: IR-number

IR-number

is the number assigned to the Service Password Request incident report. The incident report number is unique for the system.

Cause The OSM server software generated an incident report to request a new service password.

Effect The OSM Notification Director Application checks the Windows registry to see if a password exists. If one is found, the OSM Notification Director sends the password to the OSM server.

Recovery Informational message only; no corrective action is needed.

1107

The user has deleted an Alarm object. Resource Name: resource-name, Specific Problem: problem, Probable Cause: cause, Perceived Severity: severity, Alarm Creation Time: alarm-creation-time, User Name: username, Workstation: workstation-ID, Process Name: OSM-process-name

`resource-name`	is the name of the resource that generated the alarm.
`problem`	describes the specific cause of the alarm. The information in this parameter augments the information in the `cause` parameter.
`cause`	describes the probable cause of the alarm.
`severity`	indicates the severity of the alarm. Possible values include Critical, Major, Minor, Warning, and Indeterminate.
`alarm-creation-time`	is the time when the alarm was created.
`username`	is the NonStop Kernel user name of the user who deleted the alarm.
`workstation-ID`	indicates the workstation from which the alarm was deleted.
`OSM-process-name`	is the name of the OSM process associated with the alarm.

Cause An alarm has been deleted from the OSM server database.

Effect The alarm is removed from the Alarm Summary dialog box in the OSM Service Connection. If a dial-out was performed as a result of this alarm, and the problem is not corrected within eight hours, another alarm and dial-out are generated.

Recovery Informational message only; no corrective action is needed.

1108

The ServerNet Path Test on the fabric test-result Path Test Started Time: started, Path Test Completed Time: completed,

fabric

indicates which of these internal ServerNet fabrics was tested:

Fabric-X
Fabric-Y

test-result

is one of the following:

Completed with no errors.
Failed. Repair Actions:
Repair-Action 1
Repair-Action 2
Repair-Action 3
Repair-Action 4
Repair-Action 5
are the up to five possible repair actions. The first repair action lists the component that is most likely to be causing the problem, the second repair action lists the component that is second-most likely to be causing the problem, and so on. If the path test passed, no repair actions are listed.

started

is the date and time that the path test was started.

completed

is the date and time that the path test was completed.

Cause Valid for S-series only, this event indicates that the Group ServerNet Connectivity Path Test has been performed. This test can be initiated periodically by the system, by a Path Up or Path Down message system event, or by explicit user action through the OSM Service Connection.

Effect None if the test passes. If the test fails, alarms are generated in the OSM Service Connection.

Recovery If the path test failed, reseat or replace the component listed in the first repair action and run the path test again. If the test fails again, reseat or replace the component in the second repair action and run the path test again. Continue this process until the test passes or until all repair actions have been performed. If the path test still fails after you perform all repair actions, contact your service provider.

1109

Power Scrub Test passed on module. Time Started: start-time Time Ended: end-time

`module`	is the logical name of the module (system enclosure) being tested; for example, GRP-1.MOD-1.
`start-time`	is the time the power scrub test was started.
`end-time`	is the time the power scrub test ended.

Cause The Redundant Power Scrub test has been performed on an enclosure and passed. This test is initiated periodically by the system or by explicit user action through the OSM Service Connection.

Effect None.

Recovery None.

1110

OSM-Correctable-Cache-Error. text

text

is one of these:

Excessive CCE. Excessive CCEs have been detected. Replace the PMF CRU at your convenience. To determine the correct PMF CRU to replace, check the CCE alarm generated by the OSM Service Connection.
Transient CCE. cce-count CCE(s) have been detected in the past cce-read-count examinations within the last 25 hours. Repair action: None.
Intermittent CCE. Transient CCE(s) have been detected in the last No-of-days days. Replace the PMF CRU at your convenience. To determine the correct PMF CRU to replace, check the CCE alarm generated by the OSM Service Connection.
For your information. Currently, cce-count CCE(s) have been detected in the past cce-read-count examinations. Repair Action: None.

These variables are also displayed with this message when you view it in the OSM Event Viewer:

cpu

is the number that identifies the processor on which the correctable cache errors (CCEs) occurred. Possible values are in the range of zero to 15.

cpu-model

is the processor model used in the NonStop server on which the CCE was detected. Possible values are NSR-G, NSR-T, or NSR-V.

cpu-type

is the type of NonStop server on which the processor resides.

cce-count

is the number of CCEs detected on the processor.

cce-read-count

is the number of times the processor was checked for CCEs.

cce-tran-count

is the number of days in which transient CCEs were detected on the processor.

cce-type

is the classification of CCEs that were detected on the processor. Possible classifications are as follows:

Classification	Description
Information	A CCE was detected on the processor.
Excessive	Five or more CCEs were detected on the processor in a 25-hour period.
Transient	Fewer than five CCEs were detected on the processor in a 25-hour period.
Intermittent	Three or more transient CCEs were detected.

Cause The cause depends on the type of CCE that was detected:

If the `cce-type` is...	The cause is...
Information	The secondary cache in the processor had a corrected cache data error. The cache error correction code (ECC) logic has corrected these errors.
Excessive or Intermittent	The secondary cache in the processor had too many corrected cache data errors. The cache ECC logic has corrected these errors.
Transient	The secondary cache in the processor had a few corrected cache data errors. The cache ECC logic has corrected these errors.

Effect The effect depends on the type of CCE that was detected:

If the `cce-type` is...	The effect is...
Information	The corrected cache data errors do not impact processor performance or data integrity.
Excessive or Intermittent	The corrected cache data errors do not impact processor performance or data integrity. However, the probability of an uncorrectable cache error (UCCE) occurring is increased. If this situation happens, the processor halts with a Hardware Error Freeze (HEF).
Transient	The corrected cache data errors do not impact processor performance or data integrity. A 14-day timer is started to monitor the frequency of the errors.

Recovery For Information and Transient CCEs, no recovery is required. Some CCEs are part of normal operation.

For Excessive or Intermittent CCEs, replace the indicated PMF CRU at the next convenient time to avoid the possibility of a HEF caused by an UCCE. To determine the correct PMF CRU to replace, check the alarm in the OSM Service Connection that was generated for this event.

1111

Automatic configuration of an Expand line-handler process to system number target-node has been started. Initiator: initiator Line handler type: lhtype

`target-node`	is the Expand node number (in the range 0 through 254) of the target node.
`initiator`	is the name of the process on the local node that started automatic line-handler configuration.
`lhtype`	is the type of line-handler process being configured; for example, Expand-over-ServerNet.

Cause A new ServerNet remote node has been detected by the local node.

Effect Automatic configuration of the Expand-over-ServerNet line-handler process begins for the remote node.

Recovery Informational message only; no corrective action is needed.

1112

Unable to configure an Expand line-handler process to system number target-node. Initiator:initiator Line handler type:lhtype Process name:proc-name Process CPU:proc-cpu Process ALTCPU:proc-altcpu Problem area:prob-area Problem:prob-desc

`target-node`	is the Expand node number (in the range 0 through 254) of the target node.
`initiator`	is the name of the process on the local node that started automatic line-handler configuration.
`lhtype`	is the type of line-handler process being configured; for example, Expand-over-ServerNet.
`proc-name`	is the name of the line-handler process; for example, $ZZWAN.#`SCnnn`.
`proc-cpu`	is the number of the processor designated to run the primary line-handler process.
`proc-altcpu`	is the number of the processor designated to run the backup line-handler process.
`prob-area`	indicates where the line-handler configuration failed. Possible values are Adding the Profile, Adding the Device, Starting the Device, and Starting the Line.
`prob-desc`	is the SCF description of the problem, including the SCF subsystem error code.

Cause Automatic configuration of the Expand-over-ServerNet line-handler process for the target remote node has failed.

Effect Expand communications cannot take place between the local node and the target remote node.

Recovery Use these SCF command to determine the recovery action:

HELP subsys err

where subsys err is the SCF subsystem error code reported in the preceding problem description.

1113

Successfully configured an Expand line-handler process to system number target-node. Initiator:initiator Line handler type:lhtype Process name:proc-name Process CPU:proc-cpu Process ALTCPU:proc-altcpu

`target-node`	is the Expand node number (in the range 0 through 254) of the target node.
`initiator`	is the name of the process on the local node that started automatic line-handler configuration.
`lhtype`	is the type of line-handler process being configured; for example, Expand-over-ServerNet.
`proc-name`	is the name of the line-handler process; for example, `$ZZWAN.#SCnnn`.
`proc-cpu`	is the number of the processor designated to run the primary line-handler process.
`proc-altcpu`	is the number of the processor designated to run the backup line-handler process.

Cause The Expand-over-ServerNet line-handler process has been successfully configured for the target remote node.

Effect Expand communications can take place between the local node and the target remote node.

Recovery Informational message only; no corrective action is needed.

1114

Power Scrub Test failed on module. Time Started: start-time Time Ended: end-time Error result: result

`module`	is the logical name of the module (system enclosure) being tested; for example, GRP-1.MOD-1.
`start-time`	is the time the power scrub test was started.
`end-time`	is the time the power scrub test ended.
`result`	indicates the type of failure.

Cause The Redundant Power Scrub test has been performed on an enclosure and failed. Either a component in the enclosure does not have redundant power, or a precondition was not met (for example, a processor is down) prior to executing the Redundant Power Scrub test. This test is initiated periodically by the system or by explicit user action through the OSM Service Connection.

Effect Alarms are generated in the OSM Service Connection.

Recovery Use the OSM Service Connection to check for power alarms on the tested module or on CRUs within the module. Follow the repair actions associated with any power alarms.

1115

OSM-PMF-Reset-Failed. Processor number: number Processor type: processor-type Reset Type: type

`number`	is the number that identifies the processor on which the reset failed. Possible values are in the range of zero to 15.
`processor-type`	is the type of NonStop server on which the processor resides.
`type`	is the type of reset that occurred. Possible values are: Soft Reset or Hard Reset.

Cause The specified reset was performed on a processor that incurred a Hardware Error Freeze (HEF), but the reset failed.

Effect None.

Recovery None.

1116

Precondition Test failed on module. Time Started: start-time Time Ended: end-time Error result: result

`module`	is the logical name of the module (system enclosure) on which the precondition test is performed; for example, GRP-1.MOD-1.
`start-time`	is the time the precondition test was started.
`end-time`	is the time the precondition test ended.
`result`	indicates the success of the precondition test. A value of 0 indicates that the test passed; any other value indicates failure.

Cause The precondition test has been performed on an enclosure and failed. A precondition was not met (for example, a processor is down) prior to executing the Redundant Power Scrub action. This test is initiated 30 minutes after system discovery or when the Redundant Power Scrub action has been explicitly performed by the user using the OSM Service Connection.

Effect The Redundant Power Scrub action cannot be performed.

Recovery Using the OSM Event Viewer, select the Event Detail window for this message. The failed precondition is described in the Pre-condition Failure token. Correct the problem and then perform the Redundant Power Scrub action again.

1117

Precondition Test passed on module. Time Started: start-time Time Ended: end-time

`module`	is the logical name of the module (system enclosure) on which the precondition test is performed; for example, GRP-1.MOD-1.
`start-time`	is the time the precondition test was started.
`end-time`	is the time the precondition test ended.

Cause The precondition test has been initiated on an enclosure and passed. This test is initiated 30 minutes after system discovery.

Effect None.

Recovery Informational message only; no corrective action is needed.

1118

Internal Communication from OSM on node-number.

node-number

is the name of the system in a ServerNet or InfiniBand cluster from which this event was generated; for example, \STAR1.

Cause An action was performed using the OSM Service Connection on the system identified by node-number that affects all other nodes within the cluster.

Effect Informational message only; alarms are not generated.

Recovery Informational message only; no corrective action is needed.

1119

OSM RAL Command Failed. RAL Object: object-name Command: command-name Return: return-code

`object-name`	is the name of the subsystem in which the command failed. The value is RAL CPU Object.
`command-name`	is the name of the RAL command that failed.
`return-code`	indicates the type of failure. The value is Not RalRetCode_SUCCESS.

Cause A OSM RAL command failed. Alarms and events for the associated subsystem might not be generated.

Effect Informational message only; alarms are not generated.

Recovery Informational message only; no corrective action is needed.

1120

SWAN firmware update completed.

Cause The SWAN Fast Firmware update action was initiated from the OSM Service Connection and has finished. This event is generated to inform the other OSM components that the WAN subsystem has returned a response to the firmware update request for all the CLIPs for which the fast firmware update was requested.

Effect None.

Recovery Informational message only; no corrective action is needed.

1121

Disk firmware update completed. Disk Drive: Xldevname Firmware File: firmware-file

`Xldevname`	is the name of the disk drive on which the firmware update was performed successfully.
`firmware-file`	is the name of the firmware file used to perform the firmware update.

Cause A firmware update action was initiated from the OSM Service Connection on the specified disk drive and has finished successfully.

Effect None.

Recovery Informational message only; no corrective action is needed.

1122

Disk-Validate-action-started Disk Drive: Xldevname Logical Device Number: Ldev-Number

`Xldevname`	is the name of the disk drive on which the Validate Checksum disk action was initiated.
`Ldev-Number`	is the number of the logical device.

Cause The Validate Checksum disk action was initiated.

Effect None.

Recovery Informational message only; no corrective action is needed.

1123

Disk-Validate-action-completed Disk Drive: Xldevname Logical Device Number: Ldev-Number

`Xldevname`	is the name of the disk drive on which the Validate Checksum disk action was performed.
`Ldev-Number`	is the number of the logical device.

Cause The Validate Checksum disk action is finished.

Effect None.

Recovery Informational message only; no corrective action is needed.

1124

Disk-sector-checksum-error-encountered Logical Sector Address: Disk-Logical-Sector Disk Drive: Disk-Logical-Name Logical Device Number: Ldev-Number

`Disk-logical-sector`	is the address of the logical sector on which the error was found.
`Xldevname`	is the name of the disk drive that has the sector checksum error.
`Ldev-Number`	is the number of the logical device.

Cause A sector checksum error was found.

Effect The sector on the disk has a bad sector checksum.

Recovery Follow standard procedures and warnings to correct any sector checksum errors.

1125

Storage-syndrome-error-encountered Disk Drive: Disk-Logical-Name Logical Device Number: Ldev-Number

`Xldevname`	is the name of the disk drive the OSM server was accessing when the I/O failure occurred.
`Ldev-Number`	is the number of the logical device.

Cause An I/O failure (reported in the form of a syndrome) occurred while the OSM server was accessing the disk drive. This error is usually transient .

Effect None.

Recovery Informational message only; no corrective action is needed.

1126

OSM CIMOM CIMOM-name: Takeover by backup (reason)

`CIMOM-name`	is the name of the CIM object manager process.
`reason`	is the reason for the backup process takeover. Possible reasons are: Primary stopped Primary abended Primary CPU is down Primary failure

Cause The backup OSM CIMOM process has taken over because the primary process failed.

Effect This activity should have no noticeable effect on CIMOM operation. The backup is now the primary and creates a new backup process if a processor is available.

Recovery If a new backup can not be created because of CPU down, OSM continues to operate without a backup, but you should attempt to reload the processor to preserve fault-tolerance.

1127

OSM CIMOM CIMOM-name: Backup process abended (reason)

`CIMOM-name`	is the name of the CIM object manager process.
`reason`	is the reason for the backup process failure. Possible reasons are: Backup stopped Backup abended Backup CPU is down Backup failure

Cause The backup process abended or was stopped, or the processor in which it executed went down.

Effect This activity should have no noticeable effect on CIMOM operation. A new backup starts automatically if a processor is available, or if a processor becomes available.

Recovery If a new backup cannot be created because of processor down, OSM continues to operate without a backup, but you should attempt to reload the processor to preserve fault-tolerance.

1128

OSM CIMOM CIMOM-name: Backup process creation failed with error error-number, detail detail-error-code

`CIMOM-name`	is the name of the CIM object manager process.
`error-number`	is the error number returned by PROCESS_CREATE_.
`detail-error-code`	is the detail error code returned by PROCESS_CREATE_.

Cause The backup process could not be created.

Effect CIMOM runs without the backup.

Recovery To determine the problem from the error codes returned, see the Guardian Procedure Errors and Messages Manual.

1129

OSM CIMOM CIMOM-name: There is no available backup CPU. Continuing with primary only

CIMOM-name

is the name of the CIM object manager process.

Cause This problem is reported under either of these conditions:

CIMOM was started without the CPU-list startup parameter but could not find any available processor for the backup process.
CIMOM was started with the CPU-list startup parameter but no processor in that list was available for the backup process.

Effect CIMOM continues to run without a backup.

Recovery Restart CIMOM when a processor becomes available, or change the CPU-list to include available processors and then restart CIMOM.

1130

OSM CIMOM CIMOM-name: The primary CPU is not represented in the CPU list

CIMOM-name

is the name of the CIM object manager process.

Cause This problem is reported when CIMOM was started with a CPU-list startup parameter and while attempting to create a backup.

Effect CIMOM continues to run without a backup.

Recovery Restart CIMOM when a processor becomes available, or change the CPU-list to include available processors and then restart CIMOM.

1131

OSM CIMOM CIMOM-name: Problem with configuration file: problem

`CIMOM-name`	is the name of the CIM object manager process.
`problem`	is a description of the error.

Cause During CIMOM startup, an error occurred while trying to obtain the repository path or name from the configuration file manager.

Effect CIMOM is not started.

Recovery Examine the error description returned. The OSMINI configuration file might be corrupted or not readable.

1132

OSM CIMOM CIMOM-name: Repository rep-name does not exist

`CIMOM-name`	is the name of the CIM object manager process.
`rep-name`	is the name of the CIM repository.

Cause During CIMOM startup, the CIM repository file (cimrepo) could not be found in the subvolume in which the CIMOM program file resides or in the path specified in the OSMINI configuration file.

Effect CIMOM is not started.

Recovery Specify a valid path in OSMINI, or place the repository into CIMOM subvol.

1133

OSM CIMOM CIMOM-name: Problem with initializing CIMOM object: problem

`CIMOM-name`	is the name of the CIM object manager process.
`problem`	is a description of the error.

Cause During CIMOM startup, an error occurred during CIM repository initialization.

Effect CIMOM is not started.

Recovery Examine the error description returned. The repository might be corrupted. Note that cimrepo is a structured file and cannot be transferred using FTP. You need to obtain the compressed (self-extracting) binary.

1134

User has suppressed an alarm object Resource Name: resource-name, Probable Cause: cause, Specific Problem: problem, Perceived Severity: severity, Is Permanent: permanence, Alarm Creation Time: alarm-creation-time, User Name: username, Workstation: workstation-ID, Process Name: OSM-process-name

`resource-name`	is the name of the resource that generated the suppressed alarm.
`cause`	describes the probable cause of the suppressed alarm.
`problem`	describes the specific cause of the suppressed alarm. The information in this parameter augments the information in the `cause` parameter.
`severity`	indicates the severity of the alarm. Possible values include Critical, Major, Minor, Warning, and Indeterminate.
`permanence`	“Yes” indicates permanent suppression, “No” indicates temporary suppression.
`alarm-creation-time`	is the time when the alarm was created.
`username`	is the NonStop OS user name of the user who suppressed the alarm.
`workstation-ID`	indicates the workstation from which the alarm was suppressed.
`OSM-process-name`	is the name of the OSM process associated with the alarm.

Cause User has suppressed an alarm in the OSM Service Connection.

Effect Degraded Service State or Subcomponent State values due to this alarm are not propagated to parent objects in OSM.

Recovery Informational message only; no corrective action is needed.

1135

User has unsuppressed an alarm object Resource Name: resource-name, Specific Problem: problem, Probable Cause: cause, Perceived Severity: severity, Alarm Creation Time: alarm-creation-time, User Name: username, Workstation: workstation-ID, Process Name: OSM-process-name

`resource-name`	is the name of the resource that generated the alarm.
`problem`	describes the specific cause of the alarm. The information in this parameter augments the information in the `cause` parameter.
`cause`	describes the probable cause of the alarm.
`severity`	indicates the severity of the alarm. Possible values include Critical, Major, Minor, Warning, and Indeterminate.
`alarm-creation-time`	is the time when the alarm was created.
`username`	is the NonStop OS user name of the user who unsuppressed the alarm.
`workstation-ID`	indicates the workstation from which the alarm was unsuppressed.
`OSM-process-name`	is the name of the OSM process associated with the alarm.

Cause User has unsuppressed an alarm in the OSM Service Connection

Effect Degraded Service State or Subcomponent State values due to this alarm are once again propagated to parent objects in OSM.

Recovery Informational message only; no corrective action is needed.

1136

A dump of ME Enclosure.Module.Slot memory was obtained and saved in file-name

`Enclosure.Module.Slot`	is the location of the ME for which the memory dump was retrieved.
`file-name`	is the location of the memory dump.

Cause A dump of the ServerNet switch board memory was retrieved and placed in a file. The file name of the file is specified in the event.

Effect The file specified in the event should be saved for analysis of ME problems.

Recovery Informational message only; no corrective action is needed.

1138

User has suppressed the creation of Problem IRs Problem IR Generation: Dialout Suppressed, Process Name: OSM-process-name User Name: username, Workstation: workstation-ID, Reason for Suppression: reason, Suppression Duration: duration

`OSM-process-name`	is the name of the OSM process associated with the Problem IR suppression.
`username`	is the NonStop OS user name of the user who suppressed Problem IR creation.
`workstation-ID`	indicates the workstation from which Problem IR creation was suppressed.
`reason`	indicates the reason for suppression (as specified by user who initiated).
`duration`	is the length of time for which Problem IR creation was suppressed.

Cause User has suppressed Problem Incident Report creation in the OSM Service Connection for a specified duration.

Effect Problem Incident Reports are not created during the specified time period.

Recovery No corrective action is needed. OSM resumes Problem Incident Report creation (as alarm conditions dictate) when the specified duration for the suppression expires. To resume Problem Incident Report creation immediately, you use the Unsuppress Problem Incident Report Creation action in the OSM Service Connection.

1139

User has unsuppressed the creation of Problem IRs Problem IR Generation: Dialout Enabled, Process Name: OSM-process-name User Name: username, Workstation: workstation-ID Unsuppression reason: reason

`OSM-process-name`	is the name of the OSM process associated with the Problem IR suppression.
`username`	is the NonStop OS user name of the user who unsuppressed Problem IR creation.
`workstation-ID`	indicates the workstation from which Problem IR creation was unsuppressed.
`reason`	indicates the reason for unsuppression.

Cause User has unsuppressed Problem Incident Report creation in the OSM Service Connection.

Effect Allows Problem Incident Report creation to resume as alarm conditions dictate.

Recovery Informational message only; no corrective action is needed.

1140

User extended the duration of Problem IR suppression Problem IR Generation: Dialout Suppression Extended, Process Name: OSM-process-name, User Name: username, Workstation: workstation-ID, Suppression Duration: duration

`OSM-process-name`	is the name of the OSM process associated with the Problem IR suppression.
`username`	is the NonStop OS user name of the user who extended the suppression duration.
`workstation-ID`	indicates the workstation from which the suppression duration was extended.
`duration`	is the total length of time (in minutes) for which Problem IR creation has been suppressed (includes original and extended durations).

Cause User has extended the time duration for suppression of Problem Incident Report creation in the OSM Service Connection.

Effect Problem Incident Reports are not created until the duration time expires.

Recovery Informational message only; no corrective action is needed. OSM resumes Problem Incident Report creation (as alarm conditions dictate) when the specified duration for the suppression expires. To resume Problem Incident Report creation immediately, you use the Unsuppress Problem Incident Report Creation action in the OSM Service Connection.

1141

User has suppressed a problem attribute property Resource Name: resource-name, Property Name: property-name, Property Value: property-value, User Name: username, Workstation: workstation-ID, Is Permanent: value

`resource-name`	is the name of the resource on which the attribute was suppressed.
`property-name`	indicates the name of the attribute that was suppressed.
`property-value`	indicates the specific attribute value that was suppressed (“all” values is an option).
`username`	is the NonStop OS user name of the user who suppressed the attribute.
`workstation-ID`	indicates the workstation from which the attribute was suppressed.
`value`	indicates whether the attribute suppression is permanent (until unsuppressed by user) or not (which means it remains suppressed for only as long as that particular value is displayed by OSM).

Cause A problem attribute value has been suppressed by the user in the OSM Service Connection.

Effect Degraded attribute values associated with this attribute are not propagated to parent objects in OSM.

Recovery Informational message only; no corrective action is needed.

1142

User has unsuppressed a problem attribute property Resource Name: resource-name, Property Name: property-name, Property Value: property-value, User Name: username, Workstation: workstation-ID, All Values: value

`resource-name`	is the name of the resource on which the attribute was unsuppressed.
`property-name`	indicates the name of the attribute that was unsuppressed.
`property-value`	indicates the specific attribute value that was unsuppressed. (Unsuppressing “all” values is also an option.)
`username`	is the NonStop OS user name of the user who unsuppressed the attribute.
`workstation-ID`	indicates the workstation from which the attribute was unsuppressed.
`value`	indicates whether or not all values for this attribute were unsuppressed. (If all values were suppressed and only specific values were unsuppressed, other values might still be suppressed.)

Cause A problem attribute value has been unsuppressed by user in the OSM Service Connection.

Effect Degraded attribute values associated with this attribute are once again propagated to parent objects in OSM.

Recovery Informational message only; no corrective action is needed.

1144

An alarm has been created Resource name: resource-name, Specific Problem: problem, Probable Cause: cause, Perceived Severity: severity, Alarm Creation Time: alarm-creation-time, Process Name: OSM-process-name, Dialout Requested: dialout-value, Problem IR Created: IR-creation, Alarm Type: alarm-type, Repair Action: repair-action-text

`resource-name`	is the name of the resource that generated the alarm.
`problem`	describes the specific cause of the alarm. The information in this parameter augments the information in the `cause` parameter.
`cause`	describes the probable cause of the alarm.
`severity`	indicates the severity of the alarm. Possible values include Critical, Major, Minor, Warning, and Indeterminate.
`alarm-creation-time`	is the time when the alarm was created.
`OSM-process-name`	is the name of the OSM process associated with the alarm.
`dial-out value`	indicates whether or not this alarm results in a dialout.
`IR-creation`	indicates whether or not this alarm results in creation of a Problem Incident Report (IR).
`alarm-type`	indicates the type of alarm.
`repair-action-text`	describes how to recover from the conditions that prompted the alarm.

Cause OSM has determined that an alarm condition exists.

Effect The resource on which the alarm exists might not be fully functional. See the OSM Service Connection.

Recovery Follow the repair action text provided as part of the alarm detail in the OSM Service Connection.

1145

An alarm has been removed Resource name: resource-name, Specific Problem: problem, Probable Cause: cause, Perceived Severity: severity, Alarm Creation Time: alarm-creation-time, Process Name: OSM-process-name

`resource-name`	is the name of the resource that generated the alarm.
`problem`	describes the specific cause of the alarm. The information in this parameter augments the information in the `cause` parameter.
`cause`	describes the probable cause of the alarm.
`severity`	indicates the severity of the alarm. Possible values include Critical, Major, Minor, Warning, and Indeterminate.
`alarm-creation-time`	is the time when the alarm was created.
`OSM-process-name`	is the name of the OSM process associated with the alarm.

Cause An alarm has been removed from a resource object in the OSM Service Connection because the conditions causing the alarm no longer exist.

Effect The alarm should no longer appear on in the OSM Service Connection.

Recovery Informational message only; no corrective action is needed.

1146

OSM Process Trace. Process Name: Process-name, Module Name: Module-name, Action: Action-name, Message: Message-text

`Process-name`	The name of the process that created this event.
`Module-name`	The name of the module for which the trace message has been created.
`Action-name`	The name of the action for which the trace message has been created.
`Message-text`	The information text of the trace message.

Cause OSM and other subsystems use informational trace messages for debugging. For example, OSM creates this trace message event whenever OSM discovers or resets a blade element or LSU. The message text contains the Reset-Cause registers of the blade element or LSU.

Effect The trace message event is used to collect the various informational messages sent out by the various modules of OSM.

Recovery Informational message only; no corrective action is needed.

1147

The ServerNet/InfiniBand Path Test on the X-Fabric/Y-Fabric completed with no errors

X/Y

indicates which ServerNet or InfiniBand fabric, X or Y, on which the Path Test completed.

Cause The InfiniBand Path Test or Group ServerNet Connectivity Path Test on the specified fabric completed successfully.

Effect None.

Recovery Informational message only; no corrective action is needed.

1148

The ServerNet/InfiniBand Path Test on the X-Fabric/Y-Fabric failed with errors

X/Y

indicates the ServerNet or InfiniBand fabric, X or Y, on which the Path Test failed.

Cause The InfiniBand Path Test or Group ServerNet Connectivity Path Test on the specified fabric failed.

Effect Varies; see Recovery.

Recovery See the event detail for a list of ports with failures and affected processors, if any. This information is also part of the action failure details, which can be viewed through the Action Summary dialog box.

1149

System Enters Power Fail Ride-Through Period. Ride-Through Time is n seconds

n

is the duration of the ride-through period in seconds, as specified through SCF.

Cause Power failure was detected by OSM, and the system entered the ride-through period.

Effect The system continues to operate using power from the UPS during the ride-through period. After the ride-through period expires, the system is powered off.

Recovery Check the power supply of the p-switch module. For an HP Integrity NonStop NS14000 server, check the power supplies in the IOAM enclosure.

1150

Data Collection started. Start Time: Month DD, HH:MM:SS

Month DD, HH:MM:SS

is the month, date, and time (in hours:minutes:seconds) that the data collection started.

Cause Diagnostic data collection has started.

Effect This is an internal message only.

Recovery Informational message only; no corrective action is needed.

1151

Data Collection stopped. End Time: Month DD, HH:MM:SS, Pak File Name: $ADCPAKVOLUME.ZSUPPORT.ZPAKnnnn

`Month` `DD`, `HH`:`MM`:`SS`	is the month, date, and time (in hours:minutes:seconds) that the data collection stopped.
`ADCPAKVOLUME`	is the data collection volume, as specified by the system-level Set Data Collection Volume action in the OSM Service Connection.
nnnn	is the incremental name of the ZPAK file.

Cause Diagnostic data collection has stopped.

Effect This is an internal message only.

Recovery Informational message only; no corrective action is needed.

1152

A Diagnostic Data Incident Report has been created. IR id#: 382 Attachment File Name: $SYSTEM.ZSERVICE.ZZDDxxxx

xxxx	is the name of the ZZDD attachment file.

Cause A Diagnostic Data IR has been generated.

Effect This is an internal message only. A Problem IR (related to the data collection incident) is also created and can be dialed out to provide data collection file location.

Recovery Informational message only; no corrective action is needed.

1153

System Exits Power Fail Ride-Through Period. The reason is x

x

the reason that the system exited the Power Fail ride-through period.

Cause OSM detected that power was restored, and the system exited ride-through period.

Effect None.

Recovery Informational message only; no corrective action is needed.

1154

PFAIL-SHOUT is happening

Cause Power failure was detected by OSM, and the system ride-through period has expired. A power-fail shout packet was sent out to all running processors.

Effect The system stops running immediately.

Recovery Reload the system once power has been restored.

1155

The ride through time is configured as infinite time. No Power fail processing will be done.

Cause The ride through time is configured as infinite time.

Effect No power fail processing will be done.

Recovery Informational message only; no corrective action is needed.

1156

OSM encountered an exception while processing power-fail. The detail is: reason

reason

indicates the reason for the exception.

Cause See reason.

Effect This is an internal message only.

Recovery Informational message only.

1157

OSM CIMOM : The CIMOM has been stopped because it was started using a non-SUPER.SUPER logon.

Cause The OSM CIMOM was started by someone using other than a SUPER.SUPER logon.

Effect The OSM CIMOM stops.

Recovery Restart the CIMOM using a SUPER.SUPER logon.

1158

A subsystem problem occurred on the system. Resource Name: name Problem Description: description

`name`	is the name of the system resource experiencing the problem.
`description`	is a description of the problem.

Cause Varies; see Recovery.

Effect Varies.

Recovery If the problem description does not provide adequate recovery information, locate the resource in the OSM Service Connection and look for alarm details or problem attribute values for more information.

1159

ZOSM-EVT-REPOSITORY-WRITE-FAIL Write to repository file zosm-tkn-repository-name failed with a File System Error zosm-tkn-repository-failure.

zosm-tkn-repository-`name`	is the name of the failed repository file.
zosm-tkn-repository-`failure`	is the type of failure.

Cause OSM has detected an alarm processing problem.

Effect Report the problem to your service provider.

Recovery Varies; contact your service provider.

1161

Data Sanitization started on Disk zems-tkn-xldevname. Executed by Employee: zosm-tkn-employee-name from : zosm-tkn-company-name logged on as zosm-tkn-user-name from IP Address: zosm-tkn-workstation-ip.

`xldevname`	is the name of the disk drive on which the Perform Data Sanitization action was initiated.
`employee-name`	is the name of the employee initiating the action.
`company-name`	is the employee's company name.
`user-name`	is the employee's user name
`workstation-ip`	is the IP address of the workstation from which the action was initiated.

Cause The Disk Data Sanitization action was performed on the disk.

Effect None.

Recovery Informational message only; no corrective action is needed.

1162

Data Sanitization Pass zosm-tkn-sanitize-pass.zosm-ddl-sanitize-pass.z-pass-number on Disk zems-tkn-xldevname pass-result.

`pass-number`	is the number of the pass.
`xldevname`	is the name of the disk drive on which the pass was performed.
`pass-result`	reports the end result of the pass, displaying either “successfully completed” or “completed with failures.”

Cause The Disk Data Sanitization action completed a pass.

Effect None.

Recovery Informational message only; no corrective action is needed.

1163

Data Sanitization on Disk zems-tkn-xldevname action-result. The last pass executed was pass-activity pass zosm-tkn-sanitize-pass.zosm-ddl-sanitize-pass.z-pass-number. The last sector address sector-activity: zosm-tkn-last-sector-number.

xldevname

is the name of the disk drive on which the Perform Data Sanitization action was initiated.

action-result

reports the end result of the action, displaying either “successfully completed,” “completed with failures,” or “was aborted by user zosm-tkn-aborted-by-user from IP Address: zosm-tkn-workstation-ip.”

workstation-ip

is the IP address of the workstation from which the action was aborted.

pass-activity

is the activity performed during the pass; those activities include “the read and verify of,” “the write,” or “Solid State Disk Block Erase Sanitize” (in which case there is no pass number, as there is only one pass).

pass-number

is the number of the pass.

sector-activity

is the activity performed on the last sector, either “verified” or “written.”

last-sector-number

is the number of the last sector.

Cause The Disk Data Sanitization action completed.

Effect None.

Recovery Informational message only; no corrective action is needed.

1164

Suppressed an Alarm object based on persistence. Resource Name: resource-name, Probable Cause: probable-cause, Specific Problem: specific-problem, Perceived Severity: perceived-severity, Is Permanent: permanence, Alarm Creation Time: alarm-creation-time, Process Name: OSM-process-name

`resource-name`	is the name of the resource that generated the suppressed alarm.
`cause`	describes the probable cause of the suppressed alarm.
`problem`	describes the specific cause of the suppressed alarm. The information in this parameter augments the information in the `cause` parameter.
`severity`	indicates the severity of the alarm. Possible values include Critical, Major, Minor, Warning, and Indeterminate.
`permanence`	“Yes” indicates permanent suppression, “No” indicates temporary suppression.
`alarm-creation-time`	is the time when the alarm was created.
`OSM-process-name`	is the name of the OSM process associated with the alarm.

Cause A specific alarm was suppressed on a specific object during a previous OSM server session. Since this system is configured for suppression persistence (the default setting for OSM server, T0682 H02 ABX and later), the alarm remains suppressed either permanently, if the “Is Permanent:” value is “Yes,” or temporarily, if the value is “No.” Temporarily means that if the same alarm is generated again on this object at a later time, suppression is canceled and state propagation once again occurs. Suppression persistence can be disabled through your OSMCONF file; for more information, see the OSM Migration and Configuration Guide.

Effect Degraded state values due to this alarm are not propagated to parent objects in OSM.

Recovery Informational message only; no corrective action is needed.

1165

Suppressed problem property based on persistence. Resource Name: resource-name, Property Name: property-name, Property Value: property-value, Is Permanent: permanence, Process Name: OSM-process-name

`resource-name`	is the name of the resource that generated the suppressed problem attribute.
`property-name`	is the name of the suppressed problem attribute.
`property-value`	is the specific value of the problem attribute that was suppressed.
`permanence`	“Yes” indicates permanent suppression, “No” indicates temporary suppression.
`OSM-process-name`	is the name of the OSM process associated with the problem attribute.

Cause A specific problem attribute value was suppressed on a specific object during a previous OSM server session. Since this system is configured for suppression persistence (the default setting for OSM server, T0682 H02 ABX and later), the state propagation caused by this value remains suppressed either permanently, if the “Is Permanent:” value is “Yes,” or temporarily, if the value is “No.” Temporarily means that if the same attribute value is generated again on this object at a later time, suppression is canceled and state propagation once again occurs. Suppression persistence can be disabled through your OSMCONF file; for more information, see the OSM Migration and Configuration Guide.

Effect Degraded state values are not propagated to parent objects in OSM.

Recovery Informational message only; no corrective action is needed.

1166

Unsuppressed an Alarm object based on persistence. Resource Name: resource-name, Probable Cause: probable-cause, Specific Problem: specific-problem, Perceived Severity: perceived-severity, Alarm Creation Time: alarm-creation-time, Process Name: OSM-process-name

`resource-name`	is the name of the resource on which the previously suppressed alarm became unsuppressed.
`cause`	describes the probable cause of the alarm.
`problem`	describes the specific cause of the alarm. The information in this parameter augments the information in the `cause` parameter.
`severity`	indicates the severity of the alarm. Possible values include Critical, Major, Minor, Warning, and Indeterminate.
`alarm-creation-time`	is the time when the alarm was created.
`OSM-process-name`	is the name of the OSM process associated with the alarm.

Cause A specific alarm was suppressed on a specific object during a previous OSM server session. Since this system is configured for suppression persistence (the default setting for OSM server, T0682 H02 ABX and later), the alarm remained suppressed until another alarm of the same type was generated on this object, canceling the suppression and allowing state propagation based on the new alarm to occur. Suppression persistence can be disabled through your OSMCONF file; for more information, see the OSM Migration and Configuration Guide.

Effect Degraded state values due to this alarm are once again propagated to parent objects in OSM.

Recovery Informational message only; no corrective action is needed.

1167

Unsuppressed problem property based on persistence. Resource Name: resource-name, Property Name: property-name, Property Value: property-value, All values: all-values, Process Name: OSM-process-name

`resource-name`	is the name of the resource on which the problem attribute became unsuppressed.
`property-name`	is the name of the attribute that became unsuppressed, causing state propagation to resume.
`property-value`	is the specific value of the attribute that became unsuppressed.
`all-values`	this value should be “No,” as only the specific attribute value indicated by `property-value` should cause the unsuppression to occur.
`OSM-process-name`	is the name of the OSM process associated with the problem attribute.

Cause A specific problem attribute value was suppressed on a specific object during a previous OSM server session. Since this system is configured for suppression persistence (the default setting for OSM server, T0682 H02 ABX and later), the state propagation caused by this value remained in effect until conditions caused the attribute to return to that value once again, canceling suppression and allowing state propagation to resume. Suppression persistence can be disabled through your OSMCONF file; for more information, see the OSM Migration and Configuration Guide.

Effect Degraded state values are not propagated to parent objects in OSM.

Recovery Informational message only; no corrective action is needed.

1168

CME soft threshold was set. Processor number: cpu. CME Soft Threshold set to: zosm-tkn-cme-soft-thresh-value

`cpu`	is the processor number on which the soft threshold value has been set.
`zosm-tkn-cme-soft-thresh-value`	is the actual value of the CME soft threshold that has been set for the processor.

Cause A CME (corrected memory error) soft threshold value has been set for a particular processor.

Effect Instead of using the default value, the CME tracking in NSK will now use the user-specified value to interpret soft CMEs that are encountered on the processor.

Recovery Informational message only; no corrective action is needed.

1169

Memory pages have been reclaimed using OSM processor action Reclaim Memory Pages. Memory pages reclaimed on processor: cpu

cpu

is the processor number on which the “Reclaim Memory Pages” action has been executed.

Cause The “Reclaim Memory Pages” action has been performed (in the OSM Service Connection) on the processor after a memory problem has been serviced.

Effect Memory pages will be reclaimed for the processor.

Recovery Informational message only; no corrective action is needed.

1170

System Enters Power Fail Application-Shutdown Period. The reason is x

x

the reason that the system entered the Power Fail Application-Shutdown period as configured in the OSMCONF through the SHUTDOWN_SCRIPT_NAME and SHUTDOWN_SCRIPT_TIME flags. The SHUTDOWN_SCRIPT_TIME (specified in seconds, and cannot exceed the configured ride-through time) is triggered to end at the same time as the ride-through time. For example, if ride-through time is set to 60 seconds and the specified SHUTDOWN_SCRIPT_TIME is 40 seconds, then the shutdown script begins to run 20 seconds after the ride-through time starts. For more information, see the OSM Migration and Configuration Guide.

Cause Power failure was detected by OSM, the system entered the ride-through period and, because SHUTDOWN_SCRIPT_NAME and SHUTDOWN_SCRIPT_TIME parameters were defined in OSMCONF, the application shutdown script was executed and the system entered the Application-Shutdown period.

Effect System applications begin to be shut down, per the shutdown script.

Recovery Restart the system applications after the power supplies return and the system reboots.

1171

System Exits Power Fail Application-Shutdown Period. The reason is x

x

the reason that the system exited the Power Fail Application-Shutdown period.

Cause OSM detected that Application-Shutdown script had completed, ending the system (software) Application-Shutdown period.

Effect The ride-through time also ends, triggering the system hardware shutdown.

Recovery Restart the system applications after the power supplies return and the system reboots.

1172

User specified OSM startup message contains at least one invalid option: user-spec-startupmsg.

User specified OSM file security setting user-spec-security is not valid. The default value default-security is used instead.

`user-spec-startupmsg`	is the user-specified startup message.
`user-spec-security`	is the user-specified security setting.
`default-security`	is the default security setting.

Cause User has specified invalid startup message option or invalid security setting to run OSM CIMOM, EVTMGR or APPSRVR.

Effect OSM uses the default value for the invalid settings and continues running.

Recovery Informational message only; no corrective action is needed.

1173

Stop Monitoring action used on resource-name.

IP address of device: IP-address

`resource-name`	is the name of the Monitored Service LAN Device object upon which the Stop Monitoring action was performed.
`IP-address`	is the IP address of the object.

Cause The Stop Monitoring action was performed on the object.

Effect OSM will no longer monitor this object. If the object is a UPS, it should also be removed from the Power Fail Configuration for the system.

Recovery Informational message only; no corrective action is needed.

1174

An OSM role has been created. Role: acl-role, created by: user-name. Members: acl-members.

`acl-role`	Name of the OSM role that has been created.
`user-name`	User id of the user who created this new role.
`acl-members`	Comma separated list of the members of this new role.

Cause This event is generated when a user creates an OSM role using the Access Control List dialog in the OSM Service Connection.

Effect A new OSM role has been created and should now be visible in the Access Control List dialog in the OSM Service Connection.

Recovery Informational message only; no corrective action is needed.

1175

An OSM role has been modified. Role: acl-role, modified by: user-name. New members: acl-members.

`acl-role`	Name of the OSM role that has been modified.
`user-name`	User id of the user who modified this role.
`acl-members`	Comma separated list of the new members of this role.

Cause This event is generated when a user modifies an existing OSM role using the Access Control List dialog in the OSM Service Connection.

Effect An OSM role has been modified; a change has been made to the description and/or members.

Recovery Informational message only; no corrective action is needed.

1176

An OSM role has been deleted. Role: acl-role, deleted by: user-name.

`acl-role`	Name of the OSM role that has been deleted.
`user-name`	User id of the user who deleted this role.

Cause This event is generated when a user deletes an OSM role using the Access Control List dialog in the OSM Service Connection.

Effect An OSM role has been deleted.

Recovery Informational message only; no corrective action is needed.

1177

An OSM role has been assigned privileges. Role: acl-role, assigned by: user-name. Assigned privileges: acl-privileges.

`acl-role`	Name of the OSM role that has been assigned privileges.
`user-name`	User id of the user who assigned the access privileges.
`acl-privileges`	Comma separated list of privileges that have been assigned to this role.

Cause This event is generated when a role is assigned one or more privileges through the Access Control List dialog in the OSM Service Connection.

Effect A role was assigned one or more privileges.

Recovery Informational message only; no corrective action is needed.

1178

Privileges have been removed from an OSM role. Role: acl-role, removed by: user-name. Removed privileges: acl-privileges.

`acl-role`	Name of the OSM role whose privileges have been removed.
`user-name`	User id of the user who removed the access privileges.
`acl-privileges`	Comma separated list of privileges that have been removed from this role.

Cause This event is generated when a role has had one or more privileges removed through the Access Control List dialog in the OSM Service Connection.

Effect A role has had one or more privileges removed.

Recovery Informational message only; no corrective action is needed.

1179

An OSM action has been denied access. Action: action-display-name, resource: resource-name, user denied access: user-name, workstation IP address: workstation-ip.

`action-display-name`	Name of the OSM action display name corresponding to the command for which the OSM server has denied access.
`resource-name`	The resource name on which the command was attempted.
`user-name`	User id for which the access to the command has been denied.
`workstation-ip`	The IPV4 or IPv6 address of the workstation from where the command was initiated.

Cause This event is generated when an OSM command is rejected by the OSM server because the user does not have access to execute the OSM command. If the Access Control List feature is disabled, this event will not be generated.

Effect An OSM action has been denied access.

Recovery In order for that user to perform that OSM action, access privileges would have to be granted through the Access Control List dialog in the OSM Service Connection.

1180

A default OSM role has been restored. Role: acl-role, restored by: user-name.

`acl-role`	Name of the OSM role that has been restored.
`user-name`	User id of the user who restored this role.

Cause This event is generated when a default OSM role has been restored using the Access Control List dialog in the OSM Service Connection.

Effect A previously deleted default OSM role has been restored and should once again be visible in the Access Control List dialog in the OSM Service Connection.

Recovery Informational message only; no corrective action is needed.

1300

Power Regulator management was enabled for processor in blade-name. The previous Power Regulator setting was reported as setting.

processor

The processor for which this message applies.

blade-name

The server blade for which this message applies.

setting

One of the following values:

HP Power Regulator Not Enabled (High Power)
Static Low Power
Static High Performance
Dynamic Power Savings
Unknown value where an undocumented numeric value was returned by the millicode API to enable Power Regulator.

Cause OSM enabled Power Regulator on this server blade because of one of the following reasons:

An authorized user issued a command on the system object in the OSM Service Connection.
A processor was reloaded and Power Regulator was previously enabled on the system object.
The OSM server was restarted.

Effect The processor accepts new Power Regulator levels from the iLO in the server blade, enabling Power Regulator to control the power efficiency setting. Subsequent CPU subsystem event 440 instances record further changes in the Power Regulator setting.

Recovery Informational message only; no corrective action is needed. For more information about using Power Regulator with NonStop BladeSystems, refer to the NonStop BladeSystem Planning Guide.

1301

Power Regulator management was disabled for processor in blade-name. The previous Power Regulator setting was reported as setting.

processor

The processor for which this message applies.

blade-name

The server blade for which this message applies.

setting

One of the following values:

Power Regulator Not Enabled (High Power)
Static Low Power
Static High Performance
Dynamic Power Savings
Unknown value where an undocumented numeric value was returned by the millicode API to enable power management

Cause OSM disabled Power Regulator on this server blade because an authorized user issued a command on the system object in the OSM Service Connection.

Effect The processor does not accept new Power Regulator levels from the iLO in the server blade, disabling Power Regulator control of the power efficiency setting. The power efficiency setting changes to a high power setting. This change is recorded in a subsequent CPU subsystem event number 440.

Recovery Informational message only; no corrective action is needed. For more information about using Power Regulator with NonStop BladeSystems, refer to the NonStop BladeSystem Planning Guide.

1302

Enable blade Power Regulator management failed for processor on blade-name. Failure code: failure-code

processor

The processor for which this message applies.

blade-name

The server blade for which this message applies.

failure-code

One of the following values:

Blade had downrev firmware (-1)	The default version of firmware is newer than the current version on the server blade.
Power Regulator management not supported (-2)	The firmware version on the server blade does not support Power Regulator.
Hardware problem (-3)	Possible hardware problem detected in the Polaris or ICH chip.
Other error (-4)	Internal error. Retry operation and if problem persists, contact your service provider or GNSC.
Enable already in progress (-5)	Enable already in progress.

Cause OSM could not enable Power Regulator on this server blade.

Effect The Power Regulator remains unchanged.

Recovery Identify the Failure Code from the event. Review alarms for Power Regulator on the System Object in the OSM Service Connection. The textual description of the failure code may indicate the origin of the problem. Recovery may involve updating the server blade firmware to a version supporting Power Regulator, followed by repeating the OSM command to enable Power Regulator on the System Object. For more information about using Power Regulator with NonStop BladeSystems, refer to the NonStop BladeSystem Planning Guide.

1303

Disable blade Power Regulator management failed for processor on blade-name. Failure code: failure-code

processor

The processor for which this message applies.

blade-name

The server blade for which this message applies.

failure-code

One of the following values:

Blade had downrev firmware (-1)	The default version of firmware is newer than the current version on the server blade.
Power Regulator management not supported (-2)	The firmware version on the server blade does not support Power Regulator.
Hardware problem (-3)	Possible hardware problem detected in the Polaris or ICH chip.
Other error (-4)	Internal error. Retry operation and if problem persists, contact your service provider or GNSC.
Disable already in progress (-5)	Disable already in progress.

Cause OSM could not disable Power Regulator on this server blade.

Effect The Power Regulator remains unchanged.

Recovery Identify the appropriate recovery from the Failure Code from the event. Review alarms for Power Regulator on the System Object in the OSM Service Connection. The textual description of the failure code may indicate the origin of the problem. If Power Regulator was not enabled on this server blade before use of the OSM command to disable Power Regulator on the System Object, then no recovery is required. Power Regulator cannot be enabled or disabled on a server blade with versions of blade firmware which do not support this function. For more information about using Power Regulator with NonStop BladeSystems, refer to the NonStop BladeSystem Planning Guide.

1500

User user-name has issued the system shutdown script in {automatic|interactive} mode. This will result in system shutdown through power fail processing by the system.

User user-name has issued the system shutdown script in simulation mode. This will NOT result in the system shutdown.

user-name

The NonStop user ID of the user who executed the system shutdown script.

Cause A user executed the Data Center Power Control system shutdown functionality from HP Insight Control Power Management in one of three modes: automatic, interactive, or simulation.

Effect In automatic or interactive modes, the system will execute any shutdown script specified in $SYSTEM.ZSERVICE.OSMCONF and will power off. In simulation mode, the system will not power off.

Recovery Informational message only; no corrective action is needed.

7001

Rediscover-module Group, module: Enclosure, Module

Enclosure, Module

is the group and module that OSM rediscovered.

Cause OSM rediscovered a module.

Effect FRUs, CRUs, or objects that were inserted or removed and were missing from the OSM GUI will now appear. This is an internal message only.

Recovery Informational message only; no corrective action is needed.

8001

Disk-sector-failure Sector failure count: Sector-failure-count Errant sector: Disk-logical-sector Logical Volume: Object-Name Path: Path Logical Device Number: Ldev-Number

`Sector-failure-count`	is the number of sectors on which errors occurred.
`Disk-logical-sector`	is the logical sector address on which an error occurred.
`Object-Name`	is the logical name of the disk.
`Path`	is the logical path of the disk.
`Ldev-Number`	is the number of the logical device.

Cause The Validate Checksum disk action encountered one or more sector checksum errors.

Effect One or more sectors on the disk has a bad sector checksum.

Recovery Follow standard procedures and warnings to correct any sector checksum errors.