Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1263
  • Last Modified:

Trouble Jumpstarting Sun Blade 1500 with Solaris 9 9/05

I am having trouble jumpstarting a machine. Here are the specs:

Jumpstart Server: Sun Fire 280R, solaris 9, 118558-06
Jumpstart Client: Sun Blade 1500, attempting to jumpstart with solaris 9 9/05

The jumpstart client is hanging on "Requesting Internet Address for <mac address>"

Running 'snoop <client name>'  on the the jumpstart server keeps repeating the same line: "BPARAM C WHOAMI? <Ip address for client> (retransmit)

I went over the sysidcfg, bootparams, and rules files many times and cannot find anything wrong. Why is it hanging?

thanks in advance for any and all assistance thrown my way.
0
ap-it
Asked:
ap-it
  • 3
  • 2
  • 2
4 Solutions
 
vamsi_ukCommented:
Check this thread, someone had the same problem with a possible solution.

http://www.webservertalk.com/archive100-2006-2-1399762.html
0
 
Hanno P.S.IT Consultant and Infrastructure ArchitectCommented:
vamsi_uk, the thread you refer to looks different to me (btw: "boot net -v install" is valid)

ap-it,
If you don't have a naming service running, the bparam messages will take several minutes until timing out.
Did you try this already?
0
 
Hanno P.S.IT Consultant and Infrastructure ArchitectCommented:
1) Which command do you actually use to boot off the network?
2) Are you in the same subnet as the boot server and the jumpstart server?
3) Do you see any messages like "100 full-duplex link up" on your client and does it match your environment?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ap-itAuthor Commented:
I think I found the problem, having to do with the way I wrote up the ./add_install_client line referencing the sysidcfg file. But here is my new problem. I ran ./rm_install_client <client name> to start a clean ./add_install_client job. When it did not clean out the /etc/bootparams, I went in and did it manually, ran the make command and all should have been good. But now, when I run the add_install_client, it is now saying this:

"Error: Ehthernet number for <client name> not found

I dont understand why this is. It still exists in the /etc/ethers file. What is the deal? did the rm_install_client do something that revents the add_install_client from working again?

0
 
vamsi_ukCommented:
Are you sure there is no error in the command you are using?
example:
#./add_install_client   -e 7:00:40:49:38:12     -s server1:/export/install    -c server1:/jumpstart      -p server1:/jumpstart    <Jumptstart client to be installed>    sun4u
0
 
ap-itAuthor Commented:
Got ethernet back to working properly. forgot the -e option in readding client. and the original problem appeared to be a typo in my add_install_client line. All is good in the neighborhood now. Thanks.
0
 
ap-itAuthor Commented:
Fixed my own problem, but wanted to disperse the points since you all tried to help. thanks again.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now