HP StorageWorks 2/24 FW 07.00.00/HAFM SW 08.06.00 McDATA Products in a SAN Env - Page 178
Con R_Ports, McDATA Fabric 1.0, Open Fabric 1.0, No Zone Synchronization, Append IPS, Zones
View all HP StorageWorks 2/24 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 178 highlights
Implementing SAN Internetworking Solutions 4 12. Configure R_Ports - For all configured SAN router R_Ports in the same fabric: a. The R_Port interconnect modes (McDATA Fabric 1.0 or Open Fabric 1.0) must be identical. This parameter is set at the SANvergence Manager application. The corresponding E_Port interoperability mode must also be identical. This parameter is set at the director or fabric switch Element Manager application. b. The zone policies (No Zone Synchronization or Append IPS Zones) must be identical. This parameter is set at the SANvergence Manager application. c. The error detect time-out values (ED_TOVs) must be identical. This parameter is set at the director or fabric switch Element Manager application. d. The resource allocation time-out values (RA_TOVs) must be identical. This parameter is set at the director or fabric switch Element Manager application. e. The port Domain_IDs must be different. This parameter is set at the SANvergence Manager application. 13. Multi-vendor guidelines - SAN routers support existing multivendor fabrics. However, when building a new fabric, it is good practice not to mix director and fabric switch vendors within the same fabric. A homogeneous fabric simplifies operation and fault isolation. 14. Port zoning - Comply with the following rules and best practices when using port zoning in a SAN routing environment: a. When a Fibre Channel fabric connects to a SAN router, port zoning is implemented per FC-SW2 standard. When communication between devices in a fabric stays within the fabric, port zoning works normally. b. When a router zone policy is set to No Zone Synchronization, remote devices are not port zoned in a local fabric. This is because remote entries in the local mSNS are node (device) WWNs, not port WWNs. For example, when a port-zoned device in Fabric A is zoned with a device in Fabric B, the device from Fabric A is WWN zoned. Although router ports can be port zoned, devices connected to a router port are propagated to remote fabrics using node (device) WWNs. 4-34 McDATA Products in a SAN Environment - Planning Manual