AIX Error D221BD55 and BC3BE5A3 after AIX 5.3 upgrade 6.1

When we run errpt on aix after upgrading,we got the following message:

D221BD55   0601211313 I O perftune       RESTRICTED TUNABLES MODIFIED AT REBOOT

---------------------------------------------------------------------------

LABEL:          TUNE_RESTRICTED

IDENTIFIER:     D221BD55

Date/Time:       Sat Jun  1 21:13:58 EDT 2013

Sequence Number: 581725

Machine Id:      ******

Node Id:         ****

Class:           O

Type:            INFO

WPAR:            Global

Resource Name:   perftune

Description

RESTRICTED TUNABLES MODIFIED AT REBOOT

Probable Causes

SYSTEM TUNING

User Causes

TUNABLE PARAMETER OF TYPE RESTRICTED HAS BEEN MODIFIED

        Recommended Actions

        REVIEW TUNABLE LISTS IN DETAILED DATA

Detail Data

LIST OF TUNABLE COMMANDS CONTROLLING MODIFIED RESTRICTED TUNABLES AT REBOOT, SEE FILE /etc/tunables/lastboot.log

vmo

In the output above, you'll notice that we are advised to check the /etc/tunables/lastboot.log for a modified restricted vmo tuning parameter. At this point I usually like to run the tuncheck command against the current /etc/tunables/nextboot file and review its output. As you can see, in the example below, we are warned that several restricted tunables are not set to their default values. These values might not be appropriate for your newly migrated AIX 7.1 (or 6.1) system. Settings that worked well with 5.3 are most likely no longer appropriate with 7.1.

root: /apps/scripts :>tuncheck -p -f /etc/tunables/nextboot Warning: restricted tunable strict_maxperm is not at default value Checking successful

Based on the output above, the tuning for this newly migrated 6.1 system appears to be inappropriate. Unless we have a valid reason (which has been verified by IBM AIX support) we should set these tunables to their default AIX 6.1 settings.

You can reset individual tunables to their defaults using the –d flag and the corresponding tuning command. For example to set the strict_maxperm % tunable to its default you would run the following vmo command:

root:/etc/tunables :>vmo -p -d strict_maxperm Modification to restricted tunable strict_maxperm, confirmation required yes/no yes Setting strict_maxperm to 0 in nextboot file Setting strict_maxperm to 0 Warning: a restricted tunable has been modified

After the tunables have been reset, re-run the tuncheck command and ensure it runs without errors:

# tuncheck -p -f /etc/tunables/nextboot Checking successful

Another error log:

BC3BE5A3   0525202813 P S SRC            SOFTWARE PROGRAM ERROR

root: /etc/tunables :>errpt -a -j BC3BE5A3|more

---------------------------------------------------------------------------

LABEL:          SRC_SVKO

IDENTIFIER:     BC3BE5A3

Date/Time:       Sat Jun  1 21:24:13 EDT 2013

Sequence Number: 494012

Machine Id:      *****

Node Id:         ******

Class:           S

Type:            PERM

WPAR:            Global

Resource Name:   SRC

Description

SOFTWARE PROGRAM ERROR

Probable Causes

APPLICATION PROGRAM

Failure Causes

SOFTWARE PROGRAM

        Recommended Actions

        MANUALLY RESTART SUBSYSTEM IF NEEDED

Detail Data

SYMPTOM CODE

         256

SOFTWARE ERROR CODE

       -9017

ERROR CODE

           0

DETECTING MODULE

'srchevn.c'@line:'376'

FAILING MODULE

i4llmd

This error is relational to i4llmd, we may check the error under /var/ifor/I4LLMD.log

GRL-2050: *** Fatal error from I4LLMD:

License database on an invalid node.

and the solution:

 The GRL-2050 error message means that the LUM has detected a duplicated instance within the same network. This can easily happen if you clone an AIX installation image that is already configured with LUM on a partition to the other partitions in a partitioned environment.

To solve the problem, do the following as the root user on the partition that produced the error message:

1.      export PATH=$PATH:/usr/opt/ifor/ls/os/aix/bin

2.      cd /var/ifor

3.      i4cfg -stop

4.      rm i4ls.ini *.dat *.idx

5.      i4cnvini

6.      i4cfg -a n -S a -n n -b null

7.      i4cfg -start

Then, register the valid software product license again. In case of IBM C for AIX, Version 6.0, do the following (the /usr/vac/cforaix_cn.lic file is used for the concurrent node lock license):

i4blt -a -f /usr/vac/cforaix_cn.lic -T N -R "root"

Where N is the number of the license you are going to register, such as 2.

To confirm if the license has been successfully registered, use the i4blt command, as follows:

i4blt -s -lcn

i4blt Version 4.6.8.10 AIX -- LUM Basic License Tool

(c) Copyright 1995-2007, IBM Corporation, All Rights Reserved

US Government Users Restricted Rights - Use, duplication or disclosure

restricted by GSA ADP Schedule Contract with IBM Corp.

(c) Copyright 1991-1997 Gradient Technologies Inc., All Rights Reserved

(c) Copyright 1991,1992,1993, Hewlett-Packard Company, All Rights Reserved

===========================================================================

===                P r o d u c t  S t a t u s  R e p o r t              ===

===========================================================================

  Vendor Name:      IBM Software Solutions Toronto

  Product Name:     C for AIX

  Product Version:  6.0.cn

  License Type:     Concurrent Node-Locked License(s)

 ---------------------------- Usage Information ---------------------------

  Licenses    In-Use      Soft-Stop In-Use  Not In-Use

  --------    ------      ----------------  ----------

  2           0.00        0.00              2.00

                     ====================================

                     === End of Product Status Report ===

                     ====================================