ExtremeWare Installation and Release Notes Software Version 7.4.3b5 Extreme Networks, Inc. 3585 Monroe Street Santa Clara, California 95051 (888) 257-3000 http://www.extremenetworks.
Alpine, Altitude, BlackDiamond, EPICenter, Ethernet Everywhere, Extreme Ethernet Everywhere, Extreme Networks, Extreme Turbodrive, Extreme Velocity, ExtremeWare, ExtremeWorks, GlobalPx Content Director, the Go Purple Extreme Solution Partners Logo, ServiceWatch, Summit, the Summit7i Logo, and the Color Purple, among others, are trademarks or registered trademarks of Extreme Networks, Inc. or its subsidiaries in the United States and other countries.
Contents Chapter 1 Overview New and Enhanced Features in ExtremeWare 7.
Contents Tested Third-Party Clients Tested Laptops Tested PDAs Tested Tablets Tested Scanner Tested Embedded WNIC Modules Tested Spectralink Supported Handsets Tested Spectralink Gateway Legacy IP Phones Legacy Phones with Dongle Chapter 2 29 29 30 30 30 30 30 30 30 31 Upgrading to ExtremeWare 7.4 Staying Current 33 ExtremeWare Software Images for Summit 200/300/400 Series Switches 33 Upgrading ExtremeWare “i” Series Switches Upgrading Switches to ExtremeWare 7.
Contents Chapter 4 Clarifications, Known Behaviors, and Resolved Issues Clarifications and Known Behaviors General Downgrading from ExtremeWare 7.4 to ExtremeWare 7.3 or Earlier Causes a Failure Port Sharing Between G24T and G8X I/O Modules is not Working Correctly Some APs Reboot in Heavy Traffic and High RF Interference Enabling HTTP on a Non-SSH ExtremeWare 7.4 Image Upgrading the Switch to ExtremeWare 7.4 from ExtremeWare 7.
Contents Stacking 67 Bootup Time Traffic Grouping Based on Access Lists, DSCP Across Units Not Working Properly Task Utilization is High During a CPU DoS Attack Configuring the Mirrored-to Port VLAN Tagged 2 Cannot be Used When Stacking is Enabled CLI Commands Executed from Pseudo TTY Sessions Moving from a Stack Image to a Non-stack Image Wrong Number of Ports Displayed in Default VLAN Frames Being Received After Setting MAC Limit to Zero for Port Able to Receive Frames Even After Port is Locked for Lea
Contents Multicast Network Login RADIUS Routing Security SNMP Stacking Vista VRRP Wireless 74 74 74 75 75 75 75 76 76 76 Issues Resolved in ExtremeWare 7.4.2b6 General BlackDiamond Summit 200, Summit 300-24, and Summit 400 Switches Bridging Control Protocols Diagnostics Flow Redirection EAPS Multicast SNMP Spanning Tree Protocol Stacking Wireless 76 76 77 77 77 78 78 78 78 78 78 78 79 79 Issues Resolved in ExtremeWare 7.4.
Contents 8 ExtremeWare 7.4.
1 Overview These Release Notes document ExtremeWare®7.4.3b5. ExtremeWare 7.4 enables new hardware products and software features. NOTE You can only load ExtremeWare 7.0 (or later) on a switch running ExtremeWare 6.2.2 (or later). To install ExtremeWare 7.4, see “Upgrading ExtremeWare “i” Series Switches” on page 34. This chapter contains the following sections: • New and Enhanced Features in ExtremeWare 7.4 on page 9 • Features Supported in ExtremeWare 7.4.
Overview NOTE Vista support for stacking is not available. HTTPS/SSL for Network Login HTTPS access is provided through Secure Socket Layer (SSLv3) and Transport Layer Security (TLS1.0). These protocols enable clients to verify the authenticity of the server to which they are connecting, thereby ensuring that users are not compromised by intruders. SSL supports encryption of the data exchanged between the server and the client, protecting the network login credentials from exposure on the network media.
New and Enhanced Features in ExtremeWare 7.4 domains in a spatial reuse configuration. By doing this, the entire bandwidth for the ring can be used, including the LAN segment connected to the secondary port of the master switch. Multicast Extensions • Multicast Copy Count Multicast copy count extension allows you to enable or disable this feature using the CLI when you need to configure a copy count of more than 512.
Overview IP ARP Proxy Command Feature The configure iparp add proxy command now configures the always qualifier independent of the MAC address configuration. Configuring the IP ARP proxy entry without a mac_address and adding always as a qualifier prompts the switch to send the ARP response with the mac_address of the switch. The switch also answers all the ARP requests without filtering requests that belong to the same subnet of the receiving router interface. You can configure up to 64 proxy ARP entries.
Features Supported in ExtremeWare 7.4.2 and Later MAC-Based RADIUS Authentication for Network Login MAC-based RADIUS authentication uses the MAC address of the client for authentication. This feature is useful for devices that cannot function as 802.1x supplicants, such as IP phones. RADIUS is used as the transport protocol for authentication. The RADIUS server must be populated with the MAC addresses of all clients or with a MAC address and mask.
Overview Remote Connect VLAN The IP address of the remote connect (RC) VLAN is used in DNS for discovery entries (extr-remote-connect-1|2, or defined by Option 43) or for the attachment switch redirect-db. The RC VLAN of the discovery and attachment switches should be visible from the RC VLANs of the edge (or POE) switches. Run the ping from command to verify that the switches are visible from the edge switch. (PD3-46430702) • 802.
Supported Hardware Table 2: Software for supported hardware (continued) Extreme Hardware ExtremeWare Filename BootROM Filename/Version Summit 400-48t v743b5.Cxtr or v743b5.SCxtr s400_boot51.bin Summit 400-24p v743b5.Cxtr or v743b5.SCxtr s405_boot51.bin Summit 400-24t v743b5.Cxtr or v743b5.SCxtr s405_boot51.bin Summit 200-24/48 (see note) v743b5.Fxtr or v743b5.SFxtr s200_boot51.bin Summit 300-24 v743b5.Fxtr or v743b5.SFxtr s200_boot51.bin Summit 300-48 v743b5.Lxtr or v743b5.
Overview BlackDiamond Component Support BlackDiamond components supported with ExtremeWare 7.4, and the minimum ExtremeWare version required by the chassis to support each component, include: Table 3: BlackDiamond component support BlackDiamond Component ExtremeWare Required BlackDiamond 6804 6.2.2b561 BlackDiamond 6808 6.2.2b561 BlackDiamond 6816 6.2.2b561 MSM-3 7.1.1 MSM64i 6.2.2b561 G8Xi 6.1.3 G8Ti 6.1.3 G12SXi 6.1.4 G16X3 7.0.1 G24T3 7.0.1 F32Fi 6.1.8 F48Ti 6.1.2 F96Ti 6.1.
Supported Hardware Alpine Component Support Alpine components supported with ExtremeWare 7.4, and the minimum ExtremeWare version required, include: Table 4: Alpine component support Alpine Component ExtremeWare Required Alpine 3802 6.2.2b561 Alpine 3804 6.2.2b561 Alpine 3808 6.2.2b561 SMMi 6.2.2b561 GM-4Si/Xi/Ti 6.1.5 GM-16X3 7.0.1 GM-16T3 7.0.1 FM-32Ti 6.1.5 FM-24MFi 6.1.5 FM-24Ti 6.1.7 FM-24SFi 6.1.7 FM-32Pi 7.2.0b18 GM-WDMi 6.1.8 WM-4T1i 7.0.1 WM-4E1i 7.0.1 WM-1T3i 7.0.
Overview Table 5: Summit component support Summit Component ExtremeWare Required Summit48si DC Power Supply 7.1.12 1. Older switches do not require ExtremeWare 6.2.2b56. To determine the minimum revision required for your switch, see Field Notice 115A, here: http://www.extremenetworks.com/services/documentation/FieldNotices_ FN0115-MACAddressSoftwareReqmt.asp. 2. ExtremeWare 6.2.
Channel Mapping Table 7: ExtremeWare recognition of GBIC type ExtremeWare Version SX Parallel ID LX Parallel ID SX Serial ID LX Serial ID LX70 7.x SX LX SX LX LX70 Mini-GBIC Support Extreme products support the Extreme mini-GBIC only. For reliability and stability reasons, third-party mini-GBICs are not supported at this time. XENPAK Module Support XENPAK modules supported with ExtremeWare 7.
Overview Table 9: Altitude 300-2i channel mapping (continued) Country Code 802.11a Channels 802.11g 802.
Channel Mapping Table 9: Altitude 300-2i channel mapping (continued) Country Country Code 802.11a Channels 802.11g 802.
Overview Table 10: Altitude 300-2d indoor channel mapping (continued) Country Country Code Cyprus CY 36/40/44/48/52/56/60/64/100/104/108/112/116/120/124/128/ 1-13 132/136/140 1-13 Czech Republic CZ 36/40/44/48/52/56/60/64 1-13 1-13 Denmark DK 36/40/44/48/52/56/60/64/100/104/108/112/116/120/124/128/ 1-13 132/136/140 1-13 Egypt EG None 1-13 1-13 Estonia EE 36/40/44/48/52/56/60/64/100/104/108/112/116/120/124/128/ 1-13 132/136/140 1-13 Finland FI 36/40/44/48/52/56/60/64/100/104/108/11
Channel Mapping Table 10: Altitude 300-2d indoor channel mapping (continued) Country Country Code Portugal PT 36/40/44/48/52/56/60/64/100/104/108/112/116/120/124/128/ 1-13 132/136/140 1-13 Puerto Rico PR 36/40/44/48/52/56/60/64/149/153/157/161/165 1-11 1-11 Russia RU None 1-13 1-13 Saudi Arabia SA None 1-13 1-13 Singapore SG 149/153/157/161/165 1-13 1-13 Slovak Republic SK 36/40/44/48/52/56/60/64 1-13 1-13 36/40/44/48/52/56/60/64/100/104/108/112/116/120/124/128/ 1-13 132/136/
Overview Table 11: Altitude 300-2d outdoor channel mapping (continued) Country Country Code 802.11a Channels 802.11g Channels 802.
Tested Third-Party Products Table 11: Altitude 300-2d outdoor channel mapping (continued) Country Country Code 802.11a Channels 802.11g Channels 802.
Overview Table 13: 802.11 a/b wireless NICs NIC Driver OS Third-Party Software Authentication Method Linksys WPC51AB 2.0.1.254 W2K SP4 Odyssey 2.2/3.0/4.0 WinXP SP/SP21 Orinoco Gold A/B 7.64.1.316 W2K SP4 PEAP/TLS/TTLS Odyssey 2.2/3.0/4.0 WinXP SP1/SP2 D-Link DWL-650 AB Air Pro 2.4.1.130 W2K SP4 PEAP/TLS/TTLS PEAP/TLS/TTLS PEAP/TLS/TTLS Odyssey 2.2/3.0/4.0 WinXP SP1/SP2 PEAP/TLS/TTLS PEAP/TLS/TTLS Table 14: 802.
Tested Third-Party Products Table 16: 802.11g MiniPCI wireless NIC NIC Driver OS Third-Party Software Authentication Method Broadcom 54G MaxPerformance 3.20.23.0 W2K SP4 Odyssey 2.2/3.0/4.0 Card Utility PEAP/TLS/TTLS Dell True Mobile 1300 3.20.23.0 Odyssey 2.2/3.0/4.0 Card Utility PEAP/TLS/TTLS WinXP SP1/SP2 W2K SP4 WinXP SP1/SP2 The wireless PCI cards in Table 17 are tested with the listed software (or later) and authentication method.
Overview Table 18: Wireless tri-mode NICs (continued) NIC Driver OS Third-Party Software Authentication Method 3Com 3CRPAG175 1.0.0.25 W2K SP4 Odyssey 2.2/3.0/4.0 PEAP/TLS/TTLS Odyssey 2.2/3.0/4.02 PEAP/TLS/TTLS Odyssey 2.2/3.0/4.0 PEAP/TLS/TTLS Odyssey 2.2/3.0/4.0 PEAP/TLS/TTLS Odyssey 2.2/3.0/4.0 PEAP/TLS WinXP SP1/SP2 Proxim A/B/G 2.4.2.1.7 W2K SP4 WinXP SP1/SP2 D-Link AG660 2.1.3.1 W2K SP4 WinXP SP1/SP2 Linksys AG WPC55AG 3.0.0.111 W2K SP4 WinXP SP1/SP2 Cisco Air-CB21AG 3.0.
Tested Third-Party Products Table 20: Wireless 802.11 a/b NICs (WPA compliant) NIC Driver OS Third-Party Software Authentication Method NetGear WAB501 2.4.0.71 W2K SP4 Odyssey 2.2/3.0/4.0 PEAP/TLS/TTLS Odyssey 2.2/3.0/4.0 PEAP/TLS/TTLS WinXP SP1/SP2 Avaya Platinum A/B 2.4.1.21 W2K SP4 WinXP SP1/SP2 Table 21: Wireless 802.11 a/b/g PCI-NICs (WPA Compliant) NIC Driver OS Third-Party Software Authentication Method Dell True Mobile 1450 3.40.65.0 W2K SP4 Odyssey 2.2/3.0/4.
Overview • Sony PCG-K15 • Dell Latitude D600 Tested PDAs These PDAs are fully tested: • iPAQ H5550 • Dell Axim x3i • HP Pocket PC 4155 Tested Tablets These tablets are fully tested: • NEC Tablet Tested Scanner The following scanner is fully tested: • Intermec Scanner Model 700 Color-Pocket PC - 802.
Tested Third-Party Products • TI PTB48540 CL003ENG • 3COM NJ105 • 3COM NJ220 • 3COM NJ200 Old • 3COM NJ200 New • 3COM NJ100 New • 3COM NJ100 Old • 3COM 3C10248B with 3CNJVOIPMOD-NBX • 3COM 3C10248PE IP Phone • 3COM 3C10226PE IP Phone • Avaya 4602SW IP Phone • Avaya 4620 IP Phone • Avaya 4630SW IP Phone • Polycom IP 300 With 2457-11077-002 Rev.X1 • Polycom IP 500 With 2457-11077-002 Rev.
Overview 32 ExtremeWare 7.4.
2 Upgrading to ExtremeWare 7.4 This chapter contains the following sections: • Staying Current on page 33 • ExtremeWare Software Images for Summit 200/300/400 Series Switches on page 33 • Upgrading ExtremeWare “i” Series Switches on page 34 • Downgrading “i” Series Switches on page 41 • Upgrading ExtremeWare on Summit 200/300/400 Series Switches Using the CLI on page 41 • Upgrading ExtremeWare on Summit Series Switches Using EPICenter 5.
Upgrading to ExtremeWare 7.4 Table 22: ExtremeWare 7.4 software images Filename Description and Usage s300_bl.1.1.0.b2.bin This is the BootLoader file version 1.1.0 for the Summit 300-48 (build 2). Generally, most Summit 300-48 switches will be running at least this version. If this is not the case, download the BootLoader as stated in the upgrade steps. s300_bs.1.1.0.b2.bin This is the BootStrap file version 1.1.0 for the Summit 300-48 (build 2).
Upgrading ExtremeWare “i” Series Switches Table 23: Required BootROM versions ExtremeWare Version BootRom Version ExtremeWare 6.1 through ExtremeWare 6.1.7 BootROM 6.5 If your switch is running ExtremeWare 6.1.8 (or earlier), you must first upgrade to ExtremeWare 6.1.9, then upgrade to ExtremeWare 6.2.2b56 (or later). Following are specific instructions on upgrading to, and downgrading from, ExtremeWare 7.3 for Summit, Alpine, and BlackDiamond switches.
Upgrading to ExtremeWare 7.4 b Use the clear netlogin state port command on all Network Login user ports, causing all Network Login users to be unauthenticated and all client ports to move back to their respective unauthenticated VLAN configuration. c Use the show netlogin and show vlan commands to verify that all Network Login ports are in the unauthenticated state and the client ports are members of their respective unauthenticated VLANs.
Upgrading ExtremeWare “i” Series Switches Upgrading to ExtremeWare 6.2.2b56 If you are running ExtremeWare 6.1.9 to ExtremeWare 6.2.2b43, upgrade to ExtremeWare 6.2.2b56 (you can substitute ExtremeWare 6.2.2 builds 68, 108, 124, 134, and 156 for build 56): 1 TFTP download ExtremeWare 6.2.2b56 to the primary image space using the download image primary command. 2 Reboot the switch using the reboot command. The previous configuration of the switch is preserved. NOTE ExtremeWare 6.2.
Upgrading to ExtremeWare 7.4 5 TFTP download the configuration. 6 Reboot the switch using the reboot command. NOTE If you have hitless failover enabled on your MSM-3, you can use the hitless upgrade procedure. 7 Verify that the correct ExtremeWare version is loaded on the switch using the show switch command. 8 TFTP download the configuration you saved in Step 1, and enter y at the prompt to reboot the switch. NOTE If you are using EAPS and are upgrading from a version prior to ExtremeWare 6.2.
Upgrading ExtremeWare “i” Series Switches NOTE If you are upgrading multiple modules, skip step 3 until you have upgraded every module, then reboot the switch instead of rebooting each slot. 4 Verify that the correct ExtremeWare is loaded using the show version command. You should see output similar to the following: BootROM: 251.251 Image: WM4T1 Version 6.1.8 (Build 79) If you see a version other than Build 79, repeat steps 1 - 4. 5 Download the BootROM using the download bootrom slot command.
Upgrading to ExtremeWare 7.4 7 Reboot the module using the reboot slot command. NOTE If you are upgrading multiple modules, skip step 7, upgrade every module, then reboot the switch. 8 Verify the slot is operational using the show slot <#> command. Upgrading PoE Firmware on an Alpine Switch with a PoE Module If you are using an Alpine switch with a PoE module, upgrade the PoE firmware. A version of PoE firmware is built into ExtremeWare to allow easy replacement if necessary.
Downgrading “i” Series Switches 13 Save the new configuration to the primary space. Do not save to the secondary configuration space until you are certain a downgrade to the previous image is not required. Downgrading “i” Series Switches Assuming that the previous configuration is in the secondary configuration space and the previous image is in the secondary image space: 1 If you saved an ExtremeWare 6.
Upgrading to ExtremeWare 7.4 automatically converted during the initial boot of ExtremeWare 7.4 Failure to download the saved configuration will leave the switch with a minimal default configuration. Upgrading a Summit 200 to ExtremeWare 7.4 Upgrade a Summit 200 switch running ExtremeWare 6.2e or ExtremeWare 7.1e to ExtremeWare 7.4 as follows: NOTE If you are using ExtremeWare 7.1e and stacking is enabled, the stacking functionality has changed drastically in ExtremeWare 7.4.
Upgrading ExtremeWare on Summit 200/300/400 Series Switches Using the CLI 3 Save the configuration using the save configuration command. 4 Download the ExtremeWare 7.4 image, v743b5.Fxtr. 5 Reboot the switch using the reboot command. 6 The upgrade should not affect the running configuration. If you do not have the appropriate configuration downloaded, reconfigure the switch or download the original configuration saved in step 1. This step is optional.
Upgrading to ExtremeWare 7.4 7 Download the configuration you saved in step 1. For example: download config 10.60.112.254 saved.cfg This step is optional. Upgrading a Summit 400-24 to ExtremeWare 7.4 Upgrade a Summit 400-24 to ExtremeWare 7.4 as follows: 1 Upload the current configuration to a TFTP server. 2 Verify the current BootROM is version 5.1. If the BootROM is version 5.1, go to step 3, otherwise download the BootROM: s405_boot51.bin and reboot the switch. 3 Download ExtremeWare 7.4 image v743b5.
Upgrading ExtremeWare on Summit Series Switches Using EPICenter 5.0 For information on upgrading Summit 200, 300, and 400 series switches to ExtremeWare 7.4 using EPICenter, see the EPICenter 5.0 Service Pack 3 Release Note. For general information on EPICenter 5.0, and on using the EPICenter Firmware Manager, see the EPICenter Reference Guide available on the Extreme Networks website. ExtremeWare 7.4.
Upgrading to ExtremeWare 7.4 46 ExtremeWare 7.4.
3 Supported Limits This chapter summarizes the supported limits in ExtremeWare 7.4. NOTE ExtremeWare 7.4 supports the “i” series platforms, including the BlackDiamond, Alpine, and Summit “i” series switches. In addition, ExtremeWare supports the “e” series platforms, including the Summit 200, Summit 300, and Summit 400 series switches. This chapter contains the following sections: • Supported Limits for ExtremeWare “i” Series Switches on page 47.
Supported Limits Table 24: Supported limits for “i” Series Switches (continued) Metric Description Limit Application Examination rules Maximum number of Application Examination rules. 1000 Application Examination rules/port Maximum number of Application Examination rules per port. 60 BGP—Peer Groups Maximum number of BGP peer groups per switch. 16 BGP—peers Maximum number of BGP peers per switch.
Supported Limits for ExtremeWare “i” Series Switches Table 24: Supported limits for “i” Series Switches (continued) Metric Description Limit EMISTP & PVST+ — maximum domains, Summit Maximum number of EMISTP and PVST+ domains. 128 EMISTP & PVST+ — maximum domains, Alpine Maximum number of EMISTP and PVST+ domains. 256 EMISTP & PVST+ — maximum domains, BlackDiamond Maximum number of EMISTP and PVST+ domains. 512 EMISTP & PVST+ — maximum ports Maximum number of EMISTP and PVST+ ports.
Supported Limits Table 24: Supported limits for “i” Series Switches (continued) Metric Description Limit IP ARP Static entries Maximum number of permanent IP static ARP entries supported. 512 IP ARP Static Proxy entries Maximum number of permanent IP ARP proxy entries. 512 IP Route Sharing Entries (ECMP)—static or OSPF Maximum number of static or OSPF routes used in route sharing calculations.
Supported Limits for ExtremeWare “i” Series Switches Table 24: Supported limits for “i” Series Switches (continued) Metric Description Limit NetFlow—Filters Maximum number of NetFlow filters in a switch. 128 NetFlow—Groups Maximum number of NetFlow groups. 32 NetFlow—Hosts Maximum number of NetFlow hosts. 8/group Network Login—Maximum clients Maximum number of Network Login clients per switch. 1024 Network Login—802.1x Maximum recommended Session-Timeout value returned by RADIUS server.
Supported Limits Table 24: Supported limits for “i” Series Switches (continued) Metric Description Limit SLB—maximum number of VIPs For Transparent and Translational and GoGo modes respectively.
Supported Limits for ExtremeWare “e” Series Switches Table 24: Supported limits for “i” Series Switches (continued) Metric Description Limit Syslog servers Maximum number of simultaneous syslog servers that are supported. 4 Telnet—number of sessions Maximum number of simultaneous Telnet sessions. 8 Trusted MAC entries Maximum number of simultaneous trusted MAC entries. 48 UDP profiles Number of profiles that can be created for UDP forwarding.
Supported Limits Table 25: Supported limits for “e” Series Switches Metric Description Limit Access Profile entries Used by SNMP, Telnet, SSH2, and Routing Access Policies 256 EAPS—Domains/switch Maximum number of EAPS domains. 4 EAPS—Domains/ring Maximum number of EAPS domains if no switch in the ring is connected to another ring. 4 EAPS—VLAN links Recommended maximum number of Control or Protected VLANs per switch. 128 EAPS—Master nodes Number of Master nodes per EAPS domain.
Supported Limits for ExtremeWare “e” Series Switches Table 25: Supported limits for “e” Series Switches Metric Description Limit OSPF external type 1 or 2 routes Recommended maximum number of external type 1 or 2 routes contained in an OSPF LSDB. 100,000 OSPF routers in a single area Recommended maximum number of routers in a single OSPF area. 40 OSPF interfaces on a single router Maximum number of OSPF routed interfaces on a switch.
Supported Limits Table 25: Supported limits for “e” Series Switches Metric Description Limit UDP profile entries Number of entries within a single UDP profile. 16 VLANs Maximum number of VLANs (includes all VLANs). Summit 400—4094 Summit 200—255 Summit 300—255 Stacking Limits for Power over Ethernet When creating a stack of Summit 200 and Summit 300-24 switches, the maximum number of Power over Ethernet (PoE) capable switches to be used is three.
Stacking Limits for Power over Ethernet Table 26: Supported limits for stacking Summit Series switches Metric Description Stacking Limits FDB—Maximum number of L3 entries Maximum number of IP addresses. Master switch limitations apply to the entire stack. If the master is: Summit 200 and Summit 300—2000 Summit 400-24—2000 Summit 400-48—4000 IP Router interfaces Maximum number of VLANs performing IP routing. Master switch limitations apply to the entire stack.
Supported Limits Table 26: Supported limits for stacking Summit Series switches Metric Description Stacking Limits OSPF routers in a single area Recommended maximum number of routers in a single OSPF area. 40 OSPF interfaces on a single router Maximum number of OSPF routed interfaces on a switch. 2 OSPF interfaces, passive Maximum number of passive OSPF interfaces. 512 OSPF virtual links Maximum number of OSPF virtual links supported.
Stacking Limits for Power over Ethernet Table 26: Supported limits for stacking Summit Series switches Metric Description Stacking Limits UDP profiles Number of profiles that can be created for UDP forwarding. 10 UDP profile entries Number of entries within a single UDP profile. 16 VLANs Maximum number of VLANs (includes all VLANs). Master switch limitations apply to the entire stack. If the master is: Summit 400—4094 Summit 200—255 Summit 300—255 ExtremeWare 7.4.
Supported Limits 60 ExtremeWare 7.4.
4 Clarifications, Known Behaviors, and Resolved Issues This chapter describes items needing further clarification, behaviors that might not be intuitive, and issues that have been resolved since the last release. Numbers in parentheses are for internal reference and can be ignored. This chapter contains the following sections: • Clarifications and Known Behaviors on page 61 • Issues Resolved in ExtremeWare 7.4.3b5 on page 72 • Issues Resolved in ExtremeWare 7.4.
Clarifications, Known Behaviors, and Resolved Issues Port Sharing Between G24T and G8X I/O Modules is not Working Correctly Cross module port sharing involving a G24T and G8X I/O module is not working correctly and generates the following error message: * BD6808:21 # en shar 7:1 g 7:1,8:1 ERROR: Ports 7:1 and 8:1 are running at different speeds. You can only load share on links operating at same speed.
Clarifications and Known Behaviors Alpine EPICenter/SNMP Does not Show Port Display String When configuring a port string using an Alpine switch and viewing the port information from EPICenter, the configured port string is not shown in the port information (PD3-40520509). BlackDiamond 6800 BlackDiamond Switch Generates L2 Known Unicast Traffic A BlackDiamond switch is generating L2 known unicast traffic after disabling and enabling a slot (PD3-40044661).
Clarifications, Known Behaviors, and Resolved Issues Bridging Deleting Member VLANs Flushes FDB Entries Deleting a member VLAN flushes all FDB entries in the translation and member VLANs (PD3-24824553). CLI Configurations are Corrupted When Switch is Rebooted Configurations are corrupted when the switch is rebooted after performing a change in the local configuration and downloading a new configuration (PD2-232396030).
Clarifications and Known Behaviors EAPS Flushing Selective FDB Entries is not Working Properly on an EAPS Domain Selective flushing of FDB entries belonging to a protected VLAN is not working correctly. Instead, the switch flushes all FDB entries, including those for non-protected VLANs (PD3-37488841).
Clarifications, Known Behaviors, and Resolved Issues (PD3-31673591) SNMP MIB Table Becomes Empty When Adding Policy Rules through EPICenter When adding multiple IP policy rules through EPICenter's Policy Manager, frequently the MIB table will become empty or partially cleared (only some of the rules will remain), even though no error message has occurred, and the policy rules are still in place on the switch.
Clarifications and Known Behaviors Extreme Real Time Statistics Does Not Work When There are 24+ Ports When Network Management tool EPICenter tries to get real time statistics on an Extreme device that has more than 24 ports, it sometimes fails (PD3-14524212, PD3-15975950). Stacking Bootup Time A full stack consisting of 8 Summit 200 or Summit 300-24 switches amy take slightly over two minutes to bootup.
Clarifications, Known Behaviors, and Resolved Issues 4 If all ports are deleted from the default VLAN, the incorrect number of active ports is shown. (PD3-28261405) Frames Being Received After Setting MAC Limit to Zero for Port In a stack of two Summit switches, create a VLAN and add some ports. Set the MAC limit to zero on one of the ports. If you send frames from that port to the other port, the receiving port should receive one frame when in fact it is receiving multiple frames (PD3-25226331).
Clarifications and Known Behaviors Wireless Special Characters Accepted in WEP Plaintext Key While configuring the WEP Plaintext key, the following characters are accepted in the CLI and are also stored as part of the key: * - (hyphen) * _ (underscore) * . (dot) For example, eg.con sec open64wep wep key add 0 plaintext a-_.. would be an accepted key. The following character is accepted in the CLI but is not stored as part of the key: * # (hash) For example, eg.con sec open64wep wep key add 0 plaintext a-_.
Clarifications, Known Behaviors, and Resolved Issues show wireless ports detail Output Shows Incorrect BootStrap/BootLoader Version The show wireless ports detail command shows the incorrect bootstrap and bootloader version for the AP when the AP is running an older bootrom version (1.5.2). # show wireless ports 2 detail ... Hardware Version: 01010001 Software Version: v7.3.1 Bootstrap Version: v0.0.0 Primary Bootloader Ver: v64.240.254 (Booted) Secondary Bootloader Ver: v212.240.
Clarifications and Known Behaviors Workaround. When changing ISP mode to Campus mode configuration, instead of assigning Campus mode configuration to the same wireless port, assign Campus mode to a different wireless port. (PD3-36087982) Changing Switch Time Resets APs Time Incorrectly Changing the switch time backwards resets the time on the AP incorrectly.
Clarifications, Known Behaviors, and Resolved Issues A300 Cannot Boot The A300 cannot boot if the wireless management VLAN is not configured (PD3-28462210, PD3-23854771).
Issues Resolved in ExtremeWare 7.4.3b5 BlackDiamond Stand-alone BlackDiamond 6808 switches with an F48Ti module installed no longer experience high port utilization (PD3-42179804). Summit On a Summit 300-48 switch, the tRootTask no longer crashes, causing the switch to reboot in a loop (PD3-55381783). On a Summit 200 switch, the internal setting for the gigabit ports (25, 26) signal detect level is now correct (PD3-51650617.
Clarifications, Known Behaviors, and Resolved Issues The enable/disable web https command is no longer available on BlackDiamond switches running image v732b3.Sxtr (PD3-43162530). Diagnostics Enabling transceiver diagnostics and running extended diagnostics on MSM-B no longer triggers a false alarm (PD2-244409185). EAPS After rebooting, the VPST state now resets to forwarding on the EAPS shared port (PD3-53419213).
Issues Resolved in ExtremeWare 7.4.3b5 Routing Packets are now forwarded with the correct MAC address when being forwarded through the MPLS I/O module (PD3-50648341). The Summit 200 no longer reboots during large IP FDB synchronizations (PD3-48552431). If PIM snooping is disabled on a VLAN and the switch is running the show pim command, the VLAN no longer generates an assertion failure (PD3-35581552).
Clarifications, Known Behaviors, and Resolved Issues Vista Accessing a stack using Vista over an SSH connection and selecting Configuration > Ports no longer reboots the switch (PD3-42871441). ExtremeWare Vista now displays the correct IP ARP entries (PD3-41602680). VRRP Edge series switches no longer forward IP packets destined for the VRRP MAC in the VRRP backup state (PD3-48957937). Wireless After upgrading from ExtremeWare 7.3 to ExtremeWare 7.
Issues Resolved in ExtremeWare 7.4.2b6 In software redundant gigabyte ports on a Summit 48si, the link state is now correctly changed when removing and reinserting redundant links with the master link in the inactive state (PD3-25896001, PD3-3891361). Links no longer flap on neighbor switches when smart redundancy is disabled on a Summit 48si switch (PD3-14292583). BlackDiamond The G12sxi and F96ti I/O module backplane links are now reconnecting to MSM-A when MSM-B disabled (PD3-24444382).
Clarifications, Known Behaviors, and Resolved Issues Switches transmitting traffic with full IP FDB entries do not periodically reboot because of watchdog timer expiry (PD3-39558371). Transmitting packets between MSMs no longer causes packet loss or an increase in packet count (PD3-32365081).
Issues Resolved in ExtremeWare 7.4.1b5 Stacking LLDP now runs on the secondary ports of a load-sharing group (PD3-35886082). You can ping remote IP devices in the default VLAN even when the ports are spread across slots (PD3-38469181). Wireless Memory is now allocated correctly in the AP running a WPA2 security profile when clients are continuously logging in and logging out of the switch (PD3-39390951).
Clarifications, Known Behaviors, and Resolved Issues Spanning Tree Protocol All ports of a default VLAN are now shown as part of the default STP domain s0 on an Alpine switch (PD3-27096541). Stacking When eight Summit 200 switches are connected, stack formation no longer fails (PD3-26798611). Clearing a console session on a slave slot now functions properly (PD3-26482929). Layer 2 forwarding is no longer affected if a slot with a load share link is rebooted (PD3-27134464).
Issues Resolved in ExtremeWare 7.4.0b42 Switching Server load balancing traffic is no longer being forwarded to servers that are down (PD3-25374396). Vista Clicking on the access-list page no longer generates an error message (PD3-24863521.) VRRP Tracking a VLAN no longer generates an error message (PD3-24087800). IP FDB learning no longer takes too much time causing the VRRP state to continuously flip (PD3-28476981).
Clarifications, Known Behaviors, and Resolved Issues With BootROM 8.1, using the reboot slot [msm-a | msm-b] command via a direct console connection to a slave MSM locks up the MSM. To avoid this, use the command through a Telnet session or a connection to the master MSM. If the MSM is locked up, reboot it using the reboot slot [msm-a | msm-b] hard command (PD2-225327825).
