ExtremeWare Release Notes Software Version 6.2.1 Extreme Networks, Inc. 3585 Monroe Street Santa Clara, California 95051 (888) 257-3000 http://www.extremenetworks.
©2002 Extreme Networks, Inc. All rights reserved. Extreme Networks and BlackDiamond are registered trademarks of Extreme Networks, Inc. in the United States and certain other jurisdictions.
Contents ExtremeWare v6.2.1 Release Notes Overview 1 New Features in ExtremeWare 6.2 Features Added or Enhanced in v6.2.0 Features Added or Enhanced in v6.2.1 1 1 3 Supported Hardware BlackDiamond Module Support Alpine Module Support Summit Module Support GBIC Support 5 6 7 7 8 Features Unique to the “i” Chipset 8 Upgrading from ExtremeWare v6.1 to v6.2 Upgrading the BootROM Upgrading ExtremeWare Installing ExtremeWare 6.2.
Security and Access Policies Server Load Balancing Web Cache Redirection / Policy Based Routing NetFlow WEB Management - VISTA SNMP DHCP Server DLCS Virtual Chassis Issues Resolved in this Release General SNMP Server Load Balancing IGMP Snooping QoS iv - Contents 31 31 32 34 34 34 36 36 36 36 36 36 36 37 37 ExtremeWare v6.2.
Release Notes for ExtremeWare v6.2.1 Overview This document contains the following sections: • New features in ExtremeWare v6.2 • Supported hardware • “i” Chipset unique features • Instructions for upgrading from v6.1 • Supported limits • Clarifications, known behaviors, and problems For information on issues resolved from previous releases, you can obtain previous versions of release notes through a login account on the Extreme Networks Support web site at http://www.extremenetworks.com/support/support.
Release Notes for ExtremeWare v6.2.1 • MAC Address Security: MAC-based security allows you to control the way the FDB is learned and populated. By managing entries in the FDB, you can block, assign priority (queues), and control packet flows on a per-address basis. The new MAC address security feature allows you to limit the number of MAC addresses that can be learned on a virtual port. Once the learning limit has been reached, any additional addresses will be blocked.
New Features in ExtremeWare 6.2 Additionally, a load-shared group of ethernet ports can be backed up with a set of load shared redundant ethernet ports. Should a link go down in the active load shared group, the entire group will fail over to the redundant group. The commands for configuring this feature are described in detail in Chapter 4, “Configuring Slots and Ports on the Switch” in the ExtremeWare Software Command Reference Guide • BGP Enhancements: A number of enhancements were made to BGP support.
Release Notes for ExtremeWare v6.2.1 • Diagnostics: A number of enhancements have been made in ExtremeWare diagnostics. These include improved speed (decreased boot time) for the Fastpost diagnostic, improved error output, and adding some minor packet memory testing to the Normal level diagnostic.
Supported Hardware • SCP/SSH2 client: The new feature enables an Extreme Networks switch to function as an SSH2 client. This means you can connect from the switch to a remote device running an SSH2 server, and send commands to that device. You can also use SCP to transfer files to and from the remote device. See Chapter 3, “Managing the Switch” in the ExtremeWare Software Command Reference Guide for a detailed description of the commands related to this feature.
Release Notes for ExtremeWare v6.2.1 Extreme Switch Platform ExtremeWare Filename/Version BootRom Filename/Version Alpine 3808 v621b20.xtr or v621b20_ssh.xtr/v6.2.1b20 Ngboot72.bin*/ v7.2 Alpine 3804 v621b20.xtr or v621b20_ssh.xtr/v6.2.1b20 Ngboot72.bin*/ v7.2 Summit 7i/7iT v621b20.xtr or v621b20_ssh.xtr/v6.2.1b20 Ngboot72.bin*/ v7.2 Summit 1i/1iT v621b20.xtr or v621b20_ssh.xtr/v6.2.1b20 Ngboot72.bin*/ v7.2 Summit 5i/5iT/5iLX v621b20.xtr or v621b20_ssh.xtr/v6.2.1b20 Ngboot72.bin*/ v7.
Supported Hardware * BlackDiamond Module ExtremeWare v6.1.5 and above Support Uses "i" Chipset G6SX - G6LX Yes* No DC Power Supply** Yes N/A 110V AC Power Supply** Yes N/A As documented in Chapter 1 of the ExtremeWare Software User Guide v6.2.1 and within these release notes, some new features require that the "i" chipset also be present on the I/O module in order for the feature to function. Note: Mixed versions of the power supplies should not be installed in the same system.
Release Notes for ExtremeWare v6.2.1 GBIC Support The following table describes how each version of ExtremeWare interprets the media type of the installed GBIC, based on either the Vista web interface, or the show port config command. All versions correctly identify Parallel ID GBIC types; however, some versions do not correctly identify the Serial ID GBIC type because the Serial ID GBICs were introduced after the software was released.
Upgrading from ExtremeWare v6.1 to v6.2 • Extreme Automatic Protection Switching (EAPS) — Support for fast protection switching to layer 2 switches interconnected in an Ethernet ring topology.
Release Notes for ExtremeWare v6.2.1 Upgrading ExtremeWare Below are instructions specific to upgrading to, and downgrading from, ExtremeWare v6.2 for Summit, Alpine, and BlackDiamond switches. Upgrading Switches ExtremeWare v6.2 can read a stored configuration saved by ExtremeWare v6.X.
Upgrading from ExtremeWare v6.1 to v6.2 2 Reboot the switch. The previous configuration of the switch will be preserved going from the previous version of ExtremeWare to ExtremeWare v6.2.1. Verify that the switch is operating as expected. After verification, you may configure features specific to the current version of ExtremeWare. 3 Save the configuration to the primary space. Note: After upgrading from v6.1.9 to v 6.2.1, the IGMP snooping leave time-out value will be changed from 10 seconds to 0.
Release Notes for ExtremeWare v6.2.1 generated during the upgrade procedure. If you do not have the configuration file, re-configure the switch manually. Note: When downgrading to a previous version of ExtremeWare, ensure that the switch configuration matches that version of ExtremeWare or below. Pointing the configuration to a new version of ExtremeWare and using a previous version of ExtremeWare is not supported. You will get a warning message from the system when attempting to do so.
Supported Limits 7 If you have critical or major errors, save them into a text file and contact Extreme Technical Support. Error Message If you install an MSM with a BD6816 image onto a BD 6808 chassis, you may get an error message in the SYSLOG saying the image you are running isn’t supported, and the LED will light.. The message is part of the 6816/6808 download protection.
Release Notes for ExtremeWare v6.2.1 Metric Description Limit ESRP—number of instances Maximum number of ESRP supported VLANs for a single switch. 64 ESRP—number of ESRP groups Maximum number of ESRP groups within a broadcast domain 4 ESRP—number of VLANs in a single ESRP domain – Summit “i” series and Alpine Maximum number of VLANs that can be joined to 256 recommended; 2000 a single ESRP instance through an ESRP domain. max To obtain higher values see configuration notes.
Supported Limits Metric Description Limit IPX Access control lists Maximum number of Access Lists in which all rules utilize all available options worst case: 255 Logged Messages Maximum number of messages logged locally on the system. 1000 MAC-based VLANs—MAC addresses Maximum number of MAC addresses that can be downloaded to the switch when using MAC-based VLANs 7000 Mirroring—Mirrored ports Maximum number of ports that can be mirrored to the mirror port.
Release Notes for ExtremeWare v6.2.
Clarifications, Known Behaviors, and Problems Metric Description Limit VLANs—BlackDiamond 6816 Includes all VLANs plus sub VLANs, super VLANs, etc. 600 VLANs—BlackDiamond Includes all VLANs plus sub VLANs, super VLANs, etc. 3000 in an all “i”-series system.
Release Notes for ExtremeWare v6.2.1 Flow Control Flow control is fully supported only on Gigabit Ethernet ports. Gigabit ports both advertise support and respond to pause frames. 10/100 Mbps Ethernet ports also respond to pause frames, but do not advertise support. Neither 10/100 Mbps or Gigabit Ethernet ports initiate pause frames. Flow Control is enabled or disabled as part of auto-negotiation. If auto-negotiation is set to off, flow control is disabled.
Clarifications, Known Behaviors, and Problems Show Memory Output On some systems, the show memory [detail] command may show the cumulative memory allocation field as negative (9010). TFTP Download of Configuration Files When using TFTP to download a configuration file and selecting “no” for the switch reboot request, rebooting the switch at a later time will display a message that the configuration file has been corrupted. The user will be prompted to reboot the switch with factory default parameters.
Release Notes for ExtremeWare v6.2.1 Removal/Insertion of an MSM The action of inserting or removing a BlackDiamond MSM will report the following message under certain circumstances. This message can be safely ignored (8547). 04/27/2000 12:39.37 ngRxFirst failed WTX1 - (1, eeeeeeee, ffff) Extended Diagnostics Running the CLI run diags extended command can cause the following messages to appear in the log.
Clarifications, Known Behaviors, and Problems System Related – Alpine Switches Configuring Slots for the GM-4Xi and GM-4SXi On the Alpine 3808 and 3804 switches, the only configurable option for The Alpine 1000BaseX I/O modules is the “GM-4Xi” option. When using EPICenter to manage the switch, EPICenter will display a slot mismatch for the GM-4SXi modules when configured as a GM-4Xi. The GM-4SXi will be fully operational and recognized as a “GM-4Xi” for the configured type (9884).
Release Notes for ExtremeWare v6.2.1 going up in an unexpected manner, this indicates that the software is making route decisions and can be something to investigate further. Cosmetic PING Errors When a ping is unsuccessful, the initially reported number of transmit frames is four, but in actuality the switch will continue to try beyond the four frames. Accurate statistics are reported after hitting a carriage return to terminate the ping function (5132).
Clarifications, Known Behaviors, and Problems Switching and VLANs This section describes issues associated directly with Layer 2 switching and VLANs. FDB Aging Timer In ExtremeWare v6.2.0, the default value of the FDB aging timer was set to 1800 seconds on a newly configured v6.2.0 switch. In v 6.2.1 the default value has been changed back to 300 seconds. However, when upgrading from v6.2.0 to v6.2.1, the default value will remain and 1800 seconds. For upgrades from earlier versions of ExtremeWare (6.1.
Release Notes for ExtremeWare v6.2.1 packets are transmitted from the switch in the event that lower priority queues are congested. This mechanism uses internal resources and limits the number of VLANs that can be configured on a switch.
Clarifications, Known Behaviors, and Problems EMISTP and Ingress Rate Shaping. If a loop exists in your network, but STP is not enabled but Ingress Rate Shaping is, the switches appear to hang and are rebooted by the watch-dog timer.
Release Notes for ExtremeWare v6.2.1 QoS Bandwidth Settings and their impact Bandwidth settings applied to QoS Profiles that are used for ingress or egress traffic are expressed as a percentage of bandwidth. QoS Profile bandwidth settings are in turn applied to queues on physical ports. The actual impact of the bandwidth setting is determined by the port speed (10, 100 or 1000 Mbps) and by the actual granularity capabilities of the switch. Maximum bandwidth settings.
Clarifications, Known Behaviors, and Problems Minimum bandwidth settings. The minimum bandwidth percentage settings determine the reserved port bandwidth available to each queue. Use the following table to determine the actual reserved bandwidth associated with each setting. If the reserved percentage bandwidth configured does not match one of the settings listed below, it will be rounded up to the next setting.
Release Notes for ExtremeWare v6.2.1 VLAN QoS Between I/O BlackDiamond Modules When using VLAN QoS on a tagged VLAN between i-series I/O modules and non i-series I/O modules (G4X, G6X, F32T, and F32F), the “show ports qosmonitor” will display the active ports between the new and existing I/O modules as using different queues (7116). MAC QoS Broadcast MAC QoS does not take effect on non-”i” series I/O modules on a BlackDiamond.
Clarifications, Known Behaviors, and Problems features associated with ExtremeWare v6.1. These include route tracking and the ability to modify the election algorithm. Mixing Clients and Routers on an ESRP-Enabled VLAN ESRP should not be enabled on a VLAN that is also expected to exchange routes with other non-ESRP routers (e.g.: routers using RIP or OSPF). ESRP is intended and designed as a Layer 2 or Layer 3 redundancy method for clients with a single default route.
Release Notes for ExtremeWare v6.2.1 No Static ARP Entries. The use of Static ARP entries associated with superVLANs or sub-VLANs is not supported in this release (5106). VLAN Aggregation and ESRP. A sub-VLAN should not be configured to run ESRP. The system will allow you to enable ESRP on a VLAN and then designate the VLAN as a sub-VLAN, but this is not a supported configuration (5193). Multinetting Multinetting and IP Multicast Routing.
Clarifications, Known Behaviors, and Problems IPX Routing Tuning In larger environments, it is helpful to increase the IPX SAP and IPX RIP update intervals to reduce CPU load (e.g. from default of 60 to 120 seconds). To increase route stability, you may wish to increase the hold multiplier (default is 3 for 180 seconds), To modify these parameters use the following CLI commands: (4859).
Release Notes for ExtremeWare v6.2.1 “down” after the first ping check interval of 30 seconds. The ping health checking can be disabled using the command: disable slb node {all | } ping-check Server Load Balancing with 3DNS 3DNS is used as a global load balancing and site redundancy tool.
Clarifications, Known Behaviors, and Problems VLAN boundary Web Cache Redirection traffic must come in on an “i”-series switch running version 6.1 or better software. Traffic that satisfies a flow redirection must otherwise have been forwarded at layer 3 (packets must cross a VLAN boundary).
Release Notes for ExtremeWare v6.2.1 192.168.2.0/24 80 ANY 2 192.168.0.0/16 ANY 10.10.10.0/24 4 192.168.2.0/24 ANY 10.10.0.0/16 3 192.168.2.0/24 80 10.10.0.0/16 1 In this case, Rule 4 is the rule with the best match as it again contains an explicit Destination IP Port. NetFlow If a flow record filter is configured on one port with type “match-all-flows” you cannot configure the same flow filter on any other port. (1-7G1D8) WEB Management - VISTA Closing Internet Explorer 4.0 IE 4.
Clarifications, Known Behaviors, and Problems Bridge MIB Attributes Unsupported counters. The IEEE Bridge MIB dot1dTpPortEntry PortInDiscards and dot1dBasePortEntry counters do not increment (4937). dot1dBasePortTable Display. The dot1dBasePortTable only displays the first 4 slots in a BlackDiamond switch (6918). The ifTable correctly displays all slots.
Release Notes for ExtremeWare v6.2.1 DHCP Server The DHCP server is not supported as a standalone feature. It is used as part of the Network Login feature only. (1-8SAI6) DLCS DLCS is only supported on “i” series modules (8389). Virtual Chassis The Virtual Chassis is not supported in ExtremeWare v6.0 or higher. Issues Resolved in this Release General nslookup Function Did Not Handle Multi-answer DNS The nslookup function in ExtremeWare did not correctly handle a multi-answer DNS response.
Issues Resolved in this Release IGMP Snooping IGMP on Management VLAN In ExtremeWare v6.1.8, IGMP was always enabled on the management VLAN (mgmt) and there was no way to disable it. It is now disabled for the management VLAN. (15643/13745) QoS Rate Shaping Port Restrictions When rate shaping routed traffic on 10/100 ports, rate shaping ports are no longer restricted from belonging to the same block of 8 ports as loopback or normal ports. ExtremeWare v6.2.
