Accessing the Data in Core Dumps

Check out this great article by Mark Ray!

Accessing the Data in Core Dumps

Getting AIX RoCE to show up as ent’s in AIX and use as a regular network card

In order to fully use these cards and get them to show up as ent devices perform the following:

After the existing AIX RoCE file sets are updated with the new file sets, both the roce and the ent devices might appear to be configured. If both devices appear to be configured when you run the lsdev command on the adapters, complete the following steps:

1. Delete the roceX instances that are related to the PCIe2 10 GbE RoCE Adapter by entering the following command:

# rmdev -dl roce0[, roce1][, roce2,…]

2. Change the attribute of the hba stack_type setting from aix_ib (AIX RoCE) to ofed (AIX NIC + OFED RoCE) by entering the following command:

# chdev -l hba0 -a stack_type=ofed

3. Run the configuration manager tool so that the host bus adapter can configure the PCIe2 10 GbE RoCE Adapter as a NIC adapter by entering the following command:

# cfgmgr

5. Verify that the adapter is now running in NIC configuration by entering the following command:

# lsdev -Cc adapter

The following example shows the results when you run the lsdev command on the adapter when it is configured in the AIX NIC + OFED RoCE mode:

Figure 1. Example output of lsdev command on an adapter with the AIX NIC + OFED RoCE configuration

ent1 Available 00-00-01 PCIe2 10GbE RoCE Converged Network Adapter
ent2 Avaliable 00-00-02 PCIe2 10GbE RoCE Converged Network Adapter
hba0 Available 00-00 PCIe2 10GbE RoCE Converged Host Bus Adapter (b315506714101604)

You should no longer see roce0 even after running cfgmgr, you can now treat the card like a regular network card (ent)…

TIPS: FLRT reports now include security and HIPER data

You’ve asked for it, and IBM delivered!

FLRT continues to provide update and upgrade recommendations based on your input level, usually your current level, for Power firmware, HMC, AIX, VIOS and many more products.

Now, in addition to the recommendations, you’ll see any security or HIPER fixes that have been released ‘on top’ of those levels, including your input level.

This provides you with options. First, you will be able to see what issues reside on each level. Based on this data, and the end of service dates, you can make decisions about updating or upgrading or staying on your current level.

Here’s an example of an AIX report:


Notice that the information is provided for each APAR or security advisory, with direct links. Or, you can see the information in the easy to use Security APARs or HIPER APARs tables. These tables also list the service packs that the fixes will be released in, so you can plan accordingly.

The report also provides abstract information if you hover over the APAR or CVE number with your cursor.  This allows you to get a quick view before having to click on the link.  Very useful!

Here’s a quick example of a report you can try this with:

Here’s an example for a VIOS partition:


I hope you enjoy this new function and please let us know what you think with our feedback button or take our FLRT survey to let us know what other options you would like to see added to FLRT.


Julie Craft

FLRT architect

Austin, TX

su to NIS user fails with error 3004-503 cannot set process credentials.

Error description

su to NIS user fails with error 3004-503 cannot set
process creditials. This happens when system is upgraded
to 6.1 Tl09 SP01
Local fix
Problem summary

* Systems running the 6100-09 Technology Level with
* at the or level.
Switching to a NIS user using the ‘su’ command will fail with:  3004-503 cannot set process creditials.

This only affects customers using NIS (Network Information Service).
* Install APAR IV53944.
* Prior to fix availability, an interim fix is available from
* either
Problem conclusion

In the processing of NIS user credentials, the logic to find
stale cached records has been corrected so that the record is
not assigned an invalid pointer.
Temporary fix



APAR information  
APAR number IV53944
Reported component name AIX 610 STD EDI
Reported component ID 5765G6200
Reported release 610
Submitted date 2014-01-13
Closed date 2014-01-27
Last modified date 2014-03-28


APAR is sysrouted FROM one or more of the following:


Support Lifecycle Notice for AIX6.1 TL7 & AIX7.1 TL1

Support lifecycle notice
AIX 7.1 Technology Level 1
AIX 6.1 Technology Level 7

IBM announces the following schedules to help you plan for future upgrades to your AIX operating system. These plans are subject to change without notice.

AIX Technology Levels are supported for how to, usage, and problem identification for the entire life of the release. However, all Technology Levels have a limited support window for corrective service. If a fix is needed, you may be required to upgrade to a more current Technology Level to receive generally available fixes or interim fixes. IBM recommends you take a moment to verify your current service level. Simply run the ‘oslevel -r’ command.


Boost Your Productivity with Single-Line AIX Shell Scripts


Boost Your Productivity with Single-Line AIX Shell Scripts

Learn how to create time-saving shell scripts for AIX, UNIX, or Linux that run on a single command line.

Click here to read more on the PowerITPro site


Difference between backing up IBM Virtual I/O server using backupios with and without -mksysb flag

From:  Technology Magazine

Thursday, 14 November 2013 

Difference between backing up IBM Virtual I/O server using backupios with and without -mksysb flag 

On this article ,we just want to list the difference between backing up IBM Virtual I/O server using backupios with and without -mksysb flag . I have seen people make confusion specially in interview.


Backing up the Virtual I/O Server using backupios command without any flag to a remote file system  will create the nim_resources.tar image in the directory we specify.  When the -mksyb flag is used, the resources used by the installios command are not saved in the image. Therefore to restore a VIO server from this image can be used only with NIM. Whereas creating a “nim_resources.tar” for Virtual I/O Server allows this backup can be reinstalled from the HMC using the installios command.




The backupios command creates a backup of the Virtual I/O server and places it onto a file system, bootable tape or DVD. You can use this backup to reinstall a system to its original state   after it   has been corrupted. If you create the backup on tape, the tape is bootable and includes the installation programs needed to install from the backup.


For more information

Task 1:
Login with padmin privilege to VIO server

Task 2:
Change to root privilege using command

$ oem_setup_env

Task 3:
Create a mount directory where the backup image, will be written to

# mkdir /vios01/backup

Task 4:
Mount a filesystem from the NIM master on the mount directory /vios01/backup on VIOS01

# mount server1:/export/mksysb /vios01/backup

Task 5:
Run exit to go back to the padmin privilege for running backupios command


Task 6
. Run the backupios command with the –file option. Make sure to specify the path to the mounted directory

$ backupios –file /vios01/backup/`hostname`.mksysb -mksysb — will create a .mksyb image
$ backupios –file /vios01/backup/ — will create a “nim_resources.tar ”


Technology Magazine




Technology Magazine

IBM AIX : Extending Mirroring Synchronizing ROOTVG

 Usually we get an old_rootvg or altinst_rootvg volume group  after alt_disk backup, upgrade or migration. On this tutorial we will  detail the steps of removing altinst_rootvg , then extending rootvg  and Mirror rootvg with background synchronization.

Let’s  See

Step 1: List the PV with command lspv as below to see which PV hold the old_rootvg / altinst_rootvg  VG . On this example, you can see the altinst_rootvg on hdisk6
removing altinst_rootvg
Step 2:Now let remove  altinst_rootvg using alt_disk_install command with -X flag as below.
After removing altinst_rootvg
Step 3 : After removing altinst_rootvg  list again the PVs again now the hdisk6 become None.
Cleaning up AIX ALTINST
Step 4: Extending rootvg to include hdisk6 using extendvg( -f for force ) command as below and list PVs to verify  now it is part of rootvg. Now we can see hdisk6 is assigned to rootvg.
Cleaning up AIX ALTINST
Cleaning up AIX ALTINST
Step 5 : Now Mirror and Synchronized the rootvg VG using mirrorvg command with -S flag , which will run synchronization in background.
a) Before Mirroring LPs and PPs number is same means it is not mirrored yet.
Cleaning up AIX ALTINST
b) Mirroring using “mirrorvg –S rootvg .
Cleaning up AIX ALTINST
From the man page of mirrorvg
-S Background Sync Returns the mirrorvg command immediately and starts a background syncvg of the volume group. With this option, it is not obvious when the mirrors have completely finished their synchronization. owever, as portions of the mirrors become synchronized, they are immediately used by the operating system in mirror usage.
c) After Mirroring: It might take several minutes to sync LVs as you can see in the below lots of LVs are still in stale state
Cleaning up AIX ALTINST
d) After Full Sync The Out Put will be like below
Cleaning up AIX ALTINST
Step 6 : Re Create the boot image on both rootvg’s PV hdisk6 and hdisk7 and include in boot list.
bootlist -o -m normal
# output: hdisk7 blv=hd5

bosboot -ad hdisk7
# output: bosboot: Boot image is 22698 512 byte blocks.
bosboot -ad hdisk6
# output: bosboot: Boot image is 22698 512 byte blocks

bootlist -o -m normal   hdisk7 blv=hd5  hdisk6 blv=hd5
# output: hdisk7 blv=hd5
# output: hdisk6 blv=hd5

UPDATE: Kimber’s POWER Sys Ref Docs – 10/4/2013

Kimber has updated his POWER doc collections.

For those that will always have network connections whenever needing POWER docs:

For those that are not assured of having network connectivity;  Doug Ranz has slipstreamed all the docs into standalone PDFs:



IBM PowerHA SystemMirror for AIX Adds Support for the New IBM Power7+ 710/730 (8231-E1D/E2D)

IBM PowerHA SystemMirror for AIX Adds Support for the New IBM Power7+ 710/730 (8231-E1D/E2D)

May 02, 2013IBM PowerHA SystemMirror for AIX* adds support for the new IBM Power7+ 710/730 (8321-E1D/E2D).

Please refer to the following information for support details.

Power 7+ 710/730 (8321-E1D/E2D)
AIX V6.1
AIX V7.1
PowerHA SystemMirror V6.1
PowerHA V6.1 TL 6
AIX V6.1 TL 8
PowerHA V6.1 TL 6
AIX V7.1 TL 2
PowerHA SystemMirror V7.1
PowerHA V7.1.2
AIX 6.1 TL 8
PowerHA V7.1.2
AIX V7.1 TL 2

Clients are advised to obtain the latest service updates for this support.


  • Integrated Virtualization Manager (IVM) is also supported.

IBM Service can be obtained from the IBM Electronic Fix Distribution site at:

For questions or concerns, please send a note to HA Feedback at:

HA Solutions Feedback/Poughkeepsie/IBM or

* Trademark or registered trademark of International Business Machines Corporation.
Other company, product, and service names may be trademarks or service marks of others.