Ignite-UX on Itanium

[LucianoCarvalho]

Hi guys, I have one HP-UX 11.00 configured as ignite/ux server and I'd like to configure a RX2600 server with 11.22 as client. Is it possible?
If it is, what is the steps to boot the RX2600 through network to restore the make-recovery recorded on the hp-ux 11.00 (ignite-ux server)?
Thanks in advance

[John Payne_2]

It is possible, with the latest version of ignite.

Release notes:

2.1 Version B.4.1 (11/2002)
===========================

The B.4.1 release of Ignite-UX supports the HP-UX 11i (11.11) PA release and
the 11i Version 1.6 (11.22) IPF release. It can be installed on either PA or
IPF Ignite-UX servers. Changes in this release include:

- Full support of PA and IPF installs from either a PA or an IPF server.

- Fixes for the following defect Change Requests:
* JAGae28397 - Provide option for pax to use cpio with make_*recovery
Creation of an archive (make_tape_recovery) or tape (make_tape_recovery)
can now be done using either tar or cpio format. To complete this fix,
a new pax patch (either 11.00 or 11.11) must be installed on the system.
If these patches are not on the system, make_*_recovery will fail.
The B.4.1 release of Ignite-UX supports the HP-UX 11i (11.11) PA release and
the 11i Version 1.6 (11.22) IPF release. It can be installed on either PA or
IPF Ignite-UX servers. Changes in this release include:

- Full support of PA and IPF installs from either a PA or an IPF server.

- Fixes for the following defect Change Requests:
* JAGae28397 - Provide option for pax to use cpio with make_*recovery
Creation of an archive (make_tape_recovery) or tape (make_tape_recovery)
can now be done using either tar or cpio format. To complete this fix,
a new pax patch (either 11.00 or 11.11) must be installed on the system.
If these patches are not on the system, make_*_recovery will fail.
The two patches are:
PHCO_26422 s700_800 11.11 pax(1) cumulative patch
PHCO_25418 s700_800 11.00 pax(1) cumulative patch

* JAGae00621 - Update Ignite-UX SYSCMDS file with latest PAX
This was done in a previous release and verified when JAGae28397 was
fixed.

* JAGae38594 - make_config error on permissions if umask of 027
This was problem when a user had a restrictive umask setting which
would turn off other read permission such that the instl_adm check
would produce a warning about non-world-readable file. Read
permission is now guaranteed for owner, group and other on any
config file produced by make_config.

* JAGad97738 - Using the "B" version of Ignite-UX to install or
recovery systems running 10.20, or 11.00 was causing the
resulting system to dynamically assign driver major number values
to drivers that are statically reserved for other drivers. In
cases where both drivers are actually used, this could cause
system hangs, or other unexpected behavior when accessing the
devices. This version of Ignite-UX ensures that the driver
major numbers assigned are appropriate for the version of HP-UX
being installed.

- Support is now provided for assigning root passwords on clients with
a shadow password file (/etc/shadow).

- For IPF clients, itemap will now be invoked to set the keyboard
mapping.


John

[Pete Randall]

The last I heard, and despite what the release notes say, it doesn't work on Itanium. See:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe336b941255cd71190080090279cd0f9,00.html


Pete

[John Payne_2]

IPF Server Setup

The HP-UX 11i Version 1.6 based release of Ignite-UX now supports installation on IPF systems. Network installation from an IPF system requires unique network installation steps that are provided below:

Step 1. At a minimum, the Ignite-IA-11-22 bundle should be loaded on your system. If it is not, load with swinstall.
Step 2. Add your client's entries to /etc/bootptab on the server. See the bootpd(1M) manpage for more details. The following example is provided in /etc/bootptab :
ignite-defaults: ht=ethernet: hn: bf=/opt/ignite/boot/nbp.efi: bs=48
System-IPF: tc=ignite-defaults: ha=00d009000000: ip=190.40.101.22: sm=255.255.248.0: gw=190.1.48.1: ds=190.1.48.11
Duplicate (cut and paste) the System-IPF entries and change in the following ways:
Change System-IPF to reflect the client system's hostname.

Change the ha and ip fields for that client.

Change the sm, gw, and ds fields to reflect your network.
You can modify the system name, hardware address, IP address and other information for the client.
Ignite defaults section

All entries in the ignite-defaults section can be used without modification.

IPF system section

The following is a list of fields you may need to change per system and which fields are unique to your network:

The ha field requires setting to the hardware address ( Mac or LLA address of the client system). This address can be found from the firmware's user interface when adding a boot option. See IPF Client Network Boot Option Set Up. If the system is up and running, the lanscan command can also be used to find this value.


The ip field is the IP address that has been reserved for the client you are about to install and must be an IP address that is valid for your network.


The sm field is the network subnet mask and is probably the same for all systems on your network.


The gw field is the network gateway. It is optional for booting purposes, but useful to provide the system defaults.


The ds field is the domain name server (DNS) and is also optional for booting purposes, but useful to provide as a default.

Step 3. Enable bootp services in the /etc/inetd.conf file by uncommenting the bootps entry.
Step 4. Reconfigure the Internet daemon by entering:

/usr/sbin/inetd -c

[John Payne_2]

It will work, as long as you do a make_sys_image or a make_net_recovery. (Avoid the tapes...)

John

[Tommy_25]

In PA systems we do not need to add additional informations such as IP, HA in /etc/bootptab,
my concern is, is there a method to act same as PA systems to avoid these manual works?

Thanks.

[Steven E. Protter]

I have heard mixed reviews from actual users.

The problem is building a make_sys_image that will actual load on the Itanium server. To build something useful on the Itanium you might need to build it on an Itanium.

SEP