You are viewing the community [info]eserver

IBM eServer's Journal
 
 [Most Recent Entries] [Calendar View] [Friends]

Below are the 20 most recent journal entries recorded in IBM eServer's LiveJournal:

    [ << Previous 20 ]
    Thursday, May 24th, 2012
    11:30 pm
    [xaminmo]
    Manually uninstall tsmac, tipv2, and other DE products
     run all uninst* from /opt/IBM/tivoli
    remove contents of /opt/IBM/tivoli
    remove contents of /opt/tivoli
    remove contents of /home/db2inst1
    remove /export/lppsource/TSM630ac

    List the remnants in DE:
    cd /usr/ibm/common/acsi/bin/
    ./de_lsrootiu.sh

    Delete the UUID and discriminant (directory). My examples were:
    ./deleteRootIU.sh 2ADC4A33F09F4E85AD27963E850290C3 /opt/IBM/tivoli/tipv2
    ./deleteRootIU.sh 3DD9564D2E7442788584C1F35B07F2A2 /opt/IBM/tivoli/tipv2Components/TCRComponent
    ./deleteRootIU.sh 61AE95EAFC824C45BECFD427C959D5B7 /opt/IBM/tivoli/tipv2Components/TCRComponent
    ./deleteRootIU.sh 7F15FB682C80DFB90EBE3B0BF5D8EDC6 /opt/IBM/tivoli/tsmac
    ./deleteRootIU.sh C00DA95AFD9B7E0397153CD944B5A255 /opt/IBM/tivoli/tipv2
    Monday, May 7th, 2012
    6:09 pm
    [xaminmo]
    This is why InstallAnywhere sucks...
     This is a new, clean install of the OS, and a new, clean download of the 6.3.1 reporting tool.

    daltsmrpt: /install/2012/TSM/631rpt# cat /stdout
    rootRA: com.ibm.tivoli.remoteaccess.LocalUNIXProtocol@298a298a
    rootRA.isProtocolAvailable(): true
    Exception: Userid is not privileged. java.net.ConnectException: CTGRI0002E Session not established.
    (X) commiting registry
    (X) shutting down service manager
    (X) cleaning up temporary directories

    daltsmrpt: /install/2012/TSM/631rpt# whoami
    root

    daltsmrpt: /install/2012/TSM/631ac# oslevel -s
    7100-01-02-1150

    If I get this sorted out, I'll post about it.
    ( Read more... )
    Saturday, April 28th, 2012
    8:36 pm
    [xaminmo]
    TSM Storage Agent 5.4.3.2 on HP-UX 11.11 PA-RISC
     TSM Storage Agent 5.4.3.2 on HP-UX 11.11 PA-RISC.
    This is a legacy platform, so there are no updates.
    When connecting to TSM 6.3, any restores need to be done without no-query.
    If you do a no-query restore, the storage agent crashes with this:
    ( Read more... )

    You'll have to CANCEL RESTORE, then rm adsmserv.lock in the StorageAgent directory, then restart dsmsta.

    No-query restore is via dsmj -> restore -> options -> disable no query restore
    OR, from command line, make sure you have a question mark somewhere in your file path (an asterisk won't do it).

    Then, consider upgrading your legacy applications to a supported platform.
    Saturday, April 21st, 2012
    8:13 am
    [xaminmo]
    TSM 6.3 install log
     Because I've not seen any full logs of TSM 6.2 or TSM 6.3 install anywhere, I'm posting a happy working install.

    Note that this is from the download package, not base. We already have tivoli.tsm.license installed from the base CD manually (installp).

    ( installing )
    Sunday, July 31st, 2011
    5:15 pm
    [xaminmo]
    Trying to boot P701 blade...
     Was installed on the single, internal SAS disk, but was provisioned some 60G LUNs from a VNX (aka CLARiiON).
    Got the MPIO drivers on (because powerpath boot has management encumberances), and verified the devices looked good.
    Rebooted, the mirrored onto the new LUNs, removed the old SAS disk, updates bootlist and bosboot.
    shutdown -Fr and I get this:

    IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
QLogic QMI3572  Host Adapter FCode(IBM): 3.14 2010-04-30 15:03
ISP Firmware version 5.03.06
/
Elapsed time since release of system processors: 37167 mins 43 secs
DEFAULT CATCH!, exception-handler=fff00400
at   %SRR0: 0000000048000104   %SRR1: 0000000040003002
Open Firmware exception handler entered from non-OF code

Client's Fix Pt Regs:
 00 0000000000000001 0000000000038160 0000000060000000 0000000000044bd0
 04 0000000000000001 0000000000000000 0000000000000100 0000000000044bd0
 08 ffffffffffffffff 0000000000000003 0000000048000104 0000000060000000
 0c 0000000000000078 0000000000000000 0000000000000000 0000000000000000
 10 0000000000000000 0000000000000000 0000000000000000 0000000000000000
 14 0000000002000000 0000000000000008 0000000000000000 0000000000000000
 18 0000000000000000 0000000000000001 0000000000039b58 0000000000044e10
 1c 0000000000044e08 0000000000038350 0000000000000000 0000000000000000
Special Regs:
    %IV: 00000400     %CR: 22000040    %XER: 00000000  %DSISR: 00000000
  %SRR0: 0000000048000104   %SRR1: 0000000040003002
    %LR: 0000000000011d7c    %CTR: 0000000048000104
   %DAR: 0000000000000000
Virtual PID = 0
 ok
0 >


    It's been years since I got a DEFAULT CATCH so I don't remember where to go from here.

    Google is giving me no joy.
    Wednesday, July 20th, 2011
    5:50 pm
    [xaminmo]
    Permissions - DocAve / TSM for Sharepoint
     Because the AvePoint docs are somewhat Engrish and overall not so great, IBM has released a nice whitepaper at:
    https://www-304.ibm.com/support/docview.wss?uid=swg21474709

    I've annotated below with asterisk notes.


    Perms for Granular Backup :
    1. Farm Admin within SharePoint
    2. Web application policy within SharePoint
    3. Local administrator where the particular DocAve Agent is installed
    4. DBO permissions to the Content Databases and Central admin databases

    Perms for Granular Backup including MySites :
    1. Farm Admin within SharePoint
    2. Web application policy within SharePoint
    3. Full Control to Personalization Services within SharePoint
    4. Local administrator where the particular DocAve Agent is installed.
    5. Dbo permissions to the Content Databases and Central admin databases

    Perms for Platform Backup :
    1. Farm Admin within SharePoint
    2. Web application policy within SharePoint
    3. Local administrator where the particular DocAve Agent is installed
    4. DBO permissions to the Content Databases and Central admin databases with SQL
    5. Security Admin within SQL
    * NOTE: You need a member agent installed on each active SQL server.
    * NOTE: You need a member agent on each cluster node to get the cluster configs
    * NOTE: Install a member agent on each WFE to spread the small-request load around since the agents are single threaded.

    Perms How to grant SQL Sysadmin
    1. Please open SQL Server Management Studio and connect to the SharePoint SQL instance.
    2. Please go to Security -> Server Roles -> sysadmin.
    3. Please click on Add button and add DocAve Agent account into this group.

    How to give Local Admin permissions
    1. Please log in to XXX server and go to Server Manager.
    2. Please go to Configuration -> Local Users and Groups -> Groups -> Administrators.
    3. Please click on Add button and add DocAve Agent account into this group.

    Granting the Agent Farm Admin permissions
    1. Please log in to SharePoint Central Admin.
    2. Please go to Site Actions -> Site Settings -> Advanced permissions.
    3. Please click on New button to add the Agent account into the Farm Administrators group.

    Granting SSP Admin permissions
    1. Please log in to SharePoint Central Admin and click on the Shared Services Administration instance.
    2. Please click on Personalization services permissions.
    3. Please add DocAve Agent account with all permissions listed.

    Adding a user to Web Application Policy - Moss 2007:
    1. Please log in to SharePoint Central Admin.
    2. Please go to Application Management -> Policy for Web application.
    3. Please add DocAve Agent account with full control for the (specific) web application.

    Adding a user to Web Application Policy - SharePoint 2010:
    1. Please log in to SharePoint Central Admin and click on Manage web applications.
    2. Please select the Web Application and click on the User Policy button.
    3. Please click on Add Users and add DocAve Agent account with full control.

    Three additional permissions need to be granted:
    Act as part of the operation system, Log on as a batch job and Replace a process level token. Please follow the steps below to add the corresponding permissions for one user.
    1. Navigate to Start->Run, enter gpedit.msc in the pop-up window.
    2. Navigate to Computer Configuration->Windows Settings->Security Settings->Local Policies->User Rights Assignment and add the corresponding user to the three policies on the right of the window.

    For Content Manager module, the following permissions are required:
    1. The Read and Write permissions for the installation path of the Agent.
    2. The permission to create Event Logs:
    a. Navigate to Start->Run, enter regedit in the pop-up window.
    b. Find the corresponding key:
    HKEY_LOCAL_MECHINE\SYSTEM\CurrentControlSet\servicecs\Eventlog
    c. Right click on the key and click Permissions to add the corresponding permissions for the user.
    NOTE: If the module could not be used after you add the permissions above, please assign Local Admin permission to the corresponding user.

    For Replicator module, Auditor module and the other functions under the Administration module
    The Local Admin permission is required.
    Wednesday, July 6th, 2011
    3:06 pm
    [xaminmo]
    NIM limitation
     I found out today that if you're using smaller than a /24, NIM will fail to accept your host into the subnet.

    I had an "ent" definition with snm 255.255.255.0. The IP was 192.168.1.17, network was .0, gateway .1.

    I redefined this as 255.255.255.127, and when adding it to the master, it said that .17 was not a part of the .0 network.

    What a strange, and lame limitation.

    UPDATE And it was brought to my attention what my error was. For a subnet mask, it would be .128, not .127. I was mixing up the oddness of 255 plus broadcast address. *sigh*

    I M SMRT.
    Monday, July 4th, 2011
    11:58 am
    [xaminmo]
    Manually removing an LV and other woes
     System was installed on hdisk0
    New disk came in at hdisk4.
    migrated to hdisk4, bosboot, bootlist.
    hdisk0 is gone.
    boot failure for unknown reasons. Hangs at "Starting the Kernel".

    ###Access a Root Volume Group has problems.
    0516-622 synclvodm: Warning, cannot write lv control block tada.
    ln: /dev/r: No such file or directory
    getlvodm: option requires an argument -- l
    0516-104 lquerylv: Incorrect LV identifier. The format must be
    VG_identifier.LV_minor_number


    ###lspv shows it on hdisk4, but the running kernel has it as hdisk0.
    bosboot -ad hdisk4
    0518-507 odmget: Could not retrieve object for CuAt, ODM error number 5904
    bosboot: Boot image is 46871 512 byte blocks.
    0301-162 bosboot: savebase failed with /dev/hdisk4.
    0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot device.
    reboot
    PReP-BOOT : Unable to load full PReP image.
    Loaded 0 out of 1702e00 bytes.
    No OS image was detected by firmware.
    At leasrt one disk in the bootlist was not found yet.
    Firmware is now retrying the entries in the bootlist.
    Press ctrl-C to stop retrying.

    ###Access a root volume group again
    rmlv -f hd5
    mklv -ae -em -tboot -yhd5 rootvg 2
    bosboot -ad hdisk4
    0516-1734 rmlv: Warning, savebase vailed. Please manually run 'savebase' before rebooting.
    0518-507 odmget: Could not retrieve object for CuAt, ODM error number 5904
    0301-111 /usr/lib/boot/bin/mkboot_chrp: error on Object Data Manager routine "odm_get_first"
    0301-158 bosboot: mkboot failed to create bootimage.
    0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot device.

    ### Tried hardlinking the real disk's dev entries to the one disk ODM wants, but no changes.
    ### rmdev and cfgmgr didn't help
    next boot gave
    0516-010 : Volume group must be varied on; use varyonvg command.
    0516-168 bosboot: The current boot logical volume, /dev/hd5, does not exist on /dev/hdisk4

    rmlv -f hd5
    0516-306 getlvoodm: Unable to find hd5 in the Device
    Configuration Database.
    0516-912 rmlv: Unable to remove logical volume hd5.
    0516-1734 rmlv: Warning, savebase failed. Please manually run 'savebase' before rebooting.


    Ultimately, I had to odmget | grep -p hdisk4, edit all of the entries, odmdelete -o $class -q "name=hdisk4" and such (name, value3, dependency), then re-add the edited entries so that the rootvg disk matched what maint mode finds it as.

    Then, I had to manually remove hd5 since it was severely broken:

    lqueryvg -p hdisk0 -At
    copy the LVID (VGID.###)
    lquerylv -L $LVID -r > /tmp/1
    LPS=`wc -l /tmp/1`
    lreducelv -l $LVID -s $COUNT /tmp/1

    mklv and bosboot worked fine after that, but bootlist did not because hdisk0 wasn't available due to it already being brought up from ramfs. I had to boot to SMS, choose the OS disk, and then run bootlist from inside the running OS.

    Now I'm back to the point of hanging at "Starting kernel". These are "MPIO Other FC SCSI Disk Drive", a netapp device hanging off of NPIV.

    Now to go dig up my old steps for doing a debug boot... *sigh*
    These all seem like issues that should not occur at this stage of the game with AIX.
    Wednesday, June 22nd, 2011
    10:57 am
    [xaminmo]
    TS3500 metalibraries
     IBM now can crossconnect multiple libraries to make one superlibrary by installing shuttle mechanisms to transfer tapes between libraries automagically:
    http://www.flickr.com/photos/ibm_media/5707716196/in/photostream
    Tuesday, June 21st, 2011
    5:37 pm
    [xaminmo]
    POWER Blades with SDMC for Dual VIO
     Redbooks, SDMC docs, blade docs, etc give info assuming everything works.

    Everything does NOT work by default.

    Major caveats:
    1) The BladeCenter Blade IP config is for the service processor. Configure that. It's necessary. You cannot set an IP for it on both ports, so if you lose the blade switch, you lose LPAR management capabilities for the blade. Also, make sure your customer doesn't put the same IP on the AIX full system partition as was used for the service processor. You'd think this would be an easy one, but it has happened.
    Ref: https://www-304.ibm.com/support/docview.wss?uid=nas1057800440ee4dae4862573e9005ad197&wv=1

    2) The minimum firmware levels are for late may, early june of 2011. If you log in as admin/admin to the FSP and have NO OPTIONS, then you are not at the right level. Just use "update_flash" on the .img file you pull down. FixCentral does NOT provide firmware for blades. The only place I could find the list was from an AS/400 techdoc:
    POWER7: http://www-912.ibm.com/s_dir/slkbase.nsf/ibmscdirect/5DDD545112AD21218625776500573780
    POWER6 http://www-912.ibm.com/s_dir/slkbase.nsf/ibmscdirect/1C94AF8A9EAC7C138625764A006A426F

    3) The p7 blade has to be initially discovered by service processor IP address. If you discovered it through the BladeCenter, then you have to remove the POWER Blade from director before you can make it work. You can't simply rediscover it.
    Ref: https://www-304.ibm.com/support/docview.wss?uid=nas79b91491123ade0f88625786f0067dec5&wv=1


    After all that, go to Navigate Resources, click on the server, pull down Actions, System Configuration, Edit, or Create Virtual. After that, it's vaguely similar to the HMC.
    Wednesday, April 27th, 2011
    6:04 pm
    [xaminmo]
    ProtecTier TS7650G install
     The docs were scattered. Publib was best, but you can't print to PDF if you want to see the in-line diagrams. The whitebooks are out of order, missing steps, etc because they assume you have the appliance, or are recovering at DR.

    Connectivity
    Emulex = front-end 2x dual port 4gbit
    QLogic = back end 2x dual port 4gbit
    Replication = IP based
    Has a quad-port gigabit card by default. If ordered for OST, will have three of those. If ordered as zOS attach, will have 2 pSeries systems and will have 10G ethernet.

    Limits
    7610 hub: 3 clients max
    7650/7680 hun: 12 clients
    libraries 16
    drives 256/node (512 max)
    carts (55,000)
    ( How To Install )</PREL
    5:30 pm
    [xaminmo]
    Substitution for tapeutil
     tapeutil isn't gone. It's not "replaced" by itdt either.

    itdt actually contains the entire tapeutil command. You can run "itdt -f /dev/smc0 inventory", or you can run itdt and choose "U" to get into the text-gui version

    The only problem is that itdt is neither installed, nor does it like being run from anywhere other than its own directory. It's actually a pretty lame limitation, but who are we to question?

    Anyway, put this in your .profile and you'll be set:

    tapeutil() { (cd /opt/IBMtape ; ./itdt $* ;) ; }


    This assumes you unpacked ITDT into /opt/IBMtape. Adjust as necessary for your environment.

    The function is because you're passing parameters to it. The subshell is because we don't want to stay in the dir where it's installed.
    5:09 pm
    [xaminmo]
    Atape.driver
     So, last year, /storage/devdrvr was formally sunset off of service.software.ibm.com. The new way is to go through fixdist via a supported, GUI web browser. No, not lynx. Sorry, your headless server will have to either export its display, or you'll have to push things over the network.

    Well, maybe. You can copy the non-standard, new FTP address out and paste it into your putty session.

    To save you the first 18 links, IBM has a techdoc with links to the current versions and the tape guide:

    http://ibm.com/support/docview.wss?uid=ssg1S7002972
    Monday, April 11th, 2011
    9:21 pm
    [xaminmo]
    Strange TSM errors in the lab...
     Ok, so if you have to replace the OS on your TSM server, and you're not using AD, then be sure to re-take ownership of the storage volumes. I didn't notice problems with the FILE class stgpool volumes, but the DBB/DBS volumes failed with errors like this:
    2011-04-11 06:00:30 ANR1360I Output volume H:\TIVOLI\TSM\SERVER1\02519629.DBS opened (sequence number 1). (SESSION: 2390, PROCESS: 234)
    2011-04-11 06:00:30 ANR0132E lvmread.c(1245): Memory allocation failed: object Resync read page buffer, size 4096. (SESSION: 2390, PROCESS: 234)
    2011-04-11 06:00:30 ANR9999D_1112316882 (iccopy.c:1625) Thread<26>: Unable to read from db volume. (SESSION: 2390, PROCESS: 234)


    This kind of problem is more likely if you lose your user DB, because windows uses machine IDs to generate userIDs, and you don't really get to make your own UIDs. So, if you use AD and lose the user DB, or if you're not using AD and you replace the host but keep the stg drives, then this will be an issue.

    I'm posting this because I couldn't find ANYTHING on the web about this. Very few hits about lvmread.c, and none matched.

    I should probably put this in ADSM-L.
    ( actlog from the lab )
    Monday, March 28th, 2011
    8:38 pm
    [xaminmo]
    Question...
     According to the EMC Connectivity Guide for AIX, when using PowerPath greater than 4.4.2.2, the devices will get a UDID, which is what we want for VIO.

    So for whatever reason, this is not the case at one of my customer sites. Powerpath was installed at 5.1, but is now 5.3.0.4. VIO was 1.5, is now 2.0 on some, and 2.1 on others.

    So, before you say, "Oh, old vio.. blah blah blah" no, that's not it. Even on after removing VTDs, removing hdiskpower, removing hdisk, update powerpath, reconfig everything, there's still no UDID in ODM. Even for NEW devices, there is no UDID.

    My workaround has been to manually create the appropriate UDID in ODM, but I was hoping someone, somewhere had run into this and found a solution.
    Wednesday, March 16th, 2011
    10:33 pm
    [xaminmo]
    HOWTO TSM Client as non-root user
     Here's how to set up a TSM client inside of a non-root user's home directory.

    First, copy /opt/tivoli/tsm or /usr/tivoli/tsm into the location appropriate to your environment. For me, this was /home/xaminmo/tsm

    Next, modify your dsm.sys and dsm.opt files to match the new environment.

    TSM assumes hard-coded paths for a bunch of things, so the run line is like this:
    export DSM_CONFIG=/home/xaminmo/tsm/client/ba/bin/dsm.opt
    export DSM_DIR=/home/xaminmo/tsm/client/ba/bin
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/xaminmo/tsm/client/api/bin
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/xaminmo/tsm/client/ba/bin
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib:/usr/lib:/opt/lib:/usr/local/lib
    dsmc

    If you use AES encryption, you'll run into something like this:
    2011-03-16 19:26:49 ANS1467E ICC routine ICC_Init returned: majRC = 4, minRC = 2, desc = '/opt/tivoli/tsm/client/icc32/icc/icclib/libicclib.so: cannot open shared object file: No such file or directory'.
    2011-03-16 19:26:49 ANS1464S Cannot load ICC encryption library.

    The "recommended" solution is to not use AES encryption, but what fun is that?

    The fix is documented for a Windows PE defect, but is easily adapted to our needs:
    ln -s /home/xaminmo/tivoli/tsm/client/icc32/icc /home/xaminmo/tivoli/tsm/client/ba/bin
    echo "testflag localicc" >> /home/xaminmo/tivoli/tsm/client/ba/bin/dsm.opt


    Finally, with PASSWORDACCESS GENERATE set, but non-root dsmtca, you'll see something like this:
    2011-03-16 20:06:25 Unable to locate valid trusted communication agent.
    2011-03-16 20:06:25 tcaPath is >/home/xaminmo/tsm/client/ba/bin/dsmtca<. rc is 138
    2011-03-16 20:06:25 ANS1501E Trusted agent execution/owner permissions are invalid


    The fix is again simple, but only documented in the API Programmer's guide:
    chmod -R go-rwx /home/xaminmo/tsm
    chmod 4500 /home/xaminmo/tsm/client/*/bin/dsmtca
    chown -R xaminmo /home/xaminmo/tsm
    echo "PASSWORDDIR /home/xaminmo/tsm/tivinv" >> /home/xaminmo/tivoli/tsm/client/ba/bin/dsm.sys

    After that, ONLY xaminmo may run dsmc, but the password will be encrypted and stored in /home/xaminmo/tsm/tivinv/TSM.PWD.

    Not pretty, but it's all documented from IBM, and it does work in my lab.
    Monday, March 7th, 2011
    5:56 pm
    [xaminmo]
    IBM POWER5 to POWER7 JBB per Watt 2011-03-07
     While SPEC has some perf per watt stats, I couldn't find these stats for IBM POWER systems.

    Searching, I found that IBM's policy is to use SPECint_rate2006 divided by max watts.

    This didn't work for some of the older systems, which weren't showing up in that stat; however, I found that POWER5 through POWER7 are reported together on SPECjbb2005.

    Looking into the BTU ratings of IBM POWER systems, the BTU output is 100.03% of wattage consumed, then converted to BTUs and rounded up.

    For the power consumed, I pulled down from the announcement letters. Most of these gave Max Watts, but some gave only BTU or kVA. All of these were standardized into watts. px60 and px70 systems were multiplied by the number of drawers (Some p570 drawers guessed).

    For cooling costs, I assumed SEER 10 and $0.10/KWh, 8766 hours per year.

    For the Blade PS702, I assumed 1/14th of the bladecenter rather than only the wattage of the one blade. This is because you really need to include the power for the I/O modules, management module, cooling fans, etc.

    This was folded into the following spreadsheet, which I don't plan to keep updated due to the effort required.

    https://spreadsheets.google.com/pub?hl=en&hl=en&key=0As7iGasZH0DzdGVBaDU4dThfVHF4bkQyd1VnUUZXRUE&single=true&gid=0&output=html
    Saturday, March 5th, 2011
    12:03 am
    [xaminmo]
    DoS Exposure with JRE & JDK hang while converting 2.2250738585072012e-308 into a binary number
     Pretty obscure, but worth passing on anyway.

    Denial of Service Security Exposure with Java JRE/JDK hanging when converting 2.2250738585072012e-308 number (CVE-2010-4476) (PM32387)

    This Security Alert addresses a serious security issue CVE-2010-4476 (Java Runtime Environment hangs when converting "2.2250738585072012e-308" to a binary floating-point number). This vulnerability can cause the Java Runtime Environment to go into a hang, infinite loop, and/or crash resulting in a denial of service exposure. This same hang can occur if the number is written without scientific notation (324 decimal places). In addition to the Application Server being exposed to this attack, any Java program using the Double.parseDouble method is also at risk of this exposure including any customer written application or third party written application.

    The following IBM Tivoli products contain affected versions of the Java Runtime Environment:
    ( big list )
    Thursday, February 24th, 2011
    11:06 am
    [xaminmo]
    VIO 2.2.0.10 FP-24
     Migrated from P6 to P7 via mksysb clone then updates.
    cfgmgr now gives this:
    Method error (/usr/lib/methods/cfgpager -l pager0 ):
        0514-040 Error initializing a device into the kernel.
Method error (/usr/lib/methods/loadkclic -l):
        0514-038 Error loading kernel extension.
loadkclic: load kernel extension failed.

Method error (/usr/lib/perf/cfg_pmsvcs load):
        0514-068 Cause not known.
setup_branchtable: Processor not yet supported.


    The loadkclic is IZ78017 but I can't find anything about the other two.
    The fun thing is that current VIO is AIX 6.1.2.2 and you have to be at 6.1.5.0 to fully exploit POWER7 performance.

    yay.

    I'm going to apply SP01, make a backup, and then make a frankenvio by updating with AIX 6.1.6.3 and see what happens.
    Wednesday, February 23rd, 2011
    10:48 am
    [xaminmo]
    AHAFS - AIX HA File System - New to AIX 6.1.6
     This is entirely from IBM's docs. Some is cut and paste, and some is abbreviated or reworded slightly. No credit is taken for this material. All links herein go back to the source documentation which will have more details.

    In the AIX Event Infrastructure, an event is defined as any change of a state or a value that can be detected by the kernel or a kernel extension at the time the change occurs. The events that can be monitored are represented as files in a pseudo file system.

    The only steps necessary to set up the AIX Event Infrastructure are:
    1. Install the bos.ahafs fileset.
    2. Create the directory for the desired mount point.
    3. mkdir /aha
    4. mount -v ahafs /aha /aha

    Mounting an AIX Event Infrastructure file system will automatically load the kernel extension and create all monitor factories. Only one instance of an AIX Event Infrastructure file system may be mounted at a time. An AIX Event Infrastructure file system may be mounted on any regular directory, but it is suggested that users use /aha.

    Once mounted, the ahafs will contain these structures:
    evProds.list "contains" the names of all currently defined event producers.
    *.monFactory directories are automatically created for each event producer.
    Subdirectories may be used for logical separation within a factory.
    *.mon files within the factory, potentially created on open by the consumer, represent the events that can be monitored. For example, the file /aha/fs/modFile.monFactory/etc/password.mon is used to monitor the modifications to the /etc/passwd file.

    The AIX Event Infrastructure will translate text input written to .mon files into specifications on how the user wants to be notified of event occurrences. Once a user has issued a select() or a blocking read() call to signify the beginning of their monitoring, the AIX Event Infrastructure will notify the corresponding event producer to start monitoring the specified event.

    NOTE: The AIX® Event Infrastructure tracks monitoring per process, and is not thread safe. Processes should not use multiple threads to monitor the same event. Instead, spawn a separate process should the same event need to be monitored in multiple ways.

    An example output for a state change event producer who has specified that a stack trace should be taken:
      BEGIN_EVENT_INFO
      TIME_tvsec=1269377315
      TIME_tvnsec=955475223
      SEQUENCE_NUM=0
      PID=2490594
      UID=0
      UID_LOGIN=0
      GID=0
      PROG_NAME=cat
      RC_FROM_EVPROD=1000
      END_EVENT_INFO

    An example for a threshold value event:
      BEGIN_EVENT_INFO
      TIME_tvsec=1269378095
      TIME_tvnsec=959865951
      SEQUENCE_NUM=0
      CURRENT_VALUE=2
      RC_FROM_EVPROD=1000
      END_EVENT_INFO

    NOTE:Due to the asynchronous nature of process notification, the current value returned may be stale by the time a process reads the monitor file. Users are notified when the threshold is first met or exceeded, but other operations which may alter the values being monitored will not be blocked.

    All directories in the AIX® Event Infrastructure file system have an access mode of 1777 and all files have access mode of 0666. These modes cannot be changed, but the ownership of files and directories may be changed. Access control for monitoring events is done at the event producer level. Creation / modification times are not maintained and are always returned as the current time when issuing stat () on a file object within the pseudo file system. Any attempt to modify these times will return an error.

    More details on monitoring events is available in the publib section on AIX 6.1 System Information on AHAFS

    See Predefined Event Producers for info on what producers come with AIX 6.1.

    Finally, PowerHA (aka HA/CMP) has producers which can show events from other nodes in your active cluster. See Pre-Defined Event Producers for a Cluster-Aware AIX Instance to see what's available in an HA/CMP aka PowerHA environment.
[ << Previous 20 ]
About LiveJournal.com