Jumpstart installation Issue for Solaris10 11/06
Hi, All
I have a questions about the Jumpstart
(1) System Configuration
Blade 150 ( Both jumpstart server and client )
Solaris10 11/06 DVD Media
Jumpstart server and client is under the same network prefix.
Name Service: NIS ( Both Jumpstart server and client is under the same NIS domain )
(2) Error messages during " boot net - install "
Timeout wiating for ARP/RARP packets
==> It seems server failed to ARP/RARP the client MAC/IP. I am not sure the reason. Pls
help to check my configuration sheet.
(3) Jumpstart configuration procedure.
- ./setup_install_server /jumpstart/install
- Copy the rules, profile and sysidcfg files to /jumpstart/config
- Add Jumpstart client IP/MAC to /etc/host and /etc/ethers, repectively.
- ./add_install_client -s Server:/jumpstart/install -c Server:/jumpstart/config -p
Server:/jumpstart/config CLIENT sun4u
Error: unknown client "CLIENT"
Then, I used DHCP client method to try to add install_client.
- #./add_install_client -d -e 0:3:ba:44:f4:37 -s Server:/jumpstart/install -c Server:/jumpstart -p Server:/jumpstart/config sun4u
cleaning up preexisting install client "CLIENT_MAC"
removing /tftpboot/inetboot.SUN4U.Solaris_10-1
removing /tftpboot
To disable CLIENT_MAC in the DHCP server,
making /tftpboot
copying boot file to /tftpboot/inetboot.SUN4U.Solaris_10-1
To enable 0100CLIENT_MAC in the DHCP server, ensure that
the following Sun vendor-specific options are defined
(SinstNM, SinstIP4, SinstPTH, SrootNM, SrootIP4,
SrootPTH, and optionally SbootURI, SjumpCF and SsysidCF),
and add a macro to the server named 01000CLIENT_MAC,
containing the following option values:
Install server (SinstNM) : Server
Install server IP (SinstIP4) : ip-addr-for-twnet
Install server path (SinstPTH) : /jumpstart/install
Root server name (SrootNM) : Server
Root server IP (SrootIP4) : ip-addr-for-twnet
Root server path (SrootPTH) : /jumpstart/install/Solaris_10/Tools/Boot
Boot file (BootFile) : 0100CLIENT_MAC
Profile location (SjumpsCF) : Server:/jumpstart
sysidcfg location (SsysidCF) : Server:/jumpstart/config
- I tried to boot through "boot net - install", but problem persistent.
(4) I google the error messages, Google told that the messages is due to MAC_IP unmatching.
- # arp -s CLIENT_IP CLIENT_MAC
- Because I am not netadmin, I can not add ethers map to NIS server. I wonder whether there is a way to enable jumpstart serverunder NIS domain.
(5)Because I am not the net admin, I can not make ethers. I login to the NIS server and I see that there is no /etc/ethers file on the NIS server. Then, I got the "Error: unknown "CLIENT" messages when I add the install client.
Q1. I modify the /etc/nsswitch.conf in my jumpstart server as follows.
ethers: nis files -> I think it will firstly contact NIS server then /etc/ethers in the jumpstart server for
client MAC.
But the ARP/RARP timout also persistent. I wonder why the jumpstart server can not find the CLIENT MAC from the /etc/ethers of itself.
Q2. Assuming I drop the jumpstart server out of the control of NIS server. And my jumpstart client is also under
the NIS domain. I wonder whether my jumpstart client can boot install from the jumpstart server even though the jumpstart server does not have NIS naming service.
UltraSoul is offline
[3563 byte] By [
staygreena] at [2007-11-26 12:41:37]
# 1
> (2) Error messages during " boot net - install "
>
> Timeout wiating for ARP/RARP packets
> ==> It seems server failed to ARP/RARP the client
> MAC/IP. I am not sure the reason. Pls
> help to check my configuration sheet.
That suggests that RARP requests are not being returned. Is the client in the servers /etc/ethers file? It is automatically added by using -e on add_install_client.
> (3) Jumpstart configuration procedure.
>
> - ./setup_install_server /jumpstart/install
> - Copy the rules, profile and sysidcfg files to
> /jumpstart/config
> - Add Jumpstart client IP/MAC to /etc/host and
> /etc/ethers, repectively.
> - ./add_install_client -s Server:/jumpstart/install
> -c Server:/jumpstart/config -p
> Server:/jumpstart/config CLIENT sun4u
> Error: unknown client "CLIENT"
CLIENT is resolved locally on the server. Can you issue 'ping CLIENT'? Do you get a ping attempt, or does it say "unknown host"? Perhaps your server is not using /etc/hosts for name resolution and it needs to be added to DNS or NIS as well.
> Then, I used DHCP client method to try to add
> install_client.
> - #./add_install_client -d -e 0:3:ba:44:f4:37 -s
> Server:/jumpstart/install -c Server:/jumpstart -p
> Server:/jumpstart/config sun4u
> cleaning up preexisting install client "CLIENT_MAC"
> removing /tftpboot/inetboot.SUN4U.Solaris_10-1
> removing /tftpboot
> To disable CLIENT_MAC in the DHCP server,
> making /tftpboot
> copying boot file to
> /tftpboot/inetboot.SUN4U.Solaris_10-1
>
> To enable 0100CLIENT_MAC in the DHCP server, ensure
> that
> the following Sun vendor-specific options are
> defined
> (SinstNM, SinstIP4, SinstPTH, SrootNM, SrootIP4,
> SrootPTH, and optionally SbootURI, SjumpCF and
> SsysidCF),
> and add a macro to the server named 01000CLIENT_MAC,
> containing the following option values:
>
> Install server (SinstNM) : Server
> Install server IP (SinstIP4) : ip-addr-for-twnet
> Install server path (SinstPTH) : /jumpstart/install
> Root server name (SrootNM) : Server
> Root server IP (SrootIP4) : ip-addr-for-twnet
> Root server path (SrootPTH) :
> /jumpstart/install/Solaris_10/Tools/Boot
> Boot file (BootFile) : 0100CLIENT_MAC
> Profile location (SjumpsCF) : Server:/jumpstart
> sysidcfg location (SsysidCF) :
> Server:/jumpstart/config
>
> - I tried to boot through "boot net - install", but
> problem persistent.
"boot net - install" only does a traditional client request. If you want to do a DHCP request, you need "boot net:dhcp - install"
> (4) I google the error messages, Google told that the
> messages is due to MAC_IP unmatching.
> - # arp -s CLIENT_IP CLIENT_MAC
> - Because I am not netadmin, I can not add ethers map
> to NIS server. I wonder whether there is a way to
> enable jumpstart serverunder NIS domain.
The server must be able to resolve the name CLIENT. What is in the 'hosts' entry for the server in /etc/nsswitch.conf?
> (5)Because I am not the net admin, I can not make
> ethers. I login to the NIS server and I see that
> there is no /etc/ethers file on the NIS server. Then,
> I got the "Error: unknown "CLIENT" messages when I
> add the install client.
Same thing. What is in the 'ethers' entry for the server in /etc/nsswitch.conf
> Q1. I modify the /etc/nsswitch.conf in my jumpstart
> server as follows.
>
> ethers: nis files -> I think it will firstly contact
> NIS server then /etc/ethers in the jumpstart server
> for
> client MAC.
>
> But the ARP/RARP timout also persistent. I wonder why
> the jumpstart server can not find the CLIENT MAC from
> the /etc/ethers of itself.
Use snoop on the server. Can you see the client RARP request? You can start 'in.rarpd' on the server with '-d' for extra debugging. Does it see it? Is the MAC really in the correct format in /etc/ethers (colons separating the octets, lowercase letters)?
> Q2. Assuming I drop the jumpstart server out of the
> control of NIS server. And my jumpstart client is
> also under
> the NIS domain. I wonder whether my jumpstart client
> can boot install from the jumpstart server even
> though the jumpstart server does not have NIS naming
> service.
Having the 'files' entry in /etc/nsswitch.conf should be sufficient.
Test with the 'getent' utility.
# getent ethers 0:3:ba:44:f4:37
# getenet hosts CLIENT
Run those on the server and verify that they return the information you expect.
--
Darren
# 2
Thanks for your reply, Darren.
==== Start Quote ====
That suggests that RARP requests are not being returned. Is the client in the servers /etc/ethers file? It is automatically added by using -e on add_install_client.
==== End quote =====
I manually add the MAC-to-CLIENT line to /etc/ethers on jumpstart server.
#more /etc/ethers
Client_MACClient
The jumpstart server is under NIS domain and the ethers entry on the /etc/nsswitch.conf
#more /etc/nsswitch.conf | grep ethers
ethers:files nis ==> The server will firstly contact /etc/hosts of itself, then contact nis
server.
I tested the MAC/IP resolution on the jumpstart server according to your advices.
It seems fine
========================
# getent hosts CLIENT
192.168.11.11CLIENT
# getent ethers MAC_Address
CLIENTMAC_Address
========================
==== Start Quote ====
CLIENT is resolved locally on the server. Can you issue 'ping CLIENT'? Do you get a ping attempt, or does it say "unknown host"? Perhaps your server is not using /etc/hosts for name resolution and it needs to be added to DNS or NIS as well.
==== End Quote ====
I ping CLIENT and console shows no answer from CLIENT. Because CLIENT host now can not boot up and will hang at start up CDE login. Really, I am not sure whether CLIENT IP is 192.168.11.11. I think I have assigned the CLIENT_IP with a new one to
correspond the MAC address on the /etc/ethers and the host name on the /etc/hosts on jumpstart server. The configuration may work. I am not sure.
The jumpstart server has following hosts entry on /etcnsswitch.conf.
hosts:nis dns files
==== Start Quote ====
What is in the 'ethers' entry for the server in /etc/nsswitch.conf
==== End Quote ====
==>
ethers:files nis
==== Start Quote ====
Use snoop on the server. Can you see the client RARP request? You can start 'in.rarpd' on the server with '-d' for extra debugging. Does it see it? Is the MAC really in the correct format in /etc/ethers (colons separating the octets, lowercase letters)?
==== End Quote ===
I tried to use snoop -o cap server CLIENT to capture. And I ping
server at CLIENT host. But snoop does not catch anything related to rarp.
Can you advise me how to snoop the rarp-related packets.
--
Message was edited by:
staygreen
