Beruflich Dokumente
Kultur Dokumente
N4064/N4064F/N4032/N4032F/8100/N3048P/N3048/N3024P/N3024/
N3024F/N2048P/N2048/N2024P/N2024
Dell Networking
6.1.0.6 Firmware Release Notes
Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Trademarks used in this text: Dell, the DELL logo and PowerConnect are trademarks of Dell Inc; Intel and Pentium are registered trademarks and
Celeron is a trademark of Intel Corporation; Microsoft and Windows are registered trademarks of Microsoft Corporation.
Other trademarks and trade names may be used in this document to refer to either the entity claiming the marks and names or their products. Dell
Inc. disclaims any proprietary interest in trademarks and trade names other than its own. All rights reserved. This document may not, in whole or
in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form without the prior written
consent of Dell. Dell reserves the right to make changes without further notice to any products or specifications referred to herein to improve
reliability, functionality or design.
Reproduction, adaptation or translation without prior written permission is prohibited, except as allowed under the copyright laws.
Table of Contents
Introduction 1
Global Support 1
Firmware Specifications 1
Firmware Upgrade 2
Firmware Downgrade 2
Hardware Supported 3
Matrix 4
Issues Resolved 21
Known Issues 82
Introduction
This document provides specific information for the Dell Networking
N4064/N4064F/N4032/N4032F/8100/N3048P/N3048/N3024P/N3024/N3024F/N2048P/N2048/N2024P/N2024 switches
firmware version 6.1.0.6
It is recommended that this release note be thoroughly reviewed prior to installing or upgrading of this product.
Global Support
For information regarding the latest available firmware, release note revisions, or additional assistance, please visit
support.dell.com.
Firmware Specifications
Firmware Version
Firmware Image Name Version Number Release Date
N4000v6.1.0.6.stk 6.1.0.6 July 2014
N3000_N2000v6.1.0.6.stk 6.1.0.6 July 2014
Dell Networking 8100 series switches can support both 5.x.x.x and 6.x.x.x firmware versions. Dell Networking N4000 Switches
support 6.0.0.8 or later firmware. Both Dell Networking 8100 and Dell Networking N4000 switches shares the same firmware
image version from 6.0.0.8 firmware release onwards (for example. N4000v6.1.0.6.stk). After upgrading Dell Networking 8100
switches to firmware version 6.0.0.8 or later, the system model ID will show as N4000 in CLI, Web UI and SNMP interfaces.
Dell Networking 8100 series switches can be stacked with Dell Networking N4000 switches. Dell Networking N4000 series
switches require firmware version 6.0.0.8 or later and cannot be downgraded to 5.x releases. If N4000 unit is to be deployed as a
member within a stack of 8100 switches, the entire stack will be required to run 6.0.0.8 or later firmware.
Administrators upgrading Dell Networking 8100 series switches from 5.x.x.x or 6.x.x.x versions of firmware MUST follow the
instructions documented in the Upgrading Dell Networking 8100 Series Switches from Version 5.x.x.x or 6.x.x.x to 6.1.0.6
Firmware procedure. It is strongly recommended that you save your current configuration when upgrading your firmware.
Failure to follow the procedures described in that document when upgrading from 5.x.x.x or 6.x.x.x firmware may result in an
inoperable switch!
Administrators upgrading Dell Networking N4000 series switches from 6.x.x.x versions of firmware MUST follow the
instructions documented in the Upgrading Dell Networking N4000 Series Switches from Version 6.x.x.x to 6.1.0.6 Firmware
procedure. It is strongly recommended that the current configuration be save to flash when upgrading the firmware. Failure to
follow the procedures described in that document when upgrading from 6.x.x.x firmware may result in an inoperable switch!
Administrators upgrading Dell Networking N3000 and N2000 switches from 6.x.x.x versions of firmware MUST follow the
instructions documented in the Upgrading Dell Networking N3000_N2000 Series Switches from Version 6.x.x.x to 6.1.0.6
Firmware procedure. It is strongly recommended that you save your current configuration when upgrading your firmware.
Failure to follow the procedures described in that document when upgrading from 6.x.x.x firmware may result in an inoperable
switch!
Firmware Downgrade
Downgrading from 6.1.0.6 to an earlier 5.x.x.x release is supported only on Dell Networking 8100 series switches. It is NOT
supported on Dell Networking N4000/N3000/N2000 switches. Migration of configuration information from a later release to an
earlier release is not supported. It is strongly recommended that the current configuration be save locally (i.e., not on the switch)
prior to downgrading the firmware. The existing configuration may or may not work with the earlier version of firmware,
therefore, it is best to be physically present at the switch site and to be prepared to access the switch over the serial port if
necessary when downgrading firmware.
Auto-downgrade of a stack is enabled by default. To avoid accidentally downgrading a stack, be sure to disable auto-downgrade
(CLI command: no boot auto-copy-sw allow-downgrade).
Dell Networking N4000/N3000/N2000 switches can only run firmware version 6.0.0.8 or later firmware (6.1.0.6). Dell
Networking 8100 series switches can run firmware versions 5.x.x.x or 6.x.x.x firmware. It is possible to stack N4000 switches
with 8100 switches. This means that mixed stacks of N4000 and 8100 switches must both run the same version of 6.x.x.x
firmware and cannot run 5.x.x.x firmware.
Hardware Supported
• Dell Networking N4064 Ethernet Switch
• Dell Networking N4064F Ethernet Switch
• Dell Networking N4032 Ethernet Switch
• Dell Networking N4032F Ethernet Switch
• Dell Networking 8100 Series Ethernet Switch
• Dell Networking N3048P Ethernet Switch
• Dell Networking N3048 Ethernet Switch
• Dell Networking N3024P Ethernet Switch
• Dell Networking N3024 Ethernet Switch
• Dell Networking N3024F Ethernet Switch
• Dell Networking N2048P Ethernet Switch
• Dell Networking N2048 Ethernet Switch
• Dell Networking N2024P Ethernet Switch
• Dell Networking N2024 Ethernet Switch
Feature/Switch Priority Data DOT1AG ETS MLAG RSPAN PBR Tiered Hot
Flow Center Authenti Swap
Control and cation Cards
DCBx
Dell Networking
N4000 Ethernet
Switch
Dell Networking
8100 Ethernet
Switch
Dell Networking
N3000 Ethernet
Switch
Dell Networking
N2000 Ethernet
Switch
Release 6.1.0.6
Release 6.1.0.1
MLAG
Remote SPAN
Policy Based Routing/Forwarding
Tiered Authentication
IPv4/IPv6 ACL Enhancements
Per Port Flow Control
Source Specific Multicast support
Load Statistics
Full Memory Core dump
Remote Packet Capture
Added support for LAG flap counters
Logging Enhancements
Enhanced Ping and Traceroute feature
Serial access to remote members in a stacking environment
Ability to enable or disable stack ports
Give option to encrypt TACACS and RADIUS keys
Ability to track stack path in the stacking environment
Support packet capture of CPU packets with Wireshark decode
Protect U-boot access with password
Release 5.1.4.5
Added storm control “action” support for broadcast and multicast streams
Added "show running-config interface <intf-id> all" command
Release 5.1.2.3
Release 5.1.1.7
Release 5.1.0.1
Release 5.0.0.4
Release 4.2.2.3
Release 4.2.1.3
Release 4.2.0.4
DCBx on M8024-k/8024/8024F
FIP Snooping Bridge on M8024-k/8024/8024F
Add EEE Support for the PC7000 10GBaseT Ports
GUI EEE Power Savings Charts
RP Failover Performance Improvement
Flexible Dynamic LAG Limits
CLI Help Usability Improvements
Ability to Show Static Route Entries
CMC XML Support
Stacking Over Ethernet Ports
Change Dell EqualLogic iSCSI Auto Detect to default
Add CLI Macro (Port Profile) for Dell Compellent Storage Equipment
Provide Dell EqualLogic DCBx TLV Auto Detect and Configuration on M8024-k/8024/8024F
Release 4.1.0.19
Release 4.1.0.6
• DHCPv6 relay
• DHCPv6 server
• IPv6 routing/forwarding
• OSPFv3
• IPv6 Neighbor Discovery
• Configured v6-over-v4 tunnels
• Automatic (6to4) tunnels
• IPv6 Multicast
Auto-Install
USB based auto-install is an easy way to quickly bring up a switch with a known configuration. Network based auto-
install is useful in rolling out a configuration or firmware update to a group of switches or in maintaining a central
repository of switch configurations and firmware where the switches always obtain their firmware and configuration
from a central server.
The following clarifications are helpful in understanding the processing steps in auto-install:
• Always power on the switch that is desired to be the stack master first
• Auto-install never proceeds if a startup-config file is present on the (master) switch
• USB auto-install is attempted first. Network auto-install only proceeds if USB auto-install fails.
• If there are multiple .setup files present on the USB flash device, the dellswitch.setup file is selected
• If a valid .setup file is not found on the USB flash device, the single .text file is used
• If multiple .text files are present, the dellswitch.text file is used.
Network based auto-install utilizes information obtained from a DHCP server. Refer to the documentation for a
discussion of the DHCP options used by Auto-Install.
Auto-install configuration files are executed as a script. For more details on Auto-Install, refer to the User’s Guide.
Blocked Destination
Rule Type Rule Purpose Ether Type
MAC Address
Blockcdp Used to block CDP N/A 0x2000
PDU’s
Blockvtp Used to block VTP N/A 0x2003
PDU;s
Blockdtp Used to block DTP N/A 0x2004
PDU’s
Blockudld Used to block UDLD N/A 0x0111
PDU’s
Blockpagp Used to block PAGP N/A 0x0104
PDU’s
Blocksstp Used to block SSTP N/A 0x010b
PDU’s
Blockall Used to block all defined 01:00.0C:CC:CC:C0 N/A
Protocol Filtering PDU’s
DHCP Server
Switches support a simple DHCP server capability for domains that do not wish to deploy a redundant DHCP address
assignment solution or who have need of a temporary solution while (re)deploying their DHCP server solution.
In configuring DHCP scopes, be aware that the DHCP pool address and netmask must exactly match a VLAN address
and netmask assignment for DHCP addresses to be served over that VLAN.
Only a single manual IP address can be assigned to a pool. The address must have a netmask of 32.
GMRP
The GARP Multicast Registration Protocol provides a mechanism that allows networking devices to dynamically
register (and de-register) Group membership information with the MAC networking devices attached to the same
segment, and for that information to be disseminated across all networking devices in the bridged LAN that support
Extended Filtering Services. Dell switches support GMRP as specified in IEEE 802.1Q 1998.
WRED
Weighted Random Early Drop is supported on Dell Networking switches. Refer to the table at the beginning of this
section for further information. CoS queue configuration involves the following hardware port queue configuration
parameters:
Tail drop and WRED parameters are specified individually for each supported drop precedence level.
In addition, the following are specified on a per-interface basis:
• queue management type: tail drop vs. WRED (only if per-queue configuration is not supported)
• WRED decay exponent
Switch administrators should remember to configure ingress ports as trusted or un-trusted. By default ingress ports
trust dot1p values.
MVR does not require that either source or receiver ports utilize VLAN tagging.
Network planners are reminded that multicast groups in the 224.0.0.x range are reserved for multicast control plane
traffic. Network planners should select multicast groups in another range for normal multicast traffic, e.g. 239.0.1.x
iSCSI Optimization
iSCSI Optimization automatically configures array facing ports for use with the iSCSI protocol and tracks iSCSI
sessions on the t 7000 and 8000 Series switches as well as the PCM6348. Dell EqualLogic arrays are automatically
detected and configuration of Dell EqualLogic connected ports is performed automatically. Server facing ports are not
detected must be configured manually.
Administrators are advised that the configuration performed by enabling iSCSI optimization is not automatically
reversed on disabling the feature. The administrator will need to manually remove the configuration settings when
migrating Dell EqualLogic servers or iSCSI initiator ports to other ports or switches.
Detection of Dell EqualLogic arrays is keyed on receipt of the mandatory System Description TLV in the LLDP
packet. Disabling LLDP will effectively disable Dell EqualLogic array detection.
Dell EqualLogic arrays are required to be upgraded to firmware 5.0.2 or later in order to use the iSCSI Optimization
feature.
LLDP
Administrators should ensure that LLDP-MED is enabled in order to operate EEE. Disabling LLDP or LLDP-MED
will effectively disable EEE, IEEE 802.3at PoE+ high power negotiation and Dell EqualLogic array detection in the
iSCSI Optimization feature.
Email Alerting
Email alerting allows administrators to be notified via email regarding system events. Multiple email addresses can be
configured. The system will attempt to resolve mail servers specified with a FQDN immediately and, if successful,
store the mail-server as an IP address. If a new IP address is subsequently assigned to the mail server, the operator will
need to re-assign the email address on the switch.
Only the Mail User Agent functionality of RFC 4409 is implemented. Dell switches do not implement SMTP server
functionality.
Administrators are cautioned against enabling monitor mode in a deployed network where 802.1X users may gain
access to sensitive network resources.
Strong Passwords
The strong passwords feature allows administrators to specify that local switch passwords meet certain characteristics
considered to enhance network security.
Administrators are advised that the minimum character classes configuration must be enabled (value equal to 1 or
greater) along with enabling the strong password feature before the other minimum character class configurations are
enforced. These character class configurations are:
• Minimum number of uppercase letters.
• Minimum number of lowercase letters.
• Minimum number of numeric characters.
• Minimum number of special characters
The password strength restrictions do not apply to users configured for the internal authentication server.
Switch Auditing
Switch auditing enhances network security by logging sensitive administrative actions. Switch auditing logs the
following actions:
• Successful login
• Unsuccessful attempt to login
DNS Client
Dell switches support name resolution via an embedded DNS client. When a DNS name is specified, it is attempted to
be resolved against the configured DNS servers immediately. Dell switches will store the resolved IP address. If the IP
address of the host resolved via DNS changes, the administrator will need to update the configured IP address, either
via DNS or manually.
If the switch is configured to obtain an address via DHCP, DNS server information received from the DHCP server is
used to populate the DNS client configuration.
Release 6.1.0.6
Release 6.1.0.1
Modified DVLAN tunnel UI to enable QinQ tunneling on customer edge (CE) interfaces.
Release 6.0.1.3
PoE commands for N3000/N2000 PoE switches with PoE controller.
Modified CLI to configure system wide MTU for all interfaces for all frame types.
Enhanced IP route commands to display all connected and configured routes under one command.
Release 6.0.0.8
Enhanced multicast commands to align with Industry Standard CLI
Increased maximum number of iSCSI Sessions to 252
Increased maximum number of units stackable to 12 for the N4000 and 8100
Increased maximum number of VLAN’s supported to 4k
Increased maximum number of static routes supported from 512 to 1024
Release 5.1.3.7
Release 5.1.2.3
Release 5.1.1.7
Release 5.1.0.1
IGMP Snooping
IGMP snooping is enabled by default.
Traffic addressed to reserved multicast IP addresses is flooded.
Unregistered multicast is flooded to all ports in the VLAN until a multicast router port is identified.
Once mrouter port is identified the traffic is forwarded to mrouter port and listener ports only.
PIMSM
PIMSM Rendezvous Points can be positioned anywhere in the network, not just as the first hop router. Although
multiple Rendezvous Points can be configured, only one Rendezvous Point is active at any time.
Auto-Configuration
Auto-configuration recognizes any of the assigned internal switch’s MAC addresses when present in an auto-
configuration file. The switch re-writes the file to use the base MAC address of the switch.
Dot1x Clients
The maximum number of 802.1x clients (i.e. supplicants) that can be authenticated per port is increased to 24. This
increase does not include a corresponding increase in the maximum number of 802.1x clients that are supported on an
entire switch or stack.
Release 5.0.1.3
Release 5.0.0.4
Release 4.2.2.3
Release 4.2.1.3
Release 4.2.0.4
LAG Limits
Ports can be formed into LAGs in a more flexible manner. The system supports up to 128 total LAGs. Up to 144 ports
can be assigned to dynamic LAGs. Up to 72 LAGs can be configured as dynamic. A LAG may contain up to 8 ports.
The M8024 supports 12 total LAGs (static or dynamic) with up to 24 ports assigned to dynamic LAGs.
Release 4.1.1.9
Release 4.1.0.19
Release 4.1.0.6
Authentication
The enable and line authentication methods will no longer perform authentication if a password for the method is not
configured. Previously, these methods would always succeed if no password was configured. To achieve the same
functionality, add the “none” method to the list after enable or line method.
Port level configuration for a port that is configured in a dynamic LAG is disregarded. Remove the port from the LAG
to restore use of the port level configuration.
Ports in a static LAG begin forwarding on link up. Ports in a static LAG disregard port level configuration. Configure
static LAG functions on the static LAG interface.
The Dell switches implements the 802.1Q-2005 standard which builds on 802.1D-2004. 802.1D-2004 incorporates the
802.1t, 802.1w and 802.1s revisions. Port path costs are calculated based on the interface speed as shown below and
are dynamically recalculated on interface activation and link speed changes.
External Port Path Cost values (Port Path Cost in 17.14 of 802.1D-2004) are applicable in STP, RSTP, and MST modes
(Ref. Table 17-3 802.1D-2004). Use the spanning-tree cost command in interface mode to set the external port path
cost.
Internal Port Path Cost values are specific to MST mode only (Ref. Table 13-3 802.1Q-2005). Use the spanning-tree
mst <instance> cost command in interface mode to set the internal port path cost.
Captive Portal
Captive portal has been extended to support user logout and localization.
802.1Q
The following changes have been made to the operation of VLANs.
VLAN Membership:
It is now possible to configure the native VLAN on a port in trunk mode. Trunk mode ports will accept untagged
frames but will always transmit tagged frames except for the native VLAN which will always transmit untagged
frames. It is also possible to configure a trunk port to drop untagged frames by filtering on the native VLAN, e.g. by
using the switchport trunk allowed vlan remove command.
A trunk port always has a native VLAN (default is VLAN 1), so the default behavior is that untagged packets are
treated as if they are tagged in VLAN 1. To drop untagged packets, configure switchport trunk allowed vlan remove
<vlan> which has the side effect of dropping tagged packets in that VLAN.
When switching between switchport modes (access, trunk, and general), the switchport configuration applicable to the
selected mode is maintained. This means that when switching from one mode to another and back, the port will have
the same configuration as it had in the original mode. Only the configuration applicable to the selected mode is active
on the port.
VRRP
The following enhancements have been made to the operation of VRRP to increase usability and robustness of
operation in the network:
Preemption Delay:
Per the VRRP RFC 3768, when preemption is enabled, the backup router discards advertisements until the master
down-timer fires. When the preemption delay timer is set to a non-zero value and the backup switch receives a PDU
with a lower priority from the master, then backup switch waits for the preemption delay value before advertising itself
as the master.
In VRRP, all participating routers should be configured with coherent advertisement timer interval values. The
operator can now enable timer learning which causes a backup router to learn the master advertisement interval and
change its master down interval accordingly.
RFC 3768 specifies that a router may only accept IP packets sent to the virtual router’s IP address if the router is the
address owner (master). In practice, this restriction makes it more difficult to troubleshoot network connectivity
problems.
This capability adds support for responding to pings by the VRRP master, but does not allow the VRRP Master to
accept other types of packets. A configuration option controls whether the router responds to Echo Requests sent to a
VRRP IP address. When enabled, the VRRP master responds to both fragmented and un-fragmented ICMP Echo
Request packets. The VRRP master responds to Echo Requests sent to the virtual router’s primary address or any of its
secondary addresses. When the VRRP master responds with an Echo Reply, the source IPv4 address is the VRRP
address and source MAC address is the virtual router’s MAC address. The VRRP master does not respond to pings
sent from the master.
Members of the virtual router who are in backup state discard ping packets destined to VRRP addresses, just as they
discard any Ethernet frame sent to a VRRP MAC address.
DHCP Relay
The following enhancements have been made to the operation of DHCP Relay to bring the implementation into
conformance with RFC 4649:
RFC 4649 specifies the IANA assignment of the Relay Circuit Id sub-option and Remote Id option. The
implementation has been changed so that the administrator can no longer assign a numerical value to these TLVs as the
IANA assigned number is now used. The administrator can still enable or disable the insertion of these TLVs in
messages sent to the DHCP server.
The operator has the ability to enable DHCP Relay Information Options both globally and on a physical interface. The
interface configuration overrides the global configuration for the selected interface.
When DHCP Option-82 insertion is enabled for a relay agent, the server should echo received Option 82 unaltered back
toward the client. The relay agent is required to strip Option 82 information before relaying the BOOTPREPLY to the
DHCP client. When enabled, the Relay Information Option Check will cause the BOOTPREPLY packet to be dropped
if invalid sub-options are echoed by the DHCP server.
L2 Address Table
The administrator can disable MAC address table aging.
The administrator can configure static forwarding of a MAC address on a specific VLAN.
NOTE: By default, multicast frames are flooded by the switch. Utilize the
mac address-table multicast filtering command to disable flooding of
multicast frames.
LLDP Enhancements
EEE Support:
Support is added to process/communicate the EEE TLV to partner devices. The EEE TLV is an 802.3 organizationally
specific TLV used to report on the EEE Data Link Layer capabilities.
LLDP-MED Support:
LLDP-MED uses LLDP’s organizationally specific TLV extensions and defines new TLVs which make it easier to
deploy VoIP in a wired or wireless LAN/MAN environment. The LLDP implementation supports the following TLVs:
Before assigning the port to RADIUS assigned VLAN, dot1x checks if the given VLAN is in the VLAN database or
not. If the assigned VLAN is not in the VLAN database and dynamic VLAN assignment is enabled, a VLAN is
created on the port over which the client is authenticated. Each time a client is de-authenticated on an interface with a
particular VLAN, a check verifies if there any other interface which a VLAN member is. If there is no interface as a
member, the VLAN is deleted. This behavior is same for MAC based authentication as well.
Usability Enhancements
In the output of the show running-config command, the slot and member configuration is commented with the
switch/slot type in human comprehensible form.
When in interface config mode, CLI users can navigate to a different interface by entering the appropriate interface
command without leaving interface config mode.
CLI users can log out of the switch using the exit command (exit is an alias for quit).
The CLI Reference Guide is updated with acceptable character sets and maximum lengths for string parameters to
commands.
Management ACLs permit specification of service any as shorthand for enabling all services access for in-band
management.
VLANs may be administratively assigned to MSTIs in excess of the switch physical limits and without regard to
whether the VLAN is actually configured. Frames are only forwarded on VLANs assigned to interfaces.
Administrators can re-enter SYSLOG server config mode for a particular SYSLOG server entry without requiring the
deletion and re-creation of the entry.
Administrators can configure the web timeout by navigating to: System -> Management Security -> Telnet Server ->
Telnet Session Timeout.
Simple Mode
The Dell M8024-k is the only modular switch that defaults to the simple mode of operation. Simple mode contains a
restricted set of commands suitable for control of a port aggregation device that can be deployed in a network without
requiring updates to the network by a network administrator. Users needing switch capabilities which require the
network administrator to modify the network configuration can exit simple mode using the no mode simple command.
AAA Authentication
In prior releases, more than one method could be specified for dot1x authentication even though only the first method
was attempted. The CLI and Web now only accept a single method for dot1x authentication.
Issues Resolved
The following issues from previous releases have been corrected. The issues listed here may have been discovered on any of the
switches listed on the title page.
Release 6.1.0.6
Summary User Impact Resolution Affected
Platforms
Issues powering up POE When dot13af and legacy mode is enabled and Fixed high port powering N2xxxP/N3xxxP
devices on certain switch the first 12/24 switch ports are in error status, issue by updating the PoE
port interfaces. the last 12/24 ports are stay off. controller firmware version
to 263_75.
Release 6.1.0.1
Summary User Impact Resolution Affected
Platforms
Switch fails to load If user makes changes to configuration, saves Startup-configuration file is N2xxx/N3xxx
startup-configuration configuration to startup-configuration file and saved immediately when
after hard power cycle then within a short period of time (60 seconds copy command is issued and
or so depending on configuration file size) console prompt does not
removes power from the system, the startup- return until save is complete.
configuration file will be empty and
configuration will be lost.
Multicast traffic loss at Traffic loss for few groups at random interval Fixed the timing issue where All 6.1.0
irregular interval for two of time the expiry is processed supported
group ranges before the timer is updated. platforms
Auto-negotiation Combo ports on a stack member will not link Error codes are handled All 6.1.0
capabilities of combo up after rebooting the member in a stack. correctly while getting auto- supported
ports were getting reset negotiation capabilities platforms
to '0'
Need support for dot1q When user configures dvlan tunnel mode on a When user configures dot1q All 6.1.0
tunnel mode port, that port gets configured as service tunnel mode on an interface, supported
configuration per port provider port and all other ports would only that interface would be platforms
and per port ether type become customer ports set as customer port
configuration
DOT3AD helper sending Dynamic LAG will be up on partner, even stop sending LACP PDUs All 6.1.0
LACP PDUs even though it does not exist in DUT. for LAG interface upon supported
though LAG is down receipt of detach event platforms
"Login time" stamp does “show users login-history” doesn't show the Modify CLI to convert the All 6.1.0
not match the switch correct login time given raw time to UTC supported
clock platforms
802.1x authentications Authentication fails for 802.1x users using EAP packet length N2xxx/N3xxx
fails for EAP type EAP type PEAP computation corrected and
PEAP(protected EAP) on used only for first fragment
N2xxx/N3xxx platform while inserting the AVP's
Fiber Combo Port LED Wrong indication of the LED reporting port Fixed code such that LED N3024F
on partner switch reports down. microprocessor to react to
'DOWN' after an initiate linkscan callback only for
Failover on a stack ports that it manages.
Access list name is If the Access list name has a ‘-‘ character the Fixed the java script on web All 6.1.0
getting truncated in the name is not displayed properly page supported
web interface platforms
DCPDP packets are not MLAG Peer Detection continuously flaps Fixed the logic to send All 6.1.0
transmitted every one DCPDP packet every one supported
second second platforms
Web interface freezes VLAN membership web page cannot be Fixed the java script on web N4032/N4032F
when trying to view accessed. After accessing the VLAN page
VLAN membership membership web page, the browser will hang
and the browser must be restarted to access the
web interface again
VoIP VLAN reply not VOIP phones won't receive Voice VLAN Corrected Voice VLAN All 6.1.0
Release 6.0.1.3
Traffic loss due to IGMP join expiry for Periodic multicast packet loss Prioritizing the PIM All 6.0.1
some of the groups over lag when active lag port is on a join/prune messages as they supported
member unit were dropped when bursts of platforms
messages were received
IPMC deletes fail which can cause During failovers, when ports Enhanced the lookup and All 6.0.1
subsequent IPMC inserts to also fail. are down a condition might delete procedures. supported
cause subsequent IPMC inserts platforms
to also fail
MAC address learning fails after There will be traffic loss if the Primary to send proper STP All 6.0.1
secondary MLAG Reboot on setup port on which the STP status is updates to secondary. supported
running MSTP not updated properly is on platforms
traffic path
802.1p priority value discarded & reset Priority value in the vlan tag Fixed the snooping N3000/N2000
to default value for ICMPv6 packets gets reset to default value by application to retain the platforms
snooping application priority
Failure to change the port-channel Port channel mode changes MLAG port databases All 6.0.1
mode on MLAG (primary/secondary) from dynamic/static may fail handling is corrected supported
device or port state may move to platforms
discarding.
On stack configured with more than 2 There may not be traffic loss Proper checks on ether types All 6.0.1
units, the PBR traffic fails to fall back but the policy is not applied. for mac acl and ip acls. supported
to immediate next-hop after initiating platforms
failover
LAG membership detail page fails to All the needed information is Fixed the javascript to N4000/PC-81xx
display configured max 126 Dynamic not displayed on the page. properly handle the XML switches
LAGs tags
Fixed Speed 100 does not work on Link will not come up Corrected the MDIX setting for All platforms that
combo ports operationally. combo ports support combo
ports
Failure to revert to port default speed Clear config should clear and Order of the interface state All 6.0.1
after clear configuration. revert to defaults. checks corrected supported
platforms
Stack port numbering in software was Mismatch exists between the unit and port data base reworked N3000 platforms
not consistent with physical numbering physical numbering and ports according to HW spec updates
on the switch displayed in CLI.
H323 protocol functionality is not Voice call clarity is poor if both data Update code to install hardware All 6.0
working when you have data and and voice data are going through the rules properly supported
voice going through the same link same link platforms
Switch reports PSU/FAN failure Switch reports PSU/FAN failure Raise an error only if four N40xx
because of under-Voltage Input because of under-Voltage Input consecutive read cycles indicate series only
power power that there is an under voltage
input power.
Ping to VRRP master IP would fail Ping to VRRP master IP fails. When it transitions to VRRP All 6.0
when there is an unresolved data Master, the Virtual IP and Virtual supported
traffic flooding the CPU MAC addresses need to be added platforms
as a local host entry to the
hardware. These results in
prioritizing the packets coming to
CPU destined to VRIP.
Incorrect statistics displayed under "No of email Failures so far" in Added a check to communicate All 6.0
"show logging email statistics" command "show logging email with the logging email server only supported
command statistics" is incrementing even if if we have any log messages to be platforms
there are no failures. sent.
The following fields in the output User thinks that the packets are Rename the fields so that it All 6.0
of "show interface counters getting dropped at the egress reflects the counter values against supported
<interface-id>" are misleading interface correct fields there by enhancing platforms
when you have MTU set to non- user experience.
default value.
a) Received Oversize Packets
b) Transmitted Oversize Packets
Some special Characters are not Only alphanumeric characters can be Enhanced validation to accept all All 6.0
allowed for TACACS key while used for TACACS keys while printable characters from web supported
adding a TACACS server in WEB. adding a TACACS server from web interface. platforms
interface.
Error message is displayed, when Failed to configure SNMP Delete SNMP community related All 6.0
configuring SNMP community community through web using entries and target tags so that supported
through web using chrome browser chrome browser, if addition of additional of SNMP community platforms
SNMP community is followed by goes through.
deletion of SNMP community
Switch is seeing 2 query messages No functional impact, but switch Updated switch settings so that All 6.0
even though partner has sent only sees two messages for every one only one copy is sent to CPU of supported
one. This happens only if the message sent from partner, if the the stack master platforms
receiving interface is on the stack receiving port is on the stack
member member
When maximum neighbor capacity Unexpected routing behavior when Add validation such that no new All 6.0
is reached, it's picking up the old maximum neighbor capacity is neighbors are entertained if the supported
entry randomly and replacing it. reached. router maximum neighbor platforms
capacity is reached.
IPMapForwardingTask and Random crashes are occurring in the Resolved VRRP semaphore All 6.0
Interrupt Thread crashing switch IPMapForwardingTask deadlock. supported
platforms
VRRP causing switch crash and Same issue as: Resolved VRRP semaphore All 6.0
loss of management IPMapForwardingTask and Interrupt deadlock. supported
Thread crashing switch platforms
Stack member unit crash with task Random crashes are occurring in the Corrected failover issue with All 6.0
"hapiMcAsyncTask" "hapiMcAsyncTask" multicast routes supported
platforms
stack member reboots with task Random crashes are occurring in the Corrected problem when all RPC All 6.0
bcmRPC bcmRPC task. buffers are exhausted. supported
platforms
GUI showing medium temp, while GUI showing medium temp, while Corrected temperature value issue All 6.0
the CLI was showing good temp the CLI was showing good temp when displaying temperature in supported
the GUI. platforms
Release 5.1.4.5
BSR action Storm control is hitting threshold early Corrected storm control PC8132
shutdown compared to the configured threshold value. counter issue PC8132F
functionality is PC8164
not working. PC8164F
“devshell “devshell cpldTest” command reports fan Corrected fan status query. PC8024
cpldTest” errors which are invalid errors because the PC8024F
command incorrect bits were tested.
reports a fan
control error
show tech- The incorrect pagination by "show arp" Corrected pagination issue All Platforms
support output is overwrites other portions of the show tech-
incomplete and support output
overwritten by
"show arp"
entries.
Error reported First self-signed certificate is still in process Corrected error message to All Platforms
when generating of generating when the second certificate is indicate the proper reason why
2nd self-signed requested. the second certificate failed.
certificate from
CLI
storm control Added storm control action support for Added storm control action All Platforms
action support broadcast and multicast streams support for broadcast and
for broadcast multicast streams
and multicast
streams
Storm-control Storm-control as documented in the CLI Implementation of storm- All Platforms
and user configuration guide is fully control includes multicast,
implemented. Broadcast and Unicast packets.
Show mac Occasionally the switch will crash if "show Corrected buffer overflow All Platforms
address-table mac-address-table" command is issued issue.
command is
crashing the
switch
SNTP KoD If a switch receives a KoD packet (stratum Corrected back-off time issue All Platforms
packet stops 0 and ref.ID = INIT) from an NTP server
time which just reloaded and is synchronizing
synchronization time with higher strata, then the switch,
contrary to RFC 4330, stops synchronizing
to that server if no other server is
configured.
ICMP Redirect Applying "no ip redirects" command Corrected global command All Platforms
status of VLAN globally does NOT have any impact on sync issue.
is enabled when VLAN interfaces
"no ip redirects"
applied globally
Error reported Certificate larger than 1024 would generate Corrected a size issue when All Platforms
when importing and error. pasting a certificate in the Web
a certificate via UI.
GUI
Release 5.1.3.7
Stack member Random switch crashes are occurring in the Corrected problem when all All Platforms
reboots with bcmRPC task. RPC buffers are exhausted.
task bcmRPC
WebUI shows WebUI is showing medium temp, while the Corrected temperature value All Platforms
the temp status CLI is showing good temp issue when displaying
as medium, temperature in the WebUI.
while the CLI
status shows
good temp
MIB Walk on Two different PowerConnect modular Corrected data mismatch issue. PCM8024-k
blade switches switches should return the same value for PCM6348
not returning the hardware health MIB.
same results
After failover, After master is rebooted and stack failover Corrected VLAN association PC70XX
VLAN is getting to standby completes, the VLAN is getting and ports state mismatch
associated with associated with physical interface instead of between warn start and cold
physical just the port channel interface. boot.
interface.
After failover, After master is rebooted and stack failover Corrected ports spanning-tree PC70XX
the spanning- to standby completes, the spanning-tree state transition between warn
tree status of the state of the physical interface is transitioned start and cold boot.
physical from DSC state to FWD state.
interface is
transitioned
from discarding
to forwarding
SSH related SSH session to switch will occasionally Corrected memory allocation All Platforms
switch crash result in crash if SSHv1 with public key issue.
authentication is used.
OpenSSH CVE-2012-0814 vulnerability addresses: Applied OpenSSH All Platforms
Vulnerability Debug information is sent to SSH clients recommended fix.
issue: CVE- and this debug information includes private
2012-0814 information
Using WebUI to In WebUI, setting the fields "Dynamic Corrected WebUI to accurately PC70XX
set fields VLAN creation" and "GVRP Registration" reflect operation requested. PC81XX
Dynamic VLAN to “enable” actually sets them to
creation and “forbidden”.
GVRP
Registration
issue
Error with Temperature status does not transition Corrected temperature status PCM6220
temperature through “Medium” on the way to “High” reporting for medium state. PCM6348
status reporting
PCM8024
PCM8024-k
dot1sBpduRecei Log message is being thrown for an Corrected display of error All Platforms
ve(): Discarding incorrect state. message for invalid state.
the BPDU,
cannot get
buffer from buff
pool log
message
One switch Upon reboot from the CLI a switch Corrected timing issue with All Platforms
intermittently intermittently does not rejoin the stack. communications between
doesn't join a master and slave units.
stack after
reboot from CLI
Release 5.1.2.3
VLAN ACL blocks traffic VLAN policy was occasionally Corrected problem that allowed All 5.1 supported
across stack members being applied on stack ports. VLAN ACLs to be applied to platforms
stack links.
Stack master reboot forces Stack master reboot forces the Corrected problem detecting All 5.1 supported
the combo ports of the combo ports of the standby unit active copper or fiber platforms
standby unit to Duplex Full to Duplex Full mode connection.
mode
VoIP VLAN reply not being VOIP phones won't receive Corrected Voice VLAN All 5.1 supported
sent via CDP\ISDP Voice VLAN configuration from indexing problem. platforms
switch if there is an ISDP entry
on a port ID which is one port
less from VOIP phone connected
port.
Stack routing issues Whenever a reload is done on a Corrected trunk port All 5.1 supported
slave unit, the trunk fails to synchronization problem. platforms
synchronize with the newly
added unit causing routing to
that trunk to fail.
MS NLB cluster not NLB cluster not reachable after Corrected trunk ID update All 5.1 supported
reachable after rebooting the rebooting the stack due to trunk problem. platforms
stack ID assigned to static MAC
address.
SSLT: The ssltask consumes too much Corrected sslt task socket write All 5.1 supported
SSL_ERROR_SYSCALL CPU when try to open web page problem. platforms
on https web GUI login, causing the UI to hang.
switch hangs.
M8024-K switch can cause Temp range difference between Modified fan speed change PCM8024-K
high fan speed with CMC M8024k and CMC with FW 4.2 parameters and added new
4.2 and above causing chassis fan temperature handling logic.
speed stuck at 100%
All entries in IGMP Group entries in IGMP snooping Corrected timer rollover All 5.1 supported
snooping are added and are added and deleted problem that happens every platforms
deleted immediately in a immediately in a specific time 49.71 days
specific time for 5 minutes for 5 minutes
Manager is rebooted while During multicast traffic flow, on Corrected data copy problem PC8132
doing clear config due to initiating a NSF failover, the when check pointing MFC PC8132F
crash in mcastMapTask. unit acting as standby crashes data. PC8164
and there will be traffic loss. PC8164F
Release 5.1.0.1
Cannot apply ACL on User needed to use CLI Fixed the issue to be able to All 5.0 supported
VLAN 'out bound' apply in both directions from platforms
direction from GUI the web
Default VLAN cannot be Cannot change VLAN member Fixed VLAN membership web All 5.0 supported
made static from GUI ports settings page platforms
Incorrect SFP interface log The wrong port may get Calculate the correct internal Platforms that support
messages on stack reported in the trap notification interface number XFP, SFP and SFP+
transceiver modules
SNMP management IP command is missing in the CLI Added CLI command support All 5.0 supported
address can only be set in Simple Mode platforms
from WebUI and lost after
reboot.
Simple mode In-band IP "ip address vlan" command Put "ip address vlan" after PCM6220
address missing after disappears from the running- "port-aggregator group" PCM6348
reboot. config after reboot commands in the text config PCM8024
PCM8024-k
ARP entries are purged for L3 egress objects are not Use the SDK init function to All 5.0 supported
unknown reason programmed correctly resulting set defaults for egress object. platforms
in incorrect L3 forwarding.
OOB Static IP unreachable After failover stack loses static Proper checks prevent using All platforms that support
after stack failover IP address configured on OOB the previous DHCP mode. the OOB interface
interface.
http[s] authentication HTTPS authentication through parse RADIUS server response All 5.0 supported
against RADIUS only RADIUS grants only read-only properly platforms
allows privilege level 1 access.
access
Switch service tag not Switch service tag not displayed Added retry to get the Service M8024-k, M8024, M6348
displayed by “show system with “show system id” Tag value
id” command command
CLI commands are not Enabling password recovery will Fixed the issue to enable All 5.0 supported
authorized after Password not allow the user to run CLI commands from serial console platforms
Recovery commands on the serial console. also
LINK UP on all interfaces Links are UP and flapping Changed the CPLD and reset PC8024 and PC81xx
during POST, during power reset and reloads. logic
FCoE -M8024-k setting In the CEE mode there is no Check if any weight is Platforms running DCBX
TSA map to link strict and way to specify the TSA mode in configured for the TCGs, if so and including ETS
assigning bandwidth the ETS TLV set the mode to ETS.
allocation to TC
Switch GUI forcing 100Mb Switch GUI set all external ports Corrected port speed M6348
speed on External ports to 100Mb speed when cloning processing from WEB
when cloning port port configurations.
configurations
M6348/General port GUI Vlan membership information Javascript fixed to pick correct M6348
issue on web is displayed and applied enum values
incorrectly
M6348 - service tag not Service tag shows up as none on Synchronization issue fixed to M6348
displayed in GUI GUI retry and get the tag
information
email addresses with A valid email id with an Underscore is now considered All 5.0 supported
underscore "_" are rejected underscore cannot be used valid character platforms
phone port configuration The macro never returns and Fixed the issue and return error All 5.0 supported
macro incomplete appears to hang platforms
Release 5.0.1.3
Release 5.0.0.4
2. Incorrect
error message is
displayed when
not configured
Receiver index
is applied
to interface on
"System-
>sFlow->Poll
Configuration"
page.
Release 4.2.2.3
SNMP Port When setting VLAN un-tagging for a Corrected the port un-tagging All 4.2 supported
tag/untag issue specific port using the set. platforms
dot1qVlanStaticUntaggedPorts object,
All the other ports are automatically added
to that particular VLAN as tagged.
DNS client error Upgrade of 3.1.4.5 to 4.1.0.6 DNS client Corrected service port link All 4.2 supported
in logs and error “osapiSocketRecvFrom returned error status during upgrade. platforms
switch locks up “ in logs and switch locks up and needs to
and needs to be be rebooted.
rebooted.
Terminal Length Terminal length is not setting per-session is Corrected a problem with All 4.2 supported
setting not an enhancement scheduled for the next terminal scrolling. platforms
working as in release.
4.1
Trunk port Trunk port multiple VLAN assignment Corrected command parsing All 4.2 supported
multiple vlan doesn't work properly after reboot. problem. platforms
assignment
doesn't work
properly after
reboot
FIP snooping FIP snooping session is not getting Corrected FIP snooping All 4.2 supported
session is not established after script apply. command problem. platforms
getting
established after
script apply.
"ip http secure- ip http secure-server command not getting Corrected command parsing All 4.2 supported
server" applied when we migrate from 4.1.0.19 to problem. platforms
command not 4.2.1.3 release
getting migrated
from 4.1.0.19
build to 4.2.1.3
build.
Data loop in A data loop occurs in the port-aggregator if Corrected the VLAN creation PCM6220
Simple mode a new VLAN is added to an interface. error. PCM6348
when adding
VLAN PCM8024
PCM8024-k
Release 4.2.1.3
cpCaptivePortal The description of the Corrected the description in All 4.2 supported
WebLangCode. cpCaptivePortalConfigWebLangCode the fastpath_captive_portal.mx platforms
1.1 displays en object doesn't correspond to the values it file
when mib says returns.
only supported
value active (1)
LLDP When Port-Description is set as no Corrected the default Port- All 4.2 supported
Assignment of description in LLDP port configuration, the Description. platforms
port ID for Port- TLV should contain the Port Interface name
Description as the port description by default instead of
TLV 0.
The CLI shows The "show interface advanced firmware" Removed the Type column All 4.2 supported
incorrect media shows incorrect information under "Type" which was not valid. platforms
type 10GBASE- column.
T for fiber ports
Can't assign a Config migration for the "name <vlan Corrected the config migration All 4.2 supported
name to a name>" command was not correct. for the "name <vlan name>" platforms
VLAN command.
No default route "Show ip route" commands will not display Corrected the display of the All 4.2 supported
or static route even though there were routes is in the "Show ip route" command. platforms
showing in ip router(static routes, ospf routes) for
route table terminal length 0.
CLI command CLI command "show dot1x users" is Corrected the command tree All 4.2 supported
"show dot1x missing for the "show dot1x users" platforms
users" is missing command.
Missing port Changing VLAN configuration for general Corrected the issue. All 4.2 supported
membership mode affected trunk mode configuration platforms
from SNMP and there from the port membership
(dot1qVlanStati returned via SNMP.
cUntaggedPorts
and
dot1qVlanStatic
EgressPorts)
The VRPP track The VRRP track port priority in the running Corrected the retrieval of the All 4.2 supported
port priority config is retrieving the operational value configured value platforms
changes in the instead of the configured value.
running config
Firmware won't The hyphen is part of the allowed characters Added the hyphen to the All 4.2 supported
allow domain available for the email address. allowed characters for email platforms
names with addresses.
hyphen "-" in
logging email
Continuous log POE log message comes up during power Removed unwanted message. PC7024P/PC7048P
message at up sometimes.
default settings
DNS client error The meaning of the DNS error message: Corrected the text of the All 4.2 supported
“DNS Client: osapiSocketRecvFrom message. platforms
returned error for addr 0x1214BCA8” is
unclear.
VRRP Ping to a remote host will not work if Corrected a VRRP All 4.2 supported
Intermittent switch acts as VRRP master communication issue. platforms
Connectivity
Issues
VLAN VLAN membership port names are not Corrected the port numbers All 4.2 supported
membership consistent. displayed in the GUI. platforms
port names not
consistent in
GUI
Radius crash Sometimes switch crashes when receiving Corrected the crash. All 4.2 supported
of Radius packets platforms
In a Stack, the CLI output for command "show system Corrected the pagination issue. All 4.2 supported
"show system temperature" is corrupted when platforms
temperature" pagination is used because the stack
CLI command displays much more data.
breaks CLI
QOS on port There is no way to see the match packet Command "show policy-map All 4.2 supported
channel counts of a policy-map on a port-channel. interface port-channel <port- platforms
channel number>" was added.
Dropped VLAN Customer is really not able to use this Corrected by not ignoring the All 4.2 supported
frames are counter to monitor their network outage dropped VLAN frames in the platforms
included in activity. Discards counter
Discards
counters.
PC7048 Combo Combo ports are randomly not transmitting Corrected by adding a property PC70xx
ports are not traffic, but receiving frames when media to bypass the lane initialization
passing traffic. type preference set as SFP when media-type preferences
is set.
Order of The "show running-config" command Corrected the order of running- All 4.2 supported
switchport shows the detailed switchport configuration configuration output. platforms
commands in before the switchport mode. This caused
running-config problems with some scripts.
changed
Release 4.2.0.4
The copper auto The copper ports 1-24 fail on 8024 to 8024 copper ports negotiate to PC8024
negotiation negotiate at 100Mb FD. 100M FD.
process fails at
100mb FD and
fails to link up
clock summer- Time change offset is applied early. Day of month calculation has All 4.2 supported
time recurring been corrected. platforms
EU offset 60
zone "GMT" not
offsetting the
time by 60
minutes
Upgrades to The wizard in 4.1.0.9 fails to create any or Issue with switch upgrade has All 4.2 supported
4.1.0.9 are very few interfaces and there was no config been resolved. platforms
causing network for any or very few of the ports, thus, the ip,
outages. The ICMP traffic was not working between
wizard from ports as well.
4.1.0.9 fails to
setup interfaces
PC6220M GUI The issue using CLI stack ports shows up Web shows stack ports up if All 4.2 supported
shows stack- and counters shows no transfer rate but GUI they are up platforms
ports down but shows stack ports down.
CLI does not. In
previous version
issue didn't exist
M6220 - Customer has multiple M6220 switches, Ports are now checked to All 4.2 supported
Routing fails on and as part of a network change they ensure they are not part of platforms
VLAN wanted to remove a VLAN routing interface other routing VLANs before
that was no longer in use. When they clearing the ARP policy on the
removed the IP address from this VLAN, port.
they lost routing across the entire switch.
MIB walk SNMP MIB walk crashes switch. A large array is allocated All 4.2 supported
crashes switch statically instead of on the platforms
stack.
Web UI not Binding an IP ACL as out bound to an Use of the direction object has All 4.2 supported
generating error interface, via Web UI, does not generate an been corrected. platforms
for out bound error message. Furthermore, the config
ACL & applies gets applied to the interface as an inbound
the config. ACL. When the same action is done via
CLI, an error message is generated and the
config is not applied.
Auto-neg option Auto-neg is an option in the port Auto-negotiation selection is All 4.2 supported
via Web UI is configuration via Web UI for 10Gb fiber disabled for 10G ports in the platforms
not grayed out ports. Ideally the auto-neg option should be Web as auto-negotiation must
for 10Gb fiber grayed out for 10Gb fiber ports. always be enabled.
ports.
CLI command The CLI command “show interface detail The scrolling issue has been All 4.2 supported
"show interface port-channel1” generates the following corrected. platforms
detail port- errors:
channel1" locks
up console Max number of lines in the scroll buffer
session reached. Output will be truncated.
The CLI When executing the command terminal Terminal length settings now All 4.2 supported
command length <value>, the value is not updated take effect immediately. platforms
terminal length after execution.
is not setting
terminal length
value
The Service tag When executing the “show system id” is not The service tag was All 4.2 modular platforms.
is being deleted showing the service tag on modular accidentally being deleted and
on modular platforms. is now being saved correctly.
platforms.
Router crashes on OSPF The switch can crash when changing the Corrected process All Platforms
network type change. configuration from the default of broadcast synchronization problem
to point-to-point.
Occasional crash when With routing globally disabled, bouncing Correct the transition All Platforms
configuring VRRP. VRRP on a host interface occasionally between routing being
causes a crash. disabled and routing being
enabled.
Cannot create Dynamic LAG Dynamic LAG cannot be created from CLI Correct the command All Platforms
with Interface range command using interface range command. syntax to "auto " instead of
"active"
PC8024 cannot forward PC8024 cannot forward packets on port9 Correct interoperability PC8024
packets on port9 to port16 to port16 while linked on at 100Mb. problem between the PHY PC8024F
while linked on at 100Mb. and the switching core.
Show fiber-ports optical- Instead of reporting on exact ports that had Corrected register problem PCM8024
transceiver is not displaying modules, diagnostics were reported on the when accessing the SPF+
the correct interface numbers. ports that did not have modules ports
VRRP routing instances VRRP routing instances increased to 50. Increased VRRP routing All Platforms
increased to 50. instances table.
DHCP on in-band and out of The warning message about IP address Add warning message in All Platforms
band ports conflict is not printed in case DHCP is case offered IP address is
configured on in-band and out-band ports conflicting with the
and they both receive an IP address from configured one on another
one subnet. port
Config commands did not Command "spanning-tree mode mstp" Correct the command tree to All Platforms
migrate correctly from version doesn't migrate correctly from version migrate the old syntax.
3.1.5.13 3.1.5.13.
Auto-neg option via Web UI is Auto-neg option via Web UI is not grayed Corrected the Web UI. PCM8024-k
not grayed out for 10Gb fiber out for 10Gb fiber ports for the PCM8024-
ports. k.
Simple mode, VLAN setting if a port is moved from one aggregation Correct initialization when PCM6220
not active when a port is group to other, VLAN settings are retained port is moved.
moved to another group but not applied until reboot.
Unable to configure secure Error message 'sshcfg_load start' missing Corrected Web page error. All Platforms
SSH from web interface. is returned.
Secure HTTP Random Random characters populate the Secure Corrected Web page data All Platforms
Characters HTTP web page. initialization.
IP PIMSM BSR/RP Mapping When the RP or the BSR changes, the data Corrected RP join All Platforms
is not robust traffic may get affected and in some case processing.
get software forwarded.
Error messages when issuing a Accessing unsupported counters causes Change the logging priority All Platforms
show statistics command while error messages to be displayed. of the messages for
traffic running. unsupported counters so that
they are not output.
OOB Default Gateway does There was no way to configure the Add functionality for All Platforms
not save when using CLI setup gateway on Out-Of-Band interface. configuring gateway on
wizard Out-Of-Band interface.
Upgrades to 4.1.0.6 are Ports on some devices will not attach. Corrected the Configuration All Platforms
causing network outages. The Wizard to properly apply
wizard from 4.1.0.6 fails to the configuration to all
setup interfaces ports.
The combo port is not coming The fibers port associated with Fiber / Add commands to allow PC8024F/
up after performing repeated RJ45 combo ports may flap or not link up operator to prefer or force PC8024
plug-out and plug-in. with certain other switches. RJ45 or SFP port selection
on combo ports.
Line "no passive-interface The "no passive-interface Vl32" Corrected the loading of the All Platforms
Vl32" in startup-config does configuration does not get loaded from the "no passive-interface Vl32"
not get loaded on startup. startup-config on startup. configuration.
Unable to configure Secure Proper web page operation is prevented. Web page has been All Platforms
Shell from web interface. corrected.
OpenManage web interface The web page for iSCSI fails to open when Web page has been All Platforms
fails to provide an iSCSI web selected with OpenManage. corrected.
page when selecting the iSCSI
item.
Wrong information for current Incorrect stacking link status is presented Web page output has been PCM6220
link status in port in the Web page. corrected.
configuration page.
PFC sends packet after quanta This can cause FCOE failures when using Switch no longer sends PCM8024-k
extension received. PCM8024-k as a transit switch between packet after quanta
some switches. extension received.
CLI command "show ipv6 A large number of interfaces cause Fixed the pagination for the All Platforms
interface" does not paginate information to scroll off the viewing area. command.
correctly.
MOTD Banner appears at the MOTD and Login Banner is not visible Fixed the banner processing PCM6220
wrong time. before login for SSH users. function.
Switch crashes when full vlan When the full range of VLAN instances is Corrected VLAN instance PCM6220
range assigned to MST assigned to a MST region the switch buffer overflow.
regions. crashes.
Config Wizard causes iSCSI Using the config wizard to setup the Correct the handling of PC8024
error messages. PC8024 causes iSCSI error messages. iSCSI admin mode.
SSH configuration not restored The 'ip ssh protocol 2' is not being Corrected the ability to All Platforms
after reboot. included in the running configuration. place 'ip ssh protocol 2' in
the running-config.
1GB link being negotiated on Some internal links on the Modular Corrected the port mapping PCM8024
10GB Intel X520-KX4 switches will not link at 10Gb. to allow proper port PCM8024-k
configuration.
No message logged for "Max When the Max number of SSH sessions is Added an error message. All Platforms
number of SSH login sessions reached no error is logged.
exceeded"
VLAN web page not updating. When VLANs are removed using the web, Corrected the fetch of All Platforms
the GUI doesn’t display the ports that are current VLAN data.
members of the VLAN.
No password min length error If "no passwords min-length" Is set an Correct password length All Platforms
when using web GUI. error results if the password is less than 8 range check.
characters.
MIB walk crashes switch. When running a large SNMP MIB walk Corrected a memory All Platforms
the switch crashes. problem in the MIB walk.
Unable to deselect VLAN tags Once Tagged-VLAN’s are selected there Corrected the Web page that PCM8024
in web GUI. is no way to unselect them again via the allows tagged VLANs to be PCM8024-k
web GUI. unselected.
VPD CRC check hang When the switch boots, If the CRC check Corrected check for valid All Platforms
of the VPD fails, the switch will hang. VPD before CRC check.
Packet Buffer Optimization. Improved Performance with High Improved performance. PC70XX
Utilization iSCSI Workloads. PCM8024
PCM8024-k
PC8024
PC6348
PCM6220 Stack View needs PCM6220 Web pages did not have the Updated the PCM6220 web PCM6220
PCM70XX styling same styling as PC70xx. pages.
Release 4.1.0.6
Summary User Impact Resolution Affected
Platforms
SSH crash - memPartAlloc: Reduced switch functionality. Memory allocation issue is All
block too big corrected and checked for Platforms
memory leaks
PC M8024 switch reset out-of- Inability to access switches via OOB port. The out-of-band address is PCM8024
band address to none when maintained over switchport
switchports were changed changes.
Web page shows IP address as Potential operator confusion over switch The web page output has All
'0.0.0.0' for '1.1.1.1' routing operations been corrected. Platforms
interface.
Release 6.1.0.1
The example under MVR immediate command on page 580 configures MVR mode dynamic which is not
available in interface config mode. This is available only in global config mode.
The “spanning-tree mode” global command supports “no” form but the command is “no spanning-tree” and not
“no spanning-tree mode” as mentioned on page 753.
On page 765 for “spanning-tree vlan” command, the range is mentioned as 1-4094 it should read as 1-4093 for
accuracy.
On page 764 for “spanning-tree uplinkfast” command, the range for max-update-rate is mentioned is as 0-3200.
It should read as 0-32000
The supported TLVs for LLDP MED are only capabilities, network policy. Ignore the other TLVs listed under
command lldp med transmit-tlv on page 556
On page 1525 “802.1AF” should be “802.3AF”.
On page 1635 crypto is misspelt as cryptho for command crypto key generate dsa
The “storm-control broadcast” and “storm-control multicast” commands have a new parameter “action” added.
shutdown – On storm control, the affected interface shall be diag-disabled along with sending of a
trap. If the interface is diag-disabled, user needs to explicitly use “no shutdown” command to
bring back the link.
trap – On storm control, a log message and a trap when the configured threshold is exceeded.
Traffic exceeding the threshold is dropped.
The following example configures any port to shut down if the received multicast traffic rate exceeds 20%
of link bandwidth:
Example:
console(config)#show storm-control action all
Bcast Mcast
Port Action Action
--------- ---------- ----------
Gi1/0/1 Shutdown
Gi1/0/2
Gi1/0/3
The following new commands are implemented dlvan tunneling and some of these commands deprecate old
commands.
Use the switchport mode dot1q-tunnel to enable QinQ tunneling on customer edge (CE) interfaces. Use the
no form of the command to return the interface to the default switchport mode (access).
Syntax
switchport mode dot1q-tunnel
no switchport mode dot1q-tunnel
Parameter Description
N/A
Default Configuration
By default QinQ processing of frames is disabled.
Command Mode
Interface mode (physical and port channel), Interface range mode (physical and port channel)
Usage Guidelines
This command configures a customer edge (CE) port for QinQ tunneling. The dot1q-tunnel mode is an
overlay on switchport access mode. In particular, configuring the access mode PVID sets the outer dot1q-
tunnel VLAN ID. Changing the switchport mode to access, general, or trunk, effectively disables tunneling
on the interface.
Customer edge ports can be physical ports or port channels. Untagged frames received on the CE interface
will be processed as if they belong to the PVID and will be transmitted out the SP interface with a single
VLAN tag. Tagged frames received on the CE interface will be transmitted out the service provider (SP)
interface with an outer tag containing the native VLAN ID and the inner tag as received on the CE
interface.
CE interfaces MUST be configured in dot1q-tunnel mode with the PVID configured with the outer tag
(native) VLAN ID for the associated service provider (SP) interface. Configure the outer VLAN ID using
the switchport mode access vlan command. All MAC address learning and forwarding occurs on the outer
VLAN tag. The VLAN ID must be common to both the SP port and the CE ports.
The service provider interface MUST be configured for egress tagging (trunk or general mode) with a
native VLAN identical to the PVID of the associated CE ports. SP interfaces SHOULD be configured with
It is not possible to configure an inner VLAN TPID value. The inner VLAN TPID value is always 802.1Q
(0x8100).
Multiple groups of associated CE and SP ports can be defined by configuring the groups with unique
VLAN IDs where the VLANs are associated with the outer SP VLAN tag.
The port mirroring logic stage occurs after the tag processing stage on ingress and before the tag processing
stage on egress. When mirroring packets associated with SP or CE ports, the outer VLAN tag may or may
not appear in the frame. Due to the internal processing, of QinQ tagging, the TPID of ingress frames
mirrored from the SP port will always be 0x8100. In addition, packets forwarded internally across a
stacking link may have different tags applied than packets forwarded on a local egress port. This is due to
the processing required for forwarding across a stack.
Examples
This example configures ports Gi1/0/10 through Gi1/0/24 as CE ports using VLAN 10 as the service
provider VLAN ID. See the example for the switchport dot1q ethertype command to configure an
associated SP port.
console(config)#vlan 10
console(config-vlan10)#exit
console(config)#interface range gi1/0/10-24
console(config-if)#switchport access vlan 10
console(config-if)#switchport mode dot1q-tunnel
console(config-if)#exit
Use the switchport dot1q ethertype to define additional QinQ tunneling TPIDs for matching in the outer
VLAN tag of received frames. Use the no form of the command to remove the configured TPIDs.
Syntax
Parameter Description
Vman – define the Ethertype as 0x88A8
Custom – define the Ethertype as a 16 bit user defined value
802.1Q is the default Ethertype for both inner and outer VLAN TPIDs. The 802.1Q TPID cannot be
removed from the configuration.
Command Mode
Usage Guidelines
This command globally defines additional TPIDs for matching of ingress tunnel packet. Ingress packets
matching the tunnel VLAN ID and any of the TPIDs in the outer VLAN tag are accepted into the tunnel.
A TPID must be configured globally before it can be applied to an interface. Up to 3 additional TPIDs can
be configured in addition to the default TPID of 0x8100.
Use the no form of the command to remove an additional TPID. Doing so removes the TPID from all
interfaces. If the removed TPID is the primary TPID for an interface, the interface is configured to use the
default primary TPID 0x8100.
Packets are always transmitted by the system using the primary TPID value in the outer VLAN tag.
It is not possible to configure an inner VLAN TPID value. The inner VLAN TPID value is always 802.1Q
(0x8100).
Use the switchport dot1q ethertype interface configuration mode command to apply a configured TPID
value to an interface.
Examples
This example defines the VMAN (0x88A8) TPID for use on a service provider (SP) port and configures a
service provider port (Te1/0/1) in general mode after creating the common SP/CE VLAN. The port is
configured in general mode and to only allow tagged packets using the outer VLAN ID 10 to ingress the
tunnel. Packets not matching the VLAN or TPID are treated as untagged. Then the port is configured to
accept the VMAN TPID in the outer VLAN on ingress and further configured to tag packets with the
VMAN TPID and VLAN ID 10 in the outer VLAN tag on egress.
Use the switchport dot1q ethertype command to apply QinQ tunneling TPIDs to a service provider
interface. Use the no form of the command to remove the configured TPIDs.
Syntax
Parameter Description
802.1Q – allow ingress frames with Ethertype 0x8100
vman – allow ingress frames with Ethertype 0x88A8
custom – allow ingress frames with an 16 bit user defined Ethertype
primary-tpid – set the outer VLAN tag TPID to be used on an SP port for transmitted frames. Also allows
ingress of frames with the configured Ethertype.
Default Configuration
802.1Q is the default Ethertype for both inner and outer VLAN TPIDs.
By default QinQ processing of frames is disabled.
Command Mode
Interface configuration mode (physical and port channel), Interface range mode (physical and port channel)
Usage Guidelines
This command applies a previously defined TPID to an interface. The TPID must be configured using the
global configuration mode command before it can be applied to an interface. Up to 3 additional TPIDs for
use in the outer VLAN tag may be configured.
Use the no form of the command to remove the TPID from an interface.
Defining a new primary TPID command overwrites the existing primary TPID for an interface.
The no form of the command with the optional primary TPID specified sets the primary TPID value to
802.1q (0x8100).
If the TPID value was not configured as a primary TPID and the no form the command includes the
optional primary-tpid argument, the command will fail.
If the TPID value was configured as the primary TPID, and the no form of the command does not include
the optional primary-tpid argument, the command will fail.
If a TPID value is configured as the primary TPID, and it is added again without the primary-tpid optional
argument, the TPID will be treated as the primary TPID (the primary TPID includes the behavior of
secondary TPIDs).
It is not possible to configure an inner VLAN TPID value. The inner VLAN TPID value is always 802.1Q
(0x8100).
Examples
This example defines the VMAN (0x88A8) TPID for use on a service provider port and configures a
service provider port (Te1/0/1) in general mode. The general mode port is configured to only allow tagged
packets on ingress using VLAN ID 10. Then, in the last command, the port is configured to accept the
VMAN TPID in the outer VLAN on ingress and further configured to tag packets with the VMAN TPID in
the outer VLAN tag on egress.
Use the show switchport ethertype to display the configure Ethertype for each interface.
Syntax
Default Configuration
N/A
Command Mode
Usage Guidelines
It is not possible to configure an inner VLAN TPID value other than 0x8100.
Examples
This example defines the VMAN (0x88A8) TPID for use on a service provider port and configures a
service provider port (Te1/0/1) in general mode. The general mode port is configured to only allow tagged
packets on ingress using the outer VLAN ID 10. Then the port is configured to accept VMAN TPID in the
outer VLAN on ingress and further configured to tag packets with the VMAN TPID on egress.
Use the show dot1q-tunnel command to display the QinQ status for each interface.
Syntax
Parameter Description
Intf-id – a valid physical interface or port-channel
Default Configuration
Command Mode
Usage Guidelines
Examples
Use the show interfaces switchport command to display the complete switchport VLAN configuration for
all possible switch mode configurations: access, dot1q-tunnel, general, trunk, and (private VLAN) host or
(private VLAN) promiscuous.
Syntax
No changes
Parameter Description
Intf-id – a valid physical interface or port-channel
Default Configuration
Command Mode
No changes
Release 6.0.1.3
The CLI allows the user to enter Ethernet mode commands in interface stack configuration mode. These
commands do not have any effect on the stacking port.
The show ip route configured command on page 1149 of CLI Reference mentions show ip route configured
commands as deprecated but the command is retained to view the inactive configured routes
The following note has to be added to the show power inline command on page 1536 for additional clarity.
Get Power Supply Parameters API from the PoE controller returns the “Total Power Consumed” value in
Watts. For this reason, Total Power Consumption value displayed in the CLI might not exactly match the sum of
power in milliwatts consumed by various Power Devices.
The example command to display the power inline details for the single port also need to be corrected as below:
console#show power inline gigabitethernet 1/0/1 detailed
Release 6.0.0.8
There is a new CLI Reference Guide for 6.0.0.8.
The example for the mvr immediate command on page 580 of the CLI Reference contains an incorrect
example. The correct example is:
console(config)#interface Gi1/0/1
console(config-if-Gi1/0/1)#switchport access vlan 10
console(config-if-Gi1/0/1)#mvr
console(config-if-Gi1/0/1)#mvr type receiver
console(config-if-Gi1/0/1)#mvr immediate
console(config-if-Gi1/0/1)#exit
console(config)#mvr mode dynamic
Release 5.1.4.5
No Updates
Release 5.1.3.7
No Updates
Release 5.1.2.3
Default Configuration:
This command has no default configuration.
Command Mode:
User EXEC, Privileged EXEC modes, Configuration mode and all Configuration submodes
Description:
The show switch stack-ports stack-path command is useful in tracking the path a packet may take when
traversing stacking links. The command shows active paths only, not those that may be taken after a stack
failover or stack re-convergence.
User Guidelines:
The show switch stack-ports stack-path command is useful in tracking the path a packet may take when
traversing stacking links. The command shows active paths only, not those that may be taken after a stack
failover or stack reconvergence.
Examples:
Release 5.1.1.7
No Updates
Release 5.1.0.1
The following table lists issues found in the CLI Reference Guide after publication:
Command Issue
ip igmp snooping querier The guideline under this command refers to the IGMP Snooping Max Response
query-interval Time. A reference that this can be configured using command ip igmp query-max-
response-time under IGMP commands is missing. The default IGMP/MLD snooping
Max Response Time is 25 sec
terminal monitor The command does not have any arguments or a particular expected output hence
an example for this is missing in the guide.
Release 5.0.1.3
No Updates
Release 5.0.0.4
Command Issue
Show snmp filters The following note should be added to the command usage guidelines.
Snmp-server filter
When a filter is defined, SNMP treats the filter as having an 'exclude all' statement at
the beginning of the filter. Unless an include statement is specified, all notifications
will be excluded.
aaa authorization {exec } The following Exec Authorization CLI commands are missing from the CLI reference
{default | <list_name>} guide
method1[method2]
aaa authorization {exec } {default | <list_name>} method1[method2]
no aaa authorization {exec} no aaa authorization {exec} { default|<list_name>}
{ default|<list_name>} authorization exec [default |<list_name>]
no authorization exec
authorization exec [default debug aaa authorization exec
|<list_name>] no debug aaa authorization exec
no authorization exec
Release 4.2.2.3
No Updates
Release 4.2.1.3
Command Issue
Storm-control broadcast The supported syntax is Storm-control broadcast [level rate] where
rate is a parameter to level and defined to be:
The storm-control threshold as percent of port speed. Percent of
port speed is converted to PacketsPerSecond based on 512 byte
average packet size and applied to HW.
If level is not used the default rate is 5.
name "RDU-NOC The VLAN name command has been migrated to VLAN Config mode
Management VLAN" and is no longer available in interface VLAN mode.
Release 4.1.1.9
No Updates
Release 4.1.0.19
The following commands are supported on switches that have combo ports:
Command media-type
Syntax:
media-type { auto-select [rj45 | sfp ] | rj45 | sfp }
auto-select rj45 - utilize RJ45 media when both media types are active
auto-select sfp - utilize the SFP media when both media types are active
auto-select – return the selection to the default (auto-select sfp)
rj45 – force connection on the RJ45 port. Power off SFP media port
sfp – force connection on the SFP port. Power off RJ45 media port
Default Configuration:
The default is “media-type auto-select sfp”
Command Mode:
Interface Config mode
Description:
Select the media type for the interface. This command is only valid on combo ports.
User Guidelines:
When both media types are connected, the preference as determined by the auto-select keyword parameter selects the
active media. When the auto-select keyword is not specified, the selected media type is powered on and the alternate
media type is powered off. Note that when the auto-select keyword is used with any media type, the SFP port will remain
powered and the laser, if any, will remain on in order to allow connections over the SFP port.
Examples:
! Select the RJ45 port and power off the SFP port
console(config-if-Te1/0/24)#media-type rj45
! Prefer the RJ45 port and leave the SFP port powered on
console(config-if-Te1/0/24)#media-type auto-select rj45
Syntax:
show interfaces media-type
Description:
Display the configured and active media type for the combo ports
User Guidelines:
N/A
Examples:
Release 4.1.0.6
The CLI Reference Guide is completely new. Users are referred to the Configuration Migration White Paper for
information on how to migrate configurations from previous releases of firmware to the 4.0.0.6 firmware.
The following table lists issues found in the CLI Reference Guide after publication:
Command Issue
show service-policy in The supported syntax is show service-policy {in|out}
show copper-ports cable- This command is deprecated. Use the show copper-ports tdr
length command to display the stored information regarding cable lengths
and the test copper-port tdr command to perform a cable length test.
Testing a port brings the port down momentarily.
Release 6.1.0.1
No Updates
Release 6.0.1.3
No Updates
Release 6.0.0.8
There is an Updated User’s Configuration Guide for 6.0.0.8. The following corrections are applicable:
On page. 62 (Hot Add/Delete and Firmware Synchronization), add the following sentence:
“Note: ALWAYS POWER OFF a unit to be added to a stack prior to cabling it into the stack. Newly added
units must be powered on one at a time beginning with the unit directly connected to an already powered on
stack member.”
On page. 392 (Configuration File), add the following sentence after the phrase “should exist on the USB
device:”
“It must have a .text file name extension. No other file name extension is allowed.”
On page. 403 (Enabling USB Auto Configuration and Auto Image Download), replace the sentence:
“Otherwise, the switch can obtain an IP address from a DHCP server on the network.”
“An IP address and netmask are mandatory elements of each configuration line in the configuration file.”
On page. 404 (Enabling USB Auto Configuration and Auto Image Download), delete the Note and replace the
switch MAC addresses in Step 4 with suitable IP addresses and netmasks.
On page. 544 (What Does Captive Portal Do), add the following sentences to the last paragraph:
“In order to support redirection of user entered URLs from a web browser, a DNS server must be configured in
the network. If routing is enabled on the switch, IP helper must be configured and enabled to allow hosts to
obtain an IP address via DHCP.
The only type of wired interface where Captive Portal can be enabled is a physical port. Captive Portal is not
supported on multi-access VLANs or on LAGs.
A physical port’s VLAN membership does not affect Captive Portal. A physical port enabled for captive portal
can be a member of any VLAN or multiple VLANs. The VLAN may be a switching or routing VLAN.
A port enabled for Captive Portal may be directly connected to a single client (e.g., an access switch), or the
port may serve many clients (e.g., a port on an aggregation switch).
Port security and captive portal cannot both be enabled on an interface.
If a physical port configured with captive portal is made a member of a LAG, captive portal is disabled on the
port.
Dell Networking does not support configuring spanning tree on a Captive Portal port. BPDUs received on a port
enabled for captive portal will not receive their normal prioritization.
Captive portal can co-exist on an interface with DHCP snooping and Dynamic ARP Inspection (DAI).
Captive Portal is supported in IPv4 networks only. “
On page. 652 (Voice VLAN), add the following note:
Release 5.1.4.5
No Updates
Release 5.1.3.7
No Updates
Release 5.1.2.3
No Updates
Release 5.1.1.7
No Updates
Release 5.1.0.1
Issue
Unknown unicast and multicast packets are copied to the CPU on the lowest priority QoS queue. Unknown packets are
those that do not have hardware forwarding entries. Known unicast/multicast packets are hardware forwarded and are not
queued to the CPU. Control plane packets (e.g. spanning tree BPDUs) are copied or forwarded to the CPU on higher
priority queues. The rate limiting for unknown packets occurs on the internal CPU port and does not affect hardware
based traffic routing/forwarding in any way. Typically, the switch will examine the received packets in software to check
if there is a forwarding entry, create a forwarding entry (e.g., add a L2 MAC address or ARP response), and then either
discard the packet or software forward the packet (only occurs during the brief transitional period when the system is
actively adding a hardware forwarding entry but the hardware is not yet updated). Processing delays for higher priority
packets may occur when the internal CPU queue is continually kept busy handling low priority packets.
A command was created to allow the administrator to reduce the rate limit for which unknown unicast and multicast
packets are forwarded and/or copied to the CPU. It does not affect the rate limits for control plane packets. It is almost
never necessary to use this command to change from the default value. The use of this command should be restricted to
situations in which moderate to high rates of unknown unicast/multicast are continually sent to the switch CPU as
evidenced by the show proc cpu command and where the ipMapForwardingTask is showing high CPU usage. This will
occur most frequently in networks where a high number of ARPs are continually received on untrusted ports, high
numbers of L2 stations are timing out and reappearing or multicast flooding is occurring in the network. If problems with
L2, L3 or multicast learning occur after changing this value, set the rate limit back to the default value and take other
steps to correct or mitigate the underlying network issue directly.
See the CLI Reference Guide updates section of this document for the description of the “rate-limit cpu” CLI command
and its use.
Release 5.0.1.3
No Updates
Release 5.0.0.4
Issue
The following message needs to be added to warn the user that Hotplug of a module is not supported if one of the ports
on the module is operating in stacking mode.
The following copper SFP needs to be listed as the supported module. However, diagnostics are not supported on copper
SFP’s.
Finisar FCLF-8521-3
When a filter is defined, SNMP treats the filter as having an 'exclude all' statement at the beginning of the filter.
Unless an include statement is specified, all notifications will be excluded.
Release 4.2.2.3
No Updates
Release 4.2.1.3
Release 4.2.0.4
No Updates
Release 4.1.0.19
The following table lists changes to the User’s Configuration Guides after publication:
Release 6.1.0.1
Description/Summary User Impact Workaround
N20xxP/N30xxP – Issues powering up POE When legacy and dot13af mode is Configure “power inline detection
devices on high switch port interfaces. enabled for power inline detection dot13af” globally to power up all dot13af
and the first 12/24 ports are in compliant PDs on all ports. This
error/short status (Invalid workaround will not help legacy PDs.
Signature Counter incrementing), Will update PoE Firmware in the next
last 12/24 ports stay off. firmware release to address both legacy
and dot13af PDs.
Group specific query packets are transmitted Protocol behavior does not change. None.
on all the member ports, even when they are Traffic is not flooded but only the
not a part of the group query packets are unnecessarily
sent out.
Unwanted ECC Errors “CDC RX FIFO None. None.
entry 19 double-bit ECC error” noticed in
the console and syslog.
Unwanted MAC flap messages like Low. These messages are seen Disable LLDP and ISDP on the connected
%SW_MATM-4-MACFLAP_NOTIF: Host only on some variants of Cisco links.
001e.xxxx.xxxx may be noticed on Cisco switches.
console the Cisco switch interoperates with
Dell switches.
When MSTP instances are pre-configured MSTP instances are running and Do not configure MSTP instances when
with running spanning tree mode as RSTP, shall influence the port state for running spanning-tree in any mode other
MSTP instances are created and are active. the ports participating in the than MSTP.
instances.
CLI checks and restricts ports of different Will not be able to configure Fiber None.
speed/ auto-negotiation capabilities to be and Copper ports to same port-
added into same port-channel. channel even if same speed.
Release 6.0.1.3
Description/Summary User Impact Workaround
Some Traffic loss on Mcast setup at ir- Intermittently without any predefined interval there will None.
regular interval for two group ranges in a be some drop in packets before the traffic restores on few
total of 470 groups. groups.
When 10G ports on stack running Flow control doesn’t work but this only applies on 10G Turning off PFC
N4000/8100 switches are running at 1G ports running at 1G and turning it on
speed PFC may not be operational after may help.
failover
DCPDP control packets are getting None. The system recovers from this failure. When there Use routing
dropped, when OOB port has lot of traffic are a lot of packets to be processed on the OOB port the interfaces instead of
DCPDP control packets are getting dropped. OOB
Configuration issues on the stack ports Stack ports are listed for some commands that do not None
apply to stack ports. The command however is rejected
Unable to learn the max FDB entries on The Secondary FDB application remains out of sync with Sequential address
secondary while sending the line rate the hardware storms should be
traffic with 1, 31,072 sources. avoided
Release 6.0.0.8
Description/Summary User Impact Workaround
Occasional FAN failure messages are seen None – the system recovers from the None.
on the N4000 console. The typical rate of failure and fan operation is not affected.
errors detected is around 4-8 per 24 hours These messages can be safely ignored.
during normal operations. Examples:
<187> Jan 27 14:45:04 172.25.131.236-3
BOXSERV[1193277812]: boxs.c(841)
21345 %% FAN module 2 of unit 2 is now
in FAILURE STATE.
<188> Jan 27 22:40:55 172.25.131.236-1
BSP[841719292]: dps460kb.c(120) 21860
%% Failure writing PMBUS command to set
PSU-1 fan speed
QSFP Transceiver AFBR-79E4Z-D-FT1 does Port may hang and require reload of Dell recommends the use of the
not operate within required tolerances. switch to recover. Dell Qualified T9MJF QSFP
transceiver.
In multi-tier MLAG topology, primary Issue is seen only when 130k different Execute 'no feature vpc' followed
device MLAG is moved to discard state after MACs are learnt on a single MLAG by 'feature vpc' command.
executing "no feature vpc/feature vpc" interface at line rate which is not a
commands while traffic is running from practical scenario and the administrator
130K sources. executes 'no feature vpc'/'feature vpc'
during this process. This issue shows up
very rarely.
USB stick may not be detected on insertion USB device does not get mounted Execute 'unmount usb' command,
if an unmount was not performed inserting a then remove and re-insert the
new USB device. USB device.
CPU utilization goes high temporarily when CPU utilization goes high for some time CPU utilization comes down
MVR is used with more than 1K VLAN's automatically even if there are
more than 1K VLAN's
configured on the switch. The
work around is to not use more
than 1K VLAN's when MVR is
enabled on the switch
Secondary MLAG switch doesn't show peer- Primary MLAG switch shows peer- Use “show vpc brief” on primary
member as output of "show vpc brief" members as part of "show vpc brief". switch only.
Secondary MLAG switch doesn't show
peer-members.as part of “show vpc brief”.
Port-Channel interface shows member port Status is mis-leading when shown on Use “show interfaces port-
as "inactive" on Secondary MLAG device Secondary MLAG switch.. channel x” on primary switch
only.
When known unicast traffic is sent with snmpIfInUcastPkts and Send packets with correct data
frame size set to random with minimum of snmpIfHCInUcastPkts shows counts for length values.
64 bytes and maximum of 1518 bytes, it is 64 bytes packets only.
observed that snmpIfInUcastPkts and
snmpIfHCInUcastPkts shows counts for 64
bytes packets only.
DCPDP control packets are getting dropped, A log message will be seen saying peer is 1) Only peer detection would fail
while running SNMP walk on root node. not detected using DCPDP but traffic is during SNMP walk on the root
not affected. node. Peer detection will be
successful once the SNMP walk
operation is complete.
2) SNMP clients should throttle
their requests to no more than 20
per second.
In multi-tier MLAG topology, when 128K This issue shows up only if the sources are Enable and disable MLAG port
sources are sent at line rate, south bound sent at line rate, which is not a practical or send traffic at lower rate.
secondary device is unable to learn all the scenario in the networks.
sources.
Temporary console hang for 3-4 minutes is Temporary console hang is observed for 3 Wait for 3-4 minutes if you see
observed on issuing “clear counters all” to 4 minutes. console hang on “clear counters
command when sending lot of multicast all” command.
traffic into the switch.
The maximum supported size of the packet Ping and traceroute fail if command is Use maximum of 13000 and
that is supported by the switch for ping and issued with packets size greater than 39936 as the packet size for ping
traceroute is limited to 13000 and 39936 13000 and 39936 respectively. and traceroute respectively.
respectively.
Traffic is not forwarded based on the static Static route is expected to take precedence, When using PBR, use PBR to
default next hop, instead is forwarded based but PBR policy takes precedence. achieve the default route
on the PBR default next hop. forwarding behavior instead of
configuring default route.
Release 5.1.4.5
Summary User Impact Workaround
Active ports are becoming inactive and Occasionally, this condition can affect a LAG if This is the result of a
inactive ports are becoming active in LAG a link auto-negotiates to a speed that is slower configuration mismatch and
after LAG shutdown/no shutdown with than the LAG should run at and if the slower link should be corrected in the
speed change. comes up first. The first port to link up sets the topology.
rate of the LAG and link that are not of that
speed are blocked.
Port-channel is not allowed to configure Port-channel interface is not allowed to No workaround.
with same speed ports but different media configure with the warning message if user This will be supported in a
type attempts to configure 10G Base-T and 10G later release.
SFP+ ports (different media type)
CLI is not updated with default storm When the storm control configuration is If possible use the CLI to
control configuration when disabling the disabled from WEB, the change in disable storm control.
storm control configuration from WEB. configuration it is not getting updated to CLI. This will be fixed in a later
release.
Duplicate Address Detection (DAD) is not Occasionally, when deleting a IPv4 VLAN Only affects PC8100 switches.
working on link-local addresses. and re-adding the VLAN as an IPv6 VLAN to This will be fixed in a later
a port the Duplicate Address Detection release.
(DAD) can fail for that link.
Storm control action feature is not working Storm Control counters are no accurate on Only affects PC8100 switches.
on 10G copper/SFP+/pluggable module the 10G copper/fiber/pluggable module This will be fixed in a later
ports. ports. release.
Release 5.1.3.7
"Total errors" column in When the CLI command "show switch stack- None. Reloading the switch will clear the
"show switch stack-port port counters" is used "Total errors" column is counters.
counters" is not reset to not reset to zero after "clear counters stack-
zero after "clear ports" command is issued. This will be corrected in a future release.
counters stack-ports".
Receive/Transmit The CLI command “show interfaces counters None. This will be corrected in a future release.
Packets Discarded port-channel 1” does not show an accurate
counters missed on count of Rx/Tx packets discarded.
port-channel counters
Release 5.1.2.3
Release 5.1.1.7
Summary User Impact Workaround
8100 - SCP or SFTP file SCP or SFTP file transfer from 8100 switches to Workaround: None.
transfers to FreeBSD and a FreeBSD or Mac client/server causes the switch
Mac causes switch to to crash and reboot. Eventually connectivity
crash and reboot. comes back after a few seconds, but the Fixed in 5.1.2.x release
connectivity loss is long enough to cause iSCSI
connections to drop.
8024 - Routing issue, Some null mac address (0000.0000.0000) present Workaround: Reloading the switch resolves the
null address in ARP table in PC8024 ARP table. This happens after vlan issue temporally (till next vlan
after VLAN manipulation (like create, delete, define IP reconfiguration). Add static entry in ARP table
manipulation address, add and remove on trunk port).Issue resolves the issue.
occurs randomly and not immediately (take
between 30min and 1h between vlan Fixed in 5.1.2.x release
manipulation and routing issue)
PCM6220 v5.0.1.3 PCM6220 Switch crashes every 30 to 40 days Workaround: None.
switch crashes every 30- when SNMP monitoring with cacti version 0.8.8a Fixed in 5.1.2.x release
40days while SNMP
monitored
Release 5.1.0.1
Summary User Impact Workaround
Molex QSPF DAC Cable Voltage is displayed as 0.00 instead of "N/A" for Ignore the voltage displayed field for this part
with part number this diagnostic parameter. or use a SFF-8436 compliant cable.
111040-1104 does not
comply with QSFP
specification SFF-8436.
These cables do not
support 'voltage'
diagnostics.
Show AAA IAS-USERS The “show aaa ias-users [username]” command The same information can be seen within the
<Username> Command seems to have been deprecated even though it running configuration of the switch with the
Missing still exists in the CLI guide. “show running-config” command.
External CDP/ISDP Occasionally external CDP/ISDP packets are None.
traffic occasionally being forwarded to the internal ports. This
forwarded onto internal results in confusing information from the blade
ports server point of view as multiple directly
connected neighbors appear to be seen.
Multicast sources that If an intermittent multicast source that has been The default IGMP query interval is 125
cease sending multicast aged out of the multicast forwarding cache seconds. In practice, this situation is very
are timed out and begins sending again before the corresponding unlikely to occur as a multicast source that fails
removed from the S,G entry has timed out at the RP (185 seconds to send even one packet for 150 seconds is
multicast forwarding per RFC 4601), any *,G entries (joined hosts) unlikely to start sending packets before the S, G
cache after 150 seconds may take up to one IGMP Query interval to begin entry at the RP times out.
receiving the multicast stream.
Release 5.0.0.4
Summary User Impact Workaround
QSFP Base CR4 with When using the DAC copper cables with QSFP None
copper DAC cable CR4s (which are rarely used) and cable more
lengths greater than 3 than 3 meters, the switch may not even detect
meters will not work on this device and so link up never happens. Only
8100 switches the following cables are recommended with these
CR4 QSFPs:
On 8100 switches, sharp This is a corner case issue requiring many steps Stop traffic for a minute or two so that the stale
decrease in 6to4 tunnel to get to this state but if the state is reached, the entry in the Linux stack is cleared.
traffic is observed when user will see less through-put on the tunnel.
ipv4 static route is
deleted and added back
to the switch.
Failure log messages There is no effect besides the annoyance of these None
may show up on console messages while doing an SNMP walk.
on doing a SNMP walk
on root node.
Image uploaded with This might require the User to have to retry the Use alternate transfer methods like TFTP, FTP,
HTTP method can't be download or change the IP address or VLANs on etc.
downloaded back to the the switch or PC.
switch if switch and PC
are located in different
networks and the
networks are very slow.
Console messages shows Our customers requested this warning to indicate Configure the logging level to be higher than
"Thermal state raised to better visibility into the Thermal settings and “Warning”.
WARNING" often. sensors.
Finisar LRM 10G SFP+ This specific model is not recommended for use Please use the Avago 10G-BaseLRM model –
transceiver model – with our switches. AFBR-707SDZ-D1.
FTLX137D3BCL - drops
packets intermittently.
OpenManage displays OpenManage timeout warning window is None.
incorrect session timeout displaying the wrong value but uses the set value.
duration
Command "show fiber- Executing the command “show fiber-ports None.
ports optical-transceiver" optical-transceiver” with multiple transceivers
causes UI to become inserted will cause the console prompt a long
slower with multiple time to return (possibly up to 60 seconds).
transceiver count.
Port goes down if the If the port is operating in Trunk mode and UDLD Include the port in native vlan.
port is excluded from is enabled, the port goes down if it is excluded
native vlan with UDLD from the native vlan.
feature enabled on it.
SNMP V3 walk may fail After failover, SNMP V3 walk may fail, as MIB After a failover, close the browser and re-open
after “initiate failover” browser and agent can become out of time and it. SNMPv2 works correctly.
command is issued. stop intercommunication.
OOB static IP entry After receiving an IP address from the DHCP Use a different IP address than the DHCP
cannot be the same as the server, the switch gives an error and will not address given.
DHCP assigned IP allow an attempt to add a static IP address and
address gateway that is the same as the DHCP IP address.
Release 4.2.2.3
Summary User Impact Workaround
Stack member units port Wrong id for the power LED is displayed. None
display is missing in
web GUI.
WebUI sFlow Polling sFlow>Sampler configuration and sFlow>Poll None
page issues. Configuration don't work for ports Gig1/0/1 -
1/0/9.
Release 4.2.1.3
Summary User Impact Workaround
"show interfaces Some general mode VLANs tagged to the Use “show vlan” command to interfaces. No
switchport " command interface may not be displayed using this other workaround.
shows incorrect General command.
Mode Tagged VLANs
value
Release 4.2.0.4
Summary User Impact Workaround
File modification date & When internal files are modified, they do not get None
time is not getting the current time stamp.
updated with current
time & date.
SNMP walk is not SNMP walk on the root port times out. Do not do SNMP walks using root port.
successful while doing
walk on root port.
FIP sessions are getting Users are unlikely to change either the default Do not change the FIP VLAN while sessions
disconnected for VLAN VLAN or the FIP VLAN while sessions are are established. The reason is that after a
switchport mode change active. VLAN is re-assigned or even changed to
with default vlan general mode, the sessions will of course be
settings. disrupted since the FIP snooping occurs on the
VLAN and any change in this will cause
problems on the Cisco Nexus side and will
require an interruption and reestablishment of
the addressing from the CNAs on up.
OpenManage displays After the browser session timeout (default 10 Disregard the time in this GUI message.
incorrect session timeout minutes), OpenManage displays incorrect session
duration when using timeout duration in the message "Your session
secure HTTP had been inactive for more than 240 minutes",
which is the actual setting for telnet and ssh.
However, the actual timeout occurs after the
default period of 10 minutes, so the GUI message
is incorrect.
Cannot disable the SFS Even with SFS allow-downgrade disabled, the Always make sure the master has the wanted
"allow-downgrade" master will still push the older firmware to a version loaded.
feature stack member running a newer version of code.
Console port locks up Radius authenticated Telnet login attempt when Wait for timeout or ensure Radius server is
when awaiting telnet Radius daemon stopped, causes console port to reachable.
Radius response be temporarily blocked until Radius timeout
expires.
Flowcontrol is in inactive Flowcontrol gets automatically disabled and if Re-enable Flowcontrol on PCM6220 switch.
state when connected to the ports have a need for Flowcontrol, there will
Partner(PCM6220) with be no pause frames sent.
combo ports.
PC7048P, in a stack will The stack will stop passing traffic if all switches If this situation happens, it is recommended
error out when all in the stack are rebooted simultaneously. that each power switch be rebooted in sequence
rebooted at the same with a four to five minute interval between
time. each reboot.
Jumbo frames cause Transmit Errors is seen on port channel, but not None – Inaccurate transmit errors do not cause
transmit errors on port on the members of the port channel. Counters functional issues.
channel remain inaccurate.
PC8024F Stacking - CLI/WebUI shows the stack-ports counters value None – Stack-Ports counter values as zero
CLI/WebUI : stack-ports as zero after stack is formed. doesn’t affect the PC8024F stacking
counters value is always functionality.
zero
CLI command "no snmp- CLI command “no snmp-server community- None
server community- group” is not available.
group" doesn't work
Dot1x ias local The internal database feature, which is a Dell Use any other form of dot1x authentication.
authentication method specific feature, is not working correctly because
not working this feature requires a user to authenticate using
MD5, which is not supported by Windows at this
time.
"ipv6 pim join-prune CLI command “"ipv6 pim join-prune interval 30" None
interval" command is not does not change the default interval value from
working 60
Incorrect status being When 8024F combo ports 21 and 22 are used for None
reported with show stacking, the show interfaces status command
interfaces commands and show interfaces media-type commands report
the status to be Detached and Down.
Websense: Order of The order that the commands “switchport mode None.
switchport commands in general” and “switchport general allowed vlan”
running-config changed, are displayed in the running config has been
Impacts scripts changed so that now the “allowed” command is
first. This may cause problems with customer’s
scripts that expect a certain order in the “show
running-config” output.
The “show dot1x The User Guide states that there is a “show dot1x Use the “show dot1x interface statistics”
statistics” command statistics” command for displaying dot1x command.
within the User Guide is statistics on the switch when the actual command
actually “show dot1x for doing this is “show dot1x interface statistics”.
interface statistics” This can be frustrating to the customer if he has
command from the CLI. referenced the User Guide to look up the
supposed correct command.
Release 4.1.1.9
Summary User Impact Workaround
LLPF is not supported The hardware functionality needed to support Upgrade to a switch that supports LLPF like a
on the PCM6220 switch LLPF is not available on the PCM6220 switch. PCM6348 switch.
Traffic led solid green Setting advertisement from other switches or IXIA None – Traffic LED Solid Green do not cause
with 1Gb and 100Mb of 1Gb or 100Mb link speeds to 10G links on any functional issues.
link speeds on 8024, 8024F results in link up and traffic led to be
PC8024/PC8024F solid green.
Config Lost for the On boot up, the switch gives an error and rejects Remove port configuration of 10G module
Portchannel on all the config for the portchannel as well as the before removing the module from the bay and
removing a 2 Port 10 G TenGig interfaces in Bay1. reboot the switch.
Module on the
PCM8024 switch
Release 4.1.0.19
Summary User Impact Workaround
Log message output snmpwalk will report error log message related to None – error messages do not cause functional
CPU-port and vlan routing port issues.
Secure HTTP Random Under System Management -> Secure HTTP, The CLI must be used to generate
Characters random characters maybe populating some of the certifications.
fields.
Release 6.1.0.6
Description User Impact
CPLD Update on Stacked switches. Low
CPLD update using the command (update cpld) will take at least
3 minutes to complete and then reboot the switch. Also, the
CPLD update command from Master unit in the stack will
update the CPLD code only in the Master switch. User has to
update the CPLD code on other members of the stack
individually.
Workaround
None
Release 6.1.0.1
Description User Impact
When PBR route maps and ACLs are configured on the Medium
same interface, ACL rules are treated as lower precedence Even though ACLs are configured with higher priority, PBR
than PBR. rules are processed first.
Workaround
None – PBR route maps and ACL access-groups should not be
configured on the same interface as they have potential to
interfere with each other.
PBR route map counters are not incremented Not all PBR route maps are configured in the hardware. The
system optimizes away route maps whose decision logic always
results in falling through to the next route map. This includes
deny ACLs in permit route maps and all ACLs in deny route
maps. PBR counters are not incremented for “fall-through”
ACLs in the above route maps.
Workaround
None
The maximum detection limit for storm-control is 2Gbps. Low
Rates configured in excess of this limit will not detect traffc A 2 Gbps will cover a wide variety of situations where storm
exceeding for the configured type. This limitation applies to control is likely to be deployed (at the edge of the network),
all types of storm-control and includes broadcast, multicast including all 1G links.
and unknown unicast.
Workaround
Add a rate-limit ACL with the appropriate limit. ACLs can be
configured to log or drop exceeds traffic.
Release 6.0.1.3
Description User Impact
The max packet size for traceroute is limited to 39936 and Low
size is limited to 13000 for ping. This applies to Ping and Traceroute are used only during trouble shooting
configuration from CLI, WEB and SNMP. Standard MIB as
per RFC 2925 specifies the value as 65507 but snmpset will Workaround
fail if a value above 39936 for traceroute and above 13000
for is configured. Use the values actually supported and not MIB specified max
values.
Legacy phones that support only 10BaseT without auto- Low
Release 6.0.0.8
Description User Impact
Downgrade to 5.1 and prior versions of code may cause the Medium
5.1 code to crash if any EEE configuration is present in the Switch will reboot after downgrade.
startup configuration. This is a limitation of the 5.1 code.
Workaround
When the switch reboots after the crash, boot into the 6.0 code
contained in the backup image. Remove all non-default EEE
configurations from the startup configuration prior to
downgrade.
A link flap is observed on the partner if the link is connected Low
to OOB port of the switch and switch is reloaded. The link flap is observed once on the partner switch
Workaround
Remove the SFP+ DAC cable and use the no shut command to
re-enable the port.
40G port on N40xx series switches fails to link up when you Moderate
insert the following transceivers along with cable into the QSFP ports on the switch are not operational.
switch.
0MV31 Workaround
RF2MY Reboot the switch to recover the failed QSFP ports.
Use of DCPDP is not recommended in 6.0 firmware. Upon Upon peer link failure DCPDP (if enabled) will transition the
peer link failure DCPDP (if Enabled) will transition the roles of MLAG peer devices to none and bring DOWN the
roles of MLAG peer devices to “none” and bring DOWN MLAG interfaces on both MLAG peer devices. This MLAG
the MLAG interfaces on both MLAG peer devices. peers recover once the peer link is UP.
Release 5.1.3.7
Description User Impact
Limitations and Restrictions for Private VLAN Operations These are documentation limitations and
(also found in the User Configuration Guide) restrictions found in the User Configuration
Guide also provided here for convenience.
• Only a single isolated VLAN can be associated with a primary
VLAN.
• Multiple community VLANs can be associated with a primary
Once mrouter port is identified the traffic is forwarded to mrouter port and
listener ports only.
The M6220 floods unregistered IPv4 and IPv6 multicast traffic on all the
ports.
ICMP Redirects are a hardware function and not processed by the CPU Hardware limitation.
There has been no change to the functional behavior of the switch not to
generate ICMP redirects when primary and secondary IP addresses with
different subnets are configured on same VLAN and traffic is destined from
primary to secondary subnet on the same VLAN. This is a hardware
limitation and as of today we do not have a way to change this behavior of
detecting that the traffic is destined to a secondary IP address on same VLAN
and not to generate ICMP redirects.
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 Medium
CPU processing load for 5 – 10 seconds. 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 Moderate
flooded when a multicast stream is 'first' seen on a VLAN. There will be some flooding of multicast
traffic
Release 5.0.1.3
System – 5.0.1.3
Stacking
Description User Impact
Under certain conditions 5 or more ports Low
identified as stacking ports can cause This problem happens infrequently and setting those ports back to Ethernet mode
transmission errors even if the stacking has corrected the problem.
links are not up.
Release 5.0.0.4
System – 5.0.0.4
System
Description User Impact
8100 switches increment “Internal MAC Low
Rx Errors” counter, when packets are For typical IP networks this problem won't be seen because the length
received with (size > 1518) and (size <= field/Ethertype will contain a valid value.
MTU size), and the packet contains an
invalid FCS or code error detected or an
IEEE length check error
Web
Description User Impact
The device manager GUI does not Moderate – Multiple errors are displayed when trying to bring up the device GUI
support IE9 at this time. with IE9.
Workaround: The User must use an Internet Explorer version prior to IE9 with the
GUI.
Note: This is not a limitation if running Release 5.1.0.1 or later versions of
firmware.
iSCSI
Description User Impact
“show iscsi sessions” command does not Moderate –
display established sessions on
M8024/M8024-k/PC8024/PC8024F Workaround: Configure partner devices to send tagged, not priority tagged
platforms. traffic.
Username : asd
ssh-dss
AAAAB3NzaC1kc3MAAACBAJRwUAD3AuRACp1MObBeh1AgyZb18wf9Bt
dip+t+1CbAqiqNEh4lBiew184DSKk0T6SnSSXuCN+bJnQPxJeiQt+OFnmjiYhn
HcvI04Q5KnQhloZcEFgSsmQ7zJnReWtLvUQI0QvBIStanzedmQVGHvDrQ5X
2R729ToSH0ibBrnYtAAAAFQDNord7S9EJvUkKKxVBpWE6/skCmQAAAIB
MjMO+BPP5KXzNWfZhqAhxBSoBvif/z6pzi9xWLlYy99A03zmRYCpcGIoLW
iRHsR7NVpxFqwbqvez8KS0CDJ5aoKKLrpBlpg5ETkYEew/uTZ14lQQRBrzPw
GBfxvTXKCWiI2j5KFa/WKLSnmWJX0/98qpxW/lMXoXsA9iK4pnMKwAAAI
B4Jrt6jmoLybpzgOPOI0DsJ7jQwWacinD0jliz8k+qzCpanhd2wH+DEdj/xO2sFR
fnYlME3hmXoB+7NByVUtheVjuQ2CWhcGFIKm9tbuPC6DtXh1xxT0NJ7rspv
Lgb0s6y/0tk+94ZP5RCoAtLZ7wirShy3/KJ4RE0y2SFZjIVjQ==
Fingerprint : d9:d1:21:ad:26:41:ba:43:b1:dc:5c:6c:b9:57:07:6c
SSH RSA or DSA keys can be generated by using the ssh-keygen command on a
Unix system or with other publicly available utilities.
Broadcom NIC link always stays up Low- This is works as designed and is necessary for new features for 12G.
within the m8024-k status even after The Broadcom NIC 57810S never reports to the internal switch that the link is
disabling server port through device down because it needs the link to be up so that internal communications can
Release 4.2.0.4
Layer 2 – 4.2.0.4
802.1x Authentication
Description User Impact
Windows Vista® Authentication - The Low
Windows Vista® client could fail to Workaround:
authenticate properly when the option to 1. In Control Panel Network Connections, right-click on the desired
cache user credentials is selected. Local Area Connection and select Properties.
2. In the Properties window, select the Authentication tab.
3. Deselect the checkbox for Cache user information for subsequent
connections to this network.
4. Click OK.
The maximum number of 802.1x clients Low – most deployments will have at most 2 802.1x clients per physical port.
per port is 4. Note: If running Release 5.1.0.1 or later version of firmware, the maximum
number is 24.
The maximum number of configurable Low as most deployments use a single traffic class. Some limited deployments
traffic classes is 7. may use up to 3 traffic classes.
MAC Filtering
Description User Impact
Maximum number of unicast static The maximum number of unicast MAC and source port filtering entries is 20.
filtering entries
Maximum number of multicast static The maximum number of multicast MAC and source port filtering entries is 20.
filtering entries The maximum number of multicast MAC and destination port filtering entries is
256.
Static multicast MAC address table Users must enable MAC filtering using the mac addr-table multicast filtering
entries do not show with show command command to enable filtering. Static MAC multicast forwarding entries will then
be shown.
LACP
Description User Impact
LAGs Supported Number of LAGs supported:
128 total LAGs of which up to 72 may be dynamic LAGs. Up to 144 ports can be
assigned to dynamic LAGs. The PCM8024 supports 12 LAGs with up to 24 ports
assigned to dynamic LAGs.
IGMP Snooping
Description User Impact
No command to identify external IGMP There is no specific command to identify an external IGMP querier.
querier Administrators can use the show ip igmp snooping querier detail command or
the show ip igmp snooping querier vlan command to display information about
snooping queriers.
Layer 3 – 4.2.0.4
IPv6 MTU
Description User Impact
IPv6 Fragmentation Support The switch is not fragmenting the datagram and forwards even when the IP MTU
of the forwarding interface is set to a lower value (than the datagram size).
IPv6 frames are not allowed to be fragmented. IPv6 frames forwarded in silicon
can be up to the lesser of 9216 octets or the link MTU. These frames are
forwarded by the switching silicon with no effect. If a frame exceeds the link
MTU for a port, it is discarded silently.
If a packet is sent to the CPU or originated on the CPU and it exceeds the IPv6
MTU, then the packet still will not be fragmented. Instead, an ICMP error
message is returned to the sender. The maximum IPv6 MTU is 1500 bytes.
Administrators are advised that when operating in an L2 switching
configuration with jumbo frames, to only adjust the link MTU and let the
system automatically adjust the IPv4/ IPv6 MTU based on the link MTU.
VRRP
Description User Impact
The maximum number of VRRP Users can scale VRRP higher than previously.
instances is 50.
Management – 4.2.0.4
CLI
Description User Impact
radius-server mode commands do not Low - None of the commands in radius-server mode support a "no" form except
have a "no" form. for the msgauth command. To reset values to the default, delete the server entry
and add it back.
The maximum command line length is Low - Entries greater than the maximum line length throw an error, e.g. using
1536 characters. multiple interface range qualifiers.
USB
Description User Impact
Dir command can only address top-level Minimal – users can move files to top-level directory easily
directory on USB stick
Only FAT32 formatted devices are Minimal – FAT32 devices are the de-facto standard for flash devices
supported.
When multiple partitions are present on Minimal – users will typically re-partition flash drives to maximize space.
the flash drive, only the first partition is
accessible.
File Management
Description User Impact
CLI Comment Character The '!' indicates the beginning of a comment. All characters following the '!' will
be treated as a comment (except when configuring a banner where the ! is
accepted at the beginning of a line)
Broadcom CNA only supports Low – Most users prefer automatic setup of CNAs
configuration of VLAN via VLAN The Broadcom CNA does not support manual configuration of VLAN. This
Discovery process means that customers who prefer to set up their FCoE network manually will not
be able to do so if using BRCM CNAs.
FIP snooping bridge does not forward Low – No supported FCF supports this configuration option.
the DCBX FIP tlv info from While working with QLogic, it is found that CNA sends two TLVs concerning the
configuration source FIP/FCoE traffic. It sends FIP TLV along with FCoE TLV with respective
priorities - in this case same priority for both. Although, it is not a normal use case
but can be used to have different treatment for control and data traffic. There can
be a use case where host or FCF can choose to create different priorities for
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
The 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 Low - When trying to accomplish FIP snooping over the stack, the eNode address
eNode in Ethernet VLAN 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.