AIX

AIX

Connect with fellow AIX users and experts to gain knowledge, share insights, and solve problems.


#Power
 View Only
  • 1.  NIM mksysb catch-22

    Posted Mon April 07, 2008 05:56 PM

    Originally posted by: franabulax


    I'm trying to initiate a mksysb from my nim master.

    I used the command:

    nim -o define -t mksysb -a server=master -a source=duck -a mk_image=yes -a location=/export/images/mksysb.duck mksysb_duck

    /export/images exists and /export is mountable from master onto duck

    When the file /export/images/mksysb.duck does not exist, nim says that's an error, and it should exist.

    Ok, so I touch /export/images/mksysb.duck and re-run

    Nim says that the file /export/images/mksysb.duck has a type of S_IFREG but it wants S_IFDIR

    So I rm /export/images/mksysb.duck and mkdir /export/images/mksysb.duck and re-run the command

    Now Nim says that the file must be a regular file and not a directory.

    This seems like a bit of a catch-22. Is this a bug or did I get up too early this morning?

    Both machines are AIX 6.1

    Clues would be gratefully received.

    Thanks!
    #AIX-Forum


  • 2.  Re: NIM mksysb catch-22

    Posted Mon April 07, 2008 06:25 PM

    Originally posted by: esv


    <quote>

    I used the command:

    nim -o define -t mksysb -a server=master -a source=duck -a mk_image=yes -a location=/export/images/mksysb.duck mksysb_duck

    </quote>

    I have not played yet with 6.1's NIM yet but in 5.3 and before your command seems to be wrong.

    first, I don't see a source option for the define operation, that might have been added in 6.1. use : lsnim -q define -t mksysb to verify if source is part of the options.

    next, it seems to indicate that the mksysb file exists on system duck and that system is going to be used as NFS server, the NIM master must have direct execution access to duck in order to set it the NFS environment(via rsh or nimsh), if that were the case I'd say that the source and server options are mutually exclusive.

    if all you want to do is to define a mksysb resource with mksysb_duck name and your backup file resides in /export/images/mksysb.duck on the NIM master all you need to do is the following:

    nim -o define -t mksysb -a server=master -a mk_image=yes -a location=/export/images/mksysb.duck mksysb_duck

    As I said, I haven't played with NIM 6.1 yet, so I might be wrong.

    best regards,
    esv.

    Message was edited by: Enrique Sanchez
    #AIX-Forum


  • 3.  Re: NIM mksysb catch-22

    Posted Mon April 07, 2008 07:30 PM

    Originally posted by: esv


    rofl, I just checked the command again and the "source" option is there.. let me check your post again...

    regards,
    esv.
    #AIX-Forum


  • 4.  Re: NIM mksysb catch-22

    Posted Mon April 07, 2008 07:32 PM

    Originally posted by: franabulax


    Thanks, Enrique.

    The command appears pretty much as I used it in SG24-7296 "NIM from A to Z in AIX 5L" on pg. 349

    It's supposed to create the mksysb from duck as well as defining the resource in nim.

    I can talk to duck via rsh.

    I'll try as you suggest and separate the creation of the nim resource and the mksysb.

    Thanks again,

    Regards,

    Mike
    #AIX-Forum


  • 5.  Re: NIM mksysb catch-22

    Posted Mon April 07, 2008 07:45 PM

    Originally posted by: esv


    try removing /export filesystem from the exports list, NIM might be trying to export a subdirectory and since the parent directory is already exported it won't work well with NIM.

    regards,
    esv.
    #AIX-Forum