How to delete COMMITTED LPPs from AIX

Example:

bash-3.2# lslpp -l | grep -i lotus
  IBMLotusSametime70         7.0.0.0  COMMITTED  ISMP installed entry
  LotusFormsServerAPI35      3.5.0.0  COMMITTED  IBM Lotus Forms Server API

  bash-3.2# ODMDIR=/usr/lib/objrepos odmget -q "name = IBMLotusSametime70" lpp

lpp:
        name = "IBMLotusSametime70"
        size = 0
        state = 5
        cp_flag = 131345
        group = ""
        magic_letter = ""
        ver = 7
        rel = 0
        mod = 0
        fix = 0
        description = "ISMP installed entry"
        lpp_id = 1573
bash-3.2# ODMDIR=/usr/lib/objrepos odmdelete -o lpp -q "name = IBMLotusSametime70"
0518-307 odmdelete: 1 objects deleted.

X11 problem in aix

Whenever you face problem with X11 forwarding, please refer the following steps to set it right:

1)      ssh settings:

Check the following settings in the configuration file sshd_config present in /etc/ssh:

X11Fowarding yes

2)      Stop and start the ssh service:

stopsrc –s ssh

startsrc –s ssh

3)      Start the X server:

startx

4)      Logout the user and login again.

5)      When you login, issue the following command to create a Xauthority file:

Xauth

6)      Now type xclock and it will start worklng.

Source Link: http://aix4admins.blogspot.in/2011/06/using-x11-forwarding-in-ssh-ssh.html

                     http://www.cyberciti.biz/faq/x11-connection-rejected-because-of-wrong-authentication/

How to copy large files in aix

I changed the default parameters in /etc/security/limits to make the file size unlimited and it works now.

Ref: http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/how-to-copy-large-files-in-aix-2904368 

How to see the contents of .bff file (AIX)

    restore    -Tqdvf    VRTSvbs_6.0.100.000_AIX.bff

    To install a bff file, Following command is used :

  installp -Xap -d U819433.bff

How to convert from 64-bit to 32-bit and vice versa ?

To truly change the kernel to 64-bit, you need to be at least 5.1 oslevel. The
means to change to a 64-bit kernel are:

From 32-bit to 64-bit:
     ln -sf /usr/lib/boot/unix_64 /unix
     ln -sf /usr/lib/boot/unix_64 /usr/lib/boot/unix
     bosboot -ad /dev/ipldevice
     shutdown -Fr
     bootinfo -K (should now be 64)

To change the kernel back to 32-bit:

From 64-bit to 32-bit:
     ln -sf /usr/lib/boot/unix_mp /unix
     ln -sf /usr/lib/boot/unix_mp /usr/lib/boot/unix
     bosboot -ad /dev/ipldevice
     shutdown -Fr
     bootinfo -K (should now be 32)

How to mount an ISO file as a filesystem in AIX

In AIX you "dd" the ISO file into a raw LV, then mount the LV as a filesystem.

Here are the steps for copying the ISO named "image.iso" into "/cd1iso", a JFS filesystem:

1. Create a filesystem with size slightly bigger than the size of the ISO image. Do NOT mount the filesystem:
# /usr/sbin/crfs -v jfs -g rootvg -a size=800M -m/cd1iso -Ano -pro -tno -a frag=4096 -a nbpi=4096 -a ag=8

2. Get the logical volume name associated with the new filesystem:
# lsfs | grep cd1iso (assume it is /dev/lv00)

3. dd the ISO image into rlv00 (raw lv00):
# dd if=image.iso of=/dev/rlv00 bs=10M

4. Alter /cd1iso stanza in /etc/filesystems => vfs=cdrfs and options=ro (read-only)

    /cd1iso:
            dev            = /dev/cd1_lv
            vfs             = cdrfs
            log             = /dev/loglv00
            mount           = false
            options         = ro
            account         = false

5. Mount the file system :
# mount /cd1iso

6. When finished, remove the filesystem:
# rmfs /cd1iso

Enable SNMP Access on AIX

Enabling SNMP access and trap forwarding for AIX

SNMP access and trap forwarding enable SNMP-based managers to poll the managed system and receive its alerts. If System Health Monitoring is installed on the managed system also, hardware alerts can be forwarded as SNMP traps.

To enable SNMP access and trap forwarding on AIX®, you must be running AIX version 5.2 or later.

1. With root authority, open the /etc/snmpdv3.conf file in a text editor.
2. Create a community entry for the customized access view. You can create a new community entry or reuse the default community entry, as in the following example:

   #         communityName  securityName  securityLevel  netAddr  netMask  storageType
   COMMUNITY myDirector     myDirector    noAuthNoPriv   0.0.0.0  0.0.0.0  -

3. Define a security group that includes the community you defined. You can create a new group entry or reuse the default group entry, as in the following example:

   #          groupName    securityModel  securityName  storageType
   VACM_GROUP mygroup_v1   SNMPv1         myDirector    –
   VACM_GROUP mygroup_v2c  SNMPv2c        myDirector    -

   Note: The security group name cannot begin with "director_group".
4. Define a view entry to include or exclude MIB objects, as in the following example:

   #         viewName       viewSubtree              viewMask  viewType  storageType
   VACM_VIEW director_View  internet                 -         included  -
   VACM_VIEW director_View  1.3.6.1.4.1.2.2.1.1.1.0  -         included  -
   VACM_VIEW director_View  1.3.6.1.4.1.2.6.191.1.6  -         included  -
   VACM_VIEW director_View  1.3.6.1.4.1.2.6.159      -         included  -
   
   # exclude snmpv3 related MIBs from the view
   VACM_VIEW director_View  snmpModules              -         excluded  -
   VACM_VIEW director_View  1.3.6.1.6.3.1.1.4        -         included  -
   VACM_VIEW director_View  1.3.6.1.6.3.1.1.5        -         included  -
   
   # exclude aixmibd managed MIBs from the view
   VACM_VIEW director_View  1.3.6.1.4.1.2.6.191      -         excluded  -

5. Create an access entry to authorize the security group to the customized access view, as in the following example:

   #            groupName       securityLevel  securityModel  readView        notifyView 
   VACM_ACCESS  mygroup_v1  - - noAuthNoPriv   SNMPv1         director_View - director_View -
   VACM_ACCESS  mygroup_v2c - - noAuthNoPriv   SNMPv2c        director_View - director_View -

6. To configure SNMP traps, perform steps 7 and 8.
   Otherwise, go to step 9.
7. Specify a target address value for each destination to which IBM® Director will send SNMP traps, as in the following example:

   #               targetAddrName  tDomain  tAddress      tagList  targetParams
   TARGET_ADDRESS  Target1         UDP      9.181.65.131  traptag  trapparms1    - - -

8. Specify a trap community value, as in the following example:

   #                  paramsName  mpModel  securityModel  securityName  securityLevel  storageType
   TARGET_PARAMETERS  trapparms1  SNMPv1   SNMPv1         myDirector    noAuthNoPriv   -

9. Save and close the /etc/snmpdv3.conf file.
10. Stop and restart the cimlistener daemon by typing the following commands and pressing Enter after each:

    /opt/freeware/cimom/pegasus/bin/cimlistener -s
    /opt/freeware/cimom/pegasus/bin/cimlistener

11. Stop and restart the IBM Director AgentX subagent by typing the following commands and pressing Enter after each:

    /opt/ibm/icc/cimom/bin/icesnmp stop
    /opt/ibm/icc/cimom/bin/icesnmp start

12. Ignore Steps 10 and 11, if the commands are not found, do Step 13 and 14.

13. stopsrc -s snmpd;stopsrc -s dpid2;stopsrc -s aixmibd;stopsrc -s hostmibd;stopsrc -s snmpmibd

14. startsrc -s snmpd;startsrc -s dpid2;startsrc -s aixmibd;startsrc -s hostmibd;startsrc -s snmpmibd

For more info, Refer to:

http://publib.boulder.ibm.com/infocenter/director/v5r2/index.jsp?topic=/diricinfo_5.20/fqm0_t_enabling_snmp_access_and_trap_forwarding_for_aix.html

http://forums.cacti.net/about19040.html 

http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.commadmn/doc/commadmndita/snmpv1_daemon_config.htm

    
 To test, do an snmpwalk to this aix host from any linux machine as follows:

 snmpwalk -c public -v1 [aixhosttomonitor]