====== IBM SVC Problems ======
===== SVC snap =====
SVC snap (dump level 4)
IBM_2145:SVC:superuser> svc_livedump
IBM_2145:SVC:superuser> svc_snap gui3
IBM_2145:SVC:superuser>sainfo lscmdstatus
last_command satask sesdump 78xxxxx -nohdr
last_command_status CMMVC8008E Cannot execute on this SAN Volume Controller node.
T3_status
T3_status_data
cpfiles_status Complete
cpfiles_status_data Copied 64 of 64
snap_status Complete
snap_filename /dumps/snap.78xxxxx.231118.124337.tgz
installcanistersoftware_status
supportupload_status
supportupload_status_data
supportupload_progress_percent 0
supportupload_throughput_KBps 0
supportupload_filename
downloadsoftware_status
downloadsoftware_status_data
downloadsoftware_progress_percent 0
downloadsoftware_throughput_KBps 0
downloadsoftware_size
===== SVC ports Gbic =====
To find the Gbic strengh use the command (only on SVC nodes):
IBM_2145:SVC:superuser>lsportstats -node svca02
From statistics file :
Nn_stats_78GXXXX_230202_150839
**Check if TX power (transmit µW) or RX power (receive µW) is low ?**
txpwr="520" rxpwr="631"
===== Data corruption (bad blocks) =====
IBM_Storwize:V7000:superuser>lsmdisk
id name status mode mdisk_grp_id mdisk_grp_name capacity ctrl_LUN_# controller_name UID tier ence_id site_name distributed dedupe
0 mdisk0 online array 0 Pool0 6.5TB tier_enterprise no no no
1 mdisk1 online array 0 Pool0 6.5TB tier_enterprise no no no
2 mdisk2 online array 0 Pool0 6.5TB tier_enterprise no no no
IBM_Storwize:V7000:superuser>dumpmdiskbadblocks 0
IBM_Storwize:V7000:superuser>dumpmdiskbadblocks 1
IBM_Storwize:V7000:superuser>dumpmdiskbadblocks 2
IBM_Storwize:V7000:superuser>dumpallmdiskbadblocks
In case of error:
IBM_Storwize:V7000:superuser>dumpmdiskbadblocks 3
The resulting output if the MDisk has bad blocks:
Cluster name: my_cluster
Timestamp of dump: Fri Oct 31 11:27:33 2009 UTC
Mdisk id: 3
Mdisk name: mdisk3
Number of bad blocks: 6
Start LBA: 0x1234123412341234
Length: 2
Event log sequence number: 1
Start LBA: 0x5678567812341234
Length: 4
Event log sequence number: 2
The resulting output if the MDisk has no bad blocks:
Cluster name: my_cluster
Timestamp of dump: Fri Oct 31 11:27:33 2009 UTC
Remediation:
svctask repairsevdiskcopy
===== PPRC (replication) =====
if not possible to stop the replication, do a
stoprcconsistgrp -access //constistgrp_name//
stoprcrelationship -access //constistgrp_name//
Then you 'll be able to map your replicas in read-write mode
The primary volume is accessible for read and write I/O, and the secondary volume is
accessible for read-only I/O. This state is also called “normal copy state” and indicates that
your relationship is both consistent and synchronized.
===== PPRC (replication) =====
v7000 or SVC volumes (vdisk) offline, with cache corrupt:
recovervdiskbysystem
Or by volume
recovervdisk vdisk45
===== Error on mdisk path degraded =====
If an mdisk has to many error, once solved, it leave in warning state, depite clearing logs, then you have to manage it again from cluster:
IBM_2145:svc-c1:admin>lsmdisk
id name status mode mdisk_grp_id mdisk_grp_name capacity ctrl_LUN_# controller_name
8 m_v7000_c1_900_01 degraded_ports managed 1 p_v7000_c1_900_01 4.9TB 00008 v7000-c1-sc1
IBM_2145:svc-c1:admin>includemdisk 8
IBM_2145:svc-c1:admin>detectmdisk
===== Error unable to create mirror vdisk =====
On SVC / storwize (V3700 V5000 V7000) there are reserved space used for bitmap, on each IOgroup. If no more memory free (lsiogrop ), you can extend this reserved space, it's used for flashcopy, remote mirroring, vdisk mirror and raid, in case of internal disks.
chiogrp -feature --+- flash --+-- -- -size -- memory_size --+-------+-' io_group_name
+- remote -+ '- -kb -'
+- mirror -+
'- raid ---'
IBM_4939:V7000:superuser>lsiogrp
id name node_count vdisk_count host_count
0 io_grp0 2 45 16
1 io_grp1 0 0 12
2 io_grp2 0 0 12
3 io_grp3 0 0 12
4 recovery_io_grp 0 0 0
IBM_4939:V7000:superuser>lsiogrp 0
id 0
name io_grp0
node_count 2
vdisk_count 45
host_count 16
flash_copy_total_memory 20.0MB
flash_copy_free_memory 20.0MB
remote_copy_total_memory 20.0MB
remote_copy_free_memory 20.0MB
mirroring_total_memory 20.0MB
mirroring_free_memory 20.0MB
raid_total_memory 40.0MB
raid_free_memory 37.2MB
maintenance no
compression_active yes
accessible_vdisk_count 45
compression_supported yes
===== Error unable to use external virtualization or replication =====
[[http://emmanuel.iffly.free.fr/doku.php?id=storage:svc_cmd#change_system_layer_for_replication_or_external_virtualization| Change system layer (for replication or external virtualization)]]