Symmetrix open replicator hot pull issue

Rasal, do you currently have reservation on this device?  If not, you may want to look at opening a service request to have this checked out.  There may be error messages on either the Symmetrix or the CLARiiON that would help pinpoint the issue.

Rasal, I use ORS a lot and I have never seen this error. You do not mention if the pairing file has more than one device. Perhaps try creating a session on an other pair of devices if possible (you do not need to activate it) and see if you get the same error. That way you can troubleshoot if it is an array, fabric, or device issue.

Hi Mike,

I was searching for the same only. I dont see any SCSI reservation for the devices.

I started SANCOPY for the same connections came up well.

Yeah sure let me open up a case to investigate on this.

Thanks,

Rasal

I have 12 devices in the pairing file. I tried single device per pair file.

Results are same.

Thanks

Rasal

Rasal;  I have seen these types of errors many times, you need to ensure that you have the correct zoning in place and that you have granted access to the symmetrix FA's on the Clariion.

For Hot Pull, All DMX ports with access to control devices must have access to remote devices;

Therefore if your control device is mapped to FA 11a1 and 7a1 both directors 11a1 and 7a1 must be able to see the remote device.

Generally I will use symsan commands to verify the setup is correct before attempting a copy.

e.g.

Hi,

I dont have the version or microcode updated with me..

see the below error i get

root@pbtsmdby:/> symsan -sid 1335 list -dir 4a -p 1 -sanports

The requested feature is not supported for this microcode or SYMAPI version

root@pbtsmdby:/> symsan list -sanports -sid 1335 -dir 4a -p 1

The requested feature is not supported for this microcode or SYMAPI version

root@pbtsmdby:/> symmask -sid 1335 list logins |grep SP

500601643ce019b1 Fibre Clar4183_SPA4    Clar4183_SPA4    191bef Yes    Yes

5006016c3ce019b1 Fibre Clar4183_SPB4    Clar4183_SPB4    1a18ef Yes    Yes

root@pbtsmdby:/> symsan

More arguments are required.

root@pbtsmdby:/> symsan -sid 1335 list -sanluns -wnn 500601643ce019b1 -dir 4a>

root@pbtsmdby:/>  -wwn 500601643ce019b1 -dir 4a -p 1                         <

The requested feature is not supported for this microcode or SYMAPI version

root@pbtsmdby:/>

Rasal

Apologies, symsan is available from Solutions Enabler 6.4 and 5772 code, if you are not at these levels or above you won't have this functionality.

Still you really need to check Zoning, Make sure that the FA's have been granted access to the clariion.

If you are still having issues you will need to engage support.

Rasal, once you get the service request on, can you shoot me either an e-mail or private message with the service request number.  I would be interested in taking a look.

STARTING a RCOPY 'CREATE' operation.   (Ctl)Sym: 00019010xxxx Device: 00759 -   LUN WWN: 600601604F1022007B168E2DAE2ADE11 - [loc_dir:13B, rem_num:0, rem_st 0x1dUnknown error code]   (Ctl)Sym: 00019010xxxx Device: 00759 -   LUN WWN: 600601604F1022007B168E2DAE2ADE11 - [SYMAPI_C_RCOPY_DISCOVER_ERROR] The Rcopy 'CREATE' operation FAILED. (SYMAPI_C_RCOPY_DISCOVER_ERROR) An rcopy remote device discover error occurred

Rasal, you said your pulling data from the CX to the Symm so the Symm would be the one controlling.  It looks like Symm device 759 is mapped to FA13b which with the Symm doing the pull it would be your local.  If you look at what I highlighted in red, it looks like maybe an issue with the remote device?  Have you checked out the CLARiiON device to make sure that there are no issues with that?