HP Integrity rx5670 Windows Integrity nPartition Guide - Page 149

Parremove: shutdown and reset instructions, Parstatus -c -V: apparent incorrect output

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 149 highlights

Troubleshooting Operational problems NOTE Step 4. Check whether the complex name has been set with the parstatus -X -g -h command. Set the complex name to any string other than all blanks (this is the default setting) using the cplxmodify command: cplxmodify -N yourcomplexname -g -h See the on-line documentation or refer to "cplxmodify" on page 135 for details on the valid syntax of complex names. At this point, you should be able to continue to successfully create and modify your nPartitions. HP recommends that the complex name be set immediately as the first action, once a complex is set up, to prevent this error. NOTE The message, Error: Unable to update the Stable Complex Configuration Data, can also occur if some other administrator or application has locked the SCCD at the time the parcreate, parmodify, or parremove commands were run. Parremove: shutdown and reset instructions After using the parremove command to remove an active partition, you may see the following messages: NOTE: The -g option may require up to 2 minutes to complete. Please wait. NOTE: The specified partition has been marked for removal. The correct response to this message is to first perform a Windows operating system shut-down for the partition, using either the Shutdown command or a Windows menu path of Start > Shutdown. Once the partition is back at the system firmware (EFI) prompt, login to the MP and use the RR command to put the partition into the Shutdown for Reconfiguration mode. Another method is to just enter reset at the EFI shell. Either method propagates the configuration changes to all of the cells in the partition. HP recommends that in the future you place the OS into this mode before using the parremove command. Parstatus -c -V: apparent incorrect output This issue occurs when the parstatus -c -V command appears to give incorrect output. In reality this is not an error, since the output displayed for "CPU Type" is only relevant with PA-RISC systems. This output should be ignored, since it is not valid for Integrity servers running Windows Server 20003. Parstatus -p -V: apparent incorrect output This issue occurs when the parstatus -p -V command appears to give incorrect output. In reality these are not errors at all, since the output displayed for "PDC Revision" should be interpreted as your "system firmware revision". Also, the output displayed for "IODCH Version" (seen as "FFFF") is only relevant with PA-RISC systems. This output should be ignored, since it is not valid for Integrity servers running Windows Server 20003. Chapter 6 149

  • 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
Operational problems
Chapter 6
149
Step 4.
Check whether the complex name has been set with the
parstatus -X -g -h
<hostname of MP>
command. Set the complex name to any string other than all blanks
(this is the default setting) using the
cplxmodify
command:
cplxmodify -N yourcomplexname -g -h <hostname of MP>
See the on-line documentation or refer to “cplxmodify” on page 135 for details on the
valid syntax of complex names.
At this point, you should be able to continue to successfully create and modify your
nPartitions.
NOTE
HP recommends that the complex name be set immediately as the first action, once a
complex is set up, to prevent this error.
NOTE
The message,
Error: Unable to update the Stable Complex Configuration Data
,
can also occur if some other administrator or application has locked the SCCD at the
time the
parcreate
,
parmodify
, or
parremove
commands were run.
Parremove
:
shutdown and reset instructions
After using the
parremove
command to remove an active partition, you may see the
following messages:
NOTE: The -g option may require up to 2 minutes to complete. Please wait.
NOTE: The specified partition has been marked for removal.
The correct response to this message is to first perform a Windows operating system
shut-down for the partition, using either the
Shutdown
command or a Windows menu
path of
Start > Shutdown
. Once the partition is back at the system firmware (EFI) prompt,
login to the MP and use the
RR
command to put the partition into the Shutdown for
Reconfiguration mode. Another method is to just enter
reset
at the EFI shell. Either
method propagates the configuration changes to all of the cells in the partition.
HP recommends that in the future you place the OS into this mode
before
using the
parremove
command.
Parstatus -c -V
:
apparent incorrect output
This issue occurs when the
parstatus -c -V
command
appears
to give incorrect
output. In reality this is not an error, since the output displayed for “CPU Type” is only
relevant with PA-RISC systems. This output should be ignored, since it is not valid for
Integrity servers running Windows Server 20003.
Parstatus -p -V
:
apparent incorrect output
This issue occurs when the
parstatus -p -V
command
appears
to give incorrect
output. In reality these are not errors at all, since the output displayed for “PDC
Revision” should be interpreted as your “system firmware revision”. Also, the output
displayed for “IODCH Version” (seen as “
FFFF
”) is only relevant with PA-RISC systems.
This output should be ignored, since it is not valid for Integrity servers running
Windows Server 20003.