ExtremeWare Release Notes Software Version 7.1.1b11 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, ExtremeWare, Alpine, 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.1 Features Added or Enhanced in ExtremeWare 7.1.1 11 11 Supported Hardware BlackDiamond Component Support Alpine Component Support Summit Component Support GBIC Support 12 12 13 14 15 Mini-GBIC Support Chapter 2 Upgrading to ExtremeWare 7.1 Staying Current 17 Upgrading ExtremeWare Upgrading Switches to ExtremeWare 7.1.1 17 18 Save the Current Configuration Upgrade the BootROM to Version 8.1 Upgrade to ExtremeWare 6.1.
Contents The show log Command Truncates Long Commands The show log Display Truncates Configuration Parsing Do Not Create Single-Character Names 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.0 and Debug-Trace Upgrading to ExtremeWare 7.
Contents VDSL Modules in a Half-Duplex Link Summit Output of the show log Command The unconfigure switch all Command Clears the Default VLAN from s0 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) SNMP Trap Commands Not Supported The show ports mgmt info Output Missing Flags Press [Return] Key Twice With enable temperature-log Command User S
Contents Error Messages with Topology Changes The “C” Flag Might Be Permanently Set Mirroring Does Not Mirror STP BPDUs Topology Change Counter Might Continuously Increment Topology Change Affects All Domains that Share Ports Large STPD Configuration Download Might Reboot Switch A Large STP Configuration with 10 Link Transitions Configure Fewer than 4,000 VLANs in an STPD The show stpd ports Output Incorrect After Topology Change 802.
Contents Locking and Unlocking Learning Loopback Port Must be on Same Module 1000Base-T Ports as Loopback Ports EAPS Do Not Configure a Hello Time of 0 EAPS Performance Statistics ESRP and EAPS Secondary Port Incorrect show vlan Output IP Unicast Routing Multinetting Enabled by Default Reset the FDB Aging Timer Deleting a Static Entry Using SNMP The show iproute Output Traffic Crosses Layer 3 Boundary No Static ARP Entries ARP Entry Age Multinetting and the Show VLAN Stats Command Multinetting and VRRP
Contents CPU DoS Protect and ACL Precedence MSM Failover Clears Logins Network Login RADIUS Server Interoperability Network Login Supplicant Software Interoperability RADIUS and the BlackDiamond RADIUS and Telnet The show netlogin Command Output 52 52 52 52 52 53 53 SLB and Flow Redirection 53 Do Not Specify a Port Number in the disable slb node Command Enumeration Mode Redirects ICMP Packets Cache Servers Set To “Down” Under Sustained High Traffic Loads Health Checking Cannot be Disabled 53 53 53 53
Contents Bus-Stats Error Messages Spurious Message When system-down is Configured The use configuration Command Output of the show diagnostics Command Configure Auto-Recovery to online or Alarm-Level to traps Error Count Not Accurate Configuring Diagnostics Mode Off Disable Remote Syslog Before Enabling IPARP Debug-Tracing Documentation Summit48si LED Behavior Not Correct T-Control Requires Full Layer 3 License ExtremeWare 7.1.
Contents Security SNMP Troubleshooting 10 65 66 66 ExtremeWare 7.1.
1 Overview These Release Notes document ExtremeWare ® 7.1.1b11. ExtremeWare 7.1.1 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.1, see “Upgrading ExtremeWare” on page 17. This chapter contains the following sections: • “New Features in ExtremeWare 7.1” on page 11 • “Supported Hardware” on page 12 New Features in ExtremeWare 7.
Overview dropped. Hitless upgrade allows an ExtremeWare software upgrade on a BlackDiamond 6800 series chassis without taking it out of service or losing traffic. Supported Hardware Hardware in the following sections listed in italics is new for this release. ExtremeWare 7.0 (and later) supports “i” series or “3” series products only. ExtremeWare 7.1.1 requires BootROM 8.1. Table 1 lists software filenames for the supported hardware that requires software.
Supported Hardware Table 2: 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.8 WDMi 6.1.5 10GLRi 7.0 MPLS 7.0 ARM 7.0 P3cMi 7.0 P3cSi 7.0 P12cMi 7.0 P12cSi 7.0 A3cMi 7.0 A3cSi 7.0 DC Power Supply 6.1.5 110 VAC Power Supply 6.1.
Overview Table 3: 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 GM-WDMi 6.1.8 WM-4T1i 7.0.1 WM-4E1i 7.0.1 WM-1T3i 7.0.1 FM-8Vi 7.0.1 AC Power Supply 6.1 DC Power Supply 6.1.5 1. Older switches do not require ExtremeWare 6.2.2b56.
Supported Hardware GBIC Support GBICs supported with ExtremeWare 7.1.1, and the minimum ExtremeWare version required, include: Table 5: GBIC support GBIC ExtremeWare Required SX parallel ID 1.0 SX serial ID 2.0 LX parallel ID 1.0 LX serial ID 2.0 ZX 7.0.1b11 ZX Rev 03 7.0.1b11 LX70 2.0 LX100 6.1.9 UTP 6.1.9 SX Mini 7.0.1b11 LX Mini 7.0.1b11 ZX Mini 7.0.
Overview 16 ExtremeWare 7.1.
2 Upgrading to ExtremeWare 7.1 This chapter contains the following sections: • “Staying Current” on page 17 • “Upgrading ExtremeWare” on page 17 • “Downgrading Switches” on page 22 CAUTION You can only load ExtremeWare 7.0 (or later) on a switch running ExtremeWare 6.2.2b56 (or later). Staying Current If you are an Extreme Assist customer, the latest release and release notes are available after logging in to the Tech Support web site at http://www.extremenetworks.com/go/esupport.htm.
Upgrading to ExtremeWare 7.1 Upgrading Switches to ExtremeWare 7.1.1 To install ExtremeWare 7.1.1, you must: 1 Save the configuration to a TFTP server. 2 Upgrade the BootROM to Version 8.1 as described on page 19. 3 Upgrade to ExtremeWare 6.1.9 as described on page 19. 4 Upgrade to ExtremeWare 6.2.2b56 as described on page 19. 5 Upgrade to ExtremeWare 7.1.1 as described on page 20. 6 Upgrade ATM, MPLS, ARM, PoS, T1, E1, or T3 Modules as described on page 21. If you have already installed ExtremeWare 6.1.
Upgrading ExtremeWare 6 Upload the configuration to a TFTP server for safekeeping using the upload configuration command. Upgrade the BootROM to Version 8.1 Before you upgrade ExtremeWare, upgrade to BootROM 8.1 (BootROM 8.1 is compatible with all ExtremeWare versions back to ExtremeWare 6.1.9): 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.
Upgrading to ExtremeWare 7.1 3 Verify that the correct BootROM and ExtremeWare version are loaded using the show switch and show version commands. 4 TFTP download the saved configuration, and answer y at the prompt to reboot the switch. 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.
Upgrading ExtremeWare You can ignore any diagnostics failure messages generated by the synchronization. 10 Reboot the switch using the reboot command. 11 If you are using the Network Login campus mode: a Manually enable Network Login using the enable netlogin [web-based | dot1x] command. b Verify that users are able to authenticate and successfully access network resources.
Upgrading to ExtremeWare 7.1 9 TFTP download the latest ExtremeWare 7.1.1 build to the primary image space using the download image primary command. 10 Reboot the switch using the reboot command. 11 TFTP download the configuration you saved in Step 1, and enter y to reboot the switch. 12 Check the log for configuration errors. Manually enter configurations that did not load. 13 Save the new configuration to the primary space.
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 8: Supported limits Metric Description Limit Access List rules Maximum number of Access Lists (best case).
Supported Limits Table 8: Supported limits (continued) Metric Description Limit BGP—AS-Path filters Maximum number of AS-Path filters per switch. 128 BGP—AS-Path filter add entries Maximum number of AS-Path filter add entries per switch. 256 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.
Supported Limits Table 8: Supported limits (continued) Metric Description Limit ESRP—Route-track entries, Summit, Alpine, BlackDiamond Maximum number of routes that can be tracked for each ESRP domain. 4 ESRP—maximum VLAN tracks Maximum numbers of VLAN tracks per VLAN. 1 FDB—maximum ports for permanent entries Maximum number of ports supported for permanent FDB entries.
Supported Limits Table 8: Supported limits (continued) Metric Description Limit IS-IS—maximum redistributed routes, both metrics Maximum IS-IS redistributed routes using both metrics. 10,000 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 MAC-based security Maximum number of MAC-based security policies.
Supported Limits Table 8: Supported limits (continued) Metric Description Limit OSPF adjacencies—Summit7i, Alpine, BlackDiamond Maximum number of OSPF adjacencies on a switch with 256 MB memory. 225 Policy Based Routing Maximum number of policy based routes that can be stored on a switch. 64 RIP-learned routes Maximum number of RIP routes supported without aggregation. 8000 RIP interfaces on a single router Recommended maximum number of RIP routed interfaces on a switch.
Supported Limits Table 8: Supported limits (continued) Metric Description Limit Spanning Tree—number of ports Maximum number of ports that can participate in a single Spanning Tree Domain. 4096 Spanning Tree—minimum number of ports Minimum number of ports that can participate in a single Spanning Tree Domain. 1 Spanning Tree—minimum number of domains/port Minimum number of Spanning Tree Domains that can be configured per port.
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 29 • “Issues Resolved in ExtremeWare 7.1.1b11” on page 59 • “Issues Resolved in ExtremeWare 7.1.
Clarifications, Known Behaviors, and Resolved Issues The show log Command Truncates Long Commands If you download a configuration, the output of the show log command might not completely display commands longer than 240 characters. This is a display problem; the configuration loads correctly (PD2-171470611). The show log Display Truncates Configuration Parsing If you download a configuration and use the show log command to view the parsing of the configuration, the log does not display the entire parsing.
Clarifications and Known Behaviors Upgrading to ExtremeWare 7.0 and Bi-Directional Rate Shaping When you directly upgrade from ExtremeWare 6.2.2 to ExtremeWare 7.0, bi-directional rate shaping does not work if the loopback ports were in autonegotiation mode. This behavior is not displayed by 10/100Base-T or Gigabit fiber ports. A workaround is to remove and re-add the loopback ports to the VLAN (PD2-107820904). Upgrading to ExtremeWare 7.0 and Debug-Trace When you directly upgrade from ExtremeWare 6.2.
Clarifications, Known Behaviors, and Resolved Issues BOOTP-Dependent Routes in Downloaded Configuration not Created Static and default routes that depend on a BOOTP IP address/subnet are not created when you download a configuration (PD2-86888351). The disable learning Command and Flooding The disable learning command does not remove the port from the security flood list. Thus, you cannot disable flooding when learning is disabled (PD2-73199618).
Clarifications and Known Behaviors Table 9: Cross-module trunking module support (continued) Module CMT Support G16X3 Yes G24T3 Yes F32Fi Yes F48Ti Yes F96Ti Yes WDMi No 10GLRi Yes MPLS No ARM No P3cMi Yes P3cSi Yes P12cMi Yes P12cSi Yes A3cMi Yes A3cSi Yes Cross module trunking is not supported on WDMi modules (PD2-176314520).
Clarifications, Known Behaviors, and Resolved Issues Do Not Reboot Immediately After Synchronizing Using the reboot command immediately after the synchronize command, but before the MSM’s have finished synchronizing, might corrupt the configuration. To avoid this, wait for the MSM’s to synchronize before rebooting. The “state” column in the output of the show msm-failover command displays “ready” when the synchronization is complete (PD2-171614101).
Clarifications and Known Behaviors 4,000 VLANs on a BlackDiamond If you configure more than 4,000 VLANs, EDP might crash, causing ESRP to fail (PD2-153821210). E1 Module and the restart port Command After you use the restart port command, E1 modules occasionally fail to establish a physical link (PD2-85857901). PPP Links Through E1 modules PPP links through the E1 module are not always re-established after a reboot. To re-establish the PPP link, use the restart ports command (PD2-109252301).
Clarifications, Known Behaviors, and Resolved Issues Table 10: Memory scanning and mapping support in BlackDiamond modules Module Memory Scanning and Mapping F32Fi Yes F48Ti Yes F96Ti Yes G12SXi Yes G8Ti Yes G8Xi Yes WDMi Yes MSM-3 Yes MSM64i Yes 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 “un
Clarifications and Known Behaviors 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). Summit48i Single Fiber Signal Loss The Summit48i is currently not able to detect a single fiber strand signal loss due to the hardware based Auto Negotiation parameters (10995).
Clarifications, Known Behaviors, and Resolved Issues Switching and VLANs Saving ip-mtu Settings Dynamic TLS (Martini TLS) checks the MTU received from its peer in order for TLS to come to the established state. It compares against the egress VLAN’s IP-MTU. If the egress VLAN does not have an IP address defined, any non-default ip-mtu setting will not be saved through a switch reboot (PD2-64084527).
Clarifications and Known Behaviors Cannot Add FDB Entry for Management VLAN You cannot add an FDB entry for the management VLAN (PD2-156475718) Static FDB Entries and Rate-Shaping If you create a static FDB entry on a port configured for rate-shaping, the static entry incorrectly ages out. Static entries should not age out (PD2-97150551). MAC Security The source FDB address configuration will not discard ICMP packets (16340). FDB Aging Timer In ExtremeWare 6.2.
Clarifications, Known Behaviors, and Resolved Issues 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. This occurs because some ports will be selected to transmit more packets than other ports resulting in bandwidth over-subscription and subsequent packet loss.
Clarifications and Known Behaviors 802.1w Topology Change Might Cause FDB Flush of Edge Ports 802.1w topology changes might cause the FDB to flush and re-learn edge ports (PD2-161413529). FDB Not Flushed After Link Failure with RSTP When using RSTP, the FDB is not flushed when recovering from a link failure. This is the expected behavior (PD2-143730501).
Clarifications, Known Behaviors, and Resolved Issues Configure Fewer than 4,000 VLANs in an STPD If you add more than 4,000 VLANs to an STP domain, the switch might run out of memory (PD2-135842818). The show stpd ports Output Incorrect After Topology Change Occasionally, after an 802.1w topology change, the flag in the output of the show stpd ports command still displays TC (PD2-115121007). 802.1w and IGMP Snooping If you are using 802.1w and IGMP snooping, an 802.
Clarifications and Known Behaviors High Traffic with 120 STP Instances If you configure more than 120 STP instances and more than 130 VLANs, and lose a link while forwarding a high traffic load, the port might be unstable (PD2-118500801). Configuring a VLAN from Vista If you create an STPD using ExtremeWare 6.1.9 (or earlier), add a VLAN, save the configuration, upgrade to ExtremeWare 6.2.
Clarifications, Known Behaviors, and Resolved Issues operating, and the console unlocks after the processing finishes. To work around this, either wait before disabling s0, or wait until the console unlocks (PD2-159834277, PD2-151426418). Failure of Direct Link Causes Flip If you have a direct link between the master and slave switch, and that link fails, the master transitions to slave and back to master. To avoid this, configure both load-sharing links to don’t count (PD2-157406636, PD2-148539301).
Clarifications and Known Behaviors VRRP Backup Transition Creates Duplicate Packets A VRRP transition from backup to master might cause duplicate data packets to be transmitted for a short period of time. The packets are dropped, so no action is required (PD2-129379226). QoS Duplicate Precedence Rules If you create an ACL rule with the same precedence as an existing rule, an error message warns you of the duplication. However, the rule is still created.
Clarifications, Known Behaviors, and Resolved Issues Creating Access Lists from Multiple Sessions When creating or modifying access control lists, please ensure that no other administrator sessions are attempting to create or modify the system access control lists simultaneously. This may result in data corruption (1-579HD). 5,120 Access Lists and SNMP Although you can configure up to 5,120 ACLs, SNMP only recognizes 1,280.
Clarifications and Known Behaviors EAPS Performance Statistics Table 11 lists the EAPS performance statistics for a single EAPS domain with the default filter.
Clarifications, Known Behaviors, and Resolved Issues IP Unicast Routing Multinetting Enabled by Default Multinetting is enabled by default (PD2-129703201). Reset the FDB Aging Timer When you disable multinetting, you must reset the FDB aging timer to 300 seconds using the configure fdb agingtime command (PD2-160697401). Deleting a Static Entry Using SNMP If you delete a static IPARP entry using SNMP, the line in the configuration creating that entry is not deleted.
Clarifications and Known Behaviors RIP in Conjunction with other Routing Protocols It is recommended that RIP be enabled only on routers running with less than 10,000 routes from other routing protocols, such as BGP or OSPF. OSPF AS-external LSAs Might Not Be Regenerated AS-external LSAs are not regenerated after an active LSA is removed or a neighbor goes down (PD2-149426154).
Clarifications, Known Behaviors, and Resolved Issues Default Route Might Not Be Deleted If you have the export of static BGP routes enabled, the IP route table has a default static route and BGP is redistributing the default route using the configure bgp add network command, then after you delete the default route from BGP using the configure bgp delete network command, the default BGP route is not withdrawn from the neighbor’s table (PD2-159150038).
Clarifications and Known Behaviors Cisco Interoperation For proper Cisco interoperation, use Cisco IOS version 11.3 or better, which supports PIM 2.0. Cisco customer support also recommends using PIM in favor of DVMRP whenever possible on Cisco routers (4669). Traffic Rate Exceeding Last Hop Threshold When the traffic rate exceeds the configured last hop threshold, the last hop does not initialize; but if the sending traffic rate is set to 50 Kbps, it switches to STP correctly (1-57NMY).
Clarifications, Known Behaviors, and Resolved Issues precedence to the rules created first, instead of giving precedence to the most specific rule (PD2-157416614). CPU DoS Protect and ACL Precedence If you configure the CPU DoS protect feature with a filter precedence of x, you cannot create an access list with a precedence of x, x+1, or x+2. All other values are acceptable.
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 Vista Cannot Enable STP You cannot enable a STP domain using Vista. If you try, Vista does not generate an error message, but does not enable STP. (PD2-158471801). Alpine 3808 Erroneously Displays Four PSUs Vista displays PSU C and PSU D on an Alpine 3808 chassis.
Clarifications and Known Behaviors Configuration Options with Large Number of Interfaces When selecting a configuration applet with a large number of configured interfaces, the traversal of the VLAN interfaces by Vista can cause a Watchdog reset due to the task utilization of Vista during the interface data collection. It is recommended that Vista not be used for configurations with Watchdog enabled where the Vista Configuration applet is used with a large number of VLAN interfaces.
Clarifications, Known Behaviors, and Resolved Issues SNMP ifAdminStatus MIB Value The SNMP ifAdminStatus MIB value is not saved after a reboot. Ports set to down in the SNMP ifAdminStatus MIB come back up after rebooting. However, if you save the configuration using the CLI or SNMP after changing the port status to down in the ifAdminStatus MIB, the change is saved after a reboot (2-GOQMD).
Clarifications and Known Behaviors Extreme Power Supply Traps A new object was added “extremePowerSupplyNumber” to the power supply traps. The two RPS traps will no longer be sent out. Instead the extremePowerSupplyGood and extremePowerSupplyFail traps will contain the power supply number indicating which power supply has failed (1-7J56T). DHCP The DHCP server is not supported as a standalone feature. It is used as part of the Network Login feature only (1-8SAI6).
Clarifications, Known Behaviors, and Resolved Issues Packet Diagnostics Display Wrong Slot Name When you run packet diagnostics on the MSM in slot B, the console displays the slot as slot 10, instead of MSM-B. The display is wrong: the diagnostics are correctly running on the MSM in slot B. The extended diagnostics console display is correct (PD2-138607801).
Issues Resolved in ExtremeWare 7.1.1b11 Disable Remote Syslog Before Enabling IPARP Debug-Tracing With remote syslog enabled, if you configure the IPARP debug-trace to level 2 or higher, the switch hangs and is rebooted by the watchdog timer. To avoid this, disable the remote syslog prior to configuring the debug-trace (PD2-110983505). Documentation Summit48si LED Behavior Not Correct The Summit48si LED behavior described in the Consolidated Hardware Guide is not correct (PD2-170120478).
Clarifications, Known Behaviors, and Resolved Issues STP When connected to a Catalyst switch running IOS 12.1(8)EA1b no longer generates spurious STP error messages (PD2-177504915). EAPS The virtual port state of a shared port that has gone down is now correct, so the EAPS v2 shared port’s connectivity is maintained (PD2-175769104). SNMP The SNMP v1 EDPneighbor trap agent no longer has the address set to 0.0.0.0 (PD2-180021028). Issues Resolved in ExtremeWare 7.1.
Issues Resolved in ExtremeWare 7.1.1b8 General Upgrading Summit or BlackDiamond switches to ExtremeWare 7.1 with an existing configuration containing the disable ipforwarding lpm-routing command no longer generates “disable lpm” messages in the log (PD2-139986201, PD2-145444601). BlackDiamond If you download a configuration containing the configure ppp mru command, that command now loads correctly (PD2-158075064).
Clarifications, Known Behaviors, and Resolved Issues SNMP If you enable SNMP traps, you no longer have to configure at least one valid trap receiver. SNMP traps are enabled by default (PD2-161413602, PD2-159834250). If you have one of the following: • Alpine chassis running ExtremeWare 6.2.2b108 • Alpine chassis running ExtremeWare 6.2.2b134 with transceiver diagnostics enabled and you upgrade to ExtremeWare 7.1, the SNMPv3 reboot counter is no longer corrupted (PD2-161834101).
Issues Resolved in ExtremeWare 7.1.0b48 If you have the system watchdog timer enabled, executing the show fdb port command on an ATM or PoS port no longer causes the system to reboot (PD2-134826401). Routing entries with a next hop in the management interface subnet are now correctly removed from the routing table based on the MGMT port state (PD2-104430127). On a BlackDiamond 6816, the run diagnostics extended msm-d command no longer generates a system test error (PD2-134478009).
Clarifications, Known Behaviors, and Resolved Issues The enable rip originate-default command now always advertises the default RIP route to peers (PD2-124368763). OSPF After a link transition, entries created by the OSPF originated default route are no longer in the IP FDB (PD2-109830730). When the LSDB has two as-external LSAs for the same destination with a forwarding address, the best metric route is now selected (PD2-140720001).
Issues Resolved in ExtremeWare 7.1.0b48 If you configure the VRRP master priority to 0 (releasing it as the virtual router) and then configure the priority to 255, the master is now released (PD2-127681312). The track-diagnostic and track-environment features are now supported with VRRP (PD2-127681344). If you configure a new advertisement interval and then reconfigure the interval back to the default, VRRP no longer elects two master VRRP VLANs (PD2-127681301).
Clarifications, Known Behaviors, and Resolved Issues SNMP Adding or deleting a trapreceiver now detects the correct community string (1-9I5LD). You can now configure the same community string for both read-only and read-write (PD2-118578301). Troubleshooting Output from the show diagnostics command now clearly states the number of recoverable and non-recoverable errors found (PD2-142201419). When a new threshold is configured for reboot loop protection, the time stamp is now cleared (PD2-109830745).
