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

Planning Your System for Virtual Partitions, Virtual Partitions Layout Plan, Virtual Partition Names

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

7 Planning Your System for Virtual Partitions Planning Your Virtual Partitions Virtual Partition or vPars are created by specifying the resources are needed for the vPar. Resources that can be assigned to a vPar are: 1. CPU-cores - either by specifying the number of CPU-cores that are part of the vPar or by specifying the resource paths of individual CPU-cores or by specifying the socket resource paths and quantity from where the CPUs to be assigned. 2. Memory - Memory is specified by size or by specifying the socket resource path and size of the memory to be assigned. 3. I/O - I/O may be designated by either its rootport or IO slot resource path. These rootports or IO slots are where the storage or networking devices are attached. Before planning virtual partitions, collect the required hardware information about vPar assignable resources. This can typically be done using parstatus command from the OA and/or using ioscan if you have booted HP-UX in the nPar. If the nPartition is powered on in vPars mode, then vparstatus -A can also be used to get the available vPar assignable resources. Virtual Partitions Layout Plan Before you create vPars, you should have a plan of how you want to configure the virtual partitions within your server. Virtual Partition Names A vPar name must at least have one of the following non-numeric characters: a-z, A-Z, dash (-), underscore (_), or period (.). No other non-numeric characters are allowed in a vPar name. The maximum length of a vPar name is 254 characters. If the name is not specified either through the -p or -P options, a default name in the format vParNNNN is given to the vPar. Although the underscore (_) is a legal character within the name of a virtual partition, it is not a legal character within the Domain Name System (DNS), thus making it inappropriate if you wish your vPar names to match your OS hostnames. Minimal Hardware Configuration Every bootable virtual partition must have at least: • 1 CPU-core On HP Integrity Superdome 2, by default, a vPar is created with zero CPU-cores. Such a vPar cannot boot. So, for a bootable partition on Superdome 2, at least one CPU-core is required. • System memory (sufficient for HP-UX and the applications in that partition) • A boot disk (when using a mass storage unit, check your hardware manual to verify that it can support a boot disk) Although not required for booting a virtual partition, you can add LAN card(s) as required for networking. For your virtual partitions, use the number of CPUs, amount of memory, boot disk configuration, and LAN cards as is appropriate for your OS and applications. Planning Your Virtual Partitions 73

  • 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
7 Planning Your System for Virtual Partitions
Planning Your Virtual Partitions
Virtual Partition or vPars are created by specifying the resources are needed for the vPar.
Resources that can be assigned to a vPar are:
1.
CPU-cores
- either by specifying the number of CPU-cores that are part of the vPar or by
specifying the resource paths of individual CPU-cores or by specifying the socket resource
paths and quantity from where the CPUs to be assigned.
2.
Memory
- Memory is specified by size or by specifying the socket resource path and size of
the memory to be assigned.
3.
I/O
- I/O may be designated by either its rootport or IO slot resource path. These rootports
or IO slots are where the storage or networking devices are attached.
Before planning virtual partitions, collect the required hardware information about vPar assignable
resources. This can typically be done using
parstatus
command from the OA and/or using
ioscan
if you have booted HP-UX in the nPar. If the nPartition is powered on in vPars mode,
then
vparstatus -A
can also be used to get the available vPar assignable resources.
Virtual Partitions Layout Plan
Before you create vPars, you should have a plan of how you want to configure the virtual
partitions within your server.
Virtual Partition Names
A vPar name must at least have one of the following non-numeric characters: a-z, A-Z, dash (-),
underscore (_), or period (.). No other non-numeric characters are allowed in a vPar name. The
maximum length of a vPar name is 254 characters. If the name is not specified either through
the -p or -P options, a default name in the format
vParNNNN
is given to the vPar.
Although the underscore (
_
) is a legal character within the name of a virtual partition, it is not
a legal character within the Domain Name System (DNS), thus making it inappropriate if you
wish your vPar names to match your OS hostnames.
Minimal Hardware Configuration
Every bootable virtual partition must have at least:
•
1 CPU-core
On HP Integrity Superdome 2, by default, a vPar is created with zero CPU-cores. Such a
vPar cannot boot. So, for a bootable partition on Superdome 2, at least one CPU—core is
required.
•
System memory (sufficient for HP-UX and the applications in that partition)
•
A boot disk (when using a mass storage unit, check your hardware manual to verify that it
can support a boot disk)
Although not required for booting a virtual partition, you can add LAN card(s) as required for
networking.
For your virtual partitions, use the number of CPUs, amount of memory, boot disk configuration,
and LAN cards as is appropriate for your OS and applications.
Planning Your Virtual Partitions
73