###CREARE UN FILE ISO.REPO

vi /etc/yum.repos.d/iso.repo

#####CHE COSA INSERIRE

[base]
name=CDROM
baseurl=file:///mnt/cdrom/Server
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

[root@lxxxxx ~]# mpstat -P ALL
Linux 2.6.18-308.el5 (xxxxx)   08/03/2012

11:35:50 AM  CPU   %user   %nice    %sys %iowait    %irq   %soft  %steal   %idle    intr/s
11:35:50 AM  all    0.52    0.02    1.28    4.96    0.02    0.02    0.00   93.18   1023.44
11:35:50 AM    0    0.66    0.03    1.55    8.61    0.04    0.03    0.00   89.08   1023.43
11:35:50 AM    1    0.37    0.01    1.01    1.32    0.00    0.00    0.00   97.28      0.00

Aggiungere uan stringa alla fine di ogni riga di un file utilzzando awk :

awk ‘ { print $0″Testo da aggiungere” } ‘ myfile >> newfile

For insert start schedule :

 mkitab "tsm::once:/usr/bin/dsmc sched > /dev/null 2>&1 #TSM"

for manual background start  

nohup dsmc schedule 2> /dev/null &

okkio dmserror.log permission !!! 

For view old device after P2V windows server :

From command line   set devmgr_show_nonpresent_devices=1

Start device manager and select View –> Show Hidden Device

Delete old device

when i try to map  share SAMBA from windows7 or windows 2008

C:Usersxxxx>net use \10.1.1.209scambio /user:dominio username password
Errore di sistema 86.

Password di rete specificata non corretta.

For resolve the problem i need change a security policy :
Start  from command line –> secpol.msc

select Sicurezza di rete: livello di autenticazione Lan Manager
and change  from :

to:

now i try to connect samba share:
C:Usersxxxx>net use \10.1.1.209scambio /user:dominiousername password
Esecuzione comando riuscita.

du -xk . | sort -nr | head -20

A seguito di un blackout l’infrastruttura di backup di un cliente (composta da tsm 6.2 e libreria ts3310 con tre drive via FC) ha incominciato da dare degli errori (considerate che tutti e 3 i componenti HW si sono riavviati Server linux, libreria e switch in fibra) :

ANR8413E UNABLE OPEN DRIVE /dev/IBMtape2 error number 12

Dopo essermi salvato la configurazione dei drive  in un file di testo:

tsm: OMER>query path f=d

                   Source Name: OMER
                   Source Type: SERVER
              Destination Name: TS3310_MO
              Destination Type: LIBRARY
                       Library:
                     Node Name:
                        Device: /dev/IBMchanger0
              External Manager:
                           LUN:
                     Initiator: 0
                     Directory:
                       On-Line: Yes
Last Update by (administrator): ADMIN
         Last Update Date/Time: 03/16/2011 13:24:18

                   Source Name: OMER
                   Source Type: SERVER
              Destination Name: DRIVE0
              Destination Type: DRIVE
                       Library: TS3310_MO
                     Node Name:
                        Device: /dev/IBMtape2
              External Manager:
                           LUN:
                     Initiator: 0
                     Directory:
                       On-Line: Yes
Last Update by (administrator): SERVER_CONSOLE
         Last Update Date/Time: 06/22/2012 18:38:58

                   Source Name: OMER
                   Source Type: SERVER
              Destination Name: DRIVE1
              Destination Type: DRIVE
                       Library: TS3310_MO
                     Node Name:
                        Device: /dev/IBMtape1
              External Manager:
                           LUN:
                     Initiator: 0
                     Directory:
                       On-Line: Yes
Last Update by (administrator): SERVER_CONSOLE
                Source Name: OMER
                   Source Type: SERVER
              Destination Name: DRIVE2
              Destination Type: DRIVE
                       Library: TS3310_MO
                     Node Name:
                        Device: /dev/IBMtape0
              External Manager:
                           LUN:
                     Initiator: 0
                     Directory:
                       On-Line: Yes
Last Update by (administrator): SERVER_CONSOLE
         Last Update Date/Time: 06/22/2012 16:48:22

Ho ridefinito i due path che in questo caso mi davano errori i path erano del DRIVE0 e DRIVE2:

mi ero accorto che erano questi i drive perche facendo un update con le correnti configurazioni mi compariva un messaggio di errore:

tsm: OMER>update path OMER DRIVE2 srctype=SERVER autodetect=yes desttype=drive library=TS3310_MO device=/dev/IBMtape0
ANR8419E UPDATE PATH: The drive or element conflicts with an existing drive in library TS3310_MO.
ANS8001I Return code 15.

Adesso sembra andare tutto….

Link comodo per associare build a versione di ESX, Vcenter etc…

VMware KB:Pubblica post Correlating vCenter Server and ESX host build numbers to update levels

I was contacted by IBM support, the various steps required me to reset the disk, in one of these instead of remove and replace the disk I have replaced the failed drive with the new one, so I have to redo the reset recovering the dead. Now it’s all right, resetting the disk failure, the problem was solved.