UNSOLVED

OnlySandy

updated

16 years ago

O

OnlySandy

63 Posts

0

2210

January 15th, 2011 02:00

createpair error

Hi , I am facing this issue from last many days. When i do "createpair -invalidate R2" from source DMX i get below error

"A configuration mismatch was detected between your local and remote device(s) "

I checked symapi logs . If shows below line

" 01/15/2011 13:51:31.007   6709      1 EMC:SYMRDF                expand_remote_device Remote device: 07F0 (SID: XXXX) and Local device: 14C1 (SID: XXXX) do not match. "

It means i need expand the destination meta. BUT its not the case both are of same size , same number of hypers within them

I checked lots of things but found nothing wrong about size or configuration of destination meta.

Then i thought something weired and Mapped the destination devices and after mapping write_disabled them. (its not possible to write_disable device without mapping). And i used same create pair command IT WORKED WELL

I thought its one time issue but i am facing this issue everytime when i do createpair . I generally create metas on both sides and then do createpair before mapping R1 or R2 to FA's because it saves my write_disable work and also avoid me from accidental write_disable of any PROD LUN

I know , that the device should be in write_disable state only if they are MAPPED .

But here i am running create pair immediately creating meta on both sides but it still forcing me to map them and write_disable metas

Is there anything specified in any file which forcing me to follow this ???

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    927

    0

    Posted January 15th, 2011 05:00

    what code on the array, what version of solutions enabler ..have you tried running "symcfg discover" before you attempt createpair.

  • OnlySandy

    63 Posts

    927

    0

    Posted January 16th, 2011 20:00

    Hello Dynamox , the SE version on both box is 6.5.3 and code on both arrays is 5773.

    symcfg discover sounds more logical to me I will definately try this next time.

    Do you see any other culprit ?? also i checked option file . Its not having anything enabled.

  • 927

    1

    Posted January 16th, 2011 22:00

    I think this is a known problem with older version of SE. Run Symcfg discover and that should fix the issue.

    Regards,

    Saurabh Rohilla

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    927

    0

    Posted January 17th, 2011 06:00

    upgrade SE, run symcfg discover and try again ..