Unsolved
This post is more than 5 years old
15 Posts
0
2408
Can only see 2 of our 3 data Symmetrixs
Hi folks,
I was trying to add a device to a device group via a script. This script also adds the local BCV and the RBCV. The device is in a valid RDF state. However adding the RBCV to the DG fails with the message The Symmetrix ID is not known.
I ran a symcfg list and it does not show the remote symmetrix (but it does show two other symmetrixes that reside in the same data centre). The version of SE is 5.5.0. All RA adapters are working correctly. An RDF ping is not showing the 3rd Symmetrix. The host I am creating the DG on, has only recently had storage from a new Symmetrix attached .e.g in the past it always had storage from SYM1 in Site1, with R2 storage on SYm1 in Site2. But know it also has storage from SYM2 in Site1, with R2 storage on SYM3 in Site2.
Other hosts in the same data centre as this, can see all 7 remote symmetrix devices without an issue. Can anyone think what the issue is? I've ran a symcfg disco. I'm going to attach a few gatekeepers now, but this will not make a difference. ANy help appreciated.
Davod
I was trying to add a device to a device group via a script. This script also adds the local BCV and the RBCV. The device is in a valid RDF state. However adding the RBCV to the DG fails with the message The Symmetrix ID is not known.
I ran a symcfg list and it does not show the remote symmetrix (but it does show two other symmetrixes that reside in the same data centre). The version of SE is 5.5.0. All RA adapters are working correctly. An RDF ping is not showing the 3rd Symmetrix. The host I am creating the DG on, has only recently had storage from a new Symmetrix attached .e.g in the past it always had storage from SYM1 in Site1, with R2 storage on SYm1 in Site2. But know it also has storage from SYM2 in Site1, with R2 storage on SYM3 in Site2.
Other hosts in the same data centre as this, can see all 7 remote symmetrix devices without an issue. Can anyone think what the issue is? I've ran a symcfg disco. I'm going to attach a few gatekeepers now, but this will not make a difference. ANy help appreciated.
Davod
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
February 29th, 2008 06:00
Can you check the output of "symcfg -ra all -sid $first_sym list" ?? Could you find the 3rd box in the output of the command ??
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
February 29th, 2008 08:00
run the command you specified the remote SYM devices
are listed.
It looks like that RDF is OK
device, it can see the remote R2 device on the remote
sym. When I try and add the R1 device to a reg device
group (the rational for this being, if it cannot see
the remote sym it will let me add it as a regular
device) an error is generated.
Unfortunatyl even if you don't see the remote box, your devices are R1 devices and you have to add them to an RDF1 type DG
Try again and eventually post the full error message if possible.
cecida
15 Posts
0
February 29th, 2008 08:00
Yes, all SYM devices are DMX series devices. When I run the command you specified the remote SYM devices are listed. When I do a SYMDG show on the local R1 device, it can see the remote R2 device on the remote sym. When I try and add the R1 device to a reg device group (the rational for this being, if it cannot see the remote sym it will let me add it as a regular device) an error is generated. The host in question is SAN boot, their are hundreds of RDF pairings between these two sym devices.
cecida
15 Posts
0
February 29th, 2008 10:00
I discovered the cause of the issue. I noticed that it could see one remote SYM, a DMX3000. But it could not see the DMX Series 3 or Series 4 models. So I checked the version of Solutions Enabler on the box, and it is nearly as old as myself. I upgraded the version of SE, and TIU and can now see all SYM devices.
Thanks for the help.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
February 29th, 2008 12:00
SKT2
2 Intern
2 Intern
•
1.3K Posts
0
February 29th, 2008 12:00