User manual HP STORAGEWORKS 2/12 EDGE SWITCH FW 07.00.00/HAFM SW 08.06.00 MCDATA PRODUCTS IN A SAN ENVIRONMENT PLANNING MANUA

[. . . ] McDATA® Products in a SAN Environment Planning Manual P/N 620-000124-500 REV A Record of Revisions and Updates Revision 620-000124-000 620-000124-100 620-000124-200 620-000124-300 620-000124-400 620-000124-500 Date 5/2002 9/2002 2/2003 8/2003 12/2003 2/2005 Description Initial release of the manual. Revision of the manual to describe the Intrepid 6140 Director, Sphereon 4500 Switch, and Release 6. 3 of the Enterprise Fabric Connectivity Manager application. Revision of the manual to include additional information and describe Release 7. 1 of the Enterprise Fabric Connectivity Manager application. Revision of the manual to describe the Sphereon 4300 Switch and Release 7. 2 of the Enterprise Fabric Connectivity Manager application. [. . . ] These devices are physically connected to Fabric 2. One virtual switch (Domain_ID 31) that represents a routing domain with device D7 logically attached. This device is physically connected to the router. · As shown in Figure 4-5 from a logical connectivity perspective, fabric 2 appears as follows: · · · · One Fibre Channel director (Domain_ID 7) with direct-attached devices D3 and D4. One Fibre Channel switch (Domain_ID 8) with direct-attached devices D5 and D6. One edge switch (Domain_ID 2) that represents an R_Port. One virtual switch (Domain_ID 30) that represents a routing domain with devices D1 and D2 logically attached. These devices are physically connected to Fabric 1. One virtual switch (Domain_ID 31) that represents a routing domain with device D7 logically attached. This device is physically connected to the router. · Routing domains represent devices from remote fabrics and are a key part of SAN routing. The routing domain with Domain_ID 30 enables routing between multiple fabrics (mSAN routing). The routing domain with Domain_ID 31 enables routing between multiple mSANs (iSAN routing). Refer to mSAN Routing or iSAN Routing for additional information. 4-14 McDATA Products in a SAN Environment - Planning Manual Implementing SAN Internetworking Solutions 4 R_Port Domain_ID Assignment The default preferred Domain_ID for each SAN router R_Port is 1. However, each port should be assigned a preferred Domain_ID (set at the R_Ports tab of the Fabric Configuration dialog box) that is unique within the attached fabric. The principal switch in the attached fabric then attempts to allocate this requested (preferred) Domain_ID to the R_Port. If the requested value is in use, the principal switch assigns the first available Domain_ID. NOTE: If more than one R_Port (from the same router or multiple routers) is attached to a fabric, each port requires a unique Domain_ID. The Insistent Domain_ID option (enabled at the R_Ports tab of the Fabric Configuration dialog box) ensures an R_Port gets a predictable (assigned) address. However, if the Insistent Domain_ID check box is enabled for an R_Port and the port does not get the preferred address, the R_Port segments and does not connect to the fabric. In addition, R_Ports segment if: · Two R_Ports physically connect to a single fabric and the connections are configured (at the SANvergence Manager application) for attachment to a pair of fabrics. Two R_Ports physically connect to two fabrics and the connections are configured (at the SANvergence Manager application) for attachment to a single fabric. · It is recommended that insistent (unique) Domain_IDs be assigned to directors, fabric switches, and R_Ports in routed fabrics. Assigning Domain_IDs results in known network addresses, predictable device behavior, and ease of locating and identifying equipment. Router Fabric Manager A fabric-attached R_Port acts as a router fabric manager that manages fabric discovery, device registration, zoning, and other fabric-related activities between the router and attached fabric. The router fabric manager provides communication between the fabric's simple name server (SNS) and the router's metropolitan simple name server (mSNS) or Internet simple name server (iSNS). When a SAN router connects to a Fibre Channel fabric, device information is mutually exchanged. [. . . ] Log does not contain EFCM user name and IP address of EFCM client. Audit log entries related to flexible partitioning Flexpar feature not supported. Other log entries related to flexible partitioning Audit log entries (EFCM) Flexpar feature not supported. Flexpar feature not supported. Log contains EFCM user name and IP address of EFCM client. Remote workstations (clients) not supported through the SANvergence Manager application. The application supports an APP log that is functionally equivalent to the EFCM Audit log. In addition, the Element Manager application has an Audit log independent of SANvergence Manager. B-10 McDATA Products in a SAN Environment - Planning Manual Firmware Summary Table B-6 E/OS versus E/OSn and E/OSi - Management-Related Differences (Continued) E/OS 7. 0 User-selectable option on a per product basis. E/OSn 6. 0 User-selectable option on a per user (different for each login ID) or per product basis. [. . . ]