You can identify hot spot problems with your logical volumes and remedy those problems without interrupting the use of your system. A hot-spot problem occurs when some of the logical partitions on your disk have so much disk I/O that your system performance noticeably suffers. The first step toward solving the problem is to identify […]
Aix: Hot spot management in logical volumes Read More »
1. Overview The High Availability (HA) feature of application allows a properly configured application system to automatically recover from a number of possible failures, with the goal of eliminating all single points of failure in the system. The same functionality can be used to minimize the impact of regularly scheduled maintenance and/or software upgrades. The
Aix: Install and Configuration HACMP [ Overview] Read More »
minute (0-59), | hour (0-23), | | day of the month (1-31), | | | month of the year (1-12), | | | | day of the week (0-6 with 0=Sunday). | | | | | command 0 2 * * 0,4 /etc/cron.d/logchecker
Solaris : memconf – memconf reports the size of each SIMM/DIMM memory module installed in a system. It also reports the system type and any empty memory sockets. In verbose mode, it also reports information of banner name, model, CPU/system frequencies, address range and bank numbers for each module. Usage: memconf [ -v | -D
How to Get Size of Memory DIMMs on AIX / Solaris / HP-UX / Linux ? Read More »
If you remove a disk from the system using rmdev -dl hdiskX without having previously reduced the volume group to remove the disk from LVM, and thus have not updated properly the on-disk format information (called VGDA), you get a discrepancy between the ODM and the LVM configurations. Here is how to solve the issue
Altering LVM Configuration When a Disk is Not in ODM Anymore Read More »
1. mkszfile 2. Edit /image.data and add in multiple copies -in the lv_data section change COPIES = 2 or each lv (might be some other fields to change – compare a mirrored to a non-mirrored lv to check). ##Command used for lv_data; /usr/sbin/lslv lv_data: VOLUME_GROUP= rootvg LV_SOURCE_DISK_LIST= hdisk0 LV_IDENTIFIER= 00075ef10000d60000000119e75995ad.1 LOGICAL_VOLUME=
Aix mirror rootvg during System Restore Read More »
[root@sunx4150 ~]# cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 10.1.50.101 sunx4150.xyz.com localhost.localdomain localhost 127.0.0.1 sunx4150.xyz.com localhost.localdomain localhost 10.0.51.50 T5220 T5220.xyz.com 10.0.50.36 ibmaix ibmaix.xyz.com 10.0.50.9 bucnodc01.xyz.com 10.0.50.36 ibmaix.xyz.com ibmaix 10.1.50.106 ibmcl03.xyz.com ibmcl03 10.1.51.83 nnl106.xyz.com 10.1.50.134 dbcimb01 10.0.2.20 bkonetapp1 10.112.2.101 spblrdc010 10.0.2.11 bpelapp1 [root@sunx4150 ~]#
Unix Sort by IP Address Read More »
# mount /dev/fslv00 /test mount: 0506-322 Cannot determine log device to use for /dev/fslv00 (/test). Solution : Just create another logical volume in datavg vg with a size of one (1) PP. # mklv -t jfs2log -y <yournewloglv>datavg vg 1 # logform /dev/<yournewloglv> Any filesystem that is created in datavg vg after this step will
mount: 0506-322 Cannot determine log device to use for /dev/fslv Read More »
ibmcl01 is the hostname of the LPAR… which is a VIOC too oravg is the name of volume group which resides on the SAN disks impacted by the export/reimport Assuming that we want to migrate, on a VIOC, one or more currently SAN disks attached on a local fibre channel adapter to the same one
Aix: Export and Import a Volume Group After System Crash Read More »
Today vi is considered the standard. It is the only editor that will be installed by default on any UNIX system. It is small, fast and efficient; useful to make some minor editing of system files, editing of huge data files or when a slow network link is involved. It is important to learn at
How to use Unix Editor Vi (Vim) Read More »