Release Notes

Functional Area Feature Description Summary of Benefits
NOTE: This feature is only supported on the
M
X9116n switch.
See the OS10.5.2 product support pages ( w
ww.dell.com/support) for user documentation pertaining to the new features.
Known Software Behavior - Dell EMC PowerEdge MX
NOTE:
The software behaviors that are mentioned here are applicable to OS10 revision 10.5.0.1 and later.
Ethernet Modules
● Wh
en upgrading from earlier releases to 10.5.0.7, aaa authentication configuration with nonlocal authentication methods as
the first target in the startup configuration gets rejected and replaced with the default aaa authentication configuration: aaa
authentication login default local.
● If you configure multiple authentication methods on Dell EMC PowerEdge MX7000 Ethernet modules - MX9116n Fabric
Switching Engine and MX5108n Ethernet Switch, you must configure local authentication as one of the methods in the list.
Before 10.5.1.6, local authentication had to be the first method in the list.
● From 10.5.1.6, if you configure multiple authentication methods on Dell EMC PowerEdge MX7000 Ethernet modules -
MX9116n Fabric Switching Engine and MX5108n Ethernet Switch - you must configure local authentication as one of the
methods in the list.
False Errors on FC Ports
● The total errors count in the show interface fibrechannel command output displays incorrect values during
FC port flaps, IOM reboot, or port conversion from ETH to FC, followed by bringing up of the FC port.
NOTE: This behavior is applicable only to the MX9116n.
Fibre Channel
● Af
ter you change the FC Map on FIP snooping enabled active VLAN sessions, use the shut and no shut commands to
reestablish the FCoE sessions.
● The maximum number of members in an FC Zone is 255.
NOTE: This behavior is applicable only to the MX9116n.
● For the d
efault-zone settings to work properly, ensure that the maximum number of logged-in FC and FCoE nodes is
less than 120.
NOTE: This behavior is applicable only to the MX9116n.
● F
CoE-generated Access Control Lists (ACLs) take precedence over user-configured ACLs. A user-configured ingress ACL
e
ntry cannot deny FCoE and FIP snooping frames.
● After you remove the vfabric configuration from an interface, to configure the MTU to default value, configure the
nondefault MTU and then configure the default MTU.
● In a FIP snooping bridge, FIP and FCoE frames ingressing on a PFC mismatch interface are dropped.
NOTE: This behavior is only applicable to the MX9116n and MX5108n.
● PFC mismatch on a port channel member port drops FIP and FCoE frames ingressing on that member port, but the learned
Enode/Session/FCF information that is associated with the port channel is retained. This results in FCoE show commands
displaying misleading information. To resolve this issue, check and correct the PFC configuration on both the ends.
● When you configure a port channel as VLT port channel, the port channel goes down operationally and comes up in the local
device. The physical interfaces are operationally up. This leads to the switch removing the FCoE sessions. The remote server
is not aware of the port channels being up and down, so the server maintains the FCoE sessions. As these sessions are not
available in the switch, the FCoE frames are dropped in the switch. To resolve this, manually flap the port channel.
2