I think officially that both single initiator > single target and single initiator > multiple target zoning is supported, but single initiator > single target zoning is the preferred and recommend zoning. If you are ever going to use MirrorView or SANCopy you will need this type of zoning in place.

A zone should be single initiator, single target.

Now this said, the amount of zoning between a server with a CX depends on many factor but you have 2 good choice.

1. Single HBA to 1 port SP (so for 2 HBA, you go zone 1 HBA to one port of SPA and the other HBA to SPB).
2. If the server has only 1 HBA, you create 2 zones, with the same initiator (HBA) but the target will be one port on SPA and the other zone, another port to SPB
3. The full mesh way: 2 HBA, each HBA has 2 zones, each zone to a port on each SP. So you have 4 paths.

Sabey

In my environment. we have one zone with two SP's. In this case also I have 4 paths. Does this zoining will have any effect? what is the role of zoning in mirror views as mention above post.

Generally EMC recommends single initiator zoning - one HBA per zone. You can have more than one SP port in a zone, but if you are planning on using either Mirrorview or SAN Copy, then you need to keep the zones to one HBA and one SP port. The reason for this is that these packages when installed will make the SP ports behave as initiators and you must follow the single initiator zoning rule. If you have zones with two SP ports, then the SP ports will attempt to log into each other and that will cause problems.

example below is what I recommend:

HBA1 <-> SPA 0
HBA1 <-> SPB 1
HBA2 <-> SPA 1
HBA2 <-> SPB 0

glen