In order to ensure the ability to service the UE10000 domains, we need
to ensure that we are able to "boot net" each domain, in the same way
that we would "boot cdrom" any other Sun server or workstation. There
are cases where this is not possible because there are other machines
on the customer's network which interfere with the Jumpstart[TM] process,
and in other cases we may need to use "boot net" on another network in
order to prove a fault with the customer's network equipment.

Any solution must provide the following 3 features:
1) "boot net - install" must install the correct nodename on the domain.
2) "add_install_client" must put the correct hostname in /etc/bootparams
3) "netcon_server" must be able to resolve the IP address back to the
correct domainname.

For this procedure to work correctly, you must ensure that the name
service switch points to files first.
e.g.
hosts:      files nisplus dns

To ensure that the machine gets the correct nodename when
"boot net - install" is run you must ensure that the nodename appears
before any aliasname on the line in /etc/hosts, and to ensure that the
correct interface is defined by "add_install_client" you must ensure that
this interface appears before all others in /etc/hosts.
e.g.
129.156.3.168	p10k-a p10k-a-jumpstart
129.156.183.168	p10k-a p10k-a-public

NOTE: If the nodename of the domain is not the same as the domainname of
the domain, you must edit the SSP's /etc/hosts file to ensure that the
domainname is the first entry on the line for the interface (as in the
example above where "p10k-a" appears before "p10k-a-jumpstart") after the
domain is installed. The reason for this is that the netcon/cvcd must
receive the domainname when it does a reverse lookup from the IP address.

To ensure that the servername specified in /etc/bootparams can be accessed
across this hub, you must specify the network specific hostname first on
the line in /etc/hosts, so that "add_install_client" uses this name in
the /etc/bootparams file.
e.g.
129.156.183.173	s4m-sspa        loghost
129.156.1.12	s4m-sspa-le0
129.156.2.12	s4m-sspa-qfe1
129.156.3.12	s4m-sspa-qfe2 s4m-sspa-jumpstart s4m-sspa


Once the domain is installed, you need to edit /etc/nsswitch.conf such that
files is first otherwise cvcd will consume lots of CPU (see SRDB 17782).
e.g.
hosts:      files nisplus dns

Then add an entry for the extra network into the /etc/hosts file, rename
the existing /etc/hostname.<net> file to be the public network one, and
add a /etc/hostname.<net> file for the extra network.
e.g.
129.156.183.168 p10k-a  loghost
129.156.3.168   p10k-a p10k-a-jumpstart
mv /etc/hostname.qfe1 /etc/hostname.qfe0
echo p10k-a-jumpstart >> /etc/hostname.qfe1

When "ssp-config" asks for the name and IP address of the SSP, reply with
the hostname specific to the extra network.
e.g.
Please enter the hostname of the SSP for p10k-a [p10k-a-ssp]: s4m-sspa-qfe2
I could not automatically determine the IP address of s4m-sspa-qfe2.
Please enter the IP address of s4m-sspa-qfe2: 129.156.3.12