tsm sa aix installation

Installation and Configuration

Tivoli Storage Manager

Storage Agent (LAN-Free)

OnAIX Platform

Prepared By

January 12, 2007Version 1.0The information in this document shall not be disclosed outside the Capital One organization and shall not be duplicated, used or disclosed in whole or in part for any purpose other than to evaluate this document. Capital One shall have the right to duplicate, use or disclose the information to the extent provided by the contract. This restriction does not limit the right of Capital One to use information contained in this document if it is obtained from another source without restriction. The information provided to Capital One in this document was designed and developed from the existing know-how and experience of Tivoli Systems Inc. Tivoli Systems Inc. shall have the right to disclose and use such information with other Customers as it sees fit. Tivoli Systems Inc. shall also have the right to use or disclose information or know-how developed or learned in the course of performance under any agreement for services offered in this document that relate generally to the art of software development, providing software services or programming for distributed systems management software, provided that such information is not infringing on any existing patent or copyright of Capital One

Table of Contents2Installation and Configuration of TSM SA on AIX.

2Pre-requisites

3Installation

10Configuration

55Uninstall

Installation and Configuration of TSM SA on AIX.

Pre-requisites

1. AIX System Administration skills including software installation and configuration.

2. Need root user id and password.

3. TSM BAC Client code and API is required to be installed on the system. Follow the instructions in TSM BAC AIX Installation document for details.4. Need to have the following filesets available before starting the installation:

tivoli.tsm.StorageAgent.rte 5.3.3.1 (IBM Tivoli Storage Agent Runtime)

tivoli.tsm.devices.aix5.rte 5.3.3.1 (IBM Tivoli Storage Manager Device Support runtime)

3. Minimum disk space requirement:

a. Temporary 140MB: Need about 70MB for staging the tar ball and another 70MB for inflating it.

b. Permanent 200MB: Need about 200MB for installation of the product.4. Default Installation location is /usr/tivoli/tsm/StorageAgent.5. Atape IBM AIX Enhanced Tape and Medium Changer Device Driver 9.7.3.0 (Atape.driver) driver is required to be installed for access to VTL LTO2 drives.

Note: A reboot after install is needed to load the device driver in the memory.

6. For exact alignment and mapping of the drives between the Storage Agent system and the TSM server, need the information about the drives (serial number, WWPN) on the VTL.7. Ensure that the server system and client systems are attached to the SAN along with appropriate storage devices. Also the server system and client systems must be connected by means of LAN.

8. Ensure that the VTL resources are already configured and allocated to the Storage Agent as documented in TSM VTL RESOURCES ASSIGNMENT.doc present in the toolkit already.

9. The storage agent should NOT be installed on the same machine as the Tivoli Storage Manager server.

10. Do NOT forget to stop all existing TSM products prior to installing the storage agent. Installation will stop when an active TSM process is detected. If this occurs, close all active TSM products and retry the installation.

Installation

1. Login as root.

2. Stage the software in the temporary location, this document uses /usr/SA, then type smitty install_latest and press Enter key:

3. Keep the default _all_latest for SOFTWARE to install, yes for COMMIT and select yes for ACCEPT new license agreements, then press ENTER:

4. Press ENTER to confirm the installation:

5. Here is the screenshot showing the progress of the install:

6. Confirm the status of SUCCESS in Result column as shown below:

7. Issue lppchk v, if the integrity of the filesets is confirmed, it will return to the command prompt silently (no output). Also check the return code as echo $? immediately after the above command, it should hold the value of 0 as shown:

8. Issue lslpp aL tivoli*rte Atape* and confirm that the filesets are installed as shown below:

9. After verification of the installation, issue shutdown Fr to reboot to load the device driver in the memory:

Configuration

1. Configure the VTL Tape Drives on TS7510 by following the procedures in the TSM VTL Resources Assignment.doc.2. Detect the VTL drives on the SAN client ANIMAL_SAN as follows:i. First verify that there are no 3580 drives pre-existing, also find the WWPN number of the HBA configured as: lsdev Ct3580 lscfg vl fcs | grep i Net {where is the adapter number, in our case fcs2}

ii. Run cfgmgr vl fcs2 to detect the configured VTL drives:

iii. Run lsdev Ct3580 to verify the devices picked up by cfgmgr:

iv. List the attributes of the tape drives as shown below:

This completes the configuration of the VTL drives at the OS level of the Storage Agent.

3. Detect the VTL library resources on the TSM server KNOTSM03:i. Verify if the tape drives/libraries are pre-existing or pre-configured:

lsdev Ct3580

lsdev Ct3584

Alternatively, you can issue the command below to give the same results: lsdev Ct358*

ii. Determine the WWPN numbers of the HBA adapters in question by creating and then running the script as shown below:# cat /home/kov531/fcs_wwpn.sh

lsdev -Cc adapter -Fname|grep -E 'fcs[5,8]|fcs1[1,4]'|while read fcs

do

echo "($fcs):$(lscfg -vl $fcs|grep Net)"

done

iii. Then run cfgmgr vl fcs on each of the HBA adapters to pick the devices configured as shown in the next three screenshots: cfgmgr vl fcs5

cfgmgr vl fcs8

cfgmgr vl fcs11

iv. List the devices detected as shown in the next screenshots:

lsdev Ct358* | more

v. Verify that the count of devices detected agrees with VTL allocation: lsdev Ct358* | more

4. Establish the one-on-one alignment (i.e. mapping) of tape drives between the Storage-agent machine and the TSM server using the following procedure:i. On the Storage Agent machine (i.e. JOSIE_STA), list the tape-drives and make note of the Serial Number:

lsdev Ct3840 Fname | while read rmt

do

echo "$rmt -> $(lscfg -vl $rmt | grep -i Serial)done

ii. List the serial numbers of the tape drives detected by running this command

(This serial number range of '1167229506[6-8] was taken from the storage agent as shown in the previous step, we are trying to map those to the rmt drives on the TSM server):

#!/bin/ksh

lsdev -Ct3580 -Fname | while read rmt

do

lscfg -vl $rmt|grep Ser|sed 's/Serial Number//g;s/[ ]*//g;s/[\.]*//g'| grep -E '1167229506|1167229507|1167229508'|read sernum

[[ -n $sernum ]] && echo "$rmt -> $(lscfg -vl $rmt | grep -i Serial)"

done

Note the rmt drives shown along with their Serial Number.

iii. List the serial number of the tape library:

Here is the tableshowing the mapping of the drives between the TSM server and the storage agent with their respective serial numbers:

Tape Drive/Library (KNOTSM03)Tape Drive (JOSIE_STA)Serial Number

rmt66rmt121167229506

rmt67rmt131167229507

rmt68rmt141167229508

smc0N/A5KAYY00300

Configuration Information Worksheets

The following worksheets used to record information about the client and server systems have proved to be very helpful to install and configure the storage agent. Definitions for the terms in the worksheets are given in the worksheets.

Table 1. Client System Configuration Information

Client System

Storage agent properties

Enter information about the storage agent that you will need when you define the storage agent as a server to the Tivoli Storage Manager server.

Name: Enter the name for the storage agent. For example, enter storagnt.

JOSIE_STA

Password: Enter the password for the storage agent. For example, enter fun4me.

JOSIE123

TCP/IP address: Enter the TCP/IP address of the storage agent. For example, enter agent.tucson.ibm.com.204.63.58.51

TCP/IP port: Enter the TCP/IP port of the client system.1500

Client options

LAN-free communications method (lanfreecommmethod client option): Circle the communications method you choose for the LAN-free data movement function. TCPIP

SharedMemory

LAN-free port (lanfreetcpport client option): Enter the TCP/IP port used for the LAN-free data movement function.1500

Device informationn/a

External libraryn/a

Executable location: Enter the fully qualified path to the external library manager executable for each storage agent to which Tivoli Storage Manager can send media access requests.n/a

Library name: Enter a name of your choosing that is less than or equal to 32 characters.n/a

ACSLS, 3494, or SCSI drive device names

Enter the names of the tape drives for which you will define paths.. This info can be obtained from the /opt/IBMtape/tapelist command.

Drive 1/dev/rmt12 (S/N:1167229506)

Drive 2/dev/rmt13(S/N:1167229507)

Drive 3/dev/rmt14(S/N:1167229508)

Drive 4N/A

Shared disk

Local path name: Enter the name of the local path to the network-mounted file system. For example, enter /shareddisk.

n/a

Table 2. Server System Configuration Information

Server System

Server properties

Enter information about the Tivoli Storage Manager server that the storage agent will need to communicate with the server. You can verify the server information by issuing the QUERY STATUS command from a Tivoli Storage Manager administrative command line.

Name: Enter the name of the server. For example, enter tsmsrver. KDCTSM03

Password: Enter the password for the storage agent. For example, enter fun4me. capitalone

TCP/IP address: Enter the TCP/IP address for the server. For example, enter tsmsrver.tucson.ibm.com. 10.9.209.11

TCP/IP port: Enter the TCP/IP port for the server. For example, enter 1502.1500

Device information

External library

Executable location: Enter the fully qualified path to the external library manager executable for each storage agent to which Tivoli Storage Manager can send media access requests.

Library name: Enter a name of your choosing that is less than or equal to 32 characters.

ACSLS, 3494, or SCSI library information

Library name: Enter the name of an ACSLS, 3494, or SCSI library.

Library device name: Enter the device name for an ACSLS, 3494, or SCSI library, which you will use when you define the path.

ACSLS, 3494, or SCSI drive device names

Enter the names of the tape drives for which you will define paths. This info can be obtained from the /opt/IBMtape/tapelist command.

Drive 1 /dev/rmt66

(S/N: 1167229506)

Drive 2 /dev/ rmt67

(S/N: 1167229507)

Drive 3 /dev/ rmt68 (S/N: 1167229508)

Drive 4N/A

Shared disk

Local path name: Enter the name of the local path to the network-mounted file system. For example, enter /shareddisk.N/A

Client node names

Record the names of the client nodes on which you will install and configure the storage agent. This information will be needed when you register the nodes, set the policy for them, and place any needed restrictions on them. JOSIE_SYSTEM_BKUP

This completes the one-to-one mapping/alignment of the drives, this will be put to use in the next sections.

5. Configure the Backup-Archive TSM Server instance(KDCTSM03) using the procedure below:i. Define the device class VTL_LTO2 using the macro below:/* def_vtl_devc.dsm */

DEFine DEVclass VTL_LTO2 -

LIBRary=T3V5LI -

DEVType=LTO -

FORMAT=ULTRIUM2 -

ESTCAPacity=200G -

MOUNTRetention=5 -

MOUNTLimit=3

MOUNTWait=5The Screen-shot is shown below:

ii. Define the storage pool VTL_NONP_FS using the macro below:

/* def_vtl_stg.dsm */

DEFine STGpool VTL_NONP_FS VTL_LTO2

POoltype=PRimary -

DESCription="Storage pool for NonProduction Machines" -

ACCess=READWrite -

MAXSIze=NOLimit -

CRCData=No -

NEXTstgpool=TP_NONP_FS -

HIghmig=90 -

LOwmig=70 -

REClaim=60 -

RECLAIMPRocess=1 -

RECLAMATIONType=THRESHold -

COLlocate=GRoup -

MAXSCRatch=100 -

REUsedelay=0 -

MIGDelay=0 -

MIGContinue=Yes -

MIGPRocess=1 -

DATAFormat=NATive

The Screen-shot is shown below:

iii. Define the domain UNIX_SAN_NONP_FS with its policyset UNIX_SAN_NONP_FS_POL and management-class UNIX_SAN_NONP_FS_MC using the macro below:

/* def_dom_policyset_mgmt_copyg.dsm */

DEFine DOmain UNIX_SAN_NONP_FS -

DESCription="Policy Domain for backing NonProduction UNIX machines" -

BACKRETention=30 -

ARCHRETention=365

DEFine POlicyset UNIX_SAN_NONP_FS UNIX_SAN_NONP_FS_POL -

DESCription="Policy Set for backing NonProduction UNIX machines"

DEFine MGmtclass UNIX_SAN_NONP_FS UNIX_SAN_NONP_FS_POL UNIX_SAN_NONP_FS_MC -

SPACEMGTECHnique=NONE -

AUTOMIGNOnuse=0 -

MIGREQUIRESBkup=Yes -

MIGDESTination=SPACEMGPOOL-

DESCription="MGMT Class for backing NonProduction UNIX machines"

DEFine COpygroup UNIX_SAN_NONP_FS UNIX_SAN_NONP_FS_POL UNIX_SAN_NONP_FS_MC -

Type=Backup -

DESTination= VTL_NONP_FS -

VERExists=NOLimit -

VERDeleted=NOLimit -

RETExtra=31 -

RETOnly=31 -

MODE=MODified -

SERialization=STatic

The screen-shot below shows the creation (on KDCTSM01 -since it is a CONFIG_MANAGER which pushed the profile definition to KDCTSM03, one of its managed servers):

iv. First assign the management class UNIX_SAN_NONP_FS_MC as the default one in the policyset UNIX_SAN_NONP_FS_POL in domain UNIX_SAN_NONP_FS. Then validate and activate the policyset using the macro:/* assign_validate_activate.dsm */

ASSIGN DEFMGMTCLASS UNIX_SAN_NONP_FS UNIX_SAN_NONP_FS_POL UNIX_SAN_NONP_FS_MCVALIDATE POLICYSET UNIX_SAN_NONP_FS UNIX_SAN_NONP_FS_POL ACTIVATE POLICYSET UNIX_SAN_NONP_FS UNIX_SAN_NONP_FS_POL The screen-shots are shown below (on KDCTSM01 -since it is a CONFIG_MANAGER which pushed the profile definition to KDCTSM03, one of its managed servers):

Since the domain definition was pushed by CONFIG_MANAGER beforehand, need to activate the policyset which does NOT happen automatically:

ACTIVATE POLICYSET UNIX_SAN_NONP_FS UNIX_SAN_NONP_FS_POL

v. If is NOT done already, register node JOSIE_system_bkup. Register to domain UNIX_SAN_NONP_FS using the macro below:/* reg_node_system_bkup.dsm */

REGister Node josie_system_bkup josie123 -

PASSExp=0 -

USerid=NONE -

CONtact="CapitalOne" -

DOmain= UNIX_SAN_NONP_FS -

COMPression=Client -

ARCHDELete=Yes -

BACKDELete=No -

FORCEPwreset=No -

Type=Client -

MAXNUMMP=3 -

URL=josie:1581 -

AUTOFSRename=Yes -

KEEPMP=No -

VALIdateprotocol=All -

TXNGroupmax=0 -

DATAWritepath=ANY -

DATAReadpath=ANY -

SESSIONINITiation=Clientorserver -

HLAddress=josie -

LLAddress=1501

However in our case, since the node was pre-registered but belonged to another domain, we only updated it by changing its domain as shown below: update node JOSIE_SYSTEM_BKUP domain=UNIX_SAN_NONP_FSThe Screen-shot is shown below:

vi. Define the server JOSIE_STA using the macro below:/* def_server_stgagent.dsm */

DEFine SERver JOSIE_STA -

SERVERPAssword=josie123 -

HLAddress=josie -

LLAddress=1500 -

COMMmethod=tcpip


vii. Define library T3V5LI and its path to the server KDCTSM03 using the macro below:/* def_vtl_libr.dsm */

DEFine LIBRary T3V5LI -

LIBType=SCSI -

SHAREd=Yes -

AUTOLabel=OVERWRITE -

RESETDrives=NO

DEFine PATH KDCTSM03 T3V5LI -

SRCType=SERVer -

DESTType=LIBRary AUTODetect=Yes -

DEVIce=/dev/smc0 -

ONLine=Yes


viii. Define drives JOSIE_DR1, JOSIE_DR2 and JOSIE_DR3 in library T3V5LI using the macro below:/* def_vtl_drv.dsm */

DEFine DRive T3V5LI JOSIE_DR1 -

SERial=AUTODetect -

ONLine=Yes -

ELEMent=AUTODetect -

CLEANFREQuency=NONE


SERial=AUTODetect -

ONLine=Yes -


CLEANFREQuency=NONE


SERial=AUTODetect -

ONLine=Yes -


CLEANFREQuency=NONE


ix. Define path to JOSIE_DR1, JOSIE_DR2 and JOSIE_DR3 from server KDCTSM03 using the macro below:/* def_vtl_drv_path_tsmserver.dsm */

/* Define PATH to the drives from the TSM server */

DEFine PATH KDCTSM03 JOSIE_DR1 -

SRCType=SERVer -

AUTODetect=Yes -

DESTType=DRive -

LIBRary= T3V5LI -

DEVIce=/dev/rmt66 -

ONLine=YesDEFine PATH KDCTSM03 JOSIE_DR2 -

SRCType=SERVer -

AUTODetect=Yes -

DESTType=DRive -

LIBRary= T3V5LI -

DEVIce=/dev/rmt67 -

ONLine=YesDEFine PATH KDCTSM03 JOSIE_DR3 -

SRCType=SERVer -

AUTODetect=Yes -

DESTType=DRive -

LIBRary= T3V5LI -

DEVIce=/dev/rmt68 -

ONLine=Yes/* Define PATH to the drives from the STORAGE-AGENT server */

DEFine PATH JOSIE_STA JOSIE_DR1 -

SRCType=SERVer -

AUTODetect=Yes -

DESTType=DRive -

LIBRary= T3V5LI -

DEVIce=/dev/rmt12 -

ONLine=YesDEFine PATH JOSIE_STA JOSIE_DR2 -

SRCType=SERVer -

AUTODetect=Yes -

DESTType=DRive -

LIBRary= T3V5LI -

DEVIce=/dev/rmt13 -

ONLine=YesDEFine PATH JOSIE_STA JOSIE_DR3 -

SRCType=SERVer -

AUTODetect=Yes -

DESTType=DRive -

LIBRary= T3V5LI -

DEVIce=/dev/rmt14 -

ONLine=Yes


Verify the drives as shown below: x. Label library volumes in ANIMAL_LIB as shown using the macro below:/* label_libv.dsm */

/* Define Library Volume on the VTL library */

LABEl LIBVolume T1V1LA -

SEARCH=Yes LABELSource=Barcode -

CHECKIN=SCRatch OVERWRITE=YesThe Screen-shot is shown below:

This screen-shot shows the labeled library volumes below:

6. Configure the Storage Agent ANIMAL_STA on machine ANIMAL using the procedure below:i. Edit the file /usr/tivoli/tsm/client/ba/bin using vi editor as shown below:

ii. Add line SErvername kdctsm03, save the file and exit:

iii. Check for the existence of the file /opt/tivoli/tsm/client/ba/bin/dsm.sys:

iv. Using vi editor, edit dsm.sys file as shown in the screen-shot below:

v. Check for the existence of the file /usr/tivoli/tsm/StorageAgent/bin/dsmsta.opt:

vi. Using vi editor, edit dsmsta.opt file as shown in the screen-shot below:

vii. Create a Korn-shell script /usr/tivoli/tsm/StorageAgent/bin/def_stg_agent.ksh as shown below: #-----def_stg_agent.ksh-----#

#!/usr/bin/ksh

/opt/tivoli/tsm/StorageAgent/bin/dsmsta setstorageserver myname=josie_sta mypassword=josie123 myhladdress=josie servername=kdctsm03 serverpassword=capitalone hladdress=knotsm03 lladdress=1500#----EOF-----#

viii. Execute the script def_stg_agent.ksh as shown below in the screenshot:

ix. Verify that the files /usr/tivoli/tsm/StorageAgent/bin/dsmsta.opt and /usr/tivoli/tsm/StorageAgent/bin/devconfig.out are modified with the entry SERVERNAME KDCTSM03 as a result of running the def_stg_agent.ksh script above:

x. Run the following commands to start the storage-agent: export STGDIR=/usr/tivoli/tsm/StorageAgent/bin

cd $STGDIR

./dsmsta


xi. Validate if the node JOSIE_SYSTEM_BKUP is capable of LAN-Free data movement using storage agent JOSIE_STA by running the following macro on TSM server KDCTSM03:/* validate_lanfree.dsm */

VALidate LAnfree JOSIE_SYSTEM_BKUP JOSIE_STA


xii. Verify by issuing the command josie_sta:q session on TSM server KDCTSM03 to check if the Storage-Agent responds:The screen-shot below shows the output:

xiii. Now that the Storage-Agent has been verified to be starting normally, halt it and start it through a script. This script will also facilitate automatic startup at system bootup:

xiv. Create Korn-shell script /usr/tivoli/tsm/StorageAgent/bin/rc.tsmstgagnt as below:#----------rc.tsmstgagnt-------------#

#!/bin/ksh

#

# Start up TSM storage agent when the system is rebooted ....

#---------------------------- CHANGE HISTORY -----------------------------------

# 01/17/2001 rmf: New for Version 4.2

# 04/11/2001 rmf:No_MNRATIO:export AIXTHREAD* not required.

# Need link to tsm421s.nas and tsm510s.srvfree

# 11/19/2001 rmf:IC32072: path to storage agent is incorrect

################################################################################

# Get the language correct....

export LANG=en_US

# max out size of data area

ulimit -d unlimited

export STGDIR="/usr/tivoli/tsm/StorageAgent/bin"

#OK, now fire-up the storage agent in quiet mode.

print "$(date '+%D %T') Starting Tivoli Storage Manager storage agent"

cd /usr/tivoli/tsm/StorageAgent/bin

dsmsta quiet

xv. Ensure that the following line is present in /etc/inittab for automatic startup at reboot:

autostgagnt:2:once:/usr/tivoli/tsm/StorageAgent/bin/rc.tsmstgagnt >/dev/console

2>&1 #Start the Tivoli Storage Manager storage agent

This screenshot shows how nohup is used to startup the Storage-Agent: nohup /usr/tivoli/tsm/StorageAgent/bin/rc.tsmstgagnt &

This completes the configuration of Storage-Agent on the machine.

Uninstall

1. Uninstall the filesets by issuing the command:

installp -u f 'Atape.driver tivoli.tsm.StorageAgent.rte'

2. Verify that the software is removed/uninstalled: lslpp -aL Atape.driver tivoli.tsm.StorageAgent.rte

3. Reboot the system:

shutdown FrThis completes the Uninstall section and also completes this document.

_964290498.unknown

tsm sa aix installation

Documents