User Tools

Site Tools


tsm:tsm_deployement_client

Use IBM Storage Protect update client deployment

Configure Storage Protect deploy client updates

On server prepare infrastructure to update clients

define devclass IBM_DEPLOY_CLIENT_IMPORT devtype=file directory=<import_directory>
define stgpool IBM_DEPLOY_CLIENT_POOL IBM_DEPLOY_CLIENT_IMPORT maxscr=20

define domain IBM_DEPLOY_CLIENT
define policyset IBM_DEPLOY_CLIENT IBM_DEPLOY_CLIENT
define mgmtclass IBM_DEPLOY_CLIENT IBM_DEPLOY_CLIENT IBM_DEPLOY_CLIENT 
define copygroup IBM_DEPLOY_CLIENT IBM_DEPLOY_CLIENT IBM_DEPLOY_CLIENT standard type=archive destination=IBM_DEPLOY_CLIENT_POOL retver=365
assign defmgmtclass IBM_DEPLOY_CLIENT IBM_DEPLOY_CLIENT IBM_DEPLOY_CLIENT
activate policyset IBM_DEPLOY_CLIENT IBM_DEPLOY_CLIENT 
set serverhladdress <server.serveraddress.com>
set serverlladdress <tcp_port>

reg node IBM_DEPLOY_CLIENT_WIN IBM_DEPLOY_CLIENT_WIN dom=IBM_DEPLOY_CLIENT
reg node IBM_DEPLOY_CLIENT_UNX IBM_DEPLOY_CLIENT_UNX dom=IBM_DEPLOY_CLIENT

TSM deploy client updates

On windows server Add the following option to dsm.opt file:

AUTODEPLOY noreboot

Add new client update into TSM

First download latest .exp files for each clients in use, and the deployment package Ex for linux x86

https://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v8r1/Linux/autodeploy/v818/8.1.8.0-TIV-TSMBAC-LinuxX86.exp

And also the deployment package

https://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/client/updatemgr/Updatemanager-LinuxX86.exp
  

Put the file on TSMSRV1 into a folder

Ex: /tsm/tsminst2/STGP/updates

Import the client update into the management class ibm_deploy_client_import

Protect: TSMSRV1 > IMPORT NODE * filedata=archive mergefilespace=yes devclass=ibm_deploy_client_import volumenames=/tsm/tsminst2/STGP/updates/8.1.8.0-TIV-TSMBAC-LinuxX86.exp 
Protect: TSMSRV1 > IMPORT NODE * filedata=archive mergefilespace=yes devclass=ibm_deploy_client_import volumenames=/tsm/tsminst2/STGP/updates/Updatemanager-LinuxX86.exp

Verify that the packages are in a location that the server can access. Issue the following command:

Protect: TSMSRV1 > select * from archives where node_name like 'IBM_DEPLOY_CLIENT%'
     NODE_NAME: IBM_DEPLOY_CLIENT_UNX
FILESPACE_NAME: /
  FILESPACE_ID: 1
          TYPE: FILE
       HL_NAME: /deploy/client/Linux/X86/v818/v8.1.8.0/
       LL_NAME: TIVsm-BA.x86_64.rpm
     OBJECT_ID: 1804106505
  ARCHIVE_DATE: 2019-05-24 15:29:12.000000
         OWNER: root
   DESCRIPTION: DEPLOY_8180_Linux_X86
    CLASS_NAME: DEFAULT
   ACTUAL_SIZE:

     NODE_NAME: IBM_DEPLOY_CLIENT_WIN
FILESPACE_NAME: \\ibm_anr_win\c$
  FILESPACE_ID: 1
          TYPE: FILE
       HL_NAME: \DEPLOY\CLIENT\WINDOWS\X64\V818\V8.1.8.0\
       LL_NAME: 8.1.8.0-TIV-TSMBAC-WINX64.EXE
     OBJECT_ID: 1804106496
  ARCHIVE_DATE: 2019-06-11 10:10:20.000000
         OWNER:
   DESCRIPTION: DEPLOY_8180_Windows_X64
    CLASS_NAME: DEFAULT
   ACTUAL_SIZE:
...
Protect: TSMSRV1 >select HL_NAME,LL_NAME from archives where node_name like 'IBM_DEPLOY_CLIENT_UNX'and LL_NAME='deployclient.sh'

HL_NAME: /deploymngr/client/AIX/PPC/deploy/
LL_NAME: deployclient.sh

HL_NAME: /deploymngr/client/Linux/X86/deploy/
LL_NAME: deployclient.sh

Protect: TSMSRV1 >select HL_NAME,LL_NAME from archives where node_name like 'IBM_DEPLOY_CLIENT_%'and LL_NAME='DEPLOYCLIENT.BAT'

HL_NAME: \DEPLOYMNGR\CLIENT\WINDOWS\X64\DEPLOY\
LL_NAME: DEPLOYCLIENT.BAT

Client default location for logs

Client PlatformDirectory
AIX/usr/tivoli/tsm/client/IBM_ANR_UNX/PPC/deploy/log
Linux x86_64/opt/tivoli/tsm/client/IBM_ANR_UNX/X86/deploy/log
Linux ppcle/opt/tivoli/tsm/client/IBM_ANR_UNX/PPCLE/deploy/log
Solaris sparc/opt/tivoli/tsm/client/IBM_ANR_UNX/SPARC/deploy/log
Windows 64bitC:\Program Files\Tivoli\TSM\IBM_ANR_WIN\X64\deploy\log

If internet connection is available on Operation Center

Then you can automatically download packages, and update the clients from Updates tab

If no internet connection is available on Operation Center for deploying, then download the catalog file from

https://public.dhe.ibm.com/storage/tivoli-storage-management/catalog/client/catalog.json

You can check int the catalog file

Put this catalog into : <instance_dir>/deployconfig

And change the settings into TSM server:

Protect: TSMSRV1 > q sys
ClientDeployCatalogURL     https://public.dhe.ibm.com/storage/tivoli-storage-management/catalog/client/catalog.json
ClientDeployUseLocalCatalog                       No

Protect: TSMSRV1 >setopt CLIENTDEPLOYUSELOCALCATALOG yes
Protect: TSMSRV1 >setopt CLIENTDEPLOYCATALOGURL /tsm/tsminst2/deployconfig/catalog.json

Manual schedule clients update:

For Windows:

Protect: TSMSRV1 >  define schedule domain_name schedule_name action=deploy objects="deployment_package_location destination_for_package" options="-fromnode=IBM_CLIENT_DEPLOY_WIN -postnschedulecmd='relative_path\deployclient.bat schedule=schedule_name autodeploy=noreboot nodeinfo=TBD' -subdir=yes -replace=all" startdate=4/20/2013 perunits=onetime
  deployment_package_location is the path to the deployment package
  destination_for_package is the path to where you want to store the deployment package
  IBM_CLIENT_DEPLOY_WIN is the predefined name (for a Windows deployment) for the -fromnode option
  AUTODEPLOY can be YES, NO, or NOREBOOT. The default is YES.
  nodeinfo=TBD must be entered exactly as shown.

For AIX:

Protect: TSMSRV1 > define schedule UNIX deploy_aix_update action=deploy objects="/deploymngr/client/AIX/PPC/deploy/* /usr/tivoli/tsm/IBM_ANR_UNX/" options="-fromnode=IBM_CLIENT_DEPLOY_UNX -postnschedulecmd='/usr/tivoli/tsm/IBM_ANR_UNX/v818/deployclient.sh>/usr/tivoli/tsm/IBM_ANR_UNX/deploy/ui#de=DEPLOY_8180_AIX_PPC#schedule=schedule_name#domain=domain_name#nodeinfo2=TBD'-subdir=yes -replace=all" duration=1 durunits=hours perunits=onetime startdate=today starttime=now

Protect: TSMSRV1 > def assoc UNIX deploy_aix_update AIXSRV1
  deployment_package_location is the path to the deployment package
  destination_for_package is the path to where you want to store the deployment package
  IBM_CLIENT_DEPLOY_UNX is the predefined name (for a UNIX deployment) for the -fromnode option
  nodeinfo2=TBD must be entered exactly as shown.
  

Remove Storage Protect deploy client updates

To complete remove Client updates, remove the domain if no nodes are assigned, and remove the device class

Protect: ISPPROD1>q dom

Policy        Activate-     Activate-     Number of      Description
Domain        d Policy      d Defaul-     Registere-
Name          Set           t Mgmt           d Nodes
                            Class
---------     ---------     ---------     ----------     ------------------------
IBM_DEPL-     IBM_DEPL-     IBM_DEPL-              0
 OY_CLIE-      OY_CLIE-      OY_CLIE-
 NT            NT            NT

Protect: ISPPROD1>del dom IBM_DEPLOY_CLIENT

Do you wish to proceed? (Yes (Y)/No (N)) y
ANR1501I Policy domain IBM_DEPLOY_CLIENT deleted.
tsm/tsm_deployement_client.txt · Last modified: 2024/01/05 09:12 by manu