Dopo aver aggiornato TSM dalla 6.2.2 alla 6.3  ho preparato il TSM server per effettuare l’automatic deploy degli agent via Administration Center , ho utilizzato come documentazione l’infocenter dell’IBM.

Per prima cosa creo due filesystem sul server (nel mio caso linux redhat) dove uno mi servira’ per appoggiare i pacchetti di aggiornamento (.exp) nel caso voglia fare io il download dal sito IBM (l’automatic deploy permette anche di delegare a lui il downlaod e l’import sul TSM), mentre l’altro file system mi servira’ per definirci la device class per dove il tsm si archiviera’ gli agent.

# Creo la devclass  associata al file system dove verra’ messo il pacchetto da importare
define devclass ibm_client_deploy_import devtype=file directory=/import_agent

# definisco il storage pool dove verra’ messo il pacchetto (agent e’ una device class definita gia’ prima)

tsm: SERVER1>q devclass agent f=d
             Device Class Name: AGENT
        Device Access Strategy: Sequential
            Storage Pool Count: 1
                   Device Type: FILE
                        Format: DRIVE
         Est/Max Capacity (MB): 1,500.0
                   Mount Limit: 20
              Mount Wait (min):
         Mount Retention (min):
                  Label Prefix:
                       Library:
                     Directory: /clientdeploy
                   Server Name:
                  Retry Period:
                Retry Interval:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
              Drive Encryption:
               Scaled Capacity:
       Primary Allocation (MB):
     Secondary Allocation (MB):
                   Compression:
                     Retention:
                    Protection:
               Expiration Date:
                          Unit:
      Logical Block Protection:
Last Update by (administrator): ADMIN
         Last Update Date/Time: 10/02/2012 17:23:53

# definisco lo storage pool
define stgpool AgentPool agent maxscratch=20

# definisco  domain policyset etc…
define domain ibm_client_deploy
define policyset ibm_client_deploy ibm_client_deploy
define mgmtclass ibm_client_deploy ibm_client_deploy ibm_client_deploy
define copygroup ibm_client_deploy ibm_client_deploy ibm_client_deploy
standard type=archive destination=AgentPool retver=nolimit
assign defmgmtclass ibm_client_deploy ibm_client_deploy ibm_client_deploy
activate policyset ibm_client_deploy ibm_client_deploy

#definisco il mio server
set serverhladdress=server.serveraddress.com

Alcune note sui parametri utilizzati:

•ibm_client_deploy_import is the temporary location from where the deployment packages are imported. This parameter is defined by the deployment manager.
•import_directory is a previously defined directory that is accessible from the server.
•stgpool_name is the name of a storage pool of your choosing where the deployment packages are stored on the server. The storage pool name is based on a previously defined device class. That device class is different from the one which is used to perform IMPORT operations.
•storage_dc_name represents the device class where the deployment packages are stored on the server.
•retention_value (RETVER) of the DEFINE COPYGROUP command sets the retention time for the package. You can set it to NOLimit or to a number of days. If you specify a number, you must take into account the number of days that the package was on the FTP site. The days spent on the FTP site are included in the number.
 The default for the Administration Center is five years.
•server.serveraddress.com is the server IP address or host name from which you scheduled the client automatic deployment.

Prossimamente spieghero’ come importare in automatico i pacchetti e fare il vero e proprio upgrade degli agent