Run level Description
0-1 Reserved for the future use of the operating system.
2 Contains all of the terminal process and daemons that are run in themultiuser environment. This is the default run level.
3-9 Can be defined according to the user’s preferences
a,b,c,h These are not true run levels; they differ from run levels in that the initcommand cannot request the entire system to enter these run levels.
Tuesday 5 February, 2008
THE /etc/inittab FILE
Order of the /etc/inittab entriesThe base process entries in the /etc/inittab file is ordered as follows:
1. initdefault
2. sysinit
3. Powerfailure Detection (powerfail)
4. Multiuser check (rc)
5. /etc/firstboot (fbcheck)
6. System Resource Controller (srcmstr)
7. Start TCP/IP daemons (rctcpip)
8. Start NFS daemons (rcnfs)
9. cron
10.pb cleanup (piobe)
11.getty for the console (cons)
The System Resource Controller (SRC) has to be started near the beginning ofthe etc/inittab file since the SRC daemon is needed to start other processes.
Since NFS requires TCP/IP daemons to run correctly, TCP/IP daemons arestarted ahead of the NFS daemons. The entries in the /etc/inittab file are ordered
according to dependencies, meaning that if a process (process2) requires thatanother process (process1) be present for it to operate normally, then an entryfor process1 comes before an entry for process2 in the /etc/inittab file.
1. initdefault
2. sysinit
3. Powerfailure Detection (powerfail)
4. Multiuser check (rc)
5. /etc/firstboot (fbcheck)
6. System Resource Controller (srcmstr)
7. Start TCP/IP daemons (rctcpip)
8. Start NFS daemons (rcnfs)
9. cron
10.pb cleanup (piobe)
11.getty for the console (cons)
The System Resource Controller (SRC) has to be started near the beginning ofthe etc/inittab file since the SRC daemon is needed to start other processes.
Since NFS requires TCP/IP daemons to run correctly, TCP/IP daemons arestarted ahead of the NFS daemons. The entries in the /etc/inittab file are ordered
according to dependencies, meaning that if a process (process2) requires thatanother process (process1) be present for it to operate normally, then an entryfor process1 comes before an entry for process2 in the /etc/inittab file.
LED 552, 554, and 556 SUPERBLOCK CORRUPTED
1. Repeat steps 1 through 2 for LEDs 551, 555, and 557.
2. If fsck indicates that block 8 is corrupted, the super block for the file system iscorrupted and needs to be repaired. Enter the command:dd count=1 bs=4k skip=31 seek=1 if=/dev/hdn of=/dev/hdnwhere n is the number of the file system.
3. Rebuild your JFS log by using the command:/usr/sbin/logform /dev/hd8
4. If this solves the problem, stop here; otherwise, continue with step 5.
5. Your ODM database is corrupted. Restart your system and follow the proceduregiven in 4.4.2, “Accessing a system that will not boot” on page 105 to access rootvgwith choice 2 on the Volume Group Information screen.
6. Mount the root and usr file systems as follows:mount /dev/hd4 /mntmount /usr
7. Copy the system configuration to a back up directory:mkdir /mnt/etc/objrepos/backupcp /mnt/etc/objrepos/Cu* /mnt/etc/objrepos/backup
8. Copy the configuration from the RAM file system as follows:cp /etc/objrepos/Cu* /mnt/etc/objrepos
9. Unmount all file systems by using the umount all command.
10. Determine the boot disk by using the lslv -m hd5 command.
11. Save the clean ODM to the boot logical volume by using the command:savebase -d/dev/hdisknwhere n is the disk number of the disk containing boot logical volume.
12. Reboot, if the system does not come up, and reinstall BOS.
2. If fsck indicates that block 8 is corrupted, the super block for the file system iscorrupted and needs to be repaired. Enter the command:dd count=1 bs=4k skip=31 seek=1 if=/dev/hdn of=/dev/hdnwhere n is the number of the file system.
3. Rebuild your JFS log by using the command:/usr/sbin/logform /dev/hd8
4. If this solves the problem, stop here; otherwise, continue with step 5.
5. Your ODM database is corrupted. Restart your system and follow the proceduregiven in 4.4.2, “Accessing a system that will not boot” on page 105 to access rootvgwith choice 2 on the Volume Group Information screen.
6. Mount the root and usr file systems as follows:mount /dev/hd4 /mntmount /usr
7. Copy the system configuration to a back up directory:mkdir /mnt/etc/objrepos/backupcp /mnt/etc/objrepos/Cu* /mnt/etc/objrepos/backup
8. Copy the configuration from the RAM file system as follows:cp /etc/objrepos/Cu* /mnt/etc/objrepos
9. Unmount all file systems by using the umount all command.
10. Determine the boot disk by using the lslv -m hd5 command.
11. Save the clean ODM to the boot logical volume by using the command:savebase -d/dev/hdisknwhere n is the disk number of the disk containing boot logical volume.
12. Reboot, if the system does not come up, and reinstall BOS.
LED 551, 555, and 557 - Corrupted file system, corrupted JFS log, and so on
LED 551, 555, and 557 - Corrupted file system, corrupted JFS log, and so on
1. Follow the procedure described in 4.4.2, “Accessing a system that will not boot” onpage 105 to access the rootvg before mounting any file systems (choice 2 on theVolume Group Information screen).
2. Verify and correct the file systems as follows:fsck -y /dev/hd1fsck -y /dev/hd2fsck -y /dev/hd3fsck -y /dev/hd4fsck -y /dev/hd9var
3. Format the JFS log again by using the command:/usr/sbin/logform /dev/hd8
4. Use lslv -m hd5 to obtain the boot disk.
5. Recreate the boot image using the command:bosboot -a -d /dev/hdiskn
Where n is the disk number of the disk containing the boot logical volume.
1. Follow the procedure described in 4.4.2, “Accessing a system that will not boot” onpage 105 to access the rootvg before mounting any file systems (choice 2 on theVolume Group Information screen).
2. Verify and correct the file systems as follows:fsck -y /dev/hd1fsck -y /dev/hd2fsck -y /dev/hd3fsck -y /dev/hd4fsck -y /dev/hd9var
3. Format the JFS log again by using the command:/usr/sbin/logform /dev/hd8
4. Use lslv -m hd5 to obtain the boot disk.
5. Recreate the boot image using the command:bosboot -a -d /dev/hdiskn
Where n is the disk number of the disk containing the boot logical volume.
LED 223-229 - INVALID BOOT LIST SOLUTIONS
1. Set the key mode switch to service (F5 for systems without keylock) and power up the machine.
2. If display continues normally, change the key mode switch to Normal and continuewith step 3. If you do not get the prompt, go to step 4.
3. When you get the login prompt, log in and follow the procedure described in 4.4.1,“The bootlist command” on page 103 to change your bootlist. Continue with step 7.
4. Follow the procedure in 4.4.2, “Accessing a system that will not boot” to access your rootvg and continue with step 5.
5. Determine the boot disk by using the lslv -m hd5 command.
6. Change the bootlist following the procedure given in 4.4.1, “The bootlist command”on page 103.
7. Shut down and restart your system.
2. If display continues normally, change the key mode switch to Normal and continuewith step 3. If you do not get the prompt, go to step 4.
3. When you get the login prompt, log in and follow the procedure described in 4.4.1,“The bootlist command” on page 103 to change your bootlist. Continue with step 7.
4. Follow the procedure in 4.4.2, “Accessing a system that will not boot” to access your rootvg and continue with step 5.
5. Determine the boot disk by using the lslv -m hd5 command.
6. Change the bootlist following the procedure given in 4.4.1, “The bootlist command”on page 103.
7. Shut down and restart your system.
COMMON BOOT LED CODES AND SOLUTIONS
LED 201 - Damaged boot image
1. Access your rootvg by following the procedure described “Accessing asystem that will not boot”
2. Check the / and /tmp file systems. If they are almost full, create more space.
3. Determine the boot disk by using the lslv -m hd5 command.
4. Recreate the boot image using bosboot -a -d /dev/hdiskn, where n is the disknumber of the disk containing the boot logical volume.
5. Check for CHECKSTOP errors in the error log. If such errors are found, it isprobably failing hardware.
6. Shut down and restart the system.
1. Access your rootvg by following the procedure described “Accessing asystem that will not boot”
2. Check the / and /tmp file systems. If they are almost full, create more space.
3. Determine the boot disk by using the lslv -m hd5 command.
4. Recreate the boot image using bosboot -a -d /dev/hdiskn, where n is the disknumber of the disk containing the boot logical volume.
5. Check for CHECKSTOP errors in the error log. If such errors are found, it isprobably failing hardware.
6. Shut down and restart the system.
Monday 4 February, 2008
BOOT PHASE 3
Boot phase 3
After phase 2 is completed, rootvg is activated and the following steps are taken:
/etc/init process is started. It reads the /etc/inittab file and calls rc.boot with argument 3.
The /tmp file system is mounted.The rootvg is synchronized by calling the syncvg command and launching itas a background process. As a result, all stale partitions from rootvg areupdated.
At this stage, the LED code 553 is shown.
At this stage, the cfgmgr command is called; if the system is booted in normalmode,
the cfgmgr command is called with option -p2; if the system is bootedin service mode, the cfgmgr command is called with option -p3. The cfgmgrcommand reads the Config_rules file from ODM and calls all methodscorresponding to either phase=2 or phase=3.
All other devices that are notbase devices are configured at this time.
Next, the console is configured by calling the cfgcon command. After theconfiguration of the console, boot messages are sent to the console if noSTDOUT redirection is made.
However, all missed messages can be found in/var/adm/ras/conslog. LED codes that can be displayed at this time are:
-c31: Console not yet configured. Provides instructions to select console.– c32: Console is an LFT terminal.
– c33: Console is a TTY.
-c34: Console is a file on the disk._ Finally, the synchronization of the ODM in the BLV with the ODM from the /(root) file system is done by the savebase command.
_ The syncd daemon and errdemon are started.
_ The LED display is turned off.
_ If the file /etc/nologin exists, it will be removed.
_ If there are devices marked as missing in CuDv, a message is displayed on
After phase 2 is completed, rootvg is activated and the following steps are taken:
/etc/init process is started. It reads the /etc/inittab file and calls rc.boot with argument 3.
The /tmp file system is mounted.The rootvg is synchronized by calling the syncvg command and launching itas a background process. As a result, all stale partitions from rootvg areupdated.
At this stage, the LED code 553 is shown.
At this stage, the cfgmgr command is called; if the system is booted in normalmode,
the cfgmgr command is called with option -p2; if the system is bootedin service mode, the cfgmgr command is called with option -p3. The cfgmgrcommand reads the Config_rules file from ODM and calls all methodscorresponding to either phase=2 or phase=3.
All other devices that are notbase devices are configured at this time.
Next, the console is configured by calling the cfgcon command. After theconfiguration of the console, boot messages are sent to the console if noSTDOUT redirection is made.
However, all missed messages can be found in/var/adm/ras/conslog. LED codes that can be displayed at this time are:
-c31: Console not yet configured. Provides instructions to select console.– c32: Console is an LFT terminal.
– c33: Console is a TTY.
-c34: Console is a file on the disk._ Finally, the synchronization of the ODM in the BLV with the ODM from the /(root) file system is done by the savebase command.
_ The syncd daemon and errdemon are started.
_ The LED display is turned off.
_ If the file /etc/nologin exists, it will be removed.
_ If there are devices marked as missing in CuDv, a message is displayed on
BOOT PHASE 2
Boot phase 2
In boot phase 2, the rc.boot script is passed to the parameter 2.
During this phase, the following steps are taken.
The rootvg volume group is varied on with the special version of the varyonvgcommand named the ipl_varyon command. If this command is successful,the system displays 517
; otherwise, one of the following LED codes willappear: 552, 554, or 556, and the boot process is halted.
Root file system hd4 is checked using the fsck -f command. This will verifywhether the file system was unmounted cleanly before the last shutdown.
If this command fails, the system will display code 555.
The root file system (/dev/hd4) is mounted on a temporary mount point (/mnt)in RAMFS.
If this fails, 557 will appear in the LED display.
IBM Eserver p5 and pSeries Administration and Support for AIX 5L V5.3
The /usr file system is verified using the fsck -f command and thenmounted. If this operation fails, the LED 518 appears.
The /var file system is verified using the fsck -f command and thenmounted. The copycore command checks if a dump occurred. If it did, it iscopied from default dump devices, /dev/hd6, to the default copy directory,/var/adm/ras.
Afterwards, /var is unmounted. The primary paging space from rootvg, /dev/hd6, will be activated. The mergedev process is called and all /dev files from the RAM file systemare copied onto disk. All customized ODM files from the RAM file system are copied to disk.
Both ODM versions from hd4 and hd5 are now synchronized. Finally, the root file system from rootvg (disk) is mounted over the root filesystem from the RAMFS. The mount points for the rootvg file systemsbecome available.
Now, the /var and /usr file systems from the rootvg aremounted again on their ordinary mount points.There is no console available at this stage, so all boot messages will be copied to alog. The alog command maintains and manages logs.
In boot phase 2, the rc.boot script is passed to the parameter 2.
During this phase, the following steps are taken.
The rootvg volume group is varied on with the special version of the varyonvgcommand named the ipl_varyon command. If this command is successful,the system displays 517
; otherwise, one of the following LED codes willappear: 552, 554, or 556, and the boot process is halted.
Root file system hd4 is checked using the fsck -f command. This will verifywhether the file system was unmounted cleanly before the last shutdown.
If this command fails, the system will display code 555.
The root file system (/dev/hd4) is mounted on a temporary mount point (/mnt)in RAMFS.
If this fails, 557 will appear in the LED display.
IBM Eserver p5 and pSeries Administration and Support for AIX 5L V5.3
The /usr file system is verified using the fsck -f command and thenmounted. If this operation fails, the LED 518 appears.
The /var file system is verified using the fsck -f command and thenmounted. The copycore command checks if a dump occurred. If it did, it iscopied from default dump devices, /dev/hd6, to the default copy directory,/var/adm/ras.
Afterwards, /var is unmounted. The primary paging space from rootvg, /dev/hd6, will be activated. The mergedev process is called and all /dev files from the RAM file systemare copied onto disk. All customized ODM files from the RAM file system are copied to disk.
Both ODM versions from hd4 and hd5 are now synchronized. Finally, the root file system from rootvg (disk) is mounted over the root filesystem from the RAMFS. The mount points for the rootvg file systemsbecome available.
Now, the /var and /usr file systems from the rootvg aremounted again on their ordinary mount points.There is no console available at this stage, so all boot messages will be copied to alog. The alog command maintains and manages logs.
BOOT PHASE 1
Boot phase 1
During this phase, the following steps are taken:_ The init process started from RAMFS executes the boot script rc.boot 1.
If the init process fails for some reason, code c06 is shown on the LED display.
_ At this stage, the restbase command is called to copy a partial image of ODMfrom the BLV into the RAMFS. If this operation is successful, the LED displayshows 510;
otherwise, LED code 548 is shown._ After this,
the cfgmgr -f command reads the Config_Rules class from the reduced ODM. In this class, devices with the attribute phase=1 areconsidered base devices. Base devices are all devices that are necessary to access rootvg.
For example, if the rootvg is located on a hard disk, all devicesstarting from the motherboard up to the disk will have to be initialized. Thecorresponding methods are called so that rootvg can be activated in bootphase 2.
_ At the end of boot phase 1, the bootinfo -b command is called to determine the last boot device. At this stage, the LED shows 511.
During this phase, the following steps are taken:_ The init process started from RAMFS executes the boot script rc.boot 1.
If the init process fails for some reason, code c06 is shown on the LED display.
_ At this stage, the restbase command is called to copy a partial image of ODMfrom the BLV into the RAMFS. If this operation is successful, the LED displayshows 510;
otherwise, LED code 548 is shown._ After this,
the cfgmgr -f command reads the Config_Rules class from the reduced ODM. In this class, devices with the attribute phase=1 areconsidered base devices. Base devices are all devices that are necessary to access rootvg.
For example, if the rootvg is located on a hard disk, all devicesstarting from the motherboard up to the disk will have to be initialized. Thecorresponding methods are called so that rootvg can be activated in bootphase 2.
_ At the end of boot phase 1, the bootinfo -b command is called to determine the last boot device. At this stage, the LED shows 511.
AIX BOOTING OVERVIEW
Booting involves the following steps:
_ The initial step in booting a system is the Power On Self Test (POST)hardware is checked then locate ROS
System Read Only Storage (ROS) is specific to each system type. It isnecessary for AIX 5L Version 5.3 to boot, but it does not build the datastructures required for booting. It will locate and load bootstrap code
Software ROS (also named bootstrap) forms an IPL control block, which iscompatible with AIX 5L Version 5.3, that takes control and builds AIX 5Lspecific boot information. A special file system located in memory and namedthe RAMFS file system is created. Software ROS then locates, loads, andturns control over to the AIX 5L boot logical volume (BLV)
A complete list of files that are part of the BLV can be obtained from the/usr/lib/boot directory. The most important components are the following:– The AIX 5L kernel– Boot commands called during the boot process, such as bootinfo andcfgmgr– A reduced version of the ODM. Many devices need to be configuredbefore hd4 is made available, so their corresponding methods have to bestored in the BLV. These devices are marked as base in PdDv.
and then
– The rc.boot script
Next booting involves three phases
_ The initial step in booting a system is the Power On Self Test (POST)hardware is checked then locate ROS
System Read Only Storage (ROS) is specific to each system type. It isnecessary for AIX 5L Version 5.3 to boot, but it does not build the datastructures required for booting. It will locate and load bootstrap code
Software ROS (also named bootstrap) forms an IPL control block, which iscompatible with AIX 5L Version 5.3, that takes control and builds AIX 5Lspecific boot information. A special file system located in memory and namedthe RAMFS file system is created. Software ROS then locates, loads, andturns control over to the AIX 5L boot logical volume (BLV)
A complete list of files that are part of the BLV can be obtained from the/usr/lib/boot directory. The most important components are the following:– The AIX 5L kernel– Boot commands called during the boot process, such as bootinfo andcfgmgr– A reduced version of the ODM. Many devices need to be configuredbefore hd4 is made available, so their corresponding methods have to bestored in the BLV. These devices are marked as base in PdDv.
and then
– The rc.boot script
Next booting involves three phases
REMOVING THE NETWORK ADAPTER
Removing a network adapter
To remove a network adapter from the system, use the ifconfig command to
remove the network adapter and interface definitions from the system prior to
physically removing the network adapter. The ifconfig command allows you to
perform configurations and modifications directly to network interfaces.
Note: After running cfgmgr, you may receive an error message as in the
following example:
# cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed.
devices.pci.ethernet:devices.pci.14100401:devices.pci.ae120100:devices.pc
i.pciclass.020000
If a message such as this appears, you will need to install the additional
filesets listed to enable the network adapter on the system.
To remove a network adapter, perform the following steps:
1. Deactivate (down) all network interface definitions for the network adapter by
running the command:
# ifconfig Interface down
This step is technically not required, but is a good fail-safe to ensure that no
applications or processes are using the specified network interfaces.
2. Remove (detach) all network interface definitions from the network interface
list by running the command:
# ifconfig Interface detach
This step will remove all attributes associated with the network interface from
the system, including attributes like IP address and MTU size.
3. Delete the network interface definitions from the system by running the
command:
# rmdev -l Interface -d
4. Delete the network adapter definition from the system by running the
command:
# rmdev -l Adapter -d
5. Shut down and power off the system (on non hot plug machines).
6. Physically remove the network adapter.
7. Power on the system.
To remove a network adapter from the system, use the ifconfig command to
remove the network adapter and interface definitions from the system prior to
physically removing the network adapter. The ifconfig command allows you to
perform configurations and modifications directly to network interfaces.
Note: After running cfgmgr, you may receive an error message as in the
following example:
# cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed.
devices.pci.ethernet:devices.pci.14100401:devices.pci.ae120100:devices.pc
i.pciclass.020000
If a message such as this appears, you will need to install the additional
filesets listed to enable the network adapter on the system.
To remove a network adapter, perform the following steps:
1. Deactivate (down) all network interface definitions for the network adapter by
running the command:
# ifconfig Interface down
This step is technically not required, but is a good fail-safe to ensure that no
applications or processes are using the specified network interfaces.
2. Remove (detach) all network interface definitions from the network interface
list by running the command:
# ifconfig Interface detach
This step will remove all attributes associated with the network interface from
the system, including attributes like IP address and MTU size.
3. Delete the network interface definitions from the system by running the
command:
# rmdev -l Interface -d
4. Delete the network adapter definition from the system by running the
command:
# rmdev -l Adapter -d
5. Shut down and power off the system (on non hot plug machines).
6. Physically remove the network adapter.
7. Power on the system.
CONFIGURE NETWORK ADAPTER ON AIX SYSTEM
Adding a network adapter
To add a network adapter to the system, perform the following steps:
1. Examine what network adapters and interfaces are already on the system by
running the following commands:
# lscfg grep -i adapter
running the following commands:
# lscfg grep -i adapter
+ mg20 20-58 GXT130P Graphics Adapter
+ fda0 01-D1 Standard I/O Diskette Adapter
* siokma0 01-K1 Keyboard/Mouse Adapter
+ sioka0 01-K1-00 Keyboard Adapter
+ sioma0 01-K1-01 Mouse Adapter
+ ppa0 01-R1 Standard I/O Parallel Port Adapter
+ ent0 10-80 IBM PCI Ethernet Adapter (22100020)
+ fda0 01-D1 Standard I/O Diskette Adapter
* siokma0 01-K1 Keyboard/Mouse Adapter
+ sioka0 01-K1-00 Keyboard Adapter
+ sioma0 01-K1-01 Mouse Adapter
+ ppa0 01-R1 Standard I/O Parallel Port Adapter
+ ent0 10-80 IBM PCI Ethernet Adapter (22100020)
# lsdev -Cc if
en0 Defined 10-80 Standard Ethernet Network Interface
et0 Defined 10-80 IEEE 802.3 Ethernet Network Interface
lo0 Available Loopback Network Interface
et0 Defined 10-80 IEEE 802.3 Ethernet Network Interface
lo0 Available Loopback Network Interface
2. Shut down and power off the system (for systems without hot plug cards).
3. Physically install the new network adapter.
4. Power on the system in normal mode.
5. When the system is fully up, run the cfgmgr command. This will automatically
detect the network adapter and add network interfaces for the adapter.
detect the network adapter and add network interfaces for the adapter.
Sunday 3 February, 2008
AIX LVM COMMAND QUICK REVIEW
Summary of the LVM commands
All LVM commands have corresponding menus in SMIT.
a summary of LVM commands, their
corresponding SMIT fast path, and a short description of each command.
Summary of LVM commands
Command SMIT fast path Description
chpv smit chpv Changes the characteristics of a physical
volume.
lspv smit lspv Lists information about physical
volumes.
migratepv smit migratepv Migrates physical partitions from one
physical volume to other(s).
mkvg smit mkvg Creates a volume group.
lsvg smit lsvg Lists information about volume groups.
reducevg smit reducevg Removes a physical volume from a
volume group.
chvg smit chvg Changes the characteristics of a volume
importvg smit importvg Imports the definition of a volume group
into the system.
exportvg smit exportvg Removes the definition of a volume
group from the system.
varyonvg smit varyonvg Activates a volume group.
varyoffvg smit varyoffvg Deactivates a volume group.
mklv smit mklv Creates a logical volume.
lslv smit lslv Lists information about a logical volume.
chlv smit chlv Changes the characteristics of a logical
volume.
rmlv smit rmlv Deletes a logical volume.
extendlv smit extendlv Extends a logical volume.
mklvcopy smit mklvcopy Creates a copy of a logical volume.
rmlvcopy smit rmlvcopy Removes a copy of a logical volume.
All LVM commands have corresponding menus in SMIT.
a summary of LVM commands, their
corresponding SMIT fast path, and a short description of each command.
Summary of LVM commands
Command SMIT fast path Description
chpv smit chpv Changes the characteristics of a physical
volume.
lspv smit lspv Lists information about physical
volumes.
migratepv smit migratepv Migrates physical partitions from one
physical volume to other(s).
mkvg smit mkvg Creates a volume group.
lsvg smit lsvg Lists information about volume groups.
reducevg smit reducevg Removes a physical volume from a
volume group.
chvg smit chvg Changes the characteristics of a volume
importvg smit importvg Imports the definition of a volume group
into the system.
exportvg smit exportvg Removes the definition of a volume
group from the system.
varyonvg smit varyonvg Activates a volume group.
varyoffvg smit varyoffvg Deactivates a volume group.
mklv smit mklv Creates a logical volume.
lslv smit lslv Lists information about a logical volume.
chlv smit chlv Changes the characteristics of a logical
volume.
rmlv smit rmlv Deletes a logical volume.
extendlv smit extendlv Extends a logical volume.
mklvcopy smit mklvcopy Creates a copy of a logical volume.
rmlvcopy smit rmlvcopy Removes a copy of a logical volume.
AIX CLUSTERING STEPS BASIC
HACMP Configuration
Cluster Name: xxxxxxx
Participating Nodes : ddcappip00 ddcappip50
Resource Groups in new cluster : ddcapedn01 ddcapedn02 ednpdtu2 ednpdtu1
Application Servers in new cluster : ednpdtu2_oradb01 ednpdtu1_oradb01
Boot IP’s - ddcappip00 -> ddcappip00-man ddcappip00-bt01
ddcappip50 -> ddcappip50-man ddcappip50-bt01
Persistant IP’s - ddcappip00 -> ddcappip00-pers.tu.com
ddcappip50 -> ddcappip50-pers.tu.com
service ip - ddcappip00 ddcappip50 ddcappip50-rg01 ddcappip00-rg01
Other detailes
RG
Participating nodes
serviceip
VG
Application server
ddcapedn01
ddcappip00
ddcappip00
ddcapedn02
ddcappip50
ddcappip50
ednpdtu2
ddcappip50
ddcappip50-rg01
ednpdtu200vg
ednpdtu2_oradb01
ddcappip00
ednpdtu1
ddcappip00
ddcappip00-rg01
ednpdtu100vg
ednpdtu1_oradb01
ddcappip50
ednpdtu6
ddcapedn01
ddcapedn02-rg02
ednpdtu601vg
ednpdtu6_oradb01
ddcapedn02
The RG ednpdtu6 is not going to be migrated
prerequisite:-
1.Check ML level
Oslevel –r
If ML level is not up to date update ML to the required level
2. Insatll HACMP Filesets
Lslpp –Lgrep cluster
smitty install_all
minimum filesets required
cluster.es
cluster.es.cspoc
cluster.lisence
cluster.man.enus.es
cluster.adt.es
Make sure that the node is rebooted after HACMP file set Installation –Mandatory
Since we have taken MKSYSB first two steps not necessary in migration
Verify Appropriate Network Configuration :
To Add the service address to boot interface initially before HACMP
configuration is completed run the following command.
ifconfig en4 146.61.61.62 netmask 255.255.255.0 alias
Add Default Route for system:
mkdev -l inet0
mkdev -l en4
Verify network configuration.
ddcappip00:/#netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
en4 1500 link#2 0.14.5e.c7.f8.16 737377057 0 8116327 5 0
en4 1500 192.168.38 192.168.38.40 737377057 0 8116327 5 0 -- Boot IP
en4 1500 146.61.61 146.61.61.60 737377057 0 8116327 5 0 -- Per IP
en4 1500 146.61.61 146.61.61.62 737377057 0 8116327 5 0 -- Ser IP
en5 1500 link#3 0.14.5e.c7.f8.17 0 0 2043438 2043438 0
en5 1500 192.168.38 192.168.38.41 0 0 2043438 2043438 0 – Boot IP
en5 1500 146.61.68 146.61.68.216 0 0 2043438 2043438 0 – Man IP
lo0 16896 link#1 1223825 0 1477747 0 0
lo0 16896 127 127.0.0.1 1223825 0 1477747 0 0
lo0 16896 ::1 1223825 0 1477747 0 0
ddcappip00:/#
Remove Old HACMP configurations :
smitty hacmp -->
Extended Configuration -->
Extended Topology Configuration -->
Configure an HACMP Cluster -->
Remove an HACMP Cluster
Configure Various HACMP Required Files :
/etc/hosts :
146.61.61.61 ddcappip00.tu.com ddcappip00
192.168.38.40 ddcappip00-bt01.tu.com ddcappip00-bt01
192.168.38.41 ddcappip00-bt02.tu.com ddcappip00-bt02
146.61.68.216 ddcappip00-man.tu.com ddcappip00-man
146.61.61.60 ddcappip00-pers.tu.com ddcappip00-pers
146.61.61.62 ddcappip00-rg01.tu.com ddcappip00-rg01
146.61.61.67 ddcappip01.tu.com ddcappip01
192.168.38.44 ddcappip01-bt01.tu.com ddcappip01-bt01
192.168.38.45 ddcappip01-bt02.tu.com ddcappip01-bt02
146.61.68.218 ddcappip01-man.tu.com ddcappip01-man
146.61.61.66 ddcappip01-pers.tu.com ddcappip01-pers
146.61.61.68 ddcappip01-rg01.tu.com ddcappip01-rg01
146.61.61.70 ddcappip02.tu.com ddcappip02
192.168.38.46 ddcappip02-bt01.tu.com ddcappip02-bt01
192.168.38.47 ddcappip02-bt02.tu.com ddcappip02-bt02
146.61.68.219 ddcappip02-man.tu.com ddcappip02-man
146.61.61.69 ddcappip02-pers.tu.com ddcappip02-pers
146.61.61.71 ddcappip02-rg01.tu.com ddcappip02-rg01
146.61.61.73 ddcappip03.tu.com ddcappip03
192.168.38.48 ddcappip03-bt01.tu.com ddcappip03-bt01
192.168.38.49 ddcappip03-bt02.tu.com ddcappip03-bt02
146.61.68.220 ddcappip03-man.tu.com ddcappip03-man
146.61.61.72 ddcappip03-pers.tu.com ddcappip03-pers
146.61.61.74 ddcappip03-rg01.tu.com ddcappip03-rg01
146.61.61.64 ddcappip50.tu.com ddcappip50
192.168.38.42 ddcappip50-bt01.tu.com ddcappip50-bt01
192.168.38.43 ddcappip50-bt02.tu.com ddcappip50-bt02
146.61.68.217 ddcappip50-man.tu.com ddcappip50-man
146.61.61.63 ddcappip50-pers.tu.com ddcappip50-pers
146.61.61.65 ddcappip50-rg01.tu.com ddcappip50-rg01
/.rhosts :
ddcappip00.tu.com root
ddcappip00-bt01.tu.com root
ddcappip00-bt02.tu.com root
ddcappip00-man.tu.com root
ddcappip00-pers.tu.com root
ddcappip00-rg01.tu.com root
ddcappip50.tu.com root
ddcappip50-bt01.tu.com root
ddcappip50-bt02.tu.com root
ddcappip50-man.tu.com root
ddcappip50-pers.tu.com root
ddcappip50-rg01.tu.com root
/usr/es/sbin/cluster/etc/rhosts :
service address and boot address for participating nodes in cluster.
/usr/es/sbin/cluster/etc/netmon.cf :
ddcappip00-bt01
ddcappip00-bt02
ddcappip00-rg01
ddcappip01-bt01
ddcappip01-bt02
ddcappip01-rg01
ddcappip50-bt01
ddcappip50-bt02
ddcappip50-rg01
Test rsh functionality between nodes.
Use boot address to rsh to and from clustered pairs.
cluster configuration
Add Nodes To Cluster Configuration :
Initialization and Standard Configuration -->
Add Nodes to an HACMP Cluster -->
cluster name "xxxxxx"
New Nodes "ddcappip00 ddcappip50"
( Service Names )
Service Labels :
Initialization and Standard Configuration -->
Configure Resources to Make Highly Available -->
Configure Service IP Labels/Addresses -->
Add a Service IP Label/Address -->
IP Label Address "ddcappip00.tu.com"
(Service hostname)
Network Name "net_ether_01"
(Boot Label 192.168.xx.xx)
***** Perform Twice, Next ddcappip50.tu.com Service Label.
Add Persistence Labels :
Extended Configuration -->
Extended Topology Configuration -->
Configure HACMP Persistent Node IP Label/Addresses -->
Add a Persistent Node IP Label/Address -->
Select Node "ddcappip00"
Network Name "net_ether_01"
( Persistence Network Label )
Node IP Label/Address "ddcappip00-pers.tu.com"
( Persistence Node Label )
***** Perform Twice, Next ddcappip50-pers.tu.com Persistence Label.
Synchronize Cluster configuration :
Extended Configuration -->
Extended Verification and Synchronization -->
Automatically correct errors found "yes"
( Correct Timestamp for HACMP file. )
***** Accept other defaults and synchronize cluster.
Create Volume Groups and File systems On Systems:
Create Resource Groups :
Extended Configuration -->
Extended Resource Configuration -->
HACMP Extended Resource Group Configuration -->
Add a Resource Group -->
Enter RG Name for Service Labels "ddcappip00"
Participating Nodes "ddcappip00 ddcappip50"
( Priority Order of Nodes for the group )
***** Accept defaults for additional fields.
Enter RG Name for Volume groups "ednpdtu100vg"
Participating Nodes "ddcappip00 ddcappip50"
( Priority Order of Nodes for the group )
Add Application Server :
***** Perform these steps for application servers only.
Initialization and Standard Configuration -->
Configure Resources to Make Highly Available -->
Configure Application Servers -->
Add an Application Server -->
Enter APP SERVER RG Name "ednpdtu1_oradb01"
Enter Start Script "/usr/local/hascripts/ednpdtu1_oradb01_start.sh"
Enter Stop Script "/usr/local/hascripts/ednpdtu1_oradb01_stop.sh"
( Application Start and Stop Scripts )
Configure Attributes for New Resource Groups :
Extended Configuration -->
Extended Resource Configuration -->
Extended Resource Group Configuration -->
Change/Show Resources and Attributes for a Resource Group -->
Select RG "ednpdtu1"
Enter Service IP Labels "ednpdtu1"
( Failover of Serve IP for RG )
Select RG "ednpdtu1"
Enter Application Server "ednpdtu1_oradb01"
Enter Volume Groups "ednpdtu100vg"
( Failover of VG's )
Synchronize Cluster configuration :
Extended Configuration -->
Extended Verification and Synchronization -->
***** Accept defaults and synchronize cluster.
Discover HACMP-related Information from Clustered Nodes :
Discover HACMP-related Information from Configured Nodes
( Collect disk info for Disk Heartbeat Configuration etc ........ )
Disk/Serial Heartbeat Configuration/ : ( yet to be decided )
Extended Configuration -->
Extended Topology Configuration -->
Configure HACMP Communication Interfaces/Devices -->
Add Communication Interfaces/Devices -->
Select "Add Discovered Communication Interface and Devices"
Select "Communication Devices"
Select 1 Disk from each Node /LPAR "ddcappip00 ddcappip50"
***** Configure Disk Heartbeat for all VG in cluster.
Synchronize Cluster configuration :
Extended Configuration -->
Extended Verification and Synchronization -->
***** Accept defaults and synchronize cluster.
---------------------------------------------------------------------------------
Resource group
Participating nodes in the order of priority
Startup Policy
Fallover Policy
Fallback Policy
I
ddcapedn01
ddcapedn01
Online On Home Node Only
Fallover To Next Priority Node In The List
Fallback To Higher Priority Node In The List
II
ddcapedn02
ddcapedn02
Online On Home Node Only
Fallover To Next Priority Node In The List
Fallback To Higher Priority Node In The List
III
ednpdtu1
ddcapedn01 ddcapedn02
Online On Home Node Only
Fallover To Next Priority Node In The List
Never Fallback
IV
ednpdtu2
ddcapedn02 ddcapedn01
Online On Home Node Only
Fallover To Next Priority Node In The List
Never Fallback
-------------------------------------
application server
scripts
application monitor name
ednpdtu1_oradb01
start /usr/local/hascripts/ednpdtu1_oradb01_start.sh stop /usr/local/hascripts/ednpdtu1_oradb01_stop.sh
No monitoring
ednpdtu2_oradb01
start /usr/local/hascripts/ednpdtu2_oradb01_start.sh stop /usr/local/hascripts/ednpdtu2_oradb01_stop.sh
No monitoring
RG
Participating nodes
Service ip
VG
Application server
ddcapedn01
ddcappip00
ddcappip00
ddcapedn02
ddcappip50
ddcappip50
ednpdtu2
ddcappip50
ddcappip50-rg01
ednpdtu200vg
ednpdtu2_oradb01
ddcappip00
ednpdtu1
ddcappip00
ddcappip00-rg01
ednpdtu100vg
ednpdtu1_oradb01
ddcappip50
Cluster Name: xxxxxxx
Participating Nodes : ddcappip00 ddcappip50
Resource Groups in new cluster : ddcapedn01 ddcapedn02 ednpdtu2 ednpdtu1
Application Servers in new cluster : ednpdtu2_oradb01 ednpdtu1_oradb01
Boot IP’s - ddcappip00 -> ddcappip00-man ddcappip00-bt01
ddcappip50 -> ddcappip50-man ddcappip50-bt01
Persistant IP’s - ddcappip00 -> ddcappip00-pers.tu.com
ddcappip50 -> ddcappip50-pers.tu.com
service ip - ddcappip00 ddcappip50 ddcappip50-rg01 ddcappip00-rg01
Other detailes
RG
Participating nodes
serviceip
VG
Application server
ddcapedn01
ddcappip00
ddcappip00
ddcapedn02
ddcappip50
ddcappip50
ednpdtu2
ddcappip50
ddcappip50-rg01
ednpdtu200vg
ednpdtu2_oradb01
ddcappip00
ednpdtu1
ddcappip00
ddcappip00-rg01
ednpdtu100vg
ednpdtu1_oradb01
ddcappip50
ednpdtu6
ddcapedn01
ddcapedn02-rg02
ednpdtu601vg
ednpdtu6_oradb01
ddcapedn02
The RG ednpdtu6 is not going to be migrated
prerequisite:-
1.Check ML level
Oslevel –r
If ML level is not up to date update ML to the required level
2. Insatll HACMP Filesets
Lslpp –Lgrep cluster
smitty install_all
minimum filesets required
cluster.es
cluster.es.cspoc
cluster.lisence
cluster.man.enus.es
cluster.adt.es
Make sure that the node is rebooted after HACMP file set Installation –Mandatory
Since we have taken MKSYSB first two steps not necessary in migration
Verify Appropriate Network Configuration :
To Add the service address to boot interface initially before HACMP
configuration is completed run the following command.
ifconfig en4 146.61.61.62 netmask 255.255.255.0 alias
Add Default Route for system:
mkdev -l inet0
mkdev -l en4
Verify network configuration.
ddcappip00:/#netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
en4 1500 link#2 0.14.5e.c7.f8.16 737377057 0 8116327 5 0
en4 1500 192.168.38 192.168.38.40 737377057 0 8116327 5 0 -- Boot IP
en4 1500 146.61.61 146.61.61.60 737377057 0 8116327 5 0 -- Per IP
en4 1500 146.61.61 146.61.61.62 737377057 0 8116327 5 0 -- Ser IP
en5 1500 link#3 0.14.5e.c7.f8.17 0 0 2043438 2043438 0
en5 1500 192.168.38 192.168.38.41 0 0 2043438 2043438 0 – Boot IP
en5 1500 146.61.68 146.61.68.216 0 0 2043438 2043438 0 – Man IP
lo0 16896 link#1 1223825 0 1477747 0 0
lo0 16896 127 127.0.0.1 1223825 0 1477747 0 0
lo0 16896 ::1 1223825 0 1477747 0 0
ddcappip00:/#
Remove Old HACMP configurations :
smitty hacmp -->
Extended Configuration -->
Extended Topology Configuration -->
Configure an HACMP Cluster -->
Remove an HACMP Cluster
Configure Various HACMP Required Files :
/etc/hosts :
146.61.61.61 ddcappip00.tu.com ddcappip00
192.168.38.40 ddcappip00-bt01.tu.com ddcappip00-bt01
192.168.38.41 ddcappip00-bt02.tu.com ddcappip00-bt02
146.61.68.216 ddcappip00-man.tu.com ddcappip00-man
146.61.61.60 ddcappip00-pers.tu.com ddcappip00-pers
146.61.61.62 ddcappip00-rg01.tu.com ddcappip00-rg01
146.61.61.67 ddcappip01.tu.com ddcappip01
192.168.38.44 ddcappip01-bt01.tu.com ddcappip01-bt01
192.168.38.45 ddcappip01-bt02.tu.com ddcappip01-bt02
146.61.68.218 ddcappip01-man.tu.com ddcappip01-man
146.61.61.66 ddcappip01-pers.tu.com ddcappip01-pers
146.61.61.68 ddcappip01-rg01.tu.com ddcappip01-rg01
146.61.61.70 ddcappip02.tu.com ddcappip02
192.168.38.46 ddcappip02-bt01.tu.com ddcappip02-bt01
192.168.38.47 ddcappip02-bt02.tu.com ddcappip02-bt02
146.61.68.219 ddcappip02-man.tu.com ddcappip02-man
146.61.61.69 ddcappip02-pers.tu.com ddcappip02-pers
146.61.61.71 ddcappip02-rg01.tu.com ddcappip02-rg01
146.61.61.73 ddcappip03.tu.com ddcappip03
192.168.38.48 ddcappip03-bt01.tu.com ddcappip03-bt01
192.168.38.49 ddcappip03-bt02.tu.com ddcappip03-bt02
146.61.68.220 ddcappip03-man.tu.com ddcappip03-man
146.61.61.72 ddcappip03-pers.tu.com ddcappip03-pers
146.61.61.74 ddcappip03-rg01.tu.com ddcappip03-rg01
146.61.61.64 ddcappip50.tu.com ddcappip50
192.168.38.42 ddcappip50-bt01.tu.com ddcappip50-bt01
192.168.38.43 ddcappip50-bt02.tu.com ddcappip50-bt02
146.61.68.217 ddcappip50-man.tu.com ddcappip50-man
146.61.61.63 ddcappip50-pers.tu.com ddcappip50-pers
146.61.61.65 ddcappip50-rg01.tu.com ddcappip50-rg01
/.rhosts :
ddcappip00.tu.com root
ddcappip00-bt01.tu.com root
ddcappip00-bt02.tu.com root
ddcappip00-man.tu.com root
ddcappip00-pers.tu.com root
ddcappip00-rg01.tu.com root
ddcappip50.tu.com root
ddcappip50-bt01.tu.com root
ddcappip50-bt02.tu.com root
ddcappip50-man.tu.com root
ddcappip50-pers.tu.com root
ddcappip50-rg01.tu.com root
/usr/es/sbin/cluster/etc/rhosts :
service address and boot address for participating nodes in cluster.
/usr/es/sbin/cluster/etc/netmon.cf :
ddcappip00-bt01
ddcappip00-bt02
ddcappip00-rg01
ddcappip01-bt01
ddcappip01-bt02
ddcappip01-rg01
ddcappip50-bt01
ddcappip50-bt02
ddcappip50-rg01
Test rsh functionality between nodes.
Use boot address to rsh to and from clustered pairs.
cluster configuration
Add Nodes To Cluster Configuration :
Initialization and Standard Configuration -->
Add Nodes to an HACMP Cluster -->
cluster name "xxxxxx"
New Nodes "ddcappip00 ddcappip50"
( Service Names )
Service Labels :
Initialization and Standard Configuration -->
Configure Resources to Make Highly Available -->
Configure Service IP Labels/Addresses -->
Add a Service IP Label/Address -->
IP Label Address "ddcappip00.tu.com"
(Service hostname)
Network Name "net_ether_01"
(Boot Label 192.168.xx.xx)
***** Perform Twice, Next ddcappip50.tu.com Service Label.
Add Persistence Labels :
Extended Configuration -->
Extended Topology Configuration -->
Configure HACMP Persistent Node IP Label/Addresses -->
Add a Persistent Node IP Label/Address -->
Select Node "ddcappip00"
Network Name "net_ether_01"
( Persistence Network Label )
Node IP Label/Address "ddcappip00-pers.tu.com"
( Persistence Node Label )
***** Perform Twice, Next ddcappip50-pers.tu.com Persistence Label.
Synchronize Cluster configuration :
Extended Configuration -->
Extended Verification and Synchronization -->
Automatically correct errors found "yes"
( Correct Timestamp for HACMP file. )
***** Accept other defaults and synchronize cluster.
Create Volume Groups and File systems On Systems:
Create Resource Groups :
Extended Configuration -->
Extended Resource Configuration -->
HACMP Extended Resource Group Configuration -->
Add a Resource Group -->
Enter RG Name for Service Labels "ddcappip00"
Participating Nodes "ddcappip00 ddcappip50"
( Priority Order of Nodes for the group )
***** Accept defaults for additional fields.
Enter RG Name for Volume groups "ednpdtu100vg"
Participating Nodes "ddcappip00 ddcappip50"
( Priority Order of Nodes for the group )
Add Application Server :
***** Perform these steps for application servers only.
Initialization and Standard Configuration -->
Configure Resources to Make Highly Available -->
Configure Application Servers -->
Add an Application Server -->
Enter APP SERVER RG Name "ednpdtu1_oradb01"
Enter Start Script "/usr/local/hascripts/ednpdtu1_oradb01_start.sh"
Enter Stop Script "/usr/local/hascripts/ednpdtu1_oradb01_stop.sh"
( Application Start and Stop Scripts )
Configure Attributes for New Resource Groups :
Extended Configuration -->
Extended Resource Configuration -->
Extended Resource Group Configuration -->
Change/Show Resources and Attributes for a Resource Group -->
Select RG "ednpdtu1"
Enter Service IP Labels "ednpdtu1"
( Failover of Serve IP for RG )
Select RG "ednpdtu1"
Enter Application Server "ednpdtu1_oradb01"
Enter Volume Groups "ednpdtu100vg"
( Failover of VG's )
Synchronize Cluster configuration :
Extended Configuration -->
Extended Verification and Synchronization -->
***** Accept defaults and synchronize cluster.
Discover HACMP-related Information from Clustered Nodes :
Discover HACMP-related Information from Configured Nodes
( Collect disk info for Disk Heartbeat Configuration etc ........ )
Disk/Serial Heartbeat Configuration/ : ( yet to be decided )
Extended Configuration -->
Extended Topology Configuration -->
Configure HACMP Communication Interfaces/Devices -->
Add Communication Interfaces/Devices -->
Select "Add Discovered Communication Interface and Devices"
Select "Communication Devices"
Select 1 Disk from each Node /LPAR "ddcappip00 ddcappip50"
***** Configure Disk Heartbeat for all VG in cluster.
Synchronize Cluster configuration :
Extended Configuration -->
Extended Verification and Synchronization -->
***** Accept defaults and synchronize cluster.
---------------------------------------------------------------------------------
Resource group
Participating nodes in the order of priority
Startup Policy
Fallover Policy
Fallback Policy
I
ddcapedn01
ddcapedn01
Online On Home Node Only
Fallover To Next Priority Node In The List
Fallback To Higher Priority Node In The List
II
ddcapedn02
ddcapedn02
Online On Home Node Only
Fallover To Next Priority Node In The List
Fallback To Higher Priority Node In The List
III
ednpdtu1
ddcapedn01 ddcapedn02
Online On Home Node Only
Fallover To Next Priority Node In The List
Never Fallback
IV
ednpdtu2
ddcapedn02 ddcapedn01
Online On Home Node Only
Fallover To Next Priority Node In The List
Never Fallback
-------------------------------------
application server
scripts
application monitor name
ednpdtu1_oradb01
start /usr/local/hascripts/ednpdtu1_oradb01_start.sh stop /usr/local/hascripts/ednpdtu1_oradb01_stop.sh
No monitoring
ednpdtu2_oradb01
start /usr/local/hascripts/ednpdtu2_oradb01_start.sh stop /usr/local/hascripts/ednpdtu2_oradb01_stop.sh
No monitoring
RG
Participating nodes
Service ip
VG
Application server
ddcapedn01
ddcappip00
ddcappip00
ddcapedn02
ddcappip50
ddcappip50
ednpdtu2
ddcappip50
ddcappip50-rg01
ednpdtu200vg
ednpdtu2_oradb01
ddcappip00
ednpdtu1
ddcappip00
ddcappip00-rg01
ednpdtu100vg
ednpdtu1_oradb01
ddcappip50
Subscribe to:
Posts (Atom)