50 Minuteman Rd. Andover, MA 01810 USA Tel: (978) 684-1000 CUSTOMER RELEASE NOTES X-Pedition Router System Firmware Version E9.1.7.0 System Firmware Release Date: September 2003 INTRODUCTION: This document provides specific information relevant to version E9.1.7.0 of the System Firmware for the X-Pedition family of products. It includes content from the E9.0.7.7 System Firmware Maintenance Release and the E9.1.3.0A patch release.
SYSTEM FIRMWARE SPECIFICATION SYSTEM FIRMWARE SPECIFICATION: Before installing the E9.1.7.0 System Firmware, the Boot Firmware should be upgraded to at least version E3.2.0.0. Refer to the E3.2.0.0 Boot Firmware Release Notes, or any X-Pedition Getting Started Guide, for instructions on upgrading the Boot Firmware.
RELEASE NAMING CONVENTION RELEASE NAMING CONVENTION: Normally, the X-Pedition product family supports two active release lines. The older line is always in maintenance only mode and receives only maintenance improvements—the newer line receives maintenance improvements and introduces new features. For a brief time, however, the X-Pedition will support a special third line—E9.0.8. This line introduces the Security Attack Monitor (SAM) feature on the E9.0 code base. E9.0.
RELEASE NAMING CONVENTION A release line is defined by the first two digits in the name, e.g. E9.0 and E9.1. The third digit increments with each release during the development phase of a line. For example, E9.0.7.0 is the seventh development release for the E9.0 line. The fourth digit is incremented with each release during the maintenance-only period of a release line. Thus E9.0.7.4 is the fourth maintenance-only release for the E9.0 line.
HARDWARE / FIRMWARE COMPATIBILITY HARDWARE / BOOT FIRMWARE/ SYSTEM FIRMWARE COMPATIBILITY: The Minimum Boot Firmware Version is a function of: • The hardware installed in the system (as listed below). • The version of VFS used. For more information on VFS versions see the “PCMCIA Card VFS Version” subsection in the “INSTALLATION AND CONFIGURATION NOTES” section of the X-Pedition Boot Firmware Release Notes. • The need for new features or corrections that are provided in a specific version.
HARDWARE / FIRMWARE COMPATIBILITY This version of System Firmware supports the X-Pedition Router hardware listed in the following table: Part Description Minimum System Firmware Version Minimum Boot Firmware Version 1.1.0.8 5SSRM-02 6SSRLC-FX-AA Router module for the Matrix E5 8-port 100BASE-FX (MT-RJ) module for 5SSRM-02 and 6SSRM-02 E8.0.1.0 3.0.50.
HARDWARE / FIRMWARE COMPATIBILITY Part Description Minimum System Firmware Version SSR-2-LX70 SSR-2-LX70-AA 1-port 70 km 1000BASE-LX module for X-Pedition 2000 1-port 70 km 1000BASE-LX module for X-Pedition 2000 2.0.0.0 3.0.0.
HARDWARE / FIRMWARE COMPATIBILITY Part SSR-HTX32-16 SSR-MEM-128 SSR-MEM-256 Description 16-port 10/100 TX module (Cat 5 RJ-45) with 16 MB [T-Series] for X-Pedition 8000/8600 128MB Memory Upgrade Kit for SSR-CM2-64, SSR-CM2-128, SSR-CM3-128, and ER16-CM3-128 256MB ECC Memory Upgrade Kit for SSR-CM4-256 and ER16-CM4-256 Minimum System Firmware Version Minimum Boot Firmware Version 3.1.0.0 1.1.0.0 1.1.0.2 E9.0.7.4 or E9.1.3.0 1.0.0.0 E3.3.0.0 E3.0.0.
HARDWARE / FIRMWARE COMPATIBILITY Part Description Minimum System Firmware Version Minimum Boot Firmware Version XP-2-LX70-AA XP-2-SER-AA 1-port 70 km 1000BASE-LX module for X-Pedition 2400 2-port Serial module (No compression or encryption) for X-Pedition 2400 E9.0.0.0 E9.0.0.
HARDWARE / FIRMWARE COMPATIBILITY The following table lists supported hardware that is System Firmware and Boot Firmware version independent.
HARDWARE REQUIREMENTS HARDWARE REQUIREMENTS TABLE: NOTE: X-Pedition line card hardware makes use of three basic ASIC versions (pre AA-series, AA-series and Tseries). The features supported by each line card are roughly defined by which series of ASIC hardware is used on that card.
HARDWARE REQUIREMENTS 10/02/03 P/N: 9038090-53 F0615-J Per Port Rate Limiting Aggregate Rate Limiting Jumbo Frame Support Weighted Fair Queuing Weighted Random Early Detection 802.
HARDWARE REQUIREMENTS Pre AA 2 Multiple IPX Encapsulation Per Port Rate Limiting Aggregate Rate Limiting Jumbo Frame Support Weighted Fair Queuing Weighted Random Early Detection 802.
NETWORK MANAGEMENT SOFTWARE SUPPORT NETWORK MANAGEMENT SOFTWARE SUPPORT: The following table displays information on the Network Management Software that supports this release: NMS Platform NetSight Element Manager Version 3.1 NetSight Atlas Console 1.2 NetSight Atlas Console Lite 1.2 NetSight Atlas Inventory Manager 1.3 NetSight Atlas Router Services Manager 2.
INSTALLATION AND CONFIGURATION NOTES INSTALLATION AND CONFIGURATION NOTES: Password Recovery If an X-Pedition password is lost and the user is unable to log in or enter Enable mode, please refer to the Enterasys Global Knowledgebase at http://knowledgebase.enterasys.com/esupport/ . Click Search by ID and enter TK0306-9.
NEW FEATURES AND ENHANCEMENTS IN E9.1.7.0 NEW FEATURES AND ENHANCEMENTS IN E9.1.7.0: NEW FIRMWARE SUPPORT The E9.1.7.0 system firmware provides support for the new features and enhancements below. For more information on any of these enhancements, please see the Enterasys X-Pedition User Reference Manual or Native CLI Reference Manual. 10-Gig Support of Link Aggregation SmartTRUNK no protocol link aggregation is now supported on 10-Gig interface modules (ER16-OS26-01 and ER16-OS16-01).
NEW FEATURES AND ENHANCEMENTS IN E9.1.7.0 Display of the System FPGA Revision A capability has been added that permits the display of the system FPGA revision number as illustrated in the example below. SYSTEM# system show hardware Hardware Information : System type : ER16, Rev. 0 CPU Module type : CPU-ER16 (CM4), Rev. 0 Processor : R7000, Rev 3.2, 380.00 MHz Icache size : 16 Kbytes, 32 bytes/line Dcache size : 16 Kbytes, 32 bytes/line CPU Board frequency : 95.00 MHz Backplane frequency : 62.
NEW FEATURES AND ENHANCEMENTS IN E9.1.7.0 NEW HARDWARE SUPPORT 10-Gigabit Ethernet (ER16-OS16-01) This release introduces support for the ER16-OS16-01, an optical fiber-based 10-Gigabit Ethernet module for the ER16 platform. This one slot card provides a single modular port of IEEE 802.3ae standards-based connectivity and its optical interfaces are based on fully compliant IEEE 802.3ae SC duplex fiber-optic connectors.
ISSUES RESOLVED IN E9.1.7.0 ISSUES RESOLVED IN E9.1.7.0: The following tables provide brief descriptions of the issues resolved in this release. E9.1.7.0 includes all issues resolved in the E9.0.7.7 System Firmware Maintenance Release (see the E9.0.7.7 Release Notes for details). 10-Gigabit I.D. Priority queue settings on the ER16-OS26-01 may cause the X-Pedition to experience ingress buffer overflows.
ISSUES RESOLVED IN E9.1.7.0 Hot Swap I.D. Under rare circumstances, the system may occasionally core when hot swapping a line card into the router. Internet Protocol (IP) F2333 I.D. If an X-Pedition with ip enable reverse flow all configured receives an invalid TCP/UDP packet of a specific type, the router may core. Layer-4 F4345 I.D. An X-Pedition configured with Layer-4 bridging will respond incorrectly to an ICMP request that is not destined for the router.
ISSUES RESOLVED IN E9.1.7.0 Protocol Independent Multicast (PIM-SM) I.D. When running PIM in an equal cost multi-path environment, if a multicast traffic link goes down and comes back up, the client may receive duplicate packets. F4436 If a user comments the pim global start command out of the configuration, the router will write a Layer-3 drop flow when it receives a new multicast stream. The status of the stream does not change when the command is commented back into the configuration.
ISSUES RESOLVED IN E9.1.7.0 SmartTRUNK I.D. When SmartTRUNK links carrying multicast traffic go down in a Layer-2 IGMP environment, traffic may not fail over to active links in the SmartTRUNK. Furthermore, after the downed links are reestablished, multicast traffic may travel over more than one link in the SmartTRUNK, causing the client to receive duplicate packets. Spanning Tree Protocol (STP) I.D.
KNOWN RESTRICTIONS AND LIMITATIONS KNOWN RESTRICTIONS AND LIMITATIONS: Known Restrictions and Limitations are sorted alphabetically by topic heading. 10-Gigabit Ethernet I.D. PIM is not currently supported. F2025 If a single smarttrunk add ports command contains more than one 10-Gig port, hot swapping one of the ports out of, then back into the router prevents the port from rejoining the SmartTRUNK.
KNOWN RESTRICTIONS AND LIMITATIONS Multicast On a non-T-series line card, it is recommended that access ports be used when running a multicast routing protocol such as PIM or DVMRP, due to the fact that multicast packets can be replicated to only one IP VLAN in an 802.1Q trunk port. I.D. Hardware Limitation On a T-series line card, multicast packets will be replicated to multiple IP VLANs in an 802.1Q trunk port.
KNOWN RESTRICTIONS AND LIMITATIONS Protocol Independent Multicast (PIM-SM) Using the all option of the pim sparse set interface configuration command fails to set the timer options. Users must set these options individually, using each interface name and IP address. Entering the pim sparse set component mrt-spt-mult # command from configuration mode places the command in the router’s active configuration; however, the command does not appear in the configuration for GateD and is therefore not set.
INFORMATIONAL NOTES AND STATEMENTS INFORMATIONAL NOTES AND STATEMENTS: This section contains items previously listed in the Known Restrictions and Limitations section. These items are not limitations, but informational statements and notes about the firmware and hardware features of the X-Pedition products. The following tables lists the designations used to denote where information on the statement is now located.
COMPLIANCE / STANDARD SUPPORT COMPLIANCE SUPPORT: Compliance Level Year 2000 Compliant Yes IEEE STANDARDS MIB SUPPORT: Standard IEEE 802.3ad Title LACP IEEE STANDARDS SUPPORT: Standard IEEE 802.1D IEEE 802.1p IEEE 802.1Q IEEE 802.1w IEEE 802.3 IEEE 802.3ad IEEE 802.3u IEEE 802.3x IEEE 802.3z Title Spanning Tree Traffic Prioritization VLAN Trunking Rapid Spanning Tree 10 Mbps Ethernet LACP (Link Aggregation) 100BASE-T Ethernet Full Duplex Ethernet 1000 Mbps Ethernet IETF STANDARDS SUPPORT: RFC No.
COMPLIANCE / STANDARD SUPPORT RFC No.
COMPLIANCE / STANDARD SUPPORT IETF STANDARDS MIB SUPPORT: RFC No.
COMPLIANCE / STANDARD SUPPORT IETF EXPERIMENTAL MIB SUPPORT: Function DVMRP IGMP Draft Draft 4 Draft 5 FRAME RELAY STANDARD SUPPORT: Standard Frame Relay Forum FRF.1.1 Frame Relay Forum FRF.3.1 ITU-T Q.922/ANSI T1.618 ITU-T Q.933 ITU-T I.122/ANSI T1S1 ITU-T Annex D/ANSI T1.
COMPLIANCE / STANDARD SUPPORT Enterasys Networks Private Enterprise MIBs are available in ASN.1 format from the Enterasys Networks Support web site at: http://www.enterasys.com/support/mibs/. Indexed MIB documentation is also available. SNMP TRAP SUPPORT: RFC No.
