Sponsored Content
Full Discussion: OS install from NIM fails
Operating Systems AIX OS install from NIM fails Post 302502698 by kah00na on Tuesday 8th of March 2011 04:08:40 PM
Old 03-08-2011
I'd guess you don't have your NIM server's IP set correctly, you are configuring your network on a card that is not plugged in or not on the right network, or there is something blocking the ping from reaching your NIM server because of this:
Quote:
A remote host refused an attempted connect operation
 

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

Install qt-3.3.8 from sources, and fails with -thread

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

SCO 6.0 Install fails

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

NIM install hangs on LED 0608

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

SCO 6.0 MP 3 USB-UDI install fails

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

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

7. Solaris

Solaris 10 install fails on sparc

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

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

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

10. AIX

NIM Install Boot Code: 888 102 700 C20

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
bootadm(1M)															       bootadm(1M)

NAME
bootadm - manage bootability of GRUB-enabled operating system SYNOPSIS
/sbin/bootadm update-archive [-vn] [-R altroot] /sbin/bootadm list-archive [-vn] [-R altroot] only /sbin/bootadm set-menu [-R altroot] key=value /sbin/bootadm list-menu [-R altroot] The bootadm command manages the boot archive and GRUB (GRand Unified Bootloader) menu. The update-archive option provides a way for user to update the boot archive as a preventative measure or as part of the recovery procedure. The set-menu subcommand allows you to switch the auto-boot timeout and default boot entry in the GRUB menu. The list-menu subcommand displays the location of the GRUB menu and the current GRUB menu entries. While the typical location of the GRUB menu is /boot/grub/menu.lst, depending on the install method used the active GRUB menu might be located somewhere else. Use the list-menu subcommand to locate the active GRUB menu. For example, if a system was installed using Live Upgrade, the GRUB menu might not be located in the current boot environment. See the section for typical output from the list-menu option. Note that a SPARC system does not have the concept of a boot archive. The bootadm command on a SPARC system is intended for managing disk- less clients. SUBCOMMANDS
The bootadm command has the following subcommands: update-archive Updates current boot archive if required. Applies to both SPARC and platforms. list-archive Lists the files and directories to be included in the boot archive. Applies to both SPARC and platforms. set-menu Maintain the GRUB menu. The current GRUB menu is boot/grub/menu.lst, relative to root. Do not depend on this location, because it is subject to change. Applies to platforms only. list-menu Lists the location of the active GRUB menu, as well as the current GRUB menu entries. This includes the autoboot-timeout, the default entry number, and the title of each entry. Applies to platforms only. The bootadm command has the following options: -v In an update-archive operation, stale files are displayed on stderr. -n In an update-archive operation, archive content is checked but not updated. -R altroot Operation is applied to an alternate root path. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). key=value Possible values are: default=entrynum The item number (for example, 0, 1, or 2) in the GRUB menu designating the operating system to boot when the timer expires. timeout=seconds The number of seconds before the operating system designated by the default item number is booted. If the value is -1, auto boot is disabled. Example 1: Updating the Current Boot Archive The following command updates the current boot archive: # bootadm update-archive Example 2: Updating the Boot Archive on an Alternate Root The following command updates the boot archive on an alternate root: # bootadm update-archive -R /a Example 3: Listing Installed OS Instances The following command lists the installed operating system instances in a GRUB menu: # bootadm list-menu default=0 timeout=10(0) Solaris10(1) Solaris10 Failsafe(2) Linux Example 4: Switching Default Boot Entry The following command refers to the menu displayed in the previous example. The user selects Linux (item 2). # bootadm set-menu default=2 Example 5: Listing GRUB Menu Entries and Location of GRUB Menu The following command lists the GRUB menu entries and the location of the GRUB menu: # bootadm list-menu The location for the active GRUB menu is: /stubboot/boot/grub/menu.lst default 0 timeout 10 0 Solaris10 1 Solaris10 failsafe 2 Linux Example 6: Displaying Location of GRUB Menu The following command displays the location of the GRUB menu: # bootadm list-menu The location for the active GRUB menu is: /dev/dsk/c0t1d0s0 (not mounted) The filesystem type of the menu device is <ufs> default 2 timeout 10 0 c0t1d0s3 1 c0t1d0s3 failsafe 2 Solaris10 3 Solaris10 failsafe In this example, the active GRUB menu is located on a device which is not mounted. To access the GRUB menu, mount the device and access the GRUB menu at <mountpoint>/boot/grub/menu.lst. The following exit values are returned: 0 The command completed successfully. 1 The command exited due to an error. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ boot(1M), installgrub(1M), attributes(5) The GRUB home page: http://www.gnu.org/software/grub/ 10 Oct 2005 bootadm(1M)
All times are GMT -4. The time now is 11:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy