Page 1 HP NetServer AA Solution Messages HP Part Number 5969-5966 Printed in September 2000...
Page 2 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.
Page 3: Table Of Contents
Contents Preface Chapter 1 — Introduction Examining the Windows NT Event Log ..... 3 HP NetServer AA Messages......4 Format of HP NetServer AA Messages .
Page 4 Contents IOPn.MtcDsl Status Messages......98 Chapter 7 — MtcEthP and MtcEtx Messages IOPn.MtcEthP and IOPn.MtcEtx Message Summary ... . . 112 IOPn.MtcEthP Status Messages .
Page 5 Contents Chapter 14 — MtcScsiP and MtcScsiR Messages MtcScsiP and MtcScsiR Status Message Summary....294 IOPn.MtcScsiP Status Messages ..... . . 302 IOPn.MtcScsiR Status Message .
Page 6 Contents...
Page 7 Tables Event Log Icons and Severity Levels ......5 Message Reporting Source....... 7 Message Variables .
Page 8 Tables viii...
Page 9: Preface
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   , as well as all users of HP NetServer AA and software, including Microsoft Windows NT servers.
Page 10 Preface Conventions The following conventions are used in the HP NetServer AA documentation set: Convention Description Indicates a variable that you replace in a path name or command Italics, Courier font Bold, Courier Indicates actions or commands that you must type. For example, type A:\ETX font Courier font...
Page 11: Chapter 1 - Introduction
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 •...
Page 12: Examining The Windows Nt Event Log
Chapter 1 Introduction This chapter contains the following sections: Examining the Windows NT Event Log ....3 HP NetServer AA Messages ..... . 4 Format of HP NetServer AA Messages .
Page 13: Examining The Windows Nt Event Log
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.
Page 14: Hp Netserver Aa Messages
Chapter 1 Introduction HP NetServer AA Messages When it is operational, HP NetServer AA software continuously monitors the HP NetServer AA server. It reports all status and error messages in a variety of ways: • By logging them to the Windows NT Event log •...
Page 15: Format Of Hp Netserver Aa Messages
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.
Page 16: Hp Netserver Aa Message Categories And Conventions
Chapter 1 Introduction When troubleshooting an HP NetServer AA server, check the event logs for HP NetServer AA messages that start with 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.
Page 17: Message Reporting Sources
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 Chapter 9 FloR MtcFloR status Floppy Redirector messages MtcBIOS None MIC BIOS messages, displayed during the...
Page 18: Message Variables
Chapter 1 Introduction Table 1-2Message Reporting Source (Continued) Reporting Source Message Prefix Reports . . . Refer to Chapter 13 MtcMon IOPn.MtcMon Fault HP NetServer AA system control messages Handler status IOPn.MtcMon FRU IOPn.MtcMon status MtcScsiP IOPn.MtcScsiP status SCSI Provider messages Chapter 14 Chapter 14 MtcScsiR...
Page 19: Message Summary
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;...
Page 20 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 21 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 22 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 23 Chapter 1 Introduction Table 1-4HP NetServer AA Message Summary – Unprefixed Messages (Continued) Message Page Platform initialization failed page 56 Press <Enter> or Control-M for MIC setup. Press <Esc> to bypass initialization. page 56 Reboot Required: The system must be rebooted for changes to take effect. Press <Esc> to page 56 bypass automatic reboot or any other key to reboot.
Page 24 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 25 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 page 103...
Page 26 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 27 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 page 128 outgoing packets to be the current station address.
Page 28 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 29 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 page 147 Floppy Provider. The provider has registered with the DSL, but may not allow access to the floppy drives.
Page 30 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 page 167 Provider.
Page 31 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 page 193 insufficient system resources to provide a complete event history. Removed Units: x IOPn.MtcMon Fault Handler status: Fault event processing completed, but there were page 194 insufficient system resources to provide a complete event history.
Page 32 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 page 206...
Page 33 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 page 218 operating system was being attempted. 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 34 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 page 231 command = x. IOPn.MtcMon status: CE boot failed because the Monitor’s ConfigurationArcTree Registry page 231 entry on IOPx is invalid.
Page 35 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 page 240 registered with the Monitor on IOPy. IOPn.MtcMon status: CEx could not be removed or disabled because CE synchronization is page 240 currently in progress.
Page 36 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 37 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 page 263 FAULTED. IOPn.MtcMon status: IOPx joining has been aborted because the thresholding database was page 263 modified.
Page 38 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 page 274 power-on settings = 0xy. CE2 CPU power-on settings = 0xz. IOPn.MtcMon status: The CE CPU ID 0xx speeds do not match.
Page 39 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 page 282 environment is active. IOPn.MtcMon status: The CE operating system cannot be synchronized. The CE hardware page 282 platform is not supported.
Page 40 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 page 290 in use by Windows NT. Windows NT memory size = y kilobytes. CEx memory size = z kilobytes.
Page 41 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 page 306 details. IOPn.MtcScsiP status: Cannot disable write cache for DISKn. This disk type may have page 306 exhibited problems with write cache.
Page 42 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 page 312 configured on the other IOP, and it will be marked offline. IOPn.MtcScsiP status: DEVICEn has a target ID different than configured on the other IOP, page 312 and it will be marked offline.
Page 43 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 page 318 recoverable read requests. IOPn.MtcScsiP status: DISKn does not support automatic bad block remapping for write page 318 requests.
Page 44 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 page 325 Offline HP NetServer AA I/O Processor Mode to partition the disk, making sure to add an HP NetServer AA partition.
Page 45 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 page 330 join, when both CEs are down, or whenever a disk is enabled.) IOPn.MtcScsiP status: DISKn must be offline.
Page 46 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 page 336 copy write failure to local IOP’s DISKn. IOPn.MtcScsiP status: Mirror set copy from IOPn to IOPn for DISKx has halted.
Page 47 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 page 342 Configuration Utility to add a boot disk or mark an existing disk as bootable. IOPn.MtcScsiP status: Unable to flush cache for DISKn.
Page 48 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 - page 350 SECTORm for DISKn. If DISKn stays online, this error may be considered transient. Many transient errors may indicate the need for disk replacement.
Page 49 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 page 360...
Page 50 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 51 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 page 151 Floppy Provider. As a result, the floppy devices will be inaccessible. MtcFLOR status: The registration of MtcFloR with the CE Transport failed.
Page 52 Chapter 1 Introduction...
Page 53: Chapter 2 - Mic Bios Messages
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.
Page 54: Types Of Messages
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.
Page 55: Mic Bios Message Summary
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 56 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...
Page 57: Mic Bios Messages
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.
Page 58 Chapter 2 MIC BIOS Messages Confirm: Changes made to MIC settings have not been saved. Press <Esc> to return to setup; press <Enter> 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.
Page 59 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.
Page 60 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.
Page 61 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.
Page 62 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: •...
Page 63 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.
Page 64 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.
Page 65 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.
Page 66 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.
Page 67 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 •...
Page 68 Chapter 2 MIC BIOS Messages Test mode may be canceled by pressing <Esc>. Severity Informational Description During the execution of a test, it is possible to press <Esc> to cancel the test and return the element to use in an HP NetServer AA configuration. Action No action is required.
Page 69 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.
Page 70 Chapter 2 MIC BIOS Messages...
Page 71: Chapter 3 - Installation And Verification Procedure (Ivp) Messages
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.
Page 72: Types Of Message
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.
Page 73: Ivp Message Summary
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 74: Ivp Messages
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...
Page 75 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.
Page 76 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.
Page 77 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.
Page 78 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.
Page 79: Chapter 4 - Mtccex Messages
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.
Page 80: Mtccex Message Summary
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 page 73 initialization failed.
Page 81 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.
Page 82: Mtccex Messages
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. Severity Error Description...
Page 83 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.
Page 84 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.
Page 85 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.
Page 86 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.
Page 87 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.
Page 88 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.
Page 89 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.
Page 90 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.
Page 91 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.
Page 92 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.
Page 93 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.
Page 94 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.
Page 95 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.
Page 96 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.
Page 97 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.
Page 98 Chapter 4 MtcCEX Messages...
Page 99: Chapter 5 - Mtcdgs 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 .
Page 100: Iopn.mtcdgs Status Message Summary
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 101: Iopn.mtcdgs Status Messages
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. •...
Page 102 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.
Page 103 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.
Page 104 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...
Page 105: Chapter 6 - Mtcdsl Messages
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 .
Page 106: Iopn.mtcdsl Status Message Summary
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 107 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 108: Iopn.mtcdsl Status Messages
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.
Page 109 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.
Page 110 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.
Page 111 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.
Page 112 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.
Page 113 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.
Page 114 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.
Page 115 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...
Page 116 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.
Page 117 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.
Page 118 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.
Page 119 Chapter 6 MtcDsl Messages...
Page 120 Chapter 6 MtcDsl Messages...
Page 121 7 MtcEthP and MtcEtx Mes- sages 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 .
Page 122: Chapter 7 - Mtcethp And Mtcetx Messages
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 123 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 124 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 125: Iopn.mtcethp Status Messages
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.
Page 126 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...
Page 127 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...
Page 128 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.
Page 129 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.
Page 130 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.
Page 131 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.
Page 132 Chapter 7 MtcEthP and MtcEtx Messages See Also Refer to Chapter 9 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.
Page 133 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.
Page 134 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.
Page 135 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.
Page 136 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.
Page 137 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 •...
Page 138 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. Variables x –...
Page 139 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.
Page 140: Iopn.mtcetx Status Messages
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.
Page 141 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.
Page 142 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.
Page 143 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.
Page 144 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.
Page 145 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.
Page 146 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.
Page 147: Chapter 8 - Mtcevtp Messages
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 .
Page 148: Iopn.mtcevtp Status Message Summary
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. page 140 However, the provider has registered with the provider DLL and therefore is expected to continue even with limited functional capability.
Page 149 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 page 142 Registry is not set up correctly. IOPn.MtcEvtP status: The registration of event pipe logical events failed. This indicates a setup page 142 problem with the EVTP subdue under Marathon\Providers in the Registry.
Page 150: Iopn.mtcevtp Status Messages
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.
Page 151 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.
Page 152 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.
Page 153 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.
Page 154 Chapter 8 MtcEvtP Messages...
Page 155 9 MtcFLOP and MtcFLOR Mes- sages 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 .
Page 156: Chapter 9 - Mtcflop And Mtcflor 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...
Page 157: Iopn.mtcflop Status Messages
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.
Page 158 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: •...
Page 159 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.
Page 160 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.
Page 161: Mtcflor Status Messages
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.
Page 162 Chapter 9 MtcFLOP and MtcFLOR Messages...
Page 163: Chapter 10 - Mtciopdm 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 .
Page 164: Mtciopdm Status Message Summary
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 165: Iopn.mtciopdm Status Messages
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. •...
Page 166 Chapter 10 MtcIopDm Messages...
Page 167: Chapter 11 - Keyboard And Pointer (Mtckmp) 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.
Page 168: Keyboard And Pointer Message Summary
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 169 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. page 168...
Page 170: Keyboard And Pointer Redirector Messages
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.
Page 171 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.
Page 172 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.
Page 173: Iopn.mtckmp Status Messages
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).
Page 174 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. It can occur during MtcKmP initialization when attempting to perform one of the following operations: •...
Page 175 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.
Page 176 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.
Page 177 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.
Page 178 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.
Page 179: Chapter 12 - Mtcmicx Messages
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 .
Page 180: Iopn.mtcmicx Message Summary
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 181: Iopn.mtcmicx Messages
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.
Page 182 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. Figure 12-2 Example of MICX Event Detail Viewed as Words...
Page 183 Chapter 12 MtcMICX Messages Code Description Action Small SCSI buffer allocation failure For status codes 01 - 0B and 20 -24, inclusive, increase the memory size of the IOP. Medium SCSI buffer allocation failure Large SCSI buffer allocation failure Small Ethernet buffer allocation failure Medium Ethernet buffer allocation failure...
Page 184 Chapter 12 MtcMICX Messages (Continued) Code Description Action IOP ID improperly configured. • Reboot the IOP and enter the BIOS setup program. The IOP ID programmed into the MIC • Modify the IOP ID so that it matches the IOP ID that adapter by the MIC BIOS setup was specified when the HP NetServer AA software was program does not match the IOP ID...
Page 185 Chapter 12 MtcMICX Messages (Continued) Code Description Action Transport registration failed • Reinstall the HP NetServer AA software on the IOP. On startup, MtcMICX attempts to • If this does not resolve the problem, contact your service register with the HP NetServer AA provider for assistance.
Page 186 Chapter 12 MtcMICX Messages (Continued) Code Description Action Cannot initialize adapter. MtcMICX Refer to the action specified for code 15: was not able to initialize the MIC Cannot claim resources. adapter. Note: The status code returned by the MIC initialization function is also logged as additional data.
Page 187 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.
Page 188 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.
Page 189: Chapter 13 - Mtcmon Messages
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.
Page 190: Iopn.mtcmon Message Summary
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 page 190 the Fault Handler on the other IOP.
Page 191 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 page 199 caused it to shut down before it completed the joining process. IOPn.MtcMon Fault Handler status: The joining IOP has received a Fault Handler join request from page 200 another IOP, but the local IOP state is incorrect.
Page 192 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 page 213 operation. IOPn.MtcMon status: A CE protocol error was detected on IOPx during an IOPy remove or disable page 214 operation.
Page 193 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 page 227 initialization and joining will be retried.
Page 194 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 195 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 page 249 = x. Remote IOP ID = y. 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 page 250...
Page 196 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 197 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 page 274 settings = 0xy.
Page 198 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 page 282 active. IOPn.MtcMon status: The CE operating system cannot be synchronized. The CE hardware platform is page 282 not supported.
Page 199 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 page 291 size. CE1 memory size = y kilobytes. CE2 memory size = z kilobytes. IOPn.MtcMon status: The Windows NT operating system on the active CE(s) has been shut down by page 291 bugcheck.
Page 200: Iopn.mtcmon Fault Handler Status Messages
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.
Page 201 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.
Page 202 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.
Page 203 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: •...
Page 204 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: •...
Page 205 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...
Page 206 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.
Page 207 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.
Page 208 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.
Page 209 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.
Page 210 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.
Page 211: Iopn.mtcmon Fru Messages
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.
Page 212 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: •...
Page 213 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: •...
Page 214 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.
Page 215 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...
Page 216 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.
Page 217 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 •...
Page 218 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.
Page 219 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 •...
Page 220 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 –...
Page 221 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.
Page 222 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.
Page 223: Iopn.mtcmon Status Messages
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...
Page 224 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...
Page 225 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.
Page 226 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...
Page 227 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...
Page 228 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.
Page 229 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.
Page 230 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.
Page 231 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.
Page 232 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.
Page 233 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.
Page 234 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.
Page 235 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.
Page 236 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.
Page 237 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.
Page 238 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.
Page 239 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.
Page 240 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.
Page 241 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.
Page 242 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.
Page 243 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...
Page 244 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.
Page 245 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...
Page 246 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.
Page 247 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.
Page 248 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.
Page 249 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...
Page 250 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...
Page 251 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...
Page 252 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...
Page 253 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.
Page 254 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.
Page 255 Chapter 13 MtcMon Messages IOPn.MtcMon status: CEx has provided platform device information. Chipset: vendor chipset. Memory mode: mode. IPMI found: Y/N Variables x – the CE for which platform device information is detected vendor chipset – the vendor of the chipset in CEx mode –...
Page 256 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.
Page 257 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. Variables x – the ID of the CE that is attempting to synchronize y –...
Page 258 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 Floppy MtcFloP.Sys Serial Provider...
Page 259 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...
Page 260 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.
Page 261 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.
Page 262 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.
Page 263 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.
Page 264 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...
Page 265 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. Variables x –...
Page 266 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.
Page 267 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.
Page 268 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.
Page 269 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.
Page 270 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.
Page 271 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.
Page 272 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.
Page 273 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.
Page 274 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.
Page 275 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.
Page 276 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.
Page 277 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 –...
Page 278 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: • If the operating system on the CEs is running, it is shut down by the Endurance server software.
Page 279 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.
Page 280 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.
Page 281 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.
Page 282 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...
Page 283 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 –...
Page 284 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 –...
Page 285 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 –...
Page 286 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 –...
Page 287 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 is not set consistently in CEs 1 and 2. The CEs Parity Checking cannot synchronize unless this parameter matches in both CEs. Hardware/Software The software settable MIC BIOS parameter is set incorrectly on one CE.
Page 288 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...
Page 289 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...
Page 290 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...
Page 291 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...
Page 292 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.
Page 293 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.
Page 294 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.
Page 295 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).
Page 296 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...
Page 297 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.
Page 298 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...
Page 299 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...
Page 300 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 –...
Page 301 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 –...
Page 302 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.
Page 303: Mtcscsip And Mtcscsir Status Message Summary
14 MtcScsiP and MtcScsiR Mes- sages 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.
Page 304: Chapter 14 - Mtcscsip And Mtcscsir 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 305 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 page 307 controllers. IOPn.MtcScsiP status: Cannot obtain SCSI read-write recovery mode page data for DISKn. This is page 307 typical for RAID controllers.
Page 306 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 307 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 page 321 NetServer AA Manager to reset the HP NetServer AA partition. IOPn.MtcScsiP status: DISKn had its HP NetServer AA partition reset.
Page 308 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 page 327 exhibited problems with SCSI tagged queuing. This feature is disabled to prevent corruption problems.
Page 309 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.
Page 310 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, page 340 using HP NetServer AA Manager, before it can be used. IOPn.MtcScsiP status: The administrator is attempting to disable DISKn.
Page 311 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: page 346 The read request did not come from the CEs. IOPn.MtcScsiP status: Unable to read the HP NetServer AA partition for DISKn.
Page 312: Iopn.mtcscsip Status Messages
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.
Page 313 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.
Page 314 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...
Page 315 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...
Page 316 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.
Page 317 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.
Page 318 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.
Page 319 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...
Page 320 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.
Page 321 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...
Page 322 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...
Page 323 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.
Page 324 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.
Page 325 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.
Page 326 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...
Page 327 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 •...
Page 328 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.
Page 329 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...
Page 330 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.
Page 331 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...
Page 332 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.
Page 333 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.
Page 334 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.
Page 335 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...
Page 336 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.
Page 337 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...
Page 338 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.
Page 339 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...
Page 340 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...
Page 341 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...
Page 342 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.
Page 343 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.
Page 344 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 –...
Page 345 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.
Page 346 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...
Page 347 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...
Page 348 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.
Page 349 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 •...
Page 350 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.
Page 351 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.
Page 352 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.
Page 353 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.
Page 354 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.
Page 355 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.
Page 356 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 –...
Page 357 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...
Page 358 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...
Page 359 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...
Page 360 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.
Page 361 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 –...
Page 362: Iopn.mtcscsir Status Message
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.
Page 363: Chapter 15 - Mtcsmr Messages
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 .
Page 364: Iopn.mtcsmr Status Message Summary
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 page 355 or all of the memory required for unsolicited buffers for events from the Event Provider.
Page 365: Iopn.mtcsmr Status Messages
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.
Page 366 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.
Page 367: Chapter 16 - Mtcvidp Messages
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 .
Page 368: Mtcvidp Status Message Summary
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 369: Iopn.mtcvidp Status Messages
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.
Page 370 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.
Page 371 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.
Page 372 Chapter 16 MtcVidP Messages...
Page 373: Chapter 17 - Mtcvnp 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 .
Page 374: Iopn.mtcvnp Status Message Summary
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 375: Iopn.mtcvnp Status Messages
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.
Page 376 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.
Page 377 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.
Page 378 Chapter 17 MtcVnP Messages...
Page 379 18 Endurance Manager Mes- sages 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 .
Page 380: Types Of 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.
Page 381 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 382: Endurance Manager Messages
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.
Page 383 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.
Page 384 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 HP NetServer AA Solution Administrator’s Guide...
Page 385 Chapter 18 Endurance Manager Messages Could not perform request. An invalid action was specified. An invalid action keyword was specified. Refer to Chapter 5 HP NetServer AA Solution Administrator’s Guide or the online help for specific information about valid actions. Could not perform request.
Page 386 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.

This manual is also suitable for:

Netserver aa 6200

HP NetServer AA 4000 Manual

Preface

Chapter 1 - Introduction

Chapter 2 - MIC BIOS Messages

Chapter 3 - Installation and Verification Procedure (IVP) Messages

Chapter 4 - Mtccex Messages

Chapter 5 - Mtcdgs Messages

Chapter 6 - Mtcdsl Messages

Chapter 7 - Mtcethp and Mtcetx Messages

Chapter 8 - Mtcevtp Messages

Chapter 9 - Mtcflop and Mtcflor Messages

Chapter 10 - Mtciopdm Messages

Chapter 11 - Keyboard and Pointer (Mtckmp) Messages

Chapter 12 - Mtcmicx Messages

Chapter 13 - Mtcmon Messages

Chapter 14 - Mtcscsip and Mtcscsir Messages

Chapter 15 - Mtcsmr Messages

Chapter 16 - Mtcvidp Messages

Chapter 17 - Mtcvnp Messages

Chapter 18 - Endurance Manager Messages

Quick Links

Related Manuals for HP NetServer AA 4000

Summary of Contents for HP NetServer AA 4000

This manual is also suitable for:

Table of Contents