X-Pedition Router – Maintenance Release System Firmware

35 Industrial Way
PO Box 5005
Rochester, NH 03867-5005
(603) 332-9400
CUSTOMER RELEASE NOTES
X-Pedition Router – Maintenance Release
System Firmware Version E8.2.1.1
Firmware Release Date: October 2001
INTRODUCTION:
This document provides specific information for version E8.2.1.1 of the System Firmware for the X-Pedition
Router family of products. It includes content from the E8.1.0.10, E8.1.0.11, and E8.1.0.12 Patch Releases, as
well as the E8.2.0.2, E8.2.0.3, E8.2.0.4 and E8.2.0.5 Patch Releases.
Enterasys Networks recommends these Release Notes be thoroughly reviewed prior to the installation or upgrade of
this product.
GLOBAL SUPPORT:
Enterasys
By Phone:
By Email:
By Web:
By Fax:
By Mail:
Global Technical Assistance Center
(603) 332-9400
support@enterasys.com
http://www.enterasys.com/support
(603) 337-3075
Enterasys Networks, Inc.
P.O. Box 5005
Rochester, NH 03867-5005
For information regarding the latest firmware available, recent release note revisions, or if additional assistance is
required, please visit the Enterasys Networks Support web site.
10/24/01 P/N: 9038090-17
F0615-F
Subject to Change Without Notice
Page: 1 of 34
SYSTEM FIRMWARE SPECIFICATION
SYSTEM FIRMWARE SPECIFICATION:
Before installing the E8.2.1.1 System Firmware, the Boot Firmware should be upgraded to version
E3.1.0.0. Refer to the E3.1.0.0 Boot Firmware Release Notes, or any X-Pedition Getting Started Guide, for
instructions on upgrading the Boot Firmware.
System Firmware File Name
xp8210
xp8200
ssr8100
ssr8010
ssr8000
ssr3200
ssr3100
ssr3010
ssr3002
ssr3000
ssr2220
ssr2201
ssr2200
ssr2101
ssr2100
ssr2000
ssr1200
ssr1100
ssr1010
ssr1000
10/24/01 P/N: 9038090-17
F0615-F
Version No.
E8.2.1.1
E8.2.0.0
E8.1.0.0
E8.0.1.0
E8.0.0.0
3.2.0.0
3.1.0.0
3.0.1.0
3.0.0.2
3.0.0.0
2.2.2.0
2.2.0.1
2.2.0.0
2.1.0.1
2.1.0.0
2.0.0.0
1.2.0.0
1.1.0.0
1.0.1.0
1.0.0.0
Release Date
October 2001
June 2001
February 2001
October 2000
September 2000
May 2000
April 2000
March 2000
November 1999
October 1999
September 1999
May 1999
April 1999
February 1999
December 1998
November 1998
September 1998
August 1998
June 1998
April 1998
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 2 of 34
HARDWARE / BOOT FIRMWARE COMPATIBILITY
HARDWARE / BOOT FIRMWARE COMPATIBILITY:
This version of System Firmware supports the X-Pedition Router hardware listed in the following table.
The Minimum Boot Firmware Version is a function of:
• The hardware installed in the system (as listed below).
• The version of VFS you want to use. For more information on VFS versions see the “PCMCIA Card VFS
Version” sub-section in the following “INSTALLATION AND CONFIGURATION NOTES” section of the XPedition Router Boot Firmware Version E3.1.0.0 Release Notes.
• The need for new features or corrections that are provided in a specific version.
The issue of determining your minimum Boot Firmware version can be avoided by installing Boot Firmware
version E3.1.0.0. For more information, please see the X-Pedition Router Boot Firmware Version E3.1.0.0
Release Notes.
For the two SSR-PCMCIA part numbers listed below, sub-part numbers, e.g. 35-028-02, are also listed. Find the
sub-part number on your SSR-PCMCIA card. Then match it with a sub-part number listed above to aid in
determining your minimum System Firmware and Boot Firmware versions.
Part
Description
Minimum
System
Firmware
Version
5SSRM-02
6SSRLC-FX-AA
6SSRLC-LX-AA
6SSRLC-LX70-AA
6SSRLC-SER-AA
6SSRLC-SERC-AA
6SSRLC-SERCE-AA
6SSRLC-SX-AA
6SSRLC-TX-AA
6SSRM-02
ER16-04
ER16-08
ER16-AC
ER16-CK
ER16-CM3-128
ER16-CM4-256
ER16-CS
ER16-FN
ER16-SF
ER16-SX-08
ER16-TX-24
ER16-TX-32
SSR-16
SSR-2-B128
SSR-2-FX
SSR-2-FX-AA
SSR-2-GSX
SSR-2-HSSI-AA
SSR-2-LX
SSR-2-LX-AA
SSR-2-LX70
SSR-2-LX70-AA
SSR-2-SER
SSR-2-SER-AA
SSR-2-SERC
SSR-2-SERC-AA
SSR-2-SERCE
SSR-2-SERCE-AA
Router module for the Matrix E5
8-port 100Base-FX (MTRJ) module for 5SSRM-02 and 6SSRM-02
2-port 1000Base-LX module for 5SSRM-02 and 6SSRM-02
1-port 1000Base-LX 70 KM module for 5SSRM-02 and 6SSRM-02
2-port Serial module (No compression or encryption) for 5SSRM-02 and 6SSRM-02
4-port Serial module with compression (No encryption) for 5SSRM-02 and 6SSRM-02
4-port Serial module with compression & encryption for 5SSRM-02 and 6SSRM-02
2-port 1000Base-SX module for 5SSRM-02 and 6SSRM-02
8-port 10/100Base-TX module for 5SSRM-02 and 6SSRM-02
Router module for the Matrix E6 (SS6000) and Matrix E7
4-port 1000Base GBIC module [T-Series] for ER16
8-port 1000Base GBIC module [T-Series] for ER16
AC power supply for ER16
Clock module for ER16
Control Module 3 (291 MHz CPU) with 128MB for ER16
Control Module 4 (380 MHz CPU) with 256MB for ER16
ER16 Chassis with 16 slots. Comes with ER16-CK, ER16-FN, and ER16-SF.
Fan Tray module for ER16
Switching Fabric module for ER16
8-port 1000Base-SX module [T-Series] for ER16
24-port 10/100 Base-TX module [T-Series] for ER16
32-port 10/100 Base-TX module [T-Series] for ER16
X-Pedition 8600 Chassis with 16 slots. Comes with SSR-FAN-16 and SSR-SF-16.
X-Pedition 2000 Base Configuration with 16-ports 10/100 TX and 128 MB memory
8-port 100BaseFX (MTRJ) module for X-Pedition 2000
8-port 100BaseFX (MTRJ) module for X-Pedition 2000
X-Pedition 2100 with 8-ports 1000Base-SX
2-port HSSI module for X-Pedition 2000
2-port 1000Base-LX module for X-Pedition 2000
2-port 1000Base-LX module for X-Pedition 2000
1-port 70 km 1000Base-LX module MB for X-Pedition 2000
1-port 70 km 1000Base-LX module MB for X-Pedition 2000
2-port Serial module (No compression or encryption) for X-Pedition 2000
2-port Serial module (No compression or encryption) for X-Pedition 2000
4-port Serial module with compression (No encryption) for X-Pedition 2000
4-port Serial module with compression (No encryption) for X-Pedition 2000
4-port Serial module with compression and encryption for X-Pedition 2000
4-port Serial module with compression and encryption for X-Pedition 2000
E8.0.1.0
3.0.50.11
3.0.50.11
3.0.50.11
3.0.50.11
3.0.50.11
3.0.50.11
3.0.50.11
3.0.50.11
3.0.50.11
E8.0.0.0
E8.0.0.0
E8.0.0.0
E8.0.0.0
E8.0.0.0
E8.2.0.0
E8.0.0.0
E8.0.0.0
E8.0.0.0
E8.0.0.0
E8.0.0.0
E8.0.0.0
1.2.0.0
3.1.0.0
2.1.0.1
3.0.0.0
2.2.0.1
E8.0.0.0
1.2.0.0
3.0.0.0
2.0.0.0
3.0.0.0
2.1.0.0
3.0.0.0
2.1.0.0
3.0.0.0
2.1.0.0
3.0.0.0
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Minimum
Boot
Firmware
Version
1.1.0.8
1.1.0.8
E3.0.0.0
E3.1.0.0
1.1.0.9
1.1.0.5
Page: 3 of 34
HARDWARE / BOOT FIRMWARE COMPATIBILITY
Part
SSR-2-SX
SSR-2-SX-AA
SSR-2-TX
SSR-2-TX-AA
SSR-8
SSR-ARE
SSR-ATM29-02
SSR-CM2-128
SSR-CM2-64
SSR-CM3-128
SSR-CM4-256
SSR-FAN-16
SSR-FAN-8
SSR-FDDI-02
SSR-GLH39-02
SSR-GLX19-02
SSR-GLX29-02
SSR-GLX29-02-AA
SSR-GLX39-02
SSR-GLX70-01
SSR-GLX70-01-AA
SSR-GSX11-02
SSR-GSX21-02
SSR-GSX21-02-AA
SSR-GSX31-02
SSR-GTX32-02
SSR-HFX11-08
SSR-HFX21-08
SSR-HFX21-08-AA
SSR-HFX29-08
SSR-HFX29-08-AA
SSR-HSSI-02
SSR-HSSI-02-AA
SSR-HTX12-08
SSR-HTX12-08-AA
SSR-HTX22-08
SSR-HTX22-08-AA
SSR-HTX32-16
SSR-MEM-128
SSR- PCMCIA
35-028-01
35-053-01
35-053-02
35-053-03
37-002-01
SSR- PCMCIA
35-028-02
35-053-04
37-010-01
SSR- POS21-04
SSR- POS29-04
SSR- POS31-02
SSR- POS39-02
Description
Minimum
System
Firmware
Version
2-port 1000Base-SX module for X-Pedition 2000
2-port 1000Base-SX module for X-Pedition 2000
8-port 10/100 TX module for X-Pedition 2000
8-port 10/100 TX module for X-Pedition 2000
X-Pedition 8000 Chassis with 8 slots. Comes with SSR-FAN-8.
Advanced Routing Engine (currently supports AppleTalk) for X-Pedition 8000/8600
2-port ATM OC-3c base module [T-Series] for X-Pedition 8000/8600
Control Module 2 (198 MHz CPU) with 128 MB memory for X-Pedition 8000/8600
Control Module 2 (198 MHz CPU) with 64 MB memory for X-Pedition 8000/8600
Control Module 3 (291 MHz CPU) with 128MB memory for X-Pedition 8000/8600
Control Module 4 (375/380 Mhz) with 256MB memory for X-Pedition 8000/8600
Fan Tray module for X-Pedition 8600
Fan Tray module for X-Pedition 8000
2-port FDDI base module [T-Series] for X-Pedition 8000/8600
2-port 1000 LLX / LH module (SCLX for MMF / SMF) [T-Series] for X-Pedition
8000/8600
2-port 1000 LX module (SCLX for MMF or SMF) with 4 MB for X-Pedition 8000/8600
2-port 1000 LX module (SCLX for MMF or SMF) with 16 MB for X-Pedition 8000/8600
2-port 1000 LX module (SCLX for MMF or SMF) with 16 MB for X-Pedition 8000/8600
2-port 1000 LX module (SCLX for MMF or SMF) [T-Series] for X-Pedition 8000/8600
1-port 70 Km 1000 Base-LX module with 16 MB for X-Pedition 8000/8600
1-port 70 Km 1000 Base-LX module with 16 MB for X-Pedition 8000/8600
2-port 1000 SX module (SCSX for MMF Only) with 4 MB for X-Pedition 8000/8600
2-port 1000 SX module (SCSX for MMF Only) with 16 MB for X-Pedition 8000/8600
2-port 1000 SX module (SCSX for MMF Only) with 16 MB for X-Pedition 8000/8600
2-port 1000 SX module (SCSX for MMF Only) [T-Series] for X-Pedition 8000/8600
2-port 1000 TX module (Cat 5 RJ-45) [T-Series] for X-Pedition 8000/8600
8-port 100 FX module (MMF SC) with 4 MB for X-Pedition 8000/8600
8-port 100 Base-FX module (MMF SC) with 16 MB for X-Pedition 8000/8600
8-port 100 Base-FX module (MMF SC) with 16 MB for X-Pedition 8000/8600
8-port 100 Base-FX SMF module with 16 MB for X-Pedition 8000/8600
8-port 100 Base-FX SMF module with 16 MB for X-Pedition 8000/8600
2-port HSSI module for X-Pedition 8000/8600
2-port HSSI module for X-Pedition 8000/8600
8-port 10/100 TX module (Cat 5 RJ-45) with 4 MB for X-Pedition 8000/8600
8-port 10/100 TX module (Cat 5 RJ-45) with 4 MB for X-Pedition 8000/8600
8-port 10/100 TX module (Cat 5 RJ-45) with 16 MB for X-Pedition 8000/8600
8-port 10/100 TX module (Cat 5 RJ-45) with 16 MB for X-Pedition 8000/8600
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
8MB PCMCIA card for SSR-CM2-64, SSR-CM2-128, SSR-CM3-128, SSR- CM4-256,
ER16-CM3-128, and ER16-CM4-256
1.2.0.0
3.0.0.0
1.2.0.0
3.0.0.0
1.0.0.0
E8.1.0.0
3.1.0.0
1.1.0.0
1.1.0.0
E8.0.0.0
E8.2.0.0
1.0.0.0
1.0.0.0
3.2.0.0
3.1.0.0
8MB PCMCIA card for SSR-CM2-64, SSR-CM2-128, SSR-CM3-128, SSR- CM4-256,
ER16-CM3-128, and ER16-CM4-256
4-port OC-3c/STM-1 Packet over SONET/SDH MMF module [T-Series] for X-Pedition
8000/8600
4-port OC-3c/STM-1 Packet over SONET/SDH SMF module [T-Series] for X-Pedition
8000/8600
2-port OC-12c/STM-4 Packet over SONET/SDH MMF module [T-Series] for XPedition 8000/8600
2-port OC-12c/STM-4 Packet over SONET/SDH SMF module [T-Series] for XPedition 8000/8600
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Minimum
Boot
Firmware
Version
1.1.0.2
1.1.0.2
E3.0.0.0
E3.1.0.0
1.0.0.0
1.0.0.0
3.0.0.0
3.1.0.0
2.0.0.0
3.0.0.0
1.0.0.0
1.0.0.0
3.0.0.0
3.1.0.0
3.1.0.0
1.0.0.0
1.0.0.0
3.0.0.0
2.0.0.0
2.0.0.0
2.1.0.0
3.0.0.0
1.0.0.0
3.0.0.0
1.0.1.0
3.0.0.0
3.1.0.0
1.1.0.0
1.1.0.2
1.0.0.0
1.0.0.0
3.0.1.6,
3.0.1.7,
3.1.0.8
and up
excluding
3.2.0.0
3.1.0.0
E3.0.0.0
3.1.0.0
3.1.0.0
3.1.0.0
Page: 4 of 34
HARDWARE / BOOT FIRMWARE COMPATIBILITY
Part
Description
SSR- PS-16
SSR- PS-16-DC
SSR- PS-8
SSR- PS-8-DC
SSR-SERC-04
SSR-SERC-04-AA
SSR-SERCE-04
SSR-SERCE-04-AA
SSR-SF-16
XP- PCMCIA -16AT
XP- PCMCIA -32AT
XP- PCMCIA -16LN
AC Power Supply module for X-Pedition 8600
DC Power Supply module for X-Pedition 8600
AC Power Supply module for X-Pedition 8000
DC Power Supply module for X-Pedition 8000
4-port Serial module with compression for X-Pedition 8000/8600
4-port Serial module with compression for X-Pedition 8000/8600
4-port Serial module with compression and encryption for X-Pedition 8000/8600
4-port Serial module with compression and encryption for X-Pedition 8000/8600
Switching Fabric module for X-Pedition 8600
16MB ATA PCMCIA card for SSR-CM2-64, SSR-CM2-128, SSR-CM3-128, SSRCM4-256, ER16-CM3-128, and ER16- CM4-256
32MB ATA PCMCIA card for SSR-CM2-64, SSR-CM2-128, SSR-CM3-128, SSRCM4-256, ER16-CM3-128, and ER16- CM4-256
16MB PCMCIA card for SSR-CM2-64, SSR-CM2-128, SSR-CM3-128, SSR- CM4256, ER16-CM3-128, and ER16- CM4-256
Minimum
System
Firmware
Version
Minimum
Boot
Firmware
Version
1.0.0.0
1.0.0.0
1.0.0.0
1.0.0.0
2.1.0.0
3.0.0.0
2.1.0.0
3.0.0.0
1.2.0.0
E8.2.0.0
E3.1.0.0
E8.2.0.0
E3.1.0.0
3.0.1.6,
3.0.1.7,
3.1.0.8
and up
excluding
3.2.0.0
E3.0.0.0
The following table lists hardware not supported by this Firmware Release. The last Firmware Release to support
this hardware was 3.0.X.X.
Part
Description
SSR-2-B
SSR-2-B-AA
SSR-CM-128
SSR-CM-64
SSR2000 with 32 MB
SSR2000 with 32 MB
Control Module 1 with 128 MB memory for SSR8000 and SSR8600
Control Module 1 with 64 MB memory for SSR8000 and SSR8600
The following table lists supported hardware that is System Firmware and Boot Firmware version independent.
Part
APHY -21
APHY -22
APHY -29IR
APHY -67
APHY -77
APHY -82
APHY -92
FPHY -01
FPHY -02
FPHY -09
GPIM-01
GPIM-08
GPIM-09
SSR-2-RACKMOUNT
SSR-449DTE-02
SSR-530DTE-02
SSR-8-PS- IMPCT
SSR-HSSI- CAB
SSR-V35-DTE-02
SSR-X21DTE-02
10/24/01 P/N: 9038090-17
F0615-F
Description
SSR-ATM29-02 1 port OC-3 MMF Physical Interface Module
SSR-ATM29-02 1 port OC-3 UTP Physical Interface Module
SSR-ATM29-02 1 port OC-3 SMF-IR Physical Interface Module
SSR-ATM29-02 1 port DS-3/T3 Physical Interface Module (Coax)
SSR-ATM29-02 1 port E-3 Physical Interface Module (Coax)
SSR-ATM29-02 1 port T-1 Physical Interface Module (UTP)
SSR-ATM29-02 1 port E-1 Physical Interface Module (UTP)
SSR-FDDI-02 MMF DAS/SAS with SC connectors
SSR-FDDI-02 UTP SAS with RJ45 connector
SSR-FDDI-02 SMF DAS/SAS with SC connectors
ER-16 Gigabit Ethernet Physical Interface Module, 1000BaseSX
ER-16 Gigabit Ethernet Physical Interface Module, Long Haul (70Km)
ER-16 Gigabit Ethernet Physical Interface Module, 1000BaseLX
Rack Mount Kit for X-Pedition 2000 and X-Pedition 2100
4 meter 2 lead cable with 2 male RS449 DTE (male) connectors
4 meter 2 lead cable with 2 male RS530 (male) connectors
SSR 8000 Impact Kit
3 meter HSSI cable, male to male connector
4 meter 2 lead cable with 2 male V35 DTE (male) connectors
4 meter 2 lead cable and 2 make X21 DTE (male) connectors
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 5 of 34
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.
The following table shows the hardware supporting specific features in this release:
X
X
X
X
X
X
XP 6SSRM -02
6SSRM-02
Router Module for the Matrix E6 & E7
X
X
X X
X
X
X
X
X
X
XP 5SSRM -02&
XP 6SSRM -02
6SSRLC-FX-AA
6SSRLC-LX-AA
6SSRLC-LX70-AA
6SSRLC-SER-AA
6SSRLC-SERC-AA
6SSRLC-SERCE-AA
6SSRLC-SX-AA
6SSRLC-TX-AA
8-port 100Base-FX (MTRJ)
2-port 1000Base-LX
1-port 1000Base-LX 70 KM
2-port Serial
4-port Serial, compression
4-port Serial, compression & encryption
2-port 1000Base-SX
8-port 10/100Base-TX
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
XP 2000 / 2100
SSR-2-B128
SSR-2-FX
SSR-2-FX-AA
SSR-2-GSX (AA)
SSR-2-HSSI-AA
SSR-2-LX
SSR-2-LX-AA
SSR-2-LX70
SSR-2-LX70-AA
SSR-2-SER
SSR-2-SER-AA
SSR-2-SERC
SSR-2-SERC-AA
SSR-2-SERCE
SSR-2-SERCE-AA
SSR-2-SX
SSR-2-SX-AA
SSR-2-TX
SSR-2-TX-AA
X-Pedition 2000
8-port 100BaseFX
8-port 100BaseFX
X-Pedition 2100
2-port HSSI
2-port 1000Base-LX
2-port 1000Base-LX
1-port 70 km 1000Base-LX
1-port 70 km 1000Base-LX
2-port Serial
2-port Serial
4-port Serial, compression
4-port Serial, compression
4-port Serial, compression & encryption
4-port Serial, compression & encryption
2-port 1000Base-SX
2-port 1000Base-SX
8-port 10/100 TX
8-port 10/100 TX
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X X
X X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
XP 8000 / 8600
SSR-ARE
SSR-ATM29-02
SSR-FDDI-02
SSR-GLH39-02
SSR-GLX19-02
Advanced Routing Engine
2-port ATM OC-3
2-port FDDI
2-port 1000 LLX/LH
2-port 1000 LX – 4 MB
10/24/01 P/N: 9038090-17
F0615-F
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Weighted Random Early
Detection
X X
Weighted Fair Queuing
Multiple IPX
Encapsulation
X
Jumbo Frame Support
Layer 4 Bridging
X
Aggregate Rate Limiting
TOS Rewrite
Router Module for the Matrix E5
Description
Per Port Rate Limiting
Established Bit ACL
XP 5SSRM -02
5SSRM-02
X-Pedition
Feature Set /
Part Number
Network Address
Translation
Per Protocol VLAN
T – Series
Flow Aggregate Rate
Limiting
Per Flow Rate Limiting
AA – Series
Server Load Balancing
Weighted Fair Queuing
Pre
AA
X
X
X
X
X
X
X
1
X
X
X
X
X
X
X
Page: 6 of 34
HARDWARE REQUIREMENTS
1
Per Port Rate Limiting
Aggregate Rate Limiting
Jumbo Frame Support
Weighted Fair Queuing
Weighted Random Early
Detection
Flow Aggregate Rate
Limiting
Per Flow Rate Limiting
Multiple IPX
Encapsulation
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Layer 4 Bridging
4-port 1000Base GBIC
8-port 1000Base GBIC
8-port 1000Base-SX
24-port 10/100 Base-TX
32-port 10/100 Base-TX
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
TOS Rewrite
ER16
ER16-04
ER16-08
ER16-SX-08
ER16-TX-24
ER16-TX-32
X
Established Bit ACL
2-port 1000 LX – 16 MB
2-port 1000 LX – 16 MB
2-port 1000 LX
1-port 70 km 1000Base-LX
1-port 70 km 1000Base-LX
2-port 1000 SX – 4 MB
2-port 1000 SX – 16 MB
2-port 1000 SX – 16 MB
2-port 1000 SX
2-port 1000 TX
8-port 100 Base-FX – 4 MB
8-port 100 Base-FX – 16 MB
8-port 100 Base-FX – 16 MB
8-port 100 Base-FX SMF
8-port 100 Base-FX SMF
2-port HSSI
2-port HSSI
8-port 10/100 TX – 4 MB
8-port 10/100 TX – 4 MB
8-port 10/100 TX – 16 MB
8-port 10/100 TX – 16 MB
16-port 10/100 TX – 16 MB
4-port OC-3/STM-1 POS MMF
4-port OC-3/STM-1 POS SMF
2-port OC-12/STM-4 POS MMF
2-port OC-12/STM-4 POS SMF
4-port Serial, compression
4-port Serial, compression
4-port Serial, compression & encryption
4-port Serial, compression & encryption
T – Series
Per Protocol VLAN
SSR-GLX29-02
SSR-GLX29-02-AA
SSR-GLX39-02
SSR-GLX70-01
SSR-GLX70-01-AA
SSR-GSX11-02
SSR-GSX21-02
SSR-GSX21-02-AA
SSR-GSX31-02
SSR-GTX32-02
SSR-HFX11-08
SSR-HFX21-08
SSR-HFX21-08-AA
SSR-HFX29-08
SSR-HFX29-08-AA
SSR-HSSI-02
SSR-HSSI-02-AA
SSR-HTX12-08
SSR-HTX12-08-AA
SSR-HTX22-08
SSR-HTX22-08-AA
SSR-HTX32-16
SSR- POS21-04
SSR- POS29-04
SSR- POS31-02
SSR- POS39-02
SSR-SERC-04
SSR-SERC-04-AA
SSR-SERCE-04
SSR-SERCE-04-AA
Server Load Balancing
Description
AA – Series
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Network Address
Translation
X-Pedition
Feature Set /
Part Number
Weighted Fair Queuing
Pre
AA
X
X
X X
X X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
SSR-FDDI-02 jumbo frame support is limited to 4500 bytes.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 7 of 34
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-EM (NetSight Element Manager)
NetSight Switch and Topology Manager
SPECTRUM Enterprise Manager
Version
3.0
1.2
6.0.2
Part Number
NS-EM-LIC-1
NS-EM-WEB
NS-EM-CD
NS-EM-LIC-5
NS-EM-LIC-10
NS-EM-LIC-20
NETSIGHT-SM-TM
SM-CSI1091
SM-ENT1001
NOTE: Network Management Software may not utilize the latest features in the E8.2.0.0 System Firmware.
Enterasys Networks recommends reviewing the release notes included with the user’s specific Network
Management Platform for more information.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 8 of 34
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, the procedure outlined in
http://www.enterasys.com/support/techtips/tk0306-9.html can provides access to the system.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 9 of 34
ISSUES RESOLVED IN E8.2.1.1
ISSUES RESOLVED IN E8.2.1.1
•
•
Because all of the issues in the following tables have been resolved, a statement with each issue
declaring its resolution has not been included.
Resolved Issues are sorted alphabetically by topic heading.
Access Control List (ACL)
I.D.
Commented-out ACL commands will be negated after an “acl-edit” mode command is performed
and the change is saved. This issue occurs only if no other commented out lines exist in the
configuration.
F1649
Attempting to delete a line using acl-edit will lock ACL commands into the configuration database.
F1675
In order to delete all ACLs, a reboot must be performed after a hot-swap.
F1692
Address Resolution Protocol (ARP)
I.D.
If the link to an end-station from an STP-enabled port is disconnected, the ARP table will clear. If the
X-Pedition has attained a considerable amount of ARP entries, disconnecting this link could,
therefore, introduce an ARP broadcast storm to the network.
F1451
This issue originally appeared in E8.1.0.3, and was resolved in E8.1.0.7.
The arp add command now includes an additional vlan parameter. This parameter enables the
specification of a VLAN for the static ARP entry, allowing packets destined for a specified IP
address to be forwarded through all ports in the VLAN associated with that IP interface.
F1474
NOTE: The vlan and exit-port parameters cannot be used simultaneously.
This issue was added in E8.1.0.9.
When the CLI is used to add an ARP entry, the system incorrectly allows the inclusion of both the
exit-port and vlan parameters in a single command. This issue was resolved in E8.2.0.2.
F1559
Static ARP entries configured on a VLAN rather than an exit port will be modified when new ARP
traffic is seen. This issue originally appeared in E8.1.0.9, and was resolved in E8.1.0.12.
F1747
AppleTalk / Advanced Routing Engine (ARE)
I.D.
AppleTalk nodes (iMacs, for example) are able to communicate only in the default zone. When an
AppleTalk node's zone membership is changed via the chooser, those nodes are unable to browse
or communicate with any other nodes in the new zone. If the AppleTalk node's membership is
changed back to the default zone, communication between nodes will resume. This issue was
resolved in E8.1.0.9.
F1514
If a partial command for either save active (i.e. “save ac”) or save startup (i.e. “save star”) is
entered while in ‘are-config’ mode, the command line will not complete itself, and will not be
recognized. Hitting the space-bar will cause the commands to complete as they should.
F1521
NOTE: This issue occurs ONLY when the user Telnets into the router over the network.
This issue was resolved in E8.1.0.9.
AppleTalk ping results will not display during a Telnet management session. A serial console
management session works correctly.
Asynchronous Transfer Mode (ATM)
F1583
I.D.
The second port of an ATM card will not pass multicast/broadcast traffic when the interface type is
set to "point-to-point".
F1456
NOTE: The default ATM interface type is "broadcast"; when in this mode, the ATM card passes
multicast/broadcast traffic on both ports.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 10 of 34
ISSUES RESOLVED IN E8.2.1.1
Asynchronous Transfer Mode (ATM)
I.D.
The X-Pedition does not correctly bridge packets between Virtual Circuits configured on the same
physical ATM port. This issue was resolved in E8.2.0.1.
Auto-Negotiation
F1538
I.D.
When re-auto-negotiation between X-Pedition and Vertical Horizon product lines becomes
necessary (example: the X-Pedition is rebooted), the re-auto-negotiate will work incorrectly. This
causes affected ports to stop passing traffic. This issue was resolved in E8.1.0.9.
Cabletron Discovery Protocol (CDP)
F1532
I.D.
The container MAC address transmitted with CDP packets is 00 00 00 00 00 00. This is incorrect.
This issue was resolved in E8.1.0.7.
F1321
F1322
The function level transmitted with CDP packets is 00 00 00 02. It should be 00 00 00 00. This issue
was resolved in E8.1.0.7.
F1323
The "Local Port" column in output for the cdp show neighbors command displays incorrect
information for the X-Pedition ER16. This issue was resolved in E8.1.0.7.
F1349
CDP does not free memory correctly when deleting neighbors from its database.
F1442
Command Line Interface (Native)
I.D.
With this release, the arp add command now includes an additional vlan parameter. This parameter
enables the specification of a VLAN for the static ARP entry, allowing packets destined for a
specified IP address to be forwarded through all ports in the VLAN associated with that IP interface.
F1474
NOTE: The vlan and exit-port parameters cannot be used simultaneously.
This issue was resolved in E8.1.0.9.
When the CLI is used to add an ARP entry, the system incorrectly allows the inclusion of both the
exit-port and vlan parameters in a single command. This issue was resolved in E8.1.0.10.
F1559
The console session will freeze after negating the following configuration lines:
F1633
port set <wan-port> wan-encapsulation ppp speed <speed003E
interface create <ifname> WAN address-netmask <address> port <wan-port>
Console Task
I.D.
When the system show cpu-utilization command is entered repeatedly, followed by the ip show
routes command, the console task may print the following error message:
F1635
%CONS-E-CONTROL_TIMER, NU_Control_Timer failed with status -26.
This issue was resolved in E8.1.0.12.
Copy
I.D.
When using the copy tftp-server to active command to copy over an active configuration, the
system will not replace the original active configuration with the new configuration. This issue was
resolved in E8.1.0.9.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
F0812
Page: 11 of 34
ISSUES RESOLVED IN E8.2.1.1
Distance Vector Multicast Routing Protocol (DVMRP)
If DVMRP is stopped then restarted while using DVMRP scoping on an interface, an address list
may be corrupted, producing a core dump.
I.D.
F1558
The address list may be corrupted through the dvmrp show interfaces command, used from
Enable mode, however it may also occur when the X-Pedition accepts an IGMP Membership
Response packet. This issue was resolved in E8.2.0.1.
When running DVMRP and Smart TRUNK(s) on the same interface, forwarding traffic will cause the
X-Pedition to become a leaf router. It will subsequently prune the interface back to its source.
Dynamic Host Configuration Protocol (DHCP)
The X-Pedition may core dump if the en0 Management Port is not configured while multiple DHCP
clients are releasing and renewing DHCP leases.
ER16
F1908
I.D.
F1805
I.D.
If an interface is pinged while the port enable-forced-return-flows port all-ports command exists
in a configuration, the ER16 will core dump.
F1594
Attempting to remove power supplies may cause the ER16 to core dump.
F1660
Frame-Relay
I.D.
Frame-relay Data Link Connection Identifiers (DLCIs) between 992 and 1007 are not allowed as per
standard ITU-T Q.922/ANSI T1.618.
GateD
F1814
I.D.
Entering a static route with a 32-bit netmask and the same destination and preference as an existing
host route (and vice-versa) will cause GateD to stop functioning. This issue was resolved in
E8.1.0.7.
Gigabit Module
F1399
I.D.
On T-Series Gigabit ports, the LEDs may flash intermittently while auto-negotiation is disabled.
F1296
When a port on a non-T-series gigabit line card is configured as a mirror destination, connecting the
port will not turn the LEDs on.
F1525
Internet Group Management Protocol (IGMP)
I.D.
When snooping is enabled, certain channels on the ER16 will not forward IGMP membership
updates. This issue was resolved in E8.2.0.1.
F1572
Multicast group joins seen on the same port that the multicast traffic is coming from may prevent
subsequent joins on the same line card from receiving traffic. This issue was resolved in E8.1.0.12.
01576
Internet Protocol (IP)
I.D.
If the ip disable proxy-arp interface <interface name> command is applied to an interface, and
then that interface is removed, proxy-ARP will be disabled for the entire system. Subsequently, unrouted packets will not be able to resolve across interfaces. This issue was resolved in E8.1.0.7.
F1374
After the negation and restoration of the ip-helper address command, the helper addresses
(displayed through the ip show helper-address interface command) will disappear until the XPedition is rebooted. This issue was resolved in E8.1.0.9.
F1528
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 12 of 34
ISSUES RESOLVED IN E8.2.1.1
Internet Packet Exchange (IPX)
I.D.
When using a non-Ethernet II encapsulation type for IPX traffic, a novel client may not be able to
communicate with its server for several minutes after a reboot; the X-Pedition may be using the
wrong frame type for some SAP packets. This issue was resolved in E8.2.0.1.
F1375
With this release, IPX task priorities have been changed, and the following situations will no longer
cause a core dump:
F1498
• Actions on ports with IPX configured (example: losing a link)
• Hot-swapping a module with configured IPX interfaces
This issue was resolved in E8.1.0.10.
Layer-3
I.D.
When an exit port is disconnected, flows will not be removed if traffic directed toward the
disconnected port does not decrease. This results in improper failover to other/backup routes. This
issue originally appeared in E8.0.1.2, and was resolved in E8.1.0.11.
F1582
F1588
Layer-3 traffic may encounter difficulties with efficient flow setup. This issue originally appeared in
E8.1.0.4, and was resolved in E8.1.0.12.
F1827
Layer-4 Bridging
I.D.
When enabling Layer-4 bridging (vlan enable l4-bridging on xxx) on a VLAN containing
SmartTRUNKs, duplicate packet issues may occur.
F1234
Example: A packet going into st.1 will emerge from st.2 twice.
When Layer-4 bridging is enabled on both IP and IPX VLANs located on same port(s), the XPedition may core dump while trying to delete a Layer-3 IPX flow entry during aging. This issue was
resolved in E8.1.0.9
F1287
When using Layer-4 bridging, a 'tcp-established' ACL will not function properly. This issue was
resolved in E8.1.0.7.
F1455
Layer-4 bridging hardware flows will be deleted (age-out) every 5 minutes when using the GMAC or
OCMAC chipsets. This issue was resolved in E8.2.0.3.
F1636
Link-Aggregation Control Protocol (LACP)
I.D.
LACP advertisement packets will not transmit correctly if an LACP SmartTRUNK contains ports in
the lower channels only.
F1510
With this release, LACP has progressed from a static implementation to a dynamic implementation
more closely reflecting the 802.3ad standard; this is due to the dynamic configuration of LAGs and
link allocation.
F1536
Multicast
I.D.
Adding a SmartTRUNK to a VLAN containing a multicast source will stop multicast traffic from
routing. This issue was resolved in E8.1.0.10.
F0942
Multicast traffic does not pass correctly across Q-trunks on 1000Base-SX and 1000Base-LX (fiber
gigabit) ports, or 10/100Base-TX (copper gigabit) ports. This issue was resolved in E8.1.0.10.
F1571
Multicast group joins that appear on the same port as multicast traffic will prevent any subsequent
client attempting to join (on the same line card) from receiving traffic.
F1576
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 13 of 34
ISSUES RESOLVED IN E8.2.1.1
Multicast
I.D.
The workaround for multicast across Q-trunks in pre-“T-series” hardware has been restored. See
tech bulletin TK609-1 for more information. This issue originally appeared in E8.1.0.1, and was
resolved in E8.1.0.12.
F1685
Multicast streams on line cards using OCMAC and GMAC chips incorrectly age out every Layer-2
aging period.
F1818
When running IGMP and/or DVMRP on a SmartTRUNKed interface, multicast traffic will stop after
260 seconds.
F1871
Network Address Translation (NAT)
I.D.
The X-Pedition may core dump when NAT is dynamic and/or overloaded. This issue was resolved in
E8.2.0.4.
Open Shortest Path First (OSPF)
01534
01652
I.D.
The configuration of Point-t o-Multipoint interfaces will cause OSPF to remain in the “2-way” state.
This issue occurs with many Frame Relay OSPF configurations. This issue was resolved in
E8.1.0.7.
Port
F1449
I.D.
If the ifg sub-option is included in the port set <port#> |<all-ports> command, or entered after
previous port set <port#>|<all-ports> commands have been included in the X-Pedition’s
configuration, this sub-option will error the command line and disallow the line from being negated
from the configuration. This issue was resolved in E8.1.0.9.
Port-Mirroring
00617
01087
01345
I.D.
When port-mirroring is configured, the monitor port will receive multiple copies of the same multicast
packets. This issue was resolved in E8.1.0.7.
F1017
When mirroring under Layer-4 bridging mode, traffic matching an ACL may not be copied out of the
destination ports if the ACL is applied to the inbound ports. Negating a mirroring command will also
disable other configured mirrors. In rare cases, X-Pedition will core dump when a mirroring
command is saved. This issue was resolved in E8.2.0.1.
F1527
When mirroring traffic from a port with Layer-4 bridging enabled, the X-Pedition may core dump.
F1591
When an X-Pedition is routing, and port-mirroring is included in the startup configuration, packets
received by the source ports fail to be mirrored after reboot. This issue originally appeared in
E8.2.0.1, and was resolved in E8.2.0.2.
F1625
Huntgroup SmartTRUNKs may temporarily lose connectivity when port-mirroring is configured on
multiple source ports. Enterasys Networks recommends that no more than 8 source ports are
mirrored to the same destination port(s).
F1725
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 14 of 34
ISSUES RESOLVED IN E8.2.1.1
Q-Mac
I.D.
It has been determined that the QMAC may occasionally enter into a state of continual reset. With
this release, the slot containing a port affected by this state will now be hot-swapped out and then
back in again. This should recover the failing port.
01499
In addition, the following messages will display on the console:
Maximum in-a-row QMAC recoveries exceeded on port <port name>
Overflow counters - Ctl: <num>, Hi: <num>, Med: <num>, Low: <num>
Collision counters - Late: <num>, Excessive: <num>
Port %s QMAC recoveries: <num>
Total SSR QMAC recoveries: <num>
Hotswap OUT then IN slot <slot num>
The information provided by these messages should be forwarded to Enterasys Networks for
analysis. This issue was resolved in E8.1.0.11.
Quality of Service (QoS)
I.D.
Although entered as decimal numbers, the command qos show ip will display the ToS and ToS
mask as decimal values preceded with the characters ‘0x’, giving the impression that the value is in
hexadecimal.
F1425
NOTE: With this release, the display will print the decimal value, followed by the hex equivalent:
TOS: 202 (0xca)
TOSMask: 175 (0xaf)
This issue was resolved in E8.1.0.7.
Rate-Limiting
I.D.
When using the SSR-HTX32-16, attempts to apply port-based rate-limiting to the input and output
ports of the same flow will result in inaccurate rate-limiting. This issue was resolved in E8.1.0.7.
F1094
If a packet is broadcast for learning a Layer-2 flow, the VLAN rate-limiting policy for this flow may
not be set. This issue was resolved in E8.2.0.2.
F1542
If a VLAN rate-limit command does not specify a destport parameter, the rate limit will not get set.
This issue was resolved in E8.2.0.2.
F1581
When configuring a VLAN rate-limiting policy and specifying a destination port, the policy may be
applied to other destination ports upon the learning of a Layer-2 flow.
F1733
The input, flow-aggregate, vlan and aggregate rate-limit commands have been modified with the
addition of a burst compensating option. This option invokes an algorithm which will calculate ratelimit values to better handle traffic tending to come in bursts, such as FTP. The option is called
"burst -compensating" and will aut omatically be invoked when specified.
F1849
Remote Network Monitor Device (RMON)
I.D.
While running RMON configured with rmon set professional default-tables yes, the X-Pedition
may experience a core dump.
F0871
F0973
F1023
F1042
F1500
When configuring the X-Pedition to monitor a SmartTRUNK port in an RMON table, RMON will
return the following inaccurate warning message:
F1512
%CLI-W-INTRUNK, port 'xx' is part of a SmartTRUNK st.x".
This issue was resolved in E8.2.0.2.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 15 of 34
ISSUES RESOLVED IN E8.2.1.1
Remote Network Monitor Device (RMON)
When monitoring traffic on the RMON “al-host” table, high protocol ports will report incorrect
protocols. “Quake”, for example, will display as “LDAP”.
Routing
I.D.
F1604
I.D.
Prior to this release, the number of multipath (equal cost) route entries in each route table was 16.
This resulted in the allocation of excessive memory, which was subsequently never used. The
number of multipath (equal cost) route entries has been altered to the more reasonable value of 4,
resulting in the consumption of 30% less memory per route table entry. Because of this, the XPedition can now hold more route table entries and/or avoid low- or out-of-memory conditions.
F1506
When a link goes down within an OSPF or BGP domain, Layer-3 flows may not be properly
removed. This may result in a misdirected flow that will not be removed unless traffic ceases on the
flow for more than 30 seconds.
01770
01763
01757
01358
01801
Serial WAN Module
I.D.
Serial WAN modules (i.e. 2-port HSSI, 2-port Serial (SERC), 4-port Serial (SERC), and 4-port Serial
Encrypted (SERCE)) cannot be hot-swapped out of slot 15 in the X-Pedition 8600. Upon attempting
such a hot-swap, the system will fail to perform any other hot -swap request until the X-Pedition is
rebooted.
Simple Network Management Protocol (SNMP)
F1555
I.D.
When querying the 'sysHwModuleTable' MIB on an X-Pedition 8000, slot “0” will not register if a
Control Module exists in that slot. This issue was resolved in E8.1.0.7.
F0945
F1083
An SNMP Get or GetNext request for objects in the vrrpMIB may return invalid or incomplete results.
In addition, SNMP Set requests for objects in the vrrpMIB will fail.
F1344
BGP management traps are not currently supported.
F1376
If a topology change occurs, and an X-Pedition is the root bridge both before and after the change,
the X-Pedition will send out a new root bridge trap regardless of its previous function as the root.
This issue was resolved in E8.1.0.7.
F1437
When Querying the ‘dot1dTpFdbTable’, addresses belonging to SmartTRUNKs will incorrectly
display port “0”. Subsequently, the user cannot back trace the origin of a specific address. This
issue was resolved in E8.1.0.7.
F1457
Entering the command snmp set mib name <MIB> status disable will cause the X-Pedition to lose
pagination. This issue was resolved in E8.1.0.7.
F1471
The X-Pedition does not send the SNMP trap “envHotSwapOut” when the backup Control Module is
hot-swapped out. This issue was resolved in E8.1.0.10.
F1549
Entering a snmp set command with a duplicate community name will produce an error. When the
erroneous command is negated and the active configuration is saved, the error will still occur when
the command is reentered using the same community name.
F1659
If using SNMP to query the ifTable at the exact time a link goes up or down, the X-Pedition will coredump.
F1802
With SNMP turned on, removing the fan tray from an X-Pedition may cause a core dump or print out
an error message. This issue originally appeared in E8.1.0.7, and was resolved in E8.1.0.12.
01809
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 16 of 34
ISSUES RESOLVED IN E8.2.1.1
SmartTRUNK
I.D.
In E8.1.0.0 and later releases, secondary SmartTRUNK ports are incorrectly forced into the blocking
state when their links come up. It takes up to 30 seconds before these ports can settle to the correct
STP state, resulting in lost traffic during that time frame. This issue was resolved in E8.1.0.7.
F1162
F1163
When a physical port in a SmartTRUNK is disconnected, the learned Layer-2 table entries are
removed from the disabled port. As a result, Layer-2 activities will increase. This issue was resolved
in E8.1.0.7.
F1261
F1297
BPDUs may incorrectly display the same cost for SmartTRUNK ports with different link speeds.
F1423
SmartTRUNK links may be affected when the Huntgroup protocol is enabled on SmartTRUNKs
while the Control Module is too busy to send or receive Huntgroup PDUs.
F1433
NOTE: This issue was resolved in conjunction with a timer fix used to correct a VRRP packet delay
issue. For more information, please see “VRRP” on page 19 of these Release Notes.
SmartTRUNKs may prematurely age-out Layer-2 table entries, causing those entries to be
relearned at 5 minute intervals.
F1612
Specifying an uncreated SmartTRUNK through the smarttrunk lacp aggregator command (Active
configuration) will cause the X-Pedition to crash.
F1746
Spanning Tree Protocol (STP)
I.D.
Command conflicts between BPDU filtering and enabling STP on ports are not adequately detected.
F1149
NOTE: With this release, the system will now detect these conflicts and give the user an opportunity
to correct them. This issue was resolved in E8.2.0.2.
A core dump may occur on an X-Pedition running System Firmware version E8.1.2.0 or higher when
a spanning-tree packet is received on a WAN port connected to another router using System
Firmware version E8.1.0.6 or lower.
F1428
NOTE: This issue does not occur when the routers on both ends of a WAN connection are using
System Firmware prior to versions E8.1.0.6 and E8.1.2.0. In addition, this does not occur with any
System Firmware versions E8.2.X.X. This issue was resolved in E8.1.0.7.
If a topology change occurs, and an X-Pedition is the root bridge both before and after the change,
the X-Pedition will send out a new root bridge trap regardless of its previous function as the root.
This issue was resolved in E8.1.0.7.
F1437
The stp filter-bpdu all-ports command will not apply BPDU filtering to newly hot-swapped
modules. In order to filter BPDU from new modules, the user should either comment this command
out and back in, or negate and re-enter it. This issue was resolved in E8.1.0.9.
F1468
Changes in STP root bridge variables (example: hello_time, forward_delay, max_age) will not be
detected by non-root routers. This causes the X-Pedition to continue sending a TCN BPDU to the
root bridge until the variables are returned to their original values. This issue was resolved in
E8.2.0.1.
F1490
The X-Pedition will continue to forward VLAN-tagged BPDUs on a Q-trunk when STP is disabled.
This issue was resolved in E8.2.0.3.
01630
The stp enable port command fails to initialize STP on some ports when multiple ports are
specified.
F1687
BPDU filtering fails after a port is added to a VLAN. This issue was resolved in E8.2.0.3.
01691
Statistics
I.D.
The “In-errors” field, produced through the statistics show ip-interface all command, displays
inaccurate information.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
F1751
Page: 17 of 34
ISSUES RESOLVED IN E8.2.1.1
Switch Fabric Card
I.D.
When a switch fabric card is hot-swapped into an X-Pedition 8600, it is not fully ready to take over
when the other switch fabric either fails or is hot-swapped out. This results in a fail-over time, which
is slightly longer than it should be. This issue was resolved in E8.1.0.9.
System
F1531
I.D.
With this release, the System Firmware has been enhanced to prevent the use of unsupported
hardware configurations. The following error messages will appear when an unsupported
configuration is attempted:
F0899
%SYS-E-CPU_CHASSIS_PROBLEM_1
%SYS-F-CPU_CHASSIS_PROBLEM_2
%SYS-F-CPU_CHASSIS_PROBLEM_3
%SYS-E-CM_TYPE_MISMATCH
With this release, the system names for the X-Pedition E5, E6, and E7 modules have been
changed. Previously, they were referred to as "SSR 2000/6600", regardless of the system type. The
System Firmware now detects the individual system type and alters the name accordingly. The
individual system names are as follows:
F1233
• E5 = "5SSRM/5C105"
• E6 = "6SSRM/6C105"
• E7 = "6SSRM/6C107"
This issue was resolved in E8.2.0.2.
When the system set idle-time command is configured, timeouts will not occur if the console or a
Telnet session is left paginated. This presents a security risk. This issue was resolved in E8.1.0.9.
F1507
The X-Pedition may freeze after extended periods of use. While in this condition, no console or
Telnet access is possible, and the system will not pass traffic. This issue was resolved in E8.1.0.10.
F1622
Terminal Access Controller Access Control System+ (TACACS+/RADIUS)
When responding to the tacacs-plus set source x.x.x.x command, the X-Pedition incorrectly
allows any IP address as the source. The source IP address should already be associated to an
interface on the router.
I.D.
F1197
Example: If tacacs-plus set source 2.2.2.2 is entered, the X-Pedition should first verify that an
interface exists with an IP address of “2.2.2.2”. If not, an error should display upon save active, and
the command should be errored-out in the active configuration. This issue was resolved in E8.1.0.8.
TACACS +/RADIUS accounting functions may produce memory leaks. This issue was resolved in
E8.1.0.12.
Telnet
01760
I.D.
When using Telnet to connect to an X-Pedition, utilizing certain UNIX clients as intermediate hops,
the session may not connect.
F1082
In this case, the client will display the following:
Trying 10.136.64.77...
Connected to 10.136.64.77.
Escape character is '^]'.
Connection closed by foreign host.
In addition, Telnet connection to the X-Pedition may occasionally fail when the router is busy. This
issue was resolved in E8.1.0.7.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 18 of 34
ISSUES RESOLVED IN E8.2.1.1
Telnet
I.D.
Telnet users do not see error messages generated during a Telnet session.
01501
Example (Normal Operation) :
xp(config)# vlan add ports gi.3.3 to red
%CLI-W-MODNOTFOUND, gi.3.3: module '3' does not exist - ignoring
%CLI-E-IVPORTLIST, invalid port list 'gi.3.3'
In this case, the error messages above will not be returned to the Telnet user. Serial console
sessions do not have this problem. This issue was resolved in E8.1.0.8.
With this release, "inactive" Telnet sessions (during which a connection was opened but the “Enter"
key was never pressed to activate the session) will timeout, allowing the connection of other Telnet
sessions to the X-Pedition. The timeout value may be set with the Configure-mode command
system set idle-timeout telnet x, where ‘x’ represents time in minutes. This issue was resolved in
E8.2.0.5.
Trivial File Transfer Protocol (TFTP)
01557
I.D.
When using TFTP to copy configurations from the X-Pedition to external TFTP servers, the marks
around comments in the configuration will not be transferred. Consequently, any previously
commented line in the configuration is no longer considered commented when the external TFTP
server receives the file. This issue was resolved in E8.1.0.9.
Virtual Local Area Network (VLAN)
F1367
I.D.
Applying the qos set and port flow-bridging configuration commands to a VLAN will cause traffic
to be flooded through all ports in the VLAN.
F1799
Virtual Router Redundancy Protocol (VRRP)
I.D.
Extremely high levels of CPU utilization may delay VRRP packets. This issue was resolved in
E8.1.0.8.
F1433
With this release, VRRP can no longer be configured on a loopback interface.
F1488
When an exit port is disconnected, flows will not be removed if traffic directed toward the
disconnected port does not decrease. This results in improper failover to other/backup routes. This
issue was introduced in E8.0.1.2.
F1582
F1588
Attempting to enter the ip-redundancy show vrrp interface x command, when ‘x’ is any string that
is not a VRRP interface, may cause the X-Pedition to core dump or print out an error message. This
issue was resolved in E8.2.0.12.
01686
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 19 of 34
KNOWN RESTRICTIONS AND LIMITATIONS
KNOWN RESTRICTIONS AND LIMITATIONS:
Prior to E8.2.0.0, the Known Restrictions and Limitations section contained various hardware/feature
informational statements. As of E8.2.0.0, those statements have been moved to the “Informational Notes” section
of the System Firmware release notes.
6SSRM-02
I.D.
When a 6SSRM-02 or 5SSRM -02 configuration includes the system poweron-selftest on
command in startup, and the X-Pedition is cold booted, the diagnostic programs will run; these
programs will subsequently report failures such as:
F1295
%DDT-E-GMAC_PHY_LOOPBACK, (Slot 1, Port 1) : GMAC PHY Loopback : FAILED
%DDT-E-GMAC_TEST, (Slot 1, Port 1) : GMAC Test : FAILED
%DDT-E-PORT_STATUS, (Slot 1, Port 1) : FAILED
The system will be unable to use desired ports, which will be reported to have failed self-test.
The X-Pedition functions as designed when the system poweron-selftest on command is not
included in the startup configuration.
Access Control List (ACL)
Entering save in the ACL editor when no ACLs are defined causes a core dump. This issue was
introduced in E8.2.1.1.
Address Resolution Protocol (ARP)
I.D.
F1955
I.D.
After the negation of an interface configured with an ARP command, the ARP command will
automatically be reassigned to a non-existing interface in the same configuration. Attempts to
negate the ARP command will produce the following error messages:
F0309
%CLI-E-FAILED, Execution failed for "no arp set interface int1 keep-time 10"
%INTERFACE-E-NOEXIST, Interface int1 does not exist. Please check the name and try
again.
The user must then recreate the negated interface in order to negate the ARP command.
When the X-Pedition detects a topology change, it will clear the ARP entries on a specified VLAN
(or an entire ARP table if running STP) in order to ensure that Layer-3 entries maintain their
integrity. This may potentially cause all existing IP connections to re-ARP simultaneously.
F0811
Therefore, Enterasys Networks recommends that the user does not enable STP or PVST on
connections to end-stations. If this configuration is necessary, the following commands are
recommended:
stp set port <portlist> edge-port true, or
pvst set port <portlist> edge-port true spanning-tree <vlanname>
The X-Pedition will not consider a link change to an edge-port as a topology change, thereby
reducing the number of unnecessary ARP entries cleared.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 20 of 34
KNOWN RESTRICTIONS AND LIMITATIONS
Bridging
I.D.
When using line cards introduced prior to the “AA” series, SNA/DLC/NetBIOS traffic may not be
properly bridged across the X-Pedition. The issue in bridging DLC packets occurs where the length
field within an IEEE 802.3 frame indicates less than 46 bytes of data.
Hardware
Limitation
The X-Pedition removes the length field information of incoming IEEE 802.3, 802.2, and Ethernet
SNAP packets and recalculates the field prior to retransmission. Consequently, this calculation is
based on the entire length of the data field. A packet entering the X-Pedition with a length field
indicating a data field of less than 46 bytes will exit with the length field recalculated incorrectly. This
can be a problem with LLC2 and legacy IPX applications. Typically, such packets exist only in SNA
and NetBIOS/NetBEUI environments.
Cabletron Discovery Protocol (CDP)
I.D.
Cabletron Discovery Protocol will not function on a SmartTRUNK if enabled with the following
command:
F1011
cdp set port-status enable port <port-list>
This command will be rejected.
Workaround: Enable CDP with the all ports parameter, rather than the <port-list> parameter. This
should allow CDP to function properly on a SmartTRUNK.
CDP identifies some adjacent device types (such as switches, routers, etc.) incorrectly.
F1324
CDP packets are not being checked for authentication code length. This length should be 16 (in
decimal); if the value, when checked, is not within this parameter, the packet should be dropped and
the invalid authentication code counter incremented.
F1340
CDP does not correctly identify local ports which are a part of a SmartTRUNK.
F1350
If the CDP transmit frequency is altered from its default setting the hold time will not change. Hold
time should always equal 3x the increment between transmits.
F1401
CDP hold time will function normally at the default transmit frequency setting.
Control Module (CM)
I.D.
In a dual Control Module configuration, only the Primary Control Module’s Boot Firmware can be
updated.
Dynamic Host Configuration Protocol (DHCP)
F0535
I.D.
The dhcp <scope_name> set ping-timeout <number> command is not currently supported.
F1680
The Enable mode command dhcp show displays incorrect information if the DHCP configuration is
negated before lease expiration.
F1682
Distance Vector Multicast Routing Protocol (DVMRP)
I.D.
If T-series line cards are not in use, a multicast packet can be replicated to only one IP VLAN in an
802.1Q trunk port. Additionally, access-routed interfaces should be used when routing multicast
packets between two DVMRP routers.
Hardware
Limitation
Fiber Distributed Data Interface (FDDI)
I.D.
Changing the station mode on a FDDI port will negate all previously executed FDDI commands.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
F1266
Page: 21 of 34
KNOWN RESTRICTIONS AND LIMITATIONS
Hot-Swap
I.D.
Point-to-Point Protocol (PPP) does not renegotiate when a POS card (with Automatic Protection
Switch enabled) is hot-swapped, or if either end of a connection goes down. A system reboot is
required at both ends in order for PPP to renegotiate.
Interface
08223
I.D.
If an IP and IPX interface are created for a VLAN, and the IP interface is removed, traffic may stop
on both the IP and the IPX interface.
F1421
Workaround: Comment-out the IPX interface, and then comment it back in.
Internet Control Message Protocol (ICMP)
Ping packets sent by the X-Pedition have the default Type of Service (ToS) field assigned to 0xFF,
which does not conform to current RFCs.
I.D.
F0662
Workaround: This value may be changed with the ping command parameter tos.
If the X-Pedition receives a packet larger than the receiving port's MTU size, and it cannot fragment
that packet, the packet will be dropped. If the packet was to be routed, the X-Pedition will reply with
an ICMP error message; however, if the packet was to be bridged then no message will be sent.
F1268
Workaround: Configure the X-Pedition to route only ICMP packets.
Internet Protocol (IP)
I.D.
Entering a static route with a 32-bit netmask and the same destination and preference as an existing
host route (and vice-versa) will cause GateD to stop functioning.
Layer-2
F1399
I.D.
The maximum available number of static-entry filters is 505.
Layer-3
F0731
I.D.
The X-Pedition may core dump while attempting to delete an Layer-3 flow entry; it may be unable to
find the entry, or it may find a faulting address.
F0443
If a link is disconnected and then reconnected while the X-Pedition is passing traffic, Layer-3 entries
may not be deleted correctly. If routing is configured, the X-Pedition will fail to redirect traffic to a
new route.
F1358
Layer-4 Bridging
I.D.
When operating in Layer-4 bridging mode via the vlan enable l4-bridging configuration command,
the user must only employ the default address-bridging mode for Layer-2 learning on ports in the
Layer-4 bridging VLAN. In addition, the user must not apply the port flow-bridging <port-list>
command to any ports in an Layer-4 VLAN.
F0760
NOTE: This restriction exists only for T-Series line cards. These cards are recognizable by the “T”
printed upon them.
Link-Aggregation Control Protocol (LACP)
LACP SmartTRUNK will not connect to a destination router when located on a line card in slots 9-16
of the X-Pedition ER16. Unlike Huntgroup protocol SmartTRUNKs, LACP SmartTRUNKs should
function in the upper slots.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
I.D.
F1627
Page: 22 of 34
KNOWN RESTRICTIONS AND LIMITATIONS
Link-Aggregation Control Protocol (LACP)
If a line card containing an LACP SmartTRUNK is hot-swapped out and then back in, the
SmartTRUNK will not recover.
Open Shortest Pathway First (OSPF)
I.D.
F1654
I.D.
OSPF incorrectly allows the entry of numeric interface names. Numerically defined OSPF interfaces
are interpreted as IP addresses, and are not valid.
F0879
When adding interfaces to OSPF using the ospf add interface command, no function currently
exists to determine whether the interface name is valid; therefore no warning message will appear
upon the entry of an invalid interface name.
F1461
Point to Point Protocol (PPP)
I.D.
When creating an IP interface on a VLAN with a single PPP port configured, the interface should be
set to parameter type point-to-point.
Port-Mirroring
07757
I.D.
When a T-series card is used in an X-Pedition router, the first two octets in the source MAC field of
some mirror output packets may appear to be corrupted. This is due to a known issue with T-series
cards that modifies the source MAC of any unlearned packets, and corruption will cease once the
flow has been learned.
H0007
Normal switching and routing, excluding Layer-4 bridging in flow-based mode, will not be affected by
this error.
If large numbers of flows exist on an ER16 during the addition of a port-mirroring command to the
configuration, the console may appear to freeze; it may take 5 minutes or more to modify all flows
for a single port-mirror command.
Power On Self-Test (POST)
F1043
I.D.
Entering the system set poweron-selftest quick command in the ER16’s configuration causes the
system to display the following errors during "DIAG BOOT TEST":
F0619
%DDT-E-MEMORY_ALIASING, Memory error @ 0x70000000 ; Possible aliasing with: 0x70800000
%DDT-E-MEMORY_ALIASING, Memory error @ 0x70000004 ; Possible aliasing with: 0x70800004
%DDT-E-MEMORY_ALIASING, Memory error @ 0x70000008 ; Possible aliasing with: 0x70800008
%DDT-I-MEM_MAX_ERRORS, Max Errors Reached; Suppressing further errors for this test
%DDT-I-MEM_INFO, $Memory Failure : SOPP Memory MAIN DRAM [16775168 bytes]
%DDT-E-SOPP_MEM_TEST, (Slot 5) : SOPP Memory Test : FAILED
%DDT-E-GE_MODULE, GE Module (Slot 5) : FAILED
These errors are incorrect and should be ignored.
Quality of Service (QoS)
I.D.
The interface name parameter, which is the last parameter when configuring an IPX QoS entry,
does not work. Do not enter an interface name when configuring an IPX QoS entry.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
F1673
Page: 23 of 34
KNOWN RESTRICTIONS AND LIMITATIONS
Rate-Limiting
I.D.
When Flow-Aggregate Rate-Limiting is enabled, the amount of traffic exiting a serial WAN port
running PPP may be significantly less than the specified rate-limit. This is due to a PPP priorityqueue overflow.
F1475
Workaround: Change the PPP priority queue depths on the serial port using the following
commands:
ppp define service <name> [low-priority-queue-depth|med-priority-queue-depth|highpriority-queue-depth] <number>
ppp apply service <name> ports <wan-port>
10/100, Gigabit, and FDDI cards containing SIPP ASIC versions 2.0 and 2.1 are restricted to these
rate limiting ranges:
•
1.5M – 100M for 10/100 and FDDI modules
•
6M – 1G for Gigabit modules
10226
To display the version of the SIPP ASIC on the cards in your system enter the Enable mode
command system show hardware verbose . For each slot listed locate the Service String line. The
next two lines are examples of the service strings with the SIPP version bolded and slightly
enlarged:
Service String: 4_G2.1_4_I2.0 _16_02.0_2
Service String: 90_G1.1_16_I2.1 _16_02.1_16
Remote Network Monitor Device (RMON)
I.D.
RMON must be enabled in the configuration before RMON MIBs may be accessed via SNMP.
F0832
When the user negates and re-enters the rmon enable command, RMON memory will fill and
deliver the following warning message:
F1215
%SNMP-W-RMON_MEM, RMON memory max’ed out. You may want to add more memory
to RMON
Subsequently attempting to perform a hot swap through the system hotswap out command will
cause the X-Pedition to freeze.
When passing traffic from one port to another, and using RMON to capture incoming packets on one
of these ports, the receiving port will receive twice as many packets as the number that was sent.
F1378
Attempting to set the data-mask and data-not-mask options in the rmon filter command through
the CLI will not succeed. The masks will not properly convert from a string to a mask.
F1387
X-Pedition hardware currently drops BAD CRC, Runt and Jumbo packets before RMON is able to
capture them. Because of this, the RMON parameters pkt-status, status-mask and status-notmask (designed to capture these specific packet types) do not work.
F1390
Netsight 3.0's RMON tool allows the user to create packet capture indexes. Currently, however, it
will not allow the user to modify a previously created packet capture index.
F1413
After using the rmon set protocol-directory to set all parameters to “off”, protocols will still be
logged in the RMON matrix, address-map and hosts tables.
F1416
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 24 of 34
KNOWN RESTRICTIONS AND LIMITATIONS
Routing
I.D.
Aggressive internal testing has uncovered a weakness in some configurations containing static
routes. Configurations using only dynamic routing are unaffected.
Erroneously configured static routes may produce a routing loop. As a result, excessive CPU
utilization can occur when an improperly configured upstream router sends ICMP redirect messages
to a downstream router. It appears this problem has been present in the Enterasys Networks
System Firmware since the 2.1.0.0 release.
Routing protocols (e.g. OSPF, BGP, RIP) automatically discover and correct any loops in dynamic
routing configurations. In these cases, no excessive CPU utilization will occur.
Simple Network Management Protocol (SNMP)
I.D.
Sets to dot1qPvid in the Q MIB will fail for ports on line cards that do not support Layer-4 bridging.
F1020
Querying for dot1dStpPortEntry MIBs will return incorrect values for STP-disabled ports. In addition,
querying for the constant dot1dStpHoldTime will return “0” rather than “1”.
F1093
VLANs created via the CLI with names containing spaces cannot be modified using the IETF Q MIB.
F1245
Workaround: Remove spaces from VLAN names.
The use of the snmp set target command has changed in E8.2.0.0. It is now allowed to configure
multiple targets with the same IP address and different community strings. Traps will not be sent to
a target if the community string specified on the target is not configured.
F1258
Attempting to set the dot1qPvid MIB on a PVST enabled port should produce an error. At this time it
does not.
F1260
Attempting to set the dot1qPvid MIB for a port that has been forbidden from that VLAN should
produce an error. At this time it does not.
F1446
SmartTRUNK
I.D.
Huntgroup protocol supports up to 256 ports. In the ER16, Huntgroup protocol is supported only for
modules in slots 1 through 7. SmartTRUNK without Huntgroup protocol is supported for all modules.
F0480
BPDU may incorrectly display the same cost for SmartTRUNK ports with different link speeds.
F1423
Hot-swapping a line card several times will change the default Layer-2 aging time. A port on the line
card in this condition may not be added to a SmartTRUNK port.
08724
Spanning Tree Protocol (STP)
I.D.
BPDU filtering fails on all ports after any port-mirroring command is negated.
F1722
Workaround: After negating a port-mirroring command, negate and then re-enter the stp bpdu
filtering command to turn BPDU filtering back on.
The X-Pedition does not recognize (and subsequently will not filter) VLAN-tagged BPDUs. When
such a BPDU is received, it will be learned and forwarded as a normal Layer-2 packet.
F1726
Because E8.2.0.2 and releases prior to it will VLAN-tag BPDUs when STP is disabled, System
Firmware version E8.2.0.3 and above should be used on any X-Pedition with a Q-trunk connection.
Statistics
I.D.
The statistics show port-errors command incorrectly reports greater-than-1518-byte frames as
Cyclic Redundancy Check errors.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
F1388
Page: 25 of 34
KNOWN RESTRICTIONS AND LIMITATIONS
Terminal Access Controller Access Control System + (TACACS+)/RADIUS
If the X-Pedition is configured for TACACS+ or RADIUS system event accounting, some system
events may not be logged to the Accounting, Authorization, and Authentication (AAA) server.
I.D.
F1255
Workaround: Rather than configuring TACACS+ or RADIUS for system event accounting, use the
X-Pedition’s SYSLOG facility to log all system events to a SYSLOG server.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 26 of 34
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 XPedition products.
The following tables lists the designations used to denote where information on the statement is now located. If
there is no manual designation, the information has not yet been moved to the correct reference materials. Once
moved, the manual location will be noted.
Book
Designation
Getting Started Guide (model specific)
Quick Start
GSG
QS
X-Pedition Error Reference Manual
X-Pedition Native CLI Reference Manual
X-Pedition User Reference Manual
ERM
CLI
URM
6SSRM-02
Manual
Because important changes were introduced to Spanning Tree in E8.0.1.0 to prevent loops and
backplane ports from blocking, a minimum System Firmware version of E8.0.1.0 is recommended
for the 6SSRM -02 in a Matrix E7. The new changes are incorporated in firmware version 04.06.05
for the 6E2xx-xx, 6H2xx-xx, 6E3xx-xx, 6H3xx-xx, and 6G3xx-xx, and firmware version 04.11.06 for
the 6E1xx-xx, 6H1xx-xx, and 6M1xx-xx.
Asynchronous Transfer Mode (ATM) Module
Manual
The ATM default interface type is "broadcast"; therefore a peer address is not required. If an
interface is connected to a router that is only capable of "point to point”, such as a router using a
release prior to E8.2.0.0, then the interface type must be specified as "point-to-point"; in this case, a
peer address is required.
A peer address must be specified as part of the interface create command if a virtual channel is
configured in the “VC-Muxing” mode or if the interface type is set to "point-to-point".
LSNAT is not supported on interfaces configured with PVCs.
VRRP is not supported on interfaces configured with PVCs.
Control Module (CM)
Manual
In a dual Control Module configuration, both modules must be of the same type (CM2, CM3, or
CM4), the same Boot Firmware version, and use the same amount of memory. If PCMCIA cards are
installed, they must contain the same System Firmware version.
In a dual Control Module configuration, the MAC address of the Primary Control Module in slot
“CM/0” is used for both Control Modules after the system is booted. If the Control Module in slot
“CM/0” is removed and not replaced after a fail-over, or if it is replaced with a new Control Module,
and if the system is rebooted, then the system will use the MAC address of the Control Module in
slot 1 (or the new Control Module).
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 27 of 34
INFORMATIONAL NOTES AND STATEMENTS
Fiber Distributed Data Interface (FDDI)
Manual
Because FDDI full duplex is not an industry standard, its implementation in the XP -FDDI-02 is based
on the Digital Equipment Corporation (DEC) standard and will interoperate with all DE C products
and most Enterasys Networks FDDI products.
Gigabit Module
Manual
When connecting a 1000Base-SX/LX module to a device not supporting auto negotiation, ensure
that both devices exhibit the same link negotiation mode and that the link negotiation mode is off.
Management Port (en0)
Manual
The Ethernet port labeled “10/100 Mgmt” on the Control Module (referred to as en0 in Configure
mode) is a management port only, and is not intended to perform routing.
Network Address Translation (NAT)
Manual
VRRP is not currently supported on NAT interfaces.
PCMCIA Card File System
Manual
The file system on the PCMCIA card will not be corrupted under normal circumstances. Unusual
circumstances, such as loss of power while adding a System Firmware image, may corrupt the
PCMCIA card’s file system. Re-initialization of the PCMCIA card’s file system must be done from the
Boot Firmware’s CLI. The procedure is as follows:
Note: This procedure will erase the PCMCIA card. If the user boots the System Firmware from the
PCMCIA card, a copy of the System Firmware image must be placed on a TFTP server so
that it may be temporarily booted over the network.
1.
Reboot, or power off then on, the X-Pedition to reach the Boot Firmware’s CLI. When the Boot
Firmware goes through its initialization, stop it from booting the System Firmware by pressing
the Escape key. Typically, the Boot Firmware waits two seconds for user interruption before
starting to boot the System Firmware.
2.
After pressing the Escape key, the Boot Firmware’s CLI prompt will display. Enter the following
commands to unmount, erase, and mount (with initialization) the Virtual File System.
XP-boot> pcumount
(unmounts the PCMCIA card’s Virtual File System)
XP-boot> erasepcvfs (erases the PCMCIA card’s Virtual File System)
XP-boot> pcmount -i (mounts and initializes the PCMCIA card’s Virtual File System)
If the file system on the PCMCIA flash card is not mounted, the pcumount command will fail;
this results in an error message. The user may safely ignore this error message. Note that if the
PCMCIA flash card is write-protected, the erasepcvfs command will fail. The PCMCIA card’s
file system is now initialized, however it lacks a System Firmware image.
3.
The Boot Firmware requires the netaddr, bootaddr, netmask, and/or gateway parameters be
configured in order to boot a System Firmware image from a TFTP server over the network
using the “10/100 Mgmt” port. To configure these parameters, use the set command as follows:
XP-boot> set netaddr <IPaddr-of-management-port>
XP-boot> set bootaddr <IPaddr-of-TFTP-host>
XP-boot> set gateway <IPaddr-of-default-gateway>
XP-boot> set netmask <default-netmask>
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 28 of 34
INFORMATIONAL NOTES AND STATEMENTS
PCMCIA Card File System
4.
Manual
Temporarily boot a System Firmware image over the network through the following command:
XP-boot> boot <directory> <image-file-name>
5.
After the System Firmware finishes booting, copy the System Firmware image from the TFTP
server to the PCMCIA card as follows:
xp# system image add <IPaddr-of-TFTP-host> <directory> <image-file-name>
6.
Configure the Boot Firmware to boot the System Firmware image added to the PCMCIA card by
entering the following command:
xp# system image choose <image-file-name>
7.
Optionally, the user may reboot the system to verify the above process.
SmartTRUNK
Manual
When Spanning Tree Protocol (STP) is enabled on a SmartTRUNK, one link in the SmartTRUNK
participates in STP. If you use STP with a SmartTRUNK that consists of ports of the same type,
Enterasys Networks recommends that the ports in the SmartTRUNK be neighbors (i.e., in
consecutive order) on the same line card.
When SmartTRUNKing to an Ethernet GigaSwitch product, the IFG of the X-Pedition must be set to
4 or greater to allow the GigaSwitch time to properly process incoming frames.
If a SmartTRUNK has been configured to carry traffic for an IP VLAN and you want to have it carry
traffic for the L2 default VLAN as well, you must make the SmartTRUNK into an 802.1Q trunk, then
disable and enable the SmartTRUNK.
When hot swapping is performed on any card, the link for any SmartTRUNK configured with
Huntgroup protocol goes down for a few seconds.
If you hot-swap a card that has SmartTRUNK configured along with Layer 2 filters, the
SmartTRUNK commands are marked with an “E”.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 29 of 34
INFORMATIONAL NOTES AND STATEMENTS
Terminal Access Controller Access Control System + (TACACS+) and RADIUS
Manual
During system boot-up, if the user hits the “enter” key or attempts to connect using Telnet while
TACACS+ or RADIUS Authentication is enabled, the “last-resort” option will be exercised with the
following error message:
%CONS-W-AUTH_SUCCEED, contact TACACS+ [or RADIUS] server failed: last-resort ___
This may occur fort the following reasons:
1.
The user is not giving the X-Pedition enough time to boot-up properly. Although the console
may give the “Press RETURN to activate console…” message, the X-Pedition may still be
bringing up interfaces or learning routes at this time. If the AAA server’s interface is not yet up,
or the route has not yet been learned, the X-Pedition may give up attempts to communicate with
the server and go to last resort.
2.
The accounting system info option for the AAA server has been activated, and the deadtime
value is set. On boot-up, the X-Pedition will attempt to send accounting messages to the AAA
server; it will fail until the interface containing the X-Pedition has come up. If the deadtime value
is set, the AAA server will be flagged as dead, and the router will skip over it and automatically
go to last-resort.
Workaround:
•
Give the X-Pedition more time to boot-up (this may take longer with larger numbers of interfaces
and/or more configuration).
•
If the AAA server is connected to the X-Pedition through multiple hops, attempt to bring the
server closer to the router.
•
Increase the retry count.
•
If accounting system info is enabled, decrease the deadtime value.
NOTE: Until the system is fully booted, system messages will not be logged to the AAA server.
Virtual Local Area Network (VLAN)
Manual
There are two special VLANs on the X-Pedition, the Default VLAN (ID=1) and the VLAN with
ID=4095. The Default VLAN contains all of the ports not used in other VLANs. When ports are
added to VLANs, they are removed from the Default VLAN. When ports are removed from a VLAN
with an ID other than 1, they are returned to the Default VLAN. The VLAN with the ID of 4095 (a.k.a.
the "blackhole VLAN") is used as the repository for all incoming frames with no destination.
These two VLANs have the following restrictions:
•
Ports cannot explicitly be added to either of these VLANs.
•
Layer 3 interfaces cannot be associated with the "Blackhole VLAN" (ID = 4095)
•
IPX interfaces cannot be associated with the "Default VLAN" (ID = 1).
In order to pass all IBM protocol types, a unique VLAN must be configured for both the SNA and the
Bridged protocols.
Additional information can be found online at: http://www.enterasys.com/support/techbltn/tb11699.html
Wide Area Network (WAN) Modules
Manual
Port mirroring, ACL, and Layer-2 filtering are supported on a per-WAN-card basis, not a per-port
basis.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 30 of 34
COMPLIANCE AND STANDARDS 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.
RFC 1058
RFC 1075
RFC 1105
RFC 1157
RFC 1163
RFC 1256
RFC 1265
RFC 1267
RFC 1293
RFC 1332
RFC 1349
RFC 1397
RFC 1483
RFC 1490
RFC 1519
RFC 1552
RFC 1570
RFC 1583
RFC 1631
RFC 1638
RFC 1657
RFC 1661
RFC 1662
Title
RIP v1
DVMRP
BGP
SNMPv1
BGP-2
ICMP Router Discover Message
BGP Protocol Analysis
BGP-3
Inverse ARP
PPP Internet Protocol Control Protocol (IPCP)
Type of Service in the Internet Protocol Suite
BGP Default Route Advertisement
Multiprotocol Encapsulation over ATM Adaptation Layer 5
Multiprotocol Interconnect over Frame Relay
CIDR
The PPP Internetwork Packet Exchange Control Protocol (IPXCP)
PPP LCP Extensions
OSPF v2
IP Network Address Translator
PPP Bridging Control Protocol (BCP)
BGP-4 Definitions of Managed Objects
PPP (Point-to-Point Protocol)
PPP in HDLC-like Framing
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 31 of 34
COMPLIANCE AND STANDARDS SUPPORT
RFC No.
RFC 1723
RFC 1771
RFC 1772
RFC 1812
RFC 1966
RFC 1990
RFC 1997
RFC 2131
RFC 2225
RFC 2236
RFC 2338
RFC 2391
Title
RIP v2
BGP-4
Application of BGP in the Internet
Router Requirements
BGP Route Reflection
PPP Multi-Link Protocol
BGP Communities Attribute
Dynamic Host Configuration Protocol
Classical IP and ARP over ATM
Internet Group Management Protocol, Version 2
VRRP
Load Sharing using IP Network Address Translation (Load Balance)
IETF STANDARDS MIB SUPPORT:
RFC No.
RFC 1213
RFC 1253
RFC 1471
RFC 1472
RFC 1473
RFC 1474
RFC 1493
RFC 1512
RFC 1595
RFC 1643
RFC 1657
RFC 1695
RFC 1724
RFC 1742
RFC 1850
RFC 1907
RFC 2011
RFC 2012
RFC 2013
RFC 2021
RFC 2096
RFC 2115
RFC 2358
RFC 2495
RFC 2496
RFC 2571
RFC 2572
RFC 2573
RFC 2574
RFC 2575
RFC 2576
RFC 2618
RFC 2668
RFC 2674
RFC 2819
Title
MIB-2
OSPF v2 MIB
PPP LCP (Link Control Protocol)
PPP Security Protocol
PPP IP NCP (Network Control Protocol)
PPP Bridge NCP
Definitions of Managed Objects for Bridges
FDDI MIB
SONET / SDH MIB
Ethernet Like Interface MIB
BGP4 MIB
ATM MIB
RIPv2 MIB
AppleTalk Management Information Base II
OSPF MIB
SNMP v2 MIB
Internet Protocol (IP) MIB using SMIv2
Transmission Control Protocol (TCP) MIB using SMIv2
User Datagram Protocol (UDP) MIB using SMIv2
Remote Network Monitoring Version 2 (RMON 2)
IP Forwarding MIB
Frame Relay DTE using SMIv2
Ethernet-like Interface Types MIB
E1 / DS1 MIB
E3 / DS3 MIB
SNMP Framework MIB
SNMP Message Processing and Dispatching MIB
SNMP Target and Notifications MIBs
SNMP User-Based Security Model MIB
SNMP View-Based Access Control Model MIB
SNMP Community and Target Extensions MIBs
Radius Authentication Client
IEEE 802.3 Medium Attachment Units (MAUs) MIB
IETF Q MIB for Bridge with Traffic Classes, Multicast Filtering and VLAN
Extension
Remote Network Monitoring (RMON) Management Information Base
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 32 of 34
COMPLIANCE AND STANDARDS SUPPORT
RFC 2863
Interfaces Group using SMIv2
IETF EXPERIMENTAL MIB SUPPORT:
Function
DVMRP
IGMP
VRRP
Draft
Draft 4
Draft 5
Draft 9
IETF STANDARDS SNMP TRAP SUPPORT:
RFC No.
RFC 1157
RFC 1493
Title
linkDown, linkUp, authenticationFailure Traps
newRoot, topologyChange Traps
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.617
Title
User-to-Network (UNI) Implementation Agreement
Multiprotocol Encapsulation Implementation Agreement
ISDN Core Aspects of Frame Relay Protocol
Access Signaling Annex A
Standards-Based Frame Relay Specification
Additional Procedures for PVCs Using Unnumbered Information Frames
FDDI STANDARD SUPPORT:
ANSI
ANSI
ANSI
ANSI
ANSI
Standard
X3T9.5
X3T9.5/84-49 Rev 7.2
X3.139-1987
X3.148-1988
X3.166-1990
Title
Fiber Distributed Data Interface (FDDI)
FDDI Station Management (SMT)
FDDI Media Access Control (MAC)
FDDI Physical Layer Protocol (PHY)
FDDI Physical Medium Dependent (PMD)
ENTERASYS NETWORKS PRIVATE ENTERPRISE MIB SUPPORT:
Title
NOVELL-IPX-MIB
CTRON-SSR-HARDWARE-MIB
CTRON-SSR-POLICY-MIB
CTRON-SSR-SERVICE -MIB
CTRON-SSR-CAPACITY -MIB
CTRON-SSR-CONFIG
10/24/01 P/N: 9038090-17
F0615-F
Description
Novell Netware
Device specific hardware objects
L2 filters, L3 ACL set/get ability
Status of major subsystems
New with 3.0 use for performance/capacity
Retrieve/send configuration file via tftp
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 33 of 34
COMPLIANCE AND STANDARDS SUPPORT
NOVEL-RIP-SAP-MIB
CT-CONTAINER-MIB
CTRON-CHASSIS-MIB
DEC-ELAN-MIB
CTRON-CDP-MIB
CTRON-DOWNLOAD-MIB
Novell Netware RIP SAP
Cabletron container MIB
Cabletron chassis MIB (6SSRM-02 Only)
FDDI Extensions
Cabletron Discovery Protocol MIB
Cabletron Download MIB
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.
10/24/01 P/N: 9038090-17
F0615-F
CUSTOMER RELEASE NOTES
Subject to Change Without Notice
Page: 34 of 34