Figure 80 FCIP impact on existing iSCSI configurations — dual fabrics per blade
.
In the dual FC fabric case, the impact is higher because after adding an FCIP Route there is only one
remaining FC port available for iSCSI. Therefore, only the targets from one fabric or the other will be
available to iSCSI initiators connected to that MPX200 blade; access to targets on the other fabric
are through another MPX200 blade.
FCIP and iSCSI performance
In most use cases, mixing iSCSI and FCIP on the same blade provides adequate performance. However,
high availability/performance goals may dictate a dedicated MPX200 for each function or protocol.
For example, if your performance needs are for more that 8 Gb/s of FC access for iSCSI alone,
configuring FCIP on the same blade would limit FC access to only 8 Gb/s and would not meet the
performance requirements for that situation.
MPX200 iSCSI/FCIP configurations
The MPX200 router supports the following configurations:
• Figure 81
• Figure 82
MPX200 FCIP with B-series Integrated Routing
• Figure 83
MPX200 FCIP with C-series IVR
• Figure 84
• Figure 85
MPX200 high-availability configuration with fully-redundant long-distance links
• Figure 86
MPX200 configuration with remote IP distance gateway (mpx110)
• Figure 87
MPX200 highly-redundant configuration with one or two long-distance links
• Figure 88
• Figure 89
MPX200 simultaneous iSCSI and FCIP with remote dedicated FCIP blade
• Figure 90
• Figure 91
120
MPX200 FCIP
MPX200 basic FCIP configuration with one or two long-distance links
MPX200 high-availability configuration with one or two long-distance links
MPX200 highly redundant pairs of gateways with fully-redundant long-distance links
on page 124 MPX200 simultaneous iSCSI and FCIP, both local and remote
on page 125 MPX200 iSCSI and FCIP dedicated blades, both local and remote