1.

Follow ITI_TIP_18099 V02 Technical Installation Plan for IBM Power Platform Virtual IO Server - Print
Screens, but instead of creating Virtual SCSI adapter, create Fibre Channel Adapter.

2. Follow the configuration as per Server Package Configuration.

 Make sure the fcs adapters you allocate are on different SAN fabrics, so the LUN’s are presented from
different SAN switches.

US2US00078 (VIO 1)
10000000c9e3d3ba fcs0 Fabric - A
10000000c9e3d3bb fcs1 Fabric - A
10000000c9e3d7ee fcs2 Fabric - B
10000000c9e3d7ef fcs3 Fabric - B

US2US00079 (VIO 2)
10000000c9e3d1c6 fcs0 Fabric - A
10000000c9e3d1c7 fcs1 Fabric - A
10000000c9e39ec6 fcs2 Fabric - B
10000000c9e39ec7 fcs3 Fabric - B
 VIO server 1 – US2US00078
# lscfg -vl fcs0 | grep Network
Network Address.............10000000C9E3D3BA
# lscfg -vl fcs1 | grep Network
Network Address.............10000000C9E3D3BB
# lscfg -vl fcs2 | grep Network
Network Address.............10000000C9E3D7EE
# lscfg -vl fcs3 | grep Network
Network Address.............10000000C9E3D7EF
#

VIO server 1 – US2US00079

# lscfg -vl fcs0 | grep Network
Network Address.............10000000C9E3D1C6
# lscfg -vl fcs1 | grep Network
Network Address.............10000000C9E3D1C7
# lscfg -vl fcs2 | grep Network
Network Address.............10000000C9E39EC6
# lscfg -vl fcs3 | grep Network
Network Address.............10000000C9E39EC7
#

FCS FCS VIO1 VIO2

Adapter Adapter Vfchost Adapter Adapter
VIO Servers Description VIO 1 VIO 2 ID ID ID Client LPAR VIO 1 WWPN VIO 2 WWPN

SAN Boot
us2us00078 & us2us00079 LUNs fcs0 fcs2 vfchost0 101 201 us2us00081 c0507604a9180020 c0507604a9180024
SAN Boot
us2us00078 & us2us00079 LUNs fcs1 fcs3 vfchost1 102 202 us2us00081 c0507604a9180022 c0507604a9180026

SAN Boot
us2us00078 & us2us00079 LUNs fcs0 fcs2 vfchost2 103 203 us2us00082 c0507604a9180028 c0507604a918002c
SAN Boot
us2us00078 & us2us00079 LUNs fcs1 fcs3 vfchost3 104 204 us2us00082 c0507604a918002a c0507604a918002e

SAN Boot
us2us00078 & us2us00079 LUNs fcs0 fcs2 vfchost4 105 205 us2us00083 c0507604a9180030 c0507604a9180034
SAN Boot
us2us00078 & us2us00079 LUNs fcs1 fcs3 vfchost5 106 206 us2us00083 c0507604a9180032 c0507604a9180036

SAN Boot
us2us00078 & us2us00079 LUNs fcs0 fcs2 vfchost6 107 207 us2us00084 c0507604a918003a c0507604a918003e
SAN Boot
us2us00078 & us2us00079 LUNs fcs1 fcs3 vfchost7 108 208 us2us00084 c0507604a918003c c0507604a9180038

SAN Boot
us2us00078 & us2us00079 LUNs fcs0 fcs2 vfchost8 109 209 us2us00085 c0507604a9180044 c0507604a9180040
SAN Boot
us2us00078 & us2us00079 LUNs fcs1 fcs3 vfchost9 110 210 us2us00085 c0507604a9180046 c0507604a9180042

3. At VIO server 1 – US2US00078

4. At VIO server 2 – US2US00079
5. At one of the LPARs – US2US00081

6. To check WWNPs for each Client Fibre Channel that has been assigned on each LPARs

Click at Adapter ID as per above image

A pop-up window will be displayed as per below
The first number is the WWPN, e.g. c0507604a9180020 (to be given to the Storage Team when
submitting SSM request for new SAN Boot LUN allocations)
Make sure you SAVE the profiles after dynamically adding the adapters, DON’T add them again (**usually using
Manage Profiles – Edit – Create – adapters). If you SAVE, the adapters will be automatically added at the profiles,
you just need to edit it to “Yes” for required during activation.

If you add them using **, you will have 2 different sets of WWNs – at Profiles and at the LPAR itself (using
command lscfg –vl fcsX | grep –i “Network Address”).

What you can do:

1. Shutdown the LPAR, activate – normal, the WWNs at Profiles should follow the WWNs as per # lscfg output.

7. Steps required at padmin layer example follows:

Complete fibre mappings on HMC VIO Server and Client LPAR’s

On each VIO as padmin:

$ lsmap -npiv –all

$ lsnports
name physloc fabric tports aports swwpns awwpns
fcs0 U5802.001.RCH9095-P1-C2-T1 1 64 64 2048 2047
fcs1 U5802.001.RCH9095-P1-C2-T2 1 64 64 2048 2047
fcs2 U5802.001.RCH6631-P1-C6-T1 1 64 64 2048 2047
fcs3 U5802.001.RCH6631-P1-C6-T2 1 64 64 2048 2047
$

$ cfgdev

$ lsmap -npiv -vadapter vfchost0

Name Physloc ClntID ClntName ClntOS
------------- ---------------------------------- ------ -------------- -------
vfchost0 U8233.E8B.10F8E0P-V1-C101 3

Status:NOT_LOGGED_IN
FC name: FC loc code:
Ports logged in:0
Flags:1<NOT_MAPPED,NOT_CONNECTED>
VFC client name: VFC client DRC:

$ vfcmap -vadapter vfchost0 -fcp fcs0

$
$ lsmap -npiv -vadapter vfchost0
Name Physloc ClntID ClntName ClntOS
------------- ---------------------------------- ------ -------------- -------
vfchost0 U8233.E8B.10F8E0P-V1-C101 3

Status:NOT_LOGGED_IN
FC name:fcs0 FC loc code:U5802.001.RCH9095-P1-C1-T1
Ports logged in:0
Flags:4<NOT_LOGGED>
VFC client name: VFC client DRC:

$
Sample commands used for this build.

On US2US00078;

vfcmap -vadapter vfchost0 -fcp fcs0

vfcmap -vadapter vfchost1 -fcp fcs1

vfcmap -vadapter vfchost2 -fcp fcs0

vfcmap -vadapter vfchost3 -fcp fcs1

vfcmap -vadapter vfchost4 -fcp fcs0

vfcmap -vadapter vfchost5 -fcp fcs1

vfcmap -vadapter vfchost6 -fcp fcs0

vfcmap -vadapter vfchost7 -fcp fcs1

vfcmap -vadapter vfchost8 -fcp fcs0

vfcmap -vadapter vfchost9 -fcp fcs1
On US2US00079;

vfcmap -vadapter vfchost0 -fcp fcs2

vfcmap -vadapter vfchost1 -fcp fcs3

vfcmap -vadapter vfchost2 -fcp fcs2

vfcmap -vadapter vfchost3 -fcp fcs3

vfcmap -vadapter vfchost4 -fcp fcs2

vfcmap -vadapter vfchost5 -fcp fcs3

vfcmap -vadapter vfchost6 -fcp fcs2

vfcmap -vadapter vfchost7 -fcp fcs3

vfcmap -vadapter vfchost8 -fcp fcs2

vfcmap -vadapter vfchost9 -fcp fcs3

Then on Client;
o Applicable for OTHER than SAN Boot LUN – e.g. DB Volume Groups
o If for SAN Boot LUsN, we are unable to run these commands since the LPARs are not
being built yet
Update Spreadsheet with new virtual fibre WWPN’s

# cfgmgr

# prtconf | grep fcs

+ fcs0 U8202.E4B.0609E5R-V3-C20-T1 Virtual Fibre Channel Client Adapter
+ fcs1 U8202.E4B.0609E5R-V3-C30-T1 Virtual Fibre Channel Client Adapter

# lscfg -vl fcs0 | grep -i address

Network Address.............C05076049B6E0000

# lscfg -vl fcs1 | grep -i address

Network Address.............C05076049B6E0002
 Submit SSM request for the new LUNs allocation, refer to Step 6 – e.g.;

ID Name Type Status

CL825381 - RTP NA Pharma P750 Enterprise Storage -

Enterprise Storage - Attach New SAN Storage to a
8300662 AIX CLIENT LPARS SERVER Attach New SAN
Server - Submitted
BUILD Storage to a Server

!! Please take note that each SAN Boot LUN is to be zoned down ONE path initially. After the install of
the servers are complete, inform the Storage team to zone down all the LUNs with the rest of the
PATHs.

If the Storage team is unable to see the ports and the LPARs, do the following on each LPARs:
 SMS menu  Select [5] Select Boot Options  Select [1] Select Install/Boot Device  Select [7]
List all devices > It will scan and list all the devices available
 Then check with the Storage Team

If they are still unable to do see, do the following on each LPARs;

 SMS menu  Select [5] Select Boot Options  Select [4] SAN zoning support > It will display all
the available Virtual FC adapters
 Select the first port, and leave it open, the Storage team should be able to see the ports and the
LPARs now

IMPORTANT!!
 While the Storage Team is raising their CC and then implementing their CR, please make sure the
port is always open
 Whenever you need to leave, choose DISCONNECT instead of Logoff as it will preserve your
sessions and the port can be leave opened.
8. Start OS installation using NIM - follow ITI_TIP_15751 - Technical Installation Plan for the IBM AIX
Operating System (NIM) - Print Screens

You should see the same SMS menu when you open the adapter, press Esc button to get to the
first SMS menu

If you are unable to see the SMS menu again, go back to your LPAR  Open Terminal Window 
Click at Advanced, choose SMS mode

Once you have set all the IP parameters and the set up at the NIM server, exit SMS menu, you
should see up to this screen as shown below;
Choose [1], and press Enter

Choose [2] – Change/Show Installation Settings and Install

Choose [1] – Disk(s) where you want to install

Choose [1] to unselect hdisk0, then key in [2] to select hdisk1

o as hdisk0 will be the EMC GGatekeeper LUN
o hdiks1 with the correct size should be the newly assigned Boot LUNs
The final option would be as shown below;
Once you key in [0], and press Enter, the installation continues..
9. Group SAN paths/zoning

Ask the storage team to present the SAN Boot LUNs down to the rest of the paths (WWNs).
!! Please take note that each SAN Boot LUN is to be zoned down ONE path initially. After the
install of the servers are complete, inform the Storage team to zone down all the LUNs with
the rest of the PATHs.

10. After the LPARs have been build, then install PowerPath.

First Build LPAR on single fibre PATH, after build bootlist should show one disk, for example:

# bootlist -m normal -o
hdisk1 blv=hd5

After the storage team has group the paths (Step 9), proceed with the PowerPath installation.

# mount bresxuxc001p09:/export/unix_sw /unix_sw

# cd /unix_sw/AIX/Apps/EMC_Powerpath/5500_P03; installp -a -Y -d '.' EMCpower
# cd /unix_sw/AIX/Apps/EMC_Powerpath/5500_P03/AIX_ODM/5305; installp -a -Y -d '.'
EMC.Symmetrix.aix.rte EMC.Symmetrix.fcp.rte

# emcpreg -install (BIPZ-HB43-WFMV-QCC4-M49O-JKQT) where do we get this key?

# powermt check_registration
# shutdown -r now
# powermt display dev=all

# uname -a
AIX us2us00081 1 6 00F6F8E04C00
# mount bresxuxc001p09:/export/unix_sw /unix_sw
#
# cd /unix_sw
# ls
AIX firmware openssh-5.5p1-bff.tar.gz Siebel
backup lost+found openssl.0.9.8.1103.tar.Z
# cd AIX/Apps/EMC_Powerpath/5500_P03
# ls -lrt
total 135072
-rwxr--r-- 1 root system 26668 12 Apr 2011 emc_reserve_v2.sh
-rw-r--r-- 1 root system 1733 03 May 2011 emc_reserve_v2_README
-rw-r--r-- 1 root system 69120000 24 Oct 08:37 EMCpower_install
drwxr-xr-x 4 root system 256 21 Jan 08:07 AIX_ODM
-rw-r--r-- 1 root system 928 21 Jan 08:11 .toc
#
# cd /unix_sw/AIX/Apps/EMC_Powerpath/5500_P03; installp -a -Y -d '.' EMCpower

Selected Filesets
-----------------
EMCpower.base 5.5.0.3 # PowerPath Base Driver and Ut...
EMCpower.encryption 5.5.0.3 # PowerPath Encryption with RSA
EMCpower.migration_enabler 5.5.0.3 # PowerPath Migration Enabler ...
EMCpower.mpx 5.5.0.3 # PowerPath Multi_Pathing Exte...

<< End of Success Section >>

+-----------------------------------------------------------------------------+
BUILDDATE Verification ...
+-----------------------------------------------------------------------------+
Verifying build dates...done
FILESET STATISTICS
------------------
4 Selected to be installed, of which:
4 Passed pre-installation verification
----
4 Total to be installed

+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+

Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
EMCpower.base 5.5.0.3 USR APPLY SUCCESS
EMCpower.mpx 5.5.0.3 USR APPLY SUCCESS
EMCpower.migration_enabler 5.5.0.3 USR APPLY SUCCESS
EMCpower.encryption 5.5.0.3 USR APPLY SUCCESS
#

# cd /unix_sw/AIX/Apps/EMC_Powerpath/5500_P03/AIX_ODM/5305; installp -a -Y -d '.'

EMC.Symmetrix.aix.rte EMC.Symmetrix.fcp.rte

Selected Filesets
-----------------
EMC.Symmetrix.aix.rte 5.3.0.5 # EMC Symmetrix AIX Support So...
EMC.Symmetrix.fcp.rte 5.3.0.5 # EMC Symmetrix FCP Support So...

<< End of Success Section >>

+-----------------------------------------------------------------------------+
BUILDDATE Verification ...
+-----------------------------------------------------------------------------+
Verifying build dates...done
FILESET STATISTICS
------------------
2 Selected to be installed, of which:
2 Passed pre-installation verification
----
2 Total to be installed

+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+

Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
EMC.Symmetrix.aix.rte 5.3.0.5 USR APPLY SUCCESS
EMC.Symmetrix.fcp.rte 5.3.0.5 USR APPLY SUCCESS
EMC.Symmetrix.aix.rte 5.3.0.5 ROOT APPLY SUCCESS
EMC.Symmetrix.fcp.rte 5.3.0.5 ROOT APPLY SUCCESS
#

# emcpreg -install

=========== EMC PowerPath Registration ===========

Do you have a new registration key or keys to enter?[n] y
Enter the registration keys(s) for your product(s),
one per line, pressing Enter after each key.
After typing all keys, press Enter again.

Key (Enter if done): BIPZ-HB43-WFMV-QCC4-M49O-JKQT

1 key(s) successfully added.
Key successfully installed.

Key (Enter if done):

1 key(s) successfully registered.
#

# powermt check_registration

Key BIPZ-HB43-WFMV-QCC4-M49O-JKQT
Product: PowerPath
Capabilities: All
#

# powermt display dev=all

Device(s) not found.
#

# shutdown -r now

# powermt display dev=all

Pseudo name=hdiskpower0
Symmetrix ID=000192603621
Logical device ID=2DE7
state=alive; policy=SymmOpt; priority=0; queued-IOs=0;
==============================================================================
--------------- Host --------------- - Stor - -- I/O Path -- -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
0 fscsi0 hdisk1 FA 8fA active alive 0 0
1 fscsi1 hdisk3 FA 8fA active alive 0 0
2 fscsi2 hdisk5 FA 7fA active alive 0 0
3 fscsi3 hdisk7 FA 7fA active alive 0 0

11. Configuring PowerPath Boot Device

Run pprootdev on to set up multipathing to the root device:

# pprootdev on

bosboot: Boot image is 53276 512 byte blocks.

PowerPath boot is enabled for the next system boot.

Update bootlist with boot-devices, for example:

# bootlist -m normal hdisk1 hdisk3 hdisk5 hdisk7

# bootlist -m normal -o
hdisk1
hdisk3 blv=hd5
hdisk5
hdisk7
 #
# pprootdev fix

bosboot: Boot image is 53276 512 byte blocks.

You may now run bosboot.
PowerPath boot remains enabled for the next system boot.

If you are getting this error;

# pprootdev fix

0301-101 /usr/lib/boot/bin/mkboot_chrp: Device open failure: /dev/hdisk7

pprootdev: bosboot has failed. The configuration change
has not been saved to the boot device.
#

Do the following:
Add the script below and do another round of reboot.
(The script includes /usr/sbin/pprootdev fix, so you do not need to run it manually)

Add the below script to /etc/rc.d/rc2.d/S72pprootdev

--------------------------------------
#!/bin/sh
#
# After a system boots from a PowerPath device, the bosboot tool
# cannot function correctly. This is because of the state of the
# configuration after booting from a PowerPath device and the fact that
# bosboot expects the boot device to be an hdisk, not an hdiskpower
# device.
#
# The pprootdev fix command corrects the configuration to allow bosboot to work. Run
# pprootdev fix before undertaking any administrative task that runs
# bosboot. This corrects the configuration for bosboot but does not
# change the PowerPath boot switch. The next system boot still uses
# PowerPath. Run pprootdev fix only once after a system restarts that
# uses PowerPath. bosboot then functions correctly until the system
# restarts again.
#
# Note: Always use the command bosboot -ad /dev/ipldevice to create a boot
# image from the current boot kernel disk.
#

/usr/sbin/pprootdev fix
----------------------------------------

# chmod 755 /etc/rc.d/rc2.d/S72pprootdev

Reboot Server
# shutdown -r now
 The test:

# bosboot -ad /dev/ipldevice

bosboot: Boot image is 53276 512 byte blocks.

# bootlist -m normal -o
hdisk1 blv=hd5
hdisk3 blv=hd5
hdisk5 blv=hd5
hdisk7 blv=hd5

12. Install Altiris

# mount bresxuxc001p09:/export/unix_sw /unix_sw

# cd /unix_sw/AIX/Apps/Altiris; ./aex-bootstrap https://sm-nsprod.corpnet1.com
# ps -ef | grep aex
root 8585344 7995526 1 11:13:56 pts/0 0:00 grep aex
root 9306192 1 0 11:09:32 - 0:00 aex-pluginmanager.bin -D
root 10289180 9306192 0 11:09:32 - 0:00 aex-pluginmanager -F -nm -nc

# mount bresxuxc001p09:/export/unix_sw /unix_sw

# cd /unix_sw/AIX/Apps/Altiris; ./aex-bootstrap https://sm-nsprod.corpnet1.com
INFO: Creating Default Config file.
INFO: Getting Package:
https://sm-nsprod.corpnet1.com/Altiris/NS/NSCap/Bin/Unix/Agent/AIX/PowerPC into temp
dir: /opt/altiris/notification/nsagent/.tmp_inst
INFO: Success getting Package.
INFO: Installing package...

Selected Filesets
-----------------
aex-nsclt 6.2.1378.0 # Altiris Agent for UNIX and L...

<< End of Success Section >>

+-----------------------------------------------------------------------------+
BUILDDATE Verification ...
+-----------------------------------------------------------------------------+
Verifying build dates...done
FILESET STATISTICS
------------------
1 Selected to be installed, of which:
1 Passed pre-installation verification
----
1 Total to be installed

+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+

Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
aex-nsclt 6.2.1378.0 USR APPLY SUCCESS
aex-nsclt 6.2.1378.0 ROOT APPLY SUCCESS
#
 (E) Post Tasks

E.1 - Submit Remedy ticket for Netbackup configuration & scheduler

Sample UKIM20003999027

E.2 - Submit separate SSM request for Patrol configuration on each LPARs
Sample SSM Request ID: 8313997

E.3 – Install & Test Altiris

Refer to Install Altiris on AIX.txt

E.4 – Generate Install_Reports & TIRs

Refer to Generate Install report AIX.txt