Best Practices for zoning in a Storage Foundation for Windows 4.x and 5.x environment

Best Practices for zoning in a Storage Foundation for Windows 4.x and 5.x environment

  • Article ID:100031254
  • Last Published:
  • Product(s):InfoScale & Storage Foundation

Problem

Best Practices for zoning in a Storage Foundation for Windows 4.x and 5.x environment

Solution

For World-WideName (WWN) zones, a generally accepted best practice is to include only onetarget and one initiator into each zone (in general, one zone per I/O path).This means that no Host Bus Adapters (HBA) should be in the same zone as anyother HBA and no disk array controller should be in the same zone as any otherdisk array controller (Figure 1 and Figure 2). The benefit of this configurationis that events occurring in one zone will not affect components that reside inother zones. Veritas Technical Support has observed many cases where thiszoning configuration eliminated intermittent read and write issues.
Figure1
 
Figure2
 
Note: Thediagram is intended to illustrate a concept. It is not a specific recommendationfrom Veritas.

Hardware Compatibility List:

Verify that thehardware configuration matches the Hardware Compatibility List (HCL)
The HCL contains a list of supported drivers and firmwarefor  HBAs, disk arrays, and switches that are compatible with StorageFoundation. When troubleshooting disk errors, verifying that the hardwareconfiguration matches the HCL is strongly recommended, even if thisconfiguration was working before the errors appeared. The HCL also containsnumerous footnotes regarding issues that are specific to certain hardware andconfigurations.

For compatibility information, review the HCL found inthe " Compatibility & Reference" section of the Support Web site forStorage Foundation for Windows https://entsupport.veritas.com/carveout_PID_15227_view_CL.htm

Related Articles

Disk read or write errors are reported by "vxio" in the Windows Event Viewer with Storage Foundation for Windows installed

Was this content helpful?