HP UX System Management Software Recovery and the agile view, Legacy DSFs and device matching

Page 80

Recovery and the agile view

During recovery, Ignite-UX C.7.x makes changes to the new system I/O configuration to match the original system I/O configuration. This is necessary because some aspects of a system configuration depend on the unpredictable order of system I/O inventory.

The overall goal of this process is to make the system I/O configuration appear as if the system simply rebooted at the time the recovery archive was created. This process is complex, and Ignite-UX might be unable to fully restore the I/O configuration. Ignite might not be able to restore aspects of the I/O configuration due to hardware changes, limitations of system I/O software, and limitations of Ignite-UX.

The system I/O configuration must be verified during and after recovery so configuration adjustments can be made if needed.

One part of restoring the I/O configuration is the appropriate matching of device special files (DSFs) and devices. There is one approach used for legacy DSFs in HP-UX 11i v3 and previous releases, and another approach used for HP-UX 11i v3 persistent DSFs.

Legacy DSFs and device matching

Matching legacy DSFs and mass storage devices is done based on hardware paths. Generally, legacy DSFs are associated with a particular hardware path. During recovery, a device is associated with its hardware path's DSF. (See Figure 16 (page 71) for a description of the legacy addressing model.)

Hardware configuration changes are handled by assuming a new device is intended to replace the device originally at that hardware path.

Note that some I/O protocols, such as SAS and USB, associate legacy DSFs with specific devices using unique LUN IDs, and so behave like persistent DSF matching described below.

SAS devices are a special case, since their legacy DSF/unique LUN ID association can change as a result of I/O configuration changes. If you change a SAS configuration (physically move a SAS device to another bay or remove a SAS device) the hardware path associated with that and other SAS devices can change during an installation or recovery. In such a case, hardware paths are reassigned to SAS devices. Since legacy DSFs are associated with a particular hardware path, a change in a device's hardware path breaks the association between its previous legacy DSF and its unique LUN ID. Note that the way SAS devices are associated during recovery might change in future versions of Ignite-UX to use the agile addressing approach described below.

Only certain SAS configuration changes cause remapping of hardware paths. For more information see the white paper, “Ignite-UX and SAS Devices” available at http://www.hp.com/go/ ignite-ux-docs.

Persistent DSFs and device matching

Matching persistent DSFs and mass storage devices is relatively complex due to agile addressing. Ignite-UX will attempt to simulate agile addressing during recovery, while also dealing with hardware replacement. This matching is accomplished using the methods described below:

WWID — Matching is done based on the unique LUN ID of the device. Most often, this is the device's WWID. This method matches a device's original persistent DSF with the same device in the recovered system configuration.

Device ID — (Future) Matching is done based on a user-definable identifier written to the device. This method matches a device's original persistent DSF with the device that has the same device ID in the recovered system configuration. This method allows user-provided identification to control device matching. Note that some mass storage devices do not support the device ID feature.

Physical Location — Matching is done based on device physical location. This method matches the original persistent DSF associated with a particular physical location (e.g. same enclosure

80 Managing I/O for installation and recovery

Image 80
Contents Ignite-UX Administration Guide AbstractRevision History AcknowledgementsB2355-90849 HP-UX 11.00, 11i v1, 11i v1.6, 11i Contents Complex networks challenges and solutions Managing I/O for installation and recoverySimple network creating a server for anonymous clients Complex networks multi-capable serversBooting and installing HP-UX on clients using the server 110 SecurityCustomizing your installation 161 Automating installations 174Creating your own boot and installation media 180 Golden images 151Recovery 191 Support and other resources 224Documentation feedback 227 Troubleshooting 228 Configuring Dhcp services 236LIF volume contents 239 Terminal keyboard shortcuts 255HP secure development lifecycle Ignite-UX features Ignite-UX overviewOne-step installation Custom installationsAutomated installations Create custom installation mediaGetting the Ignite-UX software Ignite-UX bundles available in the Ignite-UX productIgnite-UX commands and manpages Ignite-UX command manpagesIntroduction to the Ignite-UX GUI Ignite-UX GUIFile menu View menuOptions menu Actions menuHow Ignite works Client status dialog boxIgnite-UX install environment Boot sourcesInstallation versus recovery Network booting and IP addressesPhases of operation PA-RISC SystemsItanium-Based Systems StartupPhase Ignite-UX server requirements Hardware requirementsOther considerations Supported peripherals Disks and other I/OFirmware Disk arraysSimple network solutions Making configuration decisions for Ignite serversBoot and install client from media Instlboottab Alternate boot with network server installation Diagnosing network boot issues Use DVD media to boot a system for network installationComplex networks For a detailed discussion, seeInvestigate instlbootd errors in /var/adm/syslog/syslog.log Instlboots allowHP-UX diagnosing and debugging Simple network debuggingRDP diagnosing and debugging Configuring the Ignite-UX server for PA-RISC clients Simple network creating a server for registered clientsLaunch Ignite-UX IgniteLaunch the server setup wizard Ignite-UX GUI welcome dialog boxServer setup wizard Configure booting IP addresses Register the PA-RISC clients with the serverConfiguring the Ignite-UX server for Itanium-based clients Skip Dhcp setupGo to the software setup section Register the Itanium-based clients with the serverSetting up software from OE depots More server setup options Configuring server optionsIgnite-UX server configuration tabs Configuring session options Add Dhcp addresses dialog boxSession options tab Setting up additional software on the server Example Create a configuration for compiler softwareSD software Non-SD softwareSimple network creating a server for registered clients Using the server setup wizard Editing the instlboottab fileItanium-based clients use Dhcp to boot anonymously Simple network creating a server for anonymous clientsWorking with Dhcp Understanding PXE booting of Itanium-based systemsIgnite-UX server and boot helper setup for Dhcp Page Since the install kernel and install file system must be Isolating Ignite-UX from noncontrollable Dhcp serversDhcpclassid=IgniteDHCPDeviceGroup Class-id=PXEClientArch00002IgniteDHCPDeviceGroupPage Complex network challenges Complex networks challenges and solutionsHow to use this chapter Multiple subnets Remote systemsAvoiding complex network issues Multiple boot serversUsing virtual LANs properly for Ignite-UX An Ignite-UX server for each subnetMulti-capable server for each subnet Extend the local subnetComplex network solutions Automating HP-UX OS version selectionDirected boot Limit network boot response by network interface addressLimit network response by system class Server selectionControl network boot via response timing Install remote clients through a network routerHaving the client contact the correct server Multiple NICs attach the Ignite server to multiple subnetsGetting the client the correct networking information Ignite-UX bootp boot helper HP-UX Dhcp PXE Next server boot helper for integrity systems Configuring a Next server boot helper for Integrity systemsForwarding boot requests via bootp relay Ha=000000000000\ Hm=000000000000\ Bp=10.2.1.11 Non-HP-UX bootp boot helper Multi-capable subnet boot serverNon-HP-UX Next server boot helper Complex networks multi-capable servers Configuring an RDP server for specific MAC addressesConfiguring an RDP server to delay PXE response Configuring an RDP server to initiate HP-UX installation Setting up RDP MenuOptions via Windows commandsSetting up RDP MenuOptions via interactive UI Complex networks multi-capable servers Configuring an RDP server to initiate HP-UX installation Using an RDP MenuOption for HP-UX Client MAC Addr 00 30 6E 4C AA A5Page SuSE RedHat installation from an HP-UX server FTP HttpThen you must specify the location of Linux install content Configuring an HP-UX server to support Windows installationSuSE installation from an HP-UX server Managing I/O for installation and recovery Introducing multipathingAgile view concepts Agile view I/O addressing logic looks like FigureAgile multiple path I/O stack addressing model System installation configuration Practical considerationsIgnite-UX client installation configuration tabs Disk Selection Root Disk Dialog Box With Physical Locations More Info dialog box Support for 2 TB boot disk Disk selection add/remove disks dialog boxImportant characteristics of the agile view Identifying devices for other tasksUNpath Per YH/W evi Persistent DSFs and device matching Recovery and the agile viewLegacy DSFs and device matching Persistent DSF-to-device matching methods by protocol Controlling the I/O configuration processO Configuration variables Agile view questions and answers O Configuration value typesAgile view questions and answers Security Ignite-UX server portsPort usage initiate LAN boot for Itanium-based clients Winstallfs Kernel BootSequence Port usage makenetrecovery initiated from the client Makenetrecovery Initiated from ClientPort usage makenetrecovery initiated from the server Makesysimage Initiated from ClientEnabling Ignite-UX server requirements Remove or comment-out the following lineEnabling Ignite-UX client requirements Run BastilleConfiguring Ignite to replace Tftp with NFS ProcedureOverview Ignite Product Files Moved in Version C.7.9 and LaterNow use instladm to update the install file system Set up NFS exports and check custom configuration filesUse vi to add hploadfileusenfs=true to the file Would need to be modified to beDisable Tftp on the Ignite-UX server optional Preparing the client for installation Where release is the release identifierFor 64-bit PA-RISC clients the files on the server are For Itanium-based clients the files on the server areMaking boot decisions when using the client console Boot using the networkBoot using media Using bootsys on the client console Support?Booting PA-RISC clients from the console Boot ADMINhelp bootBooting Itanium-based clients using the network Select Add a Boot Option Enter a brief description for this boot optionEnter the data type of this boot option Press Y to save the new boot optionDirect boot profiles for Itanium-based systems LAN1Options and operands Dbprofile commandSyntax Lanboot command Lanboot select -od optionaldata -dn nameExamples Shell dbprofile orInstalling HP-UX from the client console Shell lanboot orUser interface and media options Network Configuration with no Dhcp Examples Setting 100 Full Duplex Setting Mixed interface typesAdd this configuration clause to Wviinstallfs Edit the fileInstallation using bootsys Booting and installing HP-UX on clients using the serverMethods of installing client systems Touch /.bootsysblock Installation using the Ignite-UX GUI Prepare the client for installationStarting Ignite-UX Adding clientsBooting a client Select boot releaseBoot confirmation dialog box Boot process terminal windowNew client displayed in GUI Configuring the installation New installationInitializing the installation Client installation configuration interfaceFunctions available from all tabs Basic tabNo environments note Booting and installing HP-UX on clients using the server File system default choices All Legacy HW Paths Dialog BoxRoot Swap MB... button Languages dialog box Additional Configuration Controls Dialog Box Additional Configuration Controls Dialog Box Software tab Software tab for HP-UX 11i v1 and 11i Software cannot be unselected Marked ? column status can beChange Depot Location note Interactive swinstall notes Job? x/s/c System tab#nslookup test 255.255.248.0 or 0xfffff800 255.255.255.0 or 0xffffff00 Set Time Zone dialog boxSet Root Password dialog box Network Services tabs Set DNS Search Domains Dialog Box NIS tab Network Interfaces Dialog Box Select an Interface card from the selection listAdding or changing a file system configuration Configuring the installation Volume requirements for LVM and VxVM To change, add, or remove a disk from the clientAdvanced Disk Parameters dialog box Highlight a disk in the selection list to select itAdvanced File System Parameters dialog box Has these characteristics No gap is enabled between physical extents within a mirrorVolume Root volume /, the boot volume /stand, dump volumesAdvanced tab For more information, see manageindex1MRepeat an installation Executing the installation Repeat Install dialog boxInstallation Confirmation dialog box Client Status... dialog box Installation log file Viewing and printing a manifestPrintmanifest Creating a golden image Golden imagesAdvantages of golden images Installing the HP-UX operating system Installing critical patches onto the operating systemInstalling optional software Install the patch non-interactivelyCustomizing the system Creating the golden archiveOn the golden system, run Localedescription Here are the HP-UX 11i v1 swsource and swsel examples Creating and using golden images using GUI and CLI Creating golden image using GUIXhost +Ignite-UXserverhostname Opt/ignite/bin/igniteEnabling the client Creation of a golden image using CLIExamples on using makegoldenimage script Installing the golden image on the client Classes of configuration files Customizing your installationUsing configuration files Configuration File Use and Locations These install kernels and install file systems are locatedVar/opt/ignite/data/Relrelease Opt/ignite/data/Relrelease/configVar/opt/ignite/config.local Combining configuration files using Index entries Var/opt/ignite/clients/client/configConfiguration choices dialog box Example configuration files Defining DisksCombining Disks to Form a Single Volume Group Defining Networking ParametersDefining an Installation Depot Customizations based on the client hardwareCustomizations based on user selection # ia64# ia64 hp workstation zx2000 # 9000/785Avoid archiving patch files Xpatchsavefiles=falsetrueFor more information, see instldbg1M Debugging configuration filesUsing post-installation scripts Example How the installation functionsAdding a post-installation script Where t is for postconfigscript selection settings Using a saved configuration Automating installationsStarting a non-interactive installation with bootsys Using the per-client configuration file Specifying defaults in the config.local fileSetting defaults with instladm Final systemname=system11 Final ipaddrlan0=10.2.75.193 Press Ctrl-D Scheduling installationsSetting installation parameters dynamically Example Checking modified files for errors Instladm -T -f fileCreating your own boot and installation media Why use custom boot and installation media?Building PA-RISC boot and installation tape Possible tape contentsPossible PA-RISC installation tape layouts Logical interchange formatArchives and depots #nfssource=PA-RISC installation tape creation example AssumptionsSdserver = IPaddress Sddepotdir = /var/tmp/depot Change the sourcetype attribute from NET to MTExample PA-RISC installation tape creation Instladm -d -F /var/tmp/lifvol /var/tmp/cfgVerify your changes Instladm -d -f /var/tmp/lifvolCreating a boot CD/DVD or an installation DVD Boot and archive-based CD/DVDsAssumptions File and ISO image size considerationsBoot CD/DVD examples Installation archive-based DVD examples# makemediainstall -? # makeopticaldiscrecovery -?Error messages Create a recovery DVDPut a PA-RISC HP-UX 11i v2 golden archive on a DVD No DVD availableHP-UX 11i v2 Depot-based installation DVDs Depot-based DVDsNo DVD special files Missing -cargument on HP-UX 11i v2 USB DVD driveFor more information, see instladm1M and instladm4 Create the first DVDCopy the EFI partition into the first DVD pseudo-root Run mkisofs to create the first DVD image pathtodvd1imageHP-UX 11i v3 Depot-based installation DVDs Create the second DVDRun mkisofs to create the second DVD image pathtodvd2image Burn the DVD images and test themOverview RecoverySystem recovery System recovery tools Recovery tool comparisonUse maketaperecovery to Use makenetrecovery toRecovery image contents Recovery image configuration policies Recovery image creation process Create files and directories for the recovery imageVar/opt/ignite/clients/client/recovery/2005-03-17,1119 Var/opt/ignite/recovery/archives/client directoryRun the recovery interface Var/opt/ignite/clients/client/recovery/defaultsVar/opt/ignite/clients/client/recovery directory Prepare the configuration fileRecovery image creation status Examining recovery image contentsOpt/ignite/lbin/listexpander -f archivecontent Verifying recovery image results Init hpignoreswimpact=1Recovery Opt/ignite/recovery/mnressentials Creating and using recovery tapesRecovery tape creation examples Tape recovery for PA-RISC systems Recovering a minimal operating systemMaketaperecovery -x incentire=vg00 Maketaperecovery -A -s myserver -a /dev/rmt/0mTape recovery for Itanium-based systems Determining the tape drive’s EFI pathEFI menu with timer Select Boot Configuration from the Boot MenuBoot configuration Add boot entryList of selectable boot devices Enter load options Tape recovery for Integrity Blade systems Boot Manager menu with the new optionShell tapeboot select Fibre-Channel Creating and using network recovery imagesDetermine tape drive EFI path using Command Line Interface Network recovery server dependency Networking featuresAdding clients for recovery Var/opt/ignite/recovery/datetime/recovery.logXhost +Ignite-UXserverhostname Examples of network recovery image creation Recovering using the network for PA-RISC clientsMakenetrecovery -s myserver Makenetrecovery -s myserver -x incentire=vg00Recovering using the network for Itanium-based clients Retaining recovery images Hpux# rm latest # ln -s RecoveryArchive.sav latest Making recovery configuration file additions Using the recovery config.local fileVar/opt/ignite/clients/client/recovery/config.local Var/opt/ignite/recovery/config.localSelecting file systems during recovery Opt/ignite/data/RelB.11.11/configCD/DVD Using the makesysimage method Cloning a system using makenetrecovery Run # shareall -F nfsSystem recovery questions and answers QuestionCheck /etc/inetd.conf # rm oldhostname Related information Support and other resourcesContacting HP Websites Typographic Conventions Typographic conventionsFollowing conventions are used in this document Documentation feedback Troubleshooting Errors and warningsIgnite-UX server problems Installing systems with Ignite-UXProblem installing clients on multiple subnets Debugging SD during cold-installationToo much file space needed Ignite-UX requests more file system space than expectedBooting errors on PA-RISC systems Corrupted /opt/ignite/boot/bootlif fileProblems pointing to client over network Applications hang after ignitingReceived n bytes in s seconds Tftp quitBootsys Command Seems to Work in Reverse Server not listedInstalling from media Installing from golden imagesFile size miscalculated Common network booting errorsInsufficient Response to PXE Boot Request Creation of archive File Size miscalculated on HP Integrity virtual machinesConfiguring Dhcp services Overview of Dhcp servicesDhcp usage examples Using bootptab as an alternative to Dhcp Background information on Dhcp designLIF volume contents For more information, see Using configuration files For more information, see Classes of configuration filesDescription of the files in the LIF volume Using Integrated Lights Out Virtual Media with Ignite-UX 243 Using Integrated Lights Out Virtual Media with Ignite-UX 245 Using Integrated Lights Out Virtual Media with Ignite-UX 247 Using vMedia with DVD installation media and ISO images Expert recovery procedure Expert recoveryExpert recovery preparation Expert recovery Expert recovery procedure Expert recovery Expert recovery procedure # mknod /ROOT/dev/console c 0 Terminal keyboard shortcuts Basic keyboard shortcutsAdvanced keyboard navigation HP terminalsVt100 terminals Function keysAdvanced keyboard actions Glossary See Link Level Address LLAChecknetrecovery1M Maketaperecovery. See copyboottape1M Iinstall See instlcombine1M Makebundles1M Maketapenetrecovery See Software Distributor Vinstall Setting hplanadminargs, 108 boot source IndexIndex DVD Index LVM PXE Port usage on makenetrecovery, 89 port usage with bootsys Page Server display Xntp configuring, 136 screen Xntpd daemon
Related manuals
Manual 40 pages 50.5 Kb Manual 41 pages 43.08 Kb

UX System Management Software specifications

HP-UX System Management Software is a robust suite of tools designed to facilitate the administration and management of HP's Unix-based operating system, HP-UX. As organizations increasingly rely on mission-critical applications, the need for a reliable and efficient management solution becomes paramount. HP-UX provides a comprehensive understanding of system performance, resource utilization, and enterprise-wide configuration, all while maintaining high availability and security.

One of the key features of HP-UX System Management Software is its Advanced System Administrator Toolkit. This toolkit includes a wide array of utilities that streamline daily administrative tasks such as monitoring system performance, managing user accounts, and configuring system settings. Tools such as Glance provide real-time monitoring of system resources, enabling administrators to identify bottlenecks and optimize performance.

The software also boasts an advanced security framework, including features such as Role-Based Access Control (RBAC) and Secure Shell (SSH) for secure data transmission. Security patches and updates can be managed through HP’s Service Pack for HP-UX, which provides a streamlined method for maintaining system integrity and compliance with various regulatory standards.

Another notable aspect is the extensive support for virtualization technologies. HP-UX supports HP’s Integrity Virtual Machines (IVMs) and vPars, allowing administrators to create multiple isolated environments on a single physical server. This not only enhances resource utilization but also improves disaster recovery planning by enabling easier backup and restore processes.

For storage management, HP-UX offers tools that enable easy setup and management of Logical Volume Managers (LVM). This allows simplified disk space allocation and management, ensuring that critical applications have the necessary resources without manual intervention.

Furthermore, HP-UX is designed with compatibility in mind, supporting a wide range of third-party applications and frameworks. Integration with management platforms like HP System Insight Manager enhances the ability to monitor and manage systems from a centralized perspective, providing alerts and reports that help in proactive decision-making.

In summary, HP-UX System Management Software delivers a streamlined approach to system administration, focusing on performance, security, and ease of management. Its advanced features, combined with an emphasis on virtualization and storage management, make it a powerful tool for organizations seeking reliability and efficiency in their Unix-based environments. As businesses continue to evolve, tools like HP-UX will remain crucial for ensuring consistent performance and operational excellence.