======================================================================= Nortel Networks, Inc Updated: 5/25/99 Model 28115 Verion 2.0.4.6 ======================================================================= RELEASE SUMMARY: =============== This is a REV release. This release has incorporated bug fixes and feature enhancement after version 2.0.4.5. PLATFORMS SUPPORTED: =================== 28115/ADV and 28104 NOTES FOR UPGRADE: ================= VERSION OF PREVIOUS RELEASES: ============================ Verion 2.0.4 Date: 7/98 Version 2.0.4.1 Date: 8/98 Version 2.0.4.2 Date: 10/98 Version 2.0.4.3 Date: 12/98 Version 2.0.4.4 Date: 1/99 Version 2.0.4.5 Date: 4/99 COMPATIBILITY: ============= FEATURES ADDED IN THIS RELEASE: ============================== None FEATURES ADDED IN PREVIOUS RELEASES: =================================== Features added in 2.0.4.5 release: This version fixed the IP unmanageable problem totally. The bug was in switch driver directory. The code didn't do validity check in time, so for certain traffic which produces wrong data, it would corrupt the memory which unfortunately is the IEEERegTable. Features added in 2.0.4.4 release: The new feature added in this release is fast aging algorithm into spanning tree mode. In version 2.0.4.3 whenever there is a link down, a root port changed into a non-root port or when the switch send out tcn frame, it will flush the corresponding port's macstore to speed up spanning tree converge. This algorithm is a patch solution and it will not work with more complicated network configuration, e.g. 28k family switched mixed with 350 or other switches, etc. This version implemented fast aging according to RFC 802.1d standard, so the converge time should less then 1.5 munites for both broken a link or reconnect the link. Testing Note: In order to avoid multiple fast aging, this version uses a timer named fast_aging_on_timer: When fast_aging_on_timer is not set and Topology Change flag is set in Configuration Messages, Bridges start fast aging to age out dynamic entries. The fast_aging_on_timer will be set to false after 90 seconds. Within this time interval, switch will not start another fast aging event. So when testing convergence time, wait 90 seconds to start another link state change (topology change) event to get the accurate result. Features added in 2.0.4.3 release: 1. A solution to manually recover from the IP/SNMP problem without having to reset the switches. This is a feature to 'refresh' the Encapsulation entry in the IEEERegTable. Following are the steps to invoke this feature. *Go to Debug Menu (Ctrl DBG) *Go to "Encapsulation" submenu and return *Under the letter "l)" it 's "Write encap entry into IEEETB". Enter "l", you'll see the message "Encap entry is in IEEETB" appears, which indicates the action is completed. 2. This code has the ability to Enable/Disable an automatically refresh of the Encapsulate Entry in IEEERegTable feature. Following are the steps to invoke this feature. After reboot, this feature is disabled. *Go to Debug Menu (Ctrl DBG) *Go to "System" submenu and return *You'll see submenu item "Refresh IEEETable EncapEntry[Disable]". Move cursor to it and return to enable it. 3. A memory dump facility has been implemented. Following are the steps to invoke this feature. *Go to Debug Menu (ctrl DBG) *Find the submenu item "Memory Access". Select it and hit return. *You are now at the screen which has "Cmd>" only. Following are the formats to read memory. Cmd>r address e.g. Cmd>r 01c0a090 Address will start at 0x01ca090, followed by 16 bytes of data per line and up to 10 lines on the screen. *You can go up and down to see more content around this address by following the instructions on the screen. Features added in 2.0.4.2 release: 1. Multicast Outbound Filter: This feature is designed to run in spanning tree mode only. It provides the user the ability to direct multicast traffic according to the needs of the network application. The multicast filter is configured by going to the following menu: Configuration Parameters->Switch Parameters->Modify Multicast Steering Feature Multicast Steering Configuration Multicast Filtering Feature [Enabled] Multicast Address [01003c6b181e] Destination Port List 1 [17,18] Source Port List 1 [1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16] Destination Port List 2 [1] Source Port List 2 [17] Destination Port List 3 [] Source Port List 3 [] Destination Port List 4 [] Source Port List 4 [] Description of parameters: Multicast Filtering Feature [Enabled/Disabled] - Enables/disables this feature. When this option is selected, a "Confirm ?(y/n)" prompt will ask for confirmation. Enter a "y" to enable these filters or "n" to disable the filters. Multicast Address - The address that the user want to filter on. This address is specified as a single string, so if the multicast address that the user wish to filter on is 01 00 3c 6b 18 1e (hex), enter "01003c6b181e" at the prompt. Destination Port List 1 Source Port List 1 Destination Port List 2 Source Port List 2 Destination Port List 3 Source Port List 3 Destination Port List 4 Source Port List 4 - The port lists that the user want to filter on. For lists with more than one port, specify the list of ports separated with commas. For example, for a list containing 2,4,7,10, enter "2,4,7,10". To clear out the list, enter "0". Multicast filtering works by specifying lists of destination and source ports that the user want the traffic to go to and from. So, for example, if the user want the traffic to go from port 1 to port 2, in Destination Port List 1, enter "2" and Source Port List 1 enter "1". Up to three lists are provided so that the user can have flexibility with the filter definitions. This is useful when requiring three different lists of source ports directing traffic to different destinations. This code is port state sensitive, so ports in blocking mode will not forward packets with filters on them. Characteristics of the feature: 1) Overlaps in source port definitions will be resolved in reverse order. For example, if port 4 is defined in port list 1 to forward to port 2 and it is also defined in port list 2 to forward to port 3, then port 4 will forward to port 3.The last port list definition takes precedence. 2) The software does not check input for logic problems, ie. intentionally inserting loops. 3) Filters will take about 30 seconds to enable on bootup or topology change due to spanning tree. Check the Trace Log for the message "TopoStable" to know if filters are applied when there is a topology change. OLD FEATURES REMOVED IN THIS RELEASE: ==================================== None PROBLEMS RESOLVED IN THIS RELEASE: ================================= CR 103279: 28k v2.0.4.5 on 28104: Lost connectivity. The 28104 is pingable but not switches beyond it. CR 101842: MIB2 query of ifOutOctets provides invalid information. PROBLEMS RESOLVED IN PREVIOUS RELEASES: ====================================== Problems resolved in 2.0.4.5 release: CR 56823: Switch running code 2.0.3 becoming unmanageable. Version 2.0.4.3 has a patch solution for this problem. This version resolves the bug from the cause. Problems resolved in 2.0.4.3 release: CR 75355: 5 minutes to topologize with Spanning Tree When 28k family switches work with 350 switches, it takes 5 minutes for topology change converge in Spanning Tree. Problems resolved in 2.0.4.2 release: CR 57156: Cisco HSRP The Cisco HSRP enhancement in the 2.0.3 release interfered with the forwarding of HSRP frames to other devices on the network. CR 71452: Cisco HSRP Over a Trunk link between two 281xx, 58000 or 28200 switches, only the UMAC address from the HSRP protocol is learned but not the HSRP VMAC address. CR 51554: Topology For previous releases, when a TCN is detected, all ports will go into config mode. In this release, only particular port goes into config mode when a TCN has been detected, not the whole switch. CR 57647: Spanning Tree In previous versions of 2.0.x, when the primary path in Spanning Tree is lost, connectivity to the secondary link cannot be established until a broadcast frame is sent from the source. In this release, the Macstore of a port will be flushed when it changes from root port into non root port. CR 71054: MIB In previous versions when performing a MIB II query on interfaces.ifTable.ifEntry.ifInOctets, the switch returns invalid counts. CR 57336 Diagnostics Older versions of 28K I/O modules fails power up diagnostics loopback test intermittently. CR 57059 Expansion Port In previous 2.0.x releases, the 281xx expansion port will stop forwarding traffic, if the port is preconfigured to something other than 200mbps full duplex. Problems resolved in 2.0.4 release: CR 72713 TRAP Trap Receiver table is not aging out CR 57110 Year 2000 Compliance fix. KNOWN LIMITATIONS: ================= No additional known issues. For latest release note information, please go to Bay Networks web page. http://support.baynetworks.com/library (c) 1999 Nortel Networks. All rights reserved.