After the Snapmirror Create , the above command completed ,
snapmirror initialize -destination-path svm1_dr:/cg/cg1_dr
After the Initialize command completes
At the Primary Cluster for snapmirror list-destination
At Secondary Cluster snapmirror show command should have similar outptu stating that the snapmirrror relationship is in InSync state
====
When the sm-bc is in healthy state (InSync State)
Below are the Primary and Secondarys LUNs from the SM-BC Relationship and the lun uuid and lun serial number will be replicated and will be the same on the primary and secondary. (for lun show -instance command output)
==========
Vserver Name: c1_vs1
LUN Path: /vol/c1_vol1/lu1
Serial Number: wtJh6?VjHVhe
LUN UUID: e04c0011-f2c7-41e4-b70b-270fd5eab797 <<< Unique
Mapped: mapped
Vdisk ID: 8071588b0000000000000000000000650cd5fd97 <<< Not Unique
ZRTO Status: primary-in-sync <<< this is the primary LUN.
Local Target Uses Offset RTPIDs: false
ZRTO Volume consensus: true
SMBC Is Source: true << since primary it is called as smbc source
SMBC Policy Type: automated-failover
====
lun show -path /vol/c2_vol1/lu1 -instance
Vserver Name: c2_vs1
LUN Path: /vol/c2_vol1/lu1
Serial Number: wtJh6?VjHVhe
LUN UUID: e04c0011-f2c7-41e4-b70b-270fd5eab797 <<< this is Unique.
Vdisk ID: 80130e2c0000000000000000000000650cd5fd97 <<< this will be unique
ZRTO Status: secondary-in-sync <<< LUN in the Secondary
Local Target Uses Offset RTPIDs: true
ZRTO Volume consensus: false
SMBC Is Source: false <<< this is secondary hence it is called false.
SMBC Policy Type: automated-failover
====
Refer to this document for more details https://www.netapp.com/media/21888-tr-4878.pdf