It is currently Wed, 20 Jan 2021 16:25:15 GMT



 
Author Message
 Fujitsu jumpstart spradic success
Scenario : contractor on client site - short term holiday cover  ie
little insight into history of j/s server etc.

Requirement : to build several fujitsu 250 systems with solaris 8 from
a jumpstart server using a flash image.  Client has a script on j/s
server which prompts for solaris version (8), ethernet adress of new
system (gleaned from "banner" in OBP), IP address of new server, new
systemm name, and whether sun or fujitsu build required.  J/S server
(in E450 FWIW) cabled to small hub, new systems also cabled to it.
The Fujitsu servers appear top have three NICs "on board" - a single
one, and below that a pair (one above the other).  The top NIC of each
pair is used to connect to the hub (general advice from another sys
admin here).

In short everything seems set up OK...  the boxes are cabled exactly
the same.  the script on the j/s server places the ethernet address
and hostname in /etc/ethers OK, and the IP address and hostname in the
/etc/hosts file, and an entry in /etc/bootparams.

Problem :  some boxes boot from net and install OK, others don;t even
boot from the net!

ie I run "boot net - install" from the OBP/ok prompt - some systems
bootstrap and immediately do that "number count" thing and progress
through building...  whilst others bootstrap and display one "waiting
for ARP/RARP" message - then do nothing else whatsoever....  no more
ARP/RARP messages (which one would expect if the ethers info say was
wrong), no build starting....  and no response from the keyboard ie
hit return doesn't line feed...  Its as if the very initial bootp
process has begun...  but drops out/freezes/halts/fails/whatever.

This is a closed network in effect, there are no IP clashes.

The systems that fail to respond (other than a single ARP/RARP
message) have been tried also with a successfull system's cable (in
case its the cable or the hub) to no avail, and on both of the paired
NICs (other sys admins say the lone NIC is not working/used/whatever).

Any ideas?  Obviously the jumspstart server is working, the ethernet
address etc is all added correctly, and even the same cables are being
used.

cheers

ian



 Sun, 24 Sep 2006 15:47:34 GMT   
 Fujitsu jumpstart spradic success

Check net is correcly set in devalias, also that use-nvramrc? true

It may be that what you are expecting as "net" is not what you are
getting.
Also, check out local-mac-address? you may need that set to false

--
        Bruce

"The internet is a huge and diverse community and  
not every one is friendly"                            
        http://www.ytc1.co.uk                    



 Sun, 24 Sep 2006 19:24:10 GMT   
 Fujitsu jumpstart spradic success
further to my previous post :

- the successfull servers ALL run POST when boot net - install is
entered.  The unsuccessfull ones ALL fail to do so, and go straight to
the "boot" line...

- having snooped the jumpstart server I can see the following traffic
on an unsuccessful system attempt to boot net - install...

cl3      -> BROADCAST   TFTP Read "C0A8F067" (octet)    
jsserver -> cl3         TFTP Error: access violation

(cl3 is the intended hostname of the box to build; C0A8F067 equates to
192.168.240.103, the intended IP address of the box to build)

Googling the above indicates possible problems with the /tftp (or
/tftpboot ?) directory contents...  I have to return to the build area
yet to have a gander at these, but the googling also suggested their
might be an issue with the architecture....   given that ALL the
systems are Fujitsu 250s (and other F250s have been built successfully
using this j/s server...  even I've managed four out of 16!) could
this (combined with the POST thing mentioned above) point to some
OBP/firmware revision differences causing the problems?  This is a
complete quasi-educated guess I accept!

cheers

ian



 Sun, 24 Sep 2006 23:02:25 GMT   
 Fujitsu jumpstart spradic success

RARP failures cause a message and rpc.bootparams failures cause a
message.  When you don't get anything, I begin to suspect TFTP problems.

Snoop from the jumpstart server and see what's going on, probably you've
got something wrong in the /tftpboot directory.

--
Darren Dunham                                           ddun...@taos.com
Senior Technical Consultant         TAOS             http://www.**-**.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >



 Sun, 24 Sep 2006 23:21:13 GMT   
 Fujitsu jumpstart spradic success

From another host on the net, can you tftp to your jsserver and read
that file?  Is the file world readable in the /tftpboot directory?

--
Darren Dunham                                           ddun...@taos.com
Senior Technical Consultant         TAOS             http://www.**-**.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >



 Sun, 24 Sep 2006 23:22:55 GMT   
 Fujitsu jumpstart spradic success

Red herring, I'd think.

The file needs to exist and be *world* readable.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.



 Mon, 25 Sep 2006 00:15:27 GMT   
 Fujitsu jumpstart spradic success
I have found that there can be a number of problems when all you get is
ARP messages. This normally points to the mini root image not getting
loaded to the client. Is the right architecture being specifed? Is it
one particular model that is having problems? Can you narrow down the
scope?

You can use snoop program to see what the messages are coming to the
jumpstart server.  This can tell you whether the client is at least
communicating with the jumpstart server and can rule out network
configuration issues.

If you do not see any communication from the client, it could be the
switch port speed settings. We have best results with auto detect. Could
also be the network interface drivers is not loaded or supported as a
jumpstart interface. we jumpstart off the hme interface. Jumpstart can
NOT be used with gigabit (barried in the docs somewhere).

If you see that the client is trying to communicate via your snoop on
the jumpstart server, then it maybe that the image specificed for the
boot is incorrect. ie, wrong architecture or the OS image on jumpstart
does not have driver support for that server type.  For example to
jumpstart a SUN 240, you need Solaris 8 revision 12/03 on the jumpstart
server. It could be a duplicate for the mac address that has incorrect
information before the correct entry.

Good luck.



 Wed, 27 Sep 2006 02:58:32 GMT   
 
   [ 7 post ] 

Similar Threads

1. Fujitsu/Siemens MemoryBird [USB Mass Storage] on Solaris: partial success

2. Jumpstart 2.5.1 Client from a 2.6 Jumpstart Server

3. SuSE-8.0 crashes with Fujitsu-Siemens Amilo

4. Help with Fujitsu-Siemens Amilo A 7600 + RedHat 7.3

5. Help installing Linux Distro on Transmeta Crusoe Notebook (Fujitsu P-1030)

6. Fujitsu Laptop RedHat 7.2 XWindows Setup Problem

7. Linux on Fujitsu C6581

8. Installing X server on Fujitsu E370 Laptop

9. Can't install Linux on FUJITSU hard drive

10. Fujitsu HD performance


 
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software