Tuesday, 16 October 2012

how to install relocatable packages on AIX


how to install relocatable packages on AIX

1. create Volumegroup, filesystem and directory

2. create relocation path (the path that should be used instead of the ./) This can be any valid path that
is not "/" and has a size no greater than 512 characters
mkusil -R <desired_path>

3. check if location is properly created
lsusil -R ALL

4. copy packages to be installed into any folder on the box and perform inutoc_r

5. install required packages using installp_r -R
installp_r -R <desired_path> -ad <package_location> <rte package name>

6. check if installation had been successful
lslpp_r -R ALL -Lc




availabel commands:

mkusil -R creates a relocation path - Usage: mkusil -R <RelocatePath> -c <Comments> [XFa]
-a = Attach an existing installation as a USIL instance
-c = Comments to include in the USIL definition (visible with lsusil)
-R = Path to new USIL location. Must be valid directory.
-X = Automatically expand of space needed


lsusil -R lists available relocation paths - Usage: lsusil [-R <RelocatePath> | "ALL"]
-R = Path to existing USIL location.


rmusil -R removes relocation path - Usage: rmusil -R <RelocatePath>
-R = Path to existing USIL location.

chusil -R changes an attribute of an existing USIL instance - Usage: chusil -R <RelocatePath> -c <NewComments> [X]
-c = New comments to include in the USIL definition (visible with lsusil)
-R = Path to existing USIL location.
-X = Automatically expand of space needed

inutoc_r creates .toc file
inulag_r manages license agreements
instfix_r installs filesets associated with keywords or fixes
installp_r installs files into relocation path
lppchk_r verifies files of an installable software product
lslpp_r lists files

AIX Error logging


 AIX Error logging

To display a complete summary report, enter:
errpt

To display a complete detailed report, enter:
errpt -a

To display a detailed report of all errors logged for the error identifier E19E094F, enter:
errpt -a -j E19E094F

To list error-record templates for which logging is turned off for any error-log entries, enter:
errpt -t -F log=0

To view all entries from the alternate error-log file /var/adm/ras/errlog.alternate, enter:
errpt -i /var/adm/ras/errlog.alternate

To view all hardware entries from the error-log file enter:
errpt -d H

To view all software entries from the error-log file enter:
errpt -d S

To display a detailed report of all errors logged for the error label ERRLOG_ON, enter:
errpt -a -J ERRLOG_ON

To display a detailed report of all errors and group duplicate errors, enter:
errpt -aD

To display the error-record template repository, enter:
errpt -t

To disable the reporting of the ERRLOG_OFF event (error ID 192AC071), type the following:
errupdate <Enter>
=192AC071: <Enter>
Report=False <Enter>
<Ctrl-D>
<Ctrl-D>

To enable the reporting of the ERRLOG_OFF event (error ID 192AC071) in case it was turned off, type the following:
errupdate <Enter>
=192AC071: <Enter>
Report=True <Enter>
<Ctrl-D>
<Ctrl-D>

To delete the ERRLOG_OFF event (error ID 192AC071) from the Error Record Template Repository, type the following:
errupdate <Enter>
-192AC071:
<Ctrl-D>
<Ctrl-D>

To disable the logging of the ERRLOG_OFF event (error ID 192AC071), type the following:
errupdate <Enter>
=192AC071: <Enter>
Log=False <Enter>
<Ctrl-D>
<Ctrl-D>

To delete all entries from the error log, enter:
errclear 0

To delete all entries from the error log older than 3 days, enter:
errclear 3

To create an operator message for system drive reconfiguration, enter:
errlogger system drive reconfigured

To delete all entries in the error log classified as software errors, enter:
errclear -d S 0

To clear all entries from the alternate error-log file /var/adm/ras/errlog.alternate, enter:
errclear -i /var/adm/ras/errlog.alternate 0

Removing ODM information of a logical volume


Removing ODM information of a logical volume

Sometimes situations occur where a logical volume is deleted, but the ODM is not up to date. E.g. when lsvg doesn't show you the logical volume, but the lslv command can still show information about the logical volume.

To resolve this issue, first try: synclvodm -v [volume group name].

If this doesn't work, try this: (in the example below logical volume hd7 is used)

Save the ODM information of the logical volume:
odmget -q name=hd7 CuDv | tee -a /tmp/CuDv.hd7.out
odmget -q name=hd7 CuAt | tee -a /tmp/CuAt.hd7.out
(If you mess things up, you can allways use odmadd /tmp/[filename] to restore the ODM information).

Delete the ODM information of the logical volume:
odmdelete -o CuDv -q name=hd7
odmdelete -o CuAt -q name=hd7

Then, remove the device entry of the logical volume in /dev directory (if present at all)

change hostname on AIX


How to change hostname on AIX, “Cleanly”

Changing the hostname at a Windows Server will require a reboot. However, changing a hostname on a Unix/Linux server do not require a reboot! But, it is not so straightforward to change the hostname of a server online. This is because you will need to change a couple of things, like the entry in ODM, nodename and current hostname.

oldhostname:/:>chdev -l inet0 -a hostname=newhostname

inet0 changed

oldhostname:/:>uname -S newhostname => Change the network name of this machine.

oldhostname:/:>hostname newhostname => Sets the name of the current host system.

newhostname

oldhostname:/:>su -

newhostname:/:>exit



Backing up HMC Data


Backing up HMC Data

Backing up critical HMC data - Using the Command Line Interface

Use the command :

bkconsdata -r dvd



Backing up partition profile data - Using the Command Line Interface

Use the command:-

bkprofdata -m <MTMS> -f dvd

where <MTMS> is the machine type and serial number of the managed system.



Backing up critical HMC data - Using the GUI (WebSM) Interface

Describes how to back up important console information to DVD, a remote system mounted to the HMC file system (such as NFS), or a remote site through FTP.

Using the HMC, you can back up all important data, such as the following:

· User-preference files
· User information
· HMC platform-configuration files
· HMC log files
· HMC updates via Install Corrective Service

Note: The archived data should be used only in conjunction with a reinstallation of the HMC from the product CDs. For information about how to reinstall the HMC, see Reinstalling the HMC machine code.
The Backup function saves the HMC data stored on the HMC hard disk to DVD, a remote system mounted to the HMC file system (such as NFS), or a remote site through FTP. Back up the HMC after you have made changes to the HMC or to the information associated with logical partitions.

Note: The DVD must be formatted in the DVD-RAM format before data can be saved to the DVD.
To back up the HMC, you must be a member of one of the following roles:

· super administrator
· operator
· service representative

To back up the HMC, do the following:

1) In the Navigation area, click the Licensed Internal Code Maintenance icon.
2) In the Contents area, click the HMC Code Update icon.
3) Select Back up Critical Console Data.
4) Select an archive option. You can back up to DVD on the HMC, back up to a remote system mounted to the HMC file system (such as NFS), or a remote site through FTP.
5) Follow the instructions on the panel to back up the data.




Backing up partition profile data - Using the GUI (WebSM) Interface
Describes how to back up profile data on the HMC.

To back up partition profile data, you must be a member of one of the following roles:

· super administrator
· service representative

To back up partition profile data, do the following:

1) In the Contents area, select the managed system.
2) From the menu, click Selected > Profile Data > Backup.
3) Type the name you want to use for this backup file.
4) Click OK.



Checking the date & time that the last critical console data backup was performed
To display the date and time of the critical console data backup, use the lssvcevents command with the -t console option as shown below. Display the date and time when critical console data backup was performed :-


$ lssvcevents -t console -d 9999|grep 'backup of critical'

05/23/03 05:25:39 PM HSCE2062 A backup of critical console data was performed.
05/21/03 09:44:17 AM HSCE2062 A backup of critical console data was performed.
05/20/03 03:22:32 PM HSCE2062 A backup of critical console data was performed.
05/15/03 11:01:23 PM HSCE2062 A backup of critical console data was performed.
05/15/03 05:48:52 AM HSCE2062 A backup of critical console data was performed.



Checking the date & time that the last profile data backup was perfrormed
To display the date and time that the profile data backup was performed, use the lssvcevents command withthe -t console option as shown below. Display the date and time when profile data backup was performed :-


$ lssvcevents -t console -d 9999|grep 'Profile data'

05/20/03 02:44:32 PM HSCE2004 UserName hscroot Profile data of managed system ITSO_p690 has
been backup to file /var/hsc/profiles/7040-681*021768A/Theeraphong;
05/20/03 01:44:55 PM HSCE2004 UserName hscroot Profile data of managed system ITSO_p690 has
been backup to file /var/hsc/profiles/7040-681*021768A/Theeraphong;
05/20/03 12:05:41 PM HSCE2004 UserName hscroot Profile data of managed system ITSO_p690 has
been backup to file /var/hsc/profiles/7040-681*021768A/KoaTest;
Twitter Bird Gadget