hp-ux 11i v3 delta support - student guide part 1

HP-UX 11i v3 Delta Support

March 2007

Student guide: 1 of 3

Use of this material to deliver training without prior written permission from HP is prohibited.

HP-UX 11i v3 Delta Support

March 2007

Student guide

© Copyright 2007 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

This is an HP copyrighted work that may not be reproduced without the written permission of HP. You may not use these materials to deliver training to any person outside of your organization without the written permission of HP.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Printed in the USA.

HP-UX 11i v3 Delta Support Student guideMarch 2007

HP Restricted — Contact HP Education for customer training materials.

ContentsVolume 1

1 Course Introduction2 Tour HP-UX 11i v3 (11.31)

Supported Systems 9Highlights of HP-UX 11i v3 19

3 System Installation and Configuration Installation Considerations 3Installation Process 44Update Process 53Troubleshooting Installation & Update 68Post Installation Tasks 82Software Deployment 92Boot and Update 105Kernel Configuration 112Peripheral Device Configuration 132

Volume 24 Flexible Capacity

Performance and Scalability 3Montecito Processor 8Dynamic Resources 49Operating System Enhancements 127

Volume 25 Secured Availability

Montecito Processor 3Recovery 20Networking 105Security 153Serviceguard 238

6 Simplified ManagementSystem Management 3Event manager 65Event Monitoring Service 81

HP-UX 11i v3 Delta Course Introduction

March 2007 Introduction-1

© 2007 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice

Course IntroductionSection 1

PrefaceHP-UX 11i v3 is a joint release of HP-UX 11i for both the Integrity and HP 9000 server families. HP-UX 11i v3 is the next enterprise release delivering expanded infrastructure for the Adaptive Enterprise in a multi-OS world and competes with IBM's On Demand, Power architecture and AIX. The release delivers enhanced performance and feature capabilities for Montecito-based platforms. It is an enabler for a more competitive virtualization solution in 2007, including both vPars and Integrity VM. The HP-UX I/O infrastructure is enhanced for improved scalability, manageability and agility. Interoperability with other UNIX systems is improved through the delivery of NFSv4. It offers a range of HP-UX Operating Environments and capabilities including 256-way scaling, systems management, security, and high-availability software products.

Effective support is a key component of the solution, and is the subject of this HP-UX 11i v3 Delta Training course. This module serves as an introduction to the course.

NOTE: Some features described in this course release after the original release of HP-UX 11i v3. Features that have not been released should not be discussed with customers.



March 20072

Course ObjectivesUpon completion of this course, you will be able to• Compare and explain key product features and functionality differences

between HP-UX 11i v2 and HP-UX 11i v3• Explain installation, update, and configuration differences and

requirements between HP-UX 11i v2 and HP-UX 11i v3– Understand how to install or update to HP-UX 11i v3

• Understand new functionalities in these categories– Flexible Capacity– Secured Availability– Simplified Management

• Describe changes that impact serviceability of the product or create service issues

• Perform typical system management tasks using new tools

Course ObjectivesThe enabling objective of this course is to ensure that you are familiar with, and able to:

• Describe the differences between key product features and functionality from HP-UX 11i v2 to HP-UX 11i v3

• Describe changes that impact the serviceability of HP-UX 11i v3 The overall objective is to use that knowledge to provide effective support to customers running HP-UX 11i v3 on Itanium-based and PA-RISC HP-UX systems.

Note on Release NamesThe HP-UX 11.31 release is externally known as HP-UX 11i v3. In this course, the release name may be abbreviated as 11.31. Additionally, releases of HP-UX 11i v1 may be referred to as 11.11, and releases of HP-UX 11i v2 are called 11.23 or 11.23 0409, as appropriate. If it is necessary to differentiate, the month and year of the 11.11 release will be indicated, such as “11.11 June 2004”. If it is necessary to differentiate previous releases of HP-UX 11i v2, they will be indicated as either “the initial release of 11.23” or “11.23 March 2004” or “11.23.0606”.



March 20073

HP-UX 11i v3 Training Roadmap for HP Services

Intel Itanium

HP-UX (experienced*)

100

200

400

Trai

ning

leve

l

HP Itanium Fundamentals(NE71-IPFBASICvC)

WBT 4 hr

EFI (9695) VC/L 8hr(23152) VL 8hr

Intel Itanium Processor FamilyArchitecture for HP-UX

Recording (2200)

HP-UX 11i v3 Delta(35184) VC 3 days(36082) Recording

HP-UX System Internals I(36237) ILT 5 days(36238) VC 5 days

Diagnostics

L200 Diagnosticsand EMS (10619)

Recorded 7hr

Integrity Entry-Level WBT (28915)Cell-based WBT (14725)Superdome WBT (22667)

L400 Diagnostics(13210)

Recorded 8hr

*HP-UX System Admin is a prerequisite

Itanium-based SystemsThe Itanium WBT provides a good, quick introduction to Intel Itanium architecture and EFI --probably everyone should go through this. Then if someone needs more on Intel Itanium architecture, platforms or firmware, there are several options:

• EFI (Extended Firmware Interface) Module (9695) – live course on EFI• EFI – Lab (23152) – self-paced lab• HP Integrity Entry-Level and Mid-Range System Technology (28915) – WBT includes the

features, architecture, and functionality of the rx16xx, rx26xx, rx4640, rx7620, and rx8620 Integrity servers

• Cell-based Mid-Range Servers prerequisite WBT (14725) – WBT intro to Cell-Based Server components, EFI commands, Cell-Based Booting and Partition Management

• Cell Based Superdome servers prerequisite WBT (22667) – WBT intro to Superdome, Cell-Based Server components, EFI commands, Cell-Based Booting and Partition Management

• MP Fundamentals for Cell-Based Integrity Servers Virtual Lab (33213) – self-paced lab• Itanium Architecture for HP-UX is level 400 prerequisite to HP-UX Internals (2200) – self-

paced recordingHP-UX

• If you are supporting HP-UX 11i v2 and will be supporting HP-UX 11i v3, take HP-UX 11i v3 Delta (this course).

• HP-UX Internals is level 400 for GSE/WTEC, HP-UX development, support, and test engineers, and advanced HP-UX customer support engineers, such as customer performance consultants and senior RCEs.

Diagnostics• Level 200 diagnostics: offline (ODE) and online (STM) and EMS; HP-UX 11.23 general

knowledge is a recommended prerequisite.• Level 400 diagnostics: SMS, Itanium-based system monitors, other Itanium-based system

tools, Itanium-based system tool libraries.



March 20074

Audience & PrerequisitesTarget Audience• Experienced HP-UX 11i v2 support engineers

Prerequisite Knowledge• Familiarity with HP 9000 PA-RISC and HP Integrity Itanium-

based computer systems hardware• Understanding of HP-UX 11i system administration concepts

and tasks• Familiarity with the HP-UX support environment

This class is not…• In-depth hardware training• Introductory HP-UX system administration training

The level for this training material is Level 200 and the audiences are the HP service engineers who support HP-UX customers, specifically RCEs, CMTEs, and WTEC. A subset of this material, especially the new features, may be reused to educate Presales Personnel and channel partners. This course is oriented toward HP-UX support engineers that have been supporting the earlier HP-UX 11i series of releases on the Itanium-based and PA-RISC platforms. Specifically, we expect that the students have the following pre-requisite experience:

• Knowledge of PA-RISC and Itanium Architectures• Knowledge of HP 9000 PA-RISC and HP Integrity systems

– Hardware systems & configurations– Pre-OS boot environments– System administration

• Experience supporting HP-UX 11i v2 releases



March 20075

Course Ground RulesNo multitasking!• Please do not use this as a handy time to catch up on your

email– It may be tempting, but you will likely miss something important

Show up on time and stay connected• HPVC and the ‘phone bridge’ need a few minutes to access –

allow for thatMute your phone if you are not talking• Do not use the ‘other line’ to talk to someone else

Use the HPVC ‘hands-up’ feature to ask questions• Or, type them in the Questions window

The virtual classroom is a great way to deliver courses to a wide audience very quickly. However, like any other classroom environment, you will maximize your experience if a few guidelines are followed. Mainly, this means not succumbing to the temptation to try to multitask during the class. If you do that, there is no doubt that you will miss something, and it will likely be something important.

You are in the course already, so the second item is not too relevant. But, if you arrived late or had issues getting connected, you understand the value of starting that process a few minutes early, so you are ready to go on time.

If you can, and you are attending the course on an open (unmoderated) line, mute your phone so that we do not end up listening to you type, or worse!

If you have any questions, type them into the Questions window, or hold them until we do the live Q&A. It is sometimes better to have them typed in, since then the question and its answer are captured, but that is your choice.



March 20076

Course FormatThree HP VC sessions of up to 6 hours• Sessions will (usually!) consist of

– About 50 minutes presentation (with questions)– 10 minutes break– Repeat

Activity sessions of 2 - 3 hours• Written (paper-based) exercises• Hands on (lab) exercises

This course is three presentation sessions of up to six hours. We will run each hour or so about the same way. First, we will do some presentation, then have a Q&A session, then have a break. This should give the instructor plenty of time to get the information out there, and give everyone an opportunity to get her or his questions out, as well.

Additionally, there will be a few hours of exercises after each presentation session.



March 20077

Course ScheduleCourse Sections • Tour of HP-UX 11i v3• System Installation and Configuration Section• Flexible Capacity Section• Secured Availability Section• Simplified Management Section

Secured Availability Section

Simplified Management Section

Flexible Capacity Section-Montecito Module-OL* / On Demand-O.S. Enhancements-Resource Management

Tour HP-UX 11i v3 (11.31) Section

System Installation and Configuration Section

Day 3Day 2Day 1

The first day, we overview this release of HP-UX and its major differences. We also address system installation, update, and configuration. The second day is devoted to Flexible Capacity topics, including Montecito Hyper-threading, OL* and On Demand Solutions, Operating System enhancements and Resource Management solutions. The third day covers both the Secured Availability and Simplified Management sections.



March 20078

Introductions and HP-VTR OverviewIntroductions• Instructor Introduction• Student Introductions

– Name and Location– Job– Reasons for taking this course– One non-work item – what you enjoy when not working

HP Virtual Training Room Overview• Raising hands• Group chat• Questions box• Application Sharing by instructor• Private chats

It is time to get to know each other. Please state your name and location, what your job role or function is, and why you are taking this course. Also, include a non-work item – something about you, for example, what you enjoy when you are not working.

Now, we will make sure that everyone knows how to use the virtual classroom to make it as interactive as if we were together in a classroom!

HP-UX 11i v3 Delta Tour HP-UX 11i v3 (11.31)

March 2007 Tour-1


Tour HP-UX 11i v3 (11.31)Section 2

Tour HP-UX 11i v3 (11.31)This section is in a different format than the other sections in this course: it has little narrative text to accompany the slide presentation. This section is intended as a high level overview of the differences between HP-UX 11i v3 and HP-UX 11i v2. Additional detail is provided in the remaining sections of this course as well as in the release notes.


March 2007 Tour-2

March 20072

Section ObjectivesUpon completion of this section, you will be able to• Describe the overarching goals of HP-UX 11i v3• List and describe the major changes in HP-UX 11i v3 in the

following areas– Supported systems and hardware – Installation, Update, and Configuration

• Demonstrate awareness of some of the major new features of HP-UX 11i v3 in the following areas– Flexible Capacity Features– Secured Availability Features– Simplified Management Features

As you can see from the objectives, the overall goal of this section is to provide an overview of the major changes at HP-UX 11i v3. Much of the material in this section is covered in more detail in the remainder of this course.


March 2007 Tour-3

March 20073

Release Review

Intel® Itanium®& PA-RISC

B.11.23B.11.23.0409

HP-UX 11i v2 update 2 (v2UD2)

Intel® Itanium®B.11.23HP-UX 11i Version 2 (v2)

B.11.31

B.11.22

B.11.20

B.11.11

Release Identifier

Intel® Itanium®& PA-RISC

HP-UX 11i v3

Intel® Itanium®HP-UX 11i Version 1.6 (v1.6)

Intel® Itanium®HP-UX 11i Version 1.5 (v1.5)

PA-RISCHP-UX 11i Version 1 (v1)

ArchitectureOfficial Name

HP-UX 11i v3 is the latest HP-UX 11i release. It is intended for both Itanium-based and PA-RISC systems.


March 2007 Tour-4

March 20074

Purpose of HP-UX 11.31HP-UX 11i v3 is the next enterprise release delivering expanded infrastructure for the Adaptive Enterprise in a multi-OS world • Competes with IBM's On Demand, Power architecture and AIX• Delivers enhanced performance and feature capabilities for Montecito-

based platforms • Delivers the enablers for a more competitive virtualization solution,

including both vPars and Integrity VM• Enhanced HP-UX I/O infrastructure for improved scalability,

manageability and agility• Improves interoperability with other UNIX systems

HP-UX 11.31 fulfills strategy• Targeted at both Itanium-based and PA systems

HP-UX 11i v3 is designed to take full advantage of the Intel® Itanium® 2 architecture to deliver high-performance capabilities for demanding applications such as online transaction processing and decision support, while offering outstanding cross-architectural interoperability, compatibility, and manageability features. HP-UX 11i v3 is also released on HP’s PA-RISC systems.

HP-UX 11i v3 is an enterprise release delivering the next level of virtualization and automation capabilities. The release supports both HP 9000 and HP Integrity servers, including the new dual-core Intel Itanium 2 based systems. HP-UX 11i plus Integrity delivers flexible capacity, secured availability and simplified management.

HP-UX 11i v3 builds on an already competitive virtualization solution with the HP Virtual Server Environment. Some key highlights of HP-UX 11i v3 include advancements in performance, next generation mass storage stack, increased capacities for username, LUN size and file size, NFSv4, more continuous availability, security without compromise, and next generation system management.

This new version of HP-UX 11i features a common installation media for both architectures and offers cross-architectural interoperability, compatibility, and quality unmatched by competitors.


March 2007 Tour-5

March 20075

HP-UX 11i v3 Delivers Leadership PerformanceGreater than 30% performance improvements over HP-UX 11i v2 on the same serverWorld's fastest and best price/performance TPC-H 10TB benchmark• Measures business intelligence performance• Achieved on a Superdome server with 64 Montecito processors (128 cores)

running HP-UX 11i v3 and Oracle 10g R2• Delivered 171,380 tpmC at a price/performance of $38.98/QphH

World's fastest SAP SD 2 Tier benchmark ever• Tests performance of ERP applications • Achieved with HP-UX 11i v3 on an HP Integrity Superdome with 64 Dual-Core

Itanium 2 (Montecito) processors and 14 MSA 1000 StorageWorks arrays• Delivered 152,530 SAPs and 30,000 SD users

Improved performance• Unified File Cache (UFC)• Enhanced HP Logical Volume Manager (LVM) striping and mirroring• Networking

For up-to-the-minute updates on HP-UX 11i performance• Visit www.hp.com/go/hpux11iperformance

The newly designed HP-UX 11i v3 release delivers leadership performance. It achieves greater than 30% performance improvement over HP-UX 11i v2 on the same server for even faster customer application performance by simply upgrading.

HP-UX 11i v3 has the world's fastest and best price/performance TPC-H 10TB Publication. This benchmark measures business intelligence performance and was done on a Superdome server with 64 Montecito processors (128 cores) running HP-UX 11i v3 and Oracle 10g R2. The benchmark delivered 171,380 tpmC at a price/performance of $38.98/QphH.

HP-UX 11i v3 has the world's fastest SAP SD 2 Tier benchmark ever! This benchmark tests the performance of ERP applications and was run with HP-UX 11i v3 on an HP Integrity Superdome with 64 Dual-Core Itanium 2 (Montecito) processors and 14 MSA 1000 StorageWorksarrays. The system delivered 152,530 SAPs and 30,000 SD users.

Additionally, HP-UX 11i v3 has improved performance with the Unified File Cache (UFC), enhanced HP Logical Volume Manager (LVM) striping and mirroring, and networking.

For up-to-the-minute updates on HP-UX 11i performance, visit www.hp.com/go/hpux11iperformance


March 2007 Tour-6

March 20076

HP-UX 11i v3 Delivers Scalability and AvailabilityIncreased scalability• Double the number of processes• Increased username/hostname length• Larger file size• Larger LVM volume size• More Logical Units (LUNs)

Mainframe-class UNIX system availability• Hot swap processors and memory

Enhanced disaster tolerance and manageability• Modular software selection• Online patching• Automated PCI I/O recovery• Dynamic Root Disk cloning• Automated patch analysis for system maintenance and upgradesFor up-to-the-minute updates on HP-UX 11i• Visit www.hp.com/go/hpux11i

HP-UX 11i v3 on HP Integrity provides an architectural design for beyond the next decade with increased scalability including double the number of processes, increased username/hostname length, larger file size, larger LVM volume size, and more Logical Units (LUNs).

HP-UX 11i v3 provides mainframe-class UNIX system availability. It is an enterprise-class release with reliability features such as hot swap processors and memory deliver a mission-critical virtualized infrastructure designed to minimize or eliminate downtime.

HP-UX 11i v3 can eliminate unplanned downtime and lets customers take control of planned downtime while providing enhanced disaster tolerance and manageability with newly designed features such as modular software selection, online patching, automated PCI I/O recovery, Dynamic Root Disk cloning, and automated patch analysis for system maintenance and upgrades.

For up-to-the-minute updates on HP-UX 11i, visit www.hp.com/go/hpux11i


March 2007 Tour-7

March 20077

HP-UX 11i v3 Feature Overview (1 of 2)Integrated multipathing with the Next Generation Mass Storage Stack• Manages I/O devices, such as SCSI logical units (LUNs)• Enhances server scalability, adaptability, and performance while

retaining backward compatibility• New features include

– Flexible, agile and manageable LUN addressing– Native multi-pathing– Increased parallelization

• Enables enhanced storage scalability– Unlimited number of I/O busses, up from 256– 16384 LUNs supported per system, up from 8192 active LUNs– LUN size over 2TB– 32 distinct I/O paths to a LUN, up from 8

On this and the next slide is a very brief overview of some of the main new features in HP-UX 11i v3.

A key feature of HP-UX 11i v3 is integrated multipathing with the Next Generation Mass Storage Stack. The Next Generation Mass Storage Stack manages I/O devices, such as SCSI logical units (LUNs). In this release, the mass storage stack delivers functionality designed to enhance server scalability, adaptability, and performance while retaining backward compatibility. New features include flexible, agile and manageable LUN addressing, native multi-pathing, and increased parallelization.


March 2007 Tour-8

March 20078

HP-UX 11i v3 Feature Overview (2 of 2)New agile view of mass storage• New naming convention for persistent disk and tape device

special files• New minor number format that supports much larger I/O

configurations• Represents hardware pathing to disk and tape devices

New security and availability offerings• Provide increased resiliency, layered security and in-depth

protection, and multi-OS managementNew modular operating environments • Provide more flexibility in managing the products to install

and update on a system

There is a new view of mass storage, called the agile view. This view includes a new naming convention for persistent disk and tape device special files. It also has a new minor number format that supports much larger I/O configurations.

The agile view also represents hardware pathing to disk and tape devices in ways that support larger configurations and transparent multi-pathing. By default, most commands show a legacy view of mass storage compatible with prior releases. Users select the agile view with new command line options or GUI toggles, as documented for each command or tool.

The next generation mass storage stack enables enhanced storage scalability such as unlimited number of I/O busses, up from 256. There are 16384 LUNs supported per system, up from 8192 active LUNs. A LUN size over 2TB is supported. And, there are 32 distinct I/O paths to a LUN, up from 8.

New security and availability offerings provide increased resiliency, layered security and in-depth protection, and multi-OS management across HP-UX and other HP supported operating systems.

HP-UX 11i v3 offers a new modular operating environments structure that provides more flexibility in managing the products to install and update on a system. The new OE structure for HP-UX 11i v3 separates software components into several product categories, making it easier and more reliable to incrementally update a system with OE software components.


March 2007 Tour-9

March 20079

Supported Systems and Hardware

Montecito ProcessorSupported SystemsSupported Peripherals


March 2007 Tour-10

March 200710

Montecito OverviewMontecito is Intel® Itanium-2 8870Terminology tutorial:• Processor (was socket), • Core• Hyperthread (or hardware thread), LCPU in HP-UX

• CPU (it’s too ambiguous)90 nm version of Madison2 cores per processor1-2 hyperthreads per core• Up to 4 hyperthreads (or LCPUs) per processor

L3 cache: 24MB (12MB per core)130W die, 170W envelopeE.g. sx2000 with Montecito – 64 processors , 2 cores per processor, up to 2 hyperthreads per core means 256 max hardware threads (or LCPUs)11.23 (without HT)─>11.31 (with HT)─>


March 2007 Tour-11

March 200711

Montecito Split L2 Instruction and Data CacheMontecito has a larger, split L2 cache• Data – 256K• Instruction – 1M

Itanium architecture does not require hardware to maintain coherency between the i-cache and d-cacheMontecito may expose heretofore hidden software problems• Self modifying code may expose issues• Code stored as data and then executed without following protocol is at

risk• Older 11.23 HP-UX Java implementations fall victim• Code that self-modifies must follow the existing Self-Modifying Code

(SMC) related recommendations in the Intel Itanium Architecture Software Developer’s Manuals (revision 2.1 or later)

McKinley has a separate but smaller L1 split i-cache (16K) and d-cache (16K)• Small cache size effectively masked any coherency violations


March 2007 Tour-12

March 200712

Blades and Entry-level ServersBlades• All Blades (Itanium) are supported

– BL60p blade server• Hurricane, ATCA, Tobruk

IPF Entry-level Servers• Onyx, Ruby, Sapphire platforms• IPF Entry-level servers with all supported processors through Mad9 and Montecito

– rx2600-2, rx2620 (Long’s Peak) (Also rx1600, rx1620 entry-level server)• 1-2 CPUs, 4 PCI, 2U

– rx4640-8 (Mt. Diablo) (Also rx3600)• 1-8 CPUs, 6 PCI, 4U, 64 GB memory, 3MB L3 cache/6MB L3 cache

– rx5670 (Everest)• 1-4 CPUs, 10 PCI, 7U, 96 GB memory

– Nemesis, Pearl, BadgerPeakPA Entry-level Servers• rp3410-2, rp3440-4 with PA-8800 (800 MHz and 1 GHz) • StormPeak with Mako and Shortfin processors

This release of HP-UX 11i v3 release fully supports the following HP 9000 and HP Integrity servers. Additional information regarding HP servers can be found at the following Web site: http://www.hp.com/go/servers


March 2007 Tour-13

March 200713

Mid-range ServersIPF Mid-range servers• rx6600• rx7620, rx7640 (Eiger) and rx8620, rx8640 (Olympia) with

Madison, Hondo, and Mad9 IPF processors• Mittelhorn/IPF and Kona/IPF

PA Mid-range servers• rp4440 (Mt. Hamilton), rp7420 (Medel), rp8420 (Rainier)

– with Mako and Shortfin (a.k.a. Mako+) PA processors• rp7405, rp7410 (Matterhorn), rp8400 (Keystorne) w/

firmware 16.8 or later• Mittelhorn/PA and Kona/PA within 6 months of initial SR


March 2007 Tour-14

March 200714

High-end and Cell-based ServersIntegrity High-end servers• rx9610• HP Integrity Superdome (Orca/IPF through Mad9)

– Significant bus bandwidth improvements from PA-RISC– Support Management Station (SMS) is Windows 200x PC

• All SandDune/IPFPA-RISC High-end servers• All PA Superdomes (Superdome, Caribe, Pacu, Orca/PA)• All SandDune/PA, Shortfin, Mittelhorn processors within 6

months of initial SR


March 2007 Tour-15

March 200715

Cell-based systems and ccNUMA SupportHP's cell-based platforms are ccNUMA• ccNUMA = cache coherent, Non-Uniform Memory Access• Latency and bandwidth of a same-cell memory access is

better than accessing memory on a different cellFor ccNUMA platforms, HP-UX 11i v3 is ccNUMA-aware• Maintains good behavior for applications that are not

ccNUMA-aware• Gives ccNUMA-aware applications the ability to control their

memory placement as well as processor placementCore feature of HP-UX 11i v3


March 2007 Tour-16

March 200716

Unsupported Servers and WorkstationsUnsupported systems• All 32-bit PA-RISC servers• All Itanium-1 based systems (rx4610, rx9610, i2000)

Unsupported PA-RISC servers• High-end (same as HP-UX 11i v2)

– All T-Class servers– All V-Class servers

• Mid-range– N-class (rp7400)– All K-Class servers (same as HP-UX 11i v2)

• Low-end– All D-Class, E-Class, and R-Class servers (same as HP-UX 11i v2)– All A-class servers (A180/A180C, rp2400, rp2405, rp2430,

rp2450, rp2470)– All L-Class servers (rp5400, rp5405, rp5430, rp5450, rp5470)

Unsupported workstations• No PA-RISC or Integrity workstations (zx2000, zx6000) are supported

The following servers will not be supported on HP-UX 11i v3. They are still supported on previous HP-UX releases until the end of their hardware support life. The platforms based on the Stretch CEC and the Astro CEC will no longer be supported as well as some of the older platforms (V-class, T-class etc.) Those platforms who aren't supported on HP-UX 11i v3 will continue to be supported on their most recent supported release, either HP-UX 11i v1 or HP-UX 11i v2. For example, V-class and T-class are supported on HP-UX 11i v1; while, A-Class and L-Class are supported on HP-UX 11i v2.


March 2007 Tour-17

March 200717

I/O cards shipping on HP-UX 11i v3

8-port and 64-port Terminal MUX (MR: 3/01)8-port and 64-port Terminal MUX

Other

PCI-X 1000Base-SX and –T GigE / 2G FC ComboU320 SCSI/GigE Combo CardPCI-X 2-port 1000B-T/2-port 2Gb FC Combo1 port and 2-port 4Gb FC & 1 port and 2-port GigE HBA PCI-X

Combo

Hyperfabric II; PCI-X 2-Port 4X InfiniBand HCA (HPC), RoHSPCI-X 2-Port 4X InfiniBand HCA w/ HA and Database Support, RoHS

Cluster

4-port 10/100B-TX (A23); 10/100B-TX (RJ45)Next Gen 1000B-T and –SX (5701 chip)1000BaseSX and T Dual Port (Intel chip)10G Ethernet; 4-port 1000B-T Ethernet; 2-port serial (X25/FR/SDLC)PCI/PCI-X 1-port 1000Base-T and –SX Adapter

Networking

2G FC Tachlite; 2-port 2Gb FC; 2 port U320 SCSIU160 RAID - SmartArray 5304 (PA only)SmartArray 6402 2-channel and 6404 4-channel RAID1-port and 2-port 4Gb FC card PCI-X

Mass Storage

DescriptionCard Type

See the HP-UX 11i v3 Release Notes at http://docs.hp.com for product numbers and up-to-date lists.


March 2007 Tour-18

March 200718

Special I/O cards and legacy cards

Cluster: Hyperfabric (PCI 1X); HiPPi 800 (A4)Combo: 2port Ultra2-SCSI + 2port 100TMass Storage: FCMS – Tachyon; FWD SCSI; 2-port Ultra2 SCSI; 2-port FWD SCSI; 2-port FWD SCSI; RAID 4SiNetworking: 10/100B-TX (AUI, BNC, RJ45); FDDI Dual Attach; Ultra2 SCSI; 100B-FX; ATM 622 (MMF connector); ATM 155 (MMF connector); ATM 155 (UTP5 connector); Token Ring (4/16/100 Mb/s); Intel 82559 100BT; 4-port serial (X25/FR); ATM 155 MMF (V Class only)Other: PKC (Public Key Cryptography) (A3); 8-port Terminal MUX; 64-port Terminal MUX

No longer on CPL, and not supported on HP-UX 11i v3

Networking: Gigabit Ethernet (1000B-SX); Gigabit Ethernet (1000B-T)Mass Storage: FCMS – Tachlite; 1 port U160 SCSI; 2 port U160 SCSICluster: PCI-X 2-Port 4X InfiniBand HCA (HPC) and w/ HA & DB supp

Cards not on CPL, but still supported on HP-UX 11i v3

Obsidian USB/VGA PCI card (IPF only)Procurium GigE LAN/SCSI combo cardSAS card (Core for RuSa) (IPF only)1000BaseT Dual Port (Core only)ATI Radeon 7500 PCI Graphics CardSpecials (OCBU): 8 ports ACC (A13)

Special




March 2007 Tour-19

March 200719

Highlights of HP-UX 11i v3

System Installation, Update, ConfigurationFlexible Capacity FeaturesSecured Availability FeaturesSimplified Management Features


March 2007 Tour-20

March 200720

System Installation, Update, andConfiguration Highlights


March 2007 Tour-21

March 200721

HP-UX 11i v3 Packaging –Operating EnvironmentsNo Operating Environment bundles• Items noted under OEs are individual bundles and are de-

selectableTerminology change to Required, Recommended and Optional• Required are always selected and installed• Recommended and optional products are de-selectable for

cold install and updateCore is split into multiple bundles• One Required, one Optional and the rest Recommended• Allows customers more flexibility in what they load and

maintain


March 2007 Tour-22

March 200722

Additional OE Highlights to NoteCDE is now Optional• English was required in previous HP-UX releases• Need to specifically select CDE now

New localized bundles• HPUXLocales• Extn and Man bundles• Split out of main core bundle and can be deselected

New category tags• Previous releases just had OrderedApps

– All application products were here on Ignite-UX menu• 20+ new categories

– Including SupportTools, SystemManagement, CompilersDevelopment, DisksFileSystems, Localization, Manuals


March 2007 Tour-23

March 200723

Major Installation/Update DifferencesUpdate from HP-UX 11i v2 only• Not from HP-UX 11i v1

Disk Space Requirements have grown• Different enough to cause problems when updating


March 2007 Tour-24

March 200724

Disk Requirements Comparison

230 MB

32 MB (unless MTOE which is 20 MB)

2.7-4.5 GB

208 MB

4.5 GB (unless MTOE which is 1.5 GB)

304 MB

2.6-3.7 GB

HP-UX 11i v2 Size

1 GB/ (29% used)

112 MB (No MTOE)/home (5% used)

4.7-5.8 GB/opt (58-61% used)

512 MB/tmp (4% used)

8.5 GB (No MTOE)/var (3% used)

1.9 GB/stand (7% used)

3.8 GB/usr (71% used)

HP-UX 11i v3 SizeFile System


March 2007 Tour-25

March 200725

Cold Install or Update?Update from HP-UX 11iv 2 (B.11.23) Servers only• Update to same HP-UX 11i v2 OE or higher OE• Updating from HP-UX 11i v1 is not supported• Already have VxFS 5.0?

– Must copy data from your DLV 7 file systems and onto file systems created at layout version 5 or 6 because 11.31 ships with VxFS 4.1

Update Advantage• Retain user data, configuration, and applications

Cold-install supported from any supported configuration• See the Installation Configuration Requirements above

Cold Install Advantages• Use of Ignite-UX server makes clean standard configurations easy

– Use of Ignite-UX overwrites everything on the target volume• Partitions will be sized for 11.31

– Updating usually means that you will have to increase some file system partition sizes


March 2007 Tour-26

March 200726

HP-UX 11i v3 Hardware PathsAgile View• Reliability, Adaptability, Performance, Scalability• Dynamically change paths to device• Multiple paths to a device treated like single virtualized patch

– I/O distributed across the multiple pathsTypes of paths to a device• Legacy Hardware Path

– Used in releases prior to 11.31– Bus-nexus addresses separated by / leading to HBA, additional

address elements separated by .• Lunpath Hardware Path

– Use more targets and LUNs– Additional address elements printed in hex

• LUN Hardware Path– Virtualized path representing all the lunpaths to a single LUN– Virtual bus-nexus (virtual root node address of 64000)

• 64000/0xfa00/0x22


March 2007 Tour-27

March 200727

Security Considerations: HP-UX BastilleBastille is a security hardening/lockdown tool • Provides out-of-the-box security functionality

Bastille can be installed and run with Ignite-UX or Update-UX• Bastille 3.0 open source security is built into install process• May also appear during update

Bundle chosen determines degree of security• Take care! Highest levels disable most network access

– If any level is activated, logging in as root over network is disallowed• Secure Shell is the only allowed method as DMZ level, for example

Full lockdownSec30DMZ

LockdownSec20MngDMZ

Host-based lockdownSec10Host

Install security infrastructure onlySec00Tools

Effect on System BehaviorBundle Name


March 2007 Tour-28

March 200728

Install-Time Security (ITS v1.0.4)New security step added to install/update process • Allows running of Bastille security lockdown engine during

system installation using one of the four Bastille configurations• Integrated with Ignite-UX

New functionality• New questions and lockdown configuration items• Diagnostic daemon configures for local-only use• Detect if system config activities loosened hardening


March 2007 Tour-29

March 200729

Differences in the Cold-Install to HP-UX 11i v3• Root, dump, and swap devices configured with new agile

addressing• PA-RISC BCH search command displays only legacy

hardware paths• Root Disk screen displays lunpath hardware path instead of

the legacy hardware path• On Languages screen, mark Yes for HPUXLocales• CDE is an optional product in HP-UX 11i v3

– If you require it, you must explicitly select the CDE bundle• Select and deselect software bundles on the Additional

Software screen– HP-UX 11i v3 offers several product categories

• Each product category contains software components that are marked as required, recommended, or optional


March 2007 Tour-30

March 200730

Update-ux – New TUI


March 2007 Tour-31

March 200731

Verifying the Install/Update Using LogsChanged log file on HP-UX 11i v3• HP-UX 11i v2 log file is /var/adm/sw/swagent.log• HP-UX 11i v3 log file is /var/opt/swm/swm.log

Carefully review contents of /var/opt/swm/swm.log• Pay particular attention to ERROR and WARNING messages• You’ll get LOTS of NOTE messages on Update• Not everything will appear in the log

– Bastille bundle selection, for example


March 2007 Tour-32

March 200732

New Software Deployment Tool –Software Manager (swm)Provides a CLI and TUI to manage software, including bundles, products, sub-products and filesets• Similar to SD commands except swm is a single command

with major modesExtends functionality provided by SD• And has the ability to update from one operating

environment to anotherHas four major modes of operation• ‘swm install’ installs software • ‘swm list’ lists software• ‘swm job’ provides job control interface to existing jobs• ‘swm oeupdate’ updates an operating environment


March 2007 Tour-33

March 200733

Ignite-UX v C.7.0 on HP-UX 11i v3Multipath-Aware Ignite• Is aware of all hardware paths leading to a device

Operating Environments restructuring affects Ignite-UX• Software products grouped as “Required,” “Recommended,”

and “Optional”Integrates with SWM rather than SD for software installation tasksUser selectable archive format for recovery archives and golden archives Ignite-UX checks minimum memory requirements• Will not permit installation or recovery to proceed if the

system is below the memory limitIgnite-UX bundle structure has been changed


March 2007 Tour-34

March 200734

Dynamic Root Disk (DRD) on HP-UX 11i v3DRD Software deployment tool improves the OE update experienceDRD safe software packaging• Enable HP-UX software to be patched and updated while the system is

doing productive work during normal business hours Software deployment tools enhanced• Support improvements to the HP-UX Operating Environments

Provides the ability to create and manipulate an inactive systemimage• Inactive system environment is a bootable system environment that is not

currently in use by the running systemSoftware packaging changes made to support DRD• Generate backward compatible packages that work with or without DRD

New software packaging attributes and environment variables are added for DRD safe packaging

This feature releases after the original release of HP-UX 11i v3.


March 2007 Tour-35

March 200735

Overview of Kernel Configuration Command Changes on HP-UX 11i v3• Revision of error, warning, and note messages for clarity• New options for kconfig, kcmodule, and kctune for control of

automatic configuration backups• Two new options for kctune command• kctune now allows some tunable values to be specified in

terms of the percentage of some system resource• Changes have been made to the kernel configuration

commands to improve resiliency and performance• Tunable parameter values may now be overridden on the

boot loader command line• Several other changes, including some obsolescences


March 2007 Tour-36

March 200736

PCI Card On-line Deletion on HP-UX 11i v3PCI card OLD allows deleting PCI cards and associated drivers without requiring a system reboot• PCI OLAR on HP-UX 11i v2 enhanced to include deletion• Now, full PCI OL*


March 2007 Tour-37

March 200737

Flexible Capacity Features


March 2007 Tour-38

March 200738

Performance and Scalability on HP-UX 11i v3Support Montecito processor features on Integrity systems• Allow 256 hardware threads

Larger memory configuration• Up to 2TB and pre-enabled up to 4TB

Increased file system and file sizes• File system sizes up to 40 TB and file sizes up to 16 TB

Performance monitoring system tools and interfaces• Processor performance monitoring tool, perfmon• Mercury library, libhg*, enables user programs to measure performance• sar and pstat reporting enhancements• Kernel instrumentation enhancements

– Used by OpenView GlancePlus, OpenView Performance Agent, Prospect, and sar(1M) command


March 2007 Tour-39

March 200739

Modeling the hyper-thread on HP-UX

In software context hyper threads are called logical CPUs (LCPU)

User Space

LP LP

HT HT

Kernel Abstraction of LCPUs

H/W (Cores and Hyper threads)

LCPU LCPU

LCPU LCPU


March 2007 Tour-40

March 200740

HT and LCPU Enablement SummaryHT can only be enabled and disabled in firmware at system boot• Firmware setting used to turn on/off hyper-threading for the entire

machine statically at bootLCPUs can be enabled and disabled dynamically at the granularity of a processor set (pset)• Provides a “safe-haven” for applications that prefer single-threaded

hardware – Real-time, high performance technical apps, etc.

• Disabled LCPUs are parked in firmware in a power saving modeFor a customer to use HT• HT must be enabled at boot in firmware• AND• LCPUs must be enabled dynamically in HP-UX

State of HT and LCPU enablement persists across reboots


March 2007 Tour-41

March 200741

Virtualization TechnologyA set of hardware enhancements to Intel platforms• VT-i refers to the Intel Itanium architecture and processor

virtualization enhancementsDesigned to simplify virtualization software• HP Integrity VM is HP’s software virtualization machine

Virtualization brings new end user value and new differentiation opportunities • Sufficient isolation between different virtual machines• Uncompromised performance of each virtual machine• Availability, reliability, and security of the entire platform


March 2007 Tour-42

March 200742

Virtualization SummaryVirtualization Technology for Itanium(VT-i) provides:• Guest ring de-privileging• Fewer traps into VM monitor (VMM)• Less faulting into VMM

Value proposition:• Simplifies the work by a virtual machine monitor (i.e. Integrity VM) to

provide service to virtual machine guests.• Significant performance improvement over non-VT-i operation

Impacts:• IVM host (an altered HP-UX) changes to exploit VT-i

HP-UX response:• 11.23: none (although 11.23 IVM guests will work better on an 11.31

IVM host)• 11.31: IVM host begins taking advantage of some VT-i features • Post-11.31: IVM host makes full use of VT-i features

Platform Hardware

VM1

VM Monitor

VM0

Guest OS0

App AppApp...

... Guest OS1

App AppApp...


March 2007 Tour-43

March 200743

PCI On Line Deletion (PCI OLD)PCI OL* is an HA feature for interface cards• Is core HP-UX functionality• Minimizes customer risk and downtime• Allows “hot-plugging” of I/O cards

– Eliminates the need to reboot• On Line Deletion is new on HP-UX 11i v3

Benefits of the new PCI OLD feature• Remove bad cards• Move card resources from one Peripheral Device to another• Move card resources from one vPar to another• Remove card and replace with a different card• Perform Cell OL*

– Coming in an HP-UX 11i v3 update

Flexible Capacity



March 2007 Tour-44

March 200744

HP-UX 11i v3 Dynamic Resource Reconfiguration Features• Memory migration between Integrity VM guests• Dynamic memory migration between vPars guests• Cell OLA to nPars• Cell OLA to Integrity VM host• Cell migration between nPars• Cell migration between Integrity VM hosts• Cell OLD with physical removal from nPar• Cell OLD with physical removal from Integrity VM host• Cell OL* delivered post-LR in later HP-UX 11i v3 update• Integrity VM has a separate release schedule


March 2007 Tour-45

March 200745

Dynamic Resource Reconfiguration & Cell OL*Dynamic Resource Reconfiguration• Ability to change hardware resources used by OS instances

– Improves resource utilization– Satisfies application service level agreements

Cell OL* • Coming in a later HP-UX 11i v3 update release• Dynamically add/delete cell board to/from running OS

instance– Cell board includes CPUs, memory, and (optionally) I/O– Includes when cell is physically inserted/removed and when cell

is logically reassigned• Cell iCAP and Cell migration

• Cell OL* internal infrastructure used to implement CPU and memory migration for vPars and Integrity Virtual Machines



March 2007 Tour-46

March 200746

Understanding WBEM and EVMWBEM is HP’s strategic management infrastructure• Is industry standard• Ties together multiple HP-UX, Linux, & Windows systems• Provides secure distributed management• Includes object instances, methods, and indications (events)

EVM is HP-UX’s lightweight event handling system• Provides HP-UX-specific event subscription and notification interfaces and

an event delivery mechanism• Unifies HP-UX low-level kernel and user space events• Is usable within the kernel and in single user mode• Is optimized for events

– Does not support instances or methods• Has interfaces that are callable from C and shell scripts

– Interfaces are non-standard• Events are available as WBEM indications via the EVM CIM provider


March 2007 Tour-47

March 200747

iCAP and CPU MigrationgWLM uses iCAP commands to migrate CPUs• iCAP commands maintains BCS compliance

– Use iCAP authorization mechanism• Implemented by core deactivation in one partition• Followed by core activation in another

Core activations• Two parts to iCAP core activations in nPars

– Assert compliance– Activate cores

• Three parts to iCAP core activations in vPars– Assert compliance– Activate cores via migration of the core to the OS instance


March 2007 Tour-48

March 200748

HP-UX 11i v3 Mass Storage StackRe-architected Mass storage stackKey Features• Native multi-pathing built-in• Agile device files based on LUN WWID addressing• Device files and dev_t and path/location independent

– dev_t fully opaque• No longer encodes path (cXtYdZ) or device specific options in

minor number

• New features for management and trouble-shooting


March 2007 Tour-49

March 200749

HP-UX 11i v3 to 11i v2 I/O Stack Comparison

8K16KMax LUNs per system – tested

NoYesNative Multi-Pathing & Load Balancing

25616MMax storage controllers (bus instance limits)

NoYesAgile Addressing

NoYesAutomatic Device Discovery

NoYesDynamic LUN size expansion

16K64KMax LUN paths per system - tested

832Max paths per LUN - tested

32K16MMax LUNs per system – Architectural

HP-UX 11i v2

HP-UX11iv3

Product/Functionality


March 2007 Tour-50

March 200750

Agile Addressing and Multi-pathing OverviewAgile Addressing• Also known as Persistent LUN Binding• Persistent Device Special Files• New naming convention for mass storage devices• Virtualized hardware path for multi-pathing

Multi-pathing• Built-in multi-pathing• Transparent load balancing

– Choice of load balancing algorithms• Automatic handling of path and device changes• Integration with management software• Health tracking of mass storage devices


March 2007 Tour-51

March 200751

Table of Persistent and Legacy DSF Names

Autochanger device (raw access)

/dev/rac/c#t#d#_options/dev/rchgr/autoch#

Tape device(raw access)

/dev/rmt/c#t#d#options/dev/rtape/tape#options

Partition on the disk (raw access)

/dev/rdsk/c#t#d#s#/dev/rdisk/disk#_p#

Partition on the disk (block access)

/dev/dsk/c#t#d#s#/dev/disk/disk#_p#

The entire disk (raw access)

/dev/rdsk/c#t#d#/dev/rdisk/disk#

The entire disk (block access)

/dev/dsk/c#t#d#/dev/disk/disk#

DescriptionLegacy DSF NamePersistent DSF Name


March 2007 Tour-52

March 200752

Changes to I/O Commandsioscan – Displays views of I/O hardware & devicesinsf – Creates device files for adapters & devicesmksf – Creates device file for specific devicelssf – Displays device & dsf informationrmsf – Deletes the DSF, or I/O nodesioinit – Allows modification of ioconfig file• Allows online reassignment of instances if driver supports it via -f option

– User specifies file containing information on list of instances to be reassigned

– Limitation that number of entries in file cannot exceed 14 at a time• Call ioinit several times to reassign more than 14 instances online

iofind – Migrates old DSFs to new style persistent DSFsiobind – Changes driver bindingio_redirect_dsf – Allows transparent device replacement


March 2007 Tour-53

March 200753

Display legacy hw path, lunpath hw path, and LUN hw path Mappings


March 2007 Tour-54

March 200754

New scsimgr Command


March 2007 Tour-55

March 200755

USB-00 Subsystem and Device DriversDynamically managed device file system• Dynamic device special file creation and removal

Additional USB features• Plug-and-play of USB devices• Support for mass storage drivers

– USB CD-ROM/RW– DVD-ROM/+RW

• Boot/install from HP USB DVD devicesSupports mass storage encryptionDynamically extensible • Allows for fast development of new USB device drivers• Object-oriented run-time infrastructure

Replaces legacy USB stack previously in various drivers• HCD, HUB, HID, USBD legacy drivers removed


March 2007 Tour-56

March 200756

File System Tunables Changes on HP-UX 11i v3More tunables converted to dynamic• No need to reboot improves availability

Several tunables made automatic• Memory changes cause tunable change

Usability issues addressed• Unit tunables: percent(%), suffixes (K/KB/M/MB/GB)

Number of tunables reduced by more than ten• Made private, deprecated, obsoleted, or removed

Agility

Simplicity


March 2007 Tour-57

March 200757

Capacity Expansion

HP-UX File / File System SizesIndividualTestedArchitectural

8EB

8EB

2TB#

2TB

File Size

Customer driven

VxFS - 32TB*

32TB

2TB

FS Size

VxFS4.1 – 8EB;Customer driven

8EB11.XX

% HFS – 128GB;VxFS4.1 – 8EB;

VxFS - 16TB*8EB11iV3

% HFS – 128GB;VxFS3.5 –

FS 32TB, F 2TB;

2TB8EB11iV2

% HFS –128GB;VxFS - 2TB;

2TB2TB11iV1

FS limitsFile SizeFS Size

* Qual targets # OS – 8EB % HFS deprecated

Value


March 2007 Tour-58

March 200758

New fsdaemon on HP-UX 11i v3Allows new or modified file system to be installed on running system• File system recognized immediately without reboot• File system simply needs to install a new executable• File systems can have functionality added dynamically

User-level daemon to identify file systems• Calls message-related routines for each subsystem in designated /sbin

directories until the device is claimed– Returns identity and status to caller– Install program (over)writes the executable file in /sbin

Provides better time-to-market for new or upgraded file system types• HP and third party file systems supported• Commands and libraries that used to contain dependent code and code

statically-linked to them no longer need to be patchedValue

Agility


March 2007 Tour-59

March 200759

File System Stacking in HP-UX 11i v3

Base FS requires no changesMultiple stacked modules support• FS functionality as a stack of

cooperating modules• Stackable modules pushed above

existing “base” FS• Stacks are per mount point• Modules delivered as DLKM

User space support• Complete API

Possible applications• Change logging, versioning• Tracing FS activity, profiling customer’s

FS usage, customized auto-tuning

VxFS

SAFER

EFS

(or HFS)

User Application

VFS Layer

Agility


March 2007 Tour-60

March 200760

Unified File Cache (UFC) Overview• Integrates page cache and buffer cache• Provides coherency when accessing a file using both

read(2)/write(2) and mmap(2) system calls simultaneously– The read/write file system calls used the buffer cache to cache

file data prior to HP-UX 11i v3– The mmap system call used the page cache before HP-UX 11i

v3• Enables ports of NFS ONC 2.3 and VxFS 4.1• Improves compatibility with other Unix-based OSs• Potential performance improvements

The Unified File Cache (UFC) integrates and unifies the page cache and buffer cache to provide coherency for file access using read/write and mmap system calls. File systems use new interfaces, and the old interfaces are removed.

In HP-UX releases prior to HP-UX 11i v3, File Systems use the buffer cache to cache file data,and the mmap() interface uses the page cache to cache file data. If an application accessed the file using both read(2)/write(2) system calls and mmap(2) simultaneously, HP-UX did not guarantee coherency since data resides in two caches. With a Unified File Cache, coherency can be achieved.

Finally, there are potential performance improvements of applications that depend on coherency of page and buffer cache. These improvements will vary depending on the application.


March 2007 Tour-61

March 200761

UFC Key Improvements over Buffer Cache• All access of file in kernel space is virtualized• Virtual Memory Management subsystem enhanced to allow

faults in kernel address space– Limited to UFC today but can be enhanced to allow other types

of kernel access• Pages are cached until the page is re-used by another

process– Pages removed from the buffer cache cause an I/O– Overall performance improvement

• File pages cached on behalf of kernel can be paged out similarly to user pages– Allows easier paging– Helps Cell OLD to evacuate UFC kernel pages


March 2007 Tour-62

March 200762

New Features•RAID (0 + 1)•RAID (1 + 0)•Dynamic LUN

Expansion Support

•VG Modify

Performance•Large I/O

support•Performance

Tuning•Fine Grain

Striping support

High Availability•Disk OLR•Improved Error

detection•Improved Mirror

Recovery•Online Cluster

Reconfiguration

Manageability•FSWEB

integration•Volume Group

Suspend•Improved CLI

display commands

•Support for Legacy and new DSF’s

•EMT Support

Scalability•Increased

Logical Volume Size

•Increased default VG Values

LVM on HP-UX 11i v3LVM has key improvements for HP-UX 11iv3 • Full support of the new re-architected mass storage stack• New Features• Improved scalability• Increased performance• Improved System Management• Improved High Availability features

Providing key features and functionality in the following areas


March 2007 Tour-63

March 200763

Process Management Interface ExpansionRange of PIDs increased from max of 30,000 to 1,073,741,823, which is 2^^30-1Dynamic kernel tunable – nproc• New maximum value stated to be 256,000

Limit on username and groupname lengths expanded• Now 255 bytes, up from 8 bytes and 16 bytes

Longer node names supported• New limit up to 255 bytes from previous 8 byte limit

Longer hostname supported• New limit up to 255 bytes from previous 64 byte limit


March 2007 Tour-64

March 200764

HP Virtual Partitions (vPars) A.05.01New features in vPars in HP-UX 11i v3• Dynamic, online memory migration• Montecito hyperthreading support• Mixing A.04.02 and A.05.01 virtual partitions in same vPars

environmentIntegrates with HP-UX dynamic solutions• EVM, iCAP, PPU, PCI OL*, WLM, PRM• Limited VSE manager (read configuration only)• Future Fusion releases

– VSE manager integration


March 2007 Tour-65

March 200765

Secured Availability Features


March 2007 Tour-66

March 200766

Montecito Processor Power StatesAllow for a state choice of normal powerand low power for idle• Power savings of up to 50W over regular idle• Final stage of kernel idle can go into

PAL_HALT_LIGHT to save power• A processor removed via iCAP can go into

PAL_HALT_LIGHT to save power• PAL_HALT_LIGHT at final idle signals I-VM to

yield from idle guest

ProcessorPower States

(C-states)

C3C3

C0C0

C1C1

PAL_HALT_LIGHT PMI,

INIT,Reset,

Etc.PAL_HALT


March 2007 Tour-67

March 200767

Automated Processor Recovery (APR)Recovery for some transient CPU hardware error events• Cosmic ray/alpha particle events can cause transient errors• Examples include TLB corruption and register file corruption

Benefits of APR• Selective treatment of application versus OS failure

– Application cessation or Integrity-VM guest MCA– New application error recovery options

• Accurate, precise, and reliable error information– Potential HW/FW aid in testing and debugging methods


March 2007 Tour-68

March 200768

PCI Error Recovery – New on HP-UX 11i v3Detect, isolate, and automatically recover from PCI error• Avoids system crash

When error occurs on PCI bus with I/O card supporting PCI Error Recovery, automatic recovery steps are taken• Isolate PCI bus from the rest of the system• Attempt recovery from error

– Keep bus and I/O card quiesced if a nested error occurs• Re-initialize the bus


March 2007 Tour-69

March 200769

PCI OL* and Cell OL*Key components of SSHACovered in Flexible Capacity Section of this training• See OL* and On Demand Solutions

Notes on OL* on HP-UX 11i v3• Only one SSHA operation and ioscan can run at any time

– Next release of HP-UX should resolve• Cell OL* coming in later HP-UX 11i v3 update release

Cell OL* feature releases after the original release of HP-UX 11i v3.


March 2007 Tour-70

March 200770

System Fault Manager (SFM)Supported on all systems that support HP-UX 11i v3Collection of tools used to monitor the health of HP servers • Memory, CPU, power supplies, and cooling devices

Operates in the WBEM environment• WBEM indications can be logged in syslog

Features include• Event Manager

– Common Information Model Provider (EVM-CIM)• Error Management Technology (EMT)

Features not available on initial HP-UX 11i v3 release• SFM Indication Provider

– Use EVWeb Event Viewer to view equivalent indications• EVWeb Log Viewer

HP threshold indications equivalent to indications generated by High Availability Monitors are now supported• View HP threshold indications using the EVWEB Event Viewer


March 2007 Tour-71

March 200771

System Fault Manager – HP-UX 11i v3SFM never shipped on HP-UX 11i v1May also be new to many HP-UX 11i v2 customersNew SFM features since HP-UX 11i v2 June 2006• Event Manager-Common Information Model (EVM-CIM) Provider• Error Management Technology (EMT)• SFMIndicationProvider is unavailable

– View equivalent indications by using the EVWEB Event Viewer• Log Viewer is not available• HP threshold indications equivalent to indications generated by High

Availability Monitors are now supported• View HP threshold indications using the EVWEB Event Viewer• WBEM indications can be logged in syslog


March 2007 Tour-72

March 200772

Accessing HP-UX Error MessagesHP-UX 11i v2

Accessing HP-UX error message information:• Go to HP ITRC website and search

on error message• Examine each document returned

• Search may return: HPUXERR01• This is the outdated HP-UX Error

Message Catalog Manual that does not contain information on HP-UX Releases after January 1991

• Document is limited in scope

HP-UX 11i v3Accessing HP-UX error message information:

• Online HP-UX error utility on each Customer system

• Consolidated error information HP-UX 11i v3 release and onwards

• Cause and action text provided for errors


March 2007 Tour-73

March 200773

EMT GUI integrated with SMH

Custom solution administration

Simple Search

Advanced Search


March 2007 Tour-74

March 200774

Livedump on HP-UX 11i v3Performs a crashdump on a live system without a forced shutdown or panic of that system• Itanium-based platforms only

Use livedump to obtain a memory dump of the system• System stays up and running, remaining stable• Allows for subsequent offline analysis of system

Performance impact• Saves the memory onto a file system

– Causes extra system load during this save

Documentation• livedump(1M) man page

Availability


March 2007 Tour-75

March 200775

Dump time reduction on HP-UX 11i ReleasesIn HP-UX 11i v1 and HP-UX 11i v2• Two features to reduce system dump times

– Selection• Reduces the size of the memory to be dumped

– Compression• Reduces the size of the data that needs to be written to disk

In HP-UX 11iv3• New third mechanism added

– I/O parallelism• Increases the rate at which the data can be written to disk


March 2007 Tour-76

March 200776

Cache File System - CacheFSCacheFS is a general purpose file system caching mechanism• Improves NFS server performance and scalability by reducing server and

network loadHow does CacheFS work? • Data is cached on local disk when it is read from an NFS mounted file

system• Subsequent read requests are satisfied from the local disk cache

How is performance improved?• Local disk caching of remote NFS-served file systems reduces network

traffic• Reduced access requests to the server increases the server's performance

and allows more clients to access the serverPerformance improvements are dependent on the type of file system access• Good for file systems where data is read more than once

CacheFS on HP-UX 11i v3 was ported from Solaris ONC+2.3 code


March 2007 Tour-77

March 200777

Identity Management on HP-UXData Repositories• Red Hat Directory Server (LDAP Server)• LDAP-UX Integration (LDAP Client)

Authentication Services• HP-UX Identity Management Integration (HP IdMI)• HP-UX Select Access for IdMI (HP SA-IdMI)

Authorization Services• HP-UX Identity Management Integration (HP IdMI)• HP-UX Select Access for IdMI (HP SA-IdMI)• HP-UX Role Based Access Control (HP RBAC)

All are free on HP-UX


March 2007 Tour-78

March 200778

Security Containment Features on HP-UX 11i v3Compartments• Isolate unrelated resources on a system

Fine-Grained privileges• Processes are granted only privileges needed for task• Optionally granted only for time needed to complete task• Privilege-aware applications

– Elevate privilege to the required level for the operation– Lower it after the operation completes

Provide a highly secure operating environment No application modification requiredBoth technologies are part of the core


March 2007 Tour-79

March 200779

Simplified Management Features


March 2007 Tour-80

March 200780

HP System Management Homepage (HP SMH) OverviewWeb-based system administration tool for managing HP-UX 11i• Provides Web-based systems management functionality• At-a-glance monitoring of system component health• Consolidated log viewing• High performance UI that responds rapidly• Provides Terminal User Interfaces

SMH for HP-UX provides many key customer benefits• Host based authentication and tight integration with existing security

infrastructure• Management tools that consume minimal system resources• Includes “start on demand” capabilities• Highly responsive user interface supporting “access from anywhere” via a

browser• Usable “out of the box” (default installed) by root with no user

configuration• Seamless, secure integration with HP System Insight Manager (HP SIM)


March 2007 Tour-81

March 200781

SMH GUI on HP-UX 11i v3


March 2007 Tour-82

March 200782

SMH GUI View of fsweb Area


March 2007 Tour-83

March 200783

EVWeb Event Viewer Search by Event Category


March 2007 Tour-84

March 200784

Network Services Configuration - ncweb


March 2007 Tour-85

March 200785

Using nwmgr to get details on a LAN


March 2007 Tour-86

March 200786

Event Manager (EVM) – New on HP-UX 11i v3General mechanism for posting and distributing events from any part of the operating system to any interested partyComprehensive event management system• Works in cooperation with other event mechanisms• Enables event information to be accessed in a uniform

manner• Enables posting, receiving, storing, retrieving and monitoring

eventsEVM event is the basis for all EVM operation• Used to transport and store event information from many

sourcesProvides programming and user-level tools• For creation, display and management of events


March 2007 Tour-87

March 200787

Event Monitoring Service (EMS)Framework for monitoring system resources• Configures, checks resource status, and sends notification

when configured conditions are met• Provides a common interface for monitor configuration and

event notificationEMS monitors• Provide help primarily with fault and resource management• Are designed for use in high availability environments


March 2007 Tour-88

March 200788

Section SummaryThis section described• Overarching goals of HP-UX 11i v3• Major changes in HP-UX 11i v3 in the following areas

– Supported systems and hardware – Installation, Update, and Configuration

• Major new features of HP-UX 11i v3 in the following areas– Flexible Capacity Features– Secured Availability Features– Simplified Management Features


March 2007 Tour-89

March 200789

Learningcheck

See the Lab Guide.


March 2007 Tour-90

March 200790

Labactivity

See the Lab Guide.

HP-UX 11i v3 Delta System Installation and Configuration

March 2007 Installation-1


System Installation and Configuration Section 3

This section covers installing and updating HP-UX 11i v3 (11.31), software deployment options, and post-installation configuration tasks.



March 20072

Section ObjectivesUpon completion of this section, you will be able to• Describe changes to the OEs on HP-UX 11i v3• Describe HP-UX 11i v3 installation, update, and configuration requirements• Perform an HP-UX 11i v3 installation/update and troubleshoot issues• Perform post-installation/update tasks• Describe software deployment changes

– Software Manager– Ignite-UX– Update-UX– Software Distributor– Software Package Builder– Dynamic Root Disk (Pre-enablement)

• Software update while the system is up• Boot and Update

– Faster Boot– Boot-time override of Kernel Tunables– DLKM of I/O Drivers

• Perform post-installation/update configuration tasks

In this section, we will cover Installation and Update Considerations in the areas of Operating Environments, Installation/Update Differences & Requirements, Configuration Requirements, Cold Install or Update?, Peripherals Considerations, Supported I/O cards, Hardware Paths and Device Special Files, and Security.

Then we will cover both the Installation Process and the Update Process, including troubleshooting the installation/update. We will also overview some post-installation/update tasks.

This section includes a Software Deployment Module, which covers the new Software Manager (SWM). It also includes changes to Ignite-UX, Update-UX, Software Distributor (SD), and Software Package Builder (SPB).

A brief Boot and Update Module covers the new Dynamic Root Disk, Boot-time Override of Kernel Tunables, DLKM of I/O Drivers, and Faster Boot.

The section finishes with a Kernel Configuration Module and a Peripheral Device Configuration and Management Module.



March 20073

Installation andUpdate Considerations

Operating EnvironmentsInstallation/Update Differences & RequirementsConfiguration RequirementsCold Install or Update?Peripherals ConsiderationsSupported I/O cardsHardware Paths and Device Special FilesSecurity

If you are already familiar with the installation process on HP-UX 11i v2, then the process for HP-UX 11i v3 should be easy to transition to, because there are relatively few differences between the two. In this module we will cover the differences that do exist, so that the transition is made as straightforward as possible. We will cover updating to HP-UX 11i v3 versus performing a cold install.



March 20074

Installation and Update Considerations

Operating Environments

HP-UX 11i v3 has a new OE structure that provides more flexibility in managing the products. This sub-module describes the OE changes.



March 20075

Operating Environments on HP-UX 11i v3Foundation OE• Web, content, and front-end servers

Enterprise OE• Database application and logic servers • Foundation OE plus

– EMS HA monitors, MirrorDisk/UX, OV GlancePlus, PRM, Online JFSMission Critical OE• Application servers and database servers• Enterprise OE plus

– ServiceGuard and ServiceGuard NFS– Workload Manager and Workload Manager Tookit– ECM Toolkit

Technical Computing OE• Server applications using graphics applications and math libraries

No Minimal Technical Computing OE

Operating Environments (OEs) are tested and integrated sets of application bundles designed to work with the operating system and provide the functionality needed for your system’s purpose. HP-UX 11i v3 has a new OE structure that provides more flexibility in managing the products you wish to install and update on your system. The new OE structure makes it easier and more reliable to incrementally update your system with OE software components.

The HP-UX 11i v3 Foundation OE (FOE) is designed for the demands of Web servers, content servers, and front-end servers. This OE includes applications such as HP-UX Web Server Suite, Java™, and Mozilla Application Suite.

The HP-UX 11i v3 Enterprise OE (EOE) is designed for database application servers and logic servers. This OE contains the HP-UX 11i v3 Foundation OE bundles and additional applications such as OpenView GlancePlus Pak to enable an enterprise-level server. It also contains applications such as the Event Monitoring (EMS) High Availability (HA) monitors, MirrorDisk/UX, Process Resource Manager (PRM), and Online JFS 4.1.

The HP-UX 11i v3 Mission Critical OE (MCOE) is designed for the application servers and database servers. This OE contains the Enterprise OE bundles, plus applications such as HP ServiceGuard and Workload Manager to enable a mission-critical server. Specifically, it has ServiceGuard, ServiceGuard NFS, Workload Manager, Workload Manager Toolkit, and ECM Toolkit.

The HP-UX 11i v3 Technical Computing OE (TCOE) is designed for server applications. This OE contains extensive graphics applications and Math Libraries.

There is no longer a Minimal Technical Computing OE.



March 20076

HP-UX 11i v3 Packaging –Operating EnvironmentsNo Operating Environment bundles• Items noted under OEs are individual bundles and are de-

selectableTerminology change to Required, Recommended and Optional• Required are always selected and installed• Recommended and optional products are de-selectable for

cold install and updateCore is split into multiple bundles• One Required, one Optional and the rest Recommended• Allows customers more flexibility in what they load and

maintain

The Operating Environments no longer come in pre-packaged OE bundles. In other words, there are no longer bundles such as HPUX11i-OE, HPUX11i-OE-Ent, HPUX11i-OE-MC, and HPUX11i-TCOE. Instead, the contents of the OEs are individual, de-selectable bundles. This allows the system administrator more control over exactly what functionality is installed and maintained on the system.

There are three types of OE Software Components. Required components include software and administration tools needed to create a minimally bootable and maintainable system. Only drivers for basic hardware are included in this category. You may need to install additional drivers to use all hardware components. Software in this category cannot be deselected. Required components are always selected and installed.

Recommended components include software bundles that HP recommends you install because it fulfills software dependencies, if any exist. You can, however, manually de-select the bundles before you install or update your system.

Optional components include software bundles that are not installed or updated by default. You must manually select these bundles before you install or update your system.

The Core HP-UX is now split into multiple bundles. One is required, one is optional, and the rest are recommended. This allows customers more flexibility in what they load and maintain on their systems.

First, let’s highlight some of the key changes. Then we’ll look at the different packages.



March 20077

OEs – Highlighted Bundle ChangesNo longer an HPUXBaseAux bundle• Replaced with SysMgmtMin

SD is in a new bundle called SwMgmtMin• Previously was in HPUXBaseAux

HPUXEssentials recommended operating system bundle• Only deselect if absolutely sure the functionality is not required• Hewlett-Packard recommends loading HPUXEssentials

Many drivers originally required are now recommended• Do not deselect unless they are not used for your system

BaseVxFS, BaseLVM, MailServer, FTP and NameServer• No longer in core• Can roll in a quarterly release

The previous HPUXBaseAux required bundle is replaced with the required SysMgmtMin bundle.

The Software Distributor (SD) is now in the new SwMgmtMin bundle. SD was previously part of the HPUXBaseAux bundle.

The HPUXEssentials bundle is a recommended operating system bundle. Even though this means that it is de-selectable, only do so if you are absolutely sure that the functionality is not required. Hewlett-Packard recommends that HPUXEssentials be loaded.

Many drivers that were required in earlier HP-UX 11i releases are now recommended. However, you will not want to de-select these unless you are sure that they are not used on the system that you are loading.

Note that the BaseVxFS, BaseLVM, MailServer, FTP, and NameServer are no longer in the Core. This allows them to be rolled in quarterly releases.



March 20078

Required OE Bundle and Standalone ContentsOperating System Required bundle contents• HPUXMinRuntime

SysMgmtMin Required bundle contents• Kernel Config, UpdateUX, SCSIProvider, OLOSProvider,

SWGETTOOLS, OpenSSL, WBEM Services, iCAP, Device Manager, SysMgmtBASE, WBEMP-LAN, DiskFileSystems, EMS Framework, Network Config, Sec Config, UserGroups, Judy Libraries, nPartitionProvider

Required Standalone contents• Online diagnostics, SysFaultMgmt, BaseLVM, Gigabit

Ethernet (PCI), iEther (PCI), scsiU320, CommonIO, SAS HBA, USB, nParCmds, NFS, SwMgmtMin (SD), HPUX-Mailserver

This slide shows the required Operating Environment bundle and standalone contents. All standalone software can be easily removed after it is installed.



March 20079

Recommended Bundle Contents• Perl, Security Tools, Bastille, Secure Shell, Mozilla (inc. source)• FCProvider, FibrChanl XL2 PCI, FibrChanl FCD• Java JRE v1.5 Add-on, Java JDK v1.5 and Add-on, Java JPI v1.4• CIFS/9000 Server and Client, Pam Kerberos• PRM KernelSW and Libraries (No TCOE)• SysMgmtWeb, SecurePatchCheck, ParManager• HPUX Apache, HPUX Tomcat, HPUXWebmin, HPUX XML• HPUX-FTPServer, HPUX-NameServer, IP Filter, DistribSysUtil, UtilProvider,

VMGuestLib, VMProvider, vParProvider• Base-VXVM 4.1, Base-VXFS 4.1, RAID SA, gWLM Agent-trial• LDAPUX, FileSysProvider, GNOME GTK1.4• Java JRE v1.4, Java JRE v1.4 Add-on• Java JDK v 1.4 and Add-on, Java JRE v 1.5

This slide lists the contents of the Recommended Bundles. Note that the PRM bundles are not available on the TCOE.



March 200710

Optional Bundle ContentsOperating System Optional bundle• HPUX-SLP

Optional Bundle contents• HyperFabric, MUX, 10GigEther, Infiniband• IGNITE, JavaOOB, IDS (no TCOE), HP SIM• Security Level 10, 20, 30; IPSec• Netscape Directory Server v7• Mobile IPV6• SWPkgBuilder• PayPerUse• CDE• All Languages

This slide lists the contents of the Optional Bundles. Note that the Intrusion Detection (IDS) bundle is not available on the TCOE.



March 200711

HP-UX 11i v3 Operating Environments Contents

Foundation Operating Environment (FOE)

All items in the center of the diagram

SWGETTOOLSOpenSSLWBEM ServicesiCAP

Device Manager SysMgmtBASEWBEMP-LANDiskFileSystems

Kernel ConfigUpdateUXSCSIProviderOLOSProvider

EMS FrameworkNetwork ConfigSec ConfigUserGroups

Online DiagnosticsSysFaultMgmtBase LVM

CommonIOSAS HBAUSB

Gigabit Ethernet (PCI) iEther (PCI)scsiU320

PerlSecurity ToolsBastilleSecure ShellMozillaMozilla SourceFCProviderFibrChanl XL2 PCIFibrChanl FCD

Java JRE v1.5 Add-onJava JDK v1.5 Java JDK v1.5 Add-onJava JPI v1.4CIFS/9000 ServerCIFS/9000 ClientPam KerberosPRM Libraries (No TCOE)PRM KernelSW (No TCOE)

SysMgmtWebSecurePatchCheck ParManagerHPUX Apache HPUX TomcatHPUXWebminHPUX XMLHPUX-FTPServerHPUX-NameServer

IP FilterDistribSysUtilUtilProviderVMGuestLibVMProvidervParProviderBase-VXVM 4.1Base-VXFS 4.1RAID SA

gWLM Agent-trialLDAPUXFileSysProviderGNOME GTK1.4 Java JRE v1.4Java JRE v1.4 Add-onJava JDK v 1.4Java JDK v1.4 Add-onJava JRE v 1.5

HyperFabric (PCII)MUX (PCI)10GigEtherInfiband

Security Level 10Security Level 20Security Level 30Netscape Directory Svr v7

Mobile IPV6SWPkgBuilderPayPerUseIPsec

IGNITEJavaOOBIDS (No TCOE)HP SIM

Obs100BaseT-00Obs100BaseT-01ObsATM-00 ObsATM-01ObsB3187B ObsISEEPLatform

ObsFDDI-00 ObsFDDI-01ObsFDDI-02ObsFDDI-03ObsB3188BObsHPUXIPQOS

ObsTokenRing-00ObsTokenRing-01ObsTokenRing-02ObsRAID-00ObsB6192AA

ObsB7580AAObsB6816AAObsJava12ObsJava13ObsJava3dObsB6817AA

ObsT1298AAObsJ2804-J2805ObsJ3529AObsNeetscBrwsObsSCSI-00

Enterprise Operating Environment (EOE) (Recommended)

FOE plus:EMS HA MonitorsMirrorDisk/UXOV GlancePlus Pak Process Resource

ManagerOnlineJFS 4.1

Mission Critical Operating Environment

(Recommended) EOE plus: ECM ToolkitServiceguardServiceguard NFSWorkload Manager Workload Manager

Toolkit

ServersTechnicalservers

Technical ComputingOperating Environment(Recommended)All items in the center of diagram are included except where noted as “No TCOE)”

MLIBMPIGraphicsTechSysConf

Notes: • MTOE is no longer delivered. •All standalone software can be easily removed after it’s installed.

SysMgmtMin Required bundle contents:

Required Standalone contents:

Recommended bundle contents:

Operating System Required bundle contents: HPUXMinRuntime

Operating System Recommended bundle contents:

Judy LibrariesnPartiionProvider

NParCmdsNFS

SwMgmtMin (contains Software Distributor)

HPUX-MailServer

HPUXEssentialHPUXExtens: Jpn, Kor,SCh,TCHHPUXMsgs:Fre,Ger,Ita,Jpn,Kor,SCh,Spa,Swe,TCh

HPUXMan: Eng,JpnHPUXLocalesOVsmnpAgent

HPUX-DHCPv4HPUX-DHCPv6HPUX-NTP

HPUX-RAMDHPUX-TCPWRAPHPUXGatedMrouted

Optional bundle contents:

OBSOLESCENE bundle contents: Required during update onlyOperating System Optional bundle: HPUX-SLP

CDE All languages

This slide has the detailed HP-UX 11i v3 Operating Environments content definition. Items in the center are in all OEs, unless specifically noted.



March 200712

Additional OE Highlights to NoteCDE is now Optional• English was required in previous HP-UX releases• Need to specifically select CDE now

New localized bundles• HPUXLocales• Extn and Man bundles• Split out of main core bundle and can be deselected

New category tags• Previous releases just had OrderedApps

– All application products were here on Ignite-UX menu• 20+ new categories

– Including SupportTools, SystemManagement, CompilersDevelopment, DisksFileSystems, Localization, Manuals

– See table on next slide

There are several OE changes of special note that may easily go unnoticed on the previous slides.

The CDE bundle is now Optional. In previous HP-UX releases, English was required. Now, it needs to be specifically selected. There are new localized bundles including HPUXLocales and all of the Extn and Man bundles. These have all been split out of the main core bundle and can now be deselected.

There are new category tags. Previous releases just had OrderedApps. All of the application products fell into this one category on the Ignite-UX menu. Now, there are many more to make it easier for customers to decide what they want on their system.



March 200713

New Category Tags

LocalizationLocalization

Miscellaneous Utilities UtilitiesJava Tools and UtilitiesJava

System Management Tools

SystemManagementComputing Interoperability Tools

Interoperability

Diagnostic and Support Tools

SupportToolsInternet Software ToolsInternet

Security Level ChoicesSecurityChoicesInternet ServicesInetServices

Security ToolsSecurity High AvailabilityHighAvailability

Performance ToolsPerformanceI/O DriversDrivers

Product ObsolescenceObsolescenceFile Systems and Volume Management

DisksFileSystems

Networking InfrastructureNetworkingDesktop EnvironmentsDesktop

Migration to HP-UX ToolsMigrationCore HP-UXCoreOS

HP-UX Manual PagesManualsCompilers and Development Tools

CompilersDevelopment

The first and third columns are the Category Tags and the second and fourth columns are the Descriptive Titles.



March 200714

Installation and Update Considerations

Installation / Update Differencesand Requirements



March 200715

Major Installation/Update DifferencesUpdate from HP-UX 11i v2 only• Not from HP-UX 11i v1

Disk Space Requirements have grown• Different enough to cause problems when updating

Only updating to HP-UX 11i v3 from HP-UX 11i v2 is supported. Updating from earlier releases, including from HP-UX 11i v1, is not supported.

The disk requirements, which of course are dependent on a number of factors, for standard HP-UX file systems have grown significantly since HP-UX 11i v2. The disk space requirements from the Installation & Update Guide are listed on the following slide. However, note that this can vary greatly depending on what products are selected and deselected during the update or install. There is definitely a large range of possibilities.



March 200716

Installation Configuration RequirementsTo cold-install or update to HP-UX 11i v3, you must have• Supported HP-UX system

– Itanium-based servers include HP Integrity cx2600, rx16x0, rx26x0, rx3600, rx4640, rx5670, rx6600, rx76x0, rx86x0, rx9610, Superdome, BladeSystems BL60p

– Several Dual-Core Intel Itanium(2) HP Integrity and Superdome servers– PA-RISC servers include rp34x0, rp4440, rp74xx, rp84x0, HP 9000

Superdome– No workstation support

• Cold-install or update HP-UX 11i v3 software sources– HP-UX 11i v3 OE and Application (AR) media (DVDs)– SD Network Depot– Ignite-UX server

• 1 GB memory, minimum• 1 GB swap space, minimum• Approximately 24 GB of disk space to install server OEs

Note that documented minimums may be low compared to typical actual configurations

HP-UX 11i v3 (11.31) fully supports a wide range of HP Integrity and HP 9000 servers.

The supported Itanium-based Servers are the HP Integrity cx2600, rx16x0, rx2600, rx3600, rx4640, rx5670, rx6600, rx76x0, rx86x0, rx9610, and Superdome servers. It also supports the HP BladeSystems Itanium BL60p server. Additionally, HP-UX 11i v3, supports HP servers with Dual-Core Intel Itanium(2) processor 9000 sequence. These include the HP Integrity rx2620 server (2 sockets) with zx1 chipset, the HP Integrity rx4640 server (4 sockets) with zx1 chipset, the HP Integrity rx7640 server (8 sockets) with sx2000 chipset, HP Integrity rx8640 server (16 sockets) with sx2000 chipset, HP Superdome server (16 sockets) with sx2000 chipset, HP Superdome server (32 sockets) with sx2000 chipset, and the HP Superdome server (64 sockets) with sx2000 chipset.

The supported PA-RISC Servers include the HP 9000 rp34x0 and rp44x0 series, the HP 9000 rp74x0 and rp84x0 series, and the HP 9000 Superdome server.

HP-UX 11i v3 is not supported on workstations. Itanium Workstation customers use HP-UX 11i v2. PA-RISC Workstation customers use HP-UX 11i v1.



Minimal RequirementsThe slide shows the minimum set of system requirements for installing HP-UX 11i v3. Note that, as minimums, they are considerably smaller than virtually any system that you would actually encounter in a customer installation. (When was the last time you saw a system with only 1 GB of memory, for instance!) This makes them largely irrelevant from a practical standpoint, but they’re worth noting.System RequirementsTo cold-install or update HP-UX 11i v3, you must have the following:•Supported system•1 GB memory, minimum•1 GB swap space, minimum•6 GB disk space to accommodate EFI Boot Disk and HP Service Partition•24 GB disk space for the OE•HP-UX 11i v3 OE and application (AR) media

Use the DVDs in the HP-UX 11i v3 media kit when you are cold-installing or updating one system at a time.HP-UX 11i v3 OE media•Boot and install a new system or update an existing system.HP-UX Application media•Install applications not installed with the OE or install a newer version of an OE application.Consolidate your software sources in a network depot when you plan to cold-install or update many systems.•Use Software Distributor (SD) commands to create depots containing OS, OE, and other software bundles, then install or update from the depot using Ignite-UX or update-ux. For help with this method, refer to the swcopy(1M) manpage, the Software Distributor Administration Guide, and the Ignite-UX Administration Guide.Use an Ignite-UX server when you plan to create many similar systems•Use an Ignite-UX server to create a faster software source than an SD depot•Create a golden image from which to cold-install. A golden image is a snapshot of a known, good operating system installation and configuration for use in installing other clients. The copied (source) client is called the golden image. This install image can contain the OS and OE, other applications, and any needed patches. After the archive is in place, either on the Ignite-UX server or on another system, you can cold-install on each client system in a single-pass operation; you need to reboot each client only once. Please refer to the Ignite-UX Administration Guide for more information on golden images.



March 200718

Disk Requirements Comparison

230 MB

32 MB (unless MTOE which is 20 MB)

2.7-4.5 GB

208 MB

4.5 GB (unless MTOE which is 1.5 GB)

304 MB

2.6-3.7 GB

HP-UX 11i v2 Size

1 GB/ (29% used)

112 MB (No MTOE)/home (5% used)

4.7-5.8 GB/opt (58-61% used)

512 MB/tmp (4% used)

8.5 GB (No MTOE)/var (3% used)

1.9 GB/stand (7% used)

3.8 GB/usr (71% used)

HP-UX 11i v3 SizeFile System

As stated earlier, disk space requirements for standard HP-UX file systems have changed since HP-UX 11i v2. This is because of a number of factors, which include changes in the products that are included in a specific OE, additional products that are part of the release, and changes in the way that file systems are used.

The table summarizes the differences for typical installation scenarios that we have seen on systems in the lab ranging from rx2600s with the TCOE to rx8620s with the MCOE. From it, you can see that /stand has grown the most significantly as it is about six times larger! File systems / and /home have quadrupled; and, /var and /tmp have doubled.

Note that during installation, Ignite-UX (on the File System tab) shows a higher percentage of disk space used than the information in the table shows. The minimums enforced by Ignite-UX ensure that the cold install completes successfully without filling a file system.

Also note that to ensure a successful update to HP-UX 11i v3, make sure that you have at least as much disk space allocated to the file partitions listed, and that each partition has at least 10-20 percent free space to allow for any growth.

Finally, note that by default the amount of primary swap space configured will be one to two times the amount of memory in the system.



March 200719

/stand Size and Updating to HP-UX 11i v3Updates to HP-UX 11i v3 may fail due to lack of disk space in the /stand volume• Due to the larger size of the kernels• Update-UX stops if /stand is not large enough

DO NOT use lvextend command to increase the size of /stand• Doing so may render your system unbootable• IUG recommends either

– Using SMH to extend the /stand partition, or • NOTE: SMH uses lvextend though!• Refer to smh(1M) manpage or HP SMH Online Help

– Using Ignite-UX recovery to create a recovery image and resize the /stand partition• Boot from recovery image and resize /stand as you recover the system• For help creating a recovery image, refer to the Ignite-UX Administration

Guide available on the HP Technical Documentation Web site: http://docs.hp.com

Due to the larger size of the HP-UX kernels in HP-UX 11i v3, there is a chance that updates to HP-UX 11i v3 from HP-UX 11i v2 may not succeed due to lack of disk space in the /stand volume. If the default size for the /stand partition is too small for your environment, do not use the lvextend command to increase the size of the /stand partition. Doing so may render your system unbootable.

Instead, use either System Management Homepage to extend the /stand partition or Ignite-UX recovery to create a recovery image and resize the /stand partition. You can boot from the recovery image and resize /stand as you recover the system. For help using System Management Homepage, refer to the smh (1M) manpages or the HP SMH Online Help included with the product. For help creating a recovery image, refer to the Ignite-UX Administration Guideavailable on the HP Technical Documentation Web site: http://docs.hp.com

Note that SMH uses the lvextend command, so the more cumbersome, but safer method would be the IUX recovery method.



March 200720

Firmware ConsiderationsEnsure your system has the latest firmware installed• Needed to support latest versions of I/O adapters, mass storage devices, and

devices used when you install from media or a network depotRefer to http://docs.hp.com/en/hw.html#System%20Firmware• Matrix of system firmware for I/O adapters with HP-UX 11i v3 (B.11.31) boot

support• Minimum firmware requirements for HP-UX 11i v3

Obtain latest HP-UX 11i firmware updates• IT Resource Center Web site at http://itrc.hp.com

– Searchable patch database – Patch documentation that provides information on how to patch the firmware

• Business Support Center Web site at http://www.hp.com/go/bizsupport– Log in to your appropriate region– Click maintenance and support (for hp products), then find individual patches

and firmware– Subscriber’s Choice sends email notices for firmware updates

• At ITRC Web site, click maintenance and support, then support information digests

Firmware changes frequently. Make sure your system has the latest firmware installed to support, for example, the latest versions of I/O adapters, mass storage devices, and devices used when you install from media or a network depot.

For a matrix of system firmware for I/O adapters with HP-UX 11i v3 (B.11.31) boot support, as well as the minimum firmware requirements for HP-UX 11i v3, refer to the documents at http://docs.hp.com/en/hw.html#System%20Firmware

For the latest HP-UX 11i firmware updates, go to the IT Resource Center (ITRC) Web site at http://itrc.hp.com or the Business Support Center Web site at http://www.hp.com/go/bizsupport Log in to your appropriate region. Click maintenance and support (for hp products), then find individual patches and firmware. If you have to patch your firmware, the ITRC provides a patch database to search, as well as patch documentation that provides information on how to patch the firmware.

HP also provides the Subscriber’s Choice, which enables you to sign up to receive email notices for firmware updates. At the ITRC Web site, click maintenance and support (for HP products), then support information digests.



March 200721


Cold Install or Update?




March 200722

Cold Install or Update?Update from HP-UX 11iv 2 (B.11.23) Servers only• Update to same HP-UX 11i v2 OE or higher OE• Updating from HP-UX 11i v1 is not supported• Already have VxFS 5.0?

– Must copy data from your DLV 7 file systems and onto file systems created at layout version 5 or 6 because 11.31 ships with VxFS 4.1

Update Advantage• Retain user data, configuration, and applications

Cold-install supported from any supported configuration• See the Installation Configuration Requirements above

Cold Install Advantages• Use of Ignite-UX server makes clean standard configurations easy

– Use of Ignite-UX overwrites everything on the target volume• Partitions will be sized for 11.31

– Updating usually means that you will have to increase some file system partition sizes

Update means using the Update-UX tool to selectively overwrite the operating system and application software from a media or network source depot. An advantage of performing an update is that it leaves user data, configuration, and applications in place, thereby retaining system configuration information, as well as other files and applications.

You can update to HP-UX 11i v3 from HP-UX 11i v2 (B.11.23). Updating from any other release directly to HP-UX 11i v3 is not supported. If your system is running HP-UX 11i v1, you must first update to an HP-UX 11i v2 Operating Environment. Please see the HP-UX 11i v2 Installation and Update Guide for information on how to update from HP-UX 11i v1 to HP-UX 11i v2.

You cannot downgrade to a lower level Operating Environment, for example, from Enterprise OE (EOE) to Foundation OE (FOE). From an HP-UX 11i v2 Base OS, you may update to any OE. Or, from any given OE, you may update to the same OE or higher. The TCOE may only be updated to the TCOE. You cannot update between server Operating Environments and technical Operating Environments.

In addition, make sure your system meets the minimum system and disk space requirements before updating from HP-UX 11i v2 to HP-UX 11i v3. If you are updating, experience has shown that it is likely that you will have to resize some partitions on the disk in order to perform the update. If VxFS 5.0 has been used to create file systems with disk layout version 7, those disks will not be readable by the VxFS 4.1 that ships with HP-UX 11i v3. Before updating to HP-UX 11i v3, copy data from your DLV 7 file systems and onto file systems created at layout version 5 or 6.

Cold-install means installing system software on a new (uninstalled) or existing system by completely rebuilding the root volume group, erasing the existing operating system and data on that volume, and installing the new operating system and specified software and data. The cold-install process erases software on the root volume before installing. If you want to retain any existing software, make sure to back up that software before migrating or use update. Cold-installing using Ignite-UX overwrites everything on the target volume.



You can choose two different methods to cold-install HP-UX 11i v3 on a supported system. You may install directly from the DVD media. Or, you may create depots on servers using SD-UX or Ignite-UX and installing it over the network. All supported versions of HP-UX can be configured as Ignite-UX servers, which can then be configured to cold-install HP-UX 11i v3. By using Ignite-UX servers, you can ensure that a number of similarly configured systems gets a standardized configuration.

You can update to HP-UX 11i v3 on a supported system by using either the TUI or CLI of update-ux.An advantage of performing an update is that it leaves user data, configuration, and applications in place.

You can update rather than cold-install HP-UX 11i v3 when:• • You are updating from a supported HP-UX 11i v2 or HP-UX 11i v3 system. • • You are concerned about recovering unique applications and data on your root volume,

and do not want to write over non-OS files, which occurs when cold-installing HP-UX 11i v3.• • Each of your systems has a unique configuration.• • Your current disk space is sufficient for HP-UX 11i v3.

You can cold-install from any supported configuration. See the Installation Configuration Requirement section earlier in this module for a list of supported configurations.

You can cold-install rather than update to HP-UX 11i v3 when:• You have a new system.• You are managing several systems with similar OS configurations.• Your disk space needs reconfiguration. See Disk Requirement Comparison earlier in this module• Your systems are organized with clean separation of the OS from user, application, and data files.• Overwriting the root (/) volume on existing systems will not cause a loss of applications or data.• Your system configuration is not listed as a supported update path.

The HP-UX 11i v3 Installation and Update Guide, located in http://docs.hp.com outlines the process to cold-install a single system from local media. If you plan to install many systems simultaneously, use an Ignite-UX server. Additional information on Ignite-UX and newer versions are available at: http://docs.hp.com/en/IUX/



Supported Update Paths to HP-UX 11i v3You can update to HP-UX 11i v3 on a supported system by using either the TUI or CLI of update-ux.An advantage of performing an update is that it leaves user data, configuration, and applications in place.

You can update rather than cold-install HP-UX 11i v3 when:• You are updating from a supported HP-UX 11i v2 or HP-UX 11i v3 system. • You are concerned about recovering unique applications and data on your root volume,

and do not want to write over non-OS files, which occurs when cold-installing HP-UX 11i v3.

• Each of your systems has a unique configuration.• Your current disk space is sufficient for HP-UX 11i v3.

Supported Cold-Install Paths to HP-UX 11i v3You can cold-install from any supported configuration. See the Installation Configuration Requirement section earlier in this module for a list of supported configurations.

You can cold-install rather than update to HP-UX 11i v3 when:• You have a new system.• You are managing several systems with similar OS configurations.• Your disk space needs reconfiguration. See Disk Requirement Comparison earlier in this

module• Your systems are organized with clean separation of the OS from user, application, and

data files.• Overwriting the root (/) volume on existing systems will not cause a loss of applications or

data.• Your system configuration is not listed as a supported update path.

The HP-UX 11i v3 Installation and Update Guide, located in http://docs.hp.com outlines the process to cold-install a single system from local media. If you plan to install many systems simultaneously, use an Ignite-UX server. Additional information on Ignite-UX and newer versions are available at: http://docs.hp.com/en/IUX/



March 200725


Peripherals ConsiderationsSupported I/O cards




March 200726

Required Mass Storage DriversRequired mass storage drivers are automatically installed during HP-UX 11i v3 installation• HP PCI Tachyon TL/TS/XL2 Fibre Channel Driver• HP PCI Ultra160 SCSI Driver• USB-00

Certain mass storage drivers are required, which means they are automatically installed during HP-UX installation. They are the HP PCI Tachyon TL/TS/XL2 Fibre Channel Driver, the HP PCI Ultra160 SCSI Driver, and the USB-00.



March 200727

Peripherals Considerations• Before installing or updating to HP-UX 11i v3, ensure that the

drivers and I/O cards on your system are supported on the new release

• Run msv2v3check script to validate whether drivers, mass storage I/O cards, and mass storage devices installed on your system are supported on HP-UX 11i v3– Reports if any unsupported drivers, mass storage I/O cards,

and mass storage devices are found on your system– Checks minimum firmware versions required for these cards or

devices on your system to run properly on HP-UX 11i v3– Obtain msv2v3check script from the HP software depot

• http://www.hp.com/go/softwaredepot

Make sure that the drivers and I/O cards on your system are supported before installing HP-UX 11i v3.

You can run the msv2v3check script to validate whether the drivers, mass storage I/O cards, and mass storage devices installed on your system are supported on HP-UX 11i v3. This script will report if any unsupported drivers, mass storage I/O cards, and mass storage devices are found on your system. This script will also check the minimum firmware versions required for these cards or devices on your system to run properly on HP-UX 11i v3. The tool offers several options allowing users to choose what to display on the screen and/or in a log file. Refer to the msv2v3check (1M) man page for additional details.

This HP-UX 11i v2 tool is available as part of the MSV2V3Check package and can be obtained online from http://software.hp.com by searching for the keyword “MSV2V3Check”. Note: If the tool returns any WARNINGs or ERRORs, use the Mass Storage Update Guide at http://docs.hp.com to help you get more details on the required or recommended actions.



March 200728

Issues with Active/Passive DevicesConnected Active/Passive devices may cause long delays or a system hang• When cold installing or updating to HP-UX 11i v3 or

installing an Ignite-UX recovery archive• Avoid this by disconnecting all Active/Passive devices from

the system before installing HP-UX 11i v3 or an Ignite-UX recovery archive

Connecting Active/Passive device before installing Active/Passive Switch (APSW) plug-in may cause some commands to take longer to execute• Avoid this by installing APSW plug-in before connecting any

Active/Passive device to the system– Ensures that the plug-in takes control of the device

When cold installing or updating to HP-UX 11i v3 or installing an Ignite-UX recovery archive, connected Active/Passive devices will cause long delays (one hour or more) or may cause a system hang. To avoid this, make sure you disconnect all Active/Passive devices from the system before installing HP-UX 11i v3 or an Ignite-UX recovery archive.

In addition, connecting an Active/Passive device before installing the Active/Passive Switch (APSW) plug-in may cause some commands to take longer to execute. Make sure you install the Active/Passive Switch (APSW) plug-in before connecting any Active/Passive device to the system. This will ensure that the plug-in takes control of the device.



March 200729

I/O cards shipping on HP-UX 11i v3

8-port and 64-port Terminal MUX (MR: 3/01)8-port and 64-port Terminal MUX

Other

PCI-X 1000Base-SX and –T GigE / 2G FC ComboU320 SCSI/GigE Combo CardPCI-X 2-port 1000B-T/2-port 2Gb FC Combo1 port and 2-port 4Gb FC & 1 port and 2-port GigE HBA PCI-X

Combo

Hyperfabric II; PCI-X 2-Port 4X InfiniBand HCA (HPC), RoHSPCI-X 2-Port 4X InfiniBand HCA w/ HA and Database Support, RoHS

Cluster

4-port 10/100B-TX (A23); 10/100B-TX (RJ45)Next Gen 1000B-T and –SX (5701 chip)1000BaseSX and T Dual Port (Intel chip)10G Ethernet; 4-port 1000B-T Ethernet; 2-port serial (X25/FR/SDLC)PCI/PCI-X 1-port 1000Base-T and –SX Adapter

Networking

2G FC Tachlite; 2-port 2Gb FC; 2 port U320 SCSIU160 RAID - SmartArray 5304 (PA only)SmartArray 6402 2-channel and 6404 4-channel RAID1-port and 2-port 4Gb FC card PCI-X

Mass Storage


The slide shows the I/O cards that are shipping on HP-UX 11i v3.

For a current list of supported network drivers, mass storage drivers, I/O cards, and SCSI devices, refer to the HP-UX 11i v3 Release Notes at the HP Technical Documentation Web site: http://docs.hp.com/en/oshpux11iv3.html. For a list of supported and unsupported HP-UX I/O cards and mass storage devices, refer to the HP-UX Supported I/O Cards Matrix and the HP-UX Supported Mass Storage Devices Matrix at the HP Technical Documentation Web site: http://docs.hp.com. Basically, it is best practice to check the HP web site for product numbers and up-to-date lists.



March 200730

Special I/O cards and legacy cards

Cluster: Hyperfabric (PCI 1X); HiPPi 800 (A4)Combo: 2port Ultra2-SCSI + 2port 100TMass Storage: FCMS – Tachyon; FWD SCSI; 2-port Ultra2 SCSI; 2-port FWD SCSI; 2-port FWD SCSI; RAID 4SiNetworking: 10/100B-TX (AUI, BNC, RJ45); FDDI Dual Attach; Ultra2 SCSI; 100B-FX; ATM 622 (MMF connector); ATM 155 (MMF connector); ATM 155 (UTP5 connector); Token Ring (4/16/100 Mb/s); Intel 82559 100BT; 4-port serial (X25/FR); ATM 155 MMF (V Class only)Other: PKC (Public Key Cryptography) (A3); 8-port Terminal MUX; 64-port Terminal MUX

No longer on CPL, and not supported on HP-UX 11i v3

Networking: Gigabit Ethernet (1000B-SX); Gigabit Ethernet (1000B-T)Mass Storage: FCMS – Tachlite; 1 port U160 SCSI; 2 port U160 SCSICluster: PCI-X 2-Port 4X InfiniBand HCA (HPC) and w/ HA & DB supp

Cards not on CPL, but still supported on HP-UX 11i v3

Obsidian USB/VGA PCI card (IPF only)Procurium GigE LAN/SCSI combo cardSAS card (Core for RuSa) (IPF only)1000BaseT Dual Port (Core only)ATI Radeon 7500 PCI Graphics CardSpecials (OCBU): 8 ports ACC (A13)

Special


The slide shows the Special I/O cards that are shipping on HP-UX 11i v3. It also lists the cards that are no longer on the Current Price List (CPL), but are supported with the release of HP-UX 11i v3. Finally, legacy cards that are not supported on 11.31 are listed.




March 200731


Hardware Paths and Device Special Files




March 200732

HP-UX 11i v3 Hardware PathsAgile View• Reliability, Adaptability, Performance, Scalability• Dynamically change paths to device• Multiple paths to a device treated like single virtualized patch

– I/O distributed across the multiple pathsTypes of paths to a device• Legacy Hardware Path

– Used in releases prior to 11.31– Bus-nexus addresses separated by / leading to HBA, additional

address elements separated by .• Lunpath Hardware Path

– Use more targets and LUNs– Additional address elements printed in hex

• LUN Hardware Path– Virtualized path representing all the lunpaths to a single LUN– Virtual bus-nexus (virtual root node address of 64000)

• 64000/0xfa00/0x22

HP-UX 11i v3 introduces a new representation of mass storage devices, known as the agile view. In the agile view, disk devices and tape drives are identified by the actual object, not by a hardware path to the object. In addition, paths to the device can change dynamically and multiple paths to a single device can be transparently treated as a single virtualized path, with I/O being distributed across those multiple paths. This representation increases the reliability, adaptability, performance, and scalability of the mass storage stack, without the need for operatorintervention.

In HP-UX 11i v3, there are three different types of paths (numeric strings of hardware components) to a device:Legacy hardware path

• The legacy hardware path is the format used in releases prior to HP-UX 11i v3, and is displayed in the legacy view. It is composed of a series of bus-nexus addresses separated by ‘/’ leading to the host bus adapter (HBA); beyond the HBA, additional address elements are separated by ‘.’.

Lunpath hardware path• The lunpath format enables the use of more targets and LUNs than are permitted under

legacy hardware paths, and is printed in the agile view. It is identical in format to a legacy hardware path, up to the HBA (and represents the same path to the LUN). Beyond the HBA, additional elements are printed in hexadecimal.

LUN hardware path• The LUN format is a virtualized path that represents all the lunpaths to a single LUN. It is

printed in the agile view. Instead of a series of bus-nexus addresses leading to the HBA, the path contains a virtual bus-nexus (referred as the virtual root node) with an address of 64000. An example of a LUN hardware path is “64000/0xfa00/0x22”.



March 200733

Device Special Files on HP-UX 11i v3Device Special File (DSF) Types• Legacy DSF

– Locked to physical hardware path, or lunpath– Binding of DSF to device persists across reboots, but not

guaranteed to persist across installations– Each lunpath requires a different DSF

• Multi-pathed LUN has multiple DSFs

• Persistent DSF– Supports agile addressing and multipathing– Binding of DSF persists across reboots, but not guaranteed to

persist across installations

In a similar way to hardware paths, there are two types of DSFs for mass storage: legacy DSFsand persistent DSFs. Both can be used to access a given mass storage device independently, and can coexist on a given system.

A legacy device special file was the only type of mass storage DSF in releases prior to HP-UX 11i v3, so it is associated with the legacy view. It is locked to a particular physical hardware path, or lunpath, and does not support agile addressing. Each lunpath requires a different DSF, so a multi-pathed LUN has multiple DSFs, one for each lunpath.

A persistent device special file is associated with a LUN hardware path, and is seen in the agile view. Because it is based on the LUN hardware path, rather than the lunpath, it transparently supports agile addressing and multipathing. Like the LUN hardware path, the binding of device special file to device persists across reboots, but is not guaranteed to persist across installations.



March 200734

Device Special Files: Installing and UpdatingDSFs: Installing and Updating• Cold-install

– Automatically creates legacy and persistent DSFs– Uses persistent DSFs for boot, root, swap, and dump devices

• /etc/fstab, /etc/lvmtab, et. al. refer to persistent DSFs

• Update– Retains existing legacy DSFs

• Backward compatible, not affected by persistent DSFs– Creates persistent DSFs– Allows simultaneous access to device using legacy and

persistent DSFs

See “The Next Generation Mass Storage Stack: HP-UX 11i v3” at http://docs.hp.com

If you cold-install HP-UX 11i v3, both legacy and persistent DSFs are automatically created. By default, the installation process will configure system devices like the boot, root, swap, and dump devices to use persistent DSFs. This means that configuration files such as /etc/fstab, /etc/lvmtab, and others will contain references to persistent DSFs. If you update from HP-UX 11i v2 to 11i v3, existing legacy DSFs are retained, and persistent DSFs will be created. In addition, legacy DSFs are completely backward compatible, and will not be affected by any persistent DSFs on the same server. A device can be simultaneously accessed via legacy and persistent DSFs.

For more information on the new mass storage stack, see the whitepaper called, “The Next Generation Mass Storage Stack: HP-UX 11i v3” at: http://docs.hp.com/



March 200735

Boot Device Initialization and setboot Enhancements• setboot command modified to take LUN DSF as input• Customers specify a boot disk, not a path

– setboot interacts with I/O stack to get paths and state– setboot selects an active path for boot

• setboot subscribes to EVM events on path offline, lun online to update the boot path configured when current boot path goes offline

• Legacy hw_path input supported for backward compatibility and to reboot to older OS version boot disk.

The setboot command has been enhanced to enable or disable hyper-threading environment for the next boot on a Dual-Core Intel Itanium 2 platform. The following new option has been added to enable/disable hyper-threading environment: -m [ on | off ] enable or disable hyper-threading for next boot

The setboot command has been modified to accept a persistent device special file (DSF) as input. setboot selects any lunpath hardware path currently available to the corresponding LUN and writes it to stable storage for use as the bootpath at next boot. If this path happens to fail later, setboot will be notified via an EVM event and will automatically select an alternate available path to the LUN and reconfigure it to stable storage.

To maintain backwards compatibility, setboot continues to accept a legacy hardware path as input. However, the path stored in stable storage is no longer the legacy hardware path itself but is the corresponding lunpath hardware path. Also, no automatic failover will occur on that path, maintaining the same legacy behavior as in prior releases.

Although the setboot command continues to accept a legacy hardware path as input like in releases prior to 11i v3, the path it stores and displays is the corresponding lunpath hardware path. Therefore, the setboot output has been changed from prior releases.

NoteIf a legacy hardware path is provided as input to setboot, it is the corresponding lunpathhardware path that setboot will store in stable storage. So setboot will now display the lunpathhardware path instead of the legacy hardware path. If a persistent dsf is provided as input to setboot, the lunpath hardware path stored in stable storage and displayed by setboot may change automatically upon failure of this path due to setboot automatic path failover.



March 200736

Dump Device Initialization• Dump subsystem interacts with I/O stack to get paths for the

dump disk and their state– dumpconf selects an active path to configure as dump path

• Dump subsystem subscribes to EVM events on path offline, lun online to update the boot path configured when current boot path goes offline

• Enhanced dump interface drivers– Perform tagged queuing I/Os for faster dump

On HP-UX 11i v3 the dump subsystem interacts with the I/O stack to get paths for the dump disk and their state. Dumpconf selects an active path to configure as the dump path.

The dump subsystem subscribes to EVM events on path offline, lun online to update the boot path configured when current boot path goes offline.

Dump interface drivers have been enhanced to perform tagged queuing I/Os for faster dump.

Device Files: Installing and UpdatingIf you cold-install HP-UX 11i v3, both legacy and persistent DSFs are automatically created. By default, the installation process will configure system devices like the boot, root, swap, and dump devices to use persistent DSFs. This means that configuration files such as /etc/fstab, /etc/lvmtab, and others will contain references to persistent DSFs. If you update from HP-UX 11i v2 to 11i v3, existing legacy DSFs are retained, and persistent DSFs will be created. In addition, legacy DSFs are completely backward compatible, and will not be affected by any persistent DSFs on the same server. A device can be simultaneously accessed via legacy and persistent DSFs.



March 200737


Security




March 200738

Security Considerations: HP-UX BastilleBastille can be installed and run with Ignite-UX or Update-UX

DMZ.config

MANDMZ.config

HOST.config

N/A

Config File

Network-DMZ full lockdown: IPFilter blocks all incoming connections except HP-UX Secure Shell

Sec30DMZ

Lockdown: IPFilter firewall blocks incoming connections except common, secured, management protocols

Sec20MngDMZ

Host-based lockdown: firewall pre-enablement; some common clear-text services turned off, excluding Telnet and FTP

Sec10Host

Install security infrastructure without applying security; default bundle

Sec00Tools

Effect on System BehaviorBundle Name

Security Considerations: HP-UX BastilleHP-UX Bastille is a security hardening and lockdown tool that can be used to enhance security of the HP-UX operating system. It provides customized lockdown on a system-by-system basis by encoding functionality similar to Bastion Host and other hardening and lockdown checklists.

HP-UX Bastille (HPUXBastille) is included as recommended software on the Operating Environment media and can be installed and run with Ignite-UX or Update-UX. Configuration files are installed to /etc/opt/sec_mgmt/bastille and Sec00Tools is installed by default. Sec10Host, Sec20MngDMZ, and Sec30DMZ are selectable.

Each security configuration bundle provides incrementally higher security by locking down various protocols and services. Bastille uses a series of questions to determine which services and protocols to secure. Using one of the Install-time Security Configuration bundles applies a default security profile, simplifying the lockdown process.

At install- or update-time, you can choose one of the following security configuration bundles with each bundle providing incrementally higher security. The Sec00Tools security infrastructure bundle is default-installed on your system. By installing Sec00Tools, you can opt to run HP-UX Bastille at a later time to lock down your system. The selectable bundles lock down your system at install- or update-time. They depend on Sec00Tools to install the needed software to secure your system.



NOTE: When you select either the Sec30DMZ, or MngDMZ security level, IPFilter will restrict inbound network connections. For more information on how to add inbound ports to your /etc/opt/ipf.customerrules file, refer tothe HP-UX IPFilter (Version A.03.05.09 and later) Administrator's Guide and the HP-UX System Administrator’s Guide.NOTE:For more information about HP-UX Bastille, refer to the HP-UX 11i v3 Release Notes and the HP-UX System Administrator’s Guide.

Security Configuration BundlesWhen Bastille is installed, one of four Security Configuration bundles must be selected. The bundle determines the level of security that Bastille enforces; higher-level bundles imply higher-levels of security. Sec00ToolsThe Sec00Tools security infrastructure bundle is default-installed on your system. While this bundle does not implement any security changes at install- or update-time, it does ensure that the required software is installed. By installing Sec00Tools, you can opt to run Bastille at a later time to lock down your system.Sec10HostImplements host-based lockdown. No firewall is configured, and networking runs normally, including Telnet and FTP. Examples of security features include disabling login unless home directory exists, disabling NFS client & server daemons, deactivation of many security-compromising network ports (finger, tftp, etc.), and setting up a cron(1) job to run Security Patch Check automatically. Note that network login for root is disabled, as well.Sec20MngDMZLockdown level; Includes all of the previous, plus IPFilter firewall configuration that blocks incoming connections except common, secured, management protocols (HP-UX Secure Shell, HIDS agent, WBEM, web admin and web admin autostart). In addition to the introduction of the IPFilter, installing this Security Configuration bundle disables the ftp and tftpd services.Sec30DMZNetwork-DMS, or full, lockdown level; Includes all of the previous, plus IPFilter configuration blocks all incoming connections except HP-UX Secure Shell.



March 200740

Install-Time Security (ITS v1.0.4)New security step added to install/update process • Allows running of Bastille security lockdown engine during

system installation using one of the four Bastille configurations• Integrated with Ignite-UX

New functionality• New questions and lockdown configuration items• Diagnostic daemon configures for local-only use• Detect if system config activities loosened hardening

Install-Time Security (ITS) version 1.0.4 adds a security step to the install/update process that allows you to run the Bastille security lockdown engine during system installation with one of four configurations ranging from default security to “DMZ.” ITS includes the same four bundles as Bastille: Sec00Tools, Sec10Host, Sec20MngDMZ, and Sec30DMZ.

ITS 1.0.4 includes new questions and new lockdown configuration items. It also has local-only use of the diagnostic daemon and syslog. There is also new integration with Ignite-UX on the security tab.

Information can be found in the following documents:• HP-UX System Administrator's Guide: Security Management, available online at

http://docs.hp.com/en/oshpux11iv3.html• bastille (1M) manpage (add /opt/sec_mgmt/share/man/ to MANPATH)• Bastille User’s Guide, delivered in /opt/sec_mgmt/bastille/docs/user_guide.txt• HP-UX Bastille Web site at

http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6849AA

• HP-UX 11i v2 Installation and Update Guide, available online at http://docs.hp.com/en/oshpux11iv3.html



March 200741

Bastille 3.0 New Feature OverviewBastille drift analysis • Reports when configuration does not match policy

– Visibility into undone hardening

Improved ease of use• No need to re-run Bastille config, which risked breaking

system if changes had been intentional• Detect if hardening configuration was tampered with• Detect if system config activities loosened hardening

Systems Insight Manager (SIM) default configurationDetails on effects of levels are in the Installation and Configuration Guide• Also, look in /opt/sec_mgmt/bastille/docs/

HP-UX Bastille has been available on the HP-UX 11i v2 OEs since September 2004 (11.23 PI release). With the HP-UX 11i v3 release, HP-UX Bastille, version 3.0.x, includes several enhancements. These represent additional items that Bastille will be able to lock down, additional usability improvements, and a new ability for Bastille to ensure that each cluster node has a consistent set of security settings.A new feature called bastille_drift analysis is able to report when system's hardening/lockdown configuration no longer matches policy (Bastille config applied). This drift report provides visibility into undone hardening, to allow planned response without risking unexpected system breakage. It assists with regulatory/SOX compliance.Now, it is easy to tell whether any system's hardening configuration remains consistent with what was applied without risking system changes. Previously, you would need to re-run Bastille config and risk breaking system if change had been intentional, which is impractical on production systems.It is easier to detect if system hardening configuration has been tampered with to enable planned remediation.It is easier to detect if unintentional side effect of system config activities (e.g. installing new software or patches) loosened hardening configuration.New enhancements also include Bastille questions (hardening features).There is a pre-built HP Systems Insight Management (SIM) server Central Management Server (CMS)-hardened default configuration.



For additional information:• HP-UX System Administrator's Guide: Security Management, available online at

http://docs.hp.com/en/oshpux11iv3.html (specifically, Chapter 10)• bastille (1M) manpage (add /opt/sec_mgmt/share/man/ to MANPATH)• Bastille User’s Guide, delivered in /opt/sec_mgmt/bastille/docs/user_guide.txt• HP-UX Bastille Web site at

http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6849AA

• HP-UX 11i v2 Installation and Update Guide, available online at http://docs.hp.com/en/oshpux11iv3.html

Support is also offered through HP's IT Resource Center’s HP-UX Security Forum at http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FCategoryHome%2F1%2C%2C155%2C00.html&admit=-682735245+1157685896487+28353475



March 200743

Security ConsiderationsIf multiple Bastille bundles are selected, highest level will be appliedSecurity level can only be increased (w/o bastille -r)!• Once you’ve installed a higher level, you can only revert

– Idea is to protect from inadvertent decrease in security• To downgrade, revert to pre-Bastille security (bastille -r)

– Then, install appropriate Bastille bundle– Or, copy desired config file to

/etc/opt/sec_mgmt/bastille/configs and run bastille -b

Documentation• Man pages for bastille(1M) and bastille_drift(1M)• Also, look in /opt/sec_mgmt/bastille/docs/

Selecting Multiple Security Configuration BundlesIf multiple Security Configuration bundles are selected, the highest-level security selected determines the Bastille security level of the system.

Security Configuration BundlesSecurity level bundles determine the level of security that is installed on the system. Installing a higher-level bundle ratchets system security up, and once it’s been raised, it cannot easily be ratcheted down. It is not possible to uninstall a Security Level bundle and install a lower-level one, but it is possible to install a higher-level bundle. To revert to a lower-level of security, or remove Bastille security altogether, use the ‘bastille -r’ command, then install the lower-level Security Configuration bundle. See the man pages for bastille(1M) and bastille_drift(1M). Also, look in /opt/sec_mgmt/bastille/docs/.



March 200744

Installation Process

Tasks Prior to Cold Installing HP-UX 11i v3Cold-Install StepsDifferences in Cold Installing to HP-UX 11i v3Selecting & Deselecting Software Bundles

This section describes the process of installing HP-UX 11i v3.



March 200745

Tasks Prior to Cold Installing HP-UX 11i v3Select an HP-UX Console if needed• Itanium-based systems only

Back up any configuration files you want to reinstall• Configuration files in /etc• The contents of /usr/local• Any local home directories (that is, those you do not import from• another system)• Any configuration files located in the /etc/opt directories for installed software

Back up your system• Use any supported HP-UX backup software• Also, create an OS recovery image

Update your Ignite-UX server• If you intend to use Ignite-UX to cold-install HP-UX 11i v3 on more than one system

Locate source media and code wordsRefer to HP-UX 11i v3 Installation and Update Guide• Information on console selection is especially useful

Prior to cold-installing HP-UX 11i v3, perform these tasks.

Select an HP-UX Console (Itanium-based systems only), if appropriate. Refer to the HP-UX 11i v3 Installation and Update Guide for particularly useful guidance.

Back up any configuration files you want to reinstall. Specifically, consider backing up configuration files in /etc, the contents of /usr/local, any local home directories (that is, those you do not import from another system), and any configuration files located in the /etc/opt directories for installed software.

Back up your system using any supported HP-UX backup software. Also, create an OS recovery image, for example, using make_net_recovery or make_tape_recovery

If you intend to use Ignite-UX to cold-install HP-UX 11i v3 on more than one system, update your Ignite-UX server. The HP-UX 11i v3 DVD contains the complete Ignite-UX product. When you cold-install HP-UX 11i v3 from the media, a subset of Ignite-UX is used to perform the installation on a single system. Updating your Ignite-UX server and using it to update other systems ensures consistent kernel configuration with specific drivers, daemons, and kernel tunables on all systems. Use make_net_recovery or make_tape_recovery to create an OS recovery image.

Locate source media and code words.



March 200746

More Tasks Prior to Cold-Installing HP-UX 11i v3Ensure system meets system requirements to install and operate HP-UX 11i v3• File system sizes and disk size are especially important!

Complete preparation tasks covered on the previous slide• Create an operating system recovery image to protect your

data in the event of a system crashCollect available networking information and other system specific data• Refer to Installation and Update Guide for useful tables

There are a few tasks that must be double-checked for completion prior to cold-installing your system to HP-UX 11i v3. First, make sure that your system meets the system requirements to install and operate HP-UX 11i v3, which we covered earlier. File system sizes and disk size are especially important!

Ensure that you have completed the preparation tasks required to cold-install your system that were covered on the previous slide. Most importantly, make sure you created an operating system recovery image to protect your data in the event of a system crash.

Finally, make sure that you have available networking information and other data that you need to collect. A set of useful tables is provided in the Installation and Update Guide.



March 200747

Steps to Cold-Install to HP-UX 11i v3

This flowchart shows the steps to cold-install to HP-UX 11i v3. The general procedure is the same as cold-installing to HP-UX 11i v2. However, there are some differences that we will note on the following slides.



March 200748

Installation Steps - OverviewBoot system, interrupt autobootLoad and run install kernel

– See IUG for detailed instructions for both PA and IPF systems Select User Interface and Media Options

– UI options – Guided, Advanced, and Default without UI– Media options – Media only, Media with network, Ignite-UX server

Configure networking if needed– After filesets are copied to disk and system reboots, set_parms may run

If Guided or Advanced install, follow prompts– Advanced allows you to specify OE, root disk, file system type, swap

size, software, timezone, network parameters, root password, file system sizes, etc.

Perform post-load configuration– Set network, language, etc.– Can be bypassed if selected prior to fileset loading

The detailed steps in the installation process are in the HP-UX 11i Version 3 Installation & Update Guide, but here is an overview.Boot - Boot the system up. If the system is configured to autoboot, interrupt the boot process so that you get to the appropriate prompt for your system type, either PA-RISC or IPF. Load & Run Install Kernel - Then, load and run the install kernel. The HP-UX 11i v3 Installation and Update Guide has good steps to follow.Select Options - The first screen that you’ll be presented with is the “User Interface and Media Options” screen from which you select the Source Location (Media Only, Media with Network enabled, Ignite-UX Server) and User Interface (Guided, Advanced, No User Interface (use defaults), and Remote graphical interface on Ignite-UX Server) options.Where you go from here is going to depend on which of the options that you choose, obviously. Configure Networking - The system IP address, netmask, default gateway, and other network parameters are normally set at this point. This can either be done manually or via a DHCP (or Bootp) server.Provide Configuration Info - If you’re doing a Guided or Advanced install, you’ll need to follow the prompts or fill-in data on the various screens that present themselves. This is the same as it’s always been. Note that if you want to utilize the Bastille install-time security, you will need to select one of the Security Configuration bundles. By default, only the infrastructure (the base bundle) is installed.Once you get through all of that, the filesets will begin loading. Following the loading of the filesets, the system will reboot. Depending on the configuration, there may be one more screen (the local language selection, or GeoCustoms, screen), and then you’ll get to the boot prompt (or CDE login, depending).Post-Install Configuration - Once you’re up and running, you should verify that the installation has successfully completed by going through the logs, etc. (More on this later.)



March 200749

Differences in the Cold-Install to HP-UX 11i v3 (1 of 3)Root, dump, and swap devices• Configured with new agile addressing representation• Use persistent DSFs

– Although both legacy and persistent DSFs are createdPA-RISC boot console search command displays only legacy hardware paths• You can specify either hardware path in Boot command

Root Disk screen displays lunpath hardware path instead of the legacy hardware path• Select More Info to view legacy hardware path for selected root disk• The lunpath hardware path selected is used only to identify the Root Disk

itself• Any available path to that disk may then be used as boot path

– Normal to see a different lunpath hardware path to the disk used as boot path

During an installation, Ignite-UX configures the root, dump, and swap devices with the new HP-UX 11i v3 mass storage stack agile addressing representation. This means that, after installing, the commands that display the boot, dump, and swap devices will show them using the agile form. During a cold-install of HP-UX 11i v3, both legacy and persistent DSFs are automatically created. By default, the installation process will configure system devices like the boot, root, swap, and dump devices to use persistent DSFs.

On PA-RISC systems the boot console search or sea command will only display legacy hardware paths and will not display agile hardware paths. You will see the agile hardware path after booting your system. Please note that both forms of hardware paths are supported (legacy and agile) and you can specify either hardware path in the Boot command. However, only the legacy hardware path can be displayed from the Search command.

On the Root Disk screen of the Ignite-UX itool select the disk to store your root file system. Press Enter to view the choices. If you are unsure of what to choose, keep the default selection that has been calculated by the install program. The Root Disk screen displays the lunpathhardware path instead of the legacy hardware path. You can select More Info to view the legacy hardware path for the root disk selected. The lunpath hardware path selected is used only to identify the Root Disk itself, and any available path to that disk may then be used as boot path. Therefore, it is normal to see a different lunpath hardware path to the disk used as boot path.



March 200750

Differences in the Cold-Install to HP-UX 11i v3 (2 of 3)If you select VxVM or LVM on the File System Type screen• Then root disk cannot be moved to another SCSI bus or address that

results in a change in the hardware path to the device– If it is moved, you may not be able to boot safely from it

On Languages screen, mark Yes for HPUXLocales and verify language choice• Locale settings moved from CDE language bundle on HP-UX 11i v2 to

HPUXLocales bundle on HP-UX 11i v3CDE is an optional product in HP-UX 11i v3• If you require it, you must explicitly select the CDE bundle (CDE-XXX)

– This applies if you need dtterm, which is located in CDE• For some localization situations, dtterm is required

On the File System Type screen, if you select VxVM or LVM, the root disk cannot be moved to another SCSI bus or address that results in a change in the hardware path to the device. If it is moved, you may not be able to boot safely from it. This is similar to the limitation present in LVM.

On the Languages screen, make sure HPUXLocales(OE) is marked Yes. In addition, make sure the default language shown on this screen is the language you wish to install. Press Enter to view the choices. The locale settings that were previously in HP-UX 11i v2 and located in the CDE language bundle are now located in the HPUXLocales bundle. The HPUXLocales bundle contains internationalization support for many languages. This support includes date and time formats, currency, sorting methods, and so on.

CDE is an optional product in HP-UX 11i v3. If you require it, you must explicitly select the CDEbundle (CDE-XXX). This applies if you need dtterm, which is located in CDE. For some localization situations, dtterm is required, therefore CDE must be selected.



March 200751

Differences in the Cold-Install to HP-UX 11i v3 (3 of 3)Select and deselect software bundles on the Additional Software screen• HP-UX 11i v3 offers several product categories

– Each product category contains software components that are marked as required, recommended, or optional • HP recommends NOT deselecting recommended bundles or

removing them from your system unless you know for certain that the software contained in these bundles are not required for your operating environment

On the Additional Software screen, you can deselect the software bundles that are recommended and select optional software not installed by default. Browse the product list, marking your selections, then press Next to accept your selections and proceed to the Security Choices screen. HP-UX 11i v3 offers several product categories from which you can select additional software. In addition, each product category contains software components that are marked as required, recommended, or optional software components. HP recommends that you do not deselect recommended bundles or remove them from your system unless you know for certain that the software contained in these bundles are not required for your operating environment.



March 200752

Selecting and Deselecting Software Bundles

If you use the Guided Installation or Advanced Installations, then you can deselect the software bundles that are installed by default and select optional software not installed by default. From the Software tab you can select products from a list of categories to build your operating system. (If you choose the No User Interface option, then you cannot deselect the default-installed software bundles.)

HP-UX 11i v3 has a new OE structure that provides more flexibility in managing what products you wish to install on your system. The OE structure for HP-UX 11i v3 separates software components into several product categories making it easier and more reliable for you to incrementally update your system with OE software components.

CAUTION HP recommends that you do not deselect recommended software bundles or remove them from your system unless you know for certain that the software contained in these bundles is not required for your operating environment. In addition, software may have unstated dependencies. Deselecting software may prevent products with dependencies on the software you deselected from functioning correctly.



March 200753

Update Process

Tasks Prior to Updating to HP-UX 11i v3Installing/Updating Update-UXStarting the UpdateMonitoring the Update

Updating to HP-UX 11i v3 is possible from most HP-UX 11i v2 configurations as discussed earlier in this module. The update process uses Update-UX, and is similar to using that utility on previous versions of HP-UX.



March 200754

Updating to HP-UX 11i v3Process is similar to HP-UX 11i v2• Install the latest update-ux(1M) program• Run update-ux

Supports the HP-UX 11i v3 update paths• From HP-UX 11i v2 on both PA and Itanium-based systems• Checks made for supported hardware

update-ux is similar to previous versions• New –i option invokes swm TUI• New –p option runs analysis only

Bundles for selected OE will be automatically selected if you specify an OE at invocation• Choose other packages/bundles as desired

If you have either a PA-RISC or Itanium-based HP-UX system running HP-UX 11i v2, you may be able to update to HP-UX 11i v3 instead of performing a cold-install to HP-UX 11i v3. As with previous releases that supported updating from one version of HP-UX to another, there is an update utility that must be installed in order to perform the update. The bundle is Update-UX, and it’s on the HP-UX 11i v3 DVD.

As with the process, the behavior of the update-ux(1M) utility for HP-UX 11i v3 is similar to previous versions of this tool. The HP-UX 11i v3 version of update-ux comes with a new –i (interactive) option that invokes the new Software Manager (SWM) TUI. There is also a new –p option to perform an analysis run of update-ux. As with earlier releases, bundles for a selected OE will be automatically selected if you specify an OE at invocation. Otherwise, it will act as if you specified the OE that your system is currently running. However, as you have seen from the earlier OE module, there are several OE changes in this release that you will need to be very aware of.

Once you’ve installed the new version of update-ux, you can view the manpage for it.



March 200755

Steps to Update to HP-UX 11i v3

This flowchart shows the steps to update to HP-UX 11i v3. The general procedure is the same as updating to HP-UX 11i v2. However, there are some differences that we will note on the following slides.



March 200756

Installing Update-uxFrom a DVD Media• Step 1. Find the DVD-ROM device file name: ioscan -C disk -f -n -k | more• A device name associated with your DVD device should be displayed.

For example: /dev/dsk/c1t2d0• Step 2. Create the directory under root(/). For example: mkdir /dvdrom• Step 3. Mount the DVD onto the new directory as a file system. For

example: mount /dev/dsk/c1t2d0 /dvdrom• Step 4. Using swinstall, install the latest version of the Update-UX bundle

on the target system.– Ensure you use correct case to install the Update-UX bundle (in title

case)• This bundle contains the update-ux command (lowercase)

• swinstall -s /dvdrom Update-UXFrom a Depot • The depot example uses the syntax depot_server:depot_path

– swinstall -s depot_server:/var/11iv3/update-depot Update-UX

Installation of the Update-UX bundle is straightforward. The key is to remember that this is done using the HP-UX 11i v3 media on the system to be updated.

From a DVD MediaStep 1. Find the DVD-ROM device file name: ioscan -C disk -f -n -k | moreA device name associated with your DVD device should be displayed. For example: /dev/dsk/c1t2d0

Step 2. Create the directory under root(/). For example: mkdir /dvdrom

Step 3. Mount the DVD onto the new directory as a file system. For example: mount /dev/dsk/c1t2d0 /dvdrom

Step 4. Using swinstall, install the latest version of the Update-UX bundle on the target system.

NOTE Make sure you use the correct case to install the Update-UX bundle (in title case). This bundle contains the update-ux command (lowercase).

swinstall -s /dvdrom Update-UX

From a Depot The depot example uses the following syntax: depot_server:depot_path. For example:swinstall -s depot_server:/var/11iv3/update-depot Update-UX

After these steps have been successfully completed, you are ready to run update-ux(1M).



March 200757

Tasks Prior to Updating to HP-UX 11i v3• Identify all software products and bundles on your system

– /usr/sbin/swlist -l bundle -l product > /tmp/software_list• Rebuild the HP-UX kernel

– HP suggests running /usr/sbin/mk_kernel, fixing any problems indicated, and rebooting

– Better practice would be to ensure that you have a backup of your currently running kernel and kernel configuration!

• Rename your log files to make it easier to find problems encountered during an update– For example, rename /var/adm/sw/swagent.log to

/var/adm/sw/swagent.log.030107• Back up your operating system

– HP suggests using the Ignite-UX make_net_recovery or make_tape_recovery command

• Locate source media and code words– Refer to http://licensing.hp.com

Prior to updating to HP-UX 11i v3, perform these tasks.

Identify all software products and bundles on your system. For example, run /usr/sbin/swlist –l bundle –l product > /tmp/software_list

Rebuild the HP-UX kernel. HP suggests running /usr/sbin/mk_kernel, fixing any problems indicated, and rebooting. But, you may end up in a predicament if it does not work! So, a better practice would be to ensure that you have a backup of your currently running kernel and kernel configuration before doing the mk_kernel.

Rename your log files to make it easier to find problems encountered during an update. For example, rename /var/adm/sw/swagent.log to /var/adm/sw/swagent.log.030107

Back up your operating system using the Ignite-UX make_net_recovery or make_tape_recoverycommand. Note that these Ignite-UX recovery tools are intended to be used in conjunction with data recovery applications to create a means of total system recovery. HP does not recommend using Ignite-UX recovery tools to backup and recover data other than essential system data.

Locate source media and code words. Refer to http://licensing.hp.com



March 200758

Additional Tasks Prior to Updating to HP-UX 11i v3• Ensure you are updating from a supported migration path

– Basically, update from HP-UX 11i v2• Not from HP-UX 11i v1 or other 11.0 or 11.1 versions

• Ensure your system meets system requirements to update and operate HP-UX 11i v3– One of the absolutely most important of which is your file system

sizes!• More on this, and /stand in particular, shortly

• Ensure you have completed the preparation tasks from previous slide

• Finally, you must update Update-UX!

In addition to the preparation tasks outlined on the previous slide, ensure that you are updating from a supported migration path, which we covered earlier, but which is basically HP-UX 11i v2. Also, ensure that your system meets the system requirements to update and operate HP-UX 11i v3. One of the absolutely most important of which is your file system sizes!



March 200759

Updating Update-UX Prior to Updating System

You must install the latest version of Update-UX prior to updating your system. The latest version of Update-UX allows you to use the preview (-p) option, which is new for HP-UX 11i v3. Failure to install the latest version of Update-UX may cause the update to fail.

Use swinstall to update to the latest version of Update-UX. For example, run swinstall –s <source> Update-UX.



March 200760

Verifying the Update-UX Update

The version of /usr/sbin/update-ux was 11.11.86. Now it is 11.31.15.



March 200761

Starting the UpdateDetermine OE that will be used for the update• OE changes on HP-UX 11i v3 were covered earlier in this

module• Update from HP-UX 11i v2 on PA or Itanium-based systems

Determine HP-UX 11i v3 software source• If using the DVD media, it’s probably already mounted• If using a network depot, you will need the depot path

Preview the Update– /usr/sbin/update-ux –p -s /dvdrom HPUX11I-OE-MC

Start the Update– update-ux [-i] –s <depot path> <OE BUNDLE NAME>

• update-ux –s depot.hp.com:/depot/oscores/11.31/HPUX11I-OE-MC HPUX11i-OE-MC

Before you start the update, you need to determine which OE that you’re going to update to. You can use swinstall(1M) to determine which OE is currently installed. Use the HP-UX 11i Version 3 Installation and Update Guide to determine the supported update paths.

Starting the UpdateYou’ll need access to the HP-UX 11i v3 software, either over the network via a swinstall(1M) server, or via the DVD media. If you have used the DVD media to install the Update-UX bundle, then it will already be mounted. The examples shown on the slide assume that case. When you run update-ux(1M) two things are usually specified on the command line: the source of the software to be installed, and the bundle that should be selected. The source is specified as the argument of the “-s” option, and the OE name appears as the last thing on the command line. HPUX11i-OE-MC is an example of the OE name.

Before you update your system to HP-UX 11i v3, review the known problems in Appendix A, “Known Problems and Troubleshooting,” of the HP-UX 11i v3 Installation and Update Guide. Make sure to resolve any applicable issues before starting an update from HP-UX 11i v2 to HP-UX 11iv3.



March 200762

Update-ux –i Interactive Option

This run of update-ux was started using the new –i option to bring up the new interactive update-ux TUI.



March 200763

Update-ux –i Continued

Using the interactive mode of update-ux will run the new Software Manager, swm, and start the TUI. Note that output is logged to a new on HP-UX 11i v3 file, /var/opt/swm/swm.log.



March 200764

Update-ux – New TUI

The new Update-UX TUI has four tabs: Overview, Source Selection, OE Selection, and SW Selection. This screen shot shows the OE Selection tab. From here, you may select the OE that you wish to update to. By default, the OE that is currently on your system is selected.



March 200765

Update-ux TUI – Software Selection Tab

This screenshot shows the SW (Software) Selection tab. Notice the notations on the left for each software listed. The legend just below the tabs describes the meanings of the notations. For example, the notation S means that this was selected by the user.



March 200766

Update-ux –p Option

The update-ux –p option previews an update task by running the session through the analysis phase only.

Note that the biggest issue you may have with the update is, nicely enough, illustrated on this slide. This would be the insufficient disk space error. In the example shown here, /opt is not large enough for the update to succeed. If you try to extend /opt, you are likely to find that there are several daemons running in /opt that will need to be shut down.



March 200767

Monitoring the UpdateWatch the contents of the log files• tail –f /var/opt/swm/swm.log• You may wish to also check /var/adm/sw/swagent.log

Screen output is logged to• /var/adm/sw/update-ux.log

Might also want to capture screen output using script(1)• Start this before you run update for complete log

Since the system is running, it is possible to use standard HP-UX utilities to keep an eye on the progress of this process. The update-ux(1M) program writes messages to the swm log file, /var/opt/swm/swm.log, so if you do a “tail -f” on this file, you can watch the output being written. On HP-UX 11i v2, these messages were logged to /var/adm/sw/swagent.log. You may wish to check that log file as well.

If you want to capture all the keystrokes that were used, the script(1) command is handy. It writes all input and output (and error output) to a separate file as well as the screen, so it can be used to create such a record. Note that if you want to capture everything, including the start of the process, you’ll need to run the script(1) command before running update-ux(1M).



March 200768

Troubleshooting Installation & Update

Known Problems

In this sub-module, we will discuss known problems with installation and update and how to resolve them.



March 200769

Known Problems in Ignite-UX Version C.7.0.xKnown issue• Use Ignite-UX version C.7.0.x only to cold install HP-UX

– Do not use for any other task• Do not use Ignite-UX C.7.0.x to create a recovery archive

Fix• Download and install Ignite-UX Version C.7.1.x

– http://www.docs.hp.com/en/IUX/download.html

Additional information• HP will no longer support Ignite-UX C.7.0 even for cold

installing HP-UX after September 2007• Refer to Ignite-UX release notes for more information

– http://www.docs.hp.com/en/IUX/infolib.html

Ignite-UX version C.7.0.x is the first version of Ignite-UX to support HP-UX 11i v3. Known problems in Ignite-UX version C.7.0.x will prevent you from using it to successfully complete some tasks. HP recommends using Ignite-UX version C.7.0.x only to cold install HP-UX and not for any other task.

For example, do not use Ignite-UX version C.7.0.x to create a recovery archive. Refer to the Ignite-UX release notes for more information about these known problems. The Ignite-UX release notes are available with the product and at: http://www.docs.hp.com/en/IUX/infolib.html

HP recommends that you immediately stop using Ignite-UX version C.7.0.x and download and install Ignite-UX Version C.7.1.x from the following URL: http://www.docs.hp.com/en/IUX/download.html

HP will no longer support Ignite-UX version C.7.0 (even for cold installing HP-UX) after September 2007.



March 200770

Mapping Between Device Special Files and Devices Cannot be Restored During RecoveryKnown Issue• Ignite-UX may not successfully remap DSF names to refer to the original

devices during recovery on a system that has more than seven disk and tape devices

Fix• Upgrade to Ignite-UX version C.7.1.x or later to fix this problem

– Download current Ignite-UX version from Download Ignite-UX page• http://docs.hp.com/en/IUX/download.html

• After installing Ignite-UX version C.7.1.x, recreate recovery archiveAdditional note• If a recovery archive created with Ignite-UX version C.7.0.x must be used

and you encounter this problem– After recovery is complete, correct the device special file names in

your configuration content so that the correct devices are used

During recovery on a system that has more than seven disk and tape devices, Ignite-UX may not successfully remap the device special file names so that they refer to the original devices.

HP recommends that you upgrade to Ignite-UX version C.7.1.x or later to fix this problem. After installing Ignite-UX version C.7.1.x, recreate your recovery archive. You may download the most current Ignite-UX version from the Download Ignite-UX page at: http://docs.hp.com/en/IUX/download.html

If a recovery archive created with Ignite-UX version C.7.0.x must be used and you encounter this problem, then after recovery is complete, correct the device special file names in your configuration content so that the correct devices are used.



March 200771

Cannot Set Language in itool for USB KeyboardsKnown Issue• Not possible to set keyboard language using itool Keyboards

interface when installing a system with a USB keyboard• Still able to use USB keyboard

– HP has only verified correct operation of US English keyboards with this issue

Fix• Simply let the cold install continue• When the system boots the first time, itemap will prompt you

for the keyboard language and you can set it at that time– Unless set explicitly via _hp_keyboard keyword in configuration

When installing a system with a USB keyboard, it is not possible to set the keyboard language via the itool Keyboards interface. When the installing system boots for the first time, the itemapcommand will be run to select the keyboard language unless it has been set explicitly via the _hp_keyboard keyword in your configuration.

Note that you will still be able to use your USB keyboard. HP has only verified the correct operation of US English keyboards with this issue.

If you have a USB keyboard and are unable to set the keyboard language, simply let the cold install continue. When the system boots the first time, itemap will prompt you for the keyboard language and you can set it at that time.



March 200772

Third Party Storage Compatibility with HP-UX 11i v3Customers should contact third-party storage vendor to determine the compatibility of non-HP third-party storage with HP-UX 11i v3• Check with the third-party storage vendor for information

about any pre-requisites and limitations with the storage on HP-UX 11i v3

HP recommends that customers contact their third-party storage vendor to determine the compatibility of third-party (non-HP) storage with HP-UX 11i v3. Check with the third-party storage vendor for information about any pre-requisites and limitations with the storage on HP-UX 11i v3.



March 200773

/dev/random or /dev/urandom Errors During UpdateKnown IssueKnown issue• When updating your system to the HP-UX 11i v3, you may

encounter the following error message in the /var/opt/swm/swm.log file– *Running "/var/adm/sw/pre_update/RNG-DKRN.100"– ERROR: The /dev/random or /dev/urandom device special

files may not be in use during update-ux. Use the fuser(1M) command to identify these processes, then terminate them.

– ERROR: The script "/var/adm/sw/pre_update/RNG-DKRN.100" returned a value of "1" (ERROR)

– *Running "/var/adm/sw/pre_update/RNG-DKRN.100" failed with 2 errors

When updating your system to the HP-UX 11i v3, you may encounter the following error message in the /var/opt/swm/swm.log file:

*Running "/var/adm/sw/pre_update/RNG-DKRN.100".ERROR: The /dev/random or /dev/urandom device special files may not be in use during update-ux. Use the fuser(1M) command to identify these processes, then terminate them.ERROR: The script "/var/adm/sw/pre_update/RNG-DKRN.100" returned a value of "1" (ERROR)*Running "/var/adm/sw/pre_update/RNG-DKRN.100" failed with 2 errors



March 200774

/dev/random or /dev/urandom Errors During UpdateFix for known issueFix• Run fuser /dev/random or fuser /dev/urandom to retrieve a list of

process IDs that are using the special device files• Use the process ID along with the ps command to determine what

processes are using the special device files– If you find mxdtf, mxdomainmgr, or mxinventory as part of these

processes• Run /opt/mx/bin/mxstop to stop all HP SIM activities before updating to

11.31– If you find smbd as part of these processes

• Run sbin/init.d/sambastop to stop all CIFS/Samba server processes before updating to 11.31

– If you find named as part of these processes• Run /sbin/init.d/namedstop and /usr/sbin/rndcstop to stop all

DNS/BIND server processes before updating to HP-UX 11i v3– If you find sshd as part of these processes

• Run /sbin/init.d/secshstop to stop all HP Secure Shell server processes before updating to HP-UX 11i v3

If you get the error message, run fuser /dev/random or fuser /dev/urandom to retrieve a list of process IDs that are using the special device files. Use the process ID along with the pscommand to determine what processes are using the special device files.

If you find mxdtf, mxdomainmgr, or mxinventory as part of these processes, then run /opt/mx/bin/mxstop to stop all HP SIM activities before updating to HP-UX 11i v3.

If you find smbd as part of these processes, then run sbin/init.d/sambastop to stop all CIFS/Samba server processes before updating to HP-UX 11i v3.

If you find named as part of these processes, then run /sbin/init.d/namedstop and /usr/sbin/rndcstop to stop all DNS/BIND server processes before updating to HP-UX 11i v3.

If you find sshd as part of these processes, then run /sbin/init.d/secshstop to stop all HP Secure Shell server processes before updating to HP-UX 11i v3.



March 200775

Online Replacement of a LAN Card in ServiceGuard Cluster FailsKnown issue• OLR of LAN card in ServiceGuard cluster fails because CRA returns

CRA_SYS_CRITICAL– Problem occurs using either pdweb or olrad

Fix• Apply patch PHNE_35894

– No reboot required for this patch• Once the patch has been applied, you will be able to perform online

replacement of hot-swappable cards without bringing down the cluster• If for some reason you need to proceed without the patch

– Remove the node from the running cluster (cmhaltnode)– Shut down the node– Replace the card

• See “Replacing LAN or Fibre Channel Cards” in chapter 8 of Managing ServiceGuard for more information

Online replacement (OLR) of a LAN card in a ServiceGuard cluster fails because the Critical Resource Analysis (CRA) performed as part of the OLR operation returns CRA_SYS_CRITICAL. You will encounter this problem whether you use the Peripheral Device Tool (pdweb) or the HP-UX olrad command, e.g. olrad –r –f or olrad –r.

Apply patch PHNE_35894. Once the patch has been applied, you will be able to perform online replacement of hot-swappable cards without bringing down the cluster. You can applythis patch without a reboot. If for some reason you need to proceed without the patch, you must remove the node from the running cluster (cmhaltnode), shut down the node, and then replace the card, as described under “Replacing LAN or Fibre Channel Cards” in chapter 8 of Managing ServiceGuard.



March 200776

Possible Panic with Concurrent Closes/Detaches from Named Streams PipesKnown issue• Very small possibility of system panic when using named

stream pipes– "panic: Fault when executing in kernel mode out of

sth_fattach()“• Scenario involves two processes closing or detaching from a

named stream pipe at the same timeFix• Limit use of named streams pipes until PHKL_35897 is

released and installed

There is a very small possibility a system panic may occur when named stream pipes are used. This known problem affects only named streams pipes and does not affect any other form of streams pipes. The scenario that exposes this problem involves two processes that are closing or detaching from a named stream pipe at the same time. There is a corner-case that can cause one process to trigger a panic. The window in which this problem can occur is very small, making the scenario very hard to experience. In the unlikely event you do experience this problem the associated panic string is: "panic: Fault when executing in kernel mode out of sth_fattach()"

HP recommends that you limit the use of named streams pipes until a patch is released to address this problem. If you use named streams pipes you should install patch PHKL_35897 once it has been released.



March 200777

Boot Disk Must Be at Least 9 GB for HP-UX 11i v3Known issue• HP-UX 11i v3 requires more space on the HP-UX boot disk

than prior HP-UX releases• Install may fail if boot disk is too small regardless of total size

of root volumeFix• Ensure boot disk is at least 9 GB when configuring systems

for installation

HP-UX 11i v3 requires more space on the HP-UX boot disk than prior HP-UX releases. Install may fail if your boot disk is too small regardless of the total size of the root volume.

When configuring systems for installation, make sure the boot disk is at least 9 GB.



March 200778

VRTSob.VEAS-FILESET Preinstall Script Cannot Read Shutdown Lock FileKnown issue• When updating to HP-UX 11i v3 release from HP-UX 11i v2

TCOE, you may encounter the message– Running "preinstall" script for fileset "VRTSob.VEAS-FILESET“

vxsvc: error cannot read shutdown lock file (/var/vx/isis/vxisis_shutdown.lock)

Fix• You can safely ignore these error messages

When updating your system to the HP-UX 11i v3 release from HP-UX 11i v2 TCOE, you may encounter the following message: Running "preinstall" script for fileset "VRTSob.VEAS-FILESET“vxsvc: error cannot read shutdown lock file (/var/vx/isis/vxisis_shutdown.lock)

You can safely ignore these error messages.



March 200779

CPU Monopolized By evacd daemon During Tape ArchivingKnown issue• evacd daemon can monopolize CPU on small vPar configured with

floating/ejectable memory– On such a system with a workload which exhausts the file cache, the

workload may run slower than expected• A backup to tape is one such workload

• This problem does not affect non-vPars systems or vPars systems configured only with base/non-ejectable memory

To fix, try any of these• Reduce tunable filecache_max from default of 50 percent to 25 percent

– If problem still occurs, reduce tunable further• Remove floating/ejectable memory from vPar using vparmodify before

starting the operation that exhausts file cache– Add memory back after operation that exhausts file cache completes

• Install patches PHKL_35899 and PHKL_35900– For information on these patches check HP IT Resource Center Web

site• http://itrc.hp.com

The evacd daemon can monopolize the CPU on a small vPar configured with floating/ejectable memory. On such a system with a workload which exhausts the file cache, the workload may run slower than expected. A backup to tape is one such workload. Note that this problem does not affect non-vPars systems or vPars systems configured only with base/non-ejectable memory.

To fix this issue, try any of these.• Reduce the tunable filecache_max from the default of 50 percent to 25 percent. If the

problem still occurs, reduce the tunable further.• Remove the floating/ejectable memory from the vPar using vparmodify before starting the

operation that exhausts file cache. The memory can be added back after the operation that exhausts file cache completes.

• Install the patches PHKL_35899 and PHKL_35900. For information on these patches, go to the HP IT Resource Center Web site: http://itrc.hp.com



March 200780

System Panic: NULL pointer dereference in evacdKnown issue• System panic may occur on vPar configured with

floating/ejectable memory and an application running that performs remap operations– Remap operations include mmap (MAP_FIXED) or using a

debugger to place a breakpoint into program text• Problem does not affect non-vPars systems or vPars systems

configured with just base/non-ejectable memoryFix• Install patch PHKL_35899• For information on this patch, go to the HP IT Resource

Center Web site– http://itrc.hp.com

In some cases, a system panic may occur on a vPar configured with floating/ejectable memory and an application running that performs remap operations. Remap operations include mmap(MAP_FIXED) or using a debugger to place a breakpoint into program text. Note that this problem does not affect non-vPars systems or vPars systems configured with just base/non-ejectable memory.

Install the patch PHKL_35899. For information on this patch, go to the HP IT Resource Center Web site: http://itrc.hp.com



March 200781

Other Known ProblemsUDO Optical Disk Drive Not Supported in HP-UX 11i v3• Waiting on further information

VxFS inode cache may be too large• Refer to Controlling Memory Utilization of VxFS4.1 on HP-UX 11i v3 in

Appendix A of the Veritas 4.1 Installation Guide HP-UX 11i v3Integrity VM 2.0 will not support HP-UX 11i v3 guests• Full support for HP-UX 11i v3 guests will be provided in HPVM 3.0• Customer early access program available

– Run HP-UX 11i v3 guests on Integrity VM 2.0 on HP-UX 11i v3– Receive information regarding restrictions and known issues/defects– Ask questions and report issues to engineering team

Refer to latest Read Before Installing Document for HP-UX 11i v3 posted at http://docs.hp.com

VxFS inode Cache May Be Too LargeFor more information, refer to Controlling Memory Utilization of VxFS4.1 on HP-UX 11i v3 in Appendix A of the Veritas 4.1 Installation Guide HP-UX 11i v3.

HP-UX 11i v3 guests will not be supported on Integrity VM 2.0, which is the currently shipping version, on the initial release of HP-UX 11i v3. Full support for HP-UX 11i v3 guests will be provided in HPVM 3.0.

Customers that are interested can participate in an early access program to run HP-UX 11i v3 guests on Integrity VM 2.0 when HP-UX 11i v3 ships. A customer who participates in this program will receive information regarding restrictions and known issues/defects, and will be able to ask questions and report issues to the engineering team.



March 200782

Post-Installation/Update Tasks

Verifying the Install/UpdatePost-Install ConfigurationHP Service PartitionPatches

In this section we will discuss, briefly, some of the common post-install considerations.



March 200783

Verifying the Install/Update Using LogsChanged log file on HP-UX 11i v3• HP-UX 11i v2 log file is /var/adm/sw/swagent.log• HP-UX 11i v3 log file is /var/opt/swm/swm.log

Carefully review contents of /var/opt/swm/swm.log• Pay particular attention to ERROR and WARNING messages• You’ll get LOTS of NOTE messages on Update• Not everything will appear in the log

– Bastille bundle selection, for example

Check the LogsAfter the update is complete, carefully check the log files that were created during the install process. As this is an extensive change to all of the installed bundles and filesets, you should expect to see a very large number of NOTE messages in the log. You may also see some WARNING messages, and perhaps (but not likely, if the update succeeded) one or more ERROR messages. Obviously, ERROR messages will need to be dealt with if the update is to succeed, so if you find any of those you’ll have to address the problems described there and re-execute the update-ux(1M) program. WARNING messages should get a careful going-over, as these indicate potentially dangerous conditions in the system. NOTE messages are common, and, given the large number of them, you’d be hard-pressed to look them all over.

Verify the State of the PackagesAt this point you can also use the features of the Software Packaging scheme to confirm that the bundles and filesets that you’ve installed are complete and intact. A couple of examples of the commands that are used to list the installed bundle/fileset/file and verify the correctness of the installed software are shown opposite.



March 200784

Verifying the HP-UX 11i v3 Cold Install or Update Using SW ToolsList all software installed on the system• Check that all bundles/products/filesets are installed

/usr/sbin/swlist –l [bundle | product | fileset]

swlist –l bundle –l product > /tmp/software_list

• Check the list for products and bundles you desire• For cold install, compare to OE and App DVDs

swlist –l bundle –l product –s /dvdrom > /tmp/dvdcontent

Verify that packages are intact/usr/sbin/swverify \*

• Check /var/adm/sw/swverify.log and /var/adm/sw/swagent.log

To verify that HP-UX 11i v3 was installed or updated successfully, use the Software Distributor commands swlist and swverify. For help with these commands, refer to the swlist (1M) and swverify (1M) manpages, and the Software Distributor Administration Guide, which is available on the Instant Information DVD or the HP Technical Documentation Web site: http://docs.hp.com/en/oshpux11iv3.html

List all Software Installed on Your SystemStep 1. List the bundles and products installed on your system:/usr/sbin/swlist -l bundle -l product > /tmp/software_listStep 2. Check the list to see that it contains the bundles and products you wish to have installed on your system.Step 3. For a cold install, you may want to compare the output of the swlist command above with the contents of the HP-UX 11i v3 Operating Environment DVD and the Applications DVD. Tosee the contents of a DVD, issue the following command: /usr/sbin/swlist -l bundle -l product -s /dvdrom > /tmp/dvdcontent

Verify the Installed SoftwareYou can verify that all software was successfully installed on your system by typing /usr/sbin/swverify \*The message “Verification succeeded” should be displayed on the console at the end of the operation. Further messages from the verification process can be found in the log files: /var/adm/sw/swverify.log and /var/adm/sw/swagent.log



March 200785

Post-Install Tasks (1 of 3)Configure OE applications• Check log file for messages regarding required changes

Migrate to Agile Mass Storage Stack, if desired• Installing causes both legacy and persistent DSFs to be

created• Installing configures system devices to use persistent DSFs

– Boot, root, swap, and dump devices• Configuration files use persistent DSFs

– /etc/fstab, /etc/lvmtab

Configure OE ApplicationsAfter updating to an HP-UX 11i v3 Operating Environment (OE), some OE products need post-installation configuration to make them functional. This need may be indicated by a message logged in /var/opt/swm/swm.log. Refer to each product’s installation instructions for details. The location of OE product documentation is listed in the HP-UX 11i v3 Release Notes, available on the Instant Information DVD and at the HP Technical Documentation Web site: http://docs.hp.com

Migrate to the Agile Mass Storage Stack (Optional)In HP-UX 11i v3 there are two types of DSFs for mass storage: legacy DSFs and persistent DSFs. Both can be used to access a given mass storage device independently and can coexist on a given system. The new mass storage stack for HP-UX 11i v3 is intended to supersede the existing mass storage stack. However, in HP-UX 11i v3 they can exist in parallel. Existing legacy DSFs will continue to work as before; they are completely backward compatible, and will not be affected by any persistent DSFs on the same server.

If you cold-install HP-UX 11i v3, both legacy and persistent DSFs are automatically created. By default, the installation process will configure system devices like the boot, root, swap, and dump devices to use persistent DSFs. This means that configuration files such as /etc/fstab, /etc/lvmtab, and others will contain references to persistent DSFs.

You may choose to migrate to the new agile mass storage stack or you can continue to use the legacy mass storage stack. If you want to use the new features of the agile mass storage stack and are not affected by existing limitations, you may want to migrate to the new mass storage stack.

For more information on the new mass storage stack and to migrate from the legacy view to the agile view refer to the white paper called, “The Next Generation Mass Storage Stack: HP-UX 11i v3” and the white paper called “HP-UX 11i v3 Persistent DSF Migration Guide” at: http://docs.hp.com/



March 200786

Post-Install Tasks (2 of 3)Retrieve information after cold installing• Create a new root home directory, e.g. /homeroot

– Modify /etc/password– Move root’s dot files to /homeroot

• Recover files– Logout and log back in as root– Manually merge your previously saved files

• Restore your local home directory, e.g. /home– Copy it back from another directory or tape where you stored it

• Restore other files

After completing the cold-install, you can retrieve the information you had previously saved onto another system.

Create a New Root Home DirectoryConsider creating a root home directory that is not /. Doing this keeps the user root dot files out of the / directory. Make sure it is on the root volume by calling it something like /homeroot. Doing this is especially important if you are using Logical Volume Manager (LVM) and /home is a separate volume. 1. Log in as root.2. Except on trusted systems, edit /etc/passwd to change the home directory from root to /homeroot and save it.3. Create the /homeroot directory: mkdir /homeroot4. Move root’s personal files (files beginning with . ) to /homeroot: mv /.[a-zA-Z]* /homeroot5. Exit and log in again as root.

Recover FilesRecover all the customized and personal files that you saved previously by merging them manually. For example, do not overwrite /etc/passwd with your old version. Instead, either paste in entries from your old files or merge the old information into the new files.Restore /homeIf you had a local home directory, you can restore. For instance, if you copied it to /backup/system1/home, entercd /backup/system1/home ; find . -depth | cpio -pdm /system1/homeIf you backed it up to tape with fbackup, enter frecover -x -i /system1/home -v

Restore Other FilesCarefully use the same techniques to restore other files and directories, such as /usr, /local, and /opt. For help in importing entire volume groups, refer to either HP-UX System Administrator’s Guide or Managing Superdome Complexes. The commands cited in this section do not write over newer files, so your new operating system and any files you update are well protected.



March 200787

Post-Install Tasks (3 of 3)Install other OE applicationsNew versions of configuration files/scripts are loaded• If any of these were modified, modifications will have to be

reapplied

Once the install or update is complete, you can install other OE applications that were not installed during the update process. For example, the Software Package Builder (SPB), which is included in the HP-UX 11i v3 media but not by default selected, could be installed. Also, if you wanted to upgrade to a higher-level OE, this would be the time to do that. In any case, the swinstall(1M) program is used to perform this task.

During the update, configuration files that have been modified are not overwritten, and there will be NOTE messages in the log indicating that the new files have been placed in a special directory in lieu of overwriting the existing file. For example, /var/opt/swm/swm.log may have, “NOTE: A copy of the previous inittab has been saved in: /var/opt/wbem/inittab.old.” In other cases, you may have a modified version of a file that the update expects to be able to overwrite. In this situation the changes will have to be reapplied.



March 200788

Post-Update TasksConfigure OE applications• Check /var/opt/swm/swm.log• Refer to each product’s installation instructions

Migrate to Agile Mass Storage Stack, if desired• Updating causes existing legacy DSFs to be retained• Updating causes persistent DSFs to be created• Configuration files use legacy DSFs

– You may choose to change theseInstall other OE applications• For example, Software Package Builder is included in the HP-UX 11i v3

media but not by default selected• If you wanted to upgrade to a higher-level OE, this would be the time to

do that• In any case, the swinstall(1M) program is used to perform this task

Configure OE ApplicationsAfter updating to an HP-UX 11i v3 Operating Environment (OE), some OE products need post-installation configuration to make them functional. This need may be indicated by a message logged in /var/opt/swm/swm.log. Refer to each product’s installation instructions for details. The location of OE product documentation is listed in the HP-UX 11i v3 Release Notes, available on the Instant Information DVD and at the HP Technical Documentation Web site: http://docs.hp.com

Migrate to the Agile Mass Storage Stack (Optional)In HP-UX 11i v3, there are two types of DSFs for mass storage: legacy DSFs and persistent DSFs. Both can be used to access a given mass storage device independently and can coexist on a given system. The new mass storage stack for HP-UX 11i v3 is intended to supersede the existing mass storage stack. However, in HP-UX 11i v3 they can exist in parallel. Existing legacy DSFswill continue to work as before; they are completely backward compatible, and will not be affected by any persistent DSFs on the same server.

When you update from HP-UX 11i v2 to 11i v3, existing legacy DSFs are retained, and persistent DSFs will be created. Configuration files are not updated, so system devices will continue to use the existing legacy DSFs. You may choose to migrate to the new agile mass storage stack or you can continue to use the legacy mass storage stack. If you want to use the new features of the agile mass storage stack and are not affected by existing limitations, you may want to migrate to the new mass storage stack.

Install other OE applicationsOnce the install or update is complete, you can install other OE applications that were not installed during the update process. For example, the Software Package Builder (SPB), which is included in the HP-UX 11i v3 media but not by default selected, could be installed. Also, if you wanted to upgrade to a higher-level OE, this would be the time to do that. In any case, the swinstall(1M) program is used to perform this task.



March 200789

Offline Diagnostics Environment on HP-UX 11i v3ODE includes offline support tools for troubleshooting a system that is running without an OSODE is available on the following media• HP 9000 PA-RISC Offline Diagnostics CD, for PA-RISC systems.• HP Itanium-Processor Family (IPF) Offline Diagnostics and Utilities CD, for IPF

systems.Obtain latest CD and update the Offline Diagnostics for improvedfunctionality• CD-ROMs are OS independent and ordered separately from each other and of

any operating system mediaOrder the latest CD-ROM for PA-RISC or IPF from one of the following Web sites• Software Depot: http://www.hp.com/go/softwaredepot• Biz Support for IPF systems: http://www.hp.com/support/Itaniumservers• Biz Support for HP 9000 systems:

http://h20000.www2.hp.com/bizsupport/TechSupport/Product.jsp?lang=en&cc=us&prodTypeId=15351&prodCatId=321931

Refer to the Offline Diagnostics section on the following Web site• http://docs.hp.com/en/diag.html

Offline Diagnostic Environment (ODE) includes a set of offline support tools that enables you to troubleshoot a system that is running without an operating system. ODE is available on the HP 9000 PA-RISC Offline Diagnostics CD, for PA-RISC systems. It is on the HP Itanium-Processor Family (IPF) Offline Diagnostics and Utilities CD, for IPF systems.

HP highly recommends that you get the latest CD and update the Offline Diagnostics for improved functionality. Note that the CD-ROMs are OS independent and ordered separately from each other and of any operating system media.

You can order for the latest CD-ROM for your PA-RISC or IPF system from one of the following Web sites.Software Depot: http://www.hp.com/go/softwaredepotBiz Support for IPF systems: http://www.hp.com/support/ItaniumserversBiz Support for HP 9000 systems: http://h20000.www2.hp.com/bizsupport/TechSupport/Product.jsp?lang=en&cc=us&prodTypeId=15351&prodCatId=321931

For more information on ODE, refer to the Offline Diagnostics section on the web at http://docs.hp.com/en/diag.html



March 200790

PatchesPatch process is unchanged• Format, tools, all are same as HP-UX 11i v2• See the Patch Management User Guide for HP-UX 11.x Systems available

on http://docs.hp.comCustom Patch Manager (CPM)http://itrc.hp.com/wps/bin/doc.pl/sid=00f2dea61cb1fc364e

Individual patches can be downloaded from ITRChttp://itrc.hp.com

Patch Assessment Tool can be found at the ITRC (http://itrc.hp.com)• Can be used to find additionally needed patches, such as patches for

non-OE applications and new security patchesSecurity Patch Check B.02.05• Bundled with HP-UX 11i v3• Set up with Bastille or separately

Thankfully, not everything about HP-UX 11i v3 is new. In fact, the patch process for this release is virtually unchanged. Individual patches and the Custom Patch Manager (CPM) are both still on itrc.hp.com.

On HP-UX 11i v3, the Security Patch Check bundle can perform periodic scans of the patch repositories and your system, and suggest additional patches that can be installed to improve security. It can be installed and setup as a standalone package, or can be installed with Bastille, which will set it up to run periodically.



March 200791

HP-UX 11i v3 Patch Bundles & Software PackInitial release of HP-UX11i v3 does not include• Standard Quality Pack (QPK)• Hardware Enablement (HWE) patch bundles• Software Pack that delivers optional new core enhancements

Delivery of patch bundles and Software Pack is planned for the first update release of HP-UX 11i v3

The initial release of HP-UX11i v3 will not include the standard Quality Pack (QPK) and Hardware Enablement (HWE) patch bundles or the Software Pack that delivers optional new core enhancements. The delivery of these patch bundles and the Software Pack is planned for the first update release of HP-UX 11i v3.



March 200792

Software Deployment Module

New Software Manager (SWM)Ignite-UX ChangesUpdate-UX ChangesSoftware Distributor (SD) ChangesSoftware Package Builder (SPB) Changes

In this module, we will examine new and changed features in the various software deployment tools.



March 200793

Software Deployment on HP-UX 11i v3Update-UX command line continues to be primary interface for OS update• Supports a preview option (-p)

– Previews update task by running session through the analysis phase only• Interactive option (-i) brings up a TUI that steps through the entire update

No changes needed to Ignite-UX command lines to support modular OEsAll software deployment applications use SD depots as distribution source• Includes directory and serial depots

– Directory depots can be either remote or local• New attributes have been added to SD objects

– SD is enhanced to recognize some of them– Others only used during specific operations such as OE update or cold install

New log file contains results of output during OE update and cold install• swm_log

General “SD format” of messages and grouping into types remains • Types are ERROR, WARNING, or NOTE • Individual messages may be different

The update-ux command line continues to be the primary interface for an OS update. This command line supports a preview option (-p). This option previews an update task by running the session through the analysis phase only. The behavior of the interactive option (-i) will now bring up a TUI that steps through the entire update. There are no changes needed to Ignite-UX command lines to support modular OEs.

All the software deployment applications use SD depots as the distribution source. This includes directory and serial depots. Directory depots can be either remote or local. New attributes have been added to SD objects. SD is enhanced to recognize some of them, but others are only used during specific operations such as OE update or cold install.

There is a new log file (swm_log) that contains results of output during OE update and cold install. The general “SD format” of messages and grouping into ERROR/WARNING/NOTE type remains the same. Individual messages may be different.



March 200794

Software Manager (swm) New on HP-UX 11i v3Provides a CLI and TUI to manage software, including bundles, products, sub-products and filesets• Similar to SD commands except swm is a single command with major

modesExtends functionality provided by SD• And has the ability to update from one operating environment to another

Has four major modes of operation• ‘swm install’ installs software • ‘swm list’ lists software• ‘swm job’ provides job control interface to existing jobs• ‘swm oeupdate’ updates an operating environment

The list and install major modes are not supported in this release• Options, modes and behavior will change in future versions• Commands are provided for evaluation purposes only

Man pages• swm(1M), swm-install(1M), swm-list(1M)• swm-job(1M), swm-oeupdate(1M)

The Software Manager (swm) command provides a command-line interface(CLI) and Terminal User Interface(TUI) to manage software (bundles, products, subproducts and filesets). Users familiar with SD (swinstall, swremove, etc) will notice that swm is a single command with major modes, as opposed to multiple commands.

swm extends the functionality provided by SD, most notably it has the ability to update from one operating environment to another. sd(4) describes the SD software object classes, their attributes, and the file formats used to store their definitions.

The swm command has four major modes of operation. The command ‘swm install’ installs software and is similar to swinstall. ‘swm list’ lists software like swlist does. ‘swm job’ provides job control interface to existing jobs, which is similar to swjob. And, ‘swm oeupdate’ updates an operating environment, much like update-ux.

Note that the list and install major modes are not supported in this release. Options, modes and behavior will change in future versions. These commands are provided for evaluation purposes only.

Refer to the swm(1M), swm-install(1M), swm-list(1M), swm-job(1M), and swm-oeupdate(1M) man pages.



March 200795

SWM TUI

This slide shows the SWM TUI. Simply use your arrow keys to highlight the action that you want to perform: install software, manage jobs, list software, or update. Then press Enter, or Return, to begin the action.



March 200796

Listing Software with SWM TUI Simplified Management

This slide illustrates using the SWM TUI to view the currently installed software. This is so much more user friendly than running swlist!



March 200797

Ignite-UX OverviewIgnite-UX helps you install supported HP-UX releases• On multiple PA-RISC and/or Itanium-based clients on your network

Uses of Ignite-UX toolset• Create custom installation configurations, or golden images, for use in

multiple installations on clients• Recover HP-UX clients remotely• Create custom recovery media including tape, CD, and DVD• Manage and monitor multiple client installation sessions

Does not support configurations with more than one version of VxVMin the same imageDocumentation for many new changes at this release• Ignite-UX Web site has been updated for this release

– http://www.docs.hp.com/en/IUX/• Several documents updated to reflect changes

– http://www.docs.hp.com/en/IUX/infolib.html

The Ignite-UX product is an HP-UX administration toolset that helps you install supported HP-UX releases on multiple PA-RISC and/or Itanium-based clients on your network. Ignite-UX can be used to create custom installation configurations, or golden images, for use in multiple installations on clients. It can recover HP-UX clients remotely. It can be used to create custom recovery media including tape, CD, and DVD. And, it can manage and monitor multiple client installation sessions.

Note that Ignite-UX does not support configurations that include more than one version of VxVMin the same image. Make sure that your installation and recovery images contain one only one version of the VxVM product.

There are many changes to the Ignite-UX product at HP-UX 11i v3. We’ll cover these in the next slides.

The Ignite-UX product Web site containing information and documentation has been updated for this release. It can be found at http://www.docs.hp.com/en/IUX/

The following documents have been updated to reflect all changes to the product for this release. They can be found at http://www.docs.hp.com/en/IUX/infolib.htmlIgnite-UX Administration GuideIgnite-UX Custom Configuration FilesIgnite-UX ReferenceIgnite-UX Release Notes



March 200798

Ignite-UX v C.7.0 on HP-UX 11i v3 (1 of 3)Multipath-Aware Ignite• Is aware of all hardware paths leading to a device

– Will do some validation that different paths are not inappropriately reused• Displays lunpath hardware paths for HP-UX 11i v3 installations

– For 11i v2 and prior versions of HP-UX, Ignite-UX displays legacy hardware paths

• Has a “More Info” screen that shows all paths to devices and device WWIDs– Helps transition from legacy hardware paths to lunpath hardware paths– Assists with identifying devices in larger multiple path configurations

• Supports persistent DSFs of system devices through system reboot and normally through Ignite-UX recovery– Will not typically persist from installation to installation

• Handles legacy DSFs as in prior versions of Ignite-UXOperating Environments restructuring affects Ignite-UX• Software products listed on the Software tab of the client installation configuration

interface are grouped as “Required,” “Recommended,” and “Optional”– These groupings appear as selectable categories

There are several changes to Ignite-UX version C.7.0 on HP-UX 11i v3. We will cover these in this and the following slides. Beginning with HP-UX 11i v3, Ignite has some multipath-awareness for all revisions of HP-UX. This means that Ignite is aware of all hardware paths leading to a device and will do some validation that different paths are not inappropriately reused.

HP-UX 11i v3 uses a new approach for addressing I/O. This means that Ignite-UX displays lunpath hardware paths for HP-UX 11i v3 installations. For 11i v2 and prior versions of HP-UX, Ignite-UX displays legacy hardware paths.

To help with the transition from legacy hardware paths to lunpath hardware paths, and assist with identifying devices in larger multiple path configurations, Ignite-UX now has a “More Info”screen that shows all paths to devices, as well as device world-wide identifiers (WWIDs).

HP-UX 11i v3 Persistent DSFs of system devices will persist through system reboot and will normally persist through an Ignite-UX recovery, but will not typically persist from installation toinstallation. And, legacy DSFs are handled in HP-UX 11i v3 as in prior versions of Ignite-UX.

Operating Environments are restructured in HP-UX 11i v3. Software products listed on the Software tab of the client installation configuration interface are now grouped as “Required,”“Recommended,” and “Optional,” and these groupings appear as selectable categories.



March 200799

Ignite-UX v C.7.0 on HP-UX 11i v3 (2 of 3)Ignite-UX integrates with SWManager rather than SD-UX for software installation tasksHyper thread state is preserved with Ignite-UX recovery• Systems that support hyper threading have it enabled by

defaultSystem boot path is automatically managed for multiple path configurations as paths change• I/O subsystem chooses the best boot path and changes boot

paths as neededI/O inventory information collection for installation and recovery is more complex• And more efficient

New and changed messages are displayed and logged

Ignite-UX integrates with SWManager rather than SD-UX for software installation tasks on HP-UX 11i v3.

HP-UX 11i v3 systems that support hyper threading will have it enabled by default. The hyper thread state is preserved with recovery.

The system boot path is automatically managed in HP-UX 11i v3 for multiple path configurations as paths change. The I/O subsystem will choose the best boot path and change boot paths as needed.

I/O inventory information collection for installation and recovery is more complex, but more efficient. You may or may not see performance improvements.

The details of how Ignite-UX interacts with the kernel have changed, resulting in new and changed messages being displayed and logged.



March 2007100

Ignite-UX v C.7.0 on HP-UX 11i v3 (3 of 3)User selectable archive format for recovery archives and golden archives • pax has been added as a format choice

– One known issue with pax format when Ignite-UX server is not running HP-UX 11i v3• Check the Ignite-UX release notes for more information.

Ignite-UX checks minimum memory requirements• Will not permit installation or recovery to proceed if the system is below

the memory limit• Warning messages may also be issued for minimum or near minimum

memory sizeIgnite-UX bundle structure has been changed• Principle bundle tag of Ignite-UX is now IGNITE instead of B5725AA• OS-specific bundle tags like Ignite-UX-11-23 remain as is

– There is a new tag for Ignite-UX-11-31

The archive format for recovery archives and golden archives is now user selectable, and paxhas been added as a format choice. There is one known issue with the pax format when the Ignite-UX server is not running HP-UX 11i v3. Check the Ignite-UX release notes for more information.

Ignite-UX will check minimum memory requirements and will not permit installation or recovery to proceed if the system is below the memory limit. Warning messages may also be issued for minimum or near minimum memory size.

The Ignite-UX bundle structure has been changed. The principle bundle tag of Ignite-UX is now IGNITE instead of the previous B5725AA bundle tag. The OS-specific bundle tags like Ignite-UX-11-23 remain as is, and there is a new tag for Ignite-UX-11-31.



March 2007101

Update-UX on HP-UX 11i v3The update-ux command updates the HP-UX operating system to a newer version

• Includes new UPDATE-UX terminal user interface (TUI) • SW-GETTOOLS product contains a set of tools used by update-ux

– Automatically installed by update-ux and is removed on the next reboot– Updated with more up-to-date versions

Software Manager is a new application used by Ignite-UX and Update-UX to perform software installation

• Implements improvements for software selection• Provides support for OEs• Provides update support for preview and a TUI• Supports preview (-p)• Supports interactive terminal user interface (-i)• Has better support for multiple media

– More accurate disk space analysis and dependency selection across media• Has improved logging capabilities

Documentation• HP-UX 11i v3 Installation and Update Guide at http://docs.hp.com/en/oshpux11iv3.html• The update-ux(1M), swm-oeupdate(1M), and swm(1M) man pages

The update-ux command updates the HP-UX operating system to a newer version. The SW-GETTOOLS product contains a set of tools used by update-ux. It is automatically installed by update-ux and is removed on the next reboot. The set of commands in SW-GETTOOLS has been updated with more up-to-date versions.

Software Manager is a new application used by Ignite-UX and Update-UX to perform software installation. Software Manager implements improvements for software selection, provides support for OEs, and provides update support for preview and a terminal user interface (TUI). In addition to the update-ux command line, you can use the new UPDATE-UX terminal user interface (TUI) to update your system. The update-ux command uses Software Manager to perform the update.

There are several new features, including a preview capability using –p option. Using the –i option provides the interactive terminal user interface. There is better support for multiple media, including more accurate disk space analysis and dependency selection across media. Finally, there are improved logging capabilities.

For further information, refer to the latest HP-UX 11i v3 Installation and Update Guide, available at http://docs.hp.com/en/oshpux11iv3.html. Also refer to the update-ux(1M), swm-oeupdate(1M), and swm(1M) man pages.



March 2007102

Software Distributor (SD) on HP-UX 11i v3SD is the standard tool suite for working with HP-UX software packages• Used for packaging, installing, copying, listing, removing

and verifying softwareNew SD capabilities on HP-UX 11i v3 release• Support for HP-UX 11i v3-unique features

– Includes large pid, long usernames and group names• Improved support for high level software deployment tools

– Such as Software Manager and update-ux

Refer to the SD customer Web site at• http://docs.hp.com/en/SD/

Software Distributor (SD), version 11.31, is the standard tool suite for working with HP-UX software packages. SD is a group of software for packaging, installing, copying, listing, removing and verifying software.

SD is built from a common set of sources for all OS releases. Hence, HP-UX 11i v3-unique functionality is typically either OS specific or recently added. New SD capabilities on HP-UX 11i v3 release include support for HP-UX 11i v3-unique features including large pid, long usernames and group names. SD also has improved support for high level software deployment tools such as Software Manager, update-ux, and future tools.

For further information, see the SD customer Web site at http://docs.hp.com/en/SD/.



March 2007103

Software Package Builder (SPB)SPB allows the user to• Create a product specification file (PSF) to organize files into

products, filesets, and optionally, into bundles and sub-products

• Set attribute values to define the software package characteristics – Revision, architecture, file permissions, dependencies

• Control scripts customize how software is handled when installing or removing it

• Validate PSF against packaging policies– Ensures successful depot creation with swpackage and

following installation• Edit and validate PSF automatically as part of a build process

using SPB’s CLI

Software Package Builder (SPB) provides a visual method to create and edit software packages using the HP-UX Software Distributor (SD) package format. Once software is packaged, it can easily be transferred to a distribution medium, mass produced, and installed by administrators.

The SPB graphical user interface (GUI) provides a window into the software package structure, showing attributes that can be set for each package element. SPB dynamically loads packaging policies and validates software package attributes against these policies. The SPB command line interface (CLI) can also perform validation of software package attributes against policies and supports automated edits to the software package specification.

Whether you are new to packaging or experienced, SPB can help you. Features of SPB include the ability to create a product specification file (PSF) to organize files into products, filesets, and optionally, into bundles and sub-products. You can set attribute values to define the software package characteristics such as revision, architecture, file permissions, and dependencies. Control scripts can further customize how the software is handled when installing or removing it on the destination system. SPB can validate the PSF against packaging policies to ensure successful depot creation with the swpackage command and subsequent software installation. You can use SPB to edit and validate the PSF automatically as part of the nightly build process using SPB’s CLI.

With SPB, developers and administrators can easily package software in SD format, making management of software with standard SD tools, such as swinstall, swlist, swremove, possible. For example, SPB makes it easy to put an SD wrapper around open source software. As a result, software inventory management and system administration get easier.



March 2007104

Software Package Builder (SPB) on HP-UX 11i v3

New policy files for SPB on HP-UX 11i v3• New HP-internal policy file, 1131Policies.xml

– Supports packaging for the HP-UX 11i v3 release• Includes expansion of acceptable category tags and changes to the

architecture and os_release attribute rules

• New external packaging policy file, 113XPolicies_SD.xml– Supports packaging for the HP-UX 11i v3 release

• Includes changes to architecture and os_release attribute rules

• New policy files selected automatically

Procedure to correct performance issue before using SPB

On HP-UX 11i v3, there are two new policy files. A new HP-internal policy file, 1131Policies.xml, was added to support packaging for the HP-UX 11i v3 release. These policies include the expansion of the acceptable category tags, and changes to the architecture and os_release attribute rules. The external packaging policy file, 113XPolicies_SD.xml, was added to support packaging for the HP-UX 11i v3 release. This includes changes to the architecture andos_release attribute rules. If you are running HP-UX 11i v3, the new policy files will be selected automatically, transparent to the user. However, the 113XPolicies_SD.xml file may be explicitly selected by the user from the SPB command line.

There is an important performance note. Java Swing behavior may cause navigational inconsistencies when running SPB through an X emulator. If your mouse click behavior setting is too slow, it can prevent SPB from buffering all mouse clicks. This could potentially lead to data loss. The SPB product release notes contain a detailed procedure for correcting this performance issue. It is highly recommended that you complete the procedure prior to using SPB. For this and other troubleshooting topics, refer to the SPB Help system.

For further information on Software Package Builder, spb(1M) man page, the SPB Web site at http://www.docs.hp.com/en/SPB/, and the Software Package Builder 2.0 User’s Guide found at http://www.docs.hp.com



March 2007105

Boot and Update Module

Dynamic Root DiskBoot-time Override of Kernel TunablesDLKM of I/O DriversFaster Boot



March 2007106

Dynamic Root Disk (DRD) on HP-UX 11i v3DRD Software deployment tool improves the OE update experience• Improved software selection

– More modular OEs• Supports new classifications and categories of software

DRD safe software packaging changes enable HP-UX software to be patched and updated while the system is doing productive work during normal business hours Software deployment tools enhanced in support of the following improvements to the HP-UX Operating Environments• Addition of an interactive terminal user interface (TUI) for OE updates• Display of new categories and OE information in the Ignite-UX TUI• Classification of software into required, recommended and optional groups

– Use of these classifications to improve both initial software installation (in Ignite-UX) and software updates

– In addition, the software categories will also be improved.Same package and depot formats with minor changes to represent OE information and new categories

The Dynamic Root Disk Software deployment tool improves the customer experience of using HP-UX OEs by improving the OE update experience, improving software selection and supporting new classifications and categories of software. Tools support enhancements that provide a more modular Operating Environment (OE). Software packaging changes include support for DRD and OE enhancements.

DRD safe software packaging changes enable HP-UX software to be modified, allowing patches and updates, while the system is doing productive work during normal business hours.

Software deployment tools are being enhanced in support of the following improvements to the HP-UX Operating Environments (OEs). There is an addition of an interactive terminal user interface (TUI) for OE updates. The Ignite-UX TUI displays new categories and OE information. Software is classified into required, recommended and optional groups. Use of these classifications improves both initial software installation and software updates. In addition, the software categories are also improved. HP-UX 11i v3 continues to use the same package and depot formats, with minor changes to represent OE information and new categories.



March 2007107

Dynamic Root Disk (DRD) on HP-UX 11i v3Provides the ability to create and manipulate an inactive systemimage• Inactive system environment is a bootable system environment that is not

currently in use by the running system– Used for a variety of purposes

• Recovering system in event of failure• Preparing new system environment while preserving existing system

environmentSoftware packaging changes made to support DRD• Generate backward compatible packages that work with and without

DRDNew software packaging attributes and environment variables are added for DRD safe packaging• An attribute to indicate that software package is safe for install to an

inactive DRD environment• An environment variable to indicate that the package is being installed or

managed in a DRD modification environment

In the first HP-UX 11i v3 release, DRD provides the ability to create and manipulate an inactive system image. An inactive system environment is a bootable system environment that is not currently in use by the running system. This inactive system environment can be used for a variety of purposes, such as recovering the system in the event of a failure or preparing a new system environment while preserving the existing system environment.

Software packaging changes made to support DRD all generate backward compatible packages that work with and without DRD.

New software packaging attributes and environment variables are added for DRD safe packaging. There is an attribute to indicate that the software package is safe for install to an inactive DRD environment. And, there is an environment variable to indicate that the package is being installed or managed in a DRD modification environment.



March 2007108

Boot-time Override of Kernel TunablesNew on HP-UX 11i v3Ability to override HP-UX tunable values at the HP-UX boot prompt• Persistent across reboots• Entirely new feature implemented in HP-UX 11i v3

Scenarios for use• Enable disaster recovery mechanisms

– E.g. specify an alternate root device– E.g. correct if unbootable due to bad settings

• Enable test and debug mechanisms– E.g. set variables to access certain code paths for testing

• Enable optional behavior in boot process– E.g. control whether I/O scans are performed serially or in parallel

See the hpux(1M) and hpux_efi(1M) manpages

Secured Availability

The HP-UX 11i v3 release provides a new feature in which all kernel tunable values can be reset from the boot prompt. More than one tunable can be changed at a time using this method. This overrides the values in the configuration being booted. This is an entirely new feature implemented in HP-UX 11i v3.

Such overrides of tunable values are valid only for the current boot. Any changes to the tunable values made with this mechanism will be kept persistent.

Boot-time override of kernel tunables allows system administrators and developers to specify tunable values at the beginning of the boot process. It is possible to make some boot-time tunable override specifications to be documented to customers, and others not. It is possible to make boot-time tunable override specifications known to code that is not present at boot time, for example, to DLKMs. This boot-time override mechanism replaces existing usage of other ad-hoc mechanisms, for example, modifying adb variables.

This feature can be used to enable disaster recovery mechanisms. For example, it could be used to specify an alternate root device. Or, if a system seems to be in an unbootable condition due to bad tunable settings, they can be corrected on the boot prompt. This feature could be used to enable test and debug mechanisms. An example of this would be to set variables to access certain code paths for testing. Finally, it can be used to enable optional behavior in the boot process. An example of this would be to control whether I/O scans are performed serially or in parallel.

For more details, see hpux (1M) for PA-RISC systems and hpux.efi (1M) for Itanium systems.



March 2007109

DLKM of I/O Drivers on HP-UX 11i v3DLKM of I/O Drivers is new on HP-UX 11i v3• Ability to load, unload, or replace a device driver without a reboot• Allows customer to install a new driver or new version of a driver without reboot

– Saves usual downtime associated with a system rebootI/O drivers that are now DLKMs• iether• btlan• gelan• igelan• Infiniband• SCSI c8xx• SCSI mpt• Tachlite Fibre-Channel• Qlogic Fibre-Channel• iSCSI• ixgbe - 10GigE• CISS• SAS

DLKM of I/O Drivers is the ability to load, unload, or replace a device driver without a reboot. I/O drivers as DLKMs means that customers can install a new driver, or a new version of a driver, without the downtime associated with a system reboot.

Several I/O drivers are now DLKMs:• iether• btlan• gelan• igelan• Infiniband• SCSI c8xx• SCSI mpt• Tachlite Fibre-Channel• Qlogic Fibre-Channel• iSCSI• ixgbe - 10GigE• CISS• SAS

Over time, more DLKM drivers will be available.



March 2007110

SMH Showing DLKM I/O Drivers

This slide shows how you can verify the DLKM status of an I/O driver. If the Dynamic column has a “yes” entry, then that module is a DLKM.



March 2007111

Faster Boot on HP-UX 11i v3Faster (re)boot of HP-UX 11i v3 goal• Improve reboot time to less than one hour for a large sweet

spot configuration– Do not allow any reboot time degradation on similar system

configurations compared to HP-UX 11i v2 0409

Specific sample goals for HP-UX 11i v3 • Time for reboot of one 16-way Superdome single system

configuration with 128 GBytes improves by 15%• Achieve a reboot of 8000 LUNs in both SLVM and CVM

environment of 16-way systems under load without performing a dump in less than one hour

HP-UX 11i v3 had a goal to have a faster boot, or reboot, time. The goal was to improve reboot time to less than one hour for a large sweet spot configuration. Obviously a must requirement for this improvement is not to allow any reboot time degradation on similar system configurations compared to HP-UX 11i v2 0409.

Specific sample goals for HP-UX 11i v3 included that the time for a reboot of one 16-way Superdome single system configuration with 128 GBytes improves by 15%

Another specific goal was to achieve a reboot of 8000 LUNs, which is 1/8 of the maximum number of LUNS, in both SLVM and CVM environment of 16-way systems under load without performing a dump in less than 60 minutes, or one hour.



March 2007112

Kernel Configuration Module

Reconfiguring the Kernel ReviewKernel Configuration Components ReviewKernel Modules ReviewKernel Registry ReviewKernel Configuration Commands Changes

Configuring the HP-UX kernel is a common system administration task. The architecture of the HP-UX kernel has been undergoing changes over several releases. The kernel continues to become more modular and more capable of being tuned while running. This section includes a brief review of the kernel configuration architecture on HP-UX 11i v3. While users of HP-UX 11i v2 should be familiar with the “kc” commands, the kernel configuration architectural overview review should be useful. And, those migrating from older HP 9000 systems with HP-UX 11i v1 will need this overview.



March 2007113

SMH

Reconfiguring the Kernel

Running Kernel

KernelExecutable

Boot

Kernel Configuration

Alternate Kernel Config

Option 1: Configure and Reboot

Option 2: Configure Dynamically

Option 3: Configure Alternate

kconfigkctune

kcmodule

System restart not always necessary!

GUI CLI

SMH kernel config.

func. area

TUI

In HP-UX 11i v3, the administrator has many choices for configuring the kernel and maintaining saved configurations.Option 1: Configure and Reboot

• This is the traditional method of configuring the kernel. You can use commands to change the kernel configuration and then reboot. The kernel configuration (KC) commands infrastructure logs all configuration changes to the KC log file (/var/adm/kc.log). Also, you can use the commands to change the kernel configuration dynamically.

Option 2: Configure Dynamically• Using the KC commands, you can change tunables, load and unload modules, and load

alternate configurations dynamically.Option 3: Configure Alternate

• The KC commands enable you to manage a number of alternate kernel configurations. Not only can you save the current configuration under a new name, but you can change tunables and modules in an alternate configuration as well.

All tunable information is acquired at boot time from the Kernel Registry Service. This ensures that kernel rebuilds are never needed for tuning, although re-linking may be required. Reboots are still required to modify static tunable values, but data shows that few customers ever change many of these static tunables.

Tunables are now defined for each module in modmeta files by module developers. Modmetafiles are compiled into object files, which are then linked into the associated module which owns the tunables. This packaging of metadata with the module ensures that the module and metadata are never out of sync. (Modmeta files are part of the development environment and do not exist on customer systems.)



The KRS handles all runtime configuration. A kernel configuration is stored in several configuration files. The kernel itself is not recompiled. The kernel configuration mechanism in HP-UX 11i v2 and HP-UX 11i v3 never compiles any code on customer systems. It treats the entire kernel configuration as a unit. It exposes a minimum of implementation detail. It is used identically in customer and development environments. It ensures the greatest possible flexibility for future enhancement.

Administrators treat an entire kernel configuration as a single unit, which can be copied, backed up, selected by name, etc. This is the reason for the existence of the “saved kernel configuration”concept. This is also the reason that the bulk of the KC code is in a library shared by all of the KC commands: the command that works on whole kernel configurations (kconfig) must be able to do most of the tasks that the other commands can do.

This KC design provides administrators with all of the configuration flexibility that they can reasonably use, while ensuring that the bare minimum of implementation detail is exposed to them. This is the reason for module states, which hide internal details such as module registration and module preparation scripts.



March 2007115

SMH Kernel Configuration TUI

This screenshot shows the SMH kernel configuration TUI. From here, the user may view and modify kernel tunables, modules, drivers, and alarms. He or she may also view logged changes to modules and tunables. Finally, there is on-line information about the kernel tunables.



March 2007116

Commands

Kernel Configuration Components

Kernel Configurationkconfig

Kernel Modules kcmodule

Tunable Values kctune

Swap Device, Dump Device, & Driver Device Specifications

Name, Title

SMH

Tunables

Modules

Monitoring

Alarms

Reboot

kcalarm

kcusage

Logically, a kernel configuration is a collection of all of the administrator choices and settings needed to determine the behavior and capabilities of the HP-UX kernel. In this implementation, the collection includes:

• A set of kernel modules, each with a desired state• A set of kernel tunable parameter value assignments• A primary swap device specification• A set of dump device specifications• A set of bindings of devices to device drivers• A name and optional description of the kernel configuration

Physically, a kernel configuration is a directory under /stand that contains the files needed to realize the specified behavior. The directory includes:

• An HP-UX kernel executable• A set of HP-UX kernel module files• A kernel registry database, containing all of the above collection• A system file, describing the above settings in human-readable form• Various other implementation-specific files

In addition to the configuration of the running kernel, HP-UX systems can have any number of saved kernel configurations, limited only by the disk space available in /stand.



Kernel Configuration CommandsThree primary commands are used to manage kernel configurations: kconfig, kcmodule, and kctune.kconfig is used to manage whole kernel configurations. It allows configurations to be saved, loaded, copied, renamed, deleted, exported, and imported. It can also list existing saved configurations and give details about them. For more information, see the kconfig(1M) man page.

kcmodule is used to manage kernel modules. Kernel modules can be device drivers, kernel subsystems, or other bodies of kernel code. Each module can be unused, statically bound into the main kernel executable, or dynamically loaded. kcmodule will display or change the state of any module in the currently running configuration or any saved configuration. For more information, see the kcmodule(1M) man page.

kctune is used to manage kernel tunable parameters. These are variables that control the behavior of the kernel. They have many uses including controlling the allocation of system resources and tuning aspects of kernel performance. kctune will display or change the value of any tunable parameter in the currently running configuration or any saved configuration. For more information, see the kctune(1M) man page.

In addition to these three primary commands, there are two other kernel configuration commands. The kcpath command prints information about the location of the currently running kernel. It is intended for use by scripts and applications that need this information. (See the kcpath(1M) man page for details.) The kclog command searches the kernel configuration log file; for details see the kclog(1M) man page.

kcalarm and kcusage are shown in a separate block in this diagram because the are not used for configuring the kernel, but are used to monitor the usage of tunables. kcusage sets up the monitoring of certain tunables and kcalarm enables you to set alarms that expire when selected tunables exceed a specified percentage of usage.



March 2007118

SMH Tunables Tab

This slide shows the SMH GUI tunables tab. It shows that the new tunable, filecache_max, is being tracked. It is currently at 10% of its default value.



March 2007119

Using SMH to View Tunable Details

This view of the details of a kernel tunable, in this case, filecache_max, should look familiar to users of HP-UX 11i v2 kcweb GUI. Basically, SMH GUI and TUI replace kcweb and pdweb GUIs and TUIs. Running kcweb directly will launch either the SMH GUI or SMH TUI.



March 2007120

Kernel ModulesA kernel module is a device driver, kernel subsystem, or some other body of kernel code

KRS

DLKM registration reads module metadata andstores it in the KRS

Kernel Module

Module Metadata

Module Code

SymbolsDependencies

Driver Info Tunables

Boot Dispatch Directives

Initialization Routines

Tunable Handlers

Module Functions

The HP-UX kernel is built from a number of modules, each of which is a device driver, kernel subsystem, or some other body of kernel code. The DLKM Infrastructure provides a framework to load kernel modules into a running kernel. Dynamically loadable modules can be included in the kernel or excluded from the kernel dynamically, without having to re-link the entire kernel or reboot the system.

Module Metadata is compiled into each module and describes the module's characteristics and capabilities. (This developer-level information may be useful in understanding more about how kernel modules are structured.)

• Module metadata can contain the following types of information:– Module name (required)– Module version (required)– Module type (required)– Description (required)– Supported states (required)– Supported load times (required for modules that support the loaded state)– Unloadable flag– Dependencies on other modules or interfaces they export– Interfaces or symbols exported by the module– Tunable parameters– Initialization functions– Driver details (required for device driver modules)– File system details (optional; for file system modules only)



Using kernel modulesThere are two basic ways to use a kernel module. Traditionally, kernel modules have been statically bound into the main kernel executable, /stand/vmunix. This method is simple, but it has some significant disadvantages. In particular, it requires system administrators to relink the kernel executable and then reboot the system in order to add, remove, or patch a kernel module. Similarly, it requires module developers to rebuild and reboot after each change to the kernel module.

Kernel modules can also be made to support dynamic loading. A dynamically loadable kernel module (DLKM) can be loaded into the running kernel without the need for a rebuild or a reboot. Most dynamically loadable modules are also unloadable, so they can also be removed from the running kernel without needing a rebuild or reboot. System administrators prefer kernel modules that support dynamic loading because they can reconfigure their kernel more quickly, and without the need for costly downtime. Module developers prefer dynamically loadable modules because they can test changes without having to wait for systems to reboot.



March 2007122

The Kernel Registry• The Kernel Registry stores

essential kernel information– System-level data– Configuration data– Temporary data

• Periodically flushed to files• Creation of last known good

configuration at system boot• Keeps track of dynamic tunables• Users do not interact directly with

the KRS

Kernel Registry

Persistent Data

KRSDatabase

Temporary Data

Periodic Flushby the krsd

Reload onBoot

System Config

Changes to dynamic tunables are kept persistent, even across reboots. The kernel does this by keeping all kernel configuration data in the Kernel Registry. At boot time, the kernel reads configuration information from the Registry and uses it. The Registry is kept up to date whenever kernel configuration changes are made.

The KRS daemon (krsd) saves persistent data to files on disk. These files are read when the system is booted. When running in daemon mode, krsd sleeps, waking periodically to check if any persistent data have changed since the last save. If persistent data have changed, the new state of the data is saved to disk. Otherwise, krsd sleeps for another period of time and then repeats the process.

When running one time (not as a daemon), krsd unconditionally saves persistent data to disk and then exits. It is also run this way just prior to a system reboot.

Normally, krsd is executed in daemon mode by init(1M). The /etc/inittab entry for krsd will cause krsd to be respawned automatically if it is terminated. krsd uses the syslog message logging facility to log all krsd activity.

After a file has been loaded successfully by KRS during boot, it is copied to /stand/krs/system.krs.lkg, or “last known good”. This is the first place the loader looks if the default file to be loaded is missing or corrupt.

Loading KRS Data• Data loaded depends on which kernel configuration was booted.

– system data: loaded for all kernel configurations on the system– kernel data: data that is specific to a kernel configuration



March 2007123

Overview of Kernel Configuration Command Changes on HP-UX 11i v3• Revision of error, warning, and note messages for clarity• New options for kconfig, kcmodule, and kctune for control of

automatic configuration backups• Two new options for kctune command• kctune now allows some tunable values to be specified in

terms of the percentage of some system resource• Changes have been made to the kernel configuration

commands to improve resiliency and performance• Tunable parameter values may now be overridden on the

boot loader command line• Several other changes, including some obsolescences

On HP-UX 11i v3, there are several significant changes to the Kernel Configuration Commands. The error, warning, and note messages are now clearer and more understandable. There are new options for kconfig, kcmodule, and kctune for control of automatic configuration backups. There are two new options for kctune command. Also, kctune now allows some tunable values to be specified in terms of the percentage of a system resource. Changes have been made to the kernel configuration commands to improve resiliency and performance. Tunable parameter values may now be overridden on the boot loader command line. Finally, there are several other changes, including some obsolescences.



March 2007124

Kernel Configuration Commands on HP-UX 11i v3Kernel configuration (kc) commands on HP-UX 11i v3• kconfig manages whole kernel configurations

– mk_kernel is a script wrapper around kconfig• kcmodule manages kernel modules• kctune manages kernel tunable parameters• kclog, kcpath• Same commands as on HP-UX 11i v2• Replaces config and the “km” commands on HP-UX 11i v1

Documentation• Managing Kernel Configurations in HP-UX 11i

– http://docs.hp.com

HP-UX provides a set of commands for configuring the HP-UX kernel. There are three primary commands. kconfig manages whole kernel configurations. kcmodule manages kernel modules. kctune manages tunable parameters. HP-UX 11i v3 retains the mk_kernel script, which is a wrapper around kconfig. Kclog displays the log file of configuration changes. Finallly, kcpath is a helper command for scripts that need to know where configuration files are located.

While users of HP-UX 11i v2 should be familiar with the “kc” commands, those coming from HP-UX 11i v1 will find that the “kc” commands have replaced the “km” kernel configuration commands (config, kmadmin, kminstall, kmmodreg, kmpath, kmsystem, kmtune, and kmupdate). For those coming from HP-UX 11i v1, in addition to these command changes, there are changes to the location of kernels and related files on disk; to the manner in which a kernel configuration is chosen at boot time; and to the manner in which the system automatically maintains a backup kernel configuration. In addition to the man pages, documentation on the kernel configuration tools can be found in the white paper Managing Kernel Configurations in HP-UX 11i, available at http://docs.hp.com.



March 2007125

Changes to Kernel Configuration Commandson HP-UX 11i v3 (1 of 2)• Clearer error, warning, and note messages from all kernel

configuration commands– Message numbers have been assigned to all messages

• Improved resiliency and performance of all kernel configuration commands

• New options for control of automatic configuration backups– Backup behaviors are yes, once, no, and disable– After each boot, default backup behavior is to ask whether to

update the backup config before each change• Tunable parameter values may now be overridden on the

boot loader command line

The error, warning, and note messages from all kernel configuration commands have been revised for clarity. Additionally, message numbers have been assigned to all messages.

kconfig, kcmodule, and kctune have new options for control of automatic configuration backups. The system maintains a saved configuration called backup, which can be used to recover from configuration errors. Depending on the selected backup behavior, the system can automatically save the currently running configuration to backup immediately before making any requested change to the configuration. The backup behavior is set using the -b behavior option to the kconfig, kcmodule, or kctune commands. The recognized backup behaviors are yes, once, no, disable. After each boot, the default backup behavior is to ask whether to update the backup configuration before each change. Changes made non-interactively assume a "no" response. See the discussion of the “Backup Configuration” in kconfig(5) for more details.

A variety of internal changes have been made to the kernel configuration commands to improve resiliency and performance.

Tunable parameter values may now be overridden on the boot loader command line. For more details, see hpux (1M) for PA-RISC systems and hpux.efi (1M) for Itanium systems.



March 2007126

Changes to Kernel Configuration Commandson HP-UX 11i v3 (2 of 2)• create_sysfile command is obsolete• swap, dump, and driver directives in the system (4) file are

obsolete– Use swapon, crashconf, and iobind commands instead

• Format of kernel configuration log file, /var/adm/kc.log, has changed– Contains complete copy of output of each command

invocation that made configuration changes– Contains error messages from failed attempts at

configuration changes• Tunable parameter changes made through the settune() or

settune_txn() system calls may no longer remain effective across reboots– Use kctune to ensure persistence across reboots

The create_sysfile command is now obsolete. It will be removed in a future release of HP-UX.

The swap, dump, and driver directives in the system (4) file are now obsolete. Support for these directives will be removed in a future release of HP-UX. Swap devices, dump devices, and driver bindings should be configured using the swapon, crashconf, and iobind commands, respectively.

The format of the kernel configuration log file, /var/adm/kc.log, has changed. It now contains a complete copy of the output of each command invocation that made configuration changes, as well as the error messages from failed attempts at configuration changes.

Tunable parameter changes made through the settune() or settune_txn() system calls may no longer remain effective across reboots. If persistence across reboots is desired, tunable parameter changes must be made using kctune.



March 2007127

Kernel Configuration Changes in HP-UX 11i v3 (1 of 2)Kernel configuration tool• Allows user to configure an HP-UX kernel• Allows user to monitor consumption of kernel resources

controlled by parameters, or tunables• Provides GUI and TUI

– Tune kernel tunables– Load and unload kernel modules– Configure alarms– View change logs

Launch kernel configuration tool• Using SMH or SIM or kcweb command

– Using kcweb command will launch the SMH GUI or TUI

The HP-UX Kernel Configuration tool allows the user to configure an HP-UX kernel and monitor consumption of kernel resources controlled by parameters. The Kernel Configuration tool provides web-based graphical user interface (GUI) and Text User Interface (TUI). Use the HP-UX Kernel Configuration tool for tuning the kernel tunables, loading and unloading kernel modules, configuring alarms, and viewing change logs.

You can launch the HP-UX Kernel Configuration tool from the HP System Management Homepage (HP SMH) and the HP Systems Insight Manager (HP SIM). You can also use the kcweb command to launch the Kernel Configuration tool. Using the kcweb command will automatically attempt to launch the SMH GUI. However, if DISPLAY is not set, or there is another issue, it will launch the SMH TUI.



March 2007128

Kernel Configuration Changes in HP-UX 11i v3 (2 of 2)Kernel configuration tool features on HP-UX 11i v3• TUI supports form-based inputs

– User can now see and enter all the data fields in a single form

– Command preview support • Error Management Technology support• Critical defect fixes

Documentation• Kernel Configuration Online Help• kcweb (1M) and smh (1M) manpages

The HP-UX Kernel Configuration tool has the following features. The TUI, which is used in place of the legacy SAM interface, supports form-based inputs. The user can now see and enter all the data fields in a single form. There is also command preview support to allow the user to preview the commands that will be executed for a task. Of course, there is a web-based Graphical User Interface (GUI). New in HP-UX 11i v3 on both PA and IA systems is Error Management Technology support and critical defect fixes.

In addition to the Kernel Configuration Online Help, refer to the kcweb (1M), sam (1M) and smh(1M) manpages. Also see the kcalarm (1M), kcmond (1M), kconfig (5), kconfig (1M), kcmodule(5), kctune (1M), kclog (1M), kcpath (1M), kcusage (1M), system (4) and manpages.



March 2007129

Changes to kctune in HP-UX 11i v3• kctune command has two new options

– Use -F option to specify the format used for reporting tunable values– Use -m option to restrict output to tunables defined in specific module

• kctune allows some tunable values to be specified in terms of percentage – Tunables will adjust automatically when the underlying system

resource changes– For example, filecache_max can be set to “20%”, which means that

the file cache cannot exceed 20% of the physical memory on the system. If the amount of system memory increases, the size of the file cache is automatically allowed to increase as well

• kctune allows the use of “K”, “KB”, “M”, “MB”, and “GB” suffixes on tunable values– Automatically scales the values appropriately

The kctune command has two new options. The -F option allows the user to specify the format used for reporting tunable values. The -m option allows the user to restrict the output of kctune to those tunables defined by a specific module. See kctune (1M) for more details.

kctune now allows some tunable values to be specified in terms of the percentage of some system resource. These tunables will adjust automatically when the underlying system resource changes. For example, the tunable filecache_max can be set to “20%”, which means that the file cache cannot exceed 20% of the physical memory on the system. If the amount of system memory increases, the size of the file cache is automatically allowed to increase as well. For more details, see kctune (1M) and the manpages for individual tunables in section 5.

kctune now allows the use of “K”, “KB”, “M”, “MB”, and “GB” suffixes on tunable values. It automatically scales the values appropriately. See kctune (1M) for more details.



March 2007130

Using the Configuration Log to Troubleshoot Configurations• Use the kclog command to view and add comments to the

configuration log• Add a comment# kclog –C “Add this comment to kernel config log”

• Search for entries containing a specified string# kclog –f “Oracle”

• View entries for the given object (tunable or module)# kclog –n “maxdsiz”

• View entries for all tunables# kclog –t tunable

• View the last 5 entries for a named kernel configuration# kclog –c weekendConfig 5

The kernel configuration commands maintain a log file that describes all kernel configuration changes. This log file is located at /var/adm/kc.log. The kclog command can be used to search and view the log file, or to make entries that don't correspond to configuration changes. When making a configuration change using any of the commands, you can specify -C comment to add a comment to the log file. The commands will include the specified comment in the log file entry describing the change. Note that the comment usually must be quoted to avoid interpretation by the shell.

Some configuration changes can be made without using the kernel configuration commands (that is, by using system calls). No log file entries are made for such changes. The format of the log file may be changed without notice. Programs must use the kclog command to retrieve entries from the file rather than attempting to parse the file format.



March 2007131

ActionConfiguration StateSystem State

Boot a known good configurationBackup or other configurations are available & good

Boot in failsafe mode & repair errors, then reboot

H/W problems or bad configuration

Your system is down

Load a known good configuration:kconfig –l <config>

Find previous changes in the kclog and reverse them using kctune, kcmodule, or kconfig.Backup is

questionable

kconfig –l backupBackup is known good

Your system is up

Recovering From Kernel Configuration Errors

The kernel configuration architecture was designed with easier error recovery in mind. If a particular kernel configuration does not perform well, there are several things you can do.

The basic troubleshooting strategy is to first suspect the most recent changes made to the kernel. The kernel configuration log, /var/adm/kc.log, provides useful information about changes made to the kernel. After isolating suspect changes in the kclog, you might try to reverse those changes, for example, by changing a tunable back to a previous value or unloading a module.

If attempts to correct the current configuration fail, your next step is to try to reboot using a known good kernel configuration. In most cases, this will be the backup configuration. For example, perform kconfig –l backup.

In extreme circumstances, such as a hardware failure, you can boot in failsafe mode, which is a single-user run state using pre-determined values for kernel tunables. From this failsafe mode, you can then attempt to fix any problems and then reboot using a known good configuration. Boot into failsafe mode when you cannot find a good kernel configuration to boot from. In failsafe mode, you can use KC commands to look at log files to determine problems with configurations and change a kernel configuration. First off, try to determine the cause of a kernel not booting properly. The kc.log file should help you find recent changes that you can back out of. Once you have changed a kernel configuration, boot from it.

Every tunable has a failsafe value, which is the value used when stored tunable value information is not available, or when the administrator requests a failsafe boot. It must be a fixed value (not computed at run time), and must be chosen as the safest possible value to use during system recovery operations. This will often be a different value than the algorithmically computed default value. The failsafe value is not specified in the tunable definition in the module metadata; it is given as a parameter to the ktune_get() call when the tunable is initialized during boot.



March 2007132

Peripheral Device Configuration and Management

pdweb Changes on HP-UX 11i v3PCI Card On-line DeletionPCI Card On-line Addition Issue



March 2007133

Peripheral Device Management on HP-UX 11i v3HP-UX Peripheral Device tool - pdweb(1M)• Lists and manages OLRAD capable PCI slots reported by

olrad and Peripheral Devices reported by ioscan• Displays details about the selected device/slot

New in HP-UX 11i v3• Supports Agile Hardware Path Addressing• Supports Persistent Device Special Files• Supports Online Deletion of OLRAD cards in addition to

Online Addition and Replacement• Reads the detailed CRA report from the log file• Has new TUI• Supports Error Management Technology

The HP-UX Peripheral Devices Manager tool (pdweb), lists and manages the OLRAD capable PCI slots reported by olrad command and Peripheral Devices reported by ioscan command. On selecting a slot/device from the list, it displays details about the selected device/slot.

The HP-UX Peripheral Devices Manager supports the Agile Hardware Path Addressing and Persistent Device Special Files. It now supports not only Online addition and replacement, but also Online deletion of OLRAD cards. It also now reads the detailed CRA report from the log file in which the report is logged after the change in the CRA behavior.

It allows a user to Add / Replace / Delete an OLRAD capable card online. The tool allows the user to view the devices reported by ioscan command and allows to re-install the Device Special Files where possible.

The Peripheral Devices Manager (pdweb) tool is enhanced to support the Agile Hardware Path Addressing and Persistent Device Special Files. The tool provides for backward compatibility by providing a link to toggle between the Agile Addressing and Legacy Addressing. Additionally, it allows Online deletion of OLRAD Cards.

In the HP-UX 11i v3 release, the Peripheral Devices Manager (pdweb) tool is also enhanced to provide a new Text User Interface (TUI) and support Error Management Technology.

Finally, pdweb now reads the detailed CRA report from the log file in which the report is logged after the change in the CRA behavior.

For further information, refer to the Peripheral Devices Manager Online Help, smh(1M) man page, and pdweb(1M) manpage.



March 2007134

PCI Card On-line Deletion on HP-UX 11i v3PCI card OLD allows deleting PCI cards and associated drivers without requiring a system reboot• PCI OLAR on HP-UX 11i v2 enhanced to include deletion• Now, full PCI OL*

Documentation• olrad (1M)• Interface Card OL* Support Guide, third edition

– http://docs.hp.com

PCI card online deletion (OLD) allows HP-UX 11i v3 administrators to delete PCI cards and their associated drivers without requiring a system reboot. For HP-UX 11i v3, the PCI OL* feature has been enhanced to include online deletion of PCI cards and associated drivers. For HP-UX 11i v2, the OL* feature provided online addition and replacement of PCI cards.

DocumentationManpages: olrad (1M)Documents: Interface Card OL* Support Guide, third edition available at http://docs.hp.com/en/ha.html#System%20Administration



March 2007135

PCI Card OLAR Issue on HP-UX 11i v3 (1 of 2)PCI card slot may become unusable• Requires a boot to return the slot to a usable state• Caused by firmware issue

Problem occurs under following conditions• HP-UX 11i v3• HP 9000 servers rp8420 or rp7420• PDC firmware version 24.1

If a system is booted, or an Online Addition operation is completed, with the latch on a PCI slot in the open position, the slot may become unusable, requiring a boot to return the slot to a usable state. This issue is specific to HP-UX 11i v3 running on the HP 9000 servers, rp8420 or rp7420, with PDC firmware version 24.1.

Remember that to verify the PDC firmware version, you can run STM. Or you can run the sysrevcommand from the management processor Command Menu (CM) prompt, MP:CM> sysrev



March 2007136

PCI Card OLAR Issue on HP-UX 11i v3 (2 of 2)Three scenarios where this may happen• Booting with latch of occupied PCI slot in open position results in card in

that slot being unusable– ioscan will show software state for card in that slot as UNUSABLE– PCIError Reported at <H/W path> message will appear on console

• Booting with latch of unoccupied slot in open position, adding card to slot, and running ioscan– Results in card being in UNSUSABLE state

• Regardless of whether the latch is closed or left open after the card is added to the slot

• Performing PCI card online addition operation and leaving latch of slot opened while bringing card online results in the card being in the UNUSABLE state

Recovery procedure to make slot usable again• Close latch on PCI slot that is in the UNUSABLE state• Reboot the system

Expect eventual firmware fix

There are three scenarios in which this issue may occur.

Booting with the latch of an occupied PCI slot in the open position results in the card in that slot being unusable. The ioscan command will show the software state for the card in that slot as UNUSABLE. Also, a PCIError Reported at <H/W path> message will appear on the console.

Booting with the latch of an unoccupied slot in the open position, then adding a card to that slot and executing an ioscan command, will result in the card being in the UNSUSABLE state (provided the -k option is not used and the ioscan is not restricted from covering the path to that slot). In this scenario, the card will become UNUSABLE, regardless of whether the latch is closed or left open, after the card is added to the slot.

Performing a PCI card online addition (OLA) operation using the olrad command or the pdweb GUI, and leaving the latch of the slot opened while bringing the card online, results in the card being in the UNUSABLE state.

This behavior is due to a firmware issue. Until a firmware fix is available, you can close the latch on the PCI slot that is in the UNUSABLE state. Then, reboot the system. The slot will become usable again.



March 2007137

Section SummaryThis section described• Changes to the OEs on HP-UX 11i v3• HP-UX 11i v3 installation, update, and configuration requirements• How to perform an HP-UX 11i v3 installation/update and troubleshoot issues• How to perform post-installation/update tasks• Software deployment changes

– Software Manager– Ignite-UX– Update-UX– Software Distributor– Software Package Builder– Dynamic Root Disk (Pre-enablement)

• Software update while the system is up• Boot and Update

– Faster Boot– Boot-time override of Kernel Tunables– DLKM of I/O Drivers

• How to perform post-installation/update configuration tasks

In this section, we covered the installation requirements and processes for HP-UX 11i v3, as well as the update process from earlier releases. In addition, many of the modifications to post-installation configuration tasks were covered, such as kernel configuration and peripheral device configuration.



March 2007138

Learningcheck

See the Lab Guide.



March 2007139

Labactivity

See the Lab Guide.