ExtremeWare Release Note Software Version 7.0.1 Build 11 Extreme Networks, Inc. 3585 Monroe Street Santa Clara, California 95051 (888) 257-3000 http://www.extremenetworks.
©2003 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 Chapter 1 Overview New Features in ExtremeWare 7.0 Features Added or Enhanced in ExtremeWare 7.0.1b11 Features Added or Enhanced in ExtremeWare 7.0.0b68 Features Added or Enhanced in ExtremeWare 7.0.0b61 11 11 13 16 Supported Hardware BlackDiamond Component Support Alpine Component Support Summit Component Support GBIC Support 17 18 19 20 20 Mini-GBIC Support Chapter 2 Upgrading to ExtremeWare 7.0.1 Staying Current 21 Upgrading ExtremeWare Upgrading Switches to ExtremeWare 7.0.
Clarifications and Known Behaviors System Related – All Systems 33 33 GBIC Type in the show ports configuration Command Output Do Not Telnet to Port 80 and Continuously Press Keys Smart Redundancy Enabled in Saved Configuration Microsoft Load Balancing Telnet and the show ports Command The show configuration Output Configure Slots or VLANs Before Uploading a Configuration LACP not Supported Upgrading to ExtremeWare 7.0 and Bi-Directional Rate Shaping Upgrading to ExtremeWare 7.
System Health Check Events Might Not Be Logged Configuring Two Multilink groups on One T1 or E1 Module Limited Commands Mode T1 and E1 Error Message VDSL Modules in a Half-Duplex Link Summit Health Check Error Messages Limited Commands Mode Summit48i Redundant PHY Summit48i Single Fiber Signal Loss SNMP Results for Power Sources Summit48si MIB value for Input Power Voltage Command Line Interface (CLI) Only US Character Set Supported The show iproute Command Serial and Telnet Configuration Displaying Manag
Locking and Unlocking Learning Loopback Port Must be on Same Module 1000Base-T Ports as Loopback Ports Changing the Configuration of a Loopback Port EAPS WAN Modules Not Currently Supported with EAPS Do Not Configure a Hello Time of 0 A Large EAPS Configuration with a Link Transition Changing the Protected VLAN Tag EAPS Performance Statistics EAPS and STP or EMISTP EAPS Secondary Port Recovery ESRP and EAPS Secondary Port Incorrect show vlan Output ESRP Configure a Neighbor Timeout Less than 6 Times Hello
RIP in Conjunction with other Routing Protocols OSPF Default Route Entries in the IP FDB Disable OSPF Before Adding or Removing External Area Filters BGP Multi Exist Descriminator Not Compared Route Dropped if Switch’s AS is First AS in Path BGP Set Community Inadvertantly Advertised Do Not Use configure access-profile Command to Set Community Best Routes BGP Loops Redistributing BGP Routes to OSPF Removed encrypted Option from enable bgp neighbor password Command IP Multicast Routing Use the always Para
Incrementing the intfIf Value WinSCP2 Not Supported SNMP ifAdminStatus MIB Value Trap Receivers as Broadcast Entry Bridge MIB Attributes SNMP Time-out Setting SNMP Access Profile SNMP and Auto-negotiation Settings SNMP and the BGP MIB SNMP and the FDB MIB Extreme Fan Traps Extreme Power Supply Traps DHCP Diagnostics and Troubleshooting The show diagnostics backplane-utilization Command Available Spurious Message When system-down is Configured The use configuration Command Output of the show diagnostics Com
OSPF Spanning Tree ESRP VLANs IS-IS NetFlow SNMP ExtremeWare 7.
ExtremeWare 7.
1 Overview These Release Notes document ExtremeWare 7.0.1 build 11. ExtremeWare 7.0.1 introduces new hardware products and software features. NOTE You can only load ExtremeWare 7.0 on a switch running ExtremeWare 6.2.2 (or later). To install ExtremeWare 7.0, see “Upgrading ExtremeWare” on page 21. This chapter contains the following sections: • “New Features in ExtremeWare 7.
Overview Flow control is disabled by default. To enable 802.3x flow control, use the following command: enable flow-control ports [ | all] To disable 802.3x flow control, use the following command: disable flow-control ports [ | all] Use the all keyword to specify all configured “3” series ports. To see the flow control configuration, use the show ports configuration command. DSBL indicates that flow control is disabled on that port.
New Features in ExtremeWare 7.0 — Link Status—The current status of the link. Options are: • Ready (R): The port is ready to accept a link. • Active (A): The link is present at this port. • Disabled (D): The link is disabled at this port. • Not Present (NP): The link is not present at this port. — High Priority Bytes—Sum, per port, of the bytes forwarded for received high-priority packets. Reserved for a future release.
Overview The following features are no longer supported on T1 or E1 modules: — T1 port mirroring — Static Load sharing — Software-Controlled Reduntant Ports — ACLs on a per port basis — Per Port Egress QOS — Traffic Grouping for source ports — BiDirectional Rate Shaping — DLCS — MAC address and protocol-based VLANs that include T1 ports — VLAN aggregation In addition, layer 2 multicast traffic is treated as broadcast traffic by the T1 and E1 modules. This feature is not documented in the ExtremeWare 7.0.
New Features in ExtremeWare 7.0 This feature is not documented in the ExtremeWare 7.0.0 Command Reference Guide or the ExtremeWare 7.0.0 User Guide. • You can now disable auto-polarity detection on the Summit48si (PD2-102329001). The Summit48si automatically detects and corrects the polarity of cables, simplifying installation and maintenance. You can disable this feature using the following command: configure ports auto-polarity The default setting is on.
Overview This feature is not documented in the ExtremeWare 7.0.0 Command Reference Guide or the ExtremeWare 7.0.0 User Guide. Features Added or Enhanced in ExtremeWare 7.0.0b61 The following features were added or enhanced in ExtremeWare 7.0.0b61: • ExtremeWare now supports the following features in a single software image. These features formerly required you to load a dedicated software image on the MSM64i.
Supported Hardware • You can now configure the neutral state timeout value for an ESRP-enabled VLAN using the config esrp esrp-neutral-timeout command (PD2-104485403). • You can now configure reboot loop protection using the config reboot-loop-protection threshold command. • RFC 2439, Section 4 “Stability sensitive suppression of route advertisement”: BGP Route Flap Damping (10223).
Overview Table 1: Software for supported hardware Extreme Hardware ExtremeWare Filename BootROM Filename/Version BlackDiamond 6816 v701b11.Gxtr or v701b11.SGxtr Ngboot7.8.bin/7.8 BlackDiamond 6808 v701b11.xtr or v701b11.Sxtr Ngboot7.8.bin/7.8 BlackDiamond 6804 v701b11.xtr or v701b11.Sxtr Ngboot7.8.bin/7.8 Alpine 3808 v701b11.xtr or v701b11.Sxtr Ngboot7.8.bin/7.8 Alpine 3804 v701b11.xtr or v701b11.Sxtr Ngboot7.8.bin/7.8 Alpine 3802 v701b11.xtr or v701b11.Sxtr/ EW-70-3802.mig Ngboot7.8.
Supported Hardware Table 2: BlackDiamond component support (continued) BlackDiamond Component G8Xi G8Ti F48Ti WDMi F96Ti F32Fi 10GLRi MPLS ARM P3cMi P3cSi P12cMi P12cSi A3cMi A3cSi DC Power Supply 110 VAC Power Supply 220 VAC Power Supply NOTE Do not install mixed versions of the power supplies in the same system. Install power supplies of the same type. Alpine Component Support Alpine components supported with ExtremeWare 7.0.
Overview Table 3: Alpine component support (continued) Alpine Component WM-4E1i WM-1T3i FM-8Vi AC Power Supply DC Power Supply Summit Component Support Summit components supported with ExtremeWare 7.0.1 include: Table 4: Summit component support Summit Module Summit7i DC Power Supply 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.
2 Upgrading to ExtremeWare 7.0.1 This chapter contains the following sections: • “Staying Current” on page 21 • “Upgrading ExtremeWare” on page 21 • “Downgrading Switches” on page 26 CAUTION You can only load ExtremeWare 7.0 (or later) on a switch running ExtremeWare 6.2.2b56 (or later). Staying Current For support purposes, Extreme Networks recommends operating the most current General Deployment (GD) release of ExtremeWare.
Upgrading to ExtremeWare 7.0.1 Table 6: Required BootROM versions ExtremeWare Version BootRom Version ExtremeWare 6.2.2 BootROM 7.6 ExtremeWare 6.1.9 through ExtremeWare 6.2.1 BootROM 7.2 ExtremeWare 6.1 through ExtremeWare 6.1.8 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 ExtremeWare 6.2.2b68). Following are specific instructions on upgrading to, and downgrading from, ExtremeWare 7.0.
Upgrading ExtremeWare Upgrade the BootROM to Version 7.6 ExtremeWare 6.1.9 requires BootROM 7.2 (or later). ExtremeWare 6.2.2 requires BootROM 7.6 (or later). Before you upgrade to ExtremeWare 6.1.9, upgrade to BootROM 7.6: 1 Download the BootROM using the download bootrom [ | ] command. 2 Reboot the switch using the reboot command. Upgrade to ExtremeWare 6.1.9 If you are running ExtremeWare 6.1.8 (or earlier), upgrade to ExtremeWare 6.1.
Upgrading to ExtremeWare 7.0.1 5 Check the log for configuration errors. Manually enter configurations that did not load. 6 Save the configuration. Do not save to the secondary configuration space until you are certain a downgrade to the previous image is not required. NOTE After upgrading from ExtremeWare 6.1.9 to ExtremeWare 6.2.2, the IGMP snooping leave time-out value will be changed from 10 seconds to 0.
Upgrading ExtremeWare Upgrade ATM, MPLS, ARM, PoS, T1, E1, or T3 Modules If you are using a ATM, MPLS, ARM, PoS, T1, E1, or T3 module, upgrade the module to ExtremeWare 7.0.1: 1 TFTP download the latest ExtremeWare version for the module using the download image slot command. NOTE T1, E1, and T3 modules must be using ExtremeWare 6.1.8b79 before upgrading to ExtremeWare 7.0.1. 2 Reboot the module using the reboot slot command.
Upgrading to ExtremeWare 7.0.1 14 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 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.
3 Supported Limits This chapter summarizes the supported limits in ExtremeWare. Supported Limits The table below summarizes tested metrics for a variety of features. These limits may change but represent the current status. The contents of this table supersede any values mentioned in the ExtremeWare Software User Guide. Table 7: Supported limits Metric Description Limit Access List rules Maximum number of Access Lists (best case).
Supported Limits Table 7: Supported limits (continued) Metric Description Limit BGP—network statements Maximum number of network statements per switch. 256 BGP—aggregate addresses Maximum number of aggregate routes that can be originated per switch. 256 Jumbo Frame size Maximum size supported for Jumbo frames, including the CRC. 9216 EAPS—Domains/switch Maximum number of EAPS domains. 64 EAPS—Domains/ring Maximum number of EAPS domains if no switch in the ring is connected to another ring.
Supported Limits Table 7: Supported limits (continued) Metric Description Limit FDB—maximum ports for permanent entries Maximum number of ports supported for permanent FDB entries. 2,000 FDB—maximum L2/L3 entries – BlackDiamond, Summit5i, Summit7i, Alpine 3804, Alpine 3808 Maximum number of MAC addresses/IP host routes for the MSM64i, Alpine 3808, and Summit7i.
Supported Limits Table 7: Supported limits (continued) Metric Description Limit MAC-based VLANs—MAC addresses Maximum number of MAC addresses that can be downloaded to the switch when using MAC-based VLANs. 7000 MAC-based security Maximum number of MAC-based security policies. 1024 Mirroring—mirrored ports Maximum number of ports that can be mirrored to the mirror port. 8 Mirroring—number of VLANs Maximum number of VLANs that can be mirrored to the mirror port.
Supported Limits Table 7: Supported limits (continued) Metric Description Limit Route Maps Maximum number of route maps supported on a switch. 128 Route Map Entries Maximum number of route map entries supported on a switch. 256 Route Map Statements Maximum number of route map statements supported on a switch. 512 SLB—maximum number of simultaneous sessions For Transparent and Translational and GoGo modes respectively.
Supported Limits Table 7: Supported limits (continued) Metric Description Limit VLANs—Summit, Alpine Includes all VLANs plus sub VLANs, super VLANs, etc. 4095 VLANs—BlackDiamond 6816 fully populated Includes all VLANs plus sub VLANs, super VLANs, etc. 681 VLANs—BlackDiamond 6816 with up to 7 I/O modules Includes all VLANs plus sub VLANs, super VLANs, etc. 1776 VLANs—BlackDiamond Includes all VLANs plus sub VLANs, super VLANs, etc.
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 33 • “Issues Resolved in ExtremeWare 7.0.1b11” on page 60 • “Issues Resolved in ExtremeWare 7.0.
Clarifications, Known Behaviors, and Resolved Issues Smart Redundancy Enabled in Saved Configuration Smart redundancy is always enabled in a saved configuration. To work around this, disable smart redundancy after downloading a configuration (PD2-128133503).
Clarifications and Known Behaviors Routing Traffic Through the MGMT Port Routing entries with a next hop in the management interface subnet are not removed from the routing table based on the MGMT port state (PD2-104430127). Configuring the Timezone After configuring the timezone, a soft reboot can cause the switch to boot into minimum mode (PD2-109830723). Blank Space in show port info detail Command Output The output of the show port info detail command contains several blank pages.
Clarifications, Known Behaviors, and Resolved Issues UDP Echo Transmit Rate The UDP Echo utility is designed to verify network connectivity. Transmit rates of 10 pps suffice for this function. UDP Echo rates of 20 pps should be sufficient. Do not set your UDP Echo rate higher than 100 pps, as the switch does not send replies faster than that rate (1-FAO89). The disable learning Command and Flooding The disable learning command does not remove the port from the security flood list.
Clarifications and Known Behaviors • Installed ATM, MPLS, ARM, and PoS modules • Mirroring • IPX routing • Static FDB entries If the switch reaches the limit of available port tags, the following messages appear in the syslog: tNetTask: Reached maximum otp index allocation tBGTask: Reached maximum otp index allocation If this occurs, you must compromise some features (for example, mirroring) in order to expand your use of other functionality. (1-E5U7Y).
Clarifications, Known Behaviors, and Resolved Issues Synchronize a Newly Installed MSM64i When you add a slave MSM64i, you are not prompted to synchronize. If not synchronized, the slave MSM64i uses its image and the master MSM64i configuration. This image/configuration mismatch will likely cause the switch to operate differently after a failover, thereby defeating the purpose of the dual MSM64i’s. Be sure the MSM64i’s are synchronized (PD2-101615201).
Clarifications and Known Behaviors BlackDiamond 6816 MIB Value for Input Power Voltage On the BlackDiamond 6816, the extremeInputPowerVoltage attribute in extremeSytemCommonInfo is shown as “0” and the extremePowerSupplyInputVoltage in the extremePowerSupplyTable is shown as “unknown.” These values cannot be obtained from the switch (1-841J1). Backplane Traffic On the BlackDiamond switch, all backplane traffic is tagged.
Clarifications, Known Behaviors, and Resolved Issues Summit Health Check Error Messages Error messages from the system health check display the incorrect location (PD2-110132842). Limited Commands Mode When in limited commands mode, links remain active (PD2-99220424). Summit48i Redundant PHY When the primary port of a redundant pair is disabled and the link removed, the LED for that port continues to flash indicating it has a link and is disabled (9239).
Clarifications and Known Behaviors Serial and Telnet Configuration Be sure you have specified VT-100 terminal emulation within the application you are using (2125, 2126). Be sure to maximize the telnet screen in order for automatically updating screens to display correctly (2380). Displaying Management Port with show port config The show port config command will only display the “mgmt” port configuration information if the “mgmt” port is explicitly defined in the command - i.e.
Clarifications, Known Behaviors, and Resolved Issues Default Routes or Static Routes If you define a default or static route, and then delete the VLAN on the subnet associated with the default route, the default route entry remains although it is invalid. You must manually delete the configured route. If you define multiple default routes, the one with the lowest metric is used. If there are multiple routes with the same lowest metric, the switch picks one of the routes.
Clarifications and Known Behaviors Alpine and Cross Module Load Sharing. The I/O module configured to contain the “master” port must be physically present in a cross-module load sharing group for the system to pass traffic (8589, PD2-119098401). Load Sharing and Specific Ports in a Load Share Group. Due to the load sharing algorithm used for round robin load sharing, when using 3, 5, 6 or 7 ports in a load share group packet loss will be observed when sending wire-speed traffic across the load share group.
Clarifications, Known Behaviors, and Resolved Issues Mirroring Mirroring IP Multicast Traffic. Due to IGMP Snooping capabilities, Multicast traffic may cease to be seen on a “mirror port”. If you issue a “restart” command for the mirror port or remove and reinsert the port connection, multicast traffic will resume for the IGMP Host time out period (260 sec.) (3534). Mirroring and Flooding. When a mirrored port is configured, the forwarding database for items being mirrored (e.g.
Clarifications and Known Behaviors Access List Precedence Intervals Access lists with large intervals (greater than 10) between precedence values now perform better. Previously, configuring access lists using large intervals (greater than 10) between precedence values could result in several-minute delays for each add transaction. We still recommend that you configure ACL precedence with an interval value of less than 5 between each rule.
Clarifications, Known Behaviors, and Resolved Issues Bi-Directional Rate Shaping Locking and Unlocking Learning If you configure a rate shaping port to lock learning and unlock learning, the loopback FDB is not flushed. This causes traffic destined for the port to be flooded. You must manually flush the FDB using the clear fdb command (PD2-124568416). Loopback Port Must be on Same Module The loopback port must be on the same module as the rate shaped ports.
Clarifications and Known Behaviors EAPS Performance Statistics Table 9 lists the EAPS performance statistics for a single EAPS domain with the default filter.
Clarifications, Known Behaviors, and Resolved Issues 1 The EAPS ring fails, due to a Hello timeout or a link failure. 2 The EAPS master node secondary port fails or is disabled. 3 The EAPS master node secondary port recovers or is re-enabled. The port incorrectly blocks incoming traffic even though it is enabled. ESRP and EAPS Secondary Port Configuring ESRP Host Attach on an EAPS secondary port causes a broadcast storm (1-B1O4L).
Clarifications and Known Behaviors ESRP and Load Sharing If you enable load sharing on ports that belong to more than 200 VLANs, the switch reboots. To avoid this, first enable load sharing, then add the ports to the VLANs (PD2-99259801). When using load sharing with the ESRP host attach or don't count features, configure all ports in the same load-sharing group as host attach ports or don’t-count ports (PD2-97342427, PD2-106782876).
Clarifications, Known Behaviors, and Resolved Issues VRRP The show tech-support Command Through Telnet In a configuration with more than 20 VLANs, if you use the show tech-support command on the backup switch through a telnet connection, the backup transitions to master and back. To avoid this, use the show tech-support command only through a direct console connection (PD2-128764506). Increase Advertisement Interval When CPU is Busy An extremely busy CPU can create a short dual master situation.
Clarifications and Known Behaviors Traffic Crosses Layer 3 Boundary If ingress and egress VLANs do not share a port, layer 3 traffic with a broadcast MAC and unicast IP address is incorrectly forwarded to the default route across a layer 3 boundary (PD2-119375325).
Clarifications, Known Behaviors, and Resolved Issues OSPF Default Route Entries in the IP FDB After a link transition, entries created by the OSPF originated default route are still in the IP FDB (PD2-109830730, PD2-109830723). Disable OSPF Before Adding or Removing External Area Filters If you configure an OSPF area external filter on an ABR, and the filter is set to exclude routes that have already been learned, an OSPF failure occurs.
Clarifications and Known Behaviors Redistributing BGP Routes to OSPF Redistributing 70,000 BGP routes into OSPF depletes the system resources. You must reboot the system (PD2-74932501). Removed encrypted Option from enable bgp neighbor password Command The enable bgp neighbor password command no longer has the option to encrypt the password (PD2-101778801).
Clarifications, Known Behaviors, and Resolved Issues In a “real-world” IPX environment, clients and servers generally do not lose communication with the directly attached switch for the FDB entries to age out (9338). IPX and Bi-Directional Rate Shaping Bi-directional Rate Shaping is not supported in conjunction with IPX traffic (9226, 9153).
Clarifications and Known Behaviors RADIUS and Telnet If one of the following two situations occurs: 1 You have a single RADIUS server configured with a RADIUS timeout value of 10 seconds or more 2 Both primary and secondary RADIUS servers lose their connections and the configured RADIUS timeout value is 5 seconds or more The switch might not be able to fail over to the local user authentication for telnet sessions. If this happens, the switch cannot be accessed via telnet.
Clarifications, Known Behaviors, and Resolved Issues NAT If you change the name of a VLAN that is part of your NAT configuration, the NAT rule configuation is not updated. NAT rule matching continues to operate correctly, but if you save or upload the configuration, the rule is saved or uploaded incorrectly (PD2-82963707). Vista VLAN Ports Tagging Information Incorrect In the Virtual LAN Configuration screen, the information for VLAN ports displays incorrect tagging information (PD2-130140999).
Clarifications and Known Behaviors SNMP Modular Switch get Error A get request from an NMS to a modular switch for the ifMau
Clarifications, Known Behaviors, and Resolved Issues SNMP Time-out Setting SNMP management stations may need to set the SNMP time-out value to 10 seconds as some large configuration operations take longer to perform (7151). In addition, when using SNMP tools that use the bulk get request function as opposed to generic get next requests, the MIB walk can time out and subsequently fail with the default time-out setting.
Clarifications and Known Behaviors Diagnostics and Troubleshooting The show diagnostics backplane-utilization Command Available The show diagnostics backplane-utilization command is not supported on Alpine or Summit switches. Though the command is available, there are no backplane utilization diagnostics available for Alpine or Summit switches (PD2-130597218).
Clarifications, Known Behaviors, and Resolved Issues Rebooting Using SNMP or RMONII With Reboot Loop Protection If you use SNMP or RMONII to issue the reboot command, and reboot loop protection is configured with a threshold of 1, the switch will reboot into minimal mode (PD2-111307101). Configuring a New Threshold for Reboot Loop Protection When a new threshold is configured for reboot loop protection, the time stamp is not cleared, and the reboot-threshold can be violated (PD2-109830745).
Issues Resolved in ExtremeWare 7.0.0b68 If you configure more than 10 ATM PVCs on a switch and upload the configuration, the switch no longer crashes (PD2-120100801). Summit If you download a configuration, autopolarity detection is no longer automatically enabled on the Summit48si (PD2-118279201). The configure ports auto-polarity command is no longer available on platforms other than the Summit48si (PD2-118503001). Issues Resolved in ExtremeWare 7.0.
Clarifications, Known Behaviors, and Resolved Issues IS-IS If you configure IS-IS authentication on a PoS interface, the configuration is now saved after a reboot or configuration download (PD2-108735813). If you configure authentication before enabling IS-IS on a VLAN, the VLAN interface is now correctly authenticated (PD2-108735827). Issues Resolved in ExtremeWare 7.0.0b61 The following issues were resolved in ExtremeWare 7.0.0b61. Numbers in parentheses are for internal use and can be ignored.
Issues Resolved in ExtremeWare 7.0.0b61 Multicast packets are now forwarded correctly after you disable IGMP snooping (1-EUCKP). Extended diagnostics on a P12cSi or P12cMi module cause the BlackDiamond to crash. Normal diagnostics work correctly (PD2-83547401). ESRP status change no longer cause the OSPF neighbor to crash with the following error message (PD2-81648327): “Error: Insertion FAILED Neighbor already exists.” ExtremeWare now correctly checks fan tray status (PD2-63609301).
Clarifications, Known Behaviors, and Resolved Issues The EAPS master now sends an IGMP query upon link failure, if you configure the EAPS master interface with an IP address on the same protected VLAN as the transit node (PD2-100679119, PD2-91657073, PD2-112059601). A rapid link transition up, down, then up again on an EAPS transit switch no longer causes traffic disruption (PD2-102929324). FDB IP FDB aging is now disabled by default (PD2-93733656).
Issues Resolved in ExtremeWare 7.0.0b61 The slave ESRP VLAN no longer forwards traffic when the slave link transitions without an ESRP state change (PD2-89481303).
Clarifications, Known Behaviors, and Resolved Issues 66 ExtremeWare 7.
