Home » HP Manuals » Servers » HP NetServer AA 4000 » Manual Viewer

HP NetServer AA 4000 HP NetServer AA 6200 Solution Release 3.0 Administrator&a - Page 48

HP NetServer AA Messages, In the CE Event Viewer, the message

View all HP NetServer AA 4000 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 48 highlights

Chapter 2 HP NetServer AA Overview HP NetServer AA Messages When it is operational, software continuously monitors the server. It reports status and error messages by logging most messages in the Windows NT event log. Software displays some messages as they occur, either directly on the Windows NT blue screens during the text phase of boot or when a CE is being deconfigured; in pop-up windows; and for messages that pertain to the monitoring of the server, in a window on the Endurance Manager GUI. You can view logged messages using: • Windows NT Event Viewer that displays all messages reported to the Windows NT operating system, including those messages that are logged. • MTCLOG, an event log utility, that displays logged messages as they are being logged. Those messages that are logged in the Windows NT event log are logged as follows: • Each IOP's Windows NT System Event log contains the messages that were generated by that IOP. For example, IOP1 contains any messages generated by IOP1. • The CE's Windows NT System Event log contains both CE messages and the messages that are logged by each IOP. The IOP messages are logged to the CE's Event Viewer as follows: - If a CE is not active (for example, has not completely booted), the IOP messages are stored in a buffer on the IOP and sent to the CE when it becomes available. An IOP can accurately buffer up to 75 messages. - When any CE becomes active, the CE uploads the messages from the IOP event buffers, and logs those messages into the CE's Event log. Because of this process, in the CE Event Viewer, the timestamp information for messages originating in the IOPs is the time that the CE received the message; it does not necessarily indicate the time that the message occurred on the IOP. To confirm the time that the message occurred, check the event logs on the IOPs. Note: If diagnosing events that occurred while the CE operating system was out of service, it is best to copy and then merge the IOP event logs. The resulting file indicates the proper timestamp information and reflects the order in which the messages actually occurred. In the CE Event Viewer, the message IOPn.MtcMon status: The boot process has completed for CE1 indicates the CE started uploading any IOP messages. Any subsequent messages were received from the IOPs without delay. 32

Section	Page
Preface	13
Introduction	17
Introduction	18
HP NetServer AA Components	21
HP NetServer AA Server Overview	23
HP NetServer AA Server Hardware Configuration	23
Endurance Software	25
HP NetServer AA Overview	27
Overview	28
Virtual Network	30
Redirected Video and the CE Desktop Application	32
HP NetServer AA Boot Process	33
HP NetServer AA Characteristics During the CE Boot Process	36
IOP Multi-Boot Options	36
HP NetServer AA Component States	38
Server States	38
CE Operating System States	39
CE States	39
IOP States	40
Interconnect States	41
MIC Port State Display Lights	42
Mirrored Disk States	43
Mirrored Disks in the Server	44
Network Connection States	45
Keyboard/Pointer States	46
Other HP NetServer AA Component States	46
Monitoring the HP NetServer AA Server	47
HP NetServer AA Messages	48
Redirected Video and the CE Desktop Application	51
Overview	52
CE Video During Boot	53
Redirected Video Components	54
Software Running on the IOPs	54
Software Running on the CEs	54
CE Video Drivers	54
CE and IOP Video Modes	54
Booting in Base Video Mode	55
Video Recommendations	56
Some Remote Control Applications Not Supported on the CE	56
Recommendations for Efficient Use of Redirected Video	56
Using the CE Desktop Application	57
Launching the Application	57
Running the CE Desktop Application	58
Changing Input Focus	59
Setting Video Resolution and Refresh Frequency	59
Endurance Manager	61
Overview	62
Starting the Endurance Manager	63
Endurance Manager Window	64
Administration Window	66
Device Status Window	72
Last Mirror Copy Status Window	74
Display and Control Window	77
Options Window	80
Menu Options	82
View Menu	82
Tools Menu	84
Help Menu	85
Using Endurance Manager on a Remote Workstation	86
Security Features for Remote Use of Endurance Manager	87
Commands	89
Issuing Endurance Commands	90
Verifying Commands	91
Command Summary	92
CE1 or CE2 Commands	95
CE_O/S Shutdown Command	105
ESI Enable Operation Command	106
IL12 Enable Operation Command	107
IOP1 and IOP2 Commands	108
IOPn.DatagramService Commands	112
IOPn.Diskx Commands	118
IOPn.Dsl Show Configuration Command	126
IOPn.Ethernetx Commands	128
IOPn.EthernetProvider Commands	135
IOPn.EventProvider Commands	141
IOPn.InputProvider Commands	144
IOPn.Monitor Commands	159
IOPn.ScsiProvider Commands	170
Management Show Computer Information Command	175
Server Shutdown Command	176
Tuple Commands	177
Configuration Utility	181
Introduction	182
Starting the Endurance Configuration Utility	185
Using the Endurance Configuration Utility	186
Display Device Properties	186
Remove Devices	187
Change CE Ethernet Adapters Properties	188
Recommitting the Change to a Driver for a Redirected Ethernet Adapter	189
Commit Configuration Changes	189
Committing When a Floppy Drive is Available	190
Committing When a Floppy Drive is Not Available	191
Verifying Device Information	193
Tools and Utilities	197
MIC BIOS Utility	198
Using the MIC BIOS Setup Utility	198
MTCFLASH Tool	203
Running MTCFLASH	203
MTCFLASH Syntax and Switch and Option Values	204
Upgrading MIC Firmware with MTCFLASH	206
MTCCPYNT Tool	207
Running MTCCPYNT	207
MTCEINFO Tool	208
Making an MTC Diskette	210
MTCLOG Utility	210
MTCCONS (Endurance Manager Console Commands)	211
Managing Faults	217
Fault Management	218
Diagnosing Faults	219
Isolating Faults	220
Correcting Faults	221
Maintenance	223
Rebooting an IOP	225
Shutting Down an IOP	226
Shutting Down a Tuple	228
Shutting Down a CE	229
Shutting Down the CE Operating System	229
Rebooting the Server	230
Shutting Down the Server	230
Replacing an Interconnect Fiber Cable	231
Replacing an Interconnect Fiber Cable on an Online System	231
Replace an Interconnect Fiber Cable on an Offline System	232
Replacing the IL Cable	233
Replacing an IOPx.Ethernet Cable	234
Replacing a MIC	236
Removing a MIC	236
Installing a New MIC	237
Replacing an IOP	239
Removing an IOP	239
Preparing a New IOP for Installation	240
Installing a New IOP	240
Replacing a CE	243
Updating MIC BIOS, FPGA, and Microcode	243
Replacing a Failed Ethernet Adapter	244
Installing the Replacement Adapter	244
Configuring the Replacement Adapter	245
Reconfiguring a Public Ethernet Adapter	247
Updating an Ethernet Driver	249
Adding a Windows NT Service Pack	250
For the CE Operating System	250
For an IOP	250
Uninstalling a Windows NT Service Pack	251
Replacing a Failed Mirrored Disk	252
Partitioning the Replacement Mirrored Disk	253
Reenabling Faulted Components	257
MIC Specifications and LEDs	259
Marathon Interface Card (MIC) Specifications	260
MIC LEDs	261
Endurance Boot Flow Charts	263
Glossary	267

Match case Limit results 1 per page

Chapter 2

HP NetServer AA Overview

HP NetServer AA Messages

When it is operational, software continuously monitors the server. It reports status and error

messages by logging most

messages in the Windows NT event log.

Software displays some

messages as they occur, either directly on the Windows NT blue screens during the text phase

of boot or when a CE is being deconfigured; in pop-up windows; and for messages that pertain

to the monitoring of the server, in a window on the Endurance Manager GUI. You can view

logged messages using:

•

Windows NT Event Viewer that displays all messages reported to the Windows NT

operating system, including those messages that are logged.

•

MTCLOG, an event log utility, that displays logged messages as they are being logged.

Those messages that are logged in the Windows NT event log are logged as follows:

•

Each IOP

’

s Windows NT System Event log contains the messages that were generated by

that IOP. For example, IOP1 contains any messages generated by IOP1.

•

The CE

’

s Windows NT System Event log contains both CE messages and the messages

that are logged by each IOP. The IOP messages are logged to the CE

’

s Event Viewer as

follows:

If a CE is not

active

(for example, has not completely booted), the IOP messages are

stored in a buffer on the IOP and sent to the CE when it becomes available. An IOP

can accurately buffer up to 75 messages.

When any CE becomes

active

, the CE uploads the messages from the IOP event

buffers, and logs those messages into the CE

’

s Event log.

Because of this process, in the CE Event Viewer, the timestamp information for messages

originating in the IOPs is the time that the CE received the message; it does not necessarily

indicate the time that the message occurred on the IOP. To confirm the time that the

message occurred, check the event logs on the IOPs.

Note:

If diagnosing events that occurred while the CE operating system was out of

service, it is best to copy and then merge the IOP event logs. The resulting file

indicates the proper timestamp information and reflects the order in which the

messages actually occurred.

In the CE Event Viewer, the message

IOPn.MtcMon status: The boot process has

completed for CE1

indicates the CE started uploading any IOP messages. Any

subsequent messages were received from the IOPs without delay.