#mkdir –p /etc/opt/ignite

#mkdir –p /var/opt/ignite

#mkdir –p /opt/ignite/boot

#chown bin:bin /var/opt/ignite

#chmod 555 /var/opt/ignite

#chown bin:bin /etc/opt/ignite

#chmod 755 /etc/opt/ignite

#chown bin:bin /opt/ignite/boot

#chmod 555 /opt/ignite/boot

4.Add the -soption to /usr/lbin/tftpd

Add the -soption to the /usr/lbin/tftpd file on all cluster nodes that can run the Serviceguard package containing Ignite-UX. Each cluster node that can run Ignite-UX must have an entry in /etc/inetd.conf that is similar to the following:

tftp dgram udp wait root /usr/lbin/tftpd tftpd -s \ /opt/ignite\

/var/opt/ignite

For more information about the tftpd -soption, see tftpd (1m).

The directories /opt/ignite and /var/opt/ignite are also required for Ignite-UX to work correctly. If ignite-UX is installed on only one cluster node, these directory entries will not be present and must be manually added.

The /etc/inetd.conf file must be reconfigured for the changes to take effect. Run the "inetd -c"command to reconfigure the /etc/inetd.conf file.

If the -soption is not present in the /usr/lbin/tftpd file, the kernel routing table will determine the IP address used to reply to the client. The booting client might not accept the reply, because this might not be the expected IP address. This might result in intermittent network boot errors. On HP Integrity systems, errors such as PXE-E18 might be displayed, whereas on HP9000 systems, it might be difficult to diagnose the errors. In cases where the -s option is not added to the /usr/lbin/tftpd file, the possibility of the error occurring depends on package movements and the order in which packages are started in the cluster node on which the Ignite-UX package is running.

5.Mount /var/opt/ignite and create required directories on the first cluster node

Create /var/opt/ignite/data, /var/opt/ignite/clients, and /var/opt/ignite/recovery/archives on the first cluster node, then set permissions and ownership. These directories are exported when the service runs, so they must be there prior to installing Ignite.

#mount /dev/vg01/lvol2 /var/opt/ignite

#mkdir /var/opt/ignite/data

#mkdir /var/opt/ignite/clients

#mkdir –p /var/opt/ignite/recovery/archives

#chown bin:bin /var/opt/ignite/clients

7