Re: NIM restore on a system without a console



On 29 mrt, 23:37, dohhhh <4ge...@xxxxxxxxxxx> wrote:
uruk-hai wrote:
Is there anyone that can push me into the right direction?
Thanks in advance.

Mark

PUSH is the keyword my friend :-)
You have to set the "Force PUSH the installation" option to yes in the
nim"Install the base operating system on standalone client" menu.
Then you have to specify a bosinst.data file, and inside the
bosinst.data you set the prompt value to no ofcourse.

Gud luck!

OR, if the client is stilling running/available on the network, verify
the client can contact theNIMmaster (successful ping usually suffices
if theNIMnetwork/segment is different from the "public" segment that
you logged on over...then do the following the CLIENT): rm /etc/niminfo
and reconfigure it (never hurts even if there isn't one already) via
"smitnim" => configure...; once the /etc/niminfo file is rebuilt,
initiate aNIMinstall (aka, "pull" installation). When using "smit's"NIMinstallation screens, just make sure you select the correct source
and spot along with the "bosinst.data" resource/file and follow the
bouncing ball from that point on.

Depending on how loaded your network is (and the age of theNIMclient),
assuming the network is stable and the resources/spot was built
correctly, the migration install should be done in about 15 - 45
minutes. The last time I performed one was about 5 months ago from a
bunch of 520s. I was able to concurrently reload 5-10 clients/LPARs over
their 100 full duplexed interfaces in 15 minutes per node/LPAR!! Older
boxes like the 43Ps took around 30 minutes...so, YMMV depending on how
your network/s is/are configured and the age of client...HTH some :-}

Paul
p.s. Before starting the installation, you might also (from the client)
want to run "showmount -e NIM_MASTER_NAME" (NIM_MASTER_NAME = whatever
your master server's hostname is). If it shows resources allocated to
the client, you'll (probably) need to log onto the master and reset that
client's resources/allocation; otherwise, the installation will fail!
BOL2YOU!! PMS

Guys,

My problem is not how to use NIM in order to perform an installation
or the restore of a mksysb.
It's purely a matter of how to define the bosinst.data file to allow
the restore of a mksysb on a system without a (virtual) console
attached to it.

The fact remains that if you define an invalid console in the
'CONSOLE' stanza in the bosinst.data file, the installation falls back
from being non-prompted to a semi prompted state where it asks you to
define the console to use for the installation/restore.

My question is :

What do I have to define in the bosinst.data file in order to be able
to do a non-prompted restore onto a server that has no console (tty/
vty/lft) attached?
'Default' seems to be working for systems with a console only

Thanks!

Mark

.



Relevant Pages

  • Re: Client push question - the plot thickens
    ... for clients within the site boundaries of a secondary site are disseminated ... If Client Push is enabled at that site then the ... SMS 2003 and Advanced Client push installation behavior. ... secondary site unless the secondary site has both initiated discovery of the ...
    (microsoft.public.sms.admin)
  • Re: Office Installation Not Syncing to AIP
    ... We want to replace all files since we are reaching to a brand new AIP. ... To answer your question about whether or not you can tell how the client ... patches got installed. ... If the installation is in a "mixed state" the symptom that you usually see ...
    (microsoft.public.officeupdate)
  • Re: NIM restore on a system without a console
    ... You have to set the "Force PUSH the installation" option to yes in the ... nim"Install the base operating system on standalone client" menu. ... and spot along with the "bosinst.data" resource/file and follow the ... The fact remains that if you define an invalid console in the ...
    (comp.unix.aix)
  • Re: Advanced Client install nightmare
    ... I have previously successfully installed a client over the network, ... I can succesfully connect to the remote registry using the account. ... MVP Windows Server System - SMS ... account specified in the Client push installation properties. ...
    (microsoft.public.sms.admin)
  • Re: Office Installation Not Syncing to AIP
    ... to remove the clientside patches to fix the mixed state.. ... We want to replace all files since we are reaching to a brand new AIP. ... To answer your question about whether or not you can tell how the client ... If the installation is in a "mixed state" the symptom that you usually see ...
    (microsoft.public.officeupdate)