 See adapters, drivers, and microcode.

See the bottom of this section for AIX part number

mappings

lsdev -Cc adapter -spci | grep fcs   For each of the FCS instances 

 Micorcode

lsmcode -cd fcs0 

 Firmware

lscfg -vl fcs0 | grep Z9 

 Driver

lsdev -C -Ftype,name | grep -i fcs 

 Software

lslpp -l | grep -i hba

lslpp -l | grep “FC Software”

lslpp -L EMC.Symm*   Should get two outputs – aix and fcp

lslpp -L devices.pci.df1000f7.com

lslpp -L devices.pci.df1000f* 

 Disk type/info

lsattr -El hdisk

lsattr -El vpath 

 List Powerpath info

Software

lslpp -l | grep -i powerpath 

Devices

lsdev -C -t power 

WWN

Loop for each adapter

lscfg -vl fcs0 | grep Z8

 IBM Part numbers

To determine the part numbers for the HBAs

lscfg -vpl fcs0 | grep “Part Number”

To corrolate the Part Number from above to a “Feature Code”

that EMC uses in their documentation OR to a HBA vendor model. 

Emulex LP10000  FC 5716

80P4543 (FRU 80P4544)

80P4544

Emulex LP9002   FC 6228

00P2995 (FRU 00P2996)

00P2996

00P4494 (FRU 00P4495)

00P4495

03N2452 (FRU 09P0102)

09P0102

09P5079 (FRU 09P5080)

09P5080

80P4381 ???

80P4384

Emulex LP9802   FC 6239

00P4295

00P4297

Emulex LP7000   FC 6227

00P1882
 03N4167

09P1162

09P1173

09P4038

24L0023

INITIAL load software, drivers and firmware

NOTE: You may need to modify lines for the APPROPRIATE version

mount nimserver:/depot/Software/UNIX /mnt

Drivers

See if they are already loaded

lslpp -L devices.pci.df1000f* 

If not, then

cd /mnt/aix/aix52_apar_IY56722

installp -a -Q -d . devices.pci.df1000fa.rte

smit install_software

use dot (.) for directory

select the following:

devices.pci.df1000fa

devices.pci.df1000f7

 Multipath software AIX

lsvpcfg

lspv

 
 AIX SDD

datapath query version

datapath query adapter

datapath query device

datapath query essmap

datapath query wwpn

datapath query portmap

datapath query adaptstats <n>

datapath query devstats <n>

 EMC Symmetrix software

cd /mnt/EMC/Drivers/AIX

installp -qa -d ./EMC.AIX.5.2.0.0  EMC.Symmetrix.aix.rte EMC.Symmetrix.fcp.rte

 EMC ECC package

cd /mnt/EMC/ECC/Control_Center_5.2

./install_master.sh ‘pwd‘

/opt/ecc

ECC-servername

default

default

/opt/ecc/exec/start_master.csh

echo “ecc:2:once:/opt/ecc/exec/start_master.csh > /dev/console 2>&1 Start ECCagent” >>

/etc/inittab
  

EMC PowerPath

Must have a valid PowerPath license for this host

cd /mnt/EMC/PowerPath/PowerPath4.4/aix

installp -qa -d ./EMCpower_install EMCpower

/usr/sbin/emcpreg -install

/usr/sbin/powermt check_registration

View SDD

lsvpcfg

datapath query adapter

datapath query device

5.X and greater

iostat -m

 Initialize HBAs in ODM

diag

Advanced Diag Routines

System Verification

(select each fcsX => F7)

loopback plug? no

F10

 Configure disks

cfgmgr -vl fcs0

cfgmgr -vl fcs1

 
 EMC Symmetrix software

cfgmgr -v

/usr/lpp/EMC/Symmetrix/bin/emc_cfgmgr

/usr/sbin/powermt config

/usr/sbin/powermt save

 SDD

config HBA into SDD

/usr/sbin/allpaths

config Paths via HBA

cfgmgr -l dpo

**or**

/usr/lib/methods/cfallvpath -2

lsdev -Cc disk | grep -i emc

lspv

if this is the DR node, it needs to see failover disk’s serial numbers

so in can import the volumegroup

for DISK in $(lspv | grep hdiskpower | awk ‘{print $1}’)

do

echo $DISK

chdev -l $DISK -a pv=yes

 done

Posted in AIX, FastT, Storage. Leave a Comment »

Increase fastT array size, LUN and actual VG on AIX host.

March 10, 2009 — unixskylab

Increase capacity of an array first  (storage manager –> select array –> add free space –> OK). And

then increase capacity of actual LUN.  Go to AIX host and run chvg -g against volume group to make it

aware of changes. Run lsvg to see if changes took into effect.

Notes -

chvg -g < vg name >

Following message shows up  -

0516-1216 chvg: Physical partitions are being migrated for volume group descriptor area expansion. 

Please wait.

0516-1164 chvg: Volume group <>vg changed.  With given characteristics <>vg   can include upto

112 physical volumes with 8128 physical partitions each.

-g

Will examine all the disks in the volume group to see if they have
 grown in size. If any disks have grown in size attempt to add

additional PPs to PV. If necessary will determine proper 1016

multiplier and conversion to big vg. Notes:

1    The user might be required to execute varyoffvg and then

varyonvg on the volume group for LVM to see the size change

on the disks.

2    There is no support for re-sizing while the volume group is

activated in classic or enhanced concurrent mode.

3    There is no support for re-sizing for the rootvg.

AIX paging
March 3, 2009 — unixskylab

Recommendations for paging

 Creating all paging spaces the same size

 Maximum spreading across disks

 Make sure they are all online

 Avoid shared disks likely to be moved to another system (might require a reboot)

 Don’t have dedicated paging disks – when you have a peak in paging you want ALL disks to help

out.

To see current paging space use : lsps -a

Create paging space

 Use smit lvm

 set size

 set online “now”

 set online at next reboot too

Warning:

 lsps and create paging use different units!!

 use lsps -a -c
 We recommend using more paging spaces rather than growing just the one but there is a limit to the

number of paging spaces

 A paging space can be increased in size

 If the spaces are different sizes this can be used to make them all the same size.

 Paging spaces are used evenly therefore lots of paging spaces and lots of disks

If a paging space disk fails, the system will halt, on reboot the paging space will be disabled.

If your paging space is not protected by RAID5 or a disk subsystem then you should consider

mirroring.

For extra availability – mirror the paging space

Just like mirroring a logical volume (LV)

 smitty lvm + LV + Set LV + Add a copy

 or use command: mklvcopy command

Removing a Paging Space

Impossible – well it was on older AIX versions on newer version sit is possible you will have to check

for your version.

 Use: smit lvm

 take Paging Space

 then deactivate it

 then remove it

If you can’t remove it set to be offline at next reboot … wait till you can reboot.

send snap to IBM

February 28, 2009 — unixskylab
snap -r
snap -gGfkftLikc
cd /tmp/ibmsupt
mv snap.pax.Z CASE_NUMBER
ftp testcase.software.ibm.com
login: ftp
>cd /toibm/aix
>bin
>hash
>put CASE_NUMBER

Alternate disk install AIX

February 28, 2009 — unixskylab

Its possible to install AIX onto another disk on the same system. This is not partitioning, its just a

second install of the BOS, on another disk.

You need to have “bos.alt_disk_install.rte” fileset installed. This fileset ships the “alt_disk_install”

command,

which allows cloning of the rootvg and installing an AIX mksysb to an alternate disk.

“bos.alt_disk_install.boot_images” fileset installed. This fileset shipts the boot images, which is

required to install mksysb images to an alternate disk.

Once you have installed these filesets, the alternate disk installation functions are available to you.

You can use the “smitty alt_install” or “smitty alt_clone” or “smitty alt_mksysb” fastpath:

# smitty alt_install

———————————————–

Alternate Disk Installation

Move cursor to desired item and press Enter.

Install mksysb on an Alternate Disk

Clone the rootvg to an Alternate Disk

F1=Help  F2=Refresh   etc..

———————————————–
So, the Alternate Disk Installation can be used in one of two ways:

- Cloning the current rootvg to an alternate disk.

- Installing a mksysb image on another disk.

# smitty alt_mksysb

———————————————–

Install mksysb on an Alternate Disk

Type or select values in entry fields.

Press Enter AFTER making all desired changes.

Target Disk(s) to install          []

Device or image name               []

Phase to execute                    all

image.data file                    []

Customization script               []

Set bootlist to boot from this disk

on next reboot?                     yes

Reboot when complete                no

Verbose output?                     no

Debug output?                       no

resolv.conv file                   []

———————————————–

You can also use the “alt_disk_install” command to clone the rootvg to another disk.

The command creates an “altinst_rootvg” volumegroup on the destination disk and prepares

the same logical volumes as in the rootvg, except the names are prepended with “alt_”,

for example, alt_hd1. Similar are the filesystems renamed to “/alt_inst/filesystemname”

and the original data (mksysb or rootvg) is copied.

After this first fase, a second fase begins where an optional configuration action

can be performed, either a custom script or update of software, when cloning rootvg.
The third fase unmounts the /alt_inst/filesystems and renames the filesystems and logical volumes

by removing the alt names. Then the bootlist is altered to boot from the new disk.

After the system is rebooted, the original rootvg is renamed to old_rootvg.

Example:

# lspv

hdisk0      00fa7377474    rootvg

hdisk1      00hdgfh6374    None

# alt_disk_install -BC hdisk1

performs cloning hdisk0 to hdisk1 where hdisk1 will be the new rootvg.

Installing a second AIX52 partition using alt_disk_install:

———————————————————–

You can use the alt_disk_install command to clone a system image to another disk, and you may use

the -O option to remove references in the object data manager (ODM) and device (/dev) entries

to the existing system. The -O flag tells the alt_disk_install command to call the devreset command,

which resets the device database. The cloned disk can now be booted as if it were a new system.

An example of this scenario is as follows:

Boot the managed system as a Full System Partition so you have access to all the disks in the

managed system.

Configure the system and install the necessary applications.

Run the alt_disk_install command to begin cloning the rootvg on hdisk0 to hdisk1, as follows:

# /usr/sbin/alt_disk_install -O -B -C hdisk1

The cloned disk (hdisk1) will be named altinst_rootvg by default.

Rename the cloned disk (hdisk1) to alt1, so you can repeat the operation with another disk.

# /usr/sbin/alt_disk_install -v alt1 hdisk1

Run the alt_disk_install command again to clone to another disk and rename the cloned disk, as

follows:
# /usr/sbin/alt_disk_install -O -B -C hdisk2

# /usr/sbin/alt_disk_install -v alt2 hdisk2

Repeat steps 3 through 5 for all of the disks that you want to clone.

Use the HMC to partition the managed system with the newly cloned disks.

Each partition you create will now have a rootvg with a boot image.

Boot the partition into SMS mode. Use the SMS MultiBoot menu to configure the

first boot device to be the newly installed disk. Exit the SMS menus and boot the system.

NIM client define and OS install

February 3, 2009 — unixskylab

1. Define the new client (smitty nim à Nim admin tasks à manage machines à Define a machine

2. Change the cable type to N/A

3. F3 to go back on menu.

4. Select Manage Network Install Resource Allocation à Allocate resources à select the new client à  

Select the  resources (SPOT, lpp_source, mksysb, bosinst_data)

5. After completion, F3 twice to the Manage Machine menu.  Select perform operations on machines

à Select the new client à Select bos_inst 

 For NIM client

1. Boot the client partition into SMS mode from WebSM/ HMC,

2. Right click on the partition à Activate

3. Select 2) Remote IPL Settings –>Select the Ethernet adapter–>Select IP Parameters–> Verify

Adapter Settings

4. Under adapter in the virtual world, there is not much we can do.  With a real adapter, set the

speed and duplex to match the network switch

5. Turn Spanning tree off

6. Run the Ping test to ensure communications with the server

7. Go back to the Main Menu, Go to Option 5, boot options

8. Select option 1 Install Device

9. >>>Select the virtual Ethernet adapter –> normal boot–>seletc 1 for sure

10. 1 and Enter for the console

 11. 1 and enter for English

12. Always check the setting, select #2 –>change/show installation settings and install–> Check the

disk settings in option 1

13. If all looks good, use “0” to continue 

14. Done!!

VIOS build
February 3, 2009 — unixskylab

1) Place the VIO Server CD in the CD-ROM

2) Activate the VIO Server in SMS

3) Select boot options –> Install –>IDE (built in dvd) –>Select the device –> Normal boot

4) Follow the prompts to do the install

2) Change Show default settings

1) Check the disk

5) After the LPAR reboots, log in as padmin

Change password

6)  The first time in, accept the license with “license –accept”

7) Create a virtual Ethernet adapter

For dual port NICS, create an Etherchannel Device

Lsdev –Cc adapter <–find out adapters

smitty devices –>Communications –>EtherChannel –>Add

–> Select both physical network cards –> Enter on the SMIT Screen

This creates ent3, the etherchannel device

As padmin

mkvdev –sea ent3 –vadapter ent2 – default ent2 –defaultid 1

This creates the bridge device en4

This creates shared device ent3.  Configure TCP/IP on the shared interface

mktcpip –interface en4 –inetaddr 63.168.157.xxx –hostname viosrvrx –gateway 62.169.157.129 –

netmask 255.255.255.128

Enter root with “oem_setup_env”

9) Create /home/vio directory.

10) cd into /home/vio

11) ftp the files over from server/IBM

12) run “inutoc .  “  to build a table of contents

13) exit root

14) update the VIOS with “updateios –dev /home/vio”

15) Reboot

At this point you sre ready to create LVs for the rootvgs for the LPARs.

Powerpath and AIX
January 29, 2009 — unixskylab

INSTALLATION:

Prereq Files:

EMCpower.base 3.0.0.0

EMCpower.multi_path_clariio 3.0.0.0

EMCpower.multi_path 3.0.0.0

EMCpower.consistency_grp 3.0.0.0

Register PowerPath on the host: emcpreg -install (Enter the 12-character license key)

Validate your registration number using :powermt check_registration

To initialize devices at the command line :powermt config

Commands:

# emc_cfgmgr

# powermt display dev=all

# powermt config

# powermt display

# powermt remove hba=hba#

# powermt restore

# powermt check

How to uninstall -

Stop all applications/processes that access powerpath hdiskpower device.

Varyoff volumegroups that contains hdiskpower device (or) remove hdiskpower devices from the

volumegroups
Uninstall powerpath filesets using or use SMIT

# installp –u EMCpower

To remove powerpath from the system entirely, remove the file “/etc/emcp_registration”

Rsync with expect to pass password on AIX

January 25, 2009 — unixskylab

#!/usr/bin/expect -f

set timeout -1

# now connect to remote UNIX box with given script to execute

spawn rsync -avzW –stats <local dir> id@remotehost: <remote dir>

match_max 100000

# Look for passwod prompt

expect “*?assword:*”

# Send password aka $password

send — “<password>\r”

# send blank line (\r) to make sure we get back to gui

send — “\r”

expect eof

This script can be a  cron  schedule.  For security reasons, I would still prefer to exchange public

private keys to schedule rsync but for some reasons (as in my case remote host was behind DMZ and

could see only gateway IPs as an IP of my local machine).  We can always revoke permissions to this

script as 600 to not to show pwd to others. I’ll post “how to” generate (key-gen) and exchange public/

private keys later.

Install expect on AIX

January 25, 2009 — unixskylab

ftp ftp.software.ibm.com

cd /aix/freeSoftware/aixtoolbox/RPMS/ppc/tcltk

bin

prompt

mget expect-5.42.1-3.aix5.1.ppc.rpm tcl-8.4.7-3.aix5.1.ppc.rpm tk-8.4.7-3.aix5.1.ppc.rpm

Disable Direct Root Login

Allowing the root user to login directly is a major security issue, we'll show you how to disable it so you can still login as root
but just not directly, reducing the security issue.

This will force a hacker to have to guess 2 seperate passwords to gain root access.
(you do have 2 seperate passwords for admin and root right?)
What happens is you'll first need to login as your admin user in SSH, then switch to the super user with the su command to
get root.

We also will be forcing the use of SSH protocol 2, which is a newer, more secure SSH protocol
Just a couple more ways to help your server stay safe from the bad guys. If you're using cPanel make sure you add your
admin user to the 'wheel' group so that you will be able to 'su -' to root, otherwise you may lock yourself out of root.

1. SSH into your server as 'admin' and gain root access by su

2. Copy and paste this line to edit the file for SSH logins
pico -w /etc/ssh/sshd_config

3. Find the line

Protocol 2, 1

4. Uncomment it and change it to look like

Protocol 2

5. Next, find the line

PermitRootLogin yes

6. Uncomment it and make it look like PermitRootLogin no

7. Save the file Ctrl+X then Y then enter

8. Now you can restart SSH

/etc/rc.d/init.d/sshd restart

Now, no one will be able to login to root with out first loggin in as admin and 'su -' to root, and you will be forcing the use of a
more secure protocol. Just make sure you remember both passwords!