Release Notes

76 System Firmware Version 5.1.1.7
control (FIP) and FCoE data traffic.
In cases, where FIP and FCoE use different priorities, it is expected that
intermediate switches are configured to treat them accordingly. In cases where
ports are configured in DCBX auto mode and configuration source carries two
TLVs, one for FIP and other for FCoE with different priorities then it is expected
that FSB/DCB should forward this information to downstream ports.
The PowerConnect FSB implementation ignores the FIP TLV and does not
forward this information to the peers. In such cases, Host will not know the
special treatment or expected priority for FIP frames. Considering that slow
protocol and this being a corner case situation, this can be a readme and
documented in release notes.
FIP Snooping Over Stack Results in
eNode in Ethernet VLAN
Low - When trying to accomplish FIP snooping over the stack, the eNode address
is put in the wrong VLAN causing the connections to never occur. FCoE is not
supported across the stacks so this is a non-issue.
End of Release Notes