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

Example 3 Unique IDs for Virtual Partitions vPars, getconf _CS_PARTITION_IDENT

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

Example 1 Determining if an OS instance is running on Superdome 2 hardware Example 1 illustrates how the 'model' and 'getconf' commands can be used to determine whether an OS is running on Superdome 2 hardware. # /usr/bin/getconf MACHINE_MODEL ia64 hp Superdome2 16s # /usr/bin/model ia64 hp Superdome2 16s In both the examples, the presence of "Superdome 2" in the output string indicates that the nPartition or virtual partition is running on a Superdome 2 complex. Example 2 Unique IDs for an nPartition and Complex Example 2 shows the nPartition-unique and complex-unique IDs returned by the getconf command, and the local nPartition number and machine serial number. # parstatus -w The local partition number is 1. # /usr/bin/getconf _CS_PARTITION_IDENT Z3e02955673f9f7c9_P1 # /usr/bin/getconf _CS_MACHINE_IDENT Z3e02955673f9f7c9 # /usr/bin/getconf _CS_MACHINE_SERIAL USR2024FP1 # Example 3 Unique IDs for Virtual Partitions (vPars) Example 3 shows the virtual partition unique ID returned by the getconf command, the local nPartition number, and the current virtual partition name. # parstatus -w The local partition number is 0. # vparstatus -w The current virtual partition is Shad. # getconf _CS_PARTITION_IDENT Z3e0ec8e078cd3c7b_P0_V00 # For more information on virtual partitions, see "Installing or Removing the vPars product from the OS" (page 101). 16 Partitioning in HP Superdome 2

  • 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
Example 1 Determining if an OS instance is running on Superdome 2 hardware
Example 1 illustrates how the 'model' and 'getconf' commands can be used to determine whether
an OS is running on Superdome 2 hardware.
#
/usr/bin/getconf MACHINE_MODEL
ia64 hp Superdome2 16s
#
/usr/bin/model
ia64 hp Superdome2 16s
In both the examples, the presence of “Superdome 2” in the output string indicates that the nPartition
or virtual partition is running on a Superdome 2 complex.
Example 2 Unique IDs for an nPartition and Complex
Example 2 shows the nPartition-unique and complex-unique IDs returned by the
getconf
command,
and the local nPartition number and machine serial number.
#
parstatus -w
The local partition number is 1.
#
/usr/bin/getconf _CS_PARTITION_IDENT
Z3e02955673f9f7c9_P1
#
/usr/bin/getconf _CS_MACHINE_IDENT
Z3e02955673f9f7c9
#
/usr/bin/getconf _CS_MACHINE_SERIAL
USR2024FP1
#
Example 3 Unique IDs for Virtual Partitions (vPars)
Example 3 shows the virtual partition unique ID returned by the
getconf
command, the local
nPartition number, and the current virtual partition name.
#
parstatus -w
The local partition number is 0.
#
vparstatus -w
The current virtual partition is Shad.
#
getconf _CS_PARTITION_IDENT
Z3e0ec8e078cd3c7b_P0_V00
#
For more information on virtual partitions, see
“Installing or Removing the vPars product from the
OS” (page 101)
.
16
Partitioning in HP Superdome 2