Brief connectivity problem between group replication volumes and RPA
Summary: Brief connectivity problem between group replication volumes and RPA
Symptoms
From logger:/sr/138220/extracted.rp-unit-ltc.KBox1.2016.11.28.10.22.12/processes/InfoCollect/showDevs.sh
This shows __revision 00__:
0x7c0a8452d1db4f0b=>(NaaRawGuid=Vector(96,6,1,96,172,96,65,0,253,128,44,88,227,201,206,40), oldRawGuid=Option(Vector(96,6,1,96,172,96,65,0,253,128,44,88,227,201,206,40)), vendor=DGC,product=VRAID,model=Option(Unity 400F),capacity=Option(1288490188800), niceName=Option(apl-sub01-RP-6036-VM-LTC-400FA_S7B-R (279)),serialNumber=CKMxxxxxxxxxxx, bIsSymmTaggedDevice=NoOption,symmDevID=NoOption,numPaths=4,controllerIDs=Set(SP-A,SP-B), geometry=Option((bytesPerSector=512,numberOfHeads=1,sectorsPerTrack=160,numberOfCylinders=15728640)), revision=00,bIsFTSVolume=0,numSymmTargets=0,bIsUsable=1)
This log extract would appear (usually but not exclusively) in replication logs.
2016/11/28 09:41:44.788 - #2 - 7602/7485 - MultiPath: handleReservationConflict: cannot resolve reservation conflict m_volume = 0x7c0a8452d1db4f0b m_basePath = (0x500124820066815e,0x5006016747e00819,0x24,e_fiberChannel)
I/O error due to reservation conflict causes replication to stop.
Event from the logs:
Brief connectivity problem between group replication volumes and RPA Time: Mon Dec 5 15:00:38 2016 Time Zone: GMT Topic: RPA Scope: NORMAL Level: ERROR & CLEAR Event ID: 16061 Cluster: rp-unit-ltc Global links: None RPA access: RPAs: RPA: RPA 1 Groups whose replication volumes are affected: [XXX, XXX] Summary: Brief connectivity problem between group replication volumes and RPA Service Request info: N/A............................................
Impacted Configuration and Settings [Replication Mode,Splitter Type,Compression,CDP/CLR/Multi,FC/IP/iSCSI, Policies, and so on.]: Unity Midrange Storage Array, in situations such as adding and Rset and reservation conflicts occur.
Impact on RP: RP is unable to penetrate the reservation conflict.
Cause
RP code for penetrating the reservation conflict is calculated based on legacy VNX revision code.
The Unity array returns code 00 therefore RP considers this array not supporting reservation conflict penetration.
Resolution
Fixed at: target for 5.0.1 or 5.1
Workaround:
Change the tweak "t_RsrvUseClariionPenetrationKeyFromRevision =" from 26 to 0 on all RPAs that access the Unity array and reboot each one after changing the tweak.