09-21-2004 11:52 PM
Here is attached the Excel file I have received, so you can see the "hanging" in the zoning.I've looked at FAQ, and also Fabric OS procedure guide and Fabric OS reference guide, ans also Zoning guide, but I haven't found anything about hanging in the zoning.
10-11-2004 07:16 PM
"the hanging aliases were gone"<!
graemlin::)>What you noticed on the hanging aliases should have only occurred in the first week after we added this functionality to the reports. On some FOS versions SAN Health could mistakenly report some extra hanging zones - mostly for zones that used the Fabric Assist method for defining an initiator - the curly brackets were not decoded correctly Single HBA zoning most closely recreates the original SCSI bus. Each zone created has only one HBA (initiator) in the zone, with each target device then added to the zone. Typically, you should create a zone for the HBA and then add disk storage ports. If the HBA accesses tape devices, you should create a second zone for the HBA and associated tape devices. In the case of clustered systems, it might be appropriate to include an HBA from each of the cluster members in the zone. This technique is equivalent to having a shared SCSI bus between cluster members, and presumes that the clustering software provides a way to manage access to the shared devices. In a large fabric, this requires the creation of possibly hundreds of zones. However, each zone would contain only a few members. As a result, zone changes would affect the smallest possible number of devices, minimizing the impact of an incorrect zone change. Because of these advantages, the single HBA zoning strategy is considered a Brocade best practice.