Dell Unity: Status for synkroniseringsreplikering Mistet synkroniseringskommunikation (0x840e)

FC-zoneændring blev udført for at løse krydsede FC-forbindelser fra SRC SP'er til DR SP'er.

• Der blev oprettet en synkroniseringsreplikeringssession, men synkroniseringen afbrydes med det samme.
• Problemet kunne ses på SPA eller SPB eller begge SP'er.
• Når der kun ses et problem på en SP, kan sessionen flyttes til den anden SP, og det fungerer fint.

• Efter gennemgang af FC-forbindelser blev det konstateret, at forbindelserne blev krydset, og ændring af FC-forbindelse og zoneinddeling blev gjort om for at tillade korrekt SPA <=> SPA, SPB <=> SPB-forbindelser.
• Selv efter at FC-forbindelserne blev rettet, rapporterer synkroniseringsreplikeringssessionen stadig tabt synkroniseringskommunikation uden at genstarte SP'er på både SRC og DR. Men sammenkoblingen viser ok.

Med synkroniseringsreplikering, hvor FC-forbindelser og zoneinddeling blev udført, skal du sørge for at genstarte begge SP er på SRC og DR.

Til din reference er de foreslåede ændringer som følger - følgende opdateres i den fremtidige dokumentation til "Konfiguration af replikering":

Konfiguration
af zoneinddeling Sørg for, at du udfører følgende:

• Konfigurer porten som en F-port for at undgå potentielle problemer, og fjern andre typer porte fra listen over tilladte porttyper.
• For en synkron replikeringsforbindelse skal du slutte SPA-porten på kildesystemet til SPA-porten på destinationssystemet. På samme måde er kildesystemets SPB-port til destinationssystemets SPB-port

F.eks.

• OB_H1450 SPA-port 4 <--> OB_H1443 SPA-port 4
• OB_H1450 SPB-port 4 <--> OB_H1443 SPB-port 4

Nu er konfigurationen rettet:

• OB_H1450 SPA-port 4 <--> OB_H1443 SPA-port 4
• OB_H1450 SPB-port 4 <--> OB_H1443 SPB-port 4

Sørg for at genstarte både SP for både kildesystemet og destinationssystemet.

SPA- og SPB-portene på samme side (kilde eller destination) skal have den samme portkonfiguration. Konfigurationen af porte på kildesystemet kan dog være forskellig fra portkonfigurationen på destinationssystemet. F.eks. understøttes SPA-port 4 <--> SPA I/O-modul 0-port 0 og SPB-port 4 <--> SPB I/O-modul 0-port 0.

Eksempel: Følgende problem blev kun set på en NAS-serversynreplikering på SPB, hvor FC-forbindelsestopologien er SRC FC-switch <> , Core FC-switch <> , DR FC-switch.

SRC: APMxxx1
DR: APMxxx0

2: ID = RS_5
Name = unitySync
Address = x.b.8.115
Alternate Management Address = x.b.8.115
Model = Unity 400
Serial number = APMxxx0
Connection type = sync
Source interfaces = x.a.0.80, x.a.0.81
Local interfaces = x.a.0.80, x.a.0.81
Remote interfaces = x.b.8.130, x.b.8.131
Operational status = OK (0x2)
Health state = OK (5)
Health details = "Communication with the replication host is established. No action is required."
Synchronous FC ports = spa_fc4, spb_fc4


| nasServer | x.x.x.2 x.x.x.2 | Not Configured | B | bond10 bond10 | 0x180000001B | 27 | 25 | TRUE | NFS |


Name = rep_sess_nas_25_nas_34_APMxxx1_APMxxx0
Session type = nas server
Synchronization type = sync
RPO = N/A
Resource type = NAS Server
Sync State = out of sync
Health state = Minor failure (15)
Health details = "The connection with this remote replication host has been lost. On the Replication Connections page, click the Verify and Update Connection button.
Operational status = Lost Sync Communication (0x840e)
Source status = OK
Destination status = OK
Network status = Lost Sync communication
Destination type = remote
Destination system = RS_5
Local role = Source
Source resource = nas_25
Source SP-A interface = x.a.0.80
Source SP-B interface = x.a.0.81
Destination resource = nas_34
Destination SP-A interface = x.b.8.130
Destination SP-B interface = x.b.8.131
Time of last sync = N/A
Sync status =
Sync transfer rate = N/A
Sync transfer size remaining = N/A
Previous transfer rate = N/A
Average transfer rate = N/A
Element pairs = N/A
Hourly Snapshot Retention =
Daily Snapshot Retention =
Hourly snapshot keep for =
Hourly snapshot allow auto-delete =
Daily snapshot keep for =
Daily snapshot allow auto-delete =

EMCSystemLogFile.log:

"2019-02-06T05:43:40.593Z" "Unity_spb" "Kittyhawk_safe" "17322" "unix/spb/root" "INFO" "1:1050207" :: "The minimum requirements for an active mirror have been met. Placing mirror 50060160c7e05f0d:3a000000000000xx in the active state automatically." :: Category=System Component=rmd
"2019-02-06T05:43:40.605Z" "Unity_spb" "Kittyhawk_safe" "17322" "unix/spb/root" "INFO" "1:1050210" :: "Full synchronization has started on image 50060160c7e068xx of the synchronous mirror with ID 50060160c7e05f0d:3a000000000000xx." :: Category=System Component=rmd
"2019-02-06T05:43:40.622Z" "Unity_spb" "Kittyhawk_safe" "17322" "unix/spb/root" "INFO" "1:1050401" :: "K10 50060160c7e068xx became unreachable." :: Category=System Component=rmd
"2019-02-06T05:43:40.633Z" "Unity_spb" "Kittyhawk_safe" "17322" "unix/spb/root" "INFO" "1:1050208" :: "The minimum requirements for an active mirror have not been met. Placing mirror 50060160c7e05f0d:3a00000000000xxx in the attention state automatically." :: Category=System Component=rmd
"2019-02-06T05:43:40.642Z" "Unity_spb" "Kittyhawk_safe" "17322" "unix/spb/root" "INFO" "1:105020c" :: "Image 50060160c7e068xx of the synchronous mirror with ID 50060160c7e05f0d:3a000000000000xx has been system fractured." :: Category=System Component=rmd
"2019-02-06T05:43:42.361Z" "Unity_spb" "Neo_CEM" "28673" "N/A" "ERROR" "14:6077e" :: "Replication session rep_sess_nas_36_nas_40_APMxxx1_APMxxx0 lost sync communication with its remote session" :: Category=User Component=Health

c4_safe_ktrace.log:

2019/02/06-05:43:23.361373 15K 7F239F8DC7xx std:RMD: Failed CMI transmission. CMI Ack Received Status = 0x7e11f061, mirror 103079215142_APMxxx1_0000_103079215144_APM00
2019/02/06-05:43:23.361375 ~~~~ 7F239F8DC7xx std:RMD: mAbortSync() called 103079215142_APMxxx1_0000_103079215144_APMxxx0_0000[6852]
2019/02/06-05:43:23.361377 ~~~~ 7F239F8DC7xx std:RMD: AbortSync Overlap 0 mirror 103079215142_APMxxx1_0000_103079215144_APMxxx0_0000
2019/02/06-05:43:23.361377 ~~~~ 7F239F8DC7xx std:RMD: mAbortSyncOperation() 103079215142_APMxxx1_0000_103079215144_APMxxx0_0000 [6852] 0/0
2019/02/06-05:43:23.361427 44 7F238C79E7xx std:RMD: Sys. Fracturing an image in syncQueue !!
2019/02/06-05:43:23.361428 ~~~~ 7F239F8DC7xx std:RMD: Released Sync Resource 0x7f199d3194xx for SyncIo 0x7f1a95c79d70 in mirror 103079215142_APMxxx1_0000_103079215144_AP
2019/02/06-05:43:23.361429 ~~~~ 7F238C79E7xx std:RMD: configPerformFracture called from line [2674] for mirror 103079215142_APMxxx1_0000_103079215xxx_APMxxx0_0000
2019/02/06-05:43:23.361781 346 7F2395E7Bxx std:PSMSYS:PSMSYS:psmDataAreaCloseCommit(001:014) DEFERRED for DW...
2019/02/06-05:43:23.361870 83 7F2395E7B7xx std:PSMSYS:PSMSYS:psmDataAreaCloseCommit(001:014) DEFERRED for WIP...
2019/02/06-05:43:23.361871 ~~~~ 7F2395E7B7xx std:PSMSYS:PSMSYS:psmDataAreaClose(1:14): PENDED...
2019/02/06-05:43:23.365851 3974 7F238C79E7xx std:RMD: Mirror 103079215142_APMxxx1_0000_103079215144_APMxxx0_0000 - Fracturing an already fractured slave
2019/02/06-05:43:23.365902 46 7F238C79E7xx std:RMD:mirrorFractureSlave: Aborting any pending Syncs for mirror(103079215142_APMxxx1_0000_103079215144_APMxxx0_000
2019/02/06-05:43:23.365903 ~~~~ 7F238C79E7xx std:RMD: mAbortSync() called 103079215142_APMxxx1_0000_103079215144_APMxxx0_0000[5872]
2019/02/06-05:43:23.365905 ~~~~ 7F238C79E7xx std:RMD: Aborted Pending Sync IO in CMI for mirror 103079215142_APMxxx1_0000_103079215144_APMxxx0_0000
2019/02/06-05:43:23.365906 ~~~~ 7F238C79E7xx std:RMD: Mirror 103079215142_APMxxx1_0000_103079215144_APMxxx0_0000 Image #1 has been fractured; 786432 bits in FL