Configure Booting IP Addresses Dialog B

[Grayh]

While doing a Ignite ux...


which IP's should I enter at the Configure Booting IP Addresses Dialog Box...

Is it the IP's of the servers on which I have to install the OS...

[Grayh]

Sorry it's actually the DHCP Addresses Dialog Box....

I have static IP's avaliable for all of my remaining servers... what should I enter there...

Also should I need to add anything in /etc/opt/ignite/instl_boottab

[Steven E. Protter]

Shalom,

With ignite you have several choices:
1) DHCP all the time, a bad idea for servers because other systems need to know where they are and what their ip address is.
2) Hard coded within the ignite configuration.
3) Configure as part of the install.

Which you choose depends on your needs.

SEP

[Oviwan]

hi

check this:
PA-RISC Client
http://docs.hp.com/en/5992-3336/ch03s01.html

Itanium Client:
http://docs.hp.com/en/5992-3336/ch03s02.html

HTH

[Grayh]

I have issued the below command

/opt/ignite/bin/ignite

and started from there....

I am unable to understanbd the contents of /etc/bootptab

What should I enter there

# Format:
# nodename:tag=value:tag=value: ... :tag=value
#
# first field -- nodename (hostname) of terminal followed by colon
# (should be full domain name)
#
# Blank lines and lines beginning with '#' are ignored.
# Make sure you include a colon and a backslash to continue a line.
# Don't put any spaces in the tag=value string.
# The ht tag MUST precede the ha tag.
#
# The options listed below are commonly used for HP X Window terminals,
# HPUX NFS Diskless, BOOTP Fixed Address Devices. They are specified as
# tag=value and delimited by colons. For a list of all possible options,
# see the bootpd.1m man page.
#
# ba -- broadcast bootp reply for testing with bootpquery
# bf -- bootfile (for tftp download)
# bp -- bootp server IP addresses to relay the bootp requests
# bs -- bootfile size in 512-octet blocks
# ci -- client ID (for dhcp clients only)
# cs -- cookie server IP address
# dn -- domain name
# ds -- domain name server IP address
# ef -- extensions file, containing more options for the client
# gw -- gateway IP address (must have sm tag defined also)
# ha -- hardware address (link level address) (hex)
# hd -- home directory for bootfile (chrooted to tftp home directory)
# hn -- send nodename (boolean flag, no "=value" needed)
# hm -- hardware mask (hex) (must be preceded the ht tag)
# hp -- maximum hops value (cannot exceed 16)
# ht -- hardware type (ether) (must precede the ha and hm tag)
# im -- impress server IP address
# ip -- (client) IP address
# lg -- (MIT-LCS UDP) log server IP address
# lp -- LPR (line printer) server IP address
# md -- file to dump core image to in the event of a crash
# na -- NETBIOS name server IP address
# nb -- NETBIOS datagram distribution server IP address
# nc -- NETBIOS over TCP/IP node type (B-node, P-node, M-node, or H-node)
# nd -- NETBIOS over TCP/IP scope
# ns -- name server (IEN 116) IP address
# nt -- network time protocol server IP address
# rl -- resource location server
# rp -- path name to client's root disk
# sm -- network subnet mask
# ss -- swap server IP address
# tc -- template for common defaults (should be the first option listed)
# th -- threshold value in seconds
# to -- time offset in seconds from Coordinated Universal Time (UTC)
# tr -- renewal (T1) time value (a percentage of the lease time)
# ts -- time server IP address
# tv -- rebinding (T2) time value (a percentage of the lease time)
# vm -- vendor magic cookie selector (should be rfc1048)
# xd -- X window system display manager IP address
# xf -- X window system font server IP address
# yd -- NIS domain name
# ys -- NIS server IP address
# Tn -- generic option tag n
# T144 remote config file name (file name must be enclosed in "")
# Vn -- vendor specific information for vendor option tag of n
#
#----------------------------------------------------------------------------
# First example: simple network with no domains, no gateway, no subnets
#
# The first entry is the template for options common to all the
# X terminals.
#
#global.defaults:\
# bf=C2300B:\
# hd=/usr/lib/X11/700X/bin:\
# hn:\
# ht=ether:\
# vm=rfc1048:\
# T144="C2300B.cfg"
#
# Now the actual entries for the individual X terminals are listed.
#
#xterm1:\
# tc=global.defaults:\
# ha=08000903212F:\
# ip=190.40.101.22
#
#xterm2:\
# tc=global.defaults:\
# ha=0800090324AC:\
# ip=190.40.101.35
#
#----------------------------------------------------------------------------
# Second example: network with domains, subnets, and gateways
#
# The first entry is the template for options common to all the
# X terminals.
#
#----------------------------------------------------------------------------
#global.defaults:\
# bf=C2300B:\
# ds=15.2.112.119:\
# gw=15.8.19.100:\
# hd=/usr/lib/X11/700X/bin:\
# hn:\
# ht=ether:\
# sm=255.255.248.0:\
# vm=rfc1048:\
# T144="site.cfg"
#
# Now the actual entries for the individual X terminals are listed.
#
#xterm1.div.hp.com:\
# tc=global.defaults:\
# ha=08000903212F:\
# ip=15.8.19.22
#
# Note that template options can be individually overridden. Here we specify
# a gateway and a remote config file different than the template.
#
#xterm2.div.hp.com:\
# tc=global.defaults:\
# gw=15.8.19.3:\
# ha=0800090324AC:\
# ip=15.8.19.35:\
# T144="xterm2.cfg"
#
#----------------------------------------------------------------------------
#
# Third example: NFS diskless client entry:
#
# client1:\
# hn:\
# vm=rfc1048:\
# ht=ether:\
# ha=08000919BB78:\
# ip=15.1.55.234:\
# bf=/export/tftpboot/client1/stand/uxbootlf
#
#----------------------------------------------------------------------------
#
# Fourth example: bootp relay entries:
#
# Common relay entry.
#
# relay-default:\
# ht=ethernet:\
# bp=15.4.3.136 15.13.6.192:\
# th=2:\
# hp=1
#
# Relay entry for node2
#
# node2:\
# tc=relay-default:\
# ha=08000902CA00
#
# Group relay entry
#
# group-machines:\
# tc=relay-default:\
# ha=080009000000:\
# hm=080009000000
#
# Turn the relay off (block the relay) for the following machines.
#
# blocked-machines:\
# ht=ethernet:\
# ha=07000A000000:\
# hm=07000A000000
#
# Relay definition for all other machines.
#
# all:\
# tc=relay-default:\
# ha=000000000000:\
# hm=000000000000
#----------------------------------------------------------------------------

test:\
bf=C2300B:\
hd=/usr/lib/X11/700X/bin:\
hn:\
ht=ether:\
vm=rfc1048:\

[Oviwan · Accepted solution]

my content of bootptab:
ignite-defaults:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48:\
sm=:\
gw=:\
ds=

change sm,gw and ds for your environment.

now you can boot any client with the nbp.efi bootfile and connect to your ignite server.

HTH

[Grayh]

thanks Oviwan...

I have issued the followiong command to create a depot for 11i V3

/opt/ignite/bin/make_depots -s /dvdrom \-d /var/opt/ignite/depots/Rel_B.11.31/core_media

And it is running since a long time may be 5 minutes or more... Could u tell me generally wat time it takes to create a depot

[Grayh]

Also where will I get the below information on my server:-

sm=:\
ds=

Also Do I have to add all of the other 6 servers IP address here..

If not here where should I add then to cold install from this ignite server

[Oviwan]

I have never created a depot, just a clone of an existing image.

I think you will find your answers here:
http://docs.hp.com/en/5992-3336/index.html

Gateway:
grep ROUTE_GATEWAY /etc/rc.config.d/netconf

DNS
cat /etc/resolv.conf

[Grayh]

How to find the h/w address of the server to be put in the following entry

ignite-defaults:\
ht=ethernet:\
hn:\
dn=domain_name.com:\
gw=10.1.20.1:\
sm=255.255.255.0:\
vm=rfc1048:\
bf=/opt/ignite/boot/nbp.efi:
iuxclient1:\
tc=ignite-defaults:\
ha=0018FE2F01B3:\-----------------> ???
ip=10.1.20.14:

[Oviwan]

you can get the mac address with:
lanscan

[Grayh]

ignite-defaults:\

ht=ethernet:\

hn:\

dn=domain_name.com:\

gw=10.1.1.1:\

sm=255.0.0.0:\

ds=10.1.1.2 10.1.1.3:\

vm=rfc1048:\

bf=/opt/ignite/boot/nbp.efi:





iuxclient1:\ ----------à

tc=ignite-defaults:\

ha=0018FE2F01B3:\

ip=10.1.2.87: -----------------à Is this the IP of the Ignite server or the IP of the Client on which I will be Installing the OS

[Gokul Chandola]

Yes you are right.

Regards,
Gokul Chandola

[V. Nyga]

Hi,



see the desciption you've posted yourself:
# ip -- (client) IP address


Volkmar

[Grayh]

thank u