Release Notes

70 System Firmware Version 5.1.1.7
Known Restrictions and Limitations
Release 5.1.1.7
Description
User Impact
PowerConnect 8100 Series QSFP DAC CR4 40GB cable fails to link up with
partner switch (for example. Dell Force10 S4810). After upgrading a Power
Connect 8100 series switch to firmware 5.1.0.1 customers may experience
loss of connectivity when using 40G QSFP CR4 DAC cables with partner
switch. Some partner switch vendors may by default leave auto-negotiation
disabled for CR4 connections. This will cause a negotiation mismatch and
the QSFP CR4 port will not link up.
High
In 5.1.0.1 firmware a behavioral change, as
per IEEE spec, was made that means that
when a QSFP CR4 cable is connected the
40gb port has auto-negotiation enabled. In
previous versions of firmware the default
behavior was to leave auto-negotiation
disabled. This change was required in order
to ensure compliancy to the following
specifications:
IEEE 802.3-2012 Section 6 / Clause 85.3 /
Clause 82.6 / Clause 73.9 - explains that
auto-negotiation is mandatory for 40GBASE-
CR4 and 100GBASE-CR10.
Workaround:
Enable auto-negotiation on 40G interface of
Dell Force10 S4810 switch like below:
S4810#conf
S4810(conf)#int fortyGigE 0/60
S4810(conf-if-fo-0/60)#intf-type cr4 autoneg
When https enabled with a 2048 bit key CPU sslt tasks will require a high
CPU processing load for 5 – 10 seconds.
Medium
HTTPS login attempt may timeout.
Workaround:
Use 1024 or lower key.
PCM6220 switch does not support “Private VLAN” feature Private VLAN feature requires hardware
support that the PCM6220 XGS3 switching
fabric does not contain.
Workaround:
None.
Release 5.1.0.1
Description
User Impact
SNMP walk is not successful while doing walk on root port
Low
SNMP walk on root port may result in a
timeout if executed without specifying any
timeout value.
Workaround:
Execute walk with a recommended timeout
value of 2 sec
The IPMC L2_BITMAP is only updated to reflect ports that should 'not' be
flooded when a multicast stream is 'first' seen on a VLAN.
Moderate
There will be some flooding of multicast
traffic
Workaround: Issue no ip multicast followed
by ip multicast