[prev in list] [next in list] [prev in thread] [next in thread] 

List:       aix-l
Subject:    Re: unable to start nim alt disk install
From:       Frank Even <aixlists () ELITISTS ! ORG>
Date:       2009-07-08 16:27:48
Message-ID: 5d62325b0907080927k2ddf923bi3965e712112f7b33 () mail ! gmail ! com
[Download RAW message or body]

Finally success!!  Should've caught that client network config issue
long ago.  I'm losing it.  So very annoying....

On Wed, Jul 8, 2009 at 10:05 AM, Frank Even<aixlists@elitists.org> wrote:
> Yes, I did install the alt_disk filesets in the spot.
> 
> I also did try mounting nim exported filesystems locally and had no
> issue.  I've chased down name resolution issues in the past...but this
> didn't look like it.  Although...now w/ some sleep received and a
> renewed perspective...it looks like there is some funky IP
> configurations on this box I didn't pick-up on before...and it appears
> the IP I want is on ent1 while the def. route is on ent0.  Bah!  So it
> means all my remote boot attempts have probably been wrong and the
> remote mounts have probably been coming from the incorrect IP's.
> Trying again....
> 
> Thanks.
> 
> On Wed, Jul 8, 2009 at 9:46 AM, <jkstevenson@micron.com> wrote:
> > okay..
> > 
> > Name resolution can play a big part in this. If your system is defined in your \
> > NIM server as  aixXYZ, then when the request happens it must also resolve as \
> > aixXYZ .. not aixXYZ.domain.com. Why this happens? Nim can export filesystems \
> > based off of strict hostname or anonymous access. This is where I would look for \
> > a problem since your are failing to mount filesystems right off the bat. 
> > To check .. simply login to your nim server and verify the name the system has \
> > been defined as .. fully qualified or not fully qualified. Then from the nim \
> > server .. login remotely to the client.. issue the command "who am i" this will \
> > tell you what name the nim server is being resolved at from the client .. then \
> > remote again from the client back to the nim server and issue the command "who am \
> > i" this will tell you how the nim server resolves the name of the client. If a \
> > mismatch exists you can use the local hosts file to mitigate the problem. 
> > Jon
> > 
> > -----Original Message-----
> > From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of Frank \
> >                 Even
> > Sent: Tuesday, July 07, 2009 9:55 PM
> > To: aix-l@Princeton.EDU
> > Subject: unable to start nim alt disk install
> > 
> > I've tried multiple things...aside from reconfiguring major NIM
> > resources anyway...I can't seem to get this alt_disk_install to start.
> > I'm attempting to update an old standalone box from 5.2-08 to 5.3-07.
> > I'm attempting to do an alt_disk from the NIM server.  Any tried and
> > true hints?  Any good places to look for troubleshooting material?  I
> > can't for the life of me figure out where there could be any access
> > errors.  One thing that is odd is that the alt_disk doesn't seem to be
> > setting up the exports at all.  Well..at least not the SPOT /usr
> > resource.  I have to manually export that, then it seems some others
> > get setup when I try to start the alt_disk, but it still always fails
> > with the errors of the type below.
> > 
> > Command: failed        stdout: yes           stderr: no
> > 
> > Before command completion, additional instructions may appear below.
> > 
> > Initializing the NIM master.
> > Initializing NIM client nimclient.domain.com.
> > mount: 1831-011 access denied for nimsrv:/export/lpp_source/aix_5300-07-03
> > mount: 1831-008 giving up on:
> > nimsrv:/export/lpp_source/aix_5300-07-03
> > The file access permissions do not allow the specified action.
> > 0505-196 nimadm: Error mounting resource lpp_source_aix_5300-07-03 on client.
> > Cleaning up alt_disk_migration on the NIM master.
> > 
> 


[prev in list] [next in list] [prev in thread] [next in thread]