ExtremeXOS Installation and Release Notes 12.2.2
Uploaded by
Rodrigo F MartinsExtremeXOS Installation and Release Notes 12.2.2
Uploaded by
Rodrigo F MartinsExtremeXOS Installation and Release Notes
Software Version ExtremeXOS 12.2.2
Extreme Networks, Inc.
3585 Monroe Street
Santa Clara, California 95051
(888) 257-3000
(408) 579-2800
http://www.extremenetworks.com
Published: March 2009
Part Number: 120436-00 Rev 10
AccessAdapt, Alpine, Altitude, BlackDiamond, EPICenter, Essentials, Ethernet Everywhere, Extreme Enabled,
Extreme Ethernet Everywhere, Extreme Networks, Extreme Standby Router Protocol, Extreme Turbodrive, Extreme
Velocity, ExtremeWare, ExtremeWorks, ExtremeXOS, Go Purple Extreme Solution, ScreenPlay, Sentriant,
ServiceWatch, Summit, SummitStack, Triumph, Unified Access Architecture, Unified Access RF Manager, UniStack,
the Extreme Networks logo, the Alpine logo, the BlackDiamond logo, the Extreme Turbodrive logo, the Summit
logos, and the Powered by ExtremeXOS logo are trademarks or registered trademarks of Extreme Networks, Inc. or
its subsidiaries in the United States and/or other countries.
sFlow is a registered trademark of InMon Corporation.
Specifications are subject to change without notice.
All other registered trademarks, trademarks, and service marks are property of their respective owners.
2008-2009 Extreme Networks, Inc. All Rights Reserved.
ExtremeXOS 12.2.2 Installation and Release Notes
Contents
Chapter 1: Overview ........................................................................................................................ 5
Unsupported Features in ExtremeXOS 12.2.2 on the BlackDiamond 20808 Platform ........................5
New Features or Feature Enhancements in ExtremeXOS 12.2.1.......................................................7
New Hardware Supported in ExtremeXOS 12.2.2 ...........................................................................7
New Hardware Supported in ExtremeXOS 12.2.1 ...........................................................................7
Supported Hardware....................................................................................................................8
BlackDiamond 10808 Switch Component Support ...................................................................8
BlackDiamond 8800 Series of Switches Component Support.....................................................9
BlackDiamond 12800 Series Switches Component Support ....................................................10
BlackDiamond 20808 Switch Component Support .................................................................11
Summit X150 and X350 Component Support ........................................................................11
Summit X250e Component Support......................................................................................11
Summit X450 Component Support .......................................................................................12
Summit X650 Component Support .......................................................................................13
SFP (Mini-GBIC) Support .....................................................................................................13
XENPAK Module Support .....................................................................................................17
XFP Module Support............................................................................................................20
ExtremeXOS Command Line Support.....................................................................................21
Unsupported Commands on the Summit X150 and X350 Series Switches ................................21
Tested Third-Party Products .......................................................................................................22
Tested RADIUS Servers .......................................................................................................22
Tested Third-Party Clients ....................................................................................................23
PoE Capable VoIP Phones ....................................................................................................23
Extreme Switch Security Assessment ..........................................................................................24
DoS Attack Assessment .......................................................................................................24
ICMP Attack Assessment .....................................................................................................24
Port Scan Assessment .........................................................................................................24
Chapter 2: Upgrading to ExtremeXOS.............................................................................................. 25
Staying Current .........................................................................................................................25
Upgrading ExtremeXOS..............................................................................................................25
Quick Summary ..................................................................................................................26
Detailed Steps ....................................................................................................................26
Upgrading ExtremeXOS on Summit Family Switches...............................................................31
Upgrading an MSM-5 and MSM-5R to ExtremeXOS 12.2.2 on a BlackDiamond 12802 .............32
Upgrading a BlackDiamond Series of Switches Using Hitless Upgrade......................................33
Upgrading the Alternate Partition Using Hitless Upgrade.........................................................34
Dual MSM Systems with Different Images Present..................................................................35
Using a Rev 10 (or later) BlackDiamond 10808 MSM-1 or MSM-1XL ......................................36
Installing an ExtremeXOS Module ...............................................................................................36
Uninstalling an SSH Module ......................................................................................................37
Downgrading Switches...............................................................................................................38
ExtremeXOS 12.2.2 Installation and Release Notes
Contents
Chapter 3: Limits........................................................................................................................... 41
Supported Limits ......................................................................................................................41
Chapter 4: Open Issues and Known Behaviors ................................................................................. 67
Open Issues..............................................................................................................................67
Known Behaviors ......................................................................................................................84
Resolved Issues in ExtremeXOS 12.2.2 .......................................................................................87
Resolved Issues in ExtremeXOS 12.2.1 .......................................................................................88
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
These Release Notes document ExtremeXOS 12.2.2, which enables new hardware products and
software features.
This chapter contains the following sections:
Unsupported Features in ExtremeXOS 12.2.2 on the BlackDiamond 20808 Platform on page 5
New Features or Feature Enhancements in ExtremeXOS 12.2.1 on page 7
New Hardware Supported in ExtremeXOS 12.2.2 on page 7
New Hardware Supported in ExtremeXOS 12.2.1 on page 7
Supported Hardware on page 8
Tested Third-Party Products on page 22
Extreme Switch Security Assessment on page 24
Unsupported Features in ExtremeXOS 12.2.2 on the
BlackDiamond 20808 Platform
Following are the features that are not supported on the BlackDiamond 20808 platform in
ExtremeXOS 12.2.2:
64,000 Virtual Local Area Networks (VLANs)
Connectivity Fault Management (CFM)
Anycast Rendezvous Point (RP)
CLEARFlow
CPU Monitor
Disable Learning
Dynamic Access Control List (ACL)
Egress Mirroring
Extreme Standby Router Protocol (ESRP)
Fast-direct Broadcast
Hierarchical Quality of Service (H-QoS) Bandwidth Mode
Ignore-broadcast
IP Address Security
IP Directional Broadcast
IPv6
ACL
Equal Cost Multipath (ECMP)
Intermediate System-Intermediate System (IS-IS)
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
Multicast Listener Discovery v1 (MLDv1)
Multicast
netTools
Routing Information Protocol Next Generation (RIPng)/Open Shortest Path First (OSPFv3)
Routing protocol
Services
IS-IS
Link Aggregation Group (LAG)
Link Layer Discovery Protocol (LLDP)
MAC Security
Multiprotocol BGP (MBGP)
MultiProtocol Label Switching. (MPLS)
ESRP Redundant Access
Fast reroute (FRR)
Hierarchical Virtual Private LAN Services (H-VPLS)
Load Sharing
RSVP
Static Link State Packets (LSPs)
MPLS Label Experimental (EXP) Bit Replacement and Classification
VPLS Packet Counts Maintained for First 1,000 Pseudo Wires (PWs) Only
Packet/Byte Egress Counts for PWs
VPLS Support for LSPs and PWs over Link Aggregation Trunk Ports
Multicast Source Discovery Protocol (MSDP)
Netlogin-Dot1/MAC/Web
Provider Backbone Bridge (PBB) including CFM and MAC-in-MAC
Backbone Bridge-Traffic Engineering (PBB-TE)
Policy based routing (PBR)
PBR_L2
PBR Multi Next Hop (PBR_MULTINXTHOP)
Protocol VLAN
Remote Mirroring
sFlow
Unicast Reverse Path Forwarding (uRPF)
User Datagram Protocol (UDP) Forwarding
USB Port Support
IPv6-in-IPv4 Tunneling
VLAN Aggregation
vMAN Enhancement
VPLS/QoS
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
New Features or Feature Enhancements in ExtremeXOS
12.2.1
Following are the new features or feature enhancements supported in ExtremeXOS 12.2.1. These
features are documented in detail in the ExtremeXOS 12.2.1 versions of the ExtremeXOS Concepts Guide
and the ExtremeXOS Command Reference Guide, unless otherwise noted.
Improved IP multicast scaling for BlackDiamond 8800 and Summit family switches.
Command line interface (CLI) commands have been added to display new counters:
The show ports <port_list> congestion [no-refresh] command displays port congestion
counters.
The show ports <port_list> qosmonitor [congestion] [no-refresh] command displays
QoS profile congestion.
The show ports {<port_list>} rate-limit flood {no-refresh} command displays
counters for per port rate limiting of flood traffic.
Link Layer Discovery Protocol (LLDP) extensions support for ReachNXT 100-8T.
Improved quality of service (QoS) for stackable switches. For stacking links, only one QoS queue is
now reserved and QoS scheduling is improved.
New Hardware Supported in ExtremeXOS 12.2.2
The following modules are supported in ExtremeXOS 12.2.2:
Summit X650-24t switch
Option card for Summit X650-24t
VIM1-SummitStack Versatile Interface Module (VIM) (four 1-gigabit SFP ports and two 40gigabit stacking ports)
Option card for Summit X650-24t and X650-24x switch:
24 10GBASE-T ports
VIM1-10G8X (eight 10GBASE-X SFP+ ports and two 40-gigabit stacking ports)
BlackDiamond 20808 switch
New Hardware Supported in ExtremeXOS 12.2.1
The following modules are supported in ExtremeXOS 12.2.1:
Summit X650-24x switch
24 10GBASE-X SFP+ optical ports
Option card for Summit X650-24x switch:
VIM1-SummitStack Versatile Interface Module (VIM) (four 1-gigabit SFP ports and two 40-gigabit
stacking ports)
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
Option cards for the Summit X450 a/e and Summit X350 series:
XGM2-2sf (option card with two SFP+ optic ports)
XGM2-2bt (option card with two 10GBASE-T copper ports)
ReachNXT 100-8t
Supported Hardware
Refer to the Extreme Networks hardware installation guides for more information about supported
hardware. The following tables list the software filenames for the hardware that requires software.
BlackDiamond 10808 Switch Component Support
BlackDiamond 10808 components supported with ExtremeXOS 12.2.2, and the minimum ExtremeXOS
version required by the chassis to support each component, include:
Table 1: BlackDiamond 10808 Component Support
BlackDiamond Component
ExtremeXOS Filenames
ExtremeXOS Required
BootROM Version
MSM-1
bd10k-12.2.2.xos
10.1.0
1.0.1.5
MSM-1XL
bd10k-12.2.2.xos
10.1.0
1.0.1.5
10G2X
N/A
11.1.1
1.3.0.0
10G2H
N/A
11.2.0
1.3.0.0
10G6X
N/A
10.1.0
1.3.0.0
G20X
N/A
11.1.1
1.3.0.0
G60X
N/A
10.1.0
1.3.0.0
G60T
N/A
10.1.0
1.3.0.0
PSU Controller
N/A
10.1.0
N/A
700/1200 W AC PSU (Model
# 60020/PS 2336)
N/A
10.1.0
N/A
1200 W DC PSU (Model #
60021/PS 2350)
N/A
11.3.2.6
N/A
Following are the part numbers for the BlackDiamond 10808 modules with the Rev. D ASIC:
Table 2: BlackDiamond 10808 I/O Modules with Part Numbers
I/O
Module
8000 Level
Part No.
9000 Level Part
No.
G60T
804403-00,
after Rev. 16
904015-00
BlackDiamond 10808 60-port 10/100/1000BASE-T
RJ-45 Module
11.2.1.3
804408-00,
after Rev. 03
904015-10
BlackDiamond 10808 60-port 10/100/1000BASE-T
RJ-45 Module
11.2.1.3
804402-00,
after Rev. 16
904009-00/11
BlackDiamond 10808 60-port 1000BASE-X SFP
(mini-GBIC) Module
11.2.1.3
804404-00,
after Rev. 03
904009-10
BlackDiamond 10808 60-port 1000BASE-X SFP
(mini-GBIC) Module
11.2.1.3
G60X
ExtremeXOS
Required
Description
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
Table 2: BlackDiamond 10808 I/O Modules with Part Numbers
I/O
Module
8000 Level
Part No.
9000 Level Part
No.
G20X
804407-00,
after Rev. 03
904020-10
BlackDiamond 10808 20-port 1000BASE-X SFP
(mini-GBIC) Module
11.2.1.3
804470-00,
after Rev. 08
904020-00/11
BlackDiamond 10808 20-port 1000BASE-X SFP
(mini-GBIC) Module
11.2.1.3
804410-00,
after Rev. 03
904032-10
BlackDiamond 10808 2-port 10GBASE-X XENPAK
Module
11.2.1.3
804471-00,
after Rev. 11
904032-00/11
BlackDiamond 10808 2-port 10GBASE-X XENPAK
Module
11.2.1.3
804406-00,
after Rev. 09
904027-00/11
BlackDiamond 10808 Hybrid Module (2-port
10GBASE-X XENPAK, 20-port 1000BASE-X SFP,
20-port 10/100/1000BASE-T RJ-45)
11.2.1.3
804411-00,
after Rev. 03
904027-10
BlackDiamond 10808 Hybrid Module (2-port
10GBASE-X XENPAK, 20-port 1000BASE-X SFP,
20-port 10/100/1000BASE-T RJ-45)
11.2.1.3
804405-00,
after Rev. 18
904016-00/11
BlackDiamond 10808 6-port 10GBASE-X XENPAK
Module
11.2.1.3
804409-00,
after Rev. 03
904016-10
BlackDiamond 10808 6-port 10GBASE-X XENPAK
Module
11.2.1.3
10G2X
10G2H
10G6X
ExtremeXOS
Required
Description
BlackDiamond 8800 Series of Switches Component Support
BlackDiamond 8800 and BlackDiamond 8806 components supported with ExtremeXOS 12.2.2, and the
minimum BootROM version required by the chassis to support each component, include:
Table 3: BlackDiamond 8800 Series of Switches Component Support
BlackDiamond 8810 and
BlackDiamond 8806 Components
ExtremeXOS Filenames
ExtremeXOS Required
BootROM Version
MSM-G8X
bd8800-12.2.2.xos
11.1.1.9
1.0.1.7
MSM-48
bd8800-12.2.2.xos
11.6.1.9
1.0.1.11
MSM-48c
bd8800-12.2.2.xos
12.1.1.4
1.0.3.7
G48Te
N/A
11.5.1.4
1.0.1.10
G48Pe
N/A
11.5.1.4
1.0.1.10
G48Ta
N/A
11.5.1.4
1.0.1.10
G48Xa
N/A
11.5.1.4
1.0.1.10
G48P
N/A
11.1.1.9
1.0.1.7
G48T
N/A
11.1.1.9
1.0.1.7
G48Tc
N/A
12.1.1.4
1.0.3.7
G48Te2
N/A
12.1.1.4
1.0.3.7
G48Xc
N/A
12.1.1.4
1.0.3.7
G24X
N/A
11.1.1.9
1.0.1.7
G24Xc
N/A
12.1.1.4
1.0.3.7
S-G8Xc
N/A
12.1.1.4
1.0.3.7
10G4X
N/A
11.1.1.9
1.0.1.7
10G4Xa
N/A
11.6.1.9
1.0.1.11
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
Table 3: BlackDiamond 8800 Series of Switches Component Support (Continued)
BlackDiamond 8810 and
BlackDiamond 8806 Components
ExtremeXOS Filenames
ExtremeXOS Required
BootROM Version
10G4Ca
N/A
12.0.1.11
1.0.1.11
10G4Xc
N/A
12.1.1.4
1.0.3.7
10G8Xc
N/A
12.1.1.4
1.0.3.7
S-10G1Xc
N/A
12.1.1.4
1.0.3.7
PSU Controller
N/A
11.1.1.9
2.13
700/1200 W AC PSU (Model #
60020/PS 2336)
N/A
11.1.1.9
N/A
600/900 W AC PSU (Model #
41050/PS 2431) (BlackDiamond
8806 only)
N/A
11.6.1.9
N/A
1200 W DC PSU (Model #
60021/PS 2350)
N/A
11.3.2.6
N/A
NOTE
Upgrading the BootROM on a BlackDiamond 8810 or BlackDiamond 8806 switch is not automatic when you
upgrade the software. You must be running the minimum required BootROM version or later. Use the install firmware
command after upgrading the ExtremeXOS image to insure the BootROM is at the latest level.
BlackDiamond 12800 Series Switches Component Support
BlackDiamond 12802, BlackDiamond 12804, BlackDiamond 12802 R-Series, and BlackDiamond 12804 RSeries components supported with ExtremeXOS 12.2.2, and the minimum BootROM version required by
the chassis to support each component, include:
Table 4: BlackDiamond 12800 Series Switches Component Support
10
BlackDiamond 12802/12804
Components
ExtremeXOS Filenames
ExtremeXOS Required
BootROM Version
MSM-5R (BlackDiamond 12804)
bd12k-12.2.2.xos
11.4.1.4
1.0.0.2
MSM-5 (BlackDiamond 12804)
bd12k-12.2.2.xos
11.4.1.4
1.0.0.2
MSM-5 (BlackDiamond 12802)
bd12k-12.2.2.xos
12.0.1.11
1.0.0.2
MSM-6R
bd12k-12.2.2.xos
12.0.2.25
1.0.1.8
MSM-5R (BlackDiamond 12802)
bd12K-12.2.2.xos
12.0.1.11
1.0.0.2
XM-2X
N/A
12.2.2
N/A
XM-2XR
N/A
11.4.1.4
N/A
XM-2HR
N/A
12.1.1.4
N/A
GM-20XTR
N/A
11.4.1.4
N/A
GM-20XT
N/A
11.4.1.4
N/A
GM-20T
N/A
11.4.1.4
N/A
PSU Controller
N/A
11.4.1.4
2.13
700/1200 W AC PSU (Model #
60020/PS 2336)
N/A
11.4.1.4
N/A
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
Table 4: BlackDiamond 12800 Series Switches Component Support (Continued)
BlackDiamond 12802/12804
Components
1200 W DC PSU (Model #
60021/PS 2350)
ExtremeXOS Filenames
ExtremeXOS Required
BootROM Version
N/A
11.4.1.4
N/A
BlackDiamond 20808 Switch Component Support
BlackDiamond 20808 switch components supported with ExtremeXOS 12.2.2, and the minimum
BootROM version required by the chassis to support each component, include:
Table 5: BlackDiamond 20808 Switch Component Support
BlackDiamond 12802/12804
Components
ExtremeXOS Filenames
ExtremeXOS Required
GM-40XB
bd20k-12.2.2.xos
12.2.2
XM-8XB
bd20k-12.2.2.xos
12.2.2
XFM-1
bd20k-12.2.2.xos
12.2.2
MM-Base
bd20k-12.2.2.xos
12.2.2
BootROM Version
Summit X150 and X350 Component Support
Summit X150 and X350 series components supported with ExtremeXOS 12.2.2, and the minimum
BootROM version required by the switch to support each component, include:
Table 6: Summit X150 and X350 Component Support
ExtremeXOS Filenames
Minimum
ExtremeXOS
Required
Minimum BootROM
Version
Summit X150-24t
summitX-12.2.2.xos
12.0.2.25
1.0.3.1
Summit X150-48t
summitX-12.2.2.xos
12.0.2.25
1.0.3.1
Summit X150-24p
summitX-12.2.2.xos
12.0.2.25
1.0.3.1
Summit X350-24t
summitX-12.2.2.xos
12.0.3.16
1.0.3.1
Summit X350-48t
summitX-12.2.2.xos
12.0.3.16
1.0.3.1
XGM2-2sf (Summit X350 only)
summitX-12.2.2.xos
12.2.1
N/A
XGM2-2bt (Summit X350 only)
summitX-12.2.2.xos
12.2.1
N/A
Summit X150 and X350
Components
Summit X250e Component Support
Summit X250e components supported with ExtremeXOS 12.2.2, and the minimum BootROM version
required by the switch to support each component, include:
ExtremeXOS 12.2.2 Installation and Release Notes
11
Overview
Table 7: Summit X250e Component Support
Summit X250 Components
ExtremeXOS Filenames
Minimum
ExtremeXOS
Required
Summit X250e-24p
summitX-12.2.2.xos
12.0.1.11
1.0.3.0
Summit X250e-48p
summitX-12.2.2.xos
12.0.1.11
1.0.3.0
Summit X250e-24t
summitX-12.2.2.xos
12.0.1.11
1.0.3.0
Summit X250e-48t
summitX-12.2.2.xos
12.0.1.11
1.0.3.0
Summit X250e-24x
summitX-12.2.2.xos
12.0.2.25
1.0.3.1
Summit X250e-24tDC
summitX-12.2.2.xos
12.0.3.16
1.0.3.1
Summit X250e-24xDC
summitX-12.2.2.xos
12.0.3.16
1.0.3.1
Summit X250e-48tDC
summitX-12.2.2.xos
12.0.3.16
1.0.3.1
Minimum BootROM
Version
Summit X450 Component Support
Summit X450 components supported with ExtremeXOS 12.2.2, and the minimum BootROM version
required by the switch to support each component, include:
Table 8: Summit X450 Component Support
ExtremeXOS Filenames
Minimum
ExtremeXOS
Required
Minimum BootROM
Version
Summit X450a-48t
summitX-12.2.2.xos
11.5.1.4
1.0.2.2
Summit X450a-48tDC
summitX-12.2.2.xos
11.6.1.9
1.0.2.2
Summit X450a-24t
summitX-12.2.2.xos
11.5.1.4
1.0.2.2
Summit X450a-24tDC
summitX-12.2.2.xos
11.5.1.4
1.0.2.2
Summit X450a-24xDC
summitX-12.2.2.xos
11.6.1.9
1.0.2.2
Summit X450a-24x
summitX-12.2.2.xos
11.6.1.9
1.0.2.2
Summit X450e-24p
summitX-12.2.2.xos
11.5.1.4
1.0.2.2
Summit X450e-48p
summitX-12.2.2.xos
11.6.1.9
1.0.2.2
Summit X450-24x
summitX-12.2.2.xos
11.2.2.4
1.0.0.9
Summit X450-24t
summitX-12.2.2.xos
11.2.2.4
1.0.0.9
XGM-2xn
summitX-12.2.2.xos
N/A
N/A
XGM2-2xn (Summit X450a and
X450e series only)
summitX-12.2.2.xos
11.5.1.4
XGM2-2xf (Summit X450a and
X450e series only)
summitX-12.2.2.xos
11.5.1.4
XGM2-2sf (Summit X450a and
X450e series only)
summitX-12.2.2.xos
12.2.1
XGM2-2bt (Summit X450a and
X450e series only)
summitX-12.2.2.xos
12.2.1
Summit X450 Components
Summit X450a Series
Summit X450e Series
Summit X450 Series
Option Cards
12
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
Summit X650 Component Support
Summit X650 components supported with ExtremeXOS 12.2.2, and the minimum BootROM version
required by the chassis to support each component, include:
Table 9: Summit X650 Component Support
Summit X650 Components
ExtremeXOS Filenames
Minimum
ExtremeXOS
Required
Summit X650-24x
summitX-12.2.2.xos
12.2.1
1.0.5.5
Summit X650-24t
summitX-12.2.2.xos
12.2.2
1.0.5.5
VIM1-SummitStack
summitX-12.2.2.xos
12.2.1
N/A
VIM1-10G8X
summitX-12.2.2.xos
12.2.2
N/A
Minimum BootROM
Version
NOTE
Upgrading the BootROM on Summit family switches is not automatic when you upgrade the software.You must be
running the minimum required BootROM version. Use the download bootrom command to download a BootROM
image.
SFP (Mini-GBIC) Support
SFPs supported on the BlackDiamond 8810 and BlackDiamond 8806 switches with ExtremeXOS 12.2.2,
and the minimum ExtremeXOS version required, include:
Table 10: BlackDiamond 8800 Series of Switches SFP Support
SFP
ExtremeXOS Required
1000BASE-T SFP
11.1.1.9
SX SFP
11.1.1.9
LX SFP
11.1.1.9
ZX SFP
11.1.1.9
100FX/1000LX SFP
11.3.1.3
100FX SFP
11.4.3.4 or 11.5.2.10 (not supported in 11.5.1.4)
1000BX SFP
11.4.1.4
LX100 SFP
12.0.1.11
10/100/1000BASE-T Copper SFP
12.0.2.25
SFPs supported on the BlackDiamond 10808 switch with ExtremeXOS 12.2.2, and the minimum
ExtremeXOS version required, include
Table 11: BlackDiamond 10808 Switch SFP Support
SFP
ExtremeXOS Required
LX100 SFP
12.0.1.11
SX SFP
10.1.0
ExtremeXOS 12.2.2 Installation and Release Notes
13
Overview
Table 11: BlackDiamond 10808 Switch SFP Support (Continued)
SFP
ExtremeXOS Required
LX SFP
10.1.0
ZX SFP
10.1.0
1000BASE-T SFP
11.1.1.9
1000BX SFP
11.6.1.9
SFPs supported on the BlackDiamond 12804 switch with ExtremeXOS 12.2.2, and the minimum
ExtremeXOS version required, include:
Table 12: BlackDiamond 12804 Switch SFP Support
SFP
ExtremeXOS Required
SX SFP
11.4.1.4
LX SFP
11.4.1.4
ZX SFP
11.4.1.4
1000BASE-T SFP
11.4.1.4
1000BX SFP
11.6.1.9
LX100 SFP
12.0.1.11
100FX/1000LX SFP
12.0.1.11
SFPs supported on the BlackDiamond 12802 switch with ExtremeXOS 12.2.2, and the minimum
ExtremeXOS version required, include:
Table 13: BlackDiamond 12802 Switch SFP Support
SFP
ExtremeXOS Required
SX SFP
12.0.1.11
LX SFP
12.0.1.11
ZX SFP
12.0.1.11
1000BASE-T SFP
12.0.1.11
1000BX SFP
12.0.1.11
LX100 SFP
12.0.1.11
100FX/1000LX SFP
12.0.1.11
SFPs supported on the BlackDiamond 20808 switch with ExtremeXOS 12.2, and the minimum
ExtremeXOS version required, include:
Table 14: BlackDiamond 20808 Switch SFP Support
14
SFP
ExtremeXOS Required
SX SFP
12.2
LX SFP
12.2
ZX SFP
12.2
LX100
12.2
BXU
12.2
BXD
12.2
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
SFPs supported on the Summit X150 series switches with ExtremeXOS 12.2.2, and the minimum
ExtremeXOS version required, include:
Table 15: Summit X150 Series Switches SFP Support
SFP
ExtremeXOS Required
100BASE-FX (P/N 10067)
12.0.2.25
100BASE-BX SFP
12.0.2.25
100BASE LX10 SFP
12.0.2.25
SX SFP
12.0.2.25
LX SFP
12.0.2.25
ZX SFP
12.0.2.25
LX100 SFP
12.0.2.25
1000BX SFP
12.0.2.25
SFPs supported on the Summit X250e switch with ExtremeXOS 12.2.2, and the minimum ExtremeXOS
version required, include:
Table 16: Summit X250e SFP Support
SFP
ExtremeXOS Required
SX SFP, ports 25 and 26
12.0.2.25
LX SFP, ports 25 and 26
12.0.2.25
ZX SFP, ports 25 and 26
12.0.2.25
LX100 SFP, ports 25 and 26
12.0.2.25
1000BX SFP, ports 25 and 26
12.0.2.25
100BASE FX SFP (P/N 10067), ports 1 through 26
12.0.2.25
100BASE BX SFP, ports 1 through 26
12.0.2.25
100BASE LX10 SFP, ports 1 through 26
12.0.2.25
SFPs supported on the Summit X350 series switches with ExtremeXOS 12.2.2, and the minimum
ExtremeXOS version required, include:
Table 17: Summit X350 Series Switches SFP/SFP+ (XGM2-2sf Option Card Required) Support
SFP
ExtremeXOS Required
SX SFP
12.0.3.16
LX SFP
12.0.3.16
ZX SFP
12.0.3.16
LX100 SFP
12.0.3.16
1000BX SFP
12.0.3.16
SR SFP+
12.2.1
LR SFP+
12.2.1
SFP+ twin coax cables
12.2.1
ExtremeXOS 12.2.2 Installation and Release Notes
15
Overview
SFPs supported on the Summit X450 switch with ExtremeXOS 12.2.2, and the minimum ExtremeXOS
version required, include:
Table 18: Summit X450 Switch SFP Support
SFP
ExtremeXOS Required
10/100/1000BASE-T Copper SFP
12.0.2.25
Note: Not supported on combo ports.
SX SFP
11.2.2.4
LX SFP
11.2.2.4
ZX SFP
11.2.2.4
1000BASE-T SFP
11.2.2.4
100FX SFP (P/N 10063)
11.4.3.4 or 11.5.2.10 (not supported in 11.5.1.4)
Note: Not supported on combo ports.
100FX/1000LX SFP
Note: Not supported on combo ports.
11.3.1.3
LX100 SFP
12.0.1.11
1000BX SFP
11.6.1.9
SFPs supported on the Summit X450a switch with ExtremeXOS 12.2.2, and the minimum ExtremeXOS
version required, include:
Table 19: Summit X450a Switch SFP/SFP+ (XGM2-2sf Option Card Required) Support
SFP
ExtremeXOS Required
10/100/1000BASE-T Copper SFP
12.0.2.25
Note: Not supported on combo ports.
SX SFP
11.2.2.4
LX SFP
11.2.2.4
ZX SFP
11.2.2.4
SR SFP+
12.2.1
LR SFP+
12.2.1
SFP+ twin coax cables
12.2.1
100FX SFP (P/N 10063)
11.6.1.9
Note: Not supported on combo ports.
100FX/1000LX SFP
11.6.1.9
Summit X450a-24x, ports 1 through 20
Note: Not supported on combo ports.
16
LX100 SFP
12.0.1.11
1000BX SFP
11.6.1.9
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
SFPs supported on the Summit X450e switch with ExtremeXOS 12.2.2, and the minimum ExtremeXOS
version required, include:
Table 20: Summit X450e Switch SFP/SFP+ (XGM2-2sf Option Card Required) Support
SFP
ExtremeXOS Required
SX SFP
11.6.1.9
LX SFP
11.6.1.9
ZX SFP
11.6.1.9
LX100 SFP
12.0.1.11
1000BX SFP
11.6.1.9
SFPs supported on the Summit X650 series switches with ExtremeXOS 12.2.2, and the minimum
ExtremeXOS version required, include:
Table 21: Summit X650 Series Switches SFP/SFP+ Support
SFP
ExtremeXOS Required
SR SFP+, ports 1 through 24, and ports 25 through 32 (for the
VIM1-10G8X)
12.2.2
LR SFP+, ports 1-24 and 25-32 for VIM1-10G8X
12.2.2
SFP+ twin coax cable - 1-24 and 25-32 for VIM1-10G8X
12.2.2
1000BX SFP, ports 1 through 22, and 25 through 28
12.2.1
1000SX SFP, ports 1 through 22, and 25 through 28
12.2.1
1000LX SFP, ports 1 through 22, and 25 through 28
12.2.1
LX100 SFP, ports 1 through 22, and ports 25 through 28
12.2.1
ZX SFP, ports 1 through 22, and ports 25 through 28
12.2.1
XENPAK Module Support
XENPAK modules supported on the BlackDiamond 8800 series of switches with ExtremeXOS 12.2.2,
and the minimum ExtremeXOS version required, include:
Table 22: BlackDiamond 8800 Series of Switches XENPAK Support
XENPAK Module
ExtremeXOS Required
LR
11.1.1.9
ER
11.1.1.9
SR
11.1.1.9
LX4
11.3.1.3
ZR
11.3.1.3
CX4
12.0.1.11
ExtremeXOS 12.2.2 Installation and Release Notes
17
Overview
XENPAK modules supported on the BlackDiamond 10808 switch with ExtremeXOS 12.2.2, and the
minimum ExtremeXOS version required, include:
Table 23: BlackDiamond 10808 Switch XENPAK Support
XENPAK Module
ExtremeXOS Required
LR
11.1.1.9
ER
11.1.1.9
SR
11.1.1.9
LX4
11.3.1.3
ZR
11.3.1.3
LW
11.4.1.4
XENPAK modules supported on the BlackDiamond 12804 switch with ExtremeXOS 12.2.2, and the
minimum ExtremeXOS version required, include:
Table 24: BlackDiamond 12804 Switch XENPAK Support
XENPAK Module
ExtremeXOS Required
LR
11.4.1.4
ER
11.4.1.4
SR
11.4.1.4
LX4
11.4.1.4
ZR
11.4.1.4
LW
11.4.1.4
XENPAK modules supported on the BlackDiamond 12802 switch with ExtremeXOS 12.2.2, and the
minimum ExtremeXOS version required, include
Table 25: BlackDiamond 12802 Switch XENPAK Support
XENPAK Module
ExtremeXOS Required
LR
12.0.1.11
ER
12.0.1.11
SR
12.0.1.11
LX4
12.0.1.11
ZR
12.0.1.11
LW
12.0.1.11
XENPAK modules supported on the Summit X450 switch with ExtremeXOS 12.2.2, and the minimum
ExtremeXOS version required, include:
Table 26: Summit X450 Switch XENPAK Support
18
XENPAK Module
ExtremeXOS Required
SR
11.3.1.3
LR
11.3.1.3
ER
11.3.1.3
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
Table 26: Summit X450 Switch XENPAK Support
XENPAK Module
ExtremeXOS Required
LX4
11.3.1.3
ZR
11.3.1.3
XENPAK modules supported on the Summit X450a switch with ExtremeXOS 12.2.2, and the minimum
ExtremeXOS version required, include:
Table 27: Summit X450a Switch XENPAK Support
XENPAK Module
ExtremeXOS Required
SR
11.6.1.9
LR
11.6.1.9
ER
11.6.1.9
LX4
11.6.1.9
ZR
11.6.1.9
LW
11.6.1.9
CX4
12.0.1.11
XENPAK modules supported on the Summit X450e switch with ExtremeXOS 12.2.2, and the minimum
ExtremeXOS version required, include:
Table 28: Summit X450e Switch XENPAK Support
XENPAK Module
ExtremeXOS Required
SR
11.5.1.4
LR
11.5.1.4
ER
11.5.1.4
LX4
11.5.1.4
ZR
11.5.1.4
CX4
12.0.1.11
XENPAK modules supported on the Summit X350 switch with ExtremeXOS 12.2.2, and the minimum
ExtremeXOS version required, include:
Table 29: Summit X350 Switch XENPAK Support
XENPAK Module
ExtremeXOS Required
SR
12.0.3.16
LR
12.0.3.16
ER
12.0.3.16
LX4
12.0.3.16
ZR
12.0.3.16
XENPAKs not supplied by Extreme Networks will show up as Unsupported Optic Module in the
show port x:y information detail and show port x:y configuration command output.
ExtremeXOS 12.2.2 Installation and Release Notes
19
Overview
XFP Module Support
XFP modules supported on the BlackDiamond 8800 series of switches with ExtremeXOS 12.2.2, the
minimum ExtremeXOS version required include:
Table 30: BlackDiamond 8800 Series of Switches XFP Support
XFP Module
ExtremeXOS Required
SR
11.6.1.9
LR
11.6.1.9
ER
12.0.2.25
DWDM
12.1.2.17
ZR
12.1.2.17
XFP modules supported on the BlackDiamond 20808 switch with ExtremeXOS 12.2, the minimum
ExtremeXOS version required include:
Table 31: BlackDiamond 20808 Switch XFP Support
XFP Module
ExtremeXOS Required
SR
12.2
LR
12.2
ER
12.2
ZR
12.2
XFP modules supported on the Summit X450a and X450e series switch with ExtremeXOS 12.2.2, the
minimum ExtremeXOS version required, and the manufacturers supported include:
Table 32: Summit X450a and X450e Series Switch XFP Support
XFP Module
ExtremeXOS Required
SR
11.5.1.4
LR
11.5.1.4
ER
12.0.2.25
DWDM
12.1.2.17
ZR
12.1.2.17
XFP modules supported on the Summit X350 switch with ExtremeXOS 12.2.2, the minimum
ExtremeXOS version required, and the manufacturers supported include:
Table 33: Summit X350 Switch XFP Support
20
XFP Module
ExtremeXOS Required
SR
12.0.3.16
LR
12.0.3.16
ER
12.0.3.16
DWDM
12.1.2.17
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
Table 33: Summit X350 Switch XFP Support
XFP Module
ExtremeXOS Required
ZR
12.1.2.17
ExtremeXOS Command Line Support
The following is true for all Summit X150 and X350 series switches:
Summit X150 and X350 series switches do not support L3 functionality; this platform does not
support CLI commands for L3 functionality.
Summit X150 and X350 series switches do not support stacking; all CLI commands for stacking are
not supported on this platform.
Summit X150 and X350 series switches do not support IP forwarding; however, CLI commands that
configure IP addresses function in order to access the management functionality of the switch are
supported.
Upgrade or trial licensing is not available on the Summit X150 and X350 series switches.
Unsupported Commands on the Summit X150 and X350 Series
Switches
Following is the list of processes that are not supported with an L2 Edge license.
bgp
msdp
ospf
ospfv3
rip
ripng
pim
vrrp
brm
upm
Table 34 lists the CLI commands not supported on the Summit X150 and X350 series switches.
Table 34: Summit X150 and X350 Unsupported Commands
Command
Description
configure
Configure running system information
ipforwarding
Configure IP forwarding behavior
ipmcforwarding
Configure IP multicast forwarding parameters
ipmroute
IP multicast routing module
irdp
ICMP Router Discovery Protocol
stacking
Settings for stacking
vlan {vlan_name} router-discovery
IPv6 router discovery
ExtremeXOS 12.2.2 Installation and Release Notes
21
Overview
Table 34: Summit X150 and X350 Unsupported Commands (Continued)
Command
vlan {vlan_name} udp-profile
disable
Description
UDP forwarding profile
Disable running system setting
esrp
ESRP (Extreme Standby Router Protocol) Domain
ipforwarding
IP forwarding
ipmcforwarding
IP multicast forwarding help
irdp
ICMP Router Discovery Protocol
router-discovery
IPv6 router discovery
stacking
Stacking
enable
Enable running system setting
esrp <esrp-domain>
ESRP (Extreme Standby Router Protocol) Domain
ipforwarding
IP forwarding
ipmcforwarding
IP multicast forwarding help
irdp
ICMP Router Discovery Protocol
router-discovery
IPv6 router discovery
stacking
Stacking
reboot
Reboot system
node-address
Reboot a node in the stack
stack-topology
Reboot stack-topology
show
Show running system information
router-discovery
IPv6 router discovery
stacking
Stacking information
udp-profile
UDP forwarding profile
synchronize
stacking
unconfigure
Synchronize entire primary MSM to backup MSM
Synchronize stacking configuration
Unconfigure system configuration
stacking
Settings for stacking
vlan {vlan_name} router-discovery
IPv6 router discovery
vlan {vlan_name} udp-profile
UDP forwarding profile
Tested Third-Party Products
This section lists the third-party products tested for ExtremeXOS 12.2.2.
Tested RADIUS Servers
The following RADIUS servers are fully tested:
22
MicrosoftInternet Authentication Server
Funk SoftwareSteel-Belted RADIUS Enterprise Edition 4.5
ExtremeXOS 12.2.2 Installation and Release Notes
Overview
Meetinghouse
FreeRADIUS
Tested Third-Party Clients
The following third-party clients are fully tested:
Funk Odyssey 2.2
MeetingHouse Data AEGIS 2.0.5
Odyssey 3.03.0.1194
PoE Capable VoIP Phones
The following PoE capable VoIP phones are fully tested:
Avaya 4620
Avaya 4620SW IP telephone
Avaya 9620
Avaya 4602
Avaya 9630
Avaya 4621SW
Avaya 4610
Avaya 1616
Avaya one-X
Cisco 7970
Cisco 7910
Cisco 7960
ShoreTel ShorePhone IP 212k
ShoreTel ShorePhone IP 560
ShoreTel ShorePhone IP 560g
ShoreTel ShorePhone IP 8000
ShoreTel ShorePhone IP BB 24
Siemens OptiPoint 410 standard2
Siemens OpenStage 20
ExtremeXOS 12.2.2 Installation and Release Notes
23
Overview
Siemens OpenStage 40
Siemens OpenStage 60
Siemens OpenStage 80
Extreme Switch Security Assessment
DoS Attack Assessment
Tools used to assess DoS attack vulnerability:
Network Mapper (NMAP)
ICMP Attack Assessment
Tools used to assess ICMP attack vulnerability:
SSPing
Twinge
Nuke
WinFreeze
Port Scan Assessment
Tools used to assess port scan assessment:
24
Nessus
ExtremeXOS 12.2.2 Installation and Release Notes
Upgrading to ExtremeXOS
This chapter contains the following sections:
Staying Current on page 25
Upgrading ExtremeXOS on page 25
Installing an ExtremeXOS Module on page 36
Uninstalling an SSH Module on page 37
Downgrading Switches on page 38
Staying Current
If you are an Extreme Assist customer, the latest release and release notes are available after logging in
to the Tech Support web site at
http://www.extremenetworks.com/go/esupport.htm.
For more information about ExtremeXOS, see the ExtremeXOS Concepts Guide and the ExtremeXOS
Command Reference Guide.
Upgrading ExtremeXOS
Upgrading your current ExtremeXOS installation to ExtremeXOS version is a multistep process. In this
section is a quick summary of the necessary steps, followed by detailed instructions.
NOTE
Hitless upgrade for network login is not supported when upgrading from an earlier version of ExtremeXOS software to
ExtremeXOS 12.1 or later. If a hitless upgrade is required, you must globally disable network login and re-enable it
when the upgrade is complete.
NOTE
See the Hitless Upgrade Caveats for BlackDiamond 8800 Series Switches Only in the ExtremeXOS Concepts
Guide for an important caution about performing an MSM failover.
NOTE
Beginning with ExtremeXOS, an ExtremeXOS core image (.xos file) must be downloaded and installed on the
alternate (non-active) partition. If you try to download to an active partition, the error message Error: Image can
only be installed to the non-active partition. is displayed. An ExtremeXOS modular software package (.xmod file)
can still be downloaded and installed on either the active or alternate partition.
ExtremeXOS 12.2.2 Installation and Release Notes
25
Upgrading to ExtremeXOS
NOTE
With ExtremeXOS 12.2.2, the BlackDiamond 8800 series of switches and the BlackDiamond 12800 series switches
now require a firmware upgrade along with the standard software upgrade.
NOTE
A "Failed to install image" error occurs when trying to upgrade from ExtremeXOS 11.2.1 images to ExtremeXOS 11.6
or later. To upgrade to ExtremeXOS 12.2.2, you must currently be running ExtremeXOS 11.6 or later. If you are not
running 11.6 or later you must first upgrade to ExtremeXOS 11.6 or later and then upgrade to ExtremeXOS 12.2.2.
Quick Summary
To install and upgrade to ExtremeXOS on your system, you will be following these steps:
1 Download the image to your TFTP server.
2 Verify which virtual router connects to your TFTP server.
3 Save your configuration to a backup configuration file.
4 Determine your selected and booted image partitions.
5 Download and install the image to the switch.
6 Reboot the switch.
7 Save the configuration for the new image.
8 Upgrade the BootROMBlackDiamond 10808 switch only.
9 Upgrade the BootROM and PSU controller firmware--BlackDiamond 8800 series of switches only.
10 Upgrade the BootROM and PSU controller firmware--BlackDiamond 12804 series of switches only.
NOTE
If you have a dual MSM system, and the software image is not the same on both MSMs, see the section Dual MSM
Systems with Different Images Present on page 35.
Detailed Steps
NOTE
Extreme Networks recommends using a TFTP server that supports blocksize negotiation (per RFC-2348). Using this
type of server enables the switch to download the images faster.
To upgrade to ExtremeXOS on your system, follow these steps:
1 Download the image to your TFTP server.
Download the image you received from Extreme Networks to your TFTP server.
2 Verify which virtual router connects to your TFTP server.
26
ExtremeXOS 12.2.2 Installation and Release Notes
Upgrading to ExtremeXOS
Use the following ping commands to test which virtual router you will need to specify when you
download the image to your switch. This example assumes that your TFTP servers IP address is
192.168.0.12; substitute your own address when you run the command:
ping vr vr-mgmt 192.168.0.12
ping vr vr-default 192.168.0.12
At least one of these commands must successfully reach your TFTP server for you to download the
image. When you download the image in step 5, specify the virtual router that allowed you to reach
your TFTP server.
3 Save your configuration to a backup configuration file.
You must save your configuration to a backup configuration file, or you will be unable to revert to
your currently running image, if the need arises. In this example, we use the software version
number as part of the name. Use the following command to save the configuration to the file
version11_6_1_7.cfg:
save configuration version11_6_1_7
As an optional, extra precaution, we suggest that you save this configuration to a TFTP server. Use
the tftp command to save your configuration. In the following example, the TFTP servers IP
address is 192.168.0.12, the virtual router determined in step 2 is vr-mgmt, and the configuration file
is version11_6_1_7.cfg:
tftp 192.168.0.12 -v vr-mgmt -p -l version11_6_1_7.cfg
4 Determine your selected and booted image partitions.
Run the show switch command to determine your current selected and booted image partitions.
The selected image partition indicates which image will be used at the next reboot. The booted
image partition indicates which image was used at the last reboot.
Output from this command includes the version of the selected and booted images and if they are in
the primary or the secondary partition. In this example, the selected and booted images are in the
primary partition.
...
Image Selected:
Image Booted:
Primary ver:
Secondary ver:
primary
primary
11.6.1.7
11.6.1.7
Config Selected:
Config Booted:
primary.cfg
primary.cfg
5 Download and install the image to the switch.
Download and install the image to the switch using the download image command. The image will
be installed to the inactive image partition by default via the download image command. However,
you may also specify the inactive image partition by including primary or secondary as part of the
download image command. The virtual router <vr> that you will use is the one you determined in
step 2. This example assumes that you are using virtual router vr-mgmt and TFTP server
192.168.0.12. Substitute your own virtual router and IP address when you run the command.
download image 192.168.0.12 BD8800-12.2.2.xos vr vr-m <primary> or <secondary>
6 Reboot the switch.
Use the reboot command to reboot the switch.
ExtremeXOS 12.2.2 Installation and Release Notes
27
Upgrading to ExtremeXOS
NOTE
For the BlackDiamond 8800 series of switchesYou will be prompted to upgrade the BootROM on the
BlackDiamond 8800 series of switches when installing the ExtremeXOS image. If you answer "y" for yes after the
prompt and install the image after downloading, you will also be prompted to install the new BootROM during
the installation process before the switch reboots.
7 Save the configuration for the new image.
Even though your configuration was saved before you rebooted, you will need to save the
configuration with the new image. If you wait to login for some time after the reboot, you will
receive a notice that recommends that you save the configuration. If you login soon after the reboot,
you will not receive the notice, although an asterisk (*) will appear before the command prompt,
indicating that the current configuration is not saved. In either case, save the configuration with the
command:
save configuration
8 Upgrade the BootROMBlackDiamond 10808 switch only.
Extreme Networks recommends that you upgrade to the latest BootROM for the
BlackDiamond 10808. While not strictly required for this release, it is highly recommended. Run the
show version command to verify the BootROM version currently running on your switch. If you
are not running BootROM version 1.0.1.5 or later, upgrade the BootROM using the following
command:
download bootrom 192.168.0.12 bd10k-1.0.1.5-bootrom.xbr
This example assumes that you will use the same TFTP server and virtual router as in step 6 above.
You will be asked if you want to install the BootROM after downloading. Answer yes, or use the
install bootrom command to install later. Once the BootROM is downloaded and installed, it
replaces the previous image stored in the onboard FLASH memory, and will be used at the next
reboot.
9 Upgrade the BootROM and PSU controller firmware--BlackDiamond 8800 series of switches only.
NOTE
BootROMs installed by Manufacturing should never be forced to an earlier BootROM version unless explicitly
instructed by Extreme Networks support.
Extreme Networks requires that you upgrade the MSMs, I/O modules, and PSU controllers in the
BlackDiamond 8800 series of switches with the BootROM and firmware images included in this
release of ExtremeXOS.
This release of ExtremeXOS contains the following versions of the BootROM and firmware:
MSM BootROM
1.0.3.8
First available in ExtremeXOS 12.2.1
I/O module BootROM
1.0.3.7
First available in ExtremeXOS 12.1.1.4
PSU controller firmware
2.13
First available in ExtremeXOS 11.4.1.4
Use the show version command to display the versions of the BootROM and firmware currently
installed.
To install the new BootROM and firmware, wait until the show slot command indicates the MSMs
and I/O modules are operational. Then use the install firmware command. This command will
install the new BootROMs or firmware only on modules that have older BootROMs or firmware
installed. You will be asked if you want to install each type of BootROM or firmware. New PSU
28
ExtremeXOS 12.2.2 Installation and Release Notes
Upgrading to ExtremeXOS
controller firmware is used immediately after it is installed without rebooting the switch. The new
BootROM and firmware overwrite the older versions stored in FLASH memory.
BD-8806.2 # install firmware
Installing version 1.0.1.11 of the MSM bootrom(s). Do you want to continue?
(y - yes, n - no, <cr> - cancel) Yes
Do you want to save configuration changes to primary.cfg? (y or n) Yes
Saving configuration on primary MSM ....... done!
Installing version 1.0.1.11 of the IO module bootrom(s). Do you want to continue?
(y - yes, n - no, <cr> - cancel) Yes
Installing version 2.13 of the PSU control module firmware. Do you want to
continue?
(y - yes, n - no, <cr> - cancel) Yes
Installing bootrom...
MSM bootrom(s) installed successfully
MSM bootrom(s) will be activated upon next MSM reboot
Installing bootrom...
IO module bootrom(s) installed successfully
IO module bootrom(s) will be activated upon next IO module reboot
Installing firmware...
PSU controller firmware installed successfully
BD-8806.3 #
10 Upgrade the BootROM and PSU controller firmware--BlackDiamond 12804 series of switches only.
NOTE
BootROMs installed by Manufacturing should never be forced to an earlier BootROM version unless explicitly
instructed by Extreme Networks support.
Extreme Networks requires that you upgrade the MSMs, I/O modules, and PSU controllers in the
BlackDiamond 12804 with the BootROM and firmware images included in this release of
ExtremeXOS.
This release of ExtremeXOS contains the following versions of the BootROM and firmware:
MSM Bootloader
1.0.0.3
First available in ExtremeXOS 11.4.1.4
PSU controller firmware
2.13
First available in ExtremeXOS 11.4.1.4
Use the show version command to display the versions of the BootROM and firmware currently
installed.
NOTE
For single MSM systems, reboot the switch using the reboot command after the firmware installation is complete.
To install the new BootROM and firmware, wait until the show slot command indicates the MSMs
and I/O modules are operational. Then use the install firmware command. This command will
install the BootROMs and/or firmware only on modules that have older BootROMs or firmware
installed. Once this installation is complete, reboot the switch using the reboot command.
NOTE
For dual MSM systems, the install firmware command cannot install all the necessary software while the MSM
is primary. To completely install the firmware, an MSM failover is required. First, run the install firmware
ExtremeXOS 12.2.2 Installation and Release Notes
29
Upgrading to ExtremeXOS
command on the primary MSM. When the installation is complete, run the run msm-failover command to allow
the switch to failover to the secondary MSM. Run the install firmware command on the new primary MSM. To
revert back to your original primary MSM, run the run msm-failover command. Because two failovers are
required for a dual-MSM firmware installation, you will not need to run the reboot command after executing the
install firmware procedure.
NOTE
Upgrading a BlackDiamond 12804 slot can take a minimum of six minutes per slot.
BD-12804.7 # install firmware
Installing version 1.0.0.2 of the MSM bootrom(s). Do you want to continue?
(y - yes, n - no, <cr> - cancel) Yes
Installing IO module firmware, a reboot is required. Do you want to continue?
(y - yes, n - no, <cr> - cancel) Yes
Installing version 2.13 of the PSU control module firmware. Do you want to
continue?
(y - yes, n - no, <cr> - cancel) Yes
Installing micro controller image on backup MSM requires rebooting backup MSM. Do
you want to continue?
(y - yes, n - no, <cr> - cancel) Yes
Installing bootrom...
Installing bootstrap
Installing active bootrom
Installing system FPGA image
Installing bootstrap
Installing active bootrom
Installing system FPGA image
MSM bootrom(s) installed successfully
MSM bootrom(s) will be activated upon next MSM reboot
Installing bootrom...
Installing microcontroller firmware to slot 1 ...
Installing FGPA firmware to slot 1. This will takes a
Installing microcontroller firmware to slot 2 ...
Installing FGPA firmware to slot 2. This will takes a
Installing microcontroller firmware to slot 5 ...
Installing FGPA firmware to slot 5. This will takes a
Installing microcontroller firmware to slot 6 ...
Installing FGPA firmware to slot 6. This will takes a
few minutes...
few minutes...
few minutes...
few minutes...
To verify that your firmware upgrade on both the MSM and I/O modules has been successful, verify
using the following command:
show version detail
BD-12804.1 # show version detail
Chassis
: 804030-00-05 07085-00026 Rev 5.0
Slot-1
: 804031-00-05 0706F-00200 Rev 5.0 uC: 5.00 FPGA: 5.0d
Slot-2
: 804031-00-05 0703F-00184 Rev 5.0 uC: 5.00 FPGA: 5.0d
Slot-5
: 804031-00-05 0703F-00185 Rev 5.0 uC: 5.00 FPGA: 5.0d
Slot-6
:
MSM-A : 804046-00-07 0706F-00117 Rev 7.0 BootROM: 1.0.0.3 IMG: 12.2.2 uC: 5.00
FPGA: 3.30
MSM-B
: 804046-00-07 0706F-00122 Rev 7.0 BootROM: 1.0.0.3
IMG: 12.2.2
uC: 5.00
30
ExtremeXOS 12.2.2 Installation and Release Notes
Upgrading to ExtremeXOS
PSUCTRL-1 : 700111-00-01 06525-00997 Rev 1.0 BootROM: 2.13
PSUCTRL-2 : 700111-00-01 06525-00909 Rev 1.0 BootROM: 2.13
PSU-1
: PS 2336 4300-00145 0641K-22897 Rev 1.0
PSU-2
: PS 2336 4300-00145 0641K-23307 Rev 1.0
PSU-3
: PS 2336 4300-00145 0641K-23266 Rev 1.0
PSU-4
:
PSU-5
:
PSU-6
:
Image
: ExtremeXOS version 12.2.2 v1202b25 by release-manager
on Tue Nov 6 22:56:10 PST 2007
BootROM : 1.0.0.3
BD-12804.2 #
Following is an example of the old FPGA version:
MSM = 3.2a
I/O = 5.07 or earlier
Following is an example of the new FPGA version:
MSM= 3.30
I/O = 5.0d
The backup MSM version is not shown until the MSM is made the primary MSM.
Upgrading ExtremeXOS on Summit Family Switches
Upgrade ExtremeXOS on Summit family switches to ExtremeXOS 12.2.2 as follows:
1 Save your configuration to a backup configuration file using the save configuration
<configuration_file_name> command.
You must save your configuration to a backup configuration file in order to revert to your currently
running image if the need arises.
2 Run the show version command to verify the BootROM version currently running on your switch.
If you are not running BootROM version 1.0.5.5, upgrade the BootROM using the following
command:
download bootrom <tftp server ipaddress> pmon_summit-1.0.5.5.xtr vr <vrname>
3 Determine your current active image partition by running the show switch command. The Image
Booted field shows the current active partition.
4 Download the ExtremeXOS 12.2.2 image to the alternate partition using the following command:
download image <ipaddress> <filename> vr <vrname> <image partition>
For example, if your current image is running in the primary partition, download the new image in
the secondary partition:
download image 10.60.116.11 summitX-12.2.2.xos vr vr-mgmt secondary
5 Run the show switch command again to determine that the image is downloaded into the partition
you have specified.
6 Reboot the switch.
Use the reboot command to reboot the switch.
7 When the switch comes up, run the save configuration command to save the configuration in the
upgraded image.
ExtremeXOS 12.2.2 Installation and Release Notes
31
Upgrading to ExtremeXOS
Upgrading an MSM-5 and MSM-5R to ExtremeXOS 12.2.2 on a
BlackDiamond 12802
Upgrade the MSM-5 or MSM-5R to ExtremeXOS 12.2.2 as follows:
1 From the Extreme Networks eSupport website, download the ExtremeXOS 12.2.2 FCS image to your
TFTP server.
When powered up, the BlackDiamond 12802 comes up as a BlackDiamond 12804. An error is
displayed on the console and in the logs similar to the following:
Running Image ...
ohdGetChassisInfo: Incorrect Chassis type found, defaulting to BIATHLON
ohd_init_hw: Error determining chassis info
Starting Extremeware XOS 11.4.3b4
Copyright (C) 1996-2006 Extreme Networks.
All rights reserved.
Protected by US Patent Nos: 6,678,248; 6,104,700; 6,766,482; 6,618,388; 6,034,957;
6,859,438; 6,912,592; 6,954,436.
Error: Failed to connect CLI for 16 seconds!
login: admin
password:
ExtremeWare XOS
Copyright (C) 2000-2006 Extreme Networks. All rights reserved.
Protected by US Patent Nos: 6,678,248; 6,104,700; 6,766,482; 6,618,388; 6,034,957;
6,859,438; 6,912,592; 6,954,436.
========================================================================= BD12804.1 # show log
05/02/2007 00:27:10.81 <Info:HAL.Card.Info> MSM-A: Module in MSM-A is operational
05/02/2007 00:27:10.39 <Info:AAA.authPass> MSM-A: Login passed for user admin
through serial
05/02/2007 00:27:07.75 <Erro:Kern.Error> MSM-A: ohd_eeprom_read: Error reading
eeprom for slot 15 at offset 0
05/02/2007 00:27:07.75 <Erro:Kern.Error> MSM-A: ohd_eeprom_read: Error reading
eeprom for slot 15 at offset 0
05/02/2007 00:27:07.75 <Erro:Kern.Error> MSM-A: ohd_eeprom_access: Error accessing
device -1
2 Use the management VLAN virtual router to connect to your TFTP server by configuring an IP
address on the management VLAN using the following command:
configure mgmt ipaddress 192.168.1.134/24
Enter a default gateway using the following command:
configure iproute add default 10.201.1.1 vr VR-Mgmt
NOTE
The default VLAN has no ports because it does not recognize the chassis.
32
ExtremeXOS 12.2.2 Installation and Release Notes
Upgrading to ExtremeXOS
3 Test which virtual router you will need to specify when you download the image to your switch by
using the following command and your own IP address:
ping vr vr-mgmt 192.168.0.12
This command must successfully reach your TFTP server in order to download the image.
4 Download and install the image to the switch using the following command:
download image 192.168.0.12 bd12k-12.2.2.xos vr vr-mgmt
5 When the switch returns the following message:
Do you want to install image after downloading ? (yyes, nno, <cr>cancel)
Answer y to install the image after downloading.
6 Use the reboot command to reboot the switch.
7 Run the show switch command. Verify that the SysName and System Type read BD-12802, and that
the image is specified as 12.2.2.
SysName:
SysLocation:
SysContact:
System MAC:
System Type:
BD-12802
SysHealth check:
Recovery Mode:
System Watchdog:
Enabled (Normal)
All
Enabled
Current Time:
Timezone:
Boot Time:
Boot Count:
Next Reboot:
System UpTime:
Thu May 3 11:31:07 2007
[Auto DST Disabled] GMT Offset: 0 minutes, name is UTC.
Thu May 3 11:26:38 2007
11
None scheduled
4 minutes 29 seconds
Slot:
Current State:
MSM-A *
-----------------------MASTER
Image Selected:
Image Booted:
Primary ver:
Secondary ver:
secondary
secondary
12.0.0.13
12.2.2
Config Selected:
Config Booted:
NONE
Factory Default
[email protected], +1 888 257 3000
00:04:96:31:A2:40
BD-12802
Upgrading a BlackDiamond Series of Switches Using Hitless
Upgrade
NOTE
You must be running ExtremeXOS 11.1.1.9 or later to use hitless upgrade on a BlackDiamond 10808 switch.
ExtremeXOS 12.2.2 Installation and Release Notes
33
Upgrading to ExtremeXOS
NOTE
For the BlackDiamond 8800 series of switches, a hitless upgrade to ExtremeXOS 12.2.2 from an earlier release is
not supported and should not be attempted. Use the normal software upgrade process for these switches.
Upgrading the Alternate Partition Using Hitless Upgrade
Performing a hitless upgrade on the alternate partition allows you to revert to the previous image in
case the upgrade is not successful. Upgrade the alternate partition using hitless upgrade as follows:
1
Run the show switch command to determine which partition is the active partition and which
partition is the alternate partition.
2 In the following example, the secondary image is the active partition. The download is performed on
the primary image.
Execute the CLI command download image 10.201.14.13 bd12k-12.2.2.xos primary
* BD-12804.8 # download image 10.201.13.14 bd12k-12.2.2.xos primary
Do you want to install image after downloading? (y - yes, n - no, <cr> - cancel)
Yes
3 When the download is complete, run the show switch command to confirm the new image
downloaded to the primary image.
4 Verify the following before rebooting the backup MSM:
Primary ver: is the image to be downloaded.
Image Selected is set to primary.
MSM:
MSM-A *
MSM-B
------------------------------------Current State:
Image Selected:
Image Booted:
Primary ver:
Secondary ver:
MASTER
primary
secondary
12.2.1
11.4.1.4
BACKUP (In Sync)
primary
secondary
12.2.1
11.4.1.4
5 Run the reboot command to reboot MSM-B only.
reboot msm b
6 Run the show switch command to verify that:
MSM-B is (In Sync) mode.
Image Selected and Image Booted are both set for primary on the backup MSM.
MSM:
MSM-A *
MSM-B
------------------------------------Current State:
Image Selected:
Image Booted:
Primary ver:
Secondary ver:
MASTER
primary
secondary
12.2.1
11.4.1.4
BACKUP (In Sync)
primary
primary
12.2.1
11.4.1.4
7 Execute the run msm-failover command from the master MSM (MSM-A).
8 MSM-B becomes the master MSM, and MSM-A will reboot.
34
ExtremeXOS 12.2.2 Installation and Release Notes
Upgrading to ExtremeXOS
9 Run the show switch command to:.
Verify that MSM-B is the master MSM and MSM-A is the backup MSM and displays (In Sync).
Verify that Image Selected and Image Booted are set for primary on both MSMs.
MSM:
MSM-A
MSM-B *
------------------------------------Current State:
Image Selected:
Image Booted:
BACKUP (In Sync)
primary
primary
MASTER
primary
primary
10 Run the run msm-failover command again so that MSM-A becomes the master MSM.
11 Run the show switch command to confirm the master MSM is now MSM-A.
MSM:
MSM-A *
MSM-B
------------------------------------Current State:
Image Selected:
Image Booted:
Primary ver:
Secondary ver:
MASTER
primary
primary
12.2.1
11.4.1.4
BACKUP (In Sync)
primary
primary
12.2.1
11.4.1.4
Dual MSM Systems with Different Images Present
If you have a dual MSM system that has different images on the MSMs, you will need to modify the
upgrade procedure. One situation where you might have different images installed is when you add an
MSM that has been in storage to your chassis, either for the first time, or as a replacement. You will
only need to do the following procedure if one of the MSMs is running an image earlier than 11.0.0, and
the images are different on the two MSMs (earlier versions of the software are unable to automatically
synch up the configurations).
Follow the directions for upgrading the switch, and continue with step 5. When you download the
image, as described in step 5, Download and install the image to the switch., you will be asked:
Do you want to install image after downloading ? (yyes, nno, <cr>cancel)
Answer n, for no, so that the image will not be installed after downloading.
Next, manually install the image, using the following command:
install image bd10k-12.2.2.xos
Now the two MSMs have the same image installed, but may not have the same configurations. Reboot
the secondary MSM using one of the following commands:
reboot msm b (if you are running on MSM A)
reboot msm a (if you are running on MSM B)
Finally, save the configuration on both MSMs by using the command:
save configuration
ExtremeXOS 12.2.2 Installation and Release Notes
35
Upgrading to ExtremeXOS
Using a Rev 10 (or later) BlackDiamond 10808 MSM-1 or
MSM-1XL
NOTE
To use a Rev 10 (or later) MSM-1 or MSM-1XL module, you must upgrade both the active and alternate
images with the latest ExtremeWare 11.1.3 (or later) software image.
To determine which version of MSM you have installed in your switch, use the show version
command.
If you have a Rev 9 (or earlier) MSM, the show version command output will look like this:
MSM-A :804015-00-09 0414F-00728 Rev 9.0 BootROM: 1.0.1.5 IMG:
If you have a Rev 10 (or later) MSM, the show version command output will look like this:
MSM-A :804407-00-10 0505F-00429 Rev 10.0 BootROM: 1.0.1.5 IMG:
Complete show version command output with Rev 10 MSMs will look like this:
BD-10808.2 #
BD-10808.2 # show version
Chassis
: 804300-00-03 0324X-00026 Rev 3.0
MSM-A
: 804407-00-10 0505F-00429 Rev 10.0 BootROM: 1.0.1.5 IMG:
MSM-B
: 804407-00-10 0505F-00431 Rev 10.0 BootROM: 1.0.1.5 IMG:
Image
: ExtremeXOS version 11.1.3.3 v11133 by release-manager on Thu Mar 31
19:12:57 PST 2005
BootROM : 1.0.1.7
BD-10808.3 #
Installing an ExtremeXOS Module
An ExtremeXOS module has functionality that supplements a core image. You will download and
install a module onto an already installed core image. The version number of the core image and the
module must match. For example, the module bd10k-12.2.2-ssh.xmod can only be installed onto the core
image bd10k-12.2.2.xos.
You can download and install the SSH module.
NOTE
You must terminate and restart the thttpd process before you can use SSL.
Assuming that you have an installed and running ExtremeXOS 12.2.2 software on the active partition,
follow these steps to install the module:
1 Download the module image to your TFTP server.
Download the image you received from Extreme Networks to your TFTP server.
36
ExtremeXOS 12.2.2 Installation and Release Notes
Upgrading to ExtremeXOS
2 Determine the active partition for your switch.
Run the show switch command to determine your current selected and booted image partitions.
The booted image partition indicates the currently active partition.
3 Download and install the module image to the active partition.
Download the image to the switch using the download image command. The filename for the only
available module image is bd10k-12.2.2-ssh.xmod.
The virtual router <vr> that you will use is the one that connects to your TFTP server (you
determined this in step 2, Verify which virtual router connects to your TFTP server. in the upgrade
procedure). Since the system virtual router names changed from release 10.1.2.17 to 11.2.3.3, the
name will be different from that used to download the initial upgrade image. Use vr-mgmt for this
step or vr-default.
This example assumes that you are using virtual router vr-mgmt and TFTP server 192.168.0.12,
substitute your own virtual router and IP address when you run the command:
download image 192.168.0.12 bd10k-12.2.2-ssh.xmod vr vr-mgmt <partition> (primary
or secondary)
You will be asked:
Do you want to install image after downloading? (y - yes, n - no, <cr> - cancel)
Answer y, for yes, so that the image will be installed after downloading.
4 Run the run update command.
Run the following command:
run update
The run update command starts up the processes associated with the new module, and makes them
available to the system. You should now be able to run the commands associated with SSH2.
You can verify that the SSH2 module is running by issuing the following command:
show process
If SSH2 is running, you will see a process named exsshd listed. You can then configure and enable
SSH2 on the switch.
You can also verify that the SSH2 module is installed by issuing the following command:
show management
If the SSH module is installed, you will see text similar to the following:
SSH access : Disabled (Key invalid, tcp port 22 vr all)
If the SSH module is not installed, you will see text similar to the following:
SSH Access : ssh module not loaded.
Uninstalling an SSH Module
To uninstall the SSH module you must first terminate the THTTPD process:
1 Run the terminate process thttpd graceful command. This terminates the THTTPD process.
2 Run the uninstall image bd10k-12.2.2-ssh.xmod <partition> (primary or secondary)
command. This uninstalls SSH from your switch.
3 Restart the thttpd process using the start process thttpd command.
ExtremeXOS 12.2.2 Installation and Release Notes
37
Upgrading to ExtremeXOS
Downgrading Switches
Following are the instructions for downgrading your ExtremeXOS version 12.2.2 installation to a
previous version. It is assumed that you saved your configuration using the 11.4.1 image, and that the
11.4.1 image is currently installed on the switch, on the non-booted partition.
NOTE
Do not downgrade a BlackDiamond 8810 switch to an image earlier than 11.1.1 or a Summit X450 switch to an
image earlier than 11.2.1. Do not downgrade a BlackDiamond 8806 switch to an image earlier than 11.3.1.3. Do
not downgrade a Summit X450a or X450e switch to an ExtremeXOS image earlier than 11.5.1.
To downgrade to the existing ExtremeXOS version 11.4.1 image on your system, you will be following
these steps:
1 Determine your selected and booted image partitions.
Run the show switch command to determine your current selected and booted image partitions.
The selected image partition indicates which image will be used at the next reboot. The booted
image partition indicates which image was used at the last reboot.
Output from this command includes the version of the selected and booted images and if they are in
the primary or the secondary partition. In this example, the selected and booted images are in the
secondary partition.
...
Image Selected:
Image Booted:
Primary ver:
Secondary ver:
secondary
secondary
11.4.1.4
12.2.2
Config Selected:
Config Booted:
primary.cfg
primary.cfg
2 Select the reboot partition.
Assuming that the 11.4.1 image is on the non-booted partition, if you are currently running the
image booted from the primary partition, run this command:
use image secondary
If you are currently running the image booted from the secondary partition, run this command:
use image primary
3 Select the reboot configuration.
Select the configuration to be used after reboot with the use configuration command. Assuming
you saved the 11.4.1 configuration as bdversion11_4_1_4.cfg, use the following command:
use configuration bdversion11_4_1_4
4 Verify the image and configuration selection.
Again, run the show switch command. The output should show that the selected image is the 11.4.1
image that you are downgrading to, and the selected configuration is the one you saved before you
installed the 12.2.2 image:
...
Image Selected:
Image Booted:
Primary ver:
Secondary ver:
38
primary
secondary
11.4.1.4
12.2.2
ExtremeXOS 12.2.2 Installation and Release Notes
Upgrading to ExtremeXOS
Config Selected:
Config Booted:
...
bdversion11_4_1_4.cfg
primary.cfg
5 Reboot the switch.
Use the command reboot to reboot the switch.
ExtremeXOS 12.2.2 Installation and Release Notes
39
Upgrading to ExtremeXOS
40
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
This chapter summarizes the supported limits in ExtremeXOS 12.2.2.
Supported Limits
Table 35 summarizes tested metrics for a variety of features, as measured in a per-system basis unless
otherwise noted. These limits may change but represent the current status. The contents of this table
supersede any values mentioned in the ExtremeXOS Concepts Guide.
NOTE
The scaling and performance information shown in Table 35 is provided for the purpose of assisting with network
design. It is recommended that network architects and administrators design and manage networks with an
appropriate level of network scaling head room. The scaling and performance figures provided have been verified
using specific network topologies using limited switch configurations. There is no guarantee that the scaling and
performance figures shown are applicable to all network topologies and switch configurations and are provided as a
realistic estimation only. If you experience scaling and performance characteristics that you feel are sufficiently
below what has been documented, contact Extreme Networks technical support for additional assistance.
NOTE
The route limits shown in Table 35 for IPv4 and IPv6 routing protocols are software limits only. The actual hardware
limits may be lower than the software limits, based on platform. The hardware limits for specific platforms are
specified as "IPv4/IPv6 routes (LPM entries in hardware)" in the following table.
NOTE
On a BlackDiamond 8800 or a Summit X650, X450, or X250e switch, it is not advised to have greater than 25,000
total IP routes from all routing protocols. Adverse effects can occur with routing tables larger than this, especially
when a single network event or CLI command affects a significant number of routes. For example, just after such a
network event, the added system load will cause a save configuration command to time out.
Table 35: Supported Limits
Metric
Product
Limit
Access lists (policies)suggested maximum
number of lines in a single policy file.
BlackDiamond 10808
300,000
BlackDiamond 12800 series
300,000
ExtremeXOS 12.2.2 Installation and Release Notes
41
Limits
Metric
Product
Limit
Access lists (policies)maximum number of
rules in a single policy file.a
BlackDiamond 8800 series
Original series modules
(per GigE port)
(per 10 GigE port)
128
1,016
a-series modules
2,048
c-series modules
4,096
e-series modules
1,024
BlackDiamond 10808
30,000
Summit X150 and X350 series
1,024
Summit X250e
per port groups 1-24 and 25-48
1,024
Summit X450
(per GigE port)
(per 10 GigE port)
128
1,016
Summit X450a
per port groups 1-24 and 25-48
2,048
Summit X450e
per port groups 1-24 and 25-48
1,024
Summit X650-24x (with VIM1SummitStack)
per port groups 1-12 and 13-28
2,048
Summit X650-24x (with VIM1-10G8X)
per port groups 1-12, 13-24 and 25-32
2,048
Summit X650-24t (with VIM1SummitStack)
per port groups (1,3,...23,25,26,27,28)
and (2,4...24)
2,048
Summit X650-24t (with VIM1-10G8X)
per port groups (1,3,...23), (2,4...24)
and 25-32
Access lists (masks)maximum number of ACL
masks per port.b
42
2,048
BlackDiamond 8800 original series
16
Summit X450
16
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Access lists (slices)maximum number of field
selectors for ACL slices.
BlackDiamond 8800 series
a-series and c-series modules
per port groups 1-12, 25-36 and 1324, 37-48
e-series modules
per port groups 1-12, 25-36 and 1324, 37-48
Summit X150 and X350 series
Limit
16
8
8
Summit X250e
per port groups 1-24 and 25-48
Summit X450a
per port groups 1-24 and 25-48
16
Summit X450e
per port groups 1-24 and 25-48
Summit X650-24x (with VIM1SummitStack)
per port groups 1-12 and 13-28
12
12
Summit X650-24x (with VIM1-10G8X)
per port groups 1-12, 13-24 and 25-32
12
Summit X650-24t (with VIM1SummitStack)
per port groups (1,3,...23,25,26,27,28)
and (2,4...24)
12
Summit X650-24t (with VIM1-10G8X)
per port groups (1,3,...23), (2,4...24)
and 25-32
12
ACL Static L2/L3maximum number of static
ACL L2 and L3 entries.
BlackDiamond 20808
8,000
ACL (rules)maximum number of ACL rules.
BlackDiamond 20808
31,700
AAA (local)maximum number of admin and
local user accounts.
All platforms
16
BGP (aggregates)maximum number of BGP
aggregates.
All platforms with Core license or above
256
BGP (networks)maximum number of BGP
networks.
All platforms with Core license or above
1,024
ExtremeXOS 12.2.2 Installation and Release Notes
43
Limits
Metric
Product
Limit
BGP (peers)maximum number of BGP peers.
BlackDiamond 8800 series
256*
BlackDiamond 10808
512
256
MSM-1XL
MSM-1
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
256
256*
512
Summit X450
128*
Summit X450a
128*
Summit X450e
128*
Summit X650
128*
* With default keepalive and hold timers.
BGP (peer groups)maximum number of BGP
peer groups.
All platforms with Core license or above
64
BGP (policy entries)maximum number of BGP
policy entries per route policy.
All platforms with Core license or above
256
BGP (policy statements)maximum number of
BGP policy statements per route policy.
All platforms with Core license or above
1,024
BGP (unicast address-family routes)maximum
number of unicast address-family routes (LPM
entries is limited to support TCAM entries on a
BlackDiamond 10808).
BlackDiamond 8800 series
25,000
BlackDiamond 10808
MSM-1XL
MSM-1
1,000,000
400,000
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
BGP (non-unique routes)maximum number of
non-unique BGP routes (LPM entries is limited
to support TCAM entries on a BlackDiamond
10808).
400,000
400,000
1,000,000
Summit X450
25,000
Summit X450a
25,000
Summit X450e
25,000
Summit X650
25,000
BlackDiamond 8800 series
25,000
BlackDiamond 10808
2,000,000
900,000
MSM-1XL
MSM-1
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
44
900,000
900,000
2,000,000
Summit X450
25,000
Summit X450a
25,000
Summit X450e
25,000
Summit X650
25,000
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
BGP multicast address-family routes maximum
number of multicast address-family routes.
BlackDiamond 8800 series
25,000
BlackDiamond 10808
MSM-1XL
MSM-1
1,000,000
450,000
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
450,000
450,000
1,000,000
Summit X450
25,000
Summit X450a
25,000
Summit X450e
25,000
Summit X650
25,000
BOOTP/DHCP relaymaximum number of BOOTP
or DHCP servers per virtual router.
All platforms
CLEAR-Flowtotal number of rules supported.
The ACL rules plus CLEAR-Flow rules must be
less than the total number of supported ACLs.
BlackDiamond 8800 c-series
4,096
Summit X450a
2,048
Summit X650
2,048
Connectivity Fault Management (CFM)maximum
number or CFM domains.
All platforms
CFMmaximum number of CFM associations.
All platforms
4,094
CFMmaximum number of CFM up end points.
All platforms
32
CFMmaximum number of CFM down end
points.
All platforms
32
CFMmaximum number of CFM remote end
points.
All platforms
64
CFMmaximum number of dot1ag ports.
All platforms
128
Dynamic ACLsmaximum number of ACLs
processed per second.
BlackDiamond 8800 with c-series MSM
and I/O modules
Note: Limits are load dependent.
BlackDiamond 12800 series
12
Note: CLEAR-Flow is not supported on e
series switches and is only supported in a nonstack configuration in the Summit family of
switches.
Summit X450a
with 50 DACLs
with 500 DACLs
10
5
Summit X650
with 50 DACLs
with 500 DACLs
EAPS domainsmaximum number of EAPS
domains.
Note: An EAPS ring that is being spatially
reused cannot have more than four configured
EAPS domains.
EAPSv1 protected VLANsmaximum number of
protected VLANs.
ExtremeXOS 12.2.2 Installation and Release Notes
10
5
BlackDiamond 8800 series
64
BlackDiamond 10808
128
BlackDiamond 12800 series
128
Summit series
32
BlackDiamond 8800 series
2,000
BlackDiamond 10808
4,000
BlackDiamond 12800 series
4,000
Summit series
1,000
45
Limits
Metric
Product
Limit
EAPSv2 protected VLANsmaximum number of
protected VLANs.
BlackDiamond 8800 series
1,000
BlackDiamond 10808
4,000
BlackDiamond 12800 series
4,000
Summit series
500
BlackDiamond 8800 series
5,000
BlackDiamond 10808
5,000
BlackDiamond 12800 series
5,000
ESRP groupsmaximum number of ESRP
groups.
All platforms
ESRP domainsmaximum number of ESRP
domains.
BlackDiamond 8800 series
64
BlackDiamond 10808
128
BlackDiamond 12800 series
64
Summit series
64
BlackDiamond 8800 series
1,000
BlackDiamond 10808
3,000
BlackDiamond 12800 series
3,000
Summit series
1,000
ESRP (maximum ping tracks)maximum number
of IP route tracks per VLAN.
All platforms
ESRP (IP route tracks)maximum IP route
tracks per VLAN.
All platforms
ESRP (VLAN tracks)maximum number of VLAN
tracks per VLAN.
All platforms
Forwarding ratemaximum L2/L3 software
forwarding rate.
BlackDiamond 8800 series
10,000 pps
BlackDiamond 12800 series
16,000 pps
Summit series
10,000 pps
BlackDiamond 8800 original series
16,000
BlackDiamond 8800 a-series
16,000
BlackDiamond 8800 e-series
8,000
Summit X450 original
16,000
Summit X450a
16,000
Summit X450e
8,000
Summit X650
32,000
BlackDiamond 8800 original series
256
BlackDiamond 8800 a-series
1,024
BlackDiamond 8800 e-series
1,024
Summit X450 original
256
Summit X450a
1,024
Summit X450e
1,024
Summit X650
1,024
BlackDiamond 10808
224,000
BlackDiamond 12800 series
49,000
BlackDiamond 12800 R-series
224,000
ELSM (vlan-ports)maximum number of VLANports.
ESRP VLANsmaximum number of ESRP
VLANs.
FDB (blackhole entries)maximum number of
unicast blackhole FDB entries.
FDB (blackhole entries)maximum number of
multicast blackhole FDB entries.
FDB (maximum L2/L3 entries)maximum number
of MAC addresses/IP host routes.
46
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
FDB (maximum L2 entries)maximum number of
MAC addresses.
BlackDiamond 8800 original
16,384
BlackDiamond 8800 a-series
16,384
BlackDiamond 8800 c-series
32,768
BlackDiamond 8800 e-series
8,192
BlackDiamond 8800 (system)
128,000
BlackDiamond 20808
400,000
Summit X150 and X350 series
8,192
Summit X250e
8,192
Summit X450
16,384
Summit X450a
16,384
Summit X450e
8,192
Summit X650
32,768
SummitStack
128,000
BlackDiamond 12800 R-series
4,076
Hierarchical QoSmaximum number of ingress
traffic queues with egress shaping allowed per
switch.
BlackDiamond 12800 R-series
4,076
Hierarchical QoSmaximum number of egressonly traffic queues allowed per switch.
BlackDiamond 12800 R-series
4,076
Hierarchical QoSmaximum number of traffic
queues attach per port.
BlackDiamond 12800 R-series
4,076
IGMP sendermaximum number of IGMP
senders per switch (IP multicast compression
disabled).
BlackDiamond 8800 original
1,024
BlackDiamond 8800 c-series
2,048c
BlackDiamond 8800 e-series
500
BlackDiamond 10808
15,000
BlackDiamond 12800 series
15,000
BlackDiamond 20808
3,700
Summit X150
500d
Summit X250e
500d
Summit X350
500d
Summit X450
1,024
Summit X450a
1,024
Summit X450e
500d
Summit X650
2,048
Hierarchical QoSmaximum number of ingressonly traffic queues per system.
(For 20XTR, first 10 ports ranges from 1 to 10
are UNIT-I, second 10 ports ranges from 11 to
20 are UNIT-II, for 10 Gig slot each port is one
UNIT.)
ExtremeXOS 12.2.2 Installation and Release Notes
47
Limits
Metric
Product
Limit
IGMP sendermaximum number of IGMP
senders per switch (IP multicast compression
enabled).
BlackDiamond 8800 original
2,000d
BlackDiamond 8800 a-series
2,000d
BlackDiamond 8800 c-series
6,000d
BlackDiamond 8800 e-series
500d
Summit X150
500d
Summit X250e
500d
Summit X350
500d
Summit X450
2,000d
Summit X450a
2,000d
Summit X450e
500d
Summit X650
6,000d
BlackDiamond 8800 original
60
BlackDiamond 8800 a-series
1,000
BlackDiamond 8800 c-series
2,000
BlackDiamond 8800 e-series
448
Summit X150
448
Summit X250e
448
Summit X350
448
Summit X450
60
Summit X450a
1,000
Summit X450e
448
IGMP snooping per VLAN filtersmaximum
number of VLANs supported in per-VLAN IGMP
snooping mode.
Summit X650
1,000
IGMPv1/v2 SSM-map entriesmaximum number
of IGMPv1/v2 SSM mapping entries.
All platforms
500
IGMPv1/v2 SSM-MAP entriesmaximum number
of sources per group in IGMPv1/v2 SSM
Mapping entries.
All platforms
50
IGMPv2 subscribermaximum number of
IGMPv2 subscribers per port.
BlackDiamond 8800 original
1,000
BlackDiamond 8800 c-series
2,000
BlackDiamond 10808
5,000
BlackDiamond 12800 series
5,000
Summit series except Summit X650
1,000
Summit X650
2,000
BlackDiamond 8800 original
10,000
BlackDiamond 8800 c-series
20,000
BlackDiamond 10808
30,000
BlackDiamond 12800 series
30,000
Summit series except Summit X650
10,000
Summit X650
20,000
All platforms
250
IGMPv2 subscribermaximum number of
IGMPv2 subscribers per switch.
IGMPv3 maximum source per groupmaximum
number of source addresses per group.
48
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
IGMPv3 subscribermaximum number of
IGMPv3 subscribers per port.
BlackDiamond 8800 original
1,000
BlackDiamond 8800 c-series
2,000
BlackDiamond 10808
5,000
BlackDiamond 12800 series
5,000
Summit series
1,000
BlackDiamond 8800 original
10,000
BlackDiamond 8800 c-series
20,000
BlackDiamond 10808
30,000
BlackDiamond 12800 series
30,000
IGMPv3 subscribermaximum number of
IGMPv3 subscribers per switch.
Summit series
10,000
IP ARP entries in softwaremaximum number of
IP ARP entries in software.
All platforms
20,480
IPv4 ARP entries in hardware with minimum LPM
routesmaximum recommended number of
IPv4 ARP entries in hardware, with minimum
LPM routes present. For BlackDiamond 8800
and Summit series switches, assumes number
of IP route reserved entries is 100 or less.
BlackDiamond 8800 original
2,000d
BlackDiamond 8800 a-series
8,000
BlackDiamond 8800 c-series
8,000
BlackDiamond 8800 e-series
1,000d
BlackDiamond 10808
224,000
BlackDiamond 12800 series
49,000
BlackDiamond 12800 R-series
224,000
BlackDiamond 20808
20,000
Summit X250e
1,000d
Summit X450
2,000d
Summit X450a
8,000
Summit X450e
1,000d
Summit X650
8,000
BlackDiamond 8800 original
2,000d
BlackDiamond 8800 a-series
2,000d
BlackDiamond 8800 c-series
6,000d
BlackDiamond 8800 e-series
500d
BlackDiamond 10808
224,000
BlackDiamond 12800 series
49,000
BlackDiamond 12800 R-series
224,000
Summit X250e
500d
Summit X450
2,000d
Summit X450a
2,000d
Summit X450e
500d
Summit X650
6,000d
IPv4 ARP entries in hardware with maximum LPM
routesmaximum recommended number of
IPv4 ARP entries in hardware, with maximum
LPM routes present. For BlackDiamond 8800
and Summit series, assumes number of IP
route reserved entries is maximum.
ExtremeXOS 12.2.2 Installation and Release Notes
49
Limits
Metric
Product
Limit
IPv4 remote hosts in hardware with zero LPM
routesmaximum recommended number of
IPv4 remote hosts (hosts reachable through a
gateway) in hardware when LPM routing is not
used. For BlackDiamond 8800 and Summit
series, assumes number of IP route reserved
entries is 0, and number of IPv4 ARP entries
present is 100 or less.
BlackDiamond 8800 original
N/A
BlackDiamond 8800 a-series
14,000d
BlackDiamond 8800 c-series
18,000d
BlackDiamond 8800 e-series
1,000d
BlackDiamond 10808
N/A
BlackDiamond 12800 series
N/A
BlackDiamond 12800 R-series
N/A
Summit X250e
1,000d
Summit X450
N/A
Summit X450a
14,000d
Summit X450e
1,000d
Summit X650
18,000d
BlackDiamond 8800 a-series
1,000d
BlackDiamond 8800 c-series
3,000d
BlackDiamond 8800 e-series
250d
BlackDiamond 10808
112,000
BlackDiamond 12800 series
24,500
BlackDiamond 12800 R-series
112,000
Summit X250e
250d
Summit X450a
1,000d
Summit X450e
250d
Summit X650
2,000d
BlackDiamond 8800 series
25,000
BlackDiamond 10808
1,000,000
BlackDiamond 12800 series
1,000,000
Summit series
25,000
BlackDiamond 8800 original
8,000
BlackDiamond 8800 a-series
12,000
BlackDiamond 8800 c-series
12,000
BlackDiamond 8800 e-series
480
BlackDiamond 10808
256,000
IPv6 host entries in hardwaremaximum number
of IPv6 neighbor entries in hardware.
IPv4 routesmaximum number of IPv4 routes
in software (combination of unicast and
multicast routes).
IPv4 routes (LPM entries in hardware) number
of IPv4 routes in hardware.
MSM-1
MSM-1XL
98,000
229,000
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
50
49,000
229,000
229,000
Summit X250e
480
Summit X450
8,000
Summit X450a
12,000
Summit X450e
480
Summit X650
12,000
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
IPv6 routes (LPM entries in hardware)number
of IPv6 routes in hardware.
BlackDiamond 8800 a-series
6,000
BlackDiamond 8800 c-series
6,000
BlackDiamond 8800 e-series
240
BlackDiamond 10808
114,500
BlackDiamond 12800 series
114,500
Summit X250e
240
Summit X450a
6,000
Summit X450e
240
Summit X650
6,000
IP router interfacesmaximum number of
VLANs performing IP routingexcludes sub
VLANs (IPv4 and IPv6 interfaces).
All platforms with Edge license or above
512
IP multicast static routesmaximum number of
permanent multicast IP routes.
All platforms
1,024
IP unicast static routesmaximum number of
permanent IP unicast routes.
All platforms
1,024
IP route sharing (maximum gateways)
configurable maximum number of configurable
gateways used by equal cost multipath OSPF,
OSPFv3, or static routes.
BlackDiamond 8800 series
2, 4, or 8
Summit X250e
2, 4, or 8
Summit X450
2, 4, or 8
Summit X450a
2, 4, or 8
Summit X450e
2, 4, or 8
Summit X650
2, 4, or 8
ExtremeXOS 12.2.2 Installation and Release Notes
51
Limits
Metric
Product
Limit
IP route sharing (total destinations)maximum
number of unique destinations used by
multipath OSPF, OSPFv3, or static routes.
BlackDiamond 8800 original
(default maximum gateways of 4)
(if maximum gateways is 2)
(if maximum gateways is 8)
511
1,023
255
BlackDiamond 8800 a-series
(default maximum gateways of 4)
(if maximum gateways is 2)
(if maximum gateways is 8)
511
1,023
255
BlackDiamond 8800 c-series
(default maximum gateways of 4)
(if maximum gateways is 2)
(if maximum gateways is 8)
511
1,023
255
BlackDiamond 8800 e-series
(default maximum gateways of 4)
(if maximum gateways is 2)
(if maximum gateways is 8)
31
63
15
BlackDiamond 10808
(with up to 8 gateways per destination)
7,136
BlackDiamond 12800 series
(with up to 8 gateways per destination)
7,136
Summit X250e
(default maximum gateways of 4)
(if maximum gateways is 2)
(if maximum gateways is 8)
31
63
15
Summit X450
(default maximum gateways of 4)
(if maximum gateways is 2)
(if maximum gateways is 8)
511
1,023
255
Summit X450a
(default maximum gateways of 4)
(if maximum gateways is 2)
(if maximum gateways is 8)
511
1,023
255
Summit X450e
(default maximum gateways of 4)
(if maximum gateways is 2)
(if maximum gateways is 8)
31
63
15
Summit X650
(default maximum gateways of 4)
(if maximum gateways is 2)
(if maximum gateways is 8)
IP multinetting (secondary IP addresses)
maximum number of secondary IP addresses
per VLAN.
52
All platforms
511
1,023
255
64
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
IS-IS adjacenciesmaximum number of
supported IS-IS adjacencies.
BlackDiamond 8800 series
128
Black Diamond 10808
255
BlackDiamond 12800 series
255
Summit X450
128
Summit X450a
128
Summit X650
128
BlackDiamond 8800 series (configurable)
2, 4, or 8
BlackDiamond 10808
BlackDiamond 12800 series
Summit X450 (configurable)
2, 4, or 8
Summit X450a (configurable)
2, 4, or 8
Summit X650 (configurable)
2, 4, or 8
IS-IS interfacesmaximum number of interfaces
that can support IS-IS.
All platforms
255
IS-IS routers in an arearecommended
maximum number of IS-IS routers in an area.
All platforms
256
IS-IS route originationrecommended maximum
number of routes that can be originated by an
IS-IS node.
BlackDiamond 8800 series
20,000
BlackDiamond 10808
30,000
BlackDiamond 12800 series
30,000
Summit X450
5,000
Summit X450a
5,000
Summit X650
20,000
BlackDiamond 8800 series
25,000
IS-IS ECMPmaximum number of equal cost
multipath for IS-IS.
IS-IS IPv4 L1 routes in an L1 router
recommended maximum number of IS-IS Level
1 routes in a Level 1 IS-IS router.
BlackDiamond 10808
MSM-1
MSM-1XL
120,000
180,000
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
IS-IS IPv4 L2 routesrecommended maximum
number of IS-IS Level 2 routes.
100,000
120,000
180,000
Summit X450
5,000
Summit X450a
5,000
Summit X650
25,000
BlackDiamond 8800 series
25,000
BlackDiamond 10808
MSM-1
MSM-1XL
120,000
180,000
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
ExtremeXOS 12.2.2 Installation and Release Notes
100,000
120,000
180,000
Summit X450
5,000
Summit X450a
5,000
Summit X650
25,000
53
Limits
Metric
Product
Limit
IS-IS IPv4 L1 routes in an L1/L2 router
recommended maximum number of IS-IS Level
1 routes in an L1/L2 IS-IS router.
BlackDiamond 8800 series
20,000
BlackDiamond 10808
20,000
25,000
MSM-1
MSM-1XL
BlackDiamond 12800 series
20,000
20,000
25,000
MSM-5
MSM-5R
MSM-6R
IS-IS IPv6 L1 routes in an L1 router
recommended maximum number of IS-IS Level
1 routes in a Level 1 IS-IS router.
Summit X450
3,000
Summit X450a
3,000
Summit X650
20,000
BlackDiamond 8800 series
10,000
BlackDiamond 10808
30,000
65,000
MSM-1
MSM-1XL
BlackDiamond 12800 series
30,000
40,000
65,000
MSM-5
MSM-5R
MSM-6R
IS-IS IPv6 L2 routesrecommended maximum
number of IS-IS Level 2 routes.
Summit X450
5,000
Summit X450a
5,000
Summit X650
10,000
BlackDiamond 8800 series
10,000
BlackDiamond 10808
30,000
65,000
MSM-1
MSM-1XL
BlackDiamond 12800 series
30,000
40,000
65,000
MSM-5
MSM-5R
MSM-6R
IS-IS IPv6 L1 routes in a L1/L2 router
recommended maximum number of IS-IS Level
1 routes in a L1/l2 router.
Summit X450
5,000
Summit X450a
5,000
Summit X650
10,000
BlackDiamond 8800 series
10,000
BlackDiamond 10808
15,000
25,000
MSM-1
MSM-1XL
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
54
15,000
15,000
25,000
Summit X450
3,000
Summit X450a
3,000
Summit X650
10,000
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
IS-IS IPv4/IPv6 L1 routes in an L1 router
recommended maximum number of IS-IS Level
1 routes in a Level 1 IS-IS router. The numbers
documented are based on 50% IPv4 routes and
50% IPv6 routes.
BlackDiamond 8800 series
20,000
BlackDiamond 10808
MSM-1
MSM-1XL
60,000
130,000
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
IS-IS IPv4/IPv6 L2 routes in an L2 router
recommended maximum number of IS-IS Level
2 routes in a Level 2 IS-IS router. The numbers
documented are based on 50% IPv4 routes and
50% IPv6 routes.
30,000
60,000
130,000
Summit X450
5,000
Summit X450a
5,000
Summit X650
20,000
BlackDiamond 8800 series
20,000
BlackDiamond 10808
MSM-1
MSM-1XL
60,000
130,000
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
IS-IS IPv4/IPv6 L1 routes in a L1/L2 router
recommended maximum number of IS-IS Level
1 routes in a Level 1/Level2 IS-IS router. The
numbers documented are based on 50% IPv4
routes and 50% IPv6 routes.
Jumbo framesmaximum size supported for
jumbo frames, including the CRC.
ExtremeXOS 12.2.2 Installation and Release Notes
30,000
60,000
130,000
Summit X450
5,000
Summit X450a
5,000
Summit X650
20,000
BlackDiamond 8800 series
20,000
BlackDiamond 10808
20,000
BlackDiamond 12800 series
20,000
Summit X450
3,000
Summit X450a
3,000
Summit X650
20,000
All platforms
9,216
55
Limits
Metric
Product
Load sharing groupsmaximum number of load
share groups.
BlackDiamond 8800 series
Note: The actual number of load share groups
that can be configured is limited by the number
of physical ports present in the switch or
SummitStack.
Limit
with 10G4X
without 10G4X
32
128
BlackDiamond 10808
128
BlackDiamond 12800 series
128
Summit X150 and X350 series
128
Summit X250e
128
Summit X450
32
Summit X450a
128
Summit X450e
128
Summit X650
128
SummitStack
Load sharingmaximum number of ports per
load share group.
56
with Summit X450-24t
32
with Summit X450-24x
32
without Summit X450-24t
128
without Summit X450-24x
128
BlackDiamond 8800 series
BlackDiamond 10808
16
BlackDiamond 12800 series
16
Summit series
Logged messagesmaximum number of
messages logged locally on the system.
All platforms
20,000
MAC-based securitymaximum number of MACbased security policies.
All platforms
1,024
MAC-in-MACmaximum number of MAC FDB
entries (MAC addresses on the local side) and
MAC binding entries (MAC addresses on remote
side).
BlackDiamond 10808
100,000
BlackDiamond 12800 series
100,000
BlackDiamond 20808
100,000
MAC-in-MACmaximum number of regular
VLANs (VLAN, vMAN, BVLAN).
BlackDiamond 10808
4,000
BlackDiamond 12800 series
4,000
MAC-in-MACmaximum number of SVLANs.
BlackDiamond 10808 (1G DRAM)
2,000
BlackDiamond 12800 series (512 DRAM)
2,000
Mirroring (filters)maximum number of
mirroring filters.
All platforms
16
Mirroring (monitor port)maximum number of
monitor ports.
All platforms
Mirroring, one-to-many (filters)maximum
number of one-to-many mirroring filters.
All platforms
16
Mirroring, one-to-many (monitor port)maximum
number of one-to-many monitor ports.
All platforms
16
MPLS LDP enabled interfacesmaximum number
of MPLS LDP configured interfaces per switch.
BlackDiamond 10808
32
BlackDiamond 12800 R-series
32
BlackDiamond 20808
32
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
MPLS LDP peersmaximum number of MPLS
LDP peers per switch.
BlackDiamond 10808
32
BlackDiamond 12800 R-series
32
BlackDiamond 20808
32
BlackDiamond 10808
50
BlackDiamond 12800 R-series
50
BlackDiamond 20808
50
BlackDiamond 10808*
40,000
BlackDiamond 12800 R-series*
30,000
BlackDiamond 20808
16,000
MPLS LDP adjacenciesmaximum number of
MPLS LDP adjacencies per switch.
MPLS LDP labelsmaximum number of MPLS
LDP labels per switch.
*It may take a long time to converge and populate the
labels in hardware.
MPLS static LSPsmaximum number of static
LSPs.
MSDP active peersmaximum number of active
MSDP peers.
MSDP SA cache entriesmaximum number of
entries in SA cache.
MSDP maximum mesh groupsmaximum number
of MSDP mesh groups.
Multicast VLAN registration (MVR)maximum
number of senders per switch.
Network Loginmaximum number of clients
being authenticated on MAC-based VLAN
enabled ports.
ExtremeXOS 12.2.2 Installation and Release Notes
BlackDiamond 10808
1,000
BlackDiamond 12800 R-series
1,000
BlackDiamond 20808
100
BlackDiamond 8800 series
32
BlackDiamond 10808
32
BlackDiamond 12800 series
32
Summit X450
16
Summit X650
16
BlackDiamond 8800 series
16,000
BlackDiamond 10808
16,000
BlackDiamond 12800 series
16,000
Summit X450
8,000
Summit X650
8,000
BlackDiamond 8800 series
BlackDiamond 10808
BlackDiamond 12800 series
Summit X450
Summit X650
BlackDiamond 8800 series
1,024
BlackDiamond 8800 c-series
2,048
BlackDiamond 10808
15,000
BlackDiamond 12800 series
15,000
BlackDiamond 20808
3,700
Summit series
1,024
BlackDiamond 8800 series (clients per
module/per system)
1,024
BlackDiamond 12804 (per system)
4,000
Summit X150
1,024
Summit X250e (per system)
1,024
Summit X350
1,024
Summit X450 (per system)
1,024
Summit X650 (per system)
1,024
57
Limits
Metric
Product
Limit
Network Loginmaximum number of dynamic
VLANs.
All platforms
2,000
OSPF adjacenciesmaximum number of
supported OSPF adjacencies.
BlackDiamond 8800 series
128
BlackDiamond 10808
255
BlackDiamond 12800 series
255
BlackDiamond 20808
255
Summit X250e
128
Summit X450
128
Summit X650
128
OSPF areasas an ABR, how many OSPF areas
are supported within the same switch.
All platforms
OSPF ECMPmaximum number of equal cost
multipath OSPF.
BlackDiamond 8800 series (configurable)
2, 4, or 8
BlackDiamond 10808
BlackDiamond 12800 series
BlackDiamond 20808
16
Summit X250e (configurable)
2, 4, or 8
Summit X450 (configurable)
2, 4, or 8
Summit X650 (configurable)
2, 4, or 8
BlackDiamond 8800 series
20,000
BlackDiamond 10808
130,000
BlackDiamond 12800 series
130,000
BlackDiamond 20808
130,000
Summit X250e
5,000
Summit X450
5,000
Summit X650
5,000
BlackDiamond 8800 series
7,000
BlackDiamond 10808
7,000
BlackDiamond 12800 series
7,000
BlackDiamond 20808
7,000
Summit X250e
2,000
Summit X450
2,000
Summit X650
2,000
BlackDiamond 8800 series
100
BlackDiamond 10808
200
BlackDiamond 12800 series
100
BlackDiamond 20808
200
Summit X250e
50
Summit X450
50
Summit X650
50
All platforms with Core license or above
400
OSPF external routesrecommended maximum
number of external routes contained in an OSPF
LSDB without too many other types of OSPF
routes.
OSPF inter- or intra-area routesrecommended
maximum number of inter- or intra-area routes
contained in an OSPF LSDB without too many
other types of OSPF routes, with one ABR in
OSPF domain.
OSPF routers in a single arearecommended
maximum number of routers in a single OSPF
area.
OSPF subnets on a single routerrecommended
maximum number of OSPF routed subnets on a
switch.
58
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
OSPF virtual linksmaximum number of
supported OSPF virtual links.
All platforms with Core license or above
32
OSPFv3 areasas an ABR, the maximum
number of supported OSPFv3 areas.
All platforms with Core license or above
16
OSPFv3 interfacesmaximum number of
OSPFv3 interfaces.
BlackDiamond 8800 series
256
BlackDiamond 10808
384
BlackDiamond 12800 series
256
Summit X450
128
Summit X450a
128
Summit X650
128
BlackDiamond 8800 series
64
BlackDiamond 10808
128
BlackDiamond 12800 series
128
Summit X450
64
Summit X450a
64
Summit X650
64
OSPFv3 virtual linksmaximum number of
OSPFv3 virtual links supported.
All platforms with Core license or above
16
OSPFv3 external routesrecommended
maximum number of external routes.
BlackDiamond 8800 series
10,000
BlackDiamond 10808
60,000
BlackDiamond 12800 series
50,000
Summit X450
10,000
Summit X450a
10,000
Summit X650
10,000
BlackDiamond 8800 series
6,000
BlackDiamond 10808
6,000
BlackDiamond 12800 series
6,000
Summit X450
3,000
Summit X450a
3,000
Summit X650
3,000
BlackDiamond 8800 series
1,024
BlackDiamond 8800 c-series
2,048c
BlackDiamond 10808
12,000
BlackDiamond 12800 series
12,000
BlackDiamond 20808
3,700
Summit X150
500d
Summit X250e
500d
Summit X350
500d
Summit X450
1,024
Summit X450a
1,024
Summit X450e
500d
Summit X650
2,048
OSPFv3 neighborsmaximum number of
OSPFv3 neighbors.
OSPFv3 inter- or intra-area routesrecommended
maximum number of inter- or intra-area routes.
PIM snoopingmaximum number of (S,G)
entries programmed in the hardware (IP
multicast compression disabled).
ExtremeXOS 12.2.2 Installation and Release Notes
59
Limits
Metric
Product
Limit
PIM snoopingmaximum number of (S,G)
entries programmed in the hardware (IP
multicast compression enabled).
BlackDiamond 8800 original
2,000d
BlackDiamond 8800 a-series
2,000d
BlackDiamond 8800 c-series
6,000d
BlackDiamond 8800 e-series
500d
Summit X150
500d
Summit X250e
500d
Summit X350
500d
Summit X450
2,000d
Summit X450a
2,000d
Summit X450e
500d
Summit X650
6,000d
BlackDiamond 8800 series
1,024
BlackDiamond 8800 c-series
2,048c
BlackDiamond 10808
12,000
BlackDiamond 12800 series
12,000
BlackDiamond 20808
3,700
Summit series
1,024
Summit X650
2,048
BlackDiamond 8800 series
1,024
BlackDiamond 8800 c-series
2,048c
BlackDiamond 10808
15,000
BlackDiamond 12800 series
15,000
BlackDiamond 20808
3,700
Summit series
1,024
Summit X650
2,048
PIM (maximum interfaces)maximum number of
PIM active interfaces.
All platforms
256
PIM (maximum interfaces)maximum number of
PIM snooping enabled interfaces.
All platforms
256
Policy-based routing (PBR) redundancy
maximum number of flow-redirect and nexthops
per each flow-direct.
All platforms
32
Private VLANsmaximum number of
subscribers. Assumes a minimum of one port
per network and subscriber VLAN.
BlackDiamond 8800 a-, c-, and e-series
PIMmaximum routesmaximum number of
(S,G) entries installed in the hardware.
PIM-SSM (maximum SSM routes)maximum
number of (S,G) entries installed in the HW
with PIM SSM configuration.
with eight modules of 48 ports
383
BlackDiamond 10808
1,400
BlackDiamond 12800 series
1,400
Summit X450a and X450e, 24 port
with two-port option card
without option card
25
23
Summit X450a and X450e, 48 port
with two-port option card
without option card
Summit X650
60
49
47
23
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
Private VLANsmaximum number of private
VLANs with an IP address on the network
VLAN.
All platforms
512
Private VLANsmaximum number of private
VLANs in an L2-only environment.
All platforms
2,046
Provider Backbone Bridging-Traffic Engineering
(PBB-TE)maximum number of static MAC
binding entries.
BlackDiamond 10808
MSM-1
MSM-1XL
98,000
100,000
BlackDiamond 12800 series
MSM-5
MSM-5R
MSM-6R
49,000
100,000
100,000
Route policiessuggested maximum number of
lines in a route policy file.
All platforms
10,000
RIP-learned routesmaximum number of RIP
routes supported without aggregation.
BlackDiamond 8800 series
10,000
BlackDiamond 10808
10,000
Summit X250e
3,000
Summit X450
3,000
Summit X650
10,000
BlackDiamond 8800 series
256
BlackDiamond 10808
384
Summit X250e
128
Summit X450
128
Summit X650
256
BlackDiamond 8800 series
3,000
BlackDiamond 10808
5,000
BlackDiamond 12800 series
5,000
Summit X250e
1,500
Summit X450
1,500
Summit X650
3,000
BlackDiamond 10808
32
BlackDiamond 12800 R-series
32
BlackDiamond 20808
512
BlackDiamond 10808
400
BlackDiamond 12800 R-series
400
BlackDiamond 20808
400
BlackDiamond 10808
2,000
BlackDiamond 12800 R-series
2,000
BlackDiamond 20808
2,000
BlackDiamond 10808
4,000
BlackDiamond 12800 R-series
3,000
BlackDiamond 20808
4,000
RIP interfaces on a single routerrecommended
maximum number of RIP routed interfaces on a
switch.
RIPng learned routesmaximum number of
RIPng routes.
RSVP-TE interfacesmaximum number of
interfaces.
RSVP-TE neighborsmaximum number of
neighbors per interface.
RSVP-TE ingress LSPsmaximum number of
ingress LSPs.
RSVP-TE egress LSPsmaximum number of
egress LSPs.
ExtremeXOS 12.2.2 Installation and Release Notes
61
Limits
Metric
Product
Limit
RSVP-TE transit LSPsmaximum number of
transit LSPs.
BlackDiamond 10808
2,000
BlackDiamond 12800 R-series
1,500
BlackDiamond 20808
2,000
BlackDiamond 10808
1,000
BlackDiamond 12800 R-series
1,000
BlackDiamond 20808
1,000
BlackDiamond 10808
1,000
BlackDiamond 12800 R-series
1,000
BlackDiamond 20808
1,000
BlackDiamond 10808
64
BlackDiamond 12800 R-series
64
BlackDiamond 20808
64
Spanning Tree (maximum STPDs)maximum
number of Spanning Tree Domains on port
mode EMISTP.
All platforms
64
Spanning Tree PVSTmaximum number of port
mode PVST domains.
All platforms
128
Spanning Treemaximum number of multiple
spanning tree instances (MSTI) domains.
All platforms
64
Spanning Treemaximum number of VLANs per
MSTI.
All platforms
500
Spanning Treemaximum number of VLANs on
all MSTP instances.
All platforms
1,000
Spanning Tree (802.1d domains)maximum
number of 802.1d domains per port.
All platforms
Spanning Tree (number of ports)maximum
number of ports including all Spanning Tree
domains.
All platforms
2,048
Spanning Tree (maximum VLANs)maximum
number of STP protected VLANs.
dot1d
560
dot1w
560
SSH (number of sessions)maximum number of
simultaneous SSH sessions.
All platforms
Static MAC multicast FDB entriesmaximum
number of permanent multicast MAC entries
configured into the FDB.
BlackDiamond 8800 original series
256
BlackDiamond 8800 c-series
1,024
BlackDiamond 8800 a-series
1,024
BlackDiamond 8800 e-series
1,024
BlackDiamond 10808
1,024
BlackDiamond 12800 series
1,024
Summit X150
1,024
Summit X350 series
1,024
Summit X250e
1,024
Summit X450 original series
256
Summit X450e
1,024
Summit X450a
1,024
Summit X650
1,024
RSVP-TE pathsmaximum number of paths.
RSVP-TE profilesmaximum number of profiles.
RSVP-TE EROsmaximum number of EROs per
path.
62
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
Syslog serversmaximum number of
simultaneous syslog servers that are supported.
All platforms
TCAM entriesamount of entries available in
the lookup tables for Longest Prefix Match
routing lookups, learned MAC address, and
ACLs.
BlackDiamond 10808, MSM-1
128,000
BlackDiamond 10808, MSM-1XL
256,000
BlackDiamond 12800 series
49,000
BlackDiamond 12800 R-series
229,000
Telnet (number of sessions)maximum number
of simultaneous Telnet sessions.
All platforms
Virtual routersnumber of user virtual routers
that can be created on a switch.
BlackDiamond 8800 series
Not supported
BlackDiamond 10808
BlackDiamond 12800 series
BlackDiamond 20808
Summit X250e
Not supported
Summit X450
Not supported
Summit X650
Not supported
VLAN aggregationmaximum number of portVLAN combinations on any one super VLAN and
all of its sub VLANs.
All platforms
1,000
VLANsincludes all VLANs.
All platforms
4,094
VLANsmaximum number of ports.
BlackDiamond 12804
50,029
VLANs (Layer 2)maximum number of Layer 2
VLANs.
All platforms
4,094
VLANs (Layer 3)maximum number of Layer 3
VLANs.
All platforms
512
VLANs (maximum active port-based)number of
simultaneously active port-based VLANs.
All platforms
4,094
VLANs (maximum active protocol-sensitive
filters)number of simultaneously active
protocol filters in the switch.
All platforms
15
VLAN translationmaximum number of
translation VLANs. Assumes a minimum of one
port per translation and member VLAN.
BlackDiamond 8800 a-, c-, and e-series
with eight modules of 48 ports
383
BlackDiamond 10808
1,400
BlackDiamond 12800 series
1,400
Summit X450a and X450e, 24 port
with two-port option card
without option card
25
23
Summit X450a and X450e, 48 port
with two-port option card
without option card
49
47
Summit X650
23
VLAN translationmaximum number of
translation VLAN pairs with an IP address on
the translation VLAN.
All platforms
512
VLAN translationmaximum number of
translation VLAN pairs in an L2 only
environment.
All platforms
2,046
ExtremeXOS 12.2.2 Installation and Release Notes
63
Limits
Metric
Product
Limit
vMAN (maximum ACL rules for vMAN)maximum
number of ACL rules for vMAN.
BlackDiamond 10808
4,000
BlackDiamond 12800 series
4,000
VPLS: VCCV (pseudo wire Virtual Circuit
Connectivity Verification) VPNsmaximum
number of VCCV enabled VPLS VPNs.
BlackDiamond 10808
16
BlackDiamond 12800 R-series
16
BlackDiamond 20808
16
BlackDiamond 10808
60,000
BlackDiamond 12800 R-series
60,000
BlackDiamond 20808
100,000
VPLS: MAC addresses in a fully meshed VPLS
networkmaximum number of MAC addresses
learned by a switch in an evenly distributed
fully meshed VPLS network.
BlackDiamond 10808
100,000
BlackDiamond 12800 R-series
80,000
VPLS VPNsmaximum number of VPLS virtual
private networks per switch.
BlackDiamond 10808
2,000 pointto-point
BlackDiamond 12800 R-series
2,000 pointto-point
BlackDiamond 20808
500
BlackDiamond 10808
16
BlackDiamond 12800 R-series
16
BlackDiamond 20808
32
BlackDiamond 10808
2,000
BlackDiamond 12800 R-series
2,000
BlackDiamond 20808
2,000
VRRP (maximum instances)maximum number
of VRRP supported VLANs for a single switch.
All platforms (except BlackDiamond
20808) with Advanced Edge license or
above
128
VRRP (maximum VRID)maximum number of
unique VRID numbers per switch.
All platforms (except BlackDiamond
20808) with Advanced Edge license or
above
VRRP (maximum VRIDs per VLAN)maximum
number of VRIDs per VLAN.
All platforms (except BlackDiamond
20808) with Advanced Edge license or
above
VRRP (maximum ping tracks)maximum number
of ping tracks per VLAN.
All platforms (except BlackDiamond
20808) with Advanced Edge license or
above
VRRP (maximum ping tracks)maximum number
of ping tracks per VRRP Instance under 128
VRRP instances.
All platforms (except BlackDiamond
20808) with Advanced Edge license or
above
VPLS: MAC addresses in an H-VPLS network
maximum number of MAC address learned by a
switch in an evenly distributed hierarchical
VPLS
Note: Increasing the number of spokes per VPLS
will decrease the maximum number of MAC
addresses that can be learned.
VPLS peersmaximum number of VPLS peers
per switch.
VPLS pseudo wiresmaximum number of VPLS
pseudo wires per switch.
Hello interval: 100 milliseconds
Frequency: 3 seconds
Miss: 3
Hello interval: 1 second
Frequency: 3 seconds
Miss: 3
64
2
4
ExtremeXOS 12.2.2 Installation and Release Notes
Limits
Metric
Product
Limit
VRRP (maximum iproute tracks)maximum
number of iproute tracks per VLAN.
All platforms (except BlackDiamond
20808) with Advanced Edge license or
above
VRRPmaximum number of VLAN tracks per
VLAN.
All platforms (except BlackDiamond
20808) with Advanced Edge license or
above
XML requestsmaximum number of XML
requests per second.
BlackDiamond 8800 c-series with 100
DACLs
Note: Limits are dependent on load and type of
XML request. These values are dynamic ACL
data requests.
with 100 DACLs
with 500 DACLs
10
3
BlackDiamond 12800 series with MSM-6R
with 100 DACLs
with 500 DACLs
10
3
Summit X450a and X650
with 100 DACLs
with 500 DACLs
4
1
a. The table shows the total available; see the note included in PD3-77983510.
b. An ACL mask defines a unique match criteria and relative rule precedence. Masks are automatically generated based on
the contents of an access-list policy. Only adjacent rules within the policy that have identical match criteria will utilize
the same ACL mask. For this reason, it is advantageous to list all rules with the same match criteria together unless a relative precedence with other policy rules is required. Using VLAN-based or wildcard ACLs requires the ACL masks to be
allocated on every port in the system.
c. Applies only if all enabled BlackDiamond I/O modules are BlackDiamond 8800 c-series modules.
d. Effective capacity varies based on actual IP addresses and hash algorithm selected, but is higher for BlackDiamond
8800 c-series modules and Summit X650 switches compared to BlackDiamond 8800 a-series and e-series modules and
Summit X450a switches.
ExtremeXOS 12.2.2 Installation and Release Notes
65
Limits
66
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
This chapter describes items needing further clarification and behaviors that might not be intuitive. The
numbers shown in column one of the following tables are for internal reference and can be ignored.
This chapter contains the following section:
Open Issues on page 67
Known Behaviors on page 84
Resolved Issues in ExtremeXOS 12.2.2 on page 87
Resolved Issues in ExtremeXOS 12.2.1 on page 88
Open Issues
Following are the open issues for supported features in ExtremeXOS 12.2.2. They are organized into the
following sections:
Table 36: Platform-Specific and Feature PDs
PD Number
Description
General
PD4-624062541
Jumbo Frames Are Not Mirrored to Monitor Ports
Jumbo frames are not mirrored to monitor ports on Summit X650-24t switches when
one-to-many mirroring is configured.
PD3-131866114
LPM Hardware Forwarding Using IPv6 Routes With a Mask Length Greater Than 64
Bits is Not Supported
BlackDiamond 8800 series and Summit series switches do not support LPM hardware
forwarding using IPv6 routes with a mask length greater than 64 bits. As a result, IPv6
packets may be forwarded in hardware to a different next hop by using a route with a mask
length less or equal to 64. This occurs even though a route with a mask length greater
than 64 with the correct next hop is known in software, but not in hardware. The following
log message is logged when the first route with a mask length greater than 64 is added:
<Noti:HAL.IPv6FIB.Notice> MSM-A: vrId 2 dest 3218:: / 77 nexthop :
IPv6 routes w/ mask len > 64 not supported in HW. Packets may be
forwarded using less-specific routes.
PD4-491938681
Cannot Change Local Administrator Password When Logged in as RADIUS
Administrator
A user cannot change the password for a local administrator account when logged in using
a RADIUS administrator account.
PD4-489592307
DUT Not Sending icmp destination unreachable Message to Source
DUT is not sending an "icmp destination unreachable" message to the source when it
receives a jumbo packet with a "dont fragment" bit message. This applies to BlackDiamond
10800 and BlackDiamond 20808 switches only.
PD4-489359602
Conflicting LFS Alarms are Seen When Disabling Ports
Conflicting Link Fault Signal (LFS) alarms are shown when disabling local ports.
ExtremeXOS 12.2.2 Installation and Release Notes
67
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
PD4-489142320
One Gigabit Ports During Reboot
One Gigabit ports set to auto on flap twice during a switch reboot.
PD4-486972363
Detour LSP Not Signaled Regardless of Available Bandwidth Resources
Bandwidth for the detour Label Switched Paths (LSPs) are calculated from the point of
local repair (PLR) node to the egress node, and not from the PLR node to the merge point
(MP). Therefore, detour LSP is signaled only when there is enough bandwidth that is equal
to or greater than the requested bandwidth for the detour LSP from the PLR node to the
egress node.
PD4-313453484
One Gigabit Port Flaps Twice When Configuring Auto Off
A 1 Gigabit port link flaps twice when configuring auto off speed 1000 duplex
full. This does not occur when configuring auto on.
PD4-448603051
PIM VLAN Continues to Operate in SSM VLAN Even After Clearing the Configuration
The unconfigure pim vlan command clears (unconfigures) an SSM configuration on a
VLAN but the VLAN continues to operate in the SSM VLAN, even after running the
disable pim and enable pim commands.
PD4-470597781
Local VLAN with 32 IP Addresses is Down, Dynamic Route With Same IP Addresses
is Not Reachable
When a local VLAN with 32 subnet-mask IP addresses is down, the dynamic route with the
same 32 subnet-mask IP addresses is not reachable.
PD4-460892051
Installing Different Versions of ExtremeXOS and SSH Causes Error
Installing different versions of an ExtremeXOS image and an SSH image displays the
following error message:
Failed to install image- cannot read spec file" in the log
"upgrade failed installation:got error from installer DLL"
PD4-460157940
Neighbor Cache Entries Become Static When Disabling IPv6 Forwarding
Disabling IPv6 forwarding causes neighbor cache entries to become static.
PD4-464587012
MPLS Unicast Traffic is Stopped When PHP is Enabled on MPLS VLANs
All unicast traffic routed by MultiProtocol Label Switching (MPLS) is stopped when
penultimate hop popping (PHP) is enabled on all MPLS VLANs. Virtual Private LAN
Services (VPLS) traffic is not impacted.
PD4-438482720
Restart Hold Timer After Removing (*,G) Entry
When a (*,G) entry is removed, the hold timer should be restarted for the next maximum
hold time.
PD4-448681226
show l2stats Command Does Not Count ARP Packets to the CPU
The show l2stats command does not count address resolution protocol (ARP) packets
to the CPU, even though the packet goes to the CPU.
PD4-482808326
Saving a Configuration as default.xsf Configuration Displays Errors
When a configuration is saved as a default.xsf configuration, errors are seen when the
configuration comes up after running the unconfigure switch command.
PD4-467944506
Routes Not Learned Through RIPng After Port in Tunnel Source VLAN is Changed
From Tagged to Untagged
With IPv6-in-IPv4 tunnels, routes are not learned through RIPng after the port in the
tunnel source VLAN is changed from tagged to untagged or vice versa.
PD4-469889565,
PD4-274249122
68
False Link Occurs Before Remote Switch Fully Boots
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
If a Summit switch populated with an XGM2-2bt module is rebooted, a false link up is
seen on 10G links connected to the XGM2-2bt ports approximately 30 to 50 seconds
before the switch has fully booted.
PD3-210656503,
PD4-331224298
Log Filter With a Target Session Cannot be Deleted
A log filter configured with a target session cannot be deleted after logging out of a switch
and then logging back in.
PD3-190363671
Hot Swapping PSUs Generates an Error Message
The following error message is displayed while hot swapping PSUs:
Unable to read PSU-2 FRU data. Try reinserting PSU more quickly.
Workaround: Remove and reinsert the PSU quickly. Insert the PSU in a single, continuous
motion with a firm push.
PD3-207678214
User-Configured Banner Remains Active
The user-configured banner remains active when rebooting a switch without first saving the
configuration.
PD3-207576821
Upgrading the BootROM to the Minimum Version on an MSM-6R is Not Working
Correctly
Upgrading the BootROM 1.0.1.8 on an MSM-6R running ExtremeXOS 12.0.2.25 software
is not working correctly. If you run the install firmware command and then reboot
the switch, the BootROM version remains 1.0.1.8.
PD3-206179541
Most L3 Traffic Slow Path Forwarded if IP Route Compression is Enabled
Enabling IP route compression on a BlackDiamond 10808 or 12800 series switch that has
already reached the maximum IPv4 routing entries in hardware might cause slow path
forwarding for some of the L3 traffic.
PD3-202580681
Some L3 Traffic May Temporarily Be Slow Path Forwarded When IP Route
Compression is Enabled
Enabling IP route compression may cause temporary slow path forwarding for some of the
L3 traffic.
PD3-192821161
Maximum Number of Supported IPv4 and IPv6 Interfaces
For Summit X650, X450 a-series and e-series switches, and the BlackDiamond 8800
series of switches, the maximum number of supported IP interfaces is 512 (IPv4 and IPv6
combined). If there are more IP interfaces configured, the following log message is
displayed:
12/11/2007 06:06:14.73 <Info:HAL.VLAN.Info> Maximum # of IP
interfaces (512) already configured.
Could not add IP address
0x0A010101 mask 0xFFFFFF00
PD3-201570011
Relay Agent IP Address Should be Configured as the Trusted Server
When dhcp-relay is configured in a DHCP snooping environment, the relay agent IP address
should be configured as the trusted server. If the relay agent IP address is not configured
as the trusted server, DHCP responses are blocked.
PD3-132775269
Telnet Sessions Between Two Switches Causing Mount/Remount Problem
Telnet sessions between two switches using two windows causes one session to hang if
both sessions are edited and but only one session is saved.
BlackDiamond 10808 Switch
PD3-124124316
Unicast Routes with ECMP Enabled Causes Log Errors
ExtremeXOS 12.2.2 Installation and Release Notes
69
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
The following error messages are shown in the log when running 50,000 unicast routes
with ECMP enabled:
02/05/2007 15:38:37.89 <Warn:HAL.Sys.Warning> MSM-A: hal: Reached
maximum otp index allocation
02/05/2007 15:38:37.56 <Warn:HAL.Sys.Warning> MSM-A: Previous
message repeated 999 additional times in the last 1 second(s)
PD3-68165111
System Health Check Parity Walk Verification Function Should be Enabled
Various memory locations that are part of the forwarding and routing tables are parity
protected on BlackDiamond 10808 switches. The functionality should be turned on so that
faults are detectable.
PD3-41204902
Output for the "show platform ipv4mc group <group address>" Command Contains
an invalid Entry
The output for the show platform ipv4Mc group <group address> command
contains an invalid entry.
BD-10808.61 # show platform ipv4Mc g 239.255.255.1
Total Entries:27
Index
Type VrId
Port
Source Group PTI Vlan
004A6 -> 03E3A [3] - invalid
PD3-14127903,
PD3-13538171
Egress Mirror Packets are Being Sent to Mirror Port in Link Down State
Mirrored egress packets are being sent to the mirror port even when the port is in the link
down state.
BlackDiamond 12800 Series Switches
PD4-320452728
CLI Command Show an Intermittent Delay of 30 to 60 Seconds
Running CLI commands on a BlackDiamond 12800 series switch with an MSM-6R module
shows an intermittent delay of 30 to 60 seconds during command execution.
PD3-187808062
Switch Does Not Show Warning Message for Down Revision MSM and I/O Modules
A BlackDiamond 12800 series switch does not show a warning message on the console for
down revision MSM and I/O modules after initialization.
PD3-187808062
802.1P Precedence Support
Incoming 802.1P precedence is not supported when ports are used for vMAN.
PD3-125511903
System Fails with a Signal 10 Error When Running an MSM Failover
A system failure occurs with a signal 10 error when performing a run msm-failover
immediately after the backup MSM is in-sync
PD3-86738591
Traffic Queue Statistics are Incorrect when Switch is Configured
Traffic queue statistics are incorrect when a BlackDiamond 12800 series switch is
configured to work in H-QoS mode. Statistics counters are accurate when the switch is
configured in the PRI mode.
PD3-98333969
Disabling and Enabling a Port Can Take 30 Seconds for Port to Activate
During continuous FDB learning, disabling/enabling a port can take up to 30 seconds for
the port to activate.
BlackDiamond 20808 Switch
PD4-587169451
Running install firmware Command Generates Error Messages in EMS Logs
Running the install firmware command generates numerous error messages in the
Event Management System (EMS) logs.
PD4-528151231
70
System Fails When Configuring IGMPv3 Receivers and Streams
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
A BlackDiamond 20808 switch crashes when configuring 10,000 IGMPv3 receivers and
5,000 streams and then running the disable ports all and enable ports all
commands.
PD4-483661511
Hotswapping MSM Displays uC Failed Messages
Hotswapping an MSM displays numerous uC failed messages at the MSM console.
PD4-466153001,
PD4-466153053
Not All Learned IP ARP Entries are Sent
When configuring 20,000 learned IP Address Resolution Protocol (ARP) entries, only
8,000 IP hosts are sent.
PD4-461858543
Unable to Send Line Rate Multicast Traffic
In certain situations, a BlackDiamond 20808 is unable to send line rate multicast traffic.
PD4-462788985
MSM Failover With Multiple EAPS Domains Causes a Continuous Loop with IGMP
Traffic
An MSM failover from MSM-A to MSM-B with multiple Ethernet Automatic Protection
Switching (EAPS) domains causes a continuous loop with Internet Group Management
Protocol (IGMP) traffic.
PD4-458894821
Sending Bidirectional Line Rate Traffic Causes a Drop in Traffic Rate
Sending bidirectional line rate traffic between two pairs of ports causes a drop in traffic
rate.
PD4-413420051
Hot Swapping Multiple I/O Modules Causes Most Modules to be Stuck in a Failed
State
Hot swapping multiple I/O modules at one time causes most of the I/O modules to be
stuck in a failed state.
PD4-444211398
Hot Swapping Multiple I/O Modules During a Soft Reboot Causes an I/O Failure
Hot swapping multiple I/O modules during an MSM soft reboot causes an I/O failure.
PD4-444211374
MSM Failover and Hot Swapping I/O Modules Causes I/O Failure
An MSM failover performed with hot swapping multiple I/O modules causes an I/O failure.
PD4-463434121
Disabling and Enabling Primary Port Causes Traffic to Loop
Disabling and enabling a primary port multiple times causes traffic to continuously loop.
PD4-421365551
FDB Table Shows MAC Address as "Unknown"
When sending bidirectional L2 traffic between two ports, the FDB table shows the MAC
address as "unknown."
PD4-418743921
Booting Switch Takes Four Minutes after Disabling and Enabling XM-8XB Module
Booting a BlackDiamond 20808 switch with an XM-8XB module takes 4 minutes after
disabling and enabling the I/O slot.
Summit Family Switches
PD4-274249122
False Link Occurs Before Remote Switch Fully Boots
If a Summit switch populated with an XGM2-2bt module is rebooted, a false link up is
seen on 10G links connected to the XGM2-2bt ports approximately 30 to 50 seconds
before the switch has fully booted.
PD4-272143930
Port 49 LED Does Not Light When Link Up on Summit X350-48t Switch
The LED for port 49 of a Summit X350-48t switch does not light when an XGM2-2sf or
XGM2-2bt module links up. This also occurs on the front and back LEDs except for port
50, which lights.
ExtremeXOS 12.2.2 Installation and Release Notes
71
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
PD4-310814981
When Configuring a Set of ACLs, Performing a Save and a Reboot Generates an
Error
When configuring a set of ACLs on a Summit X450a-48t switch, the access control lists
are successfully applied, however, performing a save and a reboot generates an error.
PD3-204517991
Summit X250e-24X Combo Port Link May Come Up With the Correct Speed But in
Half-Duplex Mode
A Summit X250e-24X combo port link may come up with the correct speed but in halfduplex mode, even though the switch is configured as full-duplex mode when
autonegotiation is set to off on both sides of the link. For the link to come up in fullduplex mode as configured, you must disable and enable the port, or restart the port.
PD3-201233169
Port Does Not Come up After Disable/Enable or Reboot on Some Mitel IP Phones
A condition exists with some Mitel IP phones that are attached to an ExtremeXOS PoE
enabled platform that requires that you disable and enable inline power in order for the
phone to become active.
PD3-131375426
Autopolarity Does Not Work on Combo Ports
Configuring autopolarity does not work on the combo ports on the Summit family switches.
PD3-77711011
Slot Should Not be Included in show inline-power stats Command Output
The word slot should not be included in the output of the show inline-power
stats command.
PD3-77711042
Priority Column Should Not be Included in show inline-power configuration
Command Output
The Priority column should not display in the output of the show inline-power
configuration CLI command when running the command on a Summit X450-24p PoE
switch.
PD3-43606168
show log Command Output Filled with sFlow Receiver Missing Message
If sFlow does not have a collector configured using the configure sflow collector
command, the show log command generates the following messages:
08/23/2005 12:28:09.55 <Noti:sflow.debug.AddCntSmplFail> : Could
not add the counter sample for port 0:1020, as receiver is not
configured.
08/23/2005 12:07:49.55 <Noti:sflow.debug.AddCntSmplFail> : Previous
message repeated 61 additional times in the last 1200 second(s).
PD3-40266236,
PD3-40233121
Redundant Ports Not Correctly Moving to Other Ports in Load Sharing Mode
Traffic on load share ports configured as redundant ports incorrectly moves to other ports
in the load share group during link transition.
SummitStack
PD4-452191011
FDB Entries Not Shown in show fdb Output
FDB entries that are programmed in a hardware table are not shown in the show fdb
output in a stacking configuration when the front panel port flaps.
PD3-209191744
Link State May Not be Correct on a Redundant Port
After running the disable port all command on a switch that is configured with a
redundant port, the link state may not always be correct.
PD3-209191768
Some Port LEDs May Light Green Even Though Ports are Not Up
After running the disable port all command on a SummitStack, some port LEDs may
sometimes light green even though ports are not up.
72
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
PD3-204744742
Ping in VR-Mgmt in SummitStack Displays Node Address Instead of MAC Address
IPv6 neighbor-discovery in a management VLAN in a SummitStack resolves to the node
address of the stack master, instead of the stack MAC address.
ACL
PD4-506754505
Dynamic Egress ALCs Set to Deny All Traffic, Traffic Still Hits ARP Reply Counter
When creating a dynamic egress ACL to deny all traffic, the traffic still hits the address
resolution protocol (ARP) reply counter but not denying the packets.
PD4-465744039
ACL Counters Not Hitting IGMP Packets
Access Control List (ACL) counters are not hitting the Internet Group Management Protocol
(IGMP) packets.
PD3-192175421
Installing a Policy File May Generate an Error Message
The following error message is displayed when installing a policy file with more than 4,096
rules:
Error: Unable to bind traffic queue tq4095 to port 1:1.
PD3-127190211
VLAN ACLs Do Not Work When vMAN Ethertype is Set to 0x8100
Using a BlackDiamond 10808 or a 12800 series switch, VLAN ACLs do not work when a
vMAN EtherType is set to 0x8100. Incoming traffic is not matched against the rules in the
ACL policy file and the traffic is forwarded without applying the matched rule in the policy
file.
PD3-118223441,
PD3-57946832,
PD3-26612201,
PD3-24794592
Before Changing a VLAN Tag, Unconfigure all ACLs Applied to the VLAN
Before changing a VLAN tag, make sure you unconfigure all the ACLs applied to the VLAN.
Also, after changing the tag, reconfigure the ACLs to be applied on the VLAN.This applies
to BlackDiamond 10808 and 12800 series switches only.
PD3-126824622
IPv6 Protocol ICMP Should Not be Allowed
If an IPv6 address is included in a configuration, use ICMPv6 for the protocol. ICMP (IPv4)
should not be allowed.
PD3-28320363
Invalid Encapsulate Value for IPv6
In IPv6, the encapsulate value is next header, which is not currently a valid attribute.
BGP
PD4-588273813
$ Character is Not Working as a Regex Match Condition
The $ character is not working as a regex match condition when used in the show bgp
routes as-path command.
PD3-209442785
Static Multicast Route Will Not be Exported Using MBGP.
Static multicast routes are not exported using MBGP. However, a static unicast route can
be exported using MBGP.
CLEAR-Flow
PD4-278443631
CLEAR-Flow Commands Display on Platforms That Do Not Support This Capability
CLEAR-Flow commands display on platforms that do not support this capability, including
the Summit X150, X250, X350, and X450e series switches, as well as BlackDiamond
8800 non-c-series switches.
CLI
ExtremeXOS 12.2.2 Installation and Release Notes
73
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
PD3-71725881
Timezone/DST Name Truncates at Seven Characters
When configuring an optional name for the time zone/DST, the time zone name truncates
at seven characters. The system default is six characters.
PD3-57182431
RX Align Counter is Not Incremented
For the incoming traffic with alignment errors, the "RX Align" counter in the output of the
show ports <port number> rxerrors command is not incremented. Instead the
"RX CRC" counter is incremented.
PD3-57182431
upload configuration Command Contains RIP Configuration Commands
The upload configuration CLI command contains RIP configuration commands in
spite of there not being a RIP VLAN.
Control Protocols
PD3-125288233
MSTP Fails to Converge when Ethernet Type is 0x8100
MSTP fails to converge when a vMAN Ethernet type is set to 0x8100 on a BlackDiamond
12800 series switch.
Diagnostics
PD4-285686375
EEPROM Error Message Appears in Log After Upgrade
After upgrading to the latest ExtremeXOS 12.1.2.17 image, the following EEPROM error
message appears in the log:
07/03/2008 12:30:03.72 MSM-A: MSM-B card eeprom checksum failed.
0xb97 != 0xb96
PD3-203116541
MSM A and MSM B May Display EEPROM Checksum Failed Error
Following EEPROM checksum failed error messages may be seen in the syslog:
MSM-B card eeprom checksum failed. 0xb8a != 0xb89
MSM-A card eeprom checksum failed. 0xb66 != 0xb65
Backplane eeprom checksum failed. 0xd71 != 0xcd5
EAPS
PD4-471892924
Restarting EAPS May Show an Error Message
Restarting an EAPS process on a controller and partner may show the following error
message on a console:
BD-8806.80 # restart process eaps
Step 1: terminating process eaps gracefully ...
Step 2: starting process eaps ...
Restarted process eaps successfully
BD-8806.81 # ERROR:VmgrProtocolIfRegister protoId:0 numIf:1
ERROR:VmgrProtocolIfRegister protoId:0 numIf:3
ERROR:VmgrProtocolIfRegister protoId:0 numIf:1
PD4-326832374
Streams Are Flooded in All Active Ports for the Temporary Flood Duration
Streams are flooded in all active ports for the temporary flood duration after running the
restart ports all command because a kill entry is not getting installed.
PD3-104885349
Traffic Loss Occurs When a Shared Link Comes Up
When traffic is running between shared links, FDB entries are incorrectly learned on
BlackDiamond 10808 and BlackDiamond 12804 switches. Traffic loss occurs until the
incorrectly learned FDB entries age out.
PD3-97153785
If Multiple Shared Links are Down, a Loop is Created
In a specific EAPS topology, if multiple shared links are down, a loop is created.
74
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
PD3-54870537,
PD3-45729158
EAPS with Load Sharing Enabled/Disabled Causes Control Packets to be Received
on Port
Misconfigured EAPS control VLAN ports may not be detected, causing EAPS PDUs to be
accepted into the system even though they were received on an incorrect port.
ESRP
PD4-464792522
Load-Shared Ports in Host Attach Configurations are Deleted Without Warning
When Sharing is Disabled
A load-shared port in a host attach configuration is deleted without warning or error when
sharing is disabled on the port.
PD4-295424750
Running ESRP on Two Switches Causes the ESRP Domain on One Switch to
Remain in a Pre-Master State
Running ESRP on two switches causes the ESRP domain on one switch to remain in a premaster state and the neighboring switch to become the master. This issue is seen when
active ports are increased on both the master and slave switches at the same time.
PD3-52741820
Disabling a Shared Port Makes the ESRP Port Restart configuration disappears
Disabling a shared port results in the ESRP port restarting and the configuration
disappearing.
IGMP
PD4-443083317
Kill Entry is Installed in EAPS Transit Switch
A kill entry is installed in an Ethernet Automatic Protection Switching (EAPS) transit switch
and temporary flooding is not happening for unknown traffic.
IP Routing Protocols
PD3-132508261
MTU Size for a VLAN is Not Configured
When issuing the enable jumbo-frame port all command on a BlackDiamond
8800, the MTU size for the VLAN is not configured. Sending 5,000 byte traffic works
correctly. However, if you disable jumbo-frames on the egress port the error message
Packet too big is displayed.
IPv6 Unicast
PD3-139714881
Info Level Messages in Log When Configuring Link Aggregation on VLAN
Associated with IPv6 Tunnel
The following info level messages appear in the log when link aggregation is configured on
a VLAN associated with an IPv6 6-to-4 tunnel:
05:01:49.04 <Info:HAL.VLAN.Info> MSM-B:
pibIPv6InstallTunneledLinkLocalFilter: Could not install filter
unit 12, Entry exists
04/24/2007 05:01:49.05 <Info:HAL.VLAN.Info> MSM-B:
pibIPv6InstallTunneledLinkLocalFilter: Repaired filter unit 12
These messages do not affect the operation of the switch.
IS-IS
PD3-190952336
Graceful Restart for IS-IS May Fail for the Entire Node
When one or more point-to-point interfaces are present on a router with IS-IS graceful
restart enabled, the graceful restart may fail for the entire node.
Workaround: Do not use point-to-point links if graceful restart is also used.
PD3-183234835
Graceful Restart Fails During "restart process isis"
ExtremeXOS 12.2.2 Installation and Release Notes
75
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
When one or more point-to-point interfaces are present on a router with graceful restart
enabled, the graceful restart may fail for the entire node.
Workaround: Do not use point-to-point links if graceful restart is also used.
Mirroring
PD4-350969111
Traffic is Not Forwarded When Adding Multiple Ports to Remote VLAN
With bidirectional traffic running, when adding multiple ports simultaneously to a remote
VLAN in an intermediate switch, traffic is not forwarded to the destination port.
Workaround: In an intermediate switch, add ports one by one to the remote VLAN.
PD3-202013298
Use Valid Value Range for Configuring Remote Tags
The valid value range for tags on remote-mirroring VLANs is 1 to 4,094. Use these values
for configuring the remote tag in the enable mirroring command.
PD3-202013281
Running the enable learning Command on Remote Mirroring VLANs May Cause a
Loss of Traffic
Learning is disabled by default on remote mirroring VLANs. Running the enable
learning command on those VLANs may cause a loss of remote mirrored traffic.
PD3-79867211
Mirroring Port Should Not be Allowed in Load Sharing in SummitStack Switches
If you create a load sharing group (trunk), then enable mirroring to a port, the software
allows you to add the mirroring port to the load sharing group.
PD3-28378521
Enabling Load Sharing on a Mirrored Port
Enabling load sharing on a port that is being mirrored causes the mirroring to stop.
MPLS
PD4-476351932
Performing a Restart on Spoke Node Causes LDP Peer to Go Down
Performing a restart process mpls or restart process ospf on a spoke node
in an HVPLS setup causes the Label Distribution Protocol (LDP) peer to go down with the
core node.
Workaround: Disable and enable MPLS.
PD4-475414370
Changing VPLS Mappings Causes Warning Messages
The following warning message is seen numerous times after changing VLAN Virtual Private
LAN Services (VPLS) mappings:
<Warn:MPLS.LDP.InternalProb>
PD4-475414342
VPLS Instances Stay in Ready State After Disabling/Enabling I/O Module
Most Virtual Private LAN Services (VPLS) instances stay in the Ready state after disabling
and enabling an I/O module.
Workaround: Disable and enable vpls all.
PD4-438179103,
PD4-385791701
MSM Failover on Ingress LSR Generates an Error Message
During an MSM failover on a ingress Label Switch Router (LSR), the following error
message in the displayed in the egress LSR:
MSM-A: 0x00002102-34 (327) Error occurred while querying the
Route.
09/22/2008 05:05:12.27 MSM-A: 0x00002102-34 (327) Error occurred
while querying the Route.
PD4-476351932
76
Performing a Restart on a Spoke Node in an HVPLS Setup Causes LDP Peer to go
Down
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
Performing a restart process mpls or a restart process ospf on a spoke node
in an HVPLS setup causes the Label Distribution Protocol (LDP) peer to go down with the
core node.
Workaround: Disable and enabled MPLS.
PD4-475414505
In Complex Topologies, LSP Connections Are Not Set Up
In more complex topologies, detour Label Switched Path (LSP) connections are not set up.
PD4-475414558
Changing LSR ID Causes all LDP Peers into NonExist State
Changing a Label Switch Router (LSR) ID causes all Label Distribution Protocol (LDP)
peers to go into a NonExistent state.
PD4-452308541
Secondary Pseudo Wire on ESRP Master Switch Not Accepted on Secondary Core
Node Pseudo Wire
The secondary pseudo wire on an Extreme Standby Router Protocol (ESRP) master switch
does not take the secondary core node pseudo wire after the primary core is rebooted.
PD3-208178928
Adding a Static Route With MPLS LSP
Adding a static route with an MPLS LSP may cause one of the following problems:
If a static route is added with an MPLS LSP whose transport setting is IP traffic
deny, the route is displayed with an invalid nexthop in the show iproute mpls
command output.
When a static route is added with an MPLS LSP that is not present in show iproute
mpls command output. For example, if there are 17 RSVP-TE LSPs to the same
destination, only 16 LSPs are eligible for carrying traffic because of a maximum ECMP
path limit of 16. Adding static routes with 17 LSPs results in the same observation.
PD3-157687121
Control Channel Type Router Alert Label Not Found in VCCV Packets
ExtremeXOS software uses Control Channel Type 2 to indicate router alert label mode. In
MPLS Router Alert Label mode, VCCV packets are encapsulated in a label stack. However,
the existing VCCV packets are sent like a stack without any PW label.
PD3-184989177
Enabling "LDP advertise static all" Removes Ingress LSPs Using Static Routes
When an LDP advertise static setting is set to all, all static routes are treated as
egress routes and egress LSPs are created. That is, a label is generated and advertised for
the static route. If the router at the end of the static route advertises a label matching that
static route, the LSP that was previously an egress LSP becomes a transit LSP. An ingress
LSP should also be created whenever a label is received, however, the ingress LSP is never
created.
Workaround: Do not use the LDP advertise static all configuration in situations
where an ingress LSP for a static route is required.
PD3-202184409
Adding/Deleting a LAG Sharing Port Changes the VLAN Status
Adding/deleting a LAG sharing port changes the VLAN status, which is causing an OSPF/
MPLS reconvergence.
PD3-139423053
RSVP-TE: LSP Summary Statistics Take Excessive Time to Calculate
Running the show mpls rsvp-te lsp summary command on a system configured
with 2,000 ingress LSPs takes an excessive amount of time to process.
PD3-121985381
Packets Larger than Configured Jumbo Frame Size are Forwarded
You cannot configure an IP MTU that is greater than the configured jumbo frame size.
However, when the jumbo frame size is configured using a smaller value than the IP MTU,
the configuration is accepted and the traffic is forwarded using the larger packet sizes.
PD3-118914021
Label Not Advertised for a Default Route in a Stub Area
ExtremeXOS 12.2.2 Installation and Release Notes
77
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
When an OSPF neighbor is configured between two LSRs and MPLS, and an LDP session
is configured between them, the ABR router advertises a default route to the internal
router. The default route is not mapped to a label in the internal router because the ABR
does not advertise the label
PD3-97057691
Mirrored RSVP Path Message Packets have Incorrect IP Header Checksums
When creating a mirrored port and viewing all traffic on a BlackDiamond 10808, the RSVP
path packets have incorrect checksums. These path messages occur on egress traffic from
the BlackDiamond 10808.
PD3-92653036
Egress LSPs using Advertised Implicit NULL Labels are Not Displayed
The show mpls label, show mpls rsvp-te label, and show mpls rsvp-te
lsp command output currently does not display egress LSPs using advertised implicit
NULL labels.
PD3-111544904
Explicit NULL Labels are Treated as Implicit NULL Labels
When a router receives an explicit NULL label, it is incorrectly treated as an implicit NULL
label, so rather than sending label 0, no label is sent.
PD3-93218551
Packets with Router Alert Label (0x00001) are Not being Forwarded
If either an egress or a transit LSP traverses the system, and an MPLS labelled packet
containing a router alert label is received, that packet is not forwarded.
PD3-93069318
VLANs Configured as Protocol any Should be Added to MPLS
Only VLANs configured as protocol any should be added to MPLS.
PD3-104731701
ExtremeXOS Does Not Send Back ICMP Responses for Traceroute through NonPipe Mode LSPs
When a traceroute is performed by setting the MPLS TTL to the IP TTL, ExtremeXOS does
not correctly send back an ICMP response. The result is * characters in the traceroute
for the routers that timed out. If a route is available, ExtremeXOS should attempt to send
back an ICMP response.
PD3-93630853
LDP Should Not Advertise Certain Label Mappings
LDP should not advertise a label mapping for a direct VLAN that does not have IP
forwarding enabled.
PD4-475414505
In Complex Topologies, LSP Connections Are Not Set Up
In more complex topologies, detour Label Switched Path (LSP) connections are not set up.
PD4-475414558
Changing LSR ID Causes all LDP Peers into NonExist State
Changing a Label Switch Router (LSR) ID causes all Label Distribution Protocol (LDP)
peers to go into a NonExistent state.
PD3-204793983
Egress Rate-Limit is Not Accurate in show port utilization Command Output
The egress rate-limit shown in the command output of the show port utilization
command is not correct.
PD3-203917264
Changing Explicit Route Object of LSP Does Not Clearly Show LSP Status
When an explicit route object (ERO) is changed for an LSP session that is up, the LSP that
is already up is not torn down. LSP stays up based on the older values. The retry count
continues to increment as LSP tries to come up with new values by querying routes every
30 seconds. This is done while the earlier LSP session is still active using the previously
configured values. See the retry count in the command output for the show mpls rsvpte lsp <lsp_name> detail command.
Multicast
PD4-573403233
78
igmpCacheSelf From the SNMP MIB Shows a Value of "False"
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
The MIB igmpCacheSelf from the SNMP MIB shows a value of "false" for reports that are
statically added to a switch.
PD4-521915271
IGMP Group Reports May Change from Version 2 to Version 3
The Internet Group Management Protocol (IGMP) group reports may occasionally change
from Version 2 to Version 3.
PD4-584325495
Multicast Traffic is Dropped After a Failover
Multicast traffic is dropped after running the restart port all and performing a
failover.
PD4-449743037
Group Entries Not Timing Out on MVR and Non-MVR VLANs
Group entries are not timing out on Multicast VLAN Registration (MVR) and non-MVR
VLANs even though snooping is disabled on the non-MVR VLAN.
PD4-478198808
After Disabling/Enabling PIM in a RP, Kill Entries Are Not Restored
After disabling and enabling Protocol Independent Multicast (PIM) in a rendezvous point
(RP), kill entries are not restored.
PD4-438482713
Start Entry Timer Based on (*, G) Egress Hold Time
When creating a (S,G) entry from a (*, G) entry, start the entry timer based on the (*, G)
egress hold time.
PD4-438482695
PIM Cache Timeout Should Not be Determined by Configured Join/Prune Interval
Protocol Independent Multicast (PIM) cache timeout should not be determined by the
configured join/prune interval on a VLAN.
PD4-438482687
When PIM Receives a Prune from Downstream Neighbor, Prune Hold Time is Not
Considered
When Protocol Independent Multicast (PIM) receives a prune from a downstream neighbor,
the prune hold time is not considered. This is the time for which the upstream neighbor
should hold the prune.
PD4-466821462
Certain MSDP Multicast Streams are Not Received When msdp sa-cache Entry is
Correct
Certain Multicast Source Discovery Protocol (MSDP) multicast streams are not received
when the msdp sa-cache entry is correct, but no Protocol Independent Multicast (PIM)
cache entries are received.
PD4-493683561,
PD4-449901506
Disabling Multicast Flooding May Result in ARP Requests Being Blocked
Disabling multicast flooding on a port may result in ARP requests being blocked.
PD4-339945634
Packets Ingressing on a Member of a Load-Sharing Group in the Mirrored VLAN
Should be Mirrored
When a load-sharing group is a member of a mirrored VLAN, packets ingressing on the
member of the load-sharing group in the mirrored VLAN should be mirrored. On the
Summit family switches and BlackDiamond 8800 modules, packets ingressing on member
ports other than the master port of the load-sharing group in the VLAN are not mirrored.
Workaround: Packets ingressing non-master ports in the load sharing group on the mirrored
VLAN can be mirrored by adding virtual port mirroring filters for each of the non-master
member ports.
PD4-308157118
Ingress Multicast Data Packets are Not Forwarded When vMAN Ethertype is 0x8100
When IGMP snooping is disabled, ingress multicast data packets are not forwarded when
vMAN Ethertype is 0x8100.
Workaround: Set the vMAN Ethertype to default (0x88a8).
ExtremeXOS 12.2.2 Installation and Release Notes
79
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
PD3-203759919
When Disabling and Enabling MSDP, the Peers Do Not Come up
After disabling and enabling Multicast Source Discovery Protocol (MSDP), the peers do not
come up.
Workaround: Run the disable msdp command followed by the enable msdp command
PD4-318846862
L3 Multicast Traffic in a VPLS vMAN is Forwarded Twice When the LSP is Changed
L3 multicast traffic in a Virtual Private LAN Services (VPLS) vMAN is forwarded twice when
the Label Switched Path (LSP) is changed to port sharing and is then changed back.
PD4-235071630
Direct Routes Are Not Stored in the Multicast Routing Table
Direct routes are not stored in the multicast routing table, which may cause problems
processing anycast rendezvous points (RPs).
PD3-128093864
MSDP SA Responses from non-RPF Peers are Not Processed
MSDP Source-Active responses received from non-RPF peers are not processed.
PD3-189399801
show pim rp-set Command Does Not Always Show All Rendezvous Points
The command output for the show pim rp-set command does not always show all the
Rendezvous Points for a multicast group.
Workaround: Do not configure the group address in the rp-list with a non-zero host portion.
PD3-200659931
Traffic May Take 210 Seconds to Recover After a Failover
In a worst case scenario, after a failover, traffic may take 210 seconds to recover on a
switch with a PIM DM configuration.
PD3-78144711
show ipstats Command Does Not Increment IGMPv3 Statistics
The show ipstats command does not increment IGMPv3 statistics.
PD3-79383551
IGMPv3 Report Record Type "5" Message Does Not Work Correctly
IGMPv3 Report Record type "5" does not work as expected when sent after a type "2" or a
type "4" message.
PD3-2841008
Multicast Packets Getting Dropped when Sent at Line Rate
With PIM, when small-sized multicast streams are ingressed at line rate, there is an initial
packet drop of 50% to 70%. This is seen on BlackDiamond 8800 and Summit X450
switches.
PD3-139683642,
PD3-16451411
show pim Command Only Counts Null-Registers
The output of the show pim command displays the cumulative counter for the PIM
register in/out and the register-stop in/out. When the ExtremeXOS switch is a first-hop
router, it sends out the real register first. After a particular mroute has been established,
PIM then periodically sends the null-register. The "Register out" field does not count real
registers; it only counts null-registers.
Network Login
PD4-575731921
Netlogin Clients Cannot Get IP Address From External DHCP Server
Network login clients are not able to get an IP address from an external DHCP server
through VR-Mgmt.
PD4-468366251
32 Character Usernames are Not Supported
A network login client is not authenticated if the username is 32 characters. Only 31
character usernames are supported, even if the user can create a 32 character username.
PD4-427423116
80
dot1x Client Authenticated on Local and RADIUS Servers
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
When a dot1x client is authenticated at multiple VLANs, the output of the show
netlogin port command shows the client is sometimes authenticated at the local
server and other times at a RADIUS server.
Note: This occurs when dot1x and MAC authentication are enabled on the port.
PD4-422918807
EDP MAC Address Seen as Client in Network Login Port
When an extension switch is connected between a DUT and clients, the Extreme Discovery
Protocol (EDP) MAC address is seen as the client in the network login port.
Network Services
PD3-166858162
Second Combo Port Does Not Come After Reboot if First Combo Port is Redundant
to Another Port
On a Summit X250e-24x switch, if one of the combo ports is redundant to a front panel
port, after rebooting, the second combo port does not come up if the primary port for the
SRP is active.
PD3-93829391
Configurations Using VR-Mgmt Interface as RADIUS Client IP Do Not Load
Configurations using a VR-Mgmt interface as a RADIUS client IP may not load at boot-up.
However, using an interface in VR-Default will load correctly.
PD3-67431351
Ingress Rate Limiting and Egress Rate Limiting are Mapping to Multiple Ports
Configuring an ingress traffic queue and an egress traffic queue association to multiple
ports in sequential order generates the following error:
Egress queue already associated to this ingress queue
Configuration failed on backup MSM, command execution aborted!
PD3-67727590
vMAN ID ACL Translations May Fail with Transmit Errors
Creating two sets of vMAN ACLs with 4000 entries each and performing a vMAN ID
translation on each ACL may generate the following error:
.....03/15/2006 17:57:28.84 <Info:pm.config.openingFile> MSM-B:
Loading policy RLL20k from file /config/RLL20k.pol
...03/15/2006 17:57:32.46 <Info:pm.config.loaded> MSM-B: Loaded
Policy: RLL20k number of entries 4002
.........Error in alloc txmi txmi 0x9f2 txmdi 0xffffffff
Error in alloc txmi txmi 0x9f4 txmdi 0xffffffff
Error in alloc txmi txmi 0x1102 txmdi 0xffffffff
Error in alloc txmi txmi 0x9f6 txmdi 0xffffffff
Error in alloc txmi txmi 0x9f8 txmdi 0xffffffff
PD3-62778911
Converging MVR with EAPS on a BlackDiamond 8800 Causes a Large Packet Loss
With MVR enabled on a BlackDiamond 8800, when the ingress port is on the egress-list
this causes a high volume of traffic loss.
PD3-64743301
Configuring a Meter Value Not Working Properly on a BlackDiamond 12804
When configuring a meter value using a large number, for example, 10,000 Gbps on a
BlackDiamond 12804 switch, the CLI accepts the command. However, when you run the
show meter command, an incorrect value is displayed.
OSPF
PD4-299382986,
PD4-217017923
Actual Inter-Area Route is Also Shown in Summary Route
When running the show iproute command, the actual inter-area route is also shown in
the summary route with a virtual link in the command output.
PD3-133427241
OSPF Filter Not Filtering All Routes
When an OSPF external filter is configured to deny routes, not all routes are being filtered.
ExtremeXOS 12.2.2 Installation and Release Notes
81
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
QoS
PD4-259174051
Denial of Service Protection Statistics Are Not Cleared
The clear counters command does not clear dos-protect statistics.
PD3-202190332
HQoS Allows Multiple Egress Queues to be Linked to a Single Ingress allowegress Queue
Configuring HQoS allows multiple egress queues to be linked to a single ingress allowegress queue.
PD3-129177287
If IRL-ERL Traffic Queue Mapping Extends to all Ports, Port Selection is Void
Create an ingress traffic-queue with allow egress shaping and create an egress
traffic-queue. Map the IRL to ERL on all ports. Send unidirectional traffic, which should
hit the IRL rule at ingress. The same traffic is visible to the ERL at the egress port without
selecting the designated port of VLAN/vMAN.
PD3-16578296
Disabling Load Sharing or Deleting Member Ports from a Trunk
The member ports of a trunk will retain the QoS profile configuration of the trunk (based
on the master port) after load sharing is disabled, or if a port is removed from the trunk.
RMON
PD3-12950492
clear counter Command Not Supported
Issuing the clear counter command might cause a high number to be displayed in
variables such as etherHistoryOctets, etherHistoryPkts, and etherHistoryTable.
ScreenPlay
PD3-204766394
Discrepancy Between ExtremeXOS CLI and ScreenPlay When Configuring Port
Speed and Duplex Settings
There is a discrepancy between the ExtremeXOS CLI and ScreenPlay when configuring port
speed and duplex settings. Using ExtremeXOS, you can configure a preferred speed, for
example, 1,000, and enable autonegotiation for the duplex settings. Using ScreenPlay, you
can only enable or disable autonegotiation without configuring a preferred speed.
PD3-111344472
Cannot Enable DHCP using WebUI
ScreenPlay allows you to configure DHCP but you cannot enable DHCP.
Security
PD4-315092889
32 Character VLANs Display an Error
VLANs with 32 characters displays an error message stating that a VLAN does not exist
when configuring limit-learning and lock-learning on the VLAN ports.
* X250e-24t.16 # configure ports 3 vlan
"v1111111112222222222333333333312" lock-learning
Error: VLAN v111111111222222222233333333331 does not exist!
PD3-205012219
Source IP Lockdown Dynamic Deny ACL Counter Not Working Properly
A source-ip-lockdown dynamic deny acl counter is not working properly and increments
valid traffic from a trusted client.
PD3-186939931
Ingress Mirroring is Not Working for DHCP Snooping When Snooping is Enabled
Ingress mirroring is not working for DHCP snooping when snooping is enabled on
BlackDiamond 12800 series switches. DHCP snooping works correctly when DHCP
snooping is disabled.
PD3-133763260
82
New Backup MSM Reboots Twice after Failover
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
A new backup MSM reboots twice after failover (run MSM-failover). The backup MSM
initially comes up correctly but is not in the "In SYNC" state. The MSM then reboots
without a core and comes up "In Sync" on a BlackDiamond 8800.
This problem does not occur consistently and should not affect data transmission. It is
recommended that you disable the notify function in the disable ip-security
anomaly-protection notify <log | cache | snmp> command to avoid potential
problems.
PD3-75120608
Unconfigure RADIUS and TACACS Does Not Reset Timeout Value to System Default
The unconfigure radius and unconfigure tacacs commands do not reset the
timeout value to the system default of 3 seconds.
PD3-74708933
RADIUS Authentication Do Not Work Correctly if Console Accesses the Backup
MSM
If you are configuring a BlackDiamond 10808 or BlackDiamond 8800 with RADIUS
authentication, when telnet or console access is through the master MSM, RADIUS
authentication works correctly. However, if console access is through the backup MSM,
RADIUS authentication does not work correctly and generates the following error message:
<Erro:AAA.RADIUS.serverNotInit> MSM-B: Authentication server for
Switch Management is not initialized
sFlow
PD3-205380274
sFlow Does Not Work in BVLANs and SVLANs
sFlow is not working on ports that are included in BVLANs, SVLANs, and occasionally
vMANs. sFlow can be enabled and configured for ports in BVLANs, SVLANs, and vMANs,
but nothing is sent to the sFlow collector.
SNMP
PD3-206632121
SNMP Query for extremePortQosStatsTable OID Returns a Value of 0
On a Summit X450a series switch, running an SNMP query for the
extremePortQosStatsTable object identifier returns a value of 0. This should return the
actual number of packets counted.
PD3-181304741
entPhysicalDescr MIB for XENPAK Modules Always Shown as XGMAfter inserting a XENPAK in a stack (XGM2-38n, XGM-38n) and performing an snmpwalk
on the entityMib entPhysicalDescr variable, XGM- is always shown, not the complete
module description.
PD3-39411271
icmpInMsgs Counter Displays only Incoming ICMP Packets
icmpInMsgs counter will display the incoming ICMP packets for VR-Default only.
Spanning Tree Protocol
PD4-492384091
IGMP Packets Loop When a Link Flap Occurs
When scaled to the maximum number of Rapid Spanning Tree Protocol (RSTP) domains
with EMISTP port mode, an IGMP packet loops for a short period of time when a link flap
occurs.
PD4-484447829,
PD4-344322578
Topology Becomes Unstable After an STPD Priority Change of Root Bridge
After a Spanning Tree Protocol Domain (STPD) priority change of an existing root bridge for
MSTP, the topology may become unstable and may not settle.
PD3-189927343
Temporary Loop Occurs When a Root Bridge is Taken Down
A temporary loop occurs when a root bridge is taken down by disabling all ports or
powering down the switch.
ExtremeXOS 12.2.2 Installation and Release Notes
83
Open Issues and Known Behaviors
Table 36: Platform-Specific and Feature PDs (Continued)
PD Number
Description
Stacking
PD3-136493921
AAA Services Do Not Become Available on Stacking Switch that has a Mismatched
License
If a switch is added to a stack whose master switch has a license level that is greater than
the level of the switch, the switch will fail. The complete condition can be seen using the
show slot detail command. In this state, the switch does not have AAA services
available. You will only be able to log into the switch using the failsafe account that was
last assigned to it. You must log into the switch to upgrade the license. If the switch is not
using the failsafe account configured on the stack, you can use the synchronize
stacking {node-address <node-address> | slot <slot-number>} command to
copy the failsafe account information from the master switch to the failed switch NVRAM.
You can also use the configure stacking license-level command to configure a
license level restriction on the entire stack and then reboot the stack. Once the stack is
restarted, there is no longer a license mismatch, enabling you to log into the switch and
upgrade the license. From the master switch, run the unconfigure stacking
license-level command to get the stack to operate at the desired license and then
reboot the stack.
PD3-126650411
Stackable Systems with Two or More Nodes may Experience Random VRRP Master/
Backup Flapping
A stackable system with two or more nodes may experience random VRRP master/backup
flapping issues after an MSM failover when configured with the maximum 128 VRRP
instances using the minimum advertisement interval of 100ms and maximum tracking
entries.
VRRP
PD3-202801091
VRRP Master Accepting Packets Addressed to a Virtual IP Address
A VRRP master should not accept or respond to packets addressed to a virtual IP address
associated with a virtual router if the master is not the IP address owner.
WAN PHY
PD3-101226461
WAN PHY show Commands Should Not be Applied to non WAN PHY Ports
When show wan-phy commands are run on non WAN PHY ports, the ports display the
headers. It should only display the error wan command is not supported on nonwanphy port 25.
Known Behaviors
The following are limitations in ExtremeXOS system architecture that will not be resolved.
Table 37: Platform-Specific and Feature PDs
PD Number
Description
General
84
PD3-197435644
LACP with address-based algorithms on L2 links is sending multicast traffic on multiple
links.
PD4-334148318
While broadcasting jumbo frames, the "Rx Pkt Bcast" counter in the show ports
statistics command output is not updated. This issue is not seen in non-jumbo frames.
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
Table 37: Platform-Specific and Feature PDs (Continued)
PD Number
Description
PD3-204965477
On a BlackDiamond 10808 switch or BlackDiamond 12800 series switches, before loading
an ASCII configuration on an unconfigured switch using the load script command,
delete the ports from the default VLAN using the configure default delete ports
all command and delete the ports from the default virtual router using the configure
vr vr-default delete ports <port_list> command.
PD3-204022938
If a MAC move occurs in an isolated subscriber VLAN without the link of the port going
down, the MAC address is not learned on the new port.
PD3-182634820
The thttpd process cannot be restarted using the start process or restart process
commands after the process exits preceded by a Thread thttpd ID does not respond log
message.
PD3-203517161
In a network where a BlackDiamond 8800 or a Summit X450 switch is forwarding packets,
occasional packet drop is observed on certain egress ports.
BlackDiamond 10808 Switch
PD3-175604157
A BlackDiamond 10808 switch with a dual speed copper/fiber SFP shows a link as active
even though a cable is not connected.
BlackDiamond 12800 Series Switches
PD3-206766987
Hitless upgrade is not supported for network login when upgrading from a previous version
of ExtremeXOS software to ExtremeXOS 12.1. If you attempt to perform a hitless upgrade,
all existing clients must be reauthenticated after a failover. Error messages such as
genesisNetLoginHandleGet: Port 0x08 NOT found, may be shown on the console and the
system log.
If a hitless upgrade is required, is it recommended that you globally disable network login
and re-enable it when the upgrade is complete.
PD3-131941899
Disabling and enabling a GM-20XT I/O module twice causes the slot to enter the Failed
state and displays the following error message.
Error Generic Error(-1) from HAL on CardExec POWER_OFF(10) for slot
1
PD3-130441271,
PD4-281640171
Traffic queues with metering are not applied correctly with large packets, such as 256, 512,
and 1,024. The traffic fluctuates between different rates when the packet size is above
200.
BlackDiamond 20808 Switch
PD4-450852428
Static and dynamic ACL entries with a match condition of protocol ospf and an action of
deny is not stopping the OSPF packets.
Summit Family Switches
PD3-190574171
Ports on Summit X450a and X450e series switches may stay in an active state even after
the cable is disconnected with certain QoS configurations.
ACL
ExtremeXOS 12.2.2 Installation and Release Notes
85
Open Issues and Known Behaviors
Table 37: Platform-Specific and Feature PDs (Continued)
PD Number
Description
PD3-77983510
Summit X450a and Summit X450e series switches and BlackDiamond 8800 a-series and eseries modules provide more powerful ACL capabilities. Because of this, the amount and
complexity of ACL rules will naturally impact the time needed to process and apply the ACL
rules to the switch. This will also impact switch bootup time. Access Control List limitations
fall into two areas: physical and virtual.
Physical LimitsSummit X450a and Summit X450e series switches:
The per-VLAN, wildcard (port any), and single-port access list installation limitations are
1024 rules for the Summit X450e and 2048 rules for the Summit X450a.
Physical LimitsBlackDiamond 8800 a-series and e-series modules:
The per-VLAN, wildcard (port any), and single-port access list installation limitations are
1024 rules for the e-series modules, and 2048 rules for the a-series modules.
Extreme Networks recommends that you configure ACLs as per-VLAN, wildcard, or singleport. If either of the following is true, you will have to configure ACLs with multi-port lists:
Your application requires that ports do not have a homogeneous ACL policy.
When BlackDiamond 8800 original series modules are operational in the same chassis, it
may be necessary to configure ACLs to specific port-lists instead of as wildcard or per-VLAN.
This is because the original series modules have smaller physical limits.
Virtual LimitsSummit X450a and Summit X450e series switches:
When configuring a multi-port ACL, use the following guideline. The total ACL count (as
calculated by ACL rules times ports applied to) should not exceed 48,000 total ACL rules.
For example, applying a 1,000 rule policy file to a 48 port multi-port list is supported
(1,000 rules * 48 ports in the list <= 48,000).
Virtual LimitsBlackDiamond 8800 a-series and e-series modules:
When configuring a multi-port ACL, use the following guideline. For any a-series or e-series
blade in the system, its total ACL count (as calculated by ACL rules times ports applied to)
should not exceed 48,000 total ACL rules.
For example, applying a 1,000 rule policy file to a 48 port multi-port list on an a-series
module on slot 1 and an e-series module in slot 2 is fine. Neither module exceeds the
48,000 total ACL rules.
Excessive boot times and CPU resource starvation can be seen with larger total rule counts.
If your application requires additional capacity, contact Extreme Networks.
Device Management
PD3-126243853
Using a key length of 4,096 in an SSL certificate causes high CPU utilization during HTTPS
sessions.
IP Routing Products
PD3-188555286
Not all shared static IP routes may be utilized following a link flap to one or more gateways
used by those static routes. For better resiliency when sharing static routes, configure static
ARP and FDB entries for each gateway used by the shared static routes. To do this, run the
following commands for each gateway:
configure iparp add <ip_addr> {vr <vr_name>} <mac>
create fdbentry <mac_addr> vlan <vlan_name> ports <port_list>
This affects BlackDiamond 8800 series and Summit X650, X450 a-series, and
X450 e-series switches only.
Multicast
PD4-373791509
86
Multicast VLAN Registration (MVR) is not working properly on Summit X650 platforms.
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
Resolved Issues in ExtremeXOS 12.2.2
The following issues were resolved in ExtremeXOS 12.2.2. The numbers shown in column one of the
following table are for internal reference and can be ignored. ExtremeXOS 12.1 includes all fixes up to
and including ExtremeXOS 11.1.4.4, ExtremeXOS 11.2.3.3, ExtremeXOS 11.3.4.5, ExtremeXOS 11.4.4.7,
ExtremeXOS 11.5.2.10, ExtremeXOS 11.6.4.11 through patch1-8, ExtremeXOS 11.6.5.3, and ExtremeXOS
12.0.3.16 through patch1-16, and ExtremeXOS 12.1.2.17. For information on those fixes, see the release
notes for the specific release.
Table 38: Platform-Specific and Feature PDs
PD Number
Description
Summit Family Switches
PD4-572876861
On some Summit X650 switches, the following log message is displayed:
< Warn:DM.Warning > Switch, Error 4: Fan #1 failed. Rpm 1927 is
out of operating range (from 4500 to 18000 rpm). (X650-24x(SS),
P/N: 800247-00-01, S/N: 0828G-00360, Rev: 1.0)
If this message persists after upgrading to ExtremeXOS 12.2.1.2-patch1-1, replace the fan
module.
PD4-385392901
Load shared traffic may be disrupted when enabling sharing with traffic on.
PD4-459420440
Flow control is not set properly on a Summit X650 switch.
PD4-491424381
An XGM2-2bt module causes a Summit X450 switch to display the following HAL port error
messages on a console:
<Erro:HAL.Port.Error> Xenpak on port 49 detected, unable to read
Oui, possible mdio read error
<Erro:HAL.Port.Error> summitIsXenpak2Operational: port 49 data=ffff
Diagnostics
PD3-204419978
Repeatedly running diagnostics on an MSM-48 or an MSM-G8x module may sometimes fail,
resulting in the error EEPROM memory test failed.
IGMP
PD4-385405101
Per-VLAN Internet Group Management Protocol (IGMP) snooping does not work when an IP
address is removed after saving and rebooting the switch.
MPLS
PD3-99318269
If the transmit bandwidth between two RSVP-TE neighbors is sufficient for a given LSP, but
the receive bandwidth is not, the LSP does not come up. The reason for the error is not
displayed in the show mpls rsvp-te lsp detail output.
PD3-188594038,
PD3-133340423
The penultimate hop popping (PHP) feature will not work correctly and may break Label
Distribution Protocol (LDP) adjacency with its neighbors. Currently, there is no workaround.
Multicast
PD4-487728925
After deleting a VLAN from a Multiple Spanning Tree Protocol (MSTP) domain and adding it
back, some multicast streams are lost. This also occurs when MSTP converges.
PD4-375155917
Multicast forwarding ignores an Internet Group Management Protocol (IGMP) join received
on a source VLAN port when there is another IGMP join on the same port in another PIM
enabled VLAN.
OSPF
PD4-443087741
An OSPF neighbor is not formed after a graceful restart of the OSPF process.
Security
ExtremeXOS 12.2.2 Installation and Release Notes
87
Open Issues and Known Behaviors
PD3-96212671
When DHCP snooping is enabled on a port in a VLAN in monitoring only mode (that is, with
the violation-action option set to none) and the switch is acting as a BOOTP relay,
DHCP packets are not relayed from the DHCP server on that port. As a workaround, the port
can be configured as a trusted-port (trusted for DHCP server packets) with DHCP snooping
enabled with a violation-action of drop-packet instead of none. This works the
same as setting the violation-action to none viz. The DHCP bindings database is
built up by monitoring DHCP traffic, but no rogue DHCP server traffic on that port is
dropped.
Spanning Tree Protocol
PD4-543585511,
PD4-332966643
Adding a VLAN to STP domain (s0) and then enabling STP domain (s0) generates the
following error:
Error: Incorrect carrier vlan configuration of port 2 in stp
domain s0.
If you enable STP domain (s0) first and then add the VLAN to the STP domain, the
configuration is accepted.
Workaround: Enable the STP domain first and then add the VLAN.
PD4-292225290
A large number of Spanning Tree Protocol (STP) BPDUs are generated when an MSTP
configured switch is connected to another switch that is using a default configuration.
Resolved Issues in ExtremeXOS 12.2.1
The following issues were resolved in ExtremeXOS 12.2.1. The numbers shown in column one of the
following table are for internal reference and can be ignored. ExtremeXOS 12.1 includes all fixes up to
and including ExtremeXOS 11.1.4.4, ExtremeXOS 11.2.3.3, ExtremeXOS 11.3.4.5, ExtremeXOS 11.4.4.7,
ExtremeXOS 11.5.2.10, ExtremeXOS 11.6.4.11 through patch1-8, ExtremeXOS 11.6.5.3, ExtremeXOS
12.0.3.16 through patch1-16, and ExtremeXOS 12.1.2.17. For information on those fixes, see the release
notes for the specific release.
Table 39: Platform-Specific and Feature PDs
General
PD4-254500398
Each IP address configured VLAN occupies two longest prefix match (LPM) hardware entries
instead of one. One entry is for the directly attached subnet, and the other is a host route
for the interface itself. This issue affects the recommended value for the configure
iproute reserved-entries command. See the ExtremeXOS 12.1.2 Command
Reference Guide for new usage guidelines.
PD4-354531953
The ExtremeXOS CLI allows you to set both the primary and secondary vMAN ethertypes to
0x8100.The ExtremeXOS 12.1 Concepts Guide states that the primary and secondary vMAN
ethertype can be set separately as long as both are not set to 0x8100.
PD4-360515775
A loss of traffic occurs when deleting a VLAN translation member VLAN containing loopback
ports.
Workaround: If you change or delete the loopback port, save and reboot the switch, or
disable and re-enable the slot.
88
PD4-484169508,
PD4-389339527
A netTools process crash occurs when processing incoming BOOTP Reply when User
Datagram Protocol (UDP) forwarding is enabled.
PD4-477175087,
PD4-415496669
The command output for the show configuration command includes enable vman
port after adding a port to a vMAN, which should not be included in the output.
PD4-445383070,
PD4-443927611
Traffic does not egress a 10G4Xc or 10G8Xc module with load sharing enabled.
PD4-459420391,
PD4-337044674
A defective Power over Ethernet (PoE) module may cause a switch to continuously reboot.
ExtremeXOS 12.2.2 Installation and Release Notes
Open Issues and Known Behaviors
PD4-486972003,
PD4-485801147
BlackDiamond 8806 and 8810 (a-,c-, or e-series) I/O modules may reset without an external
trigger. This problem occurs with ExtremeXOS 11.6, 12.0, and 12.1.
PD4-483940103,
PD4-348356921
FDB entries are not learned when limit-learning is enabled on a vMAN.
PD4-469804042
If you upgrade a non-active partition on an ExtremeXOS switch, the software automatically
moves the pointer to boot from the upgraded image before the image download is complete.
If the switch reboots during the upgrade/install, the switch will boot from a corrupt image,
resulting in a reboot loop.
PD4-444518321
Logging out of a CLI session established using SSH or Telnet may result in a
smbuf_xfer:terminal signal error followed by a switch reboot.
PD4-256803787,
PD4-328904792
When a software-controlled redundant port is configured with a fiber port as a secondary
port, the secondary port remains ready even after the primary port fails.
Workaround: Disable and enable the secondary port.
PD4-340843040
The XGM2-2bt runs hot in a Summit X350 switch. The switch contains two fan speeds: low
and high. The fans are controlled by hardware using a thermal sensor, which does not
measure the thermal output of the XGM2-2bt module.
BlackDiamond 10808 Switch
PD4-484934043
A BlackDiamond 10808 switch with an I/O module goes into a failed state and displays the
following error in the system log:
MSM-A: Slot-6 FAILED (1) L2 ping thru MSM-A timeout
MSM-A: Slot-2 FAILED (1) L2 ping thru MSM-A timeout
MSM-A: Slot-2 FAILED (1) Control link ping timeout
Summit Family Switches
PD4-459489323,
PD4-419725145
A Summit X250e-48t stack generates the following error message each time a user is
authenticated through MAC-based network login from the backup switch in the stack:
Unable to get vpif information IPmc add port.
PD4-316990197
On Summit X650 series switches, enabling jumbo frames on an ingress port and disabling
jumbo frames on the egress port does not cause IP fragmentation to occur on the L3 jumbo
frames.
ACL
PD4-376754432
When scaling ACLs by configuring 1,024 dynamic ACLs after configuring 1,024 ACLs using
a policy file, the system fails.
PD4-332583022
Ingress meter configuration changes are not effective until after the ACL policy file is
reinstalled.
PD4-377911268
When an ACL with counters configuration over a port range is scaled up, the watchdog times
out for the EPM application and a system failure occurs.
BGP
PD4-486115919,
PD4-331422601
A border gateway protocol (BGP) route can point to the wrong next-hop in a route table
when a default route is also learned by way of BGP in another scenario.
Diagnostics
PD4-384460740
Diagnostics fails during the run test loopback eth command when the management
port is set to 1 Gbps. This issue does not occur when the management port is set to 100
Mbps.
ELRP
PD4-477175023
When running the Extreme Loop Recovery Protocol (ELRP) between an ExtremeWare "e"
series switch and an ExtremeXOS switch, the ExtremeWare switch reports a checksum error.
IGMP
PD4-477175057,
PD4-409050568
When adding a static Internet Group Management Protocol (IGMP) group to a port not
belonging to the assigned VLAN, the switch silently drops the configuration without
displaying an error or warning message.
ExtremeXOS 12.2.2 Installation and Release Notes
89
Open Issues and Known Behaviors
MPLS
PD3-109748431
The show tech command shows erroneous MPLS CLI on a non-MPLS license system
running on a BlackDiamond 10808. MPLS should determine if the system is MPLS licensed
and only then show the CLI.
PD3-99318269
If the transmit bandwidth between two RSVP-TE neighbors is sufficient for a given LSP, but
the receive bandwidth is not, the LSP does not come up. The reason for the error is not
displayed in the show mpls rsvp-te lsp detail output.
Multicast
PD3-188594038,
PD3-133340423
The penultimate hop popping (PHP) feature will not work correctly and may break Label
Distribution Protocol (LDP) adjacency with its neighbors. Currently, there is no workaround.
PD4-378262291
The age of a group in a multicast stream entry is not updated when PIM and IP multicast
forwarding is enabled.
PD4-375155917
Multicast forwarding ignores an Internet Group Management Protocol (IGMP) join received
on a source VLAN port when there is another IGMP join on the same port in another PIM
enabled VLAN.
Network Login
PD4-461738253,
PD4-457325458
The enable netlogin ports mac command is not causing a switch to purge all FDBs
on the corresponding MAC-based network login enabled ports to enforce netlogin
authentication.
PD4-461738181,
PD4-441418181
Using MAC-based network login, the MAC address is authenticated on the first VLAN only.
The same MAC address stays in the unauthenticated state in all other subsequent VLANs.
Security
PD3-96212671
90
When DHCP snooping is enabled on a port in a VLAN in monitoring only mode (that is, with
the violation-action option set to none) and the switch is acting as a BOOTP relay,
DHCP packets are not relayed from the DHCP server on that port. As a workaround, the port
can be configured as a trusted-port (trusted for DHCP server packets) with DHCP snooping
enabled with a violation-action of drop-packet instead of none. This works the
same as setting the violation-action to none viz. The DHCP bindings database is
built up by monitoring DHCP traffic, but no rogue DHCP server traffic on that port is
dropped.
ExtremeXOS 12.2.2 Installation and Release Notes
You might also like
- CCNA 2 SRWE - Switching, Routing, and Wireless Essentials (Version 7.00) - Modules 1 - 4 - Switching Concepts, VLANs, and Inter-VLAN Routing Exam Answers - InfraExam 20210% (1)CCNA 2 SRWE - Switching, Routing, and Wireless Essentials (Version 7.00) - Modules 1 - 4 - Switching Concepts, VLANs, and Inter-VLAN Routing Exam Answers - InfraExam 202144 pages
- Junos Upgrade Using A USB Device On ACX Series RoutersNo ratings yetJunos Upgrade Using A USB Device On ACX Series Routers2 pages
- CSE 324 - OBE Course Syllabus - Sec D - EEENo ratings yetCSE 324 - OBE Course Syllabus - Sec D - EEE2 pages
- ExtremeXOS Feature License RequirementsNo ratings yetExtremeXOS Feature License Requirements22 pages
- Avaya Ethernet Routing Switching ImplementationNo ratings yetAvaya Ethernet Routing Switching Implementation76 pages
- Shortest Path Bridging (802.1aq) Technical Configuration GuideNo ratings yetShortest Path Bridging (802.1aq) Technical Configuration Guide263 pages
- Dell EMC Networking N-Series ConfiguracionNo ratings yetDell EMC Networking N-Series Configuracion1,766 pages
- Avaya Virtual Services Platform 7000 ConfigurationNo ratings yetAvaya Virtual Services Platform 7000 Configuration148 pages
- CDI-AOS-CX 10.4 Switching Portfolio Launch - Lab V4.01No ratings yetCDI-AOS-CX 10.4 Switching Portfolio Launch - Lab V4.01152 pages
- NN48500 518v4.3SwitchClusteringusingSMLTwithERS AVAYANo ratings yetNN48500 518v4.3SwitchClusteringusingSMLTwithERS AVAYA214 pages
- SPBM Fundamentals and Testing: Baystack PV100% (2)SPBM Fundamentals and Testing: Baystack PV96 pages
- SS110 ADM MAN 08 Deployment Monitoring 04292015No ratings yetSS110 ADM MAN 08 Deployment Monitoring 0429201535 pages
- Junos Enterprise Switching: Chapter 7: High AvailabilityNo ratings yetJunos Enterprise Switching: Chapter 7: High Availability57 pages
- Trend Micro TippingPoint Security Management System (SMS) High Availability Troubleshooting and Best PracticesNo ratings yetTrend Micro TippingPoint Security Management System (SMS) High Availability Troubleshooting and Best Practices14 pages
- Mastering Netscaler VPX: Learn how to deploy and configure all the available Citrix NetScaler features with the best practices and techniques you need to knowFrom EverandMastering Netscaler VPX: Learn how to deploy and configure all the available Citrix NetScaler features with the best practices and techniques you need to knowNo ratings yet
- Mastering The XMPP Framework: Develop XMPP Chat Applications for iOSFrom EverandMastering The XMPP Framework: Develop XMPP Chat Applications for iOS4.5/5 (2)
- Learning OpenStack Networking (Neutron), Second Edition: Wield the power of OpenStack Neutron networking to bring network infrastructure and capabilities to your cloudFrom EverandLearning OpenStack Networking (Neutron), Second Edition: Wield the power of OpenStack Neutron networking to bring network infrastructure and capabilities to your cloudNo ratings yet
- ScaN Skills Assess - OSPF - Student TRNG - Exam0% (1)ScaN Skills Assess - OSPF - Student TRNG - Exam15 pages
- 4.2.9 Example For Configuring Wlan Services On A Small-Scale Network (Ipv4 Network)No ratings yet4.2.9 Example For Configuring Wlan Services On A Small-Scale Network (Ipv4 Network)16 pages
- OpenScape SBC V7, Installation Guide, Issue 16100% (1)OpenScape SBC V7, Installation Guide, Issue 16174 pages
- Ccie Data Center Nexus Switching: Fabricpath0% (1)Ccie Data Center Nexus Switching: Fabricpath7 pages
- Quidway S3000-EI Series Ethernet Switches Command Manual (V1.04)No ratings yetQuidway S3000-EI Series Ethernet Switches Command Manual (V1.04)518 pages
- Cisco: Questions & Answers (Retail Version - Full Questions Set)No ratings yetCisco: Questions & Answers (Retail Version - Full Questions Set)27 pages
- 3.4.1.2 Skills Integration Challenge InstructionsNo ratings yet3.4.1.2 Skills Integration Challenge Instructions3 pages
