HP UX System Management Software manual Check /etc/inetd.conf

Page 222

As long as the client is currently booted, use bootsys -ato start the installation process on the client without the need to interact with the user interface.

Ignite-UX chooses a configuration to use based on these guidelines:

If /var/opt/ignite/clients/client/config exists, use the cfg clause specified there.

If /var/opt/ignite/clients/client/config does not exist, use the default cfg clause for the client.

The default cfg clause for the client is the last applicable entry set to true in the CINDEX file if it exists. Otherwise, the default cfg clause is the last applicable entry set to true in the INDEX file. Because make_net_recovery sets the most recently created recovery cfg clause to true in CINDEX whenever it creates a new image, that will be the default unless it is manually changed.

To set Ignite-UX to choose the latest network recovery image automatically:

1.Rename or remove the config configuration file currently in the client’s directory, or use the bootsys -foption.

2.Run this from the Ignite-UX server: bootsys -aclient

For information on automating an installation, see the descriptions of run_ui, control_from_server, and INST_ALLOW_WARNINGS in instl_adm(4).

Question:

What causes tftp errors when recovering or installing a system?

Only /opt/ignite and /var/opt/ignite must be needed for tftp access.

Check /etc/inetd.conf

Files in INDEX must not be in directories outside /opt/ignite and /var/opt/ignite.

Question:

What can I do when problems occur from hot-swapping disks during recovery?

Ignite-UX supports only hot-swappable disks that are completely in place and not removed when creating a recovery image. Proper software and hardware procedures must be used for hot-swap disk removal or replacement before or after recovery, but not during. The LVM command, lvlnboot, used by save_config does not work when a disk is removed and the system is in this intermediate state. If this command is not working, a recovery cannot succeed.

Question:

Why is the EFI volume not restored during a recovery?

Ignite-UX destroys the old EFI volume on the boot disk and creates a new EFI volume every time the system is installed. At no point during the installation is the old EFI volume copied and restored to the disk.

To restore the EFI volume to the disk, reinstall the application or look at the SD configure scripts for the application and then rerun the commands that put the EFI volume in place on the disk.

Question:

Why does make_net_recovery fail when the image is 2 or more?

The make_net_recovery command uses NFS to write/read the system image from the client to/from the server. To manage images greater than 2 requires that both the client and server use NFS protocol Version 3 (PV3). NFS PV3 is standard on all HP-UX 11i releases.

222 Recovery

Image 222
Contents Ignite-UX Administration Guide AbstractRevision History AcknowledgementsB2355-90849 HP-UX 11.00, 11i v1, 11i v1.6, 11i Contents Simple network creating a server for anonymous clients Complex networks challenges and solutionsManaging I/O for installation and recovery Complex networks multi-capable serversBooting and installing HP-UX on clients using the server 110 SecurityCreating your own boot and installation media 180 Customizing your installation 161Automating installations 174 Golden images 151Recovery 191 Support and other resources 224LIF volume contents 239 Documentation feedback 227 Troubleshooting 228Configuring Dhcp services 236 Terminal keyboard shortcuts 255HP secure development lifecycle Ignite-UX features Ignite-UX overviewAutomated installations One-step installationCustom 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 boxInstallation versus recovery Ignite-UX install environmentBoot sources Network booting and IP addressesItanium-Based Systems Phases of operationPA-RISC Systems StartupPhase Ignite-UX server requirements Hardware requirementsOther considerations Firmware Supported peripheralsDisks and other I/O Disk arraysMaking configuration decisions for Ignite servers Boot and install client from mediaSimple network solutions Instlboottab Alternate boot with network server installation Complex networks Diagnosing network boot issuesUse DVD media to boot a system for network installation For a detailed discussion, seeHP-UX diagnosing and debugging Investigate instlbootd errors in /var/adm/syslog/syslog.logInstlboots allow Simple network debuggingRDP diagnosing and debugging Launch Ignite-UX Configuring the Ignite-UX server for PA-RISC clientsSimple network creating a server for registered clients IgniteLaunch the server setup wizard Ignite-UX GUI welcome dialog boxServer setup wizard Configure booting IP addresses Register the PA-RISC clients with the serverGo to the software setup section Configuring the Ignite-UX server for Itanium-based clientsSkip Dhcp setup 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 SD software Setting up additional software on the serverExample Create a configuration for compiler software Non-SD softwareSimple network creating a server for registered clients Itanium-based clients use Dhcp to boot anonymously Using the server setup wizardEditing the instlboottab file Simple network creating a server for anonymous clientsUnderstanding PXE booting of Itanium-based systems Ignite-UX server and boot helper setup for DhcpWorking with Dhcp Page Dhcpclassid=IgniteDHCPDeviceGroup Since the install kernel and install file system must beIsolating Ignite-UX from noncontrollable Dhcp servers Class-id=PXEClientArch00002IgniteDHCPDeviceGroupPage Complex networks challenges and solutions How to use this chapterComplex network challenges Multiple subnets Remote systemsAvoiding complex network issues Multiple boot serversMulti-capable server for each subnet Using virtual LANs properly for Ignite-UXAn Ignite-UX server for each subnet Extend the local subnetComplex network solutions Automating HP-UX OS version selectionLimit network response by system class Directed bootLimit network boot response by network interface address Server selectionControl network boot via response timing Install remote clients through a network routerMultiple NICs attach the Ignite server to multiple subnets Getting the client the correct networking informationHaving the client contact the correct server 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 Multi-capable subnet boot server Non-HP-UX Next server boot helperNon-HP-UX bootp boot helper Configuring an RDP server for specific MAC addresses Configuring an RDP server to delay PXE responseComplex networks multi-capable servers 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 HttpConfiguring an HP-UX server to support Windows installation SuSE installation from an HP-UX serverThen you must specify the location of Linux install content Agile view concepts Managing I/O for installation and recoveryIntroducing multipathing 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 Recovery and the agile view Legacy DSFs and device matchingPersistent DSFs and device matching Controlling the I/O configuration process O Configuration variablesPersistent DSF-to-device matching methods by protocol 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 Boot SequenceKernel 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 BastilleOverview Configuring Ignite to replace Tftp with NFSProcedure Ignite Product Files Moved in Version C.7.9 and LaterUse vi to add hploadfileusenfs=true to the file Now use instladm to update the install file systemSet up NFS exports and check custom configuration files Would need to be modified to beDisable Tftp on the Ignite-UX server optional For 64-bit PA-RISC clients the files on the server are Preparing the client for installationWhere release is the release identifier 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 Enter the data type of this boot option Select Add a Boot OptionEnter a brief description for this boot option Press Y to save the new boot optionDirect boot profiles for Itanium-based systems LAN1Dbprofile command SyntaxOptions and operands Examples Lanboot commandLanboot select -od optionaldata -dn name Shell dbprofile orInstalling HP-UX from the client console Shell lanboot orUser interface and media options Network Configuration with no Dhcp Examples Add this configuration clause to Wviinstallfs Setting 100 Full DuplexSetting Mixed interface types Edit the fileBooting and installing HP-UX on clients using the server Methods of installing client systemsInstallation using bootsys Touch /.bootsysblock Starting Ignite-UX Installation using the Ignite-UX GUIPrepare the client for installation 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 Volume Has these characteristicsNo gap is enabled between physical extents within a mirror 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 Golden images Advantages of golden imagesCreating a golden image Installing the HP-UX operating system Installing critical patches onto the operating systemCustomizing the system Installing optional softwareInstall the patch non-interactively 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/igniteCreation of a golden image using CLI Examples on using makegoldenimage scriptEnabling the client Installing the golden image on the client Customizing your installation Using configuration filesClasses of configuration files Configuration File Use and Locations These install kernels and install file systems are locatedOpt/ignite/data/Relrelease/config Var/opt/ignite/config.localVar/opt/ignite/data/Relrelease 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 hardware# ia64 hp workstation zx2000 Customizations based on user selection# ia64 # 9000/785Avoid archiving patch files Xpatchsavefiles=falsetrueDebugging configuration files Using post-installation scriptsFor more information, see instldbg1M How the installation functions Adding a post-installation scriptExample Where t is for postconfigscript selection settings Automating installations Starting a non-interactive installation with bootsysUsing a saved configuration Specifying defaults in the config.local file Setting defaults with instladmUsing the per-client configuration file Final systemname=system11 Final ipaddrlan0=10.2.75.193 Scheduling installations Setting installation parameters dynamicallyPress Ctrl-D Example Checking modified files for errors Instladm -T -f fileBuilding PA-RISC boot and installation tape Creating your own boot and installation mediaWhy use custom boot and installation media? Possible tape contentsPossible PA-RISC installation tape layouts Logical interchange formatArchives and depots #nfssource=Sdserver = IPaddress Sddepotdir = /var/tmp/depot PA-RISC installation tape creation exampleAssumptions Change the sourcetype attribute from NET to MTVerify your changes Example PA-RISC installation tape creationInstladm -d -F /var/tmp/lifvol /var/tmp/cfg Instladm -d -f /var/tmp/lifvolAssumptions Creating a boot CD/DVD or an installation DVDBoot and archive-based CD/DVDs File and ISO image size considerations# makemediainstall -? Boot CD/DVD examplesInstallation archive-based DVD examples # makeopticaldiscrecovery -?Put a PA-RISC HP-UX 11i v2 golden archive on a DVD Error messagesCreate a recovery DVD No DVD availableNo DVD special files HP-UX 11i v2 Depot-based installation DVDsDepot-based DVDs Missing -cargument on HP-UX 11i v2 USB DVD driveCopy the EFI partition into the first DVD pseudo-root For more information, see instladm1M and instladm4Create the first DVD Run mkisofs to create the first DVD image pathtodvd1imageRun mkisofs to create the second DVD image pathtodvd2image HP-UX 11i v3 Depot-based installation DVDsCreate the second DVD Burn the DVD images and test themRecovery System recoveryOverview Use maketaperecovery to System recovery toolsRecovery tool comparison Use makenetrecovery toRecovery image contents Recovery image configuration policies Var/opt/ignite/clients/client/recovery/2005-03-17,1119 Recovery image creation processCreate files and directories for the recovery image Var/opt/ignite/recovery/archives/client directoryVar/opt/ignite/clients/client/recovery directory Run the recovery interfaceVar/opt/ignite/clients/client/recovery/defaults Prepare the configuration fileRecovery image creation status Examining recovery image contentsOpt/ignite/lbin/listexpander -f archivecontent Verifying recovery image results Init hpignoreswimpact=1Recovery Creating and using recovery tapes Recovery tape creation examplesOpt/ignite/recovery/mnressentials Maketaperecovery -x incentire=vg00 Tape recovery for PA-RISC systemsRecovering a minimal operating system 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 optionCreating and using network recovery images Determine tape drive EFI path using Command Line InterfaceShell tapeboot select Fibre-Channel Adding clients for recovery Network recovery server dependencyNetworking features Var/opt/ignite/recovery/datetime/recovery.logXhost +Ignite-UXserverhostname Makenetrecovery -s myserver Examples of network recovery image creationRecovering using the network for PA-RISC clients Makenetrecovery -s myserver -x incentire=vg00Recovering using the network for Itanium-based clients Retaining recovery images Hpux# rm latest # ln -s RecoveryArchive.sav latest Var/opt/ignite/clients/client/recovery/config.local Making recovery configuration file additionsUsing the recovery config.local file 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 Support and other resources Contacting HPRelated information Websites Typographic conventions Following conventions are used in this documentTypographic Conventions Documentation feedback Ignite-UX server problems TroubleshootingErrors and warnings Installing systems with Ignite-UXToo much file space needed Problem installing clients on multiple subnetsDebugging SD during cold-installation Ignite-UX requests more file system space than expectedBooting errors on PA-RISC systems Corrupted /opt/ignite/boot/bootlif fileReceived n bytes in s seconds Problems pointing to client over networkApplications hang after igniting Tftp quitBootsys Command Seems to Work in Reverse Server not listedInstalling from media Installing from golden imagesCommon network booting errors Insufficient Response to PXE Boot RequestFile size miscalculated 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 Expert recovery preparationExpert recovery procedure Expert recovery Expert recovery procedure Expert recovery Expert recovery procedure # mknod /ROOT/dev/console c 0 Advanced keyboard navigation Terminal keyboard shortcutsBasic keyboard shortcuts 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.