Aix Help

Raja Sekhar Reddy Polu ********************************************************************************
AIX quick reference

This document will not teach you AIX administration. This reference guide help you to re-collect the output and purpose of each command.
Also it describes some common procedures for various tasks. Note: This guide may not be covered all possible causes to fail the command but most.
******************************************************************** AIX Commands output & causes to fail: lspv:Displays information about a physical volume within a volume group o/p: hdisk0 00ce46140986255c rootvg active
lspv -l pvname:List the LVs on the PV o/p: LV NAME LPs PPs DISTRIBUTION hd6 5 5 00..05..00..00..00 lspv -p pvname:List the PP usage for that PV. o/p: PP RANGE STATE REGION LV NAME 1-1 used outer edge bnbn 2-191 free outer edge 192-192 used outer middle loglv00 lsvg:List all Volume Groups. o/p: rootvg sapvg
MOUNT POINT N/A
TYPE jfs2 jfs2log
MOUNT POINT /lp N/A
1 ********************************************************************************
lsvg -o:List all active VGs. o/p: rootvg oravg datavg lsvg -l vgname:List all LVs in the VG. o/p: LV NAME mlv1 loglv00 TYPE jfs2 jfs2log LPs 5 1 PPs 5 1 PVs LV STATE 1 closed/syncd 1 open/syncd MOUNT POINT /mntpt N/A
lsvg -p vgname:List all PVs in the VG. o/p: PV_NAME PV STATE TOTAL PPs FREE PPs hdisk1 active 950 769 hdisk2 active 950 945
FREE DISTRIBUTION 183..16..190..190..190 190..185..190..190..190
lspv Pvname:List the characteristics of PV . 0/p: PHYSICAL VOLUME: hdisk1 VOLUME GROUP: backupvg PV IDENTIFIER: 0000c4baabfeec04 VG IDENTIFIER 0000c4ba00004c000000012aedb88aca PV STATE: active STALE PARTITIONS: 0 ALLOCATABLE: yes PP SIZE: 32 megabyte(s) LOGICAL VOLUMES: 2 TOTAL PPs: 542 (17344 megabytes) VG DESCRIPTORS: 2 FREE PPs: 477 (15264 megabytes) HOT SPARE: no USED PPs: 65 (2080 megabytes) MAX REQUEST: 256 kilobytes FREE DISTRIBUTION: 109..43..108..108..109 USED DISTRIBUTION: 00..65..00..00..00 lsvg VGname:List the characteristics of VG . o/p: VOLUME GROUP: rootvg VG IDENTIFIER: 0000c4ba00004c000000012aecbc50fc
2 ********************************************************************************
VG STATE: active PP SIZE: 32 megabyte(s) VG PERMISSION: read/write TOTAL PPs: 542 (17344 megabytes) MAX LVs: 256 FREE PPs: 480 (15360 megabytes) LVs: 9 USED PPs: 62 (1984 megabytes) OPEN LVs: 8 QUORUM: 2 TOTAL PVs: 1 VG DESCRIPTORS: 2 STALE PVs: 0 STALE PPs: 0 ACTIVE PVs: 1 AUTO ON: yes MAX PPs per VG: 32512 MAX PPs per PV: 1016 MAX PVs: 32 LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no HOT SPARE: no BB POLICY: relocatable
reorgvg Vgname:Reorganizes the physical partition allocation policy for a volume group. reorgvg VGname LVname:Reorganizes the physical partition allocation policy for a Logical volume. cause to fail: 1.If VG is in in-active state. 2.If no free PPs(at least one) available 3.If it is snapshot volume group 4.If it is primary volume group that has a snapshot volume group. 5. Note: The relocatable flag of each logical volume must be set to y with the chlv -r command for the reorganization to take effect; otherwise, the logical volume is ignored. mkvg -y vgname -s (ppsize in MB) pvname: Creates a volume group. cause to fail: 1. If the PV is part of another active VG. 2. If the new PV violates Max PPs/pv according to the specified PP size(in case the version is 5.2 or lower) Note: t-factor automatically assign in versions 6.1 or higher extendvg vgname pvname:Adds physical volumes to a volume group. cause to fail:
3 ********************************************************************************
1.If the PV is part of another active vg. 2.If the LTG size of VG is not support to the new PV to be extended.(If VG is created on 5.3 or lower and varied on using varyonvg -M) 3.If the VG has already filled with max. no PVs 4.If the new PV violates Max PPs/pv 5.If it is snap shot VG. 6.If the VG is in in-active state. 7. reducevg -d vgname pvname reducevg VGname PVID(incase PV is missed) Purpose: Removes physical volumes from a volume group. cause to fail: 1.If Logical Volumes are open, including swap space. 2. If the Volume group is SnapShot VG. 3.If the VG is in in-active state. varyoffvg vgname Purpose:Deactivates a volume group. cause to fail: 1. If Logical Volumes are open, including swap space. 2. varyonvg vgname Purpose:Activates a volume group. cause to fail: 1. VG does not meet QUORUM requirement. 2. if there are any physical volumes in PV_MISSING state. 3.If you use -M flag, and the PVs do not support the specified LTG size. 4. splitvg -y vgname -c copies(1 or 2 or 3) primaryVG Purpose:Splits a single mirror copy of a fully mirrored volume group. cause to fail: 1.If the PV to be split, is not active. 2.If the Primary VG has active Paging Space. 3.If you attemp to split the rootvg. 4.If the specified PV has stale PPs. 5. the mirror exists on a disk or set of disks that contains only this set of mirrors
4 ********************************************************************************
Note:The default is the second copy. --------------------------------------------------------------------joinvg VGname Purpose:Joins a snapshot volume group back into its orginal volume group. mirrorvg -c (copies 2 or 3) vgname pvname purpose:Mirrors all the logical volumes that exist on a given volume group. cause to fail: 1. If no enough free PPs are available in target PVs. 2.If the command violate mirror strictness or affect the policy (such as -m flag 3.If the specified VG is snap shot VG. syncvg [-v][-l][-p] VGname purpose:Synchronizes logical volume copies that are not current. cause to fail: 1.If volume group in read-only mode 2.PVs that contains this copy should be in ACTIVE state. 3. synclvodm vgname purpose: Tries to resync VGDA. LVCB and ODM cause to fail: 1.If the VG is not in active exportvg vgname purpose:Exports the definition of a volume group from a set of physical volumes from ODm. cause to fail: 1. If the VG is in active state. 2. If LVs are in open state. 3. If active paging space there in VG. 4. importvg -y vgname pvname purpose: Imports a new volume group definition from a set of physical volumes. cause to fail: 1.If it BIG VG, and attempt to import into AIX(R) 4.3.1 or lower versions. 2. If it is Scalable VG, and attempt to import into AIX 5.2 or lower versions. 3. Note: do not attempt to import rootvg.
5 ********************************************************************************
mklv -y LVname VGname no.ofLPs PVname purpose:Creates a logical volume. cause to fail: 1.If no free PPs are available. 2.If free PPS are not allocatable. 3.VG has reached to the Max No.of LVs 4.If PV is not in available state. 5. If VG not in active state. 6.If the specified VG is snap shot VG. extendlv LVname no.ofLPs PVname purpose:Increases the size of a logical volume by adding unallocated physical partitions from within the volume group. cause to fail: 1.If no free PPs are available. 2.If free PPS are not allocatable. 3.LV has reached to the Max No.of LPs 4.If PV is not in available state. 5.If VG not in active state. 6.if it is Mirrored LV,and you specify only one PV . 7.If the specied VG is Snapshot VG. 8. migratepv SourcePV DestnPV purpose:Moves allocated physical partitions from one physical volume to one or more other physical volumes. cause to fail: 1.If no free PPs are available in target PV or PPs are not allocatable. 2.If target PV is not part of same VG 3.If it is Primary Vg, which has snap shot VG. 4.If it is snap shot VG. 5.If the source VG contains BLV. 6. logform /dev/LV purpose: To format the Log device used by this LV
6 ********************************************************************************
lslv LVname purpose:Displays information about a logical volume. o/p: LOGICAL VOLUME: hd1 VOLUME GROUP: rootvg LV IDENTIFIER: 0001834f00004c000000012a4f635e5a.8 PERMISSION: VG STATE: active/complete LV STATE: opened/syncd TYPE: jfs WRITE VERIFY: off MAX LPs: 512 PP SIZE: 32 megabyte(s) COPIES: 1 SCHED POLICY: parallel LPs: 1 PPs: 1 STALE PPs: 0 BB POLICY: relocatable INTER-POLICY: minimum RELOCATABLE: yes INTRA-POLICY: center UPPER BOUND: 32 MOUNT POINT: /home LABEL: /home MIRROR WRITE CONSISTENCY: on/ACTIVE EACH LP COPY ON A SEPARATE PV ?: yes Serialize IO ?: NO lslv -l LVname purpose: lists the disks in the logical volume. o/p: hd1:/home PV COPIES IN BAND DISTRIBUTION hdisk0 001:000:000 100% 000:000:001:000:000 lslv m LVname o/p: fslv00:/bs LP PP1 PV1 0001 0111 hdisk1 0002 0112 hdisk1 0003 0113 hdisk1
read/write
PP2 PV2
PP3 PV3
SplitLVcopy -y LVname SourceLV copies 1 or 2 Purpose:Splits copies from one logical volume and creates a new logical volume from them. cause to fail: 1.if the specified LV copy is part of Snapshot VG. 2.
7 ********************************************************************************
Note:it is best practice to unmount file systems before attemp to splitting. mklvcopy LVname copies(2 or 3) PVname Purpose:Provides copies of data within the logical volume. cause to fail: 1. If the target PV is not part of same VG. 2. If free PPs are not available on target PV. 3. rmlvcopy LVname copies(1 or 2) PVname Purpose:Removes copies from a logical volume. cause to fail: 1. rmlv LVname Purpose:Removes logical volumes from a volume group. cause to fail: 1.If the File system residing on this Lv is mounted. 2.If the Lv resides on PrimaryVg or SnapShot VG. 3. chpv -ay PVname purpose: changes PV allocatable state to YES chpv -an PVname purpose: changes PV allocatable state to NO chpv -hy PVname purpose: enables the Physical Volume as hotspare disk. precautions: 1.All PPs should be free,even one PP is used then the command fails. 2.The hotspare disk size should be at least equal or greater than the smallest PV already in the VG. 3.The Pv to be replaced by spare disk should only have mirrored copies of Lvs. 4. chpv -hn PVname purpose: removes the Physical Volume from hotspare pool chpv -vr PVname purpose: Removes a disk from the system cause to fail: 1. If the PV is required in order to maintain a volume group quorum
8 ********************************************************************************
2. chvg -B VGname purpose: changes the VG format to BIG cause to fail: 1.If you try to change Scalable to BIG. 2.each PV whith in the VG should have free PPs to accommodate extra VGDA info.s 3.If the VG contains stale PPs. 4. chvg -G VGname purpose: changes the VG format to scalable. cause to fail: 1.If any stale PPs are there in VG. 2.exch PV with in the Vg should have free PPs to accommodate extra VGDA info. 3.If VG is in active state. Note:VGDA resides on the edge of the disk and it requires contiguous space for expansion so this will rearrange the PPs according to that. chvg -ay VGname purpose: auto vary on the volume group at system start. chvg -t factor VGname purpose: changes the t-factor value of the VG, so that the VG can accommodate bigger disks. cause to fail: 1.If it is scalable VG. 2.If the factor value is beyond 16 and it is normal VG 3.If the factor value is beyond 64 and it is BIG VG 4.If the VG contains stale PPs. 5. chvg -Qn VGname purpose: turn off Quorum checking on a VG chvg -Qy VGname purpose: turn on Quorum checking on a VG chvg -v No.LVs VGname purpose: changes the maximum no.of LVs with in the VG cause to fail: 1.If it is not scalable VG 2.If the no.of LVs specified beyond the Max.LVs allowed. 3.If the no.of LVs specified less than the current no.of LVs. 4.
9 ********************************************************************************
Note:The last logical volume is reserved for metadata chvg -P No.PPs/VG VGname purpose: changes the no.of PPs allowed for a VG cause to fail: 1.If it is not scalable VG 2. chvg -sy VGname purpose: chvg -sn VGname purpose: chlv -n newLVname oldLVname purpose: rename the Logical Volume cause to fail: 1.If the Lv is in open state. 2. chlv -L labelname LVname purpose: chlv -x max.LPs LVname purpose: chlv -sy LVname purpose: chlv -sn LVname purpose: chlv -ex Lvname purpose: chlv -em Lvname purpose: chlv -u(UpperBoundValue) LVname purpose: Note: Mirror Pool concept is available on version 6.1 and later. Note:Mirror Pool works for only scalable VGs. Note:Changes made to the logical volume are not reflected in the file systems. lsfs Purpose:Displays the characteristics of file systems. o/p: Name Nodename Mount Pt VFS Size Options Auto Accounting /dev/hd4 -(#)filesystems jfs 65536 -yes no /dev/hd1 -/home jfs 65536 -yes no
10 ********************************************************************************
lsfs -q o/p: Name Nodename Mount Pt VFS Size Options Auto Accounting /dev/hd4 -(#)filesystems jfs 65536 -yes no (lv size: 65536, fs size: 65536, frag size: 4096, nbpi: 2048, compress: no, bf: false, ag: 8) mount Purpose:Makes a file system available for use. o/p: node mounted mounted over vfs date options -------- --------------- --------------- ------ ------------ --------------/dev/hd4 / jfs Sep 07 16:29 rw,log=/dev/hd8 /dev/hd2 /usr jfs Sep 07 16:29 rw,log=/dev/hd8 mount -v vfs -o log=/dev/log /dev/LV /mnt purpose: mount the Logical Volume temporary . mklv -y logname -t vfslog VGname LPs PVname purpose: create a Logical Volume mount /mnt cause to fail: 1.if FS entry not there in /etc/filesystems. 2.If logdevice not available. 3. crfs -v vfs -d /dev/LV -a log=/dev/log -A yes -m /mnt Purpose: create a file system and adds a file system entry in to /etc/filesystems file. cause to fail: 1.If it is JFS2, the minimum LV size should not be less than 16Mb. 2.If the LV is in read-only mode 3.if the file system name already exists in /etrc/filesystems file. crfs -v vfs -g VGname -a size=sizein MB -m /mnt -A yes cause to fail: 1.If no free PPs are available. 2.If free PPS are not allocatable. 3.VG has reached to the Max No.of LVs 4.If PV is not in available state.
11 ********************************************************************************
5. If VG not in active state. 6. If the specied size is less than 16Mb and it is JFS2 7. chfs -a size=+sizeinMB /mnt purpose: increases the file system size dynamically. cause to fail: 1.If no free PPs are available. 2.If free PPS are not allocatable. 3.If PV is not in available state. 4. If VG not in active state. 5. chfs -a size=-sizeinMB /mnt purpose: lower the file system size dynamically. cause to fail: 1. If it is JFS filesystem 2. If it is JFS2 filesystem exists in 5.2 or lower versions. 3.If data is filled up . 4.If /tmp is full. 5.If you try to reduce the Fs for less than PP size. umount /mnt df -m purpose: shows the mounted file systems usage details o/p: Filesystem MB blocks Free %Used Iused %Iused Mounted on /dev/hd4 32.00 17.66 45% 1705 11% / /dev/hd2 1184.00 519.43 57% 22672 8% /usr chfs -A [yes/no] /mnt chfs -a log=/dev/log /mnt purpose: change the log device for the file system chfs -m /newmntNAME /oldmntNAME purpose: change the file system name. lsps a purpose: shows the paging space details o/p: Page Space Physical Volume Volume Group
Size %Used Active Auto Type

12
********************************************************************************
hd6
hdisk0
rootvg
512MB
1 yes
no
lv
lsps s purpose: shows the paging space usage summary. o/p: Total Paging Space Percent Used 512MB 1% mkps -s (no.of 4MB blocks) -a -n VGname PVname purpose: create paging space. cause to fail: 1.If no free PPs available in VG 2.If free PPs are not allocatable. mklv -y swapname -t paging VGname LPs PVname chps -ay swapname chps -an swapname chps -s (no.of 4MB blocks) swapname purpose: increase the size of paging space. cause to fail: 1.If no free PPs available in VG 2.If free PPs are not allocatable. 3. chps -d (no.of 4MB blocks) swapname purpose: decrease the size of paging space. cause to fail: 1.If the space space has data, and no free space space available on other Paging spaces.. 2.If /tmp is full. swapon /dev/swapname swapoff /dev/swapname cause to fail: 1.If the space space has data, and no free space space available on other Paging spaces 2.If /tmp is full. fuser -uk /mnt purpose: kill the user references using this file system.
13 ********************************************************************************
fuser -uckx /mnt purpose: kill the kernel references using this file system. fsck /mnt purpose: check the file system integrity . o/p: The current volume is: /dev/jeelv Primary superblock is valid. *** Phase 1 - Initial inode scan *** Phase 2 - Process remaining directories *** Phase 3 - Process remaining files *** Phase 4 - Check and repair inode allocation map *** Phase 5 - Check and repair block allocation map File system is clean. fsck -y/-n /mnt lsconf/prtconf m purpose: shows physical memory size lsconf/prtconf k purpose: shows kernel type lsconf/prtconf s purpose: shows CPU lock speed lsconf/prtconf c purpose: shows CPU type getconf a purpose: shows system configuration variable values. lscfg v purpose: Display Vital Product Data of the customized device. lscfg purpose: To display config, diagnostics and vital product definition info rmdev -l CuDv purpose: change the device state from available to defined. rmdev -dl CuDv purpose: delete the device definitions from ODM customized database.
14 ********************************************************************************
mkdev -l CuDv purpose: To change device from defined state to available state cfgmgr v cfgmgr -l vscsi0 purpose: To configure the components connected to the vscsi0 interface host hostname/ip purpose: Resolves ip to host name (from /etc/hosts file) and vice versa. ping -c 1 hostname/ip purpose: test the connectivity between two machines with in the network. o/p: PING 192.168.1.9: (192.168.1.9): 56 data bytes 64 bytes from 192.168.1.9: icmp_seq=0 ttl=255 time=0 ms ----192.168.1.9 PING Statistics---7 packets transmitted, 7 packets received, 0% packet loss round-trip min/avg/max = 0/0/0 ms traceroute hostname/ip nslookup hostname/ip lsattr -El CuDv purpose: shows attributes of customized device . lsdev PH purpose: To lists all supported devices lsdev CH purpose: list all customized devices. lsdev -C -c classname lsdev -P -c classname lsdev -l CuDv -F parent purpose: shows parent device of the specified customized device. lsdev -p CuDv purpose: shows child devices of the specified customized device. lsdev -Cc disk
15 ********************************************************************************
o/p: hdisk0 Available 10-80-00-2,0 16 Bit LVD SCSI Disk Drive hdisk1 Available 10-80-00-4,0 16 Bit LVD SCSI Disk Drive lsattr -El ent0 purpose: list attributes of ethernet adapter ent0 lsattr -El en0 purpose: list attributes of an interface en0 o/p: alias4 192.168.1.7,255.255.255.0 IPv4 Alias including Subnet Mask alias6 IPv6 Alias including Prefix Length arp on Address Resolution Protocol (ARP) mtu 1500 Maximum IP Packet Size for This Device netaddr 192.168.1.7 Internet Address netaddr6 IPv6 Internet Address netmask 255.255.255.0 Subnet Mask state up Current Interface Status lsattr -El sys0 -a realmem o/p: realmem 1048576 Amount of usable physical memory in Kbytes False lsattr -El mem0 o/p: goodsize 1024 Amount of usable physical memory in Mbytes False size 1024 Total amount of physical memory in Mbytes False ifconfig a purpose: shows all interfaces configuration details. o/p: en0: flags=4e080863,80<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAS T,GROUPRT,64BIT,PSEG,CHAIN> inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255 lo0: flags=e08084b<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GR OUPRT,64BIT> inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255 inet6 ::1/0
16 ********************************************************************************
True True True True True True True True
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1 ifconfig InterFace purpose: shows all interfaces configuration details. ifconfig InterFace inet ip netmask ip alias purpose: define alias IP address for an interface. ifconfig InterFace inet ip netmask ip purpose: bind the IP address for an interface as primary IP and it is temporary. ifconfig InterFace up purpose: activates the interface for use. ifconfig InterFace down purpose: disable the interface for use ifconfig InterFace detach purpose: Removes interface card from the network interface list Ifconfig InterFace delete Purpose: deletes primary IP address of an interface. Ifconfig InterFace inet delete Purpose: deletes the specified IP address of an interface. Ifconfig -a -d Purpose: shows all interfaces that are down. chdev -l InterFace -a netaddr=ip -a netmask=ip purpose: bind the IP address to an interface permanently. chdev -l InterFace -a alias4=ip,netmask purpose: define alias IP address permanently. chdev -l InterFace -a delalias4=ip,netmask purpose: delete the specified alias IP address. chdev -l inet0 -a hostname=hostname purpose: change the host name permanently.
17 ********************************************************************************
chdev -l ent0 -a media_speed=Auto_Negotiation P purpose: change media_speed attribute value to Auto_Negotiation entstat -d ent0 o/p: IBM 10/100 Mbps Ethernet PCI Adapter Specific Statistics: -----------------------------------------------Chip Version: 26 RJ45 Port Link Status : up Media Speed Selected: Auto negotiation Media Speed Running: 100 Mbps Full Duplex lssrc -g ResourceGroup lssrc -s SubSystem lssrc -a o/p: Subsystem Group syslogd ras sendmail mail portmap portmap inetd tcpip startsrc -g ResourceGroup ex: startsrc -g nfs startsrc -g portmap startsrc -g tcpip startsrc -g nfs stopsrc -g ResourceGroup ex: stopsrc -g nfs stopsrc -g portmap stopsrc -g tcpip stopsrc -g nfs startsrc -s SubSystem ex: startsrc -s inetd startsrc -s portmap startsrc -s automountd stopsrc -s SubSystem startsrc -t SubServer
18 ********************************************************************************
PID 9288 9546 5572 7528
Status active active active active
startsrc -t telnet startsrc -t ftp stopsrc -t SubServer startsrc -g ResourceGroup -h hostname refresh s inetd purpose: refresh inetd after changes to inetd.conf netstat a purpose: To show the state of all sockets o/p: Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address tcp4 0 0 *.daytime *.* LISTEN tcp 0 0 *.ftp *.* LISTEN tcp 0 0 *.telnet *.* LISTEN tcp4 0 0 *.smtp *.* LISTEN netstat -i purpose: shows interface statistics. o/p: Name Mtu Network Address en0 1500 link#2 0.4.ac.97.97.35 en0 1500 192.168.1 192.168.1.7 netstat -I en0 exportfs a purpose: exports all file systems in /etc/exports file. Exportfs Purpose: shows exported file systems list. o/p: /bs -sec=sys:none,rw /jeefs exportfs -i /mnt purpose: exports file system temporary. exportfs -u /mnt
19 ********************************************************************************
ex:
(state)
Ipkts Ierrs Opkts Oerrs Coll 8107 0 4143 0 0 8107 0 4143 0 0
purpose: unexport file system temporary. showmount -e hostname purpose: shows exported file systems of specified machine. o/p: export list for aix7: /bs (everyone) /jeefs (everyone) showmount o/p: aix6 aix8 showmount -a o/p: aix6:/abc aix6:/mpt1 aix8:/abc exportfs ua purpose: unexports all file systems in /etc/exports file. NFS mount types: Explicit mount: mount hostname:/mnt
/Localmnt
Pre-Defined mount: crfs -v nfs -d /remotemnt -a nodenmae=hostname -m /Localmnt Automount :( here /etc/mapfile is used as mapfile) steps: /etc/auto_master format: /LocalDir mapfile(Indirect Map) /mapfile(Direct Map) /etc/mapfile format: LocalDir -rw,soft,intr hostname:/mnt(Indirect Map) /LocalDir -rw,hard,nointr hostname:/mnt(Direct Map)
20 ********************************************************************************
sysdumpdev l purpose: displays current dump destination o/p: primary /dev/hd6 secondary /dev/sysdumpnull copy directory /var/adm/ras forced copy flag FALSE always allow dump TRUE dump compression ON sysdumpdev L purpose: displays information about the previous dump. o/p: Device name: /dev/hd6 Major device number: 10 Minor device number: 2 Size: 26453504 bytes Uncompressed Size: 168896125 bytes Date/Time: Mon Sep 6 10:15:13 CDT 2010 Dump status: 0 dump completed successfully 0481-195 Failed to copy the dump from /dev/hd6 to /var/adm/ras. sysdumpdev e purpose: estimates dump size of the current system in bytes. o/p: 0453-041 Estimated dump size in bytes: 36490444 sysdumpdev -d CopyDir name purpose: change the copy directory sysdumpdev -P -p PrimaryDumpDevice purpose: change primary dump device permanently. Note: primary dump device must be part of rootvg. sysdumpdev -P -s SecondaryDumpDevice purpose: change the secondary dump device permanently. sysdumpdev -p PrimaryDumpDevice purpose: change the primary dump device temporary.
21 ********************************************************************************
sysdumpdev -s SecondaryDumpDevice purpose: change the secondary dump device temporary. sysdumpstart -p purpose: initiates dump to the primary dump device. sysdumpstart -s purpose: initiates dump to the secondary dump device. sysdumpdev K purpose: enable key sequence Note: Ctrl-Alt-NumPad1 to write to the primary dump device. Ctrl-Alt-NumPad2 to write to the secondary dump device. sysdumpdev z purpose: To determine a new system dump occurred savecore -d DirName purpose: to save the dump from dump device to a file. cause to fail: 1. If the target directory is not having enough free space to store dump. 2. /usr/lib/ras/dumpcheck -p purpose: To check whether the copy directory has enough free space to accommodate dump data or not. errpt purpose: displays summary errorlog repoprt. o/p: IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION 1BA7DF4E 0907163110 P S SRC SOFTWARE PROGRAM ERROR BA431EB7 0907163110 P S SRC SOFTWARE PROGRAM ERROR errpt a
purpose: displays detailed errorlog report.
errpt a -d H/O/S/U -T PEND/PERM/PERF/INFO/TEMP/UNKN errpt -a -s MMDDHHmmYY -e MMDDHHmmYY errpt -j ErrorID errpt -i errlogPath
22 ********************************************************************************
errlogger "string" /usr/lib/errdemon Purpose: starts the errdemon for error logging. /usr/lib/errdemon -l Purpose: display error log attributes. o/p: Error Log Attributes -------------------------------------------Log File /var/adm/ras/errlog Log Size 5242880 bytes Memory Buffer Size 32768 bytes Duplicate Removal true Duplicate Interval 10000 milliseconds Duplicate Error Maximum 1000 /usr/lib/errdemon -i errlogPath /usr/lib/errstop Purpose: stops error logging. bootlist -m normal o purpose: displays bootlist o/p: hdisk0 blv=hd5 hdisk1 cd0 ent0 bootlist -m normal -o DevicesList purpose: change bootlist. bosboot -a -d /dev/ipldevice purpose: creates complete boot image on a Physical VBolume. cause to fail: 1.If you try to create boot image for the PV, which doesn't have hd5. 2.If the specified Pv is not part of rootvg. chpv -c PVname purpose: clear the boot image
23 ********************************************************************************
bootinfo b purpose: identifies the last bootable disk. savebase -d (/dev/pv) purpose: Saves customised ODM info onto the boot device. bootinfo -s PVname purpose: shows size of the disk. who r purpose: shows current run level of the system. o/p: run-level 2 Sep 07 16:30 2 0 S
init [0123456789abchSsMmq] lsitab -a o/p: init:2:initdefault: cron:23456789:respawn:/usr/sbin/cron lsitab init lsslot -c slot purpose: displays available hot pluggable logical slots. lsslot -c pci purpose: displays available hot pluggable pci slots. lslpp -l purpose:Displays the name, most recent level, state, and description of all filesets. lslpp -w filename purpose:Lists fileset that owns this file. lslpp h purpose: shows history of the filesets (installed date) emgr -l emgr -e APAR emgr -r -n APAR lppchk v purpose: checks integrity of the filesets and displays broken filesets. installp C purpose: clears broken filesets.
24 ********************************************************************************
installp -c all[fileset name] purpose: commint all apply mode filesets. installp -a[c] -v -X -g -Y -d (dirname where filesets resides) all installp -r -f file.list(have list of filesets to be commited) purpose: reject current applied filesets. installp -u -f fileset name purpose: un-install filesets installp -L -d /dev/rmt0 instfix -i purpose: list installed fixes. instfix -T -d /dev/cd0 instfix -i -k APAR instfix -k APAR -d /dev/cd0 oslevel oslevel -r oslevel s purpose: to know the TL level and service pack gzip filename gunzip file.gz inutoc dirname purpose: creates Table Of Contents i.e list the filesets in particular order . tar -c -v -f file.tar dirname purpose: create archive file tar -x -v -f file.tar dirname purpose: extract archive file. -------mksysb -i -e /dev/rmt0 purpose: create mksysb bootable backup file of rootvg to the tape drive. mksysb -i -e /mntpt/filename purpose: create rootvg backup to the file. Cause to fail: This process may get fails because of mksysb image file size violates the fsize svalue. mkszfile purpose:Creates /image.data file lsmksysb -l -f backup filename lsmksysb -L -f backup filename lsmksysb -f backupfilename
25 ********************************************************************************
lsmksysb -r -d dirname -f backupfilename ./filename savevg -f /mntpt/filename uservg purpose: take backup of user VG to the file. restvg -l -f backupfilename restvg -f backupfilename pvname find / -print |backup -i -cvf /dev/rmt0 restore -x -v -q -f /dev/rmt0 alog -t boot -o alog -L alog -L -t boot Note: Default snap output directory: /tmp/ibmsupt ------------FTP commands: ------------ftp ip/hostname put get mput mget prompt hash bin ---mkuser username mkuser -a username mkgroup groupname mkgroup -a groupname rmuser username rmuser -p usernmae rmgroup groupname lsuser -f username lsuser -a attribute username lsgroup -a attribute groupname lsgroup groupname chuser attribute=value username
26 ********************************************************************************
chgroup attribute=value groupname chgrp [-R] groupname file/Dir chown [-R] owner:group file/dir newgrp groupname SVTX(1): Sticky bit enables a directory in such a way that only owner and root can remove the files with in the directory and no one else. SUID(4) : SUID upon executable files allow users to run an executable with the permissions of the executable's owner . SGID(2) : SGID upon executable files allow users to run an executable with the permissions of the executable's group. File Descriptors: ----------------0 Standard input 1 standard output 2 standard error aclgetfile/dir acledit file/dir aclget -o outputfile file aclput -i inputfile export EDITOR=/usr/bin/vi ACL stanza: ----------ACL_type AIXC * attributes: base permissions owner(root): rwgroup(system): r-others: r-extended permissions disabled crontab -l crontab -e crontab -v
file
27 ********************************************************************************
crontab -r crontab -l>file crontab file crontab stanza: --------------minute hour day_of_month month weekday command These fields accept the following values: minute 0 through 59 hour 0 through 23 day_of_month 1 through 31 month 1 through 12 weekday 0 through 6 for Sunday through Saturday command a shell command atq at -l at -r JobID at -f file -t [[CC]YY]MMDDhhmm[.SS] The digits in the Date variable are defined as follows: CC Specifies the first two digits of the year (the century). YY Specifies the second two digits of the year. MM Specifies the month of the year (01 through 12). DD Specifies the day of the month (01 through 31). hh Specifies the hour of the day (00 through 23). mm Specifies the minute of the hour (00 through 59). SS
28 ********************************************************************************
Specifies the second of the minute (00 through 59).
Confiruration files: ---------------------/etc/ftpusers This configuration file is used to restrict the specified user for FTP access to the machine. /etc/preserve.list This configuration file is used to preserve the file content during preservation installation. /etc/exclude.rootvg This file contains filesystem name entries and is used to void the mounted file systems during mksysb image backup. Format: ^./MntName /etc/tunables This directory is used to Centralize tunable parameter values.
/etc/tunables/lastboot This file contains tunable parameter values upon last boot. /etc/tunables/nextboot This file is used to save the tunable parameter values upon next reboot. /etc/swapspaces This configuration file is used to save auto active paging space details. Stanza: PagingSpaceName: Dev = /dev/PagingName Auto = yes /etc/filesystems This configuration file is used to save file system details.
29 ********************************************************************************
Stanza: /MntPt: Dev Vfs Log Mount = = = = /dev/LV jfs/jfs2 /dev/LogName true
/etc/exports This configuration file is read by exportfs command in order to export file systems/directories listed in this file. /etc/hosts This configurastion file resolutes the hostname to IP address. /etc/services /etc/hosts.equiv /etc/inetd.conf $HOME/.rhosts /etc/resolv.conf /etc/netsvc.conf /etc/inittab Format of the tab: Identifier:runlevel:action:command -$HOME/.profile /etc/passwd stanza:Username:Password:uid:gid:gecos:home:shell ex:sekhar:!:204:0::/home/sekhar:/usr/bin/ksh /etc/security/passwd stanza:
30 ********************************************************************************
prreddy: password = AOE3k6OiF87Ro lastupdate = 1283204752 flags = ADMCHG /etc/group stanza:groupName:Passwd:gid:users ex:security:!:7:root,prreddy /etc/security/group stanza: security: admin = true /etc/environment /etc/security/environ /etc/utmp /var/adm/wtmp /var/adm/sulog /etc/nologin /etc/security/user /etc/security/login.cfg /etc/security/limits /etc/security/failedlogin /etc/security/lastlog stanza: nil: time_last_unsuccessful_login = 1282951538 tty_last_unsuccessful_login = /dev/pts/6 host_last_unsuccessful_login = 192.168.1.97 unsuccessful_login_count = 0 time_last_login = 1282951965 tty_last_login = /dev/pts/6 host_last_login = 192.168.1.97 /etc/profile /usr/lib/security/mkuser.default stanza: user: pgrp = staff
31 ********************************************************************************
groups = staff shell = /usr/bin/ksh home = /home/$USER admin: pgrp = system groups = system shell = /usr/bin/ksh home = /home/$USER /usr/lib/security/mkuser.sys /etc/motd Rootvg Default filesystems Default PP sizes.. --------------------------------------------hd1 /home PP size PV size hd2 /usr 2MB <300MB hd3 /tmp 4MB <4GB hd4 / 8MB <8GB hd5 BLV 16MB <16GB hd6 PagingSpace 32GB <32GB hd8 LogDevice hd9var /var hd10opt /opt Default VG Charecteristics: OR What is the Limitation of VG? ---------------------------VG TYPE Normal VG Big VG Scalable VG Max.PVs 32 128 1024 Max.LVs 256 512 4096 Max.PPs/VG 32512 130048 2097152 Max PP size 1 GB 1 GB 128 GB
FileSystems differences: ------------------------
32 ********************************************************************************
Function Max.Filesystem size Max File size No.of i-nodes i-node size Fragment Data block size Compression SGID INLINE log File system size decrease
JFS 1 TB 64 GB 16MB 128 bytes 512 bytes 4096 bytes Yes On No No
JFS2 4 PB 4 PB Dynamic 512 bytes 512 bytes 4096 bytes No Off Yes Yes
cfgmgr steps: -----------1.Query the device 2.Get Locator Code 3.Define object and it is in defined state. 4.Load device driver on Kerner and make entry in /dev 5.store info in ODM and turn the device to available state. Diag --------steps:To Certify Media for PVs ->Task Selection (Diagnostics, Advanced Diagnostics, Service Aids, etc.) ->Certify Media steps : To identify a device(PV or ethernet) ->Task Selection (Diagnostics, Advanced Diagnostics, Service Aids, etc.) -> Hot Plug Task ->PCI Hot Plug Manager RAID Hot Plug Devices SCSI and SCSI RAID Hot Plug Manager -> Identify a Device Attached to a SCSI Hot Swap Enclosure Device ->select the disk steps: to add/replace a disk ->Task Selection (Diagnostics, Advanced Diagnostics, Service Aids, etc.) -> Hot Plug Task ->PCI Hot Plug Manager RAID Hot Plug Devices
33 ********************************************************************************
SCSI and SCSI RAID Hot Plug Manager Replace/Remove a Device Attached to an SCSI Hot Swap Enclosure Device Default Port Numbers: ---------------------110 21 22 25 53 80 443 2049 23 pop3 FTP SSh SMTP DNS http https NFS telnet
BLV contains: 1. reduced ODM 2. boot commands 3. rc.boot script 4. kernel EXPLAIN BOOT PROCESS

After POST, the firmware (System Read Only Storage) detects the 1st bootable device stored in the bootlist. then the bootstrap code (software ROS) i.e. 1st 512 bytes of the hard disk loads to RAM. Bootstrap code locates the Boot Logical Volume (BLV = hd5) from the harddisk BLV contains AIX kernel, rc.boot Script, Reduced ODM and Boot commands. Then BLV in the RAM uncompresses and Kernel releases from it. Then AIX Kernel gets control. AIX Kernel creates a RAM File System (Rootvg not activated now). kernel starts init process from the BLV. init executes rc.boot script from the BLV in the RAM. Init with rc.boot 1 configures base devices.
34
********************************************************************************
EXPLAIN BOOT PHASES PHASE I

The init process started from RAMFS executes the boot script rc.boot 1. restbase command copies partial image of ODM from BLV to RAMFS cfgmgr -f reads Config_rules ( which are phase=1) and activates all base devices. bootinfo -b to check last boot device
rc.boot script is passwd to the parameter 2 PHASE II

ipl_varyon to activate rootvg fsck -f /dev/hd4 to check whether "/" unmounted uncleanely in the last shutdown /dev/hd4 is mounted on a temporary mount point /mnt in RAMFS. fsck -f /dev/hd2 i.e. "/usr mount /dev/hd2 in RAMFS. fsck -f /dev/hd9var i.e. check "/var" mount /var copycore command checks whether dump occured. then copy dump from primary dump device paging space (/dev/hd6) to /var/adm/ras/. unmount /var swapon /dev/hd6 i.e. activate primary paging space. mergedev is called and copy /dev from RAMFS to disk. copy customized ODM from RAMFS to hard disk(at this stage both ODM from hd5 and hd4 are sync now) now, root file system from rootvg is mounted over the root file system from RAMFS and /usr , /var filesystems mounted on their ordinary mount points. Because of console not available at this stage all boot messages will be copied to alog.
PHASE III

/etc/init starts and reads /etc/inittab file and calls rc.boot with argfument 3 /tmp file system is mounted.
35 ********************************************************************************

Rootvg is synchronized by calling syncvg command, as result all stale partitions from rootvg are updated. Cfgmgr command is called and all remaining devices are configured now. cfgcon configures console.. synchronization of the ODM in the BLV with the ODM from the / file system is done by savebase command. syncd daemon started. starts errdaemon for error logging. LED display turned OFF. rm /etc/nologin i.e. if the file is not removed, then login is not possible. If any device are in missed state display it. Display "system initialization completed"
The execution of rc.boot is has completed .process init will continue processing the next command from /etc/inittab.
---------------BOS INSTALLATION STEPS -----------------1. After POST, you listen beep sound then press F1 in order to Boot the server in to SMS mode 2.Insert the AIX volume 1 CD into managed CD device. 3.SMS menu shows you the following icons i.config ii.multiboot iii.utilities iv.exit select multiboot in order to set boot list sequence. 4.Then menu icons appear as follows i.select software ii. software default iii.instal from iv.boot sequence v.OK prompt vi.exit
36 ********************************************************************************
select boot sequence 5.It shows list of bootable devices, give the boot priority to CD-ROM and exit from SMS mennu. 6.It will start loading the CD-ROM and ask you to configure the console by pressing F1 and enter. 7.press 1 and enter to select the English during install. 8.then the following menu will appear 1.start install now with default settings 2.change/show installation settings & install 3.start Maintenance mode for system recovery. 9.Select 2 in-order to change the installation settings such as, 1.Method of Installation ------------------New and complete over write OR Preservation OR Migration 2.Disk where you want install ---------------------hdisk0 OR any other disk. 3. More options Enable 64-bit kernel -----------------------Yes Create JFS2 file systems----------------------Yes Graphics software---------------------------Yes Note: Once you have made the required changes press 0 and enter says that, install form the current settings stated above. Then installation starts. ------------------------Installation Methods 1.New and complete over write 2.Preservation 3.Migration ------------------------------------------------Difference between installation types. ----------------------------------37 ********************************************************************************
Installation steps Create rootvg Create /,/var,/usr,/tmp Create filesystem /home Save configuration Restore BOS Install additional filesets Restore Configuration
New&Complete over write Yes Yes Yes No Yes Yes No
Preservation No Yes No No Yes Yes No
Migration No No No Yes Yes Yes Yes
TERMINOLOGY -----------LVM LP PP PV VG VGDA VGSA LVCB ODM SRC ARP RPC RAMFS System ROS Software ROS POST IPL BLV Runlevel : A runlevel is a software configuration of the system that allows only a selected group of processes to exist. patch fix fileset A fileset is the smallest individual installable unit in the LPP.
38 ********************************************************************************
Package A package is a collection of related filesets. LPP An LPP is a group of packages that tend to fall with in one product type. Bundle Bundles are simply formatted lists of packages to be installed as a unit(group of LPPs) ML- Acronym for Maintenance Level TL Acronym for Technology Level, TL is set of fixes and new functions added and new hardware support. APAR PTF bff
Procedures: 1.can not change password of the user. ->Make sure that the SUID bit is enabled to the /usr/bin/passwd file. 2.how to change the log device name assosiated to the file system. ->chlv -n newLogname oldLogname ->chfs -a log=/dev/newLogname /mntpt Note: changes been done for an LV, doen't update /etc/filesystems. 3.how to change kernel type to 64 bit. Steps: # ln -sf /usr/lib/boot/unix_64 /unix #ln -sf /usr/lib/boot/unix_64 /usr/lib/boot/unix #bosboot -a -d /dev/iplDevice #shutdown -r 4.How to move VG from one machine to another machine. ->Un-mount all file systems with in the VG. ->swap off paging space, if it is exists. ->varyoffVG ->exportVG ->remove device definations using rmdev -dl PVname ->Physically remove PVs from this machine and connect to other machine. ->configure the device using cfgmgr
39 ********************************************************************************
->importVG ->run fsck on file systems ->mount file systems ->start using file systems. 5.How SUID & SGID works -> -rwxrwxrwx prreddy admin prg1 -rwx-----prreddy admin newfile Here, the prg1 is the script which is intended to write some content to the newfile . Because prg1 have exe permissions for others, others can run this script but others dont have write permissions to newfile and hence it will give error . SOLUTION:Enable SUID -rwsrwxrwx prreddy -rwx------ prreddy admin admin prg1 newfile
Now the program runs as if the owner is executing hence the others can write data to the newfile. 6.how will you recover the root password. 1. Insert the product media for the same version and level as the current installation into the appropriate drive. 2. Power on the machine. 3. When the screen of icons appears, or when you hear a double beep, press the F1 key repeatedly until the System Management Services menu appears. 4. Select Multiboot. 5. Select Install From. 6. Select the device that holds the product media and then select Install. 7. Select the AIX version icon. 8. Define your current system as the system console by pressing the F1 key and then press Enter. 9. Select the number of your preferred language and press Enter. 10. Choose Start Maintenance Mode for System Recovery by typing 3 and press Enter. 11. Select Access a Root Volume Group. A message displays explaining that you will not be able to return to the Installation menus without rebooting if you change the root volume group at this point. 12. Type 0 and press Enter. 13. Type the number of the appropriate volume group from the list and press Enter.
40 ********************************************************************************
14. Select Access this Volume Group and start a shell by typing 1 and press Enter. 15. At the # (number sign) prompt, type the passwd command at the command line prompt to reset the root password. For example: 16. # passwd 17. Changing password for "root" 18. root's New password: Enter the new password again 19. shutdown r re-bounce the machine. 7. TL upgradation steps 1.login as root #su root, and check installed fixes integrity using lppchk v Note: If installed filesets are in-consistent ,Applying a TL will not be successes and tend to give problems. : 2.oslevel s verify the current Technology Level and Service Pack. 3.Make sure that you backup your system using mksysb 3. create a dedicated file system to store TL, because this process will avoid altering the other file systems size. 4.installp c ALL commit all installed filesets. 5.download the Technology Level you want to upgrade from IBM web site www.ibm.com/support/fixcentral 6.downloaded TL is stored in local computer, use coreFTP or equivalent software to send it to dedicated TL file system in AIX machine. 7.create .toc file using inutoc, you can run this command in the directory where your filesets reside. 8.smit update_all use this fast path to install the updates. Note: It is always best practice to run in pre-view mode before the actual installation. Preview mode does nothing except validate whether something might be missing as a prerequisite of the update. Note: TL updates always be committed, because they can not be rejected. 9. bosboot a d /dev/ipldevice recreate the boot image. 9.once installation completes then recycle the box. 10.Verify the TL upgradation using #oslevel s 8.How will you increse file system size.
41 ********************************************************************************
1. df m check current file system size and LVname 2. lslv lvname check PP size and current no.of LPs and the VGname 3. bc calculate needed free PPs to increase the file system size, confirm that free PPs are available using lsvg VGname 4. If there are not enough free pp's then add a disk to a volume group using extendvg VGname PVname 5..chfs -a size=+size in MB increase the file system size. 6.df m verify the new file system size. 9.user can able to ping to the remote host, but not able to login. What could be the problem? OR A system is echoing the ping but not able to login via telnet why ? ->tcp demons may not be working at remote host. -> media_speed of ethernet adapter may not be synchronizing between client and remote host. 10.How to format inline log device. #logform /dev/LVname 11.How to configure a environment. 1.start the NFS daemons at server side and client side. startsrc -g portmap startsrc -g nfs make sure that daemons are started on the server and client. lssrc -g portmap lssrc -g nfs Note: portmap daemon must starts before starting nfs daemons. 2.export the file systems that need to be remotely available. exportfs -i /mnt (temporary) exportfs a (permanent) Note: in order to export a file system permanently make sure that you made entry in /etc/exports file. confirm whether the file systems successfully exported or not # share 3.mount the exported file systems on the remote machine(client) i.explicit mount mount hostname:/mnt /Localmnt
42 ********************************************************************************
ii. pre-define mount crfs -v nfs -d /RemoteMount
-a nodename=hostname -A yes -m /LocalMnt
iii. auto mount add entry to the /etc/auto_master file and respective map file. steps: /etc/auto_master format: /LocalDir mapfile(Indirect Map) /mapfile(Direct Map) /etc/mapfile format: LocalDir -rw,soft,intr hostname:/mnt(Indirect Map) /LocalDir -rw,hard,nointr hostname:/mnt(Direct Map)
12 How to determine the tape block size #tcopy /dev/rmt0 13.If NFS Mount failes to mount with following error message RPC: 1832-019 Program not registered : how will you troubleshoot it. Steps: #stopsrc s nfs #stopsrc s portmap #startsrc s portmap #startsrc s nfs 14.How will you initiate system dump. 1.sysdumpdev lcheck the primary dump device and copy directory. 2.sysdumpdev Lsee last dump status. 3.sysdumpdev esee the estimated dump size OR 3./usr/lib/ras/dumpcheck -p to see the estimated dump size and copy directory size. 4.calculate whether dump device and copy directory has enough space to store dump data. 5.if free space is not enough increase the corresponding file system size and corresponding LV size for dump device. 6.sysdumpstart -p initialize the system dump.
43 ********************************************************************************
7.system will re-bounce, then check the dump status using sysdumpdev -L 15.Procedure to remove a file system
1. Unmount the filesystem using umount /mnt
2. rmfs
/mountptname
16. while extending the file system size it showing the error like below how will you
troubleshoot. Error Message: 0516-787 extendlv: Maximum allocation for logical volume <LV_Name> is 512. Solution:
o o
Maximum number of LPs for the logical volume has been exceeded - must increase the allocation Calculate the number of LPs needed = LV Size in MB / LP size in MB chlv -x <new_max_lps> <logical_volume>
17.Procedure to reduce the size of a file system(JFS) - shareold is 8mb and needs to be reduced to 4mb 1. Create the file system 1. crfs -v jfs -m /usr/sharenew -g rootvg -a size=8192 2. this makes a logical volume in the root volume group of 4MB that uses jfs 2. Mount the volume 1. mount /usr/sharenew 3. Move the files from the old file system (/usr/shareold) 1. cd /usr/shareold 2. tar -cvf - | (cd /usr/sharenew; tar xvf -) 3. cd 4. Unmount the file systems 1. umount /usr/sharenew 2. umount /usr/shareold 5. Remove the old file system and it's logical volume 1. rmfs /usr/shareold 6. change the file system name
44 ********************************************************************************
Raja Sekhar Reddy Polu ******************************************************************************** 1. chfs -m /usr/shareold /usr/sharenew 7. Mount the new filesystem
1. mount /usr/shareold 8. Delete the temporary mount point 1. rmdir /usr/sharenew 18.Procedure to create Logical Volume and filesystem in a volume group using JFS:
1. lsvg to determine the size of the PP 2. lslv in similar logical volumes to determine if mirroring is in effect
3. Calculate the number of PPs needed for the logical volume 1. bc 2. scale=2 3. <size of lv in MB>/<size of PP in MB> 4. quit 4. mklv -y "<LV_NAME>" <VG_NAME> <# of LPS> --> creates the logical volume 5. crfs -v jfs -d <LV_NAME> -m /<MOUNTPOINT> -A yes --> makes the filesystem, creates the mountpoint and puts it in /etc/filesystems 6. mount /<MOUNTPOINT> --> mounts the new fileystem 7. df /<MOUNTPOINT> --> verifies the mount and the size of the new filesystem 8. Check the ownership and permissions of the new mount point ls -ld <mountpoint> chown owner:group <mountpoint> chmod XXX <mountpoint> If mirroring is in effect, then mirror this logical volume to another disk (original and 1 mirror): o mklvcopy -sy <LV_NAME> 2
o o o
2.
10.Check to see if all of the logical volumes in a volume group are mirrored lsvg -l VGname
19.A system is able to ping within the network but not outside why ? Check default gate way address 20.How will you log in or start the system in what mode if you dont know the root password?
45 ********************************************************************************
Maintenance mode 21.What is ip address and subnet means ? IP address: IP address is the length of 4 octates logical address to identify a machine with in the network. subnet: subnet divide a single network into multiple logical networks to allow multiple systems to share the same internet address class. Subnet mask: subnet mask let the operating system to identify host part and the network part of the IP address 22.There is too much of processor utilization what could be possible reason? Due to interrupts due to more i/o operations and waiting for i/o request 23. What is a sticky bit what is the effect on file and directory ? Sticky bit enables a directory in such a way that only owner and root can remove the files with in the directory and no one else. Sticky bit enables a file in such way that, once the file is loaded in to the RAM it will not be freed out even though the execution has completed. 24.Procedure to create a volume group: OR Tell me Steps to configure the VG?
1. lsdev -C -c disk -> lists available disks (and the hdisk#) on the server
2. lspv to make sure that the PV is not part of any VG 3. mkvg -y "<VG_NAME>" hdisk# --> creates the volume group on the named hard disk 4. varyonvg <VG_NAME> --> activates the volume group 25.Procedure to add a disk to a volume group (extend the volume group) OR How do u add a new disk in VG?
46 ********************************************************************************

lspv to make sure that the PV is not part of any VG lsvg VGname check current number of PVs with in the VG. extendvg <vg> <disk#> lsvg -p <vg> Verify the disk has been successfully added to the vg
26.What are the Attibutes of LVM? OR Components of LVM LV,PV,VG,PP,LP
27.Describe about LVM Adva/Dis.Adv? Advantages: The ability to make instantaneous snapshots of entire Volume Group. so that you can backup the snapshot without worrying about racing ongoing activity High data availability due to mirroring technique. File system consistency more due to logging facility.
Disadvantages: Changes been made to the Logical Volume will not effect the file system. LVM not supports to decrease the size of JFS file system. 28.How do u find the fix is installed? instfix -i 29.Attributes of FS? Super block, inode, data block, fragments, allocation map 30.Procedure to mirror the rootvg:
1. lspv --> determine the hdisk# 2. extendvg rootvg hdisk<number> --> add the hdisk to the volume group 3. lspv --> verify that the hdisk has been successfully added to the volume group 47 ********************************************************************************
Raja Sekhar Reddy Polu ******************************************************************************** 4. chvg -Q 'n' rootvg --> change the quorum so that the vg will stay active if one of the 5. 6. 7. 8. 9.
mirrors fail mirrorvg -S -c 2 rootvg --> mirror all of the logical volumes in the volume group lsvg -l rootvg --> verify successful mirroring (pps will appear "stale" until synchronization is complete). bosboot -a --> update the boot image information bootlist -m normal -o hdisk0 hdisk1 --> create a new bootlist bootlist -m normal -o --> verify the bootlist is correct
31. How to mirror logical volume? Mklvcopy LogicalVolumeName syncvg VolumeGroupName Numberofcopies
32. To remove an active paging space "paging00" 1. Deactivate the paging space using swapoff /dev/PagingName commnad 2.. remove the paging space using rmps command 33. Where ODM Object Class files are stored? This can be defined in /etc/environment file. The ODM object clases are held in three repositories 1. /etc/objrepos 2. /usr/lib/objrepos 3. /usr/share/lib/objrepos 34.Running the lsfs command fails to display any output. But the df command is working and display normal file systems. ->/etc/filesystems is missing or there is no entry in /etc/filesystems. 35.Reasons for upgrading the TL 1.when your TL is going out of the available support period. 2.you want to use the new features and functionality of TL 3.you want to test a new distribution level. 36. How will you fire mksysb.
48 ********************************************************************************
1.lsvg -l rootvg 2./etc/exclude.rootvg 3.mksysb i e /dev/rmt0 Note: this process may get fails because of mksysb image file size violates the fsize svalue. 37.How will you determinbe how much free /tmp needed to run mksysb bosboot q -=a d hdisk0 38. How to restore mksysb image from tape drive. 1.make sure that tape drive is attached to the machine 2.boot the server in to the SMS mode. 3.select multibootbootsequence set boolist to tape drive and exit 4.then server starts booting from tape, press F1 and enter to configure console 5. press 1 and enter to select English as language during install. 6.select starts maintenance mode for system recovery 7. select install from the system backup 8.provide the options such as disk, where it need to be restored 9.then it will starts restoring data from tape to disk.
39. Differentiate the terminologies ML and TL ML is acronym for Maintenance Level, IBM were using this terminology to release updates. After they have renamed it to TL, TL is acronym for Technology Level, and they have included service packs from that time on wards. 40. Describe the mksysb tape data layout OR What are the mksysb components. mksysb has 4 important components: 1. 2. 3. 4. BOS boot image. mkinsttape image. dummy.toc rootvg data
BOS Boot Image
49 ********************************************************************************
This is the first image in mksysb backup. BOS is Base Operating System. It contains kernel device drivers. Its used to boot the system from mksysb image. It uses block size of 512 KB. mkinsttape Image mkinsttape is the second image in mksysb backup. It also uses block size of 512KB. It has 3 important files: ./tapeblksz This contains block size on tape which was set at the time of taking backup. ./bosinst.data This file contains customized BOS install procedure. This is used to tailor the mksysb to adjust to the target system. ./image.data This file has the information regarding sizes, names, maps and mount points of logical volumes(LVs). This file can also be customized using mkszfile command. It can be used to exclude certain files and directories from mksysb backup. dummy.toc It contains dummy Table of Contents. Its used so that mksysb tape will have same number of images as on BOS install tape. rootvg Data This has all of the data of rootvg. Whatever filesystems are mounted at the time of mksysb image, will be backed up.
41. how to run 64-bit application on 32-bin machine -----------------------------------------------enable 64-bit application using smitty smitty->System Environments->Enable 64-bit Application Environment->Enable Now --------------------------------------
50 ********************************************************************************
42. Ethernet adapter replacement procedure. ->ifconfig en0 down" in-activate the interface ->ifconfig en0 detach" remove the interface configuration. ->rmdev -dl en0" remove interface definations from ODM ->rmdel -dl ent0" remove adapter definations from ODM ->remove and replace the new adapter ->cfgmgr ->lsdev -Cc adapter" check the adapter is available ->lsdev -Cc if" check the interface is available ->chdev -l ent0 -a netaddr=ip -a netmask=ip " configure the interface. ->ifconfig en0" determine everything is fine. 43.System prevents user logins what could be the reason. ->system has /etc/nologin file. ->/etc/passwd or /etc/security/passwd file missing. 44..user can not login to the machine. ->password got expired. ->user account got locked. ->unsuccessful_login_count crossed the login retries. ->rlogin set to false(in case of remote login). ->account got expired. 45.user can not create file what could be the reason. ->user reached max.number of files limit. ->dont have enough permissions to the directory. ->not enough free space in the /var file system. -> 46. whith in the subnet one machine is working and the other not, how will you troubleshoot. Check MAC address of these interfaces using arp -d hostname 47.mksysb image restore from tape fails. ->check the tape block_size attribute and set it to 0. 48. Mksysb image restore fails through NIM master but ping is success. ->oslevel of mksysb image is greater than the oslevel of NIM master. 49.Explain different phases in Altdisk
51 ********************************************************************************
Altername disk installation will be done in three phases.. PHASE I: create clone of the rootvg PHASE II: install any software updates PHASE III: set bootlist order and rebounce the machine if, specified. 50. I ran an 'alt_disk_install X rootvg '/ 'alt_rootvg_op X rootvg' by mistake and when i run lspv, my rootvg entry is gone. What do I do? # redefinevg -d hdisk0 rootvg # synclvodm -Pv rootvg
51.How will you Clone a rootvg and up grade the TL using alternate disk installation
1.lspv check for PVs available.make sure that the PV should have equall size or greater than rootvg disk. 2.lslpp -L bos.alt_disk_install.rte check the fileset installed or not , if not install it. installp -cYgvX -d /dev/cd0 bos.alt_disk_install.rte 3. execute alt_disk_install command in three phases. PHASE I: alt_disk_install -C -P1 PVname PHASE II: alt_disk_install -C -P2 -b update_all -I agXY -l /DIRname PVname PHASE III: alt_disk_install -C -r -P3 PVname 4.lspv confirm that rootvg changed to old_rootvg 5.bootinfo b confirm that the system is booted from alt disk. 52. what is multibos Multibos concept create and maintain two separate, bootable instances of the AIX OS within the same root volume group (rootvg).
53. will you configure NIM master 1.install the pre-requisites from volume 1 bos.sysmgt.nim.master bos.sysmgt.nim.spot bos.sysmgt.nim.clent smit install 2.configure nim network Smit nimconfigure NIM environmentadvanced configurationconfigure NIM master onlygive network name and the interface name 3.confirm that network is configured lsnim -c network
52 ********************************************************************************
4.define resources Smit nimperform nim administrative tasksmanage resourcesdefine resourceselect resource create resource by filling the options. 5.define machine Smit nimperform nim administrative tasksmanage machinesdefine machine 7.perform bos_inst operation on client machine either PULL or PUSH method. 8.chec k installation progress of the client machine. # lsnim -l MachineName
54.How will you do TL up gradation on client machine using NIM 1. I make sure that the NIM master oslevel is equal or greater than the oslevel of the Server. 2. Then download the latest TL . 3. bring it to the NIM master and keep in the dedicated file system. 4.define lpp_source resource for TL. 5.define a machine, Make sure that server is in up 6.perform TL up gradation on client. Smit nimperform NIM software installation and maintenance tasksinstall and update softwareupdate installed software to latest level(update all)select hostname,lpp_source,accept the licence. 7.rebounce the server through nim smit nimperform NIM administrative tasksmanage machinesperform operations on machines select machineselect reboot 55.how will you do non-prompted installation on NIM client using PUSH method. Make sure that NIM master have resolution in /etc/hosts for client machine Define machine Make sure that you have created mksysb resource. Make sure that you have created SPOT for the mksysb resource Extract the bosinst_data file from mksysb image and edit the options for preprompted installation by putting PROMPT=no Add bosinst_data to the resource list. Make sure that client machine have /etc/niminfo file reflecting correct NIM master information. Perform bos_inst operation on client machine using PUSH method.
53 ********************************************************************************
Now, the client machine automatically boots with interface as first boot device and starts installation with out user intervention. 56.Create a mksysb image of remote machine using NIM 1.login to the NIm master 2.define the machine as NIM client. Add resolution entry in to the /etc/hosts file. Smit nimperform NIM administrative tasksmanage machines define machinegive machine name and the interface details 3.confirm that the machine added as NIM client lsnim -c machines 4.make sure that you have file system(/export/images) to store mksysb image. 5.fire the mksysb on NIM client Smit nim perform NIM administrative tasksmanage resourcesdefine resourceselect mksysb give Resource Name,location of resource,set create mksysb image files option to yes and provide the client name. Then it will starts firing mksysb on NIM client. 57.NIM classes&objects Machines Network Master Ent Standalone Tok Diskless Fddi Dataless Atm Alternate_master Generic Resources Lpp_source Spot Mksysb Bosinst_data Script Image_data Installp_bundle Groups Mac_group Res_group
58.What is SPOT SPOT is acronym for shared product object tree, This is one of the NIM resource object and is having /usr content i.e binary files and library files also the kernel . This content is useful when doing BOS installation on NIM client. 59. Describe something about non-prompted installation using NIM. when client machine is installing through NIM mksysb resource, it will ask the user to configure the console and the language as well as the disk where to install but if If no one is on the other side making these choices, then your NIM client will patiently sit and wait at the Please Define the System Console prompt for all eternity. Using a bosinst_data resource
54 ********************************************************************************
will have pre-answered options. The purpose of the bosinst.data file is generally to run nonprompted installations. 60. How will you de-allocate resources for the NIM client. smit nimperform NIM Administration Tasks manage machinesperform operations on machinesselect the clientselect reset Note: when it is required If you want remove the machine from client list. If you want to allocate another resource to the client machine, make sure that you have de-allocated the resources for this client. 61.what are the pre-requisites needed to set up a machine as NIM master. 1. bos.sysmgt.nim.master 2. bos.sysmgt.nim.client 3. bos.sysmgt.nim.spot 62. what is /etc/niminfo file. NIM uses this configuration file in-order to keep master information. On the Master : This file is built when you first initialize the NIM environment. This is contains master information. On the Client : If the NIM client is up and running, and you intend to perform operations on the client (like take backups, or install maintenance) you will want to make sure this file exists. This file contains not only hostname information for the client, but tells the client who its master is. NOTE: This also should not be edited manually. If there is incorrect information in the file, it should be removed and recreated 63. Tell me the NIM installation methods and explain those. PULL The NIM master will setup for the install, but not initiate it. All resources will be allocated - and the master will wait for a bootp request from the NIM client.
55 ********************************************************************************
In order to initiate this request, the NIM client must be booted to SMS (System Management Services). At the SMS menus you can enter the IP address information, set the bootlist, and initiate the boot. This method is required for systems that are unable to boot into normal mode, or for those systems that have no operating system on them. PUSH The client machine must have the bos.sysmgt.nim.client fileset installed Client machine must have /etc/niminfo file reflecting correct NIM master information. The NIM master will reset the bootlist to reflect the network adapter defined in NIM, allocate all appropriate resources, and initiate a system reboot. This installation method is commonly used when installing systems in a remote location using a bosinst_data resource to allow for non-prompted installations. Provided are two examples of running a push install to a NIM client. force-PUSH The master initiates the bootlist change and reboots the client. In this case however, the client is not necessarily configured as a client of the NIM master. In order to accomplish this, you need to meet 2 requirements. 1. The NIM master must have rsh permission to the client. 2. You need to have and allocate a bosinst_data resource. It doesnt have to be for a non-prompted install or pose any sort of configuration usage for the install, but one has to be allocated 64. NIM installation encountered bootp failure, how will you troubleshoot it. make sure that bootps deamon is running on NIM master. check the /etc/bootptab file to confirm that, this file is having correct client information to take up bootp request. make sure that you initiated bosinst operation on client machine. lsnim l clientname and see the Cstate attribute. Make sure that you have given corrent gate way entry. make sure that your network is working properly Enable the bootps deamon in debug mode and see the bootp request is reaching to the NIM master or not. Stopsrc t bootps Bootpd s d d d -d 65. When a bos_inst operation is performed on a client, what effects will occur on the NIM master.
56 ********************************************************************************
Raja Sekhar Reddy Polu ******************************************************************************** 1. A link is created in /tftpboot to a boot image matching the platform type, kernel type,
and network adapter of the client. 2. The /etc/bootptab file is updated with client information to allow the boot image to be used. 3. A ClientName.info file is created in /tftpboot to provide client-specific installation and configuration information in the boot environment. 4. The /etc/tftpaccess.ctl file is modified, if necessary, to allow access to the /tftpboot directory. 66. what is the use of /tftpboot directory. This directory should always exist on the NIM master. The main purpose of this directory is to hold the boot images that are created by NIM when a boot or installation is initiated. This directory also holds informational files about the clients that are having a boot or installation operation performed. The file names that are generated in both cases are very descriptive file names. The format of the file name is <spotname>.<system_architecture>.<processor>.<adapter_type> The client info files are aptly named : <clientname>.info The NIM master will create the <client_hostnamename> file and link it to the boot image. This boot image is what is sent over to the NIM client during a boot/installation operation. 67. If pageins and pageouts are more what will you do? Create one more paging space Rearrange the paging space allocation policy to outer middle I will make sure that paging spaces are not in the same disk or in the busy disk. 68. What is the diff b/w hard mount and soft mount? A soft mount will return an error if the source / target system goes offline. A hard mount will wait until the system comes back online, and then begin transferring /copying again. 69. Have you raised IBM S/w call or H/w call? We raise hardware call if any hard ware defect in the server, for this we need to provide basic information such as, What is the issue with hardware device Client name Server locator code(topat id)
57 ********************************************************************************
Server address Machine serial number machine type Machine model Customer name Hunt ID(team contact number) Mail id(team mail id) Contact person Severity level Support type Preferable contact (mail or call) Then ,CE will give 7-digit alpha-numeric reference code ------ if we face any software issue, We provide this information to the ITS department. Server Locator code Server address Company name Username and password oslevel machine serial number machine model name mail id severity level support type then CE will give numeric reference code
70. What and all resources are required to do installation? lpp_source spot 71..Have you done installation on the any new server? Yes, I have installed the new server with AIX 6.1 through NIM master. 72. What are the filesets required to become a server as nim master bos.sysmgt.nim.master bos.sysmgt.nim.client
58 ********************************************************************************
bos.sysmgt.nim.spot 73.what is dif b/w applied mode and committed mode and which one you will prefers? If filesets are installed in apply mode then the current version come to the functional state and old version willl not be removed but it keeps in /usr/lpp/packageNmae DirectoryName. In case the new version is not compatible the we can roll back to the previous version by rejecting the new one. Where as, if you install a fileset in committed mode the old version will be remove completely and the new version will come to the functional. Roll back is not possible to go to the old version. Note: if the fileset is installing very first time and by that time the system doesnt have any versions of this fileset then, the fileset will be installed in committed mode only even though you specify apply mode. 74. What is diff b/w TL and ML ML is acronym for Maintenance Level, IBM were using this terminology to release updates. After they have renamed it to TL, TL is acronym for Technology Level, and they have included service packs from that time on wards. 75.How will you know fileset is in applied state or in committed state # lslpp l FileSetName 76.how will you know ML level? # oslevel r 77. How you exclude unwanted file from rootvg backup? By adding entry in the configuration file /etc/exclude.rootvg Format : ^./mntpt 78. what is inline log device. File system is used the same LV in-order to store LV meta-data tractions. 79.backup a directory to the tape drive. Ans: by using TAR command Syntax: # tar cvf /dev/rmt0 DirName
59 ********************************************************************************
80.difference between different AIX OS versions.

AIX 6.1 supports disabling jfs2 file system logging Mount -o log=NULL /mnt In AIX 6.1 appears in black letters In AIX 5.3 appears in green letters AIX 6.1 is 64-bit application AIX5. 3 supports 32-bit also 64-bit application. AIX 6.1 includes nmon tool as part of the base operating system. AIX 4.3 does not support to decrease the JFS2 file system size.
81. Explain the vmstat output o/p: System configuration: lcpu=1 mem=512MB kthr memory fre page re pi 0 0 0 0 po fr 0 0 0 0 0 0 0 0 sr cy 0 0 0 0 faults in sy cs 6983 cpu us 18 20 17 sy 69 66 70 id wa 0 14 0 15 0 13 0 13
r b avm
1 0 37677 83918 0 2 0 37479 84138 0 2 0 37480 84136 0 1 0 37480 84136 0 Kthr:
0 992 48000
0 1010 48174 7115 0 1007 47992 0 1023 48786 7090 7212
20 67
It shows how many threads are placed on various queues over the sample period. r: tells how many threads are waiting in the run queue. b: tells how many threads are waiting in the wait queue. Analasys: Memory: Virtual Memory Manager controls memory and paging space on the system. avm: tells the average number of 4-kb pages that are allocated to paging space.
60 ********************************************************************************
fre: shows average number of free real memory pages. Page: This column shows information about page faults and paging activity. This value pi: shows number of pages paged in from paging space po: shows number of pages paged out to paging space fr: shows number of pages that were freed out by the page-replacement algorithm during the interval. sr: shows the number of pages that were examined per second by the page-replacement algorithm during the interval. cy:
faults: in: number of interrupts made to the system per second during the sample interval . sy: number of system calls made to the kernel per second during the sample interval. cs: number of context switches per second observed during the interval. cpu: us: shows % of CPU time spent in user mode. sy: this column details the % of time the CPU was executing a process in system mode. id: shows % of time that the CPU is idle or waiting, with out pending local disk i/o. wa: details the % of time the CPU was idle with pending local disk i/o.
82.How will you set the memory tunable parameters vmo -o parameter=value
61 ********************************************************************************
83.What is sar command o/p: AIX aix6 3 5 0001835F4C00 System configuration: lcpu=1 00:01:45 00:01:47 00:01:49 00:01:51 Average %usr 16 23 19 19 %sys %wio %idle 69 66 66 67 15 11 14 14 0 0 0 0 09/28/10
sar command is used to monitor CPU utilization by various processes, it shows CPU utilization in kernel mode and user mode and waiting for i/o .by looking at these values i can come to know the total CPU utilization and if it is > 80% for single processor the system is in CPU bound. 84.How will you monitor the performance of the system. Performance of the system may degraded due to CPU bound Memory bound Disk i/o bound Network bound so I will check the CPU bound using sar command, it shows CPU utilization for kernel processes, user processes, idle and CPU utilization for i/o waiting. So by looking at these values I can conclude the busy % of CPU . and I will check memory bound using vmstat command, this command describes virtual memory characteristics. Such as pageins, pageouts, run queue value and blocked queue value, number of context switches.. by looking at these values I can conclude whether memory bound there or not.
62 ********************************************************************************
For any disk i/o performance issues, I check iostat command to see which disk is operating with more i/o requests. And for network issues using netstat -i I can come to know how much the network traffic is and is there any collisions occurred .
85.What is performance monitoring The performance of a computer system is based on human expectations and the ability of the computer system to fulfill these expectations. Monitoring the performance of the system dictates that the system is fulfilling the human expectations or not. The objective for performance tuning is to make those expectations and their fulfillment match 86.What is defunct process Defunct process is the process that has completed execution, but still has an entry in the process table. 87.How will you alter the priority of the running process By using renice command Syntax: #renice n <nicevalue> PID Note: if you dont have root authority then you can not higher the priority of the process, but you can lower the priority of processes that you own. 88.Have you ever used crontab in your office. Yes, to take the statistical information about the machine for repetitive times using nmon tool, I have submitted nmon command as cron job to run for every 10 min for one day. So that I got the nmon file and I brought it to the windows machine to analyze it using nmon analyzer. 89.What are the LVM policies LVM supports physical volume allocation policies to better organize logical volumes for increased I/O performance
63 ********************************************************************************
Intra policy: The intra-physical volume allocation policy describes the location of the logical volume (LV) on the disk regions. . Inter policy: This policy will determine whether an LV can be extended across multiple physical volumes (PV), or disks.
90. what type of software RAIDs are supported on AIX and explain what each one them do. Aix supports the RAID0, RAID1 ,and RAID10 So RAID0 =stripping(it is the way of providing high performances in large sequentially access file systems.it means , in the data writing phase each data are chopped into small pieces called strip and these chunks are written to the different drives in parallel and in the data reading phase each datas are read from the different drives and re-assemble to the actual data. RAID1=it is the way of having two or three copies of data for high availability requirements.The basic concept of this is just keep the data in the different drives to prevent the possibility of the data loss in the case of the drives block failure. RAID0+1 (10)=it gives both performance as well as availability but it is expensive
91.How will you k now what is the machine TL level and service pack and when it is released. By using # oslevel -r out put format: VR00-TL-SP-YYWW ex:6100-02-01-0847 VR base version of the operating system TLtechnology level SPservice pack
64 ********************************************************************************
YY year of release WW week of release 92.user can not use crontab what could be the cause? if cron.deny and cron.allow both does not exist. cron.allow. exists and it is not empty but username entry not there username entry been listed in cron.deny file. 93. unable to mount the file system what could be the cause. 1.log device is not available 2.mount point is removed. 3. file system entry removed from /etc/filesystems 4. 94. differentiate smit and smitty smit is the graphical interactive mode. smitty is the character based interactive mode. 95. Tell me the daemons to be running at client side and server side in-order to use NFS services. Server side: Client side: rpc.statd rpc.statd rpc.lockd rpc.lockd rpc.mountd biod nfsd 96. how will you confirm whether the server is up and running for NFS operations. # rpcinfo -p ServerHostName 97. how will you control SRC daemons of remote host. # startsrc g ResourceGroup -h RemoteHostname Note: to do this operation, remote host should be running with srcmstr deamon with r flag. 98. can you make root user as trusted user to provide password less authentication using rlogin? Yes, by adding entry to the /.rhosts file. Note: if a remote command request is made by the root user the /etc/hosts.equiv file is ignored and only the /.rhosts file is read. 99. tell me the reasons why you need to boot the box in maintenance mode?
65 ********************************************************************************
1.for root password recovery 2.to run fsck on rootvg file systems. 3.to recover corrupted ODM 4.to re-create boot image, in case of boot failure. 5.super block recovery for rootvg file systems. 100. nfsd and rpc.mountd daemons not started what could be the problem? Make sure that you have /etc/exports file. If the /etc/exports file does not exist, the nfsd and the rpc.mountd daemons will not start. This will allow the nfsd and the rpc.mountd daemons to start, although no filesystems will be exported. ----------------------------SMITTY FASTPATHS:
---------------------------------smitty smitty smitty smitty smitty smitty smitty smitty smitty smit smitty mknfsexp chnfsexp lsmksysb restmksysb mksysb update_all remove mktcpip nim nim_alt_mksysb nim_alt_clone
-----------------COMMON LED CODES: ----------------0c0 - Dump completed successfully 0c2 - Dump started 0c4 - Dump unsuccesful. Not enough space on dump device 0c5 - Dump failed to start 0c9 - System initiated dump started 201 - Damaged boot image 223-229 Invalid bootlist 551,555,557 corrupted file system, corrupted JFS log.
66 ********************************************************************************
552,554,556 super block corrupted and corrupted customized ODM database. 553 corrupted /etc/inittab file. ############## # USEFUL LINKS ############## http://www.rootvg.net http://publib.boulder.ibm.com/cgi-bin/ds_form http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base/errorsearch.hm http://www.aixtips.com/AIXtip/ http://www.rootunix.org/AIX/ http://www.rootvg.net/ledlist.htm http://www.ibm.com/developerworks/aix/ http://www.ibm.com/developerworks/forums/forum.jspa?forumID=747 http://www.perzl.org/aix/
-----------------------------------------------ALL THE BEST-------------------------------------------
67 ********************************************************************************
68 ********************************************************************************

Aix Help

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Aix Help

Hochgeladen von

Copyright:

Verfügbare Formate

Raja Sekhar Reddy Polu ********************************************************************************

AIX quick reference

MOUNT POINT N/A

TYPE jfs2 jfs2log

MOUNT POINT /lp N/A

Raja Sekhar Reddy Polu ********************************************************************************

FREE DISTRIBUTION 183..16..190..190..190 190..185..190..190..190

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Size %Used Active Auto Type

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

True True True True True True True True

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

PID 9288 9546 5572 7528

Status active active active active

Raja Sekhar Reddy Polu ********************************************************************************

Ipkts Ierrs Opkts Oerrs Coll 8107 0 4143 0 0 8107 0 4143 0 0

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Specifies the second of the minute (00 through 59).

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

FileSystems differences: ------------------------

Raja Sekhar Reddy Polu ********************************************************************************

JFS 1 TB 64 GB 16MB 128 bytes 512 bytes 4096 bytes Yes On No No

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

EXPLAIN BOOT PHASES PHASE I

rc.boot script is passwd to the parameter 2 PHASE II

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

New&Complete over write Yes Yes Yes No Yes Yes No

Preservation No Yes No No Yes Yes No

Migration No No No Yes Yes Yes Yes

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

Raja Sekhar Reddy Polu ********************************************************************************

ii. pre-define mount crfs -v nfs -d /RemoteMount