In my opinion, I think the simplest way to do this is to create the LPAR with the normal virtual ethernet adapter, and the simply switch the adapters once set up is complete.  This allows you to complete all functions through the NIM and you don’t have to worry about firewall interference until after most of the tedious parts are complete.  No CDs to mount, no files to manually copy over.  Every body wins!

When creating an LPAR, follow the steps here for help, and add these simple tweaks to make your life easier when building an LPAR in the DMZ

1. Before creating the LPAR, ensure that you have all of the details and networking set up.  This includes a public IP address, the physical port and switch, and the correct VLAN.  You will also need a spare, unused IP address to be your temporary local IP address for initial set up
2. When creating the profile for the LPAR, ensure that you create an LHEA on an open port.  This can be done later, but this will be the adapter you switch over to once the set up is complete (if you don’t know which ports are already in use, refer to the System’s profile and view the LHEA ports individually to see LPARs connected to the ports)
3. Before completing any steps on the NIM server, ensure that you add the new hostname and temporary IP address to the /etc/hosts file.
4. Proceed with installation as normal
5. Once installation is completed, you can edit the LPAR profile.  Remove the virtual ethernet adapter (ensure you do not reboot LPAR until you complete LPAR side work as well)
6. From the LPAR, “ifconfig -a” to view the adapters
7. “smit tcpip” -> “Minimum Configuration and Startup” -> “Select Adapter (eg en0)
8. Add host, ip, subnet and gateway to this adapter
9. Once new adapter initialized, remove the old adapter with “rmdev -dl”
10. Ping a known DNS IP to test configuration
11. Shutdown LPAR and activate new profile now to switch LPAR to DMZ
12. Remove entry from NIM /etc/hosts file (I have forgotten to do this and it comes back to bite you…hard)

Note: For future work, you will not be able to mount your NIM server.  All file transfers must be done through SCP (or alternative).  This means any mksysb, monitoring or general maintenance scripts will need to be different than that of a normal LPAR.

Also, any communication between your new LPAR and any servers such as TSM will need to have specific ports opened in the firewall.  Inquire your network team for more details.

From your NIM master you need to ensure that your machine has Communication Protocol used by client set to nimsh.  On my machines, they had defaulted to shell.  Easiest way to do this is:

lsnim -l [[hostname]]

you will be looking for the connect attribute set to nim sh

Alternately you can go to “smit nim” -> Perform NIM Administration Tasks -> Manage Machines ->  Change/Show Characteristics of a Machine

Find your host and view the Communication Protocol used by client attribute.  Again it needs to be set to nimsh.

If you are like me and need to fix this, here is what you do

On the NIM Client

cp /.rhosts /.rhosts.old

mv /etc/niminfo /etc/niminfo.old

niminit -a name=[[client_hostname]]-a master=[[nim_hostname]]-a master_port=1058 -a connect=nimsh

This will backup the niminfo file and the rhosts (just in case).  Once you have completed your work on the client:

On the NIM Master

nim -o change -a connect=nimsh [[hostname]]
lsnim -l [[hostname]]

This will change the definition on the master and show you the characteristics for you to double check

rsct -> Reliable Scalable Cluster Technology

adt -> Application Development Toolkit

rte -> Run Time Environment

bff -> Backup File Format

rpm -> Red Hat Package Manager

ODM -> Equivalent to Windows Registry

**If filename does not contain *.rpm then it is bff -> IBM file set

Checklist

Commands

• lslpp –l [package] -> list installed packages
• oslevel –r -> View technology level
• oslevel –s -> View software level
• showmount –e [nim server] -> View all exports of NIM server (or any other server)
• whereis [program] -> Locate program on LPAR
• which_fileset [name] -> find file set for specific program
• lslpp –w [full path to program] ->show installed file sets for a program

**NOTE about NIM -> Ensure all NFS exports are done through SMIT or using IBM command to ensure all file systems are mounted at reboot**

• mount [nim server]:[path] /mnt

Steps

Smit -> Software Installation -> Install and Update -> Install -> Path

• Software to Install (F4 then ‘/’ to search for file sets)
• Commit?
• Automatically Accept New License Agreements

lslpp –f [file set] ->displays names of file added for file set

Checklist

LPAR Information

VIO Information

Backup SSH Files

• copy ssh file to new location

   cp –r /etc/ssh /etc/ssh.backup 

Map disks from VIO

• If new disks are being allocated for additional storage or JFS to JFS2 Conversion, you will need to map the disk through the VIO server
• Once storage is allocated through SVC, login to VIO server
• detect new hard ware

   cfgdev 

• confirm LUN ID with disks allocated by storage team

   lsdev –dev hdiskx –vpd 

• create virtual device on NIM

   mkvdev –vdev hdiskx –vadapter vhostx –dev [vtd] 

• view all devices mapped with specified vhost

   lsmap –vadapter vhostx 

Confirm Disks on LPAR

• review attributes

   cfgmgr 

   lsattr –El hdiskx 

• In order to maximize consistency between redundant VIO servers, I prefer an hcheck interval of 60 and a vscsi1 path priority of 2

 chdev -l [hdiskx] -a hcheck_interval=60

chpath -l [hdiskx] -p vscsi0 -a priority=2
 

Backup rootvg

•  mount –o soft [nim server]:[mksysb image location] [mount point] 

•  /usr/bin/mksysb –i –X –p [full path including new mksysb image name] 1>[log file] 2> [err log file] 

Backup inittab, disable all non-OS processes from booting up to ensure minimum reboot time

•  cp /etc/inittab /etc/inittab.backup 

• add : to comment out in inittab.  This is important because you will initiate multiple reboots and starting up all the processes and applications can be both a waste of time and may not shut down properly (if you force a shut down etc).  It is also important to note that you DO NOT want to simply restore the inittab after installation as the os upgrade may have added entries to the inittab.  The backup is simply a precaution, and you always want to only uncomment out what you added in

   vi /etc/inittab 

Check for currently running processes not owned by root

•  ps –ef 

From NIM, ensure LPAR ready for BOS installation

• Smit nim_bosinst -> rte install -> Version Images/Spot

i.      Accept Licenses -> Yes

ii.      Initiate Reboot -> No

iii.      Accept Licenses -> Yes

• Ensure Client State is Ready for Installation

   lsnim –l [hostname] 

Re-Boot LPAR from HMC

• Shutdown LPAR (I like to do this from the HMC sending an OS level shutdown to ensure all processes closed nicely
• Activate Profile -> Open Terminal -> Advanced -> Boot Mode -> SMS Mode

Upgrade AIX on LPAR

• 2) Remote IPL -> 1) Ethernet -> 1) IPv4 -> 1) BOOTP -> 1) IP Parameters *Populate if necessary* ESC) Back -> 3) Ping Test -> 1) Run *If failed reconfirm IP or contact networking*
• 5) Boot Option -> 1) Select install/boot order -> 6) Network -> 1) BOOTP -> 1) LAN -> 2) Normal Boot -> 1) Yes

On Boot

1) Enter -> 2) Custom Settings -> Ensure Enterprise Edition selected

• At ~3% you will need to confirm settings etc.

Once Booted

• Confirm updated successfully

   oslevel –s 

• Check error reports

   bootlist –om normal 

   errpt | more 

• Check JFS or JFS2 

   lsvg –l [vg] 

Restore SSH Key

•  mv /etc/ssh /etc/ssh.old 

•  mv /etc/ssh.backup /etc/ssh 

If running JFS2 Conversion

• If splitting rootvg over 2 disks, install bos.alt_disk_*7.1.1.0
• Copy old rootvg to new JFS2 disk

   alt_disk_copy –T –d hdiskx 

• Set new rootvg

   alt_rootvg_opt –X 

• confirm boot device

   bootlist –om normal 

If creating additional VG

• smit vg -> Add VG -> Scalable
  • Change PP Size
  • Physical Location
• confirm creation

   lsvg 

Create jfs2log LV on datavg

• make LV

   mklv –t jfs2log datavg 1 

• format LV

   logform /dev/loglv0x 

If migrating file systems off of rootvg to new VG

• Backup /etc/filesystems

  •  cp /etc/filesystems /etc/filesystems.backup 

• unmount

   unmount [file system] 

  **Subdirectories must be mounted first**

• copy LV to new VG

   cplv –v [destination vg] [lv name] 

• update file system file

   chfs –a dev=/dev/[lv] –a log=/dev/[new jfs2 log] [file system] 

• mount newly created file system

   mount [file system] 

• remove old LV

   rmlv [old lv] 

• Repeat for chosen file systems

If migrating rootvg to new disk

• list disks

   lspv 

• allow VG access to new disk

   extendvg rootvg [new disk] 

• mirror disks

   mirrorvg rootvg [new disk] 

• add boot information to new disk

   bosboot –ad [new disk] 

• set system to boot from new disk

   bootlist –m normal [new disk] 

• clear boot record from old disk

•  chpv –c [old disk] 

• unmirror

   unmirrorvg rootvg [old disk] 

• remove vg off old disk

   reduce rootvg [old disk] 

• remove old disk

   rmdev –dl [old disk] 

• confirm old disk removed

   lspv 

• confirm boot device

   bootlist –om normal 

Create paging space (usually 1:1.5 memory)

• check current paging space

   lsps –a 

• check amount of memory

   lsattr –El  mem0 

• smit lv -> Paging
  • Either add space to rootvg paging space or create new LV on new VG
• confirm added page space

   lsps –a 

If you are left with disks no longer needed, delete from LPAR

• list disks

   lspv 

• delete record of disk from LPAR

   rmdev –dl [disk] 

• delete VG from ODM

   exportvg [vg] 

If you are left with disks no longer needed, delete them from VIO servers

• double check LUN ID of old disks

   lsdev –dev hdiskx –vpd 

•  lsmap –vadapter vhostx 

• remove VTD

   rmdev –dev [vtd] 

• remove backing device

   rmdev –dev hdiskx 

• Send email to Storage to confirm disk ready for retrieval

Checklist:

• IP address(es)
• LUN number(s)
• Host name
• Processing unit requirements of the new LPAR
• Memory requirements of the new LPAR
• Dedicate I/O requirements of the new LPAR
• Shared processor pool in which the new LPAR will be put Virtual I/O requirements of the new LPAR

HMC

1. Login as hscroot

2. “Systems Management”->“Servers” ->select server ->“Configuration”->”Create Logical Partition”->”AIX or Linux”
3. Do not change the system assigned partition ID. Input hostname as partition name -> click “Next”
4. Use hostname as profile name. DO NOT select “Use all the resources in the system” unless this will be the only LPAR on the system. Click “Next” to continue.
5. Choose ”Shared” and click “Next” to continue.

6. Set processing unit. Choose shared processor. Click “Next” to continue.

7. Set memory. Click “Next” to continue.

8. Assign physical I/O resources. DO NOT add dedicated hardware if you want to use Live Partition Mobility. Click “Next” to continue.

9. Setup virtual adapters. Typically 2 SCSI adapters (1 on each VIO for redundancy) and 1 ethernet adapter. Enter a large number for maximum virtual connections (ie 100).

Click “Actions”->”Create”->”SCSI Adapter…”

10. Click “System VIOS Info…”

11. Locate 2 server slots which meet all following requirements:

• Same virtual adapter numbers
• VIO servers
• Status is “Inactive”
• Backing device is empty
• Client partitions are “Any Partition”
• Client slots are “Any Partition Slot”
• Client disks are empty

Record the server slot number, VIO server name and virtual adapter number, select the first slot and click “OK”

12. Fill in virtual SCSI adapter number. Use the server adapter ID as virtual SCSI adapter, then create the second SCSI adapter connecting to the other VIO server.

If no empty slot was found in the system VIOS info, create new slots as per standard procedure.

13. Create an ethernet adapter. Use the third segment of your IP address as the VLAN ID. Example: IP: 10.1.126.96 VLAN ID:126

14. Verify the settings and click “Next” to continue.

15. Setup LHEA according to your plan. You can assign a physical port to up to 16 partitions, but you can’t dynamically migrate a partition with LHEA configured. In this example, we didn’t setup LHEA.

16. Verify settings. Click “Finish” to continue.

VIO

1. On the HMC, reserve the server SCSI slot to the new LPAR in each VIO server’s profile.
• Select one VIO server, and click “Configuration” -> “Manage Profiles”

• Go to “Virtual Adapters” tab, and click the server SCSI adapter you were using

• Change it to “Only selected client partition can connect”, select the partition you created just now, and change the “Client adapter ID” to match the VSCSI Adapter number

• Do the same thing on the other VIO server.

2. Login to each VIO server as padmin and perform the following operation. If the client needs more than one disk, you can map them to client through the same vhost.
1. Look for new disks

cfgdev

2. Verify vio picked found disks

lspv

3. Verify the LUN number with the one given by storage administrator. LUN id located under “Serial Number”

lsdev -dev [hdisk] –vpd

4. Link the virtual adapter to this disk:

mkvdev -vdev [hdisk] -vadapter [vhost] -dev [virtual target device] 

**NOTE** Device name (rootvg01) must be unique as many rootvg and datavg reside on the VIO servers…ie newlpar_rootvg01

1. **NOTE** Save your command history as you will need to execute the exact commands on both VIO servers
2. Ssh to NIM server – sudo to root
3. Smitty nim_mkmac  -> Define a machine

NIM

• Hostname
• NIM machine type= standalone
• Cable type =tp
• nim network = nimnet10_1_126  ß nim network choice is dependent on where the NEW client  vlan will reside

**NOTE** Kernel mode must be set to mp on AIX v5.3

1. Smitty nim_bosinst   choose your hostname, enter -> choose install from mksysb option -> Select standard image if present -> select the standard image for the version that needs to be installed  ->  Select the SPOT and LPP_SOURCE resource ***these should match the version you are installing***

2. Check the state of the newly created nim machine client using the following command:

 lsnim -l [hostname] 

• Client state must be BOS Installation otherwise commands were not issued properly

NIM restore operation

1. On HMC select the LPAR -> Operations -> Activate -> Profile

This opens a pop up window place a check mark on “open a terminal”, select advanced tab and change the boot mode to SMS -> ok -> ok and accept any certificates.

2. From SMS – setup the bootp parameters. choose option:

• 2) setup remote IPL
• 1)interpartition lan
•  1) IPV4
•  1) bootp
• 1) ip parameters

Enter all networking parameters (1,2,3 and 4 .. ie 1 for client ip, 2 for server ip etc.)

**Server address points to the NIM server

**NOTE** You should run a ping test to ensure network information entered correctly.  If network is slow or installation times out, you should enter advanced adapter settings and change to duplex 1000/full NOT AUTO

M) Back to main menu

5) Select boot options

1) Select install/boot device

6) Network (NIM server)

• 1) bootp
• 1) Interpartition LAN
• 2) normal Mode Boot
• yes) to confirm..

3. After reboot, follow screen to finalize all options

•  1) to choose this console etc..
• NOTE: disk errors may arise, some of these can be ignored
• Base Operating System menus screen
• Choose 2 ) Change/Show Installation settings and Install -> choose option 1 to select “disk” where you want to install
• Use 77 to double check disk options and make any changes
• Once all settings verified 0) to continue with mksysb

Post installation

1. Change root password

 passwd root 

2. Activate auditing

 audit on 

3. Change paging space according to requirements. If there’s no specific requirement, change the paging space size to match physical memory size.

• Gather information on Memory, paging space, ppsize, required paging space

</pre>
lsattr –El mem0 -> check memory
lsps –s -> check paging space
lspv –l hdisk0
smit ->storage -> LVM
smit chps

4. Reboot the newly created LPAR and run “errpt” to check for errors.

5. Document the details of the newly created LPAR