Dell PowerConnect 7024P, PowerConnect M6348, PowerConnect 7048R, PowerConnect 7024F, PowerConnect 8024F Manual
...
Dell™ PowerConnect™ 8132/8164/8132F/8164F/7024/7048/7024P/7048P/7024F/7048R/ 7048R-RA/8024/8024F/M6220/M6348/M8024/M8024-k
PowerConnect
5.1.1.7 Firmware Release Notes
Date: July 2013
System Firmware Version 5.1.1.7
Information in this document is subject to change without notice. © 2003 – 2013 Dell Inc. All rights reserved.
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 |
|
I n t r o d u c t i o n |
1 |
G l obal Sup port |
1 |
Fi rmw are Speci fi cati ons |
1 |
Fi rmw are Upgrade |
2 |
Fi rmw are Dow ngrade |
3 |
Boot C ode Dow ngrade |
4 |
Hardw are Support ed |
4 |
Supp ort Matri x |
5 |
Supp orted Fi rmw are Functi o nal i t y |
6 |
Ad d ed Fu ncti on al i t y i n thi s R el eas e |
7 |
Cha nge d Fun cti on al i t y i n thi s Rel ea se |
14 |
I ssues Res ol ve d |
22 |
CLI Ref eren ce G ui de Up dates |
55 |
User’ s Confi g urat i on G ui de Up date s |
59 |
Know n I ssues |
61 |
Know n Restri cti ons and Li mi tati on s |
70 |
S ystem – 5 . 0 . 1 . 3 |
71 |
S ystem – 5 . 0 . 0 . 4 |
71 |
Manageme nt – 4 . 2 . 1 . 3 |
72 |
La yer 2 – 4 . 2 . 0 . 4 |
73 |
La yer 3 – 4 . 2 . 0 . 4 |
74 |
Manageme nt – 4 . 2 . 0 . 4 |
74 |
Data C enter – 4 . 2 . 0 . 4 |
75 |
End of R el ea se N otes |
76 |
2 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
Introduction
This document provides specific information for the Dell PowerConnect 8132/8164/8132F/8164F/7024/7048/7024P/7048P/7024F/7048R/7048R-RA/8024/8024F/M6220/M6348/M8024/M8024-k switches firmware version 5.1.1.7.
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 |
|||||
PC8100v5.1.1.7.stk |
|
5.1.1.7 |
July 2013 |
|||||
PCM6220v5.1.1.7.stk |
|
5.1.1.7 |
July 2013 |
|||||
PC7000_M6348v5.1.1.7.stk |
5.1.1.7 |
July 2013 |
||||||
PC8024v5.1.1.7.stk |
|
5.1.1.7 |
July 2013 |
|||||
PCM8024v5.1.1.7.stk |
|
5.1.1.7 |
July 2013 |
|||||
PCM8024kv5.1.1.7.stk |
|
5.1.1.7 |
July 2013 |
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version Numbering Convention |
|
|
Version number |
|
|
|
|
|
Description |
|
|
PowerConnect |
5 |
1 |
1 |
|
7 |
Four part version number |
|
|
Series |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Denotes the build number. |
|
|
|
|
|
|
|
|
Denotes an ad hoc release of the product software. |
|
|
|
|
|
|
|
|
Denotes a scheduled maintenance release of the product software. |
||
|
|
|
|
|
|
Denotes a major version number. |
|
|
System Firmware Version 5.1.1.7 |
Page 1 |
Firmware Upgrade
NOTE: Administrators upgrading PowerConnect 7024/7048/7024P/7048P/7024F/ 7048R/7048R-RA/8024/8024F/M6220/M6348/M8024/M8024k switches from 2.x.x.x or 3.x.x.x or 4.x.x.x or 5.x.x.x versions of firmware MUST follow the instructions documented in the Upgrading PowerConnect Switches from Version 2.x.x.x or 3.x.x.x or 4.x.x.x or 5.x.x.x to 5.1.1.7 Firmware procedure. Failure to follow the procedures described in that document when upgrading from 2.x.x.x or 3.x.x.x or 4.x.x.x or 5.x.x.x firmware may result in an inoperable switch!
NOTE: After upgrading the switch firmware version to 5.1.1.7, the CPLD (Complex Programmable Logic Device) code update is required on M8024-k and PC8024/PC8024F switches via serial console if switch is running with the older CPLD version. The latest CPLD version available for M8024k switch is Version 5 and for PC8024/PC8024F switch is Version 6. Administrators upgrading PowerConnect 8024/8024F/M8024k switches MUST follow the CPLD update instructions documented in the Upgrading PowerConnect
Switches from Version 2.x.x.x or 3.x.x.x or 4.x.x.x or 5.x.x.x to 5.1.1.7 Firmware procedure.
NOTE: Administrators upgrading PowerConnect 8132/8164/8132F/8164F switches MUST follow the instructions documented in the Upgrading PowerConnect
8132_8164_8132F_8164F switches from Version 5.x.x.x to 5.1.1.7
Firmware procedure. Failure to follow the procedures described in that document when upgrading firmware may result in an inoperable switch!
NOTE: OMNM (Open Manage Network Manager) v5.2 SP1 supports firmware management of PowerConnect 7024/7048/7024P/7048P/7024F/7048R/7048R- RA/8024/8024F/M6220/M6348/M8024/M8024-k to deploy the firmware version 4.1.x.x or later. OMNM v5.2 SP1 supports PowerConnect 8132/8164/8132F/8164F to deploy the firmware version 5.0.0.4
2 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
Firmware Downgrade
Downgrading from 5.1.1.7 to an earlier release is supported on most PowerConnect series switches (except PC81xx series
with B1 CPU versions, see note below); however, migration of configuration information from a later release to an earlier release is not supported. 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 not enabled by default. If downgrading a stack, be sure to enable auto-downgrade before activating the earlier versions of firmware on the stack master.
Recent versions of the PowerConnect 81xx series switches support newer versions of CPU (B1). The B1 version of CPU requires firmware release version 5.1.0.1 or later and cannot be downgraded to earlier firmware releases. In addition, if this unit is to be deployed as a member within a stack, the entire stack will be required to run 5.1.0.1 or later firmware. Here are some steps to help determine what CPU is in the PowerConnect 8100 Series switch:
1.Run show version from the CLI prompt.
2.If there is no CPU version line, then the stack is running 5.0.x.x firmware. Since 5.0.x.x can only run on A1 CPU switches, then all switches in the stack (or a standalone) contain A1 CPUs.
3.If there is a CPU version line (like below):
CPU Version....................... XLP308H-A1
(It will display the CPU version in the last two characters - either A1 or B1).
4.On a stack, run show version m where m is the unit number assigned to the stack member to see each CPU version for each member in the stack.
In addition here are the part numbers for reference:
Part Numbers for PowerConnect 81xx |
A1 CPU |
B1 CPU |
|
PowerConnect 8132 |
(US, Canada, Mexico, South America) |
TRJ78 |
PTM0F |
PowerConnect 8132 |
(all other countries) |
0C90P |
X20W5 |
PowerConnect 8132F (US, Canada, Mexico, South America) |
W0HV1 |
NWHGV |
|
PowerConnect 8132F (all other countries) |
7D1GN |
KWHG3 |
|
PowerConnect 8164 |
(US, Canada, Mexico, South America) |
H0F6C |
N00C1 |
PowerConnect 8164 |
(all other countries) |
P8RHX |
Y2FJ0 |
PowerConnect 8164F (US, Canada, Mexico, South America) |
VTWN8 |
4PHP2 |
|
PowerConnect 8164F (all other countries) |
1JWM5 |
8KHT1 |
|
Recent versions of the PowerConnect M8024-K modular switches have hardware changes that require firmware version 4.1.0.19 or higher. PowerConnect M8024-K with a new PPID label cannot be downgraded to the firmware version below 4.1.0.19. If a downgrade is attempted, the firmware activation procedure will detect that earlier firmware version is not compatible with the switch hardware and abort the activation procedure. Any PowerConnect M8024-K with the old PPID label can accept any version of the switch firmware.
MODEL |
OLD PPID |
NEW PPID |
|
M8024K |
2F07F A00 |
2F07F A01 |
|
|
|
||
57821 A00 |
57821 A01 |
||
|
|||
|
|
|
System Firmware Version 5.1.1.7 |
Page 3 |
Boot Code Downgrade
Never downgrade the boot code! The 5.1.1.7 boot code supports all earlier versions of firmware and never needs downgrading.
Hardware Supported
•Dell PowerConnect 8132 Ethernet Switch
•Dell PowerConnect 8164 Ethernet Switch
•Dell PowerConnect 8132F Ethernet Switch
•Dell PowerConnect 8164F Ethernet Switch
•Dell PowerConnect M6220 Ethernet Switch
•Dell PowerConnect M6348 Ethernet Switch
•Dell PowerConnect 7024 Ethernet Switch
•Dell PowerConnect 7048 Ethernet Switch
•Dell PowerConnect 7024P Ethernet Switch
•Dell PowerConnect 7048P Ethernet Switch
•Dell PowerConnect 7024F Ethernet Switch
•Dell PowerConnect 7048R Ethernet Switch
•Dell PowerConnect 7048R-RA Ethernet Switch
•Dell PowerConnect 8024 Ethernet Switch
•Dell PowerConnect 8024F Ethernet Switch
•Dell PowerConnect M8024 Ethernet Switch
•Dell PowerConnect M8024-k Ethernet Switch
4 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
Support Matrix
Since not all functionality is supported on all switches, the following matrix identifies the major differences among the PowerConnect switch models. A check mark indicates support for the feature. All other features listed in the release notes are supported on all switches.
|
Feature/Switch |
Priority |
DCBx |
|
ETS |
PoE+ |
iSCSI |
USB |
grEEEn |
|
Hot |
WRED |
|
|
|
Flow |
|
|
|
|
Optimization |
|
Ethernet |
|
Swap |
|
|
|
|
|
|
|
|
|
|
|
|||||
|
|
Control |
|
|
|
|
|
|
|
|
Cards |
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
M6220 Ethernet |
|
|
|
|
|
|
|
|
|
|
|
|
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
M6348 Ethernet |
|
|
|
|
|
|
|
|
|
|||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
7024 Ethernet |
|
|
|
|
|
|
||||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
7048 Ethernet |
|
|
|
|
|
|
||||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
7024P Ethernet |
|
|
|
|
|
|||||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
7048P Ethernet |
|
|
|
|
|
|||||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
7024F Ethernet |
|
|
|
|
|
|
||||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
7048R Ethernet |
|
|
|
|
|
|
||||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
7048R-RA Ethernet |
|
|
|
|
|
|
||||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
8024 Ethernet |
|
|
|
|
|
|
|
|||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
8024F Ethernet |
|
|
|
|
|
|
|
|||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
M8024 Ethernet |
|
|
|
|
|
|
|
|
|
|||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
M8024-k Ethernet |
|
|
|
|
|
|
|
|||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
8132 Ethernet |
|
|
|
|||||||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
8164 Ethernet |
|
|
|
|||||||||
|
Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
Dell PowerConnect |
|
|
|
|
|
|
|
|
|
|
|
|
|
8132F/8164F |
|
|
|
|||||||||
|
Ethernet Switch |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
System Firmware Version 5.1.1.7 |
|
|
|
|
|
|
|
|
|
Page 5 |
|
|
Supported Firmware Functionality
For more details regarding all the supported firmware features and functionality, please refer to the Dell PowerConnect Series CLI Reference Guide and the Dell PowerConnect Series User’s Configuration Guide.
6 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
Added Functionality in this Release
This section contains a list of features added in this release that are new for at least one switch listed in the Hardware Supported section above.
Release 5.1.1.7
No Added Functionality in this Release
Release 5.1.0.1
IGMP Snooping Improvements
IP Multicast Enhancements
Support for B1 CPU – only on PC8100 series
New Browser Support
•Mozilla Firefox 14
•Internet Explorer 9
•Google Chrome 21
Static Route Maximum Increased to 512 (for all switches except for M6220 series)
USB Auto-configuration expanded for multiple MAC Address support
Ability to reset stack port counters
Increased Maximum number of dot1x clients per port to 24
Commands to remove signed certificates/Keys
Support for Additional transceivers/optics
Release 5.0.1.3
Added PoE DC Disconnect HW support – on PC7000 series
Release 5.0.0.4
Added Native EEE Support for the PC8100 10GBaseT Ports
802.1Qaz (ETS) – on 8100 series
Support for 40 Gig (QSFP+) interfaces
Support for Bootcode upgrade from pre-4.x image to 5.x image without manual system reset.
Local Preference for LAG
Private VLAN
CLI output filtering
Routing Improvements for OSPF
UDLD
Administrative Profiles
AAA Authorization
TACACS+ Accounting
Stacking over QSFP+ ports
QSFP+ diagnostics
sFlow Support on Port Channels
System Firmware Version 5.1.1.7 |
Page 7 |
Release 4.2.2.3
No Added Functionality in this Release
Release 4.2.1.3
No Added Functionality in this Release
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.1.9
No Added Functionality in this Release
Release 4.1.0.19
Media-type CLI command
Added new command "media-type" to configure an interface to select the specified media on a combo port. It is recommended the administrators select the specific media type for the particular type of network connection they expect to use. Users may observe a single port flap when the media type is changed from RJ45 to auto-select RJ45 and only the corresponding SFP port is enabled. Refer to the CLI Reference Guide Updates section below for the complete syntax.
Release 4.1.0.6
IPv4-Only Mode Optimization
PowerConnect switches allocate the maximum sizes for routing tables (and others, as applicable) for both IPv4 and IPv6. Switch Performance Optimization allows the operator to optimize the allocation of switch silicon tables for either IPv4 only or mixed IPv4/IPv6 operation. The template specified limits are enforced by routing components when routes are being learned. When IPv4 only mode is selected, the following capabilities are disabled:
•DHCPv6 relay
•DHCPv6 server
•IPv6 routing/forwarding
•OSPFv3
•IPv6 Neighbor Discovery
•Configured v6-over-v4 tunnels
•Automatic (6to4) tunnels
8 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
•IPv6 Multicast
A reboot is required when changing to or from IPv4 mode.
Auto-Install
USB based auto-install is an easy way to quickly bring up a switch with a known configuration. Network based autoinstall 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 powerconnect.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 powerconnect.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.
When auto-install downloads a firmware image to switch memory, it compares the version to the current switch image. If different, the image in memory is copied to the switch backup image and activation of the image is attempted. If activation succeeds, the switch is rebooted and auto-install then attempts configuration file download.
Auto-install configuration files are executed as a script. For more details on Auto-Install, refer to the User’s Guide.
Link Local Protocol Filtering
Link Local Protocol Filtering blocks Cisco link local protocols from being flooded in the network. By default, PowerConnect switches process and respond to Cisco CDP packets. However, in networks where this capability is not desirable or other Cisco proprietary packets are flooded over the network, the administrator can disable flooding of Cisco link local protocols. The following table identifies the matching criteria for filtering Cisco proprietary packets:
|
Rule Type |
Rule Purpose |
|
Blocked Destination |
|
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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
System Firmware Version 5.1.1.7 |
|
|
|
|
Page 9 |
|
|
DHCP Server
The PowerConnect Series 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. The PowerConnect Series switches support GMRP as specified in IEEE 802.1Q 1998.
WRED
Weighted Random Early Drop is supported on certain PowerConnect series 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:
•scheduler type: strict vs. weighted
•minimum guaranteed bandwidth
•maximum allowed bandwidth (i.e. shaping)
•queue management type: tail drop vs. WRED
•tail drop parameters: threshold
•WRED parameters: minimum threshold, maximum threshold, drop probability
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.
Stack Firmware Synchronization
Stack firmware synchronization updates all stack members to the active firmware version on the master switch. Stack firmware synchronization is enabled by default. Stack firmware downgrade is enabled by default.
Multicast VLAN Registration
Multicast VLAN Registration provides a method of coalescing multicast traffic requested by users on multiple VLANs onto a single VLAN when carried over the network.
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 ports for use with the iSCSI protocol and tracks iSCSI sessions on the PowerConnect 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.
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.
10 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
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.
Connectivity Fault Management
Connectivity Fault Management performs Metro Ethernet maintenance functions. Dell PowerConnect CFM supports the following functions defined in IEEE 802.1ag Draft 8.1:
•Path discovery (link trace messages)
•Fault detection (continuity check message)
•Fault verification and isolation (loopback and link trace messages)
•Fault notification (alarm indication signal or SNMP trap).
Management IP Address Conflict Detection
Management IP address conflict detection actively looks for duplicate IP address assignment and logs conflicts. Only the last identified IPv4 address conflict is retained for display by a show command. Administrators may examine the inmemory logs or the output from a SYSLOG server to identify the historical IP address conflicts. If console logging is enabled for traps, a message will appear on the console indicating that an address conflict has occurred.
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. The PowerConnect switch does not implement SMTP server functionality.
802.1X Monitor Mode
Monitor mode is a special debug mode that assists network administrators in configuring 802.1X authenticators. Users attempting to authenticate using the authenticator are always granted access when monitor mode is enabled. All interactions with the supplicant and the authentication server are logged.
Administrators are cautioned against enabling monitor mode in a deployed network where 802.1X users may gain access to sensitive network resources.
Time Controlled ACLs
Time controlled ACLs allow administrators to apply ACLs based on the time of day. Both periodic and absolute time periods may be configured.
Administrators are cautioned that invalid (overlapping) periodic entries within a time range will prevent the time range from being applied. Administrators are advised to test their periodic entries and validate that they become active as expected before deploying the time ranges in a production network. Administrators can check if a time range is active by using the show time-range command.
It is recommended to enable ACL logging to ensure notice of ACL activation and de-activation.
System Firmware Version 5.1.1.7 |
Page 11 |
SNTP over IPv6
SNTP operates over IPv4 and IPv6 and may be configured using IPv4 or IPv6 addresses or DNS.
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
•Logout out from the switch
•Timed out logout from the switch
•Download file to the switch
•Upload file from the switch
•Remove file from the flash
•File changes on the flash
•Clear configuration
•Add or remove user
•Change user access level
Use of a SYSLOG server for monitoring network events is highly recommended.
Authentication
The PowerConnect switches support authentication via a number of methods. The methods are specified in named lists. Lists may be assigned to the enable and login access methods. The supported authentication methods are:
•Enable
•Line
•RADIUS
•TACACS
•IAS
•Local
•None
Methods are attempted in the order specified in the authentication list. If the authentication method rejects authentication, the user login is rejected. If an authentication method fails, e.g. unable to contact the authentication server, the next method in the list is attempted. The IAS, local and none methods can never fail so, if specified, must be last in the list.
The 802.1X authentication list cannot be named and only supports the RADIUS, IAS, or none authentication methods. The 802.1X authentication can only have a single method.
12 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
Internal Authentication Server
The PowerConnect Series switches support 802.1X authentication of network users from an internal authentication database. IAS users are given access to network resources. IAS is not a valid method for login or enable authentication.
The IAS database can be downloaded to the switch using the “ias-users” target in the copy command. The ias-users file takes the form of a configuration script, as follows:
configure
aaa ias-user username client-1 password my-password1
exit
aaa ias-user username client-2
password aa5c6c251fe374d5e306c62496c3bcf6 encrypted exit
aaa ias-user username 1f3ccb1157 password 1f3ccb1157
exit
IAS users may also be configured via the web interface.
DNS Client
The PowerConnect Series 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. The PowerConnect 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.
Port Profiles (CLI Macros)
The PowerConnect series of switches provides a convenient way to save and share common configurations through the use of CLI macros. A CLI macro is a set of commands having a unique name. When a CLI macro is applied, the CLI commands contained within the macro are executed and added to the running configuration. When the macro is applied to an interface, the existing interface configurations are not lost; the new commands are added to the interface and are saved in the running configuration.
A CLI macro may have keywords (variables) which are replaced by values provided when the macro is applied (up to 3 keywords per macro). Macros can be applied to specific interfaces, a range of interfaces, or the global configuration. Administrators may add their own macros or utilize the built-in macros.
Administrators are cautioned to ensure that a macro does not change command modes (e.g., change from interface configuration mode to global configuration mode).
The software includes 6 built-in macros:
•profile-global - the global configuration used to enable RSTP and loop guard.
•profile-desktop - the interface configuration for increased network security and reliability when connecting a desktop device, such as a PC, to a switch port.
•profile-phone - the interface configuration used when connecting a desktop device such as a PC with an IP phone to a switch port.
•profile-switch - the interface configuration used when connecting an access switch and a distribution switch or between access switches.
•profile-router - the interface configuration used when connecting the switch and a WAN router.
•profile-wireless- the interface configuration used when connecting the switch and a wireless access point. Built-in macros may not be deleted or altered by the operator.
System Firmware Version 5.1.1.7 |
Page 13 |
Changed Functionality in this Release
This section contains commentary on significant differences from previous releases of firmware on PowerConnect switches, e.g. the 8132/8164/8132F/8164F/7024/7048/7024P/7048P/7024F/7048R/7048R-RA/M6348/M6220/M8024/8024/8024F/M8024-k switches. Dell PowerConnect series switches closely conform to networking industry standard operational capabilities and administrative interfaces. The differences below should be studied carefully as attempting to configure or operate the PowerConnect switches in the same manner as for previous releases of firmware for PowerConnect 8132/8164/8132F/8164F/7024/7048/7024P/7048P/7024F/7048R/7048R-RA/M6348/M6220/M8024/8024/8024F/M8024-k switches may lead to unexpected results.
Release 5.1.1.7
No Changed Functionality in this Release
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 autoconfiguration 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
No Changed Functionality in this Release
Release 5.0.0.4
Stacking Ports Change
The maximum number of ports that can be configured for stacking per switch is limited to 8. This is done to ensure that the Hardware limits for maximum stack trunk members are not exceeded.
Stacking Over QSFP+ Ports
Stacking is supported over standard QSFP+ ports at either 1x10G or 4x10G mode. The ports must be configured as stacking ports.
14 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
Bootcode upgrade
Bootcode program is enhanced to automatically upgrade bootcode on migrating switches from pre-4.x version to 5.x version.
Release 4.2.2.3
No Changed Functionality in this Release
Release 4.2.1.3
VoIP Phone Limits
The limitation on the number of VoIP phones has been increased to 576 phones for the PowerConnect 7024/7048/7024P/7048P/7024F switches.
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.
Stacking Over Ethernet Ports only on M8024-k/8024/8024F
Stacking is supported over standard Ethernet SFP+ ports. The ports must be configured as stacking ports.
iSCSI Default Changes
iSCSI optimization is enabled by default. iSCSI optimization will reconfigure ports that are attached to Dell EqualLogic arrays to utilize spanning-tree portfast and unicast storm disable.
Release 4.1.1.9
No Changed Functionality in this Release
Release 4.1.0.19
PHY microcode upgrade process
The PHY microcode upgrade process has been enhanced to upgrade the PHY microcode to the latest version based on PHY revision. If the user experiences problems links on the combo ports after the upgrade completes, a reboot may be required in order to activate the new PHY firmware.
Asymmetric flow control
Asymmetric flow control is implemented for the PC8024X, PCM8024, PCM6348, PC70XX, and PCM8024-k switches. The switch does not generate pause frames when congested. It will honor pause frames as per industry standards.
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.
System Firmware Version 5.1.1.7 |
Page 15 |
The default authentication list for telnet and SSH has been changed to enableNetList. The only authentication method contained in enableNetList is enabled. The net effect of these two changes is that a password is required to enter privileged exec mode when using telnet or SSH.
Administrators wishing to maintain the previous PowerConnect behavior can set the default authentication list for telnet and SSH to enableList, which has the enable and none authentication methods (no password required to enter privileged exec mode). The following commands change the telnet authentication method to enableList.
console(config)# line telnet
console(config)# enable authentication enableList console(config)# exit
New Web Interface
The Web interface has been enhanced with new navigation features for ease of use.
CLI Syntax Changes
The CLI has changed significantly to be compatible with the PowerConnect switch standard CLI. Configurations for previous releases may not be compatible with this release and may need to be updated. Refer Configuration Migration document for more info.
Unit/Slot/Port Naming Conventions
In-band interfaces are named based on stack unit, slot, and port. Units range from 1-12. Slots range from 0-2. Ports range from 1-48. Slots for plug-in modules are numbered 1 and 2. Fixed ports belong to slot 0.
The service port is still addressed using the out-of-band keyword.
Management VLAN Deprecated
The PowerConnect series switches do not have an in-band management VLAN by default. Administrators can designate a VLAN for support of in-band management operations.
VLAN interface configuration mode enables routing
When executing the “interface vlan x” command, routing is automatically enabled on that VLAN.
Service/Out-of-band Ethernet Port Defaults to DHCP Addressing
By default, the service/out-of-band Ethernet port will attempt to obtain an address via DHCP.
NOTE: It is recommended that administrators attach the service/out-of- band Ethernet port to a physically separate network for out-of-band network management. The service port does not offer routing or switching capabilities nor does it offer enhanced protection from DOS attacks. Configure a VLAN on one or more in-band interfaces for management of PowerConnect switches over the operational network.
LACP Ports Inactive Until Attached
Ports in a LAG configured to use LACP (dynamic LAG) remain inactive (discard received traffic) until they become attached to the LAG. LACP ports that are attached to a LAG will enter the discarding state if they become detached from the LAG for any reason.
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.
16 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
NOTE: It is recommended that administrators disable portfast and autoportfast on physical interfaces configured in a LAG. Portfast and autoportfast can interfere with an interface entering into LAG mode on a reboot and possibly enable a packet storm.
Spanning Tree Changes
Administrators may assign more than 1024 VLANs to MSTP instances. Only VLANs that are configured on the switch will forward traffic.
The PowerConnect 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.
Link Speed |
Default Value |
10 Gb/s |
2000 |
1 Gb/s |
20000 |
100 Mb/s |
200000 |
10 Mb/s |
2000000 |
1 Mb/s |
20000000 |
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.
Link Speed |
Default Value |
10 Gb/s |
2000 |
1 Gb/s |
20000 |
100 Mb/s |
200000 |
10 Mb/s |
2000000 |
1 Mb/s |
20000000 |
User Configurable CLI Banners
Administrators may configure banners for the following: MOTD, login, and exec. The banners may consist of multiple lines of text. Each new line will consume an extra two characters (CR/LF) that count against the maximum length banner that can be configured.
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:
System Firmware Version 5.1.1.7 |
Page 17 |
By default, trunk ports participate in all VLANs. VLANs created after a trunk port is created are added to all trunk ports. VLANs deleted are removed from all trunk ports. The operator may configure a trunk port to explicitly disallow certain VLANs.
Native VLAN Configuration on Trunk Ports:
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 as well IIRC.
Switchport Mode Configuration Preserved:
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.
Timer Advertisement Learning:
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.
Ping-able VRRP Interfaces:
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.
Fragmentation and Reassembly:
18 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
Fragmentation and reassembly of VRRP packets is not supported.
DHCP Relay
The following enhancements have been made to the operation of DHCP Relay to bring the implementation into conformance with RFC 4649:
DHCPv6 Relay Circuit Id/Remote Id Types
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.
Relay Information Option:
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.
Relay Information Option Check:
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 Multiple Neighbor Support:
Multiple neighbors are supported on a single LLDP interface. The number of recognized neighbors is limited to two per port or 834 LLDP neighbors on a fully stacked set of switches. There is no restriction on the number of neighbors connected to an LLDP port. If more LLDP neighbors are present than are supported, then only the last two neighbors that communicate with the local LLDP interface are recognized and any additional neighbors are ignored.
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:
System Firmware Version 5.1.1.7 |
Page 19 |
Mandatory 802.1AB TLVs
•Chassis ID TLV (subtype shall default to MAC Address)
•Port ID TLV (subtype shall default to MAC address
•TTL TLV
•MAC/PHY configuration/status TLV
•End of LLDP PDU
Optional 802.1AB TLV
•Systems Capabilities TLV
•Power via MDI TLV
NOT recommended for transmission in order to conserve LLDPDU space.
Mandatory LLDP-MED TLVs
•LLDP-MED Capabilities TLV
This TLV allows the network connectivity device to definitively determine whether particular connected devices do support LLDP-MED and to discover which specific LLDP-MED TLVs the particular end point devices are capable of supporting as well as what specific device class they belong to.
•Network Policy TLV
This TLV allows the device to advertise its VLAN and associated Layer 2 priority and Layer 3 DSCP attributes which apply for a set of specific protocol applications on this port.
•Location Identification TLV
This TLV provides the advertisement of location identifier information Class II endpoint Devices. This is expected to be related to wire map or similar network topology data, such that the configuration of the network Connectivity device is able to uniquely identify the physical location of the connected MED endpoint.
•Extended Power-via-MDI TLV
This TLV allows for advanced power management between endpoints and network connectivity devices. It transmits fine grained power requirement details. This TLV provides significantly more value than the 802.1AB Power via MDI TLV.
•EEE TLV
The EEE TLV is used to exchange information about the EEE Data Link Layer capabilities. Devices that require longer wake up times prior to being able to accept data on their receive paths may use the Data Link Layer capabilities to negotiate for extended system wake up times from the transmitting link partner. This mechanism may allow for more or less aggressive energy saving modes.
Dynamic VLAN Assignment
Dynamic VLAN assignment is intended to support the connection of hosts to a router with enhanced levels of service, typically either security or QoS. This release supports dynamic VLAN assignment as assigned from the RADIUS server as part of port authentication. The following additional checks are performed in support of dynamic VLAN assignment:
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.
20 |
System Firmware Version 5.1.1.7 |
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes
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.
User configured banners (login, exec, MOTD) appear in the running config.
By default, auto-install supports image downgrade for network installs, specific version USB installs (using a .setup file), and stack firmware synchronization.
A comprehensible message and recommendation is issued when configuring multiple services (telnet, http, etc.) to listen on the same TCP port.
The terminal length command allows user control over terminal paging.
Simple Mode
The PowerConnect 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.
System Firmware Version 5.1.1.7 |
Page 21 |
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 5.1.1.7
Summary |
User Impact |
|
Resolution |
Affected Platforms |
|
Switch crashes in |
FRU service tag value updates |
|
Correct buffer overflow. |
PCM6220 |
|
tIomEvtMon() task once per |
from CMC might result in buffer |
|
|
PCM6348 |
|
week. |
overflow as service tag and |
|
|
PCM8024 |
|
|
other related tag fields are |
|
|
|
|
|
|
|
PCM8024-k |
|
|
|
updated in the switch. |
|
|
|
|
|
|
|
|
|
|
Switch crashes in tCptvPrtl |
Switch crash occurs in captive |
|
Corrected captive portal |
All 5.1 supported |
|
task. |
portal after a reload which |
|
initialization problem |
platforms |
|
|
brings down the entire switch |
|
|
|
|
Stack member crash with |
Switch crash occurs |
|
Corrected the SDM Template |
PC8132 |
|
“SDM Template mismatch” |
occasionally when an SDM |
|
ID problem so that invalid |
PC8132F |
|
error |
Template id mismatch occurs. |
|
SDM template ids will be |
PC8164 |
|
|
|
|
ignored. |
PC8164F |
|
Stack member crash when |
Switch crash occurs |
|
Corrected a stack data plane |
PC8132 |
|
“ISO count mismatch has |
occasionally when the stack unit |
|
communications problem. |
PC8132F |
|
been detected” |
detects that it is isolated. |
|
|
PC8164 |
|
|
|
|
|
PC8164F |
|
Stack member crash from |
Switch crash occurs |
|
Enhanced DMA retry logic to |
PC8132 |
|
DMA hang |
occasionally when packet DMA |
|
allow DMA status information |
PC8132F |
|
|
from the switching fabric to the |
|
to update completely. |
PC8164 |
|
|
CPU stops. |
|
|
PC8164F |
|
Stack member crash in |
Switch crash occurs |
|
Corrected multicast routing |
PC8132 |
|
mcastMapTask |
occasionally with routing and |
|
problem. |
PC8132F |
|
|
multicast traffic. |
|
|
PC8164 |
|
|
|
|
|
PC8164F |
|
Stack master can move on |
On a stack reload the stack |
|
Corrected stack master timing |
PC8132 |
|
stack reload |
master can move to a different |
|
problem when 10GBaseT |
PC8132F |
|
|
switch based on the plug-in |
|
plug-in modules are used. |
PC8164 |
|
|
modules being used. |
|
|
PC8164F |
|
|
|
|
|
|
|
iomEventLog() might result |
Communications error in the |
|
Corrected index range error on |
PCM6220 |
|
in switch crash |
m1000e Chassis CMC can result |
|
data received from the CMC |
PCM8024 |
|
|
in a crash. |
|
|
PCM8024K |
|
|
|
|
|
PCM6348 |
|
Switch crash in DHCP |
Switch crash in DHCP server |
|
Corrected memory corruption |
All 5.1 supported |
|
server task |
task |
|
problem. |
platforms |
|
Stack member crash in |
Switch crash in bcmRLINK task |
|
Corrected memory corruption |
PC8132 |
|
bcmRLINK task |
due to unit id being out of range |
|
in ATP process. |
PC8132F |
|
|
|
|
|
PC8164 |
|
|
|
|
|
PC8164F |
|
Stack member crash in |
Switch crash in DMA |
|
Corrected in problem in cache |
PC8132 |
|
DMA processing |
processing due to memory |
|
coherency which was causing |
PC8132F |
|
|
corruption |
|
data corruption. |
PC8164 |
|
|
|
|
|
PC8164F |
|
Port detection mechanism |
dot1qVlanFdbId SNMP object |
|
Corrected problem so that the |
All 5.1 supported |
|
fails with SNMP Query |
returns incremental indexes of |
|
object will return VLAN IDs |
platforms |
|
using Q-BRIDGE-MIB |
the VLANs. |
|
|
|
|
22 |
System Firmware Version 5.1.1.7 |
Loading...