NIM Install Boot Code: 888 102 700 C20 Post: 302901666

Sponsored Content

Operating Systems AIX NIM Install Boot Code: 888 102 700 C20 Post 302901666 by Devyn on Wednesday 14th of May 2014 09:53:04 PM

05-14-2014

Registered User

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:

Code:

710tl03sp2lpp_res        resources       lpp_source
710tl03sp2spot_res      resources       spot

The 888 102 700 C20 appears when loading the kernel (the bootp and tftp transfer appears to complete fine):

Code:

# lsnim -l vm02
emglab02:
   class          = machines
   type           = standalone
   connect        = nimsh
   platform       = chrp
   netboot_kernel = 64
   if1            = network1 vm02 0
   net_settings1  = auto full
   cable_type1    = tp
   Cstate         = BOS installation has been enabled
   prev_state     = ready for a NIM operation
   Mstate         = not running
   boot           = boot
   lpp_source     = 710tl03sp1lpp_res
   nim_script     = nim_script
   spot           = 710tl03sp1spot_res
   cpuid          = 000CDF4ED600
   control        = master
#

How can I run stuff in debug mode or access the kernel messages during initial network NIM boot to get more information on the error? How can I get more information as to what's wrong or what is happening here?

The 7100-03-02 lpp was defined based on AIX 7100-03-00 DVD image then the copied lpp_res was updated using the fixpack bff's (to 7100-03-02). That process completed without an issue and checks on the spot/lpp were fine.

Cheers,
DH

Last edited by Franklin52; 05-15-2014 at 05:13 AM.. Reason: Please use code tags

Devyn

View Public Profile for Devyn

Find all posts by Devyn

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

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

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

4. AIX

RS/6000 error 888

I have a friend who has the following error message on his LED: 888-102300-0C5 I've tried searching, but can't find anything. Any ideas? tks.

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

6. AIX

NIM client boot problem

Hi all, I have created VIO Server which serves 3 lpars. All of them are on VLAN ID 50. From one lpar I installed and set up NIM master server called testAIX1. I have created client and allocated resources to it: testAIX1:/ > lsnim -l test_lpar test_lpar: class = machines ...

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

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

LEARN ABOUT HPUX

hp9000s400

machid(1)						      General Commands Manual							 machid(1)

NAME

       machid: hp9000s200, hp9000s300, hp9000s400, hp9000s500, hp9000s700, hp9000s800, hp-mc680x0, hp-pa, pdp11, u370, u3b, u3b10, u3b2, u3b5, vax
       - provide truth value about processor type

SYNOPSIS

DESCRIPTION

       The following commands return a true value (exit code 0) if the a processor type matches the command name.  Otherwise a false  value  (exit
       code  nonzero)  is returned.  These commands are commonly used within makefiles and shell procedures to improve portability of applications
       (see make(1)).

				       +-----------+-------------------------++--------+--------------------------+
				       |Command    | True for		     ||Command | True for		  |
				       +-----------+-------------------------++--------+--------------------------+
				       |hp9000s200 | Series 200 	     ||pdp11   | PDP-11/45 or PDP-11/70   |
				       |hp9000s300 | Series 300 	     ||u3b     | 3B20 computer		  |
				       |hp9000s400 | Series 400 	     ||u3b2    | 3B2 computer		  |
				       |hp9000s500 | Series 500 	     ||u3b5    | 3B5 computer		  |
				       |hp9000s700 | Series 700 	     ||u3b10   | 3B10 computer		  |
				       |hp9000s800 | Series 800 or 700	     ||u370    | IBM System/370 computer  |
				       |hp-mc680x0 | Series 200, 300, or 400 ||vax     | VAX-11/750 or VAX-11/780 |
				       |hp-pa	   | Series 700 or 800	     ||        |			  |
				       +-----------+-------------------------++--------+--------------------------+
EXAMPLES

       Given a shell script that must behave differently when run on an HP 9000 Series 700 or 800 system, select the correct code  segment  to	be
       executed:

WARNINGS

       always  returns	true on both Series 800 and Series 700 systems.  Therefore, when using this command in scripts to determine hardware type,
       always use both and in the appropriate sequence to ensure correct results (see

       machid(1) will no longer provide support for future machines beyond the Series 800 and Series 700 systems.  Decisions should  be  based	on
       the hardware and software configuration information returned by getconf(1).

SEE ALSO

       getconf(1), make(1), sh(1), test(1), true(1).

																	 machid(1)