5
1. HOW to restore a mksysb image using NIM master 1. Assumptions: 1. The client is defined on the NIM master PRDOP01 and the client's hostname and IP address are listed in the /etc/hosts file. 2.. The intended client is a pseries lpar. If the client is a B80, the NIM IPL menus will be similar, but there may be some differences. 3. The mksysb image has been transferred or restored from TSM and resides in the PRDOP01:/export/nim/mksysb. The size and sum command output match that from the source mksysb image. 2. Create a mksysb resource: Smit nim_mkres --- You should see a "Resource type" lsiting disppalyed. Scroll through the menu list and select mksysb. Hit enter and you will see menu below: Define a Resource Type or select values in entry fields. Press Enter AFTER making all desired changes. [TOP] [Entry Fields] * Resource Name [] < name > : NIM_test_Lamclient * Resource Type mksysb * Server of Resource [] master + * Location of Resource [] /export/nim/mksysb/test_lamclient.mksysb.0 ie List the absolute filename / Comments [] Source for Replication [] + -OR- System Backup Image Creation Options: CREATE system backup image? no +

NIM Restore

Embed Size (px)

Citation preview

Page 1: NIM Restore

1. HOW to restore a mksysb image using NIM master

1. Assumptions:

1. The client is defined on the NIM master PRDOP01 and the client's hostname and IP address are listed in the /etc/hosts file. 2.. The intended client is a pseries lpar. If the client is a B80, the NIM IPL menus will be similar, but there may be some differences.3. The mksysb image has been transferred or restored from TSM and

resides in the PRDOP01:/export/nim/mksysb. The size and sum command output match that from the source mksysb image. 2. Create a mksysb resource:

Smit nim_mkres --- You should see a "Resource type" lsiting disppalyed.

Scroll through the menu list and select mksysb. Hit enter and you will see menu below:

Define a Resource

Type or select values in entry fields.Press Enter AFTER making all desired changes.

[TOP] [Entry Fields]* Resource Name [] < name > : NIM_test_Lamclient* Resource Type mksysb* Server of Resource [] master +* Location of Resource [] /export/nim/mksysb/test_lamclient.mksysb.0 ie List the absolute filename / Comments []

Source for Replication [] + -OR- System Backup Image Creation Options: CREATE system backup image? no + NIM CLIENT to backup [] + PREVIEW only? no + IGNORE space requirements? no +[MORE...10]

Leave remaining fields blank since we are restoring only from specific mksysb image ( ie we are not replicating the image nor are we running a mksysb from this Smit panel).

3. Prepare Bosinstall on client:

a. Run smit nim_tasks and display smit menu....

Select Install and Update Software and press enter: Then select the Install the Base Operating System on Standalone Clients b. Select the target definition ( ie the client which will be restored).

Page 2: NIM Restore

c. Selec t the installation type: rte or mksysb or SPOT - select mksysb

d. Select the mksysb resource which you created in step e. Select the SPOT for the restore / installation.

f. The entire bos_inst smit panel should now displayed: You must select the LPP_SOURCE and make other changes shown in blue.

LPP_SOURCE [AIX53ML5_LPP] + MKSYSB mksysb_devxi01

BOSINST_DATA to use during installation [] + IMAGE_DATA to use during installation [] + RESOLV_CONF to use for network configuration [] + Customization SCRIPT to run after installation [] + Customization FB Script to run at first reboot [] + ACCEPT new license agreements? [yes] + Remain NIM client after install? [yes] + PRESERVE NIM definitions for resources on [yes] + this target?

FORCE PUSH the installation? [no] +

Initiate reboot and installation now? [no] + -OR- Set bootlist for installation at the [no] + next reboot?

Additional BUNDLES to install [] + -OR- Additional FILESETS to install [] + (bundles will be ignored)

installp Flags --- This field displays installp option flags and gets filled out only if you are installing "Additional FILESETS".

4. NIM server check for correct clientt setup and start: a. Check the subserver bootps is active - lssrc -t bootps

Service Command Description Status bootps /usr/sbin/bootpd bootpd /etc/bootptab active

b. Check the subserver tftp is active - lssrc -t tftpService Command Description Status tftp /usr/sbin/tftpd tftpd -n active

c. Tail /etc/bootptab and should see the client network info listed per example below:

testlpar:bf=/tftpboot/testlpar:ip=167.191.120.55:ht=ethernet:sa=167.191.120.120:sm=255.255.255.0:

d. Showmount -e -----> should list 3 filesystems being NFS exported to the client ( testlpar):

/export/nim/lpp_source/AIX53_ML5 testlpar

Page 3: NIM Restore

/export/nim/mksysb/devxi01.mksysb.0 testlpar/export/nim/scripts/testlpar.script testlpar

5. Boot client into SMS mode either using HMC or terminal server or onsite ascii terminal.Option 2Setup Remote IPL (Initial Program Load)

Select Ethernet AdapterUse the slot configuration info from previous step.

Select 1IP Parameters--- NIM Server: PRDOP01_TMP -- 167.191.120.243; Use server address for gateway address if both server and client are on same subnet.

Select 2 Adapter ConfigurationCheck Speed/Duplex ----- auto autoCheck Spanning Tree ----- enabledSelect mode and choose "standard" ( this is like choosing en0 instead of et0go back previous menuSelect 3Ping Test

Make sure you get a ping success; else, the NIM will fail. If ping failure, check the address info entered; check if the adapter is correct and if the adapter is connected into the network. When ping test OK, proceed to next step:

Go back to Main Menu and

Select 5Select Boot OptionsSelect 1 Select Install/Boot DeviceSelect 6NetworkSelect Adapter # from previous step.Select 2Normal Mode BootSelect 1 to Exit System Management Services

At this point, provided all has gone well, you should see the BOOTP packets increase until finally the system is able to load the minimal kernel, and start the NIM install, Once loaded, you reach the AIX install menu, from there you will chose the options to restore.