Dell PowerConnect 8100 Release Notes - Page 58
Release 5.1.0.1, Release 5.0.1.3, Release 5.0.0.4
View all Dell PowerConnect 8100 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 58 highlights
User's Configuration Guide Updates The following table lists issues found in the User's Configuration Guide after publication: Release 5.1.0.1 Issue The following paragraphs need to be added to the User's Guides for all platforms except the PCM6220: 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. Warning: One of the modular ports is operating in stacking mode. Hotplug of a module requires system reboot. Failure to do so will make the system unstable! 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. 56 System Firmware Version 5.1.0.1