Archive

Monthly Archives: February 2012

Here I will describe how to create a mksysb image of a NIM client from the NIM server using the cli and afterwards we will create a SPOT from the newly created mksysb.

So firt we define the new mksysb:

# nim -o define -t mksysb -a server=master -a location=/export2/mksysb/P2_1202_TL7.mk -a mk_image=yes -a source=power2 P2_1202_TL7_mk

+---------------------------------------------------------------------+
                System Backup Image Space Information
              (Sizes are displayed in 1024-byte blocks.)
+---------------------------------------------------------------------+

Required = 3774349 (3686 MB)    Available = 5288840 (5165 MB)

Creating information file (/image.data) for rootvg..

Creating list of files to back up
..
Backing up 68372 files..............................
55742 of 68372 files backed up (81%)................

68372 of 68372 files backed up (100%)
0512-038 savevg: Backup Completed Successfully.


-o Operation
-t Type
-a Atributes

Read More

lquerypv can read the PVID directly from the disk:

# lquerypv -h /dev/hdisk0 80 10
00000080   00C4489D 5E6002A5 00000000 00000000  |..H.^`..........|

# lspv
hdisk0          00c4489d5e6002a5                    rootvg          active    

And also the VGDA:

 lqueryvg -Atvp hdisk0 
Max LVs:        256
PP Size:        27
Free PPs:       766
LV count:       12
PV count:       2
Total VGDAs:    3
Conc Allowed:   0
MAX PPs per PV: 1016
MAX PVs:        32
Quorum (disk):  0
Quorum (dd):    0
Auto Varyon ?:  1
Conc Autovaryon 0
Varied on Conc: 0
Logical:        00c4489d00004c00000001354404cb5c.2   hd6 1  
                00c4489d00004c00000001354404cb5c.3   hd5 1  
                00c4489d00004c00000001354404cb5c.4   hd8 1  
                00c4489d00004c00000001354404cb5c.5   hd3 1  
                00c4489d00004c00000001354404cb5c.6   hd1 1  
                00c4489d00004c00000001354404cb5c.7   hd11admin 1  
                00c4489d00004c00000001354404cb5c.8   livedump 1  
                00c4489d00004c00000001354404cb5c.13  fslv00 1  
                00c4489d00004c00000001354404cb5c.14  hd4 1  
                00c4489d00004c00000001354404cb5c.15  hd2 1  
                00c4489d00004c00000001354404cb5c.16  hd9var 1  
                00c4489d00004c00000001354404cb5c.17  hd10opt 1  
Physical:       00c4489d5e6002a5                1   0  
                00cf405e3e792147                2   0  
VGid:           00c4489d00004c00000001354404cb5c
Total PPs:      1092
LTG size:       128
HOT SPARE:      0
AUTO SYNC:      0
VG PERMISSION:  0
SNAPSHOT VG:    0
IS_PRIMARY VG:  0
PSNFSTPP:       4352
VARYON MODE:    0
VG Type:        0
Max PPs:        32512
Mirror Pool Str n
Sys Mgt Mode:   0
VG Reserved:    1
PV RESTRICTION: 0
Infinite Retry: 2

To find out which application crashed the OS use:

# /usr/sbin/lquerypv -h /path/to/core 6b0 64

To show the current paging space volume, its size along with other information use the ‘lsps’ command:

#lsps -a
Page Space      Physical Volume   Volume Group    Size %Used Active Auto   Type Chksum
hd6             hdisk1            rootvg        1024MB     1   yes   yes    lv     0

The paging space may be increased on the fly using the ‘chps’ command. In order to increase this paging space to 2 GB we need to to find out the PP size, since chps will increase the paging space by the specified number of PP’s

# lslv hd6
LOGICAL VOLUME:     hd6                    VOLUME GROUP:   rootvg
LV IDENTIFIER:      00c4489d00004c00000001354404cb5c.2 PERMISSION:     read/write
VG STATE:           active/complete        LV STATE:       opened/syncd
TYPE:               paging                 WRITE VERIFY:   off
MAX LPs:            512                    PP SIZE: 128 megabyte(s)
COPIES:             2                      SCHED POLICY:   parallel
LPs:                8                      PPs:            16
STALE PPs:          0                      BB POLICY:      non-relocatable
INTER-POLICY:       minimum                RELOCATABLE:    yes
INTRA-POLICY:       center                 UPPER BOUND:    32
MOUNT POINT:        N/A                    LABEL:          None
MIRROR WRITE CONSISTENCY: off
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?:     NO
INFINITE RETRY:     no

On this system is the PP size 128M so in order to increase the paging space size to 2Gig we need 8 PP’s

 
# chps -s 8 hd6
# lsps -a
Page Space      Physical Volume   Volume Group    Size %Used Active Auto   Type Chksum
hd6             hdisk1            rootvg        2048MB     1   yes   yes    lv     0

Microcode Discovery Service in short MDS enables in conjunction with the invscout AIX tool to survey your system for the installed microcode levels on devices such as network adapters, HBA’s, HDD’s etc., and also the system (service procesor) microcode itself. The collected information from the invscout tool is exported to a file. This file can be uploaded to the MDS website which generates a simple report with an overview of the microcode levels of your devices and the current/latest microcode levels. Also for each device and his microcode level there is a coresponding readme file and a download link for the microcode.

In this post I will describe the microcode update procedure on a scsi adapter using the MDS and invscout.
Read More

This post will describe the replacement of a failed rootvg disk.

In short the procedure is the following:

1. unmirrorvg rootvg hdisk0
(savebase -v)
2. reducevg rootvg hdisk0
3. rmdev -Rdl hdisk0
4. diag (safely remove hot swap device/drive), physically remove the old disk
5. insert the new disk (diag – hotplug task)
6. cfgmgr -vl scsi0
7. extendvg -f rootvg hdisk0
8. mirrorvg -m rootvg hdisk0
9. bosboot -ad hdisk0
10. bootlist -m normal hdisk0 hdisk1
11. bootlist -m normal -o

In more detail the procedure is described below starting with the errpt logs indicating a drive problem.
Read More

AIX offers tools that allow the administrator to change configration files without editing them directly, thus reducing the possibility of causing a service outage caused by a typo in the configuration file, as described in more detail here.

In this example I have a NFS client with a filesystem mounted from the server cosmos in order to change the mount options so that the filesystem is mounted with the options soft and bg (background) I use the following command instead of directly editing /etc/filesystems.

# chnfsmnt -f /cosmos -d /strom -h cosmos -w bg -S

-f Local mount point
-d Remote direcoty
-h Remote host name
-w fg/bg
-S Makes the mount a soft mount
Read More

In this post I will describe a TL upgrade using multibos on AIX 6.1. The system will be moved from 6100-04 to 6100-07 (TL4 to TL7).

1. Create a separate filesystem for the updates
2. Create a backup of the system
3. Check current TL level
4. Preview/Create the multibos standby BOS instance.
5. Preview/Patch the OS in the standby instance
6. Verify the oslevel in the standby instance after the update
7. Reboot and check
8. Optionally return to the pre-update BOS image.
Read More