Solaris

Hi Guys,
I am a newbie in Solaris.
I have to setup jumpstart server for one of my company's clients.
I have gone through a lot of documentations but I am faced with a rather peculiar problem.
All the documentations have single server acting as boot server, config server and install server.
However the client network has multiple subnets.
So having a single boot server is not feasible.
Also I do not want same system to act as config and install server.
So this is the basic scenario.

CS = config server
IS=Install server
BS1=Boot Server 1
BS2=Boot Server 2

/export/install------This is the directory which will hold the OS image (where should be this dir ...on Config server, Install server or Boot server)
/export/config-------This will hold the sysidcfg, rules and profile file (where should be this dir ...on Config server, Install server or Boot server)

/tftpboot -----file? (Where should be this dir ...,on Config server, Install server or Boot server)

/etc/ethers ---containing the Ethernet this should be on boot server I guess

/etc/inet/hosts ---------- containing the IP this should be on boot server I guess (Where should be this file ........on Config server, Install server or Boot server)

Also where should I run add-install-client (on Config server, Install server or Boot server)

I know i need to share install and config dirs, Can they be in any subnet? ( I can ping across subnets)

Also please suggest any thing else needs to be done?

[QUOTE=nitinkgoud]

Boot server, but don't woory about that, it'll be sorted out automatically when you add a client.

Yor guess is correct, also put them on the config server.

Boot server

(on Config server, Install server or Boot server)
Yes, provided you can route between networks.

Hi Reborg,
Thanks for the reply.
I will do the folowing
1)I will place /etc/ethers and /etc/inet/hosts on both boot and config server.
2)I will run add-install-client on bootserver

Thanks again

What you can do is have boot server in different lans, but have one config and install server. When the client boots up, it needs a boot server in the same Lan segment, after it has the ip, netmask, dns etc, it can then find it's way to install server. I think you need to put /etc/ethers on config server only. The boot server really doesn't care, all it does is send the IP info and boot image to clients.

-Nitin