This is a brief Description of loading HP-UX from Ignite Server for PA Systems.
Please see below for Itanium Servers.
1. Power on the Server if not already done. Either switch it on if not then from console screen press CTRL+B (except K580 servers, where you
have to manually switch off and on)
2. Just hit enter for user name and password when prompted if not any or provide user ID & Passowrd. (Except for RP4440, RP7410 & higher
machines including Superdome, there you have to type Admin as default user name & password or user & pwd )
3. type RS or rs and hit enter and follow the instruction. For 7410 & higher including Superdome, type CM for command menu and then type
rs and hit enter. It will ask which partition you want to reset. Choose and follow.
4. After machine rebooted it will come to “BCH” (boot control handler) menu and wait for 10 seconds. Hit enter or any key within 10 seconds to
stop it.
5. Then type “ bo lan.xxx.xxx.xx.x install” for generic load or “sea” to search for the tape/dlt/lto drive in case you need to load OE/OS from
make_recovery tape. (Replace xxx.xxx.xx.x for actual IP for Ignite Server or you can use "bo lan install" )
6. Type “n” and hit enter when asked “Interact with IPL”
7. The tape drive will show as sequencial media. Select the appropriate one if you know or pick one until you get the proper one.
8. If you are loading from Ignite tape you might not have to do anything if it is same kind of machine. Otherwise you have to hit enter couple of
times. And it will continue. In case of generic load select the appropriate OS version and hit enter (for RP4440, RP7410 and higher machine
including Superdome you can’t load HPUX 11.0, Only 11i works there). Then login to ignite server from another screen to find out the IP
which is assigned for that server. To do that simply cat /etc/hosts and grep for that name.
9. Once you get the IP address. Come back to the console of the server you are loading and select “install HP-UX” and hit enter
10. Select OK for guided installation.
11. Select the first card lan0 or if you have the hardware address of the network card used use that one.
12. Then press CTRL+C or wait for 30 seconds to cancel DHCP
13. Then type in the informations like host name and the IP you got from Ignite Server. Probably after typing the hostname and IP address if
you press tab all informations likely to be filled automatically. If not please follow next.
14. When prompted type in the proper informations like server name & IP address. If Ignite Server and if any boot helper is there and setup
properly then you might not need to put Ignite Server IP. Otherwise put the IP/Subnet and gateway information, if any you can use the
same IP as gateway which you used for this Server.
15. Check the configuration if it is the same you want to load then “tab” to “OK” button and hit enter, Then press “n” for next or if not then hit
enter and it will show you the list. Choose the appropriate one and “tab” to next. Check the environment. It should be 64 bit by default
except for K-class servers, where you need to select 64 bit manually from the menu.
16. Then press next for the root disk. Press next for root swap. Next for filesystem, unless you have specific information for file systems
or change the sizes you need for each file systems.
17. Then tab to next for the available disks. If the screen looks messy please hit “CTRL+L” any time to refresh the screen. This is standard for
all unix platforms.
18. Choose next for language (default is English).
19. Next for next screen. Then again “n” for no”. Then “n” for next. And “f” for finish. And you are done.
Ignite load procedure for Itanium Servers
You need to reboot the server to install OE. Reboot the server or if it is already at hung state then press Ctrl+B from console then hit enter to get into the GSP. From GSP main menu type cm and hit enter then type rs and enter then y and enter. then type ma and hit enter. then co and hit enter. then select the partition and hit enter. it will take you to the console. When press any key in 10 seconds message comes press any arrow key or any key except enter or spacebar.
Then press down arrow key to EFI Shell and hit enter. From EFI Shell type lanboot select -dn Ignite ( I is capital, name of our Ignite Server is Ignite)
It will ask for the proper lan Card. Type the Lan card no. like 01 or 02 and hit enter. It will boot from the Ignite Server. Then follow the procedure of loading HPUX.
If no profile is there you can create one of your own. ( sip= Ignite Server IP, cip = client server ip, gip=gateway ip, m=subnet mask, b= bootfile)"
dbprofile -dn Ignite -sip 192.168.192.6 -cip 192.168.192.32 -gip 192.168.192.32 -m 255.255.255.0 -b "/opt/ignite/boot/nbp.efi"
DONOT FORGET THE QUOTES
You can do either the way I mentioned above or below way but I prefer PXE boot. Remember if you have Linux Kickstart Servers with PXE enable or Solaris Jumpstart Server with PXE boot enabled then you might have trouble with ignite/kickstart and jumpstart. I have seen RISC Servers trying to boot from Ignite Server.
You need the entries for PXE boot of Itanium Server in /etc/dhcptab file
dhcp_device_group:\
re:\
ncid:\
class-id="PXEClient:Arch:00002:.*":\
lease-time=300:\
subnet-mask=255.255.255.0:\
addr-pool-start-address=192.168.192.246:\
addr-pool-last-address=192.168.192.254:\
bf=/opt/ignite/boot/nbp.efi
If you already configured /etc/bootptab with MAC address of Itanium Server Cards then you donot have to do this
Here is the example of /etc/bootptab entry from real production
rx7620a0:tc:IADEF:ip=192.168.192.42:ha=0017084C78D6
rx7620a1:tc:IADEF:ip=192.168.192.43:ha=0017084C88AC
Update the Ignite-UX of the Client M/C
/usr/sbin/swinstall -x mount_all_filesystems=false -s 192.168.192.51:/var/opt/ignite/depots/recovery_cmds "*"
You can recover Superdome make_tape_recovery to any N4000 Server without changing any hardware.
You can recover HP-UX 11iv2 make_tape_recovery from RP7410 Server to N4000 Server. I tried 11iv1 but it failed.The reason I found is missing SCSI driver.
If you want to recover a HP Server to different kind of HP Server you must make sure that the make_tape_recovery image has the driver for the scsi card of the target machine. Otherwise it will panic after successfully completed the tape load. I recovered RP3440 to RP4440, N4000 to SD32 Npar. Almost any HP-PA server to any HP-PA and any Itanium to any Itanium Server without any problem.
How to change the speed setting for the Ignite-UX net install
instl_adm -d (see the current settings)
instl_adm -d >/tmp/instl_adm.original (Save the original setting in case)
instl_adm -d >/tmp/instl_adm.out
vi /tmp/instal_adm.out ( And the setting will be like this)
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="192.168.192.51"
netmask[]="255.255.255.0"
# end instl_adm defaults.
is_net_info_temporary=false
dhcp_class_id="Ignite-UX_Ignite -G"
( lan[].driver == "btlan" | lan[].driver == "gelan" )
{
_hp_lanadmin_args="-X 100FD"
} else {
( lan[].driver == "igelan" )
{
_hp_lanadmin_args="-X auto_on"
}
}
env_vars += "INST_ALLOW_WARNING=5"
After chaging the setting you need to run
instl_adm -f /tmp/instl_adm.out
Now verify the settings
instl_adm -d to see the defaults again
and
instl_adm -T
( look at the man page of instl_adm it has lot more information and examples)
How to include entire root volume group and another volume group with make_tape_recovery
make_tape_recovery -A -s myserver -x inc_entire=vg00 -x inc_entire=vg01 -a /dev/rmt/0m
Problem : Unable to recover RP4440 server to another RP4440 Server. OS loaded from make_tape_recovery but after OS Installation completed it fails
Possible Solution : Check the SCSI Card you are using on both the Servers. Probably old RP4440 using Ultra 160 LVD card and the new RP4440 is using Ultra320 Card. One possible and tested solution is add one Ultra 160 LVD SCSI card in the new Server and connect the SCSI Internal Disks to it. Second tested Solution is same but you can use External DASD like DS2300 or DS2320. Third solution is install the Driver to the OS of old Server for the Ultra320 LVD SCSI Card or the Card used in the New Server and then run make_tape_recovery on old server.
Check http://docs.hp.com/en/5992-2900/5992-2900.pdf for complete guide of IgniteUX and MirrorDisk implementation.
Problem : linkloop works fine still unable to ping the router or any other server in the same network.
possible solution : This worked for three servers with same issue but don't have any explanation. run ifconfig lan0 down and ifconfig lan0 unplumb
and then run ifconfig lan0 plumb and ifconfig lan0 xxx.xxx.xxx.xx netmask xxx.xxx.xxx.xx. link workes means that the Servers can see each other i.e. connected to link level. (xxx=replace with ip address and subnet mask)