Sponsored Content
Operating Systems AIX NIM install hangs on LED 0608 Post 302124416 by touny on Saturday 30th of June 2007 03:45:24 PM
Old 06-30-2007
hi
yeah me again unfortunatly.

I have checked everything. My client.info exists and is correctly defined. I have read the code error that IBM put on the redbook NIM but as i said I have also run the tftpd with te option -v and on the syslog .log I have the error: Request Timeout.
So I am assuming it is a network issue ?
Thanks
 

10 More Discussions You Might Find Interesting

1. AIX

Linux install from NIM

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. AIX

AIX 5.1 install bos.sysmgt.nim.master failed

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

3. AIX

NIM client installation hangs at 0608

Hi All, I am facing very strange problem. I have created NIM server with 6.1 TL4SP3. I am having SPOT and MKsysb of the same version. I am able to install the client using this spot and mksysb. Now I got the requirement of installing the 5.3 ML11SP3 client. So using the mksysb of 5.3 ML11SP3, I... (3 Replies)
Discussion started by: falgun6666
3 Replies

4. Solaris

Solaris Cluster Install Hangs

Greetings Forumers! I tried installing Solaris Cluster 3.3 today. I should say I tried configuring the Cluster today. The software is already installed on two systems. I am trying to configure a shared filesystem between two 6320 Blades. I selected the "Custom" install because the "Typical"... (2 Replies)
Discussion started by: bluescreen
2 Replies

5. AIX

OS install from NIM fails

Hi Guys, The ping is failing SMS menu on the client to the interface for a network boot from NIM. I checked the cables, they are plugged in and lights are blinking. this is the error i am getting when I am pushing the OS on NIM Command: OK stdout: yes stderr: no ... (2 Replies)
Discussion started by: ithinksgreen
2 Replies

6. Solaris

10_Recommended patches install - hangs!

Got a Solaris 10 05/09 machine recently built. Trying to run installcluster --s10cluster like Ive done loads of times before. On this particular machine, it just sits there, no output on command line. Any ideas what to try to see whats going wrong? (3 Replies)
Discussion started by: paulfoel
3 Replies

7. AIX

NIM - install up-to-date VIOS ?

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

8. Red Hat

Install hangs on laptop

I have an older laptop the "management" wants me to use instead of buying something that works. Not an antique but a couple years old. An HP with Turion AMD CPU, ATI video. When I try to install in graphical mode, it hangs after package selection. Doesn't matter whether I select server or... (6 Replies)
Discussion started by: RocketGuy
6 Replies

9. AIX

NIM Restore hangs at the start

Hello Gurus, I have a couple of questions, I'm trying to do a mksysb restore from backup and it has just hung at the start. RS/6000 Firmware Version TCP05287 (c) Copyright IBM Corp. 2000 All rights reserved. -------------------------------------------------------------------------------... (8 Replies)
Discussion started by: elcounto
8 Replies

10. AIX

Install RPM from NIM LPP without smitty

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
TFTPD(8)						    BSD System Manager's Manual 						  TFTPD(8)

NAME
tftpd -- Internet Trivial File Transfer Protocol server SYNOPSIS
tftpd [-cdClnow] [-F strftime-format] [-s directory] [-u user] [-U umask] [directory ...] DESCRIPTION
The tftpd utility is a server which supports the Internet Trivial File Transfer Protocol (RFC 1350). The TFTP server operates at the port indicated in the 'tftp' service description; see services(5). The server is normally started by inetd(8). The use of tftp(1) does not require an account or password on the remote system. Due to the lack of authentication information, tftpd will allow only publicly readable files to be accessed. Files containing the string ``/../'' or starting with ``../'' are not allowed. Files may be written only if they already exist and are publicly writable. Note that this extends the concept of ``public'' to include all users on all hosts that can be reached through the network; this may not be appropriate on all systems, and its implications should be considered before enabling tftp service. The server should have the user ID with the lowest possible privilege. Access to files may be restricted by invoking tftpd with a list of directories by including up to 20 pathnames as server program arguments in inetd.conf(5). In this case access is restricted to files whose names are prefixed by the one of the given directories. The given directo- ries are also treated as a search path for relative filename requests. The -s option provides additional security by changing the root directory of tftpd, thereby prohibiting accesses to outside of the specified directory. Because chroot(2) requires super-user privileges, tftpd must be run as root. However, after performing the chroot(2) call, tftpd will set its user ID to that of the specified user, or ``nobody'' if no -u option is specified. The options are: -c Changes the default root directory of a connecting host via chroot(2) based on the connecting IP address. This prevents multiple clients from writing to the same file at the same time. If the directory does not exist, the client connection is refused. The -s option is required for -c and the specified directory is used as a base. -C Operates the same as -c except it falls back to directory specified via -s if a directory does not exist for the client's IP. -F Use this strftime(3) compatible format string for the creation of the suffix if -W is specified. By default the string "%Y%m%d" is used. -d, -d [value] Enables debug output. If value is not specified, then the debug level is increased by one for each instance of -d which is speci- fied. If value is specified, then the debug level is set to value. The debug level is a bitmask implemented in src/libexec/tftpd/tftp-utils.h. Valid values are 0 (DEBUG_NONE), 1 (DEBUG_PACKETS), 2, (DEBUG_SIMPLE), 4 (DEBUG_OPTIONS), and 8 (DEBUG_ACCESS). Multiple debug values can be combined in the bitmask by logically OR'ing the values. For example, specifying -d 15 will enable all the debug values. -l Log all requests using syslog(3) with the facility of LOG_FTP. Note: Logging of LOG_FTP messages must also be enabled in the syslog configuration file, syslog.conf(5). -n Suppress negative acknowledgement of requests for nonexistent relative filenames. -o Disable support for RFC2347 style TFTP Options. -s directory Cause tftpd to change its root directory to directory. After doing that but before accepting commands, tftpd will switch credentials to an unprivileged user. -u user Switch credentials to user (default ``nobody'') when the -s option is used. The user must be specified by name, not a numeric UID. -U umask Set the umask for newly created files. The default is 022 (S_IWGRP | S_IWOTH). -w Allow write requests to create new files. By default tftpd requires that the file specified in a write request exist. Note that this only works in directories writable by the user specified with -u option -W As -w but append a YYYYMMDD.nn sequence number to the end of the filename. Note that the string YYYYMMDD can be changed with the -F option. SEE ALSO
tftp(1), chroot(2), syslog(3), inetd.conf(5), services(5), syslog.conf(5), inetd(8) The following RFC's are supported: RFC 1350: The TFTP Protocol (Revision 2). RFC 2347: TFTP Option Extension. RFC 2348: TFTP Blocksize Option. RFC 2349: TFTP Timeout Interval and Transfer Size Options. The non-standard rollover and blksize2 TFTP options are mentioned here: Extending TFTP, http://www.compuphase.com/tftp.htm. HISTORY
The tftpd utility appeared in 4.2BSD; the -s option was introduced in FreeBSD 2.2, the -u option was introduced in FreeBSD 4.2, the -c option was introduced in FreeBSD 4.3, and the -F and -W options were introduced in FreeBSD 7.4. Support for Timeout Interval and Transfer Size Options (RFC2349) was introduced in FreeBSD 5.0, support for the TFTP Blocksize Option (RFC2348) and the blksize2 option was introduced in FreeBSD 7.4. Edwin Groothuis <edwin@FreeBSD.org> performed a major rewrite of the tftpd and tftp(1) code to support RFC2348. NOTES
Files larger than 33,553,919 octets (65535 blocks, last one <512 octets) cannot be correctly transferred without client and server supporting blocksize negotiation (RFCs 2347 and 2348), or the non-standard TFTP rollover option. As a kludge, tftpd accepts a sequence of block number which wrap to zero after 65535, even if the rollover option is not specified. Many tftp clients will not transfer files over 16,776,703 octets (32767 blocks), as they incorrectly count the block number using a signed rather than unsigned 16-bit integer. BSD
June 22, 2011 BSD
All times are GMT -4. The time now is 10:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy