HP Integrity Superdome 2 8/16 HP Superdome 2 Partitioning Administrator Guide - Page 81

will need to manually add back the resource using vparmodify command when the resource is

Get HP Integrity Superdome 2 8/16 PDF manuals and user guides View all HP Integrity Superdome 2 8/16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 81 highlights

decommission the CPU from use and replace it with another good CPU if possible. If this is not possible, the partition controller will not allow the partition to boot until the user modifies the vPar configuration to use the available healthy CPU-cores. The following are some of the cases where the partition controller may not allow the when parspec change policy is disabled: • There is a deconfigured or deactivated CPU which has been reserved for the partition as part of the total (cpu::num) request and partition controller does not have any free CPUs with which to replace it. To correct this, you can delete CPUs from other partitions or from this partition. • There is a deconfigured or deactivated CPU that has been bound to the partition by resource path (cpu:hw_path). Partition Controller does not try to replace a CPU-core assigned to a vPar by resource path. To correct this, you can remove the CPU specified by resource path using vparmodify -d cpu:resourcepath to allow the deconfigured or deactivated CPU to be decommissioned. Add a different CPU to vPar using vparmodify if needed. • There is a deconfigured CPU which has been reserved for the partition as part of a SLP request (socket id:cpu::num) and there are no free SLPs in that socket. To correct this, you can make available CPUs from that socket by deleting the CPUs that are part of this socket from other partitions or delete the CPUs from the socket in this partition. If the parspec change policy is enabled (default), then the partition is booted with existing resources and the parspec is modified to delete the deconfigured resource. Please note that you will need to manually add back the resource using vparmodify command when the resource is healthy and available for use. Example • A cpu, 1/1/0/0, is added by path to a vPar with total 4 cpus. • The cpu gets deconfigured because of an error on the next boot of the vPar. • If parspec change policy is enabled, the vPar will boot without 1/1/0/0 and with the remainin 3 cpus that are part of the partition, and the parspec will be modified to delete 1/1/0/0 • The cpu might be acquitted by the health subsystem at a later point or the blade containing the cpu may be replaced. So, the CPU is now available, but is not automatically added back to the vPar. The vPar will continue to boot with 3 cpus, until the user does a vparmodify and adds back the same cpu or another cpu by count. Planning Your Virtual Partitions 81

  • 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
decommission the CPU from use and replace it with another good CPU if possible. If this is not
possible, the partition controller will not allow the partition to boot until the user modifies the
vPar configuration to use the available healthy CPU-cores. The following are some of the cases
where the partition controller may not allow the when parspec change policy is disabled:
•
There is a deconfigured or deactivated CPU which has been reserved for the partition as
part of the total (cpu::num) request and partition controller does not have any free CPUs
with which to replace it. To correct this, you can delete CPUs from other partitions or from
this partition.
•
There is a deconfigured or deactivated CPU that has been bound to the partition by resource
path (cpu:hw_path). Partition Controller does not try to replace a CPU-core assigned to a
vPar by resource path. To correct this, you can remove the CPU specified by resource path
using
vparmodify -d
cpu:resourcepath to allow the deconfigured or deactivated CPU to
be decommissioned. Add a different CPU to vPar using
vparmodify
if needed.
•
There is a deconfigured CPU which has been reserved for the partition as part of a SLP
request (socket id:cpu::num) and there are no free SLPs in that socket. To correct this, you
can make available CPUs from that socket by deleting the CPUs that are part of this socket
from other partitions or delete the CPUs from the socket in this partition.
If the parspec change policy is enabled (default), then the partition is booted with existing
resources and the parspec is modified to delete the deconfigured resource. Please note that you
will need to manually add back the resource using vparmodify command when the resource is
healthy and available for use.
Example
•
A cpu, 1/1/0/0, is added by path to a vPar with total 4 cpus.
•
The cpu gets deconfigured because of an error on the next boot of the vPar.
•
If parspec change policy is enabled, the vPar will boot without 1/1/0/0 and with the remainin
3 cpus that are part of the partition, and the parspec will be modified to delete 1/1/0/0
•
The cpu might be acquitted by the health subsystem at a later point or the blade containing
the cpu may be replaced. So, the CPU is now available, but is not automatically added back
to the vPar. The vPar will continue to boot with 3 cpus, until the user does a vparmodify
and adds back the same cpu or another cpu by count.
Planning Your Virtual Partitions
81