find big file AIX system

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

UPDATE PATH TIVOLI STORAGE MANAGER

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:

update path OMER DRIVE0 srctype=SERVER autodetect=yes desttype=drive library=TS3310_MO device=/dev/IBMtape0

update path OMER DRIVE2 srctype=SERVER autodetect=yes desttype=drive library=TS3310_MO device=/dev/IBMtape2

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 desttype=drive library=TS3310_MO device=/dev/IBMtape0
ANR8958E UPDATE PATH: Autodetect is OFF and the serial number reported by the drive did not match the serial number in the drive definition.
ANS8001I Return code 15.

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....

A che versione fa riferimento la BUILD di vmware (Vcenter, esx etc..)

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

Replace Drive storwize v7000 (2)

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.

Replace Drive storwize v7000 (1)

Today I needed to replace Hdisk V7000, I did everything step by step and now:

I called support and look forward

MERGE FAILURE ZONE SET tra 9124 e 9222i

2012 Apr 24 22:27:39 MPR-MO-01 %ZONE-2-ZS_MERGE_FAILED: %$VSAN 3%$ Zone merge failure, isolating interface fc1/2 reason: Member mismatch:[reason:0]

Compare quando abbiamo sostituito per la prima volta lo switch.

La differenza tra i due switch (9124 e 9222i) non e’ in una zona   ma nel membro delle zone e precisamente in come viene identificato lo switch 9124 sostituito che nella vsan 3 presente sul 9124 e’ indicato come sanswitch2 mentre sul 9222i e’ indicato ancora con il wwn di quello vecchio (20:00:00:0d:ec:56:a4:80) come puoi vedere da una delle zone sui il merge analisys da errore:

Zone Zone_SVC_EVA8100 will fail.
sanswitch2
sanswitch2 fc1/1
sanswitch2 fc1/2
sanswitch2 fc1/3
sanswitch2 fc1/5
sanswitch2 fc1/11
sanswitch2 fc1/12
sanswitch2 fc1/13
MPR-MO-01
Cisco 20:00:00:0d:ec:56:a4:80 fc1/1
Cisco 20:00:00:0d:ec:56:a4:80 fc1/2
Cisco 20:00:00:0d:ec:56:a4:80 fc1/3
Cisco 20:00:00:0d:ec:56:a4:80 fc1/5
Cisco 20:00:00:0d:ec:56:a4:80 fc1/11
Cisco 20:00:00:0d:ec:56:a4:80 fc1/12
Cisco 20:00:00:0d:ec:56:a4:80 fc1/13

Quindi la configurazione con i wwn corretti e’ quella sul 9124 … considera che i tre host di laboratori collegati sul 9222i non vedono lo storage attraverso il 9124 sostituito

Per risolvere ho utilizzato questo comando dal 9222i :

Il problema e’ stato risolto ho esguito il seguente comando dal 9222i su cui c’erano le zone della VSAN 3 non corrette:

zoneset import interface fc1/2 vsan 3

Restore file from mksysb

restore -xqdf mksysb-xxxxcp ./var/spool/cron/crontabs/sviluppo                                                                     

x ./var/spool/cron/crontabs/sviluppo

In questo modo mi viene creato nella directory dove c'e' l'mksysb un percorso :

/var/spool/cron/crontabs/ 

dove dentro c'e' il fiel sviluppo

View State port Host connect to SVC

From command line to view state port of host connect to SVC :

-- SSH connect to SVC  (need ssh key)

-- svcinfo lshost ( for view all host connect)
id name        port_count iogrp_count
0  xxxESX01  2          4
1  xxxESX02  2          4
2  xxxESX03  2          4
3  xxxESX04  2          4

.........

-- svcinfo lshost xxxESX01 (for view detail of host xxxESX01)


id 0
name xxxESX01
port_count 2
type generic
mask 1111
iogrp_count 4
WWPN 2100001B32873EED
node_logged_in_count 2
state active
WWPN 2100001B32875FA4
node_logged_in_count 2
state active

This case have all port active