Wednesday, May 8, 2013

How to perform the VIO Migration using NIM?


How to perform the VIO Migration using NIM? 


The key prerequisites to perform the migration are:


•        The system must be managed by HMC version 7 or later
•        The virtual IO server must be at least at version 1.3.
•        The physical volume for rootvg must be assigned to the VIO


Below steps can be done at anytime before VIOS Migration:

          #mount nim_master:/images /mnt/
          #backupios -file /mnt/<hostname>/`hostname`.mksysb_date -mksysb
          #viosbr -backup –file /mnt/<hostname>/`hostname`.viosbr
          
Take the configuration files like lsmap,lspv,lspath ....for our future reference. 


Create the resource for your VIO on NIM Server
         
          VIOS_MIG_21_lpp          resources       lpp_source
          VIOS_MIG_21_spot         resources       spot


Define the machine using ---> "smitty nim_mkmac"

Prepare the nim master for installaiton ---> "smitty nim_bosinst"


Steps to Migrate the VIOS:

Note: Make sure all the client LPAR related to the VIOS are shutdown.

Step 1: Shutdown the VIOS Partition and Activate the VIOS Partition in SMS mode via HMC.
Step 2: From the SMS menu on the console, follow this procedure:


SMS - SYSTEM MANAGEMENT SERVICES -

1. Select Language
2. Change Password Options
3. View Error Log
4. Setup Remote IPL (RIPL (Remote Initial Program Load))
5. Change SCSI Settings
6. Select Console
7. Select Boot Options


4. Setup Remote IPL (RIPL (Remote Initial Program Load))

Next you’ll have a selection of adapters to use. Select your adapter that corresponds to the adapter/host you defined in NIM. You will not see “ent0/ent1...etc” options. You will however see the hardware addresses and slots.

We then are brought to 3 options :
1. IP Parameters
2. Adapter Configuration
3. Ping Test

Chose the option 1 to set the IP Parameters

Now we need to set our IP Parameters.
1. Client IP Address [###.###.###.###]
2. Server IP Address [###.###.###.###]
3. Gateway IP Address [###.###.###.###]
4. Subnet Mask [###.###.###.###]

After setting the IP Addresses use ‘M’ to return to the main menu. You typically do not want to go into the “Adapter Parameters” (option 2 on the previous screen) to change the adapter parameters or disable spanning tree.

Also, with the Ping Test.... 

With our IP Parameters set we should now be back at the main menu.
 

SMS - SYSTEM MANAGEMENT SERVICES -
 
1. Select Language
 
2. Change Password Options
 
3. View Error Log
 
4. Setup Remote IPL (RIPL (Remote Initial Program Load))
 
5. Change SCSI Settings
 
6. Select Console
 
7. Select Boot Options
 

Now we’re ready to select our boot device.
 
7. Select Boot Options
 

The next menu should come up :
 
1. Select Install or Boot Device
 
2. Configure Boot Device Order
 
3. Multiboot Startup
 

You can take either option 1 which will make this a 1 time boot device selection,
.
1. Select Install or Boot Device

Select Device Type :
1. Diskette
2. Tape
3. CD/DVD
4. IDE
5. Hard Drive
6. Network
7. List all Devices

select : 

7. List all Devices

The system will go out for you and scan itself to determine which devices are available to boot from. All of your available boot devices will be displayed here. The menu can be a little tricky here. If you have a device pre-selected it will have a 1 next to it under the “Current Position” column. Use the “Select Device Number” listing to choose the device you want to boot from.

The next screen will offer you three choices :
1. Information
2. Normal Mode Boot
3. Service Mode Boot

Select :
2. Normal Mode Boot 

It shouldn’t really matter if you select normal or service mode, I always select normal mode.  Finally it asks if you’re sure you want to exit from SMS. Select ‘yes’ and let the boot go.

What you SHOULD see :
You’ll likely see a brief splash screen then the bootp request attempt.
Ideally you’ll see something like :
BOOTP : S=1 R=1

Which indicates it sent and received a request successfully. 


once the migration done, you will get a login prompt.  Follow the below for confirm the successful VIO migration.


$ ioslevel   
$ lsmap -all 
$ lstcpip

-------------------------------------------------------------------------------------

For updating the VIO server (For example: 2.1 to 2.2)

$ updateios –commit    (To confirm that there are no uncommitted updates)
$ updateios -accept -install -dev /vio_update_package    (To update the vio)