alt_disk_copy command is just a subset of alt_disk_install. When we run the alt_disk_install it actually runs the alt_disk_copy as well under cover.

Before proceeding with the alt_clone operation we have to verify the below mentioned file sets available on the server for the alt_clone operation:

#lslpp -l|grep -I alt_disk

bos.alt_disk_install.boot_images

bos.alt_disk_install.rte 7.2.3.0 COMMITTED Alternate Disk Installation

For this we need to get a new luns from the Storage team of equal the size of the good copy existing the rootvg disk or greater than that in size. Then we can follow the below procedure if we have 2 rootvg disks and one disk failed:

#cfgmgr
#lspv
#extendvg rootvg <new_disk_name>
#migratepv <failed_disk> <new_disk>
#reducevg -d rootvg <failed_disk>
#mirrorvg -S <hdisk_old> <hdisk_new>

We need to check for the APAR released by IBM for the software product. If yes, then download it and by using the “emgr” command install it on the server.

We need to boot the server from a bootable media either cd-rom. From there we can go to the option Installation & Maintenance Menu and can choose to start it in a system recovery mode. From there we can reset the root password.

#shutdown -r

#Option 3

#passwd <Enter new password>

chvg -Qn <vgname>

After login into the HMC on the top we can see the <HMC version>.

From the mksysb image file we can restore file by using the below command:

#restore -xvf <mksysb filename> ./<Path of the file to need to restore>/<file_name>

In AIX we have below procedures to find out the maximum resources consumed processes details:

#top: command which provides the live update of the processes and their utilization of resources
From the “nmon analyzer” we can find out the detailed details of the processes.
#ps -ef
#svmon -Put 5

To re-name a VG here is the procedure:

#lspv -> Here disks will show allocated to a VG
#varyoff <vgname_old>
#exportvg <vgname_old>
#lspv -> Here the disks will be showing none means not allocated to any VG
#importvg -y <vgname_new> hdisk*
#lspv -> Here it will show the new vg name

A downtime of VG required for this operation to be done.

With the help of “niminfo” file the client server can communicate with the Master NIM server.

In the client server generate the NIMINFO file:

#niminit -a master=<nim_servername> -a name=`uname -n`

In the “netstat -ia” command from the “Address” column you can find the MAC address.

To collect the system log “snap -gc” command.

By using the “nimadm” command we can do the OS Upgradation.

#nimadm -j nimadmvg -c <lpar_name> -s <spot_name> -l <lpp_source_name> -d <hdisk*> -Y

It has 12 steps post which the OS get successfully upgradaed.

We can change the network card speed by using the following steps:

#chdev -l en0 -a state=detach –> Detach the interface

#chdev -l ent0 -a media_speed=1000_Full_Duplex –> Make appropriate changes

#chdev -l en0 -a state=up –> Change the step to UP

Here is the command to find the real memory of a server:

#lsattr -EL sys0 -a realmem

We can find the detailed information of a server using the below commands:

#prtconf
#lscfg -vpl <devicename>
Whereas,

-v : Displays the vital product data (VPD) found in the customized VPD object class

-p : Displays platform-specific device information.

You can use the “lquerypv” command with the -M flag. The output gives the LTG size in KB.

#/usr/sbin/lquerypv -M hdisk*

If yes how to recover it to it’s previous most recent state?

Here is the procedure to recover a currupted file system:

#fsck -y <lv_name>

#fsck -p <lv_name>

By using DLPAR operation we can online allocate additional CPU/Memory/IO and adapters of a server.
Go to HMC-> Frame-> LPAR-> Right click-> DLPAR operation-> (Choose your respective operation).

If the Maximum resources limit set for a LPAR is reached then DLPAR operation won’t work in that case and a downtime is needed of the server.

Here is the procedure of mapping:

$vfcmap –vadpater vfchost* –fcp fcs* -> Perform the operation on both the VIOs.
Run the “lsmap -all -npiv” command to verify if the mapping for the corresponding client lapar is correct or not.
Run “cfgmgr” on the LPAR
Then to verify the status -> “lsdev -Cc adapter”

Quorum is a validation technique done by LVM to resolve data corruption. Quorum checking is done on the basis of VGDA information available in VG. Greater than 51% votes are needed to allow valid quorum checking.

#we can check the quorum details using the command “lsvg <vg_name>

Here is the process to set the file size limit to unlimited:

#unlimit -f -> To check the current file size limit

#vi /etc/security/limits : set the “fsize=-1” in the default option

Here is the procedure to activate the paging space:

#lsps -a -> Current paging space size
#smitty mkps -> To add paging space
#swapon /dev/<paging space_name>

TL: technology level

Ml: Maintance level

NFS means network filesystem, we can asses the filestem from one server to another server through NFS

We need to configure NFS using below

Lssrc –g nfs it will list nfs subsystems are in active or not, if it is not active we have to activate with below command

Startsrc –g nfs

If you want to activate particular  subsystem you can activate using below command

Startsrc –s nfs

Need to check NFS port no. 2049

We need to find the failed disk using below commands

Lsdev –Cc disk

Lsvg –p rootvg

Errpt –a

If the failed disk is mirrored with disk,  we need to unmirror and reduce that vg from rootvg

And raise a PMR with site engineer  and he wil replace the disk and we will extend that new disk to  existing rootvg and we will  mirror the rootvg

That new disk PVID is conflicts with other disk

For this activity we need to perform with outage

We need to unmount filesytems under the volume group

We need to varyoff volumge group

We need to  exporr the volume group

We need to import the volume group with new name

After that we need to varyon vg and mount the filesystem

Normal vg, bigvg , scalable vg

Normal vg     : 32 disks 256lvs max pps per vg   32512

Bigvg             :128 disks 512 lvs 130048

Scalablevg    : 1024 disks 4096lvs 2097152

Lsfs -q

You need to check the logs in /etc/syslog.conf, ususally all aix logs are stored in this file , otherwise you can check in errpt | more

Still if you want more info you can raise a PMR with IBM team

There is no free pp’s in volume group and we need to extend the  lp’s per lv

When ever ram memory is not enough to load new programs , that time is there any waiting process , those are moving to paging space

TL upgaradation performing in  3 ways

Direct method

Multibos method

Alt disk method

For altdisk method we need to one extra disk which is equal or higher than rootvg disk

Some filesets also need to install

Bos. Alt_disk_install.rte

Bos. Alt_diks_install,images

We need to install  below filesets of nim server, once we install those filesets then only NIM Server configured

Bos.sysmgt.nim.clinet

Bos.sysmgt.nim.maste

Bos.sysmgt.nim.spot

in nim server we can recreate using below.

Niminfo –r

On client side we can create like below

Niminit –v –a master=server –a client=hostname –a nimsh

nimesis and nimd

we can verify using lssrc –g nim

goto the path smitty nim perform nim administration tasks

aix 7.1 tl05 sp01

aix 7.2 tl02 sp02

we can decrease filesytem in jfs2

we can’t decrease filesytem in fs

account got expired, or need to account is locked or not,need to check unsuccessful login account in lsuser –f username

chdev –l eno –a alias4=ip,subnetbask

Once we got the disk from storage we need to run cfgmgr from server end

After that we need to find major and minor number for the disk in /dev

Mknoc –C majorno. Minor no. /dev/disk

I have aix migration from 6.1 to 7.1 using nimadm method

We need one free disk to perform migration using nimadm

Aix migration is happeing in 12 steps

We need to login to console, check the paging space of the server using lsps –s

And we need to increase the paging to avoid houg or fork error

Osversion, tl version, sp version , week and year of release

By using DLPAR we can add remove move the resource from one server to another

Using below command to we wil get to know the server having dlpar capability or not

Lspartition –dlpar

ftp-21,ssh-22,telnet-23,smtp-25,ns-2049,pop3-110,

Its an online activity to convert normal vg to bigvg using below ommand

Chvg –B vgname

Installp –acgxy fileset name filesetpath name

Applied means it will maintain moth old verion and new version

Commited means it will maintain only new version

Install –C all

Lssrc –ls clstrmgrES

Stable, init,

In 6.1 capacity upgrade on demand is there

In 7.1 IBM aware of aix future is there

/usr/es/sbin/cluster/bin/clRGmove –G rgname –n node –m

/usr/es/sbin/cluster/bin/clRGinfo

identifier : runlevel: action: command

2

cat /etc/init.state

topas, svmon -G

lsrsrc “IBM.Management server”

mklvcopy lvname no.of copies pvname

mksysb -iepmx /filesytemname/filename

3GB

capped: processing capacity can never exceed the entitled capacity

uncapped: processing capacity can exceed entitled capacity

smtctl -m on -w now

smtctl -m off -w now

T – factor means that it will change the pp size to increase the efficiency of vg

by using t-factor incrases the pp’ per vg decrase the pp’s per pv

diag command

chvg –Qn vgname

chvg –Qs vgname

-H/W error -S/W error

-Operator error

-Unknown error.