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
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
Come verificare quale nic sta utilizzando la mia VM
Da command-line (ESX o ESXi) lancaire esxtop e poi premendo N si visualizza il dettaglio del traffico di rete da cui poi si vede l’asssociazione delle VM->VMNIC
Maxuproc
How to verify max user proc over AIX?
root@xxxxxx:/# lsattr -El sys0 -a maxuproc
maxuproc 128 Maximum number of PROCESSES allowed per user True
How to change?
root@xxxxxx:/# chdev -l sys0 -a maxuproc=256
sys0 changed
root@xxxxxx:/# lsattr -El sys0 -a maxuproc
maxuproc 256 Maximum number of PROCESSES allowed per user True
Teamviewer and cloned virtual machine
When you have cloned a virtual machine whit running teamviewer the new machine have the same id of source VM.
For change the id in the new machine, stop the service and :
Remove ClientIC and ClientID.
64 bit
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeTeamViewerVersionX
32 bit
HKEY_LOCAL_MACHINESOFTWARETeamViewerVersionX
Disable fsck at boot
For disable fsck at boot of OS need change last number of fstab line for my filesystem :
/dev/VolGroup/LogVol /mountpoint ext4 defaults 1 0 <-- fsck is disable detail Configure MDS9000 configuration backup
Step 1 – Enable scheduler
MDS-TAPE-3S-01# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
MDS-TAPE-3S-01(config)# scheduler enable
Step 2 – Create job
MDS-TAPE-3S-01(config)#
MDS-TAPE-3S-01(config)#
MDS-TAPE-3S-01(config)# scheduler job name backup_config
MDS-TAPE-3S-01(config-job)# copy running-config startup-config
MDS-TAPE-3S-01(config-job)# copy startup-config tftp://xxx.xxx.xxx.xxx/MDS-TAPE-3S-01_$(TIMESTAMP)
MDS-TAPE-3S-01(config-job)#
MDS-TAPE-3S-01#
Step 3 – Create scheduler and connect job
MDS-TAPE-3S-01# conf t
Enter configuration commands, one per line. End with CNTL/Z.
MDS-TAPE-3S-01(config)# scheduler schedule name serale_22
MDS-TAPE-3S-01(config-schedule)# job name backup_config
MDS-TAPE-3S-01(config-schedule)# time daily 22:35
MDS-TAPE-3S-01(config-schedule)#
Step 4 – Verify configuration scheduler
DS-TAPE-3S-01# show scheduler schedule
Schedule Name : serale_22
——————————-
User Name : admin
Schedule Type : Run every day at 22 Hrs 35 Mins
Last Execution Time : Yet to be executed
———————————————–
Job Name Last Execution Status
———————————————–
backup_config -NA-
=======================================
It is possible schedule job weekley :
MDS-TAPE-3S-01(config-schedule)# time weekly Sun:23:30
For change job is not possible modify actual job but need delete and recreate