HP UX System Management Software manual Setting up RDP MenuOptions via interactive UI

Page 63

.\MenuOption162.0 (nbp.efi renamed as required by the RDP server)

.\MenuOption163.0 (nbp.efi renamed as required by the RDP server)

.\Rel_B.11.23

.\Rel_B.11.23\IINSTALLFS

.\Rel_B.11.23\IINSTALL

.\Rel_B.11.31

.\Rel_B.11.31\IINSTALL

.\Rel_B.11.31\IINSTALLFS

.\fpswa.efi

.\hpux.efi

.\AUTO

The RDP server requires the file name of the initial boot loader file and the name of the MenuOption to match. Normally, MenuOption160 will be used by the RDP server. However, if there are existing custom MenuOptions, another file name might be required. Copying the small nbp.efi boot loader to the first few custom MenuOption names the PXE Configuration Utility uses for MenuOptions must simplify the automatic set up of the RDP server. For HP-UX, this file is actually the nbp.efi network boot loader.

The Ignite-UX version for this content on the RDP server must be kept consistent with the Ignite-UX product version on the Ignite server. Note that IINSTALLFS includes config file content typically modified via use of instl_adm. Since these files will reside on the RDP server, a data center administration process for updating these files must be created to keep the RDP files consistent with the Ignite server.

The Ignite install environment on the RDP server needs to be updated when:

The IINSTALLFS config content is changed

A new version of Ignite software is installed on the Ignite server

Changes are made to the AUTO file boot menu

The HP-UX boot loader is patched

Setting up RDP MenuOptions via interactive UI

The RDP server PXE Configuration Utility may be used to interactively create a MenuOption for HP-UX boot and Ignite installation.

Before starting the interactive UI, put the Ignite-UX boot and install environment files in a directory as specified in “Setting up RDP MenuOptions via Windows commands” (page 62). Any convenient method may be used to transfer the required content from the Ignite server to the RDP server (FTP, Samba share, key chain drive, etc.). You must consider how this content will be updated in the future to stay consistent with the Ignite server.

The Interactive UI may be started using the Windows Start Menu:

StartAll ProgramsAltirisPXE ServicesPXE Configuration Utility

It may also be started from the RDP Deployment Solutions Console.

Once started, the PXE Configuration Utility will display a window similar to the following:

Configuring an RDP server to initiate HP-UX installation 63

Image 63
Contents Abstract Ignite-UX Administration GuideAcknowledgements Revision HistoryB2355-90849 HP-UX 11.00, 11i v1, 11i v1.6, 11i Contents Complex networks multi-capable servers Complex networks challenges and solutionsManaging I/O for installation and recovery Simple network creating a server for anonymous clientsSecurity Booting and installing HP-UX on clients using the server 110Golden images 151 Customizing your installation 161Automating installations 174 Creating your own boot and installation media 180Support and other resources 224 Recovery 191Terminal keyboard shortcuts 255 Documentation feedback 227 Troubleshooting 228Configuring Dhcp services 236 LIF volume contents 239HP secure development lifecycle Ignite-UX overview Ignite-UX featuresCreate custom installation media One-step installationCustom installations Automated installationsIgnite-UX bundles available in the Ignite-UX product Getting the Ignite-UX softwareIgnite-UX command manpages Ignite-UX commands and manpagesIgnite-UX GUI Introduction to the Ignite-UX GUIView menu File menuActions menu Options menuClient status dialog box How Ignite worksNetwork booting and IP addresses Ignite-UX install environmentBoot sources Installation versus recoveryStartup Phases of operationPA-RISC Systems Itanium-Based SystemsPhase Hardware requirements Ignite-UX server requirementsOther considerations Disk arrays Supported peripheralsDisks and other I/O FirmwareMaking configuration decisions for Ignite servers Boot and install client from mediaSimple network solutions Instlboottab Alternate boot with network server installation For a detailed discussion, see Diagnosing network boot issuesUse DVD media to boot a system for network installation Complex networksSimple network debugging Investigate instlbootd errors in /var/adm/syslog/syslog.logInstlboots allow HP-UX diagnosing and debuggingRDP diagnosing and debugging Ignite Configuring the Ignite-UX server for PA-RISC clientsSimple network creating a server for registered clients Launch Ignite-UXIgnite-UX GUI welcome dialog box Launch the server setup wizardServer setup wizard Register the PA-RISC clients with the server Configure booting IP addressesRegister the Itanium-based clients with the server Configuring the Ignite-UX server for Itanium-based clientsSkip Dhcp setup Go to the software setup sectionSetting up software from OE depots Configuring server options More server setup optionsIgnite-UX server configuration tabs Add Dhcp addresses dialog box Configuring session optionsSession options tab Non-SD software Setting up additional software on the serverExample Create a configuration for compiler software SD softwareSimple network creating a server for registered clients Simple network creating a server for anonymous clients Using the server setup wizardEditing the instlboottab file Itanium-based clients use Dhcp to boot anonymouslyUnderstanding PXE booting of Itanium-based systems Ignite-UX server and boot helper setup for DhcpWorking with Dhcp Page Class-id=PXEClientArch00002IgniteDHCPDeviceGroup Since the install kernel and install file system must beIsolating Ignite-UX from noncontrollable Dhcp servers Dhcpclassid=IgniteDHCPDeviceGroupPage Complex networks challenges and solutions How to use this chapterComplex network challenges Remote systems Multiple subnetsMultiple boot servers Avoiding complex network issuesExtend the local subnet Using virtual LANs properly for Ignite-UXAn Ignite-UX server for each subnet Multi-capable server for each subnetAutomating HP-UX OS version selection Complex network solutionsServer selection Directed bootLimit network boot response by network interface address Limit network response by system classInstall remote clients through a network router Control network boot via response timingMultiple 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 Configuring a Next server boot helper for Integrity systems HP-UX Dhcp PXE 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 helper Non-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 Setting up RDP MenuOptions via Windows commands Configuring an RDP server to initiate HP-UX installationSetting up RDP MenuOptions via interactive UI Complex networks multi-capable servers Configuring an RDP server to initiate HP-UX installation Client MAC Addr 00 30 6E 4C AA A5 Using an RDP MenuOption for HP-UXPage SuSE FTP Http RedHat installation from an HP-UX serverConfiguring 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 I/O addressing logic looks like Figure Managing I/O for installation and recoveryIntroducing multipathing Agile view conceptsAgile multiple path I/O stack addressing model Practical considerations System installation configurationIgnite-UX client installation configuration tabs Disk Selection Root Disk Dialog Box With Physical Locations More Info dialog box Disk selection add/remove disks dialog box Support for 2 TB boot diskIdentifying devices for other tasks Important characteristics of the agile viewUNpath 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 O Configuration value types Agile view questions and answersAgile view questions and answers Ignite-UX server ports SecurityPort usage initiate LAN boot for Itanium-based clients Winstallfs Boot SequenceKernel Makenetrecovery Initiated from Client Port usage makenetrecovery initiated from the clientMakesysimage Initiated from Client Port usage makenetrecovery initiated from the serverRemove or comment-out the following line Enabling Ignite-UX server requirementsRun Bastille Enabling Ignite-UX client requirementsIgnite Product Files Moved in Version C.7.9 and Later Configuring Ignite to replace Tftp with NFSProcedure OverviewWould need to be modified to be Now use instladm to update the install file systemSet up NFS exports and check custom configuration files Use vi to add hploadfileusenfs=true to the fileDisable Tftp on the Ignite-UX server optional For Itanium-based clients the files on the server are Preparing the client for installationWhere release is the release identifier For 64-bit PA-RISC clients the files on the server areBoot using the network Making boot decisions when using the client consoleBoot using media Support? Using bootsys on the client consoleBoot ADMINhelp boot Booting PA-RISC clients from the consoleBooting Itanium-based clients using the network Press Y to save the new boot option Select Add a Boot OptionEnter a brief description for this boot option Enter the data type of this boot optionLAN1 Direct boot profiles for Itanium-based systemsDbprofile command SyntaxOptions and operands Shell dbprofile or Lanboot commandLanboot select -od optionaldata -dn name ExamplesShell lanboot or Installing HP-UX from the client consoleUser interface and media options Network Configuration with no Dhcp Examples Edit the file Setting 100 Full DuplexSetting Mixed interface types Add this configuration clause to WviinstallfsBooting and installing HP-UX on clients using the server Methods of installing client systemsInstallation using bootsys Touch /.bootsysblock Adding clients Installation using the Ignite-UX GUIPrepare the client for installation Starting Ignite-UXSelect boot release Booting a clientBoot process terminal window Boot confirmation dialog boxNew client displayed in GUI New installation Configuring the installationClient installation configuration interface Initializing the installationBasic tab Functions available from all tabsNo environments note Booting and installing HP-UX on clients using the server All Legacy HW Paths Dialog Box File system default choicesRoot 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 Marked ? column status can be Software cannot be unselectedChange Depot Location note Interactive swinstall notes System tab Job? x/s/c#nslookup test Set Time Zone dialog box 255.255.248.0 or 0xfffff800 255.255.255.0 or 0xffffff00Set Root Password dialog box Network Services tabs Set DNS Search Domains Dialog Box NIS tab Select an Interface card from the selection list Network Interfaces Dialog BoxAdding or changing a file system configuration Configuring the installation To change, add, or remove a disk from the client Volume requirements for LVM and VxVMHighlight a disk in the selection list to select it Advanced Disk Parameters dialog boxAdvanced File System Parameters dialog box Root volume /, the boot volume /stand, dump volumes Has these characteristicsNo gap is enabled between physical extents within a mirror VolumeFor more information, see manageindex1M Advanced tabRepeat an installation Repeat Install dialog box Executing the installationInstallation Confirmation dialog box Client Status... dialog box Viewing and printing a manifest Installation log filePrintmanifest Golden images Advantages of golden imagesCreating a golden image Installing critical patches onto the operating system Installing the HP-UX operating systemCreating the golden archive Installing optional softwareInstall the patch non-interactively Customizing the systemOn the golden system, run Localedescription Here are the HP-UX 11i v1 swsource and swsel examples Creating golden image using GUI Creating and using golden images using GUI and CLIOpt/ignite/bin/ignite Xhost +Ignite-UXserverhostnameCreation 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 These install kernels and install file systems are located Configuration File Use and LocationsOpt/ignite/data/Relrelease/config Var/opt/ignite/config.localVar/opt/ignite/data/Relrelease Var/opt/ignite/clients/client/config Combining configuration files using Index entriesConfiguration choices dialog box Defining Disks Example configuration filesDefining Networking Parameters Combining Disks to Form a Single Volume GroupCustomizations based on the client hardware Defining an Installation Depot# 9000/785 Customizations based on user selection# ia64 # ia64 hp workstation zx2000Xpatchsavefiles=falsetrue Avoid archiving patch filesDebugging 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 Instladm -T -f file Checking modified files for errorsPossible tape contents Creating your own boot and installation mediaWhy use custom boot and installation media? Building PA-RISC boot and installation tapeLogical interchange format Possible PA-RISC installation tape layouts#nfssource= Archives and depotsChange the sourcetype attribute from NET to MT PA-RISC installation tape creation exampleAssumptions Sdserver = IPaddress Sddepotdir = /var/tmp/depotInstladm -d -f /var/tmp/lifvol Example PA-RISC installation tape creationInstladm -d -F /var/tmp/lifvol /var/tmp/cfg Verify your changesFile and ISO image size considerations Creating a boot CD/DVD or an installation DVDBoot and archive-based CD/DVDs Assumptions# makeopticaldiscrecovery -? Boot CD/DVD examplesInstallation archive-based DVD examples # makemediainstall -?No DVD available Error messagesCreate a recovery DVD Put a PA-RISC HP-UX 11i v2 golden archive on a DVDMissing -cargument on HP-UX 11i v2 USB DVD drive HP-UX 11i v2 Depot-based installation DVDsDepot-based DVDs No DVD special filesRun mkisofs to create the first DVD image pathtodvd1image For more information, see instladm1M and instladm4Create the first DVD Copy the EFI partition into the first DVD pseudo-rootBurn the DVD images and test them HP-UX 11i v3 Depot-based installation DVDsCreate the second DVD Run mkisofs to create the second DVD image pathtodvd2imageRecovery System recoveryOverview Use makenetrecovery to System recovery toolsRecovery tool comparison Use maketaperecovery toRecovery image contents Recovery image configuration policies Var/opt/ignite/recovery/archives/client directory Recovery image creation processCreate files and directories for the recovery image Var/opt/ignite/clients/client/recovery/2005-03-17,1119Prepare the configuration file Run the recovery interfaceVar/opt/ignite/clients/client/recovery/defaults Var/opt/ignite/clients/client/recovery directoryExamining recovery image contents Recovery image creation statusOpt/ignite/lbin/listexpander -f archivecontent Init hpignoreswimpact=1 Verifying recovery image resultsRecovery Creating and using recovery tapes Recovery tape creation examplesOpt/ignite/recovery/mnressentials Maketaperecovery -A -s myserver -a /dev/rmt/0m Tape recovery for PA-RISC systemsRecovering a minimal operating system Maketaperecovery -x incentire=vg00Determining the tape drive’s EFI path Tape recovery for Itanium-based systemsSelect Boot Configuration from the Boot Menu EFI menu with timerAdd boot entry Boot configurationList of selectable boot devices Enter load options Boot Manager menu with the new option Tape recovery for Integrity Blade systemsCreating and using network recovery images Determine tape drive EFI path using Command Line InterfaceShell tapeboot select Fibre-Channel Var/opt/ignite/recovery/datetime/recovery.log Network recovery server dependencyNetworking features Adding clients for recoveryXhost +Ignite-UXserverhostname Makenetrecovery -s myserver -x incentire=vg00 Examples of network recovery image creationRecovering using the network for PA-RISC clients Makenetrecovery -s myserverRecovering using the network for Itanium-based clients Hpux Retaining recovery images# rm latest # ln -s RecoveryArchive.sav latest Var/opt/ignite/recovery/config.local Making recovery configuration file additionsUsing the recovery config.local file Var/opt/ignite/clients/client/recovery/config.localOpt/ignite/data/RelB.11.11/config Selecting file systems during recoveryCD/DVD Using the makesysimage method Run # shareall -F nfs Cloning a system using makenetrecoveryQuestion System recovery questions and answersCheck /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 Installing systems with Ignite-UX TroubleshootingErrors and warnings Ignite-UX server problemsIgnite-UX requests more file system space than expected Problem installing clients on multiple subnetsDebugging SD during cold-installation Too much file space neededCorrupted /opt/ignite/boot/bootlif file Booting errors on PA-RISC systemsTftp quit Problems pointing to client over networkApplications hang after igniting Received n bytes in s secondsServer not listed Bootsys Command Seems to Work in ReverseInstalling from golden images Installing from mediaCommon network booting errors Insufficient Response to PXE Boot RequestFile size miscalculated File Size miscalculated on HP Integrity virtual machines Creation of archiveOverview of Dhcp services Configuring Dhcp servicesDhcp usage examples Background information on Dhcp design Using bootptab as an alternative to DhcpLIF volume contents For more information, see Classes of configuration files For more information, see Using 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 HP terminals Terminal keyboard shortcutsBasic keyboard shortcuts Advanced keyboard navigationFunction keys Vt100 terminalsAdvanced keyboard actions See Link Level Address LLA GlossaryChecknetrecovery1M Maketaperecovery. See copyboottape1M Iinstall See instlcombine1M Makebundles1M Maketapenetrecovery See Software Distributor Vinstall Index Setting hplanadminargs, 108 boot sourceIndex 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