HP 4400 HP StorageWorks Fabric OS 6.3.2b Release Notes (5697-0777, November 20 - Page 27
Broadcast frame forwarding in FCR fabric, FC Routing with Mi10K, Integrated routing, FC FastWrite
View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 27 highlights
Broadcast frame forwarding in FCR fabric Broadcast frame forwarding is not supported in an FCR fabric with a 2408 FCoE Converged Network Switch. By default, broadcast frame forwarding is disabled on the FC router. If your edge fabric includes a 2408 FCoE Converged Network Switch, do not enable broadcast frame forwarding on the FC router, which can degrade FCR performance when there is excessive broadcast traffic. FC Routing with Mi10K Using FC routing in a backbone-to-edge configuration with an Mi10k in the edge fabric, can result in slow throughput for hosts attached to the Mi10K following a bounced IFL connection between the backbone and edge fabric. To resolve this slowdown, disable and then re-enable the Mi10K ports for the affected hosts. Mi10k directors operating with firmware earlier than MEOS 9.9.5 may experience repeated system faults when attached as an FCR edge switch to a 1606 Extension SAN Switch EX_Port. To avoid this, ensure that the Mi10k is operating with MEOS 9.9.5 or later for this configuration. Integrated routing • To allow HCL on an 8/40 SAN Switch when using Integrated Routing, the edge switch connected to the 8/40 SAN Switch must be running Fabric OS 6.1 or later. • Integrated Routing and Top Talkers cannot run concurrently in Fabric OS 6.3.x. To use Integrated Routing, be sure to disable Top Talkers before configuring EX_Ports. FC FastWrite When an FC FastWrite Initiator is moved to a port that does not have FC FastWrite enabled, I/O will recover and revert to the slow path route (non-FC FastWrite). This is a change from Fabric OS 6.2.x. Native connectivity Fabric OS-based platforms operating in interopmode 2 or 3 should never be deployed in a fabric without at least one M-series switch. Fabric OS switches in interopmode 3 (McDATA Open Fabric Mode) do not support configuration of zoning without an M-series switch in the fabric. When migrating from M-series to B-series switches, all B-series switches should be configured to interopmode 0 (Brocade Native mode) after the last M-series switch has been removed from the fabric. M-EOSc switches may exhibit a behavior where they block all attached devices with a reason indication of Blocked Temporarily, Internal. This can occur when you power cycle the M-series switch while it was participating in a fabric with Frame Redirection zoning, a capability used for Fabric OS-based application or encryption services. If the switch is still participating in the fabric with Frame Redirection, issue the cfgsave command from a Brocade Fabric OS-based switch with the Frame Redirection zone in its defined zone database. If the M-EOS switch is no longer attached to the fabric with Frame Redirection zoning, issue the Config.Zoning.deleteSplZoneSet command via the CLI to the M-EOS switch. FCS Automatic Distribution • When using the FCS Automatic Distribution feature in Fabric OS 6.0 or later, all switches in the fabric must be running Fabric OS 6.0 or later. If any switches are running Fabric OS 5.x or earlier, only manual distribution can be used. HP StorageWorks Fabric OS 6.3.2b Release Notes 27