xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
I updated firmware from to on this new v7000.

Trying to re-backup the config, I get:
IBM_2076:v7000:xaminmo>svcconfig backup
CMMVC6202E This command can only be run by the superuser.

CMMVC6156W SVCCONFIG processing completed with errors

I search on this, and 3 hits, all the docs.

Reference > Block storage system messages and codes > Command-line interface messages

The cluster was not modified because the IP address is not valid.

An attempt was made to change the IP address of a cluster to an address that is not valid.
User response

Correct the address and reissue the command.
Parent topic: Command-line interface messages

What makes it most annoying is that:
A) You cannot use the same authorized_keys SSH key for more than one user
B) Only one key attempt is allowed

So, if using pagent, you have to delete the key you used for the other user, and add the one for superuser. You can't have both.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
Today, these are good link lists.

SW/HW Compatibility, drivers, hba bios, etc:

SDDPCM (MPIO) drivers and docs:
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
CMMVC8004E Cannot execute on a node with a location error
This is because the expansion and control cans were swapped between enclosures.
Once fixed and powered back up, cluster config takes 60 seconds (60 amber blinks)
You'll need to recreate your satask.txt if you haven't already.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
Because I couldn't find references to this yet...
xaminmo: (Logo Tivoli Certified New)
[personal profile] xaminmo
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/

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
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
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

daltsmrpt: /install/2012/TSM/631ac# oslevel -s

If I get this sorted out, I'll post about it.
Read more... )
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
TSM Storage Agent 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.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
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 )
xaminmo: (Baby poop)
[personal profile] xaminmo
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:

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
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.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
Because the AvePoint docs are somewhat Engrish and overall not so great, IBM has released a nice whitepaper at:

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:
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.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
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 The IP was, network was .0, gateway .1.

I redefined this as, 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*

xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
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

###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.
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.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
IBM now can crossconnect multiple libraries to make one superlibrary by installing shuttle mechanisms to transfer tapes between libraries automagically:
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
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.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
Original 2011-04 PT 2.5
Updated 2012-06 PT 3.1
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.


• Slots 1 & 2: Dual-port Emulex HBAs for HOST-side (VTL) communication
• Slots 3 & 4: Free PCI slots for Ethernet (for Open Storage API)
• Slot 5 & Integrated Ethernet: Public, Private and Replication networks.
• Slots 6 & 7: Dual-port QLogic HBAs for DISK-side (REPO) communication

OpenStorage API expansion can be 2 more 4-port 1GBE, or can be two 10GBE cards. If ordered as zOS attach, will have 2 pSeries systems and will have 10G ethernet.
Linux	Port	Description
eth0	C5-T1	Public (PTManager)
eth1	C5-T2	Cluster (GFS)
eth2	C5-T3	Replication (RepMan)
eth3	C5-T4	Management (TSSC)
eth4	A1	Cluster (GFS)
eth5	A2	Replication (RepMan)
SYS	B	Management (RSA)

The TS7610/7620 as a hub is limited to 4 replication clients.
The TS7650/7680 as a hub is limited to 12 replication clients.
All models are limited to:
• libraries: 16
• drives: 256/node (512 supported, 1024 architectural limit)
• carts: (55,000 supported, 1million architectural limit)
• LUN Size: 1GB to 8TB (Linux kernel limitation)
• LUN Count: Four to 1000 (single-LUN with RPQ).
How To Install )</PREL
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
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.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
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:

xaminmo: (Logo Tivoli Certified New)
[personal profile] xaminmo
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 )
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
According to the EMC Connectivity Guide for AIX, when using PowerPath greater than, 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 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.
xaminmo: (Logo Tivoli Certified)
[personal profile] xaminmo
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

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.


eserver: (Default)
IBM POWER servers

June 2017

45678 910


RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 25th, 2017 10:30 pm
Powered by Dreamwidth Studios