ExtremeSwitching 200 Series: Release Notes 121188-08 Published April 2019
Copyright © 2019 Extreme Networks, Inc. All rights reserved. Legal Notice Extreme Networks, Inc. reserves the right to make changes in specifications and other information contained in this document and its website without prior notice. The reader should in all cases consult representatives of Extreme Networks to determine whether any such changes have been made. The hardware, firmware, software or any specifications described or referred to in this document are subject to change without notice.
Table of Contents Preface......................................................................................................................................... 4 Conventions............................................................................................................................................................................. 4 Providing Feedback to Us........................................................................................................................................
Preface This section discusses the conventions used in this guide, ways to provide feedback, additional help, and other Extreme Networks publications. Conventions This section discusses the conventions used in this guide. Text Conventions The following tables list text conventions that are used throughout this guide. Table 1: Notice Icons Icon New! Notice Type Alerts you to... General Notice Helpful tips and notices for using the product. Note Important features or instructions.
Preface Terminology When features, functionality, or operation is specific to a switch family, such as ExtremeSwitching, the family name is used. Explanations about features and operations that are the same across all product families simply refer to the product as the switch.
Preface 1 Go to www.extremenetworks.com/support/service-notification-form. 2 Complete the form with your information (all fields are required). 3 Select the products for which you would like to receive notifications. Note You can modify your product selections or unsubscribe at any time. 4 Click Submit. Extreme Networks Documentation To find Extreme Networks product guides, visit our documentation pages at: Current Product Documentation www.extremenetworks.
1 Software Features This section lists the 200 Series software features supported for each operating platform. Feature Supported on Platform 220 Series 210 Series 802.1D Yes 802.1S Yes 802.1W Yes 802.1Q VLAN Tagging Yes Private VLAN Yes GARP/GVRP Yes 802.1p Yes 802.3x (Full Duplex & Flow Control) Yes Asymmetric Flow Control Yes RPVST / PVST Yes 802.1x Yes Guest VLAN Yes RADIUS-based VLAN assignment via.1x Yes RADIUS-based filter ID assignment via .1x Yes MAC-based .
Software Features Feature Supported on Platform 220 Series 210 Series MLD Snooping Yes IGMP Snooping Yes – Enable IGMP Snooping per VLAN Yes – Snooping Querier Yes Voice VLAN Yes Protected Ports (Private Edge VLAN) Yes 802.1ab LLDP Yes 802.1ab LLDP-MED Yes Static L2 Entries Yes STP Root Guard Yes BPDU Guard Yes Dynamic ARP Inspection Yes DHCP/DHCPv6 Client Yes SHCP Snooping Yes DHCP Client Option 60 Yes No DHCP L2 Relay (Option 82) per VLAN or per 802.1ad sub.
Software Features Feature Supported on Platform 220 Series 210 Series UDLD Yes 802.1ak MMRP Yes 802.1ak MVRP Yes MVR Yes Routing Static Routing Yes Port based Routing Yes VLAN Routing Yes – 802.
Software Features Feature Supported on Platform 220 Series 210 Series – 802.3ad (LAG) for ACL assignment Yes – Binding ACLs to VLANs Yes – ACL Logging Yes – Flow-based mirroring Yes – Support for IPv6 fields Yes Diffserv Yes – Edge Node applicability Yes – Interior Node applicability Yes – 802.3ad (LAG) for service interface Yes – Support for IPv6 fields Yes – Egress Yes No COS Yes – 802.
2 Metrics This section lists the supported limits, or maximum values, for 200 Series software features.
Metrics Feature Maximum Value for Platform 220 Series 210 Series Authentication exec lists – Max Count 5 – Max methods per list 2 – Max name length 15 Accounting Commands lists – Max Count 5 – Max methods per list 1 – Max name length 15 Login History 50 Max units per Stack Max physical ports per stack 4 NA 208 NA Max # of remote Telnet connections 5 Max # of remote SSH connections 2 MAC Addresses 16K Max agetime (s) 1000000 Max # of VLANs 1024 Maximum VLAN ID 4093 Number o
Metrics Feature Maximum Value for Platform 220 Series – Max Accounting servers Number of Static Routes 210 Series 16 64 Max # of DHCP Pools 60 8 Total # of leases 128 DNS Client – Concurrent request 16 – Name server entries 8 – Static host entries 64 – Cache entries 128 – Domain search list entries 32 # Routing interfaces (including port/vlan) 15 Static v4 ARP Entries 16 # ACLs 100 Maximum @ of configurable Rules per list 1023 COS - # Configurable Queues per port 7 COS – Config
3 Operational Characteristics and Known Issues 200 Series Base System Switching Switching SNMP Stacking QoS QoS (DiffServ) SNMP QoS (DiffServ) Configuration Routing Security Web User Interface CLI (Command-Line Interface) The following sections list operational characteristics and known issues associated with the 200 Series software. 200 Series Base System 1 S2xx-179575, S2xx-179447. The 200 Series software cannot read SFP diagnostic information. 2 S2xx-181872.
Operational Characteristics and Known Issues Switching 1 2 3 4 5 6 7 8 9 10 11 12 13 200 Series software implements IEEE 802.1s running in IEEE 802.1w-compatibility mode, rather than the IEEE 802.1w protocol itself. As such, ANVL RSTP test suites are not supported. ANVL MSTP Test cases are supported. S2xx-30109. Dynamically learned VLANs are not always flushed when GVRP is disabled globally. S2xx-75340.
Operational Characteristics and Known Issues SNMP, the timeout interval must be set to 2 or more seconds. Otherwise it says, Timed out and SNMP walk operation is not successful. 14 S2xx-149479, S2xx-103674. When RADIUS or Syslog uses a DNS host name for configuring server entries, they are unaware of changes in the DNS cache host mapping.
Operational Characteristics and Known Issues 27 S2xx-27237. MAC addresses can take longer than the age time to age from the hardware MAC table. If the age time is not being changed, it can take up to twice the age time to delete the MAC address. If the age time is changed, it can take up to three times the age time to delete the MAC address. 28 S2xx-27537.
Operational Characteristics and Known Issues 3 4 5 6 7 dot1qStaticUnicastTable, dot1qStaticMulticastTable, dot1qConstraintSetDefault, dot1qConstraintTypeDefault, dot1qPortGvrpFailedRegistrations, dot1qPortGvrpLastPduOrigin, dot1qLearningConstraintsTable In the private MIB, the object agentLagSummaryName cannot be set. Set and Get operations on object dot3adAggPortActorAdminState occurs in reverse order.
Operational Characteristics and Known Issues As an example, consider a configuration where queue 4 is set to operate in strict priority. Given this configuration, the administrator should also set queues 5 and 6 to operate in strict priority to guarantee that the CPU can send PDUs in a timely manner. 8 S2xx-158470. When CPU is flooded with control packets on an 8 unit stack, a code download fails.
Operational Characteristics and Known Issues • order. If queues are moved from one TCG to another TCG, the TCG is considered unused and the ordering requirement applies. S2xx-206662. After issuing the clear counters all command, congestion drops, but the counter does not get cleared. Users need to compare the previous reported values with the current values to determine the delta.
Operational Characteristics and Known Issues • • A policy is successfully attached to the service interface in the appropriate direction. The policy contains one or more policy-class instances (it need not have policy attributes defined when best-effort service is desired). • Each policy-class instance refers to a valid class. • A valid class consists of at least one class match condition. • Each class match condition is supported by the policy type (direction) based on platform features and limitations.
Operational Characteristics and Known Issues 11 S2xx-185220. When using the CLI, the configured client identifier cannot be seen in the show ip dhcp pool configuration all command output. The show running-config command shows the configured client identifier value. 12 S2xx-222483. When traceroute is initiated with large packet sizes, some of the fragments may get dropped due to ICMP rate limiting.
Operational Characteristics and Known Issues 5 S2xx-232629. Unable to set non-default authentication list from web. User configured authentication lists can be created via the web, but assigning various terminal types (Console, Telnet, SSH) will fail. As a workaround, use the associated CLI commands. 6 Selecting the Reset option in the System Reset page (System > Utilities > System Reset) results in a reboot of the switch, using the saved configuration.
4 Updates and Resolved Issues Updates and Resolved Issues in Version V01.02.06.0009 Updates and Resolved Issues in Version V01.02.05.0012 Updates and Resolved Issues in Version V01.02.04.0007 Updates and Resolved Issues in Version V01.02.03.0005 Updates and Resolved Issues in Version V01.02.02.0003 Updates and Resolved Issues in Version V01.02.01.0005 Updates and Resolved Issues in Version V01.01.
Updates and Resolved Issues 5 S2xx-0000218: Corrected the Web GUI showing the wrong information within the 802.1x port summary. 6 S2xx-0000222: Correct potential reset condition with resulting log message "Failed to read conflicting ARP packet from stack." 7 S2xx-0000231: Corrected an issue where PoE is disabled on a port if the unit is reset while the port was admin disabled. 8 S2xx-0000232: Corrected an issue in the Web UI that prevented configuration of Private VLAN of ports on the second page.
Updates and Resolved Issues 3 S2xx-0000132: Added support for PAP port-based MAB authentication. Previously on EAP, MD5 was supported. 4 S2xx-0000133: Added support for RADIUS attribute RADIUS_ATTR_TYPE_EVENT_TIMESTAMP. This was required for re-authentication in a NAC environment. 5 S2xx-0000134: Buffering changes made to prevent loss to IGMP membership reports trapped to the host CPU. This fixes a problem of excessive CPU utilization on clientless multicast streams when IGMP snooping is enabled on VLAN.