Use the lstcpip command to display the routing table

EXempty » Here is an example command.

lstcpip -routtable

Topic 2 - Part 2: Configure a VSCSI disk on the virtual I/O server

The purpose of this part is to create a VSCSI disk that will be used by a virtual I/O client partition. In the next part of this exercise you will create an LPAR that will use this VSCSI disk.

__ 34. Log in to the Virtual I/O Server, and verify that the VSCSI server adapter is available.

Also, using the lsmap command, check the mapping between physical, logical, and virtual devices. (There should not be any virtual target devices at this point.)

» The two commands you need to use are lsdev -virtual to find the name of the VSCSI server adapter, and lsmap -all to see any physical devices mapped to the VSCSI server adapter.

» Here is an example from the lsdev command output that shows the vhost0 adapter:

$ lsdev -virtual | grep SCSI

vhost0 Available Virtual SCSI Server Adapter » Here is example of the lsmap command output.

$ lsmap -all

SVSA Physloc Client Partition ID --- --- ---vhost0 U8233.E8B.1084AER-V1-C12 0x00000000

VTD NO VIRTUAL TARGET DEVICE FOUND

» Note the virtual adapter slot number that you defined when creating the VIOS partition.

__ 35. Now check to see that you have available disks on your VIOS partition. The number of disk devices visible will depend on the specific configuration of the systems being used for the class. It is expected that you should see eight hdisk devices in the output of the lsdev command. For example:

$ lsdev -type disk

name status description

hdisk0 Available MPIO Other FC SCSI Disk Drive hdisk1 Available MPIO Other FC SCSI Disk Drive

Course materials may not be reproduced in whole or in part

5-20 Power Virtualization I © Copyright IBM Corp. 2009, 2013

Each VIOS partition should be configured with two non-shared LUNs. If eight disks are visible, this means there are six shared LUNs visible in the VIOS. In some environments, there may be twelve shared LUNs visible on each VIOS.

__ 36. Now you must create a virtual target device that maps one FC SCSI physical disk to the VSCSI server adapter defined on your virtual I/O server. This virtual disk will be used for your AIX client LPAR operating system installation.

One LUN of 10 GB size has been defined during the lab setup for each student, and these LUNs have been assigned to all Fibre Channel adapters of your managed system (shared LUNs). This configuration will be needed for the next lab exercise (dual VIO server environment with MPIO setup).

Each student on a managed system will use one of these LUNs; this step and the information in Table 7 will determine the LUN assignment for each student.

__ a. First, check which physical hdisk devices are of 10 GB size. Execute the following script from your Virtual I/O Server CLI; it displays disk size in MB:

lsdev | grep hdisk | while read a b do

print "$a \c"

echo bootinfo -s $a | oem_setup_env done

Here is an output example; hdisk1 to hdisk6 are 10 GB in size.

hdisk0 30720

__ b. Record the hdisk numbers reported as 10 GB in ascending order in the following table. For example, based on the previous command output, record hdisk1 in the first row, hdisk2 in the second row, and so forth, up to hdisk6 in the last row.

Table 7: hdisk name for student allocation 10 GB size hdisk

EXempty __ c. Select from the table the hdisk that you will use as a backing device for your client partition; for example, based on the previous command output:

• student1 uses hdisk1 • student2 uses hdisk2 • student3 uses hdisk3 • and so on

The normal lab setup for this class has six students sharing a single managed system. When the class has twelve students, student 7 to student 12 are configured on a second managed system. Each managed system has a

separate set of six shared LUNs, so the 10 GB devices visible to students 1 to 6 are separate from the set of devices visible to students 7 to 12.

__ d. Run the following command: lsdev -dev hdisk# -attr | grep lun_id (where hdisk# is your selected disk), and write down the unique lun_id.

lun_id: ________________________________________________________

» Here is an example of the command and output.

$ lsdev -dev hdisk3 -attr | grep lun_id

lun_id 0x3000000000000 Logical Unit Number ID False Note

The hdisk name (hdiskX) is defined during the configuration sequence (cfgmgr), and the associated disk number is related to the configuration order. The configuration is done in order of increasing lun_id values of the LUNs assigned to the Fibre Channel adapter.

You can run the following command: lsdev -dev hdisk# -attr | grep lun_id This will show you the unique lun_id for the related LUN.

__ 37. Modify the reserve_policy parameter of your 10 GB disk devices from single_path to no_reserve. These modifications are needed for the next exercises (MPIO setup in a dual VIOS environment), and cannot be performed when the disk is in use. Run the following command for this hdisk of 10 GB:

$ chdev -dev <hdisk#> -attr reserve_policy=no_reserve __ 38. Create the virtual target device using the following command:

Course materials may not be reproduced in whole or in part

5-22 Power Virtualization I © Copyright IBM Corp. 2009, 2013

__ 39. List your virtual adapter device mapping by using the lsmap command. View the