McDATA StorageWorks 2/140 - Director Switch Planning Manual page 173

7. Use redundant mFCP connections - For high availability (not
increased bandwidth), use multiple mFCP connections between
SAN routers to ensure the mSAN does not partition and
connectivity to routing domains 30 and 31 remains intact.
8. Assign common-numbered mFCP port pairs - Although any
FCP port can be paired with any FCP port on another SAN router,
for simplified tracking it is good practice (where possible) to
assign identical port numbers to both connections of a
high-availability mFCP link. For example, connect port 5 of SAN
router A to port 5 of SAN router B.
9. Assign common-numbered iFCP port pairs - Although any local
intelligent port can be paired with any remote intelligent port, for
simplified tracking it is good practice (where possible) to assign
identical port numbers to both connections of an iFCP link. For
example, connect port 14 of SAN router A to port 14 of SAN
router B.
10. Track iFCP sessions - Every initiator-to-target device pair in a
merged zone is assigned an iFCP session. Be aware of the number
of active iFCP sessions. If approaching the per-port limit (64
sessions) un-export zones without active storage traffic to free up
sessions.
11. Document zones and iFCP links for each mSAN - Use the
following pair of example forms to track zone and iFCP link
information. For an initial configuration, transfer values from the
forms to the routed network using the SANvergence Manager
Element Manager applications. For sustaining maintenance, copy
information from the SAN management applications (through
printable HTML reports) to the forms for consistency checks and
archival.
Implementing SAN Internetworking Solutions
Implementing SAN Internetworking Solutions
4
4-31