HP-UX Virtual Partitions Administrator's Guide - filibeto.org

More documents

Recommendations

Info

Virtual Consoles HP-UX servers have a special terminal or window called a console that allows special control and displays system error messages. With vPars, each virtual partition has its own virtual console. On Integrity, the console is virtualized by firmware (and therefore, there is no vcs driver). On PA-RISC, for each partition, its console I/O is sent to its vcn (Virtual CoNsole) driver. From the vcn driver, the console I/O is sent to the vPars Monitor. From the vPars Monitor, the console I/O is sent to the vcs (virtual console slave) driver of the partition that owns the hardware console port. Finally, the vcs driver sends the console I/O to the physical hardware console. It is this vcs driver that manages the console I/O to the actual hardware console port. When the partition that owns the hardware console port is not running, the vPars Monitor takes over the management of the I/O to the hardware console port, so you will still have access to the virtual console displays. You can access the console port as you would on any non-vPars server, for example, through a dumb terminal or lan console. Then, to cycle between the virtual console displays of the various partitions, press Ctrl-A. 32 How vPars and Its Components Work
Each virtual partition has an 8K circular buffer for console output. If not already displayed, the vPars Monitor copies this 8K buffer to the console when you press Ctrl-A. CAUTION: (A.03.xx only) The first virtual partition that you create must own the LBA (local bus adapter) that contains the physical hardware console port. For an example, see “Assigning the Hardware Console LBA” (page 55). Virtual Consoles 33
Page 1 and 2: HP-UX Virtual Partitions Administra
Page 3 and 4: Table of Contents About This Docume
Page 5 and 6: The Update Process.................
Page 7 and 8: LVM maintenance mode steps.........
Page 9 and 10: Syntax.............................
Page 11 and 12: Archiving the Virtual Partitions Us
Page 13 and 14: List of Figures 1-1 vPars Conceptua
Page 15: About This Document Intended Audien
Page 18 and 19: NOTE: Definitions This document use
Page 20 and 21: 20 Introduction Therefore a single
Page 22 and 23: 22 Introduction — /opt/ignite/boo
Page 24 and 25: 24 Introduction vPars partition dat
Page 26 and 27: NOTE: In certain situations when us
Page 28 and 29: Figure 2-2 Software Stack of Server
Page 30 and 31: As a preventive action, you can bac
Page 34 and 35: NOTE: Note the following when using
Page 36 and 37: Security only one particular virtua
Page 38 and 39: new EFI device path. However, firmw
Page 40 and 41: Table 2-1 PA-RISC and Integrity Dif
Page 42 and 43: Resource Migration and Required Sta
Page 44 and 45: Table 2-6 CPU Rules from A.03.xx to
Page 47 and 48: 3 Planning Your System for Virtual
Page 49 and 50: 0/0/2 ba Local PCI-X Bus Adapter (7
Page 51 and 52: where 0/12 and 0/13 are the cell/CP
Page 53 and 54: The ioscan output for the example n
Page 55 and 56: 0/10 ba Local PCI Bus Adapter (782)
Page 57 and 58: Choosing the Boot and Lan Paths Aut
Page 59 and 60: • The vPars A.04.05 Monitor or la
Page 61 and 62: The following features can be execu
Page 63 and 64: keira1 B.11.31 Up keira2 B.11.23 Up
Page 65: Features Summary The following tabl
Page 68 and 69: Cautions For information on using t
Page 70 and 71: Current Flow Control: Software Do y
Page 72 and 73: vPars-related Bundles (A.03.xx and
Page 74 and 75: Ignite-UX, the LAN, the LAN card, a
Page 76 and 77: Updating from vPars A.04.xx to A.05
Page 78 and 79: keira1# vparstatus [Virtual Partiti
Page 80 and 81: keira1 # vparmodify -p keira3 -B au
Page 82 and 83:
Overview of the Mixed HP-UX 11i v1/
Page 84 and 85:
— Wait for the vPars A.03.05 upda
Page 86 and 87:
HPUX11i-OE-MC Mission Critical OE W
Page 88 and 89:
4. If gWLM is in use, disable (unde
Page 90 and 91:
NOTE: If you are updating to vPars
Page 92 and 93:
Monitor the installation progress u
Page 94 and 95:
Migrating from vPars A.03.xx to Mix
Page 96 and 97:
Updating from vPars A.04.xx to Mixe
Page 98 and 99:
Note that in a mixed HP-UX 11i v2/v
Page 100 and 101:
The nPartition number is 0. Record
Page 102 and 103:
d. Once the PRI path has been succe
Page 104 and 105:
The Steps For information on the ty
Page 106 and 107:
NOTE: If the BOOT and ALTBOOT disks
Page 108 and 109:
MON> vparload -all When the virtual
Page 110 and 111:
NOTE: If you have previously applie
Page 112 and 113:
Upgrading HP 9000 Servers from the
Page 114 and 115:
Upgrading Backplanes from PCI to PC
Page 116 and 117:
# vparboot -p winona2 -I ww.xx.yy.z
Page 118 and 119:
# vparboot -p -I [ [-d dbprofile_n
Page 120 and 121:
If you are at the console of winona
Page 122 and 123:
Notes on Examples in this Chapter S
Page 124 and 125:
• To set the mode to vPars and th
Page 126 and 127:
CAUTION: • When you set the mode
Page 128 and 129:
For more information on vparefiutil
Page 130 and 131:
# setboot -a mirror_disk_hw_path
Page 132 and 133:
Example: — If you have a backup c
Page 134 and 135:
is rebooted. If Reboot for Reconfig
Page 136 and 137:
date hostname vPars_command_name[pi
Page 138 and 139:
Table 5-2 Virtual Partition States
Page 140 and 141:
vparstatus: Verbose Information Use
Page 142 and 143:
vparstatus: Available Resources Use
Page 144 and 145:
vparstatus: CPU Information on vPar
Page 146 and 147:
vparstatus: Dual-Core CPUs You can
Page 148 and 149:
vparstatus: Pending Migrating Memor
Page 150 and 151:
vparstatus: Pending nPartition Rebo
Page 152 and 153:
use the corresponding vparcreate co
Page 154 and 155:
Booting a Virtual Partition To boot
Page 156 and 157:
When to Shutdown All Virtual Partit
Page 158 and 159:
NOTE: • To modify stable storage,
Page 160 and 161:
Setting the Primary or Alternate Bo
Page 162 and 163:
. . . [IO Details] 0.0.6 0.0.6.0.0.
Page 164 and 165:
On a vPars server, to get the same
Page 166 and 167:
NOTE: For Superdome and other nPart
Page 168 and 169:
From HP-UX shell prompt From the ru
Page 170 and 171:
5. Import the root volume group (vg
Page 172 and 173:
Memory I/O Paths (LBAs) Boot Path L
Page 174 and 175:
174
Page 176 and 177:
• “I/O: Concepts and Functional
Page 178 and 179:
Figure 6-6 vPars Allocates at LBA L
Page 180 and 181:
I/O: Allocation Notes When planning
Page 182 and 183:
Memory: Concepts and Functionality
Page 184 and 185:
NOTE: The Default is :base. When ne
Page 186 and 187:
Memory: Assigning (Adding) or Delet
Page 188 and 189:
Memory: Assigning (Adding) Or Delet
Page 190 and 191:
Memory: Converting Base Memory to F
Page 192 and 193:
Memory: Granularity Issues (Integri
Page 194 and 195:
vparcreate vparenv rather than vpar
Page 196 and 197:
Memory: Setting the Granularity Val
Page 198 and 199:
• “CPU: Notes on vPars Syntax,
Page 200 and 201:
vparcreate NOTE: CPU deletion fails
Page 202 and 203:
CPU: Adding or Deleting by CLP (Cel
Page 204 and 205:
— keira1# vparmodify -p keira2 -a
Page 206 and 207:
Figure 6-7 Using Partition Manager
Page 208 and 209:
setboot -m on|off For more informat
Page 210 and 211:
NOTE: On a vPars system, when a vir
Page 212 and 213:
The vparstatus output shows that a
Page 214 and 215:
NOTE: Regarding syntax and how vPar
Page 216 and 217:
Examples • To add all hardware us
Page 218 and 219:
different meanings depending upon t
Page 220 and 221:
NOTE: Assigning ILM or CLM memory b
Page 222 and 223:
Memory: Granularity Concepts Granul
Page 224 and 225:
Granularity Memory is normally assi
Page 226 and 227:
Example 2 If the total physical mem
Page 228 and 229:
When using this method, note that t
Page 230 and 231:
Memory: Allocation Notes CPU • Th
Page 232 and 233:
CPU: Specifying Min and Max Limits
Page 234 and 235:
keira1# vparmodify -p keira2 -m cpu
Page 236 and 237:
-a is adding -d is deleting hw_path
Page 238 and 239:
Activating and Deactivating CPUs Wh
Page 240 and 241:
CPU: Dual-Core Processors With the
Page 242 and 243:
1/0/12 BUS_BRIDGE sv_model= 10 HPA=
Page 244 and 245:
NOTE: On a vPars system, when a vir
Page 246 and 247:
NOTE: Regarding syntax and how vPar
Page 248 and 249:
Examples • To add all hardware us
Page 250 and 251:
1. The explicit specification of an
Page 252 and 253:
Memory: Specifying Address Range Wi
Page 254 and 255:
CPU: Specifying Min and Max Limits
Page 256 and 257:
CPU: Adding and Removing Bound CPUs
Page 258 and 259:
NOTE: When executing any operations
Page 260 and 261:
intctl Command Notes The intctl com
Page 262 and 263:
Figure 8-7 Using Partition Manager
Page 264 and 265:
CPU: CPU Monitor (Formerly Known As
Page 266 and 267:
• For more information on using t
Page 268 and 269:
Cab/ Cell Slot/ # of L3 L4 Family/
Page 270 and 271:
Shell> fsN: fsN:\> efi\hpux\hpux /s
Page 272 and 273:
. . Configuring CLM for an nPartiti
Page 274 and 275:
CAUTION: • If you reduce the ILM
Page 276 and 277:
276
Page 278 and 279:
3. (PA-RISC only) allows you to cho
Page 280 and 281:
• make_tape_recovery within a vPa
Page 282 and 283:
After this virtual partition is rec
Page 284 and 285:
Archiving and Recovering a Virtual
Page 286 and 287:
Archiving and Recovering a Virtual
Page 288 and 289:
4. When the User Interface and Medi
Page 290 and 291:
Then proceed with the recovery as n
Page 292 and 293:
Terms and Definitions target partit
Page 294 and 295:
Flexible Administrative Capability
Page 296 and 297:
• display whether the vPars flexi
Page 298 and 299:
For this section, let’s assume we
Page 300 and 301:
300
Page 302 and 303:
Starting the Virtual Partition Mana
Page 304 and 305:
304
Page 306 and 307:
p7400/N4000 I/O Block Diagram Figur
Page 308 and 309:
308
Page 310 and 311:
Note that the entries for the unbou
Page 312 and 313:
312
Page 314 and 315:
For example, if we calculated the s
Page 316 and 317:
• containing 8 GB of total memory
Page 318 and 319:
318
Page 320 and 321:
320
Page 322 and 323:
CLP (Cell Local Processor) ILM (Int
Page 324 and 325:
expert recovery, 22, 290 F flexibil
Page 326:
virtual consoles, 32 GSPdiag1 devic
show all

HP-UX Virtual Partitions Administrator's Guide - filibeto.org

Create successful ePaper yourself

Delete template?

Save as template?