This action might not be possible to undo. Are you sure you want to continue?
1. OS INSTALLATION 2. BOOT PROCESS 3. MOUNT THE CDROM 4. SOFTWARE MAINTENACE 5. FILESET INSTALLATION 6. LIST THE INSTALLED FILE SETS 7. LIST THE FILESET CONTENTS 8. VERIFY THE FILESET INSTALLTION 9. COMMIT THE INSTALLED FILESET 10. REJECT THE APPLIED FILESET 11. REMOVE THE COMMITTED FILESET 12. FIX APAR INSTALLATION 13. DEVICE MANAGEMENT 14. ADD NEW DEVICE 15. LIST DEV 16. LIST CONFIGURATION 17. CFGMGR, MKDEV 18. ADD PV TO SYSTEM 19. LIST PV 13 VG CREATION 14. E XTEND VG 15. LIST VG 16. LV CREATION 17. LIST LV 18. FILE SYSTEM CREATION 19. INCREASE FILE SYSTEM SIZE IN ONLINE 20. DECREASE FILE SYSTEM SIZE IN ONLINE 21. RENAME LV 22. RENAME FILE SYSTEM 23. MIGRATE PV 24. MAKE LVCOPY 25. REMOVE LV COPY 26. VARRYONVG 27. VARRYOFFVG 28. EXPORTVG 29. IMPORTVG 30. MIRRORVG 31. UNMIRRORVG
32. SYNCVG 33. ODM 34. ODM OBJECT CLASS 35. ODM OBJECTS 36. ADD ODM OBJECT 37. REMOVE ODM OBJECT 38. DELETE ODM OBJECT 39. CHANGE ODM OBJECT 40. PAGING SPACE 41. INCREASE PAGING SPACE 42. DECREASE PAGING SPACE 43. LIST PAGING SPACE 44. AUTO ON PAGING SPACE 45. AUTO OFF PAGING SPACE 46. ACTIVATE THE PAGING SPACE 47. DEACTIVATE THE PAGING SPACE 48. ADD THE NETWORK CARDS 49. ASSIGN IP TO THE NETWORK CARD 50. ASSIGN THE GATEWAY TO THE NETWORK CARD 51. DISABLE THE NETWORK CARD 52. ENABLE THE NETWORK CARD 53. CHECK THE NETWORK STATUS 54. NETWORK FILE SYSTEM(NFS) 55. EXPORTING FILE SYSTEM FROM SERVER 56. IMPORTING FILE SYSTEM TO CLIENT 57. CHECK THE MOUNTED FILE SYSTEM USING /etc/xtab 58. CHECK THE SYSTEM PERFORMANCE PERFORMANCE
1. BASIC AIX HARDWARE 2. OS INSTALLATION 3. BOOT PROCESS 4. SOFTWARE MAINTENANCE 5. FIX MAINTENANCE 6. ODM (Object Data Manager) 7. DEVICE MANAGEMENT 8. LVM (Logical Volume Manager) 9. PAGING SPACE 10. SRC AND DAEMONS 11. NETWORK 12. NFS (Network File System) 13. USER AND GROUP MANAGEMENT 14. SCHEDULING 15. BACKUP AND RESTORE 16. PERFORMANCE MONITORING 17. LPAR /DLPAR
1. BASIC AIX HARDWARE:
The AIX Os is installed in IBM P Series or I Series Servers P Series Servers (32bit and 64 bit Hardware Support) 1. 2. 3. 4. 5. RS6000 P1, P2, P3 ( Very old models) P4 ( Regatta 680, 615, 630, 641, 690(LPAR / DLPAR) P4 +( It will support many no of processors and memory compare than P4) P5 (Squadron P550, P570, P575, P590, P595(Latest) P5 + ( It will support many no of processors and memory compare than P5)
2. OS INSTALLATION:
Three kinds of OS installations available in AIX 1. New and Complete Overwrite 2. Migration 3. Preservation
Start maintenance mode for recovery This is used for recover the existing OS problems.3 . Preservation: This installation is overwriting the existing OS and user data directory /home only persevered.1 To Aix 5. 2. Start maintenance mode for recovery A. in this installation we have three options A. NOTE: In this installation we can preserve additional directories also. NOTE: In this installation System data will not be affected except the /tmp file system. /dev.1. File systems problems).2 To Aix 5. suppose if you want preserve /opt. Start installation with default settings B. C.3 or Aix 5. . Change/show installation settings and install C. /etc. Boot list. this case u should put /opt file system entry in /etc/preserve. Desktop options. New and Complete Overwrite: This is New installation. Operating system Updated from lower level to higher level i. /tmp file system will be deleted and newly created. Aix 5. i. /var. Migration: In this migration Installation.e. (Boot image.list file. /tmp. Start installation with default settings This is normal installation B. /opt will be deleted and newly created. 3. Change/show installation settings and install In this installation we can change the installation disk (hdisk0.e. rest of the directories /. or hdisk1).
Then boot image is moved to memory. Then kernel will execute. When we select the preserve installation. Then it will check the BLV (hd5) in boot device. Ros Kernel init phase (PHASE1) A. 3. BOOT PROCESS Three phases available in BOOT Process 1.list file.e. only /home directory will be preserved. Post (power on self test) In this post it will do basic hardware checking B. 2. Base Device Configuration 3. Here cfgmgr will run for device configuration. and /etc directory also will be deleted. D.Interview Question: 1. Ros kernel init phase 2. Then it will check the boot image E. .list file. if any file system entry is found then it will preserve the file system i. F. Then it will go to NVRAM and check the boot list for last boot device (hdisk0 or hdisk1). Base Device configuration (PHASE2) A. C. Then how additionally preserved directories will not be deleted? Answer: When we start the preservation installation. after that /etc file system also will be deleted and newly created. System boot phase 1. first installation will check ODM for /etc/preserve. What are the file system entries available in the /etc/preserve.
4. 8. /etc/inittab file contains four fields. Identifier. /tmp D. System Boot Phase (PHASE3) A. Action.3. Fileset installation Applying the Fileset Reject the Installed Fileset Commit the applied Fileset Remove the Committed Fileset Verify the Installed Fileset ( whether properly installed or not) Clear the braked Fileset installation List the Installed Fileset List the Installed Fileset contents ( What are the files available in File Set) 10. srcmstr /etc/rc. 3. 4. 5.tcpip. This is default run level.boot. NOTE: Run level 2: It contains all of the terminal process and daemons that are run in the multi user environment. Kernel start the init process. C. 2. Command. 11.net. 7. B. /usr. E. 2. To finding the file.tcpip /etc/rc. SOFTWARE MAINTENANCE In this software Installation we can do following things 1. To find the command file path 12.net The above network related files /etc/rc. /etc/rc. Kernel will execute. Extracted from which Fileset. it will read the /etc/inittab file and execute the following process. 1. /home. Then following file system will be mounted /. The paging space (hd6) will get start. /etc/rc. 3. 9. /var. Then it will start the system by default run level 2. 6. Runlevel 4. To view the fileset history . used to configure the ip address and routing.
perf* . Eg. LPP’s (Licensed program product) CD. Fileset Installation The Filesets has additional support files for AIX. When we mount the CDROM. this topas command is not by default come under AIX OS installation. So we should create the directory. /cdmnt and cdrfs file system.e. Bonus software CD.tool file set. Suppose we need additional files. we required mount point like one directory. Then u go to /cdmnt folder #cd cdmnt #pwd cdmnt # Now topas file will be under bos. So that topas file we have to install from some other CD’s. To find the file set using command #installp –Ld /dev/cd0 | grep bos. /cdmnt (Directory name will be whatever may be) #mkdir mount point #mkdir cdmnt Then u can mount the CDROM drive in cdmnt directory #mount –v cdrfs –o ro /dev/cd0 /mount point #mount –v cdrfs –o ro /dev/cd0 /cdmnt Verify the Cdrom drive mount process. we need topas command. First we should mount the CDROM drive in server. we can install it from Base operating system (bos) CD.1. Now we should find the file set in software cd. #mount The above command will show the cdrom drive mount point i.permaget. Expansion Software CD. NOTE: If we want to check the AIX Server performance.
we can easily reject the updated fileset. paging space usage . When we updating the old fileset to new fileset. Applying Fileset (It is not permanent installation) This applying Fileset is just file set installation. #installp –agxd /dev/cd0 bos.e. memory usage. suppose that updated fileset giving some problem. After commit the fileset this /usr/lpp/package(fileset) will updated .permaget. it will show otherwise it won’t show. If file set is found then we have to install the fileset. 2. If updated fileset is working properly we can commit the updated fileset.permaget. .tool file set is available in cd. we can easily reject(remove) the updated fileset. by default installation has done in apply state and old fileset configuration is moved to /usr/lpp/package(fileset) path. but we can uninstall the fileset. installation has done in apply state.tool (for installation) see difference Options –agxpd for preview -agxd for installation When we type the above command. this case we cannot reject the fileset. and When we updating the fileset. fileset installation will start and topas file extracted from the fileset and it will store to /usr/sbin/topas (super user or administrator commands stored in /usr/sbin) After that we can use topas performance monitor utility. like cpu usage. To install the file set using #installp –agxpd /dev/cd0 file set (for preview installation) i. this first time installation done in commit state. i.e.e. NOTE: Suppose we are installing fileset for the first time. io usage (hdisk’s) network usage. #topas The above command will display the system performance status.If the above bos. permanent installation. Because if any problems in updated fileset. i.
.rte (for preview) Flags: a . suppose that updated filesets are not working properly then we have to remove the updated fileset and pervious filesets are to be configuring to current working condition. Reject the Applied Fileset. 3.rte After Installation.rte Preview (It will show the installation preview – This preview is not required our testing purpose we are using) #installp –agxpd /dev/cd0 fileset name #installp –agxpd /dev/cd0 bos. old installed fileset configuration is moved to /usr//lpp/package (fileset). Now we will reject the updated fileset using #installp –rgp fileset name (For preview) #installp –rg fileset name #installp –rg bos. and updated fileset also available in /usr/lpp/package.command The above command is used to remove the updated fileset and automatically previous fileset is moved to working condition. After updating the fileset that installed fileset is moved to applied state.Apply g – Perquisites (supporting file) x – Expand the space p – Preview d – Specify the device After preview we can install the Fileset #installp –agxd /dev/cd0 bos.rte.For fileset installation using command installp Suppose u want to install one fileset bos.
.rte. we cannot reject.command (For un installation) The above command is used to uninstall the committed fileset.rte. then we have to commit the updated fileset for permanent installation. we have to uninstall the fileset only. 6. then we will confirm fileset is installed properly. Verify the installed fileset (Whether properly installed or not) After installation we want to verify whether filesets are properly installed are not. Remove the Committed fileset (It is complete fileset removal not reject) After commit the fileset. using following command #lppchk –v fileset name #lppchk –v bos. Now we will commit the updated fileset using #installp –cgx fileset name #installp –cgx bos. Commit the Applied fileset (It is permanent installation) After updating the fileset that installed fileset is moved to applied state.command (For preview) #installp –ug bos.command The above command is used to commit the updated fileset. Otherwise we will remove the updated fileset using reject option. 5. suppose applied filesets are working properly. that fileset is moved to permanent installation.rte.command If any problems it will show the error message otherwise no error message.rte. Now we will uninstall the committed fileset using: #installp –ugp Fileset name #installp –ugp bos.4.
9. List the installed fileset content (What are the files available in fileset) Suppose we want to see bos. it won’t show anything. This time half of the fileset only installed in server. Clear the braked fileset installation: While installing the filesets.command file Basically bos.rte.7.command The above command is display the bos.rte. i.command fileset content. Cd is not reading or space is not available in volume group. some problem has occurred.e. so before next installation. using #lslpp –f fileset name #lslpp –f bos.command fileset has user commands So it will show the /usr/bin/ls. List the installed fileset Suppose we want to see what are the filesets available in Server. if file set is not available or not installed. we should remove the half installed fileset using #Installp –C To clean the brokend fileset installation 8.rte. Using #lslpp –l | grep Fileset name The above command is list the specified fileset only. . Using #lslpp –l The above command list the all installed fileset Suppose you want to find particular fileset in server.rte.
toc (table of content) file.rte. we can create the . installed time.command The above command output will be full details of fileset.command fileset name.toc file . The above command is used to create the . Fileset version.e. Using # lslpp –w /usr/bin/ls The above command shows the bos.rte. 11. date NOTE: Whenever we installing the fileset or fix.10. which is installed from which fileset. using #which savevg /usr/sbin/savevg 12.toc file using command #inutoc . because ls command file is extracted from bos. in that current path should have the . If this file is not available we cannot install any fileset or fix from that current path If file is not available.command fileset #lslpp –w /usr/sbin/savevg The above shows some other fileset name.rte. To view the fileset history: Using #lslpp –h fileset name #lslpp –h bos. the above command output will be /usr/bin/ls Suppose we want to savevg path. To find the command file path: Using #which ls The above command is display the given file path i. To find the file.
we should install or update that fix level then only problem will solved. This case of problems we should update the fix. slow performance. 2. Problems like. To verify the installed fix Suppose we want to verify installed fix.Keyword to mention the fix name . FIX MAINTENANCE In this fix update we can do following things 1. To verify the installed fix 3.Device to mention device name The above command is used to install the given fix IK00891 from cdrom drive. if any issues on server. To list the fixes from the CD 1. Using #instfix –ki fixname #instfix –ki IK00891 Option –i for information The above command is used to display the given fix details. . particular application is not working properly. If fix is not available some error message will come.5. Suppose we want to install fix. Fix installation 2. Using #instfix –k Fixname –d device #instfix – k IK00891 –d /dev/cd0 -k -d . Fix Installation Fix is a just like patch.
To list the fix from the CD Suppose we have fix update CD.toc file using command #inutoc . then it will display the given fix name otherwise it wont display anything or some error message will come. we can create the . we want to install particular two fix in server.Displays the entire list of fixes present on the media. Using #instfix –T fixname –d /dev/cd0 #instfix –T IK00891 –d /dev/cd0 T . If fix is available in CD. If this files not available we cannot install any fileset or fix from that current path If file is not available.toc (table of content) file.3. in that current path should have the . NOTE: Whenever we installing the fileset or fix. this first we should find that 2 fixes are available in CD or not available.toc file . The above command is used to create the .
but this ODM information available in many files and different path. 5. 3. 5. selectors. 3. 4. 2. ODM (Object Data Manager) ODM generally used for Maintain the System information. Hardware vital product data information Software information Smit menu Nim TCPIP Error log Device configuration information Display information for SMIT (menus. 2. Customized(CuDv) . If you want to check the variable entry using command #env The above command is used to display the variable details ODM has two kinds of Databases 1. 1.6. 6. /usr/share/lib/objrepos NOTE: For ODM some variable entry available in /etc/environment file.U should not edit anything in this file. 1. But we cannot see any ODM information in file format. that information’s added in ODM. 4. whenever we install and reconfigure the hardware device and software. and dialogs) Vital product data for installation and update procedures Communications configuration information System resource information. /etc/objrepos 2. Pre-defined (PdDv) 2. Mainly ODM used to store the following information’s 1. /usr/lib/objrepos 3.
This case that device is moved to defined state. Defined (device status will be 0) Suppose we are installing one HDD in server. We can see this available and defined device status using odmget command #odmget CuDv ( It will display the customized device status) like this all the devices . CuDv (Object class) Objects: (Installed configuration information’s) Hdisk0 Hdisk1 Fd0 Sa0 Rmt0 Cd0 Scsi0 ODM States: ODM has two states 1. Customized In this customized Database has one Object class (CuDv) and Objects i. Predefined In this predefined Database has one Object class (PdDv) and Objects i. Available (device status will be 1) 2. That device is currently accessible this is available state. that device configuration is available in server but currently device is not accessible. i. 2.e.e. Suppose that installed device is removed from server or hdd has failed. PdDv (Object class) Object: (Physical Information’s) Floppy drive Harddisk drive Mouse like this all the devices.e.1.
odmdrop 3. odmchange The above command is used to change configurations for object in ODM 3.ODM Commands: For object: 1. odmget #odmget –q name=hdisk0 CuDv The above command is used to display the specified object hdisk0 information in ODM We can see this available and defined device status using odmget command #odmget CuDv (It will display the customized device status) 4. odmshow . 2. 4. odmadd odmchange odmget odmdelete 1. 3. odmadd The above command is used to manually we can add object information in ODM 2. odmdelete #odmdelete –o CuDv –q name=hdisk0 The above command is used to delete the specified object hdisk0 in ODMe For object class: 1. odmcreate 2.
Make/Add a Device 2. delete. List Device configuration 1.1. odmdrop The above command is used to stop the specified Object class in ODM 3. change. Remove Device 5. for object and object class in ODM (100 % we don’t have permissions for ODM) 7. this case we should run following command Suppose we want to install new Hard disk #smitty mkdev (not recommended) . DEVICE MANAGEMENT In this device management. 1. Change Device 3. odmshow The above command is used to display the specified object class in ODM NOTE: You should not add. List Device properties 6. we can do following things. odmcreate The above command is used to manually we can add object class (PdDv) in ODM 2. List Device 4. Make/Add a Device We want to install new device in server.
make. The above command is not recommended because first we should know all the details about HDD. etc. in this sort we should fill some details about hard disk drive. we can change this PVID using chdev commands Like this we can change duplex mode for network card and block size for tape media.e. 2. HDD. Change Device Suppose we want to change device configuration. Cdrom. #chdev –l inet0 –a hostname=si (To change the host name for inet0) #chdev –l rmt0 –a block_size=512 (To Change tape drive block_size is 512 blocks) #chdev –l ent0 –a media_speed=100_full_duplex (To Change Ethernet card duplex speed) .After executing the above command. We want to change PVID (Physical volume ID) for Hdd #chdev –l hdisk0 –a pv=clear (To clear the PVID) #chdev –l hdisk0 –a pv=yes (To assign the PVID) Whenever we installing the new hdd. #cfgmgr (It will detect the all the devices) #cfgmgr scsi0 Directly you want to detect hard disk then directly u should check the hdd parent device scsi0 When you run the above command it will detect only Scsi0 devices i. such as model. system will generate some Identification number for hdd. and Tape. this case we should run following command. one sort will come. capacity. Like this we can configure newly installed devices. When we run the cfgmgr command it will detect all the newly installed devices. First you connect hard disk and run the cfgmgr command it will detect the hdd. so instead of that we can use cfgmgr command.
this case se should run following command. List Device Suppose we want to list device configuration details. Remove Device Suppose you want to remove device from server. #lsdev –Cc disk #lsdev –Cc processor #lsdev –Cc adapter #lsdev –Cc memory C – Customized (object class) c – for device (object) If any confusion please refer the ODM notes 4. First you have removed the HDD from server. #lsdev –C (To list the Customized device configuration information from ODM) #lsdev – P (To list the Predefined device configuration information from ODM) The above commands list the object class device information. Then you checking device configuration details using #lsdev –Cc disk Or #odmget CuDv It will show the device status . Suppose it is one HDD.3. Suppose we want to see particular device (object) information. it will list all the device information. Whenever we list the device information that information is listed from ODM because ODM is storing the device information.
List device Properties (attributes) Suppose you want to check the device attributes details. you should use following commands. . you should run the following command #cfgmgr #cfgmgr scsi0 (Directly you can search device on Parent device scsi0) After executing above commands the device hdisk5 become to Available state. And device status is 1 5. this device configuration is available in ODM (not from OS) After executing the above command this hdisk5 configuration is available in ODM and device status is defined #odmget CuDv | grep hdisk5 It will show Hdisk5 configuration details but device status is 0 If you want install hdisk5 device again.There is two options is available in device removal #rmdev –dl hdisk5 The above command is used to remove hdisk5 device from ODM (complete removal from OS) After executing the above command this hdisk5 configuration is not available in ODM #odmget CuDv | grep hdisk5 It wont display anything because device configuration is removed from ODM Suppose you want to remove device from the server not from ODM This case you should use the following command. #rmdev –l hdisk5 The above command is used to remove hdisk5 device from server.
You want to see memory details. Suppose you want to see HDD FRU number #lscfg (it will show full system information) #lscfg –vl hdisk0 (It will show HDD configuration details FRU) #lscfg –vl eth0 (It will so MAC address details of eth0) Like this all the devices. currently connected and configured with server. First you switch on the server. we can activate the tape drive without rebooting the server using #mkdev –l rmt0 (After executing the command tape drive is come to available state) . List device Configuration Suppose you want to check the device configuration details. but tape is now powered on so tape drive is moved to defined state. #lsattr –El mem0 (For memory) #lsattr –El processor0 (For processor) #lsattr –El ent0 (For Ethernet card) #lsattr –El rmt0 (For Tape drive) E – Effective l . it is checking the tape drive. NOTE: #bindprocessor –q (It will show processor information) Suppose you are using backup device. status will be 0. 6.Device Like this all the devices. at this time tape driver is not switched on. you should use following commands. Now tape drive is switched on now we want to activate the tape drive. While booting the server.
After creating the LV using 1GB space we can increase LV size online. Suppose we have 40GB HDD.8. 7.e. this file system is belongs to one particular LV. 2. then 40GB HDD spited into i. Minimum one PV is belongs to VG. 1. 4. 5. Each pp has 32MB. then that 40GB HDD divided into 1024MB *40 = 40960MB Each pp size is 32MB. suppose we are mentioned pp size is 32MB. So you create LV with 315 PP’s. and file systems. that file system size will be 1GB.e. we have added in one VG named DataVG . After that only we can create logical volumes. While creating the VG we should mention the pp size. PP size will be 4MB to 128MB. i. this pp’s pointed to logical portions (LP). then that lv size will be 1GB. So while creating the LV we should mention the lv size is 1GB. LVM (Logical Volume Manager) In AIX first Physical volumes (PV) are added into volume group(VG). 3. 6. This LVM we can do following things. While creating the VG we should mention physical partition (pp) size. List PV Change PV Create VG List VG Extend VG Reduce VG Varryon VG Varryoff VG . reboot is not required. 8. 40960 / 32 = 1280 PP’s So DATAVG has 1280 PP’s While creating the Logical volumes we should mention the lv size by giving the no of pp Suppose you want to create one file system /userdata. but directly we cannot mention the GB size.
Extend LV 12. List Fs 19. Remove LV 16. List LV 11. Repair FS 23.9. Create LV 10. Migrate LV 28. Mirror VG 24. Change VG NOTE: After AIX installation by default root volume group (rootvg) will be available 1. Create FS 17. Unmirror VG 26. Unmount FS 21. Export VG 29. Remove FS 22. Remove LV copy 15. List Physical Volumes Suppose we want to know how many PV’s available in server. Import VG 30. Migrate PV 27. Mount FS 20. Syncvg 25. Create LV copy 14. Change LV 13. The following command is list the Pv’s #lspv Hdisk0 Hdisk1 Hdisk2 # The above command is used to display the pv availability . Change FS 18.
allocatable. used pp’s. hdisk1. Suppose we want to see logical volumes details in single hdisk2 PV Then your command will be #lspv –l hdisk2 The above command is used to display all the LV details across the PV hdisk2 Suppose we want to see pp storage information in hdisk2. hdisk2. Change PV Suppose we have three PV’s. #chpv -vr hdisk2 (To deactivate the hdisk2) #chpv –va hdisk2 (To activate the hdisk2) #chpv –an hdisk2 (hdisk2 is not allocatable) #chpv –ay hdisk2 (hdisk2 is allocatable) #chpv –hn hdisk2 (hotspare no) #chpv –hy hdisk2 (Hotspare yes) #chpv –c hdisk2 (To clear the boot image) Above operations we can do by using chpv command . now you want to deactivate the hdisk2. hotspare etc. free pp.Suppose you want to see particular PV information then your command will be #lspv hdisk1 After executing lspv command it will display the hdisk1 PV information. All the information. then your command will be #lspv –p hdisk2 The above command is display the pp usage information across the PV hdisk2 2. like hdisk0. like pp size.
List VG We can list VG information using following commands #lsvg – It will display the available vg’s #lsvg datavg – It will display full details about datavg only #lsvg –o It will display the online vg’s #lsvg – l datavg – It will display the all logical volume details across the datavg #lsvg –p datavg – It will display the information about all PV’s in datavg Above operations we can do by using lsvg commands 5.3. We can create VG by using mkvg commands #mkvg –s 32 –y datavg hdisk4 The above command is creating datavg using pv hdisk4 and pp size is 32MB #mkvg datavg hdisk4 The above command is creating datavg using pv hdisk4 and pp size is by default 128MB 4. then your command will be #extendvg datavg hdisk6 After executed command hdisk6 pv added with datavg #lsvg –l datavg Hdisk4 Hdisk5 Hdisk6 # . Extend VG We can increase VG size by adding Pv into existing VG using extendvg command #lsvg –p datavg Hdisk4 Hdisk5 # datavg has 2 PV’s now we want to extend datavg. Create VG.
After that we want to activate the VG for further data access Suppose we want to activate testvg. directly it will remove the pv from testvg. Reduce VG We can remove the VG using reducevg command. you have data in pv hdisk9. Suppose 2 PV’s available in testvg then one by one we can reduce the PV’s 7. then your command will be #lsvg Rootvg Datavg Testvg The above command shows what are VG’s available #lsvg –o Rootvg Datavg .6. Suppose we want remove testvg and testvg has one pv hdisk9 #lsvg –p testvg Hdisk9 # Now we will remove the pv from testvg #reducevg –f testvg hdisk9 f. some times clients want to deactivate VG for project restriction. that time I will not any questions. Varryon VG This is just for VG activation.option is used to force reduce.
Datavg – lv created on datavg 5 – 5 PP’s allocated for newlv ( 1 pp size 32MB the newlv size is 32MB*5 = 160MB) Hdisk4 – that newlv is belongs to PV hdisk4 . some clients want to deactivate VG for project Restriction. 8.e. Create LV All the File systems belongs to individual LV. Varryoff VG This is just for VG deactivation. after creating the VG’s we should create the LV using mklv command Suppose you want to create LV name as newlv #mklv –y newlv –t jfs2 datavg 5 hdisk4 -y for confirmation -t type mentioning the filesystem type i. jfs or jfs2.The above commands shows only online VG’s because testvg is offline so we have to activate testvg #varryonvg testvg #lsvg –o Rootvg Datavg Testvg Now above command is display the testvg. Suppose customer want deactivate testvg then your command will be #lsvg –o Rootvg Datavg Testvg #Varryoff testvg #lsvg –o Rootvg Datavg The above command display only two online VG’s and it will not show testvg because testvg is offline VG. 9.
#lslv –m newlv – To display the lvcopy information’s 11. Etc. Extend LV Suppose we want to increase LV size using extendlv command #lslv newlv The above command shows LV size.e.10. label name. suppose LV has 10 LP’s and usage is up to 95% full. List LV Suppose we want see what are the Lv’s available in datavg. then your command will be #lsvg –l datavg It will login list LV details newlv Now we want see newlv properties. Suppose you want to see this changes again use the lslv command #lslv newlv (it will show no of LV’s is 15 and some additional space) . available pp’s mount pint. i. then some additional space will available in newlv. then your command will be #lslv newlv The above command is used to display the newlv properties.e. #extendlv newlv 5 After executing the above command 5 PP’s added with newlv. that time we can increase the LV size online by adding no of LP’s in newlv i. stale partitions. no of LP’s and some other information about LV.
Create LV copy We can create LV content copy to another PV.12. #chlv –n newlvname oldlvname #lslv testlv Output is some details about testlv #chlv –n newlv testlv After executing the above command the testlv renamed to newlv #lslv testlv Some error message will come i. 13. testlv is not found #lslv newlv It will show newlv details. Changing the LV permissions: suppose we want to change LV permissions to read only then the command will be #chlv –p r testlv After executing the above command testlv permissions changed as read only . Change LV In this change LV option we can change LV name and permissions for the LV using chlv command. we can not copy new files into this LV. using After this testlv data available in both PV. hdisk1 and hdisk2. #lspv Hdisk0 Hdisk1 Hdisk2 #lspv –l hdisk1 Assume testlv available in hdisk1. after this same LV content is available in Lvcopy configured PV.e. so we can only read the LV. now we will make testlv copy to hdisk2. because testlv is renamed as newlv. we can recover testlv data from hdisk2 . suppose hdisk1 is fail.
No of copies. . Remove LV copy Using rmlvcopy we can remove the lvcopy from the PV’s Suppose we want to remove testlv copy from hdisk0 #rmlvcopy testlv 3 hdisk0 After executing the above command third copy of the testlv removed from PV hdisk0. like this we can remove 15. directly it will delete the data) After executing the above command testlv removed from the server. Remove LV Suppose we want to LV testlv from server #rmlv testlv (If data is available in testlv It will ask confirmation) #rmlv –f testlv (It won’t ask any confirmation. this case you put 3 and mention hdisk0 then third copy will be available in hdisk0) ##mklvcopy testlv 3 hdisk0 ( It will make third lvcopy on hdisk0 After executing above command testlv is copied to hdisk2 If you want to confirm run the following command #lslv –m testlv (it will show lvcopy details for testlv) Hdiks1 hdisk2 hdisk0 Testlv (copy1) testlv (copy2) testlv (copy3) 14. (we can make 3 copies also.#mklvcopy testlv 2 hdisk2 Testlv –lv name 2.
#crfs –v jfs2 –g testvg –a size=64465 –m /newfs (Directly we can create /fs from VG This case lv name will be lv00 or lv01 like this after that also we can rename the lv name) 17. Create FS Using crfs command we can create a file system. Change FS Using chfs command we can rename and increase the size of the file system online We want to increase file system size #chfs –a size=+block size /filesystem name #chfs –a size=+32m /filesystem name #chfs-a size=+4g /filesystem name +block size – We can mention the size using blocks (2048 blocks = 1MB) +32m – We can mention the size using MB +4g – We can mention the size using GB After increasing the file system size.16. we can verify using commands #df –k #ls –q /newfs Rename the file system using chfs command #lsfs /newfs It will display /newfs details # Now we want to rename /newfs to /testfs then your command will be . File systems belongs to LV’s Whenever we create the file system we should mention the LV name #crfs –v jfs2 –d testlv –m /newfs (Normal creation) The /newfs file system created on testlv.
Mount FS After creating the file system. List Fs We can list file system details using lsfs command #lsfs – List all filesystems in the /etc/filesystems entry #lsfs –q (List all filesystems with detailed info) #lsfs –a (list all filesystems (default) #lsfs –l (specify the output in the list format) #lsfs –c (specify the output in the column format) #lsfs –v jfs (List all jfs filesystems) 19. Before mount lsfs command is wont display the /newfs file system #lsfs –a That /newfs file system detail is not available #mount /newfs Now you put lsfs command it will show the /newfs details #lsfs –a .#chfs –m /testfs /newfs After executing the above command /newfs renamed as /testfs We can auto mount the file system while booting using chfs command #chfs –A /testfs 18. we should mount the file system. without file system mount we cannot access the file system using mount command we can mount the file system.
#lsfs –a 21. #umount /testfs #rmfs /testfs (Deletes FS /newfs and associated LV) After executing the above command /testfs is removed. Remove FS Using rmfs command we can remove the file systems #lsfs –a /testfs Before removing the /testfs. file system is moved to off line. #umount /newfs After this you run the lsfs –a command it wont display /newfs file system details. #rmfs –r /testfs (Deletes FS /newfs its mount point and associated LV) 22. That file system should be unmounted.e. Repair FS Using fsck command we can repair the problematic FS or corrupted FS Suppose you want check /data FS #fsck /data Or directly we can repair the LV #fsck –Y n /dev/datalv (To fsck the FS associated to /dev/datalv assuming response “Yes” #fsck –p /dev/datalv (To restore superblock from backup superblock) .20. Unmount FS Using umount or unmount command we can umount the file system i.
23. Mirror VG We can do mirroring in AIX. Data and OS installed in hdisk0 and now we want to mirror hdisk0 to hdisk1. Then your command will be #mirrorvg –S –m rootvg hdisk1 S – Backgroup mirror -m . Suppose we have two PV’s in rootvg. testlv copy get sync with lv copied PV Suppose we want to sync mirrored PV’s #syncvg –v rootvg The above sync the mirrored PV’s in rootvg 25. 24. Synchronize VG Using Syncvg command we can sync the mirrored Vg and LV copy information’s Suppose we want to sync lvcopy #syncvg –l lvname #syncvg –l testlv After executing the above command. Unmirror VG Using Unmirror command we can Unmirror the VG #unmirrorvg rootvg hdisk1 PV hdisk1 is removed from rootvg mirror . now we want mirror. using mirrorvg command and we can create max.exact (force) mirror NOTE: in mirrored VG quorum should be off line because quorum is not recommended for mirror. Three copy of mirror.
Migrate LV Using migratepv command we can migrate lv from PV to PV Suppose we want to migrate single LV #migratepv –l testlv hdisk1 hdisk2 After executing above command testlv LV is moved hdisk2.e.26. 28. Export VG Using exportvg command we can export VG (including all the PV’s) from one server to another server. DATAVG is moved to offline. #varryoff DATAVG (Varryoff the DATAVG) #exportvg DATAVG (VG information removed from ODM) . Suppose you have ServerA. we should Varryoff the DATAVG. Migrate PV Using migratepv command we can move full PV data or single LV from one PV to another PV. This is not copy just cut and past method Suppose we want to migrate data from PV to PV #migratepv hdisk1 hdisk2 After executing above command hdisk1 data is moved to hdisk2 27. i. in this server has DATAVG with two PV’s. Now we want export DATAVG to ServerB Before exporting the DATAVG.
#lsvg It won’t show DATAVG name. #importvg –y NEWDATAVG hdisk3 #importvg –y NEWDATAVG hdisk4 Like this we can import. Import VG Using importvg command we can import the DATAVG to ServerB First you should connect hdisk3. in ServerB then. run the #cfgmgr (for hard disk detection) Then check the PV’s installed or not using lspv command #lspv (it will display the installed PV’s) if hdisk3. This case we can rename the importing VG DATAVG to other name. we no need to Varryon DATAVG. Then run the command importvg for import the DATAVG #importvg –y DATAVG hdisk3 (VG information is added in ODM) #importvg –y DATAVG hdisk4 (VG information is added in ODM) NOTE: Suppose ServerB has VG with same name DATAVG.Now DATAVG is exported from the ServerA. . automatically it will Varryon while importing. Because DATAVG is exported. after this run the following command to verify the export. Then you should remove PV from the configuration #rmdev –dl hdisk3 #rmdev –dl hdisk4 After that we can remove the PV’s from ServerA for import DATAVG to ServerB 29. hdisk4. After importing the DATAVG. hdisk4 is available then PV’s are configured properly.
The VGSA is essentially a bitmap and its architecture and location on the disk Depends on the type of the volume group. VGDA. LVCB (Logical Volume control block) Logical volume control block (LVCB) contains important information about the Logical volume. Its architecture and location on the disk depends on the type of the . It Also includes information about properties and status of all physical and Logical volumes that are part of the volume group. LVCB VGDA (Volume Group Descriptor Area) Volume group descriptor area (VGDA) is an area on the disk that contains Information pertinent to the volume group that physical volume belongs to. VGDA internal architecture and location on the disk depends on the type of the volume group (original. big. Change VG Using chvg command we can change the VG options #chvg –a y datavg (datavg is automatically activated at startup) #chvg -a n datavg (To deactivate the automatic activation at startup) #chvg –t 2 datavg (To change max. There is at least one VGDA per Physical volume. such as the number of the logical partitions or disk allocation Policy. Information from VGDAs of all disks that are part of the Same volume group must de identical.30. The information from VGDA is used and updated by LVM commands. The VGSA indicates if a physical partition contains accurate or stale information. or Scalable). VGSA Is used for monitoring and maintained data copies synchronization. VGSA (Volume Group Status Area) Volume group status area (VGSA) is used to describe the state of all physical Partitions from all physical volumes within a volume group. no of PP to 2032 on vg datavg) #chvg –Qn datavg (To disable quorum on VG datavg) #chvg –Qy datavg (To activate quorum on VG datavg) #chvg –u datavg (To unlock the VG) NOTE: Quorum. VGSA.
e. For standard volume groups. When we activate quorum in VG it will recover 51% of data in VG If we have DATAVG. For scalable volume groups All relevant logical volume control information is kept in the VGDA as part of The LVCB information area and the LV entry area. the LVCB resides on The first block of user data within the LV. PAGING SPACE Paging space is configured for additional system performance i. Quorum The following commands change the quorum for the volume group testvg. then paging space size will be 1GB. If real memory getting free. it will protect only 33% data. 9. . that time further process is moved to paging space temporary. This DATAVG has two PV’s hdisk1. it will protect 66% of data and Second PV hdisk2 has 1 VGDA. To turn off the quorum use the command: #chvg -Qn testvg To turn on the quorum use the command: # chvg -Qy testvg Quorum is used for data integrity. For big volume groups there is Additional LVCB information in VGDA on the disk. Normally paging space is configured double size of the real memory If system has 512MB RAM. so hdisk1 has 2 VGDA. if real memory is occupies some system process. then process moved from paging space to real memory.Volume group it belongs to. hdisk2. This paging space is assigned from HDD space. First PV hdisk1 has 2 * VGDA and 1 *VGSA Second PV hdisk2 has 1* VGDA and 1*VGSA Each VGDA has 33% of data. This Attribute determines if the volume group will be varied off or not after losing the Simple majority of its physical volumes.
2. paging01. decrease. 4. paging02. Change paging space Using chps command we can increase. 6. auto on. and auto off the paging space. List paging space Create paging space Change paging space Activate paging space Deactivate paging space Remove paging space 1. 3. newpaging 3.size 10 – no of PP size Rootvg – specifying the VG Hdisk2 – paging space created in PV hdisk2 (PP allocated from hdisk2) Then paging space has created and name will be paging00 Using mklv command we can create paging space using different name.In this paging space we can do following things 1. List paging space Using lsps command we can view the paging space details #lsps –a (It will display the paging space details) 2. Generally paging name will be paging00. Create Paging space Using mkps command we can create the paging space #mkps –s 10 rootvg hdisk2 s. #chps –s 5 newpaging (5 LP’s added with newpaging) – To increase #chps –d 3 newpaging (3 LP’s reduced from newpaging – To Decrease #chps -ay newpaging (To start the paging space at startup) #chps –an newpaging (To stop the paging space automatic startup at boot) . #mklv –y newpaging –t paging rootvg 10 hdisk2 #lsps –a Paging00 . 5.
Start daemon List daemon stop daemon refresh (restart) daemon . Remove paging space Using rmps command we can remove the paging space #rmps newpaging NOTE: Before removing the paging space. then we can remove the paging space. Activate paging space Using swapon command we can activate the paging space #swapon /dev/newpaging (To activate paging space) The paging space is active stage. 3. using src command we can do following things with subsystems and daemons 1. then that paging space entry is removed from /etc/swapspaces 6. Deactivate paging space Using swapoff command we can deactivate the paging space #swapoff /dev/newpaging (To deactivate paging space) The paging space is deactivated. SRC AND DAEMONS Group of subsystems called daemons. and then one entry will be available in /etc/swapspaces file. 4. otherwise it will give some errors 10. 2.4. 5. paging space should be offline.
statd. Nfs daemons: Server: 1. Start daemon Using srcstart command we can start the daemon.lockd – started Rpc.statd – started # The above command is start all the 5 subsystems at the same time. List Daemon Using lssrc command we can list the daemons Suppose we want see check status of the nfs daemon. 5. 4. rpc.mountd Client: 3. 2.biod.mountd – started Rpc.lockd Suppose clients are not able to access the network file system from the server.1. If one subsystem is not working properly or not started. but it is not recommended. nfsd. whether subsystems are started or not. then the nfs is not working properly. that time you have to start or restart the nfsd and rpc. rpc. when you configured nfs in server. suppose we want to start nfs daemon Actually nfs daemon has 5 subsystems (services). #startsrc –s nfsd #startsrc –s rpc. 2. that 5 subsystems are always start state. because we are starting single nfsd subsystem Suppose we want start complete nfs daemons using –g flag #startsrc –g nfs Nfsd – started Biod – started Rpc.mountd Flag –s is mentioned for single. rpc.mountd subsystems. . Like this we start single subsystem or group of subsystems.
Suppose we want to stop nfs daemon.#lssrc –g nfs Nfsd – started Biod – started Rpc. then your command will be #stopsrc –g nfs Nfsd – stopped Biod – stopped Rpc.mountd – stopped Rpc. Stop Daemon Using stopsrc command we can stop the daemon.started NOTE: #lssrc –a The above command list the status of all the daemons.lockd – stopped Rpc. like this we can stop the daemons .lockd – started Rpc.statd – stopped Or we can stop single subsystem using –s flag #stopsrc –s nfsd Nfsd – stopped.statd – not started Or we can check single subsystem status using #lssrc –s nfsd Nfsd .mountd – not started Rpc. Like this we can list and check the status of the daemons 3.
so that time network card will be installed in server. Disable IP address 4. Check the network statistics 9. While booting the server boot process is starting the cfgmgr. Clear the gateway table 1. Remove IP address 6. NIC Configuration 2. NETWORK In this chapter we can do following things. That Ethernet card is divided into three parts Ent0 – Physical adapter En0 – Logical name Et0 – Architecture of the card (802. Assign IP address to NIC 3. Assign gateway to network 12.4.3) Or Using mkinet command we can install the NIC . Suppose we want to install new network card. Enable IP address 5.statd (restart the single subsystems) Like this we can restart the daemons 11. We have installed Ethernet card 1. NIC Configuration Using cfgmgr command we can configure to server Cfgmgr command is device management related command. 1. Trace the HOST 11. To change HOST name 10. Refresh (restart) Daemon Using refresh command we can restart the daemon #refresh –g nfs (restart the group of subsystems) #refresh –s rpc. Check the NIC device status 8. Check the NIC IP status 7. first we should connect network in server.
255. Disable IP address Using ifconfig command we can disable the IP address #ifconfig en0 down (Turns off network card en0) 4.2.1 netmask 255.255.1. Enable IP address #ifconfig en0 up (Turns on network card en0) . Assign IP address to NIC Using mktcpip or smitty tcpip command we can assign IP address to NIC #smitty tcpip It will ask following details Hostname – IP address – Subnet mask – DNS server – DNS Server name – Gateway – # Or #ifconfig en0 inet 192.168.1.0 up (Configure en0 starts Immediately) After finishing this process ip address assigned to NIC Or We can assign one more IP address to same network card #ifconfig en0 192.168.33 –alias (Removing alias IP from en0) 3.33 alias (adding alias IP to en0) #ifconfig –en0 192 168.1.
Check the Network Statistics Using netstat command we can check the network statistics #netstat –a (To show the state of all sockets) #netstat –c (To show the network buffers cache) #netstat –D (To show the net drops of packets) #netstat –i (To display interface statistics) #netstat –rn (To show routing table – ip will be given instead of host names) #netstat –s (To show statistics of the protocols) . Check the NIC device status #entstat en0 (To display the status of Ethernet device en0) #entstat –d en0 (To display detailed information about Ethernet device en0) 8.5. Check status of the NIC Using ifconfig command we can check the status of the NIC #ifconfig –a (To show status of all network interfaces for IP) 7. Remove IP address Using ifconfig command we can remove network interface from network list #ifconfig en0 detach (Removes en0 card from the network interface list) 6.
1 as default gateway for entire network) #route add 192.1 192. Changing the HOST name Using hostname command we can change the host name #hostname (It will display existing host name) ServerA #hostname ServerB #hostname ServerB ServerA host name is changed to ServerB Or Using chdev command to change the hostname for inet0 #chdev –l inet0 –a hostname=ServerB 10.1 as gateway for 0. Trace the HOST Using traceroute command we can trace the route to the host #traceroute ServerA (To trace the route to ServerA) 11.1 network Like this we can assign the gateway for network .1 (To make 1.168.1 (To make 192.0.0.1.18.104.22.168.9. Assign gateway to network Using route command we can assign gateway to network #route add 0 192.
12. Clear the Gateway Using route command we can clear the gateway #route –f (To clear the gateway)
12. NFS (Network File System)
In this NFS we can share the file systems from server to clients, across the network, using some nfs related commands we can configure the NFS in server end and client end. So clients can access the server mounted files systems through network, with specified permissions, such as read only, read write. NOTE: Before configuring the NFS, U should check the /etc/hosts file entry, and NFS daemons and all the nfs daemon subsystems nfsd, rpc.mountd subsystems is running on server end rpc.statd, rpc.lockd, rpc.mountd subsystems running on client end Server End First we should export the file system from server end. 1. 2. 3. 4. Export List the exported file systems Remove the exported file systems Change the exported file system permissions
Then we should import the file system to client end. 5. Import 6. List the imported file systems 7. Remove the imported file systems
1. Export file system Using smitty mknfsexp command we can export the file system #smitty mknfsexp One window will appear then you have to put the configuration a. File system name (what file system you want to export i.e. /usr) b. Specify the target host name (destination host name i.e. serverB) If this box is empty, then this exporting file system is allowed to all the clients. c. Specify the access permissions (Read only, Read write) d. Host allowed root access (Source Server name, ServerA) e. Then press enter button to execute the above configuration finally result will be OK, if you got OK output then your configurations are exported properly. If you got FAILED error message then you have to check the configuration. NOTE: After exporting the file system, that exported file system will be added in /etc/exports, and /etc/xtab because while boot process, server is checking exported file systems from above files, if entry found in the above file then file system are exporting on boot process.
2. List the exported file system Using lsnfsexp command we can list the exported file system #lsnfsexp /usr – rw 3. Remove the exported file system Using smitty rmnfsexp command we can remove the exported file system #smitty rmnfsexp
One smitty screen will appear, and then you press Esc+4, it will check and shows what are the file systems are exported. Then you can remove the exported file system. After this command execution, list the exported file system using command lsnfsexp, now removed file systems is not listed. NOTE: while removing the file system, the file system entry removed from /etc/exports and /etc/xtab 4. Changing exported file system permissions Using chnfsexp command we can change the permission for exported file systems #smitty chnfsexp One smitty screen will appear, and then you specify the permission and configure the file system 5. Import the file systems Using smitty mknfsmnt command we can import the file system. #smitty mknfsmnt One smitty configuration screen will appear then you have to specify the following things. a. specify the path name of mount point (client end mount point by default /mnt will be available or we have to create directory and we can specify that directory name to mount the file system /mnt) b. Specify the path name of remote directory (This is server file system name i.e. /usr, which file system was exported by server) c. Host where remote directory resides (This is exporting source server name i.e. ServerA) d. Mount type name (Specify the file system type jfs2) e. Then press enter button to execute the above configuration, finally it will exported.
Remove the imported file system Using smitty rmnfsmnt command we can remove the mounted file system from client end.5. Now you put mount command. Create user List user Change user Remove user Set password for users . Specify the mounted file system name or press Esc+4 keys. if nfs mounted file system available then it will show file system type name nfs so easily we can identify which nfs mounted file system 6. 4. Like this we can export and import the network file system. that removed file system is not listed. for system analyze and show the mount file system. After this command execution. which mounted file system will be removed from the client PC. USER AND GROUP MANAGEMENT In this user management we can do following commands 1. 3. 2. 5. 13. List the imported files system Using mount command we can check the imported file system status. then you mention from the list also. #mount Above command is used to display the mounted file system information along with file system type. #smitty rmnfsmnt Then one smitty screen will appear.
Then you have to set the password for kumar user using command passwd #passwd kumar Enter new password: ****** Confirm password again: ****** After this command execution password assigned to kumar user and kumar user password configuration entry added in /etc/security/passwd. shell group.sys Whenever login the server that last login information’s stored in /etc/security/lastlog file. user home directory. NOTE: user configuration data stored in /usr/lib/security/mkuser.e. except password #lsuser all (It will list all the user information’s except password) #lsuser kumar (It will list only kumar user information’s except password) 3. then your command will be. group. shell.1. and default group is staff. List user Using lsuser command we can list the user properties. #mkuser kumar After this command execution. etc. Suppose we want to change the kumar user group to system. i. kumar home directory created in /home/kumar/ Kumar user configuration details stored in /etc/passwd Now you can login the terminal using kumar user name without password. Change user Using chuser command we can change user properties.e. suppose you want to create new user Kumar. except password Whenever you create a user that user home directory by default created in /home file system. i. . user home directory. etc. Create user Using mkuser command we can create a new user. 2.
. staff) Like this we can change all the user properties 4. because user should know the existing password before changing the new password. 5. because root is administrator login. it will ask existing password. group is system. This not recommended security. Set password for Users Using passwd command we can set password for user and root #passwd kumar Enter new password: ***** Confirm password: ***** We are changing password for kumar user from root path. Otherwise any user can change the kumar user password. it will not ask existing password for kumar user. suppose you want to remove kumar user #rmuser kumar After this command execution.#lsuser kumar (it will show kumar user properties including group information) #chuser pgrp=system kumar (now kumar user is assigned to primary group system and secondary group is assigned to staff) #lsuser kumar (It will list modified kumar properties. kumar user will be deleted. $pwd /home/kumar $passwd kumar Enter the old password: ***** Enter the new password: ***** Confirm password again: ***** NOTE: Suppose you are forgotten root password that time what you will do. Suppose you are changing password from kumar login. Remove user Using rmuser command we can remove the user.
Suppose we want to list oracle group information #lsgroup oracle (it will display the oracle group information’s. List group Using lsgroup command we can list group information’s. 3. gid. GROUP MANAGEMENT In this group management we can do following things. Create group List group Change group Remove group 1.Answer: boot the server with BOS Cd and go to maintenance mode. then you can change the password for root. Like this we can change the password for users. 2. gname. 1. #chgroup options oracle . 4. Create group Using mkgroup command we can create the group. suppose you want to create oracle group. access the rootvg. 2. members) #lsgroup all (It will list all group details) 3. #mkgroup oracle After this command execution new oracle group has created and this group is added in /etc/groups file. Change group Using chgroup command we can change the group information’s.
so that server will create 5 users at scheduled time. suppose we want to remove oracle group. but next week system administrator is out of country. SCHEDULING In Aix Os we can schedule jobs using crontab command. these jobs are executed in background at mentioned time. Edit scheduling Using crontab command we can edit the scheduled job . 1. In this scheduling we can do following things. Suppose Administrator want to create five users on next week. that time admin can schedule this user creation job one week before using crontab command. 3. List scheduling Using crontab command we can list scheduled job. #rmgroup oracle After this command execution oracle group removed and group configuration information removed from /etc/groups files. 14. 2. Remove group Using rmgroup command we can remove a group. 4. #crontab –l The above command is list the scheduled jobs 2.4. List scheduling Edit scheduling Clear scheduling Assign user permissions 1.
see below) 0-7 (0 or 7 is Sun. in this at command we cannot specify the multiple jobs. that time you put entry in /var/adm/cron/cron. minute hour day of month month day of week 0-59 0-23 1-31 1-12 (or names. #crontab –r After command execution this crontab file entries will be removed. that time you put entry in /var/adm/cron/cron. 4. Clear the scheduling Using crontab command we can clear the scheduled jobs.#crontab –e Here you have to mention i. at a time we can run single job only.deny file Like this we can assign permissions to users for crontab process NOTE: In AIX OS at command also available for schedule the job. or use names) #run at 2:15pm on the first of 6th month Saturday (comments) 15 14 1 6 6 #mkuser kumar Kumar user will be created on mentioned time NOTE: Once crontab jobs completed. now a days this at command is not using by users.allow file Suppose u want to allow kumar user for crontab process. at what jobs will be executed. they are using only crontab . that output logs stored in /var/spool/cron/crontabs 3.e. Assign the user permissions We can allow and deny crontab usage permissions for users Suppose u want to deny kumar user for crontab process.
7. 5. 6. In this backup command we can specify the day (0(sun) – 6(sat)). BACKUP AND RESTORE In this chapter we can do following things using backup and restore commands 1. Backup Using backup and tar command to we can take full backup and incremental backup Using tar command we can normal backup. 2.15. in this tar we cannot take day wise incremental backup #tar –cvf destination source #tar –cvf /dev/rmt0 /usr/sbin #backup –if /dev/rmt0 /usr/sbin (For AIX full backup) /usr/sbin directory files is backup to tape Using backup command we can take incremental backup. Suppose you want to take Sunday backup then your command will be #backup -0 –vf destination source #backup -0 –vf /dev/rmt0 /var #backup -6 –vf /dev/rmt0 /var (Saturday backup) /var file system log is backup to tape Like this we can take normal and incremental backup in AIX . this backup command is particularly for AIX. 3. 4. backup restore rootvg backup restore rootvg backup non rootvg backup(other than rootvg) restore non rootvg backup(other than rootvg) rewind. eject and erase the tape 1.
rootvg backup Using mksysb command we can take the rootvg (AIX OS) backup #mksysb –i /dev/rmt0 #mksysb –ie /dev/rmt0 (exclude backup – please read NOTE message) i option is used for crate the image. /var – log files That time you should put entry in /etc/exclude. Restore Using tar and restore command we can restore the data in server Using tar command we can restore data to server. Suppose you not required following file systems in mksysb backup. NOTE: While taking rootvg backup we can exclude unwanted file systems in backup process. that time we can restore the os from rootvg backup.data file After the command execution rootvg backup created in tap. Like this we can restore the data in AIX 3.rootvg. Using restore command we can restore the data #restore –xdf /dev/rmt0 The tape data is restored in current directory. suppose OS got corrupted. While creating the rootvg backup. first tape is spitted in to 4 blocks (block size is 512) . this is normal restore #tar –xvf /dev/rmt0 The tape backup is restored to /data directory. before start the restore it will read the information’s from the image.data file contains all the file system information’s in rootvg while restore the rootvg backup.2.data file created in tape This image.
/bosinst.data file allows you to specify the requirements at the target system and how the user interacts with the target system. The dummy table of contents (TOC) is used so that the mksysb tape contains the same number of images as a BOS install tape. /bosinst. lv. /image. The BOS boot image contains a copy of the system’s kernel and device drivers needed to boot from the mksysb tape. It is created by the bosboot command. bosinst.data. /image.data The . 1. /tapeblksize. lv size. pp.data. like vg. Second block has following things. 3.data The /image. /tapeblksize The /tapeblksize file contains the block size the tape drive was set to when the mksysb command was run. FS The image. 1. 2. This file contains the customized BOS install procedures and dictates how the BOS install program will behave.First block has boot image. Third block has dummy toc file. 2.data 3. that is rootvg original data .data file store the information about rootvg. pp size. You can customize this file before issuing the mksysb command or use a procedure to customize this file after the image backup is done. Fourth block has data.data file resides in /var/adm/ras/image.
. Backup the non rootvg backup Using savevg command we can backup the non rootvg backup Suppose your server has 3 volume groups #lsvg Rootvg Datavg Oraclevg # Now you want to take datavg backup. then your command will be #savevg –if /dev/rmt0 /datavg #savevg –ief /dev/rmt0 /datavg Datavg volume group is backup to tape NOTE: While taking restvg backup we can exclude unwanted file systems in backup process. then run the following command #restore –T –d –v –q –f /dev/rmt0 Or Boot server with bos CD. then go to maintenance mode and access the rootvg. /var – log files That time you should put entry in /etc/exclude. Suppose you not required following file systems in mksysb backup. then go to maintenance mode and initiate the rootvg backup (one option available in maintenance mode).4. Restore rootvg backup Using restore command we can restore the rootvg backup Boot server with bos (base operating system) Cd. Like this we can restore the rootvg backup 5.datavg.
Cpu bound Memory bound Network bound I/O bound 1. Eject. Restore the non rootvg backup Using restvg command we can restore the non rootvg backup #restvg –xdf /dev/rmt0 After command execution datavg backup restored to server with same name while importing vg we can change the vg name. #tctl –f /dev/rmt0 rewind (To rewind the tape) #tctl –f /dev/rmt0 eject (To eject the tape) #tctl –f /dev/rmt0 erase (To erase the tape content) 16. Rewind. eject and erase the tape drive. 4. 5. 2. 1. 7. 3. CPU bound Using Topas command we can check the server performance monitor. Erase the tape Using tctl command we can rewind. processor (CPU Usage) Network (KB in / KB out) Memory (Page in / Page out) I/O (HDD read and write) Top 8 process . 3. the following things we can monitor. 4.6. PERFORMANCE MONITORING In this performance monitoring we can check following things 1. 2.
Memory bound Using vmstart command we can monitor the memory bound #vmstat 2 3 After this command execution. Network bound Using topas command we can monitor the network bound. 3 outputs is displayed Suppose you are checking paging space usage using command lsps #lsps –s 11% . in this network monitor we can find KB in and KB out process.Server running on slow performance 70% . Some error message will appear (fork exist failed) 3. it will show the memory page in and page out process. 4.this is normal 40% . suppose you are using two or three heavy used file system in one PV that time that particular PV usage will be very high . I/O bound Using iostat command we can monitor the I/O bound In this I/O bound we can monitor the disk usage.2.users cannot logon the server. Within 2 seconds.
online we can assign the hardware resources using HMC. Using HMC (Hardware Management Console) we can partition and operate the LPAR servers Suppose you have one P690 server with 16 CPU’s and 16GB Ram. LPAR / DLPAR We can configure LPAR and DLPAR in P690 Servers. and Change the Logical Partitions This LPAR server has hypervisor Controller. Harddisk. using this concept we can access the LPAR servers from windows desktops) 2.2. and using LPAR concept The above Os are installing in single server. using this concept we can access the LPAR servers through telnet) . like AIX 5. Suppose one particular Os assigned for 500 users that time we have to assign additional hardware resources to that partition. ssh (Secured shell. like processors and memory. Susi Linux. and it is used to maintain the server Accessing methods: 1. Delete. LPAR (Logical partitions) In single server we can install multiple operating systems. AIX 5. AIX 4. No need to reboot the server. wsm (Web based system management . Now each partitions has 1 CPU and 1GB Ram.1. this concept called DLPAR (dynamic Logical Partition) Like this we can create the LPAR / DLPAR HMC .3.17.it is a desktop pc (Linux OS) connected with P690 server through Communication (com port) cable or RJ45 Ethernet cat cable Using HMC we can Create. AIX 5. all the information’s stored in this hypervisor. before that we have to partition the hardware resources. in this server we can make 16 partitions.3.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.