distance configuration for these ports or explicitly disabling QoS on other ports, freeing up
buffers for the last four ports.
• With the Fabric OS 6.2.1 and later firmware upgrade, the default behavior of the Adaptive
Networking QoS feature changes as follows:
◦ Default QoS behavior is disabled on 4-Gb platforms.
◦ Default QoS behavior is disabled on the Extended Fabrics E_Ports on both 4-Gb and
8-Gb platforms.
This fix addressed the following unexpected behaviors that occurred when the Adaptive
Networking QoS feature was enabled by default in earlier Fabric OS releases:
◦ Splitting of a single trunk group into multiple trunk groups upon port toggle, since the
toggled ports come online with QoS enabled, while the remaining ports in the trunk group
have QoS disabled.
◦ Fewer buffer credits being made available to normal E_Ports after a port toggle, even
when QoS is not being utilized.
◦ An unexpected change to a fill-word configuration on an Extended Fabrics E_Port after
a port toggle. If an Extended Fabrics E_Port is using IDLE primitives as fill words, and if
that port toggles, the fill-word configuration is changed to use ARB primitives.
NOTE: After upgrading to this firmware release, if users want to enable the Adaptive Networking
QoS feature on 4-Gb platforms and on the Extended Fabrics E_Ports on both 4-Gb and 8-Gb
platforms, they must do so explicitly through the available user interfaces.
FC Routing
All FCR switches must be running Fabric OS 6.2.1x or later in order to support M-EOS 239 Domain
Mode on the Mi10K.
FCR backbone fabric ID changes
• With 8-Gb director blades, the switch must be disabled to change the backbone fabric ID.
• With routing and dual backbone fabrics, the backbone fabric ID must be changed to keep
the IDs unique.
Traffic isolation over FCR
• All switches and FC routers, both in edge and backbone fabrics, must be running Fabric OS
6.1.0 or later in order to support this feature.
• In order for traffic isolation over FCR to function properly, the associated TI zones in each
fabric (edge and backbone) must have failover enabled.
Integrated routing
• To allow Hot Code Load on an HP StorageWorks 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 EX_Ports are supported only in the base switch on a switch with VF enabled.
To test Integrated Routing functionality, first disable the VF feature (fosconfig --disable
vf).
• Integrated Routing and Top Talkers cannot run concurrently in Fabric OS 6.2.x. To use
Integrated Routing, be sure to disable Top Talkers before configuring EX_Ports.
22