xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
This changes periodically, but for today, here is what I would do.

My PowerHA selection process would be:
* 7.1.3 SP06 if I needed to deploy quickly, because I have build docs for that.
* 7.1.4 doesn't exist, but if it came out before deployment, I would consider it. Whichever was a newer
Read more... )
xaminmo: (Josh 2004 Happy)
[personal profile] xaminmo
yAy. More TSM issues. There's defect in TSM client 7.1, but IBM says it only exists in 6.3 and 6.4. There's a patch level about 2 weeks old (, but there are no lists of what's fixed in this patch.

I installed this, plus of the VMWare agent, and the node that runs the GUI failed to update. The installer won't uninstall, reinstall, or repair. Windows uninstall just runs their installer.

IBM says that I should not call them, but I should use their simple website to submit a problem report. To report the defect, I have to use my customer's ID. I can't do this as a business partner unless I have my own support contract, beyond the money we pay to have access to support and software on a yearly basis.

To have access to a customer's ID, I have to wait for approval, of course. Beyond that, it shows up in a list that simply says "United States". So if I have, say 10 customers, I have no idea which number is for which customer.

Also, when selecting the product I want, there is no tree. It's a JAVA APPLET which has a list of products. I can search, but the naming is not consistent. Some say "Tivoli Storage Manager" and some say "TSM". Even for different versions of the same product, this naming difference occurs.

When I find it, it says that there will be a delay if I chose this product. Am I sure I want to chose this product? WTF?

There are no places to report any of these errors through the support organization, and no links on the pages to report them either. I have to report them to a general form 8 links away that may or may not be able to help.

Ginny Rometty is so focused on cutting cost to boost stock prices so her stock options at company exit have value, that she's downright gutting the infrastructure required for things like quality assurance and customer usability. Yes, everything is being updated for usability, but if it has worse functionality, or breaks entirely, then it's not REALLY a usability update.

Anyway, after supper, I'm going to call on the phone and listen to all of the messages telling me how easy it is to open a support request online, and that I should hang up and visit the web instead of wasting their dollars to fill out a new PMR that takes them months of training to be able to almost figure out. Then, I'll wait for an email because they don't ever call back anymore, and haven't been live-call-in for years.

The email will ask me to uninstall the software and try again. I won't be able to preemptively tell them anything in advance because I won't have online access to the PMR because I'm waiting for approval and then I have to remember which customer number to look under.
xaminmo: (Josh 2004 Happy)
[personal profile] xaminmo
More and more are moving to access through fixcentral, but for now, HMC recovery media is at:


That looks to be the same as service.software and ftp.boulder.
xaminmo: (Josh 2004 Happy)
[personal profile] xaminmo
This is to prime search engines with something I couldn't find last time I looked.

The new TSM 7.1 operation center, also TSM, also called TSM Operations Center, or internally even TSM Control Center...

The default URL is https://xxx.xxx.xxx.xxx:11090/oc/

The port wasn't in the docs, and the path wasn't in some of the docs. None of it came up Googling.

So frustrating. I had a screen scrape of my install, but somehow missed this, or maybe it's only under advanced?

I couldn't find it in other docs, but Will was able to help me out.
xaminmo: (Josh 2004 Happy)
[personal profile] xaminmo
In the past, I set up TSM.PWD as root, but this seems to not be what I needed.

I'm posting because the error messages and IBM docs don't cover this.

tsmdbmgr.log shows:
ANS2119I An invalid replication server address return code rc value = 2 was received from the server.

TSM Activity log shows:
ANR2983E Database backup terminated due to environment or setup issue related to DSMI_DIR - DB2 sqlcode -2033 sqlerrmc 168. (SESSION: 1, PROCESS: 9)

db2diag.log shows:

2014-02-26- E415619A371 LEVEL: Error
PID : 15138852 TID : 1 PROC : db2vend
INSTANCE: tsminst1 NODE : 000
HOSTNAME: tsmserver
FUNCTION: DB2 UDB, database utilities, sqluvint, probe:321
DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
TSM RC=0x000000A8=168 -- see TSM API Reference for meaning.

EDUID : 38753 EDUNAME: db2med.35926.0 (TSMDB1) 0
FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog, probe:656
DATA #1 : String, 134 bytes
Vendor error: rc = 11 returned from function sqluvint.
Return_code structure from vendor library /tsm/tsminst1/sqllib/adsm/libtsm.a:

DATA #2 : Hexdump, 48 bytes
0x0A00030462F0C4D0 : 0000 00A8 3332 3120 3136 3800 0000 0000 ....321 168.....
0x0A00030462F0C4E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0A00030462F0C4F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

EDUID : 38753 EDUNAME: db2med.35926.0 (TSMDB1) 0
FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog, probe:696
MESSAGE : Error in vendor support code at line: 321 rc: 168

RC 168 per dsmrc.h means:
#define DSM_RC_NO_PASS_FILE 168 /* password file needed and user is
not root */

Verified everything required for this:
• passworddir points to the right directory
• DSMI_DIR points to the right directory
• dsmtca runs okay
• dsmapipw runs okay

Verified hostname info was correct

dsmffdc.log shows:
[ FFDC_GENERAL_SERVER_ERROR ]: (rdbdb.c:4200) GetOtherLogsUsageInfo failed, rc=2813, archLogDir = /tsm/arch.

Checked, and the log directory inside dsmserv.opt was typoed as /tsm/arch instead of /tsm/arc as was used to create the instance and as exists on the filesystems.

Updated dsmserv.opt and restarted tsm server. No change other than fixing Q LOG

The TSM.PWD file must be owned by the instance user, not by root.
Make sure to run the dsmapipw as the instance user, or chown the file after.

Simple, and fairly obvious, but maybe not always so obvious.
xaminmo: (Josh 2004 Happy)
[personal profile] xaminmo
I ran into an issue that might be procedural, but I though you guys might want to know anyway.

We are pursuing with IBM HW support as of 2013-07-18.
I am going to test further in my lab. I suspect this may be related to
bkprofata and rstprofdata copying over some internal seed for MAC addresses

I plan to try this in my lab on p5 rackmount servers via an HMC.
If I can reproduce it there, then I expect support's response to be "don't do that".
As such, I also will try a factory reset to see if that will clear the condition.

If I cannot reproduce it there, then it's either SDMC/FSM related (which is going away),
or it's blade/Flex Node related (No other test resources, but maybe L3 can help).

If L3 decides that rstprofdata cannot be used on a different system,
then I would want them to A) Limit the command to that functionality,
and B) Update documentation for both commands to reflect this.

bkprofdata & rstprofdata were used to clone the LPAR layout from one blade to another.
To reset the WWNs, I was able to delete and re-add the virtual fibre adapters.
New LPARs and new virtual fibre adapters automatically get WWNs with the blade/node number as part of the WWN.
This part works as I would expect.

To reset the MAC addresses, this did not work.
Delete and re-add virtual ethernet adapters does not change the MAC addresses.
Adding a new adapter that did not exist before to the same slot number,
on the same LPAR ID, on two different Flex nodes, and both get the same MAC accress.

Current resolution is to override the MAC address with a user specified value in the LPAR profile.
This can be done from Profile -> Virtual -> Ethernet -> Advanced -> checkbox

Change from commandline:
chsyscfg -m Server-7895-23X-SN1012345 -r prof -i \

To remove and Readd:
chsyscfg -m Server-7895-23X-SN1012345 -r prof -i \
chsyscfg -m Server-7895-23X-SN1012345 -r prof -i \

I've never seen this happen on any other POWER series servers, and I've built a lot of p7 systems, ranging from p710 to p780, including matching LPARs between CECs. This is on top of the whole slew of LPARable systems I've built and/or supported.

I looked into the profile data backup files themselves, and there is no mention of system serial, system name, WWN prefix, or MAC prefix.

I restored mode 3 of the profile data backups prior to any config work, and when adding new virtual NICs to LPARs, the MAC addresses still mirror eachother.

I plan to test this with two p505 systems on an HMC to see if similar issues occur.

I don't have the resources to test this on blades, or on another SDMC.

We are pursuing with IBM HW support as of 2013-07-18

### END NOTICE ###

After a week, still no no response from support,
but I think I found out why this was a problem.

On physical hardware, "lssyscfg -r lpar" will show virtual_eth_mac_base_value=
On the flex nodes, this value is not exposed.

I can't tell if this is an SDMC/FSM limitation, or a flex node limitation.
I know that IVM sees it, but am not sure about HMC.

So, when LPAR profiles are copied over, they will bring the VEMBV,
and there is no way to change it short of deleting and re-creating.

All in all, it may just be easier to use mksyscfg from the start.
An example might be:

mksyscfg -r lpar -m Server-8205-E6D-SN10FFFFF -i profile_name=DefaultProfile,\

But there's already reference online for this sort of command.

Also, while working on a p740 via IVM, I ran into more differences from HMC/SDMC.
When you add a client LPAR with virtual SCSI, IVM automagically creates the VIO server virtual scsi server adapter. In addition, +1 from that slot it creates a virtual serial adapter for mkvterm.

If you're used to adding virtual scsi adapters in order, and you don't skip a slot on the mksyscfg lines, then you'll get this error:
[VIOSE01050173-0290] Cannot create virtual serial adapter in the management partition in the virtual slot number specified 20.

I couldn't find this error anywhere else on the internet, and it was a little confusing since I wasn't making a virtual serial adapter.
xaminmo: (Computer Drive)
[personal profile] xaminmo
Info from digging into DS6800 (baby shark) which I didn't find online.
It's pretty sparse for the actual raw troubleshooting.
Basically though, it looks like there are recurring I/O channel failures for the primary processor card.
This has been replaced before, so it's probably a chassis issue.
There were power failures, so maybe it's a poor power regulation issue.
The PSU should take the hit and not kill the proc cards.

Since the site PDU was replaced, hopefully those problems will be gone.

Anyway, a CE is coming out to replace this processor card.
Read more... )


Dec. 4th, 2012 12:45 pm
xaminmo: (Josh 2004 Happy)
[personal profile] xaminmo
So, it came out 2 months ago, but here's the summary:
* D model numbers (9117-MMD, 9719-MHD, etc)
* Up to 128 cores in a p780+ (vs 96 in MMC)
* Double the RAM capacity (4 TB)
* CoD CPU and RAM can be in a pool shared by multiple systems.

* AIX 7.1 TL2, 71TL01SP06, 71TL00SP08, 61TL08, 61TL07SP06, 61TL06SP10
* AIX 5.3 TL12 SP07 (Expected but not released yet. Only for extended support)
* VIO 2220, VIO2215 (Dec19)
* HMC 7.7.6 (CR3 or later, and 3GB of RAM if over 256 LPARs total)
* i6.1 only supported through VIO or i7.1 client.

New 1.8" SSD enclosure:
* UltraSSD: New 1U drawer with 30SSDs (GX++ PCIe Cable and two SAS RAID controllers)
* UltraSSD 1U drawer has four 4xSAS ports for running two EXP24S 2U drawers.
* UltraSSD controllers will support EASY TIER for AIX and VIO in 2013.
* UltraSSD will be added to DS8k line in 2013.

New Disk-as-Tape device:
* "RDX" Removable Disk - looks like tape, but it hot-swap disk to replace pre-LTO tech.
* RDX SATA supported on iSeries as optical
* RDX USB supported on AIX and VIO as well.

New I/O components:
* IBM Rackswitch options, with 1GB, 10GB and 40GB ethernet ports.
* PCIe2 dual-port Remote DMA over Ethernet (vs Infiniband for low latency MPI)
* GX++ Dual Port 10gbit FCoE or 10gbit FC Adapters for p770/p780 (no Linux. iSeries through VIO)
* GX++ Dual Port 16GBFC or 10GBFCoE Adapters for p795 (no Linux or iSeries)

Hardware Enhancements:
* 4 sockets per CPU card (vs 2-sockets)
* Supports 64GB DIMMs (vs 32GB)
* Lower heat/power consumption with 32nm vs 45nm
* Better performance per core with 10MB L3 Cache vs 4MB and up to 4.4GHz
* Active Memory Expansion performance improved with on-chip Compression Accelerator
* Crypto accelerator for AES, SHA and RSA
* Random number generator on die
* Four floating point pipelines vs 2 (single precision takes 1, DP takes 2)
* Higher concurrency during firmware updates (Can reset one core at a time)
* Higher uptime with redundant lanes in cache and in CEC interconnect cables
* CPU upgrades for MMA, MMB and MMC will include new CEC enclosures.
* Free CoD: Includes 240GB memory days and 15 processor days per CPU initially shipped
* Free CoD: Includes 90 days of full activation (one shot)
* http://www-03.ibm.com/partnerworld/partnerinfo/src/atsmastr.nsf/WebIndex/TD105846

FLEX Hardware:
* p260 and p460 dual-port FCoE Mezzanine to support dual VIO
* New FCoE 8-port switch module to support new FCoE mezzanine cards
* New FC switch module
* New v7000 module
* New USB-3 storage drawer (1x RDX, 2X DVD-RAM)

Hardware Withdrawals:
* No PCI-X, HSL, RIO-1, or IOP support in POWER8
* 3.5" SAS drawers to be withdrawn in 2013.
* SCSI DISK SUPPORT IS DROPPED!!! SCSI Tape still okay on PCI-X #5736 in I/O drawer
xaminmo: (Logo IBM CATE)
[personal profile] xaminmo
I always run into issues when I work in a multiple VLAN environment, because it's not *that* common for my builds. This is a reminder for me.

The magic is when using multiple VLANs:
1) Don't use the real VLAN ID for the trunk PVID unless you know for certain that was set on the switch. It is stripped off of all packets, and who knows what the PVID of the switch is, if any.
2) Any mismatch between PVID on the SEA and the trunk will cause packets to be dropped.
3) Don't use IEEE VLAN mode for the client adapter unless you're going to add VLAN interfaces from AIX. When not in VLAN mode, the PVID is ADDED to all packets on client adapters.
4) When using multiple trunks on one SEA, they all have to be the same trunk priority. ha_mode=sharing balances not using trunk priority, but based on the order of the virt_adapters field.
xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
This is from a decade ago, so I thought it time to update the URLs and post it to LJ.

Here is information on how to decode SCSI Sense Data. This revolved around IBM Magstar products since that is where I was first exposed to the guts of SCSI errors.

The AIX Error Report records for TAPE_ERR# (usually 1-6) often include SENSE DATA in the Detail section. A SCSI LOG PAGE 06h can be parsed manually to provide the SENSE KEY, ASC and ASCQ values, as well as the ERROR CODE which will tell us if it is current or past errors being reported. An example Log Page 6 is below:
	0600 0000 0300 0000 FF80 0000 0000 0000 0000 0000 7000 0000 0000 0015 0000 000B 
	0000 0000 001C 7F00 2000 0033 7E58 0000 0000 0000 0000 0000 0000 0000 0000 0000 
	0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 
	0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 
	0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 B041 0000 0000 

If you'll notice, byte 0 is 06. Also note that there are 32 bytes per line, and two hex digits per byte.

Byte 20 represents the SCSI error class. Valid classes are:
    * 70 - Current Error (Direct Access Logical Block NOT From Sense Data).
    * F0 - Current Error (Direct Access Logical Block IS From Sense Data)
    * 71 - Deferred Error (Direct Access Logical Block NOT From Sense Data).
    * 7F - Vendor Spec. Error (Direct Access Logical Block NOT From Sense Data).
    * EE - Encryption Error
    * F1 - Deferred Error (Direct Access Logical Block IS From Sense Data).
    * FF - Vendor Spec. Error (Direct Access Logical Block IS From Sense Data).

In this example, EC (byte 20) is 70, which is valid and means this is a current error.

When the error class is valid, we can get the sense key from byte 22.

In this example, the sense key is 00 (zero) which means "NO ADDITIONAL SENSE". The standard list of sense keys is:
	X0 - No Sense         X6 - Unit Attention    XC - Equal.
	X1 - Recovered Error  X7 - Data Protect      XD - Volume Overflow.
	X2 - Not Ready        X8 - Blank Check       XE - Miscompare.
	X3 - Medium Error     X9 - Vendor Specific   XF - RESERVED.
	X4 - Hardware Error   XA - Copy Aborted
	X5 - Illegal Request  XB - Aborted Command

ASC is at byte 32 (first byte on line 2) and ASCQ is byte 33.

The ASC and ASCQ chart is pretty extensive. Please see the ASC/ASCQ Code Listing from the SCSI Technical Committee for an authoritative reference:

Note also that sometimes the ASC/ASCQ pair you're looking up may fall under a different sense key than is expected. The Sense key gives general information, such as "Recovered error", "hardware error", or the like. The ASC/ASCQ pair tells what the actual problem is. This isn't always 100% helpful, but is close.

Good reference was had from the 3590 Maintenance Information Guide, Msgs section. This gives 90% of what anyone would need to decode SCSI LOG PAGE 06h messages for IBM tape drives. The Jaguar Tape Drives (IBM 3590 & 3592) Information Center is at:

Included within are how to decode SIM/MIM Records, Log Page 6, and other related information. The 3590 Hardware Reference Guide, Appendix B also shows decent information in regards to non SIM/MIM errors. It makes reference to sense key and ASC/ASCQ bytes. You can acquire PDF copies of tape removable media storage systems' manuals via the following URLS:

The Magstar Maintenance and Ultrium SCSI Reference books makes reference to "Fault Symptom Codes" which are more definitive; however, due to confidentiality of the 3590 microcode, a complete list of fault symptom codes is not available.

For encryption records, see the Troubleshooting section of the IBM TS3500 Tape Library (IBM 3584) Information Center:

The above also has general SCSI SENSE KEY/ASC/ASCQ and extended IBM codes under the Reference section.

There are other ways to get this information, but this was easiest for me.

Yours truly,
Josh Davis
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
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
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: 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: Josh 2016 (Default)
[personal profile] xaminmo
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.

xaminmo: Josh 2016 (Default)
[personal profile] xaminmo
On Thu, 7 Feb 2002 14:41:06, I posted this to ADSM.ORG. Amazingly, other than the DB volume portion and the TIVOLI URL, it still pretty much applies today.

I've found out that IBM *and* consultants are using this text verbatim but stripping my name from it. I never put a copyright on this, but it's still very poor form not to give credit to your sources. You can search the web and find my post of this archived on ADSM.ORG, among other places.

Anyway, reposting here with a few minor tweaks below. I'm not really adding in the stuff for TSM 6.x base install due to complexity and platform variability. Ok, because I'm being lazy.

Basic In-Order TSM Server Setup Checklist
I whipped this up because I run into so many people who want to figure
it out on their own, but really are just lost in the slew of new
concepts.  Here is a basic list of things to do when setting up your tsm
server the first time.  Suggestions and corrections are welcome.


Physical Installation:
   Install physical devices
   Power on system
   Install o/s maintenance
   Install tsm server and drivers
   Define devices to the O/S
      349x, 357x, 358x and 359x use Atape/IBMTAPE/lmcpd
      all others use TSM drivers

Make a larger database and log: (Pre 6.x style)
   define dbvolume        (make space)
   define dbcopy          (mirror elsewhere)
   extend db              (tell tsm to use the new space)
   define logv            (make space)
   define logc            (mirror elsewhere)
   extend log             (tell tsm to use the new space)
   define spacetrigger    (auto-grow db and log)
   define dbbackuptrigger (only if SET LOGMODE ROLLFORWARD)

Ensure proper licensing:
   register license       (see the server/bin directory)

Storage setup inside TSM:
   define library          (top level of tape storage)
   define devclass         (points to a library)
   define drive            (points to a library)
   define stg              (points to a device class)
   define vol              (points to a devclass and storage pool)
   label libvol            (prepares a tape for TSM use)
   checkin libv            (makes tape show up in Q LIBVOL)

For Policy/Node Information:
   define domain           (top level of policy information)
   define policyset        (contained within a policy domain)
   define mgmtclass        (contained within policyset)
   define copygroup T=BACK (contained within a management class)
   define copygroup T=ARCH (contained within a management class)
   activate policy         (only one policyset active per domain)
   register node           (belongs to a policy domain)

Typical Storage Pool Hierarchy:
   Copygroup "destination" is disk pool
   Disk pool "NEXT" is tape pool
   An extra tape pool of type "COPYPOOL"

Other Important Things to Look Into:
   Administrator's Guide, Working With Network of TSM Servers
      Virtual Volumes
      Library Sharing
   Administrator's Guide, Chapter 1: Introduction
      Overview of storage hierarchy and TSM concepts
   Administrator's Guide, Protecting The Server
      Protection and recovery of the system
   Administrator's Guide, Disaster Recovery Manager
      Integrated, licensed tool for server protection
      client backup schedules
      server administrative schedules (don't overlap these)
         BACKUP STG (sync up copy pool)
         UPDATE STG RECLAIM=50 (reclaim free space from tapes)
         UPDATE STG RECLAIM=100 (turn off reclaimation)
         UPDATE STG HI=0 LO=0  (migrate the disk pool to tape)
         UPDATE STG HI=90 LO=70  (migrate only during overflow)
         BACKUP DB (TSM database is critical to server function)
         BACKUP DEVCONFIG (Device config DB in text format for DB recovery)
         BACKUP VOLHISTORY (List of volumes used in DB recovery)

In all procedures WATCH FOR ERRORS.

If you have questions, see Documentation at:
   * TSM v5.5: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1
   * TSM v6.1: http://publib.boulder.ibm.com/infocenter/tsminfo/v6
   * TSM v6.2: http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2

TSM Administrator's Guide is procedural information
TSM Administrator's Reference is command syntax
TSM Messages Guide is decyphering for ANR/ANS messages

Also, *the* reference from Richard B. Sims:
xaminmo: (Josh 2004 Happy)
[personal profile] xaminmo
So far, IBM says you cannot mount a USB mass storage device. I wanted to test this out a bit.
Howto and Details )
Suffice it to say that if you're willing to do a little but of manual work for the set-up, it's very usable.

UPDATE 2014-07-29: Minor typos and cleanup. Also, note that LVM is still not allowed on USBMSDs, even with AIX 7.1.

UPDATE 2015-05-21: In case it was not obvious, this is not supported by IBM. Currently, it's not in any whitebook, and ZTRANS says it's not supported. The biggest issue is a risk of kernel panic of the USB device is unplugged. Many of the safety mechanisms for filesystems going offline would be handled by LVM, which is completely bypassed. Doing this with a ramdisk is one thing, since if RAM goes away, you're in trouble anyway. Still no support for USBMSD being in a volume group.

Also, an IBMer had claimed copyright on the procedure in 2014, but that was rejected and deleted in 2015, mostly because it ended up in a defect complaint due to USB pull kernel panic.


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:28 pm
Powered by Dreamwidth Studios