You are on page 1of 30

HP-UX Network Ignite Recovery

TITLE:

MTS HP-UX Network Ignite Recovery

Description:

This document lists steps required to recovery a HP-UX server using an ignite image stored on the Ignite Network Servers located in the Regional Data Centers.

IJSM100Q Page 1 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


TABLE OF CONTENTS
I INTRODUCTION ..............................................................................................................3 CROSS REFERENCED DOCUMENTS.............................................................................................3 CONTROL OF QUALITY RECORDS ..............................................................................................3 A. OVERVIEW ......................................................................................................................4 B. RESTORE PROCEDURE .....................................................................................................6 APPENDIX A SAMPLE FILE OF BRMAR01P:...............................................................30 II. AMENDMENT HISTORY ...........................................................................................30

IJSM100Q Page 2 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


I Introduction
Cross Referenced Documents A listing of key documents referenced within this document is listed in the table below:
CROSS REFERENCE DOCUMENT NAME FILENAME LOCATION or SOURCE (contact for document location)

Control of Quality Records Quality records generated from this procedure are summarized as follows:

RECORD NAME/ DESCRIPTION

LOCATION or SOURCE (contact for record location)

PROTECTION

DISPOSITION

RETENTION

IJSM100Q Page 3 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


A. Overview

Ignite-UX version B.5.4.50 is currently used for the Network Ignite Backup and Recovery. If your server is running any other version of Ignite-UX software, these procedures will not work. The Ignite Server and the client server must be running this same version of software. The Ignite Server creates a partial image of the root (vg00) volume group. The files listed in /opt/ignite/recovery/mnr_essentials on the client server are the minimum number of files that are included in the ignite image. These files are the minimum that are required to create a bootable image. For example, the files listed in mnr_essentials for this version of ignite include: /bin /dev /etc /lib /sbin /stand /stand/vmunix /usr/bin /usr/ccs /usr/conf /usr/lbin /usr/lib /usr/newconfig /usr/sbin /usr/sam /usr/share /usr/obam /usr/include/sys In addition to the above, the files identified in /var/opt/ignite/clients/0xmacaddr/recovery/archive_content located on the Ignite Server will also be included in the ignite image. There is an archive_content file for each client server based on its mac address; currently all of the archive_content files contain the same data as outlined below. Regarding restores: Since not all of the files on the root volume group are include in the ignite image, once the restore of the ignite image is complete, EBR will have to be engaged to restore the remaining root volume group files. (Note: the reason why the ignite image does not contain all of the root volume group files is due to space considerations on the Ignite Server.)
IJSM100Q Page 4 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


The archive_content file contents:
include /bin include /dev include /lib include /opt/prngd include /opt/openssh2 include /sbin include /stand include /stand/vmunix include /usr include /var exclude /var/adm/sw/save

During the restore, certain information will be requested. It is best to gather this information prior to attempting the restore. Having this information ahead of time will make the restore process easier. Most of the information that is needed can be gathered from MIRs SCIM info if the server to be restored is down. The information that will be needed is: 1) The Data Center name where the server being restored is located. 2) The 55 IP address of the server being restored (if no 55 IP address, then the BOSIP IP address which is used to log onto the server). 3) The Data Center name where the Ignite Server (containing the ignite images) is located. 4) The 55 IP address of the Ignite Server performing the restore (provided in the below table). 5) The Hardware Path of the LAN of the server to be restored that corresponds to the BOSIP IP (this can be acquired by the lanscan command and by examining /etc/rc.config.d/netconf or via SCIM info). 6) The netmask of the server to be restored (this can be acquired by examining /etc/rc.config.d/netconf or via SCIM info). 7) The default router/gateway used by the server to be restored (this can be acquired by examining /etc/rc.config.d/netconf or via SCIM info). 8) The hardware path of the tape drive on the server to be restored (this can be acquired by entering the command: ioscan kfC tape or via SCIM info. Note: this information can also be acquired during server boot time). 9) Have local operations locate an Ignite Boot Helper tape and insert it into the server to be restored. There are at least 5 per Data Center per Ignite server.

IJSM100Q Page 5 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


If an Ignite Boot Helper tape can not be located or if the ones that exist are all currently in use, an additional Boot Helper tape will need to be created. The Ignite Boot Helper tape must be created on the Ignite Server that will perform the image restore. Local operations can create one by placing a scratch tape in the Ignite Servers tape drive and entering the following command: # make_boot_tape -f /opt/ignite/share/bin/cfg_for_boot_helper_tape v See Appendex A for sample contents of file above file. B. Restore Procedure There are two Ignite Servers per Regional Data Center. The Ignite Server performing the restore and the server being restored must reside in the same Data Center. Below is the list of available Ignite Servers. Determine the Data Center where the server to be restored resides.

Step 1:

HP-UX Ignite Server List ======================================================= Birmingham BRDC BRMAR01P 55.10.1.158Non-Secure 88.1.23.69 (if no 55 IP on server to be restored) BRMAR02P 55.10.34.186. Secure 88.1.23.70 (if no 55 IP on server to be restored) ======================================================= Charlotte CRDC CRMAR01P 55.70.12.41 Non-Secure 88.4.38.62 (if no 55 IP on server to be restored) CRMAR02P 55.70.34.37........... Secure 89.70.63.9 (if no 55 IP on server to be restored) ======================================================= Jackson JRDC - JRMAR01T 55.60.5.117. Non-Secure 88.2.7.24 (if no 55 IP on server to be restored) JRMAR02T 55.60.32.1... Secure 89.60.10.101 (if no 55 IP on server to be restored) ======================================================= Step 2: Determine which one of the two available Data Center Ignite Servers will be used. If the server being restore has a 55 IP address: Look at the 3rd quartet of the 55 IP of the server being restored. If that number is 1 thru 29, use the non-secure server. If that number is 30 and above, use the secure server.
IJSM100Q Page 6 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


Example: IP = 55.60.6.17 use the Non-Secure Ignite Server IP = 55.60.45.7 use the Secure Ignite Server If the server being restored does not have a 55 IP address: Use the Non-Secure or Secure non-55 IP address of the Ignite Server, for example for Birmingham Non-Secure use 88.1.23.69 Step 3: Contact local operations and have them load the Ignite Boot Helper Tape into the server being restored. Verify that the tftp service is available on the Ignite Server used to perform the restore. From any server enter the following: tftp ip_address_of_ignite_server If the check fails, request local operations to contact the proper CSA to install the service. Step 5: Connect to the console of the server to be restored and restart/reboot the server. (Note: Accessing the console is usually done via CAMCS.) Insure that the terminal emulator that is used to access the console is set to vt100 mode. This will insure that after the Ignite Boot Helper tape boots later below, that the screens are displayed properly, that is the escape sequences are interpreted properly. For example if using SecureCRT: start SecureCRT from the pc, select the camcs server to connect to, right click for properties, click on emulation. VT100 terminal mode should be displayed. If the system is operational: If the system is not operational: # shutdown r y now have local operations power cycle the server Or ctrl-b and from main menu enter reset to restart/boot the server

Step 4:

Step 6:

The server will run diagnostics which may take several minutes. Interrupt the boot process by pressing any key when the following message appears: To discontinue press any key within 10 seconds

IJSM100Q Page 7 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


See the sample output:
Firmware Version 42.01 Duplex Console IO Dependent Code (IODC) revision 4 -----------------------------------------------------------------------------(c) Copyright 1998, Hewlett-Packard Company, All rights reserved -----------------------------------------------------------------------------Processor Speed State CoProcessor State Cache Size --------- ---------------------------- ----------------- ---------0 200 MHz Active Functional 2 MB 1 200 MHz Idle Functional 2 MB 2 200 MHz Idle Functional 2 MB 3 200 MHz Idle Functional 2 MB 4 200 MHz Idle Functional 2 MB 5 200 MHz Idle Functional 2 MB Central Bus Speed (in MHz) : 100 Available Memory : 3932144 KB Good Memory Required : 374808 KB Primary boot path: 10/8.6 (dec) Alternate boot path: 10/0.6 (dec) Console path: 10/4/0.0 (dec) Keyboard path: 10/12/7.0 (dec) Processor is booting from first available device. To discontinue, press any key within 10 seconds. Boot terminated.

(Type any key now)

Step 7:

The Main Menu appears. The Ignite Boot Helper tape needs to be booted. If the hardware path of the tape drive is known, one can enter it now as: boot #/#/# ( for example: boot 10/12/5.0
)

After booting, skip to the next step. Otherwise, one can have the system search for the hardware path of the tape drive as shown in the below sample screen:
---- Main Menu --------------------------------------------------------------Command Description ----------------BOot [PRI|ALT|<path>] Boot from specified path PAth [PRI|ALT] [<path>] Display or modify a path SEArch [DIsplay|IPL] [<path>] Search for boot devices COnfiguration menu Displays or sets boot values INformation menu Displays hardware information SERvice menu Displays service commands DIsplay Redisplay the current menu HElp [<menu>|<command>] Display help for menu or command RESET Restart the system IJSM100Q Page 8 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


---Main Menu: Enter command or menu > sea

Once the hardware path of the tape drive is known, one can then boot the Ignite Boot Helper tape. See the below sample where the tape is identified as the Sequential access media and path id 5 is then used to boot (answer n to Interact with IPL):
Searching for potential boot device(s) This may take several minutes. To discontinue search, press any key (termination may not be immediate). Path# Device Path (dec) Device Path (mnem) Device Type ----- ----------------- ------------------ ----------8/8.8 Fibre Channel interface 8/12.8 Fibre Channel interface P2 10/0.6 fwscsi.6 Random access media P3 10/8.6 Random access media P4 10/12/5.2 sescsi.2 Random access media P5 10/12/5.0 sescsi.0 Sequential access media P6 10/12/6.0 lan.0 LAN Module Main Menu: Enter command or menu > boot p5 Interact with IPL (Y, N, or Cancel)?> n Booting... (path 5 in this example)

Step 8: The Ignite Boot Helper tape will boot, see the sample output:
Boot IO Dependent Code (IODC) revision 1 HARD Booted. ISL Revision A.00.43 Apr 12, 2000 ISL booting hpux (;0):INSTALL Boot : tape(10/12/5.0.0.0.0.0.0;0):INSTALL 9806276 + 1126400 + 702592 start 0x151668 NOTICE: nfs3_link(): File system was registered at index 4. ALERT: fcT1 (0, 437, 8/8) Resetting Tachyon (Bogus trans-id) ALERT: fcT1 (0, 851, 8/8) Fibre Channel Driver received an interrupt indicating a Link Failure. The Frame Manager Status Register is 0x180010FA. ALERT: fcT1 (0, 1490, 8/12) Resetting Tachyon (Bogus trans-id) ALERT: fcT1 (0, 1760, 8/8) Fibre Channel Driver received an interrupt indicating a Link Failure. The Frame Manager Status Register is 0x180010FA. ALERT: fcT1 (0, 1904, 8/12) Fibre Channel Driver received an interrupt indicating a Link Failure. The Frame Manager Status Register is 0x180010FA. ALERT: fcT1 (0, 2813, 8/12) Fibre Channel Driver received an interrupt indicating a Link Failure. The Frame Manager Status Register is 0x180010FA. btlan1: Initializing 10/100BASE-T card at 10/4/8....... Swap device table: (start & size given in 512-byte blocks) entry 0 - auto-configured on root device; ignored - no room WARNING: no swap device configured, so dump cannot be defaulted to primary swap. IJSM100Q Page 9 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


WARNING: No dump devices are configured. Dump is disabled. Starting the STREAMS daemons-phase 1 Create STCP device files Starting the STREAMS daemons-phase 2 $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:05:38 PST 2000 $ Memory Information: physical page size = 4096 bytes, logical page size = 4096 bytes Physical: 3932132 Kbytes, lockable: 3046668 Kbytes, available: 3509988 Kbytes ======= 08/10/06 12:29:24 EDT HP-UX Installation Initialization. (Thu Aug 10 12:29:24 EDT 2006) @(#) Ignite-UX Revision B.5.4.50 @(#) install/init (opt) $Revision: 10.285 $ * EISA configuration has completed. Following the completion of a successful HP-UX installation, please check the "/etc/eisa/config.err" file for any EISA configuration messages. * Scanning system for IO devices... * Querying disk device: 10/0.6.0 ... * Querying disk device: 10/8.6.0 ... * Initializing FDDI interface: 10/4/4 (/dev/lan6) /usr/sbin/fddiinit: download /usr/lib/fddi_dnld .............done NOTE: Default (boot) source does not appear to be a valid (or complete) install source, switching source to Network * Setting keyboard language.

Step 9: Depending on the terminal interface that is used to access the console of the server being restored, one may or may not see the first screen, the Welcome to Ignite-UX! screen. This screens input is critical to the restore of the server. If the Welcome to Ignite-UX! screen does not appear, do not despair. Simply continue moving forward with the screens, ignoring whatever is input until a screen appears with a Cancel option. Tab until the Cancel is highlighted and type Enter. The following text appears: Do you really wish to abort all changes [y]? Type enter to accept the y answer and the Welcome to Ignite-UX! screen will appear. Then the following steps can be used to restore the server. Step 10: When the Welcome to Ignite-UX! menu appears, tab to select Install HP-UX and type enter. Note: At any time, if the screen gets garbled, enter control-l to repaint/refresh the screen.
IJSM100Q Page 10 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


See the sample output:
Welcome to Ignite-UX! Use the <tab> key to navigate between fields, and the arrow keys within fields. Use the <return/enter> key to select an item. Use the <return/enter> or <space-bar> to pop-up a choices list. If the menus are not clear, select the "Help" item for more information. Hardware Summary: System Model: 9000/899/K570 +---------------------+----------------+-------------------+ [ Scan Again ] | Disks: 2 ( 17.0GB) | Floppies: 0 | LAN cards: 7 | | CD/DVDs: 1 | Tapes: 1 | Memory: 3839Mb | | Graphics Ports: 0 | IO Buses: 4 | CPUs: 6 | [ H/W Details ] +---------------------+----------------+-------------------+ [ [ [ [ Reboot ] Install HP-UX Run a Recovery Shell Advanced Options ] ] ] [ Help ]

Step 11: The next menu to appear will be titled: User Interface and Media Options. The Ignite-UX server based installation option should be selected as indicated by the * in the brackets. If this option is not selected, tab until the cursor is on the proper brackets and type enter. The Advanced Installation option should be selected as indicated by the * in the brackets. If this option is not selected, tab until the cursor is on the proper brackets and type enter. Tab until OK is highlighted and type enter. See the sample output:
User Interface and Media Options This screen lets you pick from options that will determine if an Ignite-UX server is used, and your user interface preference. Source Location Options: [ ] Media only installation [ ] Media with Network enabled (allows use of SD depots) [ * ] Ignite-UX server based installation User Interface Options: [ ] Guided Installation (recommended for basic installs) [ * ] Advanced Installation (recommended for disk and file system management) [ ] No user interface - setup basic networking, use defaults and go IJSM100Q Page 11 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


[ ] Remote graphical interface running on the Ignite-UX server Hint: If you need to make LVM size changes, or want to set the final networking parameters during the install, you will need to use the Advanced mode (or remote graphical interface).
[ OK ] [ Cancel ] [ Help ]

Step 12: The LAN Interface Selection screen will appear. The LAN interfaces that are listed are the lans that exist on the server being restored. (One can verify the lan interfaces with MIRs SCIM Info report for the server being restored.) Note: the lan# Interface that appears on this screen will probably be different that the one in SCIM. Use the HW Path or the Station Address in SCIM to identify the lan to select. If the server has a 55 IP address, tab to select the LAN Interface that corresponds with the EBR 55 IP address of server to be restored. If the server does not have an EBR IP, then tab to select the LAN interface of the BOSIP IP, that is the IP that one uses to log onto the server. Once the LAN Interface has been selected, type enter. See the sample output:
LAN Interface Selection More than one network interface was detected on the system. You will need to select the interface to enable. Only one interface can be enabled, and it must be the one connected to the network that can be used in contacting the install and/or SD servers. Use the <tab> and/or arrow keys to move to the desired LAN device to enable, then press <Return>. HW Path Interface Station Address Description ---------------------------------------------------------8/0/1/0 lan0 0x0060B0A6A576 HSC_10/100Base-TX_K-Class 8/0/2/0 lan1 0x0060B0A6A577 HSC_10/100Base-TX_K-Class 8/4/1/0 lan2 0x0060B0A6A57A HSC_10/100Base-TX_K-Class 8/4/2/0 lan3 0x0060B0A6A57B HSC_10/100Base-TX_K-Class 10/4/4 lan6 0x0060B007A671 HP_J2157A_-_FDDI_Interface 10/4/8 lan7 0x080009DAC04B HP_HP-PB_100_Base_TX_card 10/12/6 lan8 0x0060B083B4EF Built-in_LAN

[ [ [ [ [ [ [

] ] ] ] ] ]
]

Step 13: The system will attempt to search for a DHCP server. One can wait the 30 seconds or so for the process to end or type control C to terminate. If one waits the 30 seconds, the process will terminate and automatically proceed to the
IJSM100Q Page 12 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


next screen.

Note: If using CAMCS to access the console, entering a control C will exit CAMCS; therefore enter \ then ctrl C to exit the procedure.

Searching the network for a DHCP server to supply default networking information... This could take up to 30 seconds if a DHCP server cannot be found. If you wish to cancel the DHCP server search, you may press CTRL-C now. (press Control-C here) * Could not get DHCP information. No host specific network defaults will be supplied. (dhcpclient returned: 9)

Step 14: The Network Configuration Screen will appear. Some of the fields may be automatically filled in with erroneous data. Do not assume that any of the automatically filled in data is correct. The sample output screen below show what data was automatically filled during a test restore. For example, 55.10.0.200 is not an IP associated with this server. For example, 55.10.1.158 is the 55 IP address for the Birmingham Non-Secure Ignite Server. See the sample output:
NETWORK CONFIGURATION This system's hostname: Internet protocol address (eg. 15.2.56.1) of this host: Default gateway routing internet protocol address: 55.10.0.200 The subnet mask (eg. 255.255.248.0 or 0xfffff800): 255.255.240.0 IP address of the Ignite-UX server system: 55.10.1.158 Is this networking information only temporary? [ No ]

IJSM100Q Page 13 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


[ OK ] [ Cancel ] [ Help ]

Step 15: Tab to the field to enter proper data. This systems hostname Enter the hostname of server to be restored. Internet Protocol Address of this host Enter the EBR IP of server to be restored (if the server does not have an EBR IP which is usually a 55 IP, then enter the BOSIP IP). Default Gateway routing Enter the EBR IP used above. Although this may look unusual, please enter the EBR IP as above (This will work since the 55 IP address acts as a gateway to the Ignite Server). If a BOSIP IP was used above, then enter the gateway of the server being restored (if needed, this can be found in MIRs SCIM info under /etc/rc.config.d Files). The Subnet Mask Enter the subnet mask of the IP of the server being restored (if needed, this can be found in MIRs SCIM info under HP Data Section /etc/rc.config.d Files Section). IP Address of Ignite-UX Server Enter the IP of the Ignite Server selected in step 1. Is this networking only temporary? [No] Select default of No. Verify all entries are correct, then tab to OK and type enter.
NETWORK CONFIGURATION This system's hostname: brmrg01p Internet protocol address (eg. 15.2.56.1) of this host: 90.152.53.150 Default gateway routing internet protocol address: 90.152.53.253 The subnet mask (eg. 255.255.248.0 or 0xfffff800): 255.255.254.0 IP address of the Ignite-UX server system: 88.1.23.69 Is this networking information only temporary? [ OK ] [ Cancel ] [ No ] [ Help ]

IJSM100Q Page 14 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


Step 16: The system will initiate networking and attempt to NFS mount the restore files. See the sample output:

* Bringing up Network (lan0) * running: lanadmin -X 100FD 0 Unable to open catalog for C Switching to the use of Internal Messages. WARNING: an incorrect setting could cause serious network problems!!! Driver is attempting to set the new speed Reset will take approximately 11 seconds add net default: gateway 90.152.53.253 * Reading configuration information from server...

Step 17: If the following error occurs, the server to be restored was not able to make a tftp connection to the Ignite Server; control will be transferred to the Lan Interface Screen so that data may be re-entered.. See the sample output:
Reset will take approximately 11 seconds add net default: gateway 90.152.53.253 * Reading configuration information from server... * tftp error log follows: ERROR: Could not read /var/opt/ignite/INDEX from install tftp server. NOTE: Retrying loadfile command... * tftp error log follows: tftp> Transfer timed out. ERROR: Could not read /var/opt/ignite/INDEX from install tftp server. Press any key to return to the network configuration menu: (Press any key, will go to the LAN Interface Selection screen )

If no error occurs then NFS will mount the appropriate files and the restore will continue. See the sample output:
add net default: gateway 90.152.53.253 * Reading configuration information from server... * NFS mounting clients directory. * Using client directory: /var/opt/ignite/clients/0x0060B0A6A576 * Checking configuration for consistency...
IJSM100Q Page 15 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


* Loading configuration user interface, please wait...

Step 18: The following screen may appear with a Confirmation Statement, Settings from a previous installation session were found at startup. Do you wish to retain these settings for the current session? Tab to N and press enter so that new settings may be used. See the sample output:

If the server to be restored has not been restored before: The center of the screen will display Root Disk Choices. The default highlighted disk will be the one that was the root disk when the image was created. Assuming that this is still the correct disk for the root disk, tab to highlight the OK and type enter. See sample output below:
IJSM100Q Page 16 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery

Step 19: The tabs at the top for Basic, Software, System, File System, and Advance will now be accessible. The cursor sits on the Basic tab and the Basic information is displayed. See the sample output below:

IJSM100Q Page 17 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery

If one wanted to, one could tab across the top from Basic to Software or to any of the others to verify the settings of the server being restored is as it was at ignite system image creation time. For example, one could select the File System tab and verify the file system sizes. If one wanted to, one could select the File System tab and change the size of any of the file systems such as /stand. Typically, no changes need to be made. Step 20: The ignite image being restored contains the root password as it existed when the ignite
IJSM100Q Page 18 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


image was created which may be several months ago. Rather than assuming what the root password was then, elect now to set the root password. Tab to the System tab at the top of the screen and type enter. Tab to Set Root Password and type enter. Enter your choice of root password and type enter.

See the sample output:

The root password will need to be entered again for verification then type enter. See the sample output below:

IJSM100Q Page 19 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery

Step 21: To start the restore, tab to GO! and type enter.

Note: if the root password was not set in the previous step, the system will ask to confirm that the root password does not need to be set and still want to continue. Yes will be highlighted. It is recommended to Tab to NO in order to change the root password if it was not set earlier.
See the sample output below:

IJSM100Q Page 20 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery

Step 22: A NOTE may appear advising: Free space (### KB) in "/var" where /var/adm/crash is located is less than 25% of system memory This NOTE may be ignored. Tab to GO! and type enter to continue the restore. The actual restore of the server will now begin. This usually takes about 20-30 minutes.
IJSM100Q Page 21 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


See sample output:
* Loading configuration utility... * Beginning installation from source: 90.152.48.117 ======= 08/11/06 12:54:12 EDT Starting system configuration... * Configure_Disks: Begin * Will install B.11.11 onto this system. * Creating LVM physical volume "/dev/rdsk/c7t6d0" (10/8.6.0). * Creating volume group "vgbroot". * Creating logical volume "vgbroot/lvol1" (/stand). * Creating logical volume "vgbroot/lvol2" (swap_dump). * Creating logical volume "vgbroot/lvol3" (/). * Creating logical volume "vgbroot/lvol4" (/tmp). * Creating logical volume "vgbroot/lvol5" (/home). * Creating logical volume "vgbroot/lvol6" (/opt). * Creating logical volume "vgbroot/lvol7" (/usr). * Creating logical volume "vgbroot/lvol8" (/var). * Creating logical volume "vgbroot/lvol9" (/bto). * Extending logical volume "vgbroot/lvol1" (/stand). * Extending logical volume "vgbroot/lvol2" (swap_dump). * Extending logical volume "vgbroot/lvol3" (/). * Extending logical volume "vgbroot/lvol4" (/tmp). * Extending logical volume "vgbroot/lvol5" (/home). * Extending logical volume "vgbroot/lvol6" (/opt). * Extending logical volume "vgbroot/lvol7" (/usr). * Extending logical volume "vgbroot/lvol8" (/var). * Extending logical volume "vgbroot/lvol9" (/bto).

An error may occur if the server being restored can not NFS mount its ignite image. If this is the case the following error will occur. The ignite image for the server being restored must be properly exported in /etc/exports on the Ignite Server. This is done in the create_net_ignite script when the ignite system image is created.
x x x x x x ./etc/hosts, 486 bytes, 1 tape blocks ./etc/services, 10908 bytes, 22 tape blocks ./etc/inetsvcs.conf, 15 bytes, 1 tape blocks ./etc/nsswitch.conf, 382 bytes, 1 tape blocks ./configure3, 454656 bytes, 888 tape blocks ./monitor_bpr, 24576 bytes, 48 tape blocks * Download_mini-system: Complete * Loading_software: Begin * Installing boot area on disk. * Enabling swap areas. * Backing up LVM configuration for "vgbroot".

IJSM100Q Page 22 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


* Processing the archive source (Recovery Archive). Permission denied NOTE: Retrying: "/sbin/fs/nfs/mount -oro 88.1.23.69:/ignite/bn/m2/brmrg01p /tmp/ign_configure/archive_nfs" Permission denied NOTE: NFS mount (/sbin/fs/nfs/mount -oro 88.1.23.69:/ignite/bn/m2/brmrg01p /tmp/ign_configure/archive_nfs) failed, see messages above. ERROR: Command "/sbin/fs/nfs/mount -oro 88.1.23.69:/ignite/bn/m2/brmrg01p /tmp/ign_configure/archive_nfs" failed. Ensure that "/ignite/bn/m2/brmrg01p" is properly exported on 88.1.23.69.

If no errors occur, the progress of the restore will be indicated by the sample text:
* Processed 10% of archive

After 100% of the restore has been processed the system will shutdown and reboot. See the sample output:
x ./etc/hosts, 486 bytes, 1 tape blocks x ./etc/services, 10908 bytes, 22 tape blocks x ./etc/inetsvcs.conf, 15 bytes, 1 tape blocks x ./etc/nsswitch.conf, 382 bytes, 1 tape blocks x ./configure3, 454656 bytes, 888 tape blocks x ./monitor_bpr, 24576 bytes, 48 tape blocks * Download_mini-system: Complete * Loading_software: Begin * Installing boot area on disk. * Enabling swap areas. * Backing up LVM configuration for "vgbroot". * Processing the archive source (Recovery Archive). * Fri Aug 11 12:55:16 EDT 2006: Starting archive load of the source (Recovery Archive). * Processed 10% of archive * Processed 20% of archive * Processed 30% of archive * Processed 40% of archive * Processed 50% of archive * Processed 60% of archive * Processed 70% of archive * Processed 80% of archive * Processed 90% of archive * Completed 100% of archive * Fri Aug 11 13:12:28 EDT 2006: Completed archive load of the source (Recovery Archive). * Executing user specified script: "/opt/ignite/data/scripts/os_arch_post_l". * Running in recovery mode (os_arch_post_l). * Running the ioinit command ("/sbin/ioinit -c") * Creating device files via the insf command. insf: Installing special files for sdisk instance 0 address 10/0.6.0 insf: Installing special files for sdisk instance 1 address 10/8.6.0 insf: Installing special files for sdisk instance 2 address 10/12/5.2.0 IJSM100Q Page 23 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: insf: NOTE: Installing special files for stape instance 0 address 10/12/5.0.0 Installing special files for btlan instance 0 address 8/0/1/0 Installing special files for btlan instance 1 address 8/0/2/0 Installing special files for btlan instance 2 address 8/4/1/0 Installing special files for btlan instance 3 address 8/4/2/0 Installing special files for fddi instance 6 address 10/4/4 Installing special files for btlan1 instance 7 address 10/4/8 Installing special files for lan2 instance 8 address 10/12/6 Installing special files for pseudo driver dlpi Installing special files for ps2 instance 0 address 10/12/7 Installing special files for pseudo driver kepd Installing special files for pseudo driver framebuf Installing special files for pseudo driver sad Will not attempt to create any transition links after archive extraction. The /opt/upgrade/bin/tlinstall is not present or is not executable. * Constructing the bootconf file. * Setting primary boot path to "10/8.6.0". * Executing: "/var/adm/sw/products/OS-Core/CORE-KRN/iux_postload". * Executing: "/var/adm/sw/products/OS-Core/CORE-SHLIBS/iux_postload". * No actions taken - running in recovery mode. * Executing: "/var/adm/sw/products/PHSS_25983/pfiles/iux_postload". NOTE: Will not attempt to create any transition links after software load. The /opt/upgrade/bin/tlinstall is not present or is not executable. * Loading_software: Complete * Build_Kernel: Begin NOTE: Since the /stand/vmunix kernel is already in place, the kernel will not be re-built. Note that no mod_kernel directives will be processed. * Build_Kernel: Complete * Boot_From_Client_Disk: Begin * Rebooting machine as expected. NOTE: Rebooting system. sync'ing disks (0 buffers to flush): 0 buffers not flushed 0 buffers still dirty Closing open logical volumes... Done

Step 23: The restored system will reboot and if the restore succeeded will display an OK banner. See the sample output:
Trying Primary Boot Path -----------------------Booting... Boot IO Dependent Code (IODC) revision 152 HARD Booted. ISL Revision A.00.43 Apr 12, 2000 ISL booting hpux Boot : disc(10/8.6.0;0)/stand/vmunix 11509760 + 2637824 + 3313080 start 0x1fe2e8
IJSM100Q Page 24 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


* Bringing up Network (lan0) * running: lanadmin -X 100FD 0 * NFS mounting clients directory. * Boot_From_Client_Disk: Complete * Run_SD_Configure_Scripts: Begin * Run_SD_Configure_Scripts: Complete * Run_Postconfigure_Scripts: Begin * Run_Postconfigure_Scripts: Complete ======= 08/11/06 13:31:11 EDT Installation complete: Successful ### # ##### ##### # # ##### #### # # ## # # # # ## ## # # # # # # ## ##### # # # ## # # # # # # # # # ##### # # ##### # ### # # # # # # # # # # # # # # # # # ##### # # # # # # #### ### ##### ####### # # # # # # # # # # ####### # # # # # # ### # # # # # #

##### # # # # ##### # #

NOTE: Rebooting system. sync'ing disks (0 buffers to flush): 0 buffers not flushed 0 buffers still dirty Closing open logical volumes... Done

Step 24: The system will reboot again. Remember: Not all system root files were included when the ignite image was created. Only those system files in the ignite image can be restored; so there may be some failures at boot time which will be resolved in a later step. See the sample output:
Trying Primary Boot Path IJSM100Q Page 25 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


-----------------------Booting... Boot IO Dependent Code (IODC) revision 152 HARD Booted. ISL Revision A.00.43 Apr 12, 2000 ISL booting hpux Boot : disc(10/8.6.0;0)/stand/vmunix 11509760 + 2637824 + 3313080 start 0x1fe2e8 HP-UX Start-up in progress __________________________ Configure system crash dumps ....................................................................... OK Mount file systems ....................................................................... OK Start RPC daemon if needed ...................................................................... FAIL * Starting OpenSSH ...................................................................... FAIL * The system is ready. Console Login:

Step 25: Verify that one can login with a non-root account. Step 26: If ssh failed to start on the server that was just restored, enter the following to start it: ln -s /opt/openssh2 /opt/ssh

If dds package openssh_00026 or greater is on this server enter: ./sbin/rc2.d/SA002sshd start If an older version of dds ssh is on this system and the following file already exists (for example /bto was not on vg00), enter: ./bto/sys/platform/localinit.d/S89sshd start Step 27: Note: Some systems have /bto on the root system disk. If /bto is on the

system disk, the bdf command will show that /bto file system has not been restored:
Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol3 204800 56832 138735 29% /
IJSM100Q Page 26 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


/dev/vg00/lvol1 199381 /dev/vg00/lvol8 1843200 /dev/vg00/lvol7 1331200 /dev/vg00/lvol4 102400 /dev/vg00/lvol6 819200 /dev/vg00/lvol5 102400 /dev/vg00/lvol9 2048000 68178 111264 38% /stand 163280 1574948 9% /var 994019 316120 76% /usr 1201 94945 1% /tmp 36047 734232 5% /opt 1133 94945 1% /home 2822 1917359 0% /bto

Step 28: Note: If any of the standard vg00 file systems are not located on vg00, then that file system and all others on the other vg will be newfsd or zeroed out. For example, if /opt is not located on the root disk, then other file systems that are on the same vg as /opt will be zeroed out. Only files /opt /prngd and /opt/openssh2 files will be restored into /opt initially. So in addition to the remainder of /opt, the other file systems on the same vg as /opt will also need to be restored. Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol3 143360 47978 89431 35% / /dev/vg00/lvol1 95701 37984 48146 44% /stand /dev/vg00/lvol8 1024000 126228 841945 13% /var /dev/vg00/lvol7 1069056 821160 232458 78% /usr /dev/vg00/lvol4 204800 1782 190389 1% /tmp /dev/vg02/opt 4194304 47273 3887846 1% /opt /dev/vg00/lvol5 204800 1157 190923 1% /home /dev/vg02/lvol23 2662400 1759 2494358 0% /bto/sys/oracle /dev/vg02/lvol21 4096000 2104 3838035 0% /3pt Step 29: Create a REM case for EBR to restore the remainder of the Root File System. Request that EBR restore vg00 with no overwrite this will keep the current files and add only those files that are missing. Request that EBR restore /var/adm/sw/save since it was excluded from the ignite image. Request that EBR restore the following files with overwrite since the ignite image versions are probably out of date: /etc/passwd /etc/shadow /etc/hosts Step 30: After EBR has restored the files:
IJSM100Q Page 27 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


If Etac is on this server: If the /bto/sys/etac directory had to be restored, try to start etac by entering: . /sbin/rc2.d/S99etac start If etac fails to start, its dds package will need to be re-installed.

After Etac has started successfully: Note: It has probably been longer than 30 days since the root password that resides on the ignite image was changed via Etac: Then according to Etac, the root password has expired. To verify, one can attempt to login as root and get an error message such as: Connection closed by remote host To verify, one can login with an account with root privileges and then sesu to root and enter: selang eTrust> su root User mode : Admin, Auditor, Operator, Ignore-Holiday Audit mode : Login-Success, Failure, Login-Failure Gracelogins :# Pwd last change : 27-Jun-2006 08:32 Password interval : 30 Full name : root

Note: If the number of grace logins is not yet down to 0:.


Log in as root and change the root password locally on the restored server or change the root password for the entire Etac group. Unless the root password is changed via Etac, root cron jobs will not run. To change the root password locally, enter: sepass l
IJSM100Q Page 28 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


Note: If the number of grace logins is down to 0:
MTS will need to be contacted to assist in re-setting the root password. Unless the root password is changed via Etac, root cron jobs will not run.

IJSM100Q Page 29 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.

HP-UX Network Ignite Recovery


APPENDIX A Sample file of BRMAR01P:
/opt/ignite/share/bin/cfg_for_boot_helper_tape # instl_adm defaults: # NOTE: Manual additions between the lines containing "instl_adm defaults" # and "end instl_adm defaults" will not be preserved. # end instl_adm defaults. server="55.10.1.158" netmask[]="255.255.240.0" route_gateway[0]="55.10.0.200" route_destination[0]="default" ( lan[ ].driver ~ "btlan" ) { _hp_lanadmin_args="-X 100FD" } else { ( lan[].driver == "gelan" | lan[].driver == "igelan" ) { _hp_lanadmin_args="-X 1000FD" } }

II.

AMENDMENT HISTORY
Version 1 2 3 4 5 Date 3/03/2006 07/15/2006 09/28/2006 09/29/2006 09/20/2007 Revision Description Initial Issuance Procedure step updates Republished per John Damken. Updated footer field. MTS name change

IJSM100Q Page 30 of 30 Version 5 Parent Document: IPSM1000 Document Owner: Alan Montgomery PRIVATE/PROPRIETARY/SECURE Contains private and/or proprietary information. May not be used or disclosed outside the BellSouth companies except pursuant to a written agreement. Must be securely stored when not in use.