This post is more than 5 years old
11 Posts
0
2577
October 30th, 2017 05:00
Single Initiator and Single Target Zoning
Hi
As of now we are using zoning with single initiator and multiple targets. We have both Dell Compellent and EMC VNX 5200 storage. With Compellent we are using virtual interfaces against each physical ports / wwns and DELL recommended to use all four virtual interfaces as target in a zone. With EMC SAN and MDS we are confused to go with "single initiator with single target" or "single initiator with multiple target" option. Is there performance impact or load for single initiator with multiple target option or is a just a best practice ?
Thanks in advance
No Events found!
umichklewis
3 Apprentice
•
1.2K Posts
0
October 31st, 2017 13:00
Single Initiator with Single Target is nearly always best practice. In some cases, ports that can act as initiators or targets (i.e. MirrorView ports, for example) could accidentally log into each other if there were in a single initiator, multi-target zone.
There's seldom any performance impacts, just usability and cleanup. Let us know if that helps!
Karl
LALMS
11 Posts
0
November 1st, 2017 05:00
Thank You
We used to do the zoning with single initiator and multiple targets and didn't ever face any issues.
We are not using MirrorView, the issue you mentioned may happen only with Mirror View ports?
With Single Initiator Single Target, is there any way to control the bandwidth with Server HBA or storage ports? One Vendor told us by using SIST we can control the bandwidth usage a particular port used by storage, but we are not sure how to achieve this.
Regards
dynamox
9 Legend
•
20.4K Posts
0
November 1st, 2017 13:00
i have only seen it with MirrorView, never with SANCopy. Since you are using MDS, read up on SmartZonning, it will allow you to put multiple targets (and initiators if you wanted to) in the same zone without the fear of them logging into each other.
Bandwith usage as in QOS ? Nothing like that ever existed on MDS nor on VNX. Now on VMAX you have some host controls where you can throttle certain things from array perspective.