Chapter 126 TSM Messages

The messages in this chapter are generated by the TSM server software. The subsystem ID displayed by these messages includes TSM as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

1100

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

IR-number

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

resource-name

is the name of the resource that caused the problem incident report to be created.

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. The possible values are:

Adapter Type Mismatch	Left Neighbor Y Link Connected To Local Y Right Link	Processor Hardware Freeze
ASIC Freeze Error	Left Neighbor Y LBU Connected To Local X LBU	Processor was down and reloaded
Automatic Expand Line Handler Configuration Failure	Left Neighbor X LBU Connected To Local Y LBU	Program Checksum Error
Automatic Redundant Power Scrub Test not run because of Hardware Error Alarm on internal fabric	Link Receive Disabled on ServerNet Switch Port	Recoverable Error Threshold Exceeded
Backpressure Fault	Link Transmit Disabled on ServerNet Switch Port	Remote ServerNet Switch Connected To Wrong Port of Local ServerNet Switch
Backfeed Contact Failure	Local ServerNet Switch Port Not Connected To Remote ServerNet Switch Port	Retry Limit Exceeded
Backup Firmware Not Same as Running Firmware	Low Battery Voltage	Right Neighbor X Right Link Connected To Local X Right Link
Backup Configuration Not Same as Running Configuration	Low Inverter Voltage	Right Neighbor Y Right Link Connected To Local Y Right Link
Backup Power Rail Failure	Lower Boot Block Section of FLASH Locked	Right Neighbor X Link Connected To Local X Left Link
Battery Failure	Max. Sector Rewrites For Period Exceeded	Right Neighbor Y Link Connected To Local Y Left Link
Both Configurations Incorrect After Load	Max. Sector Spares for Life Exceeded	Right Neighbor Y LBU Connected To Local X LBU
Cable Between UPS And AC Transfer Switch Disconnected	Max. Sector Spares For Period Exceeded	Right Neighbor X LBU Connected To Local Y LBU
Cable Between AC Transfer Switch And ServerNet Switch Disconnected	Medium Error	Running Down Rev Firmware
Configuration Incompatibility Between Local ServerNet Switch And Remote ServerNet	Millicode Halt	Running Image Source Loaded From Peer
Configuration Tag Mismatch Between X And Y ServerNet Switches	Mismatch In X Left And X Right Topologies	Running Old Os Image from Peer
Configuration Version Mismatch Between X and Y ServerNet Switches	Mismatch In Y Left And Y Right Topologies	Same physical device configured as Primary and Mirror
Corrupt Firmware	Missing Battery	SANMAN Running Without a Backup
Configuration Version Mismatch Between Local and Remote ServerNet Switch	Missing Fan	SCSI Boot Code Upload Fail
Corrupt Configuration	Missing Modular ServerNet Expansion Board	SEEPROM Checksum Error
Correctable Memory Error	Missing NNA Plug-in Card	Sense Key Error
Correctable Secondary Cache Error	Missing Power Monitor and Control Unit	ServerNet Path Down
CRU Configuration Error	Missing Power Supply	ServerNet Router Port Error
CRU Initialization Failed	Missing Remote ServerNet Switch	ServerNet Router2 Port Exception
Data Integrity Error	Missing ServerNet Switch	ServerNet Services Initialization Error
Data Miscompare Error on Attached Disk	Missing ServerNet Switch PIC	ServerNet Switch Internet Stack Overflow
Data Synchronous Mark Error	MSEB Configuration Record Fetch Error	ServerNet Switch Not Responding
Disconnected Cable	Network Error	ServerNet Switch Operating on Battery Power
Disk Inaccessible (All Paths are Down)	New Configuration Incorrect After Load	ServerNet Switch Router Self Check Error
Disk Path Down	NNA Programming Error	ServerNet Switch Port Disabled For ServerNet Traffic
Disk Path Switched	NNA Verify Failure	Service Processor I/O Library Routine Call Error
Down-rev Configuration	Node Plugged Into Wrong Port of ServerNet Switch	Software Error
Down-rev Firmware	No Index Signal Error	Software Halt
Down-rev MSEB NNA PIC	No Memory	SNETMON Running Without a Backup
Expected Disk Failure	No Seek Complete Error	SNETMON Unable to Discover Remote Node
Fabric Setting Mismatch Between Local ServerNet Switch And Remote ServerNet Switch	Not Communicating	SRAM Memory Test Failure
Factory Default Configuration Loaded	Not Same Remote ServerNet Switch Connected to All Local ServerNet Switch Ports	Storage ASIC Initialization Failure
Fan Failure	Not Same Systems On X Left And Y Left Sides	SWAN Download Error
Firmware Version Mismatch Between X and Y ServerNet Switches	Not Same Systems On X Right And Y Right Sides	SWAN Kernel Error
Firmware Version Mismatch Between Local and Remote ServerNet Switch	Operational Code Download Failed	Tape Path Down
Firmware Update Problem	Optical Disk Drive Down	Tape Path Switched
FLASH Program Error	Optical Storage Library Down	Tnet Configuration Error
FLASH Sector Test Failure	Overloaded UPS	Too many Secondary Cache CMEs
FOX LBU Down	Packet Receive Disabled on ServerNet Switch Port	Too many soft CMEs
FOX Processor-to-Processor Connectivity Loss	Packet Transmit Disabled on ServerNet Switch Port	Tape Path Down
Ground Failure	Path A Down	Track Following Error
Hardware Error	Path B Down	Temperature Limits Exceeded
IBC Driver Limit of ServerNet Switches Exceeded	Peripheral Device Write Fault	Temperature Warning
Internal Target Failure	Port Number Mismatch Between Local ServerNet Switch And Remote ServerNet Switch	Too Many SS7TE3 PICs
Incorrect Logical Configuration	Possible Power Problem	Too Many ServerNet Switch Automatic Resets Because of Backpressure
Insufficient Backup Time on UPS	Power Loss	Too Many State Transitions
Interprocessor Communication Path(s) Down	Power Supply Failure	Uncorrectable Media Error on Unmirrored Drive
Invalid Fabric Parameter Error	Power-on Self Test Failed	Uncorrectable Memory Error
Invalid Fabric Setting	Power-on Self Test Not Run	Upper Boot Block Section of FLASH Locked
Invalid FLASH ID	Power Problem	UPS Failure
Invalid GUID	Power Supply Fan Failure	UPS Not Responding
Invalid MSEB Configuration Records	Power Test Failed	Value Added Diagnostic Services Disabled
Invalid ServerNet Switch Control Block	Predictive Failure Analysis Threshold Reached on Recoverable Errors Undefined	Value Added Diagnostic Services Enabled
Invalid ServerNet Switch PIC Type	Primary and Backup paths configured on same ServerNet Fabric	Value Added Diagnostic Services Warning
IOP Line Parameter Error	Primary and Backup paths configured to different devices	Volume Over Flow
I/O Process Error	Primary Power Rail Failure	Wrong PIC Type
Left Neighbor X Left Link Connected To Local X Left Link	Processor Hung	X Fabric Not Connected to the Same ServerNet Switch Port as Y Fabric
Left Neighbor Y Left Link Connected To Local Y Left Link	Process Switched Processor
Left Neighbor X Link Connected To Local X Right Link	Processor Down

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

Effect The TSM Notification Director Application receives the problem incident report. If you have configured automatic dial-out for problem incident reports, the report is dialed out to your service provider. Otherwise, you can view and authorize the incident report as you choose, using the TSM Notification Director Application.

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 on the TSM workstation.

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 periodically to test the dial-out path to the service provider. The default frequency is once every 14 days.

Effect The TSM Notification Director Application receives the periodic incident report. If you have configured automatic dial-out for periodic incident reports, the report is dialed out to your service provider. Otherwise, you can view and authorize the incident report as you choose, using the TSM Notification Director Application.

Recovery Informational message only; no corrective action is needed.

1102

An Incident Report has been acknowledged by the Tandem Support Center for IR id#: IR-number, reference number: case‑ID‑number.

`IR-number`	is the number associated with the incident report. The incident report number is unique for the system.
`case-ID-number`	is the unique service provider case ID number returned for this incident report.

Cause A case ID number for an incident report was received from the service provider.

Effect None

Recovery Informational message only; no corrective action is needed.

1103

An Incident Report has failed to be delivered. IR id#: IR-number, Reason: reason, From TSM console: workstation-ip-address, To Service Provider IP Address service-provider-ip-address, Using path: path

`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 dial-out problem (such as a busy signal), a failure to receive authorization for dial-out, or a time-out.
`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.
`path`	indicates whether the failure occurred in the primary dial-out path or in the backup dial-out path.

Cause An attempt to deliver an incident report to the service provider failed. The reason parameter describes the probable cause of the failure.

Effect The TSM Notification Director Application closes the point-to-point (PPP) link. If this error occurred for the primary path, the TSM server attempts to deliver the incident report through the backup dial-out path. If both primary and backup delivery paths fail, the incident report is marked as undelivered and is saved on your system.

Recovery Correct the problem that is preventing delivery of your incident reports. After you have corrected the problem, use the TSM Notification Director Application to retrieve this incident report.

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 S-series 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 TSM server software generate a software configuration incident report to report the software configuration change to your service provider.

Effect The TSM 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 S-series 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 TSM 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 TSM server sends the software configuration incident report to the TSM Notification Director Application. If authorized, the TSM Notification Director Application forwards the incident report to your service provider.

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 TSM server software generated an incident report to request a new service password.

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

Recovery Informational message only; no corrective action is needed.

1107

The user has deleted an Alarm object. Alarm Object ID: Alarm-ID, 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

`alarm-ID`	is the number associated with the alarm.
`resource-name`	is the name of the resource that generated the alarm.
`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.
`username`	is the NonStop OS user name of the user who deleted the alarm.
`workstation-ID`	indicates the workstation from which the alarm was deleted.

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

Effect The alarm is removed from the Alarm Summary dialog box in the TSM Service Application. 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 will be generated.

Recovery Informational message only; no corrective action is needed.

1108

Snet Path Test was run. Fabric: fabric, Path Test Started Time: started, Path Test Completed Time: completed, Result: result, Repair Action 1: repair action, Repair Action 2: repair action, Repair Action 3: repair action, Repair Action 4: repair action, Repair Action 5: repair action,

`fabric`	indicates which internal ServerNet fabric was tested: either fabric-X or fabric-Y.
`started`	is the date and time that the path test was started.
`completed`	is the date and time that the path test was completed.
`result`	indicates the success of the path test. A value of 1000000 indicates that the path test passed. A value of 3008301 indicates that the path test failed.
`repair action`	is one of 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.

Cause 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 TSM Service Application.

Effect None if the test passes. If the test fails, alarms are generated in the TSM Service Application.

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 TSM Service Application.

Effect None

Recovery Informal message only; no corrective action is needed.

1110

TSM-Correctable-Cache-Error. text

text

is one of the following:

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 TSM Service Application.
Transient CCE. cce-tran-count CCEs have been detected in the past cce-read-count examinations within the last 25 hours. Repair action: None
Intermittent CCE. Transient CCEs have been detected in the last cce-tran-count days. Replace the PMF CRU at your convenience. To determine the correct PMF CRU to replace, check the CCE alarm generated by the TSM Service Application.
For your information. Currently, cce-count CCEs were 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 TSM EMS Event Viewer Application:

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 S-series server on which the CCE was detected. The possible values are NSR-G, NSR-T, or NSR-V.

cpu-type

is the type of NonStop S-series server on which the processor resides. The value is S70000.

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 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 TSM Service Application 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 Enter this 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 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 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 TSM Service Application.

Effect Alarms are generated in the TSM Service Application.

Recovery Use the TSM Service Application 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

TSM-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 S-series server on which the processor resides. The value is S70000.
`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 Informational message only; no corrective action is needed.

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 TSM Service Application.

Effect The Redundant Power Scrub action cannot be performed.

Recovery Using the TSM EMS Event Viewer Application, 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 TSM on node-number.

node-number

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

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

Effect None

Recovery Informational message only; no corrective action is needed.

1119

TSM 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 TSM RAL command failed. Alarms and events for the associated subsystem might not be generated.

Effect None

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 TSM Service Application and has finished. This event is generated to inform the other TSM 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 TSM Service Application on the specified disk drive and has finished successfully.

Effect None

Recovery Informational message only; no corrective action is needed.

1122

TSM-Disk-Validate-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

TSM-Disk-Validate-Done 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

TSM-Disk-Sector-Checksum-Error Sector: Disk-logical-sector Disk Drive: Xldevname 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

TSM-Storage-Syndrome-Error Disk Drive: Xldevname Logical Device Number: Ldev-Number

`Xldevname`	is the name of the disk drive the TSM 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 TSM server was accessing the disk drive. This is usually a transient error.

Effect None

Recovery Informational message only; no corrective action is needed.

7001

Rediscover-module Group, module: Enclosure, Module

Enclosure, Module

is the group and module that TSM rediscovered.

Cause TSM rediscovered a module.

Effect CRUs or objects that were inserted or removed and were missing from the TSM 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.