XP Zoning

[Alzhy]

Our XP12K will be hooked up to purely HP-UX environments. Do we need a zone for each XP FC ports and Server HBAs? Or just a big zone for all the XP FC ports and all the Server HBAs since we'll be using LUN Security (Hostgroups) anyway?

[Tanapong Eamsoponkul_1]

I think that you need zoning for each pair of target and initiator , it better than big zone

1. sometime later,if you have change to a zone it not effect to another host , it effect only pair on zone (if hardzone)
2. to make sure have only pair of target and initiator in one zone

[Ranjith_5]

Hi Nelson,

Attaching a small PDF on zoning.
Hope this will helps you.

Regards,
Syam

[Duncan Edmonstone]

Nelson,

As usual there's not really a standard, just good practice - and good practice says regardless of what technology is used on the disk array use single-initiator zones - thats one zone for every HBA in every system - zoned to the ports that HBA needs to see on the XP. That can add up to a lot of zone, but it means that each HBA can only see XP ports and no other HBAs - if one of them goes faulty you minimise the impact...

HTH

Duncan

[Chad Sellars]

I have just completed rezoning about 100 systems to single initiator zones. When HP setup our 3 XP1024's they zoned by OS. We found that Stage Change Notifications propagated to all systems in the zone whenever a member rebooted. This caused errors in HPUX, Solaris and Windows system logs. Recent Brocade firmware does not propagate SCNs to the systems that are not in the same zone as the node that is changing state. We observed this by reading the tracelogs from the switches and decoding it with Brocades handy decoder.

The errors have stopped with the zoning change.

[Derek_31]

We also zone by single initiator to help isolate problems. We have all Windows hosts.