HP NetServer AA 4000 Manual Download | Manualshive

Page: 31 / 386

background image

21

Chapter 1

Introduction

IOPn.MtcMon Fault Handler status: Fault event processing completed, but there were
insufficient system resources to provide a complete event history. Removed Units: x

page 193

IOPn.MtcMon Fault Handler status: Fault event processing completed, but there were
insufficient system resources to provide a complete event history. Removed Units: x

page 194

IOPn.MtcMon Fault Handler status: Fault information dump.

page 195

IOPn.MtcMon Fault Handler status: Fault information log is not open.

page 196

IOPn.MtcMon Fault Handler status: Insufficient buffer space to retain all Fault Handling
error detail; log data is incomplete.

page 197

IOPn.MtcMon Fault Handler status: Received a bad Fault Handler control packet.

page 197

IOPn.MtcMon Fault Handler status: Removed CEx because of divergence induced by a path
error.

page 198

IOPn.MtcMon Fault Handler status: The Fault Handler received a packet from another IOP
that is not a member of this Endurance system. This may mean that you have multiple
Endurance systems on your network with the same Endurance Kit Number. This problem
should be corrected immediately; otherwise, you may lose network packets or encounter
network connectivity problems.

page 198

IOPn.MtcMon Fault Handler status: The Fault Handlers have failed to exchange
synchronization information during the merge process.

page 199

IOPn.MtcMon Fault Handler status: The joining IOP encountered an error or operator
action that caused it to shut down before it completed the joining process.

page 199

IOPn.MtcMon Fault Handler status: The joining IOP has received a Fault Handler join
request from another IOP, but the local IOP state is incorrect.

page 200

IOPn.MtcMon FRU: CEx MIC fault.

page 201

IOPn.MtcMon FRU: CEx Power supply failure.

page 201

IOPn.MtcMon FRU: CEx processing capability failure.

page 202

IOPn.MtcMon FRU: IOP operating system or subcomponent failure.

page 202

IOPn.MtcMon FRU: IOP1 <-> IOP2 interconnect fault.

page 203

IOPn.MtcMon FRU: IOP1 or IOP2 processing capability failure or data set divergence.

page 203

IOPn.MtcMon FRU: IOPx MIC fault.

page 204

IOPn.MtcMon FRU: IOPx Power supply failure.

page 204

Table 1-5HP NetServer AA Message Summary – Prefixed Messages (Continued)

Message

Page

«
...
29
30
31
32
33
...
»

Summary of Contents for NetServer AA 4000

Page 1: ...HP NetServer AA Solution Messages HP Part Number 5969 5966 Printed in September 2000 ...

Page 2: ...yright All rights are reserved No part of this document may be photocopied reproduced or translated to another language without the prior written consent of Hewlett Packard Company TRADEMARK NOTICE Assured Availability ComputeThru Computing for the long run Constant Computing Endurance Marathon Assured MIAL SplitSite and the Marathon logo are either registered trademarks or trademarks of Marathon ...

Page 3: ...mmary 9 Chapter 2 MIC BIOS Messages Types of Messages 44 MIC BIOS Message Summary 45 MIC BIOS Messages 47 Chapter 3 Installation and Verification Procedure IVP Messages Types of Message 62 IVP Message Summary 63 IVP Messages 64 Chapter 4 MtcCEX Messages MtcCEX Message Summary 70 MtcCEX Messages 72 Chapter 5 MtcDgs Messages IOPn MtcDgs Status Message Summary 90 IOPn MtcDgs Status Messages 91 Chapte...

Page 4: ... 146 IOPn MtcFLOP Status Messages 147 MtcFLOR Status Messages 151 Chapter 10 MtcIopDm Messages MtcIopDm Status Message Summary 154 IOPn MtcIopDm Status Messages 155 Chapter 11 Keyboard and Pointer MtcKmP Messages Keyboard and Pointer Message Summary 158 Keyboard and Pointer Redirector Messages 160 IOPn MtcKmP Status Messages 163 Chapter 12 MtcMICX Messages IOPn MtcMICX Message Summary 170 IOPn Mtc...

Page 5: ...s IOPn MtcSmR Status Message Summary 354 IOPn MtcSmR Status Messages 355 Chapter 16 MtcVidP Messages MtcVidP Status Message Summary 358 IOPn MtcVidP Status Messages 359 Chapter 17 MtcVnP Messages IOPn MtcVnP Status Message Summary 364 IOPn MtcVnP Status Messages 365 Chapter 18 Endurance Manager Messages Types of Messages 370 Endurance Manager Message Summary 370 Endurance Manager Messages 372 ...

Page 6: ...Contents vi ...

Page 7: ...n MtcDsl Message Summary 96 7 1 IOPn MtcEthP and IOPn MtcEtx Message Summary 112 8 1 IOPn MtcEvtP Status Message Summary 138 9 1 IOPn MtcFLOP and IOPn MtcFLOR Status Message Summary 146 10 1 MtcIopDm Status Message Summary 154 11 1 Keyboard and Pointer Message Summary 158 12 1 IOPn MtcMICX Message Summary 170 13 1 IOPn MtcMon Messages 180 14 1 MtcScsiP and MtcScsiR Status Message Summary 294 15 1 ...

Page 8: ...Tables viii ...

Page 9: ... Messages that describes all HP NetServer AA messages Endurance Messages is not shipped in printed form It is only available online using the HP NetServer AA CD HP NetServer AA 6200 Solution Release Notes Release 3 0 Service Pack 1 that describes release specific information including installation requirements operational information and known product limitations that are not documented elsewhere ...

Page 10: ...Represents examples of screen text For example scsiid 0 1 Bold Is used to Emphasize important information Indicate menu pathname or button selections Indicate actions you perform Italics Is used to Highlight the state of the HP NetServer AA server component Refer to manual chapter or section titles Blue text Available only in online documentation Indicates a hyperlink cross reference to another se...

Page 11: ... Messages that display in the HP NetServer AA Manager s GUI display This chapter assumes that you are familiar with HP NetServer AA terminology and the Windows NT process of reporting messages in the Event Viewer Some procedures in this manual refer to maintenance procedures such as shutting down an IOP a CE or the CE operating system Other procedures refer to hardware maintenance procedures such ...

Page 12: ...ns the following sections Examining the Windows NT Event Log 3 HP NetServer AA Messages 4 Format of HP NetServer AA Messages 5 HP NetServer AA Message Categories and Conventions 6 Message Reporting Sources 7 Message Variables 8 Message Summary 9 ...

Page 13: ...w you will view events From the Log menu select the computer for which to view logs to save logs or to open previously saved logs From the View menu you can choose to view all events or you can choose various filters You can also perform searches select the order in which events are displayed and view details about events After selecting these log setting parameters use the Event Viewer to examine...

Page 14: ... including the HP NetServer AA messages that are logged MTCLOG an HP NetServer AA event log utility that displays HP NetServer AA messages that are logged as they are being written Logged HP NetServer AA messages are written to the Windows NT event log as follows Each IOP s Windows NT Event log contains the messages that were generated by that IOP For example IOP1 contains any messages generated b...

Page 15: ...everity Level Description Informational Informational messages are the least severe and do not require action Examples of informational messages include Reporting benign state changes Reporting commands as they are issued Reporting completion status of user initiated processes Warning Warning messages may require attention A continued series of warning messages merits review to see if corrective a...

Page 16: ...HP NetServer AA Manager GUI displays Within chapters and categories messages are listed alphabetically When applicable a message is documented using the following Message Text Variables including their descriptions Severity either Informational Error or Warning Description Related Messages Hardware Software Action The Action section highlights corrective steps While these steps appear as bulleted ...

Page 17: ...atagram Service messages Chapter 5 MtcDsl IOPn MtcDsl status Device Synchronization Layer messages Chapter 6 MtcEthP IOPn MtcEthP status IOP Ethernet subsystem messages that occur between the IOP and the public Ethernet Chapter 7 MtcEtx IOPn MtcEtx status Ethernet transmit subsystem messages that relate to the IL the IOP Link Chapter 7 MtcEvtP IOPn MtcEvtP status IOP Event subsystem messages Chapt...

Page 18: ... NetServer AA Manager messages Chapter 15 MtcVidP IOPn MtcVidP status Video Provider messages Chapter 16 MtcVnP IOPn MtcVnP status Virtual Network Provider messages Chapter 17 MtcCons MtcMgr None HP NetServer AA Manager messages Chapter 18 Table 1 3Message Variables Variable Description CEx CEy A CE identifier Either CE1 or CE2 destIOP The IOP that is the destination of a mirror set copy Either IO...

Page 19: ...is field displays the invalid value that was detected See the message description for details phyDevName A physical device name A physical device comprises one half of a mirror set A mirror set requires two SCSI devices one on each IOP An example of a physical device name is Disk 0 0 1 0 provName The provider name A provider is a software entity that provides some service For example a SCSI provid...

Page 20: ... CEy via IOPx page 47 Confirm Changes made to MIC settings have not been saved Press Esc to return to setup press Enter to exit page 48 Confirm The selected test mode will run on exit in place of system startup Press Esc to return to setup press Enter to continue with exit page 48 Could not connect to the Endurance System Management Redirector page 374 Could not perform request An invalid action t...

Page 21: ...er page 65 Ethernet Provider is not installed page 65 Ethernet Provider should not be bound to the Virtual Network Provider page 66 Floppy detected Bypassing HP NetServer AA startup page 49 Incompatible BIOS data area allocation page 49 Incompatible MIC PCI latency timer value page 49 Incompatible platform module page 50 Incompatible remote BIOS version page 50 Initiating MIC test page 50 Insuffic...

Page 22: ...C not found page 54 MIC system error detected by CEx involving IOPy error identifier MIC error context context data page 54 Negotiating HP NetServer AA startup with IOPx page 55 No MIC identity found A MIC identity must be assigned and saved Press Enter to continue page 55 Number of redirected rails and Ethernet bindings should be equal page 68 One or more fields from the request cannot be display...

Page 23: ...d initialization failed page 373 Retrieval library thread is unavailable page 373 Retrieval library was not initialized page 373 Test test type on port port completed successfully page 57 Test test type on port port failed page 57 Test test type started on port port page 57 Test mode may be canceled by pressing Esc page 58 Test terminated by user page 58 The request cannot be completed because an ...

Page 24: ...3 IOPn MtcDgs status Send packet allocation failure page 94 IOPn MtcDgs status Unable to open NIC page 94 IOPn MtcDgs status Unable to query or set NIC page 94 IOPn MtcDsl status A packet with an invalid transport command was received offendingValue page 98 IOPn MtcDsl status A provider has an invalid Registry entry provName page 98 IOPn MtcDsl status A provider has attempted to register more than...

Page 25: ...e Windows NT Registry The problem may be fixed by re running the HP NetServer AA Configuration Utility page 105 IOPn MtcDsl status Physical device phyDevName of logical device logDevName on IOPx is offline page 105 IOPn MtcDsl status Physical device phyDevName of logical device logDevName on IOPx is online page 106 IOPn MtcDsl status Provider provName experienced an internal failure page 106 IOPn ...

Page 26: ...ing Ethernet packet to the receive buffer page 121 IOPn MtcEthP status Ethernet adapter current address mismatch page 121 IOPn MtcEthP status Ethernet adapter maximum multicast list size mismatch page 122 IOPn MtcEthP status Ethernet adapter optional properties mismatch page 122 IOPn MtcEthP status Ethernet Co Provider protocol version mismatch page 123 IOPn MtcEthP status Ethernet Redirector Prov...

Page 27: ...e been received out of sequence page 130 IOPn MtcEtx status Data PDUs have been retransmitted page 130 IOPn MtcEtx status Error accessing data in the Registry page 131 IOPn MtcEtx status Error in NIC bindings initialization aborted page 131 IOPn MtcEtx status Error transferring incoming Ethernet packet to the receive buffer page 131 IOPn MtcEtx status Ethernet transmit error page 132 IOPn MtcEtx s...

Page 28: ...o IOP message callback routine Releasing resources and continuing page 141 IOPn MtcEvtP status The Event Provider has removed event entries from the pending event queue s because they could not be delivered to a component that normally accepts those events page 141 IOPn MtcEvtP status The Event Provider or Endurance System Management Redirector could not create a worker thread for processing event...

Page 29: ...oblem with the FLOP subkey under Marathon Providers in the Registry page 150 IOPn MtcIopDm status Error in the IOP Disk Monitor device configuration page 155 IOPn MtcIopDm status The IOP Disk Monitor failed to attach to any disk drives page 155 IOPn MtcIopDm status The IOP Disk Monitor has attached to DeviceN HarddiskN PartitionN page 155 IOPn MtcKmP status A critical error occurred initializing t...

Page 30: ...cover page 177 IOPn MtcMICX Port state change failed to change the state to the required setting page 177 IOPn MtcMICX Port state change not allowed MtcMICX has detected a flow control discrepancy page 177 IOPn MtcMICX Port state change not allowed MtcMICX has not flushed packets from the MIC page 178 IOPn MtcMon Fault Handler status An error occurred while sending synchronization information to t...

Page 31: ... Endurance systems on your network with the same Endurance Kit Number This problem should be corrected immediately otherwise you may lose network packets or encounter network connectivity problems page 198 IOPn MtcMon Fault Handler status The Fault Handlers have failed to exchange synchronization information during the merge process page 199 IOPn MtcMon Fault Handler status The joining IOP encount...

Page 32: ...Processor IOPx has detected a misconnected cable on its CEy port or the CEy MIC has had its ID set incorrectly page 210 IOPn MtcMon FRU Uncorrectable memory error on CEx page 211 IOPn MtcMon FRU Uncorrectable platform error on CEx page 212 IOPn MtcMon status A CE protocol error was detected on IOPx during a CEy remove or disable operation page 213 IOPn MtcMon status A CE protocol error was detecte...

Page 33: ...est to shut down the operating system on the CE s could not be performed because shutdown is already in progress page 225 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 page 226 IOPn MtcMon status An error occurred activating Interconnect ESIx page 226 IOP...

Page 34: ...ted due to time out page 234 IOPn MtcMon status CEs are incompatible The memory sizes do not match CE1 memory size y kilobytes CE2 memory size z kilobytes page 235 IOPn MtcMon status CEx cannot be booted because IOPy cannot communicate with it page 235 IOPn MtcMon status CEx cannot be booted because not all required ESIs are available page 236 IOPn MtcMon status CEx cannot be booted by IOPy becaus...

Page 35: ... request page 244 IOPn MtcMon status CEx has been removed from service page 244 IOPn MtcMon status CEx has provided platform device information Chipset vendor chipset Memory mode mode IPMI found Y N page 245 IOPn MtcMon status CEx is available to be booted or synchronized page 245 IOPn MtcMon status CEx is FAULTED and requires repair page 246 IOPn MtcMon status CEx will not be synchronized because...

Page 36: ...s been disabled by operator request page 255 IOPn MtcMon status IOPx has been enabled by operator request page 256 IOPn MtcMon status IOPx has been removed from service page 256 IOPn MtcMon status IOPx has been successfully initialized page 257 IOPn MtcMon status IOPx has begun the IOP initialization process page 257 IOPn MtcMon status IOPx has begun the IOP joining process page 257 IOPn MtcMon st...

Page 37: ...as been requested by the operator page 268 IOPn MtcMon status The active CEs were removed because the boot device is no longer accessible page 269 IOPn MtcMon status The boot conflict could not be resolved page 269 IOPn MtcMon status The boot process has completed for CEx page 270 IOPn MtcMon status The boot process has failed for CEx page 270 IOPn MtcMon status The boot process has failed for CEx...

Page 38: ...cMon status The CE MIC FPGA revisions do not match CE1 MIC FPGA revision 0xx CE2 MIC FPGA revision 0xy page 278 IOPn MtcMon status The CE MIC microcode edit levels do not match CE1 MIC microcode revision 0xx CE2 MIC microcode revision 0xy page 278 IOPn MtcMon status The CE MIC microcode revisions are not compatible CE1 MIC microcode revision 0xx CE2 MIC microcode revision 0xy page 279 IOPn MtcMon ...

Page 39: ...ory size y kilobytes CE2 memory size z kilobytes page 286 IOPn MtcMon status The MIC Transport driver MtcMICX has not yet registered with the Monitor page 286 IOPn MtcMon status The Monitor is waiting for all required interconnects to become available page 287 IOPn MtcMon status The Monitor s ClientList value in the Windows NT Registry is invalid page 287 IOPn MtcMon status The number of CE CPU pr...

Page 40: ...re error occurred during join Contact your service provider for assistance page 303 IOPn MtcScsiP status An unrecoverable CE boot disk read error occurred during the BIOS phase of boot The disk will be marked faulted page 303 IOPn MtcScsiP status Attempt to restart mirror copy for DISKn has failed Cannot access target disk for mirror copy Check prior events for details page 304 IOPn MtcScsiP statu...

Page 41: ... NetServer AA Manager request to non mirrored disk was ignored page 309 IOPn MtcScsiP status Configured ADAPTERn failed to reset bus BUSx Disks connected to this adapter may be marked faulted page 309 IOPn MtcScsiP status Configured ADAPTERx has a misconfigured bus ID BUSn Use the HP NetServer AA Configuration Utility to change the bus ID page 309 IOPn MtcScsiP status Configured ADAPTERx has diffe...

Page 42: ... be marked offline page 315 IOPn MtcScsiP status DISKn cannot be physically accessed See prior events for reason page 315 IOPn MtcScsiP status DISKn contains an invalid partition table The disk must be repartitioned page 315 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 NetS...

Page 43: ...per sector for each of its member disks page 322 IOPn MtcScsiP status DISKn has a SCSI address other than its original configured SCSI address The HP NetServer AA partition can be reset to cure this condition but caution is advised If unsure how to proceed contact your service provider for assistance page 322 IOPn MtcScsiP status DISKn has an HP NetServer AA partition that is not at the end of the...

Page 44: ...P status DISKn has had SCSI tagged queuing disabled This disk type may have exhibited problems with SCSI tagged queuing This feature is disabled to prevent corruption problems page 327 IOPn MtcScsiP status DISKn has had write cache disabled This disk type may have exhibited problems with write cache This feature is disabled to prevent corruption problems page 327 IOPn MtcScsiP status DISKn has rea...

Page 45: ...t of date and will be updated page 333 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 The local IOP was unable to access the disk to reset the HP NetServer AA partition or the disk did not have acc...

Page 46: ...es not require resetting or disk cannot be accessed for resetting page 339 IOPn MtcScsiP status SCSI Provider on IOP1 is incompatible with the SCSI Provider on IOP2 page 340 IOPn MtcScsiP status The administrator disabled DISKn The device must be manually enabled using HP NetServer AA Manager before it can be used page 340 IOPn MtcScsiP status The administrator is attempting to disable DISKn page ...

Page 47: ... page 345 IOPn MtcScsiP status Unable to read one or more CE requested sectors SECTORn SECTORm for DISKx If DISKx stays online this error may be considered transient Many transient errors may indicate the need for disk replacement page 345 IOPn MtcScsiP status Unable to read one or more sectors SECTORn SECTORm for DISKx Note The read request did not come from the CEs page 346 IOPn MtcScsiP status ...

Page 48: ...ns The ability to log HP NetServer AA events on the CE may be partially or fully impaired Any event generated at this time will only be logged on the IOP that generated the event page 355 IOPn MtcSmR status The HP NetServer AA System Management Redirector failed to send a request to read an event from the Event Provider Attempting to continue to provide HP NetServer AA System Management control fu...

Page 49: ...ut Provider is not in the joining state page 366 IOPn MtcVnP status More than one instance of the Virtual Network Provider was installed in the control panel page 366 IOPn MtcVnP status Timeout waiting for join response from active Virtual Network Provider page 366 IOPn MtcVnP status Virtual Network Co Provider protocol version mismatch page 366 IOPn MtcVnP status Virtual Network Redirector Provid...

Page 50: ...CEX Unable to complete synchronization related initialization Status 0xy page 82 MtcCEX Unable to create device object Status 0xy page 83 MtcCEX Unable to find the CE MIC adapter page 83 MtcCEX Unable to generate SYSERR packet Status 0xy page 84 MtcCEX Unable to initialize QI mechanism Status 0xy page 84 MtcCEX Unable to initialize the MIC adapter Status 0xy page 85 MtcCEX Unable to read the Windo...

Page 51: ...n invalid sync up response from the Floppy Provider As a result the floppy devices will be inaccessible page 151 MtcFLOR status The registration of MtcFloR with the CE Transport failed page 151 Table 1 5HP NetServer AA Message Summary Prefixed Messages Continued Message Page ...

Page 52: ...Chapter 1 Introduction 42 ...

Page 53: ... BIOS messages are not written to the Windows NT Event Log and they have no prefixes This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions This chapter includes the following sections Types of Messages 44 MIC BIOS Message Summary 45 MIC BIOS Messages 47 2 MIC BIOS Messages ...

Page 54: ...ronization process or the status of MIC BIOS tests In most cases you do not need to perform any action when informational messages display Error messages indicate problems or report reasons why progress is not occurring In many cases you can retry a test or reboot an element of the server Otherwise if the error continues to be reported contact your service provider for assistance in resolving the ...

Page 55: ...up press Enter to continue with exit page 48 HP NetServer AA startup canceled by user page 48 Entering server mode Listening for client test connections page 48 Establishing CEy communication channels page 49 Floppy detected Bypassing HP NetServer AA startup page 49 Incompatible BIOS data area allocation page 49 Incompatible MIC PCI latency timer value page 49 Incompatible platform module page 50 ...

Page 56: ...ode page 55 Performing external loopback tests Please ensure MIC ports are connected page 55 Performing internal loopback tests page 56 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 bypass automatic reboot or any other key to reboot page 56 ...

Page 57: ...ot process with IOPx Variables x the ID of the IOP facilitating the boot process Severity Informational Description The specified IOP has been selected to boot the CE All further communication ensues with this IOP Action No action is required Beginning synchronization with CEy via IOPx Variables x the ID of the IOP that is facilitating the synchronization process y the ID of the CE with which sync...

Page 58: ...er to continue with exit Severity Informational Description A test mode was selected and will run following POST in place of the normal system startup Action Press Esc to return to the setup utility and cancel the test mode Otherwise press Enter to continue with the test after exit completes HP NetServer AA startup canceled by user Severity Informational Description The user pressed the Esc key du...

Page 59: ...AA startup remove the media and reboot Incompatible BIOS data area allocation Severity Error Description The System BIOS or other components in the system have allocated memory in the range 09000 09FFF in an unrecognized or unsupported way This error is typically due to an incompatibility with the System BIOS Action If you have recently updated the BIOS or added components to the system restore th...

Page 60: ...e MIC BIOS on the remote system is incompatible with the version on the local system Action Update the firmware on all MICs involved in the test Initiating MIC test Severity Informational Description A test mode was selected from the MIC BIOS setup utility Action No action is required Invalid response message description Severity Error Description The MIC BIOS received a message indicated by the d...

Page 61: ... IOP s event log for further information about why the boot process was aborted IOPx has requested a reset Variables x the ID of the IOP that has requested a reset Severity Error Description The specified IOP has requested a reset Action Consult the specified IOP s event log for further information about why a reset was requested MIC BIOS internal error module line line Severity Error Description ...

Page 62: ...er for assistance MIC communication lost with IOPx Variables x the ID of the IOP with which the MIC has lost communication Severity Error Description The MIC BIOS lost communication with the specific IOP and terminated the boot or synchronization process Often there is another error displayed prior to this with additional detail about the cause There may also be related events in the startup IOP s...

Page 63: ...ation complete Description The MIC initialization performed at system POST Power On Self Test is complete If this is an IOP this is the last message displayed by the MIC BIOS On CEs control returns to the System BIOS to complete initialization The MIC later regains control to manage the boot or synchronization process Action No action is required MIC internal error module linen context context dat...

Page 64: ... Update the firmware on the MIC Examine the system BIOS settings to ensure that your PCI slots are properly configured To determine if there is an incompatibility between the MIC and the PCI system in which it is currently installed try the MIC on a different system If the error persists replace the MIC MIC system error detected by CEx involving IOPy error identifier MIC error context context data...

Page 65: ...o the Unknown setting Action Select the appropriate element identity Save the setting in non volatile memory Upon exiting the setup utility reboot the appropriate element to reinitialize the firmware to the new setting Performing client tests Please ensure remote port s are in server mode Severity Informational Description For a client test the ports to be included in the test must be physically c...

Page 66: ...and version information to start the MIC Setup Utility Use this utility to change the MIC identity and to run diagnostics You can also press Esc on the keyboard attached to the HP NetServer AA element to bypass the normal initialization and on CEs the startup process This may be useful when it is necessary to boot off a local device or temporarily circumvent a compatibility problem while a system ...

Page 67: ...or persists contact your service provider for assistance Test test type on port port completed successfully Severity Informational Description The specified test completed without errors Action No action is required Test test type on port port failed Severity Informational Description The specified test completed with an error Additional error detail is provided in the messages displayed just prio...

Page 68: ...on This message displays only when you are running a test that was unable to contact the destination MIC via the specified port Depending on the type of test that is running this message could indicate a malfunctioning MIC or a faulty fiber connection Action If the message displays when you are running a client server test perform an external loopback test on each MIC to determine if the problem i...

Page 69: ...the system is automatically rebooted This could occur due to System BIOS incompatibilities software faults or hardware failures Action Verify that the hardware is functioning properly by running the MIC BIOS client server diagnostics between the CE and the IOP providing startup services Consult the startup IOP s event log for possible additional information If the error persists contact your servi...

Page 70: ...Chapter 2 MIC BIOS Messages 60 ...

Page 71: ... written to the Windows NT Event Log on the IOP on which the event occurs This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions This chapter includes the following sections Types of Message 62 IVP Message Summary 63 IVP Messages 64 3 Installation and Verification Procedure IVP Messages ...

Page 72: ...te action In many cases you can retry a test or reboot a component of the server Otherwise if the error continues to be reported contact your service provider for assistance in resolving the problem Several IVP messages may appear together If multiple configuration problems are detected look for related events that are logged during the same time frame If the log details multiple problems make sur...

Page 73: ...Network Provider page 65 Ethernet Provider and the IOP Link Driver should not be bound to the same adapter page 65 Ethernet Provider is not bound to any adapter page 65 Ethernet Provider is not installed page 65 Ethernet Provider should not be bound to the Virtual Network Provider page 66 IOP Link Driver is not bound to any adapter page 66 IOP Link Driver is not installed page 66 IOP Link Driver s...

Page 74: ... Service as described in Chapter 3 in the HP NetServer AA Solution Installation Guide Datagram Service should be bound to the same adapter as the IOP Link Driver Severity Error Description The HP NetServer AADatagram Service is not bound to the same adapter as the HP NetServer AAIOP Link Driver Action Bind the HP NetServer AADatagram service to the same adapter as the HP NetServer AAIOP Link Drive...

Page 75: ...AAEthernet Provider should not be bound to the same adapter as theEndurance IOP Link adapter and the Endurance IOP Link Driver cannot be bound to a redirected rail Disable one of the services from the adapter to which they are both bound Ethernet Provider is not bound to any adapter Severity Warning Description The HP NetServer AAEthernet Provider is not bound to any adapter Action If an adapter i...

Page 76: ...e Endurance IOP Link Driver is not bound to any adapter Action Bind the HP NetServer AAIOP Link Driver to the adapter used as the HP NetServer AAIOP Link Driver IOP Link Driver is not installed Severity Error Description The HP NetServer AAIOP Link Driver is not installed Action Install the HP NetServer AAIOP Link Driver as described in Chapter 3 in the HP NetServer AA Solution Installation Guide ...

Page 77: ... one two Severity Error Description The MAC address for the local adapter on the specified rail either does not exist or is not bound to the HP NetServer AAEthernet Provider Action Remove the specified rail from the configuration and commit the change Re add the rail using the MAC address of the remote and local NICs that are bound to the HP NetServer AAEthernet Provider Alternatively change the b...

Page 78: ...e HP NetServer AAEthernet Provider so that the number of adapters and rails are equal Disable the HP NetServer AAEthernet Provider from adapters so that the number of adapters and rails are equal Using the HP NetServer AAconfiguration utility add more rails until the number of adapters and rails are equal Using the HP NetServer AAconfiguration utility remove rails until the number of adapters and ...

Page 79: ...se messages are displayed either as the CE operating system is booting or when a CE is being deconfigured These messages are not written to the Windows NT Event Log This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions This chapter includes the following sections MtcCEX Message Summary 70 MtcCEX Messages 72 4 MtcCEX Messages ...

Page 80: ...started page 76 MtcCEX HP NetServer AA CE MIC Transport y is initializing page 75 MtcCEX Last IOP removed via REMOVE_IOP command page 76 MtcCEX Lost communications with boot IOP page 77 MtcCEX MIC adapter is not configured for CE operation page 77 MtcCEX MIC adapter malfunction detected page 78 MtcCEX Received illegal CE control packet page 78 MtcCEX Received illegal communication from non boot IO...

Page 81: ...itialize the MIC adapter Status 0xy page 85 MtcCEX Unable to read the Windows NT Registry Status 0xy page 85 MtcCEX Unable to register BUGCHECK notification Status 0xy page 86 MtcCEX Unable to register SHUTDOWN notification Status 0xy page 86 MtcCEX Unable to transmit SYSERR packet Status 0xy page 87 MtcCEX Unexpected internal error detected Status 0xy page 87 Table 4 1 MtcCEX Message Summary Cont...

Page 82: ...the CE Transport and the 32 bit platform specific initialization module This error is fatal to CE operations and is followed by a reset of the CE Hardware Software This message indicates a software configuration error Action The CE is reset and may attempt to reboot Windows NT If this failure recurs repeatedly the CE will be marked faulted Rerun the HP NetServer AA installation on both IOPs and ve...

Page 83: ...CE will be marked faulted Rerun the HP NetServer AA installation on both IOPs and verify that the specified CE hardware platform matches the CEs in the HP NetServer AA configuration If the failure persists contact your service provider for assistance MtcCEX Could not initialize MIC adapter Status 0xy Variables y An error status displayed in hexadecimal Severity Error Description This message displ...

Page 84: ...tance MtcCEX Could not transition IOPx MIC port to ACTIVE Variables x ID of the IOP associated with the MIC adapter port that failed 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 cannot activate a MIC adapter port as requested by the IOP during the boot proces...

Page 85: ...MIC adapter Action If CE boot does not succeed immediately or after retrying first replace the CE MIC adapter and then replace the IOP MIC adapter If the problem persists contact your service provider for assistance MtcCEX HP NetServer AA CE MIC Transport y is initializing Variables y the version of the CE Transport MtcCEX sys Severity Informational Description This message displays in a Windows N...

Page 86: ...ed via REMOVE_IOP command Severity Warning Description This message displays in a Windows NT blue screen on a monitor attached directly to a CE when the IOP directs the CE to remove the last active IOP This may occur as a result of fault handling in the HP NetServer AA system or as a result of an operator command This event terminates the CE operating system and is followed by a reset of the CE Ha...

Page 87: ... the problem persists contact your service provider for assistance MtcCEX MIC adapter is not configured for CE operation 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 detects that the CE MIC adapter is not properly configured for CE operations Related Messages M...

Page 88: ...tance MtcCEX Received illegal CE control 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 invalid packet from the IOP The CE Transport attempts to continue the boot process Hardware Software This message may be the result of either an HP NetS...

Page 89: ...the IOPs and the CE If the problem continues replace the CE MIC If the problem persists contact your service provider for assistance MtcCEX Received illegal STARTUP request from 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 an invalid START...

Page 90: ...m persists contact your service provider for assistance MtcCEX Received RESET request from 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 RESET request from the IOP The CE operating system boot terminates Hardware Software This message is ...

Page 91: ... O Processor Mode and install any HP NetServer AA service packs or hotfixes required to support the current version of Windows NT If the problem persists contact your service provider for assistance MtcCEX Unable to allocate the required resources Status 0xy Variables y an error status displayed in hexadecimal Severity Error Description This message displays in a Windows NT blue screen on a monito...

Page 92: ...CE root and reinstall the HP NetServer AA software If the problem persists contact your service provider for assistance MtcCEX Unable to complete synchronization related 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 whe...

Page 93: ...rver AA software If the problem persists contact your service provider for assistance MtcCEX Unable to find the CE MIC adapter 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 cannot locate the MIC adapter This error is fatal to CE operations and is followed by a reset of the CE Hardware Softwa...

Page 94: ...the CE is diagnosed offline After you repair or replace the CE manually return it to service MtcCEX Unable to initialize QI mechanism 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 u...

Page 95: ...es its self test Replace the MIC adapter if necessary If the problem persists contact your service provider for assistance MtcCEX Unable to read the Windows NT Registry 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 NetServ...

Page 96: ...oot and reinstall the HP NetServer AA software If the problem persists contact your service provider for assistance MtcCEX Unable to register SHUTDOWN 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...

Page 97: ...exceeds a threshold If the threshold is exceeded the CE is marked faulted and is not resynchronized In this case the CE is diagnosed offline After you repair or replace the CE manually return it to service MtcCEX Unexpected internal error detected Status 0xy Variables y an error status displayed in hexadecimal Severity Error Description This message displays in a Windows NT blue screen on a monito...

Page 98: ...Chapter 4 MtcCEX Messages 88 ...

Page 99: ...s that are written to the Windows NT Event Log This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions This chapter includes the following sections IOPn MtcDgs Status Message Summary 90 IOPn MtcDgs Status Messages 91 5 MtcDgs Messages ...

Page 100: ...rnet packet to the receive buffer page 92 IOPn MtcDgs status Ethernet transmit error page 92 IOPn MtcDgs status Incomplete transfer of incoming Ethernet packet to the receive buffer page 92 IOPn MtcDgs status Initialization error page 92 IOPn MtcDgs status Invalid Ethernet packet received page 93 IOPn MtcDgs status Invalid Registry parameter Using default value page 93 IOPn MtcDgs status NIC recei...

Page 101: ...s aborted As a result the driver did not load and the IOP cannot join the HP NetServer AA server configuration Action Confirm the MtcDgs bindings are correct Use the Network Control Panel application to remove and reinstall MtcDgs IOPn MtcDgs status Error in NIC bindings Severity Error Description Too many Network Interface Controllers NICs are bound to the MtcDgs service MtcDgs will use the first...

Page 102: ...plete transfer of incoming Ethernet packet to the receive buffer Severity Warning Description An adapter was unable to copy the entire Ethernet packet to a receive buffer owned by MtcDgs This error usually occurs because the NIC was reset while a receive was in progress The Event Viewer Data section of the message contains the length transferred and requested Action You can ignore this message unl...

Page 103: ...lookahead buffer is too small Severity Error Description When an Ethernet packet is received a NIC provides access to some portion of the packet data a lookahead buffer during the initial stage of receive processing This message is returned when during initialization MtcDgs queries the NIC and discovers the lookahead buffer size is too small to support MtcDgs operations This message can occur afte...

Page 104: ...og for errors logged by the NIC driver If a condition is preventing the driver from initializing the device follow the manufacturer s procedures for correcting the condition Verify the bindings for NICs Make any required changes to the bindings After you modify the bindings remember to reboot the IOP so the new bindings can take effect Refer to Chapter 9 in HP NetServer AA Solution Administrator s...

Page 105: ...s 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 96 IOPn MtcDsl Status Messages 98 6 MtcDsl Messages ...

Page 106: ...d offendingValue page 101 IOPn MtcDsl status An invalid component state was encountered offendingValue page 101 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 d...

Page 107: ... IOP 2 This problem may be fixed by comparing the configurations and making them consistent page 106 IOPn MtcDsl status Unable to allocate a callback descriptor page 107 IOPn MtcDsl status Unable to allocate a callback worker thread page 107 IOPn MtcDsl status Unable to find a flush descriptor on the global flush list page 107 IOPn MtcDsl status Unable to initialize the DSL page 108 IOPn MtcDsl st...

Page 108: ... Guide for information about how to reboot an IOP Verify whether the IOP is experiencing intermittent hardware failures and correct any failures IOPn MtcDsl status A provider has an invalid Registry entry provName Severity Error Description The Windows NT Registry information for a specific provider is invalid Hardware Software The Windows NT Registry information is corrupt or improperly configure...

Page 109: ...is causing the condition discontinue use of the application Contact your service provider for supported devices IOPn MtcDsl status A request for provider provName used an invalid logical device ID Severity Error Description Providers receive and process device requests A logical device ID indicates the destination device for a particular request If a request is received with an invalid device ID t...

Page 110: ...rvice provider for assistance IOPn MtcDsl status A tack timeout condition was not cleared properly Severity Error Description The Device Synchronization Layer encountered an internal error Hardware Software This message indicates an internal HP NetServer AA server software error Action Reboot the IOP and allow it to join the HP NetServer AA server Refer to Chapter 9 in HP NetServer AA Solution Adm...

Page 111: ...s an HP NetServer AA server software error or an intermittent IOP hardware failure Action Reboot the IOP and allow it to rejoin the HP NetServer AA server Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about how to reboot an IOP Verify whether the IOP is experiencing intermittent hardware failures and correct any failures IOPn MtcDsl status An invalid componen...

Page 112: ...erver Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about how to reboot an IOP Verify whether the IOP is experiencing intermittent hardware failures and correct any failures IOPn MtcDsl status An invalid IOP state was encountered offendingValue Severity Error Description The Device Synchronization Layer encountered an invalid IOP state Hardware Software This ...

Page 113: ...ware A packet descriptor goes through multiple levels of checking while in transit between HP NetServer AA server elements A packet descriptor was corrupted after it was received by a particular IOP Action Reboot the IOP and allow it to rejoin the HP NetServer AA server Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about how to reboot an IOP Verify whether th...

Page 114: ...This message indicates an HP NetServer AA server software error or an intermittent IOP hardware failure Action Reboot the IOP and allow it to rejoin the HP NetServer AA server Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about how to reboot an IOP Verify whether the IOP is experiencing intermittent hardware failures and correct any failures IOPn MtcDsl statu...

Page 115: ...elete and re add each device IOPn MtcDsl status Physical device phyDevName of logical device logDevName on IOPx is offline Variables x the ID of the IOP that originated the event Severity Informational Description This message is generated when the HP NetServer AA server tries to access a device that is not available Related Messages IOPn MtcDsl status Physical device phyDevName of logical device ...

Page 116: ...software components Hardware Software This message indicates an internal HP NetServer AA server provider error Action If this message occurs after installing a new version of HP NetServer AA server software reinstall the software If this condition persists or if it occurs after installing a new version of Windows NT contact your service provider for assistance IOPn MtcDsl status The IOPs could not...

Page 117: ... thread This message indicates an operating system resource condition usually related to insufficient memory in the reporting IOP Related Messages IOPn MtcDsl status Unable to allocate callback descriptor IOPn MtcDsl status Unable to initialize DSL Hardware Software This message indicates an operating system resource condition caused by insufficient IOP memory Action Add more memory to the reporti...

Page 118: ... system resource condition usually related to insufficient memory in the reporting IOP Related Messages IOPn MtcDsl status Unable to allocate callback worker thread Hardware Software This message usually indicates an operating system resource condition caused by insufficient memory in the reporting IOP Action Add more memory to the reporting IOP If there is sufficient memory in the IOP contact you...

Page 119: ...109 Chapter 6 MtcDsl Messages ...

Page 120: ...Chapter 6 MtcDsl Messages 110 ...

Page 121: ...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 112 IOPn MtcEthP Status Messages 115 IOPn MtcEtx Status Messages 130 7 MtcEthP and MtcEtx Mes sages ...

Page 122: ...n Ethernet Provider device configuration page 119 IOPn MtcEthP status Error in Ethernet Provider NIC bindings in the Control Panel page 120 IOPn MtcEthP status Error opening or initializing NIC page 120 IOPn MtcEthP status Error resetting Network Interface Controller page 121 IOPn MtcEthP status Error transferring incoming Ethernet packet to the receive buffer page 121 IOPn MtcEthP status Ethernet...

Page 123: ...in response from active Ethernet Provider page 128 IOPn MtcEthP status Timeout waiting for report primary message x y page 129 IOPn MtcEthP status Unable to set Ethernet multicast address list page 129 IOPn MtcEthP status Unable to set Ethernet packet filter page 129 IOPn MtcEtx status Data PDUs have been received out of sequence page 130 IOPn MtcEtx status Data PDUs have been retransmitted page 1...

Page 124: ...ismatch between IOPs Using default value page 135 IOPn MtcEtx status Send buffer descriptor allocation failure page 135 IOPn MtcEtx status Send packet allocation failure page 135 IOPn MtcEtx status Unable to open NIC initialization aborted page 136 IOPn MtcEtx status Unable to query or set NIC page 136 IOPn MtcEtx status Unable to reset NIC page 136 Table 7 1 IOPn MtcEthP and IOPn MtcEtx Message S...

Page 125: ...status A call to NdisReset timed out Severity Warning Description An NdisReset on the NIC timed out The Ethernet Provider retries the request several times If all requests timeout or fail the NIC will be failed Action Reboot the IOP to clear the error condition on the NIC You may want to power cycle the IOP when you reboot it Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for...

Page 126: ...NetServer AA configuration that has been running the least amount of time are faulted You can use the HP NetServer AA Manager to reenable them once the source of the problem has been corrected Action Start the HP NetServer AA Manager on the local IOP From the menu bar select View Revision Levels The first line displayed contains the HP NetServer AA kit number Use the HP NetServer AA Manager on the...

Page 127: ...due to a problem external to the HP NetServer AA server This message may also occur if IOPs lose communication with each other over all internal paths Action Use the HP NetServer AA Manager to disable and then enable one of the redirected network devices If the problem persists disable one of the redirected network devices and contact your service provider for assistance IOPn MtcEthP status Device...

Page 128: ...s are being received Check the LEDs on the NIC Use the MTCEINFO Tool described Chapter 7 in HP NetServer AA Solution Administrator s Guide to monitor the error counters maintained by the adapter If the cables are properly connected but the device remains in the offline state try rebooting the IOP Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about how to rebo...

Page 129: ...k Control Panel application make sure that the adapter bindings are set correctly Bind the MtcEthP driver to the adapter that provides connectivity to the local area network Make sure that NetworkAddress is correctly defined in the Registry The NetworkAddress value is defined under the subkey for the adapter HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services adapter name Parameters Make sure tha...

Page 130: ...adapter services key in the Registry to be removed and recreated Make sure that the NetworkAddress value is correctly added in the Registry by the Endurance Configuration Utility the commit function The NetworkAddress value is defined under the Parameters subkey for the adapter HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services adapter name Parameters Make sure that you are using a NIC that supp...

Page 131: ...problem with the NIC IOPn MtcEthP status Ethernet adapter current address mismatch Severity Error Description This message is logged during IOP joining when the joining Ethernet Provider receives a join response from the merging Ethernet Provider The current Ethernet addresses in use by the physical Network Interface Controllers that comprise the logical Ethernet device are not identical The Ether...

Page 132: ... are not identical replace them with NICs that are identical Use the MTCEINFO Tool described in Chapter 7 in HP NetServer AA Solution Administrator s Guide to display adapter characteristics IOPn MtcEthP status Ethernet adapter optional properties mismatch Severity Error Description This message is logged during IOP joining when the joining Ethernet Provider receives a join response from the mergi...

Page 133: ...P on both IOPs If reported following a software upgrade reapply the upgrade to both IOPs Contact your service provider for assistance IOPn MtcEthP status Ethernet Redirector Provider protocol version mismatch Severity Error Description This message is logged during CE boot when the Ethernet Redirector notifies the Ethernet Provider that it is initializing Incompatible versions of the Ethernet Redi...

Page 134: ...s persist replace the NIC IOPn MtcEthP status Incomplete transfer of incoming Ethernet packet to the receive buffer Severity Warning Description The Network Interface Controller was unable to copy the entire Ethernet packet to a receive buffer owned by the Ethernet Provider This message is usually logged if the NIC is reset while a receive was in progress IOPn MtcEthP status Invalid Ethernet packe...

Page 135: ...lues IOPn MtcEthP status Join response received but device 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 Ethernet Provider joining protocol Action Contact your service provider for assistance IOPn MtcEthP status NdisRequest returned an error Severity Error ...

Page 136: ...ta section contains the Windows NT error code This message is logged during MtcEthP initialization or during IOP state transitions The NIC will be failed Action Reboot the IOP to clear the error condition on the NIC You may want to power cycle the IOP when you reboot it Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about how to reboot an IOP IOPn MtcEthP stat...

Page 137: ... an Ethernet device fails correct the condition and reboot the IOP Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about how to reboot an IOP IOPn MtcEthP status Runt Ethernet packet received Severity Warning Description The NIC indicated that it received an Ethernet packet with an invalid header length less than 14 bytes Hardware Software A large number of rec...

Page 138: ...Action Replace the adapters with adapters and drivers that are certified for use with the HP NetServer AA You can continue to use the adapters if both IOP adapters are attached to the same physical Ethernet segment IOPn MtcEthP status Timeout waiting for join complete from active Ethernet Provider Severity Error Description The joining Ethernet Provider did not receive a join complete message from...

Page 139: ...Event Viewer Data section contains the Windows NT NdisRequest error code This message can also occur when the Ethernet Provider is attempting to clear the multicast address list after CE shutdown or when an IOP is disabled Action Reboot the IOP Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about how to reboot an IOP IOPn MtcEthP status Unable to set Ethernet ...

Page 140: ...rors try increasing the adapter parameters such as the number of receive buffers Contact your service provider for further assistance IOPn MtcEtx status Data PDUs have been retransmitted Severity Warning Description An acknowledgment for a data PDU was not received from the remote IOP within the timeout interval This message is logged when the condition first occurs and thereafter on every 1000th ...

Page 141: ...boot an IOP IOPn MtcEtx status Error in NIC bindings initialization aborted Severity Error Description This message is logged during initialization when MtcEtx verifies the NIC bindings for the IL adapter It is generated if MtcEtx is not bound to a single NIC and indicates that there is an error in the bindings that were established in the Network Control Panel application Action Run the Network C...

Page 142: ...e a problem with the cable or the adapter Verify that the adapter was set up correctly for example 100MB full duplex See Also For IL configuration information refer to Chapter 3 in HP NetServer AA Solution Installation Guide IOPn MtcEtx status Incomplete transfer of incoming Ethernet packet to the receive buffer Severity Warning Description The IL adapter was unable to copy the entire Ethernet pac...

Page 143: ...errors indicate a problem with the cable to the NIC Verify that the NIC was set up correctly for example 100 MB full duplex See Also For IL configuration information refer to Chapter 3 in HP NetServer AA Solution Installation Guide IOPn MtcEtx status Invalid Registry parameter Using default value Severity Warning Description During initialization MtcEtx reads optional parameters from the Windows N...

Page 144: ...n MtcEtx status NIC receive data lookahead buffer is too small Severity Error Description When an Ethernet packet is received a NIC provides access to some portion of the packet data during the initial stage of receive processing This is known as the lookahead buffer This message is logged during initialization when MtcEtx queries the IL s NIC and discovers the lookahead buffer size is too small t...

Page 145: ...ading and rebooting the other IOP Action Run a Registry editor and note the values under HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services MtcEtx Parameters Contact your service provider for further assistance See Also The HP NetServer AA Manager command IOPn IopLinkDriver Show Parameter Values IOPn MtcEtx status Send buffer descriptor allocation failure Severity Error Description MtcEtx was un...

Page 146: ...s message is logged during initialization or during IOP state transitions when MtcEtx attempts to set or query NIC characteristics The Event Log Data section contains the Windows NT NdisRequest error code Depending on the attempted operation MtcEtx may abort initialization or may report an error to the Fault Handler Action Rebooting the IOP should clear state transition errors Refer to Chapter 9 i...

Page 147: ... 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 138 IOPn MtcEvtP Status Messages 140 8 MtcEvtP Messages ...

Page 148: ...tP status The Event Provider detected a failure occurred when trying to send back the response to a request page 140 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 page 141 IOPn MtcEvtP status The Event Provider has detected a non response message in the IOP to IOP message callback routine Releasing r...

Page 149: ... EVTP subdue under Marathon Providers in the Registry page 142 IOPn MtcEvtP status The registration of event pipe logical events failed or an unexpected number of event pipes was found In most cases this indicates a setup problem with the EVTP subkey under Marathon Providers in the Registry page 142 IOPn MtcEvtP status There are no events awaiting delivery to the Endurance System Management Redire...

Page 150: ...DLL Severity Error Description The MtcEvtP driver could not initialize properly Messages may not be logged and Endurance Manager requests may not be able to be performed IOPn MtcEvtP status The Event Provider could not send a sync up response to the Endurance System Management Redirector Severity Error Description The MtcEvtP driver attempted to respond to the Endurance System Management Redirecto...

Page 151: ...e usually indicates a temporary condition that prevents the Event Provider from delivering messages When this occurs the Event Provider removes the undeliverable messages from the message queue This condition usually occurs when The CE operating system is down The Endurance System Management Service on either IOP or the CE is not running Windows NT on either IOP or the CE does not have sufficient ...

Page 152: ...rovider for assistance IOPn MtcEvtP status The IOP s event pipe handle was not obtained This is an indication that the Registry is not set up correctly Severity Error Action Correct the condition by reinstalling the Endurance software IOPn MtcEvtP status The registration of event pipe logical events failed This indicates a setup problem with the EVTP subdue under Marathon Providers in the Registry...

Page 153: ...r 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 144 ...

Page 155: ...the Windows NT Event Log This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions This chapter includes the following sections IOPn MtcFLOP and MtcFLOR Status Message Summary 146 IOPn MtcFLOP Status Messages 147 MtcFLOR Status Messages 151 9 MtcFLOP and MtcFLOR Mes sages ...

Page 156: ...will be inaccessible page 148 IOPn MtcFLOP status The Floppy Provider attempted to respond to a request but it was unable to send the reply back to the Redirector page 149 IOPn MtcFLOP status The Floppy Provider could not register with the DSL page 149 IOPn MtcFLOP status The registration of logical devices failed This indicates a setup problem with the FLOP subkey under Marathon Providers in the ...

Page 157: ...As a result that floppy device will be inaccessible IOPn MtcFLOP status The Floppy Provider attempted to create a floppy device but failed As a result that floppy device will be inaccessible IOPn MtcFLOP status The Floppy Provider attempted to respond to a request but it was unable to send the reply back to the Redirector IOPn MtcFLOP status The Floppy Provider could not register with the DSL IOPn...

Page 158: ...IOPs On the IOP where the floppy devices physically reside use Start Setting Control Panel Devices and make sure that the Floppy is listed and shown as running Check the Event Viewer for a Windows NT message stating that the floppy driver failed to initialize If this message was logged Windows NT did not initialize the floppy driver Refer to Windows NT documentation for information IOPn MtcFLOP st...

Page 159: ...cFLOP status The registration of logical devices failed 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 Conf...

Page 160: ...es is automatically supplied based on the parameters that you supplied using the HP NetServer AA Configuration Utility Action Using the HP NetServer AA Configuration Utility check the configuration information that you supplied for each floppy device Make any necessary corrections Remember that when you make a change using the HP NetServer AA Configuration Utility you must make the same change on ...

Page 161: ...e IOP reboots schedule an appropriate time to reboot the affected IOP or the entire server MtcFLOR status The Floppy Redirector received an invalid sync up response from the Floppy Provider As a result the floppy devices will be inaccessible Severity Error Description An internal error has occurred Action Using the HP NetServer AA Configuration Utility check the configuration information that you ...

Page 162: ...Chapter 9 MtcFLOP and MtcFLOR Messages 152 ...

Page 163: ...us 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 154 IOPn MtcIopDm Status Messages 155 10 MtcIopDm Messages ...

Page 164: ...the order that they are documented Table 10 1 MtcIopDm Status Message Summary IOPn MtcIopDm status Error in the IOP Disk Monitor device configuration page 155 IOPn MtcIopDm status The IOP Disk Monitor failed to attach to any disk drives page 155 IOPn MtcIopDm status The IOP Disk Monitor has attached to DeviceN HarddiskN PartitionN page 155 ...

Page 165: ...k Monitor failed to insert itself into the disk driver chain for any devices The most likely cause of this problem is installation of software that changed the device driver load order The IOP Disk Monitor will not be able to detect failures of the IOP boot disk or other disks that are private to the IOP Action Reinstall the HP NetServer AA IOP software Contact your service provider for further as...

Page 166: ...Chapter 10 MtcIopDm Messages 156 ...

Page 167: ...ot have an associated IOPn Mtc prefix Provider MtcKmP messages use the IOPn MtcKmP prefix This chapter assumes that you are familiar with HP NetServer AA terminology This chapter includes the following sections Keyboard and Pointer Message Summary 158 Keyboard and Pointer Redirector Messages 160 IOPn MtcKmP Status Messages 163 11 Keyboard and Pointer MtcKmP Messages ...

Page 168: ...ider is not joining page 163 IOPn MtcKmP status Device I O control error page 164 IOPn MtcKmP status Error in Keyboard Pointer device configuration page 164 IOPn MtcKmP status Error setting keyboard indicators page 164 IOPn MtcKmP status Error setting keyboard typematic rate page 165 IOPn MtcKmP status Error writing to the Registry page 165 IOPn MtcKmP status Invalid Registry parameter Using defau...

Page 169: ...inter MtcKmP Messages IOPn MtcKmP status Unconsumed pointer input discarded page 168 IOPn MtcKmP status Unsupported or invalid 16h Keyboard BIOS request page 168 Table 11 1 Keyboard and Pointer Message Summary Continued Message Page ...

Page 170: ...y resource errors a provider response timeout or a provider protocol version mismatch Memory allocation failures When this message occurs the event log dump contains an additional Windows NT status code Related Messages In the IOP event logs IOPn MtcKmP status Keyboard pointer Redirector Provider protocol version mismatch Action Check the IOP event log for Keyboard Pointer Provider errors Because ...

Page 171: ... mouse class drivers View the event data as Words The last longword 4 bytes of data should contain a Windows NT error code that can be used by your service provider to help diagnose the problem Invalid Registry parameter Using default value Severity Warning Source MtcKmR Description This is a warning indicating that an illegal value was defined in the CE Registry under Services MtcKmR Parameters A...

Page 172: ...by the Keyboard Pointer Provider View the message data as Words The last longword 4 bytes of data contains the number of keyboard input packets discarded If this error occurs frequently contact your service provider for assistance Unconsumed pointer input discarded Severity Warning Source MtcKmR Description The Keyboard Pointer Redirector provides input to the pointer mouse class driver Normally t...

Page 173: ...Keyboard Pointer Provider will not register with the HP NetServer AA Device Synchronization Layer DSL Action View the message data as Words The last longword 4 bytes of data should contain a Windows NT error code that can be used by your service provider to help diagnose the problem IOPn MtcKmP status A join response was received but the provider is not joining Severity Error Description The Keybo...

Page 174: ...diagnose the problem Note The only method of enabling a failed keyboard or pointer device is to correct the problem and reboot the IOP IOPn MtcKmP status Error in Keyboard Pointer device configuration Severity Error Description This is a fatal initialization error It occurs when the Input Provider cannot register with the HP NetServer AA Device Synchronization Layer DSL The most likely cause is th...

Page 175: ...ry so that user preferences can be restored During IOP joining the user preferences from the merging IOP are set in the joining IOP s Registry Action Unless this error occurs frequently it can be ignored Otherwise view the message data as Words The last longword 4 bytes of data should contain a Windows NT error code that can be used by your service provider to help diagnose the problem IOPn MtcKmP...

Page 176: ...t the keyboards are identical Make sure that keyboards on all IOPs are plugged in IOPn MtcKmP status Keyboard Pointer Co Provider protocol version mismatch Severity Error Description This error is caused by installing incompatible versions of the Keyboard Pointer Provider on the IOPs Action Reboot the IOPs in Offline HP NetServer AA I O Processor Mode and reinstall the HP NetServer AA IOP software...

Page 177: ...IOP to IOP messages If the merging Provider becomes unavailable prior to completing the join that Provider times out causing its input devices to fail IOPn MtcKmP status Timeout waiting for join response from active input provider Severity Error Description During the IOP join process the Keyboard Pointer Providers on each IOP exchange device and state information This requires exchanging a number...

Page 178: ...r the frequency of this warning as well as the error counters maintained by the Keyboard Pointer Provider If this error occurs frequently contact your service provider for assistance IOPn MtcKmP status Unsupported or invalid 16h Keyboard BIOS request Severity Informational Description The Keyboard Pointer Provider emulates keyboard BIOS requests during CE boot All standard INT 16h BIOS requests ar...

Page 179: ...ssages that are written to the Windows NT event log This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions This chapter includes the following sections IOPn MtcMICX Message Summary 170 IOPn MtcMICX Messages 171 12 MtcMICX Messages ...

Page 180: ... driver initialization page 176 IOPn MtcMICX MtcMICX has detected an unrecoverable error and has shut down operations The IOP will be rebooted to recover page 176 IOPn MtcMICX MtcMICX resources have not been returned following a port transition The system will be rebooted to recover page 177 IOPn MtcMICX Port state change failed to change the state to the required setting page 177 IOPn MtcMICX Por...

Page 181: ...table lists the corrective actions for the specific error codes Action View the event detail as Words and find the last word which indicates the error code Refer to Figure 12 2 for an example of event detail indicating the error code Note Data prior to the last word containing the error code may provide additional information but the specific error code is always listed in the last word The descri...

Page 182: ...essages 172 Figure 12 2 shows an example of event detail that indicates the error code in the last word when viewed as Words Figure 12 2 Example of MICX Event Detail Viewed as Words The last word indicating the error code ...

Page 183: ...thernet buffer allocation failure 06 Large Ethernet buffer allocation failure 07 Small general pool buffer allocation failure 08 Medium general pool buffer allocation failure 09 Large general pool buffer allocation failure 0A Double buffer allocation failure 0B Scan buffer allocation failure 20 Must succeed data buffer allocation failure 21 DMA lists or descriptors allocation failure 22 Dynamic DM...

Page 184: ...e BIOS setup program 10 MIC is in loopback mode The MIC adapter is in loopback mode MtcMICX will not register with the HP NetServer AA Monitor until the MIC is removed from loopback mode Remove the loopback connector from the MIC module and attach the fiber cables to the MIC module 12 Cannot create device Could not create an object for the MIC adapter with IoCreateDevice The status code returned b...

Page 185: ...adapter is properly installed Verify that the MIC is running the firmware that is shipped with the version of the HP NetServer AA software that is running on the IOP Reinstall the HP NetServer AA software on the IOP Replace the MIC adapter and install the proper firmware on the new adapter If the problem persists contact your service provider for assistance 16 Cannot initialize timeouts 17 Cannot ...

Page 186: ...sed MtcMICX to stop processing requests The actual error has been logged to the Windows NT event log prior to this message Action Refer to the corrective actions for the messages that occurred prior to this message The HP NetServer AAsoftware automatically reboots the IOP 1D Cannot initialize adapter MtcMICX was not able to initialize the MIC adapter Note The status code returned by the MIC initia...

Page 187: ...ting Severity Error Description MtcMICX attempted to change the state of the MIC port but the new port state did not match the requested port state This probably indicates a hardware error however an internal software error can also cause this problem The additional data specifies the MIC port number where the problem occurred Action The HP NetServer AA software automatically reboots the IOP IOPn ...

Page 188: ...ts from the MIC before allowing the IOP to join in the configuration This probably indicates a hardware error however an internal software error can also cause this problem The additional data specifies the MIC port number where the problem occurred Action The IOP should reboot automatically If it does not do so or if this error recurs contact your service provider for assistance ...

Page 189: ...ndler status messages FRU messages and Endurance Monitor status messages This chapter assumes that you are familiar with Endurance terminology and message conventions This chapter includes the following sections IOPn MtcMon Message Summary 180 IOPn MtcMon Fault Handler Status Messages 190 IOPn MtcMon FRU Messages 201 IOPn MtcMon Status Messages 213 13 MtcMon Messages ...

Page 190: ...fficient system resources to provide a complete event history Removed Units x page 194 IOPn MtcMon Fault Handler status Fault event processing completed but there were insufficient system resources to provide a complete event history Removed Units x page 195 IOPn MtcMon Fault Handler status Fault information dump page 195 IOPn MtcMon Fault Handler status Fault information log is not open page 196 ...

Page 191: ...bility failure page 204 IOPn MtcMon FRU IOPx CEy cross tuple fault page 205 IOPn MtcMon FRU IOPx CEy interconnect fault page 206 IOPn MtcMon FRU IOPx IOP IOP Link IL netcard capability cabling or remote netcard page 206 IOPn MtcMon FRU IOPx CEy tuple power supply failure page 207 IOPn MtcMon FRU IOPx CEx tuple processing capability failure page 207 IOPn MtcMon FRU Local hardware fault on IOPx page...

Page 192: ...or was detected on IOPx during IOP joining page 219 IOPn MtcMon status An Endurance Manager command has been issued to disable CEx page 219 IOPn MtcMon status An Endurance Manager command has been issued to disable IOPx page 220 IOPn MtcMon status An Endurance Manager command has been issued to disable Tuplex page 221 IOPn MtcMon status An Endurance Manager command has been issued to remove CEx pa...

Page 193: ...ion module file could not be opened page 232 IOPn MtcMon status CE boot or synchronization could not be performed because the 16 bit platform specific initialization module file is corrupt page 232 IOPn MtcMon status CE operating system shutdown has been requested by the operator page 233 IOPn MtcMon status CE synchronization cannot be performed at this time The operation will be retried at a late...

Page 194: ...synchronized because auto synch is set to FALSE on IOPy page 241 IOPn MtcMon status CEx could not be synchronized because the Endurance System Management Service running on the CE operating system is not yet active page 242 IOPn MtcMon status CEx did not obtain the memory controller type The presence of ECC or parity memory cannot be determined page 242 IOPn MtcMon status CEx failed to inhibit IPM...

Page 195: ...x could not be shut down or disabled because it is the only active IOP and one or more CEs are active Shut down the Windows NT operating system on the CEs first page 254 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 page 255 IOPn MtcMon status IOPx ha...

Page 196: ... memory detected on CEx Chipset vendor chipset Memory mode mode IPMI found Y N page 267 IOPn MtcMon status Removing CEx so crash dump can proceed with only one active CE page 267 IOPn MtcMon status Server shutdown has been requested by the operator page 268 IOPn MtcMon status The active CEs were removed because the boot device is no longer accessible page 269 IOPn MtcMon status The boot conflict c...

Page 197: ...ch CE1 MIC bus ID x CE2 MIC bus ID y page 277 IOPn MtcMon status The CE MIC FPGA revisions do not match CE1 MIC FPGA revision 0xx CE2 MIC FPGA revision 0xy page 278 IOPn MtcMon status The CE MIC microcode edit levels do not match CE1 MIC microcode revision 0xx CE2 MIC microcode revision 0xy page 278 IOPn MtcMon status The CE MIC microcode revisions are not compatible CE1 MIC microcode revision 0xx...

Page 198: ...tus The MIC Transport driver MtcMICX has not yet registered with the Monitor page 286 IOPn MtcMon status The Monitor is waiting for all required interconnects to become available page 287 IOPn MtcMon status The Monitor s ClientList value in the Windows NT Registry is invalid page 287 IOPn MtcMon status The number of CE CPU processors does not match CE1 CPU count x CE2 CPU count y page 288 IOPn Mtc...

Page 199: ... size y kilobytes CE2 memory size z kilobytes page 291 IOPn MtcMon status The Windows NT operating system on the active CE s has been shut down by bugcheck page 291 IOPn MtcMon status The Windows NT operating system on the active CE s has been shut down due to a system failure page 292 Table 13 1 IOPn MtcMon Messages Continued Message Page ...

Page 200: ...ork cards or cabling It may also indicate a resource problem on one of the IOPs or a network card configuration error Related Messages None Action Examine the other messages in the event log that were logged at around the time of this failure to determine if there is an indication of netcard or network malfunction Check the network card configuration for the IOPlink cards on each IOP to make sure ...

Page 201: ...ndicates a hardware error Action You need not take any action if the error occurs infrequently less than once a week If the errors occur more frequently or if the number of memory errors reported is excessive more than 10 in any of these messages this may indicate an incipient problem in the memory subsystem and you should take corrective action as follows Run any memory diagnostics supplied with ...

Page 202: ...e frequently or if the number of errors reported is excessive more than 10 per message this may indicate an incipient motherboard failure and you should take corrective action as follows Run any system diagnostics supplied with your system to verify the correct functioning of the motherboard components If the problems persist replace the CE IOPn MtcMon Fault Handler status Error writing fault info...

Page 203: ...pleted but there were insufficient resources to provide a complete event history or log removed units Action Take action as appropriate for the messages that were indicated as part of the event 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 Informational D...

Page 204: ...es on the reporting IOP were severely constrained If possible free memory on the IOP by removing unneeded applications or services 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 Sever...

Page 205: ...nents were removed in response to the fault condition Separates consecutive fault handling messages in the log Related Messages IOPn MtcMon Fault handler status Fault event processing complete Removed units x Action An error is not explicitly indicated However this message indicates that the memory resources on the reporting IOP were severely constrained If possible free memory on the IOP by remov...

Page 206: ... opened for writing This error is not directly related to the fault condition being reported but it is indicative of a file system error on the reporting IOP Related Messages IOPn MtcMon Fault Handler status Fault information dump IOPn MtcMon Fault Handler status Error writing fault information to systemroot Config MtcFh hrl Action Run chkdsk or any other file system validation program to check th...

Page 207: ...IOPn MtcMon Fault handler status Fault information dump IOPn MtcMon Fault Handler status Received a bad Fault Handler control packet Severity Error Description During the join process the Fault Handler received a packet from the other IOP that was not recognizable or was improperly formatted This may indicate that the software revisions of the MtcMon components on the two IOPs are not compatible R...

Page 208: ...etwork packets or encounter network connectivity problems Severity Error Description The local IOP is receiving packets from an IOP other than one that is the opposite member of this Endurance system Because the network address used to route these packets is based on the Endurance kit number this indicates that there is another system on the local area network that has been installed with the same...

Page 209: ...n the remote IOP to determine why it rejected or failed to answer the join request issued by the Fault Handler on this IOP IOPn MtcMon Fault Handler status The joining IOP encountered an error or operator action that caused it to shut down before it completed the joining process Severity Error Description The local IOP encountered an error or an operator command that caused it to shut down during ...

Page 210: ...e due to network cabling problems between separate Endurance systems Related Messages IOPn MtcMon Fault Handler status The Fault Handlers have failed to exchange synchronization information during the merge process Action Check the network connections on the current system In particular check the IL connections to make sure that the IOP reporting the problem is connected to the other IOP in the sy...

Page 211: ...nectivity Test in the MIC BIOS utility to validate that the paths between the CE and the Endurance server are functioning properly Replace the MIC if it appears to be faulty IOPn MtcMon FRU CEx Power supply failure Variables x the ID of the CE with the power supply failure Severity Error Description The power supply to the specified CE was interrupted Action Make sure that the CE has not been powe...

Page 212: ...r cable gone indication or power gone indication Excessive disk or CPU load Action Use diagnostics to determine if the specified CE is functioning properly If this condition persists and no other component is faulted contact your service provider for assistance IOPn MtcMon FRU IOP operating system or subcomponent failure Severity Error Description An inconsistent system state was detected in both ...

Page 213: ...se s to a request made by the CE s operating system are different This may be due to either a software or hardware malfunction in an IOP or a difference in the disk data between members of a mirror set If the condition is due to mirror set differences then the removal and rejoining of an IOP selected for removal as part of this message causes both mirror sets to be equivalent If this message occur...

Page 214: ...Description The power supply to the specified IOP was interrupted Action Make sure that the IOP has not been powered off Check the power supply connections to the specified IOP Check the internal power supply function of the IOP Make sure that line voltage to the IOP is within operational parameters Replace the IOP MIC IOPn MtcMon FRU IOPx processing capability failure Variables x the ID of the IO...

Page 215: ... IOP report a fatal condition Usually this is the result of either A serious communication problem between the components A secondary fault in the component that occurred in one component while a fault was being handled for the other component Action Run the MIC Connectivity Test in the MIC BIOS utility between the IOP and the CE to ensure that the MIC adapters and the connections between them are...

Page 216: ...e condition persists Replace the cable between the CE and IOP MICs to determine if this cable is the source of the fault Replace the MIC on the CE and then the MIC on the IOP to determine if either MIC is the source of the fault IOPn MtcMon FRU IOPx IOP IOP Link IL netcard capability cabling or remote netcard Variables x the ID of the IOP removed from the Endurance server Severity Error Descriptio...

Page 217: ...on Severity Error Description This message is generated when both the CE and IOP in a tuple report a fatal condition Usually this is the result of A serious communication problem between the components A secondary fault that occurred in one unit while another one was being handled in the other unit This message encompasses all failures of both the IOP and CE within a single tuple except for power ...

Page 218: ...ginated from a CE but the details were not sufficient to determine which CE caused the condition Note The CE removed as a result of this error may not be the source of the fault The failure may have been caused by memory or other platform errors on a CE that were not detected at the time of the failure However in these cases you may often have previous errors either fatal or non fatal reported aga...

Page 219: ... message indicates a failure of The Windows NT operating system A device driver Other kernel level software Usually this means that both CEs crashed or a stop error with screen dump was encountered However it can also indicate a problem in which erroneous responses or requests are being generated by CE software that interferes with the system s ability to continue processing It may also be due to ...

Page 220: ...Ps to ensure that the connections are correct If this problem persists contact your service provider for assistance IOPn MtcMon FRU The MIC on I O Processor IOPx has detected a misconnected cable on its CEy port or the CEy MIC has had its ID set incorrectly Variables x the ID of the IOP that detected the misconnection y the ID of the IOP to CE port that is in error or the CE that has its MIC ID se...

Page 221: ... Software Double bit memory errors are most likely caused by faulty memory or memory with marginal timing characteristics However they can also be caused by memory controller or other motherboard problems Action Run any memory diagnostics supplied with your system to verify the correct functioning of the memory subsystem If the problem can be isolated to a particular memory component DIMM or SIMM ...

Page 222: ...hat the machine state may have been corrupted and the CE has been removed Related Messages IOPn MtcMon FRU Uncorrectable memory error on CEx IOPn MtcMon Fault Handler status CEx has reported n memory error s IOPn MtcMon Fault Handler status CEx has reported n platform error s Hardware Software This message indicates a hardware error Action Run any system diagnostics supplied with your system to ve...

Page 223: ... IOP and the CE A protocol error was detected during this message exchange This message is usually generated as a result of a hardware failure that occurred during the message exchange or a software error Related Messages IOPn MtcMon status The CE remove or disable operation failed IOPn MtcMon status CEx has been removed from service IOPn MtcMon status IOPx has been removed from service Action The...

Page 224: ...ailed is also generated It is also possible that a secondary message occurs that results in removing the CE or an IOP Report this message to your service provider IOPn MtcMon status A conflict was detected during CE boot with remote IOPx Variables x the ID of the remote IOP that is attempting to boot the CE Severity Warning Description This message is generated during CE boot when it is determined...

Page 225: ...a crash dump on system failures Note that all but one active CE is removed from service while the crash dump is being performed Related Messages IOPn MtcMon status Removing CEx so crash dump can proceed with only one active CE IOPn MtcMon status CEx has been removed from service Hardware Software This message is generated as a result of a hardware or software failure on the CE s that resulted in a...

Page 226: ...rked faulted Related Messages IOPn MtcMon status IOPx is faulted and requires repair Hardware Software This message reflects a problem with the Endurance server software components Action Examine the configuration information for the specified client for inconsistencies across IOPs Examine the event log for related messages from the client itself that provide more information regarding the nature ...

Page 227: ...ked faulted if the condition persists Related Messages IOPn MtcMon status IOPx is faulted and requires repair Hardware Software This message reflects a problem with the Endurance server software components Action Examine the configuration information for the specified client for inconsistencies across IOPs Also examine the event log for related messages generated by the client for additional infor...

Page 228: ...s not successful an IOP is faulted when the threshold is exceeded If this condition occurs in the absence of any related messages make sure that the Endurance server IOPs are using compatible software If the revisions are not compatible reinstall them if necessary If the condition persists contact your service provider for assistance IOPn MtcMon status A protocol error occurred with CEx while susp...

Page 229: ...ization This message is thresholded If the threshold is not exceeded the IOP joining process is retried If the retry is not successful an IOP is faulted when the threshold is exceeded If this condition occurs in the absence of any related messages make sure that the Endurance server IOPs are using compatible software If the revisions are not compatible reinstall them if necessary If the condition ...

Page 230: ...atus IOPx has been disabled by operator request IOPn MtcMon status IOPx has been removed from service IOPn MtcMon status The IOP shutdown or disable operation failed Hardware Software This message is generated as a result of a software operation Action No action is required unless this message is followed by IOPn MtcMon status The IOP shutdown or disable operation failed In this case see the messa...

Page 231: ...down IOPn MtcMon status The Tuplex shutdown or disable operation failed IOPn MtcMon status CE operating system shutdown has been requested by the operator IOPn MtcMon status The CE operating system shutdown request failed IOPn MtcMon status The Tuplex shutdown or disable operation failed IOPn MtcMon status IOPx is being shut down by operator request IOPn MtcMon status IOPx has been removed from se...

Page 232: ...eration failed for corrective action IOPn MtcMon status An Endurance Manager command has been issued to shut down IOPx Variables x the ID of the IOP to be shut down Severity Warning Description This message is generated as a result of issuing an IOP Shutdown command Related Messages IOPn MtcMon status IOPx is being shut down by operator request IOPn MtcMon status IOPx has been removed from service...

Page 233: ...Pn MtcMon status The Windows NT operating system on the active CE s has been shut down by operator request IOPn MtcMon status The Tuplex shutdown or disable operation failed IOPn MtcMon status CE operating system shutdown has been requested by the operator IOPn MtcMon status The CE operating system shutdown request failed IOPn MtcMon status The Tuplex shutdown or disable operation failed IOPn MtcM...

Page 234: ...om one that is not active Related Messages IOPn MtcMon status An Endurance Manager command has been issued to shut down IOPx IOPn MtcMon status An Endurance Manager command has been issued to disable IOPx Hardware Software This message is generated in response to issuing a command Action The IOP removal request failed Re issue the command from the remote IOP or the CE operating system If the local...

Page 235: ...use of either an internal Endurance Manager request or an Endurance Manager command and a subsequent CE shutdown is requested Related Messages IOPn MtcMon status An Endurance Manager command has been issued to shut down Tuplex IOPn MtcMon status An Endurance Manager command has been issued to disable Tuplex IOPn MtcMon status Server shutdown has been requested by the operator IOPn MtcMon status CE...

Page 236: ... the CE s Make sure that the CEs are operational and are running Windows NT Make sure that Endurance Manager is running on the CE s IOPn MtcMon status An error occurred activating Interconnect ESIx Variables x the ID of the ESI that had an error during activation Severity Error Description During IOP joining the ESI between the joining IOP and the CE experienced an error This message results in th...

Page 237: ...tServer AA Solution Administrator s Guide for information about how to reboot an IOP IOPn MtcMon status An error occurred loading the thresholding database on the joining IOP IOP initialization and joining will be retried Severity Error Description This message is generated during the IOP joining process that occurs when an IOP starts up An unexpected error occurred on the IOP that was joining the...

Page 238: ...boot an IOP IOPn MtcMon status An invalid BOOT REQUEST packet has been received from CEx Variables x the ID of the CE that generated an invalid boot request Severity Error Description The specified CE generated an invalid request to be booted or synchronized Hardware Software This message may be generated as a result of either a hardware failure or the incorrect revision of the MIC BIOS running in...

Page 239: ...er If the error threshold for the removed IOP is exceeded the IOP is faulted until you manually resolve the condition Related Messages IOPn MtcMon status IOPx is faulted and requires repair IOPn MtcMon status IOPx has been removed from service Hardware Software An Endurance server software error that never occurs in an Endurance server using identical software revisions on both IOPs Action Make su...

Page 240: ...sually this message is a result of a software error In rare cases it can be due to a hardware error that results in the corruption of data on an IOP or CE Action When this message is generated preserve the Fault Handler s event log information and examine it to gather additional information related to the message If the IOP is removed as a result of the event a crash dump may be generated If this ...

Page 241: ...ed to the message If the IOP is removed a crash dump may be generated Contact your service provider for assistance in the analysis of the crash dump IOPn MtcMon status CE boot failed because the Monitor s ConfigurationArcTree Registry entry on IOPx is invalid Variables x the ID of the IOP that is driving the CE boot Severity Error Description This message is generated during an attempt to boot the...

Page 242: ...t of a software configuration error Action Reinstall the Endurance software on the IOP that generated this event log entry IOPn MtcMon status CE boot or synchronization could not be performed because the 16 bit platform specific initialization module file is corrupt Severity Error Description The CE s 16 bit platform specific initialization module file is corrupt The IOP that generated this messag...

Page 243: ...The CE operating system shutdown request completed successfully IOPn MtcMon status The CE operating system shutdown request failed IOPn MtcMon status CEx has been removed from service Hardware Software This message signifies the beginning of a software driven system transition Action No action is required IOPn MtcMon status CE synchronization cannot be performed at this time The operation will be ...

Page 244: ...us CE synchronization process aborted due to time out Severity Error Description The CE synchronization aborted because the operation timed out The CE synchronization timeout is a factor of the memory sizes of the CEs Synchronization timeouts are typically the result of a failure of the synchronization slave CE Related Messages IOPn MtcMon status The synchronization process has started for CEx IOP...

Page 245: ...h the specified CE Severity Error Description The specified CE cannot be booted into the system configuration because the specified IOP is active and the CE is not in communication with it In some cases the IOP may be removed from the configuration so that the CE operating system can be booted Related Messages On the Remote IOP IOPn MtcMon status IOPx has been removed from service Hardware Softwar...

Page 246: ...ues to fail contact your service provider for assistance IOPn MtcMon status CEx cannot be booted by IOPy because the Monitor s ConfigurationArcTree Registry entry is invalid Variables x the ID of the CE that cannot be booted y the ID of the IOP that is attempting to drive the CE boot Severity Error Description This message is generated during an attempt to boot the Windows NT operating system on t...

Page 247: ... y the ID of the IOP that cannot communicate with the CE Severity Error Description The specified CE cannot be synchronized into the system configuration because the specified IOP is active and the CE is not in communication with it Hardware Software This message is generated in response to the failure of an Endurance System Interconnect usually due to a hardware malfunction Action Examine the End...

Page 248: ...a boot request issued by a CE because the SCSI hard disk that is the source of the boot is not online Usually when this message is generated the boot disk on the other IOP is online and can service the boot request This message can be expected if the SCSI hard disk is the target of an unfinished mirror set copy Related Messages IOPn MtcMon status The boot process has started for CEx Hardware Softw...

Page 249: ...join and this message is then generated when the CE attempts to boot Hardware Software This error indicates a problem with the Endurance software configuration Action Make sure that the Windows NT Registry ClientList parameter for the Endurance Keyboard Mouse Provider driver contains a value of 08 If 08 is not included reinstall Endurance server software on the IOP If the condition persists contac...

Page 250: ...nfigure the IOP or IOPs and reboot Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about how to reboot an IOP Examine the event log to determine if the Endurance SCSI Provider loaded properly and if appropriate repair any problems indicated The CE boots when the IOP reboots and has a properly loaded SCSI Provider IOPn MtcMon status CEx could not be removed or d...

Page 251: ... in this manner Instead perform a normal shutdown However if you desire to terminate the operating system in this manner specify the Operator Override option in the command syntax IOPn MtcMon status CEx could not be synchronized because auto synch is set to FALSE on IOPy Variables x the ID of the CE that could not be synchronized y the ID of the IOP that is driving the CE boot Severity Warning Des...

Page 252: ...ontrol Panel double click on Services and select and start the Endurance System Management Service Reinstall Endurance software on the CE IOPn MtcMon status CEx did not obtain the memory controller type The presence of ECC or parity memory cannot be determined Variables x the ID of the CE for which memory controller type information could not be obtained Severity Warning Description The CE softwar...

Page 253: ...f the CEs Hardware Software This message is generated as a result of CE hardware configuration information Action If you need help in determining whether you are using a qualified CE in your Endurance server contact your service provider IOPn MtcMon status CEx has been disabled by operator request Variables x the ID of the CE that has been disabled Severity Warning Description This message is gene...

Page 254: ...been removed Severity Informational Description The specified CE has been removed from the Endurance server The removal may occur as a result of either A system failure requiring the removal of the CE An Endurance Manager command A normal shutdown of the Windows NT operating system on the CE Related Messages IOPn MtcMon status CEx has been disabled by operator request IOPn MtcMon status CEx is fau...

Page 255: ...s Hardware Software This message is generated as a result of CE hardware configuration information Action No action is required IOPn MtcMon status CEx is available to be booted or synchronized Variables x the ID of the CE that is available for booting or synchronization Severity Informational Description The CE has completed power on self tests and is available to the local IOP to be booted or syn...

Page 256: ...has been removed from service Hardware Software This message is generated as a result of a software or hardware failure In most cases a hardware failure prevents you from using the CE Action Examine the event log for additional details about the reason for the failure If a hardware problem is indicated repair or replace any affected hardware as necessary If a software problem is indicated replace ...

Page 257: ...Pn 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 Hardware Software This message is generated as a result of a mismatch between the capabilities allowed by the Endurance software license and the CE s hardware configuration Action To synchronize the CEs perform one of the foll...

Page 258: ...er software configuration error or an Endurance server internal error Action The client ID specifies which Endurance software component could not be registered The Monitor s ClientList Registry parameter should be examined to determine if the given client should be registered with the Monitor If the client ID does not appear in this list it should be added to the list or it should not be loaded Re...

Page 259: ...pair Hardware Software This message is a result of a combined software and hardware configuration error The tuple ID of the IOP specified via the setup utility for the BIOS of the MIC modules in the specified IOP was set to the same value as the tuple ID of the IOP in the remote tuple and the software was also configured with the same IOP ID as the remote IOP Action Use the BIOS setup utility of t...

Page 260: ... both IOPs Manually clear the faulted state of the IOP by issuing an IOP Enable Operation command and rebooting the IOP Refer to Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about how to reboot an IOP IOPn MtcMon status Differences with IOPx s CE platform name were detected during IOP initialization Variables x the ID of the remote IOP Severity Error Description The ...

Page 261: ...e This message is generated as a result of a software configuration error Action Using the Endurance installation utility determine which IOP is configured with the correct license number On the other IOP reinstall the Endurance software specifying the same license number Enable the IOP Reboot the IOP and allow it to join the Endurance configuration IOPn MtcMon status ESIx has been enabled by oper...

Page 262: ...Ex has been removed from service Hardware Software This message is usually a result of a hardware failure Action Examine the event log for additional details about the reason for the failure Repair and or replace any faulty hardware as necessary Once you resolve the condition issue an ESI Enable Operation command The Endurance server attempts to reconfigure as required IOPn MtcMon status IL12 has ...

Page 263: ...r additional details about the reason for the failure Repair and or replace any faulty hardware as necessary Once you resolve the condition issue an IL12 Enable Operation command The Endurance server attempts to reconfigure as required IOPn MtcMon status IOPx cannot be shut down because it is already offline Variables x the ID of the IOP that cannot be shut down Severity Warning Description This m...

Page 264: ...ared and the specified IOP automatically rejoins the Endurance server IOPn MtcMon status IOPx could not be shut down or disabled because it is the only active IOP and one or more CEs are active Shut down the Windows NT operating system on the CEs first Variables x the ID of the IOP that could not be shut down or disabled Severity Warning Description This message is generated in response to an IOP ...

Page 265: ... Action In this case the specified IOP cannot be removed because it would result in abnormal termination of the CE operating system since the boot disk would no longer be accessible Instead shut down Windows NT on the CE then disable or shut down the IOP Optionally allow the mirror copy of the boot disk to complete or repair the disk on the other IOP if necessary then disable or shut down the IOP ...

Page 266: ...nformational Description The specified IOP was removed from the Endurance server The removal may occur as a result of either A failure that requires the removal of the IOP An Endurance Manager or MTCCONS command A normal shutdown of the Windows NT operating system on the IOP Related Messages IOPn MtcMon status IOPx has been disabled by operator request IOPn MtcMon status IOPx is faulted and requir...

Page 267: ... began 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 been successfully initialized IOPn MtcMon status IOPx initialization failed Hardware Software A software process started Action No action is required IOPn MtcMon status IOPx has begun the IOP joining process Variab...

Page 268: ...specified IOP successfully completed the IOP joining process and is now an active part of the Endurance server configuration The joining process occurs immediately after the IOP is booted the Endurance software loads and initializes and IOP initialization is performed Related Messages IOPn MtcMon status IOPx has begun the joining process Hardware Software A software process completed Action No act...

Page 269: ...uld not be determined during IOP initialization IOPn MtcMon status IOPx could not be joined because it is configured to not automatically initialize IOPn MtcMon status A protocol error occurred on IOPx during IOP initialization IOPn MtcMon status IOPx is unavailable for initialization because it is currently faulted IOPn MtcMon status IOPx is unavailable for initialization because it is currently ...

Page 270: ... without need for user intervention If the problem persists the IOP will be marked faulted If this occurs contact your service provider for assistance IOPn MtcMon status IOPx is being shut down by operator request Variables x the ID of the IOP that is being shut down Severity Warning Description This message is generated when the Endurance software initiates a shutdown of an IOP This shutdown can ...

Page 271: ...roblem is indicated repair or replace the affected hardware as necessary If a software problem is indicated replace the software component or reconfigure it as necessary Once you resolve the condition issue an IOP Enable Operation command The Endurance server attempts to reconfigure the IOP IOPn MtcMon status IOPx is OFFLINE because the NOMTC switch is present in BOOT INI Variables x the ID of the...

Page 272: ... Link is physically connected and that the Endurance software is properly configured using the same K number and running The state of the IOP Link IL12 transitions to online when both IOPs are configured properly If the remote IOP is not available because it is broken or cannot run boot the Endurance server by setting the remote IOP to disabled from the local IOP or by setting the AUTO START flag ...

Page 273: ...curred due to a software or a hardware error Action Examine the event logs to determine the reason that the IOP was previously faulted Enable the IOP by issuing an IOP Enable Operation command IOPn MtcMon status IOPx joining has been aborted because the thresholding database was modified IOP initialization and joining will be retried Variables x the ID of the IOP whose joining has been aborted Sev...

Page 274: ...OPn MtcMon status The boot process has started for CEx IOPn MtcMon status The synchronization process has started for CEx IOPn MtcMon status An error occurred activating Interconnect ESIx IOPn MtcMon status IOPx was removed because it failed to activate the CE Interconnect s Hardware Software This message is typically generated as a result of a hardware error on the specified IOP or an Interconnec...

Page 275: ...tcMon status The boot process has started for CEx IOPn MtcMon status The synchronization process has started for CEx IOPn MtcMon status An error occurred activating Interconnect ESIx IOPn MtcMon status IOPx was removed at the direction of IOPy Hardware Software This message is typically generated as a result of a hardware error on the Interconnect Action On the IOP reported in this message use the...

Page 276: ...e Interconnect between the specified IOP and the CEs Manually repair the Interconnect and allow the IOP to rejoin the configuration IOPn MtcMon status Monitor initialization failed on the local IOP Severity Error Description The Monitor could not initialize The IOP is not activated Hardware Software This message occurs as a result of a software problem Action This message is generated as a result ...

Page 277: ...rver contact your service provider IOPn MtcMon status Removing CEx so crash dump can proceed with only one active CE Variables x the ID of the CE being removed Severity Warning Description The Windows NT operating system running on the CE s has crashed and is attempting to generate a crash dump This occurs if Windows NT initiates a crash dump and you configured Windows NT to generate a crash dump ...

Page 278: ...em on the active CE s has been shut down by operator request IOPn MtcMon status CE operating system shutdown has been requested by the operator IOPn MtcMon status The CE operating system shutdown request failed IOPn MtcMon status The CE operating system shutdown request completed successfully IOPn MtcMon status The CE remove or disable operation failed IOPn MtcMon status CEx has been removed from ...

Page 279: ...sage follows the message IOPn MtcMon status A conflict was detected during CE boot with remote IOPx and indicates that two IOPs are both attempting to boot the same CE Related Messages IOPn MtcMon status A conflict was detected during CE boot with remote IOPx IOPn MtcMon status The boot process failed for CEx IOPn MtcMon status IOPx is faulted and requires repair Hardware Software The Endurance ha...

Page 280: ...rocess does not succeed this message is generated Related Messages IOPn MtcMon status The boot process has started for CEx IOPn MtcMon status CEx has been removed from service IOPn MtcMon status CEx could not be booted because the boot device is not available on IOPx IOPn MtcMon status A conflict was detected during CE boot with remote IOPx IOPn MtcMon status A conflict was detected during CE boot...

Page 281: ...ed as a result of a software configuration error Action Reinstall the Endurance software on the IOP that generated this event log entry When prompted be sure to specify the hardware platform that matches the CE hardware type If the problem persists record the error information displayed on the CE during boot and contact your service provider for assistance IOPn MtcMon status The boot process has s...

Page 282: ... CEs Action Make sure that both CEs are using MICs with identical revision levels If not replace one or both of the MICs See Chapter 9 in HP NetServer AA Solution Administrator s Guide for information about replacing MICs Make sure that the following MIC information is identical for each CE BIOS revision Microcode revision FPGA revision Run the MTCFLASH Utility to update any that are not identical...

Page 283: ...ation Note that the CPUs must all match in family model and stepping specifications IOPn MtcMon status The CE CPU ID 0xx internal caches do not match Variables x the ID of the incompatible CPUs Severity Error Description The specified CPU contains inconsistent cache configurations across the two CEs This may indicate a difference in processors CE synchronization cannot be performed until this cond...

Page 284: ... CPUx with a CPU with identical power on settings to CPUx in the active CE Power down both CEs and replace CPUx in both CEs with CPUs with identical power on settings IOPn MtcMon status The CE CPU ID 0xx speeds do not match CE1 CPU speed y MHz CE2 CPU speed z MHz Variables x the ID of incompatible CPUs y the CPUx speed in CE1 z the CPUx speed in CE2 Severity Error Description The CPU speeds for CP...

Page 285: ...ersion to CPUx in the active CE Power down both CEs and replace CPUx in both CEs with CPUs with identical versions IOPn MtcMon status The CE CPUx model and or family types are not compatible CE1 CPU ID register 0xy CE2 CPU ID register 0xz Variables x the ID of the incompatible CPUs y the contents of the Intel Pentium CPU ID register of CE1 z the contents of the Intel Pentium CPU ID register of CE2...

Page 286: ...dically removed from service it may be necessary to replace one or both CE motherboards so that both CE motherboards contain Intel Pentium processors that have identical family numbers model numbers and stepping IDs IOPn MtcMon status The CE MIC BIOS revisions are not compatible CE1 MIC BIOS revision x CE2 MIC BIOS revision y Variables x the revision of the MIC module BIOS in CE1 y the revision of...

Page 287: ...er AA Solution Administrator s Guide If this does not resolve the problem contact your service provider for assistance IOPn MtcMon status The CE MIC bus IDs do not match CE1 MIC bus ID x CE2 MIC bus ID y Variables x the bus ID of the MIC module in CE1 y the bus ID of the MIC module in CE2 Severity Error Description The bus IDs of the CE MICs do not match The CE MICs must use the identical bus and ...

Page 288: ...evision of the MIC adapter microcode in CE1 y the revision of the MIC adapter microcode in CE2 Severity Warning Description The edit level field of the MIC adapter microcode revision information in CEs 1 and 2 does not match While the CEs will be allowed to synchronize this situation should be corrected to eliminate any potential for unexpected behavior between the CEs Hardware Software This messa...

Page 289: ...ministrator s Guide for information about using MTCFLASH IOPn MtcMon status The CE MIC module edit levels do not match CE1 MIC module revision 0xx CE2 MIC module revision 0xy Variables x the revision of the MIC adapter in CE1 y the revision of the MIC adapter in CE2 Severity Warning Description The edit level field of the MIC adapter revision information in CEs 1 and 2 does not match While the CEs...

Page 290: ...ator s Guide for information about replacing a MIC IOPn MtcMon status The CE MIC PCI base addresses x do not match CE1 PCI base address 0xy CE2 PCI base address 0xz Variables x the index into the PCI base address array y the PCI device address of the MIC adapter in CE1 z the PCI device address of the MIC adapter in CE2 Severity Error Description The message indicates that the MIC adapters in the C...

Page 291: ...dapters so that they are in the same slots and are assigned the same PCI device address IOPn MtcMon status The CE MIC PCI interrupt assignments do not match CE1 PCI interrupt information 0xx CE2 PCI interrupt information 0xy Variables x the PCI interrupt information of the MIC adapter in CE1 y the PCI interrupt information of the MIC adapter in CE2 Severity Error Description The message indicates ...

Page 292: ... message is generated because a software condition exists in the CE operating system which requires a reboot of the operating system to resolve Action Disable the CE debug environment and reboot the CE operating system IOPn MtcMon status The CE operating system cannot be synchronized The CE hardware platform is not supported Severity Error Description The CE operating system cannot be synchronized...

Page 293: ...rating system on the CE for this version of Endurance software Refer to the HP NetServer AA 6200 Solution Release Notes Release 3 0 Service Pack 1 for information about versions of the Windows NT operating system supported by this version of Endurance software Reboot the CE operating system IOPn MtcMon status The CE operating system could not be suspended to perform a system transition Severity Er...

Page 294: ... process Action Unless this error occurs frequently you can ignore it Otherwise view the message data as Words The last longword 8 bytes of data should contain a Windows NT error code that can be used by your service provider to help diagnose the problem IOPn MtcMon status The CE1 and CE2 PCI configurations do not match Severity Error Description The PCI configurations of the two CEs do not match ...

Page 295: ...t driver did not load Correct the condition as required If no related events are logged examine the software configuration to determine why the Ethernet Transport driver did not load Reconfigure the software on the IOP if necessary If the problem persists contact your service provider for assistance IOPn MtcMon status The identity of the CE s 16 bit platform specific initialization module in the R...

Page 296: ...has not successfully loaded and registered with the Monitor within the IOP startup interval two minutes The local IOP cannot join the Endurance configuration until the MIC driver registers with the Monitor Related Messages IOPn MtcMon status The IOP ID supplied by the MIC driver does not match the IOP ID of the local IOP MIC Driver IOP ID x Local IOP ID y IOPn MtcMon status The Endurance config in...

Page 297: ...the Endurance software on the IOP that reports this event If the problem persists contact your service provider for assistance IOPn MtcMon status The Monitor s ClientList value in the Windows NT Registry is invalid Severity Error Description The Monitor s Registry parameter value ClientList is not valid This occurs if either of the following conditions is true The length in bytes of the value is t...

Page 298: ...rom the CEs so that the number of CPUs exactly matches in the two CEs IOPn MtcMon status The number of CE CPU processors is not compatible CE1 CPU count x CE2 CPU count y Variables x the number of CPUs in CE1 y the number of CPUs in CE1 Severity Error Description The number of CPUs in CE1 does not match the number of CPUs in CE2 The CE attempting to synchronize cannot be synchronized unless it has...

Page 299: ...d on the IOPs Contact your service provider and purchase an Endurance license that allows the specified number of CPUs to be supported in the Endurance configuration Reinstall the Endurance software using this new license on both IOPs and the CEs IOPn MtcMon status The synchronization process has failed for CEx because the 16 bit platform initialization did not complete successfully Variables x th...

Page 300: ...memory and install additional memory IOPn MtcMon status The synchronizing CE s memory size is less than the size of memory in use by Windows NT Windows NT memory size y kilobytes CEx memory size z kilobytes Variables x the ID of the synchronizing CE y the size in kilobytes of memory in use by Windows NT on the active CE z the size in kilobytes of memory in CEx Severity Error Description The size o...

Page 301: ...OPn MtcMon status The Windows NT operating system on the active CE s has been shut down by bugcheck Severity Error Description This message indicates that the Windows NT operating system running on the CE was shut down due to a stop error with screen dump Related Messages IOPn MtcMon status A crash dump is being taken for the Windows NT operating system running on the CEs IOPn MtcMon status CEx ha...

Page 302: ...ing system did not perform an orderly and graceful system shutdown Related Messages IOPn MtcMon status CEx has been removed from service Hardware Software The Windows NT operating system running on the CE was shut down due to a hardware or software failure on the CE s Action The CE operating system automatically reboots unless it has experienced enough failures to exceed the Marathon threshold In ...

Page 303: ...MtcScsiP and SCSI Redirector MtcScsiR status messages This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions This chapter includes the following sections MtcScsiP and MtcScsiR Status Message Summary 294 IOPn MtcScsiP Status Messages 302 IOPn MtcScsiR Status Message 352 14 MtcScsiP and MtcScsiR Mes sages ...

Page 304: ...k remapping during mirror copy for DISKn is disabled page 304 IOPn MtcScsiP status Bad block remapping during mirror copy for DISKn is enabled page 304 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 page 305 IOPn MtcScsiP status Bad block remapping is already turned off for this mir...

Page 305: ...until this problem is resolved page 310 IOPn MtcScsiP status Copy for selected disk has not failed page 310 IOPn MtcScsiP status Device DISKn has failed See prior events for reason page 310 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 page 311 IOPn MtcScsiP status DEVICEn has a SCSI...

Page 306: ...n could not be enabled Check prior events for reason page 316 IOPn MtcScsiP status DISKn did not come ready and it will be marked offline page 317 IOPn MtcScsiP status DISKn did not power up properly and it will be marked offline page 317 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 parti...

Page 307: ...r AA system ID other than the current system ID This indicates DISKn has come from a completely different HP NetServer AA system The HP NetServer AA partition can be reset to cure this condition but caution is advised If unsure how to proceed contact your service provider for assistance page 324 IOPn MtcScsiP status DISKn has an invalid HP NetServer AA partition type Use the HP NetServer AA Manage...

Page 308: ...compliant page 329 IOPn MtcScsiP status DISKn member in the other IOP is remapping bad blocks encountered during mirror copy Mirror copy timeout was ignored page 329 IOPn MtcScsiP status DISKn mirror set is up to date This message may occur during IOP join when both CEs are down or whenever a disk is enabled page 330 IOPn MtcScsiP status DISKn must be offline HP NetServer AA Manager request ignore...

Page 309: ...ge 335 IOPn MtcScsiP status Mirror set copy from IOPn to IOPn for DISKx has halted due to a copy write failure to local IOP s DISKn page 335 IOPn MtcScsiP status Mirror set copy from IOPn to IOPn for DISKx has halted The local IOP lost access to DISKn page 336 IOPn MtcScsiP status Mirror set copy from IOPn to IOPn for DISKx has halted The local IOP was unable to send a packet to the other IOP or t...

Page 310: ... Unable to find a configured boot disk Use the HP NetServer AA Configuration Utility to add a boot disk or mark an existing disk as bootable page 342 IOPn MtcScsiP status Unable to flush cache for DISKn page 343 IOPn MtcScsiP status Unable to get provider information from Registry Contact your service provider for assistance page 343 IOPn MtcScsiP status Unable to locate detected bad block for DIS...

Page 311: ...not failed HP NetServer AA Manager request to restart the mirror copy was ignored page 349 IOPn MtcScsiP status Unable to shut down DISKn gracefully page 349 IOPn MtcScsiP status Unable to write HP NetServer AA partition for DISKn page 349 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 Man...

Page 312: ... administrator is attempting to enable bad block remapping for the specified disk Action No action is required IOPn MtcScsiP status Administrator is attempting to reset DISKn s HP NetServer AA partition Variables n the disk number for example DISK0 DISK1 DISK2 Severity Informational Description The administrator is attempting to reset the specified disk s HP NetServer AA partition using the HP Net...

Page 313: ...d automatically making them available for use If the CE boot disk mirror set is not current then a failover is not possible You must restore the faulted disk from backup as follows Using Windows NT Disk Administrator in Offline HP NetServer AA I O Processor Mode reformat the disk Do not select the Quick Format option when formatting Formatting without Quick Format will cause any sectors with bad s...

Page 314: ...nabled IOPn MtcScsiP status Bad block remapping during mirror copy for DISKn is disabled Variables n the disk number for example DISK0 DISK1 DISK2 Severity Warning Description The administrator has used the HP NetServer AA Manager to disallow the bad block remapping for diskn If and when it acts as the mirror copy source disk any bad blocks that are encountered cause the mirror copy to fail Action...

Page 315: ... bad block remapping However bad block remapping was already disabled so the operation was ignored Action No action is required IOPn MtcScsiP status Bad block remapping is already turned on for the DISKn mirror set HP NetServer AA Manager request to turn on bad block remapping was ignored Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description The administrator attempt...

Page 316: ...ver AA Manager However the disk cannot be accessed for the desired operation Action Check the event log for previous messages that indicate why the disk is not accessible for the desired operation IOPn MtcScsiP status Cannot disable write cache for DISKn This disk type may have exhibited problems with write cache This feature should be disabled to prevent corruption problems It is strongly recomme...

Page 317: ...2 Severity Informational Description The SCSI Provider requests SCSI cache mode page data from disk controllers SCSI cache mode page data contains disk characteristics and configuration information Many RAID adapters do not provide this information for the disks included in their configurations This information is not required for correct operation Action No action is required IOPn MtcScsiP status...

Page 318: ...or the disks included in their configurations This information is not required for correct operation Action No action is required IOPn MtcScsiP status CDROMn may not be SCSI 2 or newer SCSI standard compliant Variables Cdromn the CD ROM number either CD ROM1 or CD ROM2 Severity Warning Description The IDE CD ROM device is not recognized as a SCSI 2 or newer compliant device Action No action is req...

Page 319: ...escription HP NetServer AA SCSI software requested the specified SCSI adapter to reset its SCSI bus However the reset request did not succeed Any disks connected to this adapter may fail read or write requests causing the disks to be marked as faulted However it is unlikely that any particular disk may actually have failed Action Make sure SCSI termination and cabling is correct If a problem persi...

Page 320: ... the IOP begins booting use the SCSI adapter s BIOS configuration software to set the initiator ID of the SCSI adapter s bus to the same value used for the adapter in the remote IOP IOPn MtcScsiP status Copy for selected disk has not failed Severity Error Description An attempt was made to use the HP NetServer AA Manager to restart a mirror copy that has not failed This is not allowed Action No ac...

Page 321: ...fferent than configured on the other IOP and it will be marked offline Variables n the device number for example DISKn CDROMn TAPEn Severity Error Description A configured SCSI adapter for the device on the local IOP does not match the configured adapter number for the device on the remote IOP Action Use the HP NetServer AA Configuration Utility to fix the configuration files on each IOP so that t...

Page 322: ...rget ID different than configured on the other IOP and it will be marked offline Variables n the device number for example DISKn CDROMn TAPEn Severity Error Description A configured target ID for the device on the local IOP does not match the configured target ID for the device on the remote IOP Action Use the HP NetServer AA Configuration Utility to fix the configuration files on each IOP so this...

Page 323: ...bles n the device number for example DISKn CDROMn TAPEn Informational Description A configured device has been found and appears to have powered up without problems Action No action is required IOPn MtcScsiP status DEVICEn was not found and it will be marked offline Variables n the device number for example DISKn CDROMn TAPEn Severity Error Description No device at a configured SCSI address was fo...

Page 324: ...le the specified disk However the disk was already disabled so the operation was ignored Action No action is required IOPn MtcScsiP status Disk is already online Severity Error Description An attempt was made to enable a disk using the HP NetServer AA Manager but the disk was already online Action No action is required IOPn MtcScsiP status Disk must be offline Severity Error Description An attempt...

Page 325: ...ariables n the disk number for example DISK0 DISK1 DISK2 Severity Warning Description There are a variety of reasons for the inability to physically access a disk For example it could be misconfigured it could be powered off or it may have failed Action Review the event log looking for previous messages that describe the reason why the disk cannot be accessed IOPn MtcScsiP status DISKn contains an...

Page 326: ...et IOP number either IOP1 or IOP2 y the source IOP number either IOP1 or IOP2 Severity Error Description HP NetServer AA SCSI software does not honor an installation of HP NetServer AA software to the target disk of a mirror copy HP NetServer AA SCSI software detected a target disk only installation The target disk will be kept offline until the installation problem is corrected Action Reboot the ...

Page 327: ...ails power cycle the IOP to attempt to clear the condition If the condition persists it may be time to replace the disk or contact your service provider for assistance IOPn MtcScsiP status DISKn did not power up properly and it will be marked offline Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description A disk did not appear to power up properly This may occur for a ...

Page 328: ... for recoverable read requests Variables n the disk number for example DISK0 DISK1 DISK2 Severity Informational Description The disk does not support automatic bad block remapping for read requests Hence if the disk encounters a bad block during a read request the disk will not automatically remap the bad block Instead the read would fail and software would request a bad block remap Action No acti...

Page 329: ...us DISKn encountered a write error during a mirror copy Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description The specified mirror copy target disk encountered a write error during a mirror copy Action Reboot the IOP that contains the disk that experienced the write error Reformat any data partitions not the HP NetServer AA partition on the disk Note Do not quick for...

Page 330: ...ill cause any sectors with bad spots to be remapped making them available for use Do not repartition the disk unless the partition table itself has a bad spot Do not attempt to format the HP NetServer AA partition Apply backup data after the data partition s have been reformatted Boot the IOP in Operational HP NetServer AA I O Processor Mode Note The previously faulted disk will still be marked as...

Page 331: ...rious reasons A reset can occur because the partition contained invalid data and the administrator chose to reset the partition using the HP NetServer AA Manager Additionally a reset will occur after a disk is added to the HP NetServer AA configuration Whenever the HP NetServer AA partition is reset a mirror copy will occur at the next possible opportunity Under most circumstances the disk with th...

Page 332: ...ariables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description A disk that belongs at another SCSI address has been moved to the current SCSI address The disk must have its HP NetServer AA partition reset if it is to be used in the local HP NetServer AA system However if the disk s HP NetServer AA partition is reset it is very likely that it will become a mirror copy target ca...

Page 333: ... NetServer AA Solution Administrator s Guide for details on repartitioning a mirrored disk IOPn MtcScsiP status DISKn has an HP NetServer AA partition which is too big Use Disk Administrator in Offline HP NetServer AA I O Processor Mode to repartition the HP NetServer AA partition Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description HP NetServer AA partitions must b...

Page 334: ...if a replacement disk has been taken from elsewhere and used to replace a faulted disk In this case assuming the CEs are up and running you can reset the disk s HP NetServer AA partition and it will become a mirror copy target However if this scenario is not desirable or the CEs are not up and running contact your service provider before continuing IOPn MtcScsiP status DISKn has an invalid HP NetS...

Page 335: ...stance Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description A disk that belongs to another IOP has been moved to the local IOP The disk must have its HP NetServer AA partition reset if it is to be used in the local HP NetServer AA system However if the disk s HP NetServer AA partition is reset it is very likely that it will become a mirror copy target causing any st...

Page 336: ...isk controllers that are suspected of not handling them properly The SCSI feature disconnects was disabled for this controller Use of SCSI disconnects permits the disk controller to execute slower SCSI operations offline Executing slower commands offline allows the SCSI bus to be used for other purposes such as servicing other disk controllers for example Action No action is required IOPn MtcScsiP...

Page 337: ...hen certain SCSI features are used HP NetServer AA software attempts to disable certain SCSI features for disk controllers that are suspected of not handling them properly The SCSI feature write cache was disabled for this controller Use of write cache permits the disk controller to respond with a success status for write requests before the data is actually written to disk The cached data is late...

Page 338: ...al time Action Consider enabling write cache if the controller has not exhibited problems with write cache in the past See the documentation that came with the disk for details IOPn MtcScsiP status DISKn is already disabled HP NetServer AA Manager request to disable a disk was ignored Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description The administrator attempted t...

Page 339: ...K1 DISK2 Severity Warning Description DISKn may not be SCSI 2 or newer SCSI standard compliant Some SCSI devices and some RAID controllers do not indicate SCSI 2 compliance In these cases HP NetServer AA software cannot determine SCSI 2 compliance Action No action is required However if the device immediately experiences unexpected errors after it is installed then the potential lack of SCSI 2 com...

Page 340: ...atus DISKn must be offline HP NetServer AA Manager request ignored Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description An attempt was made to use the HP NetServer AA Manager to perform an operation that is invalid for online disks For example an online disk cannot have its HP NetServer AA partition reset Action No action is required IOPn MtcScsiP status DISKn was s...

Page 341: ...ministrator s Guide for details about replacing a mirrored disk Note The bad spot on the disk may or may not affect the integrity of the file system Whether it has an effect will become apparent as you attempt to back up your data IOPn MtcScsiP status During IOP joining the SCSI Provider detected inconsistent states between the IOPs Severity Error Description This condition occurs when an IOP atte...

Page 342: ...cScsiP status HP NetServer AA partition on DISKn has an unexpected revision number Contact your service provider for assistance Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description HP NetServer AA software found what appears to be a valid HP NetServer AA partition However the version number of the partition was not expected Action Contact your service provider for a...

Page 343: ...d class library setup for DISKn and it will be marked offline Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description The HP NetServer AA disk subsystem was unable to properly initialize with the Windows NT class library See prior messages for details Action Review the event log looking for previous entries to determine why the class library setup failed IOPn MtcScsiP ...

Page 344: ...Otherwise review the event log looking for other problems involving the disk IOPn MtcScsiP status Local member of DISKn mirror set is not online Variables n the disk number for example DISK0 DISK1 DISK2 Severity Warning Description The specified disk is not online Check the event log for previous messages to find out the reason for the offline status Action No action is required but you may want t...

Page 345: ...tional Description This is an HP NetServer AA internal status message Action No action is required IOPn MtcScsiP status Mirror set copies halting due to both CEs or an IOP being down Severity Warning Description Either an IOP or the CEs have been removed from a running HP NetServer AA system This will force all mirror set copies to halt Action No action is required IOPn MtcScsiP status Mirror set ...

Page 346: ...ce the source disk See Chapter 9 in HP NetServer AA Solution Administrator s Guide for details about replacing a mirrored disk Note The bad spot on the disk may or may not affect the integrity of the file system Whether it has an effect will become apparent as you attempt to back up your data IOPn MtcScsiP status Mirror set copy from IOPn to IOPn for DISKx has halted due to a copy write failure to...

Page 347: ...ror copies and it can be caused by different situations The remote IOP did not send a packet to the local IOP within a specified time period The local IOP was unable to send a packet to the remote IOP In either case the mirror copy will be halted and the mirror copy target disk will go offline This message may also be accompanied by other related error messages Consult the event log for other Endu...

Page 348: ... 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 starting The target disk should transition from offline to online Action No action is required IOPn MtcScsiP status Mirror set copy from IOPn to IOPn for DISKx will be performed DISKn on IOPn will be offline until the copy begins Variables n the...

Page 349: ...A SCSI software has remapped a sector that contained a bad block The remap operation makes the sector available to the operating system again However all data that was stored on that sector is lost forever Action Make a note of the bad block for later diagnostic purposes IOPn MtcScsiP status Reset of HP NetServer AA partition for DISKn has been ignored The partition does not require resetting or d...

Page 350: ... software hotfixes Reboot each IOP into Operational HP NetServer AA I O Processor Mode Power on the CEs IOPn MtcScsiP status The administrator disabled DISKn The device must be manually enabled using HP NetServer AA Manager before it can be used Variables n the disk number for example DISK0 DISK1 DISK2 Severity Warning Description An administrator has disabled the specified mirrored disk The disk ...

Page 351: ...with a larger disk capable of acting as a mirror copy target disk for the existing mirror disk IOPn MtcScsiP status The IOPs have different numbers of SCSI adapters Each SCSI adapter in an IOP must have a peer in the other IOP The IOPs will not be allowed to join until this problem is resolved Severity Error Description Each SCSI adapter in an IOP must have a peer in the other IOP The IOPs will no...

Page 352: ...ked offline Variables n the device number for example DISK0 TAPE1 CDROM1 Severity Error Description HP NetServer AA software claims IOP based devices for its own use so it can redirect those devices to the CEs Previous errors such as finding the device or finding the correct device prevent HP NetServer AA software from claiming the device Action Review the event log looking for previous entries to...

Page 353: ... they have been kept up to date Otherwise you may need to perform a full Windows NT installation on the IOP Check Windows NT documentation for more details IOPn MtcScsiP status Unable to locate detected bad block for DISKn during mirror copy No retries left Failing read operation Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description Whenever the presence of a bad blo...

Page 354: ... results from other errors that occurred just prior to it Action The specified device was not found Check for a misconfiguration in which the device was configured to reside at a particular SCSI address but instead resides at a different SCSI address If there is no problem with the configuration verify the device is powered on and review SCSI termination and cable connections IOPn MtcScsiP status ...

Page 355: ... x the disk number for example DISK0 DISK1 DISK2 SECTORn the starting sector in the range of sectors SECTORm the ending sector in the range of sectors Severity Error Description A CE read request did not complete despite repeated retries The disk s state will be set to faulted The sector addresses listed in the message indicate sectors that may contain bad spots Action If the disk is the source di...

Page 356: ... copy Action If the read error occurred in the source disk during a mirror copy the source disk may need replacement The read error indicates a bad spot somewhere on the source disk It may be in the middle of an area reserved by the file system It may be in an unused area on the disk Try restarting the mirror copy by resetting it If the mirror copy completes successfully then the error was transie...

Page 357: ...mirror copy target or if the problem persists contact your service provider for assistance IOPn MtcScsiP status Unable to read the Master Boot Record for DISKn and it will be marked offline Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description HP NetServer AA software was unable to read the Master Boot Record for the specified disk The disk will be offline until the ...

Page 358: ...ce the source disk See Chapter 9 in HP NetServer AA Solution Administrator s Guidefor details on replacing a mirrored disk Note The bad spot on the disk may or may not affect the integrity of the file system Whether it has an effect will become apparent as you attempt to back up your data IOPn MtcScsiP status Unable to reset HP NetServer AA partition for DISKn Variables n the disk number for examp...

Page 359: ...down Action Contact your service provider for assistance IOPn MtcScsiP status Unable to write HP NetServer AA partition for DISKn Variables n the disk number for example DISK0 DISK1 DISK2 Severity Error Description The HP NetServer AA disk software was unable to write the HP NetServer AA partition for the specified disk Action Reboot the IOP bringing it up in Offline HP NetServer AA I O Processor ...

Page 360: ...resses listed in the message indicate sectors that may contain bad spots Action If the disk is the source disk for a mirror copy or if the disk was the only online member of the mirror set then the mirror set will become unavailable to the CEs The disk may be reenabled but if it continues to fail disk replacement may be necessary It is also a good to verify the SCSI termination and SCSI device con...

Page 361: ... copy completes successfully then the error was transient However it is a good idea to verify the SCSI termination and SCSI device connections are correct If the mirror copy does not complete and the physical SCSI connections are correct consider reformatting the data partitions on the disk in Offline HP NetServer AA I O Processor Mode Because this will cause loss of data it should only be attempt...

Page 362: ...ription When the SCSI Redirector was initializing a non critical error occurred probably due to some devices not being available Note This message is logged only in the CE event log Severity Warning Action This message usually indicates a resource error Contact your service provider for additional instructions The message data contains information that can be used to further diagnose the problem ...

Page 363: ...ages 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 354 IOPn MtcSmR Status Messages 355 15 MtcSmR Messages ...

Page 364: ...t this time will only be logged on the IOP that generated the event page 355 IOPn MtcSmR status The HP NetServer AA System Management Redirector failed to send a request to read an event from the Event Provider Attempting to continue to provide HP NetServer AA System Management control functions The ability to log HP NetServer AA events on the CE may be partially or fully impaired Any event genera...

Page 365: ...ns The ability to log HP NetServer AA events on the CE may be partially or fully impaired Any event generated at this time will only be logged on the IOP that generated the event Severity Warning Description This is an internal message If this message is logged contact your service provider IOPn MtcSmR status The HP NetServer AA System Management Redirector failed to send a request to read an even...

Page 366: ...anagement Redirector with the CE transport failed Severity Error Description Before sending requests to an IOP the HP NetServer AA System Management Redirector driver must register with the MtcCEX driver The HP NetServer AA System Management Redirector driver could not do so This prevents HP NetServer AA messages from being sent by the IOPs to the CE Additionally HP NetServer AA Manager commands c...

Page 367: ...atus 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 358 IOPn MtcVidP Status Messages 359 16 MtcVidP Messages ...

Page 368: ...ce configuration page 359 IOPn MtcVidP status Invalid Registry parameter Using default value page 359 IOPn MtcVidP status Join response received but Provider is not in the joining state page 360 IOPn MtcVidP status Protocol version mismatch between the Video Provider and the Keyboard Pointer Provider page 360 IOPn MtcVidP status The Video Redirector and the Video Provider are Incompatible page 360...

Page 369: ... AA Device Synchronization Layer DSL The most likely cause is that the Registry key HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Marathon Providers Video is missing or invalid Action Reinstall the HP NetServer AA software on the IOP IOPn MtcVidP status Invalid Registry parameter Using default value Severity Error Description During initialization the Video Provider reads optional parameters...

Page 370: ... This message occurs during CE boot when the Video Redirector notifies the Video Provider that it is initializing It indicates that incompatible versions of the Video Redirector and Provider software are running on the CE and IOPs Action Use the HP NetServer AA Manager to obtain the revision information for MtcVidP on the IOPs and MtcVidR on the CE If reported following a software upgrade reapply ...

Page 371: ...the merging Video Provider It indicates that incompatible versions of the Video Provider software are running on the IOPs The joining IOP is not allowed to join the HP NetServer AA server Action Use the HP NetServer AA Manager to obtain the revision information for MtcVidP on the IOPs If reported following a software upgrade reapply the upgrade to the IOPs If the error persists contact your servic...

Page 372: ...Chapter 16 MtcVidP Messages 362 ...

Page 373: ...ages that are written to the Windows NT Event Log This chapter assumes that you are familiar with HP NetServer AA terminology and message conventions This chapter includes the following sections IOPn MtcVnP Status Message Summary 364 IOPn MtcVnP Status Messages 365 17 MtcVnP Messages ...

Page 374: ...y page 365 IOPn MtcVnP status Invalid Registry parameter Using default value page 365 IOPn MtcVnP status Join response received but Provider is not in the joining state page 366 IOPn MtcVnP status More than one instance of the Virtual Network Provider was installed in the control panel page 366 IOPn MtcVnP status Timeout waiting for join response from active Virtual Network Provider page 366 IOPn ...

Page 375: ...MACHINE SYSTEM CurrentControlSet Services MtcVnP Parameter key in the Registry Action View the event data as Words The last longword of data should contain a Windows NT error code that can be used by your service provider to help diagnose the problem IOPn MtcVnP status Invalid Registry parameter Using default value Severity Warning Description During initialization MtcVnP reads optional parameters...

Page 376: ...m active Virtual Network Provider Severity Error Description During IOP joining the joining Virtual Network Provider sends a request for state information to the merging Virtual Network Provider and waits for a response If a response is not received within the timeout interval the joining IOP is not allowed to join the HP NetServer AA server IOPn MtcVnP status Virtual Network Co Provider protocol ...

Page 377: ... 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 Action Use the HP NetServer AA Manager to obtain revision information for MtcVnP on all IOPs and MtcVnR on the CEs If this message is reported following a software upgrade reapply the upgrade to the CE and IOPs Contact your service...

Page 378: ...Chapter 17 MtcVnP Messages 368 ...

Page 379: ...r These messages are not written to the Windows NT event log This chapter assumes that you are familiar with Endurance terminology This chapter includes the following sections Types of Messages 370 Endurance Manager Message Summary 370 Endurance Manager Messages 372 18 Endurance Manager Mes sages ...

Page 380: ...able 18 1 Endurance Manager Messages Message Page Messages Indicating Fatal Errors An internal error has occurred in the Retrieval library page 372 An invalid parameter was provided by the caller page 372 Insufficient resources to complete operation page 372 Retrieval information is incomplete required data are missing page 372 Retrieval library thread does not exist page 372 Retrieval library thr...

Page 381: ... request An invalid CE was specified page 374 Could not perform request An invalid device or element was specified page 375 Could not perform request An invalid IOP was specified page 375 Could not perform request An invalid operation was specified page 375 Could not perform request An invalid option was specified page 375 Could not perform request The IOP or CE element number is required page 375...

Page 382: ... service provider An internal error has occurred in the Retrieval library An unexpected error has occurred An invalid parameter was provided by the caller The deallocation of an invalid resource was attempted Insufficient resources to complete operation A resource allocation error occurred during the last display update Retrieval information is incomplete required data are missing The Endurance in...

Page 383: ...suggestion about how to attempt to correct the problem A datatype entry in the MTCSMAPI DLL contains incorrect data Reinstall the Endurance Manager software If the problem persists contact your service provider for assistance A field entry in the MTCSMAPI DLL contains incorrect data Reinstall the Endurance Manager software If the problem persists contact your service provider for assistance A func...

Page 384: ...sists contact your service provider for assistance An enumeration entry in the MTCSMAPI DLL contains incorrect data Reinstall the Endurance Manager software If the problem persists contact your service provider for assistance Could not connect to the Endurance System Management Redirector One of the following problems has occurred The remote Endurance system is not running The system is running bu...

Page 385: ...about valid actions Could not perform request An invalid IOP was specified An invalid IOP was specified Refer to Chapter 5 in HP NetServer AA Solution Administrator s Guide or the online help for specific information Could not perform request An invalid operation was specified An invalid operation keyword s was specified Refer to Chapter 5 in HP NetServer AA Solution Administrator s Guide or the o...

Page 386: ...ources If you are sure that you want to perform the command reissue the command with the Operator Override option Request for memory failed The application or driver attempted to retrieve resources for the request but was unable to do so Requested object not found An invalid keyword was specified The request cannot be completed because an IOP must be specified as the destination or as the executor...

Reviews:

No comments

Related manuals for NetServer AA 4000

Brand: IBM Pages: 7

Anybus Communicator ABC4018

Brand: HMS Networks Pages: 64

EonStor GS 3000 Series

Brand: Infortrend Pages: 134

Brand: Moxa Technologies Pages: 100

301P - DP Print Server

Brand: D-Link Pages: 150

imagePRESS Server G200

Brand: Canon Pages: 98

imagePRESS A3200

Brand: Canon Pages: 192

ColorPass-Z7400

Brand: Canon Pages: 210

Flex System x240

Brand: Lenovo Pages: 42

StorTrends 3200n

Brand: American Megatrends Pages: 2

StorTrends 3200

Brand: American Megatrends Pages: 1

StorTrends 3200i

Brand: American Megatrends Pages: 34

StorTrends 3100

Brand: American Megatrends Pages: 91

TourMaster MLA2504

Brand: Coachsound Pages: 22

Brand: EVS Pages: 70

Xtreme PC NG6452

Brand: Chip PC Pages: 4

Brand: Promise Technology Pages: 318

Brand: Master Digit Pages: 15

Brands by name

0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Popular brands

Load more brands