HP NetServer AA Solution Messages HP Part Number 5969-5966 Printed in September 2000
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Preface Chapter 1 — Introduction Examining the Windows NT Event Log . . . . . . . . . . . . . . . . . . . . . 3 HP NetServer AA Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Format of HP NetServer AA Messages . . . . . . . . . . . . . . . . . . . 5 HP NetServer AA Message Categories and Conventions. . . . . . . . . . 6 Message Reporting Sources . . . . . . . . . . . . . . . . . . . . . . . . 7 Message Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents IOPn.MtcDsl Status Messages. . . . . . . . . . . . . . . . . . . . . . . . . 98 Chapter 7 — MtcEthP and MtcEtx Messages IOPn.MtcEthP and IOPn.MtcEtx Message Summary . . . . . . . . . . . . . 112 IOPn.MtcEthP Status Messages . . . . . . . . . . . . . . . . . . . . . . . . 115 IOPn.MtcEtx Status Messages. . . . . . . . . . . . . . . . . . . . . . . . . 130 Chapter 8 — MtcEvtP Messages IOPn.MtcEvtP Status Message Summary . . . . . . . . . . . . . . . . . . . 138 IOPn.MtcEvtP Status Messages . . . .
Contents Chapter 14 — MtcScsiP and MtcScsiR Messages MtcScsiP and MtcScsiR Status Message Summary. . . . . . . . . . . . . . 294 IOPn.MtcScsiP Status Messages . . . . . . . . . . . . . . . . . . . . . . . 302 IOPn.MtcScsiR Status Message . . . . . . . . . . . . . . . . . . . . . . . . 352 Chapter 15 — MtcSmR Messages IOPn.MtcSmR Status Message Summary . . . . . . . . . . . . . . . . . . . 354 IOPn.MtcSmR Status Messages. . . . . . . . . . . . . . . . . . . . . . . .
Contents vi
Tables 1-1 1-2 1-3 1-4 1-5 2-1 3-1 4-1 5-1 6-1 7-1 8-1 9-1 10-1 11-1 12-1 13-1 14-1 15-1 16-1 17-1 18-1 Event Log Icons and Severity Levels . . . . . . . . . . . . . . Message Reporting Source. . . . . . . . . . . . . . . . . . . . Message Variables . . . . . . . . . . . . . . . . . . . . . . . . HP NetServer AA Message Summary – Unprefixed Messages . HP NetServer AA Message Summary – Prefixed Messages . . MIC BIOS Message Summary. . . . . . . . . . . . . . . . . . Message Summary . . . . . . . . . . . . .
Tables viii
Preface This guide lists and describes all HP NetServer AA server messages. Audience This guide is written for experienced network administrators and technical personnel responsible for installing, configuring, administering, and managing network server hardware and software, including Microsoft Windows NT, as well as all users of HP NetServer AA servers.
Preface Conventions The following conventions are used in the HP NetServer AA documentation set: Convention Description Italics, Courier font Indicates a variable that you replace in a path name or command Bold, Courier font Indicates actions or commands that you must type. For example, type A:\ETX Courier font Represents examples of screen text. For example, scsiid = 0, 1. Bold Is used to: Italics • Emphasize important information. • Indicate menu, pathname, or button selections.
1 Introduction This chapter describes the basics about HP NetServer AA server messages, including: • Messages that are logged to the Windows NT System Event Log • Messages that display in a Windows NT blue screen on a monitor attached to the CE either as the CE operating system is booting or when a CE is being deconfigured • Messages that display on the BIOS screen or the Windows NT blue screen during the boot process or CE resynchronization process • Messages that display in a pop-up window while th
Chapter 1 This chapter contains the following sections: Examining the Windows NT Event Log . . . . . . . . . . . . . . . . 3 HP NetServer AA Messages . . . . . . . . . . . . . . . . . . . . . . 4 Format of HP NetServer AA Messages . . . . . . . . . . . . . . . . 5 HP NetServer AA Message Categories and Conventions . . . . . . . 6 Message Reporting Sources . . . . . . . . . . . . . . . . . . . . . . 7 Message Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Message Summary . . . . . . . . .
Chapter 1 Introduction Examining the Windows NT Event Log To open the Windows NT Event Log, from the Task bar, select Start Programs Administrative Tools (Common) Event Viewer. When the application launches, from the Log menu, select System, since nearly all HP NetServer AA events are written to this log. Use the Event Viewer’s menus to select various parameters that control how you will view events.
Chapter 1 Introduction HP NetServer AA Messages When it is operational, HP NetServer AA software continuously monitors the HP NetServer AA server.
Chapter 1 Introduction Because of this message logging process, in the CE Event Viewer, the timestamp information for messages logged by the IOPs is the time that the CE received the message; it does not necessarily indicate the time that the message occurred on the IOP. To confirm the time that the message occurred, check the event logs on the IOPs. In the CE Event Viewer, the message IOPn.MtcMon status: The boot process has completed for CE1 indicates the CE started uploading any IOP events.
Chapter 1 Introduction When troubleshooting an HP NetServer AA server, check the event logs for HP NetServer AA messages that start with or . Because the HP NetServer AA server uses standard event reporting, you can integrate standard notification applications (for example, paging devices and third-party software) to notify you when a fault occurs. For a detailed listing of HP NetServer AA messages, refer to subsequent chapters in this manual.
Chapter 1 Introduction Message Reporting Sources Table 1-2 lists the sources that report the HP NetServer AA messages. Table 1-2Message Reporting Source Reporting Source Message Prefix Reports . . . Refer to FloR MtcFloR status Floppy Redirector messages Chapter 9 MtcBIOS None MIC BIOS messages, displayed during the Windows NT boot and synchronization process Chapter 2 Note: These messages are not written to the Windows NT Event Log. MtcCEX IOPn.
Chapter 1 Introduction Table 1-2Message Reporting Source (Continued) Reporting Source Message Prefix Reports . . . Refer to MtcMon IOPn.MtcMon Fault Handler status HP NetServer AA system control messages Chapter 13 IOPn.MtcMon FRU IOPn.MtcMon status MtcScsiP IOPn.MtcScsiP status SCSI Provider messages Chapter 14 MtcScsiR None SCSI Redirector message that is logged only in the CE event log Chapter 14 MtcSmR IOPn.MtcSmR status HP NetServer AA Manager messages Chapter 15 MtcVidP IOPn.
Chapter 1 Introduction Table 1-3Message Variables (Continued) Variable Description logDevName A logical device name. A logical device name is an abstract representation of the mirrored drives that comprise a mirrored disk set. For example, for two physical disks that comprise a mirror set at physical SCSI settings 0-0-1-0 (IOP1 disk at SCSI settings (0-0-1-0) and IOP2 disk at SCSI settings (0-0-1-0)), the logical device name is Disk0; the next mirror set would have a logical device name of Disk1.
Chapter 1 Introduction Table 1-4HP NetServer AA Message Summary – Unprefixed Messages (Continued) Message Page A field entry in the MTCSMAPI.DLL contains incorrect data. page 373 A function entry in the MTCSMAPI.DLL contains incorrect data. page 373 A non-critical error occurred initializing the Keyboard Pointer Redirector. page 161 A provider entry in the MTCSMAPI.DLL contains incorrect data. page 373 A provider entry in the MTCSMAPI.DLL contains incorrect target data.
Chapter 1 Introduction Table 1-4HP NetServer AA Message Summary – Unprefixed Messages (Continued) Message Page Datagram Service is not bound to any adapter. page 64 Datagram Service is not installed. page 64 Datagram Service should be bound to the same adapter as the IOP Link Driver. page 64 Datagram Service should be bound to the same adapters as the Ethernet Provider. page 64 Datagram Service should not be bound to the Virtual Network Provider.
Chapter 1 Introduction Table 1-4HP NetServer AA Message Summary – Unprefixed Messages (Continued) Message Page IOPx has aborted synchronization page 51 IOPx has aborted the boot process page 51 IOPx has requested a reset page 51 MAC address for the redirected rail number n in the configuration is incorrect. page 67 Memory allocation failure. page 161 MIC BIOS internal error: module line line page 51 MIC cable fault on portn: reason.
Chapter 1 Introduction Table 1-4HP NetServer AA Message Summary – Unprefixed Messages (Continued) Message Page Platform initialization failed page 56 Press or Control-M for MIC setup. Press to bypass initialization. page 56 Reboot Required: The system must be rebooted for changes to take effect. Press to bypass automatic reboot or any other key to reboot. page 56 Request for memory failed. page 376 Requested object not found.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages Message Page IOPn.MtcDgs status: Datagram Service protocol version mismatch. page 91 IOPn.MtcDgs status: Error accessing data in the Registry. page 91 IOPn.MtcDgs status: Error in NIC bindings. page 91 IOPn.MtcDgs status: Error transferring incoming Ethernet packet to the receive buffer. page 92 IOPn.MtcDgs status: Ethernet transmit error. page 92 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcDsl status: An invalid component type was encountered (offendingValue). page 101 IOPn.MtcDsl status: An invalid DSL packet ID was encountered (offendingValue). page 102 IOPn.MtcDsl status: An invalid IOP state was encountered (offendingValue). page 102 IOPn.MtcDsl status: An invalid logical device operation type was encountered (offendingValue). page 103 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcEthP status: A call to NdisReset timed out. page 115 IOPn.MtcEthP status: A critical error occurred initializing the Ethernet Provider. page 115 IOPn.MtcEthP status: A duplicate address has been detected on device x (y). page 116 IOPn.MtcEthP status: An internal state consistency error has been detected on device x (y). page 117 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcEthP status: NdisReset returned an unknown error. page 126 IOPn.MtcEthP status: Physical Ethernet device has failed. page 127 IOPn.MtcEthP status: Runt Ethernet packet received. page 127 IOPn.MtcEthP status: The network adapter driver x (y) modifies the source address in outgoing packets to be the current station address.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcEtx status: Send packet allocation failure. page 135 IOPn.MtcEtx status: Unable to open NIC; initialization aborted. page 136 IOPn.MtcEtx status: Unable to query or set NIC. page 136 IOPn.MtcEtx status: Unable to reset NIC. page 136 IOPn.MtcEvtP status: An error has occurred that prevented proper initialization of the Event Provider.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcFLOP status: An error has occurred that prevented proper initialization of the Floppy Provider. The provider has registered with the DSL, but may not allow access to the floppy drives. page 147 IOPn.MtcFLOP status: The Floppy Provider attempted to attach a floppy device to the floppy driver’s device object, but failed. As a result, that floppy device will be inaccessible.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcKmP status: Pointer attributes mismatch. Pointer devices are not identical. page 167 IOPn.MtcKmP status: Timeout waiting for join complete from active Keyboard Pointer Provider. page 167 IOPn.MtcKmP status: Timeout waiting for join response from active input provider. page 167 IOPn.MtcKmP status: Unconsumed keyboard input discarded. page 167 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcMon Fault Handler status: Fault event processing completed, but there were insufficient system resources to provide a complete event history. Removed Units: x page 193 IOPn.MtcMon Fault Handler status: Fault event processing completed, but there were insufficient system resources to provide a complete event history. Removed Units: x page 194 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcMon FRU: IOPx processing capability failure. page 204 IOPn.MtcMon FRU: IOPx <-> CEy cross tuple fault. page 205 IOPn.MtcMon FRU: IOPx <-> CEy interconnect fault. page 206 IOPn.MtcMon FRU: IOPx IOP-IOP Link (IL) netcard capability, cabling, or remote netcard. page 206 IOPn.MtcMon FRU: IOPx/CEy tuple power supply failure. page 207 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcMon status: A protocol error occurred with CEx while suspension of the CE operating system was being attempted. page 218 IOPn.MtcMon status: A protocol error was detected on IOPx during IOP joining. page 219 IOPn.MtcMon status: An Endurance Manager command has been issued to disable CEx. page 219 IOPn.MtcMon status: An Endurance Manager command has been issued to disable IOPx.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcMon status: An unknown packet has been received by the Monitor. Packet command = x. page 231 IOPn.MtcMon status: CE boot failed because the Monitor’s ConfigurationArcTree Registry entry on IOPx is invalid. page 231 IOPn.MtcMon status: CE boot or synchronization could not be performed because the 16bit platform-specific initialization module file could not be opened. page 232 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcMon status: CEx could not be booted because the SCSI boot driver has not registered with the Monitor on IOPy. page 240 IOPn.MtcMon status: CEx could not be removed or disabled because CE synchronization is currently in progress. page 240 IOPn.MtcMon status: CEx could not be removed or disabled because it is the only active CE.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcMon status: ESIx has been enabled by operator request. page 251 IOPn.MtcMon status: ESIx is faulted and requires repair. page 252 IOPn.MtcMon status: IL12 has been enabled by operator request. page 252 IOPn.MtcMon status: IL12 is faulted and requires repair. page 253 IOPn.MtcMon status: IOPx cannot be shut down because it is already offline. page 253 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcMon status: IOPx is unavailable for initialization because it is currently FAULTED. page 263 IOPn.MtcMon status: IOPx joining has been aborted because the thresholding database was modified. IOP initialization and joining will be retried. page 263 IOPn.MtcMon status: IOPx was removed at the direction of IOPy. page 264 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcMon status: The CE CPU ID 0xx power-on settings do not match. CE1 CPU power-on settings = 0xy. CE2 CPU power-on settings = 0xz. page 274 IOPn.MtcMon status: The CE CPU ID 0xx speeds do not match. CE1 CPU speed = y MHz CE2 CPU speed = z MHz page 274 IOPn.MtcMon status: The CE CPU ID 0xx versions are not compatible. CE1 CPU version information = 0xy. CE2 CPU version information = 0xz.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcMon status: The CE operating system cannot be synchronized. A debug environment is active. page 282 IOPn.MtcMon status: The CE operating system cannot be synchronized. The CE hardware platform is not supported. page 282 IOPn.MtcMon status: The CE operating system cannot be synchronized. The version of Windows NT on the CE is not supported. page 283 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcMon status: The synchronizing CE’s memory size is less than the size of memory in use by Windows NT. Windows NT memory size = y kilobytes. CEx memory size = z kilobytes. page 290 IOPn.MtcMon status: The synchronizing CE’s memory size is not equal to the active CE’s memory size. CE1 memory size = y kilobytes. CE2 memory size = z kilobytes. page 291 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcScsiP status: Cannot access DISKn for requested operation. Check prior events for details. page 306 IOPn.MtcScsiP status: Cannot disable write cache for DISKn. This disk type may have exhibited problems with write cache. This feature should be disabled to prevent corruption problems. It is strongly recommended that this drive not be used. page 306 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcScsiP status: DEVICEn has a SCSI logical unit number (LUN) different than configured on the other IOP, and it will be marked offline. page 312 IOPn.MtcScsiP status: DEVICEn has a target ID different than configured on the other IOP, and it will be marked offline. page 312 IOPn.MtcScsiP status: DEVICEn location contains an unsupported device. page 312 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcScsiP status: DISKn does not support automatic bad block remapping for recoverable read requests. page 318 IOPn.MtcScsiP status: DISKn does not support automatic bad block remapping for write requests. page 318 IOPn.MtcScsiP status: DISKn encountered a bad block at SECTOR during a mirror copy. page 319 IOPn.MtcScsiP status: DISKn encountered a write error during a mirror copy.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcScsiP status: DISKn has an invalid partition signature. Use Disk Administrator in Offline HP NetServer AA I/O Processor Mode to partition the disk, making sure to add an HP NetServer AA partition. page 325 IOPn.MtcScsiP status: DISKn has an IOP ID other than the current IOP ID. This indicates DISKn has come from a different IOP.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcScsiP status: DISKn mirror set is up to date. (This message may occur during IOP join, when both CEs are down, or whenever a disk is enabled.) page 330 IOPn.MtcScsiP status: DISKn must be offline. HP NetServer AA Manager request ignored. page 330 IOPn.MtcScsiP status: DISKn was shut down gracefully. page 330 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcScsiP status: Mirror set copy from IOPn to IOPn for DISKx has halted due to a copy write failure to local IOP’s DISKn. page 336 IOPn.MtcScsiP status: Mirror set copy from IOPn to IOPn for DISKx has halted. The local IOP lost access to DISKn. page 337 IOPn.MtcScsiP status: Mirror set copy from IOPn to IOPn for DISKx has halted.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcScsiP status: Unable to find a configured boot disk. Use the HP NetServer AA Configuration Utility to add a boot disk or mark an existing disk as bootable. page 342 IOPn.MtcScsiP status: Unable to flush cache for DISKn. page 343 IOPn.MtcScsiP status: Unable to get provider information from Registry. Contact your service provider for assistance. page 343 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcScsiP status: Unable to write one or more CE requested sectors SECTORn SECTORm for DISKn. If DISKn stays online, this error may be considered transient. Many transient errors may indicate the need for disk replacement. page 350 IOPn.MtcScsiP status: Unable to write one or more sectors SECTORn – SECTORm for DISKn. Note: the write request did not come from the CEs. page 351 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page IOPn.MtcVidP status: Error in Video Provider device configuration. page 359 IOPn.MtcVidP status: Invalid Registry parameter. Using default value. page 359 IOPn.MtcVidP status: Join response received, but Provider is not in the joining state. page 360 IOPn.MtcVidP status: Protocol version mismatch between the Video Provider and the Keyboard Pointer Provider. page 360 IOPn.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page MtcCEX: Last IOP removed via REMOVE_IOP command. page 76 MtcCEX: Lost communications with boot IOP. page 77 MtcCEX: MIC adapter is not configured for CE operation. page 77 MtcCEX: MIC adapter malfunction detected. page 78 MtcCEX: Received illegal CE control packet. page 78 MtcCEX: Received illegal communication from non-boot IOP.
Chapter 1 Introduction Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued) Message Page MtcFLOR status: The Floppy Redirector received an invalid sync-up response from the Floppy Provider. As a result, the floppy devices will be inaccessible. page 151 MtcFLOR status: The registration of MtcFloR with the CE Transport failed.
Chapter 1 42 Introduction
2 MIC BIOS Messages This chapter lists and describes the MIC BIOS messages. These messages are displayed only on the BIOS screen. The MIC BIOS messages are not written to the Windows NT Event Log, and they have no prefixes. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: Types of Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 44 MIC BIOS Message Summary . . . . . . . . . . . . . . . . . . . .
Chapter 2 MIC BIOS Messages Types of Messages There are two types of MIC BIOS messages: • Informational messages • Error messages In general, informational messages simply report progress of the boot or synchronization process or the status of MIC BIOS tests. In most cases, you do not need to perform any action when informational messages display. Error messages indicate problems or report reasons why progress is not occurring. In many cases, you can retry a test or reboot an element of the server.
Chapter 2 MIC BIOS Messages MIC BIOS Message Summary The following table lists the HP NetServer AA server MIC BIOS messages in the order that they are documented. Table 2-1 MIC BIOS Message Summary Message Page Automatic reboot in x seconds. page 47 Beginning boot process with IOPx. . . page 47 Beginning synchronization with CEy via IOPx. . . page 47 Confirm: Changes made to MIC settings have not been saved. Press to return to setup; press to exit.
Chapter 2 MIC BIOS Messages Table 2-1 MIC BIOS Message Summary (Continued) Message Page MIC error status status: module line line page 52 MIC identity unknown page 53 MIC initialization complete page 53 MIC internal error: module linen context context data page 53 MIC internal warning: module linen context context data page 54 MIC not found page 54 MIC system error detected by CEx involving IOPy: error identifier MIC error context: context data page 54 Negotiating HP NetServer AA startup w
Chapter 2 MIC BIOS Messages MIC BIOS Messages Automatic reboot in x seconds. Variables x – the amount of time in which the reboot will occur Severity Informational Description After a non-recoverable error is displayed, the MIC BIOS will pause for 30 seconds so the message can be viewed before automatically rebooting to reset the CE. Action No action is required. Beginning boot process with IOPx. . .
Chapter 2 MIC BIOS Messages Confirm: Changes made to MIC settings have not been saved. Press to return to setup; press to exit. Severity Informational Description A change was made to the MIC identity and was not saved in non-volatile memory. Unless the change is saved, it has no effect. Action • Press to return to the setup utility to save the change. • Otherwise, press to allow the exit to proceed without saving the change.
Chapter 2 MIC BIOS Messages Establishing CEy communication channels. . . Variables y – the ID of the local CE Severity Informational Description This message is displayed on the CEs when the MIC BIOS regains control from the System BIOS. This begins the boot or synchronization process, depending on whether this is the first or second CE to join the configuration. Action No action is required. Floppy detected. Bypassing HP NetServer AA startup.
Chapter 2 MIC BIOS Messages Incompatible platform module Severity Error Description The platform module specified on the startup IOP is not compatible with the MIC BIOS. This error is probably due to a mismatch between the MIC firmware version and the HP NetServer AA software installed on the IOP providing boot or synchronization services. Action • Update the MIC firmware. • Reinstall the IOP software.
Chapter 2 MIC BIOS Messages IOPx has aborted synchronization Variables x – the ID of the IOP that has aborted synchronization Severity Error Description The specified IOP has aborted synchronization. Action Consult the specified IOP’s event log for further information about why synchronization was aborted. IOPx has aborted the boot process Variables x – the ID of the IOP that has aborted the boot process Severity Error Description The specified IOP has aborted the boot process.
Chapter 2 MIC BIOS Messages MIC cable fault on portn: reason. Variables n – the ID of the port with the cable fault; either 1 or 2 Severity Error Description This message indicates that a hardware cable fault was detected on the specified port. The possible reasons for the cable fault are: Action • Reset – the element at the other end of the port was reset or lost power.
Chapter 2 MIC BIOS Messages MIC identity unknown Severity Informational Description The MIC element identity (CE1, CE2, IOP1, IOP2) has not been specified in non-volatile memory (or has been reset to the “Unknown” setting). The MIC BIOS automatically places the system in the setup utility so an identity can be selected. Action • Select the appropriate element identity. • Save the setting in non-volatile memory.
Chapter 2 MIC BIOS Messages MIC internal warning: module linen context context data Variables n – the line number Severity Error Description An unexpected hardware or firmware condition was detected in the specified module at the specified line. The context data provides additional information about the warning. This warning should not occur during normal operation. Action Contact your service provider for assistance. MIC not found Severity Error Description The MIC adapter was not found.
Chapter 2 MIC BIOS Messages Negotiating HP NetServer AA startup with IOPx. . . Variables x – the ID of the IOP with which communication has been established and the startup process is beginning Severity Informational Description Communication has been established with the specified IOP, and the startup process is beginning. Action No action is required. No MIC identity found: A MIC identity must be assigned and saved. Press to continue.
Chapter 2 MIC BIOS Messages Performing internal loopback tests. Severity Informational Description Internal loopback tests will be performed. Action No action is required. Platform initialization failed Severity Error Description The platform module provided by the startup IOP failed to identify or initialize the system. This error is probably due to the wrong CE platform type being selected when the IOP software was installed.
Chapter 2 MIC BIOS Messages Response timeout: message description Severity Error Description A response was not received in the time allotted. This can occur if the CE loses communication with the IOP providing boot or synchronization services, or if a hardware fault occurs. Action • Run the MIC BIOS client-server diagnostics between the CE and the IOP providing startup services to verify that the hardware is functioning properly.
Chapter 2 MIC BIOS Messages Test mode may be canceled by pressing . Severity Informational Description During the execution of a test, it is possible to press to cancel the test and return the element to use in an HP NetServer AA configuration. Action No action is required. Test terminated by user Severity Informational Description The user pressed the key during the execution of a test. Action No action is required. Unable to contact destination via port port.
Chapter 2 MIC BIOS Messages Watchdog timer expired Severity Error Description The MIC BIOS monitors progress during the startup process. If there is no activity for an extended period of time, this message is displayed and the system is automatically rebooted. This could occur due to System BIOS incompatibilities, software faults, or hardware failures.
Chapter 2 60 MIC BIOS Messages
3 Installation and Verification Procedure (IVP) Messages This chapter lists and describes the HP NetServer AA Installation and Verification Procedure status messages. These messages are written to the Windows NT Event Log on the IOP on which the event occurs. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: Types of Message . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 IVP Message Summary . . . . .
Chapter 3 Installation and Verification Procedure (IVP) Messages Types of Message The two types of IVP messages are: • Warning messages • Error messages Warning messages may require attention. A continued series of warning messages merits review to see if corrective action is required. Error messages indicate problems or report reasons why progress is not occurring.
Chapter 3 Installation and Verification Procedure (IVP) Messages IVP Message Summary The following table lists the HP NetServer AAserver IVP messages in the order that they are documented. Table 3-1 Message Summary Message Page Datagram Service is not bound to any adapter. page 64 Datagram Service is not installed. page 64 Datagram Service should be bound to the same adapter as the IOP Link Driver. page 64 Datagram Service should be bound to the same adapters as the Ethernet Provider.
Chapter 3 Installation and Verification Procedure (IVP) Messages IVP Messages Datagram Service is not bound to any adapter. Severity Error Description The HP NetServer AADatagram Service is not bound to any adapter. Action Bind the HP NetServer AADatagram Service to the appropriate adapters as described in Chapter 3 in the HP NetServer AA Solution Installation Guide. Datagram Service is not installed. Severity Error Description The HP NetServer AADatagram Service is not installed.
Chapter 3 Installation and Verification Procedure (IVP) Messages Datagram Service should not be bound to the Virtual Network Provider. Severity Error Description The HP NetServer AAVirtual Network Provider should not be bound to any HP NetServer AAservice. Action Disable the HP NetServer AADatagram Service or HP NetServer AAEthernet Provider from the HP NetServer AAVirtual Network Provider. Ethernet Provider and the IOP Link Driver should not be bound to the same adapter.
Chapter 3 Installation and Verification Procedure (IVP) Messages Ethernet Provider should not be bound to the Virtual Network Provider. Severity Error Description The HP NetServer AAVirtual Network Provider should not be bound to any HP NetServer AAservice. Action Disable the HP NetServer AAEthernet Provider from the HP NetServer AAVirtual Network Provider adapter. IOP Link Driver is not bound to any adapter. Severity Error Description The Endurance IOP Link Driver is not bound to any adapter.
Chapter 3 Installation and Verification Procedure (IVP) Messages IOP Link Driver should not be bound to the Virtual Network Provider. Severity Error Description The HP NetServer AAVirtual Network Provider should not be bound to any HP NetServer AAservice. Action Disable the HP NetServer AAIOP Link Driver from the HP NetServer AAVirtual Network Provider adapter. MAC address for the redirected rail number n in the configuration is incorrect.
Chapter 3 Installation and Verification Procedure (IVP) Messages Number of redirected rails and Ethernet bindings should be equal. Severity Error Description There are either more redirected rails than there are adapters, or more adapters than redirected rails. The number of redirected rails configured by the HP NetServer AAconfiguration utility does not equal the number of adapters bound to the HP NetServer AAEthernet Provider.
4 MtcCEX Messages This chapter lists and describes the HP NetServer AA server MtcCEX messages that can display on the Windows NT blue screen on a monitor attached directly to the CE. These messages are displayed either as the CE operating system is booting or when a CE is being deconfigured. These messages are not written to the Windows NT Event Log. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions.
Chapter 4 MtcCEX Messages MtcCEX Message Summary The following table lists the HP NetServer AA server MtcCEX messages in the order that they are documented. Table 4-1 MtcCEX Message Summary Message Page MtcCEX: 32-bit platform-specific compatibility failure. page 72 MtcCEX: 32-bit platform-specific initialization failed. Status = 0xyMtcCEX: 32-bit platform-specific initialization failed. Status = 0xy page 73 MtcCEX: Could not initialize MIC adapter.
Chapter 4 MtcCEX Messages Table 4-1 MtcCEX Message Summary (Continued) Message Page MtcCEX: Unable to find the CE MIC adapter. page 83 MtcCEX: Unable to generate SYSERR packet. Status = 0xy page 84 MtcCEX: Unable to initialize QI mechanism. Status = 0xy page 84 MtcCEX: Unable to initialize the MIC adapter. Status = 0xy page 85 MtcCEX: Unable to read the Windows NT Registry. Status = 0xy page 85 MtcCEX: Unable to register BUGCHECK notification.
Chapter 4 MtcCEX Messages MtcCEX Messages The MtcCEX (CE Transport) messages display only on the CE’s Windows NT blue screen on a monitor attached directly to a CE. These messages are not written to the Windows NT Event Log. MtcCEX: 32-bit platform-specific compatibility failure.
Chapter 4 MtcCEX Messages MtcCEX: 32-bit platform-specific initialization failed. Status = 0xy Variables y – An error status displayed in hexadecimal Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE when the HP NetServer AA CE Transport experiences an unexpected failure while attempting to perform platform-specific initialization. This error is fatal to CE operations and is followed by a reset of the CE.
Chapter 4 MtcCEX Messages MtcCEX: Could not transition any IOP MIC port to ACTIVE. Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot if the HP NetServer AA CE Transport cannot activate a MIC connection to any IOP. The CE operating system boot terminates. Related Messages MtcCEX: Could not transition IOPx MIC port to ACTIVE.
Chapter 4 MtcCEX Messages MtcCEX: Could not transition IOPx MIC port to DISABLED. Variables x – ID of the IOP associated with the MIC adapter port that failed. Severity Warning Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot when the HP NetServer AA CE Transport cannot disable a MIC adapter port as requested by the IOP during the boot process. The CE Transport attempts to continue the boot process.
Chapter 4 MtcCEX Messages MtcCEX: Expected dual-processor boot, only one processor started. Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot when the HP NetServer AA CE Transport begins initialization. The CE was expected to boot with two processors; however, one of the processors failed to start during Windows NT initialization.
Chapter 4 MtcCEX Messages MtcCEX: Lost communications with boot IOP. Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot if the HP NetServer AA CE Transport loses its communication path to the IOP driving the boot process. The CE operating system boot terminates. Hardware/Software This message indicates a communications failure in the MIC subsystem.
Chapter 4 MtcCEX Messages MtcCEX: MIC adapter malfunction detected. Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot when the HP NetServer AA CE Transport detects an unexpected MIC failure during its startup sequence with the IOP. Hardware/Software This message most likely indicates a hardware failure in the CE MIC. Action • Verify that the CE MIC is properly installed and passes its self-test.
Chapter 4 MtcCEX Messages MtcCEX: Received illegal communication from non-boot IOP. Severity Warning Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot when the HP NetServer AA CE Transport receives a packet from an unexpected IOP. The CE Transport attempts to continue the boot process.
Chapter 4 MtcCEX Messages MtcCEX: Received illegal transport packet. Severity Warning Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot when the HP NetServer AA CE Transport receives an unexpected packet from the IOP. The CE Transport attempts to continue the boot process.
Chapter 4 MtcCEX Messages MtcCEX: Synchronization initialization failed. Status = 0xy Variables y – an error status displayed in hexadecimal Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot when the HP NetServer AA CE Transport experiences an unexpected failure while attempting to perform MtcCEX driver initialization. This error is fatal to CE operations and is followed by a reset of the CE.
Chapter 4 MtcCEX Messages MtcCEX: Unable to complete initialization. Status = 0xy Variables y – an error status displayed in hexadecimal Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot when the HP NetServer AA CE Transport experiences an unexpected failure during its initialization while completing initialization of the MIC adapter and the CE Transport driver. The CE operating system boot terminates.
Chapter 4 MtcCEX Messages MtcCEX: Unable to create device object. Status = 0xy Variables y – an error status displayed in hexadecimal Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot when the HP NetServer AA CE Transport experiences an unexpected failure during its initialization while creating Windows NT data structures. The CE operating system boot terminates.
Chapter 4 MtcCEX Messages MtcCEX: Unable to generate SYSERR packet. Status = 0xy Variables y – an error status displayed in hexadecimal Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE when the HP NetServer AA CE Transport experiences an unexpected failure while preparing to generate a system error. This error is fatal to CE operations and is followed by a reset of the CE.
Chapter 4 MtcCEX Messages MtcCEX: Unable to initialize the MIC adapter. Status = 0xy Variables y – an error status displayed in hexadecimal Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot when the HP NetServer AA CE Transport experiences an unexpected failure during its initialization while initializing the MIC adapter. The CE operating system boot terminates.
Chapter 4 MtcCEX Messages MtcCEX: Unable to register BUGCHECK notification. Status = 0xy Variables y – an error status displayed in hexadecimal Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE during CE operating system boot when the HP NetServer AA CE Transport experiences an unexpected failure during its initialization while attempting to register with Windows NT. The CE operating system boot terminates.
Chapter 4 MtcCEX Messages MtcCEX: Unable to transmit SYSERR packet. Status = 0xy Variables y – an error status displayed in hexadecimal Severity Error Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE when the HP NetServer AA CE Transport experiences an unexpected failure while attempting to transmit a system error to the IOPs. This error is fatal to CE operations and is followed by a reset of the CE.
Chapter 4 88 MtcCEX Messages
5 MtcDgs Messages This chapter lists and describes the HP NetServer AA server MtcDgs messages that are written to the Windows NT Event Log. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: IOPn.MtcDgs Status Message Summary . . . . . . . . . . . . . . . 90 IOPn.MtcDgs Status Messages . . . . . . . . . . . . . . . . . . . .
Chapter 5 MtcDgs Messages IOPn.MtcDgs Status Message Summary The following table lists the HP NetServer AA server MtcDgs messages in the order that they are documented. Table 5-1 IOPn.MtcDgs Status Message Summary Message Page IOPn.MtcDgs status: Datagram Service protocol version mismatch. page 91 IOPn.MtcDgs status: Error accessing data in the Registry. page 91 IOPn.MtcDgs status: Error in NIC bindings. page 91 IOPn.MtcDgs status: Error transferring incoming Ethernet packet to the receive buffer.
Chapter 5 MtcDgs Messages IOPn.MtcDgs Status Messages IOPn.MtcDgs status: Datagram Service protocol version mismatch. Severity Error Description The Datagram Service running on the remote IOP is running a different Datagram Service protocol version. Any received datagrams are discarded. Action • Check the version of the Datagram Service running on the IOPs. • If they are not identical, reinstall the HP NetServer AA software. IOPn.MtcDgs status: Error accessing data in the Registry.
Chapter 5 MtcDgs Messages IOPn.MtcDgs status: Error transferring incoming Ethernet packet to the receive buffer. Severity Warning Description The adapter was unable to copy an Ethernet packet to a receive buffer owned by MtcDgs. The Event Viewer Data section contains the Windows NT (NdisTransferData) (NDIS) error code. The cause of this message is usually that the NIC was reset while a receive was in progress. IOPn.MtcDgs status: Ethernet transmit error.
Chapter 5 MtcDgs Messages IOPn.MtcDgs status: Invalid Ethernet packet received. Severity Warning Description A network adapter provided MtcDgs with an Ethernet packet with a data length greater than 1500 bytes, or with a header length not equal to 14 bytes. The Event Viewer Data section of this message contains the data length. This message can indicate a problem with the NIC. Action You can ignore this message unless it is logged frequently. IOPn.MtcDgs status: Invalid Registry parameter.
Chapter 5 MtcDgs Messages IOPn.MtcDgs status: Send packet allocation failure. Severity Warning Description MtcDgs was unable to allocate an NDIS_PACKET needed to transmit an Ethernet packet. Action You can ignore this message unless it is logged frequently. IOPn.MtcDgs status: Unable to open NIC. Severity Error Description During initialization, the HP NetServer AA Datagram Service opens each NIC that is bound to MtcDgs. This message is reported if one of the NICs could not be opened.
6 MtcDsl Messages This chapter lists and describes the HP NetServer AA server MtcDsl messages that are written to the Windows NT Event Log. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: IOPn.MtcDsl Status Message Summary IOPn.MtcDsl Status Messages . . . . . . . . . . . . . . . 96 . . . . . . . . . . . . . . . . . . . .
Chapter 6 MtcDsl Messages IOPn.MtcDsl Status Message Summary The following table lists the HP NetServer AA server MtcDsl messages in the order that they are documented. Table 6-1 IOPn.MtcDsl Message Summary Message Page IOPn.MtcDsl status: A packet with an invalid transport command was received (offendingValue). page 98 IOPn.MtcDsl status: A provider has an invalid Registry entry (provName). page 98 IOPn.MtcDsl status: A provider has attempted to register more than once (provName). page 98 IOPn.
Chapter 6 MtcDsl Messages Table 6-1 IOPn.MtcDsl Message Summary (Continued) Message Page IOPn.MtcDsl status: Physical device phyDevName of logical device logDevName on IOPx is offline. page 105 IOPn.MtcDsl status: Physical device phyDevName of logical device logDevName on IOPx is online. page 106 IOPn.MtcDsl status: Provider provName experienced an internal failure. page 106 IOPn.MtcDsl status: The IOPs could not be joined because IOP 1 has a different device configuration than IOP 2.
Chapter 6 MtcDsl Messages IOPn.MtcDsl Status Messages IOPn.MtcDsl status: A packet with an invalid transport command was received (offendingValue). Severity Error Description Data traffic between IOPs and CEs is in packet format. A packet was received with an invalid transport command code. Hardware/Software This message indicates an internal HP NetServer AA server software error or an intermittent IOP hardware failure. Action • Reboot the IOP and allow it to rejoin the HP NetServer AA server.
Chapter 6 MtcDsl Messages IOPn.MtcDsl status: A request contained an invalid provider ID (offendingValue). Severity Error Description Providers receive and process device requests. A provider ID indicates the destination provider for a specific request. If a request is received with an invalid provider ID, this message is generated. Related Messages IOPn.MtcDsl status: A request for provider provName used an invalid physical device ID. IOPn.
Chapter 6 MtcDsl Messages IOPn.MtcDsl status: A request for provider provName used an invalid physical device ID. Severity Error Description Providers receive and process device requests. A physical device ID indicates the destination physical device for a particular request. If a request is received with an invalid device ID, an internal software error is indicated. Related Messages IOPn.MtcDsl status: A request for provider provName used an invalid logical device ID. IOPn.
Chapter 6 MtcDsl Messages IOPn.MtcDsl status: An invalid client callback ID was encountered (offendingValue). Severity Error Description The Device Synchronization Layer encountered an unknown callback identifier. Hardware/Software This message indicates an HP NetServer AA server software error or an intermittent IOP hardware failure. Action Reboot the IOP and allow it to rejoin the HP NetServer AA server.
Chapter 6 MtcDsl Messages IOPn.MtcDsl status: An invalid DSL packet ID was encountered (offendingValue). Severity Error Description This message is generated when an unknown packet ID is encountered. Data traffic between IOPs and CEs is in packet format. A packet descriptor goes through multiple levels of checking while in transit between HP NetServer AA server elements. A packet descriptor was corrupted after it was received by a particular IOP.
Chapter 6 MtcDsl Messages IOPn.MtcDsl status: An invalid logical device operation type was encountered (offendingValue). Severity Error Description The Device Synchronization Layer encountered an invalid logical device operation type. Hardware/Software This message indicates an HP NetServer AA server software error or an intermittent IOP hardware failure. Action • Reboot the IOP and allow it to rejoin the HP NetServer AA server.
Chapter 6 MtcDsl Messages IOPn.MtcDsl status: An invalid resync flush state was encountered (offendingValue). Severity Error Description The Device Synchronization Layer encountered an invalid flush state. Hardware/Software This message indicates an HP NetServer AA server software error or an intermittent IOP hardware failure. Action • Reboot the IOP and allow it to rejoin the HP NetServer AA server.
Chapter 6 MtcDsl Messages IOPn.MtcDsl status: Invalid device entries in the IOP’s configuration were pruned. This indicates an improperly set up device configuration. This problem may have occurred due to hand modifications of the Windows NT Registry. The problem may be fixed by re-running the HP NetServer AA Configuration Utility. Severity Error Description The Device Synchronization Layer has detected device configuration entries that are invalid.
Chapter 6 MtcDsl Messages IOPn.MtcDsl status: Physical device phyDevName of logical device logDevName on IOPx is online. Variables x – the ID of the IOP that originated the event Severity Informational Description This message is generated when a previously unavailable device transitions to online. Related Messages IOPn.MtcDsl status: Physical device phyDevName of logical device logDevName on IOPx is offline. IOPn.
Chapter 6 MtcDsl Messages IOPn.MtcDsl status: Unable to allocate a callback descriptor. Severity Error Description The Device Synchronization Layer was unable to allocate memory. This message indicates an operating system resource condition usually related to insufficient memory in the reporting IOP. Related Messages IOPn.MtcDsl status: Unable to allocate callback worker thread. IOPn.MtcDsl status: Unable to initialize DSL.
Chapter 6 MtcDsl Messages IOPn.MtcDsl status: Unable to initialize the DSL. Severity Error Description The Device Synchronization Layer was unable to initialize due to lack of main memory. This message indicates an operating system resource condition usually related to insufficient memory in the reporting IOP. Related Messages IOPn.MtcDsl status: Unable to allocate callback worker thread. IOPn.MtcDsl status: Provider provName experienced an internal failure.
Chapter 6 MtcDsl Messages 109
Chapter 6 110 MtcDsl Messages
7 MtcEthP and MtcEtx Messages This chapter lists and describes the HP NetServer AA server MtcEthP and MtcEtx messages that are written to the Windows NT Event Log. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: IOPn.MtcEthP and IOPn.MtcEtx Message Summary IOPn.MtcEthP Status Messages IOPn.MtcEtx Status Messages . . . . . . . 112 . . . . . . . . . . . . . . . . . . 115 . . . . . . . . . . . . . . . . . . .
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP and IOPn.MtcEtx Message Summary The following table lists the MtcEthP and MtcEtx messages in the order that they are documented. Table 7-1 IOPn.MtcEthP and IOPn.MtcEtx Message Summary Message Page IOPn.MtcEthP status: A call to NdisRequest timed out. page 115 IOPn.MtcEthP status: A call to NdisReset timed out. page 115 IOPn.MtcEthP status: A critical error occurred initializing the Ethernet Provider. page 115 IOPn.
Chapter 7 MtcEthP and MtcEtx Messages Table 7-1 IOPn.MtcEthP and IOPn.MtcEtx Message Summary Message Page IOPn.MtcEthP status: Join response received, but device is not in the joining state. page 125 IOPn.MtcEthP status: NdisRequest returned an error. page 125 IOPn.MtcEthP status: NdisRequest returned an unknown error. page 126 IOPn.MtcEthP status: NdisReset returned an error. page 126 IOPn.MtcEthP status: NdisReset returned an unknown error. page 126 IOPn.
Chapter 7 MtcEthP and MtcEtx Messages Table 7-1 IOPn.MtcEthP and IOPn.MtcEtx Message Summary Message Page IOPn.MtcEtx status: NIC receive data lookahead buffer is too small. page 134 IOPn.MtcEtx status: Receive packet allocation failure. page 134 IOPn.MtcEtx status: Registry parameter mismatch between IOPs. Using default value. page 135 IOPn.MtcEtx status: Send buffer descriptor allocation failure. page 135 IOPn.MtcEtx status: Send packet allocation failure. page 135 IOPn.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP Status Messages IOPn.MtcEthP status: A call to NdisRequest timed out. Severity Warning Description An NdisRequest to set or query the NIC timed out. The Ethernet Provider retries the request several times and may attempt to reset the NIC. If all requests timeout or fail, the NIC will be failed. Action Reboot the IOP to clear the error condition on the NIC. You may want to power cycle the IOP when you reboot it.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: A duplicate address has been detected on device x (y). Variables x – the logical device identifier for this adapter (for example, Ethernet0) y – the Windows NT device name (for example, E100B2) Severity Error Description The local IOP is receiving packets from an IOP other than one that is the opposite member of this HP NetServer AA system.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: An internal state consistency error has been detected on device x (y). Variables x – the logical device identifier for this adapter (for example, Ethernet0) y – the Windows NT device name (for example, E100B2) Severity Error Description Both IOPs claim responsibility for transmitting packets on behalf of the CE.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: Device x (y) network connectivity lost. Variables x – the logical device identifier for this adapter (for example, Ethernet0) y – the Windows NT device name (for example, E100B2) Severity Error Description The Ethernet Provider network monitoring has determined that the device lost network connectivity.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: Error in Ethernet Provider device configuration. Severity Error Description This message is logged during Ethernet Provider initialization if an error is detected in the Ethernet device configuration. Action • Run the HP NetServer AA Configuration Utility and correct the configuration for the adapter. There may be an error in the Ethernet adapter address specified for the logical device.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: Error in Ethernet Provider NIC bindings in the Control Panel. Severity Error Description This message is logged if the Ethernet Provider service is either: not bound to an Ethernet adapter, bound to too many adapters, or bound to an adapter that is not configured. Action Perform the following steps.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: Error resetting Network Interface Controller. Severity Error Description The Ethernet Provider was unable to reset the NIC. The Event Viewer Data section contains the Windows NT (NdisReset) error code. The Ethernet Provider fails the primary device and activates the standby device. Action This is usually a software error that can be corrected by rebooting the IOP.
Chapter 7 See Also MtcEthP and MtcEtx Messages Refer to Chapter 9 in HP NetServer AA Solution Administrator’s Guide for information about how to reboot an IOP. IOPn.MtcEthP status: Ethernet adapter maximum multicast list size mismatch. Severity Error Description This message is logged during IOP joining, when the joining Ethernet Provider receives a join response from the merging Ethernet Provider. The physical Network Interface Controllers that comprise the logical Ethernet device are not identical.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: Ethernet Co-Provider protocol version mismatch. Severity Error Description This message is logged during IOP joining, when the joining Ethernet Provider receives a join response from the merging Ethernet Provider. Incompatible versions of the Ethernet Provider software are running on the IOPs. The joining IOP is not allowed to join the HP NetServer AA server.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: Ethernet transmit error on device x (y) Variables x – the logical device identifier for this adapter (for example, Ethernet0) y – the Windows NT device name (for example, E100B2) Severity Warning Description The Network Interface Controller was unable to transmit an Ethernet packet. Occasional transmit errors can occur, and the packet is retransmitted by a higher level network transport protocol. Related Messages IOPn.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: Invalid Registry parameter. Using default value. Severity Warning Description During initialization, MtcEthP reads optional parameters from the Registry. This message is logged if a parameter is outside the acceptable range. The Event Log Data section contains the invalid parameter value. MtcEthP will use the default value for the parameter.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: NdisRequest returned an unknown error. Severity Error Description An NdisRequest to set or query the NIC failed, and the NIC driver returned an unrecognized or undocumented error code. The Event Log Data section contains the Windows NT error code. This message is logged during MtcEthP initialization or during IOP state transitions. The NIC will be failed. Action • Report the undocumented error code to your service provider.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: Physical Ethernet device has failed. Severity Warning Description This message is logged if an Ethernet Enable command is issued on a failed device. You cannot enable an Ethernet adapter that has failed. Action • Check the Windows NT Event Viewer for messages that indicate the cause of the failure. • If an Ethernet device fails, correct the condition and reboot the IOP.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: The network adapter driver x (y) modifies the source address in outgoing packets to be the current station address. This unsupported behavior prevents this adapter from working in a switched Ethernet environment and may degrade performance.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEthP status: Timeout waiting for report primary message x (y). Variables x – the logical device identifier for this adapter (for example, Ethernet0) y – the Windows NT device name (for example, E100B2) Severity Error Description This message can occur if IOP communication is lost during Ethernet device failover. The IOP that lost network connectivity did not receive a message from the other IOP. The Fault Handler will deconfigure one of the IOPs. IOPn.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEtx Status Messages IOPn.MtcEtx status: Data PDUs have been received out of sequence. Severity Warning Description A Data PDU with the wrong sequence number was received from the remote IOP. This message is logged when the condition first occurs and, thereafter, on every 1000th occurrence. It typically occurs when a network adapter drops an incoming Ethernet packet. The Event Viewer Data section contains the current number of receive out of sequence errors.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEtx status: Error accessing data in the Registry. Severity Error Description During initialization, MtcEtx reads NIC binding information and optional parameter values from the Windows NT Registry. This message is logged if MtcEtx is unable to read the Registry. MtcEtx fails initialization because the NIC binding information is unavailable. Action Run the Network Control Panel application. • Remove the MtcEtx service. • Reboot the IOP.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEtx status: Ethernet transmit error. Severity Warning Description The IL adapter was unable to transmit an Ethernet packet. Occasional transmit errors can occur, and the packet is retransmitted by MtcEtx. A large number of transmit errors can indicate a problem with the adapter or the Ethernet cable. If both IOPs are booted and joined, a disconnected cable or faulty adapter causes MtcEtx to report an error to the Fault Handler.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEtx status: Invalid Ethernet packet received. Severity Warning Description The IL adapter indicated that it received an Ethernet packet with an invalid data length (greater than 1500 bytes), or an invalid header length (not equal to 14 bytes). The Event Viewer Data section contains the length. This message is also logged if MtcEtx detects invalid data in the NIC lookahead buffer.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEtx status: IOP Link driver protocol version mismatch. Severity Error Description MtcEtx includes a protocol version number in the Control PDUs used to establish a virtual circuit. This message is logged if the protocol version on the IOPs does not agree. The Event Log Data section contains the protocol version number contained in the Control PDU. The IOPs cannot join because MtcEtx cannot create a virtual circuit.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEtx status: Registry parameter mismatch between IOPs. Using default value. Severity Warning Description MtcEtx includes the current parameter values in the Control PDUs used to establish a virtual circuit. This message is logged if the parameters on the IOPs do not agree. The Event Log Data section contains the invalid parameter value. MtcEtx will use the default value for the parameter.
Chapter 7 MtcEthP and MtcEtx Messages IOPn.MtcEtx status: Unable to open NIC; initialization aborted. Severity Error Description This message is logged during initialization, when MtcEtx attempts to open the IL adapter. There may be an error in the bindings that were established in the Network Control Panel application. Alternatively, the NIC driver that loads before MtcEtx may have encountered an error that prevented it from initializing the device.
8 MtcEvtP Messages This chapter lists and describes the Endurance server MtcEvtP messages that are written to the Windows NT Event Log. This chapter assumes that you are familiar with Endurance terminology and message conventions. This chapter includes the following sections: IOPn.MtcEvtP Status Message Summary IOPn.MtcEvtP Status Messages . . . . . . . . . . . . . 138 . . . . . . . . . . . . . . . . . .
Chapter 8 MtcEvtP Messages IOPn.MtcEvtP Status Message Summary The following table lists the Endurance server MtcEvtP messages in the order that they are documented. Table 8-1 IOPn.MtcEvtP Status Message Summary Message Page IOPn.MtcEvtP status: An error has occurred that prevented proper initialization of the Event Provider. However, the provider has registered with the provider DLL and therefore is expected to continue even with limited functional capability. page 140 IOPn.
Chapter 8 MtcEvtP Messages Table 8-1 IOPn.MtcEvtP Status Message Summary (Continued) Message Page IOPn.MtcEvtP status: The IOP’s event pipe handle was not obtained. This is an indication that the Registry is not set up correctly. page 142 IOPn.MtcEvtP status: The registration of event pipe logical events failed. This indicates a setup problem with the EVTP subdue under Marathon\Providers in the Registry. page 142 IOPn.
Chapter 8 MtcEvtP Messages IOPn.MtcEvtP Status Messages IOPn.MtcEvtP status: An error has occurred that prevented proper initialization of the Event Provider. However, the provider has registered with the provider DLL and therefore is expected to continue even with limited functional capability. Severity Warning Description This is an internal message. Action If this message is logged, contact your service provider for assistance. IOPn.
Chapter 8 MtcEvtP Messages IOPn.MtcEvtP status: The Event Provider found that an event was posted that had more insertion string data than could fit in the event log packet. Severity Warning Description This warning occurs when additional information was supplied with a message but the information could not be placed into a single event log entry. The information is truncated and logged if possible. IOPn.
Chapter 8 MtcEvtP Messages IOPn.MtcEvtP status: The Event Provider or Endurance System Management Redirector could not create a worker thread for processing events. Severity Error Description The MtcEvtP driver could not initialize properly. Messages may not be logged. IOPn.MtcEvtP status: The Event Provider’s function lookup table is missing a destination flag and cannot complete the request.
Chapter 8 MtcEvtP Messages IOPn.MtcEvtP status: There are no events awaiting delivery to the Endurance System Management Redirector. Severity Error Description The Endurance System Management Redirector driver attempted to read a message from the MtcEvtP driver on the IOP. The IOP did not have a copy of the message. This can occur when a low resource condition is detected on the IOP, and the IOP deleted one or more informational or warning messages to make room for new, higher severity messages.
Chapter 8 144 MtcEvtP Messages
9 MtcFLOP and MtcFLOR Messages This chapter lists and describes the HP NetServer AA server MtcFLOP and MtcFLOR messages that are written to the Windows NT Event Log. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: IOPn.MtcFLOP and MtcFLOR Status Message Summary . . . . . 146 IOPn.MtcFLOP Status Messages . . . . . . . . . . . . . . . . . . 147 MtcFLOR Status Messages . . . . . . . . . . . . . . . . . . . . .
Chapter 9 MtcFLOP and MtcFLOR Messages IOPn.MtcFLOP and MtcFLOR Status Message Summary The following table lists the HP NetServer AA server MtcFLOP and MtcFLOR messages in the order that they are documented. Table 9-1 IOPn.MtcFLOP and IOPn.MtcFLOR Status Message Summary Message Page IOPn.MtcFLOP status: An error has occurred that prevented proper initialization of the Floppy Provider. The provider has registered with the DSL, but may not allow access to the floppy drives. page 147 IOPn.
Chapter 9 MtcFLOP and MtcFLOR Messages IOPn.MtcFLOP Status Messages IOPn.MtcFLOP status: An error has occurred that prevented proper initialization of the Floppy Provider. The provider has registered with the DSL, but may not allow access to the floppy drives. Severity Warning Description An error prevented the HP NetServer AA software from properly initializing. The error was not fatal, but it may prevent floppy devices from being accessible to the CE. Related Messages IOPn.
Chapter 9 MtcFLOP and MtcFLOR Messages IOPn.MtcFLOP status: The Floppy Provider attempted to attach a floppy device to the floppy driver’s device object, but failed. As a result, that floppy device will be inaccessible. Severity Error Description One of the following problems has occurred: Action • The floppy device was not properly defined using the HP NetServer AA Configuration Utility. • The floppy driver could not find any floppy devices. • The floppy driver is not running.
Chapter 9 MtcFLOP and MtcFLOR Messages IOPn.MtcFLOP status: The Floppy Provider attempted to respond to a request, but it was unable to send the reply back to the Redirector. Severity Error Description An internal error has occurred in the HP NetServer AA software. Action Contact your service provider for assistance. IOPn.MtcFLOP status: The Floppy Provider could not register with the DSL. Severity Error Description The Floppy Provider was not able to register with the DSL.
Chapter 9 MtcFLOP and MtcFLOR Messages IOPn.MtcFLOP status: The registration of logical floppy devices failed. In most cases, this indicates a setup problem with the FLOP subkey under Marathon\Providers in the Registry. Severity Error Description The Windows NT Registry does not accurately define the floppy devices on this IOP. The Registry information for floppy devices is automatically supplied, based on the parameters that you supplied using the HP NetServer AA Configuration Utility.
Chapter 9 MtcFLOP and MtcFLOR Messages MtcFLOR Status Messages MtcFLOR status: The Floppy Redirector attempted to create a floppy device, but failed. As a result, that floppy device will be inaccessible. Severity Error Description The floppy device failed initialization. This error usually occurs because the device is not configured properly. Action • Using the HP NetServer AA Configuration Utility, check the configuration information that you supplied for each floppy device.
Chapter 9 152 MtcFLOP and MtcFLOR Messages
10 MtcIopDm Messages This chapter lists and describes the HP NetServer AA server Disk Monitor (MtcIopDm) status messages that are written to the Windows NT event log. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: MtcIopDm Status Message Summary IOPn.MtcIopDm Status Messages . . . . . . . . . . . . . . . 154 . . . . . . . . . . . . . . . . .
Chapter 10 MtcIopDm Messages MtcIopDm Status Message Summary The following table lists the HP NetServer AA server MtcIopDm messages in the order that they are documented. Table 10-1 MtcIopDm Status Message Summary IOPn.MtcIopDm status: Error in the IOP Disk Monitor device configuration. page 155 IOPn.MtcIopDm status: The IOP Disk Monitor failed to attach to any disk drives. page 155 IOPn.MtcIopDm status: The IOP Disk Monitor has attached to \DeviceN\HarddiskN\PartitionN.
Chapter 10 MtcIopDm Messages IOPn.MtcIopDm Status Messages IOPn.MtcIopDm status: Error in the IOP Disk Monitor device configuration. Severity Error Description An error in the device configuration stored in the registry was detected during IOP Disk Monitor initialization. Action • Reinstall the HP NetServer AA IOP software. • Contact your service provider for further assistance. IOPn.MtcIopDm status: The IOP Disk Monitor failed to attach to any disk drives.
Chapter 10 156 MtcIopDm Messages
11 Keyboard and Pointer (MtcKmP) Messages This chapter describes keyboard and pointer messages. Redirector (MtcKmR) messages are logged only on the CE; they are not written to the Windows NT event log and do not have an associated IOPn.Mtc prefix. Provider (MtcKmP) messages use the IOPn.MtcKmP prefix. This chapter assumes that you are familiar with HP NetServer AA terminology. This chapter includes the following sections: Keyboard and Pointer Message Summary Keyboard and Pointer Redirector Messages IOPn.
Chapter 11 Keyboard and Pointer (MtcKmP) Messages Keyboard and Pointer Message Summary The following table lists the HP NetServer AA server keyboard and pointer messages in the order that they are documented. Table 11-1 Keyboard and Pointer Message Summary Message Page A critical error occurred initializing the Keyboard Pointer Redirector. page 160 A non-critical error occurred initializing the Keyboard Pointer Redirector. page 161 Invalid Registry parameter. Using default value.
Chapter 11 Keyboard and Pointer (MtcKmP) Messages Table 11-1 Keyboard and Pointer Message Summary (Continued) Message Page IOPn.MtcKmP status: Unconsumed pointer input discarded. page 168 IOPn.MtcKmP status: Unsupported or invalid 16h Keyboard BIOS request.
Chapter 11 Keyboard and Pointer (MtcKmP) Messages Keyboard and Pointer Redirector Messages A critical error occurred initializing the Keyboard Pointer Redirector. Severity Error Source MtcKmR Description This is a fatal error that causes the Keyboard Pointer Redirector to abort initialization. As a result, keyboard and pointer devices will not be available on the CEs. This message can occur because of: • An error registering with the CE Transport API.
Chapter 11 Keyboard and Pointer (MtcKmP) Messages A non-critical error occurred initializing the Keyboard Pointer Redirector. Severity Warning Source MtcKmR Description This message can occur for the following reasons: • Error creating a symbolic link. • Error writing to the \HARDWARE\DEVICEMAP Registry key. The event log dump data contains an additional Windows NT status code.
Chapter 11 Keyboard and Pointer (MtcKmP) Messages Packet descriptor allocation failure. Severity Error Source MtcKmR Description This is a severe resource error that occurs only if your CE is out of non-paged memory. Under some circumstances, this is a fatal error. Unconsumed keyboard input discarded. Severity Warning Source MtcKmR Description The Keyboard Pointer Redirector provides input to the Keyboard class driver. Normally, the class driver consumes all the input.
Chapter 11 Keyboard and Pointer (MtcKmP) Messages IOPn.MtcKmP Status Messages IOPn.MtcKmP status: A critical error occurred initializing the Keyboard Pointer Provider. Severity Error Description An error occurred in the early stages of initializing the Keyboard/Pointer Provider. The error causes MtcKmP to abort initialization. The IOP will be prevented from joining because the Keyboard/Pointer Provider will not register with the HP NetServer AA Device Synchronization Layer (DSL).
Chapter 11 Keyboard and Pointer (MtcKmP) Messages IOPn.MtcKmP status: Device I/O control error. Severity Error Description This is a generic error indicating that a keyboard or pointer device /IO control request failed.
Chapter 11 Keyboard and Pointer (MtcKmP) Messages IOPn.MtcKmP status: Error setting keyboard typematic rate. Severity Error Description An attempt to set the keyboard typematic rate failed. This error can occur when input is switched between the CEs and the local IOP. Action Unless this error occurs frequently, it can be ignored. Otherwise, view the message data as Words.
Chapter 11 Keyboard and Pointer (MtcKmP) Messages IOPn.MtcKmP status: Keyboard attributes mismatch. Keyboards are not identical. Severity Warning Description During initialization, the Keyboard/Pointer Provider obtains the attributes of the local keyboard. During the IOP join process, the providers compare keyboard attributes to verify that the keyboards are identical. If they are not identical, this message is logged.
Chapter 11 Keyboard and Pointer (MtcKmP) Messages IOPn.MtcKmP status: Pointer attributes mismatch. Pointer devices are not identical. Severity Error Description During initialization, the Keyboard/Pointer Provider obtains the attributes of the local pointer device. During the IOP join process, these providers for each IOP compare the attributes to make sure the pointer devices are identical.
Chapter 11 Keyboard and Pointer (MtcKmP) Messages IOPn.MtcKmP status: Unconsumed pointer input discarded. Severity Warning Description The Keyboard/Pointer Provider provides input to the pointer (mouse) class driver on the IOP. Normally, the class driver consumes all the input. On a very heavily loaded system, or during a system state transition, the class driver may not be able to consume all the input, and the Keyboard/Pointer Provider discards the unconsumed input.
12 MtcMICX Messages This chapter lists and describes the HP NetServer AA server MtcMICX messages that are written to the Windows NT event log. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: IOPn.MtcMICX Message Summary . . . . . . . . . . . . . . . . 170 IOPn.MtcMICX Messages . . . . . . . . . . . . . . . . . . . . .
Chapter 12 MtcMICX Messages IOPn.MtcMICX Message Summary The following table lists the HP NetServer AA server IOPn.MtcMICX messages in the order that they are documented. Table 12-1 IOPn.MtcMICX Message Summary Message Page IOPn.MtcMICX: MtcMICX could not initialize the driver due to an error or resource failure. page 171 IOPn.MtcMICX: MtcMICX detected a non-fatal error during driver initialization. page 176 IOPn.MtcMICX: MtcMICX has detected an unrecoverable error and has shut down operations.
Chapter 12 MtcMICX Messages IOPn.MtcMICX Messages IOPn.MtcMICX: MtcMICX could not initialize the driver due to an error or resource failure. Severity Error Description MtcMICX could not be initialized during startup because it could not obtain a particular resource, or it detected a fatal error. MtcMICX is not loaded, and the IOP cannot join the HP NetServer AA configuration. See the data code table on page 12-173 for a description of the specific errors indicated by the additional data.
Chapter 12 MtcMICX Messages Figure 12-2 shows an example of event detail that indicates the error code in the last word, when viewed as Words. The last word indicating the error code.
Chapter 12 MtcMICX Messages Code Description 01 Small SCSI buffer allocation failure 02 Medium SCSI buffer allocation failure 03 Large SCSI buffer allocation failure 04 Small Ethernet buffer allocation failure 05 Medium Ethernet buffer allocation failure 06 Large Ethernet buffer allocation failure 07 Small general pool buffer allocation failure 08 Medium general pool buffer allocation failure 09 Large general pool buffer allocation failure 0A Double buffer allocation failure 0B Scan
Chapter 12 MtcMICX Messages (Continued) Code Description Action OF IOP ID improperly configured. • Reboot the IOP and enter the BIOS setup program. The IOP ID programmed into the MIC adapter by the MIC BIOS setup program does not match the IOP ID programmed into the HP NetServer AA software. MtcMICX is not loaded, and the IOP cannot join the HP NetServer AA configuration.
Chapter 12 MtcMICX Messages (Continued) Code Description Action 14 Transport registration failed • Reinstall the HP NetServer AA software on the IOP. On startup, MtcMICX attempts to register with the HP NetServer AA Monitor. This message indicates that the registration attempt failed. • If this does not resolve the problem, contact your service provider for assistance. MtcMICX is not loaded, and the IOP cannot join the HP NetServer AA configuration.
Chapter 12 MtcMICX Messages (Continued) Code Description Action 1D Cannot initialize adapter. MtcMICX was not able to initialize the MIC adapter. Refer to the action specified for code 15: Cannot claim resources. Note: The status code returned by the MIC initialization function is also logged as additional data. 1E Cannot translate interrupt vector. HalGetInterruptVector was not able to translate the interrupt vector. Note: The bus number is also logged as additional data.
Chapter 12 MtcMICX Messages IOPn.MtcMICX: MtcMICX resources have not been returned following a port transition. The system will be rebooted to recover. Severity Error Description Required resources were not returned by client software. These resources must be returned before the IOP is allowed to join the configuration. The system will reboot itself to correct the problem. Action No action is required. The HP NetServer AAsoftware automatically reboots the system to correct the problem.
Chapter 12 MtcMICX Messages IOPn.MtcMICX: Port state change not allowed. MtcMICX has not flushed packets from the MIC. Severity Error Description MtcMICX must remove all old packets from the MIC before allowing the IOP to join in the configuration. This probably indicates a hardware error; however, an internal software error can also cause this problem. The additional data specifies the MIC port number where the problem occurred. Action The IOP should reboot automatically.
13 MtcMon Messages This chapter lists and describes the messages that are reported by the Endurance Monitor and are written to the Windows NT event log. These messages include Fault Handler status messages, FRU messages, and Endurance Monitor status messages. This chapter assumes that you are familiar with Endurance terminology and message conventions. This chapter includes the following sections: IOPn.MtcMon Message Summary . . . . . . . . . . . . . . . . . 180 IOPn.MtcMon Fault Handler Status Messages . .
Chapter 13 MtcMon Messages IOPn.MtcMon Message Summary The following table lists the MtcMon messages in the order that they are documented. Table 13-1 IOPn.MtcMon Messages Message Page IOPn.MtcMon Fault Handler status: An error occurred while sending synchronization information to the Fault Handler on the other IOP. page 190 IOPn.MtcMon Fault Handler status: CEx has reported n memory error(s). page 191 IOPn.MtcMon Fault Handler status: CEx has reported n platform error(s). page 192 IOPn.
Chapter 13 MtcMon Messages Table 13-1 IOPn.MtcMon Messages (Continued) Message Page IOPn.MtcMon Fault Handler status: The joining IOP encountered an error or operator action that caused it to shut down before it completed the joining process. page 199 IOPn.MtcMon Fault Handler status: The joining IOP has received a Fault Handler join request from another IOP, but the local IOP state is incorrect. page 200 IOPn.MtcMon FRU: CEx MIC fault. page 201 IOPn.MtcMon FRU: CEx Power supply failure.
Chapter 13 MtcMon Messages Table 13-1 IOPn.MtcMon Messages (Continued) Message Page IOPn.MtcMon FRU: Uncorrectable platform error on CEx page 212 IOPn.MtcMon status: A CE protocol error was detected on IOPx during a CEy remove or disable operation. page 213 IOPn.MtcMon status: A CE protocol error was detected on IOPx during an IOPy remove or disable operation. page 214 IOPn.MtcMon status: A conflict was detected during CE boot with remote IOPx. page 214 IOPn.
Chapter 13 MtcMon Messages Table 13-1 IOPn.MtcMon Messages (Continued) Message Page IOPn.MtcMon status: An error occurred activating IOPx on the active CEs. page 227 IOPn.MtcMon status: An error occurred loading the thresholding database on the joining IOP. IOP initialization and joining will be retried. page 227 IOPn.MtcMon status: An error occurred on IOPx reading the thresholding database during IOP joining. page 228 IOPn.MtcMon status: An invalid BOOT REQUEST packet has been received from CEx.
Chapter 13 MtcMon Messages Table 13-1 IOPn.MtcMon Messages (Continued) Message Page IOPn.MtcMon status: CEx cannot be synchronized because IOPy cannot communicate with it. page 237 IOPn.MtcMon status: CEx cannot be synchronized because not all required ESIs are available. page 238 IOPn.MtcMon status: CEx could not be booted because the boot device is not available on IOPy. page 238 IOPn.
Chapter 13 MtcMon Messages Table 13-1 IOPn.MtcMon Messages (Continued) Message Page IOPn.MtcMon status: Conflicting IOP IDs have been detected in the Endurance system. Local IOP ID = x. Remote IOP ID = y. page 249 IOPn.MtcMon status: Differences in client lists with IOPx were detected during IOP initialization. page 250 IOPn.MtcMon status: Differences with IOPx’s CE platform name were detected during IOP initialization. page 250 IOPx.
Chapter 13 MtcMon Messages Table 13-1 IOPn.MtcMon Messages (Continued) Message Page IOPn.MtcMon status: IOPx is faulted and requires repair. page 261 IOPn.MtcMon status: IOPx is OFFLINE because the /NOMTC switch is present in BOOT.INI. page 261 IOPn.MtcMon status: IOPx is unavailable for initialization. page 262 IOPn.MtcMon status: IOPx is unavailable for initialization because it is currently DISABLED. page 262 IOPn.
Chapter 13 MtcMon Messages Table 13-1 IOPn.MtcMon Messages (Continued) Message Page IOPn.MtcMon status: The CE CPU ID 0xx internal caches do not match. page 273 IOPn.MtcMon status: The CE CPU ID 0xx power-on settings do not match. CE1 CPU power-on settings = 0xy. CE2 CPU power-on settings = 0xz. page 274 IOPn.MtcMon status: The CE CPU ID 0xx speeds do not match. CE1 CPU speed = y MHz CE2 CPU speed = z MHz page 274 IOPn.MtcMon status: The CE CPU ID 0xx versions are not compatible.
Chapter 13 MtcMon Messages Table 13-1 IOPn.MtcMon Messages (Continued) Message Page IOPn.MtcMon status: The CE operating system cannot be synchronized. A debug environment is active. page 282 IOPn.MtcMon status: The CE operating system cannot be synchronized. The CE hardware platform is not supported. page 282 IOPn.MtcMon status: The CE operating system cannot be synchronized. The version of Windows NT on the CE is not supported. page 283 IOPn.
Chapter 13 MtcMon Messages Table 13-1 IOPn.MtcMon Messages (Continued) Message Page IOPn.MtcMon status: The synchronizing CE’s memory size is not equal to the active CE’s memory size. CE1 memory size = y kilobytes. CE2 memory size = z kilobytes. page 291 IOPn.MtcMon status: The Windows NT operating system on the active CE(s) has been shut down by bugcheck. page 291 IOPn.MtcMon status: The Windows NT operating system on the active CE(s) has been shut down due to a system failure.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler Status Messages IOPn.MtcMon Fault Handler status: An error occurred while sending synchronization information to the Fault Handler on the other IOP. Severity Error Description A networking or system resource error occurred while the Fault Handler on the local IOP was attempting to communicate with the Fault Handler on the remote IOP during the join process. This may indicate a problem with the network cards or cabling.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler status: CEx has reported n memory error(s). Variables x – the ID of the CE reporting the errors n – the number of memory errors reported Severity Error Description This error is reported periodically when the CE contains Error Correction Code (ECC) memory and reports either recoverable or non-recoverable memory errors.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler status: CEx has reported n platform error(s). Variables x – the ID of the CE reporting the errors n – the number of platform errors reported Severity Error Description This error is reported periodically when the CE detects correctable or uncorrectable bus or other motherboard faults.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler status: Fault event processing complete. Removed Units: x Variables x – the list of removed components, separated by commas, or "None" if no components were removed Severity Error Description This is the last posted message in a fault handling sequence. It: Related Messages • Separates consecutive fault handling messages in the log • Indicates which components were removed in response to the fault condition IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler status: Fault event processing completed, but there were insufficient system resources to provide a complete event history or log Removed Units. Severity Error Description This is the last posted message in a fault handling sequence. It: • Indicates that there was insufficient memory to record all message details and FRUs associated with the fault message.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler status: Fault event processing completed, but there were insufficient system resources to provide a complete event history. Removed Units: x Variables x – the list of removed components, separated by commas, or "None" if no components were removed Severity Informational Description This is the last posted message in a fault handling sequence. It: • Indicates that the event log does not contain a complete transcript of all fault information.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler status: Fault information log is not open. Severity Error Description The Endurance software was unable to store the most recent fault message information to the MtcFh.hrl file in the config subdirectory of the IOP’s system root because the file could not be opened for writing. This error is not directly related to the fault condition being reported, but it is indicative of a file system error on the reporting IOP. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler status: Insufficient buffer space to retain all Fault Handling error detail; log data is incomplete. Severity Warning Description The fault information written to the MtcFh.hrl file is incomplete because the Fault Handler ran out of memory and could not log all the information. This message occurs if multiple fault messages or repeating fault messages occur immediately after the previous fault message is dismissed.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler status: Removed CEx because of divergence induced by a path error. Variables x – the ID of the CE that was removed Severity Error Description Occasionally, a condition that requires the removal of an IOP can also generate divergence between the CEs.The Endurance software detects this condition and prevents divergence by proactively removing a CE along with the IOP.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler status: The Fault Handlers have failed to exchange synchronization information during the merge process. Severity Error Description The join process between two IOPs failed because either the Fault Handler on the remote IOP rejected the Fault Handler join request sent by this IOP, or because it failed to respond altogether. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon Fault Handler status: The joining IOP has received a Fault Handler join request from another IOP, but the local IOP state is incorrect. Severity Error Description The local IOP received a network packet from another IOP, passing it information required for the local IOP to participate in an active Endurance system. However, the local IOP is already configured as part of an active Endurance system.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU Messages IOPn.MtcMon FRU: CEx MIC fault. Variables x – the ID of the CE with the MIC fault Severity Error Description The MIC adapter on the specified CE is malfunctioning. Usually this indicates that the MIC adapter is neither receiving nor transmitting messages properly and is probably due to a hardware problem with the specified MIC.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: CEx processing capability failure. Variables x – the ID of the CE with the processing capability failure Severity Error Description The ability of the specified CE to function as part of the Endurance server was compromised due to: Action • A system crash or stop error with screen dump. • An inconsistency detected in Endurance server software.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: IOP1 <-> IOP2 interconnect fault. Severity Error Description An unqualified failure has occurred in the communication path between two IOPs. Generally, this is a failure in the IL path. The fault may be caused by: Action • An improperly configured or failed Ethernet adapter • A faulty cable between the adapters • An IOP that is faulted • An IOP that has become hung in a device driver • Check the cabling between the IOPs.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: IOPx MIC fault. Variables x – the ID of the IOP whose MIC is malfunctioning and not receiving or transmitting messages Severity Error Description The MIC adapter on the specified IOP is both malfunctioning and also not receiving or transmitting messages properly. This is probably due to a hardware problem with the specified MIC.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: IOPx <-> CEy cross tuple fault. Variables x – the ID of the IOP experiencing the fault y – the ID of the CE experiencing the fault Because this is a cross-tuple fault, these variables are either: IOP1 and CE2, or IOP2 and CE1. Severity Error Description This message is generated when both the CE and IOP report a fatal condition.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: IOPx <-> CEy interconnect fault. Variables x – the ID of the IOP with the interconnect fault y – the ID of the CE with the interconnect fault Severity Error Description An unqualified failure has occurred in the communications path between the specified IOP and CE. The path includes: the IOPx MIC, the CEy MIC, and the cabling between these components. Action • Check the cabling between the CE and the IOP.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: IOPx/CEy tuple power supply failure. Variables x – the ID of the IOP whose tuple has lost power y – the ID of the CE whose tuple has lost power Severity Error Description All components in the tuple have lost power. Action • Check the power supply connections to the tuple components. • Make sure that the line voltage being supplied to the tuple components is within operational parameters. IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: Local hardware fault on IOPx. Variables x – the ID of the IOP with the hardware error. Severity Error Description A fault was detected on the system disk used by the specified IOP, and the IOP has been removed from service. (Note that usually the IOP reporting the message is not the same as the IOP with the problem, since an IOP with a hardware error is usually unable to report an error to the event log.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: Processing capability failure on unspecified IOP. Severity Error Description An error occurred that originated from an IOP, but the details were not sufficient to determine which IOP caused the condition. Note: The IOP removed as a result of this error may not be the source of the fault. Action • Run diagnostics on each IOP to determine if one of them is faulty.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: The MIC on Compute Element CEx has detected a misconnected cable on its IOPy port, or the CEx MIC has had its ID set incorrectly. Variables x – the ID of the CE that detected the misconnection or has its MIC ID set incorrectly y – the ID of the CE to IOP port that is in error Severity Error Description This condition occurs when the MIC on a booting or synchronizing CE determines that it is not cabled correctly based on its assigned ID.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: Uncorrectable memory error on CEx Variables x – the ID of the CE that has been removed from the Endurance server Severity Error Description The specified CE has Error Correction Code (ECC) memory, and the memory controller has detected but failed to correct one or more double-bit memory errors. This indicates that the system memory has been corrupted, and the CE has been removed. Related Messages IOPn.MtcMon FRU: Uncorrectable platform error on CEx IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon FRU: Uncorrectable platform error on CEx Variables x – the ID of the CE with the uncorrectable platform error Severity Error Description The specified CE has detected an uncorrectable bus or other hardware error on a motherboard component. This indicates that the machine state may have been corrupted, and the CE has been removed. Related Messages IOPn.MtcMon FRU: Uncorrectable memory error on CEx IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon Status Messages IOPn.MtcMon status: A CE protocol error was detected on IOPx during a CEy remove or disable operation. Variables x – the ID of the IOP on which a protocol error was detected y – the ID of the CE that was being removed or disabled when the error was detected Severity Warning Description When using the Endurance Manager to issue a request to remove or disable a CE, the Monitor performs a series of message exchanges between the local IOP and the CE.
Chapter 13 MtcMon Messages IOPn.MtcMon status: A CE protocol error was detected on IOPx during an IOPy remove or disable operation. Variables x – the ID of the IOP on which a protocol error was detected y – the ID of the IOP that was being removed or disabled when the error was detected Severity Warning Description When using the Endurance Manager to issue a request to shut down or disable an IOP, the Monitor performs a series of message exchanges between the local IOP and the CE.
Chapter 13 MtcMon Messages IOPn.MtcMon status: A crash dump is being taken for the Windows NT operating system running on the CEs. Severity Warning Description The Windows NT operating system running on the CE(s) has crashed and is attempting to generate a crash dump. This occurs if you configured Windows NT to generate a crash dump on system failures. Note that all but one active CE is removed from service while the crash dump is being performed. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: A Monitor client failed to complete initialization with the remote IOP during IOP joining. Client ID = x. Variables x – the ID of the client that failed to complete initialization with the remote IOP. The client IDs are: Client ID Client Description Client Image Name 2 Floppy MtcFloP.Sys 4 Serial Provider MtcSerP.Sys 8 Keyboard/Mouse Provider MtcKmP.Sys 10 Endurance Event Provider MtcEvtp.Sys Endurance Device Synchronization MtcDsl.
Chapter 13 MtcMon Messages IOPn.MtcMon status: A Monitor client failed to initialize with the remote IOP during IOP joining. Client ID = x. Variables x – the ID of the client that failed to initialize with the remote IOP. The client IDs are: Client ID Client Description Client Image Name 2 Floppy MtcFloP.Sys 4 Serial Provider MtcSerP.Sys 8 Keyboard/Mouse Provider MtcKmP.Sys 10 Endurance Event Provider MtcEvtp.Sys 11 Endurance Device Synchronization Layer MtcDsl.
Chapter 13 MtcMon Messages IOPn.MtcMon status: A protocol error occurred on IOPx during IOP initialization. Variables x – the ID of the IOP experiencing the protocol error Severity Error Description After an IOP starts up, it attempts to perform an initialization sequence with any remote IOP. A series of control messages are exchanged as part of this process. An illegal message was detected by an IOP during this sequence, or a missing message was detected. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: A protocol error was detected on IOPx during IOP joining. Variables x – the ID of the IOP on which the protocol error was detected Severity Error Description After an IOP completes initialization with a remote IOP, it attempts to join the Endurance server configuration. A series of control messages are exchanged between IOPs as part of this process. An illegal message was detected by an IOP during this sequence, or a missing message was detected.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An Endurance Manager command has been issued to disable IOPx. Variables x – the ID of the IOP to be disabled Severity Warning Description This message is generated as a result of issuing an IOP Disable command. Related Messages IOPn.MtcMon status: IOPx has been disabled by operator request. IOPn.MtcMon status: IOPx has been removed from service. IOPn.MtcMon status: The IOP shutdown or disable operation failed.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An Endurance Manager command has been issued to disable Tuplex. Variables x – the ID of the tuple to be disabled Severity Warning Description This message is generated when a command is issued to disable a tuple. The IOP Monitor attempts to remove the tuple from operation and then set the CE and IOP in the tuple to disabled. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An Endurance Manager command has been issued to remove CEx. Variables x – the ID of the CE to be removed Severity Warning Description This message is generated as a result of issuing a CE Remove command. Related Messages IOPn.MtcMon status: CEx has been removed from service. IOPn.MtcMon status: The CE remove or disable operation failed. Hardware/Software This message is generated as a result of a software operation.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An Endurance Manager command has been issued to shut down Tuplex. Variables x – the ID of the tuple to be shut down Severity Warning Description This message is generated when a command is issued to shut down a tuple. As a result, the IOP Monitor attempts to remove the tuple from operation by resetting or shutting down the CE and then shutting down the IOP. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An Endurance Manager request to shut down or disable IOPx failed because the IOP is active. Variables x – the ID of the IOP that failed to be shut down Severity Warning Description An Endurance Manager request to shut down or remove the remote IOP failed because the remote IOP is active and the local IOP is not. It is not legal to shut down or remove an active IOP from one that is not active. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An Endurance Manager request to shut down the operating system on the CE(s) could not be performed because shutdown is already in progress. Severity Warning Description This message is generated when a command is issued to shut down the CE’s Windows NT operating system and a previous request is still in progress. The initial request continues processing, and any subsequent requests are ignored.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An Endurance Manager request to shut down the operating system on the CE(s) could not be performed because the Endurance System Management Service on the CE(s) is not active. Severity Warning Description This message is generated after issuing a command to shut down the CE’s Windows NT operating system. To perform this operation, the Endurance System Management Service must be active on the CEs.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An error occurred activating IOPx on the active CEs. Variables x – the ID of the IOP that had an error during activation Severity Error Description An error occurred while attempting to join an IOP into an Endurance server that has an active CE. The active IOP was attempting to activate the joining IOP with the CE, and a failure occurred. A problem has occurred with the ESI between the active CE and the joining IOP. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An error occurred on IOPx reading the thresholding database during IOP joining. Variables x – the ID of the IOP that had an error Severity Error Description An error occurred while attempting to read the thresholding database on an active IOP while a remote IOP was joining. This message can be due to either a resource problem, such as a lack of available free pool, or a threshold database corruption error. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An invalid control message was received from IOPx. Variables x – the ID of the IOP that generated an invalid control message Severity Error Description The IOPs frequently exchange messages that are used to monitor and control operations. An IOP received a control message from a remote IOP that was illegal or invalid for the current state of the receiving IOP.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An invalid packet has been received by the Monitor. Packet command = x. Variables x – the transport command type of the received event Severity Error Description This message is generated if an IOP receives a message over the ESI or IL that has a legal transport command type, but is not valid to be received by the IOP. The Fault Handler is invoked, and an IOP or a CE may be removed as a result of this event. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: An unknown packet has been received by the Monitor. Packet command = x. Variables x – the transport command type of the received event Severity Error Description If this message is generated if an IOP receives a message over the ESI or IL that has an illegal transport command type. The Fault Handler is invoked, and an IOP or a CE may be removed as a result of this message. Related Messages IOPn.MtcMon status: IOPx has been removed from service. IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CE boot or synchronization could not be performed because the 16-bit platform-specific initialization module file could not be opened. Severity Error Description The CE’s 16-bit platform-specific initialization module file does not exist. The IOP that generated this message will not be capable of driving the CE Boot or CE synchronization process, although the other IOP may do so. Related Messages IOPn.MtcMon status: The boot process has failed for CEx.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CE operating system shutdown has been requested by the operator. Severity Informational Description This message occurs when a command is issued to shut down the CE’s operating system. The results of the shutdown request are entered in the system event log. Related Messages IOPn.MtcMon status: An Endurance Manager request to shut down the operating system on the CE(s) could not be performed because shutdown is already in progress. IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CE synchronization cannot be performed at this time. Windows NT is not fully loaded. The operation will be retried at a later time. Severity Warning Description Because the Windows NT operating system is not completely loaded on the CE, synchronization cannot be performed. Hardware/Software This message is generated as a result of a software condition that exists in the CE operating system. Action • CE synchronization is retried automatically.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEs are incompatible. The memory sizes do not match. CE1 memory size = y kilobytes. CE2 memory size = z kilobytes. Variables y – the size (in kilobytes) of memory in CE1 z – the size (in kilobytes) of memory in CE2 Severity Error Description The amount of physical memory on the two CEs is different. CE synchronization is not allowed. Hardware/Software This message is generated as a result of a CE hardware configuration error.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx cannot be booted because not all required ESIs are available. Variables x – the ID of the CE that cannot be booted Severity Error Description The CE cannot be booted into the system configuration because a required Endurance System Interconnect (ESI) is not available. Related Messages IOPn.MtcMon status: ESIx is faulted and requires repair. Hardware/Software This message is generated in response to the hardware failure of an ESI.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx cannot be removed because it is already offline. Variables x – the ID of the CE that is offline Severity Warning Description This message is generated if you issue a CE Remove command and the CE is already offline. Hardware/Software This message is generated as a result of a software condition. Action • No action is required. The message indicates that no action was necessary in response to the command. IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx cannot be synchronized because not all required ESIs are available. Variables x – the ID of the CE that cannot be synchronized Severity Error Description The specified CE cannot be synchronized into the system configuration because a required Endurance System Interconnect (ESI) is unavailable. Related Messages IOPn.MtcMon status: ESIx is faulted and requires repair.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx could not be booted because the keyboard boot driver has not registered with the Monitor on IOPy. Variables x – the ID of the CE that could not be booted y – the ID of the IOP on which the driver was not registered Severity Error Description The CE requested to boot the operating system before the Monitor on the IOP received a registration call from the Endurance Keyboard/Mouse Provider driver.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx could not be booted because the SCSI boot driver has not registered with the Monitor on IOPy. Variables x – the ID of the CE that could not be booted y – the ID of the IOP driving the boot process Severity Error Description A CE issued a boot request to an IOP that does not have the Endurance SCSI Provider loaded and active. If both IOPs are active, this message should occur on both simultaneously.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx could not be removed or disabled because it is the only active CE. Shut down the Windows NT operating system on the CEs instead. Variables x – the ID of the CE that could not be removed or disabled Severity Warning Description This message is generated when the CE operating system is active and you issued a CE Remove or CE Disable command without specifying “Operator Override.” As a result, the CE is not removed from service.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx could not be synchronized because the Endurance System Management Service running on the CE operating system is not yet active. Variables x – the ID of the CE that could not be synchronized Severity Warning Description This message is generated during an attempt to synchronize the Windows NT operating system on the CE(s). CE synchronization cannot be performed until the Endurance System Management Service is started on the CE operating system.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx failed to inhibit IPMI global interrupts. Variables x – the ID of the CE that attempted to disable the IPMI interrupts Severity Warning Description Because the IPMI was not found, when the CE software attempted to disable the generation of SMIs though the IPMI, it was unsuccessful. This failure may result in the CEs failure to maintain lockstep operation. This information is logged on the IOP that controls the booting and synchronizing of the CEs.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx has been enabled by operator request. Variables x – the ID of the CE that has been enabled Severity Informational Description The specified CE has been enabled using a CE Enable or Tuple Enable command. The CE had previously been in a faulted or disabled state and is now available for configuration into the Endurance server. Related Messages IOPn.MtcMon status: CEx is faulted and requires repair. IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx has provided platform device information. Chipset: vendor chipset. Memory mode: mode.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx is FAULTED and requires repair. Variables x – the ID of the CE that is faulted Severity Error Description The CE specified in the message has experienced one or more failures that prevent it from being used in the Endurance server configuration. The CE remains in the faulted state until you resolve the situation. Related Messages IOPn.MtcMon status: CEx has been removed from service.
Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx will not be synchronized because the number of processors in use by the CE operating system (y) exceeds the maximum allowed for the current Endurance license.
Chapter 13 MtcMon Messages IOPn.MtcMon status: Client registration failed on the local IOP. Client ID = x. Variables x – the ID of the client that failed the registration process with the Monitor: Client ID Client Description Client Image Name 2 Floppy MtcFloP.Sys 4 Serial Provider MtcSerP.Sys 8 Keyboard/Mouse Provider MtcKmP.Sys 10 Endurance Event Provider MtcEvtp.Sys Endurance Device Synchronization MtcDsl.Sys 11 Layer 12 Endurance Monitor MtcMon.
Chapter 13 MtcMon Messages IOPn.MtcMon status: Conflicting IOP IDs have been detected in the Endurance system. Local IOP ID = x. Remote IOP ID = y. Variables x – the ID of the local IOP y – the ID of the remote IOP Severity Error Description When an IOP is attempting initialization with a remote IOP, the IDs of the IOPs are compared. An IOP detected that its ID is the same as that of the remote IOP. The initializing IOP is marked faulted until you resolve the situation by manual intervention.
Chapter 13 MtcMon Messages IOPn.MtcMon status: Differences in client lists with IOPx were detected during IOP initialization. Variables x – the ID of the remote IOP Severity Error Description When an IOP is attempting initialization with a remote IOP, the lists of clients registered with the Monitor are compared between the two IOPs. A discrepancy was detected between the two lists. The initializing IOP is marked faulted until you resolve the situation by manual intervention. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPx.MtcMon status: Differences with IOPx’s product features were detected during IOP initialization. Variables x – the ID of the remote IOP Severity Error Description The product features are not the same for the two IOPs. The product features were specified during the Endurance installation procedure and are determined from the Endurance license number. IOP joining will not be allowed until this license difference is resolved.
Chapter 13 MtcMon Messages IOPn.MtcMon status: ESIx is faulted and requires repair. Variables x – the ID of the Endurance System Interconnect (ESI) that is faulted Severity Error Description The ESI specified in the message has experienced one or more failures that prevent it from being used in the Endurance server configuration. The ESI remains in the faulted state until you resolve the situation. Often an IOP or CE is also removed when this message occurs. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IL12 is faulted and requires repair. Severity Error Description IL12 had one or more failures resulting in the IL being faulted. (Often an IOP is also removed when the IL is faulted.) The IL remains faulted until you resolve the condition and then enable the IL using an IL12 Enable command. Related Messages IOPn.MtcMon status: IOPx has been removed from service. Hardware/Software This message is usually a result of a hardware failure.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx could not be joined because Interconnect ESIy is unavailable. Variables x – the ID of the IOP that could not be joined y – the ID of the Endurance System Interconnect (ESI) that is unavailable Severity Warning Description This message is generated during IOP join if an Interconnect between the joining IOP and an active CE is faulted. IOP joining is terminated and is not retried until the specified Interconnect is enabled. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx could not be shut down or disabled because one or more CEs are active and the boot device is not online on IOPy. Shut down the Windows NT operating system on the CEs first.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx has been enabled by operator request. Variables x – the ID of the IOP that has been enabled Severity Informational Description The specified IOP was enabled using an IOP Enable Operation or Tuple Enable Operation command. The IOP had previously been in a faulted or disabled state and is now available for configuration into the Endurance server. Related Messages IOPn.MtcMon status: IOPx is faulted and requires repair. IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx has been successfully initialized. Variables x – the ID of the IOP that has been initialized Severity Informational Description The specified IOP successfully completed initialization. The initialization process occurs immediately after the IOP is booted and the Endurance software loads and initializes. Related Messages IOPn.MtcMon status: IOPx has begun the IOP initialization process. Hardware/Software A software process completed.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx has successfully completed the joining process. Variables x – the ID of the IOP that has completed the IOP joining process Severity Informational Description The specified IOP successfully completed the IOP joining process and is now an active part of the Endurance server configuration. The joining process occurs immediately after the IOP is booted, the Endurance software loads and initializes, and IOP initialization is performed.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx initialization failed. Variables x – the ID of the IOP that failed initialization Severity Error Description When an IOP is powered up, it attempts to contact a remote IOP and initialize with it. If the process does not succeed, this message is generated. Related Messages IOPn.MtcMon status: IOPx is faulted and requires repair. IOPn.MtcMon status: Conflicting IOP IDs have been detected in the Endurance System. Local IOP ID = x Remote = y IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx is being removed because MtcMICX credit information is incorrect. Variables x – the ID of the failed IOP Severity Error Description The MIC transport credit information associated with the MIC driver on the specified IOP is invalid. Related Messages IOPn.MtcMon status: The boot process has failed for CEx. IOPn.MtcMon status: The join process has failed for IOPx.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx is faulted and requires repair. Variables x – the ID of the IOP that is faulted Severity Error Description The IOP specified in the message has experienced one or more failures that prevent it from being used in the Endurance server configuration. The IOP remains in the faulted state until you resolve the situation. Related Messages IOPn.MtcMon status: IOPx has been removed from service.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx is unavailable for initialization. Variables x – the ID of the IOP that is unavailable for initialization Severity Warning Description When the Endurance software starts, it attempts to establish communications with the remote IOP if that IOP is not faulted or disabled. The remote IOP did not become available within the Monitor’s IOP initialization timeout interval. This occurs if the remote IOP is powered down or not running the Endurance software.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx is unavailable for initialization because it is currently FAULTED. Variables x – the ID of the IOP that is unavailable for initialization Severity Warning Description This message is generated during IOP initialization when the Endurance software is loaded. The specified IOP is in a faulted state and is not available for configuration into the Endurance server. If the other IOP is not disabled or faulted, the CE is booted when it is powered up.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx was removed at the direction of IOPy. Variables x – the ID of the IOP being removed y – the ID of the IOP that directed the removal Severity Warning Description The specified IOP was removed at the direction of the remote IOP. This message is generated when a transition is occurring in the system and an error was detected on the IOP that was removed. The IOP was removed so the transition could be completed successfully. Related Messages IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx was removed because it failed to activate the CE Interconnect(s). Variables x – the ID of the IOP that was removed Severity Error Description At least one of the Interconnects to the specified IOP could not be activated during CE boot or CE synchronization. To complete booting or synchronization, the specified IOP was removed from service. When this error occurs, it is applied to a threshold.
Chapter 13 MtcMon Messages IOPn.MtcMon status: IOPx was removed from service to allow the CE operating system to be booted. Variables x – the ID of the IOP that was removed Severity Error Description The specified IOP was removed from the Endurance server configuration to allow the CE operating system to boot. This action is taken because the IOP that was removed could not communicate with any of the available CEs; as a result, it was preventing the CE operating system from being booted.
Chapter 13 MtcMon Messages IOPn.MtcMon status: No ECC or parity memory detected on CEx. Chipset: vendor chipset. Memory mode: mode. IPMI found: Y/N Variables x – the ID of the CE that has no ECC or parity memory Y – IPMI was found in CEx N – IPMI was not found in CEx Severity Warning Description The CE software has determined that no ECC or parity memory exists on the CE. The lack of this type of memory increases the risk of the CEs having data corruption or divergence.
Chapter 13 MtcMon Messages IOPn.MtcMon status: Server shutdown has been requested by the operator. Severity Informational Description This message occurs after issuing a command to shut down the Endurance server. The result is: Related Messages • If the operating system on the CEs is running, it is shut down by the Endurance server software. • Each active IOP is shut down. • The Endurance server automatically reboots. IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The active CEs were removed because the boot device is no longer accessible. Severity Error Description The active CE(s) were removed from service because the mirrored SCSI disks that contain the CE’s operating system are no longer available. This implies that both disks in the CE boot disks’s mirror set are either faulted or not available. Because Windows NT cannot run without access to its boot device, the CEs are removed from service.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The boot process has completed for CEx. Variables x – the ID of the booting CE Severity Informational Description The specified CE has successfully completed the boot process and is active in the Endurance server. Related Messages IOPn.MtcMon status: The boot process has begun for CEx. Hardware/Software A software process completed. Action No action is required. IOPn.MtcMon status: The boot process has failed for CEx.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The boot process has failed for CEx because the 16-bit platform initialization did not complete successfully. Variables x – the ID of the booting CE Severity Error Description The specified CE could not be booted because the 16-bit platform initialization process failed. This process is performed via a module uploaded from the IOP and is based on the CE hardware platform specified during IOP installation of the Endurance software.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE BIOS base addresses are not compatible. CE1 BIOS base address = 0xx. CE2 BIOS base address = 0xy. Variables x – the hexadecimal BIOS base address of CE1 y – the hexadecimal BIOS base address of CE2 Severity Error Description The base addresses of the MIC BIOS in the CEs are not compatible. The high order 16 bits of the address must match for the CEs to be compatible.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE CPUx feature sets do not match. CE1 CPU ID register set = 0xy. CE2 CPU ID register set = 0xz. Variables x – the ID of incompatible CPUs y – the CPUx feature set information in CE1 z – the CPUx feature set information in CE2 Severity Error Description The CPU feature set information for CPUx in CEs 1 and 2 is not identical. The CEs cannot be synchronized unless the CPU IDs in each CE match exactly.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE CPU ID 0xx power-on settings do not match. CE1 CPU power-on settings = 0xy. CE2 CPU power-on settings = 0xz. Variables x – the ID of incompatible CPUs y – the CPUx power-on settings in CE1 z – the CPUx power-on settings in CE2 Severity Error Description The CPU power-on settings for CPUx in CEs 1 and 2 are not identical. The CEs cannot be synchronized unless the power-on settings of the same ID CPUs in each CE match exactly.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE CPU ID 0xx versions are not compatible. CE1 CPU version information = 0xy. CE2 CPU version information = 0xz. Variables x – the ID of incompatible CPUs y – the CPUx version information in CE1 z – the CPUx version information in CE2 Severity Error Description The CPU version information for CPUx in CEs 1 and 2 is not identical. The CEs cannot be synchronized unless the versions of the same ID CPUs in each CE match exactly.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE CPUx stepping IDs do not match. CE1 CPU ID register = 0xy. CE2 CPU ID register = 0xz. Variables x – the ID of the incompatible CPUs y – the contents of the Intel Pentium CPU ID register of CE1 z – the contents of the Intel Pentium CPU ID register of CE2 Severity Warning Description The revisions (stepping IDs) of the Intel Pentium processors in the two CEs do not match.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE MIC BIOS setting for PCI parity checking differs between CEs. Severity Error Description The MIC BIOS parameter Parity Checking is not set consistently in CEs 1 and 2. The CEs cannot synchronize unless this parameter matches in both CEs. Hardware/Software The software settable MIC BIOS Parity Checking parameter is set incorrectly on one CE.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE MIC FPGA revisions do not match. CE1 MIC FPGA revision = 0xx. CE2 MIC FPGA revision = 0xy. Variables x – the revision of the MIC module FPGA in CE1 y – the revision of the MIC module FPGA in CE2 Severity Error Description The revisions of the FPGA (Field-Programmable Gate Array) in the CE MICs do not match. The CE MICs must use the same FPGA revision for the CEs to synchronize.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE MIC microcode revisions are not compatible. CE1 MIC microcode revision = 0xx. CE2 MIC microcode revision = 0xy. Variables x – the revision of the MIC module microcode in CE1 y – the revision of the MIC module microcode in CE2 Severity Error Description The revisions of the microcode in the MIC modules in the CEs are not compatible. The major and minor version numbers of the revisions must match exactly for the CEs to synchronize.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE MIC module revisions do not match. CE1 MIC module revision = x. CE2 MIC module revision = y. Variables x – the revision of the MIC module in CE1 y – the revision of the MIC module in CE2 Severity Error Description The revisions of the CE MICs do not match. The CE MICs must be the same revision for the CEs to synchronize. Hardware/Software This message is generated as a result of a hardware configuration error in the CEs.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE MIC PCI device addresses do not match. CE1 PCI address = 0xx. CE2 PCI address = 0xy. Variables x – the PCI device address of the MIC adapter in CE1 y – the PCI device address of the MIC adapter in CE2 Severity Error Description The message indicates that the MIC adapters in the CEs are not assigned identical PCI device addresses. The CEs cannot be synchronized unless the MIC adapter PCI device addresses match exactly.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE operating system cannot be synchronized. Severity Error Description A condition in the Endurance server prevents the CE operating system from being properly synchronized. Hardware/Software This message is generated because a software condition exists in the CE operating system which requires a reboot of the operating system to resolve. Action Additional data in the event log specifies why synchronization cannot be performed.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE operating system cannot be synchronized. The version of Windows NT on the CE is not supported. Severity Error Description An incorrect or unsupported version of Windows NT is running on the CE. This version or service pack is preventing the CE operating system from synchronizing. Hardware/Software This message is generated because a software condition exists in the CE operating system which requires a reboot of the operating system to resolve.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The CE operating system shutdown request completed successfully. Severity Informational Description This message is generated after successfully completing a CE_O/S Shutdown Operation command. Related Messages IOPn.MtcMon status: CE operating system shutdown has been requested by the operator. IOPn.MtcMon status: The Windows NT operating system on the CE(s) is being shut down. IOPn.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The Ethernet Transport driver (MtcEtx) has not yet registered with the Monitor. Severity Warning Description When the Endurance server initializes, the Monitor waits for all transport drivers to register before allowing the IOP to begin operations. The Ethernet Transport driver (MtcEtx.sys) has not successfully loaded and registered with the Monitor within the IOP startup interval (two minutes).
Chapter 13 MtcMon Messages IOPn.MtcMon status: The memory sizes of the CEs do not match. CE1 memory size = y kilobytes. CE2 memory size = z kilobytes. Variables y – the size (in kilobytes) of memory in CE1 z – the size (in kilobytes) of memory in CE2 Severity Warning Description The amount of physical memory on the two CEs is different. If the CE with the larger amount of memory is booted first, the CE with the smaller memory size is not allowed to synchronize.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The Monitor is waiting for all required interconnects to become available. Severity Error Description When the Endurance server initializes, the Monitor waits for all transport and datagram drivers to register before allowing the IOP to begin operations. The drivers have registered with the Monitor, but did not provide paths to all remote elements in the system as expected.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The number of CE CPU processors does not match. CE1 CPU count = x. CE2 CPU count = y. Variables x – the number of CPUs in CE1 y – the number of CPUs in CE1 Severity Error Description The number of CPUs in CE1 does not match the number of CPUs in CE2. The CEs cannot be synchronized unless the number of CPUs in each CE matches exactly. Hardware/Software This message is generated as a result of a hardware configuration error in the CEs.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The number of processors in use by CE operating system (x) exceeds the maximum allowed for the current Endurance license. CE synchronization will be prohibited. Variables x – the number of processors in use by the CE operating system Severity Warning Description The number of processors in use by the CE executing the operating system exceeds the number allowed by the Endurance software installed in the IOP.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The synchronizing CE’s memory size is greater than the active CE’s memory size. CE1 memory size = y kilobytes. CE2 memory size = z kilobytes. Variables y – the size (in kilobytes) of memory in CE1 z – the size (in kilobytes) of memory in CE2 Severity Warning Description The amount of physical memory on the synchronizing CE is greater than the amount of memory on the active CE. Synchronization is not prevented in this situation.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The synchronizing CE’s memory size is not equal to the active CE’s memory size. CE1 memory size = y kilobytes. CE2 memory size = z kilobytes. Variables y – the size (in kilobytes) of memory in CE1 z – the size (in kilobytes) of memory in CE2 Severity Error Description The physical memory sizes of the two CEs are different. CE synchronization cannot be performed until this condition is resolved.
Chapter 13 MtcMon Messages IOPn.MtcMon status: The Windows NT operating system on the active CE(s) has been shut down due to a system failure. Severity Error Description This message indicates that the Windows NT operating system running on the CE was shut down due to a system failure that resulted in the removal of the last CE executing the operating system. Note that in this scenario, the CE operating system did not perform an orderly and graceful system shutdown. Related Messages IOPn.
14 MtcScsiP and MtcScsiR Messages This chapter lists and describes the SCSI subsystem messages that are written to the Windows NT event log. These messages include SCSI Provider (MtcScsiP) and SCSI Redirector (MtcScsiR) status messages. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: MtcScsiP and MtcScsiR Status Message Summary . . . . . . . . 294 IOPn.MtcScsiP Status Messages . . . . . . . . . . . . . . . .
Chapter 14 MtcScsiP and MtcScsiR Messages MtcScsiP and MtcScsiR Status Message Summary Table 14-1 lists the MtcScsiP and MtcScsiR status messages in the order that they are documented. Table 14-1 MtcScsiP and MtcScsiR Status Message Summary Message Page IOPn.MtcScsiP status: Administrator is attempting to disable bad block remapping for DISKn. page 302 IOPn.MtcScsiP status: Administrator is attempting to enable bad block remapping for DISKn. page 302 IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages Table 14-1 MtcScsiP and MtcScsiR Status Message Summary (Continued) Message Page IOPn.MtcScsiP status: Cannot obtain SCSI mode page data for DISKn. This is typical for RAID controllers. page 307 IOPn.MtcScsiP status: Cannot obtain SCSI read-write recovery mode page data for DISKn. This is typical for RAID controllers. page 307 IOPn.MtcScsiP status: CDROMn may not be SCSI-2 (or newer SCSI standard) compliant. page 308 IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages Table 14-1 MtcScsiP and MtcScsiR Status Message Summary (Continued) Message Page IOPn.MtcScsiP status: Disk could not be enabled. page 313 IOPn.MtcScsiP status: Disk is a mirror copy target. Status is offline pending copy start. page 314 IOPn.MtcScsiP status: Disk is already disabled. page 314 IOPn.MtcScsiP status: Disk is already online. page 314 IOPn.MtcScsiP status: Disk must be offline. page 314 IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages Table 14-1 MtcScsiP and MtcScsiR Status Message Summary (Continued) Message Page IOPn.MtcScsiP status: DISKn had an invalid HP NetServer AA partition checksum. Try using the HP NetServer AA Manager to reset the HP NetServer AA partition. page 321 IOPn.MtcScsiP status: DISKn had its HP NetServer AA partition reset. page 321 IOPn.MtcScsiP status: DISKn has a different mirror set ID for each of its member disks.
Chapter 14 MtcScsiP and MtcScsiR Messages Table 14-1 MtcScsiP and MtcScsiR Status Message Summary (Continued) Message Page IOPn.MtcScsiP status: DISKn has had SCSI tagged queuing disabled. This disk type may have exhibited problems with SCSI tagged queuing. This feature is disabled to prevent corruption problems. page 327 IOPn.MtcScsiP status: DISKn has had write cache disabled. This disk type may have exhibited problems with write cache. This feature is disabled to prevent corruption problems.
Chapter 14 MtcScsiP and MtcScsiR Messages Table 14-1 MtcScsiP and MtcScsiR Status Message Summary (Continued) Message Page IOPn.MtcScsiP status: Failed class library setup for DISKn, and it will be marked offline. page 333 IOPn.MtcScsiP status: Failed to reset the HP NetServer AA partition. page 333 IOPn.MtcScsiP status: Failed to reset the HP NetServer AA partition for DISKn.
Chapter 14 MtcScsiP and MtcScsiR Messages Table 14-1 MtcScsiP and MtcScsiR Status Message Summary (Continued) Message Page IOPn.MtcScsiP status: The administrator disabled DISKn. The device must be manually enabled, using HP NetServer AA Manager, before it can be used. page 340 IOPn.MtcScsiP status: The administrator is attempting to disable DISKn. page 340 IOPn.MtcScsiP status: The administrator is attempting to enable DISKn. page 341 IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages Table 14-1 MtcScsiP and MtcScsiR Status Message Summary (Continued) Message Page IOPn.MtcScsiP status: Unable to read one or more sectors SECTORn – SECTORm for DISKx. Note: The read request did not come from the CEs. page 346 IOPn.MtcScsiP status: Unable to read the HP NetServer AA partition for DISKn. Try using the HP NetServer AA Manager to reset the HP NetServer AA partition. page 347 IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP Status Messages IOPn.MtcScsiP status: Administrator is attempting to disable bad block remapping for DISKn. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Warning Description The administrator is attempting to disable bad block remapping for the specified disk. Action No action is required. IOPn.MtcScsiP status: Administrator is attempting to enable bad block remapping for DISKn.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: An internal HP NetServer AA software error occurred during join. Contact your service provider for assistance. Severity Error Description An unexpected error occurred in HP NetServer AA software. Action Contact your service provider for assistance. IOPn.MtcScsiP status: An unrecoverable CE boot disk read error occurred during the BIOS phase of boot. The disk will be marked faulted.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Attempt to restart mirror copy for DISKn has failed. Cannot access target disk for mirror copy. Check prior events for details. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description HP NetServer AA SCSI software was unable to restart a mirror copy as requested by the administrator. Action Check the event log for previous messages that indicate why the mirror copy could not be restarted.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Bad block remapping is already turned off for the DISKn mirror set. HP NetServer AA Manager request to turn off bad block remapping was ignored. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description The administrator attempted to disable bad block remapping. However, bad block remapping was already disabled, so the operation was ignored. Action No action is required. IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Cannot access disk for requested operation. Severity Error Description The administrator attempted an operation using the HP NetServer AA Manager. However, the disk cannot be accessed for the desired operation. Action Check the event log for previous messages that indicate why the disk is not accessible for the desired operation. IOPn.MtcScsiP status: Cannot access DISKn for requested operation. Check prior events for details.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Cannot obtain geometry data for DISKn, and it will be marked offline. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description The SCSI Provider was unable to get required size characteristics from the disk controller. The disk will not be usable until the problem is corrected. Action Make sure the disk drive is present and turned on.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Cannot obtain SCSI read-write recovery mode page data for DISKn. This is typical for RAID controllers. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Informational Description The SCSI Provider requests SCSI read-write recovery mode page data from disk controllers. SCSI read-write recovery mode page data contains disk characteristics and configuration information.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Command to DISKn not valid because it is a non-mirrored disk. HP NetServer AA Manager request to non-mirrored disk was ignored. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description The administrator used HP NetServer AA Manager to issue a disk operation command to a non-mirrored disk. The operation is not allowed on a non-mirrored disk, and it has been rejected. Action No action is required. IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Configured ADAPTERx has different initiator IDs for bus BUSn. Use the BIOS setup program available via your SCSI adapter to reconfigure the initiator ID. The IOPs will not be allowed to join until this problem is resolved.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Device DISKn will be faulted because it is taking too long to complete SCSI requests. The IOP must be rebooted before the disk can be enabled. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description A disk has not completed pending SCSI requests in an appropriate time period. This typically occurs as a disk begins to fail.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DEVICEn has a SCSI logical unit number (LUN) different than configured on the other IOP, and it will be marked offline. Variables n – the device number; for example, DISKn, CDROMn, TAPEn Severity Error Description A configured logical unit number (LUN) for the device on the local IOP does not match the configured logical unit number for the device on the remote IOP.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DEVICEn location does not contain the expected device type. Variables n – the device number; for example, DISKn, CDROMn, TAPEn Error Description A device located at a configured SCSI address was not the expected device type. For example, the software may have been configured to expect a disk drive at a particular SCSI address, but instead, it encountered a CDROM drive.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Disk is a mirror copy target. Status is offline pending copy start. Severity Success Description The specified disk was selected as a mirror copy target disk. It will remain offline until a copy starts. Action No action is required. IOPn.MtcScsiP status: Disk is already disabled. Severity Error Description The administrator attempted to disable the specified disk. However, the disk was already disabled, so the operation was ignored.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn cannot be accessed for initialization, and it will be marked offline. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description A disk cannot be accessed for initialization. Check the event log for prior related messages. The problem should be corrected as indicated by these prior messages.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn contains too few partitions. Use Disk Administrator in Offline HP NetServer AA I/O Processor Mode to partition the disk, making sure to add an HP NetServer AA partition. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description All disks in an HP NetServer AA configuration must have two or more partitions: one partition to contain user data, and another partition to contain HP NetServer AA data.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn did not come ready, and it will be marked offline. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description The reported disk was found, but it did not come ready for use. Action • Make sure the disk is turned on. • If the disk is powered on, reboot the IOP that contains the disk, and break into the SCSI adapter's BIOS configuration program.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn does not have a bootable partition. Use Disk Administrator in Offline HP NetServer AA I/O Processor Mode to mark the desired boot partition as active. The disk will be kept offline until it contains a partition marked as bootable.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn encountered a bad block at SECTOR during a mirror copy. Variables n – the disk number; for example, DISK0, DISK1, DISK2 SECTOR – the sector number of the sector containing the bad block Severity Error Description The source disk of a mirror copy encountered a bad block. Action Make a note of the bad block for later diagnostic purposes. IOPn.MtcScsiP status: DISKn encountered a write error during a mirror copy.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn failed a SCSI request, and repeated retries did not succeed. The disk will be marked faulted. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description The SCSI Provider encountered a bad spot while reading one or more sectors from a CE disk. Action If the CE disk mirror set is current, then a failover to the correctly functioning disk will occur automatically.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn had an invalid HP NetServer AA partition checksum. Try using the HP NetServer AA Manager to reset the HP NetServer AA partition. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description The HP NetServer AA sector was deemed invalid because of an invalid checksum. The disk will not be allowed to go online until the HP NetServer AA partition for the disk has been reset.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn has a different number of bytes per sector for each of its member disks. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description The disk must have the same number of bytes per sector as its mirror set peer, but it does not. Action Most disks come factory set at 512 bytes per physical sector. Contact your disk drive vendor for information about your drives.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn has an HP NetServer AA partition that is not at the end of the disk. Use Disk Administrator in Offline HP NetServer AA I/O Processor Mode to repartition the HP NetServer AA partition, making sure to position it at the end of the disk.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn has an HP NetServer AA system ID other than the current system ID. This indicates DISKn has come from a completely different HP NetServer AA system. The HP NetServer AA partition can be reset to cure this condition, but caution is advised. If unsure how to proceed, contact your service provider for assistance.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn has an invalid partition signature. Use Disk Administrator in Offline HP NetServer AA I/O Processor Mode to partition the disk, making sure to add an HP NetServer AA partition. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description The disk does not have a valid partition table. It must be partitioned and formatted. Action Repartition the disk.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn has established an advertised sector count of SECTOR_COUNT sectors. Variables n – the disk number; for example, DISK0, DISK1, DISK2 SECTOR_COUNT – the count of sectors in decimal Severity Informational Description When two disks that are not the same size are initially joined, the size of the smaller disk dictates the advertised size of the larger disk. This message reports on the agreed upon advertised disk size.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn has had SCSI tagged queuing disabled. This disk type may have exhibited problems with SCSI tagged queuing. This feature is disabled to prevent corruption problems. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Warning Description Some disk controllers may exhibit problems when certain SCSI features are used.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn has write cache disabled by default. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Informational Description The SCSI disk controller has write cache disabled by default. This may have undesirable performance consequences. Unless the disk controller has had problems using write cache, Marathon recommends that the write cache feature be enabled.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn is not partitioned. Use Disk Administrator in Offline HP NetServer AA I/O Processor Mode to partition the disk, making sure to add an HP NetServer AA partition. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description All disks used in an HP NetServer AA configuration must be partitioned. The disk specified in the message was not partitioned. Action Repartition the disk.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn mirror set is up to date. (This message may occur during IOP join, when both CEs are down, or whenever a disk is enabled.) Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Informational Description Whenever IOPs join together, the CEs go down, or a disk is enabled, HP NetServer AA SCSI software will examine all disk states to determine if a mirror copy is required.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: DISKn was unable to use remapped sector SECTOR during a mirror copy. The disk may need replacement. Variables n – the disk number; for example, DISK0, DISK1, DISK2 SECTOR – the sector number of the remapped sector. Severity Error Description During a mirror set copy, the source disk encountered a bad block. The software remapped the bad block, and then attempted to use the remapped area, but the attempt failed.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: HP NetServer AA partition is already valid, or disk cannot be accessed for resetting. Severity Error Description The administrator attempted to reset the specified disk’s HP NetServer AA partition using the HP NetServer AA Manager. However, the sector is already valid or the disk cannot be accessed for an HP NetServer AA partition reset. Action If the disk is online, then the HP NetServer AA sector did not require resetting.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: HP NetServer AA partition on DISKn is out of date and will be updated. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Informational Description An outdated HP NetServer AA partition can be a normal part of a new HP NetServer AA software installation. It signifies an HP NetServer AA partition format or content change over the previous revision of HP NetServer AA software. Action No action is required. IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Failed to reset the HP NetServer AA partition for DISKn. The local IOP was unable to access the disk to reset the HP NetServer AA partition, or the disk did not have access to become a copy target. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description The administrator attempted to reset the specified disk's HP NetServer AA partition using the HP NetServer AA Manager, but the reset failed.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Mirror copy could not be restarted. Severity Error Description HP NetServer AA SCSI software was unable to restart a mirror copy as requested by the administrator. Action Review the event log, looking for previous messages that indicate why the mirror copy could not be restarted.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Mirror set copy from IOPn to IOPn for DISKx has halted due to a copy read failure from local IOP’s DISKn. Variables n – the IOP number; either IOP1 or IOP2 x – the disk number; for example, DISK0, DISK1, DISK2 Severity Warning Description A mirror copy for the specified disk has halted because the mirror copy source disk experienced a read error while trying to read copy data.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Mirror set copy from IOPn to IOPn for DISKx has halted. The local IOP lost access to DISKn. Variables n – the IOP number; either IOP1 or IOP2 x – the disk number; for example, DISK0, DISK1, DISK2 Severity Warning Description This message occurs only during mirror copies, and it can be caused by a variety of conditions. Check the event log for previous messages relating to the state of the specified disk.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Mirror set copy from IOPn to IOPn for DISKx is complete. Variables n – the IOP number; either IOP1 or IOP2 x – the disk number; for example, DISK0, DISK1, DISK2 Severity Informational Description A mirror copy from the specified IOP for the specified disk is complete. The mirror set is now considered current because the mirror copy source disk and the mirror copy target disk contain identical data. Action No action is required. IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Registry update thread did not start. Contact your service provider for assistance. Severity Error Description The SCSI Provider is experiencing an unexpected error condition. This is most likely the result of the IOP’s operating system experiencing problems. Action • Rebooting the IOP may correct the problem. • Reinstall HP NetServer AA software on IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: SCSI Provider on IOP1 is incompatible with the SCSI Provider on IOP2. Severity Error Description The SCSI Provider on IOP1 is incompatible with the SCSI provider on IOP2. This may be the result of improper installation of IOP HP NetServer AA software on either or both IOPs. It may also be the result of improper installation of HP NetServer AA software patches. Action • Power off the CEs.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: The administrator is attempting to enable DISKn. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Informational Description The administrator is attempting to enable the specified disk using the HP NetServer AA Manager. Action No action is required. IOPn.MtcScsiP status: The DISKn copy target has too few sectors to support a copy from its mirror set peer. The copy target must be replaced with a larger disk.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: The SCSI Redirector and the SCSI Provider are incompatible. Severity Error Description The SCSI Redirector and the SCSI Provider have incompatible version numbers. This may be the result of improper installation of the CE or IOP HP NetServer AA software. It may also be the result of improper installation of HP NetServer AA software hotfixes. Action • Power off the CEs. • Reboot each IOP into Offline HP NetServer AA I/O Processor Mode.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Unable to flush cache for DISKn. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description HP NetServer AA software must occasionally flush the write cache for disk controllers, which support write cache. However, HP NetServer AA software was unable to flush write cache for the specified disk. A mirrored disk set with inconsistent data between each member disk may exist, although this is unlikely.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Unable to locate detected bad block for DISKn during mirror copy. Retrying read operation. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Warning Description Whenever the presence of a bad block is detected, it will be localized down to a specific sector. However, if the error was transient, it may be impossible to identify because the error will not recur.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Unable to read and process the HP NetServer AA partition of DISKn, and it will be marked offline. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description A fatal disk error occurred which prevents HP NetServer AA disk subsystem software from reading and processing the MTC sector of a disk. Action • Review the event log, looking for any previous message that may explain why this message occurred.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Unable to read one or more sectors SECTORn – SECTORm for DISKx. Note: The read request did not come from the CEs. Variables x – the disk number; for example, DISK0, DISK1, DISK2 SECTORn – the starting sector in the range of sectors SECTORm – the ending sector in the range of sectors Severity Error Description HP NetServer AA software executing on the IOPs issues background read requests to disks that are redirected to the CEs.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Unable to read the HP NetServer AA partition for DISKn. Try using the HP NetServer AA Manager to reset the HP NetServer AA partition. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description The HP NetServer AA disk software was unable to read the HP NetServer AA sector for the specified disk. Action • Use the HP NetServer AA Manager to reset the HP NetServer AA partition on the disk.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Unable to remap bad block at SECTOR for DISKn during a mirror copy. Variables n – the disk number; for example, DISK0, DISK1, DISK2 SECTOR – the sector number of the sector unable to be remapped Severity Error Description During a mirror set copy, the source disk encountered a bad block. The software attempted to remap the bad block, but the attempt failed.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Unable to restart a mirror copy for DISKn because its copy has not failed. HP NetServer AA Manager request to restart the mirror copy was ignored. Variables n – the disk number; for example, DISK0, DISK1, DISK2 Severity Error Description An attempt was made to use the HP NetServer AA Manager to restart a mirror copy that has not failed. This is not allowed. Action No action is required. IOPn.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Unable to write one or more CE requested sectors SECTORn - SECTORm for DISKn. If DISKn stays online, this error may be considered transient. Many transient errors may indicate the need for disk replacement.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiP status: Unable to write one or more sectors SECTORn – SECTORm for DISKn. Note: the write request did not come from the CEs. Variables n – the disk number; for example, DISK0, DISK1, DISK2 SECTORn – the starting sector in the range of sectors SECTORm – the ending sector in the range of sectors Severity Error Description HP NetServer AA SCSI software executing on the IOPs issues background write requests to disks that are redirected to the CEs.
Chapter 14 MtcScsiP and MtcScsiR Messages IOPn.MtcScsiR Status Message IOPn.MtcScsiR status: A non-critical error occurred initializing the SCSI Redirector. Some devices may not be available. Description When the SCSI Redirector was initializing, a non-critical error occurred, probably due to some devices not being available. Note: This message is logged only in the CE event log. Severity Warning Action This message usually indicates a resource error.
15 MtcSmR Messages This chapter lists and describes the HP NetServer AA server MtcSmR Status messages that are written to the Windows NT event log. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: IOPn.MtcSmR Status Message Summary IOPn.MtcSmR Status Messages . . . . . . . . . . . . . 354 . . . . . . . . . . . . . . . . . .
Chapter 15 MtcSmR Messages IOPn.MtcSmR Status Message Summary The following table lists the HP NetServer AA server IOPn.MtcSmR messages in the order that they are documented. Table 15-1 IOPn.MtcSmR Status Message Summary Message Page IOPn.MtcSmR status: The HP NetServer AA System Management Redirector failed to obtain some or all of the memory required for unsolicited buffers for events from the Event Provider. Attempting to continue to provide HP NetServer AA System Management control functions.
Chapter 15 MtcSmR Messages IOPn.MtcSmR Status Messages IOPn.MtcSmR status: The HP NetServer AA System Management Redirector failed to obtain some or all of the memory required for unsolicited buffers for events from the Event Provider. Attempting to continue to provide HP NetServer AA System Management control functions. The ability to log HP NetServer AA events on the CE may be partially or fully impaired. Any event generated at this time will only be logged on the IOP that generated the event.
Chapter 15 MtcSmR Messages IOPn.MtcSmR status: The HP NetServer AA System Management Redirector received an invalid sync-up response from the Event Provider. Attempting to continue to provide HP NetServer AA System Management control functions. No HP NetServer AA events will be logged to the CE. Any event generated at this time will only be logged on the IOP that generated the event. Severity Warning Description This is an internal message. If this message is logged, contact your service provider.
16 MtcVidP Messages This chapter lists and describes the HP NetServer AA server Video Provider (MtcVidP) status messages that are written to the Windows NT event log. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: MtcVidP Status Message Summary IOPn.MtcVidP Status Messages . . . . . . . . . . . . . . . . 358 . . . . . . . . . . . . . . . . . .
Chapter 16 MtcVidP Messages MtcVidP Status Message Summary The following table lists the HP NetServer AA server MtcVidP messages in the order that they are documented. Table 16-1 MtcVidP Status Message Summary Message Page IOPn.MtcVidP status: A critical error occurred initializing the Video Provider. page 359 IOPn.MtcVidP status: Error in Video Provider device configuration. page 359 IOPn.MtcVidP status: Invalid Registry parameter. Using default value. page 359 IOPn.
Chapter 16 MtcVidP Messages IOPn.MtcVidP Status Messages IOPn.MtcVidP status: A critical error occurred initializing the Video Provider. Severity Error Description This message is logged if an error is returned by a Windows NT system routine during the early stages of MtcVidP initialization. The Event Log Data section contains the Windows NT error code. Action Contact your service provider for assistance. IOPn.MtcVidP status: Error in Video Provider device configuration.
Chapter 16 MtcVidP Messages IOPn.MtcVidP status: Join response received, but Provider is not in the joining state. Severity Error Description An IOP join response was received, but joining is no longer in progress. A previous join request may have timed out, or there is an error in the Video Provider joining protocol. Action Contact your service provider for assistance. IOPn.MtcVidP status: Protocol version mismatch between the Video Provider and the Keyboard Pointer Provider.
Chapter 16 MtcVidP Messages IOPn.MtcVidP status: Video Co-Provider protocol version mismatch. Severity Error Description This message occurs during IOP joining, when the joining Video Provider receives a join response from the merging Video Provider. It indicates that incompatible versions of the Video Provider software are running on the IOPs. The joining IOP is not allowed to join the HP NetServer AA server.
Chapter 16 362 MtcVidP Messages
17 MtcVnP Messages This chapter lists and describes the HP NetServer AA server MtcVnP status messages that are written to the Windows NT Event Log. This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions. This chapter includes the following sections: IOPn.MtcVnP Status Message Summary . . . . . . . . . . . . . . 364 IOPn.MtcVnP Status Messages . . . . . . . . . . . . . . . . . . .
Chapter 17 MtcVnP Messages IOPn.MtcVnP Status Message Summary Table 17-1 lists the HP NetServer AA server IOPn.MtcVnP status messages in the order that they are documented. Table 17-1 IOPn.MtcVnP Status Message Summary Message Page IOPn.MtcVnP status: Error in Virtual Network Provider device configuration. page 365 IOPn.MtcVnP status: Error writing to the Registry. page 365 IOPn.MtcVnP status: Invalid Registry parameter. Using default value. page 365 IOPn.
Chapter 17 MtcVnP Messages IOPn.MtcVnP Status Messages IOPn.MtcVnP status: Error in Virtual Network Provider device configuration. Severity Error Description This event is logged during Virtual Network Provider initialization if an error is detected in the Virtual Network device configuration. Action If reported following a software upgrade, reapply the upgrade to the IOPs. Contact your service provider for assistance. IOPn.MtcVnP status: Error writing to the Registry.
Chapter 17 MtcVnP Messages IOPn.MtcVnP status: Join response received, but Provider is not in the joining state. Severity Error Description An IOP join response was received, but joining is no longer in progress. A previous join may have timed out, or there is an error in the Virtual Network joining protocol. Action Contact your service provider for assistance. IOPn.MtcVnP status: More than one instance of the Virtual Network Provider was installed in the control panel.
Chapter 17 MtcVnP Messages IOPn.MtcVnP status: Virtual Network Redirector-Provider protocol version mismatch. Severity Error Description This occurs during CE boot, when the Virtual Network Redirector notifies the Virtual Network Provider that it is initializing. It indicates that incompatible versions of the Virtual Network Redirector and Provider software are running on the CE and IOPs.
Chapter 17 368 MtcVnP Messages
18 Endurance Manager Messages This chapter describes the messages that can be reported during use of the Endurance Manager. These messages are not written to the Windows NT event log. This chapter assumes that you are familiar with Endurance terminology. This chapter includes the following sections: Types of Messages . . . . . . . . . . . . . . . . . . . . . . . . . 370 Endurance Manager Message Summary . . . . . . . . . . . . . . 370 Endurance Manager Messages . . . . . . . . . . . . . . . . . . .
Chapter 18 Endurance Manager Messages Types of Messages Two types of messages can occur when you use the Endurance Manager: • Messages that indicate fatal errors and are displayed in a pop-up window • Non-fatal informational messages that are reported to the Endurance Manager’s GUI display If you receive a message that is not documented, or if you need help interpreting a message, contact your service provider.
Chapter 18 Endurance Manager Messages Table 18-1 Endurance Manager Messages (Continued) Message Page A provider entry in the MTCSMAPI.DLL contains incorrect data. page 373 A provider entry in the MTCSMAPI.DLL contains incorrect target data. page 374 A required parameter is missing. page 374 An action entry in the MTCSMAPI.DLL contains incorrect data. page 374 An enumeration entry in the MTCSMAPI.DLL contains incorrect data.
Chapter 18 Endurance Manager Messages Endurance Manager Messages Messages Indicating Fatal Errors The following messages indicate fatal errors that cause the Endurance Manager to terminate automatically. These messages display in a pop-up window. When one of these messages displays on your terminal, click OK to acknowledge the message and dismiss the window. The Endurance Manager terminates immediately. Note: If you are unable to restore the Endurance Manager, contact your service provider.
Chapter 18 Endurance Manager Messages Retrieval library thread initialization failed. A resource allocation error occurred during the creation of a thread. Retrieval library thread is unavailable. A thread was disabled due to the premature closing of the retrieval library. Retrieval library was not initialized. A retrieval call was attempted before the library was initialized. General Informational Messages The following messages display information about the Endurance server and the Endurance Manager.
Chapter 18 Endurance Manager Messages A provider entry in the MTCSMAPI.DLL contains incorrect target data. Reinstall the Endurance Manager software. If the problem persists, contact your service provider for assistance. A required parameter is missing. The command requires a parameter that was not supplied. Refer to Chapter 5 in HP NetServer AA Solution Administrator’s Guide or the online help for specific information about the missing parameter. An action entry in the MTCSMAPI.
Chapter 18 Endurance Manager Messages Could not perform request. An invalid action was specified. An invalid action keyword was specified. Refer to Chapter 5 in HP NetServer AA Solution Administrator’s Guide or the online help for specific information about valid actions. Could not perform request. An invalid CE was specified. An invalid CE was specified. Refer to Chapter 5 in HP NetServer AA Solution Administrator’s Guide or the online help for specific information. Could not perform request.
Chapter 18 Endurance Manager Messages One or more fields from the request cannot be displayed. The MTCSMAPI.DLL may contain missing or incorrect data. Reinstall the Endurance Manager software. If the problem persists, contact your service provider for assistance. Operator override is required. You attempted to execute a command that, if applied, may affect the availability of the server or its resources.
