CREATING AND EXTENDING A FILE SYSTEM IN HACMP
CREATING A FILE SYSTEM IN HACMP
/usr/sbin/cluster/sbin/cl_crfs -cspoc “-ncws,pci” -v jfs2 -gconvg -a size=32786 -m/test-export -prw -a size=4096
In the above command –n for nodes here pci and cws are nodes
-v for type of file system –g for vgname
-m for mount point
-p for permissions
-a size is size in blocks
EXTENDING A FILE SYSTEM IN HACMP
# /usr/es/sbin/cluster/sbin/cl_chfs -cspoc "-g testrg" -a size=+32768 /shfs
cws: File System size changed to 65536
#
In the above command –g for resource group
-a size is the size in block
CHECKING THE FILE SYSTEM
# df -k /shfs
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/lv1 32768 31408 5% 4 1% /shfs
#
#
MOVE THE RG TO OTHER NODE AND VERIFY FILE SYSTEM
# /usr/es/sbin/cluster/utilities/clRGmove -g testrg -n pci -m
Attempting to move group testrg to node pci.
Waiting for cluster to process the resource group movement request....
Waiting for the cluster to stabilize............
Resource group movement successful.
Resource group testrg is online on node pci.
REDUCING VG IN HACMP
# ./cl_reducevg -cspoc "-g testrg" -R pci sh1vg hdisk4
Posted by Shivakant Tiwari at 4:34 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: creating a file system in hacmp, extending a file system in hacmp, HACMP ADMINISTRATION AND CONFIGURATIONS, reducing a vg in hacmp
SATURDAY, JUNE 4, 2011
EXTENDING A SHARED VG IN HACMP / ADDING A DISK IN SHARED VG IN HACMP
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
TO EXTEND A SHARED VOLUME IN HACMP
PCI
# lspv
hdisk2 000ac1331e511d20 con1vg
hdisk3 000ac1331e513fe5 None
hdisk4 000ac1331e51658a None
hdisk0 000ac13395197f5e rootvg
hdisk5 000ac13382115287 None
CWS
# lspv
hdisk0 00fad1d465b1b385 rootvg
hdisk1 00fad1d4b98a1756 None
hdisk2 00fad1d4b98a1a3e None
hdisk3 000ac1331e511d20 con1vg
hdisk4 00fad1d4b98a23b2 None
hdisk5 000ac133b98a2e01 None
GO TO C-SPOC >> HACMP Logical Volume Management
System Management (C-SPOC)
Move cursor to desired item and press Enter.
Manage HACMP Services
HACMP Communication Interface Management
HACMP Resource Group and Application Management
HACMP Log Viewing and Management
HACMP File Collection Management
HACMP Security and Users Management
HACMP Logical Volume Management
HACMP Concurrent Logical Volume Management
HACMP Physical Volume Management
Configure GPFS
Open a SMIT Session on a Node
GO TO >> Shared Volume Groups
HACMP Logical Volume Management
Move cursor to desired item and press Enter.
Shared Volume Groups
Shared Logical Volumes
Shared File Systems
Synchronize Shared LVM Mirrors
Synchronize a Shared Volume Group Definition
GO TO >> Set Characteristics of a Shared Volume Group
Shared Volume Groups
Move cursor to desired item and press Enter.
List All Shared Volume Groups
Create a Shared Volume Group
Create a Shared Volume Group with Data Path Devices
Set Characteristics of a Shared Volume Group
Import a Shared Volume Group
Mirror a Shared Volume Group
Unmirror a Shared Volume Group
GO TO >> Add a Volume to a Shared Volume Group
Set Characteristics of a Shared Volume Group
Move cursor to desired item and press Enter.
Add a Volume to a Shared Volume Group
Remove a Volume from a Shared Volume Group
Enable/Disable a Shared Volume Group for Cross-Site LVM Mirroring Verification
SELECT THE VOLUME GROUP NEEDED TO EXTEND
Add a Volume to a Shared Volume Group
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
Resource Group Name RG1
VOLUME GROUP name testshare
Reference node pci
VOLUME names hdisk4
NOW SELECT >> Synchronize a Shared Volume Group Definition
HACMP Logical Volume Management
Move cursor to desired item and press Enter.
Shared Volume Groups
Shared Logical Volumes
Shared File Systems
Synchronize Shared LVM Mirrors
Synchronize a Shared Volume Group Definition
SELECT THE VOLUME GROUP TO SHARE
Synchronize a Shared Volume Group Definition
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
SHARED VOLUME GROUP name []
+--------------------------------------------------------------------------+
| SHARED VOLUME GROUP name |
| |
| Move cursor to desired item and press Enter. |
| |
| cws: con1vg |
| cws: testshare |
| |
| Esc+1=Help Esc+2=Refresh Esc+3=Cancel |
Esc+1=Help | Esc+8=Image Esc+0=Exit
Enter=Do | Esc+4=List
Esc+5=Reset | /=Find n=Find Next | Esc+8=Image Esc+9=Shell +--------------------------------------------------------------------------+
IF IT GIVES PROBLEM - SYNCHRONISE IT WITH THE COMMAND BELOW
# cl_updatevg -cspoc "-g RG1" testshare
NOW TRY TO IMPORT AND EXPORT THE VG MANYALLY ON BOTH NODES
ON CWS
# lsvg -o
rootvg
# lsvg
rootvg
testshare
con1vg
# lspv
hdisk0 00fad1d465b1b385 rootvg
hdisk1 00fad1d4b98a1756 None
hdisk2 00fad1d4b98a1a3e None
hdisk3 000ac1331e511d20 con1vg
hdisk4 00fad1d4b98a23b2 testshare
hdisk5 000ac133b98a2e01 testshare
# exportvg testshare
# importvg -y testshare hdisk4
synclvodm: No logical volumes in volume group testshare.
testshare
# lsvg
rootvg
testshare
con1vg
#
# varyoffvg testshare
# lsvg
rootvg
testshare
con1vg
#
ON PCI
# hostname
pci
# lsvg
rootvg
testshare
con1vg
# lspv
hdisk2 000ac1331e511d20 con1vg
hdisk3 00fad1d4b98a23b2 testshare
hdisk4 000ac133b98a2e01 testshare
hdisk0 000ac13395197f5e rootvg
hdisk5 000ac133b98a3360 None
# exportvg testshare
# importvg -y testshare hdisk3
synclvodm: No logical volumes in volume group testshare.
testshare
# lspv
hdisk2 000ac1331e511d20 con1vg
hdisk3 00fad1d4b98a23b2 testshare
hdisk4 000ac133b98a2e01 testshare
hdisk0 000ac13395197f5e rootvg
hdisk5 000ac133b98a3360 None
# lsvg
rootvg
testshare
con1vg
#
NOW STOP CLUSTER SERVICE
Stop Cluster Services
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Stop now, on system restart or both now
Stop Cluster Services on these nodes [cws,pci]
BROADCAST cluster shutdown? true
* Shutdown mode graceful
+--------------------------------------------------------------------------+
| ARE YOU SURE? |
| |
| Continuing may delete information you may want |
| to keep. This is your last chance to stop |
| before continuing. |
| Press Enter to continue. |
| Press Cancel to return to the application. |
| |
Esc+1=Help Es| Esc+1=Help Esc+2=Refresh Esc+3=Cancel | Esc+4=List
Esc+5=Reset Es| Esc+8=Image Esc+0=Exit Enter=Do | Esc+8=Image
VERIFY AND SYNCHORONISE THE CLUSTER
Extended Configuration
Move cursor to desired item and press Enter.
Discover HACMP-related Information from Configured Nodes
Extended Topology Configuration
Extended Resource Configuration
Extended Event Configuration
Extended Performance Tuning Parameters Configuration
Security and Users Configuration
Snapshot Configuration
Export Definition File for Online Planning Worksheets
Extended Verification and Synchronization
HACMP Cluster Test Tool
RESTART THE CLUSTER
MOVE THE RESOURCE GROUP AND TEST VG
/usr/es/sbin/cluster/sbin/cl_chvg -cspoc "-g RG1 " -a n testshare
Posted by Shivakant Tiwari at 2:25 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: ADDING A DISK IN SHARED VOLUME IN HACMP, EXTENDING A SHARED VOLUME, HACMP ADMINISTRATION AND CONFIGURATIONS, HACMP VG EXTEND
THURSDAY, MAY 26, 2011
HACMP LOGS - HACMP.OUT
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
HACMP.OUT
This file contains the output of all the events in a cluster the events are located in directory /usr/es/sbin/cluster/events
This file also gives complete command line to perform the task and the output of that task
To start troubleshooting hacmp find messages like EVENT FAILED IN THE hacmp.out file
# cat hacmp.out |grep "EVENT FAILED"
May 6 08:45:47 EVENT FAILED: 1: get_disk_vg_fs ALL Testnode1vg 1
Now We know that there is a failed event on May 6 and the event is get_disk_vg_fs
The error shows that the get_disk_vg_fs failed as it could not mount a file system "cl_activate_fs /sapmnt/X10" which is showed in the log below
cirg:cl_activate_fs[85] mount /sapmnt/X10
mount: /dev/X10sapmntlv on /sapmnt/X10: Missing file or filesystem
cirg:cl_activate_fs[87] [[ fsck == logredo ]]
cirg:cl_activate_fs[107] cl_RMupdate resource_error /sapmnt/X10 cl_activate_fs
Reference string: Fri.May.6.08:45:47.IST.2011.cl_activate_fs..sapmnt.X10.cirg.ref
cirg:cl_activate_fs[108] cl_echo 10 'cl_activate_fs: Failed mount of /sapmnt/X10.' cl_activate_fs /sapmnt/X10
cirg:cl_echo[49] version=1.13
cirg:cl_echo[98] HACMP_OUT_FILE=/tmp/hacmp.out
May 6 2011 08:45:47 cl_activate_fs: Failed mount of /sapmnt/X10.cirg:cl_activate_fs[109] STATUS=1
Posted by Shivakant Tiwari at 3:55 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HACMP ADMINISTRATION AND CONFIGURATIONS, HACMP LOGS, HACMP.OUT, understanding hacmp.out
HACMP LOGS CLSTRMGR.DEBUG
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
CLSTRMGR.DEBUG
This file containes time stamed output generated by the clstrmgrES daemon
This file is very much helpul in finding cause of errors
FOR EXAMPLE THE BELOW EXAMPLE SHOWS HOW CLUSTER MANAGER SEARCHES FOR NODES IN CLUSTER
Mon Dec 13 10:58:56 ResGroupList::initialize() Constructing new list with 2 groups
Mon Dec 13 10:58:56 NodeList::NodeList constructor called.Mon Dec 13 10:58:56 NodeList::NodeList: Found node name Testnode2.
Mon Dec 13 10:58:56 NodeList::NodeList: Found node name Testnode1.
Mon Dec 13 10:58:56 NodeList::DumpNodeList called.Mon Dec 13 10:58:56 NodeList::DumpNodeList: There are 2 nodes in this list.
Mon Dec 13 10:58:56 NodeList::DumpNodeList: Their names, states and ids are:
Mon Dec 13 10:58:56 Testnode2, 4, 2
Mon Dec 13 10:58:56 Testnode1, 4, 1
Mon Dec 13 10:58:56 NodeList::DumpNodeList: The nodes are not ordered.
Mon Dec 13 10:58:56 Creating Resource Group : dbrg (2)
Mon Dec 13 10:58:56 NodeList::NodeList constructor called.Mon Dec 13 10:58:56 NodeList::NodeList: Found node name Testnode1.
Mon Dec 13 10:58:56 NodeList::NodeList: Found node name Testnode2.
Mon Dec 13 10:58:56 NodeList::DumpNodeList called.Mon Dec 13 10:58:56 NodeList::DumpNodeList: There are 2 nodes in this list.
Mon Dec 13 10:58:56 NodeList::DumpNodeList: Their names, states and ids are:
Mon Dec 13 10:58:56 Testnode1, 4, 1
Mon Dec 13 10:58:56 Testnode2, 4, 2
Mon Dec 13 10:58:56 NodeList::DumpNodeList: The nodes are not ordered.
Mon Dec 13 10:58:56 Creating Resource Group : cirg (1)
Mon Dec 13 10:58:56 RGTemporalDep::initialize(): CALLED, 1
Mon Dec 13 10:58:56 GetObjects: Called with criteria:
EXAMPLE OF HEARTBEAT INFORMATION IN THE LOG
Mon Dec 13 10:59:49 interface Testnode2_hdisk22_01 on network net_diskhb_01 is up on node Testnode2
Mon Dec 13 10:59:49 Network::setGlobalState: network net_diskhb_01(0) is already 2, return
Mon Dec 13 10:59:49 interface Testnode2_hdisk22_01 on network net_diskhb_01 is up on node Testnode2
Mon Dec 13 10:59:49 Network::setState: network net_diskhb_01(0) is already 2, return
Mon Dec 13 10:59:49 interface Testnode2_boot on network net_ether_01 is up on node Testnode2
Mon Dec 13 10:59:49 Network::setGlobalState: network net_ether_01(1) is already 2, return
Mon Dec 13 10:59:49 interface Testnode2_boot on network net_ether_01 is up on node Testnode2
Mon Dec 13 10:59:49 Network::setState: network net_ether_01(1) is already 2, return
Mon Dec 13 10:59:49 transition from stable to unstanle - refresh clinfo
Mon Dec 13 10:59:49 MqSend: Setting up MQ_TENODE_INFO_MSG for event TE_UNSTABLE, te_nodeid = 1
Mon Dec 13 10:59:49 FSMrun: next state = ST_UNSTABLE, FSM-event = FSM_NONE
Mon Dec 13 10:59:49 FSMrun: complete(1) 0 secs
NOTE SEE FILE hacmprd_rcovcmd.err FOR ADDITIONAL ERROR
Posted by Shivakant Tiwari at 3:20 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: clstrmgr.debuc, HACMP ADMINISTRATION AND CONFIGURATIONS, HACMP LOGS
HACMP LOG FILES - CLCOMD.LOG
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
CLCOMD.LOG
clcomd contains informatuion related with communication so generally this log is not used for troubleshooting
A SAMPLE OF CLCOMD.LOG
Fri Apr 15 23:58:59 2011: RSH: Command='lsvg -Lo',pid=3543832
Fri Apr 15 23:58:59 2011: RSH:COMPLETED: exit code = 0, pid=3543832
Fri Apr 15 23:58:59 2011: RSH: ACCEPTED: Testnode1: 172.16.1.31->172.16.1.29
Posted by Shivakant Tiwari at 2:32 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: CLCOMD.LOG, HACMP ADMINISTRATION AND CONFIGURATIONS, HACMP LOG FILES, HACMP LOGS
WEDNESDAY, MAY 18, 2011
UNDERSTANDING HACMP LOGS -autoverify.log
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY --- IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
BELOW IS THE OUTPUT OF autoverify.log
This log stores the error and warnings when we are running verification on hacmp nodes ,
while verification is running this log can be viewed to see any error occurred during verification process
main:2: : Function 'main<1> Testnode2'
main:10: is_autover_running
is_autover_running:3: get_local_nodename
is_autover_running:3: LOCALNODENAME=Testnode2
is_autover_running:3: typeset LOCALNODENAME
is_autover_running:4: clnodename
is_autover_running:4: CLUSTER_NODES=$'Testnode1\nTestnode2'
is_autover_running:4: typeset CLUSTER_NODES
is_autover_running:5: ACTIVE_NODES=''
is_autover_running:5: typeset ACTIVE_NODES
is_autover_running:7: [[ Testnode1 != Testnode2 ]]
is_autover_running:8: cl_rsh Testnode1 /usr/es/sbin/cluster/utilities/cl_auto_versync -a
is_autover_running:8: IS_ACTIVE=INACTIVE
is_autover_running:9: [[ INACTIVE == ACTIVE ]]
is_autover_running:7: [[ Testnode2 != Testnode2 ]]
is_autover_running:15: return 1
main:10: ACTIVE_NODES=''
main:17: (( 1 != 1 ))
main:28: unset ACTIVE_NODES
main:32: require_dir /tmp/autoverify/352898/ACD
require_dir:2: : Function 'require_dir<1> /tmp/autoverify/352898/ACD'
require_dir:4: mkdir -p /tmp/autoverify/352898/ACD
main:33: require_dir /tmp/autoverify/352898/DCD
require_dir:2: : Function 'require_dir<1> /tmp/autoverify/352898/DCD'
require_dir:4: mkdir -p /tmp/autoverify/352898/DCD
main:36: clnodename
main:36: CLUSTER_NODES=$'Testnode1\nTestnode2'
main:37: (( 11 ))
main:41: DOWN_NODES=''
main:43: clgetaddr Testnode2
main:43: [[ Testnode2 == Testnode2 ]]
main:45: [[ -n '' ]]
main:51: (( 0 == 0 ))
main:51: errmsg 33
errmsg:2: : Function 'errmsg<1>33'
errmsg:4: (( 1 ))
errmsg:5: target=33
errmsg:5: typeset target
errmsg:6: shift
errmsg:7: dspmsg -s 20 scripts.cat 33 '\nVerifying Cluster Configuration Prior to Starting Cluster Services.\n'
Posted by Shivakant Tiwari at 10:32 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: autoverify.log, HACMP ADMINISTRATION AND CONFIGURATIONS, understanding hacmp logs
UNDERSTANDING HACMP LOGS cl_event_summary
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
cl_event_summary
BELOW IS THE OUTPUT OF cl_event_summary
cl_event_summary contains events pulled out from hacmp.out file , whenever a hacmp.out file completes its cycle event summary is pulled into this file , this file is the best place to start looking for all the events that took place recently , before going to hacmp.out
THIS LOG IS THE FIRST PLACE TO LOOK WHEN STUDYING THE HACMP FOR ANY ERROS OR EVENTS
HACMP Event Summary
Event: /usr/es/sbin/cluster/events/check_for_site_up Testnode2
Start time: Wed May 4 15:57:01 2011
End time: Wed May 4 15:57:01 2011
Action: Resource: Script Name:
----------------------------------------------------------------------------
No resources changed as a result of this event
----------------------------------------------------------------------------
HACMP Event Summary
Event: node_up Testnode2
Start time: Wed May 4 15:57:01 2011
End time: Wed May 4 15:59:01 2011
Action: Resource: Script Name:
----------------------------------------------------------------------------
Acquiring resource group: dbrg process_resources
Search on: Wed.May.4.15:57:03.IST.2011.process_resources.dbrg.ref
Acquiring resource: All_service_addrs acquire_service_addr
Search on: Wed.May.4.15:57:03.IST.2011.acquire_service_addr.All_service_addrs.dbrg.ref
Resource online: All_nonerror_service_addrs acquire_service_addr
Search on: Wed.May.4.15:57:04.IST.2011.acquire_service_addr.All_nonerror_service_addrs.dbrg.ref
Acquiring resource: All_disks cl_disk_available
Search on: Wed.May.4.15:57:04.IST.2011.cl_disk_available.All_disks.dbrg.ref
Resource online: All_nonerror_disks cl_disk_available
Search on: Wed.May.4.15:57:35.IST.2011.cl_disk_available.All_nonerror_disks.dbrg.ref
Acquiring resource: All_volume_groups cl_activate_vgs
Search on: Wed.May.4.15:57:35.IST.2011.cl_activate_vgs.All_volume_groups.dbrg.ref
Resource online: All_nonerror_volume_groups cl_activate_vgs
Search on: Wed.May.4.15:58:34.IST.2011.cl_activate_vgs.All_nonerror_volume_groups.dbrg.ref
Acquiring resource: All_filesystems cl_activate_fs
Search on: Wed.May.4.15:58:44.IST.2011.cl_activate_fs.All_filesystems.dbrg.ref
Resource online: All_non_error_filesystems cl_activate_fs
Search on: Wed.May.4.15:58:45.IST.2011.cl_activate_fs.All_non_error_filesystems.dbrg.ref
----------------------------------------------------------------------------
HACMP Event Summary
Event: node_up_complete Testnode2
Start time: Wed May 4 15:59:01 2011
End time: Wed May 4 15:59:04 2011
Action: Resource: Script Name:
----------------------------------------------------------------------------
Acquiring resource: All_servers start_server
Search on: Wed.May.4.15:59:01.IST.2011.start_server.All_servers.dbrg.ref
Resource online: All_nonerror_servers start_server
Search on: Wed.May.4.15:59:02.IST.2011.start_server.All_nonerror_servers.dbrg.ref
Resource group online: dbrg process_resources
Search on: Wed.May.4.15:59:02.IST.2011.process_resources.dbrg.ref
----------------------------------------------------------------------------
HACMP Event Summary
Event: /usr/es/sbin/cluster/events/check_for_site_up_complete Testnode2
Start time: Wed May 4 15:59:04 2011
End time: Wed May 4 15:59:04 2011
Action: Resource: Script Name:
----------------------------------------------------------------------------
No resources changed as a result of this event
----------------------------------------------------------------------------
Clear event summaries periodically, using the Problem Determination Tools > HACMP Log Viewing and Management > View/Save/Remove HACMP Event Summaries > Remove Event Summary History
Posted by Shivakant Tiwari at 10:24 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: cl_event_summary, HACMP ADMINISTRATION AND CONFIGURATIONS, understanding hacmp logs
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)
TOTAL PAGEVIEWS
10,052
Your Ad Here
FEEDJIT
Your Ad Here
TUESDAY, MAY 10, 2011
COLLECTING VG AND PV INFORMATION
GETTING VG AND PV INFORMATION
THIS SCRIPT COLLECTS VOLUME GROUP AND PHYSICAL VOLUME INFORMATION AND COLLECTS THEM IN A FILE
THIS INFORMATION IS IMOPORTANT AS ONE SCRIPT ON A SERVER WILL PROVIDE ALL THE INFORMATION ABOUT ALL THE VG AND PV UNDER IT
for x in $(lsvg) ;SELECT ALL THE VOLUME GROUPS
do
echo "************************************" >> /tmp/lsvg.out ;PUT A START MARKER
echo VG INFORMATION FOR $x >> /tmp/lsvg.out
lsvg -p $x >> /tmp/lsvg.out ;COLLECT INFO ABOUT DRIVES
lsvg -l $x >> /tmp/lsvg.out ;COLLECT INFO ABOUT LV
lsvg $x >> /tmp/lsvg.out ;COLLECT DETAIL INFO ABOUT VG
echo "************************************" >> /tmp/lsvg.out
done
for x in $(lspv|awk ‘{print $1}’) ;SELECT ALL PHYSICAL VOLUME
do
echo"************************************" >> /tmp/lspv.out
lspv $x >> /tmp/lspv.out ;STORE THE PV INFORMATION
lspv –l $x >> /tmp/lspv.out
echo"************************************" >> /tmp/lspv.out
done
Posted by Shivakant Tiwari at 4:04 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, collecting all the vg and pv info using shell script, COllecting vg and pv info off all the machines using shell script
TO CUT REQUIRED LOG FROM A LARGE LOG FILE
TO CUT REQUIRED LOG FROM A LARGE LOG FILE
In the script “mm” “dd” “yy” is month date and year respectively , this script is useful if a logfile has large content of everyday logs and we have to fetch log of a specific date for a specific host or string
for x in hostname1 hostname2 hostname3 ...
do
cat <logfile name>|awk '/"mm"\/"dd"\/"yy""/,/END/'|awk /"$x"/,/"<string for end"/
done
Posted by Shivakant Tiwari at 3:59 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, customizing log view in aix, shell script to cut a portion of log in aix
TAKING VIO BACKUP TO A REMOTE FILESYSTEM
TAKING VIO BACKUP TO A REMOTE FILESYSTEM
HN=`hostname`
LOGFILE="/home/padmin/bckvio.log"
EMAILADDR=xyz@abc.com
echo "GATHERING VIOS CONFIGURATION" > $LOGFILE
/home/padmin/gathervios.ksh >> $LOGFILE 2>&1
date >> $LOGFILE 2>&1
/usr/ios/cli/ioscli mount <remote machine>:/<remote path> /<local dir> >> $LOGFILE 2>&1
/usr/ios/cli/ioscli backupios -file /<local dir>/${HN}_mksysb -mksysb >> $LOGFILE 2>&1
if [[ $? -ne 0 ]]
then
mail -s "ERROR CREATING VIOS BACKUP" $EMAILADDR <<EOF
vio bachup for $HN has failed ! Please look into log /home/padmin/bckvio.log !
EOF
fi
/usr/ios/cli/ioscli unmount /<local dir> >> $LOGFILE 2>&1
Posted by Shivakant Tiwari at 3:56 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, TAKING VIO BACKUP TO A REMOTE FILESYSTEM, VIO BACKUP USING SCRIPT
COLLECT ALL THE INFORMATION OF A CHILD DEVICE COMING FROM A FC ADAPTER
COLLECT ALL THE INFORMATION OF A CHILD DEVICE COMING FROM A FC ADAPTER
lsdev -l $1
echo "PARENT DEVICE FOR ** $1 ***"
lsdev -l $1 -F parent
a=$(lsdev -l $1 -F parent)
echo "PARENT DEVICE FOR ** $a ** IS"
lsdev -l $(lsdev -l $1 -F parent) -F parent
b=$(lsdev -l $(lsdev -l $1 -F parent) -F parent)
echo "ALL THE CHILD DEVICES CONNECTED TO DEVICE ** $a **"
lsdev -p $(lsdev -l $1 -F parent)
echo "ALL THE CHILD DEVICES CONNECTED TO DEVICE ** $b **"
lsdev -p $(lsdev -l $(lsdev -l $1 -F parent) -F parent)
fc=$(echo $b|grep -e fcs0 -e fcs1 -e fcs2 -e fcs4 -e fcs5)
ck=${#fc}
if [ $ck -eq 0 ]
then
echo "BACKUP ADAPTER IS NOT FC"
exit
else
echo "PLEASE WAIT WHILE COLLECTING FC COMMUNICATION"
for x in $fc
do
c=5
echo "DATA TRANSFER FOR ** $x ** "
while [ $c -gt 0 ]
do
fcstat $x|awk '/Transmit/,/Words/'
sleep 10
c=$(($c-1))
done
done
fi
Posted by Shivakant Tiwari at 3:54 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, collecting fc information . troubleshooting a device coming from a fc
COLLECTING MICROCODE INFORMATION
COLLECTING MICROCODE INFORMATION
###### THIS SCRIPT COLLECTS INFORMATION ###########
############# AND HOST LISTS ARE IN FILE HOST.LST###########
exportfs –i /suptools
for x in $(cat /home/aixadmin/host.lst)
do
echo $x >> /suptools/coldata.out
ssh $x ls -lasd /suptools
if [ $? == 0 ]
then
ssh $x mount -o rw <local_machine>:/suptools /suptools
echo "************************************************8" >> /suptools/coldata.out
ssh $x /suptools/./coldata >> /suptools/coldata.out
ssh $x umount /suptools
echo "************************************************8" >> /suptools/coldata.out
else
ssh $x mkdir /suptools
ssh $x mount -o rw <local_machine>:/suptools /suptools
echo "************************************************8" >> /suptools/coldata.out
ssh $x /suptools/./coldata >> /suptools/coldata.out
ssh $x umount /suptools
echo "************************************************8" >> /suptools/coldata.out
fi
done
CONTENTS OF coldata
hostname >> /suptools/coldata.out
oslevel -s >> /suptools/coldata.out
lsmcode -r >> /suptools/coldata.out
for dv in $(lsdev -Cc adapter|awk '{print $1}'|grep -e ent -e fcs -e sisscsi)
do
echo $dv >> /suptools/coldata.out
lsmcode -r -d $dv >> /suptools/coldata.out
done
#
Posted by Shivakant Tiwari at 3:52 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, SHELL SCRIPT TO COLLECT MICROCODE INFORMATION
CREATING A USER IN AIX
CREATING A USER
#############################################################
############ THIS WILL ASK UID AND USER NAME #################
############AND WILL CREATE USER NAME ON THE SERVERS #############
##### LISTED IN THE FILE "xyz" ########
echo enter user-id followed by user name for eg 30 username
read uid usd
#echo enter password to reset for the user $usd
for x in $(cat xyz)
do
echo creating user $usd on host $x
ssh $x mkuser id=$uid $usd
done
exportfs -i /exportfilesystem
echo enter password to reset for the user $usd
read pas
echo "echo $usd:$pas|chpasswd" > /exportfilesystem/passet.sh
chmod +x /exportfilesystem/passet.sh
for x in $(cat xyz)
do
ssh $x mkdir /exportfilesystem
ssh $x mount current_server:/exportfilesystem /exportfilesystem
ssh $x /exportfilesystem/passet.sh
ssh $x umount /exportfilesystem
done
Posted by Shivakant Tiwari at 3:48 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, creating user in aix on all the servers, script to create user in aix
RESETTING A USER LOCKED PASSWD
RESETTING A USER LOCKED PASSWD
echo enter user name to reset
read usd
echo this will reset user $usd locked password
chsec -f /etc/security/lastlog -a "unsuccessful_login_count=0" -s $usd
chuser "account_locked=false" $usd
echo $usd:test@1234|chpasspw
Posted by Shivakant Tiwari at 3:45 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: .RESETTING A USER LOCKED PASSWD IN AIX, AIX SHELL SCRIPTS
FINDS OUT FILE SYSTEM UTILIZATION
FINDS OUT FILE SYSTEM UTILIZATION
THIS SCRIPT FINDS AND TELLS YOU WHICH FILE SYSTEM ARE UTILIZING SPACE BOVE THAN THRESHOLD SET BY YOU
h=$(hostname)
df -gt |grep -v Filesystem|grep -v proc|while read out
do
fs=$(echo $out|awk '{print $5 }'|cut -f1 -d%)
if [ "$fs" -gt 90 ]; then
echo "***********************************"
echo FILE SYSTEM LARGER THAN 90% ON $h ARE
echo $out
echo "***********************************"
fi
done
Posted by Shivakant Tiwari at 2:24 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, file system utilization alert in aix, how to find out file system utilization, shell script to monitor aix file system utilization
GETTING PORT ADDRESS FOR SERVICES
GETTING PORT ADDRESS FOR SERVICES
THIS SCRIPT CALCULATES AND SHOWS WHICH PORT IS USED BY WHICH SERVICE ,VERY IMPORTANT SCRIPT FOR ALL AIX ADMINISTRATORS
for x in $(netstat -Aan|grep LISTEN|awk '{print $1}')
do
a=$(netstat -Aan|grep LISTEN|grep $x|awk '{print $5}'|cut -f2 -d .)
b=$(rmsock $x tcpcb|awk '{print $9}')
echo PORT $a is used by
ps -ef |grep $b
done
Posted by Shivakant Tiwari at 2:22 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: aix port used by services, AIX SHELL SCRIPTS, how to get port address of services, which service is using which port in aix
FINDING USER’S PASSORD EXPIRE DATE
SCRIPT 1 – FINDING USER’S PASSORD EXPIRE DATE
############################################################################
# THIS SCRIPT WILL ASK A USER NAME AND TELL WHEN ITS PASSWORD WILL EXPIRE
#I HAD NOT MADE IT VERY SMOOTH BUT STILL IT SOLVES A VERY BIG THING
################################################################################
echo enter user name ; PROVIDE THE USER NAME
read uame
lstup=$(pwdadm -q $uame|grep -e lastupdate|cut -f2 -d=)
echo LAST PASSWORD UPDATED FOR USER $uame ON >> /tmp/pwexp.out
echo $lstup| perl -e 'print localtime(<>) . "\n";' >> /tmp/pwexp.out
mxag=$(lsuser -a maxage $uame|cut -f2 -d=)
pwexp=$(expr 604800 \* $mxag)
pwexp=$(($lstup + $pwexp))
echo PASSWORD EXPIRE DATE FOR USER $uame >> /tmp/pwexp.out
echo $pwexp| perl -e 'print localtime(<>) . "\n";' >> /tmp/pwexp.out
cat /tmp/pwexp.out ;THE OUTPUT IS STORED IN pwexp.out FILE
Posted by Shivakant Tiwari at 2:20 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, aix user password expire, finding users FINDING USER’S PASSORD EXPIRE DATE in aix
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)
TOTAL PAGEVIEWS
10,053
Your Ad Here
FEEDJIT
Your Ad Here
MONDAY, MAY 9, 2011
VIEWING INFORMATION OF LPAR FROM HMC - SOME EXAMPLES
TO VIEW ALL THE MANAGED SERVER CONNECTED TO THE HMC
hscroot@localhost:~> lssyscfg -r lpar -m PRIMARY-Servers-
9117-570 -F name
PRIMARY-SERVER
SECONDARY-SERVER
65-095FE
TO VIEW ALL THE LPAR IN A MANAGED SERVER
hscroot@localhost:~> lssyscfg -r lpar -m Server-8204-E8A -F name
SERVER-2
SERVER-1
VIOSERVER
SCRIPT TO FIND MANAGED SERVER TO WHICH MY LPAR BELONGS
For x in $( lssyscfg -r lpar -m PRIMARY-Servers-9117-570 -F name)
Do
Echo $x
lssyscfg -r lpar -m $x -F name
done
TO VIEW ALL THE IO UNITS IN MANAGED SERVER
hscroot@localhost:~> lshwres -r io --rsubtype unit -m Server-8204-E8A -F
U5796.001.0601894
U78A0.001.DNWGYKN
TO VIEW ALL THE IO BUS IN MANAGED SERVER
hscroot@localhost:~> lshwres -r io --rsubtype bus -m Server-8204-E8A -F --header
unit_phys_loc,bus_id,backplane_phys_loc,bus_drc_index,bus_drc_name
U5796.001.0601894,288,U5796.001.0601894-P1,20000120,PHB 288
U5796.001.0601894,289,U5796.001.0601894-P1,20000121,PHB 289
U5796.001.0601894,290,U5796.001.0601894-P1,20000122,PHB 290
U5796.001.0601894,292,U5796.001.0601894-P1,20000124,PHB 292
U5796.001.0601894,293,U5796.001.0601894-P1,20000125,PHB 293
U5796.001.0601894,294,U5796.001.0601894-P1,20000126,PHB 294
U78A0.001.DNWGYKN,512,U78A0.001.DNWGYKN-P1,20000200,PHB 512
U78A0.001.DNWGYKN,513,U78A0.001.DNWGYKN-P1,20000201,PHB 513
U78A0.001.DNWGYKN,514,U78A0.001.DNWGYKN-P1,20000202,PHB 514
U78A0.001.DNWGYKN,515,U78A0.001.DNWGYKN-P1,20000203,PHB 515
U78A0.001.DNWGYKN,516,U78A0.001.DNWGYKN-P1,20000204,PHB 516
U78A0.001.DNWGYKN,517,U78A0.001.DNWGYKN-P1,20000205,PHB 517
U78A0.001.DNWGYKN,518,U78A0.001.DNWGYKN-P1,20000206,PHB 518
U78A0.001.DNWGYKN,519,U78A0.001.DNWGYKN-P1,20000207,PHB 519
TO VIEW ALL THE IO SLOTS IN MANAGED SERVER
hscroot@localhost:~> lshwres -r io --rsubtype slot -m Server-8204-E8A -F unit_phys_loc,bus_id
,phys_loc,drc_index,lpar_name,lpar_id,description,feature_codes,vpd_type,vpd_model --header
unit_phys_loc,bus_id,phys_loc,drc_index,lpar_name,lpar_id,description,feature_codes,vpd_type,vpd_model
U5796.001.0601894,288,C1,21010120,null,none,RAID Controller,none,null,null
U5796.001.0601894,289,C2,21010121,VIOSERVER,2,Ethernet controller,none,null,null
U5796.001.0601894,290,C3,21010122,SERVER-1,3,Ethernet controller,none,null,null
U5796.001.0601894,292,C4,21010124,VIOSERVER,2,SCSI bus controller,none,null,null
U5796.001.0601894,293,C5,21010125,SERVER-2,4,Ethernet controller,none,null,null
U5796.001.0601894,294,C6,21010126,null,none,Empty slot,"0,0,0",null,null
U78A0.001.DNWGYKN,512,T9,21010200,VIOSERVER,2,RAID Controller,none,null,null
U78A0.001.DNWGYKN,513,T3,21010201,null,none,Universal Serial Bus UHC Spec,none,null,null
U78A0.001.DNWGYKN,514,C4,21010202,SERVER-2,4,4 GB Single-Port Fibre Channel PCI-X 2.0 DDR Adapter,"5758,5758,5758",null,null
U78A0.001.DNWGYKN,515,C5,21010203,SERVER-2,4,4 GB Single-Port Fibre Channel PCI-X 2.0 DDR Adapter,"5758,5758,5758",null,null
U78A0.001.DNWGYKN,516,C1,21010204,null,none,Empty slot,"0,0,0",null,null
U78A0.001.DNWGYKN,517,C2,21010205,SERVER-1,3,4 Gigabit PCI Express Single Port Fibre Channel Adapter,"5773,5773,5773",null,null
U78A0.001.DNWGYKN,518,C10,21010206,null,none,Empty slot,"0,0,0",null,null
U78A0.001.DNWGYKN,519,C3,21010207,SERVER-1,3,4 Gigabit PCI Express Single Port Fibre Channel Adapter,"5773,5773,5773",null,null
TO VIEW ALL THE VIRTUAL ETHERNET IN MANAGED SERVER
hscroot@localhost:~> lshwres -r virtualio --rsubtype eth -m Server-8204-E8A--level lpar -F –header
lpar_name,lpar_id,slot_num,state,is_required,is_trunk,trunk_priority,ieee_virtual_eth,port_vlan_id,addl_vlan_ids,mac_addr,connect_status,drc_name,shared_adapter,backing_device,device_name
VIOSERVER,2,12,1,0,1,1,0,1,,BE164625C70C,active,U8204.E8A.06D4552-V2-C12-T1,ent4,ent0,ent2
VIOSERVER,2,13,1,0,1,1,0,2,,BE164625C70D,none,U8204.E8A.06D4552-V2-C13-T1,,,ent3
SERVER-2,4,3,1,0,0,unavailable,0,1,,BE1649F95103,active,U8204.E8A.06D4552-V4-C3-T1,,,ent2
TO VIEW ALL THE VIRTUAL FIBRE CHANNEL IN MANAGED SERVER
hscroot@localhost:~> lshwres -r virtualio --rsubtype fc -m Server-8204-E8A--level lpar -F –header
No results were found.
TO VIEW ALL THE VIRTUAL SCSI IN MANAGED SERVER
hscroot@localhost:~> lshwres -r virtualio --rsubtype scsi -m Server-8204-E8A--level lpar -F –header
lpar_name,lpar_id,slot_num,state,is_required,adapter_type,remote_lpar_id,remote_lpar_name,remote_slot_num,backing_devices,connect_status,backing_device,server_loc_code,active_loc_code,active_lpar_id,active_lpar_name,active_slot_num,remote_backing_device,topology
VIOSERVER,2,11,1,1,server,any,,any,null,active,"clientlv1,hdisk2,hdisk4,cd0",U8204.E8A.06D4552-V2-C11,U8204.E8A.06D4552-V3-C2-T1,3,SERVER-1,2,"hdisk0, hdisk1, hdisk2","///vhost0//clientlv1,///vhost0//hdisk2,///vhost0//hdisk4,///vhost0//cd0"
VIOSERVER,2,14,1,0,server,any,,any,null,active,"clientlv2,hdisk3,hdisk5",U8204.E8A.06D4552-V2-C14,U8204.E8A.06D4552-V4-C2-T1,4,SERVER-2,2,"hdisk0, hdisk1, hdisk2, hdisk20","///vhost1//clientlv2,///vhost1//hdisk3,///vhost1//hdisk5"
SERVER-1,3,2,1,1,client,2,VIOSERVER,11,null,active,"hdisk0, hdisk1, hdisk2",U8204.E8A.06D4552-V2-C11,U8204.E8A.06D4552-V3-C2-T1,2,VIOSERVER,11,"clientlv1,hdisk2,hdisk4,cd0","unavailable/unavailable/unavailable/vhost0//hdisk0,unavailable/unavailable/unavailable/vhost0//hdisk1,unavailable/unavailable/unavailable/vhost0//hdisk2"
SERVER-2,4,2,1,0,client,2,VIOSERVER,14,null,active,"hdisk0, hdisk1, hdisk2, hdisk20",U8204.E8A.06D4552-V2-C14,U8204.E8A.06D4552-V4-C2-T1,2,VIOSERVER,14,"clientlv2,hdisk3,hdisk5","unavailable/unavailable/unavailable/vhost1//hdisk0,unavailable/unavailable/unavailable/vhost1//hdisk1,unavailable/unavailable/unavailable/vhost1//hdisk2,unavailable/unavailable/unavailable/vhost1//hdisk20"
TO VIEW ALL THE VIRTUAL SCSI IN MANAGED SERVER (FILTERED VIEW)
hscroot@localhost:~> lshwres -r virtualio --rsubtype scsi -m Server-8204-E8A--level lpar –F lpar_name,lpar_id, lpar_name,lpar_id,slot_num,state,is_required,adapter_type,remote_lpar_id,remote_lpar_name,remote_slot_num,backing_devices,connect_status,backing_device,active_lpar_id,active_lpar_name -–header
lpar_name,lpar_id,slot_num,state,is_required,adapter_type,remote_lpar_id,remote_lpar_name,remote_slot_num,backing_devices,connect_status,backing_device,active_lpar_id,active_lpar_name
VIOSERVER,2,11,1,1,server,any,,any,"""0x8100000000000000,0x8200000000000000,0x8300000000000000,0x8400000000000000/,U78A0.001.DNWGYKN-P2-D3,U78A0.001.DNWGYKN-P2-D8,U78A0.001.DNWGYKN-P2-D2/clientlv1,hdisk2,hdisk4,cd0""",active,"clientlv1,hdisk2,hdisk4,cd0",3,SERVER-1
VIOSERVER,2,14,1,0,server,any,,any,"""0x8100000000000000,0x8300000000000000,0x8200000000000000/,U78A0.001.DNWGYKN-P2-D6,U78A0.001.DNWGYKN-P2-D7/clientlv2,hdisk3,hdisk5""",active,"clientlv2,hdisk3,hdisk5",4,SERVER-2
SERVER-1,3,2,1,1,client,2,VIOSERVER,11,null,active,"hdisk0, hdisk1, hdisk2",2,VIOSERVER
SERVER-2,4,2,1,0,client,2,VIOSERVER,14,null,active,"hdisk0, hdisk1, hdisk2, hdisk20",2,VIOSERVER
TO VIEW ALL THE MEMORY INFORMATION OF A MANAGED SERVER
hscroot@localhost:~> lshwres -r mem -m Server-8204-E8A--level sys -F --header
configurable_sys_mem,curr_avail_sys_mem,pend_avail_sys_mem,installed_sys_mem,max_capacity_sys_mem,deconfig_sys_mem,sys_firmware_mem,mem_region_size,configurable_num_sys_huge_pages,curr_avail_num_sys_huge_pages,pend_avail_num_sys_huge_pages,max_num_sys_huge_pages,requested_num_sys_huge_pages,huge_page_size,total_sys_bsr_arrays,bsr_array_size,curr_avail_sys_bsr_arrays,max_mem_pools
65536,2816,2816,65536,deprecated,0,3328,256,0,0,0,3,0,16384,16,8,16,0
TO VIEW ALL THE MEMORY INFORMATION OF A MANAGED SERVER AT LPAR LEVEL(FILTERED VIEW)
hscroot@localhost:~> lshwres -r mem -m Server-8204-E8A--level lpar -F --header
lpar_name,lpar_id,curr_min_mem,curr_mem,curr_max_mem,pend_min_mem,pend_mem,pend_max_mem,run_min_mem,run_mem,curr_min_num_huge_pages,curr_num_huge_pages,curr_max_num_huge_pages,pend_min_num_huge_pages,pend_num_huge_pages,pend_max_num_huge_pages,run_num_huge_pages,curr_bsr_arrays
SERVER-2,4,2048,28672,45056,2048,28672,45056,2048,28672,0,0,0,0,0,0,0,0
SERVER-1,3,4096,28672,45056,4096,28672,45056,4096,28672,0,0,0,0,0,0,0,0
VIOSERVER,2,1024,2048,4096,1024,2048,4096,1024,2048,0,0,0,0,0,0,0,0
TO VIEW ALL THE PROCESSOR INFORMATION OF A MANAGED SERVER
hscroot@localhost:~> lshwres -r proc -m Server-8204-E8A--level sys -F --header
configurable_sys_proc_units,curr_avail_sys_proc_units,pend_avail_sys_proc_units,installed_sys_proc_units,max_capacity_sys_proc_units,deconfig_sys_proc_units,min_proc_units_per_virtual_proc,max_virtual_procs_per_lpar,max_procs_per_lpar,max_shared_proc_pools
8.0,0.0,0.0,8.0,deprecated,0,0.1,64,64,64
TO VIEW ALL THE MEMORY INFORMATION OF A MANAGED SERVER AT LPAR LEVEL (FILTERED VIEW)
hscroot@localhost:~> lshwres -r mem -m Server-8204-E8A--level lpar –F lpar_name,lpar_id,curr_min_mem,curr_mem
,curr_max_mem,run_mem --header
lpar_name,lpar_id,curr_min_mem,curr_mem,curr_max_mem,run_mem
SERVER-2,4,2048,28672,45056,28672
SERVER-1,3,4096,28672,45056,28672
VIOSERVER,2,1024,2048,4096,2048
TO VIEW ALL THE PROCESSOR INFORMATION OF A MANAGED SERVER AT LPAR LEVEL
hscroot@localhost:~> lshwres -r proc -m Server-8204-E8A--level lpar -F --header
lpar_name,lpar_id,curr_shared_proc_pool_id,curr_shared_proc_pool_name,curr_proc_mode,curr_min_proc_units,curr_proc_units,curr_max_proc_units,curr_min_procs,curr_procs,curr_max_procs,curr_sharing_mode,curr_uncap_weight,pend_shared_proc_pool_id,pend_shared_proc_pool_name,pend_proc_mode,pend_min_proc_units,pend_proc_units,pend_max_proc_units,pend_min_procs,pend_procs,pend_max_procs,pend_sharing_mode,pend_uncap_weight,run_proc_units,run_procs,run_uncap_weight
SERVER-2,4,0,DefaultPool,shared,2.0,4.0,6.0,2,4,6,uncap,
128,0,DefaultPool,shared,2.0,4.0,6.0,2,4,6,uncap,128,4.0,4,128
SERVER-1,3,0,DefaultPool,shared,1.0,3.8,6.0,1,4,6,uncap,
128,0,DefaultPool,shared,1.0,3.8,6.0,1,4,6,uncap,128,3.8,4,128
VIOSERVER,2,0,DefaultPool,shared,0.1,0.2,0.4,1,1,1,cap,0,0,DefaultPool,shared,0.1,0.2,0.4,1,1,1,cap,0,0.2,1,0
TO VIEW ALL THE PROCESSOR INFORMATION OF A MANAGED SERVER AT LPAR LEVEL(FILTERED VIEW)
hscroot@localhost:~> lshwres -r proc -m Server-8204-E8A--level lpar -F lpar_name,lpar_id,curr_proc_mode,
curr_min_proc_units,curr_proc_units,curr_max_proc_units,curr_min_procs,curr_procs,curr_max_procs,curr_sharing_mode,curr_uncap_weight,run_proc_units,run_procs,run_uncap_weight –header
lpar_name,lpar_id,curr_proc_mode,curr_min_proc_units,curr_proc_units,curr_max_proc_units,curr_min_procs,curr_procs,curr_max_procs,curr_sharing_mode,curr_uncap_weight,run_proc_units,run_procs,run_uncap_weight
SERVER-2,4,shared,2.0,4.0,6.0,2,4,6,uncap,128,4.0,4,128
SERVER-1,3,shared,1.0,3.8,6.0,1,4,6,uncap,128,3.8,4,128
VIOSERVER,2,shared,0.1,0.2,0.4,1,1,1,cap,0,0.2,1,0
Posted by Shivakant Tiwari at 5:34 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX VIRTUALIZATION, lshwres -r virtualio, lssyscfg, min desired maximum value throug command line, min maximum memory through command line, rsubtype unit
MONDAY, APRIL 18, 2011
TO MOVE A RESOURCE FROM ONE LPAR TO ANOTHER LPAR
Select lpar on which you have to to do DLPAR operation
select tasks or (the arrow besides the lpar)
Select dynamic logical partitioning > resource to move(for example here processor) select move
In the coming window select destination partition (the partition to which we want to move resources)
Select the amount of resource to move
PUT THE AMOUNT OF RESOURCES TO BE MOVED AND SELECT THE DESTINATION PARTITION
TO MOVE MEMORY RESOURCES
select tasks or (the arrow besides the lpar)
Select dynamic logical partitioning > resource to move(for example here memory ) select move
As in the screen above
Now you will be presented the screen below
Write the amount of memory resource to move
Select Destination Lpar and click on ok
TO MOVE I/O RESOURCES
Select the adapter (there are no removable adapter in the screen shot below )
By clicking ok after selecting the adapter you will remove the adapter from the lpar selected
select destination lpar from the option to move the adapter to the destination LPAR
select tasks or (the arrow besides the lpar)
Select dynamic logical partitioning > resource to move(for example here adapter ) select move
As in the screen above
Posted by Shivakant Tiwari at 3:16 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX VIRTUALIZATION, DLPAR RESOURCES, TO MOVE A RESOURCE FROM ONE LPAR TO ANOTHER LPAR, TO MOVE I/O RESOURCES, TO MOVE MEMORY RESOURCES
MONDAY, MARCH 28, 2011
INSTALLING VIO SERVER
IBM VIRTUAL I/O SERVER
The Virtual I/O Server is part of the eServer p5 Advanced Power Virtualization hardware
feature. Virtual I/O Server allows sharing of physical resources between LPARs including virtual
SCSI and virtual networking. This allows more efficient utilization of physical resources through
sharing between LPARs and facilitates server consolidation.
INSTALLATION
You have two options to install the AIX-based VIO Server:
1. Install from CD
2. Install from network via an AIX NIM-Server
Installation method #1 is probably the more frequently used method in a pure Linux
environment as installation method #2 requires the presence of an AIX NIM (Network
Installation Management) server. Both methods differ only in the initial boot step and are then
the same. They both lead to the following installation screen:
Elapsed time since release of system processors: 51910 mins 20 secs
-------------------------------------------------------------------------------
Welcome to the Virtual I/O Server.
boot image timestamp: 10:22 03/23
The current time and date: 17:23:47 08/10/2005
number of processors: 1 size of memory: 2048MB
boot device: /pci@800000020000002/pci@2,3/ide@1/disk@0:\ppc\chrp\bootfile.exe
SPLPAR info: entitled_capacity: 50 platcpus_active: 2
This system is SMT enabled: smt_status: 00000007; smt_threads: 2
kernel size: 10481246; 32 bit kernel
-------------------------------------------------------------------------------
The next step then is to define the system console. After some time you should see the
following screen:
******* Please define the System Console. *******
Type a 1 and press Enter to use this terminal as the
system console.
Pour definir ce terminal comme console systeme, appuyez
sur 1 puis sur Entree.
Taste 1 und anschliessend die Eingabetaste drücken, um
diese Datenstation als Systemkonsole zu verwenden.
Premere il tasto 1 ed Invio per usare questo terminal
come console.
88 Help ?
This is the main installation menu of the AIX-based VIO-Server:
Welcome to Base Operating System
Installation and Maintenance
Type the number of your choice and press Enter. Choice is indicated by >>>.
>>> 1 Start Install Now with Default Settings
2 Change/Show Installation Settings and Install
3 Start Maintenance Mode for System Recovery
88 Help ?
99 Previous Menu
>>> Choice [1]:
System Backup Installation and Settings
Either type 0 and press Enter to install with the current settings, or type the
number of the setting you want to change and press Enter.
Setting: Current Choice(s):
1 Disk(s) where you want to install ...... hdisk0
Use Maps............................. No
2 Shrink File Systems..................... No
3 Import User Volume Groups............... No
4 Recover Devices......................... No
>>> 0 Install with the settings listed above.
+-----------------------------------------------------
88 Help ? | WARNING: Base Operating System Installation will
99 Previous Menu | destroy or impair recovery of ALL data on the
| destination disk hdisk0.
>>> Choice [0]:
Selection of disks:
Change Disk(s) Where You Want to Install
Type one or more numbers for the disk(s) to be used for installation and press
Enter. To cancel a choice, type the corresponding number and Press Enter.
At least one bootable disk must be selected. The current choice is indicated
by >>>.
Name Location Code Size(MB) VG Status Bootable Maps
>>> 1 hdisk0 03-08-00-3,0 70006 none Yes No
2 hdisk1 03-08-00-4,0 70006 none Yes No
3 hdisk2 03-08-00-5,0 70006 none Yes No
4 hdisk3 03-08-00-8,0 70006 none Yes No
>>> 0 Continue with choices indicated above
55 More Disk Options
66 Devices not known to Base Operating System Installation
77 Display More Disk Information
88 Help ?
99 Previous Menu
>>> Choice [0]:
Now start the installation.
Installing Base Operating System
Please wait...
Approximate Elapsed time
% tasks complete (in minutes)
8 0 1% of mksysb data restored.
-------------------------------------------------------------------------------
Welcome to the Virtual I/O Server.
boot image timestamp: 17:44 08/10
The current time and date: 17:46:01 08/10/2005
number of processors: 1 size of memory: 2048MB
boot device: /pci@800000020000002/pci@2,4/pci1069,b166@1/scsi@0/sd@3:2
SPLPAR info: entitled_capacity: 50 platcpus_active: 2
This system is SMT enabled: smt_status: 00000007; smt_threads: 2
kernel size: 12405120; 64 bit kernel
-------------------------------------------------------------------------------
Saving Base Customize Data to boot disk
Starting the sync daemon
Starting the error daemon
System initialization completed.
Setting tunable parameters...complete
Starting Multi-user Initialization
Performing auto-varyon of Volume Groups
Activating all paging spaces
0517-075 swapon: Paging device /dev/hd6 is already active.
swapon: Paging device /dev/paging00 activated.
The current volume is: /dev/hd1
Primary superblock is valid.
The current volume is: /dev/hd10opt
Primary superblock is valid.
Performing all automatic mounts
Multi-user initialization completed
System reconfiguration in progress. Please wait.
Rebuild of Scriptinfo file is complete
Checking for srcmstr active...complete
Starting tcpip daemons:
0513-059 The syslogd Subsystem has been started. Subsystem PID is 217224.
Aug 10 12:46:40 localhost syslog:err|error syslogd: /tmp/syslog.out: errno = 2
0513-059 The sendmail Subsystem has been started. Subsystem PID is 180374.
0513-059 The portmap Subsystem has been started. Subsystem PID is 69844.
0513-059 The inetd Subsystem has been started. Subsystem PID is 118936.
0513-059 The snmpd Subsystem has been started. Subsystem PID is 184462.
0513-059 The hostmibd Subsystem has been started. Subsystem PID is 131306.
0513-059 The snmpmibd Subsystem has been started. Subsystem PID is 172216.
0513-059 The aixmibd Subsystem has been started. Subsystem PID is 204952.
0513-059 The muxatmd Subsystem has been started. Subsystem PID is 164006.
Finished starting tcpip daemons.
Starting NFS services:
0513-059 The biod Subsystem has been started. Subsystem PID is 176302.
0513-059 The rpc.lockd Subsystem has been started. Subsystem PID is 262390.
0513-059 The ctrmc Subsystem has been started. Subsystem PID is 229540.
Completed NFS services.
IBM Virtual I/O Server
login:
3 Initial setup
After the reboot you are presented with the VIO-Server login prompt. You can't login
as user root as you have to use the special user id padmin. No initial default
password is set. Immediately after login you are forced to set a new password.
[compat]: 3004-610 You are required to change your password.
Please choose a new one.
padmin's New password:
Enter the new password again:
The following file has been updated: .profile
Changes will take affect at next login.
Before you can do anything you have to accept the I/O Server license. This is done with the
license command.
$ lsmap
The I/O Server license must be accepted before running this command.
Only the chlang command may be run before accepting the license.
To view the license, run the license command with the -view option.
If the -lang flag is not specified the license will by displayed in
the current locale (set by the chlang command). If the license is not
available in the language selected, English will be the default.
To accept the license, run the license command with the -accept option.
Locale currently set to: "en_US".
Usage: license [-view] [-accept] [-lang Name]
license [-ls]
View and accept the I/O Server license agreement.
-accept Accept the license agreement.
-lang Specifies the language-territory (locale name) the license
is displayed in.
-ls Lists available locales.
-view Displays the license agreement.
Please enter:
license -accept
Before you start to define and assign resources please make sure you have the latest version and
updates installed before you proceed. Updates and support for the AIX-based Virtual I/O Server
Details beyond the scope of this publications can be found in the following Redbook
Advanced POWER Virtualization on eServer p5 Servers: Introduction and Basic
Once you are logged in as user padmin you find yourself in a restricted Korn shell with only a
limited set of commands. You can see all available commands with the command help. All these
commands are shell aliases to a single SUID-binary called ioscli which is located in the directory
/usr/ios/cli/bin. If you are familiar with AIX you will recognize most commands but most
command line parameters differ from the AIX versions.
Asking help in vio
As there are no man pages available you can see all options for each command separately by
issueing the command help . Here is an example for the command lsmap:
$ help lsmap
Usage: lsmap {-vadapter ServerVirtualAdapter | -plc PhysicalLocationCode |
-all}
[-net] [-fmt delimiter]
Displays the mapping between physical and virtual devices.
-all Displays mapping for all the server virtual adapter
devices.
-vadapter Specifies the server virtual adapter device
by device name.
-plc Specifies the server virtual adapter device
by physical location code.
-net Specifies supplied device is a virtual server
Ethernet adapter.
-fmt Divides output by a user-specified delimiter.
A very important command is oem_setup_env which gives you access to the regular AIX
command line interface. This is provided solely for the installation of OEM device drivers.
4 VIRTUAL SCSI SETUP
To map a LV
• mkvg: creates the volume group, where a new LV will be created using the mklv
command
• lsdev: shows the virtual SCSI server adapters that could be used for mapping with the LV
• mkvdev: maps the virtual SCSI server adapter to the LV
• lsmap -all: shows the mapping information
To map a physical disk
• lsdev: shows the virtual SCSI server adapters that could be used for mapping with a
physical disk
• mkvdev: maps the virtual SCSI server adapter to a physical disk
• lsmap -all: shows the mapping information
Client partition commands
• No commands needed, the Linux kernel is notified immediately
Create new volume group datavg with member disk hdisk1
• mkvg -vg datavg hdisk1
Create new logical volume vdisk0 in volume group
• mklv -lv vdisk0 datavg 10G
Maps the virtual SCSI server adapter to the logical volume
• mkvdev -vdev vdisk0 -vadapter vhost0
Display the mapping information
• lsmap -all
5 VIRTUAL ETHERNET SETUP
To list all virtual and physical adapters use the lsdev -type adapter command.
$ lsdev -type adapter
name status description
ent0 Available 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
ent1 Available 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
ent2 Available Virtual I/O Ethernet Adapter (l-lan)
ide0 Available ATA/IDE Controller Device
sisscsia0 Available PCI-X Dual Channel Ultra320 SCSI Adapter
vhost0 Available Virtual SCSI Server Adapter
vhost1 Available Virtual SCSI Server Adapter
vhost2 Available Virtual SCSI Server Adapter
vhost3 Available Virtual SCSI Server Adapter
vsa0 Available LPAR Virtual Serial Adapter
Choose the virtual Ethernet adapter we want to map to the physical Ethernet adapter.
$ lsdev -virtual
name status description
ent2 Available Virtual I/O Ethernet Adapter (l-lan)
vhost0 Available Virtual SCSI Server Adapter
vhost1 Available Virtual SCSI Server Adapter
vhost2 Available Virtual SCSI Server Adapter
vhost3 Available Virtual SCSI Server Adapter
vsa0 Available LPAR Virtual Serial Adapter
The command mkvdev maps a physical adapter to a virtual adapter, creates a layer 2 network
bridge and defines the default virtual adapter with its default VLAN ID. It creates a new
Ethernet interface, e.g., ent3.
Make sure the physical and virtual interfaces are unconfigured (down or detached).
6 SCENARIO A (ONE VIO SERVER)
Create a shared ethernet adapter ent3 with a physical one (ent0) and a virtual one (ent2)
with PVID 1:
$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1
ent3 Available
en3
et3
This has created a new shared ethernet adapter ent3 (you can verify that with the lsdev
command). Now configure the TCP/IP settings for this new shared ethernet adapter (ent3).
Please note that you have to specify the interface (en3) and not the adapter (ent3).
$ mktcpip -hostname op710-1-vio -inetaddr 9.156.175.231 -interface en3 \
-netmask 255.255.255.0 -gateway 9.156.175.1 -nsrvaddr 9.64.163.21 \
-nsrvdomain munich.de.ibm.com
7 SCENARIO B (TWO VIO SERVERS)
Create a shared ethernet adapter ent3 with a physical one (ent0) and a virtual one (ent2)
with PVID 1:
mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1
Configure the TCP/IP settings for the new shared ethernet adapter (ent3):
mktcpip -hostname op710-1-vio -inetaddr 9.156.175.231 -interface en3 \
-netmask 255.255.255.0 -gateway 9.156.175.1 -nsrvaddr 9.64.163.21 \
-nsrvdomain munich.de.ibm.com
INSTALLING FROM HMC
mksysb backup but a full one that creates theinstallios command.
hscroot@server1:~> installios
The following objects of type "managed system" were found. Please select one:
1. p570-ITSO
Enter a number: 1
The following objects of type "virtual I/O server partition" were found. Please
select one:
1. VIOS_DR_MACHINE
2. VIO_Server1
Enter a number (1-2): 1
The following objects of type "profile" were found. Please select one:
1. normal
Enter a number: 1
Enter the source of the installation images [/dev/cdrom]:
server5:/export/ios_backup/
Enter the client's intended IP address: 10.1.1.123
Enter the client's intended subnet mask: 255.255.255.0
Enter the client's gateway: 9.3.5.41
Enter the client's speed [100]:auto
Enter the client's duplex [full]:auto
Would you like to configure the client's network after the
installation [yes]/no? no
Note: If the CD or DVD backup spanned multiple disks, during the install, you will be
prompted to insert the next disk in the set with a similar message to the following message:
Please remove volume 1, insert volume 2, and press the ENTER key.
Note: The trailing slash in the NFS location server5:/export/ios_backup/ must be included
in the command as shown.
The configure client network setting must be set to no as shown. This is because the
physical adapter we are installing the backup through might already be used by an SEA
and the IP configuration will fail if this is the case. Log in and configure the IP if necessary
after the installation using a console session.
Retrieving information for available network adapters
This will take several minutes...
The following objects of type "Ethernet adapters" were found. Please select one:
1. ent U9117.570.107CD9E-V2-C2-T1 523300002002
2. ent U7311.D20.10832BA-P1-C01-T1 00096b6e8458
3. ent U7311.D20.10832BA-P1-C01-T2 00096b6e8459
Enter a number (1-3): 2
Here are the values you entered:
managed system = p570-ITSO
virtual I/O server partition = VIOS_DR_MACHINE
profile = normal
source = server5:/export/ios_backup/
IP address = 9.3.5.123
subnet mask = 255.255.255.0
gateway = 9.3.5.41
speed = 100
duplex = full
configure network = no
ethernet adapters = 00:09:6b:6e:84:58
Press enter to proceed or type Ctrl-C to cancel...
nimol_config MESSAGE: No NIMOL server hostname specified, using
server1.itsc.austin.ibm.com as the default.
Starting RPC portmap daemon
done
Starting kernel based NFS server
done
nimol_config MESSAGE: Added "REMOTE_ACCESS_METHOD /usr/bin/rsh" to the file
"/etc/nimol.conf"
nimol_config MESSAGE: Removed "disable = yes" from the file "/etc/xinetd.d/tftp"
nimol_config MESSAGE: Added "disable = no" to the file "/etc/xinetd.d/tftp"
Shutting down xinetd:
done
Starting INET services. (xinetd)
done
nimol_config MESSAGE: Removed "SYSLOGD_PARAMS=" from the file
"/etc/sysconfig/syslog"
nimol_config MESSAGE: Added "SYSLOGD_PARAMS=-r " to the file
"/etc/sysconfig/syslog"
nimol_config MESSAGE: Removed "local2,local3.* -/var/log/localmessages" from the
file "/etc/syslog.conf"
nimol_config MESSAGE: Added "local3.* -/var/log/localmessages" to the file
"/etc/syslog.conf"
nimol_config MESSAGE: Added "local2.* /var/log/nimol.log" to the file
"/etc/syslog.conf"
Shutting down syslog services
done
Starting syslog services
done
nimol_config MESSAGE: Executed /usr/sbin/nimol_bootreplyd -l -d -f /etc/nimoltab
-s server1.itsc.austin.ibm.com.
nimol_config MESSAGE: Successfully configured NIMOL.
nimol_config MESSAGE: target directory: /info/default5
nimol_config MESSAGE: Executed /usr/sbin/iptables -I INPUT 1 -s server5 -j ACCEPT.
nimol_config MESSAGE: source directory: /mnt/nimol
Chapter 2. Administration, backup, and restore 29
nimol_config MESSAGE: Checking /mnt/nimol/nim_resources.tar for existing
resources.
nimol_config MESSAGE: Executed /usr/sbin/iptables -D INPUT -s server5 -j ACCEPT.
nimol_config MESSAGE: Added "/info/default5 *(rw,insecure,no_root_squash)" to the
file "/etc/exports"
nimol_config MESSAGE: Successfully created "default5".
nimol_install MESSAGE: The hostname "lpar11.itsc.austin.ibm.com" will be used.
nimol_install MESSAGE: Added "CLIENT lpar11.itsc.austin.ibm.com" to the file
"/etc/nimol.conf"
nimol_install MESSAGE: Added
"lpar11.itsc.austin.ibm.com:ip=9.3.5.123:ht=ethernet:gw=9.3.5.41:sm=255.255.255.0:
bf=lpar11.itsc.austin.ibm.com:sa=9.3.5.194:ha=00096b6e8458" to the file
"/etc/nimoltab"
nimol_install MESSAGE: Executed kill -HUP 5149.
nimol_install MESSAGE: Created /tftpboot/lpar11.itsc.austin.ibm.com.
nimol_install MESSAGE: Executed /sbin/arp -s lpar11.itsc.austin.ibm.com
00:09:6b:6e:84:58 -t ether.
nimol_install MESSAGE: Executed /usr/sbin/iptables -I INPUT 1 -s
lpar11.itsc.austin.ibm.com -j ACCEPT.
nimol_install MESSAGE: Created
/info/default5/scripts/lpar11.itsc.austin.ibm.com.script.
nimol_install MESSAGE: Created /tftpboot/lpar11.itsc.austin.ibm.com.info.
nimol_install MESSAGE: Successfully setup lpar11.itsc.austin.ibm.com for a NIMOL
install
# Connecting to VIOS_DR_MACHINE
# Connected
# Checking for power off.
# Power off complete.
# Power on VIOS_DR_MACHINE to Open Firmware.
# Power on complete.
# Client IP address is 9.3.5.123.
# Server IP address is 9.3.5.194.
# Gateway IP address is 9.3.5.41.
# /pci@800000020000011/pci@2/ethernet@1 ping successful.
# Network booting install adapter.
# bootp sent over network.
# Network boot proceeding, lpar_netboot is exiting.
# Finished.
IT can be installed from full backup (not a
nim_resources.tar file), you can use the HMC to install these using the
Posted by Shivakant Tiwari at 2:54 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX VIRTUALIZATION, DLPAR/VIO, INSTALLING VIO SERVER, INSTALLING VIO SERVER STEP BY STEP, TYPES OF VIO SERVER INSTALLATION, VIO SERVER INSTALLATION EASY STEPS
Newer Posts Older Posts Home
FRIDAY, JUNE 3, 2011
AIX TL UPGRADE
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
TABLE OF CONTENTS
DOWNLOAD FIX 1
VERIFY THE SYSTEM 2
INSTALL SOFTWARE 3
TL UPGRADE BEST PRACTICES 4
IN A CLUSTERED ENV 5
REFERENCES 5
1) DOWNLOAD FIX
To download fix and service pack go to IBM fix central site
http://www-933.ibm.com/support/fixcentral/
Follow the screen shot
Select the required service pack and its prerequisite
And Download them, if download fails check for your latest java version on your desktop
1) VERIFY THE SYSTEM
Check for any installed emergency fix
Checking for installed ifixes
# emgr –l
Removing an ifix if it is installed
# emgr –r –L <ifix Label>
Verify that the system installed file sets are consistent
# lppchk –v
#lppchk –m3
Check all the file sets have same TL/ML level available
# instfix -i|grep ML
All filesets for 6100-00_AIX_ML were found.
All filesets for 6100-01_AIX_ML were found.
All filesets for 6100-02_AIX_ML were found.
All filesets for 6100-03_AIX_ML were found.
Commit all applied file set
# installp -c -f -g –X
3) INSTALL SOFTWARE
Now go to the download directory
Run
Smitty update_all
Update Installed Software to Latest Level (Update All)
Type or select a value for the entry field. Press Enter AFTER making all desired changes.
[Entry Fields]
* INPUT device / directory for software [.]
Just Type . and Press enter
Update Installed Software to Latest Level (Update All)
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* INPUT device / directory for software .
* SOFTWARE to update _update_all
PREVIEW only? (update operation will NOT occur) no
COMMIT software updates? Yes
SAVE replaced files? No
AUTOMATICALLY install requisite software? Yes
EXTEND file systems if space needed? Yes
VERIFY install and check file sizes? No
DETAILED output? No
Process multiple volumes? Yes
ACCEPT new license agreements? Yes
Preview new LICENSE agreements? No
WPAR Management
Perform Operation in Global Environment yes
Perform Operation on Detached WPARs no
Detached WPAR Names [_all_wpars]
Remount Installation Device in WPARs yes
Alternate WPAR Installation Device []
VERIFY THE UPDATE OF NEW TL BY
Oslevel –s
4) TL UPGRADE BEST PRACTICES
Try the above steps on a test scenario first
If the root vg is mirrored, it is better to unmirrorvg and then apply TL
Create an alt_disk_copy on the second disk, and apply TL at the same time
alt_disk_copy -d "<hdisk to install on >" -b update_all -l /<location of TL>
5) IN A CLUSTERED ENV
BRING THE CLUSTER NODE DOWN
a) Perform a round of cluster verification& sync from primary
b) Perform VG sync
c) Wait for cluster to be stable
d) Stop cluster service on inactive node ie-NodeB
e) Perform ML upgrade on NodeB & reboot
f) Start cluster service on NodeB
g) Perform cluster failover (From NodeA to NodeB) - (Stop with takeover is the best method)
h) Make sure cluster service is down on NodeA
i) Perform ML upgrade on NodeA& reboot
j) Start cluster service
k) Perform cluster verification from NodeB
l) Perform cluster failover (from NodeB to NodeA) - (Stop with takeover is the best method)
m) Start cluster service on NodeB
6) REFERENCES
http://www.ibm.com/developerworks/aix/library/au-aixtlupdate/index.html
Posted by Shivakant Tiwari at 3:19 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADV CONFS, AIX TL best practices, aix TL upgrage, How to upgrade TL in aix
SATURDAY, FEBRUARY 26, 2011
MOUNTING ISO IMAGE IN AIX
Crete a logical volume to accomodate your image
# mklv -y cdlv -s n -L /dev/cdlv rootvg 2G
cdlv
Copy the iso image to the lv just cerated "/dev/cdlv"
# ls
cd_image_163898 lost+found
# dd if=cd_image_163898 of=/dev/cdlv
Note that this command may take a long time and will create two dd processes.
root 368724 422050 1 02:08:39 pts/2 0:00 dd if=cd_image_163898 of=/dev/cdlv
root 393292 188554 0 01:22:54 - 0:00 telnetd -a
root 405736 434208 0 00:38:32 pts/1 0:00 -ksh
root 422050 155758 0 02:08:39 pts/2 0:00 dd if=cd_image_163898 of=/dev/cdlv
Create a Mount point and mount the device "/dev/cdlv" as a cdrom
# mount -v cdrfs -o ro /dev/cdlv /iso
# cd /iso
# ls
OSLEVEL etc ismp root usr
RPMS image.data mkcd.data sbin
bosinst.data installp ppc udi
#
Posted by Shivakant Tiwari at 1:02 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADV CONFS, INSTALLING PACKAGES FROM A ISO IMAGE ON AIX, Mount a aix iso image in aix, MOUNTING ISO IMAGE IN AIX
CREATING AIX MKSYSB ISO BOOTABLE IMAGE
Create a Mksysb image (Assuming that the system has two disk and rootvg contains 1 disk )
Create VG
mkvg -y datavg hdisk1
Create a File system in the new vg
crfs -v jfs2 -g datavg -a size=10G -m /data
Mount the new file system
mount /data
now crete a exclude.rootvg in /etc
echo "/data/" >> /etc/exclude.rootvg
Run mksysb command
mksysb -X -i -e /data/root.mkisysb
Now Create a bootable iso image from mksysb image
# mkdvd -S -m /root.mksysb
Initializing mkdvd log: /var/adm/ras/mkcd.log...
Verifying command parameters...
0512-054 mkdvd: File /root.mksysb does not exist or is empty.
# mkdvd -S -m /root.mkisysb
Initializing mkdvd log: /var/adm/ras/mkcd.log...
Verifying command parameters...
Creating temporary file system: /mkcd/cd_fs...
Populating the CD or DVD file system...
Building chrp boot image...
Copying backup to the CD or DVD file system...
......................................
Creating temporary file system: /mkcd/cd_images...
Creating Rock Ridge format image: /mkcd/cd_images/cd_image_163898
Running mkisofs ...
.......................................
mkrr_fs was successful.
Making the CD or DVD image bootable...
Removing temporary file system: /mkcd/cd_fs...
# pwd
/mkcd/cd_images
# ls -l
total 3236104
-rw-r--r-- 1 root sys 1656872960 Feb 25 01:50 cd_image_163898
drwxrwx--- 2 root system 512 Feb 25 01:44 lost+found
#
Posted by Shivakant Tiwari at 12:03 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADV CONFS, aix bootable mksysb, createing a bootable mksysb cd/dvd image, creating bootable cdrom from mksysb, creating iso image from mksysb image, making bootable cdrom from mksysb image
HOW TO CONFIGURE ISCSI CLIENT ON AIX
VERIFICATION OF DISK
This screen shot shows the output of lspv when we dont have any iscsi disk on the server
The screen show above shows that how a disk is mapped to a target
Now configure the target on aix server
Go to /etc/iscsi directory
and provide the target configuration In this example 192.168.5.202 is the storage and aix-target is the target
# cd /etc/iscsi
# ls
autosecrets targets targetshw
# tail -6 targets
# The target line would look like:
# 10.2.1.106 3260 iqn.2003-01.com.ibm:00.fcd0ab21.shark128 \
# "123ismysecretpassword.fc1b"
#
192.168.5.202 3260 aix-target
#
Now at the Aix server add the ip and change iscsi0 adapter configuration
Added ip as alias to connect to storage
Checked the connectivity
and changed iscsi0 adapter configuration
Run cfgmgr after that
# chdev -l en0 -a alias4=192.168.5.200 -a netmask=255.255.255.0
en0 changed
# ping -c 2 192.168.5.202
PING 192.168.5.202: (192.168.5.202): 56 data bytes
64 bytes from 192.168.5.202: icmp_seq=0 ttl=64 time=0 ms
64 bytes from 192.168.5.202: icmp_seq=1 ttl=64 time=0 ms
----192.168.5.202 PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms
# chdev -l iscsi0 -a initiator_name=aix-target
iscsi0 changed
# lspv
hdisk0 00c402db281a05c4 None
hdisk1 00c402db1717210e rootvg active
# cfgmgr
Now you can see a new disk from storage
# cfgmgr
# lspv
hdisk2 00c402db175641a3 None
hdisk0 00c402db281a05c4 None
hdisk1 00c402db1717210e rootvg active
# lsattr -El hdisk2
clr_q no Device CLEARS its Queue on error True
host_addr 192.168.5.201 Hostname or IP Address False
location Location Label True
lun_id 0x0 Logical Unit Number ID False
max_transfer 0x40000 Maximum TRANSFER Size True
port_num 0xcbc PORT Number False
pvid 00c402db175641a30000000000000000 Physical volume identifier False
q_err yes Use QERR bit True
q_type simple Queuing TYPE True
queue_depth 1 Queue DEPTH True
reassign_to 120 REASSIGN time out value True
rw_timeout 30 READ/WRITE time out value True
start_timeout 60 START unit time out value True
target_name aix-target Target NAME False
#
Posted by Shivakant Tiwari at 11:10 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX iscsi0 adapter configuration, AIX ADV CONFS, CONFIGURE ISCSI CLIENT ON AIX, configure the initiator on aix server, configuring iscsi initiator on aix, OPENFILER AIX
MONDAY, JANUARY 17, 2011
AIX SAMBA CONFIGURATION - BASIC SETUP
INSTALLING AND CONFIGURING SAMBA
DOWNLOAD SAMBA PACKAGE
Obtain samba from http://pware.hvcc.edu/download/aix53-64/
pware53-64.base.5.3.0.0.bff.gz pware53-64.krb5.1.7.1.0.bff.gz pware53-64.openldap.2.4.21.0.bff.gz pware53-64.readline.6.1.0.0.bff.gz
pware53-64.cyrus-sasl.2.1.23.0.bff.gz pware53-64.libiconv.1.13.1.0.bff.gz pware53-64.openssl.0.9.8.13.bff.gz pware53-64.samba.3.5.3.0.bff
pware53-64.gettext.0.17.0.0.bff.gz pware53-64.ncurses.5.7.0.1.bff.gz pware53-64.popt.1.10.4.0.bff.gz
INSTALLING SAMBA
Unzip package
# gunzip *
gunzip: pware53-64.samba.3.5.3.0.bff: unknown suffix -- ignored
Create table of contents
# inutoc .
Install Packages
installp -a -c -g -X -Y -d $(pwd) pware53-64.samba
+-----------------------------------------------------------------------------+
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
pware53-64.zlib.rte 1.2.3.0 USR APPLY SUCCESS
pware53-64.bdb.rte 4.7.25.4 USR APPLY SUCCESS
pware53-64.openssl.rte 0.9.8.13 USR APPLY SUCCESS
pware53-64.krb5.rte 1.7.1.0 USR APPLY SUCCESS
pware53-64.cyrus-sasl.rte 2.1.23.0 USR APPLY SUCCESS
pware53-64.openldap.rte 2.4.21.0 USR APPLY SUCCESS
pware53-64.samba.rte 3.5.3.0 USR APPLY SUCCESS
CONFIGURE BASIC SAMBA
# pwd
/opt/pware64/lib
# cat smb.conf
[global]
workgroup=mygroup
security=user
browseable=yes
[homes]
browseable=yes
read only=no
valid users=test1,test2,test3
START SAMBA DAEMONS
/opt/pware64/sbin/smbd -D
/opt/pware64/sbin/nmbd -D
Posted by Shivakant Tiwari at 6:07 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADV CONFS, AIX SAMBA CONFIGURATION, CONFIGURING SAMBA IN AIX, SAMBA AIX, SAMBA CONFIGURATION
SUNDAY, JANUARY 16, 2011
FAST CONNECT INSTALLATION AND CONFIGURATION
INSTALLING AND CONFIGURING FASTCONNECT ON AIX
# ls
VIEW FAST CONNECT INSTALLER BINARIES
cifs.advanced-demo cifs.msg.ca_ES cifs.msg.en_US cifs.msg.hu_HU cifs.msg.ko_KR cifs.msg.ru_RU cifs.msg.zh_TW
cifs.base cifs.msg.cs_CZ cifs.msg.es_ES cifs.msg.it_IT cifs.msg.pl_PL cifs.msg.sk_SK cifs.websm
cifs.client cifs.msg.de_DE cifs.msg.fr_FR cifs.msg.ja_JP cifs.msg.pt_BR cifs.msg.zh_CN
CREATE INUTOC
# inutoc .
#
RUN INSTALLP COMMAND TO INSTALL FAST CONNECT
installp -a -c -X -Y -g -d $(pwd) all
+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+
Pre-installation Failure/Warning Summary
----------------------------------------
Name Level Pre-installation Failure/Warning
-------------------------------------------------------------------------------
cifs.base.ldap 3.2.0.0 Requisite failure
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
cifs.client.rte 3.2.0.0 USR APPLY SUCCESS
cifs.base.smit 3.2.0.0 USR APPLY SUCCESS
cifs.base.lic 3.2.0.0 USR APPLY SUCCESS
cifs.base.cmd 3.2.0.0 USR APPLY SUCCESS
cifs.base.cmd 3.2.0.0 ROOT APPLY SUCCESS
cifs.advanced-demo.rte 3.2.0.0 USR APPLY SUCCESS
cifs.advanced-demo.rte 3.2.0.0 ROOT APPLY SUCCESS
cifs.websm.apps 3.2.0.0 USR APPLY SUCCESS
cifs.msg.zh_TW.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.zh_TW.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.zh_CN.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.zh_CN.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.sk_SK.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.sk_SK.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ru_RU.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ru_RU.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.pt_BR.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.pt_BR.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.pl_PL.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.pl_PL.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ko_KR.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ko_KR.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ja_JP.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ja_JP.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.it_IT.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.it_IT.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.hu_HU.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.hu_HU.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.fr_FR.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.fr_FR.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.es_ES.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.es_ES.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.en_US.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.en_US.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.de_DE.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.de_DE.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.cs_CZ.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.cs_CZ.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ca_ES.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ca_ES.base 3.2.0.0 USR APPLY SUCCESS
NOW FOLLOW STEP BY STEP INSTRUCTION
# smit smb
CONFIGURING SHARES
create a directory testshare
mkdir /testshare
create a share testshare and verify by viewing it
# net share
Share Name Share Type Path Name/Queue Name Share Description
---------- ---------- -------------------- -----------------
HOME File $HOME User's Home Directory Share
# man net
Manual entry for net not found or not installed.
# net share /add /type:file /netname:testshare /path:/testshare /desc:"A TEST SHARE"
Command completed successfully.
# net share
Share Name Share Type Path Name/Queue Name Share Description
---------- ---------- -------------------- -----------------
HOME File $HOME User's Home Directory Share
TESTSHARE File /testshare A TEST SHARE
#
You have to create a system user for fastconnect user to add and work
# net user /add fastusr -p
ERROR: 'fastusr' is not a valid system user.
# mkuser fastusr
# net user /add fastusr -p
Enter fastusr's password:
Command completed successfully.
## net user
Client user name Server user name User Comment
---------------- ---------------- ----------------
fastusr fastusr root nobody
#
configure acl permissions for each user created on share path
Posted by Shivakant Tiwari at 3:04 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADV CONFS, CONFIGURING FAST CONNECT IN AIX, EASY FAST CONNECT CONFIGURATION STEP BY STEP, FAST CONNECT INSTALLATION AND CONFIGURATION
Newer Posts Older Posts Home
THURSDAY, MAY 5, 2011
COMMAND TO SEE ALL THE MANAGED SYSTEM ON HMC
COMMAND TO SEE ALL THE MANAGED SYSTEM ON HMC
THW COMAND BELOW WILL SHOW YOU ALL THE MANAGED SYSTEM , MANAGED THROUGH HMC
hscroot@localhost:~> lsyscfg -r sys -F name
JKKUUYP5-9115-505-SN65A
EPDB-9131-52A-
CIServers-9117-570-SN6
BWDEV49-9110-51A-SN06E
JKKUUYP1-9115-505-
JKKUUYP7-9131-52A-SN6
UUYO-9133-55A-
SMGR61-9110-51A-SN9E
JKKUUYP4-9115-505-SN652155A
CRMQA-9110-51A-
UUYODEV-9110-51A-
JKKDB-9117-570-SN65095BE
BWDB-9117-570-SN65095CE
JKKQA-9110-51A-SN07E
TEST51-9110-51A-
JKKUUYP2-9115-505-
JKKUUYP6-9115-505-SN65
Server-8204-E8A-
UUYODB-9133-55A-
NETBACKUP-9110-51A-
IDES-9110-51A-
BACKUP-9110-51A-SN65
JKKDEV45-9110-51A-
JKKUUYP3-9115-505-SA
CRMDEV-9110-51A-SNE
UUYOCI-9133-55A-
EPDEV53-9110-51A-
THE COMMAND BELOW WILL GIVE THE DETAILED PROFILE CONFIGURATION OF A LPAR
hscroot@localhost:~> lssyscfg -r prof -m BACKUP-9110-
name=Full,lpar_id=1,lpar_env=aixlinux,state=Running,resource_config=1,os_version=Unknown,logical_serial_num=652BBFE1,default_profile=Normal,curr_profile=Normal,work_group_id=none,shared_proc_pool_util_auth=0,allow_perf_collection=0,power_ctrl_lpar_ids=none,boot_mode=norm,lpar_keylock=norm,auto_start=0,redundant_err_path_reporting=0
hscroot@localhost:~> lssyscfg -rprof prof -m BACKUP-9110-51A-
name=Normal,lpar_name=Full,lpar_id=1,lpar_env=aixlinux,all_resources=1,boot_mode=norm,conn_monitoring=0,auto_start=0,redundant_err_path_reporting=0
YOU CAN ALSO CONNECT TO ANY LPAR USING VTMENU hscroot@localhost:~> vtmenu
Retrieving name of managed system(s) . . . JKKUUYP5-9115-505-SN6 EPDB-9131-52A-SN CIServers-9117-570-SNFE BWDEV49-9110-51A-SN00E JKKUUYP1-9115-505-SN6A JKKUUYP7-9131-52A-SN656DG UUYO-9133-55A-SN650188H SMGR61-9110-51A-SN JKKUUYP4-9115-505-SN6 CRMQA-9110-51A-SN0 UUYODEV-9110-51A-SN0 CADE Server-8204-E8A-SN02 JKKDB-9117-570-SN65 BWDB-9117-570-SN65095CE JKKQA-9110-51A-S TEST51-9110-51A-SN0E JKKUUYP2-9115-505-SN6A JKKUUYP6-9115-505-S3A Server-8204-E8A-SN06D4552 UUYODB-9133-55A-SN0601AFH NETBACKUP-9110-51A-SN062CB4E DFG-9110-51A-SN BACKUP-9110-51A-SN6 JKKDEV45-9110-51A-SN65 JKKUUYP3-9115-505-SN0A CRSDEV-9110-51A-SN0E UUYOCI-9133-55A-SN0 EPSSV53-9110-51A-SN0
----------------------------------------------------------
Managed Systems:
----------------------------------------------------------
1) JKKUUYP5-9115-
2) DFG-9131-52A-SN65G
3) SDFG-9117-570-
4) BWDEV49-9110-51A-SN062
5) JKKUUYP1-9115-505-SNA
6) JKKUUYP7-9131-52A-SG
7) UUYO-9133-55A-SN61
8) SOLVH-9110-51A-SN062C
9) JKKUUYP4-9115-505-SNA
10) HBU-9110-51A-SN0CE
11) UUYODEV-9110-51A-SNDE
12) Server-8204-E8A-SN06542
13) JKKDB-9117-570-
14) KIUB-9117-570-SN69E
15) JKKQA-9110-51A-SN0E
16) TEST51-9110-51A-SN6AEE
17) JKKUUYP2-9115-505-SN6554A
18) JKKUUYP6-9115-505-
19) Server-8204-E8A-SND42
20) UUYODB-9133-55A-SN060H
21) NETBACKUP-9110-51A-SNB4E
22) IDES-9110-51A-SN0B6
23) BACKUP-9110-51A-SN6FE
24) JKKDEV45-9110-51A-
25) JKKUUYP3-9115-505-SN08A
26) CRMDEV-9110-51A-
27) UUYOCI-9133-55A-
28) xxxV53-9110-51A-SN1E
Enter Number of Managed System. (q to quit): 23
----------------------------------------------------------
Partitions On Managed System: BAC-9110-51A-
OS/400 Partitions not listed
----------------------------------------------------------
1) Full Running
Enter Number of Running Partition (q to quit): 1
1
Opening Virtual Terminal On Partition Full . . .
Open in progress
Open Completed.
AIX Version 5
(C) Copyrights by IBM and by others 1982, 2007.
login:
Posted by Shivakant Tiwari at 9:15 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, To list all managed resource objects in hmc
MONDAY, APRIL 18, 2011
SCHEDULING HMC BACKUP
SCHEDULING HMC BACKUP
Click on SCHEDULE OPERATIONS
Select new and click next
Fill date and time of schedule , select one time or repeated schedule
Select options select ftp or remote (nfs) and fill the in coming window
SELECT FTP SERVER
PROVIDE IP ADDRESS OF THE FTP SERVER
PROVIDE THE DIRECTORY TO STORE DATA
PROVIDE ADMIN PASSWORD TO COMPLETE THE OPERATION
Posted by Shivakant Tiwari at 3:01 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, SCHEDULING HMC BACKUP, taking hmc backup step by step screen shots
VIEWING HMC LOGS
Viewing HMC events
Open hmc
In the left side click on wecome screen
Click HMC operations
Click hmc events
Posted by Shivakant Tiwari at 2:55 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, HMC operations, Viewing HMC events
THURSDAY, MARCH 17, 2011
HMC Tips VI - Reference Code
1. To list the current reference code for the managed system :
# lsrefcode -r sys -m Managed-System
2. To list last 10 reference codes for the managed system :
# lsrefcode -r sys -m Managed-System -n 10
3. To list the reference code (Its called as LED in old pSeries servers) for each partition in the managed system :
# lsrefcode -r lpar -m Managed-System -F lpar_name,time_stamp,refcode
4. To list last 25 reference codes (led) for partitions lpar-a and lpar-b :
# lsrefcode -r lpar -m Managed-System -n 25 --filter ""lpar_names=lpar-a,lpar-b""
Posted by Shivakant Tiwari at 12:56 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: GETTING REFERENCE CODES IN HMC USING COMMAND LINE, HMC, HMC Reference Code, HMC COMMAND LINE FOR REFERENCE CODE
TUESDAY, MARCH 1, 2011
HMC Tips I - HMC and Managed System
HMC Tips I - HMC and Managed System
1. To enable ssh in a hmc :
# chhmc -c ssh -s enable
You can disable it by replacing the word 'enable' with 'disable'
2. To enable xntp in a hmc :
# chhmc -c xntp -s enable
You can disable it by replacing the word 'enable' with 'disable'
3. To add an entry in the syslog config file :
# chhmc -c syslog -s add -a IP_Addr ( or '-h host_name' )
You can remove an entry by replacing the word 'add' with 'remove'
4. To add an entry in the ntp config file :
# chhmc -c xntp -s add -a IP_Addr ( or 'h host_name' )
You can remove an entry by replacing the word 'add' with 'remove'
5. To configure the network as a startup device :
# chhmc -c netboot -s enable
You can disable it by replacing the word 'enable' with 'disable'
6. To permit IP addresses from utilizing HMC services :
# chhmc -s ssh ( or any_service) -s add -a IP_Addr
You can remove an entry by replacing the word 'add' with 'remove'
7. To add a DNC_server or domain_suffix :
chhmc -c network -s add [-ns DNS_Server] [-ds domain_suffix ]
You can remove an entry by replacing the word 'add' with 'remove'
8. To change network settings for a specific network interface :
# chhmc -c network -s modify -i interface_name
[-a IP_Addr] [-nm network_mask] [ --lparcomm on|off]
Note: Network settings for the s10 interface cannot be changed.
9. To change other network settings :
# chhmc -c network -s modify [-h hostname] [-d network-domain-name][-g gateway]
10. To change the locale for the HMC :
# chhmc -c locale -s modify -l locale
11. To change the HMC date and time, time zone :
# chhmc -c date -s modify[ --datetime ][ --clock {local | utc} ] [ --timezone {time-zone | none} ]
Posted by Shivakant Tiwari at 7:33 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: chhmc command, HMC, HMC Managed System commands, To enable ssh in a hmc, To enable xntp in a hmc
HMC Tips II - Partitions and Profiles
HMC Tips II - Partitions and Profiles
1. To list all machines configured in a hmc
# lssyscfg -r sys
2. To list all lpars(partitions) in a power machine
# lssyscfg -r lpar -m Managed_System
3. To activate/start an LPAR :
# chsysstate -r lpar -m Managed_System -o on -n LPAR_Name -f Profile_ name
4. To deactivate/shutdown an LPAR :
# chsysstate -r lpar -m Managed_System -o shutdown --immed -n LPAR_Name
5. To open the console of a partition :
# mkvterm -m Managed_System -p LPAR_Name
6. To close the console of a partition:
# rmvterm -m Managed_System -p LPAR_Name
7. To list the profile of a partition:
# lssyscfg -r prof -m Managed_System --filter "lpar_names=LPAR_Name,profile_names=Profile_Name"
8. To change the min/desired/maximum memory settings of a partition profile :
# chsyscfg -r prof -m Managed_System -i "name=Profile_Name,lpar_name=LPAR_Name,min_mem=512,desired_mem=19456,max_mem=20480"
9. To change the min/desired/maximum processor units of a partition profile :
# chsyscfg -r prof -m Managed_System -i "name=Profile_Name,lpar_name=LPAR_Name,min_proc_units=0.2,desired_proc_units=0.5,max_proc_units=2.0"
10. To change the min/desired/maximum virtual processor of a partition profile :
# chsyscfg -r prof -m Managed_System -i "name=Profile_Name,lpar_name=LPAR_Name,min_procs=1,desired_procs=2,max_procs=6"
11. To change capped/uncapped setting in a partition profile :
# chsyscfg -r prof -m Managed_System -i "name=Profile_Name,lpar_name=LPAR_Name,sharing_mode=uncap,uncap_weight=128"
Possible values for sharing_mode are cap and uncap.
Possible values for uncap_weight are from 0 to 128.
12. To change the name of a partition profile :
# chsyscfg -r prof -m Managed_System -i "name=Profile_Name,lpar_name=LPAR_Name,new_name=New_Profile_Name"
13. To change the name of a partition :
# chsyscfg -r lpar -m Managed_System -i "name=LPAR_Name,new_name=New_LPAR_Name"
14. To change the default profile of a partition :
# chsyscfg -r lpar -m Managed_System -i "name=LPAR_Name,default_profile=Partition_Profile_Name"
15. To set "power off the machine after all partitions are shutdown" for a power machine :
# chsysscfg -r sys -m Managed_System -i "power_off_policy=0"
Possible values are
0 -> Power off after all partitions are shutdown
1 -> Do not power off after all partitions are shutdown
16. To rename a system profile :
# chsyscfg -r sysprof -m Managed_System -i "name=Sys_Prof_Name,new_name=New_Sys_Prof_Name"
17. To add 2 more partition profiles to a system profile :
# chsyscfg -r sysprof -m Managed_System -i "name=,"lpar_names+=partition3,partition4",
"profile_names+=profile3,profile4""
Posted by Shivakant Tiwari at 7:31 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, To activate/start an LPAR, To change the min/desired/maximum memory settings of a partition profile, To change the min/desired/maximum processor units of a partition profile
HMC Tips III - User Management
HMC Tips III - User Management
1. To list all users in a HMC
# lshmcusr
2. To list only user names and managed resource roles for all HMC users :
# lshmcusr -F name:resourcerole
3. To create a user :
# mkhmcusr -u User_Id -a ROLE -d DESCRIPTION --passwd PASSWORD -M PASSWD_EXPIRATION_DAYS
3. To remove a user :
# rmhmcusr -u USER_NAME
4. To change an hmc user's password :
# chhmcusr -u User_Name -t passwd -v New_Password
5. To change the task role for the user "user1" to hmcoperator :
# chhmcusr -r user1 -t taskrole -v hmcoperator
Available task roles are
hmcsuperadmin, hmcoperator, hmcviewer, hmcpe, hmcservicerep or a user defined task role
6. To list all managed resource objects :
# lsaccfg -t resource
7. To list all managed resource roles :
# lsaccfg -t resourcerole
8. To create a task role using a config file :
# mkaccfg -t resourcerole -f /tmp/fil1
9. To create a task role :
# mkaccfg -t taskrole -i "name=tr1,parent=hmcsuperadmin,"resources=cec:chcod+lscod+lshwres,lpar:chssyscfg+lssyscfg+mksyscfg""
10. To change a task role :
# chaccfg -t taskrole -i "name=tr1,"resources=cec:chhwres+chsysstate,lpar:chssyscfg+chled+chhwres""
11. To remove a task role :
# rmaccfg -t taskrole -n tr1
Posted by Shivakant Tiwari at 7:30 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, To change an hmc user's password, To list all managed resource objects in hmc, To list all managed resource roles
HMC Tips VII - General Terms
HMC Tips VII - General Terms
1. What is the maximum number of servers managed by HMC ?
> Maximum of 48 non-590-595 servers
> Maximum of 32 590/595 servers
2. What is the maximum number of LPARs supported by a HMC ?
> Maximum of 254 LPARs
3. How many HMCs can manage a server at one time ?
> You can have a maximum of 2 HMCs manage a server at one time
4. What are the different types of dynamic operations you can do with CPU, Memory and I/O Adapter on a LPAR ?
> Add
> Remove
> Move
5. How do we connect the HMC to power machines ?
For Power-4 machines, we connect the hmc using serial cables.
But for Power-5 machines, HMC connects to service processors via SSL-encrypted Ethernet, replacing the serial cables.
6. Do we have firewall configured in HMC ?
Yes. Each network card has an integrated firewall.
7. Do we need to configure DHCP in HMC ?
HMC may be a DHCP server for entry and mid-range servers.
But for high-end servers like P595, HMC must be a DHCP server
8. can we have the same HMC to manage P4 and P5 machines ?
POWER5 HMCs cannot manage POWER4 servers, and vice versa.
9. Can we have the existing P4 HMCs upgraded to support P5 machines ?
Yes. We can. This involves a complete overwirte of teh disk and the loss of all previous configuration including user profiles.
10. What to do incase of disk failure in HMC ?
We can restore the HMC using recovery CD.
Then restore the latest Critical consule data backup which will restore the profiles, user ids, passwords, etc..
11. What is the default user id and password for the HMC ?
When the HMC is powered on the first time, login as hscroot and password as 'abc123'.
12. Can we manage a power machine without a HMC ?
Yes. We can run a server in manufacturing default mode, will all resources but no logical partitionings, CoD or Service Focal point,etc..
For entry level server, we can use the Integrated Virtualization Manager.
13. What is the network critetia for dual HMC connection ?
Dual HMCs require two different private networks.
14. What is the default service processor IP address in Power-5 Machines ?
Eth0 - HMC1 - 192.168.2.147 / 255.255.255.0
Eth1 - HMC2 - 192.168.3.147 / 255.255.255.0
15. What is the default user id and password for accessing service processor ?
User id - admin
Password - admin
16. Do we need a HMC for p5 model servers ?
One HMC is mandatory for 590, 595 or 575.
Dual HMC are recommended.
17. Do we need private network for HMc connectivity for p5-595 ?
One private network is mandatory for p5 590,595 or 575.
18. Can we have IVM support multiple servers ?
One IVM allowed per server and it only manages partitions on one server.
19. What does FSP (Flexible Service Processor) has ?
FSP has
a. Operating System
b. UserIds / Passwords
c. Filesystem
d. Networking
e. Firewall
f. Webserver
g. ASMI
h. Firmware
20. What to do if you forgot the admin password for FSP ?
If you do not know the admin password, place a hardware call to get 'celogin'
21. What to do if you forgot the HMC hostname/ipaddress for a long running LPAR ?
You can always get the HMC IPaddress from a LPAR if we have performed "handshake" with the HMC.
Issue the below command to get the HMC IPAddress
# lsrsrc IBM.ManagementServer
Resource Persistent Attributes for IBM.ManagementServer
resource 1:
Name = "169.121.54.48"
Hostname = "169.121.54.48"
ManagerType = "HMC"
LocalHostname = "169.121.54.59"
ClusterTM = "9078-160"
ClusterSNum = ""
ActivePeerDomain = ""
NodeNameList = {"SAP-PRodServer"}
22. One HMC should be within 8metres of Managed Server
23. Each FSP Ethernet port should be connected to only one HMC
Posted by Shivakant Tiwari at 7:29 PM 1 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: command to get the HMC IPAddress, Flexible Service Processor, HACMP BASIC QUESTIONS, HMC, HMC - General Terms, HMC INTERVIEW QUESTIONS, service processor IP address in Power-5 Machines
HMC Tips IV - Backup
HMC Tips IV - Backup
1. To backup HMC data on DVD :
# bkconsdata -r dvd
2. To backup HMC data to a ftp server :
# bkconsdata -r ftp -h ftp_server_name -u ftp_username --passwd ftp_password
3. To backup HMC data to a NFS mounted file system :
# bkconsdata -r nfs -n nfs_server_name -l Nfs_mount_point
4. To list storage media devices :
# lsmediadev
5. To backup profile data for a managed system :
# bkprofdata -m Managed-System -f File_name
Profile data files are kept under /var/hsc/profiles/Managed-Machine-Serial-Number
6. To restore a managed profile data :
# rstprofdata -m Managed-System -l restore_type -f File-Name
Valid restore types are
1 - Full restore from the backup file.
2 - Merge the current profile data and backup profile data, with priority to backup.
3 - Merge the current profile data and backup profile data, with priority to current data.
4 - Initialize the profile data. All partition, partition/system profiles will be deleted.
Posted by Shivakant Tiwari at 7:20 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, HMC Backup, To backup HMC data to a ftp server, To backup HMC data to a NFS mounted file system
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)
THURSDAY, MARCH 3, 2011
AIX DISK RELATED TROUBLESHOOTING - REMOVING MISSING DISK
HOW TO DEAL WITH MISSING DISK
IF YOU REMOVE A DISK WITHOUT REMOVING THE DISK FROM VOLUME GROUP IT CAN CREATE A BIG ISSUE ASSUMING THAT YOU HAVE MORE THAN ONE DISK IN THE VOLUME GROUP
1)COLLECT THE ODM INFORMATION OF THE OTHER DISK
2)MANUPULATE VALUES LIKE PVID AND CONNECTION AND NAME
3)ADD THE CHANGED ENTRY TO ODM
3)REDUCE THE PV FROM ODM
1)SIMULATE PROBLEM
# lsvg testvg
VOLUME GROUP: testvg VG IDENTIFIER: 00fad1d400004c00000001300193c765
VG STATE: active PP SIZE: 16 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 801 (12816 megabytes)
MAX LVs: 256 FREE PPs: 801 (12816 megabytes)
LVs: 0 USED PPs: 0 (0 megabytes)
OPEN LVs: 0 QUORUM: 2
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no
# lsvg -p testvg
testvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 259 259 52..52..51..52..52
hdisk4 active 542 542 109..108..108..108..109
# varyoffvg testvg
# rmdev -dl hdisk4
hdisk4 deleted
#
# varyonvg testvg
PV Status: hdisk2 00fad1d44e4f4d58 PVACTIVE
00fad1d47168f544 PVMISSING
varyonvg: Volume group testvg is varied on.
#
2)COLLECT DATA
# odmget -q "name=hdisk2" CuAt
CuAt:
name = "hdisk2"
attribute = "maxlun"
value = "7"
type = "R"
generic = "UD"
rep = "nr"
nls_index = 44
CuAt:
name = "hdisk2"
attribute = "pvid"
value = "00fad1d44e4f4d580000000000000000"
type = "R"
generic = "D"
rep = "s"
nls_index = 2
# odmget -q "name=hdisk2" CuDv
CuDv:
name = "hdisk2"
status = 1
chgstatus = 2
ddins = "scdisk"
location = "04-C0-00-2,0"
parent = "scsi0"
connwhere = "2,0"
PdDvLn = "disk/scsi/osdisk"
JUST USE THIS SCRIPT TO COLLECT DATA
for x in CuDv CuAt CuPath
do
odmget -q "name=hdisk2" $x > /tmp/disk/hdisk2.$x
done
2)MANUPULATE THE DATA
PVID OF FAILED HDISK YOU CAN GET BY DOING lsvg -p ON THE VG
# lsvg -p testvg
testvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 259 259 52..52..51..52..52
0516-304 lsvg: Unable to find device id 00fad1d47168f544 in the Device
Configuration Database.
00fad1d47168f544 missing 542 542 109..108..108..108..109
CREATE A SEPERATE FILE FOR CHANGED DATA
cat /tmp/disk/hdisk2.CuAt|sed -e 's/hdisk2/hdisk4/g' -e 's/00fad1d44e4f4d58/00fad1d47168f544/' -e 's/609SYMMETRIX/719SYMMETRIX/' > /tmp/disk/hdisk4.CuAt
cat /tmp/disk/hdisk2.CuDv| sed -e 's/hdisk2/hdisk4/' -e 's/2,0/2,4/' > /tmp/disk/hdisk4.CuDv
SEE THE CHANGED VALUES
# pwd
/tmp/disk
# ls
hdisk2.CuAt hdisk2.CuDv hdisk2.CuPath hdisk4.CuAt hdisk4.CuDv
# cat hdisk4.CuAt
CuAt:
name = "hdisk4"
attribute = "maxlun"
value = "7"
type = "R"
generic = "UD"
rep = "nr"
nls_index = 44
CuAt:
name = "hdisk4"
attribute = "pvid"
value = "00fad1d47168f5440000000000000000"
type = "R"
generic = "D"
rep = "s"
nls_index = 2
# cat hdisk4.CuDv
CuDv:
name = "hdisk4"
status = 1
chgstatus = 2
ddins = "scdisk"
location = "04-C0-00-2,4"
parent = "scsi0"
connwhere = "2,4"
PdDvLn = "disk/scsi/osdisk"
#
3)ADD THE DATA INTO ODM
odmadd /tmp/disk/hdisk4.CuAt
odmadd /tmp/disk/hdisk4.CuDv
# lsvg -p testvg
testvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 259 259 52..52..51..52..52
hdisk4 missing 542 542 109..108..108..108..109
4)REMOVE THE DISK FROM VG AND THEN FROM ODM
# odmadd /tmp/disk/hdisk4.CuAt
# odmadd /tmp/disk/hdisk4.CuDv
# lsvg -p testvg
testvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 259 259 52..52..51..52..52
hdisk4 missing 542 542 109..108..108..108..109
# lspv hdisk4
PHYSICAL VOLUME: hdisk4 VOLUME GROUP: testvg
PV IDENTIFIER: 00fad1d47168f544 VG IDENTIFIER 00fad1d400004c00000001300193c765
PV STATE: missing
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 16 megabyte(s) LOGICAL VOLUMES: 0
TOTAL PPs: 542 (8672 megabytes) VG DESCRIPTORS: 1
FREE PPs: 542 (8672 megabytes) HOT SPARE: no
USED PPs: 0 (0 megabytes)
FREE DISTRIBUTION: 109..108..108..108..109
USED DISTRIBUTION: 00..00..00..00..00
REMOVE USING PVID ONLY
# reducevg -df testvg 00fad1d47168f544
# lsvg -p testvg
testvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 259 259 52..52..51..52..52
#
# odmdelete -o CuDv -q "name=hdisk4"
0518-307 odmdelete: 2 objects deleted.
# odmdelete -o CuAt -q "name=hdisk4"
0518-307 odmdelete: 4 objects deleted.
Posted by Shivakant Tiwari at 10:13 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX REMOVING DISK THAT ARE ACCIDENTALLY REMOVED, AIX TROUBLESHOOTING, REMOVING DISKS FROM ODM, removing missing disk, SOLVING AIX VG PROBLEMS
REPAIRING CORRUPT VG
If there is a hardware failure, and one or 2 disk in the volume group get completely trashed. The vg was reduced by two disks.
1. Use the (undocumented) readvgda command to get the detailed VGDA from one of the disks, e.g. "readvgda /dev/hdiskn". I advise you to do the same on a disk that *didn't* fail and compare (a disk that didn't fail might be a more reliable source). Check the list of PVIDs and make sure they are all
present and accessible by the system (no hardware problems). Save the readvgda output in a file, you will need it if you make a mistake later and want to start over.
2. Among the readvgda output is the layout of each LV on the PVs, from which you can construct LV map files for the mlkv command.
3. You will also need a good copy of the /etc/filesystems file,unless you remember the original LV mount points and filesystem types.
4. When you have all the LV map files, export the volume group and re−create it on the original PVs, with the original PP size:
mkvg −f −y vgdvd −s 1024 hdisk3 hdisk4 ...
5. Re−create each LV using the map files. I assume here that your filesystems were jfs (change accordingly if you had jfs2):
mklv −y loglv02 −m <loglv02_mapfile> −t jfslog vgdvd <numlp>
mklv −y data1 −m <data1_mapfile> −t jfs vgdvd <numlp>
...
6. Restore /etc/filesystems or add the missing stanzas manually. *Do not mount the filesystems yet.*
7. For each filesystem LV, update the LVCB with the log and label information:
chfs −a log=/dev/loglv02 <mountpoint>
chlv −L <mountpoint> data1
8. Run a fsck on each filesystem. This is the critical step – if the command fails because it can't find the superblock, then the LVs were not re−created correctly, stop and check your map files. If the jfslog LV was not re−created correctly, fsck will not be able to replay the log and you will probably lose some data. Consider stopping and double−checking the map files before answering yes to the fsck "fix" questions. Also, if filesystems were active at the time of the crash, fsck might find unrecoverable errors on some inodes or blocks, your only option here is to fix these errors at the risk of losing some inodes (the price for not having a tape backup). If errors were fixed, re−run fsck until there are no errors.
9. When fsck run without errors on each FS, mount the filesystems. If errors were fixed during fsck, check the lost+found directories, they might contain missing files or directories you can salvage.
Posted by Shivakant Tiwari at 10:04 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX TROUBLESHOOTING, AIX VG TROUBLESHOOTING, REPAIRING CORRUPT VG IN AIX
TUESDAY, MARCH 1, 2011
REPLACING A FAILED PV IN A MIRRORED VOLUME GROUP
INTRODUCTION
The following procedures replace a failed physical volume (PV) within a mirrored volume group. The replacepv command provides a method for replacing a failed PV in most configurations. An alternative procedure is also provided for configurations where the replacepv command cannot be used.
Prerequisites
All logical volumes using the failed PV have valid copies on other available PVs (with the possible exception of a dedicated dump logical volume). If any of the prerequisites listed below cannot be met, see the alternate procedure.
The volume group containing the failed PV is not rootvg.
The replacement PV can be added to the volume group containing the failed PV (this might not be possible depending on the PV size and volume group characteristics, such as MAX PPs per PV).
The replacement PV must be able to be configured into the system at the same time as the failing PV.
The replacement PV's name can differ from the failed PV's name.
The size of the replacement PV must be at least the size of the failed PV.
The volume group containing the failed PV must not be a snapshot volume group or have a snapshot volume group.
PROCEDURE TO REPLACE FAILED DISK
Complete the following steps, assuming that the failed PV is hdisk2 and the replacement PV is hdisk10:
If the replacement PV is not yet installed on the system, perform the steps necessary to install it. To use the configuration manager to define a new PV, run the following command:
cfgmgr
Use the lspv command to determine the name assigned to the PV. For this example, assume that the new PV is named hdisk10.
To replace the failed PV with the one defined in
Step 1, run the following command:
replacepv hdisk2 hdisk10
\When the command runs, hdisk2 is replaced by hdisk10, and hdisk2 is no longer assigned to a volume group.
To undefine the failed PV, run the following command:
rmdev -dl hdisk2
Physically remove the failed disk from the system.
Verify that the procedure was successful by completing the following steps:
To check that all logical volumes are mirrored to the new PV as desired, run the following command:
lslv lvname
Check the COPIES attribute of each logical volume affected by the failed PV to ensure that the desired number of copies now exist. If the number of copies of the logical volume is below the desired number, use the mklvcopy command to create additional copies.
To verify that all logical volume partitions are synchronized and there are no stale partitions, run the following command:
lspv hdisk10
Check the STALE PARTITIONS attribute of the replaced PV to ensure that the count is zero. If there are stale partitions use the syncvg command to synchronize the partitions.
Replacing a failed PV when the configuration does not allow the use of the replacepv command
Assume that the failed physical volume, hdisk0, and its mirror, hdisk1, are part of the yourvg volume group.
To remove mirror copies from the failed PV, run the following command:
unmirrorvg yourvg hdisk0
If the PV failure occurred on rootvg, remove hdisk0 from the boot list by running the following command:
Note: If your configuration uses boot devices other than hdisk0 and hdisk1, add them to the command syntax.
bootlist -om normal hdisk1
This step requires that hdisk1 remains a bootable device in rootvg. After completing this step, ensure that hdisk0 does not appear in output.
If the PV failure occurred on rootvg, recreate any dedicated dump devices from the failed PV.
If you have a dedicated dump device that was on the failed PV, you can use the mklv command to create a new logical volume on an existing PV. Use the sysdumpdev command to set the new logical volume as the primary dump device.
To undefine the failed PV, run the following command:
Note: Removing the disk device entry will also remove the /dev/ipldevice hard link if the failed PV is the PV used to boot the system.
reducevg yourvg hdisk0
rmdev -dl hdisk0
If the failed PV is the most recently used boot device, recreate the /dev/ipldevice hard link that was removed in Step 4 by running the following command:
ln /dev/rhdisk1 /dev/ipldevice
Note the r prefixed to the PV name.
To verify that your /dev/ipldevice hard link has been recreated, run the following command:
ls /dev/ipldevice
Replace the failed disk.
To define the new PV, run the following command:
cfgmgr
The cfgmgr command assigns a PV name to the replacement PV. The assigned PV name is likely to be the same as the PV name previously assigned to the failed PV. In this example, assume that the device hdisk0 is assigned to the replacement PV.
To add the new PV to the volume group, run the following command:
extendvg yourvg hdisk0
You might encounter the following error message:
0516-050 Not enough descriptor space left in this volume group.
Either try adding a smaller PV or use another volume group.
If you encounter this error and cannot add the PV to the volume group, you can try to mirror logical volumes to another PV that already exists in the volume group or add a smaller PV. If neither option is possible, you can try to bypass this limitation by upgrading the volume group to a Big-type or Scalable-type volume group using the chvg command.
Mirror the volume group.
Note: The mirrorvg command cannot be used if all of the following conditions exist:
The target system is a logical partition (LPAR).
A copy of the boot logical volume (by default, hd5) resides on the failed PV.
The replacement PV's adapter was dynamically configured into the LPAR since the last cold boot.
If all of the above conditions exist, use the mklvcopy command to recreate mirror copies for each logical volume as follows:
Create copies of the boot logical volume to ensure that it is allocated to a contiguous series of physical partitions.
Create copies of the remaining logical volumes, and synchronize the copies using the syncvg command.
Make the disk bootable by shutting down the LPAR and activating it instead of rebooting using the shutdown or reboot commands. This shutdown does not have to be done immediately, but it is necessary for the system to boot from the new PV.
Otherwise, create new copies of logical volumes in the volume group using the new PV with the following command:
Note: The mirrorvg command disables quorum by default. For rootvg, you will want to use the -m option to ensure that the new logical volume copies are mapped to hdisk0 in the same way as the working disk.
mirrorvg yourvg hdisk0
If your configuration holds third copies of some logical volumes, you might need to recreate those copies with the following command:
mklvcopy -k
If the PV failure occurred on rootvg, initialize the boot record by running the following command:
bosboot -a
If the PV failure occurred on rootvg, update the boot list by running the following command:
Note: If your configuration uses boot devices other than hdisk0 and hdisk1, add them to the command.
bootlist -om normal hdisk0 hdisk1
Verify that the procedure was successful.
To verify that all logical volumes are mirrored to the new PV, run the following command:
lslv lvname
Check the COPIES attribute of each logical volume affected by the failed PV to ensure that the desired number of copies now exist. If the number of copies of the logical volume is below the desired number, use the mklvcopy command to create additional copies.
To verify that all the logical volume partitions are synchronized, check that there are no stale partitions by running the following command:
lspv hdisk0
Check the STALE PARTITIONS attribute of the replaced PV to ensure that the count is zero. If there are stale partitions use the syncvg command to synchronize the partitions.
If the PV failure occurred on rootvg, use the following steps to verify other aspects of this procedure:
To verify the boot list, run the following command:
bootlist -om normal
To verify the dump device, run the following command:
sysdumpdev -l
To verify the list of bootable PVs, run the following command:
ipl_varyon -i
To verify the /dev/ipl_device, run the following command:
ls -i /dev/rhdisk1 /dev/ipldevice
Ensure the output of the ls command has the same i-node number for both entries.
This step completes the procedure.
Posted by Shivakant Tiwari at 7:18 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX TROUBLESHOOTING, Mirror the volume group., PROCEDURE TO REPLACE FAILED DISK IN AIX, reducevg, REPLACING A FAILED PV IN A NIRRORED VOLUME GROUP, USING REPLACEPV COMMAND
FRIDAY, SEPTEMBER 24, 2010
AIX PRINT QUEUE AND NFS TROUBLESHOOTING
AIX PRINT QUEUE AND NFS RELATED TROUBLESHOOTING
Check for system date and verify that it is correct
The qdaemon automatically rebuilds the qconfig.bin file When the /etc/qconfig file changes. If the date on the qconfig file is of earlier than the date on the qconfig.bin file, the qconfig file is not digested, even if it was just modified.
IF the changes to the qconfig file are correct,.If the dates on the qconfig.bin file and the qconfig file are not correct the /etc/qconfig file is no longer linked to the /usr/lpd/qconfig file
If no other user except root can print, check the permissions of the /tmp directory. Also, check the permissions of the print commands being used
refreshed the print queue with command
qadm –K <queue name>
qadm –U <queue name>
or use enq command
Verify the configuration of the queue
root@node1[/etc]-> cat qconfig|awk '/mos/,/backend/'
mos:
device = hp@mos
hp@mos:
file = /var/spool/lpd/pio/@local/dev/hp@mos#hpJetDirect#9100
header = never
trailer = never
access = both
backend = /usr/lib/lpd/pio/etc/piojetd mos 9100
root@node1[/etc]->
Here queue name is mos , device type is HP jet direct on
port 9100 The line backend runs the command/script to
print
A TYPICAL OUTPUT OF piojetd SCRIPT
Shows that the background print manager is piobe
"if [[ $1 = +([0-9]) && ! -f $1 ]]
then
port=$1
shift
else
port=9100
fi
trap "trap 15;kill -15 0;exit 0" 15
/usr/lib/lpd/piobe "$@" | /usr/lib/lpd/pio/etc/piohpnpf -x $hostname -p
$port
if [ "$?" -ne 0 ]
then
exit 64
fi"
Check the status of print queue
root@node1[/etc]-> qchk -P mos
Queue Dev Status Job Files User PP % Blks Cp Rnk
------- ----- --------- --- ------------------ ---------- ---- -- ----- --- ---
mos hp@mo READY
Step 3)
If required kill the queue and restart it
root@node1[/etc]-> qadm -K mos
root@node1[/etc]-> qadm -U mos
Step 4)
ping the network printer
root@node1[/etc]-> ping -c 2 mos
PING mos.com: (10.24.190.86): 56 data bytes
64 bytes from 10.24.190.86: icmp_seq=0 ttl=60 time=50 ms
64 bytes from 10.24.190.86: icmp_seq=1 ttl=60 time=68 ms
----mos.com PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 50/59/68 ms
root@node1[/etc]->
If ping is all right check printer connectivity
root@node1[/etc]-> telnet 10.24.190.86 9100
Trying...
Connected to 10.24.190.86.
If connectivity is all right , Printer should print , if it is still
not printing either there is a problem in physical device ,
or printer is not responding , restart the physical device
(power cycle) and check
Verify the virtual printer queue
stiwari@ch [/tmp]-> cat /etc/qconfig |awk '/A00a:/,/backend/'
A00a:
device = @option
up = TRUE
host = option
s_statfilter = /usr/lib/lpd/bsdshort
l_statfilter = /usr/lib/lpd/bsdlong
rq = A00a
@option:
backend = /usr/lib/lpd/rembak -T10
Here virtual host is option and remote queue is A00a , the
script/program that is printing in the background is
rembak
remote printer
Check the remote printer as same as we checked the virtual printer
Run the following command to get a detail diagnostic of
stiwari@che[/tmp]->
This command prints on server 120.. print queue A00a
and gives the output in print.out
The file getting printed is /tmp/asd
/usr/lib/lpd/rembak -S 120.23.2.219 -P A00a -N /usr/lib/lpd/aixv2short –D /tmp/print.out /tmp/asd
stiwari@che[/tmp]-> cat print.out
rembak[1466612] main: Wed Sep 22 16:46:17 2010
rembak[1466612] main: /usr/lib/lpd/rembak -S 120.23.2.219 -P A00a -N
/usr/lib/lpd/aixv2short -D /tmp/print.out /tmp/asd
rembak[1466612] main: backend=0.
rembak[1466612] hookup: Try to connect, current time=1285188377.
rembak[1466612] sendjob: sendjob starts, jobname=/tmp/asd, current
time=1285188377.
rembak[1466612] sendjob: datafn[0]=dfA377che, fakedfn=dfA377che.
rembak[1466612] makecontrolfile: Entering makecontrolfile.
rembak[1466612] makecontrolfile: dfnames[0]=dfA377che
/ò@ak[1466612] getbsdinfo: bsd3=Hche\10 Proot\10 J/tmp/asd\10 Cche\10
Lroot\10
rembak[1466612] get_bsd_4file: bsd nc=1
/ò
][N/tmp/asd\10 ][N/tmp/asd\10 ]
/ò@ak[1466612] getbsdinfo: bsd3=Hche\10 Proot\10 J/tmp/asd\10 Cche\10
Lroot\10 fdfA377che\10 UdfA377che\10 N/tmp/asd\10
rembak[1466612] gettmpr: Opening file /tmp//rembakmTypqa.
rembak[1466612] gettmpr: File /tmp//rembakmTypqa opened successfully,
fd=5.
rembak[1466612] sendjob: ctrlfname=/tmp//rembakmTypqa,
fakecfn=cfA377che.
rembak[1466612] sendjob: State machine starts.....
rembak[1466612] sendjob: State 1 - send the "Receive a Print Job" request.
/ò sendreq - sending lpd request [\2 A00a\10 ].
rembak[1466612] gotack: Reading ACK status.....current time=1285188377,
timeout_ack=90.
rembak[1466612] gotack: ACK status=0x0.
rembak[1466612] sendjob: state 3 - Send data file(s), dfcount=1.
rembak[1466612] sendjob: realfn=/tmp/asd, fakefn=dfA377che,
filter=/usr/lib/lpd/aixv2short.
/òPak[1466612] sendreq: sendreq - sending lpd request [\3 11 dfA377chew\10
].
rembak[1466612] gotack: Reading ACK status.....current time=1285188377,
timeout_ack=90.
rembak[1466612] gotack: ACK status=0x0.
rembak[1466612] senddatafile: Opening file /tmp/asd.
rembak[1466612] senddatafile: File /tmp/asd opened successfully, fd=6.
rembak[1466612] send_file_rembak: Reading 11 bytes from file, fd=6.
rembak[1466612] send_file_rembak: Writing 11 bytes to socket 4.
rembak[1466612] send_file_rembak: File sent.
rembak[1466612] ack: Send ACK.
rembak[1466612] send_file_rembak: waiting for ACK.
ıak[1466612] get_bsd_4file: bsd strings: [N/tmp/asd\10 ][N/tmp/asd\10
rembak[1466612] gotack: Reading ACK status.....current time=1285188377,
timeout_ack=90.
rembak[1466612] gotack: ACK status=0x0.
rembak[1466612] sendjob: State 2 - send control file,
ctrlfname=/tmp//rembakmTypqa, fakecfn=cfA377che.
/òPak[1466612] sendreq: sendreq - sending lpd request [\2 76 cfA377che\10 ].
rembak[1466612] gotack: Reading ACK status.....current time=1285188377,
timeout_ack=90.
rembak[1466612] gotack: ACK status=0x0.
rembak[1466612] sendcontrolfile: Opening file /tmp//rembakmTypqa.
rembak[1466612] sendcontrolfile: File /tmp//rembakmTypqa opened
successfully, fd=6.
rembak[1466612] send_file_rembak: Reading 76 bytes from file, fd=6.
rembak[1466612] send_file_rembak: Writing 76 bytes to socket 4.
rembak[1466612] send_file_rembak: File sent.
rembak[1466612] ack: Send ACK.
rembak[1466612] send_file_rembak: waiting for ACK.
rembak[1466612] gotack: Reading ACK status.....current time=1285188377,
timeout_ack=90.
rembak[1466612] gotack: ACK status=0x0.
rembak[1466612] sendjob: State 5 - end of job /tmp/asd.
rembak[1466612] sendjob: Delete control file /tmp//rembakmTypqa.
stiwari@che[/tmp]->
This output will give all the details of sending file to be printed
on the remote host and it can be diagnosed easily where is
the error
TROUBESHOOTING NFS
Verify that the network connections are good.
Verify that the server is up and running by running the following command at the shell prompt of the client:
/usr/bin/rpcinfo -p server_name
protocols, and port numbers is printed, similar to the following
If the server is up, a list of programs, versions,:
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 1025 mountd
100001 1 udp 1030 rstatd
100001 2 udp 1030 rstatd
100001 3 udp 1030 rstatd
100002 1 udp 1036 rusersd
100002 2 udp 1036 rusersd
100008 1 udp 1040 walld
100012 1 udp 1043 sprayd
100005 1 tcp 694 mountd
100003 2 udp 2049 nfs
100024 1 udp 713 status
100024 1 tcp 715 status
100021 1 tcp 716 nlockmgr
100021 1 udp 718 nlockmgr
100021 3 tcp 721 nlockmgr
100021 3 udp 723 nlockmgr
100020 1 udp 726 llockmgr
100020 1 tcp 728 llockmgr
100021 2 tcp 731 nlockmgr
If a similar response is not returned, log in to the server at the
server console and check the status of the inetd daemon
lssrc –ls inetd
Verify that the mountd, portmap and nfsd daemons are running on the NFS server by entering the following commands at the client shell prompt :
:
/usr/bin/rpcinfo -u server_name mount
SHIVAKANT Page 8 9/24/2010
/usr/bin/rpcinfo -u server_name portmap
/usr/bin/rpcinfo -u server_name nfs
If the daemons are running at the server, the following responses are returned:
program 100005 version 1 ready and waiting
program 100000 version 2 ready and waiting
program 100003 version 2 ready and waiting
The program numbers correspond to the commands, respectively, as shown in the previous example. If a similar response is not returned, log in to the server at the server
console and check the status of the daemons
lssrc –g nfs
Verify that the /etc/exports file on the server lists the name of the file system that the client wants to mount and that the file system is exported. Do this by entering the command:
showmount -e server_name
This command lists all the file systems currently exported by the
server_name.
TROUBLESHOOTING NFS MOUNT ERROR
Check that the directory which is being exported , its child directory is not already exported ( a parent directory cannot be exported if the child is already exported)
Check that both the server and client can ping and can do reverse lookup if DNS is already configured
Run commands
Nslookup client name
Dig client name
These two commands will give you pretty good results
If reverse lookup is not successful add the client host in /etc/hosts file of nfs server and add server host to /etc/hosts file of clients
Echo "ipaddress hostname" >> /etc/hosts
This should solve the nfs mount errors
Posted by Shivakant Tiwari at 7:21 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX NFS TROUBLESHOOTING, AIX PRINTER TROUBLESHOOTING, AIX TROUBLESHOOTING, STEP BY STEP TROUBLESHOOTING OF PRINTER IN AIX
Newer Posts Older Posts Home
MONDAY, MAY 16, 2011
MOVING A LOGICAL VOLUME FROM ONE VOLUME GROUP TO ANOTHER
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
TO MOVE A LOGICAL VOLUME FROM A VOLUME GROUP TO ANOTHER VOLUME GROUP
ACTUALLY MOVING A LOGICAL VOLUME IS A PROCESS TO COPY VOLUME TO ANOTHER VOLUME GROUP AND THEN REMOVE IT FROM THE SOURCE LOCATION
1. CREATE A LOGICAL VOLUME
# mklv -t jfs2 rootvg 1
fslv15
2)CREATE A FILE SYSTEM ON THAT LOGICAL VOLUME
# crfs -v jfs2 -d /dev/fslv15 -m /abc
File system created successfully.
130864 kilobytes total disk space.
New File System size is 262144
3)USE CPLV COMMAND TO MOVE THE LOGICAL VOLUME FROM OLD VG TO NEW VG
# cplv -v vijayvg fslv15
cplv: Logical volume fslv15 successfully copied to fslv16 .
4) VERIFY THE MOVEMENT IN NEW VG
# lsvg -l vijayvg
vijayvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
loglv00 jfs2log 1 1 1 open/syncd N/A
fslv00 jfs2 120 120 1 open/syncd /wpar-file
fslv05 jfs2 48 48 1 open/syncd /tsmsoftwares
loglv01 jfslog 1 1 1 closed/syncd N/A
fslv16 jfs2 1 1 1 closed/syncd N/A
fslv02 jfs2 20 20 1 open/syncd /opt/tivoli
fslv06 jfs2 32 32 1 open/syncd /tsm01
fslv11 jfs2 40 40 1 open/syncd /nimfs
#
IF THE VOLUME COPIED ABOVE ALREADY EXISTS IN THE DESTINATION VOLUME GROUP THEN IT WILL RENAME THE VOLUME GROUP TO THE NEXT AVAILABLE NAME
5)NOW REMOVE LOGICAL VOLUME FROM THE SOURCE
# lsvg -l rootvg |grep fslv15
fslv15 jfs2 1 1 1 open/syncd /abc
# umount /abc
# rmlv fslv15
Warning, all data contained on logical volume fslv15 will be destroyed.
rmlv: Do you wish to continue? y(es) n(o)? y
rmlv: Logical volume fslv15 is removed.
Posted by Shivakant Tiwari at 9:08 AM 3 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADVANCE COMMANDS, move a logical volume to another volume group
Thursday, April 21, 2011AIX ADVANCE COMMANDS
USING REPLACEPV COMMAND
INITIALLY ROOTVG HAD ONE DISK
hdisk0
WE REPLACED hdisk0 with hdisk1
# replacepv hdisk0 hdisk1
0516-1011 replacepv: Logical volume hd5 is labeled as a boot logical volume.
0516-1232 replacepv:
NOTE: If this program is terminated before the completion due to
a system crash or ctrl-C, and you want to continue afterwards
execute the following command
replacepv -R /tmp/replacepv344288
0516-1011 replacepv: Logical volume hd5 is labeled as a boot logical volume.
0516-1734 replacepv: Warning, savebase failed. Please manually run 'savebase' before rebooting.
0516-1734 replacepv: Warning, savebase failed. Please manually run 'savebase' before rebooting.
#
# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk1 active 546 202 37..00..00..99..66
#
USING alt_disk_install
# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk1 active 546 202 37..00..00..99..66
# alt_disk_copy -d hdisk0
Calling mkszfile to create new /image.data file.
0301-168 bosboot: The current boot logical volume, /dev/hd5,
does not exist on /dev/hdisk0.
Checking disk sizes.
Creating cloned rootvg volume group and associated logical volumes.
Creating logical volume alt_hd5
Creating logical volume alt_hd6
Creating logical volume alt_hd8
Creating logical volume alt_hd4
Creating logical volume alt_hd2
Creating logical volume alt_hd9var
Creating logical volume alt_hd3
Creating logical volume alt_hd1
Creating logical volume alt_hd10opt
Creating logical volume alt_fwdump
Creating logical volume alt_fslv00
Creating logical volume alt_fslv03
Creating logical volume alt_pagelv00
Creating logical volume alt_paging00
Creating /alt_inst/ file system.
Creating /alt_inst/export/spot file system.
Creating /alt_inst/home file system.
Creating /alt_inst/opt file system.
Creating /alt_inst/tmp file system.
Creating /alt_inst/usr file system.
Creating /alt_inst/var file system.
Creating /alt_inst/var/adm/ras/platform file system.
Generating a list of files
for backup and restore into the alternate file system...
Backing-up the rootvg files and restoring them to the
alternate file system...
Modifying ODM on cloned disk.
Building boot image on cloned disk.
forced unmount of /alt_inst/var/adm/ras/platform
forced unmount of /alt_inst/var
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/home
forced unmount of /alt_inst/export/spot
forced unmount of /alt_inst
forced unmount of /alt_inst
Changing logical volume names in volume group descriptor area.
Fixing LV control blocks...
Fixing file system superblocks...
Bootlist is set to the boot disk: hdisk0
alt_disk_copy: 0505-218 ATTENTION: /usr/sbin/savebase returned an unexpected result.
alt_disk_copy: 0505-218 ATTENTION: /usr/sbin/savebase returned an unexpected result.
# bosboot -ad /dev/hdisk1
bosboot: Boot image is 30420 512 byte blocks.
# bootlist -m normal -o
hdisk0 blv=hd5
# bootlist -m normal hdisk1
#
#
CREATING MKSYSB OF THE ACTIVE ROOTVG AND USING alt_disk_mksysb TO COPY ON ANOTHER DISK
df -g
/dev/hd4 5.88 5.23 11% 4625 1% /
/dev/hd2 6.38 5.26 18% 31963 3% /usr
/dev/hd9var 0.25 0.23 10% 410 1% /var
/dev/hd3 8.12 8.11 1% 142 1% /tmp
/dev/fwdump 0.12 0.12 1% 4 1% /var/adm/ras/platform
/dev/hd1 0.12 0.12 1% 23 1% /home
/proc - - - - - /proc
/dev/hd10opt 0.12 0.08 39% 969 6% /opt
/dev/fslv00 0.38 0.03 91% 13142 60% /export/spot
#
CREATING LIST OF DIRECTORIES TO EXCLUDE
#
# echo "/export/spot/" > /etc/exclude.rootvg
# echo "/tmp/" >> /etc/exclude.rootvg
ADJUSTING/CHANGING FILE SYSTEM SIZE
chfs -a size=1G /
Filesystem size changed to 2097152
# chfs -a size=2G /usr
Filesystem size changed to 4194304
# df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 1.00 0.36 65% 4626 6% /
/dev/hd2 2.00 0.89 56% 31963 14% /usr
/dev/hd9var 0.25 0.23 10% 410 1% /var
/dev/hd3 8.12 8.11 1% 144 1% /tmp
/dev/fwdump 0.12 0.12 1% 4 1% /var/adm/ras/platform
/dev/hd1 0.12 0.12 1% 23 1% /home
/proc - - - - - /proc
/dev/hd10opt 0.12 0.08 39% 969 6% /opt
/dev/fslv00 0.38 0.03 91% 13142 60% /export/spot
# chfs -a size=+4G /tmp
0516-1734 extendlv: Warning, savebase failed. Please manually run 'savebase' before rebooting.
Filesystem size changed to 25427968
FIRING MKSYSB BACKUP IN A FILE
# mksysb -e -i /tmp/galaxy.mksysb
0301-168 bosboot: The current boot logical volume, /dev/hd5,
does not exist on /dev/hdisk0.
Creating information file (/image.data) for rootvg.
Creating list of files to back up.
Backing up 36681 files...................
36681 of 36681 files (100%)
0512-038 mksysb: Backup Completed Successfully.
#
OOPS WE RECEIVED THE ERROR DUE TO PREVIOUS EXERCISE
WHEN WE TRIED TO RESTOTE USING alt_disk_mksysb
# alt_disk_mksysb -m /tmp/galaxy.mksysb -d hdisk0
0505-126 alt_disk_install: target disk hdisk0 has a volume group assigned to it.
HOW TO RECTIFY THIS ERROR
# alt_disk_install -X
+-----------------------------------------------------------------------------+
ATTENTION: calling new module /usr/sbin/alt_rootvg_op. Please see the alt_rootvg_op man page
and documentation for more details.
Executing command: {/usr/sbin/alt_rootvg_op -X }
+-----------------------------------------------------------------------------+
Bootlist is set to the boot disk: hdisk1
FIRING THE RESTORATION ONCE AGAIN USING THE SAME MKSYSB IMAGE WE CREATED BEFORE
# alt_disk_mksysb -m /tmp/galaxy.mksysb -d hdisk0
Restoring /image.data from mksysb image.
Checking disk sizes.
Creating cloned rootvg volume group and associated logical volumes.
Creating logical volume alt_hd5
Creating logical volume alt_hd6
Creating logical volume alt_hd8
Creating logical volume alt_hd4
Creating logical volume alt_hd2
Creating logical volume alt_hd9var
Creating logical volume alt_hd3
Creating logical volume alt_hd1
Creating logical volume alt_hd10opt
Creating logical volume alt_fslv00
Creating logical volume alt_fslv03
Creating logical volume alt_pagelv00
Creating logical volume alt_paging00
Creating /alt_inst/ file system.
Creating /alt_inst/export/spot file system.
Creating /alt_inst/home file system.
Creating /alt_inst/opt file system.
Creating /alt_inst/tmp file system.
Creating /alt_inst/usr file system.
Creating /alt_inst/var file system.
Restoring mksysb image to alternate disk(s).
Linking to 64bit kernel.
Changing logical volume names in volume group descriptor area.
Fixing LV control blocks...
forced unmount of /alt_inst/var
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/home
forced unmount of /alt_inst/export/spot
forced unmount of /alt_inst
forced unmount of /alt_inst
Fixing file system superblocks...
Bootlist is set to the boot disk: hdisk0
#
Posted by Shivakant Tiwari at 7:25 PM 0 comments Email This
BlogThis!
Share to Twitter
Share to Facebook
Share to Google Buzz
Links to this post
Labels: /etc/exclude.rootvg, AIX ADVANCE COMMANDS, alt_disk_mksysb, CREATING MKSYSB OF THE ACTIVE ROOTVG AND USING alt_disk_mksysb, ERROR alt_disk_mksysb, USING alt_disk_install, USING REPLACEPV COMMAND
AIX AUDITING
AIX auditing can be configured using configuration files stored in /etc/securty/audit
The two files which are user to configure basic auditing are config and objects
The config files has basic configurations like which type of logging will be used and which command to use what are the users to monitor and which events are to be monitored
The object file containes the type of activity being recorded for all the events
MAJOR CHANGES IN CONFIG FILE
# cd /etc/security/audit
# cat config
start:
binmode = off
streammode = on ; STREAMING ON
stream:
cmds = /etc/security/audit/streamcmds
users:
root = general,lvm,SRC ; SELECTING THE CLASSES
#
CHANGING THE STREAMCMDS FILE
# cat streamcmds
/usr/sbin/auditstream -c SRC | auditpr -v >> /audit/stream.out & ; SELECTING ONLY SRC EVENTS HERE
ACTIVITY ON SPECIFIC FILES CAN BE RECORDED BY CHANGING IN objects FILE
# cat objects
/etc/security/environ:
w = "S_ENVIRON_WRITE"
/etc/security/group:
w = "S_GROUP_WRITE"
/etc/security/limits:
w = "S_LIMITS_WRITE"
/etc/security/login.cfg:
w = "S_LOGIN_WRITE"
STARTING AUDITING
audit on
WE CAN SEE LOGIN IN /audit/stream.out file
# cat /audit/stream.out
event login status time command
--------------- -------- ----------- ------------------------ -------------------------------
event login status time command
--------------- -------- ----------- ------------------------ -------------------------------
SRC_Stop root OK Thu Apr 21 23:11:25 2011 srcmstr
tftpd
SRC_Start root OK Thu Apr 21 23:11:29 2011 srcmstr
tftpd
SRC_Stop root OK Thu Apr 21 23:11:48 2011 srcmstr
rpc.mountd
#
Posted by Shivakant Tiwari at 5:49 PM 0 comments Email This
BlogThis!
Share to Twitter
Share to Facebook
Share to Google Buzz
Links to this post
Labels: AIX ADVANCE COMMANDS, AUDITING AIX USERS ACTIVITIES, auditpr, CONFIGURING AIX AUDITING, STREAMCMDS
Thursday, April 7, 2011AIX PERFORMANCE MONITORING WITH EXAMPLES
Displaying the top 10 CPU-consuming processes
# ps aux | head -1; ps aux | sort -rn +2 | head -10
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 8196 21.5 0.0 48 40 - A May 11 3577:57 wait
root 45078 18.7 0.0 48 40 - A May 11 3110:34 wait
tsm1 274632 0.2 2.0 33240 13616 - A May 11 31:54 db2sysc 0
root 552976 0.1 0.0 1400 1436 - A May 13 8:00 dtgreet
root 532694 0.1 0.0 72 72 - A May 12 16:07 trclogio
you 638978 0.0 0.0 288 80 pts/2 A May 14 0:00 rlogin cws
you 540676 0.0 0.0 780 820 pts/2 A May 14 0:00 -ksh
you 495768 0.0 0.0 296 88 pts/2 A May 14 0:00 rlogin cws
you 397328 0.0 0.0 780 820 pts/2 A May 14 0:00 -ksh
you 221224 0.0 0.0 776 816 pts/2 A May 14 0:00 -ksh
Displaying number of processors in the system
# lsdev -Cc processor
proc0 Available 00-00 Processor
Displaying the top 10 memory-consuming processes using SZ
# ps -ealf | head -1 ; ps -ealf | sort -rn +9 | head
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
242001 A tsm1 331940 1 0 60 20 17346400 75688 * May 11 - 6:41 /opt/tivoli/tsm/server/bin/dsmserv -u tsm1 -i /home/tsm1/tsminst1 -q
242001 A pconsole 499926 471054 0 60 20 1f34e400 70500 * May 14 - 2:15 /usr/java5/bin/java -Xmx512m -Xms20m -Xscmx10m -Xshareclasses -Dfile.
encoding=UTF-8 -Xbootclasspath/a:/pconsole/lwi/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/rcpbootcp.jar:/pconsole/lwi/lib/ISCJaasModul
e.jar:/pconsole/lwi/lib/icl.jar:/pconsole/lwi/lib/jaas2zos.jar:/pconsole/lwi/lib/jaasmodule.jar:/pconsole/lwi/lib/lwinative.jar:/pconsole/lwi/lib/lwinl1.jar:/pc
onsole/lwi/lib/lwinl2.jar:/pconsole/lwi/lib/lwinl3.jar:/pconsole/lwi/lib/lwirolemap.jar:/pconsole/lwi/lib/passutils.jar -Xverify:none -cp eclipse/launch.jar:ecl
ipse/startup.jar:/pconsole/lwi/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/launcher.jar com.ibm.lwi.LaunchLWI
40401 A tsm1 274632 356590 0 60 20 1c56d400 33240 * May 11 - 31:55 db2sysc 0
242001 A tsm1 430296 356590 0 60 20 105e1400 16476 * May 11 - 3:06 db2acd 0
240001 A root 294918 188528 0 60 20 17b26400 14068 May 11 - 7:15 /usr/sbin/dpid2
240001 A root 163928 86110 0 60 20 c17d400 10348 f1000100194d55e0 May 11 - 1:15 /usr/lpp/X11/bin/X -cc 4 -D /usr/lib/X11//rgb -T -force :0 -au
th /var/dt/A:0-LfufUa
242001 A tsm1 233690 356590 0 60 20 11b20400 6696 * May 11 - 3:55 db2fmp (C) 0
242001 A tsm1 450620 356590 0 60 20 11be0400 3408 * May 11 - 0:00 db2fmp (idle) 0
240001 A root 737438 188528 0 39 20 1df0a400 2840 * May 14 - 0:02 /usr/sbin/rsct/bin/vac8/IBM.CSMAgentRMd
240001 A root 180370 188528 0 60 20 2253400 2280 May 11 - 0:14 sendmail: accepting connections
#
Displaying the processes in order of being penalized
# ps -eakl | head -1 ; ps -eakl | sort -rn +5
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
303 A 0 57372 0 120 16 -- 1030000 68 3d2af70 - 2:20 wlmsched
303 A 0 12294 0 120 17 -- 19008000 56 - 0:14 sched
303 A 0 0 0 120 16 -- 15004000 60 - 3:25 swapper
10307 Z 0 32784 0 20 254 rt 0:00 <defunct>
240005 A 0 614566 622792 1 60 20 a0f9400 836 pts/1 0:00 ksh
200001 A 0 524388 614566 1 60 20 1f369400 920 pts/1 0:00 ps
340001 A 0 352462 188528 0 39 20 1a44b400 2124 f10008071001d640 - 0:00 rmcd
242001 A 1002 450620 356590 0 60 20 11be0400 3408 * - 0:00 db2fmp
242001 A 1002 430296 356590 0 60 20 105e1400 16476 * - 3:06 db2fmp
242001 A 1002 331940 1 0 60 20 17346400 75688 * - 6:41 dsmserv
242001 A 1002 233690 356590 0 60 20 11b20400 6696 * - 3:55 db2fmp
242001 A 8 499926 471054 0 60 20 1f34e400 70500 * - 2:15 java
240401 A 0 463082 188528 0 60 20 4b75400 348 * - 0:00 dfpd
240401 A 0 372928 1 0 60 20 7296400 100 28e4b28 - 0:00 uprintfd
240401 A 0 311494 1 0 60 20 1e34f400 1112 f10001001a54f8b0 - 1:59 db2fmcd
240401 A 0 307400 188528 0 60 20 1f3ce400 1600 * - 0:00 IBM.ServiceRMd
240401 A 0 135380 188528 0 60 20 1a04c400 680 - 0:00 nimesis
240001 A 8 635014 499926 0 60 20 e5f8400 292 f10001001563c1e8 - 0:00 pconsole_exec
240001 A 8 471054 569380 0 60 20 4435400 816 - 0:00 ksh
240001 A 1 557274 1 0 60 20 1f0ad400 2100 - 0:00 sendmail
240001 A 0 737438 188528 0 39 20 1df0a400 2840 * - 0:02 IBM.CSMAgentRMd
240001 A 0 581740 188528 0 60 20 ab18400 332 f1000200067374c8 - 0:00 tftpd
240001 A 0 569380 188528 0 60 20 13462400 816 - 0:00 ksh
240001 A 0 561364 409748 0 60 20 2877400 788 pts/2 0:00 ksh
240001 A 0 552976 434188 0 60 20 5393400 1400 - 8:01 dtgreet
240001 A 0 479486 418030 0 60 20 1818f400 788 f1000200008f1478 pts/0 0:00 ksh
240001 A 0 475280 1 0 27 20 1a72f400 1216 * - 0:30 posixtrace
240001 A 0 458982 188528 0 60 20 12b63400 408 - 0:00 timed
240001 A 0 454892 188528 0 60 20 1eb4f400 428 - 0:08 routed
240001 A 0 446576 577610 0 60 20 1c7ae400 784 pts/4 0:00 ksh
240001 A 0 393352 188528 0 60 20 b89a400 548 - 0:00 dhcpcd
240001 A 0 368828 188528 0 60 20 142e5400 316 f1000010dd008010 - 0:00 qdaemon
240001 A 0 360628 188528 0 60 20 f2be400 328 f10001001a4ae3a0 - 0:00 rpc.lockd
Displaying the processes in order of priority
# ps -eakl | sort -n +6 | head
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
303 A 0 0 0 120 16 -- 15004000 60 - 3:25 swapper
303 A 0 16392 0 0 16 -- 1b00a000 64 f100080009786c08 - 0:26 lrud
303 A 0 24588 0 0 16 -- 1f00e000 108 - 0:00 vmmd
303 A 0 28686 0 0 16 -- 1010000 52 - 0:00 memgrdd
303 A 0 57372 0 120 16 -- 1030000 68 3d2af70 - 2:20 wlmsched
303 A 0 61470 0 0 16 -- 3032000 52 - 0:00 armtrace_kproc
303 A 0 12294 0 120 17 -- 19008000 56 - 0:14 sched
40201 A 0 98416 0 0 17 20 8119000 136 * - 0:00 dog
240001 A 0 475280 1 0 27 20 1a72f400 1216 * - 0:30 posixtrace
#
Displaying the processes in order of time
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +3 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
8196 - A 3581:13 0 48 40 xx 0 0 21.5 0.0 wait
45078 - A 3113:23 0 48 40 xx 0 0 18.7 0.0 wait
532694 - A 16:07 0 72 72 32768 0 0 0.1 0.0 trclogio
552976 - A 8:01 0 1356 1436 xx 48 80 0.1 0.0 dtgreet
294918 - A 7:16 218 14052 14000 32768 27 24 0.0 2.0 /usr/sbi
168044 - A 4:32 91 544 392 xx 3 4 0.0 0.0 /usr/sbi
254082 - A 3:15 995 216 192 32768 0 0 0.0 0.0 nfsd
0 - A 3:25 7 60 48 xx 0 0 0.0 0.0 swapper
57372 - A 2:20 0 68 32 xx 0 0 0.0 0.0 wlmsched
53274 - A 2:06 0 120 96 xx 0 0 0.0 0.0 gil
Displaying the processes in order of real memory use
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +6 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
294918 - A 7:16 218 14052 14000 32768 27 24 0.0 2.0 /usr/sbi
163928 - A 1:15 1059 7132 3448 xx 3219 1128 0.0 0.0 /usr/lpp
737438 - A 0:02 264 2056 2468 xx 788 412 0.0 0.0 /usr/sbi
352462 - A 0:00 301 1584 2084 xx 542 500 0.0 0.0 /usr/sbi
180370 - A 0:14 137 1096 1596 32768 1187 1000 0.0 0.0 sendmail
307400 - A 0:00 136 1344 1520 xx 258 176 0.0 0.0 /usr/sbi
552976 - A 8:01 0 1356 1436 xx 48 80 0.1 0.0 dtgreet
475280 - A 0:30 20 1144 1208 32768 73 64 0.0 0.0 posixtra
544916 pts/1 A 0:00 0 868 972 32768 80 104 0.0 0.0 ps vx
614566 pts/1 A 0:00 1 600 876 32768 240 276 0.0 0.0 -ksh
Displaying the processes in order of I/O
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +4 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
106632 - A 0:00 2338 136 152 xx 36 36 0.0 0.0 /usr/ccs
163928 - A 1:15 1059 7132 3448 xx 3219 1128 0.0 0.0 /usr/lpp
254082 - A 3:15 995 216 192 32768 0 0 0.0 0.0 nfsd
1 - A 0:09 549 708 492 32768 30 32 0.0 0.0 /etc/ini
352462 - A 0:00 301 1584 2084 xx 542 500 0.0 0.0 /usr/sbi
217218 - A 1:37 267 1076 452 32768 151 44 0.0 0.0 /usr/sbi
737438 - A 0:02 264 2056 2468 xx 788 412 0.0 0.0 /usr/sbi
294918 - A 7:16 218 14056 14004 32768 27 24 0.0 2.0 /usr/sbi
356590 - A 0:00 209 508 152 32768 54 48 0.0 0.0 db2wdog
290960 - A 0:00 166 1572 60 32768 46 8 0.0 0.0 /usr/sbi
Displaying WLM classes
# ps -a -o pid,user,class,pcpu,pmem,args
PID USER CLASS %CPU %MEM COMMAND
32784 <defunct>
221224 you Default 0.0 0.0 -ksh
397328 you Default 0.0 0.0 -ksh
467058 root System 0.0 0.0 ksh
487458 root System 0.0 0.0 -ksh
495768 you Default 0.0 0.0 rlogin cws
520194 root System 0.0 0.0 ps -a -o pid,user,class,pcpu,pmem,args
540676 you Default 0.0 0.0 -ksh
638978 you Default 0.0 0.0 rlogin cws
659554 root System 0.0 0.0 pg
708804 root System 0.0 0.0 pg
Determining the PID of wait processes
# ps vg | head -1 ; ps vg | grep -w wait
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
8196 - A 3582:56 0 48 40 xx 0 0 21.5 0.0 wait
45078 - A 3114:52 0 48 40 xx 0 0 18.7 0.0 wait
#
Posted by Shivakant Tiwari at 6:52 PM 1 comments Email This
BlogThis!
Share to Twitter
Share to Facebook
Share to Google Buzz
Links to this post
Labels: AIX ADVANCE COMMANDS, AIX PERFORMANCE MONITORING, AIX PERFORMANCE TOOLS EXAMPLES, L1 monitoring commands in AIX, ps for aix, ps in AIX
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)
Total Pageviews
10,062 Your Ad Here
Feedjit
Your Ad Here
FRIDAY, APRIL 15, 2011
AIX PAGING SPACE
AIX PAGING SPACE
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
hd6 hdisk0 rootvg 512MB 17 yes yes lv
CREATE A NEW LV TO USE FOR PAGING SPACE
# mklv -t paging rootvg 5
pagelv00
SEE CURRENT PAGING SPACES WHICH ARE REGISTERED
#
# cat /etc/swapspaces
* /etc/swapspaces
*
* This file lists all the paging spaces that are automatically put into
* service on each system restart (the 'swapon -a' command executed from
* /etc/rc swaps on every device listed here).
*
* WARNING: Only paging space devices should be listed here.
*
* This file is modified by the chps, mkps and rmps commands and referenced
* by the lsps and swapon commands.
hd6:
dev = /dev/hd6
ENABLING A PAGING SPACE
# swapon /dev/pagelv00
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
pagelv00 hdisk0 rootvg 640MB 1 yes no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
#
DISABLING A PAGING SPACE
# swapoff /dev/pagelv00
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
pagelv00 hdisk0 rootvg 640MB 0 no no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
#
CREATING A PAGING SPACE THROUGH mkps
# mkps -a -n -s3 rootvg
paging00
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging00 hdisk0 rootvg 384MB 1 yes yes lv
pagelv00 hdisk0 rootvg 640MB 0 no no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
MKPS AUTOMATICALLY ADDS PAGING SPACE IN /etc/swapspaces
# cat /etc/swapspaces
* /etc/swapspaces
*
* This file lists all the paging spaces that are automatically put into
* service on each system restart (the 'swapon -a' command executed from
* /etc/rc swaps on every device listed here).
*
* WARNING: Only paging space devices should be listed here.
*
* This file is modified by the chps, mkps and rmps commands and referenced
* by the lsps and swapon commands.
hd6:
dev = /dev/hd6
paging00:
dev = /dev/paging00
CHANGING PAGING SPACE
INCREASING PAGING SIZE
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging00 hdisk0 rootvg 384MB 1 yes yes lv
pagelv00 hdisk0 rootvg 640MB 0 no no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
# chps -s 2 paging00
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging00 hdisk0 rootvg 640MB 1 yes yes lv
pagelv00 hdisk0 rootvg 640MB 0 no no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
#
DECREASING PAGING SPACE
# chps -d 1 paging00
shrinkps: Temporary paging space paging01 created.
shrinkps: Paging space paging00 removed.
shrinkps: Paging space paging00 recreated with new size.
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging00 hdisk0 rootvg 512MB 1 yes yes lv
pagelv00 hdisk0 rootvg 640MB 0 no no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
#
Posted by Shivakant Tiwari at 5:52 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX AIX PAGING SPACE, AIX commands, AIX ENABLING A PAGING SPACE, AIX INCREASING PAGING SIZE, AIX PAGING SPACE, CREATING A PAGING SPACE THROUGH mkps
AIX SYSTEM DUMP
VIEWING A DUMP DEVICE
# sysdumpdev -l
primary /dev/hd6
secondary /dev/sysdumpnull
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump FALSE
dump compression ON
CREATING A SECONDARY DUMP DEVICE
# mklv -t jfs2 rootvg 2
fslv03
# sysdumpdev -s /dev/fslv03
primary /dev/hd6
secondary /dev/fslv03
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump FALSE
dump compression ON
SCANNING A DUMP DEVICE
# sysdumpdev -L -S /dev/hd6
0453-019 No previous dumps recorded.
Scanning device /dev/hd6 for existing dump.
A valid dump was not detected in the dump devices.
Scanning device /dev/fslv03 for existing dump.
A valid dump was not detected in the dump devices.
#
ESTIMATING A DUMP SIZE
# sysdumpdev -e
0453-041 Estimated dump size in bytes: 138621747
#
EXTENDING A DUMP DEVICE
# extendlv fslv03 1
# sysdumpdev -l
primary /dev/hd6
secondary /dev/fslv03
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump FALSE
dump compression ON
#
#
Posted by Shivakant Tiwari at 5:32 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX commands, AIX SYSTEM DUMP, DUMP SIZE TOO SMALL, EXTENDING A DUMP DEVICE, SCANNING A DUMP DEVICE
TUESDAY, MARCH 1, 2011
AIX commands
VG COMMANDS
lsvg Display all VGs
lsvg -o Display all active VGs
lsvg rootvg Display info about rootvg
lsvg -l rootvg Display info about all LVs in rootvg
lsvg -o |lsvg -il Display info about all LVs in all VGs
lsvg -p rootvg Display info about all PVs in rootvg
mkvg -s 8 hdisk1 Create VG with name vgxx on hdisk1 with partition size 8MB
mkvg -s 8 -y sivg hdisk1 Create VG with name sivg on hdisk1 with partition size 8MB
mkvg -s 4 -t 2 -y sivg hdisk1 Create sivg on hdisk1 with PP size 4 and no of partions 2 * 1016
chvg -a y newvg To cuase VG newvg automatically activated at startup
chvg -a n newvg To deactivate the automatic activation at startup
chvg -t 2 newvg To change maximum no. of PP to 2032 on vg newvg
chvg -Q n newvg To disable quorum on VG newvg
reorgvg newvg Reorganises PP allocation of VG newvg
extendvg newvg hdisk3 hdisk4 Add PV hdisk3 and hdisk4 to VG newvg
exportvg newvg Exports the VG newvg
importvg -V 44 -y newvg hdisk2 Import the hdisk2 with name newvg, and assign major number 44
redcucevg newvg hdisk3 Remove PV hdisk3 from VG newvg
varyoffvg newvg To deactviate VG newvg
varyonvg newvg To activate VG newvg
syncvg -v sivg To sync the mirrored LV in the VG sivg
mirrorvg -S -m sivg hdisk2 To mirror LVs of sivg with hdisk2 (-m for exact mirror, -S
forbackground mirror)
unmirrorvg sivg hdisk2 To remove the mirrored PV from the set.
FS COMMANDS
lsfs Lists all filesystems in the /etc/filesystems entry
lsfs -q List all filesystems with detailed info
lsfs -a To list all filesystems (default)
lsfs -l Specify the output in list format
lsfs -c Specify the output in column format
lsfs -v jfs Lists all jfs filesystems
chfs -a size=24576 /si Change size of FS /si to 24576 x 512 bytes blocks (12 MB)
chfs -a size=+24576 /si Add 24576 x 512 byte blocks to FS /si
chfs -m /si /bi Change the mount point from /si to /bi
chfs -A /si To auto mount the filesystem si
chfs -d account /si Remove account attribute of /si. ( from /etc/filesystems file)
chfs -a splitcopy=/backup -a copy=2 /oracle This will mount the 2nd copy of mirrored filesystem oracle to
/backup in read-only mode
crfs -v jfs -g testvg -a size=64465 -m /SHIVA Creates FS /SHIVA of type jfs in VG testvg of blocksize 64465
crfs -v jfs -d /dev/lv00 -m /SHIVA Create FS /SHIVA of type jfs on device /dev/lv00
rmfs /SHIVA Deletes FS /SHIVA and associated LV
rmfs -r /SHIVA Deletes FS /SHIVA its mount point and associated LV
defragfs /sifs To defragment the file system /sifs
defragfs -q /sifs Display the current defrag status of the file system
fsck -y n /dev/lv00 To fsck the filesystem associated to /dev/lv00 assuming response "yes"
fsck -p /dev/lv00 To restore superblock from backup superblock
PV COMMANDS
lspv hdisk0 Display status and characteristics of the PV
lspv -p hdisk0 Display PP usage of hdisk0
lspv -l hdisk0 To list all logical volumes on PV hdisk0
chpv -v r hdisk1 Close the PV (Used while removing PV without varyon)
chpv -v a hdisk1 Open the PV
chpv -c hdisk0 Clear the master boot record on PV hdisk0
migratepv hdisk1 hdisk2 To move PPs from PV hdisk1 to hdisk2
migratepv -l silv hdisk1 hdisk2 To migrate LV silv from PV hdisk1 to hdisk2
LV COMMANDS
lslv -l lv00 Display info about LV by PV
lslv -p hdisk1 Display LV allocation map for hdisk1
chlv -t copy lv00 To change the lv00 to copy type
chlv -p r lv00 To change the lv00 to readonly mode
rmlv silv To remove silv
rmlv -f silv To remove silv without user intervention
mklv -s n -c 3 silv hdisk1 To make LV silv with three copies on hdisk1
extendlv silv 5 To extend the LV silv with 5 LPs
mklvcopy -s n lvsi 2 hdisk1 To mirror LV lvsi on same PV with 2 copies
mklvcopy lvsi 3 hdisk1 hdisk2 To mirror LV lvsi on PV hdisk1 and hdisk2 with 3 copies
rmlvcopy lvsi 2 hdisk1 Will remove one copy of LV lsvi from hdisk1
mklv -t jfslog -y log00 newvg 2 To create a jfslog with name log00 on VG newvg with 2LPs
logform /dev/log00 To format jfslog volume log00
BLV COMMANDS
bootlist -m normal -o To see the boot sequence in normal mode
bootlist -m service -o To see the boot sequence in service mode
bootlist -m normal cd0 hdisk0 To change boot sequence to cd0,hdisk0 in normal mode
bootlist -m service cd0 rmt0 hdisk0 To change boot sequence to cd0,rmt0,hdisk0 in service mode
bosboot -ad /dev/hdisk1 To create boot image on PV hdisk1
mkboot -cd /dev/hdisk1 To clear the boot image
bootinfo -b Specifies the bootable disk
bootinfo - t Specifies the type of boot
bootinfo -e Check the machine can boot from tape
bootinfo -T To see the machine type
bootinfo -s hdisk0 To see the size of hdisk0
bootinfo -r To see the size of memory
PAGE SPACE COMMANDS
lsps -a To list out all paging spaces
lsps hd6 To display the details of the paging space hd6
chps -a y paging00 To turn on the paging space paging00
chps -a n paging00 To turn off the paging space paging00
chps -s4 paging00 To increase the size of the paging space in 4 LP blocks
mkps -a -n -s4 sivg To create a paging space on VG sivg of 4 LP size (-s4) and activate it
immediately (-n) and activate it at every restarts
rmps paging00 To remove the paging space paging00
swapon -a To invoke all entries in /etc/swapspaces file
swapon /dev/paging00 To make available swap space paging00
SYSTEM DUMP COMMANDS
sysdumpdev -l To list the current dump destination
sysdumpdev -L List the details of the previous dump
sysdumpstart -p Starts dump in the primary dump device
sysdumpstart -s Starts dump in the secondary dump device
sysdumpdev -p /dev/lv00 To make lv00 as primary dump device
sysdumpdev -P -p /dev/lv00 To make lv00 as primary dump device permanently
sysdumpdev -s /dev/rmt0 To make rmt0 as secondary dump device
sysdumpdev -z To determine a new system dump occurred
Device related commands
cfgmgr To configure devices and installs device software in system
cfgmgr -l vscsi0 To configure the components connected to the vscsi0 interface
lscfg To display config, diagnostics and vital product definition info
lscfg -l mem0 Display info about device mem0
lscfg -l ent* Display info about all Ethernet cards
lscfg -v Display vpd
lscfg -v -l hdisk0 Display vpd of hdisk0
mkdev -l rmt0 To change device rmt0 from defined state to available state
lsdev -P To lists all supported devices
lsdev -P -c disk To list all supported disks
lsdev -P -r class To display supported class
lsdev -P -r subclass To display all sub class
lsdev -C To lists all configured devices
lsdev -C -l mem0 To display the properties of mem0
chdev -l sys0 -a maxproc=100 To change default maxproc value to 100
chdev -l rmt0 -a blocksize=512 To change the block size to 512
chdev -l rmt0 -a ret=no To avoid tape retension
rmdev -l rmt0 To remove the device rmt0
rmdev -d -l rmt0 To remove the device totally from database
rmdev -l rmt0 -S To change the state of the device stopped
lsparent -C -k rs232 To display possible parent devices which accept rs232 devices
lsparent -C -l hdisk0 To display parent devices which accept child device hdisk0
lsattr -Dl rmt0 To see the default values of the device rmt0
lsattr -El rmt0 To see the current values of the device rmt0
lsattr -El tty0 -a login -R To see all possible values of the login attribute of tty0
lsconn -p scsi0 To list all possible connection scsi0 can accept
lvlstmajor To list the available major numbers
mknod /dev/null c 2 2 Create null device with major (2) and minor (2) nos. (c - char device)
Console emulation commands
lscons To list the current console
lscons -b To list the console at next boot
chcons /dev/tty3 To change the console to tty3
chcons -a login=enable /dev/tty3 Redirect console to tty3 and provide login prompt
swcons /dev/tty3 To change system console to tty3 temporarily
Installation specific commands
lslpp -l To see the details of installed file sets
lslpp -ha bos.net.* To list the installation history of all file set in bos.net packages
lslpp -f bos.rte To list the files in the bos.rte package
lslpp -w /etc/hosts To list the file set which contain /etc/hosts file
lslpp -p bos.net.nfs.server To list the pre requisites for bos.net.nfs.server file set
installp -L -d /dev/rmt0.1 To list the installable products on the device rmt0
installp -aX -d /dev/rmt0.1 bos.net To install all filesets within bos.net and expands file system if it requires
installp -u bos.net To remove bos.net
installp -r To reject the applied software
installp -c -f <product> To commit the <product>
installp -C To cleanup an incomplete installation
lppchk -c <product> To check the <product>
instfix -k IX9999 -d /dev/rmt0.1 To install the file set associated with fix IX9999 from rmt0
instfix -ik IX9999 To verify fix IX9999 installed
Network related commands
host 193.9.200.1 Resolves ip to host name (from /etc/hosts file)
host ibm Resolve ibm to ip address (from /etc/hosts file)
hostname ibm To change the host name to ibm
entstat en0 To the status of ethernet device en0
entstat -d en0 To list the detailed status of device en0
no -a To list all net configurable attributes and their values
no -d thewall To change thewall parameter to its default value
no -o ipforwarding=1 To make the machine as router in tcpip networks
traceroute ibm To trace the route to ibm
ping ibm To tcp ping to the machine ibm
ifconfig -a To show the status of all network interfaces
ifconfig en0 To show the status of en0
ifconfig en0 up Turns on network card en0
ifconfig en0 down Turns off network card en0
ifconfig en0 detach Removes en0 card from the network interface list
ifconfig en0 inet 194.35.52.1 netmask 255.255.255.0 up
Configure en0 starts immediately
ifconfig en0 alias 195.60.60.1 Create alias ip address for en0
route add 0 192.100.13.7 To make 192.100.13.7 as default gateway for entire network
route add 192.100.12.0 192.100.13.7 To make 13.7 as gateway for 12.0 network
route -f To clear the gateway table
chdev -l inet0 -a hostname=si To change the host name to si permanently
netstat -a To show the state of all sockets
netstat -c To show the network buffers cache
netstat -D To show the net drops of packets
netstat -i To display interface statistics
netstat -r To show the routing table
netstat -rn To show routing table (ip will be given instead of host names)
netstat -s To show the statistics of the protocols
netstat -s -p < tcp/udp/ipv6> To show the statistics of respective protocols
Space usage commands
du -k To list number of bytes in 1k blocks
du -l To list number of bytes in 512 bytes blocks
du -s To list only the total disk usage in the current directory
df -i To display no of free and used inodes
df -k To display diskspace in 1024 bytes format
Backup commands
mksysb -i -X /dev/rmt0 Creates image.data and system backup (-X expands /tmp if required)
mksysb -m /dev/rmt0 Creates image.data file with map file and system backup
mksysb -e /dev/rmt0 Creates system data but excludes the files listed in /etc/exclude.rootvg
mkszfile Creates /image.data file
mkcd -d /dev/cd1 Creates system boot backup to the CD-R device /dev/cd1
mkcd -d /dev/cd1 -v vg00 Creates backup of vg vg00 to CD-R device /dev/cd1
mkcd -d /dev/cd1 -G Creates generic boot backup
savevg -i -f /dev/rmt0 vg00 Creates vg00.data image file and backup vg vg00
savevg -ef /dev/rmt0 vg00 Creates vg00 backup but excludes files listed in the /etc/exclude.vg00
find / -print | backup -ivf /dev/rmt0 Backup entire system to rmt0
backup -0vf /dev/rmt0 /home Backup /home directory to rmt0 with backup level 0
restore -Tvf /dev/rmt0 List the archive in rmt0
restore -xvf /dev/rmt0 /home Restore /home from archive in device rmt0
find ./home -print |cpio -ocvumB > /dev/rmt0
Archives /home directory
cpio -icvdumB < /dev/rmt0 Restores cpio archive from rmt0
cpio -ivt < /dev/rmt0 List the contents of cpio archive from rmt0
cpio -icvd < /dev/rmt0 /home Restores /home directory from rmt0
tar -cvf /dev/rmt0 /home Archives /home to rmt0 device
tar -tvf /dev/rmt0 List the archives in rmt0
tar -xvf /dev/rmt0 /home Extract /home from rmt0
dd if=si of=si1 conv=ebcdic Convert and copy ascii file si to ebcdic si1
dd if=/dev/rmt0 ibs=512 obs=1024 of=/dev/rmt1
To copy blocks from rmt0 with 512 blocks to rmt1 with 1024 blocks
tctl -f /dev/rmt0 rewind To rewind the tape
tctl -f /dev/rmt0 offline To eject the tape
tctl -f /dev/rmt0 status To show the status of tape
chdev -l rmt0 -a block_size=512 To change the block size of the tape to 512
Print commands
qchk -q To display the default q
qchk -P lp0 To display the status of the printer lp0
qchk -# 123 To display the status of job number 123
qchk -A To display the status of all queues
qcan -x 123 To cancel the print job 123
qcan -X -P lp0 To cancel all jobs submitted to lp0
qpri -#570 -a 25 To change the priority of the job to 25
qhld # 569 To hold the job 569
qhld -r -#569 To remove holding from 569
qmov -m lpa -#11 To move the job 11 to queue lpa
enable psq To enable queue psq
disable psq To disable queue psq
cancel -#111 To cancel job 111
lpstat To display the status all queues
lpstat -p lp0 To display the status of print queue lp0
lpstat -u root To display the jobs submitted by user root
lpq -P lp0 To display the status of queue lp0
last To list all the records in the /var/adm/wtmp file
last |grep shutdown To show the shutdown sessions
uptime (w -u ) To show how long the system has been up
Licensing commands
oslevel To list the operating system level
lslicense To see the number of license
chlicense -u30 To change the fixed user license to 30
chlicense -f on To enable floating user license
User commands
id To list all system identifications for current user
id -gn To list the default group for current user
id -Gn To list all system groups for current user
lsuser root To list the attribute of user root
lsuser ALL To list the attributes of all users
lsuser -a HOME ALL To list the home directory of all users
lsuser -a ALL To list all usernames
lsuser -a auth1 auth2 ALL To list the authentication method for all users
lsuser -a expires ALL To list expiry date
lsuser -a account_locked ALL To check account lock status of all users
chuser -a login=true san To enable the user san
chuser -a rlogin=true san Enable san to login remotely
mkuser si Creates user si with default values in /usr/lib/security/mkuser.defalault
mkuser su=false si Create user si without su facility
rmuser si To remove user si
rmuser -p si To remove user si and his all attributes
who List users with tty nos and ip numbers
who /var/adm/wtmp Lists history of login logout system startup and shutdowns
who -r To list the run level
who am i /who -m To list the current user
mkgroup dcm To create the group dcm
chgroup users=u1,u2,u3 dcm To add users u1 u2 and u3 to dcm group
rmgroup dcm To delete the group dcm
chauthent To change the authentication methods
Subsystem Commands
lssrc -a To list the status of all subsystems
lssrc -h node1 -a To list the status of all subsystems on foreign host node1
lssrc -s kadmind To list the status of the subsystem kadmind
lssrc -g tcpip To get the status of the subsystem group tcpip
mkssys To add a subsystem
rmssys -s kerberos To remove the subsystem kerberos
chssys -s kerb -s kad To rename the subsystem kerb to kad
startsrc -s kadmin To start the subsystem kadmin
startsrc -g tcpip To start the subsystem group tcpip
stopsrc -s kadmin To stop the subsystem kadmin
stopsrc -g tcpip To stop the subsystem group tcpip
refresh -s nfsd To refresh nfsd subsystem
refresh -g tcpip To refresh tcpip subsystem group
Scheduling commands
crontab -l To list the crontab entries
crontab -e To edit the crontab entries
crontab -l > /si To copies the entries of crontab to /si file
crontab -r To remove all crontab entries
crontab -v To list the submission time
/var/adm/cron/cron.allow File containing users who allowed cron service
/var/adm/cron/cron.deny File containing users denied cron service
at -l To list the jobs scheduled via at command
at -r root.dfjdhjdh.21 To remove the scheduled job root.dfjdhjdh.21
/var/adm/cron/at.allow File containing users who allowed at service
/var/adm/cron/at.deny File containing users denied at service
batch To run the command when the system load permits
atq joe To list all the jobs submitted by user joe
ODM Commands
odmget sm_menu_opt
To get the objects from class sm_menu_opt
odmget -q "id=licenses" sm_menu_opt
To list objects that matches query id=licenses from object sm_menu_opt
odmdelete -o sm_menu_opt -q "id=licenses"
To delete the entries from class sm_menu_opt which agrees the query id=licenses
odmshow sm_menu_opt
To show the object class definition
odmdrop -o sm_menu_opt
To drop sm_menu_opt object class
odmchange -o sm_menu_opt -q "id=licenses" file1
To change the attributes from file1
errpt To display complete summary of report
errpt -a To list complete detailed report
errpt -d H To list all hardware related errors
errpt -d S To list all software related errors
errpt -a -j 34564423 To list detailed error report of error id 34564423
chitab tty002:23:respawn:/usr/sbin/getty /dev/tty
To enter the entry tty002:23:respawn:/usr/sbin/getty /dev/tty in inittab
lssrc -g portmap To start tcpip
HACMP Commands
logs
/tmp/hacmp.out Detailed event script output logged in 7 day rolling history
/var/adm/cluster.log High level view of cluster events (No clean up on this file)
/usr/sbin/cluster/history/cluster.mmdd Day by day view of cluster events. (one file / day of month)
/tmp/cm.log Clstrmgr messages
/tmp/cspoc.log Output from C-SPOC commands (similar to smit.log)
/tmp/emuhacmp.out Output from event emulation
rdist -b -f /etc/disfile1 To distribute the files in disfile1 to all nodes in disfile1 in binary mode
Sample entry for disfile1
HOSTS = ( root@node1 root@node3 )
FILES = ( /etc/passwd /etc/security/passwd)
${FILES} -> ${HOSTS}
clstart -m -s -b -i -l To start cluster daemons (m-clstrmgr, s-clsmuxpd,
b-broadcast message, -i-clinfo, -l cllockd)
clstop -f -N To force shutdown cluster immediately without releasing resources
clstop -g -N To do graceful shutdown immediately with no takeover
clstop -gr -N To do graceful shutdown immediately with takeover
cldare -t To sync the cluster toplogy
cldare -t -f To do the mock sync of topology
cldare -r To sync the cluster resources
cldare -r -f To do the mock sync of resources
clverify cluster verification utility
cllscf To list clustur topology information
cllsclstr To list the name and security level of the cluster
cllsnode To list the info about the cluster nodes
cllsnode -i node1 To list info about node1
cllsdisk -g shrg To list the PVID of the shared hard disk for resource group shrg
cllsnw To list all cluster networks
cllsnw -n ether1 To list the details of network ether1
cllsif To list the details by network adapter
cllsif -n node1_service To list the details of network adapter node1_service
cllsvg To list the shared vgs which can be accessed by all nodes
cllsvg -g sh1 To list the shared vgs in resource group sh1
cllslv To list the shared lvs
cllslv -g sh1 To list the shared lvs in the resource group sh1
cllsdisk -g sh1 To list the PVID of disks in the resource group sh1
cllsfs To list the shared file systems
cllsfs -g sh1 To list the shared file systems in the resource group sh1
cllsnim Show info about all network modules
cllsnim -n ether Show info about ether network module
cllsparam -n node1 To list the runtime parameters for the node node1
cllsserv To list all the application servers
claddclstr -i 3 -n dcm To add a cluster definition with name dcm and id 3
claddnode To add an adapter
claddnim To add network interface module
claddgrp -g sh1 -r cascading -n n1 n2 To create resource group sh1 with nodes n1,n2 in cascade
claddserv -s ser1 -b /usr/start -e /usr/stop Creates an application server ser1 with startscript as /usr/start
and stop script as /usr/stop
clchclstr -i 2 -n dcmds To change cluster definitions name to dcmds and id to 2
clchclstr -s enhanced To change the clustur security to enhanced
clchnode To change the adapter parameters
clchgrp To change the resource group name or node relationship
clchparam To change the run time parameters (like verbose logging)
clchserv To change the name of app. server or change the start/end scripts
clrmclstr To remove the cluster definition
clrmgrp -g sh1 To delete the resource group sh1 and related resources
clrmnim ether To remove the network interface module ether
clrmnode -n node1 To remove the node node1
clrmnode -a node1_svc To remove the adapter named node1_svc
clrmres -g sh1 To remove all resources from resource group sh1
clrmserv app1 To remove the application server app1
clrmserv ALL To remove all applicaion servers
clgetactivenodes -n node1 To list the nodes with active cluster manager processes from cluster
manager on node node1
clgetaddr node1 returns a pingable address from node node1
clgetgrp -g sh1 To list the info about resource group sh1
clgetgrp -g sh1 -f nodes To list the participating nodes in the resource group sh1
clgetif To list interface name/interface device name/netmask associated with
a specified ip label / ip address of a specific node
clgetip sh1 To get the ip label associated to the resource group
clgetnet 193.9.200.2 255.255.255.0 To list the network for ip 193.9.200.2, netmask 255.255.255.0
clgetvg -l nodelv To list the VG of LV nodelv
cllistlogs To list the logs
clnodename -a node5 To add node5 to the cluster
clnodename -o node5 -n node3 To change the cluster node name node5 to node3
clshowres Lists resources defined for all resource group
clfindres To find the resource group within a cluster
xclconfig X utility for cluster configuration
xhacmpm X utility for hacmp management
xclstat X utility for cluster status
NIM Commands
nimconfig -a pif_name=en0 -a netname=net1
To initialise the NIM master with network name net1
nimconfig -r To rebuild /etc/niminfo file which contains the variables for NIM
nim -o define -t lpp_source -a source=/dev/cd0 -a server=master -a location=/export/lpp_source/lpp_source1 lpp_source1
To define lpp_source1 image in /export/lpp_source/lpp_source directory from source cd0
nim -o define -t mksysb -a server=master -a location=/resources/mksysb.image mksysb1
To define mksysb resource mksysb1, from source /resources/mksysb.image on master
nim -o remove inst_resource To remove the resource inst_resource
nim -o check lpp_source1 To check the status of lpp_source lpp_source1
nim -o allocate -a spot=spot1 -a lpp_source=lpp_source1 node1 To allocate the resources spot1 and lpp_source1 to the the client node1
nim -o bos_inst node1 To initialise NIM for the BOS installation on node1 with the allocated resources
nim -o dkls_init dcmds To initialize the machine dcmds as diskless operation
nim -o dtls_init dcmds To initialize the machine dcmds for dataless operation
nim -o cust dcmds To initialize the machine dcmds for customize operation
nim -o diag dcmds To initialize the machine dcmds for diag operation
nim -o maint dcmds To initialize the machine dcmds for maintenance operation
nim -o define -t standalone -a platform=rspc -a if1="net1 dcmds xxxxx" -a cable_type1=bnc dcmds
To define the machine dcmds as standalone with platform as rspc and network as net1 with cable
type bnc and mac address xxxxx
nim -o unconfig master To unconfigure nim master master
nim -o allocate -a spot=spot1 dcmds
To allocate the resource spot1 from machine dcmds
nim -o deallocate -a spot=spot1 dcmds
To de allocate the resource spot1 from machine dcmds
nim -o remove dcmds To re move machine dcmds after removing all resources associated to it
nim -o reboot dcmds To reboot ther client dcmds
nim -o define -t lpp_source -a location=/software/lpp1 -a server=master -a source=/dev/cd0 lpp1
To define lppsource lpp1 on master at /software/lpp1 directory from source device /dev/cd0
lsnim To list the nim resources
lsnim -l dcmds To list the detailed info about the object dcmds
lsnim -O dcmds To list the operation dcmds object can support
lsnim -c resources dcmds To list the resources allocated to the machine dcmds
nimclient The client version of nim command (User can obtain same results of nim in server )
Thursday, April 7, 2011AIX PERFORMANCE MONITORING WITH EXAMPLES
Displaying the top 10 CPU-consuming processes
# ps aux | head -1; ps aux | sort -rn +2 | head -10
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 8196 21.5 0.0 48 40 - A May 11 3577:57 wait
root 45078 18.7 0.0 48 40 - A May 11 3110:34 wait
tsm1 274632 0.2 2.0 33240 13616 - A May 11 31:54 db2sysc 0
root 552976 0.1 0.0 1400 1436 - A May 13 8:00 dtgreet
root 532694 0.1 0.0 72 72 - A May 12 16:07 trclogio
you 638978 0.0 0.0 288 80 pts/2 A May 14 0:00 rlogin cws
you 540676 0.0 0.0 780 820 pts/2 A May 14 0:00 -ksh
you 495768 0.0 0.0 296 88 pts/2 A May 14 0:00 rlogin cws
you 397328 0.0 0.0 780 820 pts/2 A May 14 0:00 -ksh
you 221224 0.0 0.0 776 816 pts/2 A May 14 0:00 -ksh
Displaying number of processors in the system
# lsdev -Cc processor
proc0 Available 00-00 Processor
Displaying the top 10 memory-consuming processes using SZ
# ps -ealf | head -1 ; ps -ealf | sort -rn +9 | head
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
242001 A tsm1 331940 1 0 60 20 17346400 75688 * May 11 - 6:41 /opt/tivoli/tsm/server/bin/dsmserv -u tsm1 -i /home/tsm1/tsminst1 -q
242001 A pconsole 499926 471054 0 60 20 1f34e400 70500 * May 14 - 2:15 /usr/java5/bin/java -Xmx512m -Xms20m -Xscmx10m -Xshareclasses -Dfile.
encoding=UTF-8 -Xbootclasspath/a:/pconsole/lwi/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/rcpbootcp.jar:/pconsole/lwi/lib/ISCJaasModul
e.jar:/pconsole/lwi/lib/icl.jar:/pconsole/lwi/lib/jaas2zos.jar:/pconsole/lwi/lib/jaasmodule.jar:/pconsole/lwi/lib/lwinative.jar:/pconsole/lwi/lib/lwinl1.jar:/pc
onsole/lwi/lib/lwinl2.jar:/pconsole/lwi/lib/lwinl3.jar:/pconsole/lwi/lib/lwirolemap.jar:/pconsole/lwi/lib/passutils.jar -Xverify:none -cp eclipse/launch.jar:ecl
ipse/startup.jar:/pconsole/lwi/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/launcher.jar com.ibm.lwi.LaunchLWI
40401 A tsm1 274632 356590 0 60 20 1c56d400 33240 * May 11 - 31:55 db2sysc 0
242001 A tsm1 430296 356590 0 60 20 105e1400 16476 * May 11 - 3:06 db2acd 0
240001 A root 294918 188528 0 60 20 17b26400 14068 May 11 - 7:15 /usr/sbin/dpid2
240001 A root 163928 86110 0 60 20 c17d400 10348 f1000100194d55e0 May 11 - 1:15 /usr/lpp/X11/bin/X -cc 4 -D /usr/lib/X11//rgb -T -force :0 -au
th /var/dt/A:0-LfufUa
242001 A tsm1 233690 356590 0 60 20 11b20400 6696 * May 11 - 3:55 db2fmp (C) 0
242001 A tsm1 450620 356590 0 60 20 11be0400 3408 * May 11 - 0:00 db2fmp (idle) 0
240001 A root 737438 188528 0 39 20 1df0a400 2840 * May 14 - 0:02 /usr/sbin/rsct/bin/vac8/IBM.CSMAgentRMd
240001 A root 180370 188528 0 60 20 2253400 2280 May 11 - 0:14 sendmail: accepting connections
#
Displaying the processes in order of being penalized
# ps -eakl | head -1 ; ps -eakl | sort -rn +5
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
303 A 0 57372 0 120 16 -- 1030000 68 3d2af70 - 2:20 wlmsched
303 A 0 12294 0 120 17 -- 19008000 56 - 0:14 sched
303 A 0 0 0 120 16 -- 15004000 60 - 3:25 swapper
10307 Z 0 32784 0 20 254 rt 0:00 <defunct>
240005 A 0 614566 622792 1 60 20 a0f9400 836 pts/1 0:00 ksh
200001 A 0 524388 614566 1 60 20 1f369400 920 pts/1 0:00 ps
340001 A 0 352462 188528 0 39 20 1a44b400 2124 f10008071001d640 - 0:00 rmcd
242001 A 1002 450620 356590 0 60 20 11be0400 3408 * - 0:00 db2fmp
242001 A 1002 430296 356590 0 60 20 105e1400 16476 * - 3:06 db2fmp
242001 A 1002 331940 1 0 60 20 17346400 75688 * - 6:41 dsmserv
242001 A 1002 233690 356590 0 60 20 11b20400 6696 * - 3:55 db2fmp
242001 A 8 499926 471054 0 60 20 1f34e400 70500 * - 2:15 java
240401 A 0 463082 188528 0 60 20 4b75400 348 * - 0:00 dfpd
240401 A 0 372928 1 0 60 20 7296400 100 28e4b28 - 0:00 uprintfd
240401 A 0 311494 1 0 60 20 1e34f400 1112 f10001001a54f8b0 - 1:59 db2fmcd
240401 A 0 307400 188528 0 60 20 1f3ce400 1600 * - 0:00 IBM.ServiceRMd
240401 A 0 135380 188528 0 60 20 1a04c400 680 - 0:00 nimesis
240001 A 8 635014 499926 0 60 20 e5f8400 292 f10001001563c1e8 - 0:00 pconsole_exec
240001 A 8 471054 569380 0 60 20 4435400 816 - 0:00 ksh
240001 A 1 557274 1 0 60 20 1f0ad400 2100 - 0:00 sendmail
240001 A 0 737438 188528 0 39 20 1df0a400 2840 * - 0:02 IBM.CSMAgentRMd
240001 A 0 581740 188528 0 60 20 ab18400 332 f1000200067374c8 - 0:00 tftpd
240001 A 0 569380 188528 0 60 20 13462400 816 - 0:00 ksh
240001 A 0 561364 409748 0 60 20 2877400 788 pts/2 0:00 ksh
240001 A 0 552976 434188 0 60 20 5393400 1400 - 8:01 dtgreet
240001 A 0 479486 418030 0 60 20 1818f400 788 f1000200008f1478 pts/0 0:00 ksh
240001 A 0 475280 1 0 27 20 1a72f400 1216 * - 0:30 posixtrace
240001 A 0 458982 188528 0 60 20 12b63400 408 - 0:00 timed
240001 A 0 454892 188528 0 60 20 1eb4f400 428 - 0:08 routed
240001 A 0 446576 577610 0 60 20 1c7ae400 784 pts/4 0:00 ksh
240001 A 0 393352 188528 0 60 20 b89a400 548 - 0:00 dhcpcd
240001 A 0 368828 188528 0 60 20 142e5400 316 f1000010dd008010 - 0:00 qdaemon
240001 A 0 360628 188528 0 60 20 f2be400 328 f10001001a4ae3a0 - 0:00 rpc.lockd
Displaying the processes in order of priority
# ps -eakl | sort -n +6 | head
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
303 A 0 0 0 120 16 -- 15004000 60 - 3:25 swapper
303 A 0 16392 0 0 16 -- 1b00a000 64 f100080009786c08 - 0:26 lrud
303 A 0 24588 0 0 16 -- 1f00e000 108 - 0:00 vmmd
303 A 0 28686 0 0 16 -- 1010000 52 - 0:00 memgrdd
303 A 0 57372 0 120 16 -- 1030000 68 3d2af70 - 2:20 wlmsched
303 A 0 61470 0 0 16 -- 3032000 52 - 0:00 armtrace_kproc
303 A 0 12294 0 120 17 -- 19008000 56 - 0:14 sched
40201 A 0 98416 0 0 17 20 8119000 136 * - 0:00 dog
240001 A 0 475280 1 0 27 20 1a72f400 1216 * - 0:30 posixtrace
#
Displaying the processes in order of time
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +3 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
8196 - A 3581:13 0 48 40 xx 0 0 21.5 0.0 wait
45078 - A 3113:23 0 48 40 xx 0 0 18.7 0.0 wait
532694 - A 16:07 0 72 72 32768 0 0 0.1 0.0 trclogio
552976 - A 8:01 0 1356 1436 xx 48 80 0.1 0.0 dtgreet
294918 - A 7:16 218 14052 14000 32768 27 24 0.0 2.0 /usr/sbi
168044 - A 4:32 91 544 392 xx 3 4 0.0 0.0 /usr/sbi
254082 - A 3:15 995 216 192 32768 0 0 0.0 0.0 nfsd
0 - A 3:25 7 60 48 xx 0 0 0.0 0.0 swapper
57372 - A 2:20 0 68 32 xx 0 0 0.0 0.0 wlmsched
53274 - A 2:06 0 120 96 xx 0 0 0.0 0.0 gil
Displaying the processes in order of real memory use
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +6 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
294918 - A 7:16 218 14052 14000 32768 27 24 0.0 2.0 /usr/sbi
163928 - A 1:15 1059 7132 3448 xx 3219 1128 0.0 0.0 /usr/lpp
737438 - A 0:02 264 2056 2468 xx 788 412 0.0 0.0 /usr/sbi
352462 - A 0:00 301 1584 2084 xx 542 500 0.0 0.0 /usr/sbi
180370 - A 0:14 137 1096 1596 32768 1187 1000 0.0 0.0 sendmail
307400 - A 0:00 136 1344 1520 xx 258 176 0.0 0.0 /usr/sbi
552976 - A 8:01 0 1356 1436 xx 48 80 0.1 0.0 dtgreet
475280 - A 0:30 20 1144 1208 32768 73 64 0.0 0.0 posixtra
544916 pts/1 A 0:00 0 868 972 32768 80 104 0.0 0.0 ps vx
614566 pts/1 A 0:00 1 600 876 32768 240 276 0.0 0.0 -ksh
Displaying the processes in order of I/O
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +4 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
106632 - A 0:00 2338 136 152 xx 36 36 0.0 0.0 /usr/ccs
163928 - A 1:15 1059 7132 3448 xx 3219 1128 0.0 0.0 /usr/lpp
254082 - A 3:15 995 216 192 32768 0 0 0.0 0.0 nfsd
1 - A 0:09 549 708 492 32768 30 32 0.0 0.0 /etc/ini
352462 - A 0:00 301 1584 2084 xx 542 500 0.0 0.0 /usr/sbi
217218 - A 1:37 267 1076 452 32768 151 44 0.0 0.0 /usr/sbi
737438 - A 0:02 264 2056 2468 xx 788 412 0.0 0.0 /usr/sbi
294918 - A 7:16 218 14056 14004 32768 27 24 0.0 2.0 /usr/sbi
356590 - A 0:00 209 508 152 32768 54 48 0.0 0.0 db2wdog
290960 - A 0:00 166 1572 60 32768 46 8 0.0 0.0 /usr/sbi
Displaying WLM classes
# ps -a -o pid,user,class,pcpu,pmem,args
PID USER CLASS %CPU %MEM COMMAND
32784 <defunct>
221224 you Default 0.0 0.0 -ksh
397328 you Default 0.0 0.0 -ksh
467058 root System 0.0 0.0 ksh
487458 root System 0.0 0.0 -ksh
495768 you Default 0.0 0.0 rlogin cws
520194 root System 0.0 0.0 ps -a -o pid,user,class,pcpu,pmem,args
540676 you Default 0.0 0.0 -ksh
638978 you Default 0.0 0.0 rlogin cws
659554 root System 0.0 0.0 pg
708804 root System 0.0 0.0 pg
Determining the PID of wait processes
# ps vg | head -1 ; ps vg | grep -w wait
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
8196 - A 3582:56 0 48 40 xx 0 0 21.5 0.0 wait
45078 - A 3114:52 0 48 40 xx 0 0 18.7 0.0 wait
#
Posted by Shivakant Tiwari at 6:52 PM 1 comments Email This
BlogThis!
Share to Twitter
Share to Facebook
Share to Google Buzz
Links to this post
Labels: AIX ADVANCE COMMANDS, AIX PERFORMANCE MONITORING, AIX PERFORMANCE TOOLS EXAMPLES, L1 monitoring commands in AIX, ps for aix, ps in AIX
THURSDAY, MARCH 17, 2011
AIX PERFORMANCE TOOLS TPROF VMSTAT SAR AND MPSTAT EXAMPLES
THESE EXAMPLES ARE TAKEN FROM THE MAN PAGE OF THESE COMMANDS
TPROF EXAMPLES
1Basic global program and thread-level summary . This command will give you details of cpu utilization of each process
$ tprof -x sleep 10
Mon May 20 00:39:26 2002 System: AIX 5.2 Node: dreaming Machine: 000671894C00
Starting Command sleep 10
stopping trace collection.
Generating sleep.prof
The resulting sleep.prof file only contains the summary report section.
2 Global profiling with all options
$ tprof -skeuj -x sleep 10
Mon May 20 00:39:26 2002
System: AIX 5.2 Node: drea
ming Machine: 000671894C00
Starting Command sleep 10
stopping trace collection.
Generating sleep.prof
The resulting sleep.prof file contains the summary report and global profile sections.
3 Single process level profiling
$ tprof -u -p workload -x workload
Mon May 20 00:39:26 2002
System: AIX 5.2 Node: drea
ming Machine: 000671894C00
Starting Command workload stopping trace collection.
Generating workload.prof
The resulting workload.prof file contains the summary report and the global user mode profile sections, and one process level profile
section for the process 'workload' that contains only a user mode profile subsection.
4 Multiple process level profiling
$ tprof -se -p send,receive -x startall
Mon May 20 00:39:26 2002
System: AIX 5.2 Node: dreaming Machine: 000671894C00
Starting Command startall
stopping trace collection.
Generating startall.prof
The resulting startall.prof file contains the summary report, the global shared library mode profile, and the global kernel extension
profile sections, and two process level profile sections: one for the process 'send', and one for the process 'receive'. The process
level sections each contain two subsections: one with shared library profiling information and one with kernel extensions profiling
information.
5 Microprofiling and listing annotation
$ tprof -m ./tcalc -L ./tcalc -u -x ./tcalc
Mon May 20 00:47:09 2002
System: AIX 5.2 Node: dreaming Machine: 000671894C00
Starting Command ./tcalc
stopping trace collection.
Generating tcalc.prof
Generating tcalc.tcalc.c.mprof
Generating tcalc.tcalc.c.alst
The resulting tcalc.prof file contains the summary report and the global user mode profile sections. The resulting tcalc.tcalc.c.mprof
and tcalc.tcalc.c.alst files contain the micro-profiling report and the annotated listing.
6 For event-based profiling on processor cycles, sampling once every 100 milliseconds, enter:
tprof -E -f 100 -Askex sleep 10
Output similar to the following displays:
Starting Command sleep 10
stopping trace collection.
Tue Apr 26 14:44:02 2005
System: AIX 5.3 Node: bigdomino Machine: 00C0046A4C00
Generating sleep.trc
Generating sleep.prof
Generating sleep.syms
7 For event-based profiling on completed instructions, sampling once every 20,000 completed instructions, enter:
tprof -E PM_INST_CMPL -f 20000 -Askex sleep 10
Output similar to the following displays:
Starting Command sleep 10
stopping trace collection.
Tue Apr 26 14:42:44 2005
System: AIX 5.3 Node: bigdomino Machine: 00C0046A4C00
Generating sleep.trc
Generating sleep.prof
Generating sleep.syms
8 For event-based profiling on emulation interrupts, sampling once every 10,000 events, enter:
tprof -E EMULATION -Askex sleep 10
Output similar to the following displays:
Starting Command sleep 10
stopping trace collection.
Tue Apr 26 14:41:44 2005
System: AIX 5.3 Node: bigdomino Machine: 00C0046A4C00
Generating sleep.trc
Generating sleep.prof
Generating sleep.syms
9 Automated offline mode
tprof -c -A all -x sleep 10
Starting Command sleep 10
stopping trace collection.
Mon May 20 00:52:52 2002
System: AIX 5.2 Node: dreaming Machine: 000671894C00
Generating sleep.ctrc
Generating sleep.csyms
Generating sleep.prof
The resulting sleep.prof file only has a summary report section, while the two cooked files are ready to be re-postprocessed.
10 Automated offline mode enabling source line collecting.
$ tprof -A -N -x sleep 10
Starting Command sleep 10
stopping trace collection.
Wed Feb 8 15:12:41 2006
System: AIX 5.3 Node: aixperformance Machine: 000F9F3D4C00
Generating sleep.trc
Generating sleep.prof
Generating sleep.syms
The resulting sleep.prof file only contains the summary report section, while sleep.syms contains the source line information.
11 Automated offline mode enabling source line and instruction collecting.
$ tprof -A -N -I -r RootString -x sleep 10
Starting Command sleep 10
stopping trace collection.
Wed Feb 8 15:16:37 2006
System: AIX 5.3 Node: aixperformance Machine: 000F9F3D4C00
Generating RootString.trc
Generating RootString.prof
Generating RootString.syms
The resulting rootstring.prof file is generated, while rootstring.syms contains the source line information and binary instructions.
12 Real-time mode enabling Java source line and instructions collecting.
$ tprof -N -I -x java -Xrunjpa:source=1,instructions=1 HelloAIX
Thu Feb 9 13:30:38 2006
System: AIX 5.3 Node: perftdev Machine: 00CEBB4A4C00
Starting Command java -Xrunvpn_jpa:source=1,instructions=1 HelloAIX
Hello AIX!
stopping trace collection.
Generating java.prof
The resulting java.prof file is generated, and it contains the JIT source line information as well as JIT instructions.
13 Processor usage for the vloop_lib_32 program with no shared library and thread-level profiling, no per-processor tracing, and no post
processing:
$ tprof -A -n -s -t -r test -x vloop_lib_32 5
Starting Command vloop_lib_32 5
stopping trace collection.
Generating test.trc
Generating test.syms
EXAMPLES OF SAR
1 To report system unit activity, enter:
sar
2 To report current tty activity for each 2 seconds for the next 40 seconds, enter: sar -y -r 2 20
3 To watch system unit for 10 minutes and sort data, enter: sar -o temp 60 10
4 To report processor activity for the first two processors, enter: sar -u -P 0,1
This produces output similar to the following:
cpu %usr %sys %wio %idle
0 45 45 5 5
1 27 65 3 5
5 To report message, semaphore, and processor activity for all processors and system-wide, enter: sar -mu -P ALL
On a four-processor system, this produces output similar to the following (the last line indicates system-wide statistics for all
processors):
cpu msgs/s sema/s %usr %sys %wio %idle
0 7 2 45 45 5 5
1 5 0 27 65 3 5
2 3 0 55 40 1 4
3 4 1 48 41 4 7
- 19 3 44 48 3 5
6 To see physical processor consumed and entitlement consumed for all processors system-wide, run sar command in a shared processor
logical partition machine, as follows:
sar -P ALL
On a two-logical processor system, this produces output similar to the following (the last line indicates system-wide statistics for all
processors, and the line with cpuid U indicates the system-wide Unused capacity):
cpu %usr %sys %wio %idle physc %entc
0 0 0 0 100 0.02 3.1
1 0 0 0 100 0.00 1.0
U - - 0 96 0.48 96.0
- 0 0 0 100 0.02 4.0
7 To report system call, kernel process, and paging activities with separate headers for each of the three lines of data at each iteration
for every 2 seconds for the next 40 seconds, enter:
sar -Mckr 2 20
8 To report all activities with multiple sets of headers for every 2 seconds for the next 40 seconds, enter:
sar -MA 2 20
VMSTAT EXAMPLES
1 To display a summary of the statistics since boot, enter:
vmstat
2 To display five summaries at 2-second intervals, enter:
vmstat 2 5
3 To display a summary of the statistics since boot including statistics for logical disks scdisk13 and scdisk14, enter:
vmstat scdisk13 scdisk14
4 To display fork statistics, enter:
vmstat -f
5 To display the count of various events, enter:
vmstat -s
6 To display time-stamp next to each column of output of vmstat, enter:
vmstat -t
7 To display the I/O oriented view with an alternative set of columns, enter:
vmstat -I
8 To display all the VMM statistics available, enter:
vmstat -vs
9 To display the large-page section with the alp and flp columns at 8-second intervals, enter:
vmstat -l 8
10 To display the VMM statistics specific to a particular page size (in the example, 4 K), enter:
vmstat -p 4 K
11 To display the VMM statistics for all page sizes that are supported on the system, enter:
vmstat -p ALL
OR
vmstat -p all
12 To display only the VMM statistics for a particular page size (in this example, 4K), enter:
vmstat -P 4K
13 To display only the per-page breakdown of VMM statistics for all supported page sizes, enter:
vmstat -P ALL
OR
vmstat -P all
MPSTAT EXAMPLES
1 To see the default set of utilization metrics, type:
mpstat 1 1
2 To see the default set of utilization metrics in wide display mode, type:
mpstat -w 1 1
3 To see the detailed dispatch & affinity metrics, type:
mpstat -d 1 1
4 To see the detailed interrupts report, type:
mpstat -i 1 1
5 To see all the statistics, type:
mpstat -a 1 1
6 To see simultaneous multi-threading utilization, type:
mpstat -s 1 1
Posted by Shivakant Tiwari at 12:53 PM 1 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX GENERAL DOCUMENTS, AIX PERFORMANCE MONITORING, AIX PERFORMANCE TOOLS TPROF VMSTAT SAR AND MPSTAT EXAMPLES
SATURDAY, FEBRUARY 26, 2011
AIX DISK PERFORMANCE MONITORING (DISK MONITORING )
To know if the disks are performing under permitted values
run iostat on disks connected to a adpater
#lsdev -p fscsi0
will show all the disk connected
run iostat on these disks to know their transfer rate
add the transfer rates of all the disk and
compare it with max_xfer_size
To get max_xfer_size
type command
lsattr -El fcs0
If max_xfer_size is lower than the kbs of all the disk collectively disk performance is comprimised
I had created a script for my usage change according to your usage
SCRIPT TO CALCULATE TOTAL DISK TRANSFER
d=0
for x in $(lsdev -p fscsi0|awk '{print $1}')
do
a=$(iostat -d $x |grep hdisk|awk '{print $3}')
d=$(echo "$a + $d"|bc)
done
echo CURRENT TRANSFER RATE IS $d
Posted by Shivakant Tiwari at 11:55 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX PERFORMANCE MONITORING, CALCULATING DISK IO PERFORMANCE, HOW TO KNOW DISK PERFORMANCE IN AIX, HOW TO VERIFY DISK PERFORMANCE, script to calculate disk io performance
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)
TOTAL PAGEVIEWS
10,063
Your Ad Here
FEEDJIT
Your Ad Here
MONDAY, MAY 16, 2011
WORKING WITH WPAR - CREATING AND STARTING WPAR
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
CREATE A FILE SYSTEM TO BE USED BY WPAR
# crfs -v jfs2 -g vijayvg -a size=30G -m /wpar-file
File system created successfully.
31456116 kilobytes total disk space.New File System size is 62914560
PUT 700 PERMISSION ON THAT FILE SYSTEM
# mount /wpar-file
chmod -R 700 /wpar-file
CREATE A WPAR IN THE BASE DIRECTORY
This command will create a wpar with ip 193.9.200.230 with hostname shivawpar in directory /wpar-file/wpars
mkwpar -n shivawpar -N address=193.9.200.230 -d /wpar-file/wpars/
+---------- Space statistics (in 512 byte-blocks) ----------+
File system: /wpar-file/wpars, Free: 209512, Required: 137, Deficit: 0.
syncroot: Installing RPM file: /etc/cdrecord.conf
syncroot: RPM root packages are currently synchronized.
syncroot: Root part is currently synchronized.
syncroot: Returns Status = SUCCESS
Workload partition shivawpar created successfully.
mkwpar: 0960-390 To start the workload partition, execute the following as root: startwpar [-v] shivawpar
SHOW THE STATUS OF WPAR
# lswpar
Name State Type Hostname Directory
----------------------------------------------------
shivawpar D S shivawpar /wpar-file/wpars
SYNTAX OF START WPAR
Usage: startwpar [-a] [-m] [-v] [-1 [-R] | -2 [-e 'environment'] | -I] wparName
Flags:
-1 = Phase 1 - load.
-2 = Phase 2 - start initial process.
-a = Automatically resolve erroneous/conflicting settings.
-e = Environment string to pass through to alternate initial process.
-I = Only exec default initial process.
-m = Maintenance mode - starts workload partition with no network interfaces.
-R = Flag the workload partition as restarted (from checkpoint).
-v = Verbose mode.
STARTING A WPAR
# startwpar -v shivawpar
Starting workload partition shivawpar.
Mounting all workload partition file systems.
Mounting /wpar-file/wpars
Mounting /wpar-file/wpars/home
Mounting /wpar-file/wpars/opt
Mounting /wpar-file/wpars/proc
Mounting /wpar-file/wpars/tmp
Mounting /wpar-file/wpars/usr
Mounting /wpar-file/wpars/var
Loading workload partition.
Exporting workload partition devices.
Starting workload partition subsystem cor_shivawpar.
0513-059 The cor_shivawpar Subsystem has been started. Subsystem PID is 483472.
Verifying workload partition startup.
Return Status = SUCCESS.
STOPPING A WPAR
# stopwpar -v shivawpar
Stopping workload partition shivawpar.
Stopping workload partition subsystem cor_shivawpar.
0513-044 The cor_shivawpar Subsystem was requested to stop.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Shutting down all workload partition processes.
WPAR='shivawpar' CID=1
ID=9437199 KEY=0x4107001c UID=0 GID=9 RT=-1
ID=624951327 KEY=0xffffffff UID=0 GID=0 RT=-1
Unmounting all workload partition file systems.
Umounting /wpar-file/wpars/var.
Umounting /wpar-file/wpars/usr.
Umounting /wpar-file/wpars/tmp.
Umounting /wpar-file/wpars/proc.
Umounting /wpar-file/wpars/opt.
Umounting /wpar-file/wpars/home.
Umounting /wpar-file/wpars.
Return Status = SUCCESS.
LOGIN TO WPAR
# clogin shiwawpar
Workload partition shiwawpar is not found.
# clogin shivawpar
*******************************************************************************
* *
* *
* Welcome to AIX Version6.1! *
* *
* *
* Please see the README file in /usr/lpp/bos for information pertinent to *
* this release of the AIX Operating System. *
* *
* *
*******************************************************************************
Posted by Shivakant Tiwari at 8:55 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: CREATING A WPAR, LOGINA WPAR, WPAR
WORKING WITH WPARS
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
1)STARTING A LPAR
# startwpar -v shivawpar
Starting workload partition shivawpar.
Mounting all workload partition file systems.
Mounting /wpar-file/wpars
Mounting /wpar-file/wpars/home
Mounting /wpar-file/wpars/opt
Mounting /wpar-file/wpars/proc
Mounting /wpar-file/wpars/tmp
Mounting /wpar-file/wpars/usr
Mounting /wpar-file/wpars/var
Loading workload partition.
Exporting workload partition devices.
Starting workload partition subsystem cor_shivawpar.
0513-059 The cor_shivawpar Subsystem has been started. Subsystem PID is 483472.
Verifying workload partition startup.
Return Status = SUCCESS.
2)STOPPING A WPAR
# stopwpar -v shivawpar
Stopping workload partition shivawpar.
Stopping workload partition subsystem cor_shivawpar.
0513-044 The cor_shivawpar Subsystem was requested to stop.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Shutting down all workload partition processes.
WPAR='shivawpar' CID=1
ID=9437199 KEY=0x4107001c UID=0 GID=9 RT=-1
ID=624951327 KEY=0xffffffff UID=0 GID=0 RT=-1
Unmounting all workload partition file systems.
Umounting /wpar-file/wpars/var.
Umounting /wpar-file/wpars/usr.
Umounting /wpar-file/wpars/tmp.
Umounting /wpar-file/wpars/proc.
Umounting /wpar-file/wpars/opt.
Umounting /wpar-file/wpars/home.
Umounting /wpar-file/wpars.
Return Status = SUCCESS.
3)REMOVING A WPAR
# rmwpar shivawpar
rmwpar: Removing file system /wpar-file/wpars/var.
rmlv: Logical volume fslv14 is removed.
rmwpar: Removing file system /wpar-file/wpars/usr.
rmwpar: Removing file system /wpar-file/wpars/tmp.
rmlv: Logical volume fslv13 is removed.
rmwpar: Removing file system /wpar-file/wpars/proc.
rmwpar: Removing file system /wpar-file/wpars/opt.
rmwpar: Removing file system /wpar-file/wpars/home.
rmlv: Logical volume fslv12 is removed.
rmwpar: Removing file system /wpar-file/wpars.
rmlv: Logical volume fslv01 is removed.
4)LOGIN TO A WPAR CONSOLE
# clogin shivawpar
*******************************************************************************
* *
* *
* Welcome to AIX Version 6.1! *
* *
* *
* Please see the README file in /usr/lpp/bos for information pertinent to *
* this release of the AIX Operating System. *
* *
* *
*******************************************************************************
5)VIEWING A WPAR STATE
# lswpar -a name,active
Name Active
------------------
shivawpar yes
# lswpar -a name,active,shares_cpu,shares_memory
Name Active CPU Shares Memory Shares
---------------------------------------------
shivawpar yes
6)VIEWING DEVICES OF A WPAR
# lswpar -D
Name Device Name Type
-----------------------------------
shivawpar /dev/null pseudo
shivawpar /dev/tty pseudo
shivawpar /dev/console pseudo
shivawpar /dev/zero pseudo
shivawpar /dev/clone pseudo
shivawpar /dev/sad clone
shivawpar /dev/xti/tcp clone
shivawpar /dev/xti/tcp6 clone
shivawpar /dev/xti/udp clone
shivawpar /dev/xti/udp6 clone
shivawpar /dev/xti/unixdg clone
shivawpar /dev/xti/unixst clone
shivawpar /dev/error pseudo
shivawpar /dev/errorctl pseudo
shivawpar /dev/audit pseudo
shivawpar /dev/nvram pseudo
7)VIEWING ALL THE DETAILS OF WLPAR
# lswpar -L
=================================================================
shivawpar - Defined
=================================================================
GENERAL
Type: S
Owner: root
Hostname: shivawpar
WPAR-Specific Routing: no
Directory: /wpar-file/wpars
Start/Stop Script:
Auto: no
Private /usr: no
Checkpointable: no
Application:
NETWORK
Interface Address(6) Mask/Prefix Broadcast
-----------------------------------------------------------------
en2 193.9.200.230 255.255.255.0 193.9.200.255
USER-SPECIFIED ROUTES
Type Destination Gateway Interface
-----------------------------------------------------------------
FILE SYSTEMS
MountPoint Device Vfs Nodename Options
-----------------------------------------------------------------
/wpar-file/wpars /dev/fslv01 jfs2
/wpar-file/wpars/home /dev/fslv12 jfs2
/wpar-file/wpars/opt /opt namefs ro
/wpar-file/wpars/proc /proc namefs rw
/wpar-file/wpars/tmp /dev/fslv13 jfs2
/wpar-file/wpars/usr /usr namefs ro
/wpar-file/wpars/var /dev/fslv14 jfs2
RESOURCE CONTROLS
Active: yes
Resource Set:
CPU Shares:
CPU Limits:
Memory Shares:
Memory Limits:
Per-Process Virtual Memory Limit: unlimited
Total Processes:
Total Threads:
Total PTYs:
Total Large Pages:
Max Message Queue IDs:
Max Semaphore IDs:
Max Shared Memory IDs:
Max Pinned Memory:
OPERATION
Operation: none
Process ID:
Start Time:
SECURITY SETTINGS
Privileges: PV_AU_,PV_AU_ADD,PV_AU_ADMIN,PV_AU_PROC,PV_AU_READ,
PV_AU_WRITE,PV_AZ_ADMIN,PV_AZ_CHECK,PV_AZ_READ,PV_AZ_ROOT,
PV_DAC_,PV_DAC_GID,PV_DAC_O,PV_DAC_R,PV_DAC_RID,PV_DAC_UID,
PV_DAC_W,PV_DAC_X,PV_DEV_CONFIG,PV_DEV_QUERY,PV_FS_CHOWN,
PV_FS_CHROOT,PV_FS_CNTL,PV_FS_LINKDIR,PV_FS_MKNOD,
PV_FS_MOUNT,PV_FS_PDMODE,PV_FS_QUOTA,PV_KER_ACCT,
PV_KER_CONF,PV_KER_DR,PV_KER_EWLM,PV_KER_EXTCONF,
PV_KER_IPC,PV_KER_IPC_O,PV_KER_IPC_R,PV_KER_IPC_W,
PV_KER_NFS,PV_KER_RAC,PV_KER_RAS_ERR,PV_KER_REBOOT,
PV_NET_PORT,PV_PROC_CKPT,PV_PROC_CORE,PV_PROC_CRED,
PV_PROC_ENV,PV_PROC_PRIO,PV_PROC_PDMODE,PV_PROC_RAC,
PV_PROC_RTCLK,PV_PROC_SIG,PV_PROC_TIMER,PV_PROC_VARS,
PV_PROC_PRIV,PV_SU_UID,PV_TCB,PV_TP,PV_TP_SET,PV_MIC,
PV_MIC_CL,PV_LAB_,PV_LAB_CL,PV_LAB_CLTL,PV_LAB_LEF,
PV_LAB_SLDG,PV_LAB_SLDG_STR,PV_LAB_SL_FILE,PV_LAB_SL_PROC,
PV_LAB_SL_SELF,PV_LAB_SLUG,PV_LAB_SLUG_STR,PV_LAB_TL,
PV_MAC_,PV_MAC_CL,PV_MAC_R,PV_MAC_R_CL,PV_MAC_R_STR,
PV_MAC_R_PROC,PV_MAC_W,PV_MAC_W_CL,PV_MAC_W_DN,PV_MAC_W_UP,
PV_MAC_W_PROC,PV_MAC_OVRRD,PV_KER_SECCONFIG,
PV_PROBEVUE_TRC_USER,PV_PROBEVUE_TRC_USER_SELF
DEVICE EXPORTS
Name Type
-----------------------------------------------------------------
/dev/null pseudo
/dev/tty pseudo
/dev/console pseudo
/dev/zero pseudo
/dev/clone pseudo
/dev/sad clone
/dev/xti/tcp clone
/dev/xti/tcp6 clone
/dev/xti/udp clone
/dev/xti/udp6 clone
/dev/xti/unixdg clone
/dev/xti/unixst clone
/dev/error pseudo
/dev/errorctl pseudo
/dev/audit pseudo
/dev/nvram pseudo
8)VIEWING AND CHANGING CPU AND MEMORY RESOURCES OF WPAR
# lswpar -a cpu,memory
CPU Limits Memory Limits
----------------------------
0%-100%,100% 0%-100%,100%
# chwpar -R CPU=2%-10%,30% memory=2%-5%,20% shivawpar
# lswpar -a cpu,memory shivawpar
CPU Limits Memory Limits
--------------------------
2%-10%,30% 2%-5%,20%
#
Posted by Shivakant Tiwari at 8:54 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: CHANGING CPU AND MEMORY RESOURCES OF WPAR, REMOVING A WPAR, STARTING A WPAR, STOPPING, WPAR
WPAR BACKUP AND RESTORE
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
TAKE BACKUP OF SHIVAWPAR IN A FILE
# savewpar -f /wpar-file/shivawpar.back shivawpar
Creating information file for workload partition shivawpar.
Creating list of files to back up.
Backing up 6238 files.
6238 of 6238 files (100%)0512-038 savewpar: Backup Completed Successfully.
FOR TEST PURPOSE WE ARE GOING TO REMOVE WPAR SHIVAWPAR
1) STOP SHIVAWPAR
# stopwpar shivawpar
Stopping workload partition shivawpar.
Stopping workload partition subsystem cor_shivawpar.
0513-044 The cor_shivawpar Subsystem was requested to stop.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Shutting down all workload partition processes.
Unmounting all workload partition file systems.
2)REMOVE THE CURRENT WPAR
# rmwpar shivawpar
rmwpar: Removing file system /wpar-file/wpars/var.
rmlv: Logical volume fslv14 is removed.
rmwpar: Removing file system /wpar-file/wpars/usr.
rmwpar: Removing file system /wpar-file/wpars/tmp.
rmlv: Logical volume fslv13 is removed.
rmwpar: Removing file system /wpar-file/wpars/proc.
rmwpar: Removing file system /wpar-file/wpars/opt.
rmwpar: Removing file system /wpar-file/wpars/home.
rmlv: Logical volume fslv12 is removed.
rmwpar: Removing file system /wpar-file/wpars.
rmlv: Logical volume fslv01 is removed.
RESTORE WPAR WITH FOLLOWING COMMAND
# restwpar -n shivawpar -f /wpar-file/shivawpar.back
New volume on /wpar-file/shivawpar.back:
Cluster size is 51200 bytes (100 blocks).
The volume number is 1.
The backup date is: Fri May 13 06:10:18 PAKDT 2011
Files are backed up by name.
The user is root.
x 2851 ./.savewpar_dir/wpar.spec
x 4655 ./.savewpar_dir/image.data
x 150544 ./.savewpar_dir/backup.data
The total size is 158050 bytes.
The number of restored files is 3.
mkwpar: Creating file systems...
/
Creating logical volume 'fslv01' specified in image.data
Creating file system '/' specified in image.data
/home
Creating logical volume 'fslv12' specified in image.data
Creating file system '/home' specified in image.data
/opt
/proc
/tmp
Creating logical volume 'fslv13' specified in image.data
Creating file system '/tmp' specified in image.data
/usr
/var
Creating logical volume 'fslv14' specified in image.data
Creating file system '/var' specified in image.data
Mounting all workload partition file systems.
New volume on /wpar-file/shivawpar.back:
Cluster size is 51200 bytes (100 blocks).
The volume number is 1.
The backup date is: Fri May 13 06:10:18 PAKDT 2011
Files are backed up by name.
The user is root.
x 15 ./.savewpar_dir/image.info
x 136 ./.savewpar_dir/data.files569476
x 136 ./.savewpar_dir/vgdata.files
x 3964 ./.savewpar_dir/filesystems
x 2851 ./.savewpar_dir/wpar.spec
x 4655 ./.savewpar_dir/image.data
x 150544 ./.savewpar_dir/backup.data
x 0 ./var
x 0 ./var/lost+found
x 0 ./var/adm
x 0 ./var/adm/cron
x 4 ./var/adm/cron/at.deny
x 3 ./var/adm/cron/cron.deny
x 284 ./var/adm/cron/log
x 1313 ./var/adm/cron/queuedefs
x 0 ./var/adm/cron/FIFO
x 0 ./var/adm/ras
x 1638 ./var/adm/ras/raspertune
x 199119 ./var/adm/ras/codepoint.cat
x 0 ./var/adm/ras/platform
x 57797 ./var/adm/ras/devinst.log
#
restore: 0511-102 Import of Access Control Lists failed.
The file system has read permission only.
restore: 0511-101 Import of Process Control Lists for file ./opt failed.
The file system has read permission only.
x 0 ./opt
./opt: The file system has read permission only.
x 0 ./proc
restore: 0511-102 Import of Access Control Lists failed.
The file system has read permission only.
restore: 0511-101 Import of Process Control Lists for file ./usr failed.
The file system has read permission only.
x 0 ./usr
./usr: The file system has read permission only.
The total size is 75699210 bytes.
The number of restored files is 6238.
syncroot: Processing root part installation status.
syncroot: Installp root packages are currently synchronized.
syncroot: RPM root packages are currently synchronized.
syncroot: Root part is currently synchronized.
syncroot: Returns Status = SUCCESS
Workload partition shivawpar created successfully.
mkwpar: 0960-390 To start the workload partition, execute the following as root: startwpar [-v] shivawpar
#
#
Posted by Shivakant Tiwari at 8:52 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: WPAR
Newer Posts Older Posts Home
FRIDAY, APRIL 22, 2011
TAKING MKSYSB BACKUP USING NIM
CREATE NIM MASTER
# nimconfig -a netname=testmaster -a pif_name=en0 -a platform=rspc -a cable_type1=tp -a netboot_kernel=up
0513-071 The nimesis Subsystem has been added.
0513-071 The nimd Subsystem has been added.
0513-059 The nimesis Subsystem has been started. Subsystem PID is 545010.
#
CREATE A STANDALONE MACHINE
# nim -o define -t standalone -a platform=rspc -a if1="find_net cws 0" nodecws
VIEW THE CURRENTLY CREATED MACHINE
# lsnim -l nodecws
nodecws:
class = machines
type = standalone
connect = shell
platform = rspc
netboot_kernel = mp
if1 = testmaster cws 0
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
#
ADD THE FILE SYSTEMS TO EXCLUDE
# echo "/tmp/" > /etc/exclude.rootvg
# echo "/export/nim/" >> /etc/exclude.rootvg
DEFINE MKSYSB RESOURCE AND USE MKSYSB REQUIRED SWITCHES
# nim -o define -t mksysb -a mk_image=yes -a mksysb_flags=e -a server=master -a location=/export/nim/mksysb -a source=nodecws cwsmksysb
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in 1024-byte blocks.)
+---------------------------------------------------------------------+
Required = 1048678 (1024 MB) Available = 10869900 (10615 MB)
Data compression will be used by the system backup utilities which
create the system backup image. This may reduce the required space
by up to 50 percent.
Creating information file (/image.data) for rootvg.....
Creating list of files to back up..
Backing up 29207 files..............................
5395 of 29207 files (18%)..............................
6282 of 29207 files (21%)..............................
6426 of 29207 files (22%)..............................
6452 of 29207 files (22%)..............................
7608 of 29207 files (26%)..............................
7648 of 29207 files (26%)..............................
7751 of 29207 files (26%)..............................
8086 of 29207 files (27%)..............................
9054 of 29207 files (30%)..............................
9481 of 29207 files (32%)..............................
10091 of 29207 files (34%)..............................
12922 of 29207 files (44%)..............................
13119 of 29207 files (44%)..............................
13354 of 29207 files (45%)..............................
22726 of 29207 files (77%)..............................
24617 of 29207 files (84%)........................
29207 of 29207 files (100%)
0512-038 savevg: Backup Completed Successfully.
Posted by Shivakant Tiwari at 5:49 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: aixG, mksysb backup using nim, mksysb on nim, nim -o define -t mksysb, NIM Commands, nim mksysb with mksysb switches, taking mksysb from network
THURSDAY, JANUARY 27, 2011
SIMPLEST NIM CONFIGURATION
SIMPLEST DOCUMENT TO IMPLEMENT NIM
1. Create a nim server
(Here netname is name of nim server , primary adapter in en0 , caple type is twisted pair, for a rs6000 server and for single processor )
# nimconfig -a netname=testnim -a pif_name=en0 -a cable_type=tp -a platform=rspc -a netboot_kernel=up
0513-071 The nimesis Subsystem has been added.
0513-071 The nimd Subsystem has been added.
0513-059 The nimesis Subsystem has been started. Subsystem PID is 602362.
Test the newly created server
# lsnim –l
master:
class = machines
type = master
max_nimesis_threads = 20
comments = machine which controls the NIM environment
platform = rspc
netboot_kernel = up
if1 = testnim galaxy 000D60DEFDAE
cable_type1 = tp
Cstate = ready for a NIM operation
prev_state =
Mstate = currently running
serves = boot
serves = nim_script
master_port = 1058
registration_port = 1059
reserved = yes
boot:
class = resources
type = boot
comments = represents the network boot resource
Rstate = ready for use
location = /tftpboot
alloc_count = 0
server = master
reserved = yes
nim_script:
class = resources
type = nim_script
comments = directory containing customization scripts created by NIM
Rstate = ready for use
location = /export/nim/scripts
alloc_count = 0
server = master
reserved = yes
testnim:
class = networks
type = ent
Nstate = ready for use
prev_state = information is missing from this object's definition
net_addr = 193.9.200.0
snm = 255.255.255.0
2. Define lpp source from cdrom
(Here source is cd0 , location is where we are storing lpp source and name is testlpp)
# nim -o define -t lpp_source -a server=master -a source=/dev/cd0 -a location=/export/lpp_source testlpp
Preparing to copy install images (this will take several minutes)...
Check the newly created lpp source
testlpp:
class = resources
type = lpp_source
arch = power
Rstate = ready for use
prev_state = unavailable for use
location = /export/lpp_source
simages = yes
alloc_count = 0
server = master
3. Define a spot from the lpp source
(Here source is the lpp we defined earlier , and location is where we are keeping our spot , name of the spot is spottest)
nim -o define -t spot -a server=master -a source=testlpp -a location=/export/spot spottest
Test the newly created spot
spottest:
class = resources
type = spot
plat_defined = chrp
arch = power
plat_defined = rs6k
plat_defined = rspc
bos_license = yes
Rstate = ready for use
prev_state = verification is being performed
location = /export/spot/spottest/usr
version = 5
release = 1
mod = 0
oslevel_r = 5100-01
alloc_count = 0
server = master
Rstate_result = success
mk_netboot = yes
mk_netboot = yes
4. Define machine
(Here platform is rs6000, xyz is the name of the host for which machine is created , and the name of resource is testpci)
# nim -o define -t standalone -a platform=rspc -a if1="find_net xyz 0" -a cable_type1=tp -a netboot_kernel=up testpci
Test the newly created machine
# lsnim -l testpci
testpci:
class = machines
type = standalone
connect = shell
platform = rspc
netboot_kernel = up
if1 = testnim pci 0
cable_type1 = tp
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
5. Allocate the RESOURCES
newly created lpp and spot resources to the newly cerated machine
## nim -o allocate -a spot=spottest -a lpp_source=testlpp testpci
6. Initiate bos installation on the machine
nim -o bos_inst -a accept_licenses=yes testpci
Posted by Shivakant Tiwari at 8:10 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: EASY NIM CONFIGURATION USING COMMAND LINE, NIM Commands, NIM SIMPLE COMMANDS, NIM STEP BY STEP USING COMMANDS, SIMPLEST NIM CONFIGURATION
CREATING A FILE SYSTEM IN HACMP
/usr/sbin/cluster/sbin/cl_crfs -cspoc “-ncws,pci” -v jfs2 -gconvg -a size=32786 -m/test-export -prw -a size=4096
In the above command –n for nodes here pci and cws are nodes
-v for type of file system –g for vgname
-m for mount point
-p for permissions
-a size is size in blocks
EXTENDING A FILE SYSTEM IN HACMP
# /usr/es/sbin/cluster/sbin/cl_chfs -cspoc "-g testrg" -a size=+32768 /shfs
cws: File System size changed to 65536
#
In the above command –g for resource group
-a size is the size in block
CHECKING THE FILE SYSTEM
# df -k /shfs
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/lv1 32768 31408 5% 4 1% /shfs
#
#
MOVE THE RG TO OTHER NODE AND VERIFY FILE SYSTEM
# /usr/es/sbin/cluster/utilities/clRGmove -g testrg -n pci -m
Attempting to move group testrg to node pci.
Waiting for cluster to process the resource group movement request....
Waiting for the cluster to stabilize............
Resource group movement successful.
Resource group testrg is online on node pci.
REDUCING VG IN HACMP
# ./cl_reducevg -cspoc "-g testrg" -R pci sh1vg hdisk4
Posted by Shivakant Tiwari at 4:34 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: creating a file system in hacmp, extending a file system in hacmp, HACMP ADMINISTRATION AND CONFIGURATIONS, reducing a vg in hacmp
SATURDAY, JUNE 4, 2011
EXTENDING A SHARED VG IN HACMP / ADDING A DISK IN SHARED VG IN HACMP
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
TO EXTEND A SHARED VOLUME IN HACMP
PCI
# lspv
hdisk2 000ac1331e511d20 con1vg
hdisk3 000ac1331e513fe5 None
hdisk4 000ac1331e51658a None
hdisk0 000ac13395197f5e rootvg
hdisk5 000ac13382115287 None
CWS
# lspv
hdisk0 00fad1d465b1b385 rootvg
hdisk1 00fad1d4b98a1756 None
hdisk2 00fad1d4b98a1a3e None
hdisk3 000ac1331e511d20 con1vg
hdisk4 00fad1d4b98a23b2 None
hdisk5 000ac133b98a2e01 None
GO TO C-SPOC >> HACMP Logical Volume Management
System Management (C-SPOC)
Move cursor to desired item and press Enter.
Manage HACMP Services
HACMP Communication Interface Management
HACMP Resource Group and Application Management
HACMP Log Viewing and Management
HACMP File Collection Management
HACMP Security and Users Management
HACMP Logical Volume Management
HACMP Concurrent Logical Volume Management
HACMP Physical Volume Management
Configure GPFS
Open a SMIT Session on a Node
GO TO >> Shared Volume Groups
HACMP Logical Volume Management
Move cursor to desired item and press Enter.
Shared Volume Groups
Shared Logical Volumes
Shared File Systems
Synchronize Shared LVM Mirrors
Synchronize a Shared Volume Group Definition
GO TO >> Set Characteristics of a Shared Volume Group
Shared Volume Groups
Move cursor to desired item and press Enter.
List All Shared Volume Groups
Create a Shared Volume Group
Create a Shared Volume Group with Data Path Devices
Set Characteristics of a Shared Volume Group
Import a Shared Volume Group
Mirror a Shared Volume Group
Unmirror a Shared Volume Group
GO TO >> Add a Volume to a Shared Volume Group
Set Characteristics of a Shared Volume Group
Move cursor to desired item and press Enter.
Add a Volume to a Shared Volume Group
Remove a Volume from a Shared Volume Group
Enable/Disable a Shared Volume Group for Cross-Site LVM Mirroring Verification
SELECT THE VOLUME GROUP NEEDED TO EXTEND
Add a Volume to a Shared Volume Group
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
Resource Group Name RG1
VOLUME GROUP name testshare
Reference node pci
VOLUME names hdisk4
NOW SELECT >> Synchronize a Shared Volume Group Definition
HACMP Logical Volume Management
Move cursor to desired item and press Enter.
Shared Volume Groups
Shared Logical Volumes
Shared File Systems
Synchronize Shared LVM Mirrors
Synchronize a Shared Volume Group Definition
SELECT THE VOLUME GROUP TO SHARE
Synchronize a Shared Volume Group Definition
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
SHARED VOLUME GROUP name []
+--------------------------------------------------------------------------+
| SHARED VOLUME GROUP name |
| |
| Move cursor to desired item and press Enter. |
| |
| cws: con1vg |
| cws: testshare |
| |
| Esc+1=Help Esc+2=Refresh Esc+3=Cancel |
Esc+1=Help | Esc+8=Image Esc+0=Exit
Enter=Do | Esc+4=List
Esc+5=Reset | /=Find n=Find Next | Esc+8=Image Esc+9=Shell +--------------------------------------------------------------------------+
IF IT GIVES PROBLEM - SYNCHRONISE IT WITH THE COMMAND BELOW
# cl_updatevg -cspoc "-g RG1" testshare
NOW TRY TO IMPORT AND EXPORT THE VG MANYALLY ON BOTH NODES
ON CWS
# lsvg -o
rootvg
# lsvg
rootvg
testshare
con1vg
# lspv
hdisk0 00fad1d465b1b385 rootvg
hdisk1 00fad1d4b98a1756 None
hdisk2 00fad1d4b98a1a3e None
hdisk3 000ac1331e511d20 con1vg
hdisk4 00fad1d4b98a23b2 testshare
hdisk5 000ac133b98a2e01 testshare
# exportvg testshare
# importvg -y testshare hdisk4
synclvodm: No logical volumes in volume group testshare.
testshare
# lsvg
rootvg
testshare
con1vg
#
# varyoffvg testshare
# lsvg
rootvg
testshare
con1vg
#
ON PCI
# hostname
pci
# lsvg
rootvg
testshare
con1vg
# lspv
hdisk2 000ac1331e511d20 con1vg
hdisk3 00fad1d4b98a23b2 testshare
hdisk4 000ac133b98a2e01 testshare
hdisk0 000ac13395197f5e rootvg
hdisk5 000ac133b98a3360 None
# exportvg testshare
# importvg -y testshare hdisk3
synclvodm: No logical volumes in volume group testshare.
testshare
# lspv
hdisk2 000ac1331e511d20 con1vg
hdisk3 00fad1d4b98a23b2 testshare
hdisk4 000ac133b98a2e01 testshare
hdisk0 000ac13395197f5e rootvg
hdisk5 000ac133b98a3360 None
# lsvg
rootvg
testshare
con1vg
#
NOW STOP CLUSTER SERVICE
Stop Cluster Services
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Stop now, on system restart or both now
Stop Cluster Services on these nodes [cws,pci]
BROADCAST cluster shutdown? true
* Shutdown mode graceful
+--------------------------------------------------------------------------+
| ARE YOU SURE? |
| |
| Continuing may delete information you may want |
| to keep. This is your last chance to stop |
| before continuing. |
| Press Enter to continue. |
| Press Cancel to return to the application. |
| |
Esc+1=Help Es| Esc+1=Help Esc+2=Refresh Esc+3=Cancel | Esc+4=List
Esc+5=Reset Es| Esc+8=Image Esc+0=Exit Enter=Do | Esc+8=Image
VERIFY AND SYNCHORONISE THE CLUSTER
Extended Configuration
Move cursor to desired item and press Enter.
Discover HACMP-related Information from Configured Nodes
Extended Topology Configuration
Extended Resource Configuration
Extended Event Configuration
Extended Performance Tuning Parameters Configuration
Security and Users Configuration
Snapshot Configuration
Export Definition File for Online Planning Worksheets
Extended Verification and Synchronization
HACMP Cluster Test Tool
RESTART THE CLUSTER
MOVE THE RESOURCE GROUP AND TEST VG
/usr/es/sbin/cluster/sbin/cl_chvg -cspoc "-g RG1 " -a n testshare
Posted by Shivakant Tiwari at 2:25 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: ADDING A DISK IN SHARED VOLUME IN HACMP, EXTENDING A SHARED VOLUME, HACMP ADMINISTRATION AND CONFIGURATIONS, HACMP VG EXTEND
THURSDAY, MAY 26, 2011
HACMP LOGS - HACMP.OUT
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
HACMP.OUT
This file contains the output of all the events in a cluster the events are located in directory /usr/es/sbin/cluster/events
This file also gives complete command line to perform the task and the output of that task
To start troubleshooting hacmp find messages like EVENT FAILED IN THE hacmp.out file
# cat hacmp.out |grep "EVENT FAILED"
May 6 08:45:47 EVENT FAILED: 1: get_disk_vg_fs ALL Testnode1vg 1
Now We know that there is a failed event on May 6 and the event is get_disk_vg_fs
The error shows that the get_disk_vg_fs failed as it could not mount a file system "cl_activate_fs /sapmnt/X10" which is showed in the log below
cirg:cl_activate_fs[85] mount /sapmnt/X10
mount: /dev/X10sapmntlv on /sapmnt/X10: Missing file or filesystem
cirg:cl_activate_fs[87] [[ fsck == logredo ]]
cirg:cl_activate_fs[107] cl_RMupdate resource_error /sapmnt/X10 cl_activate_fs
Reference string: Fri.May.6.08:45:47.IST.2011.cl_activate_fs..sapmnt.X10.cirg.ref
cirg:cl_activate_fs[108] cl_echo 10 'cl_activate_fs: Failed mount of /sapmnt/X10.' cl_activate_fs /sapmnt/X10
cirg:cl_echo[49] version=1.13
cirg:cl_echo[98] HACMP_OUT_FILE=/tmp/hacmp.out
May 6 2011 08:45:47 cl_activate_fs: Failed mount of /sapmnt/X10.cirg:cl_activate_fs[109] STATUS=1
Posted by Shivakant Tiwari at 3:55 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HACMP ADMINISTRATION AND CONFIGURATIONS, HACMP LOGS, HACMP.OUT, understanding hacmp.out
HACMP LOGS CLSTRMGR.DEBUG
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
CLSTRMGR.DEBUG
This file containes time stamed output generated by the clstrmgrES daemon
This file is very much helpul in finding cause of errors
FOR EXAMPLE THE BELOW EXAMPLE SHOWS HOW CLUSTER MANAGER SEARCHES FOR NODES IN CLUSTER
Mon Dec 13 10:58:56 ResGroupList::initialize() Constructing new list with 2 groups
Mon Dec 13 10:58:56 NodeList::NodeList constructor called.Mon Dec 13 10:58:56 NodeList::NodeList: Found node name Testnode2.
Mon Dec 13 10:58:56 NodeList::NodeList: Found node name Testnode1.
Mon Dec 13 10:58:56 NodeList::DumpNodeList called.Mon Dec 13 10:58:56 NodeList::DumpNodeList: There are 2 nodes in this list.
Mon Dec 13 10:58:56 NodeList::DumpNodeList: Their names, states and ids are:
Mon Dec 13 10:58:56 Testnode2, 4, 2
Mon Dec 13 10:58:56 Testnode1, 4, 1
Mon Dec 13 10:58:56 NodeList::DumpNodeList: The nodes are not ordered.
Mon Dec 13 10:58:56 Creating Resource Group : dbrg (2)
Mon Dec 13 10:58:56 NodeList::NodeList constructor called.Mon Dec 13 10:58:56 NodeList::NodeList: Found node name Testnode1.
Mon Dec 13 10:58:56 NodeList::NodeList: Found node name Testnode2.
Mon Dec 13 10:58:56 NodeList::DumpNodeList called.Mon Dec 13 10:58:56 NodeList::DumpNodeList: There are 2 nodes in this list.
Mon Dec 13 10:58:56 NodeList::DumpNodeList: Their names, states and ids are:
Mon Dec 13 10:58:56 Testnode1, 4, 1
Mon Dec 13 10:58:56 Testnode2, 4, 2
Mon Dec 13 10:58:56 NodeList::DumpNodeList: The nodes are not ordered.
Mon Dec 13 10:58:56 Creating Resource Group : cirg (1)
Mon Dec 13 10:58:56 RGTemporalDep::initialize(): CALLED, 1
Mon Dec 13 10:58:56 GetObjects: Called with criteria:
EXAMPLE OF HEARTBEAT INFORMATION IN THE LOG
Mon Dec 13 10:59:49 interface Testnode2_hdisk22_01 on network net_diskhb_01 is up on node Testnode2
Mon Dec 13 10:59:49 Network::setGlobalState: network net_diskhb_01(0) is already 2, return
Mon Dec 13 10:59:49 interface Testnode2_hdisk22_01 on network net_diskhb_01 is up on node Testnode2
Mon Dec 13 10:59:49 Network::setState: network net_diskhb_01(0) is already 2, return
Mon Dec 13 10:59:49 interface Testnode2_boot on network net_ether_01 is up on node Testnode2
Mon Dec 13 10:59:49 Network::setGlobalState: network net_ether_01(1) is already 2, return
Mon Dec 13 10:59:49 interface Testnode2_boot on network net_ether_01 is up on node Testnode2
Mon Dec 13 10:59:49 Network::setState: network net_ether_01(1) is already 2, return
Mon Dec 13 10:59:49 transition from stable to unstanle - refresh clinfo
Mon Dec 13 10:59:49 MqSend: Setting up MQ_TENODE_INFO_MSG for event TE_UNSTABLE, te_nodeid = 1
Mon Dec 13 10:59:49 FSMrun: next state = ST_UNSTABLE, FSM-event = FSM_NONE
Mon Dec 13 10:59:49 FSMrun: complete(1) 0 secs
NOTE SEE FILE hacmprd_rcovcmd.err FOR ADDITIONAL ERROR
Posted by Shivakant Tiwari at 3:20 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: clstrmgr.debuc, HACMP ADMINISTRATION AND CONFIGURATIONS, HACMP LOGS
HACMP LOG FILES - CLCOMD.LOG
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
CLCOMD.LOG
clcomd contains informatuion related with communication so generally this log is not used for troubleshooting
A SAMPLE OF CLCOMD.LOG
Fri Apr 15 23:58:59 2011: RSH: Command='lsvg -Lo',pid=3543832
Fri Apr 15 23:58:59 2011: RSH:COMPLETED: exit code = 0, pid=3543832
Fri Apr 15 23:58:59 2011: RSH: ACCEPTED: Testnode1: 172.16.1.31->172.16.1.29
Posted by Shivakant Tiwari at 2:32 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: CLCOMD.LOG, HACMP ADMINISTRATION AND CONFIGURATIONS, HACMP LOG FILES, HACMP LOGS
WEDNESDAY, MAY 18, 2011
UNDERSTANDING HACMP LOGS -autoverify.log
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY --- IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
BELOW IS THE OUTPUT OF autoverify.log
This log stores the error and warnings when we are running verification on hacmp nodes ,
while verification is running this log can be viewed to see any error occurred during verification process
main:2: : Function 'main<1> Testnode2'
main:10: is_autover_running
is_autover_running:3: get_local_nodename
is_autover_running:3: LOCALNODENAME=Testnode2
is_autover_running:3: typeset LOCALNODENAME
is_autover_running:4: clnodename
is_autover_running:4: CLUSTER_NODES=$'Testnode1\nTestnode2'
is_autover_running:4: typeset CLUSTER_NODES
is_autover_running:5: ACTIVE_NODES=''
is_autover_running:5: typeset ACTIVE_NODES
is_autover_running:7: [[ Testnode1 != Testnode2 ]]
is_autover_running:8: cl_rsh Testnode1 /usr/es/sbin/cluster/utilities/cl_auto_versync -a
is_autover_running:8: IS_ACTIVE=INACTIVE
is_autover_running:9: [[ INACTIVE == ACTIVE ]]
is_autover_running:7: [[ Testnode2 != Testnode2 ]]
is_autover_running:15: return 1
main:10: ACTIVE_NODES=''
main:17: (( 1 != 1 ))
main:28: unset ACTIVE_NODES
main:32: require_dir /tmp/autoverify/352898/ACD
require_dir:2: : Function 'require_dir<1> /tmp/autoverify/352898/ACD'
require_dir:4: mkdir -p /tmp/autoverify/352898/ACD
main:33: require_dir /tmp/autoverify/352898/DCD
require_dir:2: : Function 'require_dir<1> /tmp/autoverify/352898/DCD'
require_dir:4: mkdir -p /tmp/autoverify/352898/DCD
main:36: clnodename
main:36: CLUSTER_NODES=$'Testnode1\nTestnode2'
main:37: (( 11 ))
main:41: DOWN_NODES=''
main:43: clgetaddr Testnode2
main:43: [[ Testnode2 == Testnode2 ]]
main:45: [[ -n '' ]]
main:51: (( 0 == 0 ))
main:51: errmsg 33
errmsg:2: : Function 'errmsg<1>33'
errmsg:4: (( 1 ))
errmsg:5: target=33
errmsg:5: typeset target
errmsg:6: shift
errmsg:7: dspmsg -s 20 scripts.cat 33 '\nVerifying Cluster Configuration Prior to Starting Cluster Services.\n'
Posted by Shivakant Tiwari at 10:32 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: autoverify.log, HACMP ADMINISTRATION AND CONFIGURATIONS, understanding hacmp logs
UNDERSTANDING HACMP LOGS cl_event_summary
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
cl_event_summary
BELOW IS THE OUTPUT OF cl_event_summary
cl_event_summary contains events pulled out from hacmp.out file , whenever a hacmp.out file completes its cycle event summary is pulled into this file , this file is the best place to start looking for all the events that took place recently , before going to hacmp.out
THIS LOG IS THE FIRST PLACE TO LOOK WHEN STUDYING THE HACMP FOR ANY ERROS OR EVENTS
HACMP Event Summary
Event: /usr/es/sbin/cluster/events/check_for_site_up Testnode2
Start time: Wed May 4 15:57:01 2011
End time: Wed May 4 15:57:01 2011
Action: Resource: Script Name:
----------------------------------------------------------------------------
No resources changed as a result of this event
----------------------------------------------------------------------------
HACMP Event Summary
Event: node_up Testnode2
Start time: Wed May 4 15:57:01 2011
End time: Wed May 4 15:59:01 2011
Action: Resource: Script Name:
----------------------------------------------------------------------------
Acquiring resource group: dbrg process_resources
Search on: Wed.May.4.15:57:03.IST.2011.process_resources.dbrg.ref
Acquiring resource: All_service_addrs acquire_service_addr
Search on: Wed.May.4.15:57:03.IST.2011.acquire_service_addr.All_service_addrs.dbrg.ref
Resource online: All_nonerror_service_addrs acquire_service_addr
Search on: Wed.May.4.15:57:04.IST.2011.acquire_service_addr.All_nonerror_service_addrs.dbrg.ref
Acquiring resource: All_disks cl_disk_available
Search on: Wed.May.4.15:57:04.IST.2011.cl_disk_available.All_disks.dbrg.ref
Resource online: All_nonerror_disks cl_disk_available
Search on: Wed.May.4.15:57:35.IST.2011.cl_disk_available.All_nonerror_disks.dbrg.ref
Acquiring resource: All_volume_groups cl_activate_vgs
Search on: Wed.May.4.15:57:35.IST.2011.cl_activate_vgs.All_volume_groups.dbrg.ref
Resource online: All_nonerror_volume_groups cl_activate_vgs
Search on: Wed.May.4.15:58:34.IST.2011.cl_activate_vgs.All_nonerror_volume_groups.dbrg.ref
Acquiring resource: All_filesystems cl_activate_fs
Search on: Wed.May.4.15:58:44.IST.2011.cl_activate_fs.All_filesystems.dbrg.ref
Resource online: All_non_error_filesystems cl_activate_fs
Search on: Wed.May.4.15:58:45.IST.2011.cl_activate_fs.All_non_error_filesystems.dbrg.ref
----------------------------------------------------------------------------
HACMP Event Summary
Event: node_up_complete Testnode2
Start time: Wed May 4 15:59:01 2011
End time: Wed May 4 15:59:04 2011
Action: Resource: Script Name:
----------------------------------------------------------------------------
Acquiring resource: All_servers start_server
Search on: Wed.May.4.15:59:01.IST.2011.start_server.All_servers.dbrg.ref
Resource online: All_nonerror_servers start_server
Search on: Wed.May.4.15:59:02.IST.2011.start_server.All_nonerror_servers.dbrg.ref
Resource group online: dbrg process_resources
Search on: Wed.May.4.15:59:02.IST.2011.process_resources.dbrg.ref
----------------------------------------------------------------------------
HACMP Event Summary
Event: /usr/es/sbin/cluster/events/check_for_site_up_complete Testnode2
Start time: Wed May 4 15:59:04 2011
End time: Wed May 4 15:59:04 2011
Action: Resource: Script Name:
----------------------------------------------------------------------------
No resources changed as a result of this event
----------------------------------------------------------------------------
Clear event summaries periodically, using the Problem Determination Tools > HACMP Log Viewing and Management > View/Save/Remove HACMP Event Summaries > Remove Event Summary History
Posted by Shivakant Tiwari at 10:24 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: cl_event_summary, HACMP ADMINISTRATION AND CONFIGURATIONS, understanding hacmp logs
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)
TOTAL PAGEVIEWS
10,052
Your Ad Here
FEEDJIT
Your Ad Here
TUESDAY, MAY 10, 2011
COLLECTING VG AND PV INFORMATION
GETTING VG AND PV INFORMATION
THIS SCRIPT COLLECTS VOLUME GROUP AND PHYSICAL VOLUME INFORMATION AND COLLECTS THEM IN A FILE
THIS INFORMATION IS IMOPORTANT AS ONE SCRIPT ON A SERVER WILL PROVIDE ALL THE INFORMATION ABOUT ALL THE VG AND PV UNDER IT
for x in $(lsvg) ;SELECT ALL THE VOLUME GROUPS
do
echo "************************************" >> /tmp/lsvg.out ;PUT A START MARKER
echo VG INFORMATION FOR $x >> /tmp/lsvg.out
lsvg -p $x >> /tmp/lsvg.out ;COLLECT INFO ABOUT DRIVES
lsvg -l $x >> /tmp/lsvg.out ;COLLECT INFO ABOUT LV
lsvg $x >> /tmp/lsvg.out ;COLLECT DETAIL INFO ABOUT VG
echo "************************************" >> /tmp/lsvg.out
done
for x in $(lspv|awk ‘{print $1}’) ;SELECT ALL PHYSICAL VOLUME
do
echo"************************************" >> /tmp/lspv.out
lspv $x >> /tmp/lspv.out ;STORE THE PV INFORMATION
lspv –l $x >> /tmp/lspv.out
echo"************************************" >> /tmp/lspv.out
done
Posted by Shivakant Tiwari at 4:04 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, collecting all the vg and pv info using shell script, COllecting vg and pv info off all the machines using shell script
TO CUT REQUIRED LOG FROM A LARGE LOG FILE
TO CUT REQUIRED LOG FROM A LARGE LOG FILE
In the script “mm” “dd” “yy” is month date and year respectively , this script is useful if a logfile has large content of everyday logs and we have to fetch log of a specific date for a specific host or string
for x in hostname1 hostname2 hostname3 ...
do
cat <logfile name>|awk '/"mm"\/"dd"\/"yy""/,/END/'|awk /"$x"/,/"<string for end"/
done
Posted by Shivakant Tiwari at 3:59 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, customizing log view in aix, shell script to cut a portion of log in aix
TAKING VIO BACKUP TO A REMOTE FILESYSTEM
TAKING VIO BACKUP TO A REMOTE FILESYSTEM
HN=`hostname`
LOGFILE="/home/padmin/bckvio.log"
EMAILADDR=xyz@abc.com
echo "GATHERING VIOS CONFIGURATION" > $LOGFILE
/home/padmin/gathervios.ksh >> $LOGFILE 2>&1
date >> $LOGFILE 2>&1
/usr/ios/cli/ioscli mount <remote machine>:/<remote path> /<local dir> >> $LOGFILE 2>&1
/usr/ios/cli/ioscli backupios -file /<local dir>/${HN}_mksysb -mksysb >> $LOGFILE 2>&1
if [[ $? -ne 0 ]]
then
mail -s "ERROR CREATING VIOS BACKUP" $EMAILADDR <<EOF
vio bachup for $HN has failed ! Please look into log /home/padmin/bckvio.log !
EOF
fi
/usr/ios/cli/ioscli unmount /<local dir> >> $LOGFILE 2>&1
Posted by Shivakant Tiwari at 3:56 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, TAKING VIO BACKUP TO A REMOTE FILESYSTEM, VIO BACKUP USING SCRIPT
COLLECT ALL THE INFORMATION OF A CHILD DEVICE COMING FROM A FC ADAPTER
COLLECT ALL THE INFORMATION OF A CHILD DEVICE COMING FROM A FC ADAPTER
lsdev -l $1
echo "PARENT DEVICE FOR ** $1 ***"
lsdev -l $1 -F parent
a=$(lsdev -l $1 -F parent)
echo "PARENT DEVICE FOR ** $a ** IS"
lsdev -l $(lsdev -l $1 -F parent) -F parent
b=$(lsdev -l $(lsdev -l $1 -F parent) -F parent)
echo "ALL THE CHILD DEVICES CONNECTED TO DEVICE ** $a **"
lsdev -p $(lsdev -l $1 -F parent)
echo "ALL THE CHILD DEVICES CONNECTED TO DEVICE ** $b **"
lsdev -p $(lsdev -l $(lsdev -l $1 -F parent) -F parent)
fc=$(echo $b|grep -e fcs0 -e fcs1 -e fcs2 -e fcs4 -e fcs5)
ck=${#fc}
if [ $ck -eq 0 ]
then
echo "BACKUP ADAPTER IS NOT FC"
exit
else
echo "PLEASE WAIT WHILE COLLECTING FC COMMUNICATION"
for x in $fc
do
c=5
echo "DATA TRANSFER FOR ** $x ** "
while [ $c -gt 0 ]
do
fcstat $x|awk '/Transmit/,/Words/'
sleep 10
c=$(($c-1))
done
done
fi
Posted by Shivakant Tiwari at 3:54 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, collecting fc information . troubleshooting a device coming from a fc
COLLECTING MICROCODE INFORMATION
COLLECTING MICROCODE INFORMATION
###### THIS SCRIPT COLLECTS INFORMATION ###########
############# AND HOST LISTS ARE IN FILE HOST.LST###########
exportfs –i /suptools
for x in $(cat /home/aixadmin/host.lst)
do
echo $x >> /suptools/coldata.out
ssh $x ls -lasd /suptools
if [ $? == 0 ]
then
ssh $x mount -o rw <local_machine>:/suptools /suptools
echo "************************************************8" >> /suptools/coldata.out
ssh $x /suptools/./coldata >> /suptools/coldata.out
ssh $x umount /suptools
echo "************************************************8" >> /suptools/coldata.out
else
ssh $x mkdir /suptools
ssh $x mount -o rw <local_machine>:/suptools /suptools
echo "************************************************8" >> /suptools/coldata.out
ssh $x /suptools/./coldata >> /suptools/coldata.out
ssh $x umount /suptools
echo "************************************************8" >> /suptools/coldata.out
fi
done
CONTENTS OF coldata
hostname >> /suptools/coldata.out
oslevel -s >> /suptools/coldata.out
lsmcode -r >> /suptools/coldata.out
for dv in $(lsdev -Cc adapter|awk '{print $1}'|grep -e ent -e fcs -e sisscsi)
do
echo $dv >> /suptools/coldata.out
lsmcode -r -d $dv >> /suptools/coldata.out
done
#
Posted by Shivakant Tiwari at 3:52 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, SHELL SCRIPT TO COLLECT MICROCODE INFORMATION
CREATING A USER IN AIX
CREATING A USER
#############################################################
############ THIS WILL ASK UID AND USER NAME #################
############AND WILL CREATE USER NAME ON THE SERVERS #############
##### LISTED IN THE FILE "xyz" ########
echo enter user-id followed by user name for eg 30 username
read uid usd
#echo enter password to reset for the user $usd
for x in $(cat xyz)
do
echo creating user $usd on host $x
ssh $x mkuser id=$uid $usd
done
exportfs -i /exportfilesystem
echo enter password to reset for the user $usd
read pas
echo "echo $usd:$pas|chpasswd" > /exportfilesystem/passet.sh
chmod +x /exportfilesystem/passet.sh
for x in $(cat xyz)
do
ssh $x mkdir /exportfilesystem
ssh $x mount current_server:/exportfilesystem /exportfilesystem
ssh $x /exportfilesystem/passet.sh
ssh $x umount /exportfilesystem
done
Posted by Shivakant Tiwari at 3:48 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, creating user in aix on all the servers, script to create user in aix
RESETTING A USER LOCKED PASSWD
RESETTING A USER LOCKED PASSWD
echo enter user name to reset
read usd
echo this will reset user $usd locked password
chsec -f /etc/security/lastlog -a "unsuccessful_login_count=0" -s $usd
chuser "account_locked=false" $usd
echo $usd:test@1234|chpasspw
Posted by Shivakant Tiwari at 3:45 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: .RESETTING A USER LOCKED PASSWD IN AIX, AIX SHELL SCRIPTS
FINDS OUT FILE SYSTEM UTILIZATION
FINDS OUT FILE SYSTEM UTILIZATION
THIS SCRIPT FINDS AND TELLS YOU WHICH FILE SYSTEM ARE UTILIZING SPACE BOVE THAN THRESHOLD SET BY YOU
h=$(hostname)
df -gt |grep -v Filesystem|grep -v proc|while read out
do
fs=$(echo $out|awk '{print $5 }'|cut -f1 -d%)
if [ "$fs" -gt 90 ]; then
echo "***********************************"
echo FILE SYSTEM LARGER THAN 90% ON $h ARE
echo $out
echo "***********************************"
fi
done
Posted by Shivakant Tiwari at 2:24 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, file system utilization alert in aix, how to find out file system utilization, shell script to monitor aix file system utilization
GETTING PORT ADDRESS FOR SERVICES
GETTING PORT ADDRESS FOR SERVICES
THIS SCRIPT CALCULATES AND SHOWS WHICH PORT IS USED BY WHICH SERVICE ,VERY IMPORTANT SCRIPT FOR ALL AIX ADMINISTRATORS
for x in $(netstat -Aan|grep LISTEN|awk '{print $1}')
do
a=$(netstat -Aan|grep LISTEN|grep $x|awk '{print $5}'|cut -f2 -d .)
b=$(rmsock $x tcpcb|awk '{print $9}')
echo PORT $a is used by
ps -ef |grep $b
done
Posted by Shivakant Tiwari at 2:22 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: aix port used by services, AIX SHELL SCRIPTS, how to get port address of services, which service is using which port in aix
FINDING USER’S PASSORD EXPIRE DATE
SCRIPT 1 – FINDING USER’S PASSORD EXPIRE DATE
############################################################################
# THIS SCRIPT WILL ASK A USER NAME AND TELL WHEN ITS PASSWORD WILL EXPIRE
#I HAD NOT MADE IT VERY SMOOTH BUT STILL IT SOLVES A VERY BIG THING
################################################################################
echo enter user name ; PROVIDE THE USER NAME
read uame
lstup=$(pwdadm -q $uame|grep -e lastupdate|cut -f2 -d=)
echo LAST PASSWORD UPDATED FOR USER $uame ON >> /tmp/pwexp.out
echo $lstup| perl -e 'print localtime(<>) . "\n";' >> /tmp/pwexp.out
mxag=$(lsuser -a maxage $uame|cut -f2 -d=)
pwexp=$(expr 604800 \* $mxag)
pwexp=$(($lstup + $pwexp))
echo PASSWORD EXPIRE DATE FOR USER $uame >> /tmp/pwexp.out
echo $pwexp| perl -e 'print localtime(<>) . "\n";' >> /tmp/pwexp.out
cat /tmp/pwexp.out ;THE OUTPUT IS STORED IN pwexp.out FILE
Posted by Shivakant Tiwari at 2:20 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX SHELL SCRIPTS, aix user password expire, finding users FINDING USER’S PASSORD EXPIRE DATE in aix
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)
TOTAL PAGEVIEWS
10,053
Your Ad Here
FEEDJIT
Your Ad Here
MONDAY, MAY 9, 2011
VIEWING INFORMATION OF LPAR FROM HMC - SOME EXAMPLES
TO VIEW ALL THE MANAGED SERVER CONNECTED TO THE HMC
hscroot@localhost:~> lssyscfg -r lpar -m PRIMARY-Servers-
9117-570 -F name
PRIMARY-SERVER
SECONDARY-SERVER
65-095FE
TO VIEW ALL THE LPAR IN A MANAGED SERVER
hscroot@localhost:~> lssyscfg -r lpar -m Server-8204-E8A -F name
SERVER-2
SERVER-1
VIOSERVER
SCRIPT TO FIND MANAGED SERVER TO WHICH MY LPAR BELONGS
For x in $( lssyscfg -r lpar -m PRIMARY-Servers-9117-570 -F name)
Do
Echo $x
lssyscfg -r lpar -m $x -F name
done
TO VIEW ALL THE IO UNITS IN MANAGED SERVER
hscroot@localhost:~> lshwres -r io --rsubtype unit -m Server-8204-E8A -F
U5796.001.0601894
U78A0.001.DNWGYKN
TO VIEW ALL THE IO BUS IN MANAGED SERVER
hscroot@localhost:~> lshwres -r io --rsubtype bus -m Server-8204-E8A -F --header
unit_phys_loc,bus_id,backplane_phys_loc,bus_drc_index,bus_drc_name
U5796.001.0601894,288,U5796.001.0601894-P1,20000120,PHB 288
U5796.001.0601894,289,U5796.001.0601894-P1,20000121,PHB 289
U5796.001.0601894,290,U5796.001.0601894-P1,20000122,PHB 290
U5796.001.0601894,292,U5796.001.0601894-P1,20000124,PHB 292
U5796.001.0601894,293,U5796.001.0601894-P1,20000125,PHB 293
U5796.001.0601894,294,U5796.001.0601894-P1,20000126,PHB 294
U78A0.001.DNWGYKN,512,U78A0.001.DNWGYKN-P1,20000200,PHB 512
U78A0.001.DNWGYKN,513,U78A0.001.DNWGYKN-P1,20000201,PHB 513
U78A0.001.DNWGYKN,514,U78A0.001.DNWGYKN-P1,20000202,PHB 514
U78A0.001.DNWGYKN,515,U78A0.001.DNWGYKN-P1,20000203,PHB 515
U78A0.001.DNWGYKN,516,U78A0.001.DNWGYKN-P1,20000204,PHB 516
U78A0.001.DNWGYKN,517,U78A0.001.DNWGYKN-P1,20000205,PHB 517
U78A0.001.DNWGYKN,518,U78A0.001.DNWGYKN-P1,20000206,PHB 518
U78A0.001.DNWGYKN,519,U78A0.001.DNWGYKN-P1,20000207,PHB 519
TO VIEW ALL THE IO SLOTS IN MANAGED SERVER
hscroot@localhost:~> lshwres -r io --rsubtype slot -m Server-8204-E8A -F unit_phys_loc,bus_id
,phys_loc,drc_index,lpar_name,lpar_id,description,feature_codes,vpd_type,vpd_model --header
unit_phys_loc,bus_id,phys_loc,drc_index,lpar_name,lpar_id,description,feature_codes,vpd_type,vpd_model
U5796.001.0601894,288,C1,21010120,null,none,RAID Controller,none,null,null
U5796.001.0601894,289,C2,21010121,VIOSERVER,2,Ethernet controller,none,null,null
U5796.001.0601894,290,C3,21010122,SERVER-1,3,Ethernet controller,none,null,null
U5796.001.0601894,292,C4,21010124,VIOSERVER,2,SCSI bus controller,none,null,null
U5796.001.0601894,293,C5,21010125,SERVER-2,4,Ethernet controller,none,null,null
U5796.001.0601894,294,C6,21010126,null,none,Empty slot,"0,0,0",null,null
U78A0.001.DNWGYKN,512,T9,21010200,VIOSERVER,2,RAID Controller,none,null,null
U78A0.001.DNWGYKN,513,T3,21010201,null,none,Universal Serial Bus UHC Spec,none,null,null
U78A0.001.DNWGYKN,514,C4,21010202,SERVER-2,4,4 GB Single-Port Fibre Channel PCI-X 2.0 DDR Adapter,"5758,5758,5758",null,null
U78A0.001.DNWGYKN,515,C5,21010203,SERVER-2,4,4 GB Single-Port Fibre Channel PCI-X 2.0 DDR Adapter,"5758,5758,5758",null,null
U78A0.001.DNWGYKN,516,C1,21010204,null,none,Empty slot,"0,0,0",null,null
U78A0.001.DNWGYKN,517,C2,21010205,SERVER-1,3,4 Gigabit PCI Express Single Port Fibre Channel Adapter,"5773,5773,5773",null,null
U78A0.001.DNWGYKN,518,C10,21010206,null,none,Empty slot,"0,0,0",null,null
U78A0.001.DNWGYKN,519,C3,21010207,SERVER-1,3,4 Gigabit PCI Express Single Port Fibre Channel Adapter,"5773,5773,5773",null,null
TO VIEW ALL THE VIRTUAL ETHERNET IN MANAGED SERVER
hscroot@localhost:~> lshwres -r virtualio --rsubtype eth -m Server-8204-E8A--level lpar -F –header
lpar_name,lpar_id,slot_num,state,is_required,is_trunk,trunk_priority,ieee_virtual_eth,port_vlan_id,addl_vlan_ids,mac_addr,connect_status,drc_name,shared_adapter,backing_device,device_name
VIOSERVER,2,12,1,0,1,1,0,1,,BE164625C70C,active,U8204.E8A.06D4552-V2-C12-T1,ent4,ent0,ent2
VIOSERVER,2,13,1,0,1,1,0,2,,BE164625C70D,none,U8204.E8A.06D4552-V2-C13-T1,,,ent3
SERVER-2,4,3,1,0,0,unavailable,0,1,,BE1649F95103,active,U8204.E8A.06D4552-V4-C3-T1,,,ent2
TO VIEW ALL THE VIRTUAL FIBRE CHANNEL IN MANAGED SERVER
hscroot@localhost:~> lshwres -r virtualio --rsubtype fc -m Server-8204-E8A--level lpar -F –header
No results were found.
TO VIEW ALL THE VIRTUAL SCSI IN MANAGED SERVER
hscroot@localhost:~> lshwres -r virtualio --rsubtype scsi -m Server-8204-E8A--level lpar -F –header
lpar_name,lpar_id,slot_num,state,is_required,adapter_type,remote_lpar_id,remote_lpar_name,remote_slot_num,backing_devices,connect_status,backing_device,server_loc_code,active_loc_code,active_lpar_id,active_lpar_name,active_slot_num,remote_backing_device,topology
VIOSERVER,2,11,1,1,server,any,,any,null,active,"clientlv1,hdisk2,hdisk4,cd0",U8204.E8A.06D4552-V2-C11,U8204.E8A.06D4552-V3-C2-T1,3,SERVER-1,2,"hdisk0, hdisk1, hdisk2","///vhost0//clientlv1,///vhost0//hdisk2,///vhost0//hdisk4,///vhost0//cd0"
VIOSERVER,2,14,1,0,server,any,,any,null,active,"clientlv2,hdisk3,hdisk5",U8204.E8A.06D4552-V2-C14,U8204.E8A.06D4552-V4-C2-T1,4,SERVER-2,2,"hdisk0, hdisk1, hdisk2, hdisk20","///vhost1//clientlv2,///vhost1//hdisk3,///vhost1//hdisk5"
SERVER-1,3,2,1,1,client,2,VIOSERVER,11,null,active,"hdisk0, hdisk1, hdisk2",U8204.E8A.06D4552-V2-C11,U8204.E8A.06D4552-V3-C2-T1,2,VIOSERVER,11,"clientlv1,hdisk2,hdisk4,cd0","unavailable/unavailable/unavailable/vhost0//hdisk0,unavailable/unavailable/unavailable/vhost0//hdisk1,unavailable/unavailable/unavailable/vhost0//hdisk2"
SERVER-2,4,2,1,0,client,2,VIOSERVER,14,null,active,"hdisk0, hdisk1, hdisk2, hdisk20",U8204.E8A.06D4552-V2-C14,U8204.E8A.06D4552-V4-C2-T1,2,VIOSERVER,14,"clientlv2,hdisk3,hdisk5","unavailable/unavailable/unavailable/vhost1//hdisk0,unavailable/unavailable/unavailable/vhost1//hdisk1,unavailable/unavailable/unavailable/vhost1//hdisk2,unavailable/unavailable/unavailable/vhost1//hdisk20"
TO VIEW ALL THE VIRTUAL SCSI IN MANAGED SERVER (FILTERED VIEW)
hscroot@localhost:~> lshwres -r virtualio --rsubtype scsi -m Server-8204-E8A--level lpar –F lpar_name,lpar_id, lpar_name,lpar_id,slot_num,state,is_required,adapter_type,remote_lpar_id,remote_lpar_name,remote_slot_num,backing_devices,connect_status,backing_device,active_lpar_id,active_lpar_name -–header
lpar_name,lpar_id,slot_num,state,is_required,adapter_type,remote_lpar_id,remote_lpar_name,remote_slot_num,backing_devices,connect_status,backing_device,active_lpar_id,active_lpar_name
VIOSERVER,2,11,1,1,server,any,,any,"""0x8100000000000000,0x8200000000000000,0x8300000000000000,0x8400000000000000/,U78A0.001.DNWGYKN-P2-D3,U78A0.001.DNWGYKN-P2-D8,U78A0.001.DNWGYKN-P2-D2/clientlv1,hdisk2,hdisk4,cd0""",active,"clientlv1,hdisk2,hdisk4,cd0",3,SERVER-1
VIOSERVER,2,14,1,0,server,any,,any,"""0x8100000000000000,0x8300000000000000,0x8200000000000000/,U78A0.001.DNWGYKN-P2-D6,U78A0.001.DNWGYKN-P2-D7/clientlv2,hdisk3,hdisk5""",active,"clientlv2,hdisk3,hdisk5",4,SERVER-2
SERVER-1,3,2,1,1,client,2,VIOSERVER,11,null,active,"hdisk0, hdisk1, hdisk2",2,VIOSERVER
SERVER-2,4,2,1,0,client,2,VIOSERVER,14,null,active,"hdisk0, hdisk1, hdisk2, hdisk20",2,VIOSERVER
TO VIEW ALL THE MEMORY INFORMATION OF A MANAGED SERVER
hscroot@localhost:~> lshwres -r mem -m Server-8204-E8A--level sys -F --header
configurable_sys_mem,curr_avail_sys_mem,pend_avail_sys_mem,installed_sys_mem,max_capacity_sys_mem,deconfig_sys_mem,sys_firmware_mem,mem_region_size,configurable_num_sys_huge_pages,curr_avail_num_sys_huge_pages,pend_avail_num_sys_huge_pages,max_num_sys_huge_pages,requested_num_sys_huge_pages,huge_page_size,total_sys_bsr_arrays,bsr_array_size,curr_avail_sys_bsr_arrays,max_mem_pools
65536,2816,2816,65536,deprecated,0,3328,256,0,0,0,3,0,16384,16,8,16,0
TO VIEW ALL THE MEMORY INFORMATION OF A MANAGED SERVER AT LPAR LEVEL(FILTERED VIEW)
hscroot@localhost:~> lshwres -r mem -m Server-8204-E8A--level lpar -F --header
lpar_name,lpar_id,curr_min_mem,curr_mem,curr_max_mem,pend_min_mem,pend_mem,pend_max_mem,run_min_mem,run_mem,curr_min_num_huge_pages,curr_num_huge_pages,curr_max_num_huge_pages,pend_min_num_huge_pages,pend_num_huge_pages,pend_max_num_huge_pages,run_num_huge_pages,curr_bsr_arrays
SERVER-2,4,2048,28672,45056,2048,28672,45056,2048,28672,0,0,0,0,0,0,0,0
SERVER-1,3,4096,28672,45056,4096,28672,45056,4096,28672,0,0,0,0,0,0,0,0
VIOSERVER,2,1024,2048,4096,1024,2048,4096,1024,2048,0,0,0,0,0,0,0,0
TO VIEW ALL THE PROCESSOR INFORMATION OF A MANAGED SERVER
hscroot@localhost:~> lshwres -r proc -m Server-8204-E8A--level sys -F --header
configurable_sys_proc_units,curr_avail_sys_proc_units,pend_avail_sys_proc_units,installed_sys_proc_units,max_capacity_sys_proc_units,deconfig_sys_proc_units,min_proc_units_per_virtual_proc,max_virtual_procs_per_lpar,max_procs_per_lpar,max_shared_proc_pools
8.0,0.0,0.0,8.0,deprecated,0,0.1,64,64,64
TO VIEW ALL THE MEMORY INFORMATION OF A MANAGED SERVER AT LPAR LEVEL (FILTERED VIEW)
hscroot@localhost:~> lshwres -r mem -m Server-8204-E8A--level lpar –F lpar_name,lpar_id,curr_min_mem,curr_mem
,curr_max_mem,run_mem --header
lpar_name,lpar_id,curr_min_mem,curr_mem,curr_max_mem,run_mem
SERVER-2,4,2048,28672,45056,28672
SERVER-1,3,4096,28672,45056,28672
VIOSERVER,2,1024,2048,4096,2048
TO VIEW ALL THE PROCESSOR INFORMATION OF A MANAGED SERVER AT LPAR LEVEL
hscroot@localhost:~> lshwres -r proc -m Server-8204-E8A--level lpar -F --header
lpar_name,lpar_id,curr_shared_proc_pool_id,curr_shared_proc_pool_name,curr_proc_mode,curr_min_proc_units,curr_proc_units,curr_max_proc_units,curr_min_procs,curr_procs,curr_max_procs,curr_sharing_mode,curr_uncap_weight,pend_shared_proc_pool_id,pend_shared_proc_pool_name,pend_proc_mode,pend_min_proc_units,pend_proc_units,pend_max_proc_units,pend_min_procs,pend_procs,pend_max_procs,pend_sharing_mode,pend_uncap_weight,run_proc_units,run_procs,run_uncap_weight
SERVER-2,4,0,DefaultPool,shared,2.0,4.0,6.0,2,4,6,uncap,
128,0,DefaultPool,shared,2.0,4.0,6.0,2,4,6,uncap,128,4.0,4,128
SERVER-1,3,0,DefaultPool,shared,1.0,3.8,6.0,1,4,6,uncap,
128,0,DefaultPool,shared,1.0,3.8,6.0,1,4,6,uncap,128,3.8,4,128
VIOSERVER,2,0,DefaultPool,shared,0.1,0.2,0.4,1,1,1,cap,0,0,DefaultPool,shared,0.1,0.2,0.4,1,1,1,cap,0,0.2,1,0
TO VIEW ALL THE PROCESSOR INFORMATION OF A MANAGED SERVER AT LPAR LEVEL(FILTERED VIEW)
hscroot@localhost:~> lshwres -r proc -m Server-8204-E8A--level lpar -F lpar_name,lpar_id,curr_proc_mode,
curr_min_proc_units,curr_proc_units,curr_max_proc_units,curr_min_procs,curr_procs,curr_max_procs,curr_sharing_mode,curr_uncap_weight,run_proc_units,run_procs,run_uncap_weight –header
lpar_name,lpar_id,curr_proc_mode,curr_min_proc_units,curr_proc_units,curr_max_proc_units,curr_min_procs,curr_procs,curr_max_procs,curr_sharing_mode,curr_uncap_weight,run_proc_units,run_procs,run_uncap_weight
SERVER-2,4,shared,2.0,4.0,6.0,2,4,6,uncap,128,4.0,4,128
SERVER-1,3,shared,1.0,3.8,6.0,1,4,6,uncap,128,3.8,4,128
VIOSERVER,2,shared,0.1,0.2,0.4,1,1,1,cap,0,0.2,1,0
Posted by Shivakant Tiwari at 5:34 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX VIRTUALIZATION, lshwres -r virtualio, lssyscfg, min desired maximum value throug command line, min maximum memory through command line, rsubtype unit
MONDAY, APRIL 18, 2011
TO MOVE A RESOURCE FROM ONE LPAR TO ANOTHER LPAR
Select lpar on which you have to to do DLPAR operation
select tasks or (the arrow besides the lpar)
Select dynamic logical partitioning > resource to move(for example here processor) select move
In the coming window select destination partition (the partition to which we want to move resources)
Select the amount of resource to move
PUT THE AMOUNT OF RESOURCES TO BE MOVED AND SELECT THE DESTINATION PARTITION
TO MOVE MEMORY RESOURCES
select tasks or (the arrow besides the lpar)
Select dynamic logical partitioning > resource to move(for example here memory ) select move
As in the screen above
Now you will be presented the screen below
Write the amount of memory resource to move
Select Destination Lpar and click on ok
TO MOVE I/O RESOURCES
Select the adapter (there are no removable adapter in the screen shot below )
By clicking ok after selecting the adapter you will remove the adapter from the lpar selected
select destination lpar from the option to move the adapter to the destination LPAR
select tasks or (the arrow besides the lpar)
Select dynamic logical partitioning > resource to move(for example here adapter ) select move
As in the screen above
Posted by Shivakant Tiwari at 3:16 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX VIRTUALIZATION, DLPAR RESOURCES, TO MOVE A RESOURCE FROM ONE LPAR TO ANOTHER LPAR, TO MOVE I/O RESOURCES, TO MOVE MEMORY RESOURCES
MONDAY, MARCH 28, 2011
INSTALLING VIO SERVER
IBM VIRTUAL I/O SERVER
The Virtual I/O Server is part of the eServer p5 Advanced Power Virtualization hardware
feature. Virtual I/O Server allows sharing of physical resources between LPARs including virtual
SCSI and virtual networking. This allows more efficient utilization of physical resources through
sharing between LPARs and facilitates server consolidation.
INSTALLATION
You have two options to install the AIX-based VIO Server:
1. Install from CD
2. Install from network via an AIX NIM-Server
Installation method #1 is probably the more frequently used method in a pure Linux
environment as installation method #2 requires the presence of an AIX NIM (Network
Installation Management) server. Both methods differ only in the initial boot step and are then
the same. They both lead to the following installation screen:
Elapsed time since release of system processors: 51910 mins 20 secs
-------------------------------------------------------------------------------
Welcome to the Virtual I/O Server.
boot image timestamp: 10:22 03/23
The current time and date: 17:23:47 08/10/2005
number of processors: 1 size of memory: 2048MB
boot device: /pci@800000020000002/pci@2,3/ide@1/disk@0:\ppc\chrp\bootfile.exe
SPLPAR info: entitled_capacity: 50 platcpus_active: 2
This system is SMT enabled: smt_status: 00000007; smt_threads: 2
kernel size: 10481246; 32 bit kernel
-------------------------------------------------------------------------------
The next step then is to define the system console. After some time you should see the
following screen:
******* Please define the System Console. *******
Type a 1 and press Enter to use this terminal as the
system console.
Pour definir ce terminal comme console systeme, appuyez
sur 1 puis sur Entree.
Taste 1 und anschliessend die Eingabetaste drücken, um
diese Datenstation als Systemkonsole zu verwenden.
Premere il tasto 1 ed Invio per usare questo terminal
come console.
88 Help ?
This is the main installation menu of the AIX-based VIO-Server:
Welcome to Base Operating System
Installation and Maintenance
Type the number of your choice and press Enter. Choice is indicated by >>>.
>>> 1 Start Install Now with Default Settings
2 Change/Show Installation Settings and Install
3 Start Maintenance Mode for System Recovery
88 Help ?
99 Previous Menu
>>> Choice [1]:
System Backup Installation and Settings
Either type 0 and press Enter to install with the current settings, or type the
number of the setting you want to change and press Enter.
Setting: Current Choice(s):
1 Disk(s) where you want to install ...... hdisk0
Use Maps............................. No
2 Shrink File Systems..................... No
3 Import User Volume Groups............... No
4 Recover Devices......................... No
>>> 0 Install with the settings listed above.
+-----------------------------------------------------
88 Help ? | WARNING: Base Operating System Installation will
99 Previous Menu | destroy or impair recovery of ALL data on the
| destination disk hdisk0.
>>> Choice [0]:
Selection of disks:
Change Disk(s) Where You Want to Install
Type one or more numbers for the disk(s) to be used for installation and press
Enter. To cancel a choice, type the corresponding number and Press Enter.
At least one bootable disk must be selected. The current choice is indicated
by >>>.
Name Location Code Size(MB) VG Status Bootable Maps
>>> 1 hdisk0 03-08-00-3,0 70006 none Yes No
2 hdisk1 03-08-00-4,0 70006 none Yes No
3 hdisk2 03-08-00-5,0 70006 none Yes No
4 hdisk3 03-08-00-8,0 70006 none Yes No
>>> 0 Continue with choices indicated above
55 More Disk Options
66 Devices not known to Base Operating System Installation
77 Display More Disk Information
88 Help ?
99 Previous Menu
>>> Choice [0]:
Now start the installation.
Installing Base Operating System
Please wait...
Approximate Elapsed time
% tasks complete (in minutes)
8 0 1% of mksysb data restored.
-------------------------------------------------------------------------------
Welcome to the Virtual I/O Server.
boot image timestamp: 17:44 08/10
The current time and date: 17:46:01 08/10/2005
number of processors: 1 size of memory: 2048MB
boot device: /pci@800000020000002/pci@2,4/pci1069,b166@1/scsi@0/sd@3:2
SPLPAR info: entitled_capacity: 50 platcpus_active: 2
This system is SMT enabled: smt_status: 00000007; smt_threads: 2
kernel size: 12405120; 64 bit kernel
-------------------------------------------------------------------------------
Saving Base Customize Data to boot disk
Starting the sync daemon
Starting the error daemon
System initialization completed.
Setting tunable parameters...complete
Starting Multi-user Initialization
Performing auto-varyon of Volume Groups
Activating all paging spaces
0517-075 swapon: Paging device /dev/hd6 is already active.
swapon: Paging device /dev/paging00 activated.
The current volume is: /dev/hd1
Primary superblock is valid.
The current volume is: /dev/hd10opt
Primary superblock is valid.
Performing all automatic mounts
Multi-user initialization completed
System reconfiguration in progress. Please wait.
Rebuild of Scriptinfo file is complete
Checking for srcmstr active...complete
Starting tcpip daemons:
0513-059 The syslogd Subsystem has been started. Subsystem PID is 217224.
Aug 10 12:46:40 localhost syslog:err|error syslogd: /tmp/syslog.out: errno = 2
0513-059 The sendmail Subsystem has been started. Subsystem PID is 180374.
0513-059 The portmap Subsystem has been started. Subsystem PID is 69844.
0513-059 The inetd Subsystem has been started. Subsystem PID is 118936.
0513-059 The snmpd Subsystem has been started. Subsystem PID is 184462.
0513-059 The hostmibd Subsystem has been started. Subsystem PID is 131306.
0513-059 The snmpmibd Subsystem has been started. Subsystem PID is 172216.
0513-059 The aixmibd Subsystem has been started. Subsystem PID is 204952.
0513-059 The muxatmd Subsystem has been started. Subsystem PID is 164006.
Finished starting tcpip daemons.
Starting NFS services:
0513-059 The biod Subsystem has been started. Subsystem PID is 176302.
0513-059 The rpc.lockd Subsystem has been started. Subsystem PID is 262390.
0513-059 The ctrmc Subsystem has been started. Subsystem PID is 229540.
Completed NFS services.
IBM Virtual I/O Server
login:
3 Initial setup
After the reboot you are presented with the VIO-Server login prompt. You can't login
as user root as you have to use the special user id padmin. No initial default
password is set. Immediately after login you are forced to set a new password.
[compat]: 3004-610 You are required to change your password.
Please choose a new one.
padmin's New password:
Enter the new password again:
The following file has been updated: .profile
Changes will take affect at next login.
Before you can do anything you have to accept the I/O Server license. This is done with the
license command.
$ lsmap
The I/O Server license must be accepted before running this command.
Only the chlang command may be run before accepting the license.
To view the license, run the license command with the -view option.
If the -lang flag is not specified the license will by displayed in
the current locale (set by the chlang command). If the license is not
available in the language selected, English will be the default.
To accept the license, run the license command with the -accept option.
Locale currently set to: "en_US".
Usage: license [-view] [-accept] [-lang Name]
license [-ls]
View and accept the I/O Server license agreement.
-accept Accept the license agreement.
-lang Specifies the language-territory (locale name) the license
is displayed in.
-ls Lists available locales.
-view Displays the license agreement.
Please enter:
license -accept
Before you start to define and assign resources please make sure you have the latest version and
updates installed before you proceed. Updates and support for the AIX-based Virtual I/O Server
Details beyond the scope of this publications can be found in the following Redbook
Advanced POWER Virtualization on eServer p5 Servers: Introduction and Basic
Once you are logged in as user padmin you find yourself in a restricted Korn shell with only a
limited set of commands. You can see all available commands with the command help. All these
commands are shell aliases to a single SUID-binary called ioscli which is located in the directory
/usr/ios/cli/bin. If you are familiar with AIX you will recognize most commands but most
command line parameters differ from the AIX versions.
Asking help in vio
As there are no man pages available you can see all options for each command separately by
issueing the command help . Here is an example for the command lsmap:
$ help lsmap
Usage: lsmap {-vadapter ServerVirtualAdapter | -plc PhysicalLocationCode |
-all}
[-net] [-fmt delimiter]
Displays the mapping between physical and virtual devices.
-all Displays mapping for all the server virtual adapter
devices.
-vadapter Specifies the server virtual adapter device
by device name.
-plc Specifies the server virtual adapter device
by physical location code.
-net Specifies supplied device is a virtual server
Ethernet adapter.
-fmt Divides output by a user-specified delimiter.
A very important command is oem_setup_env which gives you access to the regular AIX
command line interface. This is provided solely for the installation of OEM device drivers.
4 VIRTUAL SCSI SETUP
To map a LV
• mkvg: creates the volume group, where a new LV will be created using the mklv
command
• lsdev: shows the virtual SCSI server adapters that could be used for mapping with the LV
• mkvdev: maps the virtual SCSI server adapter to the LV
• lsmap -all: shows the mapping information
To map a physical disk
• lsdev: shows the virtual SCSI server adapters that could be used for mapping with a
physical disk
• mkvdev: maps the virtual SCSI server adapter to a physical disk
• lsmap -all: shows the mapping information
Client partition commands
• No commands needed, the Linux kernel is notified immediately
Create new volume group datavg with member disk hdisk1
• mkvg -vg datavg hdisk1
Create new logical volume vdisk0 in volume group
• mklv -lv vdisk0 datavg 10G
Maps the virtual SCSI server adapter to the logical volume
• mkvdev -vdev vdisk0 -vadapter vhost0
Display the mapping information
• lsmap -all
5 VIRTUAL ETHERNET SETUP
To list all virtual and physical adapters use the lsdev -type adapter command.
$ lsdev -type adapter
name status description
ent0 Available 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
ent1 Available 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
ent2 Available Virtual I/O Ethernet Adapter (l-lan)
ide0 Available ATA/IDE Controller Device
sisscsia0 Available PCI-X Dual Channel Ultra320 SCSI Adapter
vhost0 Available Virtual SCSI Server Adapter
vhost1 Available Virtual SCSI Server Adapter
vhost2 Available Virtual SCSI Server Adapter
vhost3 Available Virtual SCSI Server Adapter
vsa0 Available LPAR Virtual Serial Adapter
Choose the virtual Ethernet adapter we want to map to the physical Ethernet adapter.
$ lsdev -virtual
name status description
ent2 Available Virtual I/O Ethernet Adapter (l-lan)
vhost0 Available Virtual SCSI Server Adapter
vhost1 Available Virtual SCSI Server Adapter
vhost2 Available Virtual SCSI Server Adapter
vhost3 Available Virtual SCSI Server Adapter
vsa0 Available LPAR Virtual Serial Adapter
The command mkvdev maps a physical adapter to a virtual adapter, creates a layer 2 network
bridge and defines the default virtual adapter with its default VLAN ID. It creates a new
Ethernet interface, e.g., ent3.
Make sure the physical and virtual interfaces are unconfigured (down or detached).
6 SCENARIO A (ONE VIO SERVER)
Create a shared ethernet adapter ent3 with a physical one (ent0) and a virtual one (ent2)
with PVID 1:
$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1
ent3 Available
en3
et3
This has created a new shared ethernet adapter ent3 (you can verify that with the lsdev
command). Now configure the TCP/IP settings for this new shared ethernet adapter (ent3).
Please note that you have to specify the interface (en3) and not the adapter (ent3).
$ mktcpip -hostname op710-1-vio -inetaddr 9.156.175.231 -interface en3 \
-netmask 255.255.255.0 -gateway 9.156.175.1 -nsrvaddr 9.64.163.21 \
-nsrvdomain munich.de.ibm.com
7 SCENARIO B (TWO VIO SERVERS)
Create a shared ethernet adapter ent3 with a physical one (ent0) and a virtual one (ent2)
with PVID 1:
mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1
Configure the TCP/IP settings for the new shared ethernet adapter (ent3):
mktcpip -hostname op710-1-vio -inetaddr 9.156.175.231 -interface en3 \
-netmask 255.255.255.0 -gateway 9.156.175.1 -nsrvaddr 9.64.163.21 \
-nsrvdomain munich.de.ibm.com
INSTALLING FROM HMC
mksysb backup but a full one that creates theinstallios command.
hscroot@server1:~> installios
The following objects of type "managed system" were found. Please select one:
1. p570-ITSO
Enter a number: 1
The following objects of type "virtual I/O server partition" were found. Please
select one:
1. VIOS_DR_MACHINE
2. VIO_Server1
Enter a number (1-2): 1
The following objects of type "profile" were found. Please select one:
1. normal
Enter a number: 1
Enter the source of the installation images [/dev/cdrom]:
server5:/export/ios_backup/
Enter the client's intended IP address: 10.1.1.123
Enter the client's intended subnet mask: 255.255.255.0
Enter the client's gateway: 9.3.5.41
Enter the client's speed [100]:auto
Enter the client's duplex [full]:auto
Would you like to configure the client's network after the
installation [yes]/no? no
Note: If the CD or DVD backup spanned multiple disks, during the install, you will be
prompted to insert the next disk in the set with a similar message to the following message:
Please remove volume 1, insert volume 2, and press the ENTER key.
Note: The trailing slash in the NFS location server5:/export/ios_backup/ must be included
in the command as shown.
The configure client network setting must be set to no as shown. This is because the
physical adapter we are installing the backup through might already be used by an SEA
and the IP configuration will fail if this is the case. Log in and configure the IP if necessary
after the installation using a console session.
Retrieving information for available network adapters
This will take several minutes...
The following objects of type "Ethernet adapters" were found. Please select one:
1. ent U9117.570.107CD9E-V2-C2-T1 523300002002
2. ent U7311.D20.10832BA-P1-C01-T1 00096b6e8458
3. ent U7311.D20.10832BA-P1-C01-T2 00096b6e8459
Enter a number (1-3): 2
Here are the values you entered:
managed system = p570-ITSO
virtual I/O server partition = VIOS_DR_MACHINE
profile = normal
source = server5:/export/ios_backup/
IP address = 9.3.5.123
subnet mask = 255.255.255.0
gateway = 9.3.5.41
speed = 100
duplex = full
configure network = no
ethernet adapters = 00:09:6b:6e:84:58
Press enter to proceed or type Ctrl-C to cancel...
nimol_config MESSAGE: No NIMOL server hostname specified, using
server1.itsc.austin.ibm.com as the default.
Starting RPC portmap daemon
done
Starting kernel based NFS server
done
nimol_config MESSAGE: Added "REMOTE_ACCESS_METHOD /usr/bin/rsh" to the file
"/etc/nimol.conf"
nimol_config MESSAGE: Removed "disable = yes" from the file "/etc/xinetd.d/tftp"
nimol_config MESSAGE: Added "disable = no" to the file "/etc/xinetd.d/tftp"
Shutting down xinetd:
done
Starting INET services. (xinetd)
done
nimol_config MESSAGE: Removed "SYSLOGD_PARAMS=" from the file
"/etc/sysconfig/syslog"
nimol_config MESSAGE: Added "SYSLOGD_PARAMS=-r " to the file
"/etc/sysconfig/syslog"
nimol_config MESSAGE: Removed "local2,local3.* -/var/log/localmessages" from the
file "/etc/syslog.conf"
nimol_config MESSAGE: Added "local3.* -/var/log/localmessages" to the file
"/etc/syslog.conf"
nimol_config MESSAGE: Added "local2.* /var/log/nimol.log" to the file
"/etc/syslog.conf"
Shutting down syslog services
done
Starting syslog services
done
nimol_config MESSAGE: Executed /usr/sbin/nimol_bootreplyd -l -d -f /etc/nimoltab
-s server1.itsc.austin.ibm.com.
nimol_config MESSAGE: Successfully configured NIMOL.
nimol_config MESSAGE: target directory: /info/default5
nimol_config MESSAGE: Executed /usr/sbin/iptables -I INPUT 1 -s server5 -j ACCEPT.
nimol_config MESSAGE: source directory: /mnt/nimol
Chapter 2. Administration, backup, and restore 29
nimol_config MESSAGE: Checking /mnt/nimol/nim_resources.tar for existing
resources.
nimol_config MESSAGE: Executed /usr/sbin/iptables -D INPUT -s server5 -j ACCEPT.
nimol_config MESSAGE: Added "/info/default5 *(rw,insecure,no_root_squash)" to the
file "/etc/exports"
nimol_config MESSAGE: Successfully created "default5".
nimol_install MESSAGE: The hostname "lpar11.itsc.austin.ibm.com" will be used.
nimol_install MESSAGE: Added "CLIENT lpar11.itsc.austin.ibm.com" to the file
"/etc/nimol.conf"
nimol_install MESSAGE: Added
"lpar11.itsc.austin.ibm.com:ip=9.3.5.123:ht=ethernet:gw=9.3.5.41:sm=255.255.255.0:
bf=lpar11.itsc.austin.ibm.com:sa=9.3.5.194:ha=00096b6e8458" to the file
"/etc/nimoltab"
nimol_install MESSAGE: Executed kill -HUP 5149.
nimol_install MESSAGE: Created /tftpboot/lpar11.itsc.austin.ibm.com.
nimol_install MESSAGE: Executed /sbin/arp -s lpar11.itsc.austin.ibm.com
00:09:6b:6e:84:58 -t ether.
nimol_install MESSAGE: Executed /usr/sbin/iptables -I INPUT 1 -s
lpar11.itsc.austin.ibm.com -j ACCEPT.
nimol_install MESSAGE: Created
/info/default5/scripts/lpar11.itsc.austin.ibm.com.script.
nimol_install MESSAGE: Created /tftpboot/lpar11.itsc.austin.ibm.com.info.
nimol_install MESSAGE: Successfully setup lpar11.itsc.austin.ibm.com for a NIMOL
install
# Connecting to VIOS_DR_MACHINE
# Connected
# Checking for power off.
# Power off complete.
# Power on VIOS_DR_MACHINE to Open Firmware.
# Power on complete.
# Client IP address is 9.3.5.123.
# Server IP address is 9.3.5.194.
# Gateway IP address is 9.3.5.41.
# /pci@800000020000011/pci@2/ethernet@1 ping successful.
# Network booting install adapter.
# bootp sent over network.
# Network boot proceeding, lpar_netboot is exiting.
# Finished.
IT can be installed from full backup (not a
nim_resources.tar file), you can use the HMC to install these using the
Posted by Shivakant Tiwari at 2:54 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX VIRTUALIZATION, DLPAR/VIO, INSTALLING VIO SERVER, INSTALLING VIO SERVER STEP BY STEP, TYPES OF VIO SERVER INSTALLATION, VIO SERVER INSTALLATION EASY STEPS
Newer Posts Older Posts Home
FRIDAY, JUNE 3, 2011
AIX TL UPGRADE
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
TABLE OF CONTENTS
DOWNLOAD FIX 1
VERIFY THE SYSTEM 2
INSTALL SOFTWARE 3
TL UPGRADE BEST PRACTICES 4
IN A CLUSTERED ENV 5
REFERENCES 5
1) DOWNLOAD FIX
To download fix and service pack go to IBM fix central site
http://www-933.ibm.com/support/fixcentral/
Follow the screen shot
Select the required service pack and its prerequisite
And Download them, if download fails check for your latest java version on your desktop
1) VERIFY THE SYSTEM
Check for any installed emergency fix
Checking for installed ifixes
# emgr –l
Removing an ifix if it is installed
# emgr –r –L <ifix Label>
Verify that the system installed file sets are consistent
# lppchk –v
#lppchk –m3
Check all the file sets have same TL/ML level available
# instfix -i|grep ML
All filesets for 6100-00_AIX_ML were found.
All filesets for 6100-01_AIX_ML were found.
All filesets for 6100-02_AIX_ML were found.
All filesets for 6100-03_AIX_ML were found.
Commit all applied file set
# installp -c -f -g –X
3) INSTALL SOFTWARE
Now go to the download directory
Run
Smitty update_all
Update Installed Software to Latest Level (Update All)
Type or select a value for the entry field. Press Enter AFTER making all desired changes.
[Entry Fields]
* INPUT device / directory for software [.]
Just Type . and Press enter
Update Installed Software to Latest Level (Update All)
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* INPUT device / directory for software .
* SOFTWARE to update _update_all
PREVIEW only? (update operation will NOT occur) no
COMMIT software updates? Yes
SAVE replaced files? No
AUTOMATICALLY install requisite software? Yes
EXTEND file systems if space needed? Yes
VERIFY install and check file sizes? No
DETAILED output? No
Process multiple volumes? Yes
ACCEPT new license agreements? Yes
Preview new LICENSE agreements? No
WPAR Management
Perform Operation in Global Environment yes
Perform Operation on Detached WPARs no
Detached WPAR Names [_all_wpars]
Remount Installation Device in WPARs yes
Alternate WPAR Installation Device []
VERIFY THE UPDATE OF NEW TL BY
Oslevel –s
4) TL UPGRADE BEST PRACTICES
Try the above steps on a test scenario first
If the root vg is mirrored, it is better to unmirrorvg and then apply TL
Create an alt_disk_copy on the second disk, and apply TL at the same time
alt_disk_copy -d "<hdisk to install on >" -b update_all -l /<location of TL>
5) IN A CLUSTERED ENV
BRING THE CLUSTER NODE DOWN
a) Perform a round of cluster verification& sync from primary
b) Perform VG sync
c) Wait for cluster to be stable
d) Stop cluster service on inactive node ie-NodeB
e) Perform ML upgrade on NodeB & reboot
f) Start cluster service on NodeB
g) Perform cluster failover (From NodeA to NodeB) - (Stop with takeover is the best method)
h) Make sure cluster service is down on NodeA
i) Perform ML upgrade on NodeA& reboot
j) Start cluster service
k) Perform cluster verification from NodeB
l) Perform cluster failover (from NodeB to NodeA) - (Stop with takeover is the best method)
m) Start cluster service on NodeB
6) REFERENCES
http://www.ibm.com/developerworks/aix/library/au-aixtlupdate/index.html
Posted by Shivakant Tiwari at 3:19 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADV CONFS, AIX TL best practices, aix TL upgrage, How to upgrade TL in aix
SATURDAY, FEBRUARY 26, 2011
MOUNTING ISO IMAGE IN AIX
Crete a logical volume to accomodate your image
# mklv -y cdlv -s n -L /dev/cdlv rootvg 2G
cdlv
Copy the iso image to the lv just cerated "/dev/cdlv"
# ls
cd_image_163898 lost+found
# dd if=cd_image_163898 of=/dev/cdlv
Note that this command may take a long time and will create two dd processes.
root 368724 422050 1 02:08:39 pts/2 0:00 dd if=cd_image_163898 of=/dev/cdlv
root 393292 188554 0 01:22:54 - 0:00 telnetd -a
root 405736 434208 0 00:38:32 pts/1 0:00 -ksh
root 422050 155758 0 02:08:39 pts/2 0:00 dd if=cd_image_163898 of=/dev/cdlv
Create a Mount point and mount the device "/dev/cdlv" as a cdrom
# mount -v cdrfs -o ro /dev/cdlv /iso
# cd /iso
# ls
OSLEVEL etc ismp root usr
RPMS image.data mkcd.data sbin
bosinst.data installp ppc udi
#
Posted by Shivakant Tiwari at 1:02 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADV CONFS, INSTALLING PACKAGES FROM A ISO IMAGE ON AIX, Mount a aix iso image in aix, MOUNTING ISO IMAGE IN AIX
CREATING AIX MKSYSB ISO BOOTABLE IMAGE
Create a Mksysb image (Assuming that the system has two disk and rootvg contains 1 disk )
Create VG
mkvg -y datavg hdisk1
Create a File system in the new vg
crfs -v jfs2 -g datavg -a size=10G -m /data
Mount the new file system
mount /data
now crete a exclude.rootvg in /etc
echo "/data/" >> /etc/exclude.rootvg
Run mksysb command
mksysb -X -i -e /data/root.mkisysb
Now Create a bootable iso image from mksysb image
# mkdvd -S -m /root.mksysb
Initializing mkdvd log: /var/adm/ras/mkcd.log...
Verifying command parameters...
0512-054 mkdvd: File /root.mksysb does not exist or is empty.
# mkdvd -S -m /root.mkisysb
Initializing mkdvd log: /var/adm/ras/mkcd.log...
Verifying command parameters...
Creating temporary file system: /mkcd/cd_fs...
Populating the CD or DVD file system...
Building chrp boot image...
Copying backup to the CD or DVD file system...
......................................
Creating temporary file system: /mkcd/cd_images...
Creating Rock Ridge format image: /mkcd/cd_images/cd_image_163898
Running mkisofs ...
.......................................
mkrr_fs was successful.
Making the CD or DVD image bootable...
Removing temporary file system: /mkcd/cd_fs...
# pwd
/mkcd/cd_images
# ls -l
total 3236104
-rw-r--r-- 1 root sys 1656872960 Feb 25 01:50 cd_image_163898
drwxrwx--- 2 root system 512 Feb 25 01:44 lost+found
#
Posted by Shivakant Tiwari at 12:03 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADV CONFS, aix bootable mksysb, createing a bootable mksysb cd/dvd image, creating bootable cdrom from mksysb, creating iso image from mksysb image, making bootable cdrom from mksysb image
HOW TO CONFIGURE ISCSI CLIENT ON AIX
VERIFICATION OF DISK
This screen shot shows the output of lspv when we dont have any iscsi disk on the server
The screen show above shows that how a disk is mapped to a target
Now configure the target on aix server
Go to /etc/iscsi directory
and provide the target configuration In this example 192.168.5.202 is the storage and aix-target is the target
# cd /etc/iscsi
# ls
autosecrets targets targetshw
# tail -6 targets
# The target line would look like:
# 10.2.1.106 3260 iqn.2003-01.com.ibm:00.fcd0ab21.shark128 \
# "123ismysecretpassword.fc1b"
#
192.168.5.202 3260 aix-target
#
Now at the Aix server add the ip and change iscsi0 adapter configuration
Added ip as alias to connect to storage
Checked the connectivity
and changed iscsi0 adapter configuration
Run cfgmgr after that
# chdev -l en0 -a alias4=192.168.5.200 -a netmask=255.255.255.0
en0 changed
# ping -c 2 192.168.5.202
PING 192.168.5.202: (192.168.5.202): 56 data bytes
64 bytes from 192.168.5.202: icmp_seq=0 ttl=64 time=0 ms
64 bytes from 192.168.5.202: icmp_seq=1 ttl=64 time=0 ms
----192.168.5.202 PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms
# chdev -l iscsi0 -a initiator_name=aix-target
iscsi0 changed
# lspv
hdisk0 00c402db281a05c4 None
hdisk1 00c402db1717210e rootvg active
# cfgmgr
Now you can see a new disk from storage
# cfgmgr
# lspv
hdisk2 00c402db175641a3 None
hdisk0 00c402db281a05c4 None
hdisk1 00c402db1717210e rootvg active
# lsattr -El hdisk2
clr_q no Device CLEARS its Queue on error True
host_addr 192.168.5.201 Hostname or IP Address False
location Location Label True
lun_id 0x0 Logical Unit Number ID False
max_transfer 0x40000 Maximum TRANSFER Size True
port_num 0xcbc PORT Number False
pvid 00c402db175641a30000000000000000 Physical volume identifier False
q_err yes Use QERR bit True
q_type simple Queuing TYPE True
queue_depth 1 Queue DEPTH True
reassign_to 120 REASSIGN time out value True
rw_timeout 30 READ/WRITE time out value True
start_timeout 60 START unit time out value True
target_name aix-target Target NAME False
#
Posted by Shivakant Tiwari at 11:10 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX iscsi0 adapter configuration, AIX ADV CONFS, CONFIGURE ISCSI CLIENT ON AIX, configure the initiator on aix server, configuring iscsi initiator on aix, OPENFILER AIX
MONDAY, JANUARY 17, 2011
AIX SAMBA CONFIGURATION - BASIC SETUP
INSTALLING AND CONFIGURING SAMBA
DOWNLOAD SAMBA PACKAGE
Obtain samba from http://pware.hvcc.edu/download/aix53-64/
pware53-64.base.5.3.0.0.bff.gz pware53-64.krb5.1.7.1.0.bff.gz pware53-64.openldap.2.4.21.0.bff.gz pware53-64.readline.6.1.0.0.bff.gz
pware53-64.cyrus-sasl.2.1.23.0.bff.gz pware53-64.libiconv.1.13.1.0.bff.gz pware53-64.openssl.0.9.8.13.bff.gz pware53-64.samba.3.5.3.0.bff
pware53-64.gettext.0.17.0.0.bff.gz pware53-64.ncurses.5.7.0.1.bff.gz pware53-64.popt.1.10.4.0.bff.gz
INSTALLING SAMBA
Unzip package
# gunzip *
gunzip: pware53-64.samba.3.5.3.0.bff: unknown suffix -- ignored
Create table of contents
# inutoc .
Install Packages
installp -a -c -g -X -Y -d $(pwd) pware53-64.samba
+-----------------------------------------------------------------------------+
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
pware53-64.zlib.rte 1.2.3.0 USR APPLY SUCCESS
pware53-64.bdb.rte 4.7.25.4 USR APPLY SUCCESS
pware53-64.openssl.rte 0.9.8.13 USR APPLY SUCCESS
pware53-64.krb5.rte 1.7.1.0 USR APPLY SUCCESS
pware53-64.cyrus-sasl.rte 2.1.23.0 USR APPLY SUCCESS
pware53-64.openldap.rte 2.4.21.0 USR APPLY SUCCESS
pware53-64.samba.rte 3.5.3.0 USR APPLY SUCCESS
CONFIGURE BASIC SAMBA
# pwd
/opt/pware64/lib
# cat smb.conf
[global]
workgroup=mygroup
security=user
browseable=yes
[homes]
browseable=yes
read only=no
valid users=test1,test2,test3
START SAMBA DAEMONS
/opt/pware64/sbin/smbd -D
/opt/pware64/sbin/nmbd -D
Posted by Shivakant Tiwari at 6:07 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADV CONFS, AIX SAMBA CONFIGURATION, CONFIGURING SAMBA IN AIX, SAMBA AIX, SAMBA CONFIGURATION
SUNDAY, JANUARY 16, 2011
FAST CONNECT INSTALLATION AND CONFIGURATION
INSTALLING AND CONFIGURING FASTCONNECT ON AIX
# ls
VIEW FAST CONNECT INSTALLER BINARIES
cifs.advanced-demo cifs.msg.ca_ES cifs.msg.en_US cifs.msg.hu_HU cifs.msg.ko_KR cifs.msg.ru_RU cifs.msg.zh_TW
cifs.base cifs.msg.cs_CZ cifs.msg.es_ES cifs.msg.it_IT cifs.msg.pl_PL cifs.msg.sk_SK cifs.websm
cifs.client cifs.msg.de_DE cifs.msg.fr_FR cifs.msg.ja_JP cifs.msg.pt_BR cifs.msg.zh_CN
CREATE INUTOC
# inutoc .
#
RUN INSTALLP COMMAND TO INSTALL FAST CONNECT
installp -a -c -X -Y -g -d $(pwd) all
+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+
Pre-installation Failure/Warning Summary
----------------------------------------
Name Level Pre-installation Failure/Warning
-------------------------------------------------------------------------------
cifs.base.ldap 3.2.0.0 Requisite failure
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
cifs.client.rte 3.2.0.0 USR APPLY SUCCESS
cifs.base.smit 3.2.0.0 USR APPLY SUCCESS
cifs.base.lic 3.2.0.0 USR APPLY SUCCESS
cifs.base.cmd 3.2.0.0 USR APPLY SUCCESS
cifs.base.cmd 3.2.0.0 ROOT APPLY SUCCESS
cifs.advanced-demo.rte 3.2.0.0 USR APPLY SUCCESS
cifs.advanced-demo.rte 3.2.0.0 ROOT APPLY SUCCESS
cifs.websm.apps 3.2.0.0 USR APPLY SUCCESS
cifs.msg.zh_TW.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.zh_TW.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.zh_CN.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.zh_CN.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.sk_SK.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.sk_SK.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ru_RU.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ru_RU.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.pt_BR.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.pt_BR.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.pl_PL.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.pl_PL.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ko_KR.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ko_KR.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ja_JP.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ja_JP.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.it_IT.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.it_IT.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.hu_HU.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.hu_HU.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.fr_FR.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.fr_FR.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.es_ES.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.es_ES.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.en_US.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.en_US.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.de_DE.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.de_DE.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.cs_CZ.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.cs_CZ.base 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ca_ES.websm 3.2.0.0 USR APPLY SUCCESS
cifs.msg.ca_ES.base 3.2.0.0 USR APPLY SUCCESS
NOW FOLLOW STEP BY STEP INSTRUCTION
# smit smb
CONFIGURING SHARES
create a directory testshare
mkdir /testshare
create a share testshare and verify by viewing it
# net share
Share Name Share Type Path Name/Queue Name Share Description
---------- ---------- -------------------- -----------------
HOME File $HOME User's Home Directory Share
# man net
Manual entry for net not found or not installed.
# net share /add /type:file /netname:testshare /path:/testshare /desc:"A TEST SHARE"
Command completed successfully.
# net share
Share Name Share Type Path Name/Queue Name Share Description
---------- ---------- -------------------- -----------------
HOME File $HOME User's Home Directory Share
TESTSHARE File /testshare A TEST SHARE
#
You have to create a system user for fastconnect user to add and work
# net user /add fastusr -p
ERROR: 'fastusr' is not a valid system user.
# mkuser fastusr
# net user /add fastusr -p
Enter fastusr's password:
Command completed successfully.
## net user
Client user name Server user name User Comment
---------------- ---------------- ----------------
fastusr fastusr root nobody
#
configure acl permissions for each user created on share path
Posted by Shivakant Tiwari at 3:04 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADV CONFS, CONFIGURING FAST CONNECT IN AIX, EASY FAST CONNECT CONFIGURATION STEP BY STEP, FAST CONNECT INSTALLATION AND CONFIGURATION
Newer Posts Older Posts Home
THURSDAY, MAY 5, 2011
COMMAND TO SEE ALL THE MANAGED SYSTEM ON HMC
COMMAND TO SEE ALL THE MANAGED SYSTEM ON HMC
THW COMAND BELOW WILL SHOW YOU ALL THE MANAGED SYSTEM , MANAGED THROUGH HMC
hscroot@localhost:~> lsyscfg -r sys -F name
JKKUUYP5-9115-505-SN65A
EPDB-9131-52A-
CIServers-9117-570-SN6
BWDEV49-9110-51A-SN06E
JKKUUYP1-9115-505-
JKKUUYP7-9131-52A-SN6
UUYO-9133-55A-
SMGR61-9110-51A-SN9E
JKKUUYP4-9115-505-SN652155A
CRMQA-9110-51A-
UUYODEV-9110-51A-
JKKDB-9117-570-SN65095BE
BWDB-9117-570-SN65095CE
JKKQA-9110-51A-SN07E
TEST51-9110-51A-
JKKUUYP2-9115-505-
JKKUUYP6-9115-505-SN65
Server-8204-E8A-
UUYODB-9133-55A-
NETBACKUP-9110-51A-
IDES-9110-51A-
BACKUP-9110-51A-SN65
JKKDEV45-9110-51A-
JKKUUYP3-9115-505-SA
CRMDEV-9110-51A-SNE
UUYOCI-9133-55A-
EPDEV53-9110-51A-
THE COMMAND BELOW WILL GIVE THE DETAILED PROFILE CONFIGURATION OF A LPAR
hscroot@localhost:~> lssyscfg -r prof -m BACKUP-9110-
name=Full,lpar_id=1,lpar_env=aixlinux,state=Running,resource_config=1,os_version=Unknown,logical_serial_num=652BBFE1,default_profile=Normal,curr_profile=Normal,work_group_id=none,shared_proc_pool_util_auth=0,allow_perf_collection=0,power_ctrl_lpar_ids=none,boot_mode=norm,lpar_keylock=norm,auto_start=0,redundant_err_path_reporting=0
hscroot@localhost:~> lssyscfg -rprof prof -m BACKUP-9110-51A-
name=Normal,lpar_name=Full,lpar_id=1,lpar_env=aixlinux,all_resources=1,boot_mode=norm,conn_monitoring=0,auto_start=0,redundant_err_path_reporting=0
YOU CAN ALSO CONNECT TO ANY LPAR USING VTMENU hscroot@localhost:~> vtmenu
Retrieving name of managed system(s) . . . JKKUUYP5-9115-505-SN6 EPDB-9131-52A-SN CIServers-9117-570-SNFE BWDEV49-9110-51A-SN00E JKKUUYP1-9115-505-SN6A JKKUUYP7-9131-52A-SN656DG UUYO-9133-55A-SN650188H SMGR61-9110-51A-SN JKKUUYP4-9115-505-SN6 CRMQA-9110-51A-SN0 UUYODEV-9110-51A-SN0 CADE Server-8204-E8A-SN02 JKKDB-9117-570-SN65 BWDB-9117-570-SN65095CE JKKQA-9110-51A-S TEST51-9110-51A-SN0E JKKUUYP2-9115-505-SN6A JKKUUYP6-9115-505-S3A Server-8204-E8A-SN06D4552 UUYODB-9133-55A-SN0601AFH NETBACKUP-9110-51A-SN062CB4E DFG-9110-51A-SN BACKUP-9110-51A-SN6 JKKDEV45-9110-51A-SN65 JKKUUYP3-9115-505-SN0A CRSDEV-9110-51A-SN0E UUYOCI-9133-55A-SN0 EPSSV53-9110-51A-SN0
----------------------------------------------------------
Managed Systems:
----------------------------------------------------------
1) JKKUUYP5-9115-
2) DFG-9131-52A-SN65G
3) SDFG-9117-570-
4) BWDEV49-9110-51A-SN062
5) JKKUUYP1-9115-505-SNA
6) JKKUUYP7-9131-52A-SG
7) UUYO-9133-55A-SN61
8) SOLVH-9110-51A-SN062C
9) JKKUUYP4-9115-505-SNA
10) HBU-9110-51A-SN0CE
11) UUYODEV-9110-51A-SNDE
12) Server-8204-E8A-SN06542
13) JKKDB-9117-570-
14) KIUB-9117-570-SN69E
15) JKKQA-9110-51A-SN0E
16) TEST51-9110-51A-SN6AEE
17) JKKUUYP2-9115-505-SN6554A
18) JKKUUYP6-9115-505-
19) Server-8204-E8A-SND42
20) UUYODB-9133-55A-SN060H
21) NETBACKUP-9110-51A-SNB4E
22) IDES-9110-51A-SN0B6
23) BACKUP-9110-51A-SN6FE
24) JKKDEV45-9110-51A-
25) JKKUUYP3-9115-505-SN08A
26) CRMDEV-9110-51A-
27) UUYOCI-9133-55A-
28) xxxV53-9110-51A-SN1E
Enter Number of Managed System. (q to quit): 23
----------------------------------------------------------
Partitions On Managed System: BAC-9110-51A-
OS/400 Partitions not listed
----------------------------------------------------------
1) Full Running
Enter Number of Running Partition (q to quit): 1
1
Opening Virtual Terminal On Partition Full . . .
Open in progress
Open Completed.
AIX Version 5
(C) Copyrights by IBM and by others 1982, 2007.
login:
Posted by Shivakant Tiwari at 9:15 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, To list all managed resource objects in hmc
MONDAY, APRIL 18, 2011
SCHEDULING HMC BACKUP
SCHEDULING HMC BACKUP
Click on SCHEDULE OPERATIONS
Select new and click next
Fill date and time of schedule , select one time or repeated schedule
Select options select ftp or remote (nfs) and fill the in coming window
SELECT FTP SERVER
PROVIDE IP ADDRESS OF THE FTP SERVER
PROVIDE THE DIRECTORY TO STORE DATA
PROVIDE ADMIN PASSWORD TO COMPLETE THE OPERATION
Posted by Shivakant Tiwari at 3:01 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, SCHEDULING HMC BACKUP, taking hmc backup step by step screen shots
VIEWING HMC LOGS
Viewing HMC events
Open hmc
In the left side click on wecome screen
Click HMC operations
Click hmc events
Posted by Shivakant Tiwari at 2:55 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, HMC operations, Viewing HMC events
THURSDAY, MARCH 17, 2011
HMC Tips VI - Reference Code
1. To list the current reference code for the managed system :
# lsrefcode -r sys -m Managed-System
2. To list last 10 reference codes for the managed system :
# lsrefcode -r sys -m Managed-System -n 10
3. To list the reference code (Its called as LED in old pSeries servers) for each partition in the managed system :
# lsrefcode -r lpar -m Managed-System -F lpar_name,time_stamp,refcode
4. To list last 25 reference codes (led) for partitions lpar-a and lpar-b :
# lsrefcode -r lpar -m Managed-System -n 25 --filter ""lpar_names=lpar-a,lpar-b""
Posted by Shivakant Tiwari at 12:56 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: GETTING REFERENCE CODES IN HMC USING COMMAND LINE, HMC, HMC Reference Code, HMC COMMAND LINE FOR REFERENCE CODE
TUESDAY, MARCH 1, 2011
HMC Tips I - HMC and Managed System
HMC Tips I - HMC and Managed System
1. To enable ssh in a hmc :
# chhmc -c ssh -s enable
You can disable it by replacing the word 'enable' with 'disable'
2. To enable xntp in a hmc :
# chhmc -c xntp -s enable
You can disable it by replacing the word 'enable' with 'disable'
3. To add an entry in the syslog config file :
# chhmc -c syslog -s add -a IP_Addr ( or '-h host_name' )
You can remove an entry by replacing the word 'add' with 'remove'
4. To add an entry in the ntp config file :
# chhmc -c xntp -s add -a IP_Addr ( or 'h host_name' )
You can remove an entry by replacing the word 'add' with 'remove'
5. To configure the network as a startup device :
# chhmc -c netboot -s enable
You can disable it by replacing the word 'enable' with 'disable'
6. To permit IP addresses from utilizing HMC services :
# chhmc -s ssh ( or any_service) -s add -a IP_Addr
You can remove an entry by replacing the word 'add' with 'remove'
7. To add a DNC_server or domain_suffix :
chhmc -c network -s add [-ns DNS_Server] [-ds domain_suffix ]
You can remove an entry by replacing the word 'add' with 'remove'
8. To change network settings for a specific network interface :
# chhmc -c network -s modify -i interface_name
[-a IP_Addr] [-nm network_mask] [ --lparcomm on|off]
Note: Network settings for the s10 interface cannot be changed.
9. To change other network settings :
# chhmc -c network -s modify [-h hostname] [-d network-domain-name][-g gateway]
10. To change the locale for the HMC :
# chhmc -c locale -s modify -l locale
11. To change the HMC date and time, time zone :
# chhmc -c date -s modify[ --datetime ][ --clock {local | utc} ] [ --timezone {time-zone | none} ]
Posted by Shivakant Tiwari at 7:33 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: chhmc command, HMC, HMC Managed System commands, To enable ssh in a hmc, To enable xntp in a hmc
HMC Tips II - Partitions and Profiles
HMC Tips II - Partitions and Profiles
1. To list all machines configured in a hmc
# lssyscfg -r sys
2. To list all lpars(partitions) in a power machine
# lssyscfg -r lpar -m Managed_System
3. To activate/start an LPAR :
# chsysstate -r lpar -m Managed_System -o on -n LPAR_Name -f Profile_ name
4. To deactivate/shutdown an LPAR :
# chsysstate -r lpar -m Managed_System -o shutdown --immed -n LPAR_Name
5. To open the console of a partition :
# mkvterm -m Managed_System -p LPAR_Name
6. To close the console of a partition:
# rmvterm -m Managed_System -p LPAR_Name
7. To list the profile of a partition:
# lssyscfg -r prof -m Managed_System --filter "lpar_names=LPAR_Name,profile_names=Profile_Name"
8. To change the min/desired/maximum memory settings of a partition profile :
# chsyscfg -r prof -m Managed_System -i "name=Profile_Name,lpar_name=LPAR_Name,min_mem=512,desired_mem=19456,max_mem=20480"
9. To change the min/desired/maximum processor units of a partition profile :
# chsyscfg -r prof -m Managed_System -i "name=Profile_Name,lpar_name=LPAR_Name,min_proc_units=0.2,desired_proc_units=0.5,max_proc_units=2.0"
10. To change the min/desired/maximum virtual processor of a partition profile :
# chsyscfg -r prof -m Managed_System -i "name=Profile_Name,lpar_name=LPAR_Name,min_procs=1,desired_procs=2,max_procs=6"
11. To change capped/uncapped setting in a partition profile :
# chsyscfg -r prof -m Managed_System -i "name=Profile_Name,lpar_name=LPAR_Name,sharing_mode=uncap,uncap_weight=128"
Possible values for sharing_mode are cap and uncap.
Possible values for uncap_weight are from 0 to 128.
12. To change the name of a partition profile :
# chsyscfg -r prof -m Managed_System -i "name=Profile_Name,lpar_name=LPAR_Name,new_name=New_Profile_Name"
13. To change the name of a partition :
# chsyscfg -r lpar -m Managed_System -i "name=LPAR_Name,new_name=New_LPAR_Name"
14. To change the default profile of a partition :
# chsyscfg -r lpar -m Managed_System -i "name=LPAR_Name,default_profile=Partition_Profile_Name"
15. To set "power off the machine after all partitions are shutdown" for a power machine :
# chsysscfg -r sys -m Managed_System -i "power_off_policy=0"
Possible values are
0 -> Power off after all partitions are shutdown
1 -> Do not power off after all partitions are shutdown
16. To rename a system profile :
# chsyscfg -r sysprof -m Managed_System -i "name=Sys_Prof_Name,new_name=New_Sys_Prof_Name"
17. To add 2 more partition profiles to a system profile :
# chsyscfg -r sysprof -m Managed_System -i "name=,"lpar_names+=partition3,partition4",
"profile_names+=profile3,profile4""
Posted by Shivakant Tiwari at 7:31 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, To activate/start an LPAR, To change the min/desired/maximum memory settings of a partition profile, To change the min/desired/maximum processor units of a partition profile
HMC Tips III - User Management
HMC Tips III - User Management
1. To list all users in a HMC
# lshmcusr
2. To list only user names and managed resource roles for all HMC users :
# lshmcusr -F name:resourcerole
3. To create a user :
# mkhmcusr -u User_Id -a ROLE -d DESCRIPTION --passwd PASSWORD -M PASSWD_EXPIRATION_DAYS
3. To remove a user :
# rmhmcusr -u USER_NAME
4. To change an hmc user's password :
# chhmcusr -u User_Name -t passwd -v New_Password
5. To change the task role for the user "user1" to hmcoperator :
# chhmcusr -r user1 -t taskrole -v hmcoperator
Available task roles are
hmcsuperadmin, hmcoperator, hmcviewer, hmcpe, hmcservicerep or a user defined task role
6. To list all managed resource objects :
# lsaccfg -t resource
7. To list all managed resource roles :
# lsaccfg -t resourcerole
8. To create a task role using a config file :
# mkaccfg -t resourcerole -f /tmp/fil1
9. To create a task role :
# mkaccfg -t taskrole -i "name=tr1,parent=hmcsuperadmin,"resources=cec:chcod+lscod+lshwres,lpar:chssyscfg+lssyscfg+mksyscfg""
10. To change a task role :
# chaccfg -t taskrole -i "name=tr1,"resources=cec:chhwres+chsysstate,lpar:chssyscfg+chled+chhwres""
11. To remove a task role :
# rmaccfg -t taskrole -n tr1
Posted by Shivakant Tiwari at 7:30 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, To change an hmc user's password, To list all managed resource objects in hmc, To list all managed resource roles
HMC Tips VII - General Terms
HMC Tips VII - General Terms
1. What is the maximum number of servers managed by HMC ?
> Maximum of 48 non-590-595 servers
> Maximum of 32 590/595 servers
2. What is the maximum number of LPARs supported by a HMC ?
> Maximum of 254 LPARs
3. How many HMCs can manage a server at one time ?
> You can have a maximum of 2 HMCs manage a server at one time
4. What are the different types of dynamic operations you can do with CPU, Memory and I/O Adapter on a LPAR ?
> Add
> Remove
> Move
5. How do we connect the HMC to power machines ?
For Power-4 machines, we connect the hmc using serial cables.
But for Power-5 machines, HMC connects to service processors via SSL-encrypted Ethernet, replacing the serial cables.
6. Do we have firewall configured in HMC ?
Yes. Each network card has an integrated firewall.
7. Do we need to configure DHCP in HMC ?
HMC may be a DHCP server for entry and mid-range servers.
But for high-end servers like P595, HMC must be a DHCP server
8. can we have the same HMC to manage P4 and P5 machines ?
POWER5 HMCs cannot manage POWER4 servers, and vice versa.
9. Can we have the existing P4 HMCs upgraded to support P5 machines ?
Yes. We can. This involves a complete overwirte of teh disk and the loss of all previous configuration including user profiles.
10. What to do incase of disk failure in HMC ?
We can restore the HMC using recovery CD.
Then restore the latest Critical consule data backup which will restore the profiles, user ids, passwords, etc..
11. What is the default user id and password for the HMC ?
When the HMC is powered on the first time, login as hscroot and password as 'abc123'.
12. Can we manage a power machine without a HMC ?
Yes. We can run a server in manufacturing default mode, will all resources but no logical partitionings, CoD or Service Focal point,etc..
For entry level server, we can use the Integrated Virtualization Manager.
13. What is the network critetia for dual HMC connection ?
Dual HMCs require two different private networks.
14. What is the default service processor IP address in Power-5 Machines ?
Eth0 - HMC1 - 192.168.2.147 / 255.255.255.0
Eth1 - HMC2 - 192.168.3.147 / 255.255.255.0
15. What is the default user id and password for accessing service processor ?
User id - admin
Password - admin
16. Do we need a HMC for p5 model servers ?
One HMC is mandatory for 590, 595 or 575.
Dual HMC are recommended.
17. Do we need private network for HMc connectivity for p5-595 ?
One private network is mandatory for p5 590,595 or 575.
18. Can we have IVM support multiple servers ?
One IVM allowed per server and it only manages partitions on one server.
19. What does FSP (Flexible Service Processor) has ?
FSP has
a. Operating System
b. UserIds / Passwords
c. Filesystem
d. Networking
e. Firewall
f. Webserver
g. ASMI
h. Firmware
20. What to do if you forgot the admin password for FSP ?
If you do not know the admin password, place a hardware call to get 'celogin'
21. What to do if you forgot the HMC hostname/ipaddress for a long running LPAR ?
You can always get the HMC IPaddress from a LPAR if we have performed "handshake" with the HMC.
Issue the below command to get the HMC IPAddress
# lsrsrc IBM.ManagementServer
Resource Persistent Attributes for IBM.ManagementServer
resource 1:
Name = "169.121.54.48"
Hostname = "169.121.54.48"
ManagerType = "HMC"
LocalHostname = "169.121.54.59"
ClusterTM = "9078-160"
ClusterSNum = ""
ActivePeerDomain = ""
NodeNameList = {"SAP-PRodServer"}
22. One HMC should be within 8metres of Managed Server
23. Each FSP Ethernet port should be connected to only one HMC
Posted by Shivakant Tiwari at 7:29 PM 1 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: command to get the HMC IPAddress, Flexible Service Processor, HACMP BASIC QUESTIONS, HMC, HMC - General Terms, HMC INTERVIEW QUESTIONS, service processor IP address in Power-5 Machines
HMC Tips IV - Backup
HMC Tips IV - Backup
1. To backup HMC data on DVD :
# bkconsdata -r dvd
2. To backup HMC data to a ftp server :
# bkconsdata -r ftp -h ftp_server_name -u ftp_username --passwd ftp_password
3. To backup HMC data to a NFS mounted file system :
# bkconsdata -r nfs -n nfs_server_name -l Nfs_mount_point
4. To list storage media devices :
# lsmediadev
5. To backup profile data for a managed system :
# bkprofdata -m Managed-System -f File_name
Profile data files are kept under /var/hsc/profiles/Managed-Machine-Serial-Number
6. To restore a managed profile data :
# rstprofdata -m Managed-System -l restore_type -f File-Name
Valid restore types are
1 - Full restore from the backup file.
2 - Merge the current profile data and backup profile data, with priority to backup.
3 - Merge the current profile data and backup profile data, with priority to current data.
4 - Initialize the profile data. All partition, partition/system profiles will be deleted.
Posted by Shivakant Tiwari at 7:20 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: HMC, HMC Backup, To backup HMC data to a ftp server, To backup HMC data to a NFS mounted file system
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)
THURSDAY, MARCH 3, 2011
AIX DISK RELATED TROUBLESHOOTING - REMOVING MISSING DISK
HOW TO DEAL WITH MISSING DISK
IF YOU REMOVE A DISK WITHOUT REMOVING THE DISK FROM VOLUME GROUP IT CAN CREATE A BIG ISSUE ASSUMING THAT YOU HAVE MORE THAN ONE DISK IN THE VOLUME GROUP
1)COLLECT THE ODM INFORMATION OF THE OTHER DISK
2)MANUPULATE VALUES LIKE PVID AND CONNECTION AND NAME
3)ADD THE CHANGED ENTRY TO ODM
3)REDUCE THE PV FROM ODM
1)SIMULATE PROBLEM
# lsvg testvg
VOLUME GROUP: testvg VG IDENTIFIER: 00fad1d400004c00000001300193c765
VG STATE: active PP SIZE: 16 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 801 (12816 megabytes)
MAX LVs: 256 FREE PPs: 801 (12816 megabytes)
LVs: 0 USED PPs: 0 (0 megabytes)
OPEN LVs: 0 QUORUM: 2
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no
# lsvg -p testvg
testvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 259 259 52..52..51..52..52
hdisk4 active 542 542 109..108..108..108..109
# varyoffvg testvg
# rmdev -dl hdisk4
hdisk4 deleted
#
# varyonvg testvg
PV Status: hdisk2 00fad1d44e4f4d58 PVACTIVE
00fad1d47168f544 PVMISSING
varyonvg: Volume group testvg is varied on.
#
2)COLLECT DATA
# odmget -q "name=hdisk2" CuAt
CuAt:
name = "hdisk2"
attribute = "maxlun"
value = "7"
type = "R"
generic = "UD"
rep = "nr"
nls_index = 44
CuAt:
name = "hdisk2"
attribute = "pvid"
value = "00fad1d44e4f4d580000000000000000"
type = "R"
generic = "D"
rep = "s"
nls_index = 2
# odmget -q "name=hdisk2" CuDv
CuDv:
name = "hdisk2"
status = 1
chgstatus = 2
ddins = "scdisk"
location = "04-C0-00-2,0"
parent = "scsi0"
connwhere = "2,0"
PdDvLn = "disk/scsi/osdisk"
JUST USE THIS SCRIPT TO COLLECT DATA
for x in CuDv CuAt CuPath
do
odmget -q "name=hdisk2" $x > /tmp/disk/hdisk2.$x
done
2)MANUPULATE THE DATA
PVID OF FAILED HDISK YOU CAN GET BY DOING lsvg -p ON THE VG
# lsvg -p testvg
testvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 259 259 52..52..51..52..52
0516-304 lsvg: Unable to find device id 00fad1d47168f544 in the Device
Configuration Database.
00fad1d47168f544 missing 542 542 109..108..108..108..109
CREATE A SEPERATE FILE FOR CHANGED DATA
cat /tmp/disk/hdisk2.CuAt|sed -e 's/hdisk2/hdisk4/g' -e 's/00fad1d44e4f4d58/00fad1d47168f544/' -e 's/609SYMMETRIX/719SYMMETRIX/' > /tmp/disk/hdisk4.CuAt
cat /tmp/disk/hdisk2.CuDv| sed -e 's/hdisk2/hdisk4/' -e 's/2,0/2,4/' > /tmp/disk/hdisk4.CuDv
SEE THE CHANGED VALUES
# pwd
/tmp/disk
# ls
hdisk2.CuAt hdisk2.CuDv hdisk2.CuPath hdisk4.CuAt hdisk4.CuDv
# cat hdisk4.CuAt
CuAt:
name = "hdisk4"
attribute = "maxlun"
value = "7"
type = "R"
generic = "UD"
rep = "nr"
nls_index = 44
CuAt:
name = "hdisk4"
attribute = "pvid"
value = "00fad1d47168f5440000000000000000"
type = "R"
generic = "D"
rep = "s"
nls_index = 2
# cat hdisk4.CuDv
CuDv:
name = "hdisk4"
status = 1
chgstatus = 2
ddins = "scdisk"
location = "04-C0-00-2,4"
parent = "scsi0"
connwhere = "2,4"
PdDvLn = "disk/scsi/osdisk"
#
3)ADD THE DATA INTO ODM
odmadd /tmp/disk/hdisk4.CuAt
odmadd /tmp/disk/hdisk4.CuDv
# lsvg -p testvg
testvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 259 259 52..52..51..52..52
hdisk4 missing 542 542 109..108..108..108..109
4)REMOVE THE DISK FROM VG AND THEN FROM ODM
# odmadd /tmp/disk/hdisk4.CuAt
# odmadd /tmp/disk/hdisk4.CuDv
# lsvg -p testvg
testvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 259 259 52..52..51..52..52
hdisk4 missing 542 542 109..108..108..108..109
# lspv hdisk4
PHYSICAL VOLUME: hdisk4 VOLUME GROUP: testvg
PV IDENTIFIER: 00fad1d47168f544 VG IDENTIFIER 00fad1d400004c00000001300193c765
PV STATE: missing
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 16 megabyte(s) LOGICAL VOLUMES: 0
TOTAL PPs: 542 (8672 megabytes) VG DESCRIPTORS: 1
FREE PPs: 542 (8672 megabytes) HOT SPARE: no
USED PPs: 0 (0 megabytes)
FREE DISTRIBUTION: 109..108..108..108..109
USED DISTRIBUTION: 00..00..00..00..00
REMOVE USING PVID ONLY
# reducevg -df testvg 00fad1d47168f544
# lsvg -p testvg
testvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 259 259 52..52..51..52..52
#
# odmdelete -o CuDv -q "name=hdisk4"
0518-307 odmdelete: 2 objects deleted.
# odmdelete -o CuAt -q "name=hdisk4"
0518-307 odmdelete: 4 objects deleted.
Posted by Shivakant Tiwari at 10:13 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX REMOVING DISK THAT ARE ACCIDENTALLY REMOVED, AIX TROUBLESHOOTING, REMOVING DISKS FROM ODM, removing missing disk, SOLVING AIX VG PROBLEMS
REPAIRING CORRUPT VG
If there is a hardware failure, and one or 2 disk in the volume group get completely trashed. The vg was reduced by two disks.
1. Use the (undocumented) readvgda command to get the detailed VGDA from one of the disks, e.g. "readvgda /dev/hdiskn". I advise you to do the same on a disk that *didn't* fail and compare (a disk that didn't fail might be a more reliable source). Check the list of PVIDs and make sure they are all
present and accessible by the system (no hardware problems). Save the readvgda output in a file, you will need it if you make a mistake later and want to start over.
2. Among the readvgda output is the layout of each LV on the PVs, from which you can construct LV map files for the mlkv command.
3. You will also need a good copy of the /etc/filesystems file,unless you remember the original LV mount points and filesystem types.
4. When you have all the LV map files, export the volume group and re−create it on the original PVs, with the original PP size:
mkvg −f −y vgdvd −s 1024 hdisk3 hdisk4 ...
5. Re−create each LV using the map files. I assume here that your filesystems were jfs (change accordingly if you had jfs2):
mklv −y loglv02 −m <loglv02_mapfile> −t jfslog vgdvd <numlp>
mklv −y data1 −m <data1_mapfile> −t jfs vgdvd <numlp>
...
6. Restore /etc/filesystems or add the missing stanzas manually. *Do not mount the filesystems yet.*
7. For each filesystem LV, update the LVCB with the log and label information:
chfs −a log=/dev/loglv02 <mountpoint>
chlv −L <mountpoint> data1
8. Run a fsck on each filesystem. This is the critical step – if the command fails because it can't find the superblock, then the LVs were not re−created correctly, stop and check your map files. If the jfslog LV was not re−created correctly, fsck will not be able to replay the log and you will probably lose some data. Consider stopping and double−checking the map files before answering yes to the fsck "fix" questions. Also, if filesystems were active at the time of the crash, fsck might find unrecoverable errors on some inodes or blocks, your only option here is to fix these errors at the risk of losing some inodes (the price for not having a tape backup). If errors were fixed, re−run fsck until there are no errors.
9. When fsck run without errors on each FS, mount the filesystems. If errors were fixed during fsck, check the lost+found directories, they might contain missing files or directories you can salvage.
Posted by Shivakant Tiwari at 10:04 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX TROUBLESHOOTING, AIX VG TROUBLESHOOTING, REPAIRING CORRUPT VG IN AIX
TUESDAY, MARCH 1, 2011
REPLACING A FAILED PV IN A MIRRORED VOLUME GROUP
INTRODUCTION
The following procedures replace a failed physical volume (PV) within a mirrored volume group. The replacepv command provides a method for replacing a failed PV in most configurations. An alternative procedure is also provided for configurations where the replacepv command cannot be used.
Prerequisites
All logical volumes using the failed PV have valid copies on other available PVs (with the possible exception of a dedicated dump logical volume). If any of the prerequisites listed below cannot be met, see the alternate procedure.
The volume group containing the failed PV is not rootvg.
The replacement PV can be added to the volume group containing the failed PV (this might not be possible depending on the PV size and volume group characteristics, such as MAX PPs per PV).
The replacement PV must be able to be configured into the system at the same time as the failing PV.
The replacement PV's name can differ from the failed PV's name.
The size of the replacement PV must be at least the size of the failed PV.
The volume group containing the failed PV must not be a snapshot volume group or have a snapshot volume group.
PROCEDURE TO REPLACE FAILED DISK
Complete the following steps, assuming that the failed PV is hdisk2 and the replacement PV is hdisk10:
If the replacement PV is not yet installed on the system, perform the steps necessary to install it. To use the configuration manager to define a new PV, run the following command:
cfgmgr
Use the lspv command to determine the name assigned to the PV. For this example, assume that the new PV is named hdisk10.
To replace the failed PV with the one defined in
Step 1, run the following command:
replacepv hdisk2 hdisk10
\When the command runs, hdisk2 is replaced by hdisk10, and hdisk2 is no longer assigned to a volume group.
To undefine the failed PV, run the following command:
rmdev -dl hdisk2
Physically remove the failed disk from the system.
Verify that the procedure was successful by completing the following steps:
To check that all logical volumes are mirrored to the new PV as desired, run the following command:
lslv lvname
Check the COPIES attribute of each logical volume affected by the failed PV to ensure that the desired number of copies now exist. If the number of copies of the logical volume is below the desired number, use the mklvcopy command to create additional copies.
To verify that all logical volume partitions are synchronized and there are no stale partitions, run the following command:
lspv hdisk10
Check the STALE PARTITIONS attribute of the replaced PV to ensure that the count is zero. If there are stale partitions use the syncvg command to synchronize the partitions.
Replacing a failed PV when the configuration does not allow the use of the replacepv command
Assume that the failed physical volume, hdisk0, and its mirror, hdisk1, are part of the yourvg volume group.
To remove mirror copies from the failed PV, run the following command:
unmirrorvg yourvg hdisk0
If the PV failure occurred on rootvg, remove hdisk0 from the boot list by running the following command:
Note: If your configuration uses boot devices other than hdisk0 and hdisk1, add them to the command syntax.
bootlist -om normal hdisk1
This step requires that hdisk1 remains a bootable device in rootvg. After completing this step, ensure that hdisk0 does not appear in output.
If the PV failure occurred on rootvg, recreate any dedicated dump devices from the failed PV.
If you have a dedicated dump device that was on the failed PV, you can use the mklv command to create a new logical volume on an existing PV. Use the sysdumpdev command to set the new logical volume as the primary dump device.
To undefine the failed PV, run the following command:
Note: Removing the disk device entry will also remove the /dev/ipldevice hard link if the failed PV is the PV used to boot the system.
reducevg yourvg hdisk0
rmdev -dl hdisk0
If the failed PV is the most recently used boot device, recreate the /dev/ipldevice hard link that was removed in Step 4 by running the following command:
ln /dev/rhdisk1 /dev/ipldevice
Note the r prefixed to the PV name.
To verify that your /dev/ipldevice hard link has been recreated, run the following command:
ls /dev/ipldevice
Replace the failed disk.
To define the new PV, run the following command:
cfgmgr
The cfgmgr command assigns a PV name to the replacement PV. The assigned PV name is likely to be the same as the PV name previously assigned to the failed PV. In this example, assume that the device hdisk0 is assigned to the replacement PV.
To add the new PV to the volume group, run the following command:
extendvg yourvg hdisk0
You might encounter the following error message:
0516-050 Not enough descriptor space left in this volume group.
Either try adding a smaller PV or use another volume group.
If you encounter this error and cannot add the PV to the volume group, you can try to mirror logical volumes to another PV that already exists in the volume group or add a smaller PV. If neither option is possible, you can try to bypass this limitation by upgrading the volume group to a Big-type or Scalable-type volume group using the chvg command.
Mirror the volume group.
Note: The mirrorvg command cannot be used if all of the following conditions exist:
The target system is a logical partition (LPAR).
A copy of the boot logical volume (by default, hd5) resides on the failed PV.
The replacement PV's adapter was dynamically configured into the LPAR since the last cold boot.
If all of the above conditions exist, use the mklvcopy command to recreate mirror copies for each logical volume as follows:
Create copies of the boot logical volume to ensure that it is allocated to a contiguous series of physical partitions.
Create copies of the remaining logical volumes, and synchronize the copies using the syncvg command.
Make the disk bootable by shutting down the LPAR and activating it instead of rebooting using the shutdown or reboot commands. This shutdown does not have to be done immediately, but it is necessary for the system to boot from the new PV.
Otherwise, create new copies of logical volumes in the volume group using the new PV with the following command:
Note: The mirrorvg command disables quorum by default. For rootvg, you will want to use the -m option to ensure that the new logical volume copies are mapped to hdisk0 in the same way as the working disk.
mirrorvg yourvg hdisk0
If your configuration holds third copies of some logical volumes, you might need to recreate those copies with the following command:
mklvcopy -k
If the PV failure occurred on rootvg, initialize the boot record by running the following command:
bosboot -a
If the PV failure occurred on rootvg, update the boot list by running the following command:
Note: If your configuration uses boot devices other than hdisk0 and hdisk1, add them to the command.
bootlist -om normal hdisk0 hdisk1
Verify that the procedure was successful.
To verify that all logical volumes are mirrored to the new PV, run the following command:
lslv lvname
Check the COPIES attribute of each logical volume affected by the failed PV to ensure that the desired number of copies now exist. If the number of copies of the logical volume is below the desired number, use the mklvcopy command to create additional copies.
To verify that all the logical volume partitions are synchronized, check that there are no stale partitions by running the following command:
lspv hdisk0
Check the STALE PARTITIONS attribute of the replaced PV to ensure that the count is zero. If there are stale partitions use the syncvg command to synchronize the partitions.
If the PV failure occurred on rootvg, use the following steps to verify other aspects of this procedure:
To verify the boot list, run the following command:
bootlist -om normal
To verify the dump device, run the following command:
sysdumpdev -l
To verify the list of bootable PVs, run the following command:
ipl_varyon -i
To verify the /dev/ipl_device, run the following command:
ls -i /dev/rhdisk1 /dev/ipldevice
Ensure the output of the ls command has the same i-node number for both entries.
This step completes the procedure.
Posted by Shivakant Tiwari at 7:18 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX TROUBLESHOOTING, Mirror the volume group., PROCEDURE TO REPLACE FAILED DISK IN AIX, reducevg, REPLACING A FAILED PV IN A NIRRORED VOLUME GROUP, USING REPLACEPV COMMAND
FRIDAY, SEPTEMBER 24, 2010
AIX PRINT QUEUE AND NFS TROUBLESHOOTING
AIX PRINT QUEUE AND NFS RELATED TROUBLESHOOTING
Check for system date and verify that it is correct
The qdaemon automatically rebuilds the qconfig.bin file When the /etc/qconfig file changes. If the date on the qconfig file is of earlier than the date on the qconfig.bin file, the qconfig file is not digested, even if it was just modified.
IF the changes to the qconfig file are correct,.If the dates on the qconfig.bin file and the qconfig file are not correct the /etc/qconfig file is no longer linked to the /usr/lpd/qconfig file
If no other user except root can print, check the permissions of the /tmp directory. Also, check the permissions of the print commands being used
refreshed the print queue with command
qadm –K <queue name>
qadm –U <queue name>
or use enq command
Verify the configuration of the queue
root@node1[/etc]-> cat qconfig|awk '/mos/,/backend/'
mos:
device = hp@mos
hp@mos:
file = /var/spool/lpd/pio/@local/dev/hp@mos#hpJetDirect#9100
header = never
trailer = never
access = both
backend = /usr/lib/lpd/pio/etc/piojetd mos 9100
root@node1[/etc]->
Here queue name is mos , device type is HP jet direct on
port 9100 The line backend runs the command/script to
A TYPICAL OUTPUT OF piojetd SCRIPT
Shows that the background print manager is piobe
"if [[ $1 = +([0-9]) && ! -f $1 ]]
then
port=$1
shift
else
port=9100
fi
trap "trap 15;kill -15 0;exit 0" 15
/usr/lib/lpd/piobe "$@" | /usr/lib/lpd/pio/etc/piohpnpf -x $hostname -p
$port
if [ "$?" -ne 0 ]
then
exit 64
fi"
Check the status of print queue
root@node1[/etc]-> qchk -P mos
Queue Dev Status Job Files User PP % Blks Cp Rnk
------- ----- --------- --- ------------------ ---------- ---- -- ----- --- ---
mos hp@mo READY
Step 3)
If required kill the queue and restart it
root@node1[/etc]-> qadm -K mos
root@node1[/etc]-> qadm -U mos
Step 4)
ping the network printer
root@node1[/etc]-> ping -c 2 mos
PING mos.com: (10.24.190.86): 56 data bytes
64 bytes from 10.24.190.86: icmp_seq=0 ttl=60 time=50 ms
64 bytes from 10.24.190.86: icmp_seq=1 ttl=60 time=68 ms
----mos.com PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 50/59/68 ms
root@node1[/etc]->
If ping is all right check printer connectivity
root@node1[/etc]-> telnet 10.24.190.86 9100
Trying...
Connected to 10.24.190.86.
If connectivity is all right , Printer should print , if it is still
not printing either there is a problem in physical device ,
or printer is not responding , restart the physical device
(power cycle) and check
Verify the virtual printer queue
stiwari@ch [/tmp]-> cat /etc/qconfig |awk '/A00a:/,/backend/'
A00a:
device = @option
up = TRUE
host = option
s_statfilter = /usr/lib/lpd/bsdshort
l_statfilter = /usr/lib/lpd/bsdlong
rq = A00a
@option:
backend = /usr/lib/lpd/rembak -T10
Here virtual host is option and remote queue is A00a , the
script/program that is printing in the background is
rembak
remote printer
Check the remote printer as same as we checked the virtual printer
Run the following command to get a detail diagnostic of
stiwari@che[/tmp]->
This command prints on server 120.. print queue A00a
and gives the output in print.out
The file getting printed is /tmp/asd
/usr/lib/lpd/rembak -S 120.23.2.219 -P A00a -N /usr/lib/lpd/aixv2short –D /tmp/print.out /tmp/asd
stiwari@che[/tmp]-> cat print.out
rembak[1466612] main: Wed Sep 22 16:46:17 2010
rembak[1466612] main: /usr/lib/lpd/rembak -S 120.23.2.219 -P A00a -N
/usr/lib/lpd/aixv2short -D /tmp/print.out /tmp/asd
rembak[1466612] main: backend=0.
rembak[1466612] hookup: Try to connect, current time=1285188377.
rembak[1466612] sendjob: sendjob starts, jobname=/tmp/asd, current
time=1285188377.
rembak[1466612] sendjob: datafn[0]=dfA377che, fakedfn=dfA377che.
rembak[1466612] makecontrolfile: Entering makecontrolfile.
rembak[1466612] makecontrolfile: dfnames[0]=dfA377che
/ò@ak[1466612] getbsdinfo: bsd3=Hche\10 Proot\10 J/tmp/asd\10 Cche\10
Lroot\10
rembak[1466612] get_bsd_4file: bsd nc=1
/ò
][N/tmp/asd\10 ][N/tmp/asd\10 ]
/ò@ak[1466612] getbsdinfo: bsd3=Hche\10 Proot\10 J/tmp/asd\10 Cche\10
Lroot\10 fdfA377che\10 UdfA377che\10 N/tmp/asd\10
rembak[1466612] gettmpr: Opening file /tmp//rembakmTypqa.
rembak[1466612] gettmpr: File /tmp//rembakmTypqa opened successfully,
fd=5.
rembak[1466612] sendjob: ctrlfname=/tmp//rembakmTypqa,
fakecfn=cfA377che.
rembak[1466612] sendjob: State machine starts.....
rembak[1466612] sendjob: State 1 - send the "Receive a Print Job" request.
/ò sendreq - sending lpd request [\2 A00a\10 ].
rembak[1466612] gotack: Reading ACK status.....current time=1285188377,
timeout_ack=90.
rembak[1466612] gotack: ACK status=0x0.
rembak[1466612] sendjob: state 3 - Send data file(s), dfcount=1.
rembak[1466612] sendjob: realfn=/tmp/asd, fakefn=dfA377che,
filter=/usr/lib/lpd/aixv2short.
/òPak[1466612] sendreq: sendreq - sending lpd request [\3 11 dfA377chew\10
].
rembak[1466612] gotack: Reading ACK status.....current time=1285188377,
timeout_ack=90.
rembak[1466612] gotack: ACK status=0x0.
rembak[1466612] senddatafile: Opening file /tmp/asd.
rembak[1466612] senddatafile: File /tmp/asd opened successfully, fd=6.
rembak[1466612] send_file_rembak: Reading 11 bytes from file, fd=6.
rembak[1466612] send_file_rembak: Writing 11 bytes to socket 4.
rembak[1466612] send_file_rembak: File sent.
rembak[1466612] ack: Send ACK.
rembak[1466612] send_file_rembak: waiting for ACK.
ıak[1466612] get_bsd_4file: bsd strings: [N/tmp/asd\10 ][N/tmp/asd\10
rembak[1466612] gotack: Reading ACK status.....current time=1285188377,
timeout_ack=90.
rembak[1466612] gotack: ACK status=0x0.
rembak[1466612] sendjob: State 2 - send control file,
ctrlfname=/tmp//rembakmTypqa, fakecfn=cfA377che.
/òPak[1466612] sendreq: sendreq - sending lpd request [\2 76 cfA377che\10 ].
rembak[1466612] gotack: Reading ACK status.....current time=1285188377,
timeout_ack=90.
rembak[1466612] gotack: ACK status=0x0.
rembak[1466612] sendcontrolfile: Opening file /tmp//rembakmTypqa.
rembak[1466612] sendcontrolfile: File /tmp//rembakmTypqa opened
successfully, fd=6.
rembak[1466612] send_file_rembak: Reading 76 bytes from file, fd=6.
rembak[1466612] send_file_rembak: Writing 76 bytes to socket 4.
rembak[1466612] send_file_rembak: File sent.
rembak[1466612] ack: Send ACK.
rembak[1466612] send_file_rembak: waiting for ACK.
rembak[1466612] gotack: Reading ACK status.....current time=1285188377,
timeout_ack=90.
rembak[1466612] gotack: ACK status=0x0.
rembak[1466612] sendjob: State 5 - end of job /tmp/asd.
rembak[1466612] sendjob: Delete control file /tmp//rembakmTypqa.
stiwari@che[/tmp]->
This output will give all the details of sending file to be printed
on the remote host and it can be diagnosed easily where is
the error
TROUBESHOOTING NFS
Verify that the network connections are good.
Verify that the server is up and running by running the following command at the shell prompt of the client:
/usr/bin/rpcinfo -p server_name
protocols, and port numbers is printed, similar to the following
If the server is up, a list of programs, versions,:
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 1025 mountd
100001 1 udp 1030 rstatd
100001 2 udp 1030 rstatd
100001 3 udp 1030 rstatd
100002 1 udp 1036 rusersd
100002 2 udp 1036 rusersd
100008 1 udp 1040 walld
100012 1 udp 1043 sprayd
100005 1 tcp 694 mountd
100003 2 udp 2049 nfs
100024 1 udp 713 status
100024 1 tcp 715 status
100021 1 tcp 716 nlockmgr
100021 1 udp 718 nlockmgr
100021 3 tcp 721 nlockmgr
100021 3 udp 723 nlockmgr
100020 1 udp 726 llockmgr
100020 1 tcp 728 llockmgr
100021 2 tcp 731 nlockmgr
If a similar response is not returned, log in to the server at the
server console and check the status of the inetd daemon
lssrc –ls inetd
Verify that the mountd, portmap and nfsd daemons are running on the NFS server by entering the following commands at the client shell prompt :
:
/usr/bin/rpcinfo -u server_name mount
SHIVAKANT Page 8 9/24/2010
/usr/bin/rpcinfo -u server_name portmap
/usr/bin/rpcinfo -u server_name nfs
If the daemons are running at the server, the following responses are returned:
program 100005 version 1 ready and waiting
program 100000 version 2 ready and waiting
program 100003 version 2 ready and waiting
The program numbers correspond to the commands, respectively, as shown in the previous example. If a similar response is not returned, log in to the server at the server
console and check the status of the daemons
lssrc –g nfs
Verify that the /etc/exports file on the server lists the name of the file system that the client wants to mount and that the file system is exported. Do this by entering the command:
showmount -e server_name
This command lists all the file systems currently exported by the
server_name.
TROUBLESHOOTING NFS MOUNT ERROR
Check that the directory which is being exported , its child directory is not already exported ( a parent directory cannot be exported if the child is already exported)
Check that both the server and client can ping and can do reverse lookup if DNS is already configured
Run commands
Nslookup client name
Dig client name
These two commands will give you pretty good results
If reverse lookup is not successful add the client host in /etc/hosts file of nfs server and add server host to /etc/hosts file of clients
Echo "ipaddress hostname" >> /etc/hosts
This should solve the nfs mount errors
Posted by Shivakant Tiwari at 7:21 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX NFS TROUBLESHOOTING, AIX PRINTER TROUBLESHOOTING, AIX TROUBLESHOOTING, STEP BY STEP TROUBLESHOOTING OF PRINTER IN AIX
Newer Posts Older Posts Home
MONDAY, MAY 16, 2011
MOVING A LOGICAL VOLUME FROM ONE VOLUME GROUP TO ANOTHER
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
TO MOVE A LOGICAL VOLUME FROM A VOLUME GROUP TO ANOTHER VOLUME GROUP
ACTUALLY MOVING A LOGICAL VOLUME IS A PROCESS TO COPY VOLUME TO ANOTHER VOLUME GROUP AND THEN REMOVE IT FROM THE SOURCE LOCATION
1. CREATE A LOGICAL VOLUME
# mklv -t jfs2 rootvg 1
fslv15
2)CREATE A FILE SYSTEM ON THAT LOGICAL VOLUME
# crfs -v jfs2 -d /dev/fslv15 -m /abc
File system created successfully.
130864 kilobytes total disk space.
New File System size is 262144
3)USE CPLV COMMAND TO MOVE THE LOGICAL VOLUME FROM OLD VG TO NEW VG
# cplv -v vijayvg fslv15
cplv: Logical volume fslv15 successfully copied to fslv16 .
4) VERIFY THE MOVEMENT IN NEW VG
# lsvg -l vijayvg
vijayvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
loglv00 jfs2log 1 1 1 open/syncd N/A
fslv00 jfs2 120 120 1 open/syncd /wpar-file
fslv05 jfs2 48 48 1 open/syncd /tsmsoftwares
loglv01 jfslog 1 1 1 closed/syncd N/A
fslv16 jfs2 1 1 1 closed/syncd N/A
fslv02 jfs2 20 20 1 open/syncd /opt/tivoli
fslv06 jfs2 32 32 1 open/syncd /tsm01
fslv11 jfs2 40 40 1 open/syncd /nimfs
#
IF THE VOLUME COPIED ABOVE ALREADY EXISTS IN THE DESTINATION VOLUME GROUP THEN IT WILL RENAME THE VOLUME GROUP TO THE NEXT AVAILABLE NAME
5)NOW REMOVE LOGICAL VOLUME FROM THE SOURCE
# lsvg -l rootvg |grep fslv15
fslv15 jfs2 1 1 1 open/syncd /abc
# umount /abc
# rmlv fslv15
Warning, all data contained on logical volume fslv15 will be destroyed.
rmlv: Do you wish to continue? y(es) n(o)? y
rmlv: Logical volume fslv15 is removed.
Posted by Shivakant Tiwari at 9:08 AM 3 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX ADVANCE COMMANDS, move a logical volume to another volume group
Thursday, April 21, 2011AIX ADVANCE COMMANDS
USING REPLACEPV COMMAND
INITIALLY ROOTVG HAD ONE DISK
hdisk0
WE REPLACED hdisk0 with hdisk1
# replacepv hdisk0 hdisk1
0516-1011 replacepv: Logical volume hd5 is labeled as a boot logical volume.
0516-1232 replacepv:
NOTE: If this program is terminated before the completion due to
a system crash or ctrl-C, and you want to continue afterwards
execute the following command
replacepv -R /tmp/replacepv344288
0516-1011 replacepv: Logical volume hd5 is labeled as a boot logical volume.
0516-1734 replacepv: Warning, savebase failed. Please manually run 'savebase' before rebooting.
0516-1734 replacepv: Warning, savebase failed. Please manually run 'savebase' before rebooting.
#
# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk1 active 546 202 37..00..00..99..66
#
USING alt_disk_install
# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk1 active 546 202 37..00..00..99..66
# alt_disk_copy -d hdisk0
Calling mkszfile to create new /image.data file.
0301-168 bosboot: The current boot logical volume, /dev/hd5,
does not exist on /dev/hdisk0.
Checking disk sizes.
Creating cloned rootvg volume group and associated logical volumes.
Creating logical volume alt_hd5
Creating logical volume alt_hd6
Creating logical volume alt_hd8
Creating logical volume alt_hd4
Creating logical volume alt_hd2
Creating logical volume alt_hd9var
Creating logical volume alt_hd3
Creating logical volume alt_hd1
Creating logical volume alt_hd10opt
Creating logical volume alt_fwdump
Creating logical volume alt_fslv00
Creating logical volume alt_fslv03
Creating logical volume alt_pagelv00
Creating logical volume alt_paging00
Creating /alt_inst/ file system.
Creating /alt_inst/export/spot file system.
Creating /alt_inst/home file system.
Creating /alt_inst/opt file system.
Creating /alt_inst/tmp file system.
Creating /alt_inst/usr file system.
Creating /alt_inst/var file system.
Creating /alt_inst/var/adm/ras/platform file system.
Generating a list of files
for backup and restore into the alternate file system...
Backing-up the rootvg files and restoring them to the
alternate file system...
Modifying ODM on cloned disk.
Building boot image on cloned disk.
forced unmount of /alt_inst/var/adm/ras/platform
forced unmount of /alt_inst/var
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/home
forced unmount of /alt_inst/export/spot
forced unmount of /alt_inst
forced unmount of /alt_inst
Changing logical volume names in volume group descriptor area.
Fixing LV control blocks...
Fixing file system superblocks...
Bootlist is set to the boot disk: hdisk0
alt_disk_copy: 0505-218 ATTENTION: /usr/sbin/savebase returned an unexpected result.
alt_disk_copy: 0505-218 ATTENTION: /usr/sbin/savebase returned an unexpected result.
# bosboot -ad /dev/hdisk1
bosboot: Boot image is 30420 512 byte blocks.
# bootlist -m normal -o
hdisk0 blv=hd5
# bootlist -m normal hdisk1
#
#
CREATING MKSYSB OF THE ACTIVE ROOTVG AND USING alt_disk_mksysb TO COPY ON ANOTHER DISK
df -g
/dev/hd4 5.88 5.23 11% 4625 1% /
/dev/hd2 6.38 5.26 18% 31963 3% /usr
/dev/hd9var 0.25 0.23 10% 410 1% /var
/dev/hd3 8.12 8.11 1% 142 1% /tmp
/dev/fwdump 0.12 0.12 1% 4 1% /var/adm/ras/platform
/dev/hd1 0.12 0.12 1% 23 1% /home
/proc - - - - - /proc
/dev/hd10opt 0.12 0.08 39% 969 6% /opt
/dev/fslv00 0.38 0.03 91% 13142 60% /export/spot
#
CREATING LIST OF DIRECTORIES TO EXCLUDE
#
# echo "/export/spot/" > /etc/exclude.rootvg
# echo "/tmp/" >> /etc/exclude.rootvg
ADJUSTING/CHANGING FILE SYSTEM SIZE
chfs -a size=1G /
Filesystem size changed to 2097152
# chfs -a size=2G /usr
Filesystem size changed to 4194304
# df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 1.00 0.36 65% 4626 6% /
/dev/hd2 2.00 0.89 56% 31963 14% /usr
/dev/hd9var 0.25 0.23 10% 410 1% /var
/dev/hd3 8.12 8.11 1% 144 1% /tmp
/dev/fwdump 0.12 0.12 1% 4 1% /var/adm/ras/platform
/dev/hd1 0.12 0.12 1% 23 1% /home
/proc - - - - - /proc
/dev/hd10opt 0.12 0.08 39% 969 6% /opt
/dev/fslv00 0.38 0.03 91% 13142 60% /export/spot
# chfs -a size=+4G /tmp
0516-1734 extendlv: Warning, savebase failed. Please manually run 'savebase' before rebooting.
Filesystem size changed to 25427968
FIRING MKSYSB BACKUP IN A FILE
# mksysb -e -i /tmp/galaxy.mksysb
0301-168 bosboot: The current boot logical volume, /dev/hd5,
does not exist on /dev/hdisk0.
Creating information file (/image.data) for rootvg.
Creating list of files to back up.
Backing up 36681 files...................
36681 of 36681 files (100%)
0512-038 mksysb: Backup Completed Successfully.
#
OOPS WE RECEIVED THE ERROR DUE TO PREVIOUS EXERCISE
WHEN WE TRIED TO RESTOTE USING alt_disk_mksysb
# alt_disk_mksysb -m /tmp/galaxy.mksysb -d hdisk0
0505-126 alt_disk_install: target disk hdisk0 has a volume group assigned to it.
HOW TO RECTIFY THIS ERROR
# alt_disk_install -X
+-----------------------------------------------------------------------------+
ATTENTION: calling new module /usr/sbin/alt_rootvg_op. Please see the alt_rootvg_op man page
and documentation for more details.
Executing command: {/usr/sbin/alt_rootvg_op -X }
+-----------------------------------------------------------------------------+
Bootlist is set to the boot disk: hdisk1
FIRING THE RESTORATION ONCE AGAIN USING THE SAME MKSYSB IMAGE WE CREATED BEFORE
# alt_disk_mksysb -m /tmp/galaxy.mksysb -d hdisk0
Restoring /image.data from mksysb image.
Checking disk sizes.
Creating cloned rootvg volume group and associated logical volumes.
Creating logical volume alt_hd5
Creating logical volume alt_hd6
Creating logical volume alt_hd8
Creating logical volume alt_hd4
Creating logical volume alt_hd2
Creating logical volume alt_hd9var
Creating logical volume alt_hd3
Creating logical volume alt_hd1
Creating logical volume alt_hd10opt
Creating logical volume alt_fslv00
Creating logical volume alt_fslv03
Creating logical volume alt_pagelv00
Creating logical volume alt_paging00
Creating /alt_inst/ file system.
Creating /alt_inst/export/spot file system.
Creating /alt_inst/home file system.
Creating /alt_inst/opt file system.
Creating /alt_inst/tmp file system.
Creating /alt_inst/usr file system.
Creating /alt_inst/var file system.
Restoring mksysb image to alternate disk(s).
Linking to 64bit kernel.
Changing logical volume names in volume group descriptor area.
Fixing LV control blocks...
forced unmount of /alt_inst/var
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/home
forced unmount of /alt_inst/export/spot
forced unmount of /alt_inst
forced unmount of /alt_inst
Fixing file system superblocks...
Bootlist is set to the boot disk: hdisk0
#
Posted by Shivakant Tiwari at 7:25 PM 0 comments Email This
BlogThis!
Share to Twitter
Share to Facebook
Share to Google Buzz
Links to this post
Labels: /etc/exclude.rootvg, AIX ADVANCE COMMANDS, alt_disk_mksysb, CREATING MKSYSB OF THE ACTIVE ROOTVG AND USING alt_disk_mksysb, ERROR alt_disk_mksysb, USING alt_disk_install, USING REPLACEPV COMMAND
AIX AUDITING
AIX auditing can be configured using configuration files stored in /etc/securty/audit
The two files which are user to configure basic auditing are config and objects
The config files has basic configurations like which type of logging will be used and which command to use what are the users to monitor and which events are to be monitored
The object file containes the type of activity being recorded for all the events
MAJOR CHANGES IN CONFIG FILE
# cd /etc/security/audit
# cat config
start:
binmode = off
streammode = on ; STREAMING ON
stream:
cmds = /etc/security/audit/streamcmds
users:
root = general,lvm,SRC ; SELECTING THE CLASSES
#
CHANGING THE STREAMCMDS FILE
# cat streamcmds
/usr/sbin/auditstream -c SRC | auditpr -v >> /audit/stream.out & ; SELECTING ONLY SRC EVENTS HERE
ACTIVITY ON SPECIFIC FILES CAN BE RECORDED BY CHANGING IN objects FILE
# cat objects
/etc/security/environ:
w = "S_ENVIRON_WRITE"
/etc/security/group:
w = "S_GROUP_WRITE"
/etc/security/limits:
w = "S_LIMITS_WRITE"
/etc/security/login.cfg:
w = "S_LOGIN_WRITE"
STARTING AUDITING
audit on
WE CAN SEE LOGIN IN /audit/stream.out file
# cat /audit/stream.out
event login status time command
--------------- -------- ----------- ------------------------ -------------------------------
event login status time command
--------------- -------- ----------- ------------------------ -------------------------------
SRC_Stop root OK Thu Apr 21 23:11:25 2011 srcmstr
tftpd
SRC_Start root OK Thu Apr 21 23:11:29 2011 srcmstr
tftpd
SRC_Stop root OK Thu Apr 21 23:11:48 2011 srcmstr
rpc.mountd
#
Posted by Shivakant Tiwari at 5:49 PM 0 comments Email This
BlogThis!
Share to Twitter
Share to Facebook
Share to Google Buzz
Links to this post
Labels: AIX ADVANCE COMMANDS, AUDITING AIX USERS ACTIVITIES, auditpr, CONFIGURING AIX AUDITING, STREAMCMDS
Thursday, April 7, 2011AIX PERFORMANCE MONITORING WITH EXAMPLES
Displaying the top 10 CPU-consuming processes
# ps aux | head -1; ps aux | sort -rn +2 | head -10
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 8196 21.5 0.0 48 40 - A May 11 3577:57 wait
root 45078 18.7 0.0 48 40 - A May 11 3110:34 wait
tsm1 274632 0.2 2.0 33240 13616 - A May 11 31:54 db2sysc 0
root 552976 0.1 0.0 1400 1436 - A May 13 8:00 dtgreet
root 532694 0.1 0.0 72 72 - A May 12 16:07 trclogio
you 638978 0.0 0.0 288 80 pts/2 A May 14 0:00 rlogin cws
you 540676 0.0 0.0 780 820 pts/2 A May 14 0:00 -ksh
you 495768 0.0 0.0 296 88 pts/2 A May 14 0:00 rlogin cws
you 397328 0.0 0.0 780 820 pts/2 A May 14 0:00 -ksh
you 221224 0.0 0.0 776 816 pts/2 A May 14 0:00 -ksh
Displaying number of processors in the system
# lsdev -Cc processor
proc0 Available 00-00 Processor
Displaying the top 10 memory-consuming processes using SZ
# ps -ealf | head -1 ; ps -ealf | sort -rn +9 | head
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
242001 A tsm1 331940 1 0 60 20 17346400 75688 * May 11 - 6:41 /opt/tivoli/tsm/server/bin/dsmserv -u tsm1 -i /home/tsm1/tsminst1 -q
242001 A pconsole 499926 471054 0 60 20 1f34e400 70500 * May 14 - 2:15 /usr/java5/bin/java -Xmx512m -Xms20m -Xscmx10m -Xshareclasses -Dfile.
encoding=UTF-8 -Xbootclasspath/a:/pconsole/lwi/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/rcpbootcp.jar:/pconsole/lwi/lib/ISCJaasModul
e.jar:/pconsole/lwi/lib/icl.jar:/pconsole/lwi/lib/jaas2zos.jar:/pconsole/lwi/lib/jaasmodule.jar:/pconsole/lwi/lib/lwinative.jar:/pconsole/lwi/lib/lwinl1.jar:/pc
onsole/lwi/lib/lwinl2.jar:/pconsole/lwi/lib/lwinl3.jar:/pconsole/lwi/lib/lwirolemap.jar:/pconsole/lwi/lib/passutils.jar -Xverify:none -cp eclipse/launch.jar:ecl
ipse/startup.jar:/pconsole/lwi/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/launcher.jar com.ibm.lwi.LaunchLWI
40401 A tsm1 274632 356590 0 60 20 1c56d400 33240 * May 11 - 31:55 db2sysc 0
242001 A tsm1 430296 356590 0 60 20 105e1400 16476 * May 11 - 3:06 db2acd 0
240001 A root 294918 188528 0 60 20 17b26400 14068 May 11 - 7:15 /usr/sbin/dpid2
240001 A root 163928 86110 0 60 20 c17d400 10348 f1000100194d55e0 May 11 - 1:15 /usr/lpp/X11/bin/X -cc 4 -D /usr/lib/X11//rgb -T -force :0 -au
th /var/dt/A:0-LfufUa
242001 A tsm1 233690 356590 0 60 20 11b20400 6696 * May 11 - 3:55 db2fmp (C) 0
242001 A tsm1 450620 356590 0 60 20 11be0400 3408 * May 11 - 0:00 db2fmp (idle) 0
240001 A root 737438 188528 0 39 20 1df0a400 2840 * May 14 - 0:02 /usr/sbin/rsct/bin/vac8/IBM.CSMAgentRMd
240001 A root 180370 188528 0 60 20 2253400 2280 May 11 - 0:14 sendmail: accepting connections
#
Displaying the processes in order of being penalized
# ps -eakl | head -1 ; ps -eakl | sort -rn +5
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
303 A 0 57372 0 120 16 -- 1030000 68 3d2af70 - 2:20 wlmsched
303 A 0 12294 0 120 17 -- 19008000 56 - 0:14 sched
303 A 0 0 0 120 16 -- 15004000 60 - 3:25 swapper
10307 Z 0 32784 0 20 254 rt 0:00 <defunct>
240005 A 0 614566 622792 1 60 20 a0f9400 836 pts/1 0:00 ksh
200001 A 0 524388 614566 1 60 20 1f369400 920 pts/1 0:00 ps
340001 A 0 352462 188528 0 39 20 1a44b400 2124 f10008071001d640 - 0:00 rmcd
242001 A 1002 450620 356590 0 60 20 11be0400 3408 * - 0:00 db2fmp
242001 A 1002 430296 356590 0 60 20 105e1400 16476 * - 3:06 db2fmp
242001 A 1002 331940 1 0 60 20 17346400 75688 * - 6:41 dsmserv
242001 A 1002 233690 356590 0 60 20 11b20400 6696 * - 3:55 db2fmp
242001 A 8 499926 471054 0 60 20 1f34e400 70500 * - 2:15 java
240401 A 0 463082 188528 0 60 20 4b75400 348 * - 0:00 dfpd
240401 A 0 372928 1 0 60 20 7296400 100 28e4b28 - 0:00 uprintfd
240401 A 0 311494 1 0 60 20 1e34f400 1112 f10001001a54f8b0 - 1:59 db2fmcd
240401 A 0 307400 188528 0 60 20 1f3ce400 1600 * - 0:00 IBM.ServiceRMd
240401 A 0 135380 188528 0 60 20 1a04c400 680 - 0:00 nimesis
240001 A 8 635014 499926 0 60 20 e5f8400 292 f10001001563c1e8 - 0:00 pconsole_exec
240001 A 8 471054 569380 0 60 20 4435400 816 - 0:00 ksh
240001 A 1 557274 1 0 60 20 1f0ad400 2100 - 0:00 sendmail
240001 A 0 737438 188528 0 39 20 1df0a400 2840 * - 0:02 IBM.CSMAgentRMd
240001 A 0 581740 188528 0 60 20 ab18400 332 f1000200067374c8 - 0:00 tftpd
240001 A 0 569380 188528 0 60 20 13462400 816 - 0:00 ksh
240001 A 0 561364 409748 0 60 20 2877400 788 pts/2 0:00 ksh
240001 A 0 552976 434188 0 60 20 5393400 1400 - 8:01 dtgreet
240001 A 0 479486 418030 0 60 20 1818f400 788 f1000200008f1478 pts/0 0:00 ksh
240001 A 0 475280 1 0 27 20 1a72f400 1216 * - 0:30 posixtrace
240001 A 0 458982 188528 0 60 20 12b63400 408 - 0:00 timed
240001 A 0 454892 188528 0 60 20 1eb4f400 428 - 0:08 routed
240001 A 0 446576 577610 0 60 20 1c7ae400 784 pts/4 0:00 ksh
240001 A 0 393352 188528 0 60 20 b89a400 548 - 0:00 dhcpcd
240001 A 0 368828 188528 0 60 20 142e5400 316 f1000010dd008010 - 0:00 qdaemon
240001 A 0 360628 188528 0 60 20 f2be400 328 f10001001a4ae3a0 - 0:00 rpc.lockd
Displaying the processes in order of priority
# ps -eakl | sort -n +6 | head
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
303 A 0 0 0 120 16 -- 15004000 60 - 3:25 swapper
303 A 0 16392 0 0 16 -- 1b00a000 64 f100080009786c08 - 0:26 lrud
303 A 0 24588 0 0 16 -- 1f00e000 108 - 0:00 vmmd
303 A 0 28686 0 0 16 -- 1010000 52 - 0:00 memgrdd
303 A 0 57372 0 120 16 -- 1030000 68 3d2af70 - 2:20 wlmsched
303 A 0 61470 0 0 16 -- 3032000 52 - 0:00 armtrace_kproc
303 A 0 12294 0 120 17 -- 19008000 56 - 0:14 sched
40201 A 0 98416 0 0 17 20 8119000 136 * - 0:00 dog
240001 A 0 475280 1 0 27 20 1a72f400 1216 * - 0:30 posixtrace
#
Displaying the processes in order of time
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +3 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
8196 - A 3581:13 0 48 40 xx 0 0 21.5 0.0 wait
45078 - A 3113:23 0 48 40 xx 0 0 18.7 0.0 wait
532694 - A 16:07 0 72 72 32768 0 0 0.1 0.0 trclogio
552976 - A 8:01 0 1356 1436 xx 48 80 0.1 0.0 dtgreet
294918 - A 7:16 218 14052 14000 32768 27 24 0.0 2.0 /usr/sbi
168044 - A 4:32 91 544 392 xx 3 4 0.0 0.0 /usr/sbi
254082 - A 3:15 995 216 192 32768 0 0 0.0 0.0 nfsd
0 - A 3:25 7 60 48 xx 0 0 0.0 0.0 swapper
57372 - A 2:20 0 68 32 xx 0 0 0.0 0.0 wlmsched
53274 - A 2:06 0 120 96 xx 0 0 0.0 0.0 gil
Displaying the processes in order of real memory use
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +6 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
294918 - A 7:16 218 14052 14000 32768 27 24 0.0 2.0 /usr/sbi
163928 - A 1:15 1059 7132 3448 xx 3219 1128 0.0 0.0 /usr/lpp
737438 - A 0:02 264 2056 2468 xx 788 412 0.0 0.0 /usr/sbi
352462 - A 0:00 301 1584 2084 xx 542 500 0.0 0.0 /usr/sbi
180370 - A 0:14 137 1096 1596 32768 1187 1000 0.0 0.0 sendmail
307400 - A 0:00 136 1344 1520 xx 258 176 0.0 0.0 /usr/sbi
552976 - A 8:01 0 1356 1436 xx 48 80 0.1 0.0 dtgreet
475280 - A 0:30 20 1144 1208 32768 73 64 0.0 0.0 posixtra
544916 pts/1 A 0:00 0 868 972 32768 80 104 0.0 0.0 ps vx
614566 pts/1 A 0:00 1 600 876 32768 240 276 0.0 0.0 -ksh
Displaying the processes in order of I/O
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +4 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
106632 - A 0:00 2338 136 152 xx 36 36 0.0 0.0 /usr/ccs
163928 - A 1:15 1059 7132 3448 xx 3219 1128 0.0 0.0 /usr/lpp
254082 - A 3:15 995 216 192 32768 0 0 0.0 0.0 nfsd
1 - A 0:09 549 708 492 32768 30 32 0.0 0.0 /etc/ini
352462 - A 0:00 301 1584 2084 xx 542 500 0.0 0.0 /usr/sbi
217218 - A 1:37 267 1076 452 32768 151 44 0.0 0.0 /usr/sbi
737438 - A 0:02 264 2056 2468 xx 788 412 0.0 0.0 /usr/sbi
294918 - A 7:16 218 14056 14004 32768 27 24 0.0 2.0 /usr/sbi
356590 - A 0:00 209 508 152 32768 54 48 0.0 0.0 db2wdog
290960 - A 0:00 166 1572 60 32768 46 8 0.0 0.0 /usr/sbi
Displaying WLM classes
# ps -a -o pid,user,class,pcpu,pmem,args
PID USER CLASS %CPU %MEM COMMAND
32784 <defunct>
221224 you Default 0.0 0.0 -ksh
397328 you Default 0.0 0.0 -ksh
467058 root System 0.0 0.0 ksh
487458 root System 0.0 0.0 -ksh
495768 you Default 0.0 0.0 rlogin cws
520194 root System 0.0 0.0 ps -a -o pid,user,class,pcpu,pmem,args
540676 you Default 0.0 0.0 -ksh
638978 you Default 0.0 0.0 rlogin cws
659554 root System 0.0 0.0 pg
708804 root System 0.0 0.0 pg
Determining the PID of wait processes
# ps vg | head -1 ; ps vg | grep -w wait
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
8196 - A 3582:56 0 48 40 xx 0 0 21.5 0.0 wait
45078 - A 3114:52 0 48 40 xx 0 0 18.7 0.0 wait
#
Posted by Shivakant Tiwari at 6:52 PM 1 comments Email This
BlogThis!
Share to Twitter
Share to Facebook
Share to Google Buzz
Links to this post
Labels: AIX ADVANCE COMMANDS, AIX PERFORMANCE MONITORING, AIX PERFORMANCE TOOLS EXAMPLES, L1 monitoring commands in AIX, ps for aix, ps in AIX
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)
Total Pageviews
10,062 Your Ad Here
Feedjit
Your Ad Here
FRIDAY, APRIL 15, 2011
AIX PAGING SPACE
AIX PAGING SPACE
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
hd6 hdisk0 rootvg 512MB 17 yes yes lv
CREATE A NEW LV TO USE FOR PAGING SPACE
# mklv -t paging rootvg 5
pagelv00
SEE CURRENT PAGING SPACES WHICH ARE REGISTERED
#
# cat /etc/swapspaces
* /etc/swapspaces
*
* This file lists all the paging spaces that are automatically put into
* service on each system restart (the 'swapon -a' command executed from
* /etc/rc swaps on every device listed here).
*
* WARNING: Only paging space devices should be listed here.
*
* This file is modified by the chps, mkps and rmps commands and referenced
* by the lsps and swapon commands.
hd6:
dev = /dev/hd6
ENABLING A PAGING SPACE
# swapon /dev/pagelv00
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
pagelv00 hdisk0 rootvg 640MB 1 yes no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
#
DISABLING A PAGING SPACE
# swapoff /dev/pagelv00
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
pagelv00 hdisk0 rootvg 640MB 0 no no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
#
CREATING A PAGING SPACE THROUGH mkps
# mkps -a -n -s3 rootvg
paging00
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging00 hdisk0 rootvg 384MB 1 yes yes lv
pagelv00 hdisk0 rootvg 640MB 0 no no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
MKPS AUTOMATICALLY ADDS PAGING SPACE IN /etc/swapspaces
# cat /etc/swapspaces
* /etc/swapspaces
*
* This file lists all the paging spaces that are automatically put into
* service on each system restart (the 'swapon -a' command executed from
* /etc/rc swaps on every device listed here).
*
* WARNING: Only paging space devices should be listed here.
*
* This file is modified by the chps, mkps and rmps commands and referenced
* by the lsps and swapon commands.
hd6:
dev = /dev/hd6
paging00:
dev = /dev/paging00
CHANGING PAGING SPACE
INCREASING PAGING SIZE
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging00 hdisk0 rootvg 384MB 1 yes yes lv
pagelv00 hdisk0 rootvg 640MB 0 no no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
# chps -s 2 paging00
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging00 hdisk0 rootvg 640MB 1 yes yes lv
pagelv00 hdisk0 rootvg 640MB 0 no no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
#
DECREASING PAGING SPACE
# chps -d 1 paging00
shrinkps: Temporary paging space paging01 created.
shrinkps: Paging space paging00 removed.
shrinkps: Paging space paging00 recreated with new size.
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging00 hdisk0 rootvg 512MB 1 yes yes lv
pagelv00 hdisk0 rootvg 640MB 0 no no lv
hd6 hdisk0 rootvg 512MB 17 yes yes lv
#
Posted by Shivakant Tiwari at 5:52 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX AIX PAGING SPACE, AIX commands, AIX ENABLING A PAGING SPACE, AIX INCREASING PAGING SIZE, AIX PAGING SPACE, CREATING A PAGING SPACE THROUGH mkps
AIX SYSTEM DUMP
VIEWING A DUMP DEVICE
# sysdumpdev -l
primary /dev/hd6
secondary /dev/sysdumpnull
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump FALSE
dump compression ON
CREATING A SECONDARY DUMP DEVICE
# mklv -t jfs2 rootvg 2
fslv03
# sysdumpdev -s /dev/fslv03
primary /dev/hd6
secondary /dev/fslv03
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump FALSE
dump compression ON
SCANNING A DUMP DEVICE
# sysdumpdev -L -S /dev/hd6
0453-019 No previous dumps recorded.
Scanning device /dev/hd6 for existing dump.
A valid dump was not detected in the dump devices.
Scanning device /dev/fslv03 for existing dump.
A valid dump was not detected in the dump devices.
#
ESTIMATING A DUMP SIZE
# sysdumpdev -e
0453-041 Estimated dump size in bytes: 138621747
#
EXTENDING A DUMP DEVICE
# extendlv fslv03 1
# sysdumpdev -l
primary /dev/hd6
secondary /dev/fslv03
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump FALSE
dump compression ON
#
#
Posted by Shivakant Tiwari at 5:32 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX commands, AIX SYSTEM DUMP, DUMP SIZE TOO SMALL, EXTENDING A DUMP DEVICE, SCANNING A DUMP DEVICE
TUESDAY, MARCH 1, 2011
AIX commands
VG COMMANDS
lsvg Display all VGs
lsvg -o Display all active VGs
lsvg rootvg Display info about rootvg
lsvg -l rootvg Display info about all LVs in rootvg
lsvg -o |lsvg -il Display info about all LVs in all VGs
lsvg -p rootvg Display info about all PVs in rootvg
mkvg -s 8 hdisk1 Create VG with name vgxx on hdisk1 with partition size 8MB
mkvg -s 8 -y sivg hdisk1 Create VG with name sivg on hdisk1 with partition size 8MB
mkvg -s 4 -t 2 -y sivg hdisk1 Create sivg on hdisk1 with PP size 4 and no of partions 2 * 1016
chvg -a y newvg To cuase VG newvg automatically activated at startup
chvg -a n newvg To deactivate the automatic activation at startup
chvg -t 2 newvg To change maximum no. of PP to 2032 on vg newvg
chvg -Q n newvg To disable quorum on VG newvg
reorgvg newvg Reorganises PP allocation of VG newvg
extendvg newvg hdisk3 hdisk4 Add PV hdisk3 and hdisk4 to VG newvg
exportvg newvg Exports the VG newvg
importvg -V 44 -y newvg hdisk2 Import the hdisk2 with name newvg, and assign major number 44
redcucevg newvg hdisk3 Remove PV hdisk3 from VG newvg
varyoffvg newvg To deactviate VG newvg
varyonvg newvg To activate VG newvg
syncvg -v sivg To sync the mirrored LV in the VG sivg
mirrorvg -S -m sivg hdisk2 To mirror LVs of sivg with hdisk2 (-m for exact mirror, -S
forbackground mirror)
unmirrorvg sivg hdisk2 To remove the mirrored PV from the set.
FS COMMANDS
lsfs Lists all filesystems in the /etc/filesystems entry
lsfs -q List all filesystems with detailed info
lsfs -a To list all filesystems (default)
lsfs -l Specify the output in list format
lsfs -c Specify the output in column format
lsfs -v jfs Lists all jfs filesystems
chfs -a size=24576 /si Change size of FS /si to 24576 x 512 bytes blocks (12 MB)
chfs -a size=+24576 /si Add 24576 x 512 byte blocks to FS /si
chfs -m /si /bi Change the mount point from /si to /bi
chfs -A /si To auto mount the filesystem si
chfs -d account /si Remove account attribute of /si. ( from /etc/filesystems file)
chfs -a splitcopy=/backup -a copy=2 /oracle This will mount the 2nd copy of mirrored filesystem oracle to
/backup in read-only mode
crfs -v jfs -g testvg -a size=64465 -m /SHIVA Creates FS /SHIVA of type jfs in VG testvg of blocksize 64465
crfs -v jfs -d /dev/lv00 -m /SHIVA Create FS /SHIVA of type jfs on device /dev/lv00
rmfs /SHIVA Deletes FS /SHIVA and associated LV
rmfs -r /SHIVA Deletes FS /SHIVA its mount point and associated LV
defragfs /sifs To defragment the file system /sifs
defragfs -q /sifs Display the current defrag status of the file system
fsck -y n /dev/lv00 To fsck the filesystem associated to /dev/lv00 assuming response "yes"
fsck -p /dev/lv00 To restore superblock from backup superblock
PV COMMANDS
lspv hdisk0 Display status and characteristics of the PV
lspv -p hdisk0 Display PP usage of hdisk0
lspv -l hdisk0 To list all logical volumes on PV hdisk0
chpv -v r hdisk1 Close the PV (Used while removing PV without varyon)
chpv -v a hdisk1 Open the PV
chpv -c hdisk0 Clear the master boot record on PV hdisk0
migratepv hdisk1 hdisk2 To move PPs from PV hdisk1 to hdisk2
migratepv -l silv hdisk1 hdisk2 To migrate LV silv from PV hdisk1 to hdisk2
LV COMMANDS
lslv -l lv00 Display info about LV by PV
lslv -p hdisk1 Display LV allocation map for hdisk1
chlv -t copy lv00 To change the lv00 to copy type
chlv -p r lv00 To change the lv00 to readonly mode
rmlv silv To remove silv
rmlv -f silv To remove silv without user intervention
mklv -s n -c 3 silv hdisk1 To make LV silv with three copies on hdisk1
extendlv silv 5 To extend the LV silv with 5 LPs
mklvcopy -s n lvsi 2 hdisk1 To mirror LV lvsi on same PV with 2 copies
mklvcopy lvsi 3 hdisk1 hdisk2 To mirror LV lvsi on PV hdisk1 and hdisk2 with 3 copies
rmlvcopy lvsi 2 hdisk1 Will remove one copy of LV lsvi from hdisk1
mklv -t jfslog -y log00 newvg 2 To create a jfslog with name log00 on VG newvg with 2LPs
logform /dev/log00 To format jfslog volume log00
BLV COMMANDS
bootlist -m normal -o To see the boot sequence in normal mode
bootlist -m service -o To see the boot sequence in service mode
bootlist -m normal cd0 hdisk0 To change boot sequence to cd0,hdisk0 in normal mode
bootlist -m service cd0 rmt0 hdisk0 To change boot sequence to cd0,rmt0,hdisk0 in service mode
bosboot -ad /dev/hdisk1 To create boot image on PV hdisk1
mkboot -cd /dev/hdisk1 To clear the boot image
bootinfo -b Specifies the bootable disk
bootinfo - t Specifies the type of boot
bootinfo -e Check the machine can boot from tape
bootinfo -T To see the machine type
bootinfo -s hdisk0 To see the size of hdisk0
bootinfo -r To see the size of memory
PAGE SPACE COMMANDS
lsps -a To list out all paging spaces
lsps hd6 To display the details of the paging space hd6
chps -a y paging00 To turn on the paging space paging00
chps -a n paging00 To turn off the paging space paging00
chps -s4 paging00 To increase the size of the paging space in 4 LP blocks
mkps -a -n -s4 sivg To create a paging space on VG sivg of 4 LP size (-s4) and activate it
immediately (-n) and activate it at every restarts
rmps paging00 To remove the paging space paging00
swapon -a To invoke all entries in /etc/swapspaces file
swapon /dev/paging00 To make available swap space paging00
SYSTEM DUMP COMMANDS
sysdumpdev -l To list the current dump destination
sysdumpdev -L List the details of the previous dump
sysdumpstart -p Starts dump in the primary dump device
sysdumpstart -s Starts dump in the secondary dump device
sysdumpdev -p /dev/lv00 To make lv00 as primary dump device
sysdumpdev -P -p /dev/lv00 To make lv00 as primary dump device permanently
sysdumpdev -s /dev/rmt0 To make rmt0 as secondary dump device
sysdumpdev -z To determine a new system dump occurred
Device related commands
cfgmgr To configure devices and installs device software in system
cfgmgr -l vscsi0 To configure the components connected to the vscsi0 interface
lscfg To display config, diagnostics and vital product definition info
lscfg -l mem0 Display info about device mem0
lscfg -l ent* Display info about all Ethernet cards
lscfg -v Display vpd
lscfg -v -l hdisk0 Display vpd of hdisk0
mkdev -l rmt0 To change device rmt0 from defined state to available state
lsdev -P To lists all supported devices
lsdev -P -c disk To list all supported disks
lsdev -P -r class To display supported class
lsdev -P -r subclass To display all sub class
lsdev -C To lists all configured devices
lsdev -C -l mem0 To display the properties of mem0
chdev -l sys0 -a maxproc=100 To change default maxproc value to 100
chdev -l rmt0 -a blocksize=512 To change the block size to 512
chdev -l rmt0 -a ret=no To avoid tape retension
rmdev -l rmt0 To remove the device rmt0
rmdev -d -l rmt0 To remove the device totally from database
rmdev -l rmt0 -S To change the state of the device stopped
lsparent -C -k rs232 To display possible parent devices which accept rs232 devices
lsparent -C -l hdisk0 To display parent devices which accept child device hdisk0
lsattr -Dl rmt0 To see the default values of the device rmt0
lsattr -El rmt0 To see the current values of the device rmt0
lsattr -El tty0 -a login -R To see all possible values of the login attribute of tty0
lsconn -p scsi0 To list all possible connection scsi0 can accept
lvlstmajor To list the available major numbers
mknod /dev/null c 2 2 Create null device with major (2) and minor (2) nos. (c - char device)
Console emulation commands
lscons To list the current console
lscons -b To list the console at next boot
chcons /dev/tty3 To change the console to tty3
chcons -a login=enable /dev/tty3 Redirect console to tty3 and provide login prompt
swcons /dev/tty3 To change system console to tty3 temporarily
Installation specific commands
lslpp -l To see the details of installed file sets
lslpp -ha bos.net.* To list the installation history of all file set in bos.net packages
lslpp -f bos.rte To list the files in the bos.rte package
lslpp -w /etc/hosts To list the file set which contain /etc/hosts file
lslpp -p bos.net.nfs.server To list the pre requisites for bos.net.nfs.server file set
installp -L -d /dev/rmt0.1 To list the installable products on the device rmt0
installp -aX -d /dev/rmt0.1 bos.net To install all filesets within bos.net and expands file system if it requires
installp -u bos.net To remove bos.net
installp -r To reject the applied software
installp -c -f <product> To commit the <product>
installp -C To cleanup an incomplete installation
lppchk -c <product> To check the <product>
instfix -k IX9999 -d /dev/rmt0.1 To install the file set associated with fix IX9999 from rmt0
instfix -ik IX9999 To verify fix IX9999 installed
Network related commands
host 193.9.200.1 Resolves ip to host name (from /etc/hosts file)
host ibm Resolve ibm to ip address (from /etc/hosts file)
hostname ibm To change the host name to ibm
entstat en0 To the status of ethernet device en0
entstat -d en0 To list the detailed status of device en0
no -a To list all net configurable attributes and their values
no -d thewall To change thewall parameter to its default value
no -o ipforwarding=1 To make the machine as router in tcpip networks
traceroute ibm To trace the route to ibm
ping ibm To tcp ping to the machine ibm
ifconfig -a To show the status of all network interfaces
ifconfig en0 To show the status of en0
ifconfig en0 up Turns on network card en0
ifconfig en0 down Turns off network card en0
ifconfig en0 detach Removes en0 card from the network interface list
ifconfig en0 inet 194.35.52.1 netmask 255.255.255.0 up
Configure en0 starts immediately
ifconfig en0 alias 195.60.60.1 Create alias ip address for en0
route add 0 192.100.13.7 To make 192.100.13.7 as default gateway for entire network
route add 192.100.12.0 192.100.13.7 To make 13.7 as gateway for 12.0 network
route -f To clear the gateway table
chdev -l inet0 -a hostname=si To change the host name to si permanently
netstat -a To show the state of all sockets
netstat -c To show the network buffers cache
netstat -D To show the net drops of packets
netstat -i To display interface statistics
netstat -r To show the routing table
netstat -rn To show routing table (ip will be given instead of host names)
netstat -s To show the statistics of the protocols
netstat -s -p < tcp/udp/ipv6> To show the statistics of respective protocols
Space usage commands
du -k To list number of bytes in 1k blocks
du -l To list number of bytes in 512 bytes blocks
du -s To list only the total disk usage in the current directory
df -i To display no of free and used inodes
df -k To display diskspace in 1024 bytes format
Backup commands
mksysb -i -X /dev/rmt0 Creates image.data and system backup (-X expands /tmp if required)
mksysb -m /dev/rmt0 Creates image.data file with map file and system backup
mksysb -e /dev/rmt0 Creates system data but excludes the files listed in /etc/exclude.rootvg
mkszfile Creates /image.data file
mkcd -d /dev/cd1 Creates system boot backup to the CD-R device /dev/cd1
mkcd -d /dev/cd1 -v vg00 Creates backup of vg vg00 to CD-R device /dev/cd1
mkcd -d /dev/cd1 -G Creates generic boot backup
savevg -i -f /dev/rmt0 vg00 Creates vg00.data image file and backup vg vg00
savevg -ef /dev/rmt0 vg00 Creates vg00 backup but excludes files listed in the /etc/exclude.vg00
find / -print | backup -ivf /dev/rmt0 Backup entire system to rmt0
backup -0vf /dev/rmt0 /home Backup /home directory to rmt0 with backup level 0
restore -Tvf /dev/rmt0 List the archive in rmt0
restore -xvf /dev/rmt0 /home Restore /home from archive in device rmt0
find ./home -print |cpio -ocvumB > /dev/rmt0
Archives /home directory
cpio -icvdumB < /dev/rmt0 Restores cpio archive from rmt0
cpio -ivt < /dev/rmt0 List the contents of cpio archive from rmt0
cpio -icvd < /dev/rmt0 /home Restores /home directory from rmt0
tar -cvf /dev/rmt0 /home Archives /home to rmt0 device
tar -tvf /dev/rmt0 List the archives in rmt0
tar -xvf /dev/rmt0 /home Extract /home from rmt0
dd if=si of=si1 conv=ebcdic Convert and copy ascii file si to ebcdic si1
dd if=/dev/rmt0 ibs=512 obs=1024 of=/dev/rmt1
To copy blocks from rmt0 with 512 blocks to rmt1 with 1024 blocks
tctl -f /dev/rmt0 rewind To rewind the tape
tctl -f /dev/rmt0 offline To eject the tape
tctl -f /dev/rmt0 status To show the status of tape
chdev -l rmt0 -a block_size=512 To change the block size of the tape to 512
Print commands
qchk -q To display the default q
qchk -P lp0 To display the status of the printer lp0
qchk -# 123 To display the status of job number 123
qchk -A To display the status of all queues
qcan -x 123 To cancel the print job 123
qcan -X -P lp0 To cancel all jobs submitted to lp0
qpri -#570 -a 25 To change the priority of the job to 25
qhld # 569 To hold the job 569
qhld -r -#569 To remove holding from 569
qmov -m lpa -#11 To move the job 11 to queue lpa
enable psq To enable queue psq
disable psq To disable queue psq
cancel -#111 To cancel job 111
lpstat To display the status all queues
lpstat -p lp0 To display the status of print queue lp0
lpstat -u root To display the jobs submitted by user root
lpq -P lp0 To display the status of queue lp0
last To list all the records in the /var/adm/wtmp file
last |grep shutdown To show the shutdown sessions
uptime (w -u ) To show how long the system has been up
Licensing commands
oslevel To list the operating system level
lslicense To see the number of license
chlicense -u30 To change the fixed user license to 30
chlicense -f on To enable floating user license
User commands
id To list all system identifications for current user
id -gn To list the default group for current user
id -Gn To list all system groups for current user
lsuser root To list the attribute of user root
lsuser ALL To list the attributes of all users
lsuser -a HOME ALL To list the home directory of all users
lsuser -a ALL To list all usernames
lsuser -a auth1 auth2 ALL To list the authentication method for all users
lsuser -a expires ALL To list expiry date
lsuser -a account_locked ALL To check account lock status of all users
chuser -a login=true san To enable the user san
chuser -a rlogin=true san Enable san to login remotely
mkuser si Creates user si with default values in /usr/lib/security/mkuser.defalault
mkuser su=false si Create user si without su facility
rmuser si To remove user si
rmuser -p si To remove user si and his all attributes
who List users with tty nos and ip numbers
who /var/adm/wtmp Lists history of login logout system startup and shutdowns
who -r To list the run level
who am i /who -m To list the current user
mkgroup dcm To create the group dcm
chgroup users=u1,u2,u3 dcm To add users u1 u2 and u3 to dcm group
rmgroup dcm To delete the group dcm
chauthent To change the authentication methods
Subsystem Commands
lssrc -a To list the status of all subsystems
lssrc -h node1 -a To list the status of all subsystems on foreign host node1
lssrc -s kadmind To list the status of the subsystem kadmind
lssrc -g tcpip To get the status of the subsystem group tcpip
mkssys To add a subsystem
rmssys -s kerberos To remove the subsystem kerberos
chssys -s kerb -s kad To rename the subsystem kerb to kad
startsrc -s kadmin To start the subsystem kadmin
startsrc -g tcpip To start the subsystem group tcpip
stopsrc -s kadmin To stop the subsystem kadmin
stopsrc -g tcpip To stop the subsystem group tcpip
refresh -s nfsd To refresh nfsd subsystem
refresh -g tcpip To refresh tcpip subsystem group
Scheduling commands
crontab -l To list the crontab entries
crontab -e To edit the crontab entries
crontab -l > /si To copies the entries of crontab to /si file
crontab -r To remove all crontab entries
crontab -v To list the submission time
/var/adm/cron/cron.allow File containing users who allowed cron service
/var/adm/cron/cron.deny File containing users denied cron service
at -l To list the jobs scheduled via at command
at -r root.dfjdhjdh.21 To remove the scheduled job root.dfjdhjdh.21
/var/adm/cron/at.allow File containing users who allowed at service
/var/adm/cron/at.deny File containing users denied at service
batch To run the command when the system load permits
atq joe To list all the jobs submitted by user joe
ODM Commands
odmget sm_menu_opt
To get the objects from class sm_menu_opt
odmget -q "id=licenses" sm_menu_opt
To list objects that matches query id=licenses from object sm_menu_opt
odmdelete -o sm_menu_opt -q "id=licenses"
To delete the entries from class sm_menu_opt which agrees the query id=licenses
odmshow sm_menu_opt
To show the object class definition
odmdrop -o sm_menu_opt
To drop sm_menu_opt object class
odmchange -o sm_menu_opt -q "id=licenses" file1
To change the attributes from file1
errpt To display complete summary of report
errpt -a To list complete detailed report
errpt -d H To list all hardware related errors
errpt -d S To list all software related errors
errpt -a -j 34564423 To list detailed error report of error id 34564423
chitab tty002:23:respawn:/usr/sbin/getty /dev/tty
To enter the entry tty002:23:respawn:/usr/sbin/getty /dev/tty in inittab
lssrc -g portmap To start tcpip
HACMP Commands
logs
/tmp/hacmp.out Detailed event script output logged in 7 day rolling history
/var/adm/cluster.log High level view of cluster events (No clean up on this file)
/usr/sbin/cluster/history/cluster.mmdd Day by day view of cluster events. (one file / day of month)
/tmp/cm.log Clstrmgr messages
/tmp/cspoc.log Output from C-SPOC commands (similar to smit.log)
/tmp/emuhacmp.out Output from event emulation
rdist -b -f /etc/disfile1 To distribute the files in disfile1 to all nodes in disfile1 in binary mode
Sample entry for disfile1
HOSTS = ( root@node1 root@node3 )
FILES = ( /etc/passwd /etc/security/passwd)
${FILES} -> ${HOSTS}
clstart -m -s -b -i -l To start cluster daemons (m-clstrmgr, s-clsmuxpd,
b-broadcast message, -i-clinfo, -l cllockd)
clstop -f -N To force shutdown cluster immediately without releasing resources
clstop -g -N To do graceful shutdown immediately with no takeover
clstop -gr -N To do graceful shutdown immediately with takeover
cldare -t To sync the cluster toplogy
cldare -t -f To do the mock sync of topology
cldare -r To sync the cluster resources
cldare -r -f To do the mock sync of resources
clverify cluster verification utility
cllscf To list clustur topology information
cllsclstr To list the name and security level of the cluster
cllsnode To list the info about the cluster nodes
cllsnode -i node1 To list info about node1
cllsdisk -g shrg To list the PVID of the shared hard disk for resource group shrg
cllsnw To list all cluster networks
cllsnw -n ether1 To list the details of network ether1
cllsif To list the details by network adapter
cllsif -n node1_service To list the details of network adapter node1_service
cllsvg To list the shared vgs which can be accessed by all nodes
cllsvg -g sh1 To list the shared vgs in resource group sh1
cllslv To list the shared lvs
cllslv -g sh1 To list the shared lvs in the resource group sh1
cllsdisk -g sh1 To list the PVID of disks in the resource group sh1
cllsfs To list the shared file systems
cllsfs -g sh1 To list the shared file systems in the resource group sh1
cllsnim Show info about all network modules
cllsnim -n ether Show info about ether network module
cllsparam -n node1 To list the runtime parameters for the node node1
cllsserv To list all the application servers
claddclstr -i 3 -n dcm To add a cluster definition with name dcm and id 3
claddnode To add an adapter
claddnim To add network interface module
claddgrp -g sh1 -r cascading -n n1 n2 To create resource group sh1 with nodes n1,n2 in cascade
claddserv -s ser1 -b /usr/start -e /usr/stop Creates an application server ser1 with startscript as /usr/start
and stop script as /usr/stop
clchclstr -i 2 -n dcmds To change cluster definitions name to dcmds and id to 2
clchclstr -s enhanced To change the clustur security to enhanced
clchnode To change the adapter parameters
clchgrp To change the resource group name or node relationship
clchparam To change the run time parameters (like verbose logging)
clchserv To change the name of app. server or change the start/end scripts
clrmclstr To remove the cluster definition
clrmgrp -g sh1 To delete the resource group sh1 and related resources
clrmnim ether To remove the network interface module ether
clrmnode -n node1 To remove the node node1
clrmnode -a node1_svc To remove the adapter named node1_svc
clrmres -g sh1 To remove all resources from resource group sh1
clrmserv app1 To remove the application server app1
clrmserv ALL To remove all applicaion servers
clgetactivenodes -n node1 To list the nodes with active cluster manager processes from cluster
manager on node node1
clgetaddr node1 returns a pingable address from node node1
clgetgrp -g sh1 To list the info about resource group sh1
clgetgrp -g sh1 -f nodes To list the participating nodes in the resource group sh1
clgetif To list interface name/interface device name/netmask associated with
a specified ip label / ip address of a specific node
clgetip sh1 To get the ip label associated to the resource group
clgetnet 193.9.200.2 255.255.255.0 To list the network for ip 193.9.200.2, netmask 255.255.255.0
clgetvg -l nodelv To list the VG of LV nodelv
cllistlogs To list the logs
clnodename -a node5 To add node5 to the cluster
clnodename -o node5 -n node3 To change the cluster node name node5 to node3
clshowres Lists resources defined for all resource group
clfindres To find the resource group within a cluster
xclconfig X utility for cluster configuration
xhacmpm X utility for hacmp management
xclstat X utility for cluster status
NIM Commands
nimconfig -a pif_name=en0 -a netname=net1
To initialise the NIM master with network name net1
nimconfig -r To rebuild /etc/niminfo file which contains the variables for NIM
nim -o define -t lpp_source -a source=/dev/cd0 -a server=master -a location=/export/lpp_source/lpp_source1 lpp_source1
To define lpp_source1 image in /export/lpp_source/lpp_source directory from source cd0
nim -o define -t mksysb -a server=master -a location=/resources/mksysb.image mksysb1
To define mksysb resource mksysb1, from source /resources/mksysb.image on master
nim -o remove inst_resource To remove the resource inst_resource
nim -o check lpp_source1 To check the status of lpp_source lpp_source1
nim -o allocate -a spot=spot1 -a lpp_source=lpp_source1 node1 To allocate the resources spot1 and lpp_source1 to the the client node1
nim -o bos_inst node1 To initialise NIM for the BOS installation on node1 with the allocated resources
nim -o dkls_init dcmds To initialize the machine dcmds as diskless operation
nim -o dtls_init dcmds To initialize the machine dcmds for dataless operation
nim -o cust dcmds To initialize the machine dcmds for customize operation
nim -o diag dcmds To initialize the machine dcmds for diag operation
nim -o maint dcmds To initialize the machine dcmds for maintenance operation
nim -o define -t standalone -a platform=rspc -a if1="net1 dcmds xxxxx" -a cable_type1=bnc dcmds
To define the machine dcmds as standalone with platform as rspc and network as net1 with cable
type bnc and mac address xxxxx
nim -o unconfig master To unconfigure nim master master
nim -o allocate -a spot=spot1 dcmds
To allocate the resource spot1 from machine dcmds
nim -o deallocate -a spot=spot1 dcmds
To de allocate the resource spot1 from machine dcmds
nim -o remove dcmds To re move machine dcmds after removing all resources associated to it
nim -o reboot dcmds To reboot ther client dcmds
nim -o define -t lpp_source -a location=/software/lpp1 -a server=master -a source=/dev/cd0 lpp1
To define lppsource lpp1 on master at /software/lpp1 directory from source device /dev/cd0
lsnim To list the nim resources
lsnim -l dcmds To list the detailed info about the object dcmds
lsnim -O dcmds To list the operation dcmds object can support
lsnim -c resources dcmds To list the resources allocated to the machine dcmds
nimclient The client version of nim command (User can obtain same results of nim in server )
Thursday, April 7, 2011AIX PERFORMANCE MONITORING WITH EXAMPLES
Displaying the top 10 CPU-consuming processes
# ps aux | head -1; ps aux | sort -rn +2 | head -10
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 8196 21.5 0.0 48 40 - A May 11 3577:57 wait
root 45078 18.7 0.0 48 40 - A May 11 3110:34 wait
tsm1 274632 0.2 2.0 33240 13616 - A May 11 31:54 db2sysc 0
root 552976 0.1 0.0 1400 1436 - A May 13 8:00 dtgreet
root 532694 0.1 0.0 72 72 - A May 12 16:07 trclogio
you 638978 0.0 0.0 288 80 pts/2 A May 14 0:00 rlogin cws
you 540676 0.0 0.0 780 820 pts/2 A May 14 0:00 -ksh
you 495768 0.0 0.0 296 88 pts/2 A May 14 0:00 rlogin cws
you 397328 0.0 0.0 780 820 pts/2 A May 14 0:00 -ksh
you 221224 0.0 0.0 776 816 pts/2 A May 14 0:00 -ksh
Displaying number of processors in the system
# lsdev -Cc processor
proc0 Available 00-00 Processor
Displaying the top 10 memory-consuming processes using SZ
# ps -ealf | head -1 ; ps -ealf | sort -rn +9 | head
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
242001 A tsm1 331940 1 0 60 20 17346400 75688 * May 11 - 6:41 /opt/tivoli/tsm/server/bin/dsmserv -u tsm1 -i /home/tsm1/tsminst1 -q
242001 A pconsole 499926 471054 0 60 20 1f34e400 70500 * May 14 - 2:15 /usr/java5/bin/java -Xmx512m -Xms20m -Xscmx10m -Xshareclasses -Dfile.
encoding=UTF-8 -Xbootclasspath/a:/pconsole/lwi/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/rcpbootcp.jar:/pconsole/lwi/lib/ISCJaasModul
e.jar:/pconsole/lwi/lib/icl.jar:/pconsole/lwi/lib/jaas2zos.jar:/pconsole/lwi/lib/jaasmodule.jar:/pconsole/lwi/lib/lwinative.jar:/pconsole/lwi/lib/lwinl1.jar:/pc
onsole/lwi/lib/lwinl2.jar:/pconsole/lwi/lib/lwinl3.jar:/pconsole/lwi/lib/lwirolemap.jar:/pconsole/lwi/lib/passutils.jar -Xverify:none -cp eclipse/launch.jar:ecl
ipse/startup.jar:/pconsole/lwi/runtime/core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200/launcher.jar com.ibm.lwi.LaunchLWI
40401 A tsm1 274632 356590 0 60 20 1c56d400 33240 * May 11 - 31:55 db2sysc 0
242001 A tsm1 430296 356590 0 60 20 105e1400 16476 * May 11 - 3:06 db2acd 0
240001 A root 294918 188528 0 60 20 17b26400 14068 May 11 - 7:15 /usr/sbin/dpid2
240001 A root 163928 86110 0 60 20 c17d400 10348 f1000100194d55e0 May 11 - 1:15 /usr/lpp/X11/bin/X -cc 4 -D /usr/lib/X11//rgb -T -force :0 -au
th /var/dt/A:0-LfufUa
242001 A tsm1 233690 356590 0 60 20 11b20400 6696 * May 11 - 3:55 db2fmp (C) 0
242001 A tsm1 450620 356590 0 60 20 11be0400 3408 * May 11 - 0:00 db2fmp (idle) 0
240001 A root 737438 188528 0 39 20 1df0a400 2840 * May 14 - 0:02 /usr/sbin/rsct/bin/vac8/IBM.CSMAgentRMd
240001 A root 180370 188528 0 60 20 2253400 2280 May 11 - 0:14 sendmail: accepting connections
#
Displaying the processes in order of being penalized
# ps -eakl | head -1 ; ps -eakl | sort -rn +5
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
303 A 0 57372 0 120 16 -- 1030000 68 3d2af70 - 2:20 wlmsched
303 A 0 12294 0 120 17 -- 19008000 56 - 0:14 sched
303 A 0 0 0 120 16 -- 15004000 60 - 3:25 swapper
10307 Z 0 32784 0 20 254 rt 0:00 <defunct>
240005 A 0 614566 622792 1 60 20 a0f9400 836 pts/1 0:00 ksh
200001 A 0 524388 614566 1 60 20 1f369400 920 pts/1 0:00 ps
340001 A 0 352462 188528 0 39 20 1a44b400 2124 f10008071001d640 - 0:00 rmcd
242001 A 1002 450620 356590 0 60 20 11be0400 3408 * - 0:00 db2fmp
242001 A 1002 430296 356590 0 60 20 105e1400 16476 * - 3:06 db2fmp
242001 A 1002 331940 1 0 60 20 17346400 75688 * - 6:41 dsmserv
242001 A 1002 233690 356590 0 60 20 11b20400 6696 * - 3:55 db2fmp
242001 A 8 499926 471054 0 60 20 1f34e400 70500 * - 2:15 java
240401 A 0 463082 188528 0 60 20 4b75400 348 * - 0:00 dfpd
240401 A 0 372928 1 0 60 20 7296400 100 28e4b28 - 0:00 uprintfd
240401 A 0 311494 1 0 60 20 1e34f400 1112 f10001001a54f8b0 - 1:59 db2fmcd
240401 A 0 307400 188528 0 60 20 1f3ce400 1600 * - 0:00 IBM.ServiceRMd
240401 A 0 135380 188528 0 60 20 1a04c400 680 - 0:00 nimesis
240001 A 8 635014 499926 0 60 20 e5f8400 292 f10001001563c1e8 - 0:00 pconsole_exec
240001 A 8 471054 569380 0 60 20 4435400 816 - 0:00 ksh
240001 A 1 557274 1 0 60 20 1f0ad400 2100 - 0:00 sendmail
240001 A 0 737438 188528 0 39 20 1df0a400 2840 * - 0:02 IBM.CSMAgentRMd
240001 A 0 581740 188528 0 60 20 ab18400 332 f1000200067374c8 - 0:00 tftpd
240001 A 0 569380 188528 0 60 20 13462400 816 - 0:00 ksh
240001 A 0 561364 409748 0 60 20 2877400 788 pts/2 0:00 ksh
240001 A 0 552976 434188 0 60 20 5393400 1400 - 8:01 dtgreet
240001 A 0 479486 418030 0 60 20 1818f400 788 f1000200008f1478 pts/0 0:00 ksh
240001 A 0 475280 1 0 27 20 1a72f400 1216 * - 0:30 posixtrace
240001 A 0 458982 188528 0 60 20 12b63400 408 - 0:00 timed
240001 A 0 454892 188528 0 60 20 1eb4f400 428 - 0:08 routed
240001 A 0 446576 577610 0 60 20 1c7ae400 784 pts/4 0:00 ksh
240001 A 0 393352 188528 0 60 20 b89a400 548 - 0:00 dhcpcd
240001 A 0 368828 188528 0 60 20 142e5400 316 f1000010dd008010 - 0:00 qdaemon
240001 A 0 360628 188528 0 60 20 f2be400 328 f10001001a4ae3a0 - 0:00 rpc.lockd
Displaying the processes in order of priority
# ps -eakl | sort -n +6 | head
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
303 A 0 0 0 120 16 -- 15004000 60 - 3:25 swapper
303 A 0 16392 0 0 16 -- 1b00a000 64 f100080009786c08 - 0:26 lrud
303 A 0 24588 0 0 16 -- 1f00e000 108 - 0:00 vmmd
303 A 0 28686 0 0 16 -- 1010000 52 - 0:00 memgrdd
303 A 0 57372 0 120 16 -- 1030000 68 3d2af70 - 2:20 wlmsched
303 A 0 61470 0 0 16 -- 3032000 52 - 0:00 armtrace_kproc
303 A 0 12294 0 120 17 -- 19008000 56 - 0:14 sched
40201 A 0 98416 0 0 17 20 8119000 136 * - 0:00 dog
240001 A 0 475280 1 0 27 20 1a72f400 1216 * - 0:30 posixtrace
#
Displaying the processes in order of time
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +3 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
8196 - A 3581:13 0 48 40 xx 0 0 21.5 0.0 wait
45078 - A 3113:23 0 48 40 xx 0 0 18.7 0.0 wait
532694 - A 16:07 0 72 72 32768 0 0 0.1 0.0 trclogio
552976 - A 8:01 0 1356 1436 xx 48 80 0.1 0.0 dtgreet
294918 - A 7:16 218 14052 14000 32768 27 24 0.0 2.0 /usr/sbi
168044 - A 4:32 91 544 392 xx 3 4 0.0 0.0 /usr/sbi
254082 - A 3:15 995 216 192 32768 0 0 0.0 0.0 nfsd
0 - A 3:25 7 60 48 xx 0 0 0.0 0.0 swapper
57372 - A 2:20 0 68 32 xx 0 0 0.0 0.0 wlmsched
53274 - A 2:06 0 120 96 xx 0 0 0.0 0.0 gil
Displaying the processes in order of real memory use
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +6 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
294918 - A 7:16 218 14052 14000 32768 27 24 0.0 2.0 /usr/sbi
163928 - A 1:15 1059 7132 3448 xx 3219 1128 0.0 0.0 /usr/lpp
737438 - A 0:02 264 2056 2468 xx 788 412 0.0 0.0 /usr/sbi
352462 - A 0:00 301 1584 2084 xx 542 500 0.0 0.0 /usr/sbi
180370 - A 0:14 137 1096 1596 32768 1187 1000 0.0 0.0 sendmail
307400 - A 0:00 136 1344 1520 xx 258 176 0.0 0.0 /usr/sbi
552976 - A 8:01 0 1356 1436 xx 48 80 0.1 0.0 dtgreet
475280 - A 0:30 20 1144 1208 32768 73 64 0.0 0.0 posixtra
544916 pts/1 A 0:00 0 868 972 32768 80 104 0.0 0.0 ps vx
614566 pts/1 A 0:00 1 600 876 32768 240 276 0.0 0.0 -ksh
Displaying the processes in order of I/O
# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +4 | head -10
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
106632 - A 0:00 2338 136 152 xx 36 36 0.0 0.0 /usr/ccs
163928 - A 1:15 1059 7132 3448 xx 3219 1128 0.0 0.0 /usr/lpp
254082 - A 3:15 995 216 192 32768 0 0 0.0 0.0 nfsd
1 - A 0:09 549 708 492 32768 30 32 0.0 0.0 /etc/ini
352462 - A 0:00 301 1584 2084 xx 542 500 0.0 0.0 /usr/sbi
217218 - A 1:37 267 1076 452 32768 151 44 0.0 0.0 /usr/sbi
737438 - A 0:02 264 2056 2468 xx 788 412 0.0 0.0 /usr/sbi
294918 - A 7:16 218 14056 14004 32768 27 24 0.0 2.0 /usr/sbi
356590 - A 0:00 209 508 152 32768 54 48 0.0 0.0 db2wdog
290960 - A 0:00 166 1572 60 32768 46 8 0.0 0.0 /usr/sbi
Displaying WLM classes
# ps -a -o pid,user,class,pcpu,pmem,args
PID USER CLASS %CPU %MEM COMMAND
32784 <defunct>
221224 you Default 0.0 0.0 -ksh
397328 you Default 0.0 0.0 -ksh
467058 root System 0.0 0.0 ksh
487458 root System 0.0 0.0 -ksh
495768 you Default 0.0 0.0 rlogin cws
520194 root System 0.0 0.0 ps -a -o pid,user,class,pcpu,pmem,args
540676 you Default 0.0 0.0 -ksh
638978 you Default 0.0 0.0 rlogin cws
659554 root System 0.0 0.0 pg
708804 root System 0.0 0.0 pg
Determining the PID of wait processes
# ps vg | head -1 ; ps vg | grep -w wait
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
8196 - A 3582:56 0 48 40 xx 0 0 21.5 0.0 wait
45078 - A 3114:52 0 48 40 xx 0 0 18.7 0.0 wait
#
Posted by Shivakant Tiwari at 6:52 PM 1 comments Email This
BlogThis!
Share to Twitter
Share to Facebook
Share to Google Buzz
Links to this post
Labels: AIX ADVANCE COMMANDS, AIX PERFORMANCE MONITORING, AIX PERFORMANCE TOOLS EXAMPLES, L1 monitoring commands in AIX, ps for aix, ps in AIX
THURSDAY, MARCH 17, 2011
AIX PERFORMANCE TOOLS TPROF VMSTAT SAR AND MPSTAT EXAMPLES
THESE EXAMPLES ARE TAKEN FROM THE MAN PAGE OF THESE COMMANDS
TPROF EXAMPLES
1Basic global program and thread-level summary . This command will give you details of cpu utilization of each process
$ tprof -x sleep 10
Mon May 20 00:39:26 2002 System: AIX 5.2 Node: dreaming Machine: 000671894C00
Starting Command sleep 10
stopping trace collection.
Generating sleep.prof
The resulting sleep.prof file only contains the summary report section.
2 Global profiling with all options
$ tprof -skeuj -x sleep 10
Mon May 20 00:39:26 2002
System: AIX 5.2 Node: drea
ming Machine: 000671894C00
Starting Command sleep 10
stopping trace collection.
Generating sleep.prof
The resulting sleep.prof file contains the summary report and global profile sections.
3 Single process level profiling
$ tprof -u -p workload -x workload
Mon May 20 00:39:26 2002
System: AIX 5.2 Node: drea
ming Machine: 000671894C00
Starting Command workload stopping trace collection.
Generating workload.prof
The resulting workload.prof file contains the summary report and the global user mode profile sections, and one process level profile
section for the process 'workload' that contains only a user mode profile subsection.
4 Multiple process level profiling
$ tprof -se -p send,receive -x startall
Mon May 20 00:39:26 2002
System: AIX 5.2 Node: dreaming Machine: 000671894C00
Starting Command startall
stopping trace collection.
Generating startall.prof
The resulting startall.prof file contains the summary report, the global shared library mode profile, and the global kernel extension
profile sections, and two process level profile sections: one for the process 'send', and one for the process 'receive'. The process
level sections each contain two subsections: one with shared library profiling information and one with kernel extensions profiling
information.
5 Microprofiling and listing annotation
$ tprof -m ./tcalc -L ./tcalc -u -x ./tcalc
Mon May 20 00:47:09 2002
System: AIX 5.2 Node: dreaming Machine: 000671894C00
Starting Command ./tcalc
stopping trace collection.
Generating tcalc.prof
Generating tcalc.tcalc.c.mprof
Generating tcalc.tcalc.c.alst
The resulting tcalc.prof file contains the summary report and the global user mode profile sections. The resulting tcalc.tcalc.c.mprof
and tcalc.tcalc.c.alst files contain the micro-profiling report and the annotated listing.
6 For event-based profiling on processor cycles, sampling once every 100 milliseconds, enter:
tprof -E -f 100 -Askex sleep 10
Output similar to the following displays:
Starting Command sleep 10
stopping trace collection.
Tue Apr 26 14:44:02 2005
System: AIX 5.3 Node: bigdomino Machine: 00C0046A4C00
Generating sleep.trc
Generating sleep.prof
Generating sleep.syms
7 For event-based profiling on completed instructions, sampling once every 20,000 completed instructions, enter:
tprof -E PM_INST_CMPL -f 20000 -Askex sleep 10
Output similar to the following displays:
Starting Command sleep 10
stopping trace collection.
Tue Apr 26 14:42:44 2005
System: AIX 5.3 Node: bigdomino Machine: 00C0046A4C00
Generating sleep.trc
Generating sleep.prof
Generating sleep.syms
8 For event-based profiling on emulation interrupts, sampling once every 10,000 events, enter:
tprof -E EMULATION -Askex sleep 10
Output similar to the following displays:
Starting Command sleep 10
stopping trace collection.
Tue Apr 26 14:41:44 2005
System: AIX 5.3 Node: bigdomino Machine: 00C0046A4C00
Generating sleep.trc
Generating sleep.prof
Generating sleep.syms
9 Automated offline mode
tprof -c -A all -x sleep 10
Starting Command sleep 10
stopping trace collection.
Mon May 20 00:52:52 2002
System: AIX 5.2 Node: dreaming Machine: 000671894C00
Generating sleep.ctrc
Generating sleep.csyms
Generating sleep.prof
The resulting sleep.prof file only has a summary report section, while the two cooked files are ready to be re-postprocessed.
10 Automated offline mode enabling source line collecting.
$ tprof -A -N -x sleep 10
Starting Command sleep 10
stopping trace collection.
Wed Feb 8 15:12:41 2006
System: AIX 5.3 Node: aixperformance Machine: 000F9F3D4C00
Generating sleep.trc
Generating sleep.prof
Generating sleep.syms
The resulting sleep.prof file only contains the summary report section, while sleep.syms contains the source line information.
11 Automated offline mode enabling source line and instruction collecting.
$ tprof -A -N -I -r RootString -x sleep 10
Starting Command sleep 10
stopping trace collection.
Wed Feb 8 15:16:37 2006
System: AIX 5.3 Node: aixperformance Machine: 000F9F3D4C00
Generating RootString.trc
Generating RootString.prof
Generating RootString.syms
The resulting rootstring.prof file is generated, while rootstring.syms contains the source line information and binary instructions.
12 Real-time mode enabling Java source line and instructions collecting.
$ tprof -N -I -x java -Xrunjpa:source=1,instructions=1 HelloAIX
Thu Feb 9 13:30:38 2006
System: AIX 5.3 Node: perftdev Machine: 00CEBB4A4C00
Starting Command java -Xrunvpn_jpa:source=1,instructions=1 HelloAIX
Hello AIX!
stopping trace collection.
Generating java.prof
The resulting java.prof file is generated, and it contains the JIT source line information as well as JIT instructions.
13 Processor usage for the vloop_lib_32 program with no shared library and thread-level profiling, no per-processor tracing, and no post
processing:
$ tprof -A -n -s -t -r test -x vloop_lib_32 5
Starting Command vloop_lib_32 5
stopping trace collection.
Generating test.trc
Generating test.syms
EXAMPLES OF SAR
1 To report system unit activity, enter:
sar
2 To report current tty activity for each 2 seconds for the next 40 seconds, enter: sar -y -r 2 20
3 To watch system unit for 10 minutes and sort data, enter: sar -o temp 60 10
4 To report processor activity for the first two processors, enter: sar -u -P 0,1
This produces output similar to the following:
cpu %usr %sys %wio %idle
0 45 45 5 5
1 27 65 3 5
5 To report message, semaphore, and processor activity for all processors and system-wide, enter: sar -mu -P ALL
On a four-processor system, this produces output similar to the following (the last line indicates system-wide statistics for all
processors):
cpu msgs/s sema/s %usr %sys %wio %idle
0 7 2 45 45 5 5
1 5 0 27 65 3 5
2 3 0 55 40 1 4
3 4 1 48 41 4 7
- 19 3 44 48 3 5
6 To see physical processor consumed and entitlement consumed for all processors system-wide, run sar command in a shared processor
logical partition machine, as follows:
sar -P ALL
On a two-logical processor system, this produces output similar to the following (the last line indicates system-wide statistics for all
processors, and the line with cpuid U indicates the system-wide Unused capacity):
cpu %usr %sys %wio %idle physc %entc
0 0 0 0 100 0.02 3.1
1 0 0 0 100 0.00 1.0
U - - 0 96 0.48 96.0
- 0 0 0 100 0.02 4.0
7 To report system call, kernel process, and paging activities with separate headers for each of the three lines of data at each iteration
for every 2 seconds for the next 40 seconds, enter:
sar -Mckr 2 20
8 To report all activities with multiple sets of headers for every 2 seconds for the next 40 seconds, enter:
sar -MA 2 20
VMSTAT EXAMPLES
1 To display a summary of the statistics since boot, enter:
vmstat
2 To display five summaries at 2-second intervals, enter:
vmstat 2 5
3 To display a summary of the statistics since boot including statistics for logical disks scdisk13 and scdisk14, enter:
vmstat scdisk13 scdisk14
4 To display fork statistics, enter:
vmstat -f
5 To display the count of various events, enter:
vmstat -s
6 To display time-stamp next to each column of output of vmstat, enter:
vmstat -t
7 To display the I/O oriented view with an alternative set of columns, enter:
vmstat -I
8 To display all the VMM statistics available, enter:
vmstat -vs
9 To display the large-page section with the alp and flp columns at 8-second intervals, enter:
vmstat -l 8
10 To display the VMM statistics specific to a particular page size (in the example, 4 K), enter:
vmstat -p 4 K
11 To display the VMM statistics for all page sizes that are supported on the system, enter:
vmstat -p ALL
OR
vmstat -p all
12 To display only the VMM statistics for a particular page size (in this example, 4K), enter:
vmstat -P 4K
13 To display only the per-page breakdown of VMM statistics for all supported page sizes, enter:
vmstat -P ALL
OR
vmstat -P all
MPSTAT EXAMPLES
1 To see the default set of utilization metrics, type:
mpstat 1 1
2 To see the default set of utilization metrics in wide display mode, type:
mpstat -w 1 1
3 To see the detailed dispatch & affinity metrics, type:
mpstat -d 1 1
4 To see the detailed interrupts report, type:
mpstat -i 1 1
5 To see all the statistics, type:
mpstat -a 1 1
6 To see simultaneous multi-threading utilization, type:
mpstat -s 1 1
Posted by Shivakant Tiwari at 12:53 PM 1 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX GENERAL DOCUMENTS, AIX PERFORMANCE MONITORING, AIX PERFORMANCE TOOLS TPROF VMSTAT SAR AND MPSTAT EXAMPLES
SATURDAY, FEBRUARY 26, 2011
AIX DISK PERFORMANCE MONITORING (DISK MONITORING )
To know if the disks are performing under permitted values
run iostat on disks connected to a adpater
#lsdev -p fscsi0
will show all the disk connected
run iostat on these disks to know their transfer rate
add the transfer rates of all the disk and
compare it with max_xfer_size
To get max_xfer_size
type command
lsattr -El fcs0
If max_xfer_size is lower than the kbs of all the disk collectively disk performance is comprimised
I had created a script for my usage change according to your usage
SCRIPT TO CALCULATE TOTAL DISK TRANSFER
d=0
for x in $(lsdev -p fscsi0|awk '{print $1}')
do
a=$(iostat -d $x |grep hdisk|awk '{print $3}')
d=$(echo "$a + $d"|bc)
done
echo CURRENT TRANSFER RATE IS $d
Posted by Shivakant Tiwari at 11:55 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: AIX PERFORMANCE MONITORING, CALCULATING DISK IO PERFORMANCE, HOW TO KNOW DISK PERFORMANCE IN AIX, HOW TO VERIFY DISK PERFORMANCE, script to calculate disk io performance
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)
TOTAL PAGEVIEWS
10,063
Your Ad Here
FEEDJIT
Your Ad Here
MONDAY, MAY 16, 2011
WORKING WITH WPAR - CREATING AND STARTING WPAR
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
CREATE A FILE SYSTEM TO BE USED BY WPAR
# crfs -v jfs2 -g vijayvg -a size=30G -m /wpar-file
File system created successfully.
31456116 kilobytes total disk space.New File System size is 62914560
PUT 700 PERMISSION ON THAT FILE SYSTEM
# mount /wpar-file
chmod -R 700 /wpar-file
CREATE A WPAR IN THE BASE DIRECTORY
This command will create a wpar with ip 193.9.200.230 with hostname shivawpar in directory /wpar-file/wpars
mkwpar -n shivawpar -N address=193.9.200.230 -d /wpar-file/wpars/
+---------- Space statistics (in 512 byte-blocks) ----------+
File system: /wpar-file/wpars, Free: 209512, Required: 137, Deficit: 0.
syncroot: Installing RPM file: /etc/cdrecord.conf
syncroot: RPM root packages are currently synchronized.
syncroot: Root part is currently synchronized.
syncroot: Returns Status = SUCCESS
Workload partition shivawpar created successfully.
mkwpar: 0960-390 To start the workload partition, execute the following as root: startwpar [-v] shivawpar
SHOW THE STATUS OF WPAR
# lswpar
Name State Type Hostname Directory
----------------------------------------------------
shivawpar D S shivawpar /wpar-file/wpars
SYNTAX OF START WPAR
Usage: startwpar [-a] [-m] [-v] [-1 [-R] | -2 [-e 'environment'] | -I] wparName
Flags:
-1 = Phase 1 - load.
-2 = Phase 2 - start initial process.
-a = Automatically resolve erroneous/conflicting settings.
-e = Environment string to pass through to alternate initial process.
-I = Only exec default initial process.
-m = Maintenance mode - starts workload partition with no network interfaces.
-R = Flag the workload partition as restarted (from checkpoint).
-v = Verbose mode.
STARTING A WPAR
# startwpar -v shivawpar
Starting workload partition shivawpar.
Mounting all workload partition file systems.
Mounting /wpar-file/wpars
Mounting /wpar-file/wpars/home
Mounting /wpar-file/wpars/opt
Mounting /wpar-file/wpars/proc
Mounting /wpar-file/wpars/tmp
Mounting /wpar-file/wpars/usr
Mounting /wpar-file/wpars/var
Loading workload partition.
Exporting workload partition devices.
Starting workload partition subsystem cor_shivawpar.
0513-059 The cor_shivawpar Subsystem has been started. Subsystem PID is 483472.
Verifying workload partition startup.
Return Status = SUCCESS.
STOPPING A WPAR
# stopwpar -v shivawpar
Stopping workload partition shivawpar.
Stopping workload partition subsystem cor_shivawpar.
0513-044 The cor_shivawpar Subsystem was requested to stop.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Shutting down all workload partition processes.
WPAR='shivawpar' CID=1
ID=9437199 KEY=0x4107001c UID=0 GID=9 RT=-1
ID=624951327 KEY=0xffffffff UID=0 GID=0 RT=-1
Unmounting all workload partition file systems.
Umounting /wpar-file/wpars/var.
Umounting /wpar-file/wpars/usr.
Umounting /wpar-file/wpars/tmp.
Umounting /wpar-file/wpars/proc.
Umounting /wpar-file/wpars/opt.
Umounting /wpar-file/wpars/home.
Umounting /wpar-file/wpars.
Return Status = SUCCESS.
LOGIN TO WPAR
# clogin shiwawpar
Workload partition shiwawpar is not found.
# clogin shivawpar
*******************************************************************************
* *
* *
* Welcome to AIX Version6.1! *
* *
* *
* Please see the README file in /usr/lpp/bos for information pertinent to *
* this release of the AIX Operating System. *
* *
* *
*******************************************************************************
Posted by Shivakant Tiwari at 8:55 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: CREATING A WPAR, LOGINA WPAR, WPAR
WORKING WITH WPARS
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
1)STARTING A LPAR
# startwpar -v shivawpar
Starting workload partition shivawpar.
Mounting all workload partition file systems.
Mounting /wpar-file/wpars
Mounting /wpar-file/wpars/home
Mounting /wpar-file/wpars/opt
Mounting /wpar-file/wpars/proc
Mounting /wpar-file/wpars/tmp
Mounting /wpar-file/wpars/usr
Mounting /wpar-file/wpars/var
Loading workload partition.
Exporting workload partition devices.
Starting workload partition subsystem cor_shivawpar.
0513-059 The cor_shivawpar Subsystem has been started. Subsystem PID is 483472.
Verifying workload partition startup.
Return Status = SUCCESS.
2)STOPPING A WPAR
# stopwpar -v shivawpar
Stopping workload partition shivawpar.
Stopping workload partition subsystem cor_shivawpar.
0513-044 The cor_shivawpar Subsystem was requested to stop.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Shutting down all workload partition processes.
WPAR='shivawpar' CID=1
ID=9437199 KEY=0x4107001c UID=0 GID=9 RT=-1
ID=624951327 KEY=0xffffffff UID=0 GID=0 RT=-1
Unmounting all workload partition file systems.
Umounting /wpar-file/wpars/var.
Umounting /wpar-file/wpars/usr.
Umounting /wpar-file/wpars/tmp.
Umounting /wpar-file/wpars/proc.
Umounting /wpar-file/wpars/opt.
Umounting /wpar-file/wpars/home.
Umounting /wpar-file/wpars.
Return Status = SUCCESS.
3)REMOVING A WPAR
# rmwpar shivawpar
rmwpar: Removing file system /wpar-file/wpars/var.
rmlv: Logical volume fslv14 is removed.
rmwpar: Removing file system /wpar-file/wpars/usr.
rmwpar: Removing file system /wpar-file/wpars/tmp.
rmlv: Logical volume fslv13 is removed.
rmwpar: Removing file system /wpar-file/wpars/proc.
rmwpar: Removing file system /wpar-file/wpars/opt.
rmwpar: Removing file system /wpar-file/wpars/home.
rmlv: Logical volume fslv12 is removed.
rmwpar: Removing file system /wpar-file/wpars.
rmlv: Logical volume fslv01 is removed.
4)LOGIN TO A WPAR CONSOLE
# clogin shivawpar
*******************************************************************************
* *
* *
* Welcome to AIX Version 6.1! *
* *
* *
* Please see the README file in /usr/lpp/bos for information pertinent to *
* this release of the AIX Operating System. *
* *
* *
*******************************************************************************
5)VIEWING A WPAR STATE
# lswpar -a name,active
Name Active
------------------
shivawpar yes
# lswpar -a name,active,shares_cpu,shares_memory
Name Active CPU Shares Memory Shares
---------------------------------------------
shivawpar yes
6)VIEWING DEVICES OF A WPAR
# lswpar -D
Name Device Name Type
-----------------------------------
shivawpar /dev/null pseudo
shivawpar /dev/tty pseudo
shivawpar /dev/console pseudo
shivawpar /dev/zero pseudo
shivawpar /dev/clone pseudo
shivawpar /dev/sad clone
shivawpar /dev/xti/tcp clone
shivawpar /dev/xti/tcp6 clone
shivawpar /dev/xti/udp clone
shivawpar /dev/xti/udp6 clone
shivawpar /dev/xti/unixdg clone
shivawpar /dev/xti/unixst clone
shivawpar /dev/error pseudo
shivawpar /dev/errorctl pseudo
shivawpar /dev/audit pseudo
shivawpar /dev/nvram pseudo
7)VIEWING ALL THE DETAILS OF WLPAR
# lswpar -L
=================================================================
shivawpar - Defined
=================================================================
GENERAL
Type: S
Owner: root
Hostname: shivawpar
WPAR-Specific Routing: no
Directory: /wpar-file/wpars
Start/Stop Script:
Auto: no
Private /usr: no
Checkpointable: no
Application:
NETWORK
Interface Address(6) Mask/Prefix Broadcast
-----------------------------------------------------------------
en2 193.9.200.230 255.255.255.0 193.9.200.255
USER-SPECIFIED ROUTES
Type Destination Gateway Interface
-----------------------------------------------------------------
FILE SYSTEMS
MountPoint Device Vfs Nodename Options
-----------------------------------------------------------------
/wpar-file/wpars /dev/fslv01 jfs2
/wpar-file/wpars/home /dev/fslv12 jfs2
/wpar-file/wpars/opt /opt namefs ro
/wpar-file/wpars/proc /proc namefs rw
/wpar-file/wpars/tmp /dev/fslv13 jfs2
/wpar-file/wpars/usr /usr namefs ro
/wpar-file/wpars/var /dev/fslv14 jfs2
RESOURCE CONTROLS
Active: yes
Resource Set:
CPU Shares:
CPU Limits:
Memory Shares:
Memory Limits:
Per-Process Virtual Memory Limit: unlimited
Total Processes:
Total Threads:
Total PTYs:
Total Large Pages:
Max Message Queue IDs:
Max Semaphore IDs:
Max Shared Memory IDs:
Max Pinned Memory:
OPERATION
Operation: none
Process ID:
Start Time:
SECURITY SETTINGS
Privileges: PV_AU_,PV_AU_ADD,PV_AU_ADMIN,PV_AU_PROC,PV_AU_READ,
PV_AU_WRITE,PV_AZ_ADMIN,PV_AZ_CHECK,PV_AZ_READ,PV_AZ_ROOT,
PV_DAC_,PV_DAC_GID,PV_DAC_O,PV_DAC_R,PV_DAC_RID,PV_DAC_UID,
PV_DAC_W,PV_DAC_X,PV_DEV_CONFIG,PV_DEV_QUERY,PV_FS_CHOWN,
PV_FS_CHROOT,PV_FS_CNTL,PV_FS_LINKDIR,PV_FS_MKNOD,
PV_FS_MOUNT,PV_FS_PDMODE,PV_FS_QUOTA,PV_KER_ACCT,
PV_KER_CONF,PV_KER_DR,PV_KER_EWLM,PV_KER_EXTCONF,
PV_KER_IPC,PV_KER_IPC_O,PV_KER_IPC_R,PV_KER_IPC_W,
PV_KER_NFS,PV_KER_RAC,PV_KER_RAS_ERR,PV_KER_REBOOT,
PV_NET_PORT,PV_PROC_CKPT,PV_PROC_CORE,PV_PROC_CRED,
PV_PROC_ENV,PV_PROC_PRIO,PV_PROC_PDMODE,PV_PROC_RAC,
PV_PROC_RTCLK,PV_PROC_SIG,PV_PROC_TIMER,PV_PROC_VARS,
PV_PROC_PRIV,PV_SU_UID,PV_TCB,PV_TP,PV_TP_SET,PV_MIC,
PV_MIC_CL,PV_LAB_,PV_LAB_CL,PV_LAB_CLTL,PV_LAB_LEF,
PV_LAB_SLDG,PV_LAB_SLDG_STR,PV_LAB_SL_FILE,PV_LAB_SL_PROC,
PV_LAB_SL_SELF,PV_LAB_SLUG,PV_LAB_SLUG_STR,PV_LAB_TL,
PV_MAC_,PV_MAC_CL,PV_MAC_R,PV_MAC_R_CL,PV_MAC_R_STR,
PV_MAC_R_PROC,PV_MAC_W,PV_MAC_W_CL,PV_MAC_W_DN,PV_MAC_W_UP,
PV_MAC_W_PROC,PV_MAC_OVRRD,PV_KER_SECCONFIG,
PV_PROBEVUE_TRC_USER,PV_PROBEVUE_TRC_USER_SELF
DEVICE EXPORTS
Name Type
-----------------------------------------------------------------
/dev/null pseudo
/dev/tty pseudo
/dev/console pseudo
/dev/zero pseudo
/dev/clone pseudo
/dev/sad clone
/dev/xti/tcp clone
/dev/xti/tcp6 clone
/dev/xti/udp clone
/dev/xti/udp6 clone
/dev/xti/unixdg clone
/dev/xti/unixst clone
/dev/error pseudo
/dev/errorctl pseudo
/dev/audit pseudo
/dev/nvram pseudo
8)VIEWING AND CHANGING CPU AND MEMORY RESOURCES OF WPAR
# lswpar -a cpu,memory
CPU Limits Memory Limits
----------------------------
0%-100%,100% 0%-100%,100%
# chwpar -R CPU=2%-10%,30% memory=2%-5%,20% shivawpar
# lswpar -a cpu,memory shivawpar
CPU Limits Memory Limits
--------------------------
2%-10%,30% 2%-5%,20%
#
Posted by Shivakant Tiwari at 8:54 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: CHANGING CPU AND MEMORY RESOURCES OF WPAR, REMOVING A WPAR, STARTING A WPAR, STOPPING, WPAR
WPAR BACKUP AND RESTORE
ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM
TAKE BACKUP OF SHIVAWPAR IN A FILE
# savewpar -f /wpar-file/shivawpar.back shivawpar
Creating information file for workload partition shivawpar.
Creating list of files to back up.
Backing up 6238 files.
6238 of 6238 files (100%)0512-038 savewpar: Backup Completed Successfully.
FOR TEST PURPOSE WE ARE GOING TO REMOVE WPAR SHIVAWPAR
1) STOP SHIVAWPAR
# stopwpar shivawpar
Stopping workload partition shivawpar.
Stopping workload partition subsystem cor_shivawpar.
0513-044 The cor_shivawpar Subsystem was requested to stop.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Shutting down all workload partition processes.
Unmounting all workload partition file systems.
2)REMOVE THE CURRENT WPAR
# rmwpar shivawpar
rmwpar: Removing file system /wpar-file/wpars/var.
rmlv: Logical volume fslv14 is removed.
rmwpar: Removing file system /wpar-file/wpars/usr.
rmwpar: Removing file system /wpar-file/wpars/tmp.
rmlv: Logical volume fslv13 is removed.
rmwpar: Removing file system /wpar-file/wpars/proc.
rmwpar: Removing file system /wpar-file/wpars/opt.
rmwpar: Removing file system /wpar-file/wpars/home.
rmlv: Logical volume fslv12 is removed.
rmwpar: Removing file system /wpar-file/wpars.
rmlv: Logical volume fslv01 is removed.
RESTORE WPAR WITH FOLLOWING COMMAND
# restwpar -n shivawpar -f /wpar-file/shivawpar.back
New volume on /wpar-file/shivawpar.back:
Cluster size is 51200 bytes (100 blocks).
The volume number is 1.
The backup date is: Fri May 13 06:10:18 PAKDT 2011
Files are backed up by name.
The user is root.
x 2851 ./.savewpar_dir/wpar.spec
x 4655 ./.savewpar_dir/image.data
x 150544 ./.savewpar_dir/backup.data
The total size is 158050 bytes.
The number of restored files is 3.
mkwpar: Creating file systems...
/
Creating logical volume 'fslv01' specified in image.data
Creating file system '/' specified in image.data
/home
Creating logical volume 'fslv12' specified in image.data
Creating file system '/home' specified in image.data
/opt
/proc
/tmp
Creating logical volume 'fslv13' specified in image.data
Creating file system '/tmp' specified in image.data
/usr
/var
Creating logical volume 'fslv14' specified in image.data
Creating file system '/var' specified in image.data
Mounting all workload partition file systems.
New volume on /wpar-file/shivawpar.back:
Cluster size is 51200 bytes (100 blocks).
The volume number is 1.
The backup date is: Fri May 13 06:10:18 PAKDT 2011
Files are backed up by name.
The user is root.
x 15 ./.savewpar_dir/image.info
x 136 ./.savewpar_dir/data.files569476
x 136 ./.savewpar_dir/vgdata.files
x 3964 ./.savewpar_dir/filesystems
x 2851 ./.savewpar_dir/wpar.spec
x 4655 ./.savewpar_dir/image.data
x 150544 ./.savewpar_dir/backup.data
x 0 ./var
x 0 ./var/lost+found
x 0 ./var/adm
x 0 ./var/adm/cron
x 4 ./var/adm/cron/at.deny
x 3 ./var/adm/cron/cron.deny
x 284 ./var/adm/cron/log
x 1313 ./var/adm/cron/queuedefs
x 0 ./var/adm/cron/FIFO
x 0 ./var/adm/ras
x 1638 ./var/adm/ras/raspertune
x 199119 ./var/adm/ras/codepoint.cat
x 0 ./var/adm/ras/platform
x 57797 ./var/adm/ras/devinst.log
#
restore: 0511-102 Import of Access Control Lists failed.
The file system has read permission only.
restore: 0511-101 Import of Process Control Lists for file ./opt failed.
The file system has read permission only.
x 0 ./opt
./opt: The file system has read permission only.
x 0 ./proc
restore: 0511-102 Import of Access Control Lists failed.
The file system has read permission only.
restore: 0511-101 Import of Process Control Lists for file ./usr failed.
The file system has read permission only.
x 0 ./usr
./usr: The file system has read permission only.
The total size is 75699210 bytes.
The number of restored files is 6238.
syncroot: Processing root part installation status.
syncroot: Installp root packages are currently synchronized.
syncroot: RPM root packages are currently synchronized.
syncroot: Root part is currently synchronized.
syncroot: Returns Status = SUCCESS
Workload partition shivawpar created successfully.
mkwpar: 0960-390 To start the workload partition, execute the following as root: startwpar [-v] shivawpar
#
#
Posted by Shivakant Tiwari at 8:52 AM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: WPAR
Newer Posts Older Posts Home
FRIDAY, APRIL 22, 2011
TAKING MKSYSB BACKUP USING NIM
CREATE NIM MASTER
# nimconfig -a netname=testmaster -a pif_name=en0 -a platform=rspc -a cable_type1=tp -a netboot_kernel=up
0513-071 The nimesis Subsystem has been added.
0513-071 The nimd Subsystem has been added.
0513-059 The nimesis Subsystem has been started. Subsystem PID is 545010.
#
CREATE A STANDALONE MACHINE
# nim -o define -t standalone -a platform=rspc -a if1="find_net cws 0" nodecws
VIEW THE CURRENTLY CREATED MACHINE
# lsnim -l nodecws
nodecws:
class = machines
type = standalone
connect = shell
platform = rspc
netboot_kernel = mp
if1 = testmaster cws 0
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
#
ADD THE FILE SYSTEMS TO EXCLUDE
# echo "/tmp/" > /etc/exclude.rootvg
# echo "/export/nim/" >> /etc/exclude.rootvg
DEFINE MKSYSB RESOURCE AND USE MKSYSB REQUIRED SWITCHES
# nim -o define -t mksysb -a mk_image=yes -a mksysb_flags=e -a server=master -a location=/export/nim/mksysb -a source=nodecws cwsmksysb
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in 1024-byte blocks.)
+---------------------------------------------------------------------+
Required = 1048678 (1024 MB) Available = 10869900 (10615 MB)
Data compression will be used by the system backup utilities which
create the system backup image. This may reduce the required space
by up to 50 percent.
Creating information file (/image.data) for rootvg.....
Creating list of files to back up..
Backing up 29207 files..............................
5395 of 29207 files (18%)..............................
6282 of 29207 files (21%)..............................
6426 of 29207 files (22%)..............................
6452 of 29207 files (22%)..............................
7608 of 29207 files (26%)..............................
7648 of 29207 files (26%)..............................
7751 of 29207 files (26%)..............................
8086 of 29207 files (27%)..............................
9054 of 29207 files (30%)..............................
9481 of 29207 files (32%)..............................
10091 of 29207 files (34%)..............................
12922 of 29207 files (44%)..............................
13119 of 29207 files (44%)..............................
13354 of 29207 files (45%)..............................
22726 of 29207 files (77%)..............................
24617 of 29207 files (84%)........................
29207 of 29207 files (100%)
0512-038 savevg: Backup Completed Successfully.
Posted by Shivakant Tiwari at 5:49 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: aixG, mksysb backup using nim, mksysb on nim, nim -o define -t mksysb, NIM Commands, nim mksysb with mksysb switches, taking mksysb from network
THURSDAY, JANUARY 27, 2011
SIMPLEST NIM CONFIGURATION
SIMPLEST DOCUMENT TO IMPLEMENT NIM
1. Create a nim server
(Here netname is name of nim server , primary adapter in en0 , caple type is twisted pair, for a rs6000 server and for single processor )
# nimconfig -a netname=testnim -a pif_name=en0 -a cable_type=tp -a platform=rspc -a netboot_kernel=up
0513-071 The nimesis Subsystem has been added.
0513-071 The nimd Subsystem has been added.
0513-059 The nimesis Subsystem has been started. Subsystem PID is 602362.
Test the newly created server
# lsnim –l
master:
class = machines
type = master
max_nimesis_threads = 20
comments = machine which controls the NIM environment
platform = rspc
netboot_kernel = up
if1 = testnim galaxy 000D60DEFDAE
cable_type1 = tp
Cstate = ready for a NIM operation
prev_state =
Mstate = currently running
serves = boot
serves = nim_script
master_port = 1058
registration_port = 1059
reserved = yes
boot:
class = resources
type = boot
comments = represents the network boot resource
Rstate = ready for use
location = /tftpboot
alloc_count = 0
server = master
reserved = yes
nim_script:
class = resources
type = nim_script
comments = directory containing customization scripts created by NIM
Rstate = ready for use
location = /export/nim/scripts
alloc_count = 0
server = master
reserved = yes
testnim:
class = networks
type = ent
Nstate = ready for use
prev_state = information is missing from this object's definition
net_addr = 193.9.200.0
snm = 255.255.255.0
2. Define lpp source from cdrom
(Here source is cd0 , location is where we are storing lpp source and name is testlpp)
# nim -o define -t lpp_source -a server=master -a source=/dev/cd0 -a location=/export/lpp_source testlpp
Preparing to copy install images (this will take several minutes)...
Check the newly created lpp source
testlpp:
class = resources
type = lpp_source
arch = power
Rstate = ready for use
prev_state = unavailable for use
location = /export/lpp_source
simages = yes
alloc_count = 0
server = master
3. Define a spot from the lpp source
(Here source is the lpp we defined earlier , and location is where we are keeping our spot , name of the spot is spottest)
nim -o define -t spot -a server=master -a source=testlpp -a location=/export/spot spottest
Test the newly created spot
spottest:
class = resources
type = spot
plat_defined = chrp
arch = power
plat_defined = rs6k
plat_defined = rspc
bos_license = yes
Rstate = ready for use
prev_state = verification is being performed
location = /export/spot/spottest/usr
version = 5
release = 1
mod = 0
oslevel_r = 5100-01
alloc_count = 0
server = master
Rstate_result = success
mk_netboot = yes
mk_netboot = yes
4. Define machine
(Here platform is rs6000, xyz is the name of the host for which machine is created , and the name of resource is testpci)
# nim -o define -t standalone -a platform=rspc -a if1="find_net xyz 0" -a cable_type1=tp -a netboot_kernel=up testpci
Test the newly created machine
# lsnim -l testpci
testpci:
class = machines
type = standalone
connect = shell
platform = rspc
netboot_kernel = up
if1 = testnim pci 0
cable_type1 = tp
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
5. Allocate the RESOURCES
newly created lpp and spot resources to the newly cerated machine
## nim -o allocate -a spot=spottest -a lpp_source=testlpp testpci
6. Initiate bos installation on the machine
nim -o bos_inst -a accept_licenses=yes testpci
Posted by Shivakant Tiwari at 8:10 PM 0 comments
Email This BlogThis! Share to Twitter Share to Facebook Share to Google Buzz
Links to this post
Labels: EASY NIM CONFIGURATION USING COMMAND LINE, NIM Commands, NIM SIMPLE COMMANDS, NIM STEP BY STEP USING COMMANDS, SIMPLEST NIM CONFIGURATION
Digital transformation services meaning --
ReplyDeleteDigital transformation services refers to the process of using digital technologies to create new or modify existing business processes, culture, and customer experiences to meet changing business and market requirements. This transformation goes beyond traditional methods and embraces innovative solutions such as cloud computing, artificial intelligence, and big data analytics. The goal is to improve efficiency, increase value for customers, and stay competitive in a rapidly evolving digital landscape. Digital transformation involves rethinking the way an organization operates, integrating digital tools into all areas of the business, and fostering a culture that encourages experimentation and adapts quickly to new opportunities. This comprehensive change is essential for businesses to thrive in the modern era where digital interactions and data-driven decisions are paramount.