Re: mksysb NIM ressource on a nfs mounted filesystem

From: 0xDEADABE (none_at_nowhere.net)
Date: 11/27/05

  • Next message: Dmitri Pasyutin: "Re: Power 5 p570 problem when service processor fails" 
    Date: Sun, 27 Nov 2005 09:22:39 -0500

    Hajo Ehlers wrote:
    > sgeigenmueller@hotmail.com wrote:
    >
    >>Hi all,
    >>
    >>I have the mksysb images of a lot of aix servers stored locally on a
    >>harddisk of the NIM master. It's no problem to define them as NIM
    >>ressources there. But I have also a few images stored remotely (because
    >>of too low bandwidth of the connections) and the filesystems are
    >>mounted via nfs on the master - so "it looks like" stored locally too.
    >>But when I try to define the images there as ressources I always get
    >>the error
    >>
    >>the file ... has a vfstype of 18. This conflicts with the expected
    >>vfstype, which is one of the following: 0 3
    >>
    >>is there any way to define these images as mksysb ressources too? Maybe
    >>any add. option?
    >>I found something at a french website about /usr/include/sys/vmount.h,
    >>but I my french isn't good enough. :-/
    >
    >
    > NIM only supports JFS and JFS2. The point is that NIM uses NFS to
    > export its resource and exporting an NFS mount is not possible.
    >
    > So define a mksysb resource on a remote server.
    > smitty nim
    > -> Perform NIM Administration Task
    > --> Manage Resources
    > ---> Define a Resource
    > ----> Select: mksysb = a mksysb image
    > -----> Select : Server of Resource
    >
    > This means that the resource definition is still on the NIM master but
    > the remote server will serve the resource.
    >
    > Also its good to read a redbook about nim. ( Search for NIM on
    > http://www.redbooks.ibm.com )
    >
    > hth
    > Hajo
    >

    Just out of curiosity, have you attempted to boot any of these images on
    one of your NIM clients? This is a process I haven't been able to
    master as of yet, and am curious if anybody has, and what their process
    to do so was. I have gotten good at setting up the clients, and making
    the images, but haven't been able to boot the images after I make them.
      I believe I am missing something simple, but haven't had the time to
    spend on it.

    Also, don't look for any great information in a Redbook about NIM. The
    one that is out there was written for 4.3.3, and the subtle differences
    has the potential to drive one mad.

  • Next message: Dmitri Pasyutin: "Re: Power 5 p570 problem when service processor fails"

    Relevant Pages

    • Re: Help with Mksysb/Sysback Chapter for OReilly Book?
      ... mksysb with an NFS mount instead of a tape. ... -L is for creating DVD-sized images (else, without it, CD-sized ... -P is for create PP mapping during mksysb/savevg run that mkcd ... I've never really used NIM much to do mksysb restores, ...
      (comp.unix.aix)
    • Re: NIM server for DPLAR systems
      ... you only true concern is where the mksysb is located. ... The NIM ... server is just a tool to put the mksysb back on the box. ... I would recommend that you do regular "rsavevg" of the rootvg and any ...
      (AIX-L)
    • Re: Mksysb image question
      ... thinking of plaing the mksysb image in a NIM server. ... We keep 2 copies on separate disk systems and backup 2x per ...
      (comp.unix.aix)
    • Re: mksysb NIM ressource on a nfs mounted filesystem
      ... It's no problem to define them as NIM ... But I have also a few images stored remotely (because ... So define a mksysb resource on a remote server. ...
      (comp.unix.aix)
    • Re: write mksysb to tape after the fact
      ... patch level on on the tape (for example an AIX 5.3.00 CD and a mksysb ... There's something going on with the networking on the NIM ... How to make a bootable installable mksysb tape from a mksysb image on ...
      (comp.unix.aix)