This post is more than 5 years old
70 Posts
0
3824
Problem unmapping devices from FA ports
I'm trying to unmap a device that I've moved to a new FA:port, but it is giving an error when I do the preview. It is complaining that the device must be write disabled or not ready, but it is already marked write disabled (it is the R2 in an SRDF pair). Has anyone seen this before?
The command file contains:
unmap dev 00D3 from dir 7b:0;
# symconfigure -f unmap.1 -sid 123 preview
Execute a symconfigure operation for symmetrix '000000000123' (y/ ) ? y
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Processing symmetrix 000000000123
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Definition 1 is in error:
Unmap change: Device must be write-disabled or not ready
Device 00D3 generated the failure
Terminating the configuration change session..............Done.
The configuration change session has failed.
svdnj005# symdev list -RANGE 00D3:00d3 -sid 804
Symmetrix ID: 000000000123
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Sym Physical SA : P DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------
00D3 Not Visible ***:* 02A:D2 RDF2+R-5 Grp'd WD 35001
Message was edited by: SymmetrixForumsModerator Changed Symmetrix ID.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
June 23rd, 2011 07:00
symld write_disable should work.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
1
June 22nd, 2011 14:00
it's write disable on the link ? ..look at symdev show output.
5449Pr4QlS12567
46 Posts
1
June 23rd, 2011 01:00
Can you post symdev show 00D3 -sid xxxx o/p?
You need to WD the device on all SA. Maybe we can figure out more if you can give symdev o/p
Trouphaz
70 Posts
0
June 23rd, 2011 07:00
Ah, ok. I see where I marked in red. I was focusing on one device for this post, but I'm moving an entire device group. Can I use "symld -sid 0123 -g GRP1 -SA ALL write_disable" or would I want to make them not_ready since these are R2's that are already write disabled?
# symdev show 00D3 -sid 123
Device Physical Name : Not Visible
Device Symmetrix Name : 00D3
Device Serial ID : N/A
Symmetrix ID : 000000000123
Device Group Name : GRP1
Device Logical Name : DEV081
Attached BCV Device : N/A
Attached VDEV TGT Device : N/A
Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5773
Device WWN : 00000000000000100000000000004433
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0001
Cache Partition Name : DEFAULT_PARTITION
Device Block Size : 512
Device Capacity
{
Cylinders : 37334
Tracks : 560010
512-byte Blocks : 71681280
MegaBytes : 35001
KiloBytes : 35840640
}
Device Configuration : RDF2+R-5 (Non-Exclusive Access)
Device is WORM Enabled : No
Device is WORM Protected : No
SCSI-3 Persistent Reserve: Disabled
Dynamic Spare Invoked : No
Dynamic RDF Capability : RDF1_OR_RDF2_Capable
STAR Mode : No
STAR Recovery Capability : None
STAR Recovery State : NA
Device Service State : Normal
Device Status : Write Disabled (WD)
Device SA Status : Ready (RW)
Front Director Paths (4):
{
----------------------------------------------------------------------
POWERPATH DIRECTOR PORT LUN
--------- ---------- ---- -------- ---------
PdevName Type Type Num Sts VBUS TID SYMM Host
----------------------------------------------------------------------
Not Visible N/A FA 07B:0 RW 000 00 001 N/A
Not Visible N/A FA 10B:0 RW 000 00 001 N/A
Not Visible N/A FA 07C:0 RW 000 00 001 N/A
Not Visible N/A FA 10C:0 RW 000 00 001 N/A
}
Mirror Set Type : [R1 Remote,RAID-5,RAID-5,N/A]
Mirror Set DA Status : [RW,RW,RW,N/A]
Mirror Set Inv. Tracks : [0,0,0,0]
Back End Disk Director Information
{
Hyper Type : R1 Remote
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
Hyper Type : RAID-5
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
Hyper Type : RAID-5
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
}
RAID-5 Device Information
{
Number of Tracks in a Stripe : 4
Overall Ready State of RAID-5 Device : Ready
Overall WriteProtect State of RAID-5 Device : Enabled
Member Number of the Failing Device : None
Member Number that Invoked the Spare : None
Disk Director (DA) that Owns the Spare : Inv
Copy Direction : N/A
RAID-5 Hyper Devices (3+1):
{
Device : 00D3
{
--------------------------------------------------------------
Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB)
--------------------------------------------------------------
02A:D2 231 3 11668 4 RW N/A 1 286102
16A:D2 227 3 11668 2 RW N/A 1 286102
01C:C2 20 3 11668 1 RW N/A 1 286102
15C:C2 20 3 11668 3 RW N/A 1 286102
}
}
}
Clone Device Information
{
Source (SRC) Device Symmetrix Name : 00D3
Source (SRC) Device Group Name : GRP1
Source (SRC) Composite Group Name : N/A
Target (TGT) Device Symmetrix Name : 016C
Target (TGT) Device Group Name : GRP1
Target (TGT) Composite Group Name : N/A
State of Session (SRC ====> TGT) : Copied
Percent Copied : 100%
Time of Last Clone Action : Thu Jun 23 03:15:37 2011
Clone State Flags : (Copy) (Diff)
Number of Prot. Tracks for SRC Device : 0
Number of Indir Tracks for TGT Device : 0
Number of Changed Tracks for SRC Device: 0
Number of Changed Tracks for TGT Device: 0
}
RDF Information
{
Device Symmetrix Name : 00D3
RDF Type : R2
RDF (RA) Group Number : 4 (03)
Remote Device Symmetrix Name : 0187
Remote Symmetrix ID : 000000000122
R2 Device Is Larger Than The R1 Device : False
RDF Pair Configuration : Normal
RDF STAR Mode : False
RDF Mode : Asynchronous
RDF Adaptive Copy : Disabled
RDF Adaptive Copy Write Pending State : N/A
RDF Adaptive Copy Skew (Tracks) : 65535
RDF Device Domino : Disabled
RDF Link Configuration : Fibre
RDF Link Domino : Disabled
Prevent Automatic RDF Link Recovery : Enabled
Prevent RAs Online Upon Power ON : Enabled
Device RDF Status : Ready (RW)
Device SA Status : Ready (RW)
Device RA Status : Write Disabled (WD)
Device Link Status : Ready (RW)
Device Suspend State : N/A
Device Consistency State : Disabled
RDF R2 Not Ready If Invalid : Disabled
Device RDF State : Write Disabled (WD)
Remote Device RDF State : Ready (RW)
RDF Pair State ( R1 <===> R2 ) : Consistent
Number of R1 Invalid Tracks : 0
Number of R2 Invalid Tracks : 0
RDFA Information:
{
Session Number : 3
Cycle Number : 28161
Number of Devices in the Session : 160
Session Status : Active
Session Consistency State : Disabled
Minimum Cycle Time : 00:00:30
Average Cycle Time : 00:00:30
Duration of Last cycle : 00:00:30
Session Priority : 33
Tracks not Committed to the R2 Side: 0
Time that R2 is behind R1 : 00:00:50
R2 Image Capture Time : Thu Jun 23 10:27:35 2011
R1 Side Percent Cache In Use : 0
R2 Side Percent Cache In Use : 0
Transmit Idle Time : 00:00:00
R1 Side DSE Used Tracks : 0
R2 Side DSE Used Tracks : 0
}
}
Message was edited by: SymmetrixForumsModerator Changed WWN and SSID.
Trouphaz
70 Posts
0
June 23rd, 2011 08:00
very nice. thanks for the help guys. i was able to unmap those devices. setting them back to rw_enable now.
Trouphaz
70 Posts
0
June 23rd, 2011 08:00
Oh, one quick question. Is there any way to list all write disabled devices on the array? I just wanted to make sure I didn't miss anything when setting them back to rw.
GEMC
36 Posts
0
June 23rd, 2011 10:00
Normal symdev list command won't show that?
symdev -sid 123 list | grep WD
Trouphaz
70 Posts
0
June 23rd, 2011 10:00
No. Apparently there are 2 ways to be write disabled. When I run that command, device 0044 shows up as write disabled, but when I run symdev show 0044 it shows this in there:
Device Status : Write Disabled (WD)
Device SA Status : Ready (RW)
So, for SRDF, it is write disabled since it is an R2 device, but on the SA it is still RW.
GEMC
36 Posts
0
June 23rd, 2011 11:00
Then how about this
symdev -sid 123 list -noport -R2 --> It should list the R2 (WD) devices which are not masked to any port.