03-08-2011
Check DNS and network setup
10 More Discussions You Might Find Interesting
1. AIX
Has anyone ever done this and is it easy to do with SLES9/10? All I can find so far is this link
http://www-941.ibm.com/collaboration/wiki/display/Wikip5/16Jan07+Using+NIM+to+Install+VIO+and+Linux
Can you still use all the feature of autoyast etc?
TIA. (1 Reply)
Discussion started by: backslash
1 Replies
2. BSD
This is my problem:
I am logged in as root, and the location is:
/usr/local/qt (which is qt-X11-free-3.3.8 sources)
./configure -thread (which ends ok)
/usr/bin/make
and I got this error
----------------------------------
cd designer && make -f Makefile
/usr/local/qt/bin/uic -L... (0 Replies)
Discussion started by: mihk
0 Replies
3. SCO
Anybody have a problem installing version 6 on a machine with a Mylex DAC960 host adapter. Everything runs as normal until the kernel is relinked at the end of the install process. The kernel re-link fails with the message that it cannot find the scsi driver (dak) in this case. (3 Replies)
Discussion started by: jgt
3 Replies
4. AIX
Hi guys,
I am trying to install a new machine via nim but it is hanging on 0608 => it should be a network issue
here the situation hoping you will be able to help:
server NIM on a subnet/IP 10.36.12.64
client on 161.43.56.25
the ping test is successful but when I launch the isntall it... (9 Replies)
Discussion started by: touny
9 Replies
5. SCO
Hi All,
When I install SCO 6.0 maintenance package 3 I get some mails:
Message 338:
From root Tue Nov 20 12:39:15 2007
From: Superuser <root@hocopart.hocoparts.local>
X-Mailer: SCO OpenServer 6.0.0 Mail
To: root@hocopart.hocoparts.local
Date: Tue, 20 Nov 2007 12:39:15 +0100 (CET)... (0 Replies)
Discussion started by: frederik1
0 Replies
6. AIX
I was trying to install bos.sysmgt.nim.master on AIX 5.1 with a mounted NFS source, but it failed:
# installp -agXd /nfs/aix51cd1 bos.sysmgt.nim.master
installp: APPLYING software for:
bos.sysmgt.nim.master 5.1.0.50
restore: 0511-123 The volume on... (0 Replies)
Discussion started by: ezlee
0 Replies
7. Solaris
I'm trying to do an upgrade/install from Solaris 8 to Solaris 10 on a SUN Sparc system.
I halt the system, as documented, but when I attempt to boot off the distribution DVD; i.e.
halt
:
:
OK> boot cdrom
The system indicates that the device is 'unrecognizable'
These are SUN... (5 Replies)
Discussion started by: imagtek
5 Replies
8. AIX
Hello,
Is it possible to install up-to-date vios in one NIM operation ?
For example I have vios v2.1 DVD and current vios version is v2.2.1.3(we update to fixpack v2.2.1.1_FP25 and apply service pack 2.2.1.3-FP25-SP01)
I know it's possible if we install AIX using NIM - we just update... (0 Replies)
Discussion started by: vilius
0 Replies
9. AIX
I want to install single RPM from LPP on NIM system without doing it interactively (with single non-interactive command), so I 'got' that command from smitty this way:
# smitty nim > Install and Update Software > Install Software
Select the LPP_SOURCE containing the install images
>... (5 Replies)
Discussion started by: n.i.b
5 Replies
10. AIX
I've got code: 888 102 700 C20 when starting a NIM install. (Tried the online search results and it hasn't worked)
The OS is AIX 7100-03-02. The lpp_source and spot were defined as such:
710tl03sp2lpp_res resources lpp_source
710tl03sp2spot_res resources spot
The... (4 Replies)
Discussion started by: Devyn
4 Replies
LEARN ABOUT NETBSD
ndbootd
NDBOOTD(8) BSD System Manager's Manual NDBOOTD(8)
NAME
ndbootd -- Sun Network Disk (ND) Protocol server
SYNOPSIS
ndbootd [-s boot2] [-i interface] [-w windowsize] [-d] boot1
DESCRIPTION
ndbootd is a server which supports the Sun Network Disk (ND) Protocol. This protocol was designed by Sun before they designed NFS. ND sim-
ply makes the raw blocks of a disk available to network clients. Contrast this with the true namespace and file abstractions that NFS pro-
vides.
The only reason you're likely to encounter ND nowadays is if you have an old Sun 2 machine, like the 2/120 or 2/50. The Sun 2 PROMs can only
use ND to boot over the network. (Later, the Sun 3 PROMs would use RARP and TFTP to boot over the network.)
ndbootd is a very simple ND server that only supports client reads for booting. It exports a disk that the clients consider to be /dev/ndp0
(ND public unit zero). The disk is available only to clients that are listed in /etc/ethers and have valid hostnames. (Sun 2 PROMs don't do
RARP, but they do learn their IP address from the first ND response they receive from the server.)
boot1 is a file containing the mandatory first-stage network boot program, typically /usr/mdec/bootyy. The layout of the exported disk is:
o block 0: normally a Sun disklabel (but ignored by the PROM)
o blocks 1-15: the first-stage network boot program
With the -s boot2 option, ndbootd will also make a second-stage network boot program available to clients, typically /usr/mdec/netboot. When
boot2 is a filename, that file is the single second-stage network boot program to be served to all clients.
When boot2 is a directory name, typically /tftpboot, ndbootd finds a client's second-stage network boot program by turning its IP address
into a filename in that directory, in the same manner later Sun 3 PROMs do when TFTPing (i.e., if a client has IP address 192.168.1.10,
ndbootd expects to find /tftpboot/C0A8010A.SUN2 ).
When used in this last manner with an ND-aware first-stage boot program, ndbootd serves the same purpose in the Sun 2 netboot process as
tftpd(8) serves in the Sun 3 netboot process.
Any second-stage network boot program always begins at block 16 of the exported disk, regardless of the length of the first-stage network
boot program.
All first- and second-stage network boot programs must have all executable headers stripped off; they must be raw binary programs.
The remaining options are:
-i interface
Only listen for ND clients on interface interface. Normally ndbootd listens for clients on the first non-loopback IP interface
that is up and running.
-w windowsize
This adjusts the window size of the ND protocol. This is the number of 1-kilobyte packets that can be transmitted before waiting
for an acknowledgement. Defaults to 6.
-d Run in debug mode. Debugging output goes to standard error and the server will not fork.
FILES
/etc/ethers
/etc/hosts
SEE ALSO
tftpd(8)
BUGS
Whether or not there is a second-stage network boot program, the exported disk appears to all clients to have infinite length. The content
of all blocks not used by the first- or second-stage network boot programs is undefined. All client reads of undefined blocks are silently
allowed by the server.
BSD
May 9, 2001 BSD