Warning: Solaris 10 x86 jumpstart (grub) from Solaris 8 server

Hi all,
I'm just posting this here in case someone comes across the same problem I did.
When trying to do a custom jumpstart installation on x86 boxes from a Solaris 8 SPARC server, Grub was failing to do TFTP of the "multiboot" and "x86.miniroot" files. A snoop of the traffic would reveal some "TFTP Error: not defined" packets.
Turns out this is a known bug:
http://sunsolve.sun.com/search/document.do?assetkey=1-1-6395719-1
The bug doesn't make any reference to jumpstart, and because of this it took me a while to find it.
I copied the in.tftpd binary from a Solaris 9 box, and it worked like a charm. (Would it be very difficult to issue a Solaris 8 patch?)
kind regards,

Here is the error output:
# ./add_install_client -i 192.168.1.51 -c sun1:/jumpstart/ -p sun1:/jumpstart/Sysidcfg/Solaris_10-intel/ host2 i86pc
unmount: warning: /tftboot/I86PC.Solaris_10-1 not in mnttab
unmount: /tftpboot/I86PC.Solaris_10-1 no such file or directory
mount: Mount point /tftboot.I86PC.Solaris_10-1 does not exist.
cleaning up preexisting install client "host2"
removing host2 from bootparams
rm: /tftboot/ is a directory
updating /etc/bootparams
ln: cannot create /tftpboot//pxegrub.I86PC.Solaris_10-1: File exists
Create a grub boot flloppy and edit GRUB menu to contain
the following entry:
title Solaris netinstall
rarp
kernel /I86PC.Solaris_10-1/multiboot kernel/unix -B install_media=192.168.1.100:/jumpstart/OS/intel
module /I86PC.Solaris_10-1/x86.miniroot
------------- end ---------------
So, I have tried this with the -i, -e -i+-e, with -s and without.
I have an entry in /etc/ethers and /etc/hosts. However, I don't think it is a FQDN or simular issue. Looks like a script issue.
/tftpboot/ ends up with
boot/
nbp. -> pxegrub.I86PC.Solaris_10-1
pxegrub.I86PC.Solaris_10-1
rm.192.168.1.51
/tftpboot/boot/
grub/
/tftpboot/boot/grub/
menu.1st
# cat menu.1st
default 0
timeout=30
title Solaris_10 jumpstart
kernel /i86PC.Solaris_10-1/multiboot kernel/unix -B install_config=192.168.1.100:/jumpstart,sysid_config=192.168.1.100:/jumpstart/Sysidcfg/Solaris_10-1-intel/,install_media=192.168.1.100:/jumpstart/OS/intel
module /I86PC.Solaris_10-1/x86.miniroot
---- end ----
Thanks for the help.
Aaron

Similar Messages

Solaris 10 x86 jumpstart installing from cd instead of install server

Hi all,
I am building a Solaris 10 x86 jumpstart server and was able to jump the client to a certain point. The jump appears to be running but for some reason stops after the first CD ( very peculiar considering the jumpstart is automated). After watching the jump, I discover that the install is using my CD to install rather than from the install server. It is, however, getting the sysidcfg info, rules and profiles from my install server. I booted from CD and then selected Custom Jumpstart to install via the network. Can someone tell me what I am doing wrong?
Here is my add_install_client command:
/jumpstart/OS/Solaris_10_x86_2006-06/Solaris_10/Tools/add_install_client -s server1:/jumpstart/OS/Solaris_10_x86_2006-06 -c server1:/jumpstart -p server1:/jumpstart/Sysidcfg host1 i86pc
Here is the output from that command:
Adding Ethernet number for jre-dlt to /etc/ethers
updating /etc/bootparams
ln: cannot create /tftpboot/pxegrub.I86PC.Solaris_10-1: File exists
Create a grub floppy and edit GRUB menu to contain
the following entry:
title Solaris netinstall
rarp
kernel /I86PC.Solaris_10-1/multiboot kernel/unix -B install_media=192.168.1.100:/jumpstart/OS/Solaris_10_x86_2006-06,install_boot=192.168.1.100:/jumpstart/OS/Solaris_10_x86_2006-06/boot
module /I86PC.Solaris_10-1/x86.miniroot
BTW, can someone tell me how to create a grub floppy? Can't seem to find any documentation on that!
Thanks in advance,
Brian

Here is the error output:
# ./add_install_client -i 192.168.1.51 -c sun1:/jumpstart/ -p sun1:/jumpstart/Sysidcfg/Solaris_10-intel/ host2 i86pc
unmount: warning: /tftboot/I86PC.Solaris_10-1 not in mnttab
unmount: /tftpboot/I86PC.Solaris_10-1 no such file or directory
mount: Mount point /tftboot.I86PC.Solaris_10-1 does not exist.
cleaning up preexisting install client "host2"
removing host2 from bootparams
rm: /tftboot/ is a directory
updating /etc/bootparams
ln: cannot create /tftpboot//pxegrub.I86PC.Solaris_10-1: File exists
Create a grub boot flloppy and edit GRUB menu to contain
the following entry:
title Solaris netinstall
rarp
kernel /I86PC.Solaris_10-1/multiboot kernel/unix -B install_media=192.168.1.100:/jumpstart/OS/intel
module /I86PC.Solaris_10-1/x86.miniroot
------------- end ---------------
So, I have tried this with the -i, -e -i+-e, with -s and without.
I have an entry in /etc/ethers and /etc/hosts. However, I don't think it is a FQDN or simular issue. Looks like a script issue.
/tftpboot/ ends up with
boot/
nbp. -> pxegrub.I86PC.Solaris_10-1
pxegrub.I86PC.Solaris_10-1
rm.192.168.1.51
/tftpboot/boot/
grub/
/tftpboot/boot/grub/
menu.1st
# cat menu.1st
default 0
timeout=30
title Solaris_10 jumpstart
kernel /i86PC.Solaris_10-1/multiboot kernel/unix -B install_config=192.168.1.100:/jumpstart,sysid_config=192.168.1.100:/jumpstart/Sysidcfg/Solaris_10-1-intel/,install_media=192.168.1.100:/jumpstart/OS/intel
module /I86PC.Solaris_10-1/x86.miniroot
---- end ----
Thanks for the help.
Aaron

Solaris X86 Jumpstart slow

I'm trying to jumpstart a Sun x4240 and during the boot up when it runs the install-discovery script, the server goes very very slow. It will eventually move past this part, but only after many hours. The server has 4 disks, which I have setup on the raid controller as JBOD's, we are not using the RAID functions of the card at all.
It seems the longest time is taken when running the the the script /boot/solaris/bin/create_diskmap, which is mostly this:
/sbin/biosdev 2> /dev/null | while read diskno diskpath
do
devname=`/bin/ls -l /dev/rdsk/*p0 | /bin/grep $diskpath | /bin/nawk '{ print $9 }'`
ctdname=`echo $devname | /bin/sed "s#/dev/rdsk/##" | /bin/sed "s#p0##"`
grubdisk=`echo $diskno | /bin/sed "s/0x8//"`
echo "$grubdisk $ctdname $diskpath" >> "$GRUBDISKMAP"
done
Then once it gets past this part (many hours) it hangs again around this part:
# x86 config cleanup logic
if [ -x /usr/sbin/install.d/atconfig ]; then
/usr/sbin/install.d/atconfig
fi
Atconfig is described thusly:
Besides ON changes there are changes needed in the
Install consolidation. When you boot the Solaris CD/DVD,
the atconfig binary is run that searches the disk for
kernel/misc/sysinit file and copies this to
/tmp/root/kernel/misc/sysinit so the
svc_serial.c code from Suninstall can try to preserve the
hostid during an upgrade and even an install. We need
to modify this code to also search for /etc/hostid and preserve
it. However, for older systems we also need to search for
kernel/misc/sysinit for those systems that have hostid stored
there, and convert the hostid in sysinit into a hostid in /etc/hostid.
There was no contract between ON and Install for sysinit;
we now have a contract in place between the two consolidations
for Install's use of /kernel/misc/sysinit and /etc/hostid.
The server installs fine during a normal DVD install. I'm not sure what else to do on this. If anyone has any guidance that would be great.

Yes... I've seen and used the grub -b switches for input-device and output-device and this does change the way certain things work. However, this does not redirect input and output solely to the console, as you would, lets say, any sparc box. I start a jumpstat process, tell it to go to the console, and it hangs and waits for input from the VGA device. Right now, I have an odd interaction going on between the ILOM webgui redirection and the console. I can't login through the webgui and reboot the box through the console, nor can I hit CTRL+N to get it to boot off the network when I have the ILOM Webgui redirected to my keyboard. But when it boots off the virtual CD, or if I use the console to get into the BIOS, then and only then can I use my keyboard in the ILOM Webgui.
There is some sort of odd interaction between the console and that stupid VGA port on the ILOM that is not explained in ILOM docs that I have read. And that is what this post is trying to figure out. When you jumpstart a sparc box, you have total control from the console. This is not the case on x86.
Please re-read my other post before you comment on double posting. Both are about x86 jumpstart. One is about console redirection (this post). The other post is asking about getting jumpstart NOT to go through an interactive install through the -b switches. Two separate issues.

Mounting a Solaris x86 CD/DVD from a remote Windows CD/DVD-ROM drive

Greetings, all.
Is it possible to mount a remote Windows CD/DVD-ROM drive? I have the Solaris 10x86 Companion Software DVD sitting in a CD/DVD-ROM drive that's installed on a Windows server on my network. It is shared-out (F:) and the two servers can ping each other. I've also confirmed the NFS services/daemons are running on the Solaris x86 machine. I've tried the following variations but, all have failed to produce successful results:
# mount -F nfs x.x.x.x:/f /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F hsfs x.x.x.x:/f /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f
# mount -F hsfs x.x.x.x:/F /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F
[FYI: S10_106_SOFTWARE is the DVD's label as reported by Windows Explorer.]
# mount -F hsfs x.x.x.x:/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/S10_106_SOFTWARE
# mount -F hsfs x.x.x.x:/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/s10_106_software
# mount -F nfs x.x.x.x:/S10_106_SOFTWARE /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F nfs x.x.x.x:/s10_106_software /mnt
nfs mount: x.x.x.x: : RPC: Program not registered
nfs mount: retrying: /mnt
# mount -F hsfs x.x.x.x:/f/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f/s10_106_software
# mount -F hsfs x.x.x.x:/F/s10_106_software /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F/s10_106_software
# mount -F hsfs x.x.x.x:/f/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/f/S10_106_SOFTWARE
# mount -F hsfs x.x.x.x:/F/S10_106_SOFTWARE /mnt
mount: No such device
mount: cannot mount x.x.x.x:/F/S10_106_SOFTWARE
I've also tried mounting it at bootup by adding the appropriate entry in the /etc/vfstab file but, this does not work as well. I've tried Google'ing for an answer to my issue but, I haven't been able to find anything that applies directly to what I'm reporting. It's usually chatter about mounting from one UNIX server to another. Any advice from the community would be greatly appreciated.

After three weeks, you deserve a reply. Windoze does
not natively support NFS.Also deserves a decent answer...
There are two ways to do this:
Install Microsoft's free "Windows Services for UNIX," which includes a Windows NFS server; or
Install the 'sharity' package (google for it); it provides Solaris systems the ability to mount Windows shares

Solaris x86 on Compaq DL360 (P21) server

I am having issues installing this OS on the server in the title... it is a DL360 with Dual PIII 998 processors and 1.4G RAM.
I setup the RAID controller at statup to use RAID1 with 2 x 36G drives.... and then boot from the Solaris Disk 1 (no the installer disk)...
I am using the RAID controller driver supplied from Compaq for Solaris 8 and at the first stage it successfully is added during the installation process....
The process goes through as per expected, setup network, setup drive layout and even install required OS modules.. then it happens....
... the request to insert the disk holding file CPQARY2 pops up, disk is inserted but the message 'file cannot be found on disk' is returned....
Silly thing is that the system has already used this driver from this disk to load the HDD RAID conntroller info into memory... it even installs to the disks with no problems....
Is this an issue because the drivers are for Sol8 and not 9??... and does anyone know where and if I can get the drivers for 9??.. they are not on the website for this server model....

did you make any experiance regarding Solaris 10 X86 ?No, but...
Unfortunately there is no Solaris 10 driver for the
built in SmartArray of the DL360 (P21) available.... I expect that the same workaround is OK for Solaris 10, that is,
rename the DU/sol_28 directory to DU/sol_210 on HP's driver
update floppy.

Jumpstart installation from Solaris 10 zone

Hi,
I am using a Sol 10 zone as a jumpstart server, and have encountered a problem.
Due to not being able to use the out-of-the-box nfs server, as it does not run in a local zone on Sol 10, I have looked at using a user-space nfs server, unfsd.
unfsd runs fine, and can be used by a client to nfs-mount a directory, but when it comes to using the client's flash archive to build the client, I get this error below in my snoop output:
10:54:46.04754 js-client -> js-server MOUNT3 C Mount /flash_archives/TEST/js-client.flar
10:54:46.04779 js-server -> js-client MOUNT3 R Mount Not a directory
Which implies to me that the jumpstart client is trying to nfs-mount a file, and unfsd does nto allow this.
Any advice/suggestions on how to resolve this would be appreciated.
Richard.
Edited by: Richard on Jun 22, 2012 8:51 AM

Just to provide an update.
I switched to using ftp to get the flar file from the jumpstart server, which works fine.
I do believe that the issue with NFS is because the Solaris in-built NFS will allow a file to be NFS-mounted, but the user-space NFS daemon I used ( unfsd ) does not allow this, although I've not done sufficient snooping to prove this.
Richard.

Install solaris 10 to UCS from network server

Can anyone share your experience on doing this?

Not seeing Solaris 10 on supportted list,
http://www.cisco.com/en/US/docs/unified_computing/ucs/interoperability/matrix/hw_sw_interop_matrix.pdf

Using isfinite on Solaris 11.1 x86 with CC from Solaris Studio 12.3

Hello,
I am trying to build GEOS , a C++ API that uses isfinite. From the man page, isfinite is defined in math.h and is a c99 feature.
The header is properly included the build fails with error :
/bin/sh ../../libtool --tag=CXX   --mode=compile CC -DHAVE_CONFIG_H -I. -I../../include -I../../include/geos -I../../include -m64 -g -library=stlport4 -library=Crun -c -o HCoordinate.lo HCoordinate.cpp
libtool: compile: CC -DHAVE_CONFIG_H -I. -I../../include -I../../include/geos -I../../include -m64 -g -library=stlport4 -library=Crun -c HCoordinate.cpp -KPIC -DPIC -o .libs/HCoordinate.o
"HCoordinate.cpp", line 76: Error: The function "isfinite" must have a prototype.
"HCoordinate.cpp", line 76: Error: The function "isfinite" must have a prototype.
"HCoordinate.cpp", line 153: Error: The function "isfinite" must have a prototype.
"HCoordinate.cpp", line 164: Error: The function "isfinite" must have a prototype.
4 Error(s) detected.
gmake[3]: *** [HCoordinate.lo] Erreur 1
In fact, the function is not defined because CC does not define __C99FEATURES__ as c99 does. If I add a -D__C99FEATURES__ parameter to CC, the build ends properly but I think it is not the proper way to do it.
Does anybody knows the right way to do so ?
Best regards
Eric

There is currently no support for the C99 math features in Studio C++. We have an outstanding request (bug 16263435) to make the features available, but there are some issues to be resolved. Because of the way the C headers and runtime library are implemented, if you get the C99 math features, you also get C99 (instead of C90) behavior for various types and functions that changed from C90 to C99.
Defining your own configuration macros, like __C99FEATURES__ is not recommend or supported. Try it at your own risk.
You could consider writing in C the routines that need access to C99 math, and compiling them with the C compiler. Simple example:
file isfinite.c
#include <math.h>
#include <stdbool.h>
bool myisfinite(double x) { return isfinite(x); }
file mymath.h
extern "C" bool myisfinite(double);
inline bool isfinite(double x) { return myisfinite(x); }
file myprog.cc
include "mymath.h"
void foo()
    if( isfinite(xval) ) { ... }
    else { ... }
% cc -xc99=all isfinite.c
% CC myprog.cc isfinite.o

Solaris x86: learning tool for Solaris SPARC?

I would like to know to what extent Sol x86 knowledge and experience would translate over to Sol SPARC. Not in a *NIX general sense, but Solaris specific. The company I work for sells backup devices including virtual tape library devices, and it is my job to test them with various operating systems and backup software. We have a Sol SPARC server solely for that purpose but it's still not something I can muck around with. Something I definitely need experience with is setting up and configuring tape libraries. So, specifically in this regard, but also in general, how would Sol x86 experience carry over to Sol SPARC? Thanks in advance.

Most commands are identical. Performance analysis, loading all are similar. Tape interaction, creation of tape devices is going to be pretty much the same.
The differences show up a lot at the hardware level. HBAs aren't usually the same, many drivers (and their quirks) are different between the architectures. If you're debugging connectivity to a tape library, those differences may be critical.
So you can't get as close as you may want, but I'll bet it would still be helpful.
Darren

Solaris 9 Jumpstart Failure

Greetings.
I am in the process of changing a system over to Solaris 9 (9/04) from Solaris 8 (we cannot move to Solaris 10 due to ClearCase incompatiblities).
We use flash archives in our jumpstart process. The master system is created using a very Spartin profile (SUNWCreq with a number of other required packages). There are also a number of additional tweaks made to the master system to stop unrequired services, deamons, etc. The only additional patches installed are the Java cluster patches.
I have been able to successfully jumpstart the jumpstart server host from CD. However any attempts to jumpstart other clients using the jumpstart server have failed. I suspect that it is related to the inability to copy the sysidcfg file during the jumpstart process.
The address for the jumpstart server is 10.1.1.1; the hostname is n1; the MAC address is 0:3:ba:35:80:88
The address for the jumpstart client is 10.1.1.34; the hostname is n34; the MAC address is 0:3:ba:14:c6.
On the jumpstart server some of the relevant files are included below.
/etc/bootparams:
n34 root=n1:/jumpstart/OS/Solaris_9_2004-09/Solaris_9/Tools/Boot install=n1:/jumpstart/OS/Solaris_9_2004-09 boottype=:in sysid_config=n1:/jumpstart/Sysidcfg install_config=n1:/jumpstart rootopts=:rsize=32768
/etc/hosts:
# Internet host table
127.0.0.1 localhost
10.1.1.1 n1 oam1a loghost
10.1.1.2 n2 db1a
10.1.1.34 n34
/etc/ethers:
0:3:ba:14:c6:cd n34
/etc/dfs/dfstab:
share -F nfs -o ro,anon=0 /jumpstart
share -F nfs -o ro,anon=0 /jumpstart/OS/Solaris_9_2004-0�9
/tftpboot directory:
lrwxrwxrwx 1 root root 26 Aug 8 10:36 0A010122 -> inetboot.SUN4U.Solaris_9-1
lrwxrwxrwx 1 root root 26 Aug 8 10:36 0A010122.SUN4U -> inetboot.SUN4U.Solaris_9-1
-rwxr-xr-x 1 root root 152376 Aug 8 10:36 inetboot.SUN4U.Solaris_9-1
-rw-r--r-- 1 root root 313 Aug 8 10:36 rm.10.1.1.34
ls -l /jumpstart/Sysidcfg/sysidcfg:
-rw-r--r-- 1 root root 375 Aug 4 17:12 /jumpstart/Sysidcfg/sysidcfg
/jumpstart/Sysidcfg/sysidcfg:
system_locale=en_AU
timezone=Australia/NSW
name_service=none
root_password=<removed for this post>
terminal=xterm
network_interface=primary { protocol_ipv6=no netmask=255.255.240.0 default_route
=10.1.0.1 }
timeserver=localhost
timeserver=47.153.235.110
Once the install is started on the client the following output is generated (note the sysidcfg copy failure):
ok boot net - install
Res
LOM event: +21h32m35s host reset
etting ...
�
Netra 120 (UltraSPARC-IIe 648MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #51693261.
Ethernet address 0:3:ba:14:c6:cd, Host ID: 8314c6cd.
Executing last command: boot net - install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: - install
SunOS Release 5.9 Version Generic_117171-07 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
whoami: no domain name
Configuring /dev and /devices
Using RPC Bootparams for network configuration information.
Skipping interface eri1
Configured interface eri0
Searching for configuration file(s)...
cp: cannot create /etc/sysidcfg: Permission denied
chmod: WARNING: can't change /etc/sysidcfg
Using sysid configuration file 10.1.1.1:/jumpstart/Sysidcfg/sysidcfg
Search complete.
WARNING: IP: Hardware address '00:03:ba:35:80:88' trying to be our address 010.001.001.001!
WARNING: IP: Hardware address '00:03:ba:35:80:88' trying to be our address 010.001.001.001!
The IP address conflict is with the jumpstart server. The address for the jumpstart server is 10.1.1.1. The warning message is generated for a number of minutes after it starts. I figure that it is caused by the inability to copy the sysidcfg file.
This same system can be installed successfully using a Solaris 8 jumpstart configuration.
Note that the client system is currently installed with Solaris 8.
I did use the command "boot net -v - install" from the OK prompt, but no additional information was provided relating to when the sysidcfg file could not be copied.
If anyone has any ideas about what could be causing this problem or has any information about additional debugging which could be used to figure out this issue, I would greatly appreciate your thoughts.
Thanks in advance.
Cheers,
Jason.

Ideas.. Hmm, none which seems that correct, but you could try some things.
If it gets the wrong IP that could explain why it fails to copy the sysidcfg file.
First you could try and do a snoop on the ethernet address;
snoop ether 0:3:ba:14:c6:cd
(you could also try the -v flag to increase the verbosity).
The things you should look for are arp/rarp requests, the jumpstart client will use arp/rarp to determine its IP address, snoop will show you which server that responds, and what address it gets, futher more its a good idea to verify that the response to the bootparams requests comes from the correct server.
Of course there might be other oddnesses as well.
Was the data you provided extracts? If it was you should check the /etc/ethers and /etc/bootparams for duplicates entries, so there are no other occourances of the clients ehternet address in /etc/ethers, and no bogus entries starting with * or the same hostname in /etc/bootparams.
If you added the client manually you could always try and use the Tools/rm_install_client and Tools/add_install_client scripts to add it again, these script sometimes detect problems with the configuration.
Lastly you didn't show us your /etc/nsswitch.conf file, but i assume that it has "files" first for the ethers, hosts and bootparams entries?
Good luck
//Magnus

Can't see Solaris X86/SPARC Agents for 12c

I've ran the manual updates and automatic updates and the only agents i can see in the repository are still the linux x86 and X64 agents. Is there any way to manually load the agent to the repository so we can start testing the deployment?
I see the sparc/x86 agents are available for manual download on OTN

Go to Setup > Extensibility > Self Update. From the Self Update page, look in the Agent Software folder, you should see information showing that agents for Solaris x86 (64-bit) and Solaris Sparc (64bit) are available.
If necessary, see the following doc for information on using Self Update:
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/self_update.htm#CACCIFBF
Regards,

Solaris 10 x86 PXE and jumpstart using Linux DHCP server !!

Hi,
I am trying to get a my Solaris 10x86 jumpstart rolling.
I have created the images for the OS, but the only issue I have ahead is using a Linux box as a DHCP server for my X86 box to get the image.
Is it possible to have a linux host that serves as a dhcp server to jumstart X86 host with Sol 10 x86
or do I need to have a solaris host that runs DHCP service on it.
Any advice on this issue.
Thanks.

Well, if you don't think the online Documentation helpful, then the better way is reading step-by-step instructions from a book. Get to local bookstore, i.e Barne&Nobles or Border or any big local bookstore, there should be pretty good book for Unix Administrator (Solaris version).
If you have time and think you can memorize then, read on the spot; otherwise, buy the book for future reference.
If that's not what you had in mind, then this link of free online book might help : http://www.oreilly.com/catalog/solaris8/chapter/ch04.html
Normally, oreilly online bookstore offers free books to accredited universities, colleges, and organizations. However, if that option isn't for you, it might even offer free sample chapters that might just suit your needs.
hoep it helps.
-van.

Problem jumpstarting a Solaris 9 SPARC from Solaris 10 x86

Hi all,
I'm going to install a couple of servers using Jumpstart, but I've run
into a problem so I'm kinda in panic.
This is the net boot:
Executing last command: boot net - install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: - install
Timeout waiting for ARP/RARP packet
29200 panic - boot: Could not mount filesystem.
Program terminated
ok
I've setup the jumpstart server on my x86 PC, which is Solaris 10 final
with JET 3.7.3. Since I'm jumpstarting Solaris 9 onto a SPARC machine, I
had to do copy_solaris_media over NFS, since I can't mount the SPARC
ISO-CD1 on my x86. The install server seems to be OK, at least it didn't
complain during setup.
The log entry from sniffing the JS server:
3266 1:15:25.48103 aaa -> xxx WHO C port=33345
3267 1:15:25.48427 aaa -> xxx WHO C port=33345
3268 1:15:25.48636 aaa -> xxx WHO C port=33345
3269 1:15:25.48748 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3270 1:15:25.49044 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3271 1:15:25.49283 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
3272 1:15:25.49394 aaa -> xxx PORTMAP R GETPORT port=32775
3273 1:15:25.49541 aaa -> xxx PORTMAP R GETPORT port=32775
3274 1:15:25.49673 aaa -> xxx PORTMAP R GETPORT port=32775
3275 1:15:25.49867 aaa -> xxx PORTMAP R GETPORT port=32775
/etc/bootparams:
xxx root=aaa:/opt/install/media/Solaris_9/Solaris_9/Tools/Boot
install=192.168.4.5:/opt/install/media/Solaris_9 boottype=:in
sysid_config=192.168.4.5:/opt/jet/Clients/xxx
install_config=192.168.4.5:/opt/jet rootopts=:rsize
32768
term=:vt100
Any idea what could be wrong? It stops at 29200, wheres Solaris 10 runs
further up to 38000 something.
Jumpstarting the Solaris 10 onto the same SPARC works perfectly, using
the exact same configuration files.
Thanks

Hi all,
I managed to solve the problem.
This is very weird! can someone explain why this happens?
Output for working Solaris 10 boot:
Executing last command: boot net -v
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v
38600 Using RARP/BOOTPARAMS...
Internet address is: 192.168.4.6
hostname: xxx
Requesting Ethernet address for: 192.168.4.5
Found 192.168.4.5 @ 0:0:86:1f:f7:92
root server: aaa (192.168.4.5)
root directory: /opt/install/media/Solaris_10/Solaris_10/Tools/Boot
Size: 0x704c8+0x1b8d2+0x2e1ba Bytes
Output for non-working Solaris 9 boot:
Executing last command: boot net -v
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v
Timeout waiting for ARP/RARP packet
29200 Using RARP/BOOTPARAMS...
Internet address is: 192.168.4.6
hostname: xxx
Found 192.168.4.5 @ 0:0:86:1f:f7:92
root server: aaa (192.168.4.5)
root directory: /opt/install/media/Solaris_9/Solaris_9/Tools/Boot
panic - boot: Could not mount filesystem.
Program terminated
ok
I then replaced /tftpboot/inetboot.SUN4U.Solaris_9-1 with /tftpboot/inetboot.SUN4U.Solaris_10-1 from the Solaris 10 tree, renamed /tftpboot/inetboot.SUN4U.Solaris_10-1 to /tftpboot/inetboot.SUN4U.Solaris_9-1
Voila!
Now works.
inetboot.SUN4U.Solaris_9-1 was not corrupt (must be some internal bootimage bug related to Netra-T1?).
Old bootimage: "inetboot.SUN4U.Solaris_9-1", 152376 bytes, "sum" 3662 and 298.
New bootimage: "inetboot.SUN4U.Solaris_9-1" (Sol 10 image), 214880 bytes, "sum" 53512 and 420.
By the way I was using latest Solaris 9/04, u7

Migration from Solaris Sparc server to Solaris x86

Hi ,
I would like to know.
Migration from SAP ECC6 , Oracle , Solaris Sparc to Ecc6, Oracle, Solaris x86 , Is this consider Heterogeneous or Homogeneous system copy?
Thanks.
Best Regards,
ck chai

Solaris on SPARC is a BIgEndian platform, Solaris on X86 is LittleEndian - so it's heterogeneous --> you need to use R3load to performa a migration - and you need to have a certified migration consultant on-site to do that migration (http://service.sap.com/osdbmigration --> FAQ).
Markus

Network install from solaris 10 x86 server to x86 client

My setup is:
install server OS: Solaris 10, i86pc .
The install server is also boot server using tftpboot.
The dhpc server is configured according to the instructions which are
given when adding an install client in Solaris 10.
The client can communicate with the install and boot server but fails
to load the boot image. The snoop output is
Using device /dev/iprb0 (promiscuous mode)
cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
cdm2 -> cdm3 TFTP Read "nbp.cdm2" (octet)
cdm3 -> cdm2 UDP D=2070 S=39122 LEN=22
cdm2 -> cdm3 TFTP Error: not defined
cdm2 -> cdm3 TFTP Read "nbp.cdm2" (octet)
cdm3 -> cdm2 UDP D=2071 S=39123 LEN=23
cdm2 -> cdm3 TFTP Ack block 0
cdm3 -> cdm2 TFTP Data block 1 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 1
cdm3 -> cdm2 TFTP Data block 2 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 2
cdm3 -> cdm2 TFTP Data block 3 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 3
cdm3 -> cdm2 TFTP Data block 4 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 4
cdm3 -> cdm2 TFTP Data block 5 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 5
cdm3 -> cdm2 TFTP Data block 6 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 6
cdm3 -> cdm2 TFTP Data block 7 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 7
cdm3 -> cdm2 TFTP Data block 8 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 8
cdm3 -> cdm2 TFTP Data block 9 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 9
cdm3 -> cdm2 TFTP Data block 10 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 10
cdm3 -> cdm2 TFTP Data block 11 (1456 bytes)
cdm2 -> cdm3 TFTP Ack block 11
cdm3 -> cdm2 TFTP Data block 12 (172 bytes) (last block)
cdm2 -> cdm3 TFTP Ack block 12
cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
cdm3 -> cdm2 DHCP/BOOTP DHCPOFFER
cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
cdm3 -> cdm2 DHCP/BOOTP DHCPOFFER
cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
cdm3 -> cdm2 DHCP/BOOTP DHCPOFFER
And then fails: i.e. it seems not to find the boot image.
Any suggestions???
Lydia

I can't tell exactly what's wrong, since you attached only
snoop log.
But since you're using DHCP, I guess you are trying to
do PXE boot to install. When you use PXE boot, you need
to configure some vendor options (like SrootIP4, SrootNM
etc) and also create macros with dhcpmgr.
there is documentation at
http:docs.sun.com
so check the documentation to see what is missing.
If you've already done these, check NFS configuration
if all directory are correctly shared.

Warning: Solaris 10 x86 jumpstart (grub) from Solaris 8 server

Similar Messages

Maybe you are looking for