Solaris

IBM Work Intruction
-1-
UNIX Work Instructions
IBM Work Intruction
-2Table of Contents
IBM AIX Activities...................................................................................................................................... 5

File System Creation.................................................................................................................................... 6
Mirroring a root disk..................................................................................................................................... 6
For a Symmetrix LUN................................................................................................................................... 6
For an IBM DS LUN,.................................................................................................................................... 7
Kernel parameter Changes..........................................................................................................................7
Tuning Scheduler/Memory Load Control Tunable parameters.....................................................................7
Configuring Asynchronous IO...................................................................................................................... 8
Paging Space Size....................................................................................................................................... 8
Raw LV Creation.......................................................................................................................................... 9
To check the No. of Physical Processors currently Available,......................................................................9
To Check Internal SCSI disk drives on the Server.....................................................................................10
To Check EMC powerpath disks................................................................................................................10
Taking an OS Backup/mksysb................................................................................................................... 10
Pre-Restart Activities.................................................................................................................................. 12
To change the Network media Speed........................................................................................................15
Patch installation........................................................................................................................................ 16
ssh-keygen Generation.............................................................................................................................. 16
To establish the link on the Switch after connecting the fiber cables from the Storage.............................16
To check the WWPN of the Fiber card,......................................................................................................16
To analyse the Server error log report........................................................................................................17
Call Logging Format................................................................................................................................... 19
Hewlett Packard.......................................................................................................................................... 20
Check physical memory............................................................................................................................. 21
Check processor........................................................................................................................................ 21
Check mount point (mounted file systems)................................................................................................22
Check root and /var file system usage.......................................................................................................22
Detect new hardware................................................................................................................................. 22
Remove tape device files........................................................................................................................... 23
Before rebooting the server and after booting the OS...............................................................................23
Checking all the mount point are mounted properly...................................................................................24
Set Parameter............................................................................................................................................ 25
For Static Parameter.................................................................................................................................. 26
For Dynamic Parameter............................................................................................................................. 26
Ignite backup.............................................................................................................................................. 26
Unlocking the user..................................................................................................................................... 27
Enable FTP TELNET and RSH services....................................................................................................27
Password Reset......................................................................................................................................... 27
File system create (If the OS is fresh)........................................................................................................28
If GUNZIP is not working in oracle user account........................................................................................28
Changing permission and ownership of mount points...............................................................................28
User creation.............................................................................................................................................. 29
Hardware issues (will log a call with hp with serial number and model)....................................................29
Making the entry of hostname and ipaddress in /etc/hosts files.................................................................29
Configuring NTP client............................................................................................................................... 29
CRON access............................................................................................................................................. 30
Collecting sec audit report.......................................................................................................................... 30
For performance issue............................................................................................................................... 30
Linux Activities.............................................................................................................................................. 31
Check Processor........................................................................................................................................ 32
Check root and /var file system usage.......................................................................................................32
Before rebooting the server and after booting the OS...............................................................................33
Set all parameter ie network ,kernel ,vm....................................................................................................34
Changing permission and ownership of mount points...............................................................................36
SUN Solaris Activities............................................................................................................................ 38
Unlocking user Password...........................................................................................................................39
Check Physical Memory............................................................................................................................. 39
Check Processor........................................................................................................................................ 39
Checking weather the database is running or not......................................................................................39
Start, Stop or Refresh Services.................................................................................................................. 42
Check gateway........................................................................................................................................... 42
User creation.............................................................................................................................................. 43
IBM Work Intruction
-3-
Finding OS, Hostname, Version of OS, OS Level Patch, Model Details....................................................43

CRON Access............................................................................................................................................ 43
Performance Issue..................................................................................................................................... 44
Veritas File System Activities.....................................................................................................................44
FTP............................................................................................................................................................. 47
RCP Issue.................................................................................................................................................. 47
Package Installation................................................................................................................................... 47
Patch Installation........................................................................................................................................ 47
Adding and Removing Route.....................................................................................................................47
Additional Space Requirement.................................................................................................................... 48
Adding Space on CRM server.................................................................................................................... 49
AIX Server Installation and Patching..........................................................................................................51
AIX Server Installation................................................................................................................................ 52
AIX Server Patching................................................................................................................................... 62
BCV Work Instructions................................................................................................................................. 64
Prerequisite:............................................................................................................................................... 64
Steps for configuring Device Group (DG)..................................................................................................64
Daily Activities for BCV Backup:.................................................................................................................65
BCV is released to Veritas Team for tape...................................................................................................65
Creating Logical Volumes with the Device FileSuppose the device file name is /dev/rdsk/c3t5d2......66
Suppose the device file name is /dev/rdsk/c3t5d2....................................................................................67
File System Creation.................................................................................................................................... 68
Prerequisites:............................................................................................................................................. 68
Steps for File System Creation with AIX....................................................................................................68
Step for File System Creation with HP-UX.................................................................................................72
HP-UX Server Patching................................................................................................................................ 77
HP UX Patching How to:............................................................................................................................ 78
Boot Configuration..................................................................................................................................... 79
Create PV and add it to VG........................................................................................................................ 79
Copy boot utilities to new PV..................................................................................................................... 80
[Split LVs.................................................................................................................................................... 81
Create new FSTAB..................................................................................................................................... 81
Perform patching........................................................................................................................................ 82
Booting from alternate boot device........................................................................................................82
Booting into LV maintenance mode............................................................................................................82
Activating VG............................................................................................................................................. 84
Configuring the system with the new boot information...............................................................................84
Check new configuration............................................................................................................................ 85
Reboot................................................................................................................................................... 85
Finally, reboot the system...........................................................................................................................85
Boot from the alt PV................................................................................................................................... 85
Conclusion........................................................................................................................................... 85
Kernel Parameter Changes.......................................................................................................................... 85
Scheduler and memory load control tunable parameters..........................................................................85
MAXUPROC.......................................................................................................................................... 86
Asynchronous I/O tunable parameters.......................................................................................................87
Disk and disk adapter tunable parameters.................................................................................................88
LINUX Hardening and Installation...............................................................................................................88
Linux Hardening......................................................................................................................................... 88
Linux Operating System Installation...........................................................................................................91
LPAR Creation............................................................................................................................................. 104
New Space Requirement on UNIX Servers...............................................................................................114
Steps........................................................................................................................................................ 115
Post Completion tasks.............................................................................................................................. 115
SEC Audit Report Generation....................................................................................................................116
Steps........................................................................................................................................................ 116
Server Startup and Shutdown.................................................................................................................... 116
Prerequisites............................................................................................................................................. 116
Shutting Down Server Work Instructions...............................................................................................117
Starting Up Server Work Instructions....................................................................................................117
Service Request Closure............................................................................................................................118
Work Instructions...................................................................................................................................... 118
SUN Solaris Server Patching.....................................................................................................................122
Decide on which method you wish to install the cluster:..........................................................................122
Mirroring of ROOT File System.................................................................................................................124
USER ID Management................................................................................................................................ 127
User Addition............................................................................................................................................ 128
IBM Work Intruction
-4-
User deletion............................................................................................................................................ 128

User Modification..................................................................................................................................... 129
Unlocking a user on the system (HP-UX)................................................................................................129
Changing password for a user................................................................................................................. 129
Adding groups in a system....................................................................................................................... 130
Deleting group in a system....................................................................................................................... 130
Modifying group in a system.................................................................................................................... 130
USER ID Creation........................................................................................................................................ 131
Prerequisites............................................................................................................................................ 131
User creation in AIX/ HP-UX/ LINUX/ SOLARIS......................................................................................131
User creation in HP-UX using SAM.........................................................................................................133
Server Health Check................................................................................................................................... 137
CPU: Check for CPU usage (%).............................................................................................................137
Disk: To check disk usage & utilization.....................................................................................................137
File related parameters: To check if parameters are adequate................................................................137
To check memory status.......................................................................................................................... 137
To check top resource utilizing processes................................................................................................138
To check memory segment usages by users & size................................................................................138
To check system date & time................................................................................................................... 138
HP-UX Cluster Restarts.............................................................................................................................. 139
Solaris Solstice Work Instructions............................................................................................................141
SUN Solaris New Disk Creation.................................................................................................................142
FORMAT MENU:...................................................................................................................................... 142
PARTITION MENU:.................................................................................................................................. 142
FORMAT MENU:...................................................................................................................................... 143
PARTITION MENU:.................................................................................................................................. 143
FORMAT MENU:...................................................................................................................................... 144
PARTITION MENU:.................................................................................................................................. 145
FORMAT MENU:...................................................................................................................................... 145
SUN Solaris Operating System Backup (UFSDUMP)..............................................................................150
Condition 1:.............................................................................................................................................. 150
Condition 2:.............................................................................................................................................. 150
Veritas File System Creation...................................................................................................................... 150
Vendor Call Log Details.............................................................................................................................. 152
HP............................................................................................................................................................ 153
IBM........................................................................................................................................................... 153
Sun........................................................................................................................................................... 153
Dept . Code / Project Code ( for IBM Only)...............................................................................................153
Appendix...................................................................................................................................................... 154
IBM Work Intruction
IBM AIX Activities
-5-
IBM Work Intruction
-6-
File System Creation

#mkvg -y datavg hdisk2
#Creating a Volume Group using a PV/hdisk2
#mklv -t jfs2 -y datavglvol1 datavg 40
#Creating a Logical Volume datavglvol1 of size 40 PPs
Creates a LV datavglvol1 of size 10GB (40*256MB)

To check the Physical Partition Size,do a lsvg VGName|grep "PP Size"
#crfs -v jfs2 -d datavglvol1 -m /oracle -p rw -A yes -a agblksize=4096
(Creating a File System /oracle)
#mount /oracle
#df g /oracle
Mirroring a root disk

Confirm the disk that has the OS boot image by #lsvg rootvg -l
Check if #bootlist -m normal -o shows a blv=hd5 for hdiskx
To mirror it to hdisky,
#mirrorvg -S rootvg hdiskx hdisky
#bosboot -ad hdisky
#bootlist -m normal hdiskx hdisky
#bootlist -m normal -o
hdiskx blv=hd5
hdisky blv=hd5
For a Symmetrix LUN

On a Server with Symmetrix LUNs,
Install EMC SymmetriX ODM and powerpath packages.
Confirm the installation using
lslpp -L "EMC*"
lslpp -l|grep -i power
To Synchronize the Symmetrix Database with the Server Device Configuration Database,
powermt config
powermt save
cfgmgr -v
powermt display dev=all
and create the appropriate Volumes.
NOTE:
If the powerpath package hasnt been installed on the Server, which would be if multipathing is not being utilized,
cd /opt/emc/SYMCLI/V6.5.0/bin
./syminq
IBM Work Intruction
-7-
get the power disk LUN ID's and appropriately create the VG from the disks.
For an IBM DS LUN,

Install the following sddpcm and ODM packages, (#smitty installp)
devices.sddpcm.53.rte &
devices.fcp.disk.ibm.mpio.rte
do a #cfgmgr v
#pcmpath query device
and create the Volumes.
Also Verify if pcmpath query device is showing the desired number of paths to all the disks.
Kernel parameter Changes

To change, Virtual Memory, Filesystem, Logical Volume Manager, Network or NFS kernel parameters,
(a) To check the Kernel Parameters, currently defined;
#vmo -a
#ioo -a
#no -a
#nfso -a
/Virtual Memory Parameters

/IO Parameters
/Network Tunable Parameters
/NFS "
OR
#smitty tuning
Tuning Network & Kernel Parameters
Move cursor to desired item and press Enter.
Save/Restore All Tuning Parameters
Tuning Scheduler & Memory Load Control Parameters
Tuning Virtual Memory Manager, File System and Logical Volume Manager Params
Tuning Network Option Parameters
Tuning NFS Option Parameters
Tuning IO Parameters
Tuning RAS Parameters
Tuning Scheduler/Memory Load Control Tunable parameters

maxuproc
To display the current value
lsattr -E -l sys0 -a maxuproc
To Change the value,
chdev -l sys0 -a maxuproc=NewValue
Change takes effect immediately and is preserved over boot.
But if the value is reduced, then it goes into effect only after a system boot.
Diagnosis: Users cannot fork any additional processes.
IBM Work Intruction
-8-
Configuring Asynchronous IO
Following are the parameters that need to be tuned to configure the System to us Asynchronous IO.
maxreqs
Purpose: Specifies the maximum number of asynchronous I/O requests that can be outstanding at any one time.
Values: Default: 4096; Range: 1 to AIO_MAX (/usr/include/sys/limits.h)
To Display: lsattr -E -l aio0 -a maxreqs
To Change: chdev -l aio0 -a maxreqs=NewValue Change is effective after reboot and is permanent.
Tuning: This includes requests that are in progress, as well as those that are waiting to be started. The maximum
number of asynchronous I/O requests cannot be less than the
value of AIO_MAX, as defined in the /usr/include/sys/limits.h file, but can be greater. It would be appropriate for a
system with a high volume of asynchronous I/O to have a maximum number of asynchronous I/O requests larger
than AIO_MAX.
maxservers
Purpose: Specifies the maximum number of AIO kprocs per processor.
Values: Default: 10 per processor
Display: lsattr -E -l aio0 -a maxservers
Change: chdev -l aio0 -a maxservers=NewValue Change is effective after reboot and is permanent.
Tuning: This value limits the number of concurrent asynchronous I/O requests. The value should be about the same
as the expected number of concurrent AIO requests.
minservers
Purpose: Specifies the number of AIO kprocs that will be created when the AIO kernel extension is loaded.
Values: Default: 1
Change: chdev -l aio0 -a minservers=NewValue Change is effective after reboot and is permanent.
Tuning: Making this a large number is not recommended, because each process takes up some memory. Leaving
this number small is acceptable in most cases because AIO will create additional kprocs up to maxservers as
needed.
Paging Space Size

Purpose: The amount of disk space required to hold pages of working storage.
Values: Default: configuration-dependent; Range: 32 MB to n MB for hd6, 16 MB to n MB for non-hd6
To Display the current paging space size,
lsps -a
To change the paging space size,
#mkps a n s 24 rootvg hdisk0
Creates a paging space of 24 LPs on hdisk0
-a
-n
Specifies that the paging space is configured at subsequent restarts.

Activates the paging space immediately
To increase or decrease the size of the paging space,

#chps s 12 paging00
(Increases the size of the paging space paging00 by 12 LPs)
or
#smitty pgsp
IBM Work Intruction
-9Paging Space

List All Paging Spaces
Add Another Paging Space
Change / Show Characteristics of a Paging Space
Remove a Paging Space
Activate a Paging Space
Deactivate a Paging Space
Change: Change is effective immediately and is permanent. Paging space is not necessarily put into use
immediately, however.
Diagnosis: Run: lsps -a. If processes have been killed for lack of paging space, monitor the situation with the
psdanger() subroutine.
Tuning: If it appears that there is not enough paging space to handle the normal workload, add a new paging space
on another physical volume or make the existing paging spaces larger.
Raw LV Creation
After the LUN's from Storage have been assigned and are visible to the host,
Create a Volume Group.
Say vg20d has been created.
To create the raw device,
#mklv -t raw -y vg20d_8192m_01 vg20d 8192M
After creating the raw LV,
give the LV ownership to oracle:dba
#chown oracle:dba /dev/rvg20d_8192m_01
To check the No. of Physical Processors currently Available,

# lsdev -Cc processor|grep Available
proc0 Available 00-00 Processor
NOTE: This could be the Physical Processors or Virtual Processor (In case the LPAR is assigned
Processors from the Shared pool)
IBM Work Intruction
- 10 -
To check is multithreading is enabled,

#smtctl
.
.
.
proc2 has 2 SMT threads.
Bind processor 2 is bound with proc2
Bind processor 3 is bound with proc2
# prtconf|grep -i proc
Processor Type: PowerPC_POWER5
Number Of Processors: 14
Processor Clock Speed: 2302 MHz
# sar 1 2
AIX AIX-BCV 3 5 00C55DDE4C00
01/30/09
System configuration: lcpu=28 ent=7.00 mode=Uncapped

19:19:51
19:19:52
19:19:53
%usr
0
0
Average
%sys
0
0
0
%wio %idle physc %entc

0
100
0.02
0.3
0
100
0.01
0.2
0
100
0.02
0.3
Conclusion: The Server has been assigned 7 Physical Processors,14 Virtual Processors and with smt
enabled, the count becomes 28
i.e entitlement is the Actual Physical Processors assigned to the Partition.
What prtconf shows is the Virtual CPU's
Average
0
0
0 100 0.02
0.3
To Check Internal SCSI disk drives on the Server

lsdev -Cc disk|grep SCSI
hdisk0
Available 04-08-00-8,0 16 Bit LVD SCSI Disk Drive
hdisk1
Available 04-08-00-9,0 16 Bit LVD SCSI Disk Drive
To Check EMC powerpath disks

lsdev -Cc disk|grep PowerPath
.
hdiskpower198 Available 08-08-02
PowerPath Device
PowerPath Device
PowerPath Device
PowerPath Device
Taking an OS Backup/mksysb
#nohup mksysb ievX /dev/rmt0 &
OR
#smitty mksysb
IBM Work Intruction
- 11 -
Back Up the System

Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
WARNING: Execution of the mksysb command will
result in the loss of all material
previously stored on the selected
output medium. This command backs
up only rootvg volume group.
* Backup DEVICE or FILE
+/
Create MAP files?
+
EXCLUDE files?
+
List files as they are backed up?
+
Verify readability if tape device?
+
Generate new /image.data file?
+
EXPAND /tmp if needed?
+
Disable software packing of backup?
+
Backup extended attributes?
+
Number of BLOCKS to write in a single output
#
(Leave blank to use a system default)
[]
no
no
no
no
yes
no
no
yes
[]
NOTE: If an internal tape drive is not available on the System,

Take it on to a Server which can be later configured as a NIM Master.
Ensure that the host entries of both, the Server whose backup is to be taken and the Server on which the backup is
being stored, are present in the /etc/hosts file of each other.
Start all the NFS Services, If they arent Active
#startsrc g nfs
On both the servers, ensure that #ulimit a is set to unlimited.
(edit the /etc/security/limits file)
vi /etc/security/limits
.
.
default:
fsize = -1
core = -1
cpu = -1
data = -1
rss = -1
stack = -1
nofiles = -1
stack_hard = -1
IBM Work Intruction
- 12 -
.
.
.
Note:
Client
= NIM Client
Master Server = NIM server
On the Client,
#cd /
#mkdir backupfs
#cd backupfs
#mkdir logs
#chmod R 777 /backupfs
create a /backupfs mount point on the Master Server, spacious enough to store the mksysbs of a sufficient no. of
clients.
On the Client,
// the Server whose mksysb is to be taken
Mount the Master Servers /backupfs mount point onto the Clients /backupfs directory
#mount 10.77.8.102:/backupfs /backupfs
#nohup mksysb -i -e -X /backupfs/`hostname`_`date +"%d-%h-%y"` > /backupfs/logs/`hostname`_`date +"%d-%h%y"`.log &
After this is done,
Verify the logs directory (/backupfs/logs) which would show the mksysb Completion logs on the Master Server.
Eg:
more /backupfs/logs/UPSSUATAPP_Jan-27-2009.log
Creating information file (/image.data) for rootvg.
Creating list of files to back up..
Backing up 48454 files...............
48454 of 48454 files (100%)0512-038 mksysb: Backup Completed Successfully.
Pre-Restart Activities
Before Restarting the Server,
The following steps need to be performed
(a) Check if the root Volume Group is mirrored,
# lsvg rootvg -l
rootvg:
LV NAME
TYPE
hd5
boot
1
hd6
paging 2
hd8
jfs2log 1
hd4
jfs2
12
hd2
jfs2
20
hd9var
jfs2
16
hd3
jfs2
16
hd1
jfs2
16
hd10opt
jfs2
16
lg_dumplv
sysdump
fslv00
jfs2
280
LPs
2
4
2
24
40
32
32
32
32
8
280
PPs PVs LV STATE

MOUNT POINT
2 closed/syncd N/A
2 open/syncd N/A
2 open/syncd N/A
2 open/syncd /
2 open/syncd /usr
2 open/syncd /var
2 open/syncd /tmp
2 open/syncd /home
2 open/syncd /opt
8
1 open/syncd N/A
1 open/syncd /software
IBM Work Intruction

fslv01
fslv02
paging00
- 13 -
jfs2
280 280 1 open/syncd /postscript
jfs2
280 280 2 open/syncd /data1
paging 32
32
1 open/syncd N/A
bootlist m normal o
hdisk0 blv=hd5
hdisk1 blv=hd5
i.e if PPs is double the LPs and if the blv is updated on both the disks, the rootvg is mirrored.
(b) Take the LVM Configuration backup.
for i in `lsvg -o`
do
lsvg rootvg|grep "VOLUME GROUP"|awk '{print $1,$2,$3}'
rootvg
lsvg $i -p
lsvg $i -l
done
> /tmp/cfgbkp.outVOLUME GROUP:

>> /tmp/cfgbkp.out
>> /tmp/cfgbkp.out
(c) Take a snap output backup

# snap -gc
/var/adm/ras/trcfile: No such file or directory
Checking space requirement for general
information......................................................................................................................................................................
......... done.
.********Checking and initializing directory structure
Creating /tmp/ibmsupt directory tree... done.
Creating /tmp/ibmsupt/svCollect directory tree... done.
Creating /tmp/ibmsupt/client_collect directory tree... done.
Creating /tmp/ibmsupt/general directory tree... done.
Creating /tmp/ibmsupt/general/diagnostics directory tree... done.
Creating /tmp/ibmsupt/pcixscsi directory tree... done.
Creating /tmp/ibmsupt/sissas directory tree... done.
Creating /tmp/ibmsupt/testcase directory tree... done.
Creating /tmp/ibmsupt/other directory tree... done.
********Finished setting up directory /tmp/ibmsupt
Checking Space requirement for svCollect
The script svCollect is not executable in /usr/lib/ras/snapscripts
Checking Space requirement for client_collect
Checking for enough free space in filesystem... done.
/var/adm/ras/trcfile: No such file or directory
Gathering general system
information......................................................................................................................................................................
..done.
Gathering platform/scanout information.done.
Gathering svCollect data
The script svCollect is not executable in /usr/lib/ras/snapscripts
Gathering client_collect data
Gathering pcixscsi system information.................................... done.
Gathering sissas system information...... done.
Creating compressed pax file...
Starting pax/compress process... Please wait... done.
-rw------- 1 0
935378 Jan 30 18:40 snap.pax.Z
IBM Work Intruction
- 14 -
(d) Take a backup of all critical files to /tmp;

cp /etc/inittab /tmp/inittab_`date+%d-%m-%y`
cp /etc/hosts /tmp/hosts_`date+%d-%m-%y`
cp /etc/passwd /tmp/passwd_`date+%d-%m-%y`
cp /etc/services /etc/services_`date+%d-%m-%y`
netstat rn > /tmp/netstat_rn.out
prtconf > /tmp/prtconf.out
lscfg vp > /tmp/lscfg_vp.out
vmo a > /tmp/vmo.out
ioo a > /tmp/ioo.out
no a > /tmp/no.out
nfso a > /tmp/nfso.out
tar cvf crontabs.tar /var/spool/cron/
Post Restart, Verify that the LVM Configuration, kernel parameters, users, cronjobs are all in place.
IBM Work Intruction
- 15 -
To change the Network media Speed

#ifconfig en0 down detach
#smitty devices
Communinication
Ethernet Adapter
Adapter
Select the adapter whose Media Speed has to be changed,
The fields that need to be changed,
Media Speed
Apply Changes to Database
Auto Negotiation/1000_Full
Yes
After successfully changing the media speed,

Refresh the inetd daemon,
#smitty mktcpip
en0
#Assuming the Network on which the IP is configured is en0
Your Cable Type

Start Now
tp
Yes
#twisted pair
After this is done,

Check for successful ping connectivity to the gateway,
ping 10.77.132.1
ssh Installation
The following packages need to be installed
#smitty installp from the
AIX Toolbox for Linux Applications CD & the Expansion Pack (Expansion Pack required only for pre-5.8 AIX)
openssl-0.9.7g-1
openssl-devel-0.9.7g-1
openssl-doc-0.9.7g-1
openssh.base.client
openssh.base.server
openssh.license
openssh.man.en_US
openssh.msg.en_US
IBM Work Intruction
- 16 -
Check for the ssh version

& check localhost ssh connectivity
# ssh -version
OpenSSH_4.3p2, OpenSSL 0.9.7g 11 Apr 2005
#ssh localhost
Patch installation
Applying a patch
#smitty installp
Updating the Service Pack level #smitty update_all
OR
Post patch installation,

Check,
oslevel s
&
lppchk -v
(-v
Verifies that the / (root), /usr and /usr/share parts of the system are valid with each other. In other words,
this flag verifies that all software products installed on the / (root) file system are also installed on the /usr file
system and, conversely, all the software products installed in the /usr file system are also installed on the / (root) file
system. )
ssh-keygen Generation
# ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (//.ssh/id_dsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in //.ssh/id_dsa.
Your public key has been saved in //.ssh/id_dsa.pub.
The key fingerprint is:
e7:c8:05:9c:b6:f1:79:72:a3:6c:9d:70:ee:51:94:bb root@EBBP-VIEW
create a authorised_keys file in a .ssh directory in the home directory of the user that you wish to ssh to,without a
password
To establish the link on the Switch after connecting the fiber cables from the
Storage
# chdev -P fcs0
fcs0 Defined
# chdev -l fcs0 -a init_link=pt2pt
To check the WWPN of the Fiber card,

# lscfg -vl fcs0|grep Network
Network Address.............10000000C972A276
To check the firmware level of the filber card,

# lscfg -vl fcs0|grep Z9
Device Specific.(Z9)........ZS2.71A2
IBM Work Intruction
- 17 -
To analyse the Server error log report

#errpt|more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
BFE4C025 0129232309 P H sysplanar0 UNDETERMINED ERROR
C69F5C9B 0116144809 P S SYSPROC
SOFTWARE PROGRAM ABNORMALLY TERMINATED
.
.
.
Give the Identifier of the error that you wish to analyse,
# errpt aj BFE4C025|more
--------------------------------------------------------------------------LABEL:
SCAN_ERROR_CHRP
IDENTIFIER: BFE4C025
Date/Time:
Thu Jan 29 23:23:54 CST 2009
Sequence Number: 329
Machine Id:
00CD45814C00
Node Id:
EBBP-VIEW
Class:
H
Type:
PERM
Resource Name: sysplanar0
Resource Class: planar
Resource Type: sysplanar_rspc
Location:
Description
UNDETERMINED ERROR
Failure Causes
UNDETERMINED
Recommended Actions
RUN SYSTEM DIAGNOSTICS.
Detail Data
PROBLEM DATA
0644 00E0 0000 06D8 9E00 8E00 0000 0000 0000 0000 4942 4D00 5048 0030 0100 DD00
2009 0129 1851 0599 2009 0129 1851 1439 4500 010A 0000 0000 0000 0000 0000 0000
5150 68EF 5150 68EF 5548 0018 0100 DD00 2303 2000 0000 E500 0000 A800 0000 0000
5053 00FC 0101 DD00 0201 0009 0000 00F4 0300 00F0 28E1 0120 C139 20FF 4100 00FF
0083 1932 0000 0001 00A0 008A 5522 420E 4231 3233 4535 3030 2020 2020 2020 2020
2020 2020
.
.
.
Diagnostic Analysis
IBM Work Intruction

Diagnostic Log sequence number: 469
Resource tested:
sysplanar0
Resource Description: System Planar
Location:
SRC:
B123E500
Description: Memory subsystem including external cache Predictive
Error, general. Refer to the system service documentation for more information.
Additional Words: 2-030000F0 3-28E10120 4-C13920FF 5-410000FF
6-00831932 7-00000001 8-00A0008A 9-5522420E
Possible FRUs:
Priority: M FRU: 41V2097 S/N: YH10B181A38L CCIN: 316C
Location: U787C.001.91806V5-P4-C15
Priority: M FRU: 41V2097 S/N: YH10B18170UL CCIN: 316C
Location: U787C.001.91806V5-P4-C14
- 18 -
IBM Work Intruction
- 19 -
Call Logging Format

To: rccindia@in.ibm.com,powersupport@in.ibm.com
Cc: Abhay B Jhaveri/India/IBM, Sanket R Rane/India/IBM, Vivek Naik/India/IBM, Siddheshwar Hingmire/India/IBM,
Santosh C Kumar/India/Contr/IBM, Karthikeyan Subramanian4/India/IBM,
Hello,
Please log a call for the following problem.
System Model: IBM,9113-550
Machine Serial Number:6587A7E
Physical Location - Row 9.2 / 10.77.132.62
Problem Description
The system Firmware microcode Level needs to be upgraded.
The current Firmware Image is SF222_075.
The Manage Serviceable Events Section in Service Management in the HMC shows the Affected FRU Part No.
80P5530 / Description - Backplane
Dept Code - X1G
Contact Address:IBM India Pvt. Ltd.
2nd Floor,Vodafone-Essar Cellular Limited,
Opp. Tata Motors Showroom,
Wakdewadi,
Pune-411001.
Contact Person - Siddheshwar Hingmire 9923118958/Rohan Gupta 9921716441/ Santosh C Kumar 9049003891
IBM Work Intruction
Hewlett Packard HP-UX Activities
- 20 -
IBM Work Intruction
- 21 -
Check physical memory

# print_manifest |grep -i memory
Main Memory:
12288 MB
or
# cat /var/adm/syslog/syslog.log |grep -i Phy
Nov 20 16:44:59 NDCRP1V6 vmunix:
Nov 20 16:44:59 NDCRP1V6 vmunix:
11070196 Kbytes
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 12582912 Kbytes, lockable: 9636284 Kbytes, available:
or #sam--------------> Performance Monitors ---------> System Properties -----memory

Physical Memory:
Real Memory:
Active:
Total:
Virtual Memory:
Active:
Total:
Free Memory Pages:
Swap Space:
Avail:
Used:
12299.0 MB
123019.1 KB
260072.5 KB
206876.7 KB
453451.1 KB
2468390 at 4 KB/page
24576 MB
332 MB
Check processor
#
ioscan -fnC processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
processor
or
0 0/10
1 0/11
2 0/12
3 0/13
4 0/14
5 0/15
6 0/16
7 0/17
8 1/10
9 1/11
10 1/12
11 1/13
12 1/14
13 1/15
14 1/16
15 1/17
16 2/10
17 2/11
18 2/12
19 2/13
20 2/14
21 2/15
22 2/16
23 2/17
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
processor CLAIMED
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
PROCESSOR Processor
IBM Work Intruction
- 22 -
# print_manifest |grep -i processor

Processors:
or
24
#sam--------------> Performance Monitors ---------> System Properties ----------> processor

Processors:
Active:
3
Total:
24
CPU Version:
CPU(0A) PA8900 4.1
Clock Frequency:
1066 MHz
Machine Identification: 1399117030
Hardware Model:
9000/800/rp8440
Kernel Width Support: 64
Check mount point (mounted file systems)

#bdf
#mount -p
Check root and /var file system usage

#bdf /
#bdf /var
Detect new hardware

#ioscan -fnc (disk,processor or tape)
#insf -e
IBM Work Intruction
- 23 -
Remove tape device files

#ioscan -fnC tape
Class I H/W Path
Driver S/W State H/W Type Description
========================================================================
tape
0 1/0/10/1/1.3.0 stape CLAIMED DEVICE
HP
C7438A
/dev/rmt/0m
/dev/rmt/0mnb
/dev/rmt/c1t3d0BESTn /dev/rmt/c1t3d0DDSb
/dev/rmt/0mb
/dev/rmt/c1t3d0BEST /dev/rmt/c1t3d0BESTnb /dev/rmt/c1t3d0DDSn
/dev/rmt/0mn
/dev/rmt/c1t3d0BESTb /dev/rmt/c1t3d0DDS /dev/rmt/c1t3d0DDSnb
#rmsf -e /dev/rmt/0m /dev/rmt/0mb /dev/rmt/0mn
#ioscan -fnC tape
#insf -e
Before rebooting the server and after booting the OS

a) Need to take important files backup with network details.( servers shutdown and startup checklist need
to fill)
#ps -ef |grep pmon ( checking weather the database is running or not)
date >> /home/monitor/all_outputs/uptime
uptime >> /home/monitor/all_outputs/uptime
echo "****************************************************************************" >>
/home/monitor/all_outputs/uptime
date >> /home/monitor/all_outputs/bdfout
bdf >> /home/monitor/all_outputs/bdfout
echo "****************************************************************************" >>
/home/monitor/all_outputs/bdfout
date >> /home/monitor/all_outputs/mountp_out
mount -p >> /home/monitor/all_outputs/mountp_out
echo "****************************************************************************" >>
/home/monitor/all_outputs/mountp_out
date >> /home/monitor/all_outputs/vgdisplay_out
vgdisplay -v >> /home/monitor/all_outputs/vgdisplay_out
echo "****************************************************************************" >>
/home/monitor/all_outputs/vgdisplay_out
date >> /home/monitor/all_outputs/lvmtab_out
strings /etc/lvmtab >> /home/monitor/all_outputs/lvmtab_out
echo "****************************************************************************" >>
/home/monitor/all_outputs/lvmtab_out
IBM Work Intruction

date >> /home/monitor/all_outputs/passwd_out
cat /etc/passwd >> /home/monitor/all_outputs/passwd_out
echo "****************************************************************************" >>
/home/monitor/all_outputs/passwd_out
date >> /home/monitor/all_outputs/logins_out
logins >> /home/monitor/all_outputs/logins_out
echo "****************************************************************************" >>
/home/monitor/all_outputs/logins_out
date >> /home/monitor/all_outputs/fstab_out
cat /etc/fstab >> /home/monitor/all_outputs/fstab_out
echo "****************************************************************************" >>
/home/monitor/all_outputs/fstab_out
date >> /home/monitor/all_outputs/lvlnboot_out
lvlnboot -v >> /home/monitor/all_outputs/lvlnboot_out
echo "****************************************************************************" >>
/home/monitor/all_outputs/lvlnboot_out
date >> /home/monitor/all_outputs/parstatus_out
parstatus >> /home/monitor/all_outputs/parstatus_out
echo "****************************************************************************" >>
/home/monitor/all_outputs/parstatus_out
sleep 45
date >> /home/monitor/all_outputs/ioscan_out
ioscan -fn >> /home/monitor/all_outputs/ioscan_out
echo "****************************************************************************" >>
/home/monitor/all_outputs/ioscan_out
tar -cvf /home/monitor/`hostname`_week`date +%U`.tar /home/monitor/all_outputs
b) After booting the os
Checking all the mount point are mounted properly

#bdf
#bdf |wc -l ( comparing with old output)
#cat /tmp/bdf_oldout |wc -l
#date
#uptime
(checking date and time)
- 24 -
IBM Work Intruction
- 25 -
#ps -ef|grep ntp ( checking ntp deamon has started or not if the service is not started )
#/sbin/int.d/xntpd start
#ps -ef |grep cron ( check cron deamon has started or not if not need to start the cron)
#/sbin/init.d/cron start
#cat /etc/services
#cat /etc/hosts ( checking the host entris)
#hostname ( checking the hostname)
#ifconfig lan0 ( checking the ip address )
#netstat -rn ( checking the gateway)
#ls -lrt / ( checking the ownership)
Note: After checking all the above steps we will inform to DBA team to start the database
Set Parameter
(Note: Before changing the parameter take the backup of vmunix and build)
#kmtune (To check all OS parameter)
#kmtune |grep nfile
Need to check weather the parameter is static or dynamic, if the parameter is static reboot is required.
IBM Work Intruction
- 26 -
For Static Parameter

#kmtune |grep semmap (Note : where semmap is parameter name)
semmap
8122 - 8122
#cp /stand/vmunix /stand/vmunix.prev

#tar -cvf /tmp/build.tar build
#kmtune -s parametername=new value
#kmtune -d
parameter name
256 - 1024
Where 1024 is the new parameter, it will get effect in the next reboot
then build the new kernel
#mk_kernel
#kmupdate ( need to take reboot)
For Dynamic Parameter

#kmtune -s parameter name=new value
To update the new value
#kmtune -u
( Note : No need to take reboot for dynamic parameter)
Check free disk

# cd /opt/emc/SYMCLI/V6.5.0/bin
#./syminq > /tmp/syminq_output
Need to verify with vgdisplay, lvmtab and fstab
#vgdisplay -v > /tmp/vgdisplay_out
#vgdisplay -v |grep "PV Name" > /tmp/all_pvs
#strings /etc/lvmtune > /tmp/lvmtab_out
Ignite backup
#make_tape_recovery -A -v -I -a /dev/rmt/0mn
To check the status
#cd /var/opt/ignite/recovery/latest
IBM Work Intruction
- 27 -
#cat recovery.log
12/26/08 14:56:47 IST Started make_tape_recovery.
Unlocking the user

To check weather the account is locked or not
#/usr/lbin/getprpw -l oracle
uid=111, bootpw=NO, audid=21, audflg=1, mintm=-1, maxpwln=-1, exptm=-1, lftm=-1, spwchg=Wed Jan 28
00:24:43 2009, upwchg=-1, acctexp=-1, llog=-1, expwarn=-1, usrpick=DFT, syspnpw=DFT, rstrpw=DFT,
nullpw=DFT, admnum=-1, syschpw=DFT, sysltpw=DFT, timeod=-1, slogint=Fri Jan 30 16:45:21 2009,
ulogint=1, sloginy=-1, culogin=-1, uloginy=-1, umaxlntr=-1, alock=NO, lockout=0000100
#/usr/lbin/modprpw -k oracle
or
#su - oracle
Enable FTP TELNET and RSH services

#vi /etc/inetd.conf ( Need to uncomment the hash)
#inetd -c ( To refresh the inetd.conf file)
Password Reset
Note : To reset the password user has to take approval from his respective manager
Login to all servers checking root and /var mount paint usage,
if root is above 80% or 90%, need to check any directory is mounted on /,
#df -k * |sort -n ( To sort the size of directories in assending order
If /var is crosing 80% or 90%
# cd /var
#du -sk * |sort -n
# cd mail
(Delete users old mail if the size is more than 1 or 2 gb)
After taking backup of wtmp, syslog and cronlog ( make empty)
If you make syslog file empty excecute the below command
#kill -HUP syslogd ( To refresh the syslogd deamon)
IBM Work Intruction
- 28 -
File system create (If the OS is fresh)

#cd /opt/emc/SYMCLI/V6.5.0/bin
#./syminq > /tmp/sym_output
#pvcreate /dev/rdsk/c23t45d37 ( where /dev/rdsk/c23t45d37 and 38 are the raw disk)
#pvcreate /dev/rdsk/c24t46d38
#ll /dev/*/group ( To check special device file)
#mkdir /dev/vg_01 ( Where vg_01 is vgname)
#mknod /dev/vg_01/group c 64 0x090000
#ll /dev/vg_01/group
crw-r--r-- 1 root
sys
64 0x090000 Dec 30 13:56 /dev/vg_01/group
#vgcreate -s 16 vg_01 /dev/dsk/c23t45d37 /dev/dsk/c23t45d36 /dev/dsk/24t46d38 /dev/dsk/24t46d40
( where 36 and 40 are alternative disks)
#lvcreate -L size(M) -r n -n lvol1 vg_01 ( where lvol1 is the logical volume)
# mkfs -F vxfs -o largefiles /dev/vg_01/lvol1 ( To assing file system or format with vxfs file system)
#mkdir /data01 ( where /data01 is the mount point
#mount /dev/vg_01/lvol1 /data01
Make entry in /etc/fstab
#vi /etc/fstab
/dev/vg_01/lvol1 /data01 vxfs log
:wq
#
#bdf /data01
/dev/vg_01/lvol1
02
( total size in kb) ( used size in kb) ( available size in kb) ( usage in %) /data01
If GUNZIP is not working in oracle user account

#whereis gunzip
gunzip: /usr/contrib/bin/gunzip /usr/contrib/man/man1.Z/gunzip.1
Need to export /usr/contrib/bin/gunzip in the user profile or the user has to excecute the gunzip command
with full path
#/usr/contrib/bin/gunzip gip file name
Changing permission and ownership of mount points

To change the permission
#chmod 755 (file or directory name)
To change the ownership
#chown -R oracle:dba /oracle ( where oracle is the user name and dba is group name, /oracle is the mount
point )
IBM Work Intruction
- 29 -
User creation
( Users has to send the user creation form with there respective managers approval)
#useradd -md /home/oracle oracle ( to create the oracle user under /home)
#usermod -g dba oracle ( changing the oracle user group)
#passwd oracle ( To set password to oracle user)
Hardware issues (will log a call with hp with serial number and model)
#parstatus |grep -i serial ( To check the serial number)
#model ( Check the model)
Making the entry of hostname and ipaddress in /etc/hosts files

ip address
hostname
:wq
Making the new port entry in /etc/services as per the application request.
(Approval is required)
Configuring NTP client

#vi /etc/ntp.conf
server 0.0.0.0 version 3
( Where 0.0.0.0 is the ntp server )
#/sbin/init.d/xntpd start
#ps -ef |grep ntp
root 2031 1 0 Jan 24 ?
0:50 /usr/sbin/xntpd
root 29735 9253 0 17:46:41 pts/4 0:00 grep ntp
#
IBM Work Intruction
- 30 -
CRON access
#vi /var/adm/cron/cron.allow
oracle
:wq
#ps -ef |grep cron
root 2085 1 0 Jan 24 ?
1:16 /usr/sbin/cron
root 627 9253 1 17:47:18 pts/4 0:00 grep cron
#
Collecting sec audit report

cfg2html as per the request
For performance issue

#sar -d 1 5 (To check which disk is busy.)
("1" is time interval between each of "5" outputs.)
#sar 1 5 (To check cpu utilisation.)
#vmstat 1 5 (To check memory utilisation.)
#swapinfo -m (To check swap memory details.)
#glance
or
(To check avarage memory,cpu,disk,network utilisation.)
#top
#glance -d
or
#top -d
(To check perticular disk read/write details)
#glance -c
or
#top -w
(To check perticular cpu usage)
#glance -i (To check disk read/write by meance of io)

#glance -g (To check detail report of system & user processes.)
IBM Work Intruction
Linux Activities
- 31 -
IBM Work Intruction

Check Physical Memory
- 32 -
#dmidecode -q |grep -i 'range size

Range Size: 32 GB
or
# cat /proc/meminfo| grep I MemTotal
MemTotal:
2975140
#free m
total
used
free
Mem:
2905
2773
131
-/+ buffers/cache:
534
2371
Swap:
39997
0
39997
shared
0
buffers cached
30
2209
Check Processor
#dmidecode -q |egrep -i 'Socket Designation: Node '
Socket Designation: Node 1 CPU 3
or
# cat /proc/cpuinfo | grep 'processor' | wc l
32

#df h
#mount l
Check root and /var file system usage

#df /
#df /var
Detect new hardware

#kudzu
IBM Work Intruction
- 33 -
Before rebooting the server and after booting the OS .

a) Need to take important files backup with network details.( servers shutdown and startup checklist need
to fill)
#!/bin/bash
sudo su cd /tmp/testing/
mkdir log_`hostname -s`_`date +%m_%d_%y`
cd log_`hostname -s`_`date +%m_%d_%y`
echo
echo
echo
echo "****************************************************************************************************
echo "IP : `/sbin/ifconfig eth0 | grep 'inet addr'| cut -d: -f2| cut -d' ' -f1`" >> `hostname -s`_`date +%m_%d_
%y`.txt
echo
echo "Hostname = `hostname` " >> `hostname -s`_`date +%m_%d_%y`.txt
echo "Current date and time is = `date`" >> `hostname -s`_`date +%m_%d_%y`.txt
echo
echo "Uptime is = `uptime | cut -d' ' -f4` days " >> `hostname -s`_`date +%m_%d_%y`.txt
echo
echo "Disk Usage "
echo
df -k | grep "mapper" > aa.txt
df -k |grep -v Filesystem | sed -e '/dev/d' >bb.txt
paste aa.txt bb.txt >cc.txt
df -k | grep /dev/sd >> cc.txt
cat cc.txt >> `hostname -s`_`date +%m_%d_%y`.txt
echo
mount l > mount.out
echo
vgdisplay vvv > vginfo.out
echo
cat /etc/passwd > passwd.out
echo
cat /etc/fstab > fstab.out
echo
netstat rn > netstat.out
echo
tar cvf log_`hostname -s`_`date +%m_%d_%y`.tar log_`hostname -s`_`date +%m_%d_%y`
echo "***************************************************Done*******************************************
echo
echo
exit
exit
#ps -ef |grep pmon ( checking weather the database is running or not)
#ps ef | grep java ( for actuate /websphere application)
b) After booting the os
Checking all the mount point are mounted properly
#df h ( comparing with old output)
IBM Work Intruction

#date
- 34 -
(checking date and time)
#uptime
# service ntpd status (checking ntp deamon has started or not if the service is not started)
#/service ntpd start
#service crond status ( check cron deamon has started or not if not need to start the cron)
#/service crond start
#cat /etc/services
#cat /etc/hosts ( checking the host entris)
#hostname ( checking the hostname)
#ifconfig a eth0 ( checking the ip address )
#netstat -rn ( checking the gateway)
#ls -lrt / ( checking the ownership)
Note : After checking all the above steps we will inform to dba team to start the database
Set all parameter ie network ,kernel ,vm

# sysctl a ( to check all parameter )
#sysctl a |grep fs.file-max
Edit /etc/sysctl.conf
Add parameter with requested value
fs.file-max= 204318
save and quit
#sysctl p
Check free disk

#fdisk l
Unlocking the user

To check weather the account is locked or not
#faillog u oracle
To unlock
#faillog m u oracle
IBM Work Intruction
- 35 -
Enable FTP, TELNET and RSH services

#vi /etc/xinetd.d/krb5-telnet
Edit
disable
= yes
change yes to no
# service xinetd restart
Password reset
Note : To reset the password user has to take approval from his respective manager
Login to all servers checking root and /var mount paint usage,
if root is above 80% or 90%, need to check any directory is mounted on /,
#df -k * |sort -n ( To sort the size of directories in assending order
If /var is crosing 80% or 90%
# cd /var
#du -sk * |sort -n
# cd /var/spool/mail
(Delete users old mail if the size is more than 1 or 2 gb)
After taking backup of wtmp, syslog and cronlog httplogs (accesslog and errorlog ) ( make empty)
If you make syslog file empty excecute the below command
#service syslogd restart ( To refresh the syslogd deamon)
13 File system create ( If the os is fresh)
# fdisk l To check free disk
#pvcreate /dev/sdb /dev/sdc /dev/sdd ( where /dev/sdb,sdc disk)
#pvdisplay or pvs To check PV
#vgcreate vg0 /dev/sdb /dev/sdc /dev/sdd
#vgdisplay
#lvcreate L +10240M n lv01 vg0
#lvdisplay
#mkfs t ext3 /dev/vg0/lv01
#mkdir /oracle
#mount /dev/vg0/lv01 /oracle
#df
Edit /etc/fstab and add mount point entry
/dev/vg0/lv01 /oracle ext3 defaults
Save and quit
12
IBM Work Intruction
- 36 -

To change the permission
#chmod 755 (file or directory name)
To change the ownership
#chown -R oracle:dba /oracle ( where oracle is the user name and dba is group name, /oracle is the mount
point )
User Creation
#useradd -md /home/oracle oracle ( to create the oracle user under /home)
#usermod -g dba oracle ( changing the oracle user group)
#passwd oracle ( To set password to oracle user)
Hardware issues (will log a call with hp with serial number and model)
#demidecode |grep -i System Information (To check the serial number/model)
Making the entry of hostname and ipaddress in /etc/hosts files

ip address
hostname
:wq
Making the new port entry in /etc/services as per the application request. ( approval is required)
Configuring NTP client

#vi /etc/ntp.conf
server 0.0.0.0 version 3
( Where 0.0.0.0 is the ntp server )
#service ntpd start
# service ntpd status
IBM Work Intruction
- 37 -
CRON access
#vi /etc/cron/cron.allow
oracle
:wq
#service crond status
Collecting sec audit report, cfg2html as per the request
For performance issue #sar -d 1 5 (To check which disk is busy.)

#sar 1 5 (To check cpu utilisation.)
#vmstat 1 5 (To check memory utilisation.)
#cat /proc/meminfo | grep SwapFree (To check swap memory details.)
# free
#top
(To check avarage memory,cpu,disk,network utilisation.)
# iostat 5 10 ( to check disk utilization)
IBM Work Intruction
SUN Solaris Activities
- 38 -
IBM Work Intruction
- 39 -
Unlocking user Password

# passwd -s "User Name" -------------------------> (To check the Status)
# passwd -u "User Name" -------------------------> (To Unlock Password)
Check Physical Memory.

# prtconf -v |grep Memory
Memory size: 32768 Megabytes
Check Architecture of SUN machine.

# isainfo -v
Check Processor.
# psrinfo -v OR #psrinfo
Status of virtual processor 0 as of: 01/31/2009 00:00:25
0
on-line since
01/20/2009 10:15:10
on-line since 01/20/2009 10:15:10
on-line since 01/20/2009 10:15:10.
2
on-line since
01/20/2009 10:15:10
on-line since 01/20/2009 10:15:08
The sparcv9 processor operates at 1593 MHz, and has a sparcv9 floating point processor.
on-line since 01/20/2009 10:15:10.
on-line since 01/20/2009 10:15:10.
on-line since 01/20/2009 10:15:08.

# df -k or df -h
Detect new hardware

#devfsadm
Checking weather the database is running or not

#ps -ef |grep pmon
Check CRON daemon has started or not

If not need to start the CRON
#ps -ef |grep cron
IBM Work Intruction
Check the Services status (online or offline)

Note: - Only In Solaris 5.10 Version
# svcs
STATE
STIME FMRI
legacy_run Jan_20 lrc:/etc/rcS_d/S29wrsmcfg
legacy_run Jan_20 lrc:/etc/rc2_d/S10lu
legacy_run Jan_20 lrc:/etc/rc2_d/S20sysetup
legacy_run Jan_20 lrc:/etc/rc2_d/S40llc2
legacy_run Jan_20 lrc:/etc/rc2_d/S42ncakmod
legacy_run Jan_20 lrc:/etc/rc2_d/S47pppd
legacy_run Jan_20 lrc:/etc/rc2_d/S70uucp
legacy_run Jan_20 lrc:/etc/rc2_d/S72autoinstall
legacy_run Jan_20 lrc:/etc/rc2_d/S73cachefs_daemon
legacy_run Jan_20 lrc:/etc/rc2_d/S76ACT_dumpscript
legacy_run Jan_20 lrc:/etc/rc2_d/S81dodatadm_udaplt
legacy_run Jan_20 lrc:/etc/rc2_d/S89PRESERVE
legacy_run Jan_20 lrc:/etc/rc2_d/S90loc_ja_cssd
legacy_run Jan_20 lrc:/etc/rc2_d/S91afbinit
legacy_run Jan_20 lrc:/etc/rc2_d/S91gfbinit
legacy_run Jan_20 lrc:/etc/rc2_d/S91ifbinit
legacy_run Jan_20 lrc:/etc/rc2_d/S91jfbinit
legacy_run Jan_20 lrc:/etc/rc2_d/S91kfbinit
legacy_run Jan_20 lrc:/etc/rc2_d/S91zuluinit
legacy_run Jan_20 lrc:/etc/rc2_d/S94ncalogd
legacy_run Jan_20 lrc:/etc/rc2_d/S98deallocate
legacy_run Jan_20 lrc:/etc/rc2_d/S99dbora
legacy_run Jan_20 lrc:/etc/rc2_d/S99sneep
legacy_run Jan_20 lrc:/etc/rc3_d/S16boot_server
legacy_run Jan_20 lrc:/etc/rc3_d/S50apache
legacy_run Jan_20 lrc:/etc/rc3_d/S52imq
legacy_run Jan_20 lrc:/etc/rc3_d/S80mipagent
legacy_run Jan_20 lrc:/etc/rc3_d/S84appserv
legacy_run Jan_20 lrc:/etc/rc3_d/S98Xvfb
legacy_run Jan_20 lrc:/etc/rc3_d/S99EIS-DVDtag
legacy_run Jan_20 lrc:/etc/rc3_d/S99Silverstream
legacy_run Jan_20 lrc:/etc/rc3_d/S99pis3113ProvisoInfoServer
online
Jan_20 svc:/system/svc/restarter:default
online
Jan_20 svc:/network/pfil:default
online
Jan_20 svc:/network/loopback:default
online
Jan_20 svc:/system/installupdates:default
online
Jan_20 svc:/milestone/name-services:default
online
Jan_20 svc:/network/physical:default
online
Jan_20 svc:/milestone/network:default
online
Jan_20 svc:/system/identity:node
online
Jan_20 svc:/system/metainit:default
online
Jan_20 svc:/system/filesystem/root:default
online
Jan_20 svc:/system/boot-archive:default
online
Jan_20 svc:/system/scheduler:default
online
Jan_20 svc:/system/filesystem/usr:default
online
Jan_20 svc:/system/keymap:default
online
Jan_20 svc:/system/device/local:default
online
Jan_20 svc:/system/filesystem/minimal:default
online
Jan_20 svc:/system/identity:domain
online
Jan_20 svc:/system/rmtmpfiles:default
online
Jan_20 svc:/system/name-service-cache:default
online
Jan_20 svc:/system/resource-mgmt:default
online
Jan_20 svc:/system/sysevent:default
- 40 -
IBM Work Intruction

online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
svc:/system/coreadm:default
svc:/system/device/fc-fabric:default
svc:/system/picl:default
svc:/milestone/devices:default
svc:/system/power:default
svc:/system/cryptosvc:default
svc:/network/initial:default
svc:/system/manifest-import:default
svc:/network/service:default
svc:/application/print/ppd-cache-update:default
svc:/milestone/single-user:default
svc:/system/filesystem/local:default
svc:/system/cron:default
svc:/system/sysidtool:net
svc:/application/psncollector:default
svc:/application/font/fc-cache:default
svc:/network/routing-setup:default
svc:/network/rpc/bind:default
svc:/network/nfs/status:default
svc:/system/sysidtool:system
svc:/network/nfs/cbd:default
svc:/network/nfs/mapid:default
svc:/network/nfs/nlockmgr:default
svc:/milestone/sysconfig:default
svc:/application/stosreg:default
svc:/system/sac:default
svc:/network/inetd:default
svc:/application/sthwreg:default
svc:/system/utmp:default
svc:/system/console-login:default
svc:/application/management/wbem:default
svc:/network/rpc/gss:default
svc:/network/rpc/meta:default
svc:/application/x11/xfs:default
svc:/application/font/stfsloader:default
svc:/network/nfs/client:default
svc:/network/rpc/rstat:default
svc:/network/rpc/cde-calendar-manager:default
svc:/network/rpc/cde-ttdbserver:tcp
svc:/network/rpc/smserver:default
svc:/network/rpc/mdcomm:default
svc:/network/rpc/metamed:default
svc:/network/rpc/metamh:default
svc:/network/rpc/rusers:default
svc:/network/cde-spc:default
svc:/network/security/ktkt_warn:default
svc:/system/filesystem/volfs:default
svc:/network/telnet:default
svc:/network/nfs/rquota:default
svc:/network/ftp:default
svc:/system/filesystem/autofs:default
svc:/network/finger:default
svc:/network/login:rlogin
svc:/network/shell:default
svc:/network/rpc-100235_1/rpc_ticotsord:default
svc:/network/stdiscover:default
svc:/network/stlisten:default
svc:/network/fs/tcp:default
svc:/system/system-log:default
svc:/system/dumpadm:default
svc:/network/smtp:sendmail
svc:/application/management/seaport:default
- 41 -
IBM Work Intruction

online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
offline
offline
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_20
Jan_27
Jan_27
Jan_27
Jan_27
Jan_20
Jan_20
svc:/system/mdmonitor:default
svc:/network/ssh:default
svc:/application/management/snmpdx:default
svc:/application/management/sma:default
svc:/application/management/dmi:default
svc:/system/fmd:default
svc:/milestone/multi-user:default
svc:/application/cde-printinfo:default
svc:/application/graphical-login/cde-login:default
svc:/milestone/multi-user-server:default
svc:/system/zones:default
svc:/system/basicreg:default
svc:/system/webconsole:console
svc:/network/nfs/server:default
svc:/network/bpcd/tcp:default
svc:/network/vnetd/tcp:default
svc:/network/vopied/tcp:default
svc:/network/bpjava-msvc/tcp:default
svc:/application/print/ipp-listener:default
svc:/application/print/rfc1179:default
Start, Stop or Refresh Services

(Only In Solaris 5.10 Version)
# svcadm "status" "Serivice name OR Path" ----------------------> You Will get the
"Service Name OR path" with ( # svcs -a )
For Example:
# svcadm
# svcadm
# svcadm
# svcadm
disable -t network/ssh:default
enable -t network/ssh:default
restart network/ssh:default
refresh network/ssh:default
For Other than Solaris 5.10 Like Solaris 5.7 , 5.8 , 5.9 Version OS.
To start & stop Service.
# /etc/init.d/sshd stop
# /etc/init.d/sshd start OR
# /etc/init.d/sshd stop; /etc/init.d/sshd start
# kill -HUP `cat /var/run/sshd.pid` -------------------> To refresh the sshd service
# cat /etc/services
---------------------------------> the service configuration file
# cat /etc/hosts -------------------------------------> ( checking the host entris)
# hostname -------------------------------------------> ( checking the hostname)
# ifconfig -a -------------------------------------------> (To Check the Network Interfaces)
Check gateway
# netstat -rn
- 42 -
IBM Work Intruction
- 43 -

Change the permission
# chmod 755 (file or directory name)
Change the ownership
# chown -R oracle:dba /oracle ( where oracle is the user name and dba is group name, /oracle is the mount point )
User creation
# useradd -md /home/oracle oracle ( to create the oracle user under /home)
# usermod -g dba oracle ( changing the oracle user group)
# passwd oracle ( To set password to oracle user)
Finding OS, Hostname, Version of OS, OS Level Patch, Model Details

# uname -a
SunOS PROVISIODM 5.10 Generic_137111-07 sun4u SPARC SUNW, Netra-440
(Operating System, Hostname, Version of OS, OS level patch, SUN Architecture, Model)
CRON Access
# vi /etc/cron.d/cron.allow
oracle
root
:wq!
Check Disks (Hard Disks)

# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@1f,700000/scsi@2/sd@0,0
/pci@1f,700000/scsi@2/sd@1,0
/pci@1f,700000/scsi@2/sd@2,0
/pci@1f,700000/scsi@2/sd@3,0
IBM Work Intruction
- 44 -
Performance Issue
# sar -d 1 5 (To check which disk is busy.)
# sar 1 5 (To check cpu utilisation.)
# vmstat 1 5 (To check virtual memory utilisation.)
Veritas File System Activities

# vxdisk list
DEVICE
Disk_0
Disk_1
EMC3_0
EMC3_1
EMC3_2
EMC3_3
EMC3_4
EMC3_5
EMC3_6
EMC3_7
-------------------------> To list the disks

TYPE
DISK
GROUP
STATUS
auto:sliced
rootdg01
rootdg
online
auto:sliced
rootdg02
rootdg
online
auto:none
online
invalid
auto:cdsdisk smsvg1-disk01 smsvg1
online
online
online
online
auto:cdsdisk opscvg1-disk01 opscvg1
online
online
online
Make Disks Visible by vxdisk Command

# vxdisk scandisks
# vxdg list
NAME
rootdg
opscvg1
smsvg1
STATE
enabled
enabled,cds
enabled,cds
ID
536152017.11.BMDSERVER
1227011624.22.BMDSERVER
1226567711.25.BMDSERVER
Print DG Information
# vxprint -l rootdg
Disk group: rootdg
Group: rootdg
info: dgid=536152017.11.BMDSERVER
version: 110
alignment: 512 (bytes)
activation: read-write
detach-policy: global
copies: nconfig=default nlog=default
devices: max=0 cur=2
minors: >= 38000
IBM Work Intruction
- 45 -
Hierarchy of volumes under ROOTDG

# vxprint -g rootdg -hvt --------------------------> (hirerchary of volumes under rootdg)
V NAME
PL NAME
SD NAME
SV NAME
SC NAME
DC NAME
SP NAME
RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE

VOLUME
KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
PLEX
DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
PLEX
VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
PLEX
CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
PARENTVOL LOGVOL
SNAPVOL
DCO
v rootvol
ENABLED ACTIVE 20972736 ROUND pl rootvol-01 rootvol
ENABLED ACTIVE 20972736 CONCAT sd rootdg01-B0 rootvol-01 rootdg01 143328959 1
0
Disk_0
sd rootdg01-02 rootvol-01 rootdg01 0
20972735 1
Disk_0
pl rootvol-02 rootvol
ENABLED ACTIVE 20972736 CONCAT sd rootdg02-01 rootvol-02 rootdg02 0
20972736 0
Disk_1
root
RW
ENA
ENA
RW
ENA
v swapvol
ENABLED NEEDSYNC 61442688 ROUND swap
pl swapvol-01 swapvol
ENABLED ACTIVE 61442688 CONCAT RW
sd rootdg01-01 swapvol-01 rootdg01 20972735 61442688 0
Disk_0 ENA
pl swapvol-02 swapvol
ENABLED ACTIVE 61442688 CONCAT RW
sd rootdg02-02 swapvol-02 rootdg02 20972736 61442688 0
Disk_1 ENA
IBM Work Intruction
- 46 -
DISK GROUP Long Name

# vxprint -l rootdg --------------------> ( long list of diskgroup)
Example:
# vxdisksetup -i "Divice Nmae" ---------------------> ( it will create in sliced format)
#
vxdisksetup -i EMC3_0
# vxdisksetup -i "Device Name" format =cds -------------------> ( It will create in cds format)
#
vxdisksetup -i EMC3_0 format- =cds
# vxdisksetup -i "Device Name" ----------------------------> (it will create in sliced format)
#
vxdisksetup -i EMC3_0
# vxdisksetup -i "Device Name" format=cds -----------------------------> (It will create in cds format)
# vxdisksetup -i EMC3_0 format=cds
# vxdiskunsetup "Device Nmme" ---------------------------------------> (To remove the disk from the control of veritas)
# vxdiskunsetup EMC3_0
# vxdg init "Dgname" "Diskname"="Device Nmae" -----------> ( diskname is for veritas to use, this command used
to create disk group)
# pkginfo -l VRTSvxvm ----------------------------> ( To check the version of vxvm)
PKGINST: VRTSvxvm
NAME: VERITAS Volume Manager, Binaries
CATEGORY: system
ARCH: sparc
VERSION: 4.0,REV=12.06.2003.01.35
BASEDIR: /
VENDOR: VERITAS Software
DESC: Virtual Disk Subsystem
PSTAMP: VERITAS-4.0R_p1.4:14-January-2004
INSTDATE: Dec 28 1986 03:39
HOTLINE: 800-342-0652
EMAIL: support@veritas.com
STATUS: completely installed
FILES:
823 installed pathnames
24 shared pathnames
18 linked files
97 directories
411 executables
257411 blocks used (approx)
# vxlicrep ---------------------> (To check the VERITAS licence)
# vxdg -g "dgname" adddisk "disknams" ="Dive Name" ------------------> (To add the disk to existed diskgroup)
According to above Example:----# vxdg -g smsdg1 adddisk "diskname"=EMC3_1
# vxdg -g "dgname" rmdisk "diskname" -----------------------------------> ( To remove the disk from the diskgroup)
# vxdg list
NAME
Rootdg
opscvg1
smsvg1
STATE
enabled
enabled,cds
enabled,cds
ID
536152017.11.BMDSERVER
1227011624.22.BMDSERVER
1226567711.25.BMDSERVER
# vxassist -g opscvg1 maxsize --------------> (To check the Maxsize of volume)

Maximum volume size: 4657152 (2274Mb)
# vxassist -g dgname make "LV Name" 400g -----------------------> ( To create lv with 400gb )
# vxresize -g "Diskgroupname" "lvname" +100g ------------------> ( To extend the LV Size in Online )
# vxedit -g "Diskgroupname" -rf rm "lvname" ---------------------> ( To remove logical volume after unmounting the
mount point)
# vxdg destroy "Dgname" ---------------------------------> ( To remove diskgroup compleately)
# vxdiskunsetup "Diskname" -------------------------------> ( To remove the disk from veritas control)
IBM Work Intruction
- 47 -
FTP
Disable ftp access for particular user put user name in below file.
# vi /etc/ftpd/ftpusers
root
oracle
:wq!
RCP Issue
(Basic Steps to check)
a. First check the user home shell in /etc/passwd file

b. put that shell in /etc/shells file ( By Default it will not be thier we have to create this file.)
c. # vi /etc/inetd.conf
---------> (Uncomment the shell & login lines)
:wq!
d. refresh the inetd service.
Package Installation
# pkginfo -l -------------------------------> ( To list the installed packages)
# pkgadd -d "Package Name" ----------------------> (To add package)
-d SUNWgtar
# pkgchk "Packge Name" --------------------------> (To check Package status)
SUNWgtar
# pkgrm "Packge Name" --------------------------> (To remove package)
SUNWgtar
For Example:- # pkgadd

# pkgchk
# pkgrm
Patch Installation
# patchadd "Patch Name" ---> (To Add Patch)
patchadd /var/sadm/spool/104945-02
# patchrm
"Patch Name" ----------> (To remove Patch)
Adding and Removing Route

# route add -net "IP Address" "Gateway"
For Example.
# route add -net 172.26.0.0 172.16.26.2 2
Put the gateway IP Address in /etc/defaultrouter file
# vi /etc/defaultrouter
172.16.26.2.2
:wq!
# route delete default "Gateway Address" ------------------------->
(To delete default router)
# route delete -net "Static IP Address" "Gateway of static router"
For Example:- #
IBM Work Intruction
Additional Space Requirement
- 48 -
IBM Work Intruction
- 49 -
Adding Space on CRM server

1. Check the request is received with complete requirement, approved & remedy call has been logged for
request.
2. Check for the total requirement in each category like data chunks or index chunks.
3. Check if required space is available in existing same type (Data/Index) volume group.
4. Note last sequence of the chunk created in the VG where new chunk is to be created.
5. Create logical volume (chunk) using following command.
mklv t raw y chunkname (next sequence) vgname size
e.g.
mklv t raw y vg15d_8192m_123 vg15d 8192M

Logical volume type (must be raw always for CRM)
The naming convention should be same like vgname_size_sequence
Volume Group Name
Size of the chunk requested
6. Repeat the above command as many times no of chunks required.

7. Care should be taken to to use data vg (naming convention vg15d etc. ) for data chunks & index vg
(naming convention vg15x etc.) for index chunks.
8. It will create 2 files in dev directory.
e.g. /dev/vg15d_8192m_123 & /dev/rvg15d_8192m_123
Change ownership of raw chunk with oracle user and group.
e.g. chown oracle:dba /dev/rvg15d_8192m_123
9. Inform requestor on mail with names of the respective chunks created.
10. Close the request in remedy tool.
If free space & devices are not available on server?

In this case forward request to storage team for assigning required disk devices with no. of BCV devices (if
required) for allocation. Follow above steps post getting confirmation about disk addition from storage team.
Post Completion tasks.

Provide modified VG details to BCV team for updating existing DG configuration .
IBM Work Intruction
- 50 -
Adding space on existing server

request.
2. The space requirement is of the type of extending existing mount point or new mount point.
3. If existing mount point extension then
a. Check is requested space is already available in Volume group.
b. If space is not available on VG check if free devices are available on server.
c. If yes then extend VG with required no of disks.
d. Extend the logical volume of related file system with requested space.
4. If new mount point creation then check usage of the new mount point (will be used for data files, index files
or application files). Check if requested space is available on any of the existing VG of same type.
5. If space is available then create mount point with requested parameters like space, ownership to particular
user, mount name etc.
6. If space is not available then add extend VG with available free devices on system. Then add new logical
volume & mount it with requested parameters like space, ownership to particular user, mount name etc.
7. Send the confirmation mail to requestor & close ticket in Remedy.
If free space & devices are not available on server?

In this case forward request to storage team for assigning required disk devices with no. of BCV devices (if
required) for allocation. Follow above steps post getting confirmation about disk addition from storage team.
Post Completion tasks.

Provide modified VG details to BCV team for updating existing DG configuration.
IBM Work Intruction
AIX Server Installation and Patching
- 51 -
IBM Work Intruction
- 52 -
AIX Server Installation

(a) To perform a new and a complete overwrite BOS installation using an HMC
and a CD-ROM device
Prerequisites
In this procedure, you will perform a new and complete AIX BOS installation on a logical partition using the partition's CD-ROM device.
This procedure assumes that there is an HMC attached to the managed system.
Before you begin this procedure, you should have already used the HMC to create a partition and partition profile for the client. Assign
the SCSI bus controller attached to the CD-ROM device, a network adapter, and enough disk space for the AIX operating system to the
partition. Set the boot mode for this partition to be SMS mode. After you have successfully created the partition and partition profile,
leave the partition in the Ready state.
Step 1. Activate the partition

1.
Activate the partition

a. Insert the AIX 5L Volume 1 CD into the CD device of the managed system.
b. Right-click on the partition to open the menu.
c. Select Activate. The Activate Partition menu opens with a selection of partition profiles. Be sure the correct profile is
highlighted.
d. Select Open a terminal window or console session at the bottom of the menu to open a virtual terminal (vterm)
window.
e. Select Advanced to open the Advanced options menu.
f.
For the Boot mode, select SMS.
g. Select OK to close the Advanced options menu.
h. Select OK. A vterm window opens for the partition.
Step 2. In the SMS menu on the vterm

1.
In the SMS menu on the vterm, do the following:

a. Press the 5 key and press Enter to select 5. Select Boot Options.
PowerPC Firmware
Version SF220_001 SMS 1.5
(c) Copyright IBM Corp. 2000, 2003 All rights reserved.
----------------------------------------------------------Main Menu
1.
2.
3.
4.
5.
Select Language
Setup Remote IPL (Initial Program Load)
Change SCSI Settings
Select Console
Select Boot Options
----------------------------------------------------------Navigation Keys:
X = eXit System Management Services
----------------------------------------------------------Type the number of the menu item and press Enter or select
Navigation Key: 5
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
Press the 2 key and press Enter to select 2. Select Boot Devices.
Press the 1 key and press Enter to select 1. Select first Boot Device.
Press the 3 key and press Enter to select 3. CD/DVD.
Select the media type that corresponds to the CD-ROM device and press Enter.
Select the device number that corresponds to the CD-ROM device and press Enter. The CD-ROM device is now the
first device in the Current Boot Sequence list.
Press the ESC key until you return to the Configure Boot Device Order menu.
Press the 2 key to select 2. Select the second Boot Device.
Press the 5 key and press Enter to select 5. Hard Drive.
If you have more than one hard disk in your partition, determine which hard disk you will use to perform the AIX
installation. Select the media type that corresponds to the hard disk and press Enter.
Select the device number that corresponds to the hard disk and press Enter.
Press the x key to exit the SMS menu. Confirm that you want to exit SMS.
Step 3. Boot from the AIX 5L Volume 1

1.
Boot from the AIX 5L Volume 1, as follows:

a. Select Console and press Enter.
IBM Work Intruction

b.
c.
- 53 -
Select Language for BOS installation menus and press Enter to open the Welcome to Base Operating System
Installation and Maintenance menu.
Type 2 to select Change/Show Installation Settings and Install in the Choice field and press Enter.
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
Change/Show Installation Settings and Install
Start Maintenance Mode for System Recovery
88 Help ?
99 Previous Menu
>>> Choice [1]: 2
Step 4. Verify or change BOS installation settings

1.
Verify or change BOS installation settings, as follows:

a. Type 1 in the Choice field to select the System Settings option.
b. Type 1 for New and Complete Overwrite in the Choice field and press Enter.
c.
d.
e.
Note:
The installation methods available depend on whether your disk has a previous Version of AIX installed.
When the Change Disk(s) screen displays, you can change the destination disk for the installation. If the default
shown is correct, type 0 in the Choice field and press Enter. To change the destination disk, do the following:
1. Type the number for each disk you choose in the Choice field and press Enter. Do not press Enter a final
time until you have finished selecting all disks. If you must deselect a disk, type its number a second time
and press Enter.
2. When you have finished selecting the disks, type 0 in the Choice field and press Enter. The Installation
and Settings screen displays with the selected disks listed under System Settings.
If needed, change the primary language environment. Use the following steps to change the primary language used
by this installation to select the language and cultural convention you want to use.
Note:
Changes to the primary language environment do not take effect until after the BOS installation has completed and
your system is rebooted.
1. Type 2 in the Choice field on the Installation and Settings screen to select the Primary Language
Environment Settings option.
2. Select the appropriate set of cultural convention, language, and keyboard options. Most of the options are
a predefined combination; however, you can define your own combination of options.
To choose a predefined Primary Language Environment, type that number in the Choice field
and press Enter.
To configure your own primary language environment, do the following:
a. Select MORE CHOICES.
b. Select Create Your Own Combination.
c. When the Set Primary Cultural Convention screen displays, type the number in the
Choice field that corresponds to the cultural convention of your choice and press Enter.
d. When the Set Primary Language screen displays, type the number in the Choice field
that corresponds to your choice for the primary language and press Enter.
e. When the Set Keyboard screen displays, type the number in the Choice field that
corresponds to the keyboard attached to the system and press Enter.
After you have made all of your selections, verify that the selections are correct. Press Enter to confirm your
selections and to begin the BOS installation. The system automatically reboots after installation is complete.
IBM Work Intruction
- 54 -
Step 5. Switch the partition to Normal Mode

1.
Switch the partition to Normal Mode, as follows:

a. Right-click on the Partition profile to open the menu. Be sure the correct partition profile is highlighted.
b. Select Properties.
c. Select the Settings tab.
d. For the Boot Mode, select Normal.
e. Select OK to close the Properties menu.
f.
Right-click on the partition to open the menu.
g. Select Restart Partition.
h. Select Immediate for the Restart Options.
i.
Confirm that you want to restart the partition.
j.
When the partition has restarted, right-click on the partition to open the menu.
k. Select Open terminal window to open a virtual terminal (vterm) window.
Step 6. Complete the BOS installation

1.
Complete the BOS installation, as follows:

a. Type vt100 as the terminal type.
Set Terminal Type

The terminal is not properly initialized. Please enter a
terminal type and press Enter. Some terminal types are
not supported in non-English languages.
Ibm3101 tvi912 vt330
Ibm3151 tvi920 vt340
Ibm3161 tvi925 wyse30
Ibm3162 tvi950 wyse50
Ibm3163 vs100
wyse60
Ibm3164 vt100
wyse100
Ibmpc
vt320
wyse350
lft
sun
+---------------------------Messages---------| If the next screen is unreadable, press
88 Help ? | Break (Ctrl-c) to return to this screen.
99 Exit
|
|
>>> Choice []: vt100
b.
c.
d.
e.
In the License Agreement menu, select Accept License Agreements.

Select Yes to ACCEPT Installed License Agreements.
Press F10 or Esc+0 to exit the License Agreement menu.
In the Installation Assistant main menu, select Set Date and Time.
Installation Assistant
Set Date and Time
Set root Password
Configure Network Communications
Install Software Applications
Using SMIT (information only)
F1=Help
F9=Shell
f.
F2=Refresh
F10=Exit
F3=Cancel F8=Image
Enter=Do
Set the correct date, time, and time zone. Press the F3 or Esc+3 key to return to the Installation Assistant main
menu.
IBM Work Intruction

g.
h.
i.
j.
- 55 -
Select Set Root Password. Set a root password for the partition.
Select Configure Network Communications. Select TCP/IP Startup. Select from the Available Network
Interfaces and press Enter. Enter the appropriate network information in the Minimum Configuration and Startup
menu and press Enter. Use the F3 or Esc+3 key to return to the Installation Assistant main menu.
Exit the Installation Assistant by typing F10 or Esc+0.
The vterm window displays a login prompt.
At this point, the installation is complete.
(b) Perform a Migration BOS installation from CD

Note:
If you are overwriting an existing system, gather the TCP/IP information before you begin this scenario. Also, before you perform a
migration installation, make sure you have reliable backups of your data and any customized applications or volume groups. The
instructions on how to create a system backup are described later in this article.
NOTE: Using this scenario, you can migrate a system from AIX 4.3.3 (or later) to AIX 5.3.
Step 1. Prepare for the migration

Before starting the migration, complete the following prerequisites:
1. Ensure that the root user has a primary authentication method of SYSTEM. You can check this condition by typing the
following command:
# lsuser -a auth1 root
If needed, change the value by typing the following command:
# chuser auth1=SYSTEM root

2.
3.
4.
5.
Before you begin the installation, other users who have access to your system must be logged off.
Verify that your applications will run on AIX 5L Version 5.3. Also, check if your applications are binary compatible with AIX 5L
Version 5.3. If your system is an application server, verify that there are no licensing issues. Refer to your application
documentation or provider to verify on which levels of AIX your applications are supported and licensed. Check that your
hardware microcode is up to date.
All requisite hardware, including any external devices, such as tape drives or CD/DVD-ROM drives must be physically
connected and powered on.
Use the errpt command to generate an error report from entries in the system error log. To display a complete detailed report,
type the following:
# errpt a
6.
7.
There must be adequate disk space and memory available. AIX 5L Version 5.3 requires 128MB of memory and 2.2GB of
physical disk space.
Run the pre-migration script located in the mount_point/usr/lpp/bos directory on your CD. To mount the CD, run the following
command:
# mount -v cdrfs -o ro /dev/cdN /mnt
where "N" is your CD drive number.

8.
9.
Make a backup copy of your system software and data. The instructions on how to create a system backup are described
elsewhere in this article.
Always refer to the release notes for the latest migration information.
Step 2. Boot from the AIX product CD

1.
2.
3.
If they are not already on, turn on your attached devices.

Insert the AIX Volume 1 CD into the CD-ROM device.
Reboot the system by typing the following command:
# shutdown r
IBM Work Intruction

4.
5.
6.
7.
- 56 -
When the system beeps twice, press F5 on the keyboard or 5 on an ASCII terminal. If you have a graphics display, you will
see the keyboard icon on the screen when the beeps occur. If you have an ASCII terminal, you will see the word keyboard
when the beeps occur.
Select the system console by pressing F1 or 1 on an ASCII terminal and press Enter.
Select the English language for the BOS installation menus by typing a 1 at the Choice field and press Enter. The Welcome
to Base Operating System Installation and Maintenance menu opens.
Type 2 to select Change/Show Installation Settings and Install in the Choice field and press Enter.
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]: 2
Step 3. Verify migration installation settings and begin installation

1.
Verify that migration is the method of installation. If migration is not the method of installation, select it now. Select the disk or
disks you want to install.
1 System Settings:
Method of Installation....................Migration
Disk Where You Want to Install............hdisk0
2.
3.
4.
5.
Select Primary Language Environment Settings after install.

Type 3 and press Enter to select More Options. To use the Help menu to learn more about the options available during a
migration installation, type 88 and press Enter in the Installation Options menu. For more information about the installation
options available in AIX 5L Version 5.3, see Installation Options in the AIX 5L Version 5.3 Installation Guide and Reference.
Verify the selections in the Migration Installation Summary screen and press Enter.
When the Migration Confirmation menu displays, follow the menu instructions to list system information or continue with the
migration by typing 0 and pressing Enter.
IBM Work Intruction
- 57 -
Migration Confirmation
Either type 0 and press Enter to continue the installation,
or type the number of your choice and press Enter.
1. List the saved Base System configuration files which
will not be merged into the system. These files are
saved in /tmp/bos.
2. List the filesets which will be removed and not replaced.
3. List directories which will have all current contents
removed.
4. Reboot without migrating.
Acceptance of license agreements is required before using
system. You will be prompted to accept after the system
reboots.
>>> 0 Continue with the migration.
88 Help ?
-----------------------------------------------------------WARNING: Selected files, directories, and filesets
(installable options) from the Base System will be removed.
Choose 2 or 3 for more information.
>>> Choice[0]:
Step 4. Verify system configuration after installation

After the migration is complete, the system will reboot. Verify the system configuration, as follows:
1. After a migration installation, the Configuration Assistant opens on systems with a graphics display. And after a migration
installation, the Installation Assistant opens on systems with an ASCII display.
2.
3.
4.
5.
6.
Select the Accept Licenses option to accept the electronic licenses for the operating system.
Verify the administrator (root user) password and network communications (TCP/IP) information.
Use any other options at this time. You can return to the Configuration Assistant or the Installation Assistant by typing
configassist or smitty assist at the command line.
Select Exit the Configuration Assistant and select Next. Or, press F10 or ESC+0 to exit the Installation Assistant.
If you are in the Configuration Assistant, select Finish now. Do not start the Configuration Assistant when restarting AIX and
select Finish.
When the login prompt displays, log in as the root user to perform system administration tasks.
Run the /usr/lpp/bos/post_migration script.
(c) Clone a rootvg using alternate disk installation

Using this scenario, you can clone AIX running on rootvg to an alternate disk on the same system, install a user-defined software
bundle, and run a user-defined script to customize the AIX image on the alternate disk. Because the alternate disk installation process
involves cloning an existing rootvg to a target alternate disk, the target alternate disk must not be already assigned to a volume group.
Step 1. Prepare for the alternate disk installation

1.
Check the status of physical disks on your system. Type:

# lspv
2.
Output similar to the following displays:
IBM Work Intruction

hdisk0
hdisk1
0009710fa9c79877
0009710f0b90db93
- 58 rootvg
None
active
You can use hdisk1 as our alternate disk because no volume group is assigned to this physical disk.
3.
Check to see if the alt_disk_install fileset has been installed by running the following (Note: This command is obsolete in AIX
5L Version 5.3. It has been replaced by alt_disk_copy, alt_disk_mksysb, and alt_rootvg_op.):
# lslpp -L bos.alt_disk_install.rte
4.
Output similar to the following displays if the alt_disk_install fileset is not installed:
lslpp: 0504-132 Fileset bos.alt_disk_install.rte not installed.
5.
Using Volume 1 of the AIX installation media, install the alt_disk_install fileset by running the following:
# geninstall -d/dev/cd0 bos.alt_disk_install.rte
6.
+-------------------------------------------------------------+
Summaries
+-------------------------------------------------------------+
Installation Summary
--------------------------------------------------------------Name
Level Part Event Result
--------------------------------------------------------------bos.alt_disk_install.rte 5.3.0.0 USR
APPLY SUCCESS
7.
Create a user-defined bundle called /usr/sys/inst.data/user_bundles/MyBundle.bnd that contains the following filesets:
I:bos.content_list
I:bos.games
8.
To create a user-defined software bundle, Create a text file with the extension .bnd in the /usr/sys/inst.data/user_bundles path by
running the following:
# vi /usr/sys/inst.data/user_bundles/MyBundle.bnd
Add the software products, packages, or filesets to the bundle file with one entry per line. Add a format-type prefix to each entry. For this
example, we are dealing with AIX installp packages, so the format-type prefix is I:.
Type the following in the MyBundle.bnd file: I: sysmgt.websm.security.
9. Create the /home/scripts directory:
mkdir /home/scripts
10. Create a user-defined customization script called AddUsers.sh in the /home/scripts directory:
touch /home/scripts/AddUsers.sh
chmod 755 /home/scripts/AddUsers.sh
11. Edit /home/scripts/AddUsers.sh to contain the following lines:
mkuser johndoe
touch /home/johndoe/abc.txt
IBM Work Intruction
- 59 -
touch /home/johndoe/xyz.txt
Step 2. Perform the alternate disk installation and customization

1.
To clone the rootvg to an alternate disk, type the following at the command line to open the SMIT menu:
# smit alt_clone
2.
3.
4.
5.
6.
7.
8.
Select hdisk1 in the Target Disk to Install field.

Select the MyBundle bundle in the Bundle to Install field.
Insert Volume 1 of the installation media.
Type /dev/cd0 in the Directory or Device with images field. (Note: Required only if filesets, bundles or fixes used, else point 4
& 5 can be ignored)
Type /home/scripts/AddUsers.sh in the Customization script field.
Press Enter to start the alternate disk installation.
Check that the alternate disk was created by running the following:
# lspv
9.
hdisk0
hdisk1
0009710fa9c79877
0009710f0b90db93
rootvg
altinst_rootvg
Step 3. Boot from the alternate disk

1.
By default, the alternate disk installation process changes the boot list to the alternate disk. To check this, run the following:
# bootlist -m normal -o
2.

hdisk1
3.
Reboot the system. Type:

# shutdown -r
4.
The system boots from the boot image on the alternate disk (hdisk1).
Step 4. Verify the operation

1.
When the system reboots, it will be running off the alternate disk. To check this, type the following:
# lspv
2.
hdisk0
hdisk1
3.
0009710fa9c79877
0009710f0b90db93
old_rootvg
rootvg
Verify that the customization script ran correctly by typing the following:
# find /home/johndoe print
4.
/home/johndoe
/home/johndoe/.profile
/home/johndoe/abc.txt
/home/johndoe/xyz.txt
5.
Verify that the contents of your software bundle was installed by typing the following:
# lslpp -Lb MyBundle
6.
IBM Work Intruction
- 60 -
Fileset
Level State Description
-----------------------------------------------------------bos.content_list 5.3.0.0 C AIX Release Content List
bos.games
5.3.0.0 C Games
(d) Install a client using NIM

The AIX Network Installation Manager (NIM) is a function that allow you to install AIX over the network. NIM provides the ability to install
AIX on a pSeries machine from a server called the NIM master over the network. NIM can install and maintain not only the AIX
operating system, but also any additional software and fixes. NIM also allows you to customize the configuration of machines both
during and after installation, such as a host name and TCP/IP addresses. NIM eliminates the need for access to physical media, such
as tapes and CD-ROMs, because the installation images are stored on a NIM server as resources.
In this section, we briefly outline the simple NIM installation steps:
1. Configure the NIM master.
2. Create a mksysb image from your master system.
3. Transfer the mksysb image to the NIM master.
4. Define the mksysb image as a resource to NIM and allocate it to a new client.
5. Power on the new machine by specifying a network adapter as the boot device
IBM Work Intruction
- 61 -
Configure the NIM master

Although NIM configuration can be complex due to the rich functions provided by NIM, we used the nim_master_setup command in
this section to quickly set up the minimum NIM master configuration. The command can take a while to run, as it has to build all the NIM
resources shown in Table below. You will be prompted to change the AIX 5L Version 5.3 media while the command is running.
Please make sure that you have enough free space in rootvg before running
nim_master_setup.
It will automatically create two new file systems, /tftpboot and /export/nim in rootvg; these will require approximately 4.5 GB of space.
Also, if you have disabled tftp, bootp, and NFS for security reasons, you will need to re-enable them for NIM. This is another reason a
build zone is recommended.
Resource name Description
boot The network boot image.
nim_script NIM customization script.
generic_sysb Generic mksysb image.
resolv_res The /etc/resolv.conf file to be used.
bid_tty_ow bosinst.data for the installation using a serial console. Instructs AIX
on how to set the parameters upon installation, for example, locale
settings, disks to use, and the type of install.
bid_lft_ow bosinst.data for the installation using the lft device.
530lpp_res AIX 5L Version 5.3 installable package files.
530spot_res AIX 5L Version 5.3 spot or root file system to be used during install
Creating your master mksysb image file
To create a mksysb image file on the system you wish to clone, use the mksysb command, as shown.
# mksysb -ieX /backup/clone01.mksysb
Creating information file (/image.data) for rootvg..
0512-039 mksysb: WARNING: /backup/clone01.mksysb does not appear to be a tape device and will NOT have a bootable image.
Creating list of files to back up.Backing up 27388 files...............
27388 of 27388 files (100%)
0512-038 mksysb: Backup Completed Successfully.
0512-040 mksysb: WARNING: /backup/clone01.mksysb does not appear to be a tape device and does NOT have a bootable image.
Then transfer the mksysb image file to the NIM master using ftp or scp and place it in the /export/nim file system.
Defining NIM resources
On the NIM master, do the following steps:
1. Define the template bosinst_data resource: bosinst_mksysb In this example, the bid_tty_mksysb file is modified from the default
bid_tty_ow file to enable unattended installation:
# nim -o define -t bosinst_data -a server=master\ -a location=/export/nim/bid_tty_mksysb bosinst_mksysb
2. Define the NIM client resource svr03:
# nim -o define -t standalone -a netboot_kernel=mp\ -a platform=chrp -a cable_type1=tp\ -a if1="master_net svr03 00045576ABDD"
svr03
# nim -o reset svr03
where svr03 is the host name of new server you are going to install, and 00045576ABDD is the MAC address of the integrated Ethernet
adapter of this server.
3. Deallocate the script resources if it is allocated to the client:
# nim -o deallocate -a bosinst_data=bosinst_template svr03
4. Define the mksysb image resource svr03_mksysb_res:
# nim -o define -t mksysb -a location=/export/nim/clone01.mksysb\ -aserver=master svr03_mksysb_res
5. Allocate these 4 resources - mksysb, bosinst_data, spot, and lppsource to the NIM client:
# nim -o allocate -a mksysb=svr03_mksysb_res\
-a bosinst_data=bosinst_mksysb -a spot=530spot_res\
-a lpp_source=530lpp_res svr03
Verify the resources allocation status using lsnim -l svr03, as shown in the
following example:
# lsnim -l svr03
svr03:
class = machines
type = standalone
IBM Work Intruction
- 62 -
platform = chrp
netboot_kernel = mp
if1 = master_net svr03 00045576ABDD
cable_type1 = tp
Cstate = BOS installation has been enabled
prev_state = ready for a NIM operation
Mstate = currently running
boot = boot
bosinst_data = bosinst_mksysb
lpp_source = 530lpp_res
mksysb = svr03_mksysb_res
nim_script = nim_script
spot = 530spot_res
control = master
Perform the installation operation
When powering on the new machine, specify a network adapter as the boot device using the SMS menu. Then, perform the installation
operation on the NIM master using the following command:
# nim -o bos_inst -asource=mksysb -a boot_client=no svr03
Use lsnim -l svr03 to monitor progress of the install.
This completes your NIM Client Installation.
AIX Server Patching

Hdiskx = disk removed for alt disk install
Hdisky = primary disk
Break rootvg mirror
lsvg -p rootvg
Pick one of the disks in rootvg to remove.
unmirrorvg rootvg hdiskx
chpv -c hdiskx
bosboot -a
bootlist -m normal -o hdisky
(Clears boot image from hdiskx)

(Rebuilds boot image on hdisky)
(Sets bootlist for hdisky only)
Check to see if there are logical volumes left on the disk

lspv -l hdiskx
If there is move it to the remaining disk in the rootvg
migratepv -l [logical volume name] hdiskx hdisky
OR:
If not enough space on hdisky delete it:
sysdumpdev -l
(to list the dump areas, substitute primary in p field below if not the same as example)
sysdumpdev -p /dev/pridumplv -s /dev/sysdumpnull (Removes secondary dumpdevice)
rmlv -p hdiskx secdumplv
(Removes secdumplv from hdiskx)
When there is nothing left on the hdisk remove it from the rootvg
reducevg rootvg hdiskx
Backup (Clone Disk)
Change your putty settings (connections -> Seconds between keepalives put it as 10 or 20) as this may take
roughly 30 minutes.
IBM Work Intruction
- 63 -
smit alt_clone
Use the disk freed from the rootvg as the target disk Set bootlist to boot from this disk at next reboot NO All
other options are default.
This may take 20 to 30 minutes, once it is completed okay check for lspv you will find something like this.
[m013313@kaha1_csm]:/home/m013313 > lspv
hdisky
00cc596d606185b3
rootvg
active
hdiskx
00cc596d0e86f1e1
altinst_rootvg
Commit any applied software
smit commit
All options are default
Apply TL (if applicable)
Copy TL on the CSM server to LPAR and unpack (default location /opt/tecunix)
smit update_all
Check everything is applied
oslevel -s
Reboot
shutdown -Fr
Remirror rootvg
alt_disk_install -X
(to delete the old alt disk)
extendvg -f rootvg hdiskx

(to add hdiskx to the rootvg)
mirrorvg rootvg hdisky hdiskx (to mirror the rootvg except the dump areas)
bosboot -a
bootlist -m normal -o hdisky hdiskx
Dump devices reinstating:
sysdumpdev -l
(to list the dump areas)
migratepv -l [logical volume name] hdisky hdiskx (to migrate the dump area)
or
Create seconday dump device and reassign
mklv -y'secdumplv' -t'sysdump' -a'ie' rootvg <PP> hdiskx (<PP> denotes the physical partitions required, see
primary dump device for size > lspv -l hdisky)
sysdumpdev -l
(to list the dump areas, substitute primary in -p field below if not the same as example)
sysdumpdev -p /dev/pridumplv -s /dev/secdumplv -P (Reassign secondary dump device secdumplv)
IBM Work Intruction
- 64 -
BCV Work Instructions

Prerequisite:
List of devices on primary server with details of corresponding Volume Group (VG) details
List of Filesystems (Mount Points) to be configured in BCV with respective VG details
Required no of BCV devices are already available on respective BCV server
Steps for configuring Device Group (DG)
Source devices are paired with respective target device in DG using following command. (this is to be done
on BCV server)
To add source device - symld -g DGNAME add dev {device id}
To add target device - symld -g DGNAME add dev {device id} tgt
Once DG creation is completed synchronization is triggered in full backup differential mode using following
command. (this is to be done on BCV server)
symclone -g DGNAME create -precopy -diff -tgt
Check for 99% completion of BCV replication. This can be done using following command
symclone -g DGNAME query i 10
Once 99% replication is complete for having consistent backup copy production database needs to be
changed in backup mode. This is done by logging in production server & executing following script from
/backup folder (this is to be done on Production server)
./ora_begin
This will put all database datafiles in backup mode
Now when database is in backup mode snapshot of BCV will be taken using following command
symclone -g DGNAME activate -tgt
Immediately after this the database will be brought back to normal mode from backup mode using following
command (this is to be done on Production server)
./ora_end
After 100% completion of background copy (can be verified using symclone verify command) all VGs will
be imported using respective map file created on production server on BCV server.
Once all VGs are imported successfully on BCV server mount directories will be created for all the
filesystems to be mounted on BCV server. All the filesystems will be mounted on BCV server after
completing fsck (file system check).
Ownership of all mounted filesystems will be changed to oracle user recursively & BCV copy will be
released to Oracle Team for validation.
IBM Work Intruction
- 65 -
After validation confirmation from database tem, BCV is released to Veritas Team with entire details of
mount points to be backed up for tape backup.
All the above mentioned steps are converted into standard script format to be used during day-to-day
operations.
Daily Activities for BCV Backup:

Following are the activities performed while taking regular configured BCV backups
As per backup schedule earlier backup completion is verified with Veritas team
On confirmation of successful tape backup the related filesystems of the environment to be backed up are
dismounted from BCV server using preconfigured script
DG is resynced in recreate in differential mode using following command

symclone -g DGNAME recreate -precopy -tgt
Once 99% replication is complete for having consistent backup copy production database needs to be
changed in backup mode. This is done by logging in production server & executing following script from
/backup folder (this is to be done on Production server)
./ora_begin
Now when database is in backup mode snapshot of BCV will be taken using following command
symclone -g DGNAME activate -tgt
Immediately after this the database will be brought back to normal mode from backup mode using following
command (this is to be done on Production server)
./ora_end
After 100% completion of background copy (can be verified using symclone verify command) predefined
script will be executed which will import all VGs & filesystems will be imported, permissions of file systems
mounted will be changed to oracle user
BCV is released to Veritas Team for tape
IBM Work Intruction
Creating Logical Volumes with the Device File
- 66 -
IBM Work Intruction
- 67 -
Suppose the device file name is /dev/rdsk/c3t5d2

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Login to the server as root.

Create the Physical Volume using pvcreate /dev/rdsk/c3t5d2
Create the volume group mkdir /dev/vg539_13
Create the volume group character device file using
mknod /dev/vg539_13/group c 64 0x140000
To ensure the uniqueness, run ll /dev/*/group |sort -k 6
Create the volume group on the Physical volume
Vgcreate s 16 /dev/vg539_13 /dev/dsk/c3t5d2
Extend the volume group if required on the other Physical Volume as well as alternate links. Vgextends
automatically recognizes the two paths for the same devices and adds them as alternate links.
vgextend /dev/vg539_13 /dev/dsk/c5t5d2
Display the new volume group using vgdisplay /dev/vg539_13
Create the logical volume using
lvcreate -l 17425 -n lvol1 /dev/vg539_13
Create file system using newfs -F vxfs -o largefiles /dev/vg539_13/rlvol1
Create mount point mkdir /ipos_arch01
mount it using mount /dev/vg539_13/lvol1 /ipos_arch01
Enter the entry in fstab
Provide permissions to users.
For cluster systems vgchange -a n /dev/vg..
vgchange -c y /dev/vg...
vgchange -a e /dev/vg...
IBM Work Intruction
- 68 -
File System Creation

Prerequisites:
Request from user or application owner

Collect details whether volume group is exist or not.
Check whether sufficient disk is allocated or not.
Whether disk allocated is internal or storage disk.
Steps for File System Creation with AIX

The essential steps to adding a disk and creating a file system on it are:
1.
2.
3.
4.
5.
6.
Log on as a root .Check the disk in system.

Make the disk a physical volume.
Add the physical volume to a volume group or create a new volume group for it.
Create a logical volume with the characteristics you desire.
Create a file system to be contained in the logical volume.
Mount the file system.
You can do all of through SMITTY.

1. Check free disk using command
#lspv
hdisk0
hdisk1
hdisk2
hdisk3
00cadd4201c15c12
00cadd4251431c49
none
none
rootvg
rootvg
active
active
none
none
>If in case disk is not showing run cfgmgr command to detect disk
>Check disk size using command
#bootinfo -s <hdiskn> where n disk number
# bootinfo -s hdisk2
286102
2 Create Volume Group
>Use Smitty mkvg command
===============================================================
Add a Volume Group
Add an Original Volume Group
Add a Big Volume Group
Add a Scalable Volume Group
===============================================================
IBM Work Intruction
- 69 -
>Select Add Original Volume Group

===============================================================
Add an Original Volume Group
[Entry Fields]
VOLUME GROUP name
Physical partition SIZE in megabytes
* PHYSICAL VOLUME names
Force the creation of a volume group?
Activate volume group AUTOMATICALLY
at system restart?
Volume Group MAJOR NUMBER
Create VG Concurrent Capable?
[datavg01]
256
+
[hdisk2]
no
+
yes
+
[]
no
+#
+
===============================================================
> Enter Volume group name
>Select Physical partition (PP) SIZE as required, 128mb is default PP size.
>Select physical volume in this case hdisk2 by pressing function key f4.
>Keep Activate volume group automatically always yes
3. Create Logical volume.
>Create Logical volume using Smitty mklv.
===============================================================
Add a Logical Volume
Type or select a value for the entry field.
* VOLUME GROUP name
[Entry Fields]
[datavg02]
>Select volume group name by using F4 function key and press enter.
===============================================================
Add a Logical Volume
[TOP]
[Entry Fields]
Logical volume NAME
[datavg02lvol01]
* VOLUME GROUP name
datavg02
* Number of LOGICAL PARTITIONS
[40]
#
PHYSICAL VOLUME names
[hdisk2]
+
Logical volume TYPE
[jfs2]
+
POSITION on physical volume
middle
+
RANGE of physical volumes
minimum
+
MAXIMUM NUMBER of PHYSICAL VOLUMES
[]
#
to use for allocation
Number of COPIES of each logical
1
+
partition
IBM Work Intruction
- 70 -
Mirror Write Consistency?

active
+
Allocate each logical partition copy
yes
+
[MORE...12]
===============================================================
>Enter logical volume name here datavg02lvol01
>Enter number of logical partition here 40.
No of LP = ( filesystem size in GB * 1024 ) / PP size
= (10 GB * 1024) / 256
= 40
>Select PV name
>Select logical volume type jfs2 and Press enter
4. Create mount point
Use # smitty jfs2
command
===============================================================
Enhanced Journaled File Systems
Add an Enhanced Journaled File System
Add an Enhanced Journaled File System on a Previously Defined Logical Volume
Change / Show Characteristics of an Enhanced Journaled File System
Remove an Enhanced Journaled File System
Manage Quotas for an Enhanced Journaled File System
Defragment an Enhanced Journaled File System
List Snapshots for an Enhanced Journaled File System
Create Snapshot for an Enhanced Journaled File System
Mount Snapshot for an Enhanced Journaled File System
Remove Snapshot for an Enhanced Journaled File System
Unmount Snapshot for an Enhanced Journaled File System
Change Snapshot for an Enhanced Journaled File System
Rollback an Enhanced Journaled File System to a Snapshot
===============================================================
>Select Add an Enhanced Journaled File System select volume group name and press enter .
===============================================================
Add an Enhanced Journaled File System
[Entry Fields]
Volume group name
datavg02
SIZE of file system
Unit Size
Gegabytes
+
*
Number of units
[]
#
* MOUNT POINT
[/data]
Mount AUTOMATICALLY at system restart?
yes
+
PERMISSIONS
read/write
+
Mount OPTIONS
[]
+
Block Size (bytes)
4096
+
Logical Volume for Log
+
Inline Log size (MBytes)
[]
#
Extended Attribute Format
Version 1
+
ENABLE Quota Management?
no
+
Enter Mount Point Name here /data
===============================================================
IBM Work Intruction

>Select
- 71 -
Mount AUTOMATICALLY at system restart yes and press enter.
5. Finally mount mount point using following command.

# mount /data
6. Check entry in /etc/filesystems
Using command
#lsfs
Or
cat /etc/filesystems
# lsfs
Name
Nodename Mount Pt
/dev/hd4
-/
/dev/hd1
-/home
/dev/hd2
-/usr
/dev/hd9var -/var
/dev/hd3
-/tmp
/proc
-/proc
/dev/hd10opt -/opt
/dev/datavg02lvol01 -/data
VFS Size Options Auto Accounting

jfs2 10485760 -yes no
jfs2 10485760 -yes no
jfs2 10485760 -yes no
jfs2 10485760 -yes no
jfs2 20971520 -yes no
procfs --yes no
jfs2 10485760 -yes no
jfs2 10485760 rw
yes no
IBM Work Intruction
- 72 -
Step for File System Creation with HP-UX

Using SAM to Install a Disk and Create a File System
1. Log on as root.
2. Run SAM.
3. Highlight Disks and File Systems-> and activate Open.
Select Open Item
in Action menu ..
Select volume group and enter.
IBM Work Intruction
Select create action for new volume group.
Select new volume group name tab .Enter volume group name .Press OK
- 73 -
IBM Work Intruction
- 74 -
Within the Select disk to add window, highlight the disk you wish to add. You can identify it by its model number,
select code and bus address. Activate OK
Select new Logical Volume tab and press enter.
IBM Work Intruction
- 75 -
Enter lvname LV size, Mount Directory name
If you want to give file system type, mount options like large files.
Select Modify FS Defaults press enter.
Exit SAM by returning to the System Administration Manager window and activating Exit SAM
Check entry in /etc/fstab
# cat /etc/fstab
#cat /etc/fstab
IBM Work Intruction

######## rootvg ###############
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /opt vxfs delaylog 0 2
/dev/vg00/lvol5 /tmp vxfs delaylog 0 2
/dev/vg00/lvol6 /usr vxfs delaylog 0 2
/dev/vg00/lvol7 /var vxfs delaylog 0 2
/dev/vg00/lvol8 /home vxfs delaylog 0 2
/dev/testvg01/testvg01lvol01 /test vxfs rw,suid,largefiles,delayl
- 76 -
og,datainlog 0 2
IBM Work Intruction
HP-UX Server Patching
- 77 -
IBM Work Intruction
- 78 -
HP UX Patching How to:

First check your configuration. Make sure that your vg00 is not already mirrored. If it is you can skip part that covers
mirroring. Lines that we should look at are 'Used PV', if it is bigger than one it means that logical volume is mirrored.
All system volumes in vg00 should be mirrored.
# vgdisplay -v /dev/vg00
--- Volume groups --VG Name
VG Write Access
VG Status
Max LV
Cur LV
Open LV
Max PV
Cur PV
Act PV
Max PE per PV
VGDA
PE Size (Mbytes)
Total PE
Alloc PE
Free PE
Total PVG
Total Spare PVs
Total Spare PVs in use
/dev/vg00
read/write
available
255
8
8
16
1
1
2500
1
4
2168
1392
776
0
0
0
--- Logical volumes --LV Name

LV Status
LV Size (Mbytes)
Current LE
Allocated PE
Used PV
/dev/vg00/lvol1
available/syncd
300
75
75
1
LV Name
LV Status
LV Size (Mbytes)
Current LE
Allocated PE
Used PV
/dev/vg00/lvol2
available/syncd
256
64
64
1
LV Name
LV Status
LV Size (Mbytes)
Current LE
Allocated PE
Used PV
/dev/vg00/lvol3
available/syncd
200
50
50
1
LV Name
LV Status
LV Size (Mbytes)
Current LE
Allocated PE
Used PV
/dev/vg00/lvol4
available/syncd
200
50
50
1
LV Name
LV Status
LV Size (Mbytes)
Current LE
/dev/vg00/lvol5
available/syncd
20
5
IBM Work Intruction
- 79 -
Allocated PE
Used PV
5
1
LV Name
LV Status
LV Size (Mbytes)
Current LE
Allocated PE
Used PV
/dev/vg00/lvol6
available/syncd
2572
643
643
1
LV Name
LV Status
LV Size (Mbytes)
Current LE
Allocated PE
Used PV
/dev/vg00/lvol7
available/syncd
1264
316
316
1
LV Name
LV Status
LV Size (Mbytes)
Current LE
Allocated PE
Used PV
/dev/vg00/lvol8
available/syncd
756
189
189
1
--- Physical volumes --PV Name

PV Status
Total PE
Free PE
Autoswitch
/dev/dsk/c0t4d0
available
2168
776
On
Here we saw that none of the logical volumes is mirrored and that we have only one physical volume (/dev/dsk/c0t4d0) in
vg00. In order to mirror this VG we will need to add another physical volume.
Boot Configuration
Let's check our boot configuration.
# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t4d0 (8/16/5.4.0) -- Boot Disk
No Boot Logical Volume configured
Root: lvol3
on:
/dev/dsk/c0t4d0
Swap: lvol2
on:
/dev/dsk/c0t4d0
Dump: lvol2
on:
/dev/dsk/c0t4d0, 0
We can see that our root volume is lvol3 and our swap and dump volume is lvol2 volume, all are in /dev/vg00
volume group.
Create PV and add it to VG

We need to create another physical volume (/dev/dsk/c0t6d0) and add it to the vg00 volume group. This PV has
also to be bootable, thus we use -B option with pvcreate command.
# pvcreate -B /dev/dsk/c0t6d0
# vgextend /dev/vg00 /dev/dsk/c0t6d0
Volume group "/dev/vg00" has been successfully extended.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
IBM Work Intruction
- 80 -
Let's check if it is OK.

# vgdisplay -v /dev/vg00|grep "PV Name"
PV Name
/dev/dsk/c0t4d0
PV Name
/dev/dsk/c0t6d0
Yes, our vg00 VG now has two physical volumes.
Copy boot utilities to new PV

In order to boot from new physical volume we need to copy boot utilities to this volume.
# mkboot /dev/dsk/c0t6d0
# mkboot -a "hpux" /dev/dsk/c0t6d0
We also need to set this PV as second (alternate) boot device. For this we will need hardware path to this device.
# ioscan -fnC disk
Class
I H/W Path
Driver
S/W State H/W Type Description
=====================================================================
disk
2 8/16/5.4.0 sdisk
CLAIMED
DEVICE
IBMAS400DCHS09W
/dev/dsk/c0t4d0
/dev/rdsk/c0t4d0
disk
1 8/16/5.6.0 sdisk
CLAIMED
DEVICE
IBMAS400DCHS09W
/dev/dsk/c0t6d0
/dev/rdsk/c0t6d0
# setboot -a 8/16/5.6.0
Now, let's check if we succeeded.
# lvlnboot -v
Root: lvol3
on:
/dev/dsk/c0t4d0
Swap: lvol2
on:
/dev/dsk/c0t4d0
Dump: lvol2
on:
/dev/dsk/c0t4d0, 0
# setboot
Primary bootpath : 8/16/5.4.0
Alternate bootpath : 8/16/5.6.0
Autoboot is ON (enabled)
Autosearch is ON (enabled)
Mirror vg00
Next step is to mirror all logical volumes in vg00 volume group. We can mirror one by one logical volume but it is
easier and faster to mirror them all at once. This can take some time.
# for i in /dev/vg00/lv*; do lvextend -m 1 $i /dev/dsk/c0t6d0; done
The newly allocated mirrors are now being synchronized. This operation will
take some time. Please wait ....
Logical volume "/dev/vg00/lvol1" has been successfully extended.
--(text cut)--
IBM Work Intruction
- 81 -
Make sure all logical volumes are mirrored.

# vgdisplay -v /dev/vg00|egrep 'LV Name|Used PV'
LV Name
/dev/vg00/lvol1
Used PV
2
LV Name
/dev/vg00/lvol2
Used PV
2
LV Name
/dev/vg00/lvol3
Used PV
2
LV Name
/dev/vg00/lvol4
Used PV
2
LV Name
/dev/vg00/lvol5
Used PV
2
LV Name
/dev/vg00/lvol6
Used PV
2
LV Name
/dev/vg00/lvol7
Used PV
2
LV Name
/dev/vg00/lvol8
Used PV
2
[Split LVs
Now all logical volumes in /dev/vg00 volume group are mirrored. It is time to split this mirror so we have two
identical copies of our system. To make sure you don't loose any data this should be done only when all your
applications are stopped.
# lvsplit -s bkp /dev/vg00/lv*
Logical volume "/dev/vg00/lvol1bkp" has been successfully created with
character device "/dev/vg00/rlvol1bkp".
Logical volume "/dev/vg00/lvol1" has been successfully split.
--(text cut)-Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
With this we have split every logical volume to the original and copy with 'bkp' sufix. For example, lvol1 and
lvol1bkp, lvol2 and lvol2bkp, and so on. In case of a problem after patching we will use 'bkp' logical volumes.
After splitting, new logical volumes (ones with the 'bkp' suffix) needs to be checked with the fsck for consistency.
# for i in /dev/vg00/lv*bkp; do fsck -F $(fstyp $i) $i; done
log replay in progress
replay complete - marking super-block as CLEAN
unknown_fstyp (no matches)
fsck: invalid argument to "-F FStype" option
fsck: /dev/vg00/lvol2bkp is not a valid file system type
usage: fsck [-F FStype] [-V] [-m] [special...]
or fsck [-F FStype] [-V] [-m] [-o specific_options] [special...]
log replay in progress
replay complete - marking super-block as CLEAN
--(text cut)-Do not worry about that error we got there. It is because we tried to fsck SWAP filesystem.
Create new FSTAB

To save time in case of a problem, it is best to create a copy of /etc/fstab file. All you need to do is to rename all
volumes in vg00 to new names with 'bkp' suffix. You can also mount /dev/vg00/lvol3bkp (bkp / filesystem) and copy
this file to this LV too.
# cat /etc/fstab.new
IBM Work Intruction
- 82 -
/dev/vg00/lvol3bkp
/dev/vg00/lvol1bkp
/dev/vg00/lvol4bkp
/dev/vg00/lvol5bkp
/dev/vg00/lvol6bkp
/dev/vg00/lvol7bkp
/dev/vg00/lvol8bkp
/ vxfs delaylog 0 1
/stand hfs defaults 0 1
/tmp vxfs delaylog 0 2
/home vxfs delaylog 0 2
/opt vxfs delaylog 0 2
/usr vxfs delaylog 0 2
/var vxfs delaylog 0 2
# mount /dev/vg00/lvol3bkp /mnt

# cp /etc/fstab.new /mnt/etc
Perform patching
Before executing the patch installation it is recommended to check again output of 'lvlnboot -v' command and to run
preview of patch installation (-p option with swinstall command).
# lvlnboot -v
Root: lvol3
on:
/dev/dsk/c0t4d0
Swap: lvol2
on:
/dev/dsk/c0t4d0
Dump: lvol2
on:
/dev/dsk/c0t4d0, 0
# swinstall -p -i -s /var/patches/depot/GOLDQPK11i_B.11.11.0612.459.depot
Execute the installation of patches.
# swinstall -i -s /var/patches/depot/GOLDQPK11i_B.11.11.0612.459.depot
And finally, reboot the system.
# shutdown -r -y 0
Booting from alternate boot device
Booting into LV maintenance mode

So, patching went wrong? Do not despair; we created a copy of our system before patching so it is easy to go back
to the old version. First we need to boot into LV maintenance mode. We do that by interrupting our system during
the boot (pressing any key), booting from alternate disc and choosing the option to interact with IPL (Initial Program
Loader).
Firmware Version
39.32
Duplex Console IO Dependent Code (IODC) revision 1

-----------------------------------------------------------------------------(c) Copyright 1996-1999, Hewlett-Packard Company, All rights reserved
-----------------------------------------------------------------------------Processor Speed
--------------180 MHz
Coprocessor State
----------------Functional
Cache Size
---------64 KB
Model: A180/1
Available memory (bytes)
134217728
IBM Work Intruction

Primary boot path:
Alternate boot path:
Console path:
- 83 8/16/5.4
8/16/5.6
8/16/4.0
(dec)
(dec)
(dec)
Processor is booting from first available device.

To discontinue, press any key within 10 seconds.
Boot terminated.
------- Main Menu -------------------------------------------------------------
-------
Command
------BOot [PRI|ALT|<path>]
PAth [PRI|ALT|CON] [<path>]
SEArch [DIsplay|IPL] [<path>]
Description
----------Boot from specified path
Display or modify a path
Search for boot devices
COnfiguration [<command>]
INformation [<command>]
SERvice [<command>]
Access Configuration menu/commands

Access Information menu/commands
Access Service menu/commands
DIsplay
HElp [<menu>|<command>]
RESET
Redisplay the current menu

Display help for menu or command
Restart the system
Main Menu: Enter command > sea

Searching for potential boot device(s)...
This may take several minutes.
To discontinue search, press any key (termination may not be immediate).
Path Number
----------P0
P1
P2
Device Path (dec)

----------------8/16/5.6
8/16/5.4
8/0/20/0.0
Device Type
----------Random access media
Random access media
LAN Module
Main Menu: Enter command > bo alt

Interact with IPL (Y, N, or Cancel)?> y
Booting...
Boot IO Dependent Code (IODC) revision 144
SOFT Booted.
ISL Revision A.00.43
Apr 12, 2000
ISL>
When you see 'ISL>' prompt it means that you are in Initial System Loader which will enable you to boot the system
into single user mode or logical volume maintenance mode. In this case we will use LV maintenance mode. This is
done by entering 'hpux -lm'.
ISL> hpux -lm
Boot
: disk(8/16/5.6.0.0.0.0.0;0)/stand/vmunix
IBM Work Intruction
- 84 -
Activating VG
We need to activate /dev/vg00 volume group in order to change boot information. Also, we need to mount /usr
filesystem as we will need commands that reside on it.
# vgchange -a y /dev/vg00
Activated volume group
Volume group "/dev/vg00" has been successfully changed.
# mount /dev/vg00/lvol7bkp /usr
Configuring the system with the new boot information

Remember the copy of /etc/fstab we created earlier, well time has come to use it. Coppy it over the existing
/etc/fstab.
# cp /etc/fstab /etc/fstab.old
# cp /etc/fstab.new /etc/fstab
Instruct the system to use new logical volumes (the ones with the 'bkp' suffix) during the boot.
# lvrmboot -r /dev/vg00
# lvlnboot -r /dev/vg00/lvol3bkp
lvlnboot: WARNING !! Creating a separate root volume, Use the -b option to the
lvlnboot command to create a separate boot e
# lvlnboot -s /dev/vg00/lvol2bkp
# lvlnboot -d /dev/vg00/lvol2bkp
IBM Work Intruction
- 85 -
Check new configuration

Mount all filesystems in order to check if there are some problems.
# rm /etc/mnttab
# mount -aQ
Now, check with 'bdf' command that new logical volumes are used and with 'lvlnboot -v' that they will also be used
during the next boot.
# bdf
Filesystem
kbytes
used
/dev/root
204800
88616
/dev/vg00/lvol8bkp 774144 242384
/dev/vg00/lvol6bkp 2633728 1731632
/dev/vg00/lvol5bkp
20480
2312
/dev/vg00/lvol4bkp 204800
2408
/dev/vg00/lvol1bkp 295024
22576
/dev/vg00/lvol7bkp 1294336 934272
avail %used Mounted on

115352
43% /
527664
31% /var
895112
66% /opt
18032
11% /home
200816
1% /tmp
242944
9% /stand
357264
72% /usr
# lvlnboot -v
Root: lvol3bkp on:
/dev/ddk/c0t6d0
Swap: lvol2bkp on:
/dev/dsk/c0t6d0
Dump: lvol2bkp on:
/dev/dsk/c0t6d0, 0
Reboot
Finally, reboot the system.

# reboot -q
Boot from the alt PV

You should again inerupt the system during the reboot and instruct it to boot from the alternate device. No
interaction with the PLU is needed.
Main Menu: Enter command > bo alt
Interact with IPL (Y, N, or Cancel)?> n
Conclusion
And that's all. Now you should have usable system that looks the same as your system before reboot.
Kernel Parameter Changes

Scheduler and memory load control tunable parameters
IBM Work Intruction
- 86 -
MAXUPROC
Purpose: Specifies the maximum number of processes per user ID.
Values: Default: 40; Range: 1 to 131072
Display: lsattr -E -l sys0 -a maxuproc
Change: chdev -l sys0 -a maxuproc=NewValue
Change takes effect immediately and is preserved over boot. If value is reduced, then it goes into effect only after a
system boot.
Diagnosis: Users cannot fork any additional processes.
Tuning: This is a safeguard to prevent users from creating too many processes.
NCARGS
Purpose: Specifies the maximum allowable size of the ARG/ENV list (in 4 KB blocks) when running exec()
subroutines.
Display: lsattr -E -l sys0 -a ncargs
Change: chdev -l sys0 -a ncargs=NewValue
Change takes effect immediately and is preserved over boot.
Diagnosis: Users cannot execute any additional processes because the argument list passed to the exec() system
call is too long. A low default value might cause some programs to fail with the arg list too long error message, in
which case you might try increasing the ncargs value with the chdev command above and then rerunning the
program.
Tuning: This is a mechanism to prevent the exec() subroutines from failing if the argument list is too long. Please
note that tuning to a higher ncargs value puts additional constraints on system memory resources.
Synchronous I/O tunable parameters

MAXBUF
Purpose: Number of (4 KB) pages in the block-I/O buffer cache.
Display: lsattr -E -l sys0 -a maxbuf
Change: chdev -l sys0 -a maxbuf=NewValue
Change is effective immediately and is permanent. If the -T flag is used, the change is immediate and lasts until the
next boot. If the -P flag is used, the change is deferred until the next boot and is permanent.
Diagnosis: If the sar b command shows breads or bwrites with %rcache and %wcache being low, you might want
to tune this parameter.
Tuning: This parameter normally has little performance effect on systems, where ordinary I/O does not use the
block-I/O buffer cache.
MAXPOUT
Purpose: Specifies the maximum number of pending I/Os to a file.
Values: Default: 0 (no checking); Range: 0 to n (n should be a multiple of 4, plus 1)
Display: lsattr -E -l sys0 -a maxpout
Change: chdev -l sys0 -a maxpout=NewValue Change is effective immediately and is permanent. If the -T flag is
used, the change is immediate and lasts until the next boot. If the -P flag is used, the change is deferred until the
next boot and is permanent.
Diagnosis: If the foreground response time sometimes deteriorates when programs with large amounts of
sequential disk output are running, sequential output may need to be paced.
Tuning: Set maxpout to 33 and minpout to 16. If sequential performance deteriorates unacceptably, increase one or
both. If foreground performance is still unacceptable, decrease both.
MINPOUT
Purpose: Specifies the point at which programs that have reached maxpout can resume writing to the file.
Values: Default: 0 (no checking); Range: 0 to n (n should be a multiple of 4 and should be at least 4 less than
maxpout)
Display: lsattr -E -l sys0 -a minpout
Change: chdev -l sys0 -a minpout=NewValue Change is effective immediately and is permanent. If the -T flag is
used, the change is immediate and lasts until the next boot. If the -P flag is used, the change is deferred until the
next boot and is permanent.
IBM Work Intruction
- 87 -
Diagnosis: If the foreground response time sometimes deteriorates when programs with large amounts of
sequential disk output are running, sequential output may need to be paced.
Tuning: Set maxpout to 33 and minpout to 16. If sequential performance deteriorates unacceptably, increase one or
both. If foreground performance is still unacceptable, decrease both.
MOUNT O NOINTEGRITY
Purpose: A new mount option (nointegrity) may enhance local file system performance for certain write-intensive
applications. This optimization basically eliminates writes to the JFS log. Note that the enhanced performance is
achieved at the expense of metadata integrity. Therefore, use this option with extreme caution because a system
crash can make a file system mounted with this option unrecoverable. Nevertheless, certain classes of applications
do not require file data to remain consistent after a system crash, and these may benefit from using the nointegrity
option. Two examples in which a nointegrity file system may be beneficial is for compiler temporary files, and for
doing a nonmigration or mksysb installation.
Paging Space Size

Purpose: The amount of disk space required to hold pages of working storage.
Values: Default: configuration-dependent; Range: 32 MB to n MB for hd6, 16 MB to n MB for non-hd6
Display: lsps -a mkps or chps or smitty pgsp
Change: Change is effective immediately and is permanent. Paging space is not necessarily put into use
immediately, however.
Diagnosis: Run: lsps -a. If processes have been killed for lack of paging space, monitor the situation with the
psdanger() subroutine.
Tuning: If it appears that there is not enough paging space to handle the normal workload, add a new paging space
on another physical volume or make the existing paging spaces larger.
SYNCD <Interval>
Purpose: The time between sync() calls by syncd.
Values: Default: 60; Range: 1 to any positive integer
Display: grep syncd /sbin/rc.boot vi /sbin/rc.boot or
Change: Change is effective at next boot and is permanent. An alternate method is to use the kill command to
terminate the syncd daemon and restart it from the command line with the command /usr/sbin/syncd interval.
Diagnosis: I/O to a file is blocked when syncd is running.
Tuning: At its default level, this parameter has little performance cost. No change is recommended. Significant
reductions in the syncd interval in the interests of data integrity (as for HACMP) could have adverse performance
consequences.
Asynchronous I/O tunable parameters

MAXREGS
Purpose: Specifies the maximum number of asynchronous I/O requests that can be outstanding at any one time.
Values: Default: 4096; Range: 1 to AIO_MAX (/usr/include/sys/limits.h)
Display: lsattr -E -l aio0 -a maxreqs
Change: chdev -l aio0 -a maxreqs=NewValue Change is effective after reboot and is permanent.
Diagnosis: N/A
Tuning: This includes requests that are in progress, as well as those that are waiting to be started. The maximum
number of asynchronous I/O requests cannot be less than the value of AIO_MAX, as defined in the
/usr/include/sys/limits.h file, but can be greater. It would be appropriate for a system with a high volume of
asynchronous I/O to have a maximum number of asynchronous I/O requests larger than AIO_MAX.
MAXSERVERS
Purpose: Specifies the maximum number of AIO kprocs per processor.
Values: Default: 10 per processor
Change: chdev -l aio0 -a maxservers=NewValue Change is effective after reboot and is permanent.
Diagnosis: N/A
Tuning: This value limits the number of concurrent asynchronous I/O requests. The value should be about the same
as the expected number of concurrent AIO requests.
IBM Work Intruction
- 88 -
MINSERVERS
Purpose: Specifies the number of AIO kprocs that will be created when the AIO kernel extension is loaded.
Values: Default: 1
Change: chdev -l aio0 -a minservers=NewValue Change is effective after reboot and is permanent.
Diagnosis: N/A
Tuning: Making this a large number is not recommended, because each process takes up some memory. Leaving
this number small is acceptable in most cases because AIO will create additional kprocs up to maxservers as
needed.
Disk and disk adapter tunable parameters

Disk Adapter Outstanding-Requests Limit
Num_cmd_elems
Purpose: Maximum number of requests that can be outstanding on a SCSI bus. (Applies only to the SCSI-2
Fast/Wide Adapter.)
Display: lsattr -E -l scsin -a num_cmd_elems
Change: chdev -l scsin -a num_cmd_elems=NewValueChange is effective immediately and is permanent. If the -T
flag is used, the change is immediate and lasts until the next boot. If the -P flag is used, the change is deferred until
the next boot and is permanent.
Diagnosis: Applications performing large writes to striped raw logical volumes are not obtaining the desired
throughput rate.
Tuning: Value should equal the number of physical drives (including those in disk arrays) on the SCSI bus, times
the queue depth of the individual drives.
Disk Drive Queue Depth

q_type
Purpose: Maximum number of requests the disk device can hold in its queue.
Values: Default: For IBM disks=3; Non-IBM disks=0; Range: specified by manufacturer
Display: lsattr -E -l hdiskn
Change: chdev -l hdiskn -a q_type=simple -a queue_depth=NewValueChange is effective immediately and is
permanent. If the -T flag is used, the change is immediate and lasts until the next boot. If the -P flag is used, the
change is deferred until the next boot and is permanent.
Diagnosis: N/A
Tuning: If the non-IBM disk drive is capable of request-queuing, make this change to ensure that the operating
system takes advantage of the capability.
LINUX Hardening and Installation

Linux Hardening
/etc/login.defs
PASS_MAX_DAYS 30
PASS_MIN_DAYS 0
PASS_MIN_LEN 8
PASS_WARN_AGE 8
edit /etc/default/useradd
change INACTIVE=-1 to 14
vi /etc/pam.d/system-auth
add following line
password required pam_unix.so remember=3 use_authtok md5 shadow
auth required pam_tally.so deny=5
password required /lib/security/$ISA/pam_cracklib.so retry=3 minlen=8 dcredit=0 ucredit=0 lcredit=0 ocredit=0
type=
IBM Work Intruction
- 89 -
vi /etc/security/opasswd
chmod 0600 /etc/security/opasswd
vi /etc/sysctl.conf
net.ipv4.tcp_syncookies =1
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.conf.all.accept_redirects = 0
sysctl -p
echo 1 >/proc/sys/net/ipv4/tcp_syncookies
echo 1 >/proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
echo 0 >/proc/sys/net/ipv4/conf/all/accept_redirects
cd /root
chattr +a .bash_history
chattr +i .bash_history
Edit /etc/ssh/sshd_config to disable direct root logins at the SSH level .
PermitRootLogin no
check
lsof -i -n | egrep 'COMMAND|LISTEN|UDP'
nmap -sTU localhost
stop unnessesory services and make it off on all the runlevel such as
nfs portmap nfslock cups anacron xinetd
atd
The default runlevel should be set to 3 since X11 (X Windows System) should not be running on a production
server
# grep ':initdefault' /etc/inittab
id:3:initdefault
To have changes in /etc/inittab become effective immediately, you can run:
# init q
Chmod 600 /etc/inittab
Disable sftp if it's not needed:
#Subsystem
sftp /usr/lib/misc/sftp-server
edit sshd_config
Edit /etc/motd
copy
#############################################################################
Welcome
#############################################################################
This is an official computer system and is the property of Vodafone Essar Ltd. and / or its affiliates. It is for
authorized users only. Unauthorized users are prohibited. Users (authorized or unauthorized) have no explicit or
implicit expectation of privacy. Any or all uses of this system may be subject to one or more of the following actions:
interception, monitoring, recording, auditing, inspection and disclosing to security personnel and law enforcement
personnel, as well as authorized officials of other agencies, both domestic and foreign. By using this system, the
user consents to these actions. Unauthorized or improper use of this system may result in administrative
disciplinary action and civil and criminal penalties. By accessing this system you indicate your awareness of and
IBM Work Intruction
- 90 -
consent to these terms and conditions of use. Discontinue access immediately if you do not agree to the conditions
stated in this notice.
#############################################################################
edit /etc/vsftpd/vsftpd.conf
change anonymous_enable=YES to NO
Run following command
chmod 777 /tmp
Chmod +t /tmp
service xinetd stop
service portmap stop
service nfs stop
service nfslock stop
service cups stop
chkconfig xinetd off
chkconfig nfs off
chkconfig nfslock off
chkconfig cups off
chkconfig portmap off
IBM Work Intruction
Linux Operating System Installation
- 91 -
IBM Work Intruction
- 92 -
1) Insert the first installation CD into the CD drive and turn on or reset the system.
2) The system boots from the CD and displays a screen of instructions with a boot: prompt at the bottom
Select linux instead of askmethod or simply press enter.

3) Choose a language and select OK.
3) Choose a language and select OK.
IBM Work Intruction
4) Select a keyboard and select OK.

.
5) Set up an CD-ROM installation method and select OK
- 93 -
IBM Work Intruction
- 94 -
IBM Work Intruction

6) Youll see the first installation screen.
Click Next.
7) Enter Installation Number.
- 95 -
IBM Work Intruction
8) Select remove Linux portions on selected drive and create default layout.
Check Review And Modify Partitioning Layout.
- 96 -
IBM Work Intruction
- 97 -
9) Choose Yes
10) Create LVM and change partitions as per requirement. Make any desired changes to default layout.
IBM Work Intruction
11) Click next
- 98 -
IBM Work Intruction
- 99 -
12) Configure IP and Hostname to the network , assign it manually.
13) Set the time zone for your system. Keep the System Clock Uses UTC option active. Then click Next.
IBM Work Intruction
14) Type in and confirm the root password for your system.
- 100 -
IBM Work Intruction
15) Select customize now
- 101 -
IBM Work Intruction
16) Select the package groups as per requirement.
17) You get one last chance to go back before starting the installation process.
- 102 -
IBM Work Intruction

Click next if youre happy with your choices, or click Back to make changes.
18) The next step is to reboot your computer into RHEL. Click Reboot.
- 103 -
IBM Work Intruction
LPAR Creation
- 104 -
IBM Work Intruction
- 105 -
Log on to the HMC of the Frame that is hosting the Managed System on which you wish to create an LPAR, using the
hscroot user id.
(https://10.77.41.48:/preloginmonitor/index.jsp)
Go to the Tasks Section, Configuration, Create Logical Partition.
Select AIX or Linux.
Below is the set of screenshots that would follow.
Enter the Partition name which should be similar in name to the hostname of the LPAR.
IBM Work Intruction
- 106 -
IBM Work Intruction
- 107 -
Assign processor units to the LPAR.

Dedicated, for Dedicated Use or from the Shared Processor Pool if the partition would be using processors from the
Shared pool.
IBM Work Intruction
Assign the No. of Processor Units.
- 108 -
IBM Work Intruction
- 109 -
Assign Memory Resources to the Partition.

NOTE: The Desired Memory Tab would be the Actual Physical Processors that the partition would be using.
If the LPAR finds anything less than whats specified in the The Minimum Memory Tab, it would fail to Activate.
The Partition would use Memory upto the Maximum Memory Setting , if at all it finds memory Resources in the free pool,
depending upon the Uncapped Weight.(would be applicable only for Shared Partitions.)
IBM Work Intruction
- 110 -
Assign IO Resources to the LPAR.

NOTE:
To activate the partition, a minimum of 1 SCSI/RAID Controller would be required.
Additionally, an Ethernet Controller, a 4GB PCI-X Dual Port FC Adapter would be required in multiples, depending on the
Partition Requirement.
Add them as Required Resources or else in case another LPAR has these Resources added as Desired Resources in its
Profile as Desired too, the Partition that gets Activated first would take the Resources and would not let the other Partition
Activate.
Resources like a CDROM Controller, should be added as a Desired Resource, especially in P595 Frames because there
would be just 1 CDROM Controller for the 8 LPARs that it hosts.
IBM Work Intruction
- 111 -
Select the Enable Connection Monitoring & Redundant Error Path Reporting Tabs which would enable the Manage
Serviceable Events in the Service Management Section of the HMC to be populated with Hardware errors that the
Server would encounter in the future.
Select the Boot Mode to be Normal unless you plan to boot the Server in SMS/Maintenance Mode.
IBM Work Intruction
This is the final Screen that would appear showing the profile Summary/Configuration.
- 112 -
IBM Work Intruction
- 113 -
Click Finish and Activate the Partition in the Normal Mode.

NOTE - The First time you activate the Partition, enable it in SMS mode & Select the Appropriate Boot Mode and the Boot
device.
Remote IPL to boot through the Network/NIM & select the network adapter, that has been configured in the Profile of
the LPAR.
CDROM to boot using the Base OS CD
Once OS installation is complete, set the Date/Time, Accept Software License Agreements, Set the root password and
Select the Terminal type /vt100.
IBM Work Intruction
New Space Requirement on UNIX Servers
- 114 -
IBM Work Intruction
- 115 -
Steps
request.
2. Check following
a. HBA are configured at operating system level.
b. Are fiber connectivity completed between server, switch.
c. Is required free space is available on storage.
3. Pass the request to Storage team with detailed requirement.
4. Post confirmation from storage team about new devices addition.
a. Scan server for newly added devices.
b. Create different volume groups as per requirement from application team.
c. Create required logical volume in newly created VG.
d. Create file system on logical volumes created.
e. Create requested mount points & mount the filesystems.
f. Assign ownership of requested user to respective mount points.
5. Send the confirmation mail to requestor & close ticket in Remedy.
Post Completion tasks

Provide the details of all VGs to be backed up for DG configuration.
Update backup team with details of mount points & schedule for backup.
IBM Work Intruction
- 116 -
SEC Audit Report Generation

Steps
1. Copy the secaudit.tar file in tmp dir
2. tar xvf secaudit.tar /tmp
3. cd /tmp/secaudit/secaudit_unix/
4. /secaudit_local CUSTOMER=VEL ENCRYPT=no
5. Secaudit file output hostname.sec
Server Startup and Shutdown

Prerequisites
o
Request from user, application owner or from system administrator.
o
o
o
If request from user or application owner then verify why shutdown is necessary?
Do they have valid reason? Check shut down is required or not?
Do they have valid approval from circles IT Head, Application Owner, Manager UNIX Team.
If request from Server admin Team .Take approval from Circles IT Head , Application Owner , Manager
Unix Team, User .Justify why shutdown is required .
IBM Work Intruction
- 117 -
Shutting Down Server Work Instructions

1. Request Application/DBA Team to Stop Application /Database.
Command to Check Database
#ps ef | grep pmon (aix)
#ps ef | grep smon (hp)
Command to Check application like java, websphere, actuate running or not.
# ps ef | grep java
2. Verify all application/Database is stopped.
3. Verify any other application is running.
4. List services running on server.
For aix
# lssrc a | grep active
# netstat an | egrep i listen established
5. Take df (AIX).bdf (hp), cat /etc/filesystems (aix), cat /etc/fstab (hp/linux) output and netstat rn out put, date
output.
# netstat rn
# date
6. Take prtconf (aix.solaris), parstatus (hp) output.
7. Check any mount point is there which will set not to start automatically on restart.
8. Take mksysb (aix) or ignite (hp) backup of OS.
9. Verify any user is connected to the system.
To check user logged in
#w
If any user is logged in issue message by using command wall
# wall System will shut down in 5 minutes. Kindly save all your work and logoff
10. Verify for any dependant cross-platform jobs (If not a regular shutdown)
11. If server is BCV server then unmount all BCV mount points using unmount script.
12. If AIX,
Shutdown F -- to shutdown the system
Shutdown Fr -- to restart the system
13. If Solaris/Linux,
Init 0 --- to shutdown the system
Init 6 --- to restart the system
For HP UX
Shutdown now --- to shutdown the system
Shutdown ry now
--- to restart the system
Starting Up Server Work Instructions

1.
2.
3.
4.
5.
6.
7.
8.
Power on the system.

Power on the external devices (if any)
Check the key positions of the system (if any)
Once the system started, check all the services are started. If they are not part of rc scripts, start the
services manually.
Check system date, netstat rn output ,ping response to gateway and network.
Verify all mount points are mounted with previously captured df or bdf output. Mount manually mountpoints
which are not mounted.
For BCV server run mount script.
Verify all the required services are started
IBM Work Intruction
- 118 -
Service Request Closure

Work Instructions
Service Request: - Service Request is been logged by a end user by logging into remedy tool
http://10.77.131.108/shared/login.jsp?/home , This is a dedicated tool for raising any request; basically service
request can be of 4 types.
1.
2.
3.
4.
Service Request
Severity 1
Severity 2
Severity 3
Once the Service request is been raised it can be seen on to the remedy tool, for which an admin has to login to the
remedy by putting his user name and password.
IBM Work Intruction
- 119 -
This is main management console admin has to click on Incident Management console, which will take the admin
to Personalized Incident Management console.
Here admin needs to select his group and he can list all the tickets which have been assigned to his group or to him
individually, Once ticket is been identified he can double click on that ticket to get the generic details.
IBM Work Intruction
- 120 -
Ticket has got different tabs in a single window which contains all the information about the Incident, As the
administrator works on the incident closure he can close the ticket.
For ticket closure admin has to give resolution details in the below mentioned fields and select appropriate reason
for closure.
IBM Work Intruction
- 121 -
Once the reason has been selected then revolvers name should be entered in the Assignee field and for successful
closure of the ticket this resolution window needs to be saved.
IBM Work Intruction
- 122 -
SUN Solaris Server Patching

First, be sure the patch cluster has been unzipped if the cluster was received as a .zip file, then proceed as follows:
Decide on which method you wish to install the cluster:

Recommended Method Using Save Feature:
By default, the cluster installation procedure uses the patchadd save feature to save the original objects being
patched. Prior to installing the patches the cluster installation script will first determine if enough system disk space
is available in /var/sadm/patch to save the objects and will terminate if not. Using the default save feature is
recommended.
Method Using No Save Option:
It is possible to override the save feature by using the [-nosave] option when executing the cluster installation script.
Using the nosave option means that you will not be able to backout individual patches if the need arises.
Run the install_cluster script

cd <patch cluster directory>
./install_cluster
By default, a message warning the user to check for minimum disk space allowance (separate from the save
feature) will appear and allow the user to abort if inadequate space exists. To suppress this interactive message
the "-q" (quiet) option can be used when invoking install_cluster. The progress of the script will be displayed on your
terminal. It should look something like:
# ./install_cluster
Patch cluster install script for <cluster name>
Determining if sufficient save space exists...
Sufficient save space exists, continuing...
Installing patches located in <patch cluster directory>
Installing <patch-id>
.
.
.
For more installation messages refer to the installation logfile:
/var/sadm/install_data/<cluster name>_log
Use '/usr/bin/showrev -p' to verify installed patch-ids. Refer to individual patch README files for more patch detail.
Rebooting the system is usually necessary after installation.
#
Check the logfile if more detail is needed.

If errors are encountered during the installation of this cluster, error messages will be displayed during installation.
More details about the causes of failure can be found in the detail logfile:
more /var/sadm/install_data/<cluster name>_log
If this log file previously existed the latest cluster installation data will be concatenated to the file, so check the end
of the file.
IBM Work Intruction
Reboot the System
- 123 -
IBM Work Intruction
Mirroring of ROOT File System
- 124 -
IBM Work Intruction
- 125 -
Work Instructions
Create a physical volume using pvcreate with the -B option.
# pvcreate -B /dev/rdsk/c0t5d0
Add the physical volume to your existing root volume group with vgextend:
# vgextend /dev/vg00 /dev/dsk/c0t5d0
Use mkboot to place boot utilities in the boot area:
# mkboot -l /dev/rdsk/c0t5d0
Use mkboot to add an AUTO file in boot LIF area:
# mkboot -a "hpux" /dev/rdsk/c0t5d0
Or, use the -lq option to allow your system to boot in the event that one of your disks is unavailable, resulting in a
loss of quorum.
# mkboot -a "hpux -lq" /dev/rdsk/c0t5d0
NOTE: Use the -lq option when your root volume group contains only 2 disks. If more than 2 disks are in the root
volume group, the -lq option is not needed as quorum will be maintained even if 1 disk fails.
You can check the contents of the AUTO file with
# lifcp /dev/rdsk/c0t5d0:AUTO If you choose, you can set the alternate boot path variable according to e.g.
# setboot -a 8/0/19/0.5.0
You can determine the hardware address of the disk that will become the mirror disk with 'ioscan -fnC' disk. To
check use setboot without any arguments.
Mirror the boot logical volume, primary swap logical volume, root logical volume and other logical volumes as
needed, to the above disk in the following sequence
# lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c0t5d0
# lvextend -m 1 (additional LV)
To check use lvdisplay -v.
Update all physical volumes in the volume group so that the logical volume becomes the root, boot, primary swap,
or a dump volume when the system is next booted:
For HP-UX 10.20 (not updated to) and 11.X only:
# lvlnboot -r /dev/vg00/lvol3
# lvlnboot -b /dev/vg00/lvol1
# lvlnboot -s /dev/vg00/lvol2
IBM Work Intruction

# lvlnboot -d /dev/vg00/lvol2
# lvlnboot -v
- 126 -
IBM Work Intruction
- 127 -
In order to test your mirror configuration, shut down the system and boot from the mirror disk.
# shutdown -ry 0
The system will shut down and reboot. As the system starts to come back up, look for the message (system's
output may vary):
TO INTERRUPT THE BOOT SEQUENCE, PRESS ...
Interrupt the boot sequence. This will display the Boot Admin display. At the boot_admin> prompt type:
bo Mirror_disk_hardware_address or
bo alt
if the alternate boot device has been configured. The system will prompt to interact with IPL, answer 'no', and the
system will boot from the mirror root disk.
NOTE: This example includes creating a mirror copy of the primary swap logical volume. The primary swap
mirror does not need to be on a specific disk or at a specific location, but it does need to be allocated on
contiguous disk space. The recommended mirror policy for primary swap is to have the Mirror Write Cache
and the Mirror Consistency Recovery Mechanisms disabled.
When primary swap is mirrored and your primary swap device also serves as a dump area, you must make
sure that Mirror Write Cache and Mirror Consistency Recovery is set to off at boot time to avoid loss of
your dump. To reset these options, you will need to reboot your system in maintenance mode. Then use
the lvchange(1M) command with the -M n and -c n options.
IBM Work Intruction
USER ID Management
- 128 -
IBM Work Intruction
- 129 -
User Addition
This command is used for adding users in a UNIX system
This is accomplished with the command useradd in all the flavors of UNIX (HP-UX, AIX and Solaris)
Command syntax:useradd (username)
Ex -: useradd test will add one user in the system with the name test
There are different switches associated with this command mentioned below
-g group :- Specifies the integer group ID or character string name of an existing group. This defines the primary
group membership of the new login.
-G group: - Specifies the integer group ID or character string name of an existing group. This defines the
supplemental group memberships of the new login
-d dir :-
Specifies the home directory of the new login
-m:- Creates the home directory for the new login if it does not exist
For example to create a user test which primary group sys and secondary group other, home directory as
/home/test and creating the home directory as well while adding user, the syntax is
useradd test g root G other d /home/test m
User deletion
This command is used for deleting users in a UNIX system
This is accomplished with the command userdel in all the flavors of UNIX (HP-UX, AIX and Solaris)
Command syntax:userdel (username)
Ex -: userdel test will delete the user test in the system
There are different switches associated with this command mentioned below
-r
The home directory of login is removed from the system
For example to remove user test along with the contents of its home directory as well, the syntax is
userdel r test
IBM Work Intruction
- 130 -
User Modification
This command is used for modifying an existing user in a UNIX system
This is accomplished with the command usermod in all the flavors of UNIX (HP-UX, AIX and Solaris)
Command syntax:usermod parameter (username)
The different parameters that are modified are mentioned below
-o :- Allows the UID to be non-unique (i.e., duplicate)
-g :-redefines the new primary group membership for the log in specified
-G :- redefines the new secondary group membership for the log in specified
-d dir:- specifies the new home directory for the log in
-e expire :- Specifies the date on which this login can no longer be used.
For example to modify an existing user test primary group to root , secondary group to mail , making its uid non
unique , changing its home directory as /home/test1 and expiry date as 7/14/2008 , the syntax is
usermod o g root G mail d /home/test1 e 7/14/2008 test
Unlocking a user on the system (HP-UX)

In HP-UX systems, the user can be unlocked with the command modprpw
The syntax for the command is
modprpw k (username)
For example for enabling user test that is disabled on the system , the syntax is
modprpw k test
For unlocking user in Solaris and AIX passwd (username) command is being used.
Changing password for a user

This command is used for modifying an existing user password in a UNIX system
This is accomplished with the command passwd in all the flavors of UNIX (HP-UX, AIX and Solaris)
Command syntax:passwd (username)
The system then prompts for a new password
For example for changing the password for user test, the syntax is
passwd test
IBM Work Intruction
- 131 -
Adding groups in a system

This command is used for adding groups in a UNIX system
This is accomplished with the command groupadd in all the flavors of UNIX (HP-UX, AIX and Solaris)
Command syntax:groupadd (group name)
For example for adding group staff in a UNIX system, the command syntax is
groupadd staff
Deleting group in a system

This command is used for deleting groups in a UNIX system
This is accomplished with the command groupdel in all the flavors of UNIX (HP-UX, AIX and Solaris)
Command syntax:groupdel (group name)
For example for deleting group staff in a UNIX system, the command syntax is
groupdel staff
Modifying group in a system

This command is used for modifying groups in a UNIX system
This is accomplished with the command groupmod in all the flavors of UNIX (HP-UX, AIX and Solaris)
Command syntax:groupmod parameter (group name)
The parameters that can be modified are -:
-g gid :- Change the value of the group ID to gid.
-o
:- Allow the gid to be non-unique
-n name :- Change the name of the group to name
IBM Work Intruction
- 132 -
USER ID Creation
Prerequisites
o
o
o
o
o
o
o
o
o
Check proper approval from UNIX Team Manager, Application manager if user is application user is
available.
Request him to fill User Request Form containing details like user id name, home folder, default group,
permission required i.e. read/write/execute, cron, ftp access. IP of server,
User description.
Verify information given in User Request Form is complete or not. Proper approval is available or not.
If any information is missing, tell user to provide it and take fresh approval from its manager.
If it is privilege ID request make sure that proper approval is available
If security approval is not there please dont create privilege ID.
Admin should maintain a record of (user id, name of owner, employee id, access rights etc) when he
creates id, which would help in reducing the collection work which he does,
when a request comes for data.
Make sure you are maintaining the artifact for id creation.
User creation in AIX/ HP-UX/ LINUX/ SOLARIS

Login as a root
Use Command
# useradd -g <primary group> -md <home directory> <username>
# passwd <user name>
# pwdadm c test
Using smitty in AIX
# smitty user
for aix only
IBM Work Intruction
- 133 -
Select add user and press enter
Enter user name , select primary group pressing function key F4 ,enter home directory.
Press enter.
After creating user through smitty it will show command status OK .Press function key F3 it will go back to main
menu .
Select change users password and enter
Enter user name. Press enter it will prompt for password enter password .
IBM Work Intruction
- 134 -
Press F10 to exit smitty screen .

Type command on cmmand line
# pwdadm c test
For cron access add user in /var/adm/cron/cron.allow
FTP access is given by default to every user .We can deny this by adding user in /etc/ftpuser file.
User creation in HP-UX using SAM

Type command SAM on command line
# SAM
Enter highlighted menu for creating user account .
IBM Work Intruction
- 135 -
Select menu users and enter .
press tab key

go to action
menu .select
Add menu and
press enter.
Enter user
name ,home
directory,
default shell
,default group .
Select ok to
confirm . You
can select
fields by
pressing tab
key .
You can select
primary group
by highlighting
primary group
name field.
IBM Work Intruction
Select required primary group and press OK .
After confirming user addition system will give system generated password
Type command passwd on command line to change user password
# passwd testuser
- 136 -
IBM Work Intruction
- 137 -
Enter p to change user password and enter new password.
Server Health Check

CPU: Check for CPU usage (%)
Execute following command to check CPU utilization
sar Mu 2 10
Disk: To check disk usage & utilization

To check disk usage use following command
df k
To check disk I/O utilization use following command
sar d 2 10
iostat 2 10
File related parameters: To check if parameters are adequate

To check this use following command
sar v 2 10
To check memory status

To check physical & virtual memory utilization us following command
vmstat 2 10
swapinfo tam
IBM Work Intruction
To check top resource utilizing processes

To check this use top command
top d3 s10 f <file name>
-f switch is to be used only if output is to be captured in file
To check memory segment usages by users & size

To check memory segment usage by users & size use following command
ipcs ma
To check system date & time

To check system date & time use following command
date
- 138 -
IBM Work Intruction
HP-UX Cluster Restarts
- 139 -
IBM Work Intruction
- 140 -
Work Instructions
we need to make sure AUTO_RUN is disabled in cmviewcl.
cmmodpkg -d pkgname ------ this disables the pkg AUTO_RUN
ie.,
PACKAGE
gjsdpkg0
STATUS
up
STATE
running
AUTO_RUN NODE
disabled
gjsdp0
Steps for cluster Down & up :perform these steps from MP Console for the host (pls verify host first by netstat -in)
Capture all the seesion o/p.
#bdf
#cmviewcl
you will know the node name & pkg name by this.
Before rebooting the host :cmhaltpkg -v pkg_name
cmhaltnode -v Nodename
*******************
After reboot :cmrunnode -v Nodename
cmrunpkg -v pkg_name
vgchange -a y VG_name
vgchange -a e VG_name
fsck /dev/vg_name/lvol1
mount /dev/vg_name/lvol1 /mount_point
xntpd -x
exportfs -a
Note >> Please moniter the log file in another session when performing these steps.logs path is :cd /etc/cmcluser/pkgname
cat pkgname.log
Capture all the seesion o/p.
verify all the mount points before releasing.
----------------------------------------------------------------------------------------------------------For example :cmhaltpkg -v appkg0
cmhaltnode -v sd128bp0
*******************
cmrunnode -v sd128bp0
cmrunpkg -v appkg0
vgchange -a y
VG_name
vgchange -a e VG_name
fsck /dev/mumbscs02/lvol1
mount /dev/mumbscs02/lvol1
xntpd x
/mumbcsc02
IBM Work Intruction
- 141 -
Solaris Solstice Work Instructions

metastat -p
format
clear
syminq |grep 044C
format
clear
format
format
format
clear
prtvtoc -s /dev/rdsk/c4t19d57s2 | fmthard -s - /dev/rdsk/c4t19d58s2
format
clear
df -k
metainit -p
metastat -p
metainit d10 4 1 /dev/dsk/c4t19d57s4 1 /dev/dsk/c4t19d58s4 1 /dev/dsk/c4t
/dev/dsk/c4t19d60s4
metastat -p
newfs /dev/md/rdsk/d10
df -k /data44
df -k /data45
df -k|grep /data45
mkdir /data45
ls -lrt /data45
df -k /data46
df -k |grep /data46
mkdir /data46
mount /dev/md/rdsk/d10 /data46
mount /dev/md/dsk/d10 /data46
df -k |grep /data46
df -k /data45
cd /data45
ls -lrt
cd /data44
19d59s4 1
IBM Work Intruction
SUN Solaris New Disk Creation

FORMAT MENU:
disk
- select a disk
type
- select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label
- write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save
- save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> save
Please name this partition type before saving it
format> p
PARTITION MENU:
0
- change `0' partition
1
2
3
4
5
6
7
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
quit
partition> quit
- 142 -
IBM Work Intruction
- 143 -
FORMAT MENU:
disk
- select a disk
type
label
save
quit
format> save
format> p
PARTITION MENU:
0
1
2
3
4
5
6
7
quit
partition> p
Current partition table (unnamed):
Total disk cylinders available: 37178 + 2 (reserved cylinders)
Part
Tag Flag Cylinders
Size
Blocks
0
root wm
0 - 68
129.38MB (69/0/0)
264960
1
swap wu
69 - 137
129.38MB (69/0/0)
264960
2 backup wu
0 - 37177
68.07GB (37178/0/0) 142763520
3 unassigned wm
0
0
(0/0/0)
0
4 unassigned wm
0
0
(0/0/0)
0
5 unassigned wm
0
0
(0/0/0)
0
6
usr wm 138 - 37177
67.82GB (37040/0/0) 142233600
7 unassigned wm
0
0
(0/0/0)
0
partition> 6
Part
Tag Flag Cylinders
6
usr wm 138 - 37177
Enter partition id tag[usr]: new_disk
`new_disk' not expected.
Enter partition id tag[usr]: newdisk
`newdisk' not expected.
Size
67.82GB
Blocks
(37040/0/0) 142233600
IBM Work Intruction

Enter partition id tag[usr]: 6
`6' not expected.
Enter partition id tag[usr]: ?
Expecting one of the following: (abbreviations ok):
unassigned boot
root
swap
usr
backup
stand
var
home
alternates
Enter partition id tag[usr]: unassigned
Enter partition permission flags[wm]:
Enter new starting cyl[138]:
Enter partition size[142233600b, 37040c, 69450.00mb, 67.82gb]:
partition> label newdisk
Ready to label disk, continue? newdisk
`newdisk' is not expected.
partition> label
Ready to label disk, continue? y
partition> save
`save' is not expected.
partition> q
FORMAT MENU:
disk
- select a disk
type
label
save
quit
format> save
format> save name
format> label
Ready to label disk, continue?
Ready to label disk, continue? y
format> save
format> ls
`ls' is not expected.
format> ?
Expecting one of the following: (abbreviations ok):
disk
- select a disk
type
label
- 144 -
IBM Work Intruction

save
quit
format> p
PARTITION MENU:
0
1
2
3
4
5
6
7
quit
partition> name
Enter table name (remember quotes): "new_disk"
partition> q
FORMAT MENU:
disk
- select a disk
type
label
save
quit
format> save
Saving new disk and partition definitions
Enter file name["./format.dat"]: /etc/format.dat
format> q
root@ebp-hyd # cd /
root@ebp-hyd # newfs /dev/rdsk/c2t16d247s2
newfs: construct a new file system /dev/rdsk/c2t16d247s2: (y/n)? y
/dev/rdsk/c2t16d247s2: 142763520 sectors in 37178 cylinders of 60 tracks, 64 sectors
69708.8MB in 1377 cyl groups (27 c/g, 50.62MB/g, 6272 i/g)
- 145 -
IBM Work Intruction

super-block backups (for fsck -F ufs -o b=#) at:
32, 103776, 207520, 311264, 415008, 518752, 622496, 726240, 829984, 933728,
1037472, 1141216, 1244960, 1348704, 1452448, 1556192, 1659936, 1763680,
1867424, 1971168, 2074912, 2178656, 2282400, 2386144, 2489888, 2593632,
2697376, 2801120, 2904864, 3008608, 3112352, 3216096, 3319840, 3423584,
3527328, 3631072, 3734816, 3838560, 3942304, 4046048, 4149792, 4253536,
4357280, 4461024, 4564768, 4668512, 4772256, 4876000, 4979744, 5083488,
5187232, 5290976, 5394720, 5498464, 5602208, 5705952, 5809696, 5913440,
6017184, 6120928, 6224672, 6328416, 6432160, 6535904, 6635552, 6739296,
6843040, 6946784, 7050528, 7154272, 7258016, 7361760, 7465504, 7569248,
7672992, 7776736, 7880480, 7984224, 8087968, 8191712, 8295456, 8399200,
8502944, 8606688, 8710432, 8814176, 8917920, 9021664, 9125408, 9229152,
9332896, 9436640, 9540384, 9644128, 9747872, 9851616, 9955360, 10059104,
10162848, 10266592, 10370336, 10474080, 10577824, 10681568, 10785312,
10889056, 10992800, 11096544, 11200288, 11304032, 11407776, 11511520,
11615264, 11719008, 11822752, 11926496, 12030240, 12133984, 12237728,
12341472, 12445216, 12548960, 12652704, 12756448, 12860192, 12963936,
13067680, 13171424, 13271072, 13374816, 13478560, 13582304, 13686048,
13789792, 13893536, 13997280, 14101024, 14204768, 14308512, 14412256,
14516000, 14619744, 14723488, 14827232, 14930976, 15034720, 15138464,
15242208, 15345952, 15449696, 15553440, 15657184, 15760928, 15864672,
15968416, 16072160, 16175904, 16279648, 16383392, 16487136, 16590880,
16694624, 16798368, 16902112, 17005856, 17109600, 17213344, 17317088,
17420832, 17524576, 17628320, 17732064, 17835808, 17939552, 18043296,
18147040, 18250784, 18354528, 18458272, 18562016, 18665760, 18769504,
18873248, 18976992, 19080736, 19184480, 19288224, 19391968, 19495712,
19599456, 19703200, 19806944, 19906592, 20010336, 20114080, 20217824,
20321568, 20425312, 20529056, 20632800, 20736544, 20840288, 20944032,
21047776, 21151520, 21255264, 21359008, 21462752, 21566496, 21670240,
21773984, 21877728, 21981472, 22085216, 22188960, 22292704, 22396448,
22500192, 22603936, 22707680, 22811424, 22915168, 23018912, 23122656,
23226400, 23330144, 23433888, 23537632, 23641376, 23745120, 23848864,
23952608, 24056352, 24160096, 24263840, 24367584, 24471328, 24575072,
24678816, 24782560, 24886304, 24990048, 25093792, 25197536, 25301280,
25405024, 25508768, 25612512, 25716256, 25820000, 25923744, 26027488,
26131232, 26234976, 26338720, 26442464, 26542112, 26645856, 26749600,
26853344, 26957088, 27060832, 27164576, 27268320, 27372064, 27475808,
27579552, 27683296, 27787040, 27890784, 27994528, 28098272, 28202016,
28305760, 28409504, 28513248, 28616992, 28720736, 28824480, 28928224,
29031968, 29135712, 29239456, 29343200, 29446944, 29550688, 29654432,
29758176, 29861920, 29965664, 30069408, 30173152, 30276896, 30380640,
30484384, 30588128, 30691872, 30795616, 30899360, 31003104, 31106848,
31210592, 31314336, 31418080, 31521824, 31625568, 31729312, 31833056,
31936800, 32040544, 32144288, 32248032, 32351776, 32455520, 32559264,
32663008, 32766752, 32870496, 32974240, 33077984, 33177632, 33281376,
33385120, 33488864, 33592608, 33696352, 33800096, 33903840, 34007584,
34111328, 34215072, 34318816, 34422560, 34526304, 34630048, 34733792,
34837536, 34941280, 35045024, 35148768, 35252512, 35356256, 35460000,
35563744, 35667488, 35771232, 35874976, 35978720, 36082464, 36186208,
36289952, 36393696, 36497440, 36601184, 36704928, 36808672, 36912416,
37016160, 37119904, 37223648, 37327392, 37431136, 37534880, 37638624,
37742368, 37846112, 37949856, 38053600, 38157344, 38261088, 38364832,
38468576, 38572320, 38676064, 38779808, 38883552, 38987296, 39091040,
39194784, 39298528, 39402272, 39506016, 39609760, 39713504, 39813152,
39916896, 40020640, 40124384, 40228128, 40331872, 40435616, 40539360,
40643104, 40746848, 40850592, 40954336, 41058080, 41161824, 41265568,
41369312, 41473056, 41576800, 41680544, 41784288, 41888032, 41991776,
42095520, 42199264, 42303008, 42406752, 42510496, 42614240, 42717984,
42821728, 42925472, 43029216, 43132960, 43236704, 43340448, 43444192,
43547936, 43651680, 43755424, 43859168, 43962912, 44066656, 44170400,
44274144, 44377888, 44481632, 44585376, 44689120, 44792864, 44896608,
45000352, 45104096, 45207840, 45311584, 45415328, 45519072, 45622816,
- 146 -
IBM Work Intruction

45726560, 45830304, 45934048, 46037792, 46141536, 46245280, 46349024,
46448672, 46552416, 46656160, 46759904, 46863648, 46967392, 47071136,
47174880, 47278624, 47382368, 47486112, 47589856, 47693600, 47797344,
47901088, 48004832, 48108576, 48212320, 48316064, 48419808, 48523552,
48627296, 48731040, 48834784, 48938528, 49042272, 49146016, 49249760,
49353504, 49457248, 49560992, 49664736, 49768480, 49872224, 49975968,
50079712, 50183456, 50287200, 50390944, 50494688, 50598432, 50702176,
50805920, 50909664, 51013408, 51117152, 51220896, 51324640, 51428384,
51532128, 51635872, 51739616, 51843360, 51947104, 52050848, 52154592,
52258336, 52362080, 52465824, 52569568, 52673312, 52777056, 52880800,
52984544, 53084192, 53187936, 53291680, 53395424, 53499168, 53602912,
53706656, 53810400, 53914144, 54017888, 54121632, 54225376, 54329120,
54432864, 54536608, 54640352, 54744096, 54847840, 54951584, 55055328,
55159072, 55262816, 55366560, 55470304, 55574048, 55677792, 55781536,
55885280, 55989024, 56092768, 56196512, 56300256, 56404000, 56507744,
56611488, 56715232, 56818976, 56922720, 57026464, 57130208, 57233952,
57337696, 57441440, 57545184, 57648928, 57752672, 57856416, 57960160,
58063904, 58167648, 58271392, 58375136, 58478880, 58582624, 58686368,
58790112, 58893856, 58997600, 59101344, 59205088, 59308832, 59412576,
59516320, 59620064, 59719712, 59823456, 59927200, 60030944, 60134688,
60238432, 60342176, 60445920, 60549664, 60653408, 60757152, 60860896,
60964640, 61068384, 61172128, 61275872, 61379616, 61483360, 61587104,
61690848, 61794592, 61898336, 62002080, 62105824, 62209568, 62313312,
62417056, 62520800, 62624544, 62728288, 62832032, 62935776, 63039520,
63143264, 63247008, 63350752, 63454496, 63558240, 63661984, 63765728,
63869472, 63973216, 64076960, 64180704, 64284448, 64388192, 64491936,
64595680, 64699424, 64803168, 64906912, 65010656, 65114400, 65218144,
65321888, 65425632, 65529376, 65633120, 65736864, 65840608, 65944352,
66048096, 66151840, 66255584, 66355232, 66458976, 66562720, 66666464,
66770208, 66873952, 66977696, 67081440, 67185184, 67288928, 67392672,
67496416, 67600160, 67703904, 67807648, 67911392, 68015136, 68118880,
68222624, 68326368, 68430112, 68533856, 68637600, 68741344, 68845088,
68948832, 69052576, 69156320, 69260064, 69363808, 69467552, 69571296,
69675040, 69778784, 69882528, 69986272, 70090016, 70193760, 70297504,
70401248, 70504992, 70608736, 70712480, 70816224, 70919968, 71023712,
71127456, 71231200, 71334944, 71438688, 71542432, 71646176, 71749920,
71853664, 71957408, 72061152, 72164896, 72268640, 72372384, 72476128,
72579872, 72683616, 72787360, 72891104, 72990752, 73094496, 73198240,
73301984, 73405728, 73509472, 73613216, 73716960, 73820704, 73924448,
74028192, 74131936, 74235680, 74339424, 74443168, 74546912, 74650656,
74754400, 74858144, 74961888, 75065632, 75169376, 75273120, 75376864,
75480608, 75584352, 75688096, 75791840, 75895584, 75999328, 76103072,
76206816, 76310560, 76414304, 76518048, 76621792, 76725536, 76829280,
76933024, 77036768, 77140512, 77244256, 77348000, 77451744, 77555488,
77659232, 77762976, 77866720, 77970464, 78074208, 78177952, 78281696,
78385440, 78489184, 78592928, 78696672, 78800416, 78904160, 79007904,
79111648, 79215392, 79319136, 79422880, 79526624, 79626272, 79730016,
79833760, 79937504, 80041248, 80144992, 80248736, 80352480, 80456224,
80559968, 80663712, 80767456, 80871200, 80974944, 81078688, 81182432,
81286176, 81389920, 81493664, 81597408, 81701152, 81804896, 81908640,
82012384, 82116128, 82219872, 82323616, 82427360, 82531104, 82634848,
82738592, 82842336, 82946080, 83049824, 83153568, 83257312, 83361056,
83464800, 83568544, 83672288, 83776032, 83879776, 83983520, 84087264,
84191008, 84294752, 84398496, 84502240, 84605984, 84709728, 84813472,
84917216, 85020960, 85124704, 85228448, 85332192, 85435936, 85539680,
85643424, 85747168, 85850912, 85954656, 86058400, 86162144, 86261792,
86365536, 86469280, 86573024, 86676768, 86780512, 86884256, 86988000,
87091744, 87195488, 87299232, 87402976, 87506720, 87610464, 87714208,
87817952, 87921696, 88025440, 88129184, 88232928, 88336672, 88440416,
88544160, 88647904, 88751648, 88855392, 88959136, 89062880, 89166624,
89270368, 89374112, 89477856, 89581600, 89685344, 89789088, 89892832,
89996576, 90100320, 90204064, 90307808, 90411552, 90515296, 90619040,
- 147 -
IBM Work Intruction

90722784, 90826528, 90930272, 91034016, 91137760, 91241504, 91345248,
91448992, 91552736, 91656480, 91760224, 91863968, 91967712, 92071456,
92175200, 92278944, 92382688, 92486432, 92590176, 92693920, 92797664,
92897312, 93001056, 93104800, 93208544, 93312288, 93416032, 93519776,
93623520, 93727264, 93831008, 93934752, 94038496, 94142240, 94245984,
94349728, 94453472, 94557216, 94660960, 94764704, 94868448, 94972192,
95075936, 95179680, 95283424, 95387168, 95490912, 95594656, 95698400,
95802144, 95905888, 96009632, 96113376, 96217120, 96320864, 96424608,
96528352, 96632096, 96735840, 96839584, 96943328, 97047072, 97150816,
97254560, 97358304, 97462048, 97565792, 97669536, 97773280, 97877024,
97980768, 98084512, 98188256, 98292000, 98395744, 98499488, 98603232,
98706976, 98810720, 98914464, 99018208, 99121952, 99225696, 99329440,
99433184, 99532832, 99636576, 99740320, 99844064, 99947808, 100051552,
100155296, 100259040, 100362784, 100466528, 100570272, 100674016, 100777760,
100881504, 100985248, 101088992, 101192736, 101296480, 101400224, 101503968,
101607712, 101711456, 101815200, 101918944, 102022688, 102126432, 102230176,
102333920, 102437664, 102541408, 102645152, 102748896, 102852640, 102956384,
103060128, 103163872, 103267616, 103371360, 103475104, 103578848, 103682592,
103786336, 103890080, 103993824, 104097568, 104201312, 104305056, 104408800,
104512544, 104616288, 104720032, 104823776, 104927520, 105031264, 105135008,
105238752, 105342496, 105446240, 105549984, 105653728, 105757472, 105861216,
105964960, 106068704, 106168352, 106272096, 106375840, 106479584, 106583328,
106687072, 106790816, 106894560, 106998304, 107102048, 107205792, 107309536,
107413280, 107517024, 107620768, 107724512, 107828256, 107932000, 108035744,
108139488, 108243232, 108346976, 108450720, 108554464, 108658208, 108761952,
108865696, 108969440, 109073184, 109176928, 109280672, 109384416, 109488160,
109591904, 109695648, 109799392, 109903136, 110006880, 110110624, 110214368,
110318112, 110421856, 110525600, 110629344, 110733088, 110836832, 110940576,
111044320, 111148064, 111251808, 111355552, 111459296, 111563040, 111666784,
111770528, 111874272, 111978016, 112081760, 112185504, 112289248, 112392992,
112496736, 112600480, 112704224, 112803872, 112907616, 113011360, 113115104,
113218848, 113322592, 113426336, 113530080, 113633824, 113737568, 113841312,
113945056, 114048800, 114152544, 114256288, 114360032, 114463776, 114567520,
114671264, 114775008, 114878752, 114982496, 115086240, 115189984, 115293728,
115397472, 115501216, 115604960, 115708704, 115812448, 115916192, 116019936,
116123680, 116227424, 116331168, 116434912, 116538656, 116642400, 116746144,
116849888, 116953632, 117057376, 117161120, 117264864, 117368608, 117472352,
117576096, 117679840, 117783584, 117887328, 117991072, 118094816, 118198560,
118302304, 118406048, 118509792, 118613536, 118717280, 118821024, 118924768,
119028512, 119132256, 119236000, 119339744, 119439392, 119543136, 119646880,
119750624, 119854368, 119958112, 120061856, 120165600, 120269344, 120373088,
120476832, 120580576, 120684320, 120788064, 120891808, 120995552, 121099296,
121203040, 121306784, 121410528, 121514272, 121618016, 121721760, 121825504,
121929248, 122032992, 122136736, 122240480, 122344224, 122447968, 122551712,
122655456, 122759200, 122862944, 122966688, 123070432, 123174176, 123277920,
123381664, 123485408, 123589152, 123692896, 123796640, 123900384, 124004128,
124107872, 124211616, 124315360, 124419104, 124522848, 124626592, 124730336,
124834080, 124937824, 125041568, 125145312, 125249056, 125352800, 125456544,
125560288, 125664032, 125767776, 125871520, 125975264, 126074912, 126178656,
126282400, 126386144, 126489888, 126593632, 126697376, 126801120, 126904864,
127008608, 127112352, 127216096, 127319840, 127423584, 127527328, 127631072,
127734816, 127838560, 127942304, 128046048, 128149792, 128253536, 128357280,
128461024, 128564768, 128668512, 128772256, 128876000, 128979744, 129083488,
129187232, 129290976, 129394720, 129498464, 129602208, 129705952, 129809696,
129913440, 130017184, 130120928, 130224672, 130328416, 130432160, 130535904,
130639648, 130743392, 130847136, 130950880, 131054624, 131158368, 131262112,
131365856, 131469600, 131573344, 131677088, 131780832, 131884576, 131988320,
132092064, 132195808, 132299552, 132403296, 132507040, 132610784, 132710432,
132814176, 132917920, 133021664, 133125408, 133229152, 133332896, 133436640,
133540384, 133644128, 133747872, 133851616, 133955360, 134059104, 134162848,
134266592, 134370336, 134474080, 134577824, 134681568, 134785312, 134889056,
134992800, 135096544, 135200288, 135304032, 135407776, 135511520, 135615264,
- 148 -
IBM Work Intruction

135719008, 135822752, 135926496, 136030240, 136133984, 136237728, 136341472,
136445216, 136548960, 136652704, 136756448, 136860192, 136963936, 137067680,
137171424, 137275168, 137378912, 137482656, 137586400, 137690144, 137793888,
137897632, 138001376, 138105120, 138208864, 138312608, 138416352, 138520096,
138623840, 138727584, 138831328, 138935072, 139038816, 139142560, 139246304,
139345952, 139449696, 139553440, 139657184, 139760928, 139864672, 139968416,
140072160, 140175904, 140279648, 140383392, 140487136, 140590880, 140694624,
140798368, 140902112, 141005856, 141109600, 141213344, 141317088, 141420832,
141524576, 141628320, 141732064, 141835808, 141939552, 142043296, 142147040,
142250784, 142354528, 142458272, 142562016, 142665760,
root@ebp-hyd # fsck /dev/rdsk/c2t16d247s2
** /dev/rdsk/c2t16d247s2
** Last Mounted on
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
2 files, 9 used, 70280113 free (9 frags, 8785013 blocks, 0.0% fragmentation)
- 149 -
IBM Work Intruction
- 150 -
SUN Solaris Operating System Backup (UFSDUMP)

Condition 1:
If /var /usr and /opt is mounted separately then the command for backup is:
ufsdump 0uf /dev/rmt/0n /
ufsdump 0uf /dev/rmt/0n /usr
ufsdump 0uf /dev/rmt/0n /var
ufsdump 0uf /dev/rmt/0n /opt
The above mentioned steps are only if there are many filesystems mounted separately i.e / (root) , /var , /usr etc.
Condition 2:
If var usr and opt is inside the root then backup command is :
ufsdump 0uf /dev/rmt/0 /
Veritas File System Creation

Vxdisksetup i c#t#d# format=sliced
Vxdg g ofpdatdg adddisk ofpdatd24=c0t1d0
vxassist -g ofpdatdg maxsize
Vxassist g ofpdatdg make datavol10 1g(*size of vol*) layout=stripe diskname???
vxdg -g ofpdatdg free
Mkfs F vxfs o largefiles,bsize=8192 /dev/vx/rdsk/ofpdatdg/datavol10
cd /
mkdir /ofp/data10
mount -F vxfs /dev/vx/dsk/ofpdatdg/datavol10 /ofp/data10
********************
Vxdg init ofpdatadg disk01=c$t$d$ if creating new vg ....N/A in this case
**************************
disk
dgname
datadis03 datadg1 c1t1d0s2
datadis04 datadg1 c1t2d0s2
vxdg init datadg1 datadis03=c1t1d0 cds=off
Vxdg g datadg1 adddisk datadis03=c1t1d0
root@appstest # vxassist -g datadg1 maxsize
IBM Work Intruction

vxassist g datadg1 make datavol1 69400m layout=stripe stwidth=32
datadis06
datadg1 c4t16d148
vxdisksetup i c4t16d148 format=sliced
vxdg init datadg1 datadis06=c4t16d148 cds=off
Vxdg g datadg1 adddisk datadis03=c1t1d0
root@appstest # vxassist -g datadg1 maxsize
vxassist g datadg1 make datavol1 69400m layout=stripe stwidth=32
- 151 -
IBM Work Intruction
Vendor Call Log Details
- 152 -
IBM Work Intruction
HP
Mail ID ( Monday to Firday - hpi.rc@hp.com only for official time 10:00 AM to 5:30 PM)
Mail id Night disk - nightdesk.bangalore@hp.com time 5:30 PM to 7:00 AM
Including Saturday and Sunday
Toll Free Number - 800-425-8080 1800-425-4994 / 18004258080 Cell 9844152008
+ 91 080 2563 3555 ( Transfer to CMG )
IBM
Mail ID -- rccindia@in.ibm.com (24* 7 support )
Toll Free Numbers - : 1800 425 6666
Toll Free Fax No : 1800 425 1133
Alternate STD No : 080 26788940/ 970
Sun
( this is use for only AMC server )
Mail id - escare@wipro.com this is for only Monday to Saturday 9;00 AM to 6:00 PM
Toll Free Number 18002003456/18003453456 All days ( 24*7 )
For New server / within warranty servers
Mail id - sun-service-request-info@Sun.COM /apen-support@Sun.COM
Toll Free Number 18004254786
NOTE : For login call below details should be provide

1.
2.
3.
4.
5.
System Serial Number

Server model number
contact person
details address
problem description
Dept . Code / Project Code ( for IBM Only)
- 153 -
IBM Work Intruction
- 154 -
Appendix
OS Hardening and
SA&D Checklist for
Security Health Check
UNIX
Server Provisioning
for UNIX
WI Server Health
Check for UNIX

Solaris

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Solaris

Uploaded by

Copyright:

Available Formats

IBM Work Intruction

UNIX Work Instructions

IBM Work Intruction

IBM AIX Activities...................................................................................................................................... 5

IBM Work Intruction

Finding OS, Hostname, Version of OS, OS Level Patch, Model Details....................................................43

IBM Work Intruction

User deletion............................................................................................................................................ 128

IBM Work Intruction

IBM AIX Activities

IBM Work Intruction

File System Creation

#Creating a Volume Group using a PV/hdisk2

#mklv -t jfs2 -y datavglvol1 datavg 40

#Creating a Logical Volume datavglvol1 of size 40 PPs

Creates a LV datavglvol1 of size 10GB (40*256MB)

Mirroring a root disk

For a Symmetrix LUN

IBM Work Intruction

For an IBM DS LUN,

Kernel parameter Changes

/Virtual Memory Parameters

Tuning Scheduler/Memory Load Control Tunable parameters

IBM Work Intruction

Paging Space Size

Specifies that the paging space is configured at subsequent restarts.

To increase or decrease the size of the paging space,

IBM Work Intruction

Move cursor to desired item and press Enter.

To check the No. of Physical Processors currently Available,

IBM Work Intruction

To check is multithreading is enabled,

System configuration: lcpu=28 ent=7.00 mode=Uncapped

%wio %idle physc %entc

To Check Internal SCSI disk drives on the Server

To Check EMC powerpath disks

IBM Work Intruction

Back Up the System

NOTE: If an internal tape drive is not available on the System,

IBM Work Intruction

// the Server whose mksysb is to be taken

PPs PVs LV STATE

IBM Work Intruction

> /tmp/cfgbkp.outVOLUME GROUP:

(c) Take a snap output backup

935378 Jan 30 18:40 snap.pax.Z

IBM Work Intruction

(d) Take a backup of all critical files to /tmp;

IBM Work Intruction

To change the Network media Speed

After successfully changing the media speed,

#Assuming the Network on which the IP is configured is en0

Your Cable Type

After this is done,

IBM Work Intruction

Check for the ssh version

Post patch installation,

To check the WWPN of the Fiber card,

To check the firmware level of the filber card,

IBM Work Intruction

To analyse the Server error log report

IBM Work Intruction