02-14-2008
Resolved
I found the problem in the menu.lst file.
To correct, I changed the following:
install_media=192.168.17.251:/export/home/jumpstart/install/solaris_10_2006_11/Solaris_10/
to:
install_media=192.168.17.251:/export/home/jumpstart/install/solaris_10_2006_11/
Issue resolved.
9 More Discussions You Might Find Interesting
1. Solaris
Hi
I just configured a jumpstart server for x86 and sparc clients. I don't use a dhcp server, so I configured /etc/ethers and did add_install_client to update /etc/bootparams. The sparc installation ist working, but the x86 installation stops after CD1 was successfully installed.
What I did:
I... (2 Replies)
Discussion started by: Jay_Fisi
2 Replies
2. Solaris
Does anyone know how to Jumpstart a Solaris 10 x86 system without the GUI?
I would like to keep the Jumpstart and/or Flash Archive install in a console text mode if possible but I've not had much luck finding instructions. I'm guessing this is going to be accomplished from the grub menu with a... (5 Replies)
Discussion started by: alias.256
5 Replies
3. Solaris
I am trying to find an approach that has been effective for automating the installation of Solaris 10 x86 using Jumpstart technology. I have configured an Jumpstart server and a Solaris dhcp server with appropriate macros for passing the client information about its boot environment. The problem is... (7 Replies)
Discussion started by: chajo19
7 Replies
4. Solaris
Can I use a Jumpstart enviroment on x86 to install a sparc64 client?
The idea is to install Solaris in an virtual environment (Sun Virtual Box) running on a pc (AMD), configure a Jumpstart server, and have a SUN Ultra 60 (sparc64) installed via the Jumpstart server.
The SUN has no cdrom... (4 Replies)
Discussion started by: eldiablo
4 Replies
5. Solaris
Hi All,
Is there a possible way to fully automate Solaris x86 jumpstart or make the x86 jumpstart unattended?
I'm currently checking the possible options on how can I do the x86 jumpstart to be kicked off during midnight.
We have an automated jumpstart (start to run from midnight) for... (2 Replies)
Discussion started by: racbern
2 Replies
6. Solaris
Hi friends ,
i have on ultra 10 Sparc machine . Due to some problem my OS is fully corrupted , so i am planning to install again but my problem is the cd drive in Ultra 10 machine is not working.
Now i am planning to use Jumpstart installation method to install my server.
But i... (4 Replies)
Discussion started by: vr_mari
4 Replies
7. Solaris
client boots fine, it gets the ip 192.168.0.10 and the bootfile. Then there is :
SunOS 5.10 Version Generic_141445-09 32-bit"
...
Configuring devices.
Custom JumpStart
Reading ZFS config: done
Setting up Java. Please wait ...
NOTE: Not enough memory for graphical installation. Graphical... (4 Replies)
Discussion started by: TomSu
4 Replies
8. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
9. Solaris
Installing Solaris x86 using jumpstart does not set the hostname for the target. Any idea where do we need to specify hostname to be set for jumpstart installation. (1 Reply)
Discussion started by: hemalsid
1 Replies
LEARN ABOUT FREEBSD
nos-tun
NOS-TUN(8) BSD System Manager's Manual NOS-TUN(8)
NAME
nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel
SYNOPSIS
nos-tun -t tunnel -s source -d destination -p protocol_number [source] target
DESCRIPTION
The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface.
Tunnel is the name of the tunnel device /dev/tun0 for example.
Source and destination are the addresses used on the tunnel device. If you configure the tunnel against a cisco router, use a netmask of
``255.255.255.252'' on the cisco. This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not
really implement.
Protocol number sets tunnel mode. Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org.
Target is the address of the remote tunnel device, this must match the source address set on the remote end.
EXAMPLES
This end, a FreeBSD box on address 192.168.59.34:
nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45
Remote cisco on address 192.168.56.45:
interface tunnel 0
ip address 192.168.61.2 255.255.255.252
tunnel mode nos
tunnel destination 192.168.59.34
tunnel source 192.168.56.45
AUTHORS
Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page. Isao SEKI
<iseki@gongon.com> added a new flag, IP protocol number.
BUGS
We do not allow for setting our source address for multihomed machines.
BSD
April 11, 1998 BSD