HP Integrity rx5670 Windows Integrity nPartition Guide - Page 155

Application Event Log messages, My Computer, Properties, Message, Cause, Recommended Action

Get HP Integrity rx5670 PDF manuals and user guides View all HP Integrity rx5670 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 155 highlights

Table 6-1 Troubleshooting Error messages and corrective actions nPartition commands messages (Continued) Message Cause Recommended Action Cannot read . Unable to read . Unable to get . No information available for . information unavailable. In most cases, these messages are caused by lost datagrams over an unreliable network connection. See the AEL entry for more information. identifies the specific data that is not available. identifies the specific component for which data was not available. Retry the command, or use a management PC with a more reliable network connection to the target MP or nPartition. NOTE: This error may occur if -w and -g options are used in the same command. This condition should be reported by the parstatus command as a syntax error because there is never a local partition when using the -g and -h option combination. LED operation on failed. Attempted to turn on or off an LED that does not exist on the target complex. Only Superdome servers support all LEDs. Midrange partitionable servers (like rx8620) do not have cabinet or I/O chassis LEDs. See the AEL entry to confirm this. Do not specify a non-existent LED. Application Event Log messages Due to limitations in the Microsoft WMI implementation, some of the error message data returned by the nPartition provider are not transmitted through the WMI server to the client command when the error occurs. However, under Windows, the provider logs the error data in the Application Event Log (AEL). Additional information about an error is obtained by examining the most recent entries logged by the nPartition provider in the AEL. Access the AEL from the context menu of the My Computer desktop icon. Select My Computer > Manage, and when the application opens select System Tools > Event Viewer > Application in the left hand pane. Select the desired entry in the right hand pane and then choose Properties from the context menu to see the message itself. After retrieving the error message from the AEL, refer to the following table to locate that message and see the recommended course of action. In some cases, additional information will follow the general message shown in the table below. Chapter 6 155

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
Troubleshooting
Error messages and corrective actions
Chapter 6
155
Application Event Log messages
Due to limitations in the Microsoft WMI implementation, some of the error message data
returned by the nPartition provider are not transmitted through the WMI server to the
client command when the error occurs. However, under Windows, the provider logs the
error data in the Application Event Log (AEL). Additional information about an error is
obtained by examining the most recent entries logged by the nPartition provider in the
AEL.
Access the AEL from the context menu of the
My Computer
desktop icon. Select
My
Computer > Manage
, and when the application opens select
System Tools > Event Viewer >
Application
in the left hand pane. Select the desired entry in the right hand pane and
then choose
Properties
from the context menu to see the message itself.
After retrieving the error message from the AEL, refer to the following table to locate
that message and see the recommended course of action. In some cases, additional
information will follow the general message shown in the table below.
Cannot read <info>.
Unable to read <info>.
Unable to get <info>.
No information available
for <component>.
<Component>
information unavailable.
In most cases, these
messages are caused by
lost datagrams over an
unreliable network
connection. See the AEL
entry for more
information.
<info> identifies the
specific data that is not
available.
<component> identifies
the specific component for
which data was not
available.
Retry the command, or use a
management PC with a
more reliable network
connection to the target MP
or nPartition.
NOTE: This error may occur
if
-w
and
-g
options are used
in the same command. This
condition should be reported
by the
parstatus
command
as a syntax error because
there is never a local
partition when using the
-g
and
-h
option combination.
LED operation on
<component> failed.
Attempted to turn on or
off an LED that does not
exist on the target
complex. Only Superdome
servers support all LEDs.
Midrange partitionable
servers (like rx8620) do
not have cabinet or I/O
chassis LEDs. See the
AEL entry to confirm this.
Do not specify a non-existent
LED.
Table 6-1
nPartition commands messages (Continued)
Message
Cause
Recommended Action