Dell PowerConnect 8100 Release Notes - Page 35
Release 4.2.0.4
View all Dell PowerConnect 8100 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 35 highlights
PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/ M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA Release Notes Dropped VLAN frames are included in Discards counters. PC7048 Combo ports are not passing traffic. Customer is really not able to use this counter to monitor their network outage activity. Combo ports are randomly not transmitting traffic, but receiving frames when media type preference set as SFP Corrected by not ignoring the dropped VLAN frames in the Discards counter All 4.2 supported platforms Corrected by adding a property to bypass the lane initialization when media-type preferences is set. PC70xx Order of switchport commands in running-config changed The "show running-config" command shows the detailed switchport configuration before the switchport mode. This caused problems with some scripts. Corrected the order of running- All 4.2 supported configuration output. platforms Release 4.2.0.4 Summary PowerConnect sFlow implementation is not per specification Using config wizard to setup 8024 causes iscsi error messages off out-of-band in console 8024 stack does not follow similar banner execution for console, telnet and ssh Simple Switch should have FC enabled by default OSPF error message after reboot User Impact sFlow implementation is not per specification Resolution Issues corrected and passes conformance test Doesn't affect any iscsi traffic. Constant log messages with the error "Can't create static rule". Issue is corrected. If a user logs in via console - motd and login banners are executed If a user logs in via ssh - only exec banner is executed If a user logs in via telnet - all 3 banners are executed FC not functional Behavior is now as follows: Add motd banner display for telnet connection before motd acknowledge question is asked. Remove motd banner after motd acknowledge question. FC is enabled by default in simple switch mode. With 128 IPv4 & IPv6 interfaces & OSFP configured a reboot caused the following error messages to be generated: Failed to send message to OSPF mapping thread in ospfMapRoutingEventChangeCallBack() Issue has been corrected. These lost events could lead to incorrect routing. Affected Platforms All 4.2 supported platforms PC8024 All 4.2 supported platforms All 4.2 supported platforms All 4.2 supported platforms System Firmware Version 5.1.0.1 Page 33