Resync a node manually

To manually resync a node with the Deployment Manager, shutdown everything on that node and run the syncNode command.
Syntax:

syncNode.bat [options]

WebSphere 5:

syncNode.bat deploymgr 8889 -username username -password password

WebSphere 6:

syncNode.bat deploymgr 8879 -username username -password password

Remove a dead node

The cleanupNode command cleans up a node configuration from the cell repository. Only use this command to clean up a node if you have a node defined in the cell configuration, but the node no longer exists. You must run this command from the install_root/bin directory of a Network Deployment installation.
Note: The cleanupNode command may not remove application server information from clusters when the associated node has already been removed. In these cases, you will need to manually remove entries related to the server from WebSphere Application Server configuration files (cluster.xml, security.xml, multi-broker.xml, EAR deployment descriptors, for example).

Syntax:

cleanupNode [options]

WebSphere 5:

cleanupNode nodename deploymgr 8889 -username username -password password

WebSphere 6:

cleanupNode nodename deploymgr 8879 -username username -password password

Federate a node manually

To federate a node by hand, go to the app server bin directory and run addNode.bat.

Syntax:
addNode.bat [options]

WebSphere 5:

addNode.bat deploymgr 8889 -username username -password password

WebSphere 6:

addNode.bat deploymgr 8879 -username username -password password 

St. Ignace 2009 – PICS

Went to the St. Ignace car show this year. Turnout was pretty good. I hadn’t been in a couple of years, but I think the turnout was slightly up this year. I saw a lot of the same cars as previous years, but there were some new ones too. John Schneider, Bo Duke from the Dukes of Hazard TV show, was there. Got some free stuff courtesy of the Kewadin Casino, and got a free bag from Hagerty Insurance, who I will have to call about insurance on Dad’s 1969 Triumph.

Test network performance

This command test memory to memory copies over rsh (a low overhead protocol). This should be about all the throughput you are going to get from your network adapters:

export RSH_TEST_HOST=hostname
time dd if=/dev/zero count=1000 bs=1M | rsh $RSH_TEST_HOST dd of=/dev/null

If you want to test TCP, here’s the same thing using FTP:

ftp> put "|dd if=/dev/zero bs=1M count=1000" /dev/null

and NCFTP with time:

time dd if=/dev/zero bs=1M count=1000 | /usr/local/bin/ncftpput -u USER -p PASSWORD -c HOST /dev/null

AIX Debug Install

If an installation or migration fails, you can run the install in “debug” mode. Boot from the CD as normal, select the console and language. Then type “911”. The screen should silently refresh without saying anything about an invalid selection. Now continue the install as normal. The output of the scripts the install process runs with show up on the screen. It’s sometimes a lot of data, but you can often see what’s wrong with the install this way.

Storage Pool SHOW commands

Show archives for a given Node within a Policy Set:

SHow Archives PolicySet NodeName

This command will list out all the files in a storage pool that are marked as damaged. To fix them, run an AUDIT VOL command.

SHow DAMAGED poolname

This command was added with TSM version 5.2.2. It will check out all possible destination storage pools for a given client node and tell you if this storage pool can support LAN-free backup and restore.

SHOW LANFREE nodeName storageAgent

Shows the status of the library and its drives:

SHow LIBrary

The fields are:

  • busy=0 means the drive is not mounted or even acquired by TSM.
  • busy=1 should reflect TSM using the drive (Query MOunt). But this could result from drive maintenance. Fix by trying ‘cfgmgr’ AIX command, or killing the lmcpd AIX process and then doing ‘cfgmgr’ or ‘/etc/lmcpd’.
  • online=0 means the drive is “offline”. You can update a drive to be offline, in which case the polled flag will be 0.
  • polled=1 means that TSM could not use the drive for one of three reasons:
    1. The drive is loaded with a Non-TSM volume (eg a cleaner cartridge, or a volume from the other TSM server)
    2. The drive is unavailable to the library manager (usually set this way by load/unload failures)
    3. The drive cannot be opened (some other application has it open, or there’s some connection problem, etc)
  • polled= 1 means the server is polling the drive every 30 seconds to see when the above three conditions all clear (it also means that the online flag should be 0). When the conditions clear, it turns online back to 1 and the drive should now be available to be acquired.

Note that if no tape drive is currently available, TSM will wait rather than kill the client and administrative tasks.

Show all SPACEMGMT Files for node:

SHOW SPAce nodename filespace

Useful for displaying the states and attributes of defined storage pools.

SHOW SSPOOL

You use this command to get statistics from the last migration or backup stgpool process.

SHOW TRANSFERSTATS poolname

This command show the files stored for the node and filespace:

SHOW VERsions nodename filespace

For UNIX clients I’ve had to add namet=unicode. For example,

show versions hnaa * namet=unicode

Shows the volumes being used by a given Node. Does not show Copy Storage Pools. IBM intends to replace this with a similar, supported command.

SHow VOLUMEUSAGE nodename

Database and Log SHOW commands

SHOW BUFSTATS:

Use this command to see if you need to increase your database buffer pool size. An associated command is SHOW BUFV, but it is less obvious what the output means.

Example output is:

    Database Buffer Pool Statistics:

    Total Buffer Latch Requests:   184217213
    Times Scavenging Required:      1123642  0.61%
    Times Scavenging by Stealing:   1105210  0.60%
    Times Scavenging by Waiting:          0  0.00%
    Times Read Required:            1123574  0.61%
    Cache Hit Percentage:             99.39%

SHow BUFVars:

Shows database buffer pool global variables.

SHOW DBTXNT:

Use this command to displays the database transaction table.

Example output is:

    Open objects:
    name ->AS.Segments<- (sp=0)
    name ->SS.Pools<-    (sp=0)
    name ->SS.Pool.Ids<- (sp=0)
    name ->AF.Clusters<- (sp=0)
    Tsn=0:813772319 --> Valid=1, inRollback=0, endNTA=0, State=2, 
    Index=10, LatchCount=0, SavePoint=0, TotLogRecs=0, TotLogBytes=0, 
    UndoLogRecs=0, UndoLogBytes=0, LogReserve=0, PageReserve=0, 
    Elapsed=346279 (secs), MinLsn=0.0.0, MaxLsn=0.0.0, LastLsn=0.0.0, 
    UndoNextLsn=0.0.0, logWriter=False, backupTxn=False

This is showing that this transaction has 4 database tables open, that the transaction is valid, and that it is not writing log records.

SHOW DBV:

Displays database global attributes.

SHOW DBBACKUPVOLS:

Use this command to get details on the latest full and incremental database backup volumes.

SHOW LOGPINNED:

You can use this command if your logfile is running out of space. The oldest active record in the log is pinning the log. This command will tell you what task owns that oldest record. You could follow this up with SHOW LOGPINNED CANCEL which will cancel whatever is holding the pinned record. This is one of those ‘UPDATE’ SHOW commands that you need to use with extreme care, and preferably after advice from Tivoli. However, if your log is rapidly filling up, will you have time to make that support call? It would be best to investigate and test this command before you need to use it in an emergency. The command is only available in TSM version 5.1.7.0 or above.

SHOW LOGV:

You can use this command to display the recovery log global attributes, but it is less obvious what they all mean.

SHOW LOGstats:

Use this command to see statistics on log usage. An associated command is SHOW LOGRESET This command will RESET the log statistics back to 0.