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

Resource health policy, nPartition Health Status

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

Figure 6-23 nPartition Health Status Resource health policy Resource health or status will be checked by Partition management subsystem before activating a resource in a partition, be it an nPartition or vPar. Unhealthy resources are not activated as part of activation of a partition. For an nPartition, blades and I/O bays are activated only if they are reported as healthy by the Health management subsystem on the OA. Additionally, there is also a user specified attribute "failure_usage" for a blade and I/O bay which can be set to indicate whether the partition to which the blade is assigned should be activated or not if the blade is found faulty. If the nPartition can be activated, the unhealthy resource is excluded before activating the nPartition. The setting of this attribute (failure_usage) can be done either during partition creation time, or modified later using parmodify. For sub-blade resources, like cpu-cores, memory and root ports, the partition (nPartition or vPar) is always activated with the subset of healthy resources. An indicted resource is not considered unhealthy. Only deconfigured (or marked for deconfiguration) resources are considered unhealthy. A resource is also considered unhealthy if its parent is reported as unhealthy. nPartition and Resource Health Status 71

  • 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
Figure 6-23 nPartition Health Status
Resource health policy
Resource health or status will be checked by Partition management subsystem before activating
a resource in a partition, be it an nPartition or vPar. Unhealthy resources are not activated as
part of activation of a partition.
For an nPartition, blades and I/O bays are activated only if they are reported as healthy by the
Health management subsystem on the OA. Additionally, there is also a user specified attribute
“failure_usage” for a blade and I/O bay which can be set to indicate whether the partition to
which the blade is assigned should be activated or not if the blade is found faulty. If the nPartition
can be activated, the unhealthy resource is excluded before activating the nPartition. The setting
of this attribute (failure_usage) can be done either during partition creation time, or modified
later using
parmodify
.
For sub-blade resources, like cpu-cores, memory and root ports, the partition (nPartition or vPar)
is always activated with the subset of healthy resources.
An indicted resource is not considered unhealthy. Only deconfigured (or marked for
deconfiguration) resources are considered unhealthy. A resource is also considered unhealthy
if its parent is reported as unhealthy.
nPartition and Resource Health Status
71