Assuming this is related to your MirrorView post, I'd start by getting both VNX into the same Unisphere management domain, for simplicity.
Next, I'd review the MirrorView knowledge book from the other post, as it has the instructions for ensuring your zones are correct. Where as MirrorView ports can accept server storage traffic, MirrorView port cannot be used for SANCopy, so ensure you're not using those ports for your SANCopy setup.
Also, once your VNX are properly zoned together, you'll see them in Unisphere GUI under the Connectivity Status pane and the SAN Copy Initiators Tab:
SAN Copy Operations and management > Managing with Unisphere
Did you update the SAN Copy connections? The initiator type should say "SAN Copy". Once that's done, and the initiators added to the Storage Group (Right Click SG > SAN Copy Connections), things should proceed without connectivity problems.
Make sure that your zones are single initiator zones. The scenario as I understand it is:
VNX1 replicating with a SAN Copy Push to VNX2
In that case, VNX2 is a "target" (like an array is normally) and VNX1 is an "initiator" (like a host, since it's pushing the data to VNX1). So, the zones between the two arrays really need to be one port on VNX1, to another port on VNX2. Don't put two ports from the same array into the same zone. The VNX ports can be initiators or targets, so putting two into the same zone can be confusing in some instances. Here's the recommended zoning:
Zones
SAN Copy storage system
Remote storage system
Zone 1
SP A1
SP A1
Zone 2
SP A1
SP B1
Zone 3
SP B1
SP A1
Zone 4
SP B1
SP B1
In your case, VNX1 is the SAN Copy storage system. A1 (or B1) is the second port on the module, A0 is the first one, and is a MirrorView port so don't use that.
Then you need to create a storage group on VNX2, and call it "SAN_Copy" or something like that. Place the VNX1, as a host, into that storage group, along with the target luns you want VNX1 to write to.
The SAN copy white paper referenced above should help.
That was just an example, but it does apply to your configuration. Your zones should work like you are showing - you have single initiator zones so you are good there. The only difference from the example is that they also connect SPA to SPB. In your case, that would mean adding zones like this:
vnx1a1; vnx2b1
vnx1b1; vnx2a1
Then the same for the other switch. That's just an additional level of redundancy, this should work with only one port on each VNX. From your latest screenshot, A1 and B1 are not logged into the switch (speed is N/A). I would go back and double check the ports are logged into the switch, and make sure your zones are correct. Until VNX1 shows up in the Initiators list in VNX2 you can't get anywhere.
Once those initiators do show up, do the update SAN Copy Connections. Then get VNX1 as a host, added to the storage group on VNX2 and you should be in business.
Run the Update SAN Copy Connections. In Unisphere go to Storage->Data Migration->SAN Copy. Click on Update SAN Copy Connections in the Data Migration area in the panel to the right. That should result in the VNX2 logging into the VNX1.
If you haven't done so, I'd open an SR with EMC Support. At the minimum, they'll have you walk through your zoning again. I have to think, if everything is zoned correctly, it has to be something with the switchport or feature configuration. Speaking of that, which type of switch are you using? Cisco MDS? Brocade? What code version?
I once worked on a customer POC involving a QLogic SANSurfer fabric. We couldn't get MirrorView working because the customer's switch config disabled RSCNs to configured ports. Therefore, the CXs were not able to discover each other, unless we power-cycled the SPs or physically unplugged cables. Once they enabled the feature (and rebooted the switches!), we had no issues.
What happens when you run "Update SAN Copy Connections?" Do it on both arrays. What you are looking for is VNX1 to login to VNX2 as a host. When that happens, on VNX2 you should see the initiator records from VNX1. At that point you can create your storage group on VNX2 and put the VNX1 initiators in it.
You can update SAN Copy connections from the CLI instead of the GUI if you want:
naviseccli -h SPA sancopy -updateconnections
Other things to check:
- Just to be sure - you do have a SAN Copy enabler installed on VNX1, yes?
- Double check your zoning.
- Logout of Unisphere, and log back in.
- Reset the management server (point your browser at IP Address>/setup.html)
Can you expand on that error message you posted the image of? What is it saying about zoning?
umichklewis
3 Apprentice
•
1.2K Posts
0
August 27th, 2015 09:00
Assuming this is related to your MirrorView post, I'd start by getting both VNX into the same Unisphere management domain, for simplicity.
Next, I'd review the MirrorView knowledge book from the other post, as it has the instructions for ensuring your zones are correct. Where as MirrorView ports can accept server storage traffic, MirrorView port cannot be used for SANCopy, so ensure you're not using those ports for your SANCopy setup.
Also, once your VNX are properly zoned together, you'll see them in Unisphere GUI under the Connectivity Status pane and the SAN Copy Initiators Tab:
Let us know if that helps!
Karl
adhamakady
65 Posts
0
August 27th, 2015 11:00
I'd check out the SAN Copy White Paper (https://support.emc.com/docu32565_White-Paper:-SAN-Copy---A-Detailed-Review.pdf?language=en_US), page 13:
SAN Copy Operations and management > Managing with Unisphere
Did you update the SAN Copy connections? The initiator type should say "SAN Copy". Once that's done, and the initiators added to the Storage Group (Right Click SG > SAN Copy Connections), things should proceed without connectivity problems.
Adham
usao
2 Intern
•
222 Posts
0
August 27th, 2015 14:00
I tried updating the connections, but the arrays continue to only see them selfs and do not see each other.
The initiators are only for the local array, not the other array.
Also, one of the arrays is only showing 2 ports correctly, instead of 4 ports.
usao
2 Intern
•
222 Posts
0
August 27th, 2015 14:00
It's related, but someone had recomended using SanCopy instead of mirrorview, so im trying that route currently.
Both VNX arrays are in the same domain.
Not sure where to find the "connectivity status". All I can find is a page for "Initiators" which is what I showed above.
storagtetalk
1 Rookie
•
53 Posts
0
August 27th, 2015 20:00
Make sure that your zones are single initiator zones. The scenario as I understand it is:
VNX1 replicating with a SAN Copy Push to VNX2
In that case, VNX2 is a "target" (like an array is normally) and VNX1 is an "initiator" (like a host, since it's pushing the data to VNX1). So, the zones between the two arrays really need to be one port on VNX1, to another port on VNX2. Don't put two ports from the same array into the same zone. The VNX ports can be initiators or targets, so putting two into the same zone can be confusing in some instances. Here's the recommended zoning:
In your case, VNX1 is the SAN Copy storage system. A1 (or B1) is the second port on the module, A0 is the first one, and is a MirrorView port so don't use that.
Then you need to create a storage group on VNX2, and call it "SAN_Copy" or something like that. Place the VNX1, as a host, into that storage group, along with the target luns you want VNX1 to write to.
The SAN copy white paper referenced above should help.
usao
2 Intern
•
222 Posts
0
August 28th, 2015 08:00
Guess im a bit confused about the zoning.
Currently all the A1/B1 ports are going to one switch, while the A2/B2 ports are going to the second switch.
If I only zone the A1/B1 ports, then all the traffic would be on a single switch.
The way it's currently zoned is:
SW1:
zone: VNX_SCa vnx1a1; vnx2a1
zone: VNX_SCb vnx1b1; vnx2b1
SW2:
zone: VNX_SCa vnx1a2; vnx2a2
zone: VNX_SCb vnx1b2; vnx2b2
Is this satisfactory? Ive paired the A1 ports together, the B1 ports together, the A2 ports together and the B2 ports together.
Correction, im using ports A2/B2 and A3/B3, while A0/B0 and A1/B1 are not connected to anything currently.
storagtetalk
1 Rookie
•
53 Posts
0
August 28th, 2015 12:00
That was just an example, but it does apply to your configuration. Your zones should work like you are showing - you have single initiator zones so you are good there. The only difference from the example is that they also connect SPA to SPB. In your case, that would mean adding zones like this:
vnx1a1; vnx2b1
vnx1b1; vnx2a1
Then the same for the other switch. That's just an additional level of redundancy, this should work with only one port on each VNX. From your latest screenshot, A1 and B1 are not logged into the switch (speed is N/A). I would go back and double check the ports are logged into the switch, and make sure your zones are correct. Until VNX1 shows up in the Initiators list in VNX2 you can't get anywhere.
Once those initiators do show up, do the update SAN Copy Connections. Then get VNX1 as a host, added to the storage group on VNX2 and you should be in business.
usao
2 Intern
•
222 Posts
0
August 28th, 2015 14:00
Correct. ports 0 and 1 are not physically connected to anything. Only ports 2 and 3 are connected to the switches.
The issue I seem to have is that the arrays (although zoned together) do not see each others initiators.
On VNX1 I only see the VNX1 initiators, and the same for VNX2.
At this time, I don't know how to make them see each others initiators. I must be missing something, but not sure what it is.
storagtetalk
1 Rookie
•
53 Posts
0
August 28th, 2015 18:00
Run the Update SAN Copy Connections. In Unisphere go to Storage->Data Migration->SAN Copy. Click on Update SAN Copy Connections in the Data Migration area in the panel to the right. That should result in the VNX2 logging into the VNX1.
usao
2 Intern
•
222 Posts
0
August 31st, 2015 12:00
It's just not working. I don't know what im doing wrong, and my boss is getting frustrated with the lack of progress.
SW1:
zone: VNX_SCa vnx1a2; vnx2a2
zone: VNX_SCb vnx1b2; vnx2b2
SW2:
zone: VNX_SCa vnx1a3; vnx2a3
zone: VNX_SCb vnx1b3; vnx2b3
Is there some service or something which I can find someone to login to the array and fix this once and for all?
storagtetalk
1 Rookie
•
53 Posts
0
August 31st, 2015 14:00
Live chat is your friend. They should have you up and running pretty quickly.
Rainer_EMC
4 Operator
•
8.6K Posts
0
August 31st, 2015 14:00
Then I would suggest to open a service request
umichklewis
3 Apprentice
•
1.2K Posts
0
August 31st, 2015 14:00
If you haven't done so, I'd open an SR with EMC Support. At the minimum, they'll have you walk through your zoning again. I have to think, if everything is zoned correctly, it has to be something with the switchport or feature configuration. Speaking of that, which type of switch are you using? Cisco MDS? Brocade? What code version?
I once worked on a customer POC involving a QLogic SANSurfer fabric. We couldn't get MirrorView working because the customer's switch config disabled RSCNs to configured ports. Therefore, the CXs were not able to discover each other, unless we power-cycled the SPs or physically unplugged cables. Once they enabled the feature (and rebooted the switches!), we had no issues.
storagtetalk
1 Rookie
•
53 Posts
0
August 31st, 2015 14:00
What happens when you run "Update SAN Copy Connections?" Do it on both arrays. What you are looking for is VNX1 to login to VNX2 as a host. When that happens, on VNX2 you should see the initiator records from VNX1. At that point you can create your storage group on VNX2 and put the VNX1 initiators in it.
You can update SAN Copy connections from the CLI instead of the GUI if you want:
naviseccli -h SPA sancopy -updateconnections
Other things to check:
- Just to be sure - you do have a SAN Copy enabler installed on VNX1, yes?
- Double check your zoning.
- Logout of Unisphere, and log back in.
- Reset the management server (point your browser at IP Address>/setup.html)
Can you expand on that error message you posted the image of? What is it saying about zoning?
usao
2 Intern
•
222 Posts
0
August 31st, 2015 21:00
Nothing changes when I update connections on both VNX arrays.
They still only show their own initiators.
Where is this "live chat", and with whom to chat? I thought that was the purpose of this support forum?